Bug 15301

Summary: display switch hotkey does not work anymore
Product: ACPI Reporter: Denis Laxalde (denis)
Component: Power-VideoAssignee: Zhang Rui (rui.zhang)
Status: REJECTED INVALID    
Severity: normal CC: acpi-bugzilla, rui.zhang
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 2.6.32.8 Subsystem:
Regression: Yes Bisected commit-id:
Attachments: acpidump of Dell D620

Description Denis Laxalde 2010-02-14 16:00:57 UTC
Bug originally reported in the Debian BTS:
    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540711

Display switch hotkey Fn+F8 stopped working.
It worked with 2.6.26 but not with 2.6.29 or higher (not tested with versions in between).

Hardware: Dell Latitude D620, nvidia graphic card GeForce Go 7300
Current system:
 - Kernel: 2.6.32.8 (Debian package)
 - nvidia-graphics-drivers 190.53
Comment 1 Zhang Rui 2010-02-22 06:21:39 UTC
using acpi_listen, can you receive any ACPI events when pressing the hotkey?
If no, can you receive any events in 2.6.26?
Comment 2 Denis Laxalde 2010-02-23 01:29:52 UTC
With 2.6.32, acpi_listen returns:
video/switchmode VMOD 00000080 00000000
video/switchmode VMOD 00000080 00000000

I cannot test with 2.6.26 anymore (ext4).
Comment 3 Zhang Rui 2010-02-23 01:42:06 UTC
please attach the acpidump output of your laptop.
Comment 4 Denis Laxalde 2010-02-23 02:14:45 UTC
Created attachment 25170 [details]
acpidump of Dell D620
Comment 5 Len Brown 2010-02-23 02:54:37 UTC
comment #2 says that the ACPI part of video switching is working --
we deliver the event.  ACPI is not responsible for actually
switching displays.  So it seems that this is an issue with
the X server and/or native (nvidia) device driver).
Comment 6 Denis Laxalde 2010-02-23 03:15:12 UTC
(In reply to comment #5)
> So it seems that this is an issue with the X server
> and/or native (nvidia) device driver).
That's also what the Debian maintainer thinks...
Comment 7 Zhang Rui 2010-02-23 07:25:11 UTC
(In reply to comment #2)
> With 2.6.32, acpi_listen returns:
> video/switchmode VMOD 00000080 00000000
> video/switchmode VMOD 00000080 00000000
> 
this is weird, I can not find the VMOD device in the acpidump you attached.
will you please make a double check that the laptop you get the acpidump output from is the one that you run the test on?

please run "lsof /proc/acpi/event" and kill all the processes that reading this file, and then run "cat /proc/acpi/event",
please attach the output when pressing the hotkeys.
Comment 8 Denis Laxalde 2010-02-23 12:34:54 UTC
(In reply to comment #7)
> will you please make a double check that the laptop you get the acpidump
> output
> from is the one that you run the test on?
There's no doubt, I only have one laptop.

> please run "lsof /proc/acpi/event" and kill all the processes that reading
> this
> file, and then run "cat /proc/acpi/event",
> please attach the output when pressing the hotkeys.
Sorry, this event file does not exist on my system...
Comment 9 Zhang Rui 2010-02-24 02:25:47 UTC
please set both CONFIG_ACPI_PROCFS and CONFIG_ACPI_PROC_EVENT in the kernel config, and rebuild your kernel.
does the problem still exist?
If yes, please do the test in comment #7.
Comment 10 Denis Laxalde 2010-03-06 02:49:03 UTC
Ok (sorry for the late reply), rebuilding the kernel with CONFIG_ACPI_PROC_EVENT solved the problem.
I guess it is actually nvidia's fault and they'll have to adapt to the new way of catching acpi events...