On Thu, Dec 04, 2008 at 07:15:39PM +0100, Matthias Heinz wrote: > 1) Backlight support: I cant control the brightness of the backlight with a > 2.6.28-rc7. It worked under mysterious circumstances with a 2.6.26. > Mysterious, because i had to use /proc/acpi/video/NVID/LCD/brightness to set > it, which obviously belongs to a nvidia driver (but theres nothing from > nvidia in there...) Do you have the i915 module loaded? NVID is simply the vendor's name for the ACPI object representing the video controller. > 2) Wifi LED: I dont know if this is a wifi driver issue or has to be > controlled by acpi. There's no standardised way for controlling LEDs via ACPI, so it's probably a wifi driver issue. > 3) The keyboard is not sending acpi events for several switches. It sends > (unknown) keycodes that have to be interpreted by the OS. > But there seems to be an option to change between acpi events and key events, > because i can control the backlight when grub is running and in the early > boot phase of the kernel. I dont know if this should be classified as > problem, but because X is catching all key events handling the wlan power > function is a problem of the actual user. The brightness keys will be trapped by the BIOS and brightness change code run in system management mode before ACPI is enabled, which only happens part-way through the Linux boot process. So it's normal for the behaviour to change at that point. It's also not unusual for hotkeys to be sent via the ekyboard - ACPI doesn't have any specified way for handling generic hotkeys other than the sleep and power buttons. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
