LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: Alex Romosan <romosan@sycorax.lbl.gov>
Cc: Yaroslav Halchenko <kernel@onerussian.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
linux-fbdev-devel@lists.sourceforge.net,
James Simmons <jsimmons@infradead.org>
Subject: Re: no backlight on radeon after recent kernel "upgrade"s
Date: Wed, 21 Feb 2007 22:41:57 +0000 [thread overview]
Message-ID: <1172097718.5790.29.camel@localhost.localdomain> (raw)
In-Reply-To: <877iub9mu2.fsf@sycorax.lbl.gov>
On Wed, 2007-02-21 at 14:18 -0800, Alex Romosan wrote:
> Richard Purdie <rpurdie@rpsys.net> writes:
> i have exactly the same problem with 2.6.21-rc1 on a thinkpad t40
> with an ati radeon card. the machine boots up but the backlight never
> comes on. 2.6.20 worked okay.
Can you have a look at the differences between the defconfigs for 2.6.20
and 2.6.21-rc1?
If the backlight changes are at fault, I'm guessing James' Kconfig
changes to the video Kconfig would be the culprit since
FB_RADEON_BACKLIGHT only used to be selectable if PMAC_BACKLIGHT was
enabled. On a thinkpad, the backlight is probably under ACPI control.
If FB_RADEON_BACKLIGHT wasn't set for 2.6.20, can you try 2.6.21-rc1
with that option disabled?
An ls /sys/class/backlight under 2.6.20 will tell us which driver it was
using...
Thanks,
Richard
next prev parent reply other threads:[~2007-02-21 22:42 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 4:46 Yaroslav Halchenko
2007-02-19 8:04 ` Andrew Morton
2007-02-19 9:19 ` Richard Purdie
2007-02-21 5:56 ` Yaroslav Halchenko
2007-02-22 0:34 ` Richard Purdie
2007-02-22 1:07 ` James Simmons
2007-02-22 9:46 ` Richard Purdie
2007-02-22 15:18 ` James Simmons
2007-02-22 1:11 ` [Linux-fbdev-devel] " James Simmons
2007-02-22 2:09 ` Joel Becker
2007-02-22 15:55 ` James Simmons
2007-02-22 17:28 ` David Miller
2007-02-28 16:55 ` James Simmons
2007-03-01 10:57 ` Richard Purdie
2007-03-01 21:08 ` James Simmons
2007-02-21 22:18 ` Alex Romosan
2007-02-21 22:41 ` Richard Purdie [this message]
2007-02-21 23:17 ` Henrique de Moraes Holschuh
2007-02-22 0:12 ` Richard Purdie
2007-02-22 0:51 ` Henrique de Moraes Holschuh
2007-02-22 1:10 ` Richard Purdie
2007-02-22 2:13 ` Henrique de Moraes Holschuh
2007-02-22 1:10 ` Henrique de Moraes Holschuh
2007-02-22 1:16 ` ACPI: ibm-acpi: fix initial status of backlight device Henrique de Moraes Holschuh
2007-02-22 10:03 ` Richard Purdie
2007-02-22 14:45 ` Henrique de Moraes Holschuh
2007-02-22 18:19 ` Henrique de Moraes Holschuh
2007-02-22 10:00 ` no backlight on radeon after recent kernel "upgrade"s Richard Purdie
2007-02-22 14:56 ` Henrique de Moraes Holschuh
2007-02-22 15:19 ` Richard Purdie
2007-02-22 16:00 ` James Simmons
2007-02-22 16:34 ` Henrique de Moraes Holschuh
2007-02-22 17:08 ` Richard Purdie
2007-02-21 23:51 ` Alex Romosan
2007-02-22 1:13 ` James Simmons
2007-02-22 9:56 ` Richard Purdie
2007-02-22 14:38 ` Henrique de Moraes Holschuh
2007-02-22 4:03 ` Alex Romosan
2007-02-22 4:58 ` Alex Romosan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1172097718.5790.29.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=akpm@linux-foundation.org \
--cc=jsimmons@infradead.org \
--cc=kernel@onerussian.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=romosan@sycorax.lbl.gov \
--subject='Re: no backlight on radeon after recent kernel "upgrade"s' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).