From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: "Nikula, Jani" <jani.nikula@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: Screen unusable for console until X starts (945GM)
Date: Sat, 20 Oct 2012 14:20:55 +0200 [thread overview]
Message-ID: <3355489.fbQxDfRbyW@eto> (raw)
In-Reply-To: <CAKMK7uGowaBGD0OxQ4-NruMFQWnRKjzG7K2GwRj66HXjTGPfig@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2697 bytes --]
Am Samstag 20 Oktober 2012, 14:18:10 schrieb Daniel Vetter:
> On Sat, Oct 20, 2012 at 2:14 PM, Rolf Eike Beer <eike-kernel@sf-tec.de>
wrote:
> > Am Samstag 20 Oktober 2012, 13:57:37 schrieb Daniel Vetter:
> >> On Sat, Oct 20, 2012 at 8:30 AM, Rolf Eike Beer <eike-kernel@sf-tec.de>
> >
> > wrote:
> >> > I have an older Laptop with this card in it:
> >> >
> >> > [ 0.813208] agpgart-intel 0000:00:00.0: Intel 945GM Chipset
> >> > [ 0.813284] agpgart-intel 0000:00:00.0: detected gtt size: 262144K
> >> > total, 262144K mappable
> >> > [ 0.814188] agpgart-intel 0000:00:00.0: detected 8192K stolen memory
> >> > [ 0.814377] agpgart-intel 0000:00:00.0: AGP aperture is 256M @
> >> > 0xc0000000
> >> >
> >> > I observe the following strange behavior: if I start up the system
> >> > (grub2,
> >> > openSUSE 12.1) I see the splash screen appearing shortly. In most cases
> >> > it
> >> > will then disappear and the screen will become just black. This is not
> >> > the
> >> > delay "X is loading but has not put anything on the screen", but it is
> >> > much
> >> > earlier. I'm asked for a crypt password during bootup, which in most
> >> > cases
> >> > now happens totally in the dark, i.e. no console messages at all, no
> >> > prompt. Booting just to runlevel 3 leaves me with a black screen but a
> >> > functional system.
> >> >
> >> > The strange thing is: sometimes (like 10%) things are just working,
> >> > i.e. I
> >> > have console output. I've tested with 3.1.10 as well as 3.6.2 and both
> >> > have
> >> > the problem. I've run a number of 2.6 kernels before on this system,
> >> > but I
> >> > do not recall when the problem occured or which is one that definitely
> >> > worked.
> >> >
> >> > Starting X will always get the screen back into working state, i.e. the
> >> > system is normally usable after startup, but it is just annoying to see
> >> > nothing during startup.
> >> >
> >> > Any hints, patches, whatever?
> >>
> >> Please attach drm.debug=0xe to your kernel cmdline, boot 3.6 and
> >> attach complete dmesg (up to the point where X makes something appear
> >> on the screen).
> >
> > Attached. Since I did not mention it earlier: from the moment on X is
> > started consoles also work fine.
>
> Another case where something sets the backlight brightness to zero
> when we take over, and the X restores it to something sane again. If
> the backlight keys on your machine work, you should be able to
> brighten things up even before X starts.
>
> Adding Jani since he's recently looked at an eerily similar bug.
I can switch the screen brightness during startup, but that only makes the
black screen a dark grey screen, I still see no text.
Eike
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2012-10-20 12:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 6:30 Screen unusable for console until X starts (945GM) Rolf Eike Beer
2012-10-20 11:57 ` Daniel Vetter
2012-10-20 12:14 ` Rolf Eike Beer
2012-10-20 12:18 ` Daniel Vetter
2012-10-20 12:20 ` Rolf Eike Beer [this message]
2012-10-20 13:27 ` Daniel Vetter
2012-10-20 18:18 ` Rolf Eike Beer
2012-10-20 18:33 ` Daniel Vetter
2012-10-20 19:03 ` Rolf Eike Beer
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=3355489.fbQxDfRbyW@eto \
--to=eike-kernel@sf-tec.de \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.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