From: Daniel Jacobowitz <dan@debian.org>
To: Miles Lane <miles.lane@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linus' 2.6.0-test1 (PPC) -- Radeon Mobility M7 LW (AGP) display messed up (DRI update problem?)
Date: Tue, 29 Jul 2003 14:01:40 -0400 [thread overview]
Message-ID: <20030729180138.GA30012@nevyn.them.org> (raw)
In-Reply-To: <200307282135.27750.miles.lane@comcast.net>
On Mon, Jul 28, 2003 at 09:35:27PM -0700, Miles Lane wrote:
> Hi Linus,
>
> It looks like maybe something went wrong in your DRI merge.
> >From 2.6.0-test1, I have had major problems with my Radeon
> display when XFree86 (cvs HEAD) starts up. I am running
> on a PowerBook G4 (Titanium III/800) with DRI enabled.
> Earlier 2.5 kernels rendered XFree86 okay. The weird thing
> since test1 is that once XFree86 starts up, switching to a
> VT and back does not clear up the problem. The VT displays
> are hosed as well (the problem is that only about the top
> one line of text (in a VT window) looks okay. Below that,
> the whole screen is an out-of-sync blur.
>
> When I run fbset in a VT window, it shows the same info
> that shows up when running under 2.5 kernels (with no display
> corruption).
>
> I will test again with DRI disabled and see if the problem goes away.
> If it does, I will check again with your DRI updates from 2.6.0-test1
> backed out. I'll let you know what happens.
FYI, I'm having similar problems with an aty128. DRI does not affect
it, however. With X set to UseFBDev I get striping; without it I get a
head-numbing blur effect.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-07-29 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 4:35 Linus' 2.6.0-test1 (PPC) -- Radeon Mobility M7 LW (AGP) display messed up (DRI update problem?) Miles Lane
2003-07-29 18:01 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-29 11:22 Miles Lane
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=20030729180138.GA30012@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@comcast.net \
/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