From: Alex Bennee <kernel-hacker@bennee.com>
To: Florian Mickler <florian@mickler.org>
Cc: xorg@freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.30-rc2 + xorg-intel-2.7.0 + DRM_I915_KMS = corruption
Date: Tue, 28 Apr 2009 06:37:10 +0100 [thread overview]
Message-ID: <b2cdc9f30904272237h3a815282h7e6b932e1c252d17@mail.gmail.com> (raw)
In-Reply-To: <20090427234947.394f774f@schatten>
2009/4/27 Florian Mickler <florian@mickler.org>:
> On Sun, 19 Apr 2009 07:27:35 +0100
> Alex Bennee <kernel-hacker@bennee.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.
><snip>
>
> hm, are you using the xf86-video-intel git-branch "2.7"? if i use that,
> i need a kernel fix queued in eanholts for-linus git-tree or else i
> also get unusable X.
No, I'm using the actual released 2.7.0 driver (as built via a simple
Gentoo ebuild)
> i assumed that this was because of some not-yet-released fixes
> on the 2.7-branch which will get released as soon as erics queue is
> merged? but i didn't double check ... maybe the released version is
> also broken in this regard for me....
I tried again with the latest drm-intel kernel git tree @
commit 44ab43155e8071fbf037513e57de9a79044edf56
Author: Matthew Garrett <mjg59@srcf.ucam.org>
Date: Wed Apr 1 19:53:33 2009 +0100
drm/i915: Enable ASLE if present
The changes to opregion initialisation order meant that the ASLE setup
code might not be run at the correct time. Ensure that the interrupts are
set up.
Signed-off-by: Matthew Garrett <mjg@redhat.com>
Signed-off-by: Eric Anholt <eric@anholt.net>
Still broken :-(
--
Alex, homepage: http://www.bennee.com/~alex/
CV: http://www.bennee.com/~alex/cv.php
next prev parent reply other threads:[~2009-04-28 5:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 6:27 Alex Bennee
2009-04-27 21:49 ` Florian Mickler
2009-04-28 5:37 ` Alex Bennee [this message]
2009-04-28 16:53 ` Jesse Barnes
2009-04-29 7:49 ` Alex Bennee
2009-04-29 16:06 ` Jesse Barnes
[not found] ` <b56f065e0904291118r7f008508s32852ccd1bb0b645@mail.gmail.com>
2009-04-29 18:46 ` Andreas Proschofsky
2009-04-29 20:07 ` Alex Bennee
2009-04-29 21:57 ` Alex Bennee
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=b2cdc9f30904272237h3a815282h7e6b932e1c252d17@mail.gmail.com \
--to=kernel-hacker@bennee.com \
--cc=florian@mickler.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xorg@freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®