All of lore.kernel.org
 help / color / mirror / Atom feed
From: Justin Madru <jdm64@gawab.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Regression: 2.6.25-rc5: Blank Screen: Intel 945]
Date: Mon, 31 Mar 2008 12:24:36 -0700	[thread overview]
Message-ID: <47F13A74.8010206@gawab.com> (raw)
In-Reply-To: <200803251308.43830.jbarnes@virtuousgeek.org>

Jesse Barnes wrote:
> So somehow both pipes are getting disabled, and your LCD is getting turned
> off and things never get re-enabled.  The X driver should have turned things
> back on though, after detecting what's available.  Do you have your X logs
> from the working & broken cases?  Also, did you try reproducing the blank
> screen problem w/o gdm enabled as Bryce suggested?  That could help narrow
> down if it's just an intelfb problem vs. a new intelfb/X driver interaction
> bug.

Well, I disabled gdm and tryed to trigger the blank screen. I did about ~16 reboots and it blanked out on me only 2 times.
I was using a script to reboot and/or startx. One time I'm not exactly sure if X was started, so it might have blanked out on a "startx".
The other time I'm fairly sure X wasn't started, so it blanked out on a terminal login.

Both of the blank outs were different than the ones with gdm started. Pressing ctrl+alt+f# changed nothing on the screen;
the screen seemed almost completely off (no or little backlight). A few seconds after pressing the power button the shutdown splash screen would show, but this time it was _very_ faint.

Usually, when gdm is enabled, pressing ctrl+alt+f# would "refresh" (or mode/resolution change) the screen, but it would still be blank.
Also the backlight still seamed to be on and at full brightness (although, still displaying black).

Well, I don't know what to say, it's the strangest of problems.

Justin


  parent reply	other threads:[~2008-03-31 19:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12 19:02 [Regression: 2.6.25-rc5: Blank Screen: Intel 945] 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
2008-03-20  2:00                             ` Bryce Harrington
2008-03-25  3:07                             ` Justin Madru
2008-03-25 20:08                               ` Jesse Barnes
2008-03-25 20:08                                 ` Jesse Barnes
2008-03-26 18:32                                 ` Justin Madru
2008-03-31 19:24                                 ` Justin Madru [this message]
2008-04-01 20:22                                   ` Jesse Barnes
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=47F13A74.8010206@gawab.com \
    --to=jdm64@gawab.com \
    --cc=jbarnes@virtuousgeek.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.