please attach the acpidump output. please apply this patch and see if it helps, http://patchwork.kernel.org/patch/17339/ thanks, rui On Mon, 2009-04-13 at 02:37 +0800, Niel Lambrechts wrote: > On 04/12/2009 06:14 PM, Henrique de Moraes Holschuh wrote: > > On Sat, 11 Apr 2009, Andrew Morton wrote: > > > >>> With latest git kernel, I'm no longer able to control my Thinkpad (W500) > >>> brightness, although I can still control the backlight, bluetooth etc. > >>> > > > > Niels, something just occourred to me. Is your problem the hotkeys, or the > > brightness control itself? Check /sys/class/backlight/*, please. What do > > you have in there? Does it work? > > > Hi Henrique, > > The directory is empty - this is when I used 2.6.30-rc1 (latest git) > from yesterday. I'll keep retrying with the latest git kernels though. > > The only additional observations I can provide is: > 1) pulling/plugging the power cord does actually have an effect on the > brightness. > 2) resuming form hibernate - Xorg is blank, until I simultaneously press > a keyboard key and touch the synaptics pad. But I have this problem in > 2.6.28/2.6.29 as well, and I guess it could either be vesafb or ACPI > related, as it also happened when I used s2disk in a console session > outside of X. > > In 2.6.29.1: > lrwxrwxrwx 1 root root 0 Apr 12 20:01 /sys/class/backlight/acpi_video0 > -> ../../devices/virtual/backlight/acpi_video0 > > which contains: > drwxr-xr-x 3 root root 0 Apr 12 20:01 ./ > drwxr-xr-x 3 root root 0 Apr 12 20:01 ../ > -r--r--r-- 1 root root 4096 Apr 12 20:02 actual_brightness > -rw-r--r-- 1 root root 4096 Apr 12 20:02 bl_power > -rw-r--r-- 1 root root 4096 Apr 12 20:02 brightness > -r--r--r-- 1 root root 4096 Apr 12 20:01 max_brightness > drwxr-xr-x 2 root root 0 Apr 12 20:02 power/ > lrwxrwxrwx 1 root root 0 Apr 12 20:01 subsystem -> > ../../../../class/backlight/ > -rw-r--r-- 1 root root 4096 Apr 12 20:01 uevent > > max_brightness = 15 and echoing values [0-15] to brightness controls it > as expected, or just using the standard thinkpad keys (Fn-Home to increase). > > If it is the hotkeys, make sure you either have the legacy ACPI events > > enabled in kconfig, or that you have something tied to the thinkpad-acpi > > input device (no, HAL doesn't do it _yet_, it just forwards the events to > > X.org)... > > > I'm not sure what provides the "glue", other than "it works" in 2.6.29.1 > and 2.6.28.9 with OpenSUSE 11.1 with xorg-x11-server-7.4-41.8. > > Would it help if I send the ACPI parts of my .config? These are based on > the default /proc/config.gz that comes with the distro. > > # Power management and ACPI > options > CONFIG_ACPI=y > > CONFIG_ACPI_SLEEP=y > > CONFIG_ACPI_PROCFS=y > > CONFIG_ACPI_PROCFS_POWER=y > > CONFIG_ACPI_SYSFS_POWER=y > > CONFIG_ACPI_PROC_EVENT=y > > CONFIG_ACPI_AC=m > > CONFIG_ACPI_BATTERY=m > > CONFIG_ACPI_BUTTON=m > > CONFIG_ACPI_VIDEO=m > > CONFIG_ACPI_FAN=m > > CONFIG_ACPI_DOCK=y > CONFIG_ACPI_PROCESSOR=m > CONFIG_ACPI_HOTPLUG_CPU=y > CONFIG_ACPI_THERMAL=m > CONFIG_ACPI_CUSTOM_DSDT_FILE="" > # CONFIG_ACPI_CUSTOM_DSDT is not set > CONFIG_ACPI_BLACKLIST_YEAR=2001 > # CONFIG_ACPI_DEBUG is not set > # CONFIG_ACPI_PCI_SLOT is not set > CONFIG_ACPI_CONTAINER=m > CONFIG_ACPI_SBS=m > CONFIG_X86_ACPI_CPUFREQ=m > CONFIG_X86_POWERNOW_K7_ACPI=y > CONFIG_X86_POWERNOW_K8_ACPI=y > CONFIG_HOTPLUG_PCI_ACPI=m > CONFIG_HOTPLUG_PCI_ACPI_IBM=m > CONFIG_PNPACPI=y > CONFIG_BLK_DEV_IDEACPI=y > CONFIG_ATA_ACPI=y > CONFIG_PATA_ACPI=m > CONFIG_THINKPAD_ACPI=m > # CONFIG_THINKPAD_ACPI_DEBUGFACILITIES is not set > # CONFIG_THINKPAD_ACPI_DEBUG is not set > CONFIG_THINKPAD_ACPI_BAY=y > CONFIG_THINKPAD_ACPI_VIDEO=y > CONFIG_THINKPAD_ACPI_HOTKEY_POLL=y > CONFIG_ACPI_WMI=m > # CONFIG_ACPI_ASUS is not set > CONFIG_ACPI_TOSHIBA=m > > Regards, > Niel > -- > 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 -- 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