On 13-12-17 21:09, Jeremy Cline wrote:
On 11/03/2017 04:59 AM, Hans de Goede wrote:
> On 01-11-17 20:34, Laura Abbott wrote:
>> I'm always a bit uneasy about enabling hardware power saving
>> since it rarely seems to be done correctly but as Peter pointed
>> out it's easy to revert if something goes wrong. Having the
>> endorsement of upstream is also good since it means they should
>> be responsive.
>> Enabling for 4.14 sounds like a good plan. Did you intend for
>> this to end up in stable releases on rebase?
> That was my original intention yes. But now that you explicitly
> ask I guess that we may want to hold off on that and just
> make the change for rawhide / F28. I will try to get the
> change committed to the master branch today (otherwise
> I will do it Monday). I will leave it up to you if you also
> make the change to the stable releases on rebase.
We ended up putting this in the 4.14 rebase and there were a few issues
reported on i686 and x86_64 so I've set it back to 0 on all arches
in F27 and F26. Hans, do you want to leave in on in Rawhide and see if
we can come up with some fixes or should I switch it to 0 there as well?
I would like to keep this as is for F28/rawhide, assuming that you've
made the change to only enable this on x86_64 there. IOW I think we
By disabling the power_saving / setting the option to 0 on i686,
those machines are so old that I don't want to spend too much
effort there, also the reported symptoms
And look further into fixing this for x86_64 for F28+.
I've just send a mail about fixing this to the alsa-devs,
and I've put you (Jeremy) in the Cc.