From: Melchior FRANZ <melchior.franz@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Chris Wilson <chris@chris-wilson.co.uk>, Greg KH <greg@kroah.com>
Subject: Re: i915 completely unusable in 2.6.38.x
Date: Tue, 26 Apr 2011 09:59:52 +0200 [thread overview]
Message-ID: <201104260959.53084@rk-nord.at> (raw)
In-Reply-To: <20110425210323.GA23418@kroah.com>
I didn't really want to hijack this thread -- just confirm that the i915
driver is/was broken through the whole 2.6.38 series, up to 2.6.38.4.
* Greg KH -- Monday 25 April 2011:
> On Mon, Apr 25, 2011 at 10:10:46PM +0200, Melchior FRANZ wrote:
> > I'm still using 2.6.38-rc8 (with SuSE 11.4/tumbleweed) on this machine
> > (Acer TravelMate 5735Z-452G32Mnss), because that's the last version that
> > supported KMS on my chipset.
> I don't understand, .38 should work as it has the above fix in it,
> right?
[https://bugzilla.kernel.org/show_bug.cgi?id=31522]
Argh, sorry -- I hadn't noticed that someone closed this bug report.
No, this isn't fixed. Exact same symptoms: The notebook's screen
goes black early in the boot process with KMS. Closing and reopening
the lid doesn't help, contrary to what some people reported. Turning
off KMS kind-of helps: The virtual console is right after that, but
Xorg apparently gets contradicting info about the screen size, so
that parts of the desktop end up outside the screen area.
> Otherwise, what should be done for the .38-stable tree?
I had assumed that the commit that broke it was known, as there hasn't
much been committed between 2.6.38-rc8 and 26.6.38, but I'll bisect
and investigate.
m.
next prev parent reply other threads:[~2011-04-26 7:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 9:14 Boris B. Zhmurov
2011-04-25 9:15 ` Boris B. Zhmurov
2011-04-25 20:10 ` Melchior FRANZ
2011-04-25 21:03 ` Greg KH
2011-04-26 7:59 ` Melchior FRANZ [this message]
2011-04-26 10:31 ` Boris B. Zhmurov
2011-04-26 18:04 ` Melchior FRANZ
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=201104260959.53084@rk-nord.at \
--to=melchior.franz@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®