Although this bug is marked as "fix released" I'm commenting this.
Some Asus and Samsung notebooks share ACPI features like hotkeys and both are supported
by the asus_laptop kernel module. This report here added an ACPI hotkey event for the Fn+F4
(video switch) combo on my Samsung P35 (ATI Radeon 9700 r300), but there is no effect to the key press.
The situation is as follows:
- key press
- /etc/acpi/events/asus-video
- /etc/acpi/videobtn.sh
- acpi_fakekey $KEY_VIDEOOUT
- KEY_VIDEOOUT maps to 227
- no reaction :(
Which application should handle this event in hardy? Where to look for more hints?
I've written some helper scripts, I can call manually, which efectively do:
xrandr --output VGA-0 --auto
xrandr --output LVDS --mode 1280x1024
xvattr -a XV_CRTC -v 1
or
xrandr --output VGA-0 --off
xrandr --output LVDS --mode 1400x1050
xvattr -a XV_CRTC -v 0
Why is there no general handler for this case? It's hard to switch video-out during run-time and
especially after resume, as there seems to be no automatisation.
Although this bug is marked as "fix released" I'm commenting this.
Some Asus and Samsung notebooks share ACPI features like hotkeys and both are supported
by the asus_laptop kernel module. This report here added an ACPI hotkey event for the Fn+F4
(video switch) combo on my Samsung P35 (ATI Radeon 9700 r300), but there is no effect to the key press.
The situation is as follows:
- key press events/ asus-video videobtn. sh
- /etc/acpi/
- /etc/acpi/
- acpi_fakekey $KEY_VIDEOOUT
- KEY_VIDEOOUT maps to 227
- no reaction :(
Which application should handle this event in hardy? Where to look for more hints?
I've written some helper scripts, I can call manually, which efectively do:
xrandr --output VGA-0 --auto
xrandr --output LVDS --mode 1280x1024
xvattr -a XV_CRTC -v 1
or
xrandr --output VGA-0 --off
xrandr --output LVDS --mode 1400x1050
xvattr -a XV_CRTC -v 0
Why is there no general handler for this case? It's hard to switch video-out during run-time and
especially after resume, as there seems to be no automatisation.
[Maybe related report is at bug #212790]