This is a dark spot. as long as acpi_call does not work reliably on most laptops there is no safe way to tell if it's working. For this reason I'm putting this as purely experimental state and not supporting it for now. Your issue was reported and is known on a variety of ASUS laptops. I'll recommend to read about acpi_call and their known-to-work laptops. BTW: Thanks!
- I think the higher Power consumption is caused by the X-Server that gets hung up (it hogs 100% of one CPU Core) when you switch off the Card via acpi_call. I've got the same issue here on a ASUS X53S, which also has a NVidia GT 540M.
- florianb 00:19, 1 August 2011 (CET)
- Try disabling the X server first or you will have some issues. If there is still a problem try the vga-switcheroo option.
- Samsagax 19:27, 31 July 2011 (EDT)
- I tried to reproduce the errors successfully
- 1. If you switch off the NVIDIA Card before you stop the bumblebee daemon (which starts/stops the 2nd X-Server) you get into trouble, the X process hogs 100% CPU, gets unkillable and the overall power consumption (in my case) goes from about 1500mA to 2100mA
- 2. If you only stop the bumblebee daemon without switching off the NVIDIA Card, power consumption goes from about 1500mA to 1800-1900mA (maybe user "thewall" only stopped the daemon without switching off the NVIDIA Card?)
- 3. If you switch off the NVIDIA Card (which is a GT 540M in my case) via acpi_call, power consumption goes down to 1200mA, which is quite nice *BUT* the Fan goes 100% some seconds after you switch it off.. this seems to consume about 50mA more power.. blah blah and first of all is totally annoying
- A guy in the ubuntu forum apparently already fixed 3) on similar hardware as i have, but i guess the differences are in detail, i'm trying to find it out.
- florianb 08:07, 1 August 2011 (CET)
- I'll try to release today the new model for nvidia driver, similar to the one of nouveau. That way power switching is made automatically and by means of vga-switcheroo by default. I have to remind you that acpi_call method calls are guessed and (in your case) they may be incorrect. Samsagax 10:42, 1 August 2011 (EDT)
- Okay, sounds nice. I'd really like to contribute something to your work, if there's anything i could do, let me know.
- florianb 10:37, 2 August 2011 (CET)
Multiple monitors with screenclone - wrong info
At the end of the manual it says "Take note of the position of the VIRTUAL display in the list of Outputs as shown by xrandr. The counting starts from zero, i.e. if it is the third display shown, you would specify -x 2 as parameter to screenclone", however, this was wrong information in my case; i had to specify -x 2 even though VIRTUAL was first in my xrandr call(and thus it should be -x 0, which only cloned my laptop display). Making a change that mentions this. Futile (talk) 21:29, 6 July 2013 (UTC)