2.6.20.x dims my laptop-screen

Submitted by Anonymous
on March 23, 2007 - 10:41am

Hi there,

recently I've installed the 2.6.20-, 2.6.20.3- and the 2.6.21-rc4-Kernel on my Asus M6Ne Laptop I'm running with Debian Etch. With all these kernels I have a problem I never had with 2.6.19.2 and before. It's about this: When I start the Mplayer, my laptop-display is dimmed down so I can hardly see anything. With Mplayer it happens just one time - the first time I start it during one session. With VLC it happens every time I start a video. The only thing I've noticed up to now is this output of /var/log/Xorg.0.log that appears every time, the lcd is dimmed down:

(**) RADEON(0): RADEONDisplayPowerManagementSet(0,0x0)

It's a Ati Radeon Mobility 9700.

I've activated the backlight-options in the kernel and all ACPI-Options are compiled into the kernel.

Does anyone know what this is about and maybe how to fix it?

Thanks in advance;-)!

Some possibly relevant modules:

cushioncritter
on
March 23, 2007 - 1:09pm

/lib/modules/2.6.20.3/kernel/drivers/video/backlight/backlight.ko

/lib/modules/2.6.20.3/kernel/drivers/video/backlight/lcd.ko

/lib/module/s2.6.20.3/kernel/drivers/acpi/asus_acpi.ko

How about rmmod backlight, rmmod lcd, rmmod asus_acpi and see if the problem goes away when you load mplayer, vlc, etc.. You may also want to get a very recent nightly build of mplayer from an unofficial repository, where you can also get a matching mencoder, which can now convert flash video swf/flv (i.e youtube) into avi, etc.

That assumes you built backlight.ko, etc. as modules and that various "helpful" layers like udev, hotplug, distro. hardware detection will allow you to not load them. That's why I manually detect hardware using lspci -n, then look in a table such as /lib/discover/pci.lst to see what module is supposed to be loaded for the hex vendor:device id. In a minimal Debian, we just list modules we want loaded at boot in /etc/modules. But normally installing heavyweight DE like Gnome/KDE pulls in all the hal/udev/etc.

For example, if my server has a sound card on the motherboard, who says I want to use it? But it is accepted dogma that if a device is there is must be detected and used, even if the module doesn't work and it doubles the boot time detecting unwanted devices.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.