linux-kernel - Re: 2.6.30-rc2 + xorg-intel-2.7.0 + DRM_I915

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <b2cdc9f30904290049k290a59bfh1265a66735b510e2@mail.gmail.com>
Date:	Wed, 29 Apr 2009 08:49:47 +0100
From:	Alex Bennee <kernel-hacker@...nee.com>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
Cc:	Florian Mickler <florian@...kler.org>, xorg@...edesktop.org,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.30-rc2 + xorg-intel-2.7.0 + DRM_I915_KMS = corruption

2009/4/28 Jesse Barnes <jbarnes@...tuousgeek.org>:
> On Tue, 28 Apr 2009 06:37:10 +0100
> Alex Bennee <kernel-hacker@...nee.com> wrote:
>
>> 2009/4/27 Florian Mickler <florian@...kler.org>:
>> > On Sun, 19 Apr 2009 07:27:35 +0100
>> > Alex Bennee <kernel-hacker@...nee.com> wrote:
>> >
>> >> Heading the warnings in the menuconfig I did try and ensure I have
>> >> all the up to date parts of user-space. With KMS enabled GDM
>> >> starts up but then corrupts the display with vertical lines.
>> >> Disabling the kernel config and everything starts up fine, UXA
>> >> acceleration seems OK and the speed of compiz is finally back up
>> >> to ~60fps thanks to the A17 fix.
>> >>
>> >> Am I missing another bit of user space for KMS to work properly?
>>
>> Apparently I was missing a key bit and had to enable fbdev from the
>> command line:
>>
>> kernel /kernel-2.6-drm root=/dev/sda2
>> video=intelfb:mode=1440x900-32@75,accel,hwcursor
>>
>> However I still saw the same corruption kick in when GDM started. I
>> couldn't switch mode either which kinda defeated the point.
>
> The above seems to indicate that you have some FB drivers built into
> your kernel; that will likely fail in weird ways.  Try disabling all
> the FB drivers, but keep CONFIG_FRAMEBUFFER_CONSOLE enabled.  Then when
> you load the i915 driver you should get a nice console.

Ahh, I was under the (mistaken) impression that the kernel
frame-buffer drivers where linked to the console frame buffer driver
and needed for it to work well. Disabling them all and I do indeed get
a lovely framebuffer console on boot up but still the same corruption
when GDM starts. I'm also still not able to switch back to the console
like I can with KMS disabled.

I've attached my .config, a dump of the dmesg of the failing case and
a broken and working Xorg.log (working being no KMS and the Linus tree
rather than the intel-drm tree, although I have tested the Linus tree
fails with KMS enabled in the same way).


-- 
Alex, homepage: http://www.bennee.com/~alex/
CV: http://www.bennee.com/~alex/cv.php

Download attachment ".config" of type "application/octet-stream" (74000 bytes)

Download attachment "xcrash" of type "application/octet-stream" (31709 bytes)

Download attachment "Xorg.0.log.failed" of type "application/octet-stream" (23181 bytes)

Download attachment "Xorg.0.log.working" of type "application/octet-stream" (44940 bytes)