You do not have permission to delete messages in this group
Report message as abuse
Sign in to report message as abuse
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
Here is the report on a brand new (Sept 2015) Lenovo 440P with discreet Nividia.
Key note: Lenovo on the 440P model has removed the bios module that gives switchable control over the display adapters.
On all other models I have had you had options to always have switched/optimus and intel only disabling the discreet card. As they mainly cater to Windows they have allowed the control to go to the drivers thru OS. Thus you are stuck disabling it via Modset and blacklist.
As I have only run it off the USB drive I have not trying creating a USBVM.
Despite the issues with the lose of the display disable function in the bios I find Lenovo T series has one of the most option rich bios found in laptops. While I am not one to trust SED encrypt given its blackbox nature I have to use one for consulting per customer contract opsec requirements. Using mdsed to configure Opal 2 options for a linux option. The one thing I do like about the SED function is the secure erase feature (if its not been purposely broken). Ideally I am hoping to get a program written to allow a different password at the same prompt to script the secure erase function. Thus if made to give up a password I can wipe the whole drive.
I am wondering the opal 2.0 SED effects will have with AEM function but will not be getting around to that until I get the new laptop.
I was running the qubes off fast flash drive as without the bios control over the discreet card I was not sure if I was keeping it and have decided to swap it for a intel only version (The Nvidia cards are soldered onto the motherboard BTW)
I have run been in charge of Windows only shop for years so my Linux fu is very
very rough. But even though I can not recall how to much of anything from
a linux shell was able to simply use the commands listed in the old
https://www.qubes-os.org/doc/InstallNvidiaDriver/ how to.
After a reboot the weird unresponsive periods that happened every few minutes stopped.
But I did find that this does not fully disable the power to the nvidia card thus you are still running higher watt draw than needed.
It seems that whatever Lenovo has done in there powermanagment you need to actually manually enter acpi_calls for the kernel so that it will fully disable this card and get you back a good amount of power watts.
If you follow the comment posts about half way down the list you will find post :
Add rdblacklist=nouveau i965.modeset=1 nouveau.modeset to the GRUB_CMDLINE_LINUX_DEFAULT flags in /etc/default/grub, also for full KVM support (e.g. better brightness control etc.) I've found adding acpi_osi=\"!Windows 2012\" helps too.
run sudo update-grub
His next post states :
You may also need to force the disable on resume, create a /etc/pm/sleep.d/10_disable_nvidia:
I thought this could all be of possible use to many others than have issue with disabling their nvidia cards. The info at the various links should give info for what acpi calls need to be made to fully disable the cards in much the same way as if the bios itself had the module to do so.
BTW I would like to give a huge prop to the Lenovo customer support team I dealt with a Regina Goods out of North Carolina center. She was fantastic. First tech support found that the ones in charge of bios support would not that what would be 5-15mins to send me a bios flash with the added display module. They were also suprised it was not in the bios themselves. They immediately offered to take back the laptop and send a new one out to me without the nvidia card. I also got to keep this one till the other arrives and then rma it back to them.
Otherwise everything after initial install AND FULL UPDATING seems functional and without issues. Whonix was very irratic with stutterin effect trying to scroll in the browser etc. Updating took care of this. You must do this from the terminal. The auto update and scripted does not seem to work and I do believe is documented IIRC.
The only issue I seem to have which I am thinking maybe a issue of the fact its on a flash drive but feel I need to mention: For the initial Luk encryption password credentials box. If I enter my password immediately when it shows up on the screen and press enter the system ended up not loading and I end up at a cmd shell prompt to save the log file. But if I wait till the status bar shows its 3/4 finished it will load fine and I get the standard OS login and everything is fine from that point.
I have to give enormous props to Joanna, Marek,and rest of the those doing the dev work. Qubes 3.0 is a far cry from the the very rendition Joanna first released for experimentation. Its a huge jump forward. At this point its fully usable and configurable for an experienced Linux user or anyone willing to take some time to search thru the doc and group etc. the fact I have extremely spare contact with linux boxes (and not much prior)since Qubes was initially released and yet was able to load and configure this on a flash drive speaks volumes to all the hard work that has gone into this project and the OS's level of maturity.