From: "Michel Dänzer" <michel@daenzer.net>
To: Miles Lane <miles.lane@comcast.net>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: linuxppc-2.5 (mvista rsync) -- Please push changesets for AGPGART / RadeonFB / Radeon DRI to Linus
Date: 03 Aug 2003 19:04:54 +0200 [thread overview]
Message-ID: <1059930294.14545.31.camel@thor.holligenstrasse29.lan> (raw)
In-Reply-To: <200308021832.08242.miles.lane@comcast.net>
On Sun, 2003-08-03 at 03:32, Miles Lane wrote:
>
> When I build and run a Linus kernel 2.5.72 - 2.6.0-test2 kernel,
> the video gets thrown way out of sync when I start my Radeon
> card with DRI enabled. The symptom is twofold, the colormap
> is all wrong and all I get is a very blurry, oversized pointer. The
> sync seems to be way out of whack. Switching to a VT window
> doesn't help. In fact, the video in VT windows exhibits the
> same problems. I have tried switching back and forth repeatedly.
> The only thing that fixes the problem is starting XFreee86 with
> DRI disabled or rebooting.
Do you have radeonfb working? If so, I want to see your .config. :)
The radeon DRM should work out of the box in any recent 2.5/2.6 kernel,
the lack of agpgart may be a problem on some machines though. It's hard
to say exactly what's the cause of your problems without knowing
anything about the version of XFree86, its configuration, ... but I'm
not sure that's really on topic for this list...
--
Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer
Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-08-03 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 1:32 linuxppc-2.5 (mvista rsync) -- Please push changesets for AGPGART / RadeonFB / Radeon DRI to Linus Miles Lane
2003-08-03 17:04 ` Michel Dänzer [this message]
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=1059930294.14545.31.camel@thor.holligenstrasse29.lan \
--to=michel@daenzer.net \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).