From: Joshua Baergen <joshuabaergen@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ATI Radeon Xpress 200 Drivers
Date: Tue, 28 Jun 2005 18:08:05 -0600 [thread overview]
Message-ID: <5e0a35ef05062817085dce6676@mail.gmail.com> (raw)
In-Reply-To: <42C161C2.1070204@cdf123.net>
This might be a problem with the drivers as well. I have seen this
issue on other systems with various ATI cards and I have yet to come
across the solution for it.
On 6/28/05, Chris Frederick <cdf123@cdf123.net> wrote:
> Luca Barbato wrote:
> > Chris Frederick wrote:
> >
> >
> >>I'd be happy to help test. Is there any testing methodology that I
> >>should follow? Or any specific application I should test, or xorg
> >>config settings I should try?
> >
> >
> > Just unmask and emerge the .13.4 driver as usual and use it as a
> > standard ati-driver. If it works as should that means that I repackaged
> > it correctly and requires no other patching...
> >
> > lu
> >
>
> Everything works. The only problem is that it appears to be painfully
> slow. I have 4M generic video cards from the mid 90's that are giving
> faster framerates, and this thing is in an amd64 3K. I'm going to check
> the bios tonight, the board is using shared memory, and I might have set
> it really low since it wasn't working before. Other than that it's
> working well.
>
> Thanks
>
> Chris Frederick
>
> --
> gentoo-dev@gentoo.org mailing list
>
>
--
Joshua Baergen
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2005-06-29 0:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-25 22:35 [gentoo-dev] ATI Radeon Xpress 200 Drivers Chris Frederick
2005-06-26 0:04 ` Luca Barbato
2005-06-27 14:53 ` Chris Frederick
2005-06-27 21:24 ` Luca Barbato
2005-06-28 14:42 ` Chris Frederick
2005-06-29 0:08 ` Joshua Baergen [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=5e0a35ef05062817085dce6676@mail.gmail.com \
--to=joshuabaergen@gmail.com \
--cc=gentoo-dev@lists.gentoo.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