mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Justin Madru <jdm64@gawab.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Bryce Harrington <bryce@canonical.com>
Subject: Re: [Regression: 2.6.25-rc5: Blank Screen: Intel 945]
Date: Wed, 19 Mar 2008 16:48:59 -0700	[thread overview]
Message-ID: <200803191648.59400.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <47E1A3F1.3020004@gawab.com>

On Wednesday, March 19, 2008 4:38 pm Justin Madru wrote:
> Jesse Barnes wrote:
> >> I've put in a sync request for this to get updated for hardy.  (It still
> >> will only be in universe, so won't be built automatically with -intel,
> >> but at least users will be able to more easily compile it by hand.)
> >>
> >> Meanwhile, here is a Ubuntu Hardy build of Debian's package:
> >>
> >> http://people.ubuntu.com/~bryce/Testing/libpciaccess/libpciaccess-dev_0.
> >>10-1_i386.deb
> >> http://people.ubuntu.com/~bryce/Testing/libpciaccess/libpciaccess0_0.10-
> >>1_i386.deb
> >
> > Thanks a lot Bryce, hopefully this will help Justin build the register
> > dumper so we can track down his problem...
> >
> > Jesse
>
> Thanks for all your help so far! Well I tried to install the deb files
> that Bryce created, unfortunately they're dependent on a newer version
> of libc6. I think (_hope_) this is the one in Hardy _because_ that's
> what I'm doing right now; I've decided to upgrade to Hardy. (so sad
> because I have to download _1.5GB_)
>
> Jesse, do you still think it's a bug in the X server driver instead of
> the kernel driver (dri I guess)? Because I can trigger the blank screen
> before the X server even starts. If I press ctr+alt+f1 at the _right_
> time when the kernel is booting (or I guess when the boot splash is
> showing) it will instantly blank out. That doesn't seem like something
> related to X.

Depends on the boot splash program.  I think in some configurations it'll be X 
based, but again Bryce probably knows more here as the Ubuntu X guy. :)

> Anyways maybe it's multiple things, and by upgrading to Hardy it might
> fix it (which would prove that it's not a kernel bug, but some software
> version dependency bug - which would still be good to know).

Good luck with the upgrade...

Jesse

  reply	other threads:[~2008-03-20  0:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12 19:02 Justin Madru
2008-03-12 19:36 ` Jesse Barnes
     [not found]   ` <47D8BF6A.9020905@gawab.com>
2008-03-13 17:09     ` Jesse Barnes
2008-03-14  4:22       ` Justin Madru
2008-03-14 17:29         ` Jesse Barnes
2008-03-15  3:48           ` Justin Madru
2008-03-15 17:35             ` Jesse Barnes
2008-03-15 18:16               ` Bryce Harrington
2008-03-17  1:28               ` Justin Madru
2008-03-18 19:07                 ` Bryce Harrington
2008-03-18 20:00                   ` Jesse Barnes
2008-03-18 20:53                     ` Bryce Harrington
2008-03-18 21:14                     ` Bryce Harrington
2008-03-18 21:17                       ` Jesse Barnes
2008-03-19 23:38                         ` Justin Madru
2008-03-19 23:48                           ` Jesse Barnes [this message]
2008-03-20  2:00                             ` Bryce Harrington
2008-03-25  3:07                             ` Justin Madru
2008-03-25 20:08                               ` Jesse Barnes
2008-03-26 18:32                                 ` Justin Madru
2008-03-31 19:24                                 ` Justin Madru
2008-04-01 20:22                                   ` Jesse Barnes
2008-04-09  4:56                                     ` Justin Madru
2008-04-09 15:24                                       ` Jesse Barnes
2008-04-14  3:46                                         ` Justin Madru

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=200803191648.59400.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=bryce@canonical.com \
    --cc=jdm64@gawab.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

Powered by JetHome