http://bugzilla.novell.com/show_bug.cgi?id=558706 http://bugzilla.novell.com/show_bug.cgi?id=558706#c2 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |rui.zhang@intel.com Info Provider| |a.woodcock1@o2.co.uk --- Comment #2 from Thomas Renninger 2009-12-02 09:21:57 UTC --- ACPI: Cant attach device This is from the video.ko driver which is doing brightness switching. Hmm, I've seen seen "booting in dimmed state reports" a way too often. Rui: Do you know about this? I've found a patch to set higher default values in an asus specific driver and added it to 11.2, but this could be a more general problem? Andy: Can you try blacklisting the video driver: /etc/modprobe.conf.local add: blacklist video.ko and reboot. Does it help? If yes, remove or comment out with "#" the blacklist line you've added to modprobe.conf.local first and try these commands: rmmod thermal # avoid too much output logger START echo 0xFFFFFFFF >/sys/module/acpi/parameters/debug_layer echo 0x20F >/sys/module/acpi/parameters/debug_level modprobe video sleep 1 echo 0 >/sys/module/acpi/parameters/debug_layer logger STOP and send the output from /var/log/messages (between START and STOP). Also attach acpidump output, please (acpidump >/tmp/acpidump). The I/O conflict you mentioned looks harmless and unrelated: ACPI: I/O resource 0000:00:1f.3 [0x1c00-0x1c1f] conflicts with ACPI region SMBI [0x1c00-0x1c0f] which is a warning or more for info. The next line describes its meaning: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver There are three (boot) options: acpi_enforce_resources=strict,lax,no: * - strict (2) * -> further driver trying to access the resources will not load * - lax (default) (1) * -> further driver trying to access the resources will load, but you * get a system message that something might go wrong... * * - no (0) * -> ACPI Operation Region resources will not be registered Our default is "lax" which should be the same behavior as on 10.3, but also shows this message. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558706 http://bugzilla.novell.com/show_bug.cgi?id=558706#c4 Andy Woodcock changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |a.woodcock1@o2.co.uk Info Provider|a.woodcock1@o2.co.uk | --- Comment #4 from Andy Woodcock 2009-12-02 14:47:32 UTC --- Inhibiting the load of the video driver prevents the dimming of the LCD back-light during the boot. The resulting functionality appears to match openSUSE 10.3, i.e. back-light state inherited from BIOS set-up (mains powered give full illumination), back-light function keys do nothing. I am quite happy with the 10.3 functionality (I have not had an issues in the KDE desktop environment with the video driver load inhibited), could somebody add a note on the implications of inhibiting the load of the video driver. Other observations: #1 the video driver load was inhibited by adding the following line to the configuration file /etc/modprobe.d/50-blacklist.conf blacklist video #2 On loading the video driver during the debug gathering exercise the back-light did not dim. #3 The acpidump command flagged some checksum errors, I have redirected these into the acpidump log as well. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558706 http://bugzilla.novell.com/show_bug.cgi?id=558706#c6 --- Comment #6 from Andy Woodcock 2009-12-02 18:46:58 UTC --- Loading the video driver at runlevel 3 causes the LCD back-light to dim. Loading the video driver at runlevel 5 results in no change in LCD back-light illumination. I have attached the comment#2 debug information collected for runlevel 3 video driver load. The same set of drivers is loaded at both runlevel 3 and 5; the only difference is the order the driver appear in the LSMOD (see attached), presumably this reflects the order in which the drivers where loaded. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558706 http://bugzilla.novell.com/show_bug.cgi?id=558706#c8 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |a.woodcock1@o2.co.uk --- Comment #8 from Thomas Renninger 2010-02-23 14:09:21 UTC --- Could you try whether this is a duplicate of bug #549994, please. Check /sys/devices/virtual/backlight/acpi_video0 and try to change backlight manually by echoing different backlight levels into the right file: echo 100 >/sys/devices/virtual/backlight/acpi_video0/brightness (I think it was brightness, didn't double check). If this works, please mark the bug as duplicate and follow the other bug. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558706 http://bugzilla.novell.com/show_bug.cgi?id=558706#c10 --- Comment #10 from Rui Zhang 2010-02-25 03:21:35 UTC --- (In reply to comment #6)

Loading the video driver at runlevel 3 causes the LCD back-light to dim. Loading the video driver at runlevel 5 results in no change in LCD back-light illumination.

If the ACP -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558706 http://bugzilla.novell.com/show_bug.cgi?id=558706#c12 --- Comment #12 from Andy Woodcock 2010-02-25 20:40:53 UTC --- Yes I can confirm the above behaviour. Scenario #1 Video driver not blacklisted during boot; boot to run-level3 at which point the backlight dims. Scenario #2 Video driver blacklisted during boot; boot to run-level3 backlight does not dim. Removal of blacklist on video driver and load of video driver causes backlight to dim. Scenario #3 Video driver blacklisted during boot; boot to run-level5 backlight does not dim. Removal of blacklist on video driver and load of video driver does not cause the backlight to dim. So what's the difference between scenario #2 and #3 when video driver loaded; X running? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=558706 http://bugzilla.novell.com/show_bug.cgi?id=558706#c14 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marcus@swedcore.net --- Comment #14 from Thomas Renninger 2010-02-26 11:38:19 UTC --- *** Bug 570065 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=570065 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.