Dear Corentin, 2012/8/9 Carlos Alberto Lopez Perez <clopez@xxxxxxxxxx>: > On 08/08/12 11:34, Corentin Chary wrote: >>> The problem is that the /sys/class/backlight/acpi_video0 directory still exists >>> > and the gnome-settings-daemon will choose acpi_video0 for the >>> > brightness functions >> Are you sure acpi_video_unregister() was called in this case ? can you >> add some traces to video.c to see what happened and why >> backlight_device_unregister() wasn't called ? Yes, you are right, acpi_video_unregister() is not be called. #ifdef CONFIG_ACPI_VIDEO doesn't work as expected. In ubuntu kernel, it's config as module, CONFIG_ACPI_VIDEO=m. I will try to figure out what happened. >>> > But, if asus-wmi is loaded before video, then video won't call >>> > backlight_device_register(), >>> > since the flag is already be set. >> Honestly, I don't know if there is a way to do that, and asus-wmi >> should be loadable and working at any time, not only on boot. > > What about writing an udev rule to force using acpi_video0 for asus-wmi? > > Use udevadm to get the attributes for building the rule > > udevadm info --attribute-walk --path=/sys/class/backlight/acpi_video0 > -- Chia-Lin Kao(AceLan) http://blog.acelan.idv.tw/ E-Mail: acelan.kaoATcanonical.com (s/AT/@/) -- To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
