From: Miles Lane <miles.lane@comcast.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: linuxppc-2.5 (mvista rsync) -- Please push changesets for AGPGART / RadeonFB / Radeon DRI to Linus
Date: Sat, 2 Aug 2003 18:32:08 -0700 [thread overview]
Message-ID: <200308021832.08242.miles.lane@comcast.net> (raw)
Hi,
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.
I have a:
ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500]
Also, if there are other changesets that should be in 2.6.0, this might
be a good time to get those in, right?
Thanks!
Miles
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-08-03 1:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 1:32 Miles Lane [this message]
2003-08-03 17:04 ` linuxppc-2.5 (mvista rsync) -- Please push changesets for AGPGART / RadeonFB / Radeon DRI to Linus Michel Dänzer
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=200308021832.08242.miles.lane@comcast.net \
--to=miles.lane@comcast.net \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).