From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: Anca Emanuel <anca.emanuel@gmail.com>,
Ubuntu kernel team mailing list <kernel-team@lists.ubuntu.com>,
LKML <linux-kernel@vger.kernel.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: is there a fix for ubuntu with intel GPU booting to blank screen?
Date: Sun, 2 Jan 2011 07:13:11 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.00.1101020700220.4087@localhost6.localdomain6> (raw)
In-Reply-To: <1293832014.27359.7.camel@maxim-laptop>
On Fri, 31 Dec 2010, Maxim Levitsky wrote:
> On Fri, 2010-12-31 at 12:01 -0500, Robert P. J. Day wrote:
> > On Fri, 31 Dec 2010, Maxim Levitsky wrote:
> >
> > ... snip related to i915 blank screen issues ...
> >
> > > Since you know how to compile kernel, and even have a close working
> > > version, you really should just bisect the bug.
> > >
> > > Bisection is a built-in in the git binary search that allows you to
> > > find the first commit that introduced the bug.
> > >
> > > For example, quick google gives,
> > > http://www.kernel.org/pub/software/scm/git-core/docs/v1.0.13/howto/isolate-bugs-with-bisect.txt
> >
> > oh, i know how to do bisection but, to be frank, i just don't have
> > the time. i'm under a brutal deadline for some billable work and,
> > even if i had the time, i suspect that when i eventually tracked down
> > the commit, i probably wouldn't really appreciate what i was looking
> > at, anyway.
> You truly underestimate this. Having commit that broke things points
> perfectly at the issue. Then, developers can even just revert the
> offending commit until it is understood why it breaks stuff.
i suspect what i'm about to type won't come as a surprise to anyone
currently working on this problem, but there is a cheap workaround to
boot to the command line using one of the offending kernels.
when i boot, say, 2.6.37-rc8+ (or any other kernel, for that
matter), the first two lines i always see are (paraphrasing):
/dev/pts busy ...
ureadahead info ...
and that's it, just those two lines. it's the same no matter which
kernel i boot. and here's where things differ.
for a properly functioning kernel, the display then switches to
hi-res mode, the two lines are redisplayed in a smaller font and the
boot continues normally, right up to the desktop (say, with my
2.6.37-rc5+ kernel).
for a bad kernel (say, my 2.6.37-rc8+), it's that switch to hi-res
after those original two lines of output where the display goes black
and stays that way so it looks like a KMS-related problem.
a workaround to at least let me boot to the command line is to add
"i915.modeset=0"
as a kernel parm, but that won't then let me start X once i'm up and
running. there are all sorts of reports of this type of behaviour,
like this:
https://bbs.archlinux.org/viewtopic.php?id=96759
which is where i got the idea to use that kernel parm and the
behaviour i saw matches exactly what's in that post. in any event,
as i reported, this is still happening with -rc8.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2011-01-02 12:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.DEB.2.00.1012270640240.3071@localhost6.localdomain6>
2010-12-31 6:32 ` Anca Emanuel
2010-12-31 14:23 ` Robert P. J. Day
2010-12-31 16:48 ` Maxim Levitsky
2010-12-31 17:01 ` Robert P. J. Day
2010-12-31 21:46 ` Maxim Levitsky
2011-01-01 11:18 ` Robert P. J. Day
2011-01-02 12:13 ` Robert P. J. Day [this message]
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=alpine.DEB.2.00.1101020700220.4087@localhost6.localdomain6 \
--to=rpjday@crashcourse.ca \
--cc=anca.emanuel@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kernel-team@lists.ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
/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®