lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1172103159.5790.45.camel@localhost.localdomain>
Date:	Thu, 22 Feb 2007 00:12:39 +0000
From:	Richard Purdie <rpurdie@...ys.net>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
Cc:	Alex Romosan <romosan@...orax.lbl.gov>,
	Yaroslav Halchenko <kernel@...russian.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	linux-fbdev-devel@...ts.sourceforge.net,
	James Simmons <jsimmons@...radead.org>
Subject: Re: no backlight on radeon after recent kernel "upgrade"s

On Wed, 2007-02-21 at 21:17 -0200, Henrique de Moraes Holschuh wrote:
> On Wed, 21 Feb 2007, Richard Purdie wrote:
> > enabled. On a thinkpad, the backlight is probably under ACPI control.
> 
> BIOS+ACPI, actually.  Without ACPI video loaded, the firmware does
> everything correctly.  With ACPI video, the firmware does it, then its
> changes are clobbered over by ACPI video's.
> 
> If ibm-acpi is loaded, a backlight device "ibm" is added.  ibm-acpi's ibm
> backlight device can change the display brightness.  It is *not* capable of
> turning the backlight on or off, AFAIK.
> 
> BTW, some ThinkPads don't have a Radeon, but rather an Intel GM/GMX device.

I have a thinkpad with Intel GM graphics ;-). I need it to work so I try
not to experiment too much on it. I've just tried the ibm-acpi driver
and it doesn't work well :-(.

So far I've noticed:

* 'cat brightness' != 'cat actual_brightness' upon bootup (doesn't have
to be true if there is hardware brightness limiting or level changing in
action but that wouldn't be the case here and this could be fixed
easily).
* 'echo 0 > brightness' lowered the intensity but by a level or two, not
set it to level 0. A couple of more attempts and it did jump from 7 -> 1
and so on, it seems erratic.

actual_brightness always seems to be correct, as does brightness so it
looks like its not updating the hardware correctly.

Regards,

Richard







-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ