[Intel-gfx] Black screen on boot with KMS and unable to start X

[Scott Silverman]

/proc/acpi/button/lid/LID/state = "state:      open"

drm.debug=0x04 (with KMS enabled) = http://paste.pocoo.org/show/191402/

Also, per Florian's suggestion, I am currently recompiling a kernel
that removes all the fb hardware drivers, I will post results with
that once I am done.

Thanks,
Scott

On Thu, Mar 18, 2010 at 7:58 PM, ykzhao <yakui.zhao at intel.com> wrote:
> On Fri, 2010-03-19 at 00:53 +0800, Scott Silverman wrote:
>> My kernel .config can be found here: http://paste.pocoo.org/show/191168/
>>
>> I have disabled uvesafb, and removed all modesetting/framebuffer
>> related entries from my grub config.
>> i.e.: kernel /vmlinuz26 root=/dev/disk/by-uuid/<snip> ro
>>
>> When I boot, I see the boot process up until the point where I believe
>> the i915 module is loaded, at which point I get a black screen, though
>> the backlight is still on. The kernel continues to load properly, and
>> after this point I can access the machine via SSH, or blindly via the
>> console.
>
> Will you please boot the system with the option of "nomodeset" and cat
> the output of /proc/acpi/button/lid/LID/state?
>
> It will be great if you can add the boot option of "drm.debug=0x04" with
> KMS enabled and attach the output of dmesg.
>
> Thanks.
>    Yakui
>>
>> If at this point I attempt to start X, I will see the backlight flash
>> off, then back on. The log for Xorg can be found herE:
>> http://paste.pocoo.org/show/191171/
>>
>> The configuration I am using for X is here: http://paste.pocoo.org/show/191172/
>>
>> I can also try to start X without a config, the log for that attempt
>> is here (results the same, backlight flashes, then nothing):
>> http://paste.pocoo.org/show/191173/
>>
>> Ideally, when I boot, I will see the console, and when I startx, I
>> will be able to see X.
>>
>> Do you think I should file a bug?
>>
>> Thanks,
>> Scott
>>
>> On Thu, Mar 18, 2010 at 5:54 AM, Florian Mickler <florian at mickler.org> wrote:
>> > On Wed, 17 Mar 2010 15:55:04 -0500
>> > Scott Silverman <ssilverman at simplexinvestments.com> wrote:
>> >
>> >> I tried updating to the driver you specified (Actually, I went to 2.10.902).
>> >>
>> >> I still can't start X, I get:
>> >>
>> >> (EE) intel(0): No kernel modesetting driver detected.
>> >> (EE) Screen(s) found, but none have a usable configuration.
>> >>
>> >> I have checked dmesg, doesn't appear to be anything interesting there.
>> >>
>> >> In the interest of confirming that I have a proper configuration, I changed
>> >> " Driver "Intel" " to " Driver "vesa" " temporarily, X started up (thought
>> >> without decorations, I didn't really bother to look into that).
>> >>
>> >> I am currently using the uvesafb framebuffer driver, but as soon as the i915
>> >> module loads it enables modesetting and my display goes blank.
>> >>
>> >
>> > Hi!
>> >
>> > please post your kernel .config.
>> >
>> > short summary of the kernel side:
>> > 1. all kernel-graphics support is consolidated into i915 module.
>> > fbcon is used by i915 to display the console. kernel mode setting is
>> > needed for userspace x-driver.
>> >
>> > 2. all other kernel framebuffer-drivers are not to be used together with
>> > the i915 module.
>> >
>> > if you honor those two points, you should see the kernel booting up.
>> > if you don't see the kernel booting up, you should probably file a bug.
>> >
>> > hth,
>> > Flo
>> >
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
>