ACPI quirks - acpi_osi="!Windows 2006" required on FSC Amilo notebooks to enable brightness keys
Peter Paul
They do not create any events for the OS but work even when in BIOS or GRUB, but not in Linux without said kernel parameter.
Userspace tools are able controlling brightness using standard methods regardless of any ACPI parameters, they only seem to affect the keys themselves.
Forum reports state that this is true for the whole Fujitsu (Simens) Amilo series, tested on Amilo Pi 2515.
___________________________________________________________
Preisknaller: WEB.DE DSL Flatrate fï¿œr nur 16,99 Euro/mtl.!
http://produkte.web.de/go/02/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Matthew Garrett
> The brightness control keys (Fn+F7 & Fn+F8) only work when adding this boot parameter.
> They do not create any events for the OS but work even when in BIOS or GRUB, but not in Linux without said kernel parameter.
> Userspace tools are able controlling brightness using standard methods regardless of any ACPI parameters, they only seem to affect the keys themselves.
What do you mean by "work"? Do you get any ACPI interrupts when you hit
the keys without the override parameter?
--
Matthew Garrett | mj...@srcf.ucam.org
Matthew Garrett
> Nope, neither with nor without acpi_osi="!Windows 2006", there is nothing in dmesg, no output in acpi_listen and no event in xev.
> I've compared the ACPI messages in dmesg with and without the parameter, the only change is the rather obvious
> ACPI: Deleted _OSI(Windows 2006)
And /proc/interrupts doesn't change when you hit those keys?
Peter Paul
> On Sat, Jan 09, 2010 at 08:14:59PM +0100, Peter Paul wrote:
>
> > I've compared the ACPI messages in dmesg with and without the parameter, the only change is the rather obvious
> > ACPI: Deleted _OSI(Windows 2006)
>
> And /proc/interrupts doesn't change when you hit those keys?
>
/proc/interrupts does change all the time
The only backlight related interrupt seems to be IO-APIC-fasteoi (9) - I
get 5-7 interrupts there when pressing either Fn+F8 (brightness down) or
Fn+F7 (brightness up), but only when brightness has not reached a
maximim level in the direction I want to go.
Brightness changes not.
When adding the acpi_osi parameter, I get 10 interrupts for brightness
every key press as long as brighness has not reached it's maximum resp.
minimum.
Brightness changes.
When using a userspace application like brightness-applet, I get >100
interrupts, brightness changes.
Every once in a while I also get some interrupts there without touching
anything (but brightness does not change)
CPU0 CPU1
0: 149418 0 IO-APIC-edge timer
1: 200 0 IO-APIC-edge i8042
8: 174 0 IO-APIC-edge rtc0
9: 3066 0 IO-APIC-fasteoi acpi
12: 7712 0 IO-APIC-edge i8042
14: 34368 0 IO-APIC-edge ata_piix
15: 0 0 IO-APIC-edge ata_piix
16: 0 0 IO-APIC-fasteoi uhci_hcd:usb2
18: 0 0 IO-APIC-fasteoi ehci_hcd:usb1,
uhci_hcd:usb6
19: 0 0 IO-APIC-fasteoi uhci_hcd:usb5
21: 0 0 IO-APIC-fasteoi uhci_hcd:usb3
22: 280 0 IO-APIC-fasteoi HDA Intel
23: 0 0 IO-APIC-fasteoi uhci_hcd:usb4,
ehci_hcd:usb7
27: 6472 0 PCI-MSI-edge i915
28: 8369 0 PCI-MSI-edge ahci
29: 2852 0 PCI-MSI-edge eth0
30: 47238 0 PCI-MSI-edge iwl3945
NMI: 0 0 Non-maskable interrupts
LOC: 30854 62124 Local timer interrupts
SPU: 0 0 Spurious interrupts
PMI: 0 0 Performance monitoring interrupts
PND: 0 0 Performance pending work
RES: 51052 49567 Rescheduling interrupts
CAL: 18 27 Function call interrupts
TLB: 3098 3001 TLB shootdowns
TRM: 0 0 Thermal event interrupts
THR: 0 0 Threshold APIC interrupts
MCE: 0 0 Machine check exceptions
MCP: 8 8 Machine check polls
ERR: 0
MIS: 0
Matthew Garrett
> /proc/interrupts does change all the time
> The only backlight related interrupt seems to be IO-APIC-fasteoi (9) - I
> get 5-7 interrupts there when pressing either Fn+F8 (brightness down) or
> Fn+F7 (brightness up), but only when brightness has not reached a
> maximim level in the direction I want to go.
Ok, so there's an ACPI event generated when you hit the keys. Can you
please run the acpidump command as root and send me the output?
--
Matthew Garrett | mj...@srcf.ucam.org
Peter Paul
> Ok, so there's an ACPI event generated when you hit the keys. Can you
> please run the acpidump command as root and send me the output?
I've attached the output
Matthew Garrett
Peter Paul
> It all looks like it should work. What do you have in /proc/acpi/video ?
/proc/acpi/video/:
GFX0
/proc/acpi/video/GFX0:
DD01 DD02 DD03 DD04 DD05 DOS info POST POST_info ROM
/proc/acpi/video/GFX0/DD01:
brightness EDID info state
/proc/acpi/video/GFX0/DD02:
brightness EDID info state
/proc/acpi/video/GFX0/DD03:
brightness EDID info state
/proc/acpi/video/GFX0/DD04:
brightness EDID info state
/proc/acpi/video/GFX0/DD05:
brightness EDID info state
But like I said, it is possible to adjust the brightness software side
(even without acpi_osi parameter), it's only the keys that don't work.
Matthew Garrett
Peter Paul
> Can you attach the output of
>
> grep . /proc/acpi/video
No, because there is none
Matthew Garrett
Peter Paul
> grep -r . /proc/acpi/video
/proc/acpi/video/GFX0/DD05/EDID:<not supported>
/proc/acpi/video/GFX0/DD05/brightness:<not supported>
/proc/acpi/video/GFX0/DD05/state:state: 0x1d
/proc/acpi/video/GFX0/DD05/state:query: 0x00
/proc/acpi/video/GFX0/DD05/info:device_id: 0x0005
/proc/acpi/video/GFX0/DD05/info:type: UNKNOWN
/proc/acpi/video/GFX0/DD05/info:known by bios: no
/proc/acpi/video/GFX0/DD04/EDID:<not supported>
/proc/acpi/video/GFX0/DD04/brightness:<not supported>
/proc/acpi/video/GFX0/DD04/state:state: 0x1d
/proc/acpi/video/GFX0/DD04/state:query: 0x00
/proc/acpi/video/GFX0/DD04/info:device_id: 0x0004
/proc/acpi/video/GFX0/DD04/info:type: UNKNOWN
/proc/acpi/video/GFX0/DD04/info:known by bios: no
/proc/acpi/video/GFX0/DD03/EDID:<not supported>
/proc/acpi/video/GFX0/DD03/brightness:<not supported>
/proc/acpi/video/GFX0/DD03/state:state: 0x1d
/proc/acpi/video/GFX0/DD03/state:query: 0x00
/proc/acpi/video/GFX0/DD03/info:device_id: 0x0003
/proc/acpi/video/GFX0/DD03/info:type: UNKNOWN
/proc/acpi/video/GFX0/DD03/info:known by bios: no
/proc/acpi/video/GFX0/DD02/EDID:<not supported>
/proc/acpi/video/GFX0/DD02/brightness:levels: 13 25 38 50 63 75 88 100
/proc/acpi/video/GFX0/DD02/brightness:current: 13
/proc/acpi/video/GFX0/DD02/state:state: 0x1f
/proc/acpi/video/GFX0/DD02/state:query: 0x01
/proc/acpi/video/GFX0/DD02/info:device_id: 0x0002
/proc/acpi/video/GFX0/DD02/info:type: UNKNOWN
/proc/acpi/video/GFX0/DD02/info:known by bios: no
/proc/acpi/video/GFX0/DD01/EDID:<not supported>
/proc/acpi/video/GFX0/DD01/brightness:<not supported>
/proc/acpi/video/GFX0/DD01/state:state: 0x1f
/proc/acpi/video/GFX0/DD01/state:query: 0x01
/proc/acpi/video/GFX0/DD01/info:device_id: 0x0001
/proc/acpi/video/GFX0/DD01/info:type: UNKNOWN
/proc/acpi/video/GFX0/DD01/info:known by bios: no
/proc/acpi/video/GFX0/DOS:DOS setting: <0>
/proc/acpi/video/GFX0/POST:<not supported>
/proc/acpi/video/GFX0/POST_info:<not supported>
/proc/acpi/video/GFX0/ROM:<TODO>
/proc/acpi/video/GFX0/info:Switching heads: yes
/proc/acpi/video/GFX0/info:Video ROM: no
/proc/acpi/video/GFX0/info:Device to be POSTed on boot: no