-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.0 Milestone #119
Comments
Also, the rework needed for the first point might be the right time to look at #18. |
Regarding changed behavior after advertisement of Windows 2013, this would mean that newer Windows versions cannot run on those machines either, can they? Maybe there is a BIOS update available or the approach is wrong. The current suspend logic in bbswitch aims to be as compatible as possible by powering it on before suspend. Unfortunately this possibly has adverse effects on the battery (though I have not verified this yet). The broken handles problem will probably remaing unfixed, it is a problem that needs to be addressed in the ACPI core of Linux. |
I have modified some parts of the code to make suspend reliable for P650SE(had battery drain problems while suspended). Anyway, as I've said, it is a workaround. To solve it in a elegant way we need to patch the kernel I guess. |
As pointed in #112 after a more thorough reading of it, there is at least a probable issue on PCIe port PM that should be handled somewhere in bbswitch or kernel, especially if it’s able to save around 2 W for every concerned laptop. |
@Lekensteyn in case a release can't be cut before the 25th of January, is there any patch that you think would be useful to include in the next Debian stable release? pm-rework etc. Consider that Debian 9 will ship with kernel 4.9 |
@bluca You can try the patches on the pm-rework branch until 5c7b3f5 (that is, w/o the audio devices patch). Only problem is that it is not much tested and I have no time to work on it in this month (January), sorry. (In particular, I do not think that this new version of bbswitch has been tested at all on the old models using DSM instead of PR3.) |
I have an old laptop (Latitude E5540 with 720m) and unfortunately testing doesn't look good. I see the problem already reported in another issue with the card refusing to change state from D3 and the nvidia kernel module failing to load (PM runtime for the card is reported as "bad" by powertop, which I think means off?). So I'll hold out the patches from Stretch to avoid regressions I think, and if I'm reading correctly in other issues on newer laptops 0.8 will still work fine with pm_runtime off, so there's a way to support both old and new models as far as I can see, is that correct? |
Yes, you’re almost right, because most laptops supporting the newer interface also support the older one. However, it’s not the case for some, e.g. #112. @Lekensteyn Whenever that’s needed, I’ve still have my old Asus laptop accessible, and being from 2009 or 10, it definitively represents the old category. ;) |
@bluca Can you link the specific issue you found? Some (most?) laptops should indeed still work with |
For the next release, that would probably deserve a 1.0 version number, I see three things that should be worked on:
Windows 2013
OSI since kernel 3.15 or 3.16. For some laptops (Thinkpad only?), this change the behaviour of the “_DSM
” function, and results in card not turned OFF (so no power savings) and sometimes other errors. Also, this revealed that we might also need to handle the pcie link powerstate.@Lekensteyn Will you have any time soon to look at this?
The text was updated successfully, but these errors were encountered: