[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#593432: Black screen with kms and i915

I have a i830 also..
If you turn off KMS  the old framebuffer driver works fine....
obviously, this means 2.6.34 and beyond are unusable at this point in time on 
the i830
although I did get the blacklight on in the terminal using 2.6.35 with KMS on 
My Toshiba 1200-S212 "i830" only has 8 megs of video ram,
which I concluded was not enough to run the new drmframebuffer drivers...
Than intel introduced the virtual memory stuff, but AFAICT it's not active on 
the i830 yet....

"from memory" (so forgive the incomplete description) 
both pipe A and pipe B are active 
when cloning the xorg.conf device and [screen or monitor] sections...
but I also haven't attached an external monitor to look at how it behaves...
"1there are only so many (24) hours in one day" [-) .......

----- Original Message ----
From: Julien Cristau <jcristau@debian.org>
To: sander@zedat.fu-berlin.de; 593432@bugs.debian.org
Sent: Wed, August 18, 2010 8:55:35 AM
Subject: Bug#593432: Black screen with kms and i915

retitle 593432 [i830] Black screen with kms and i915

On Wed, Aug 18, 2010 at 07:53:29 +0200, sander@zedat.fu-berlin.de wrote:

> When booting the screen goes black at the moment the frame buffer is
> switched on.
> Booting continues until the 'login prompt', but the screen remains black. 
> When
> switching to a text screen, the screen gets darker for a second, but no
> text login
> appears.  I can then, however, login blind and the machine works.  For
> example,
> I can reboot it when logging in as root and calling 'shutdown' (all blind,
> of course).
> The problem goes away when adding the line
> options i915 modeset=0
> to the file /etc/modprobe.d/i915-kms.conf, so I guess it is a kms problem.
> If I wasn't a newbie I'd mark this bug as 'important', because it left a
> freshly installed machine more or less completely unusable.
Is this a regression from a previous revision?  Can you attach the dmesg
from a kms boot?



Reply to: