From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: ATI Radeon 9550
Date: Wed, 10 Jan 2007 17:25:24 +0000 (UTC) [thread overview]
Message-ID: <loom.20070110T135311-576@post.gmane.org> (raw)
In-Reply-To: 45A45BD6.1020905@verizon.net
Sean <tech.junk <at> verizon.net> writes:
> Anyway, have had nothing but problems trying to get
this thing working.
> Found many bugs listed against the ati-drivers, and
not having much more
> success using the open source drivers also listed in
the Gentoo ATI faq.
> Before I go much further, or post for any help here,
have any others
> here managed to get this card working on Gentoo,
Hello Sean,
I do not have a 9550 card, but, here are a few resources
and suggesting
that I have found that might help. I did get my ATI 1900
to work, but,
only after quit a lot of pain....
1. unmask the lastest ATI drivers ( as the ATI web
sites says there
are lots of bug fixes in 8.32.5) and install it. It
was the only version
that worked on my ati 1900 card.
http://www2.ati.com/drivers/linux/linux_8.32.5.html
2. Pay very close attention to your xorg.conf file.
Mine ended up being
quite different that my "radeon" driver based systems.
I used 'xorgconfig' to generate the intial xorg.conf
file. From there,
I just addressed each issue individually. If web
pages(wikis) do not specifically
talk about version 8.30.x or later, ignore them. They
are out of date
and none I tried to follow were very useful. These old
web pages are about
95% of the problem with getting ati-drivers to work,
as most reverence
old 2.6 kernels and xorg (before 7.0).....
3. Run 'lspci -v' and then Look at this web page to
see exactly which
video card you have. There is quite a lot of
'disinformation' floating
about between vendors being deceptive and
inacccurate/old web pages
concerning video hardware.
http://pci-ids.ucw.cz/iii//?i=1002
http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html#4_nodevice
http://www.thinkwiki.org/wiki/Fglrx#Building_for_Xorg_7.0
http://www.legionhardware.com/document.php?id=596
http://www.gentoo.org/doc/en/ati-faq.xml
http://en.wikipedia.org/wiki/Radeon_R300
http://post.gmane.org/post.php?group=gmane.linux.gentoo.user&followup=177360
hth,
James
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-01-10 17:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-10 3:21 [gentoo-user] ATI Radeon 9550 Sean
2007-01-10 4:30 ` Mark Kirkwood
2007-01-10 4:56 ` [gentoo-user] " Grant Edwards
2007-01-10 9:45 ` Neil Bothwick
2007-01-10 14:42 ` Grant Edwards
2007-01-10 15:37 ` Neil Bothwick
2007-01-11 8:14 ` [gentoo-user] " Mark Kirkwood
2007-01-11 14:09 ` sean
2007-01-11 23:35 ` Mark Kirkwood
2007-01-14 22:53 ` Mark Kirkwood
2007-01-14 23:23 ` [gentoo-user] Problem with kernel 2.6.18-r6 Iván Pérez Domínguez
2007-01-14 23:27 ` Iván Pérez Domínguez
2007-01-15 11:59 ` Nelson, David (ED, PAR&D)
2007-01-10 12:58 ` [gentoo-user] ATI Radeon 9550 William Kenworthy
2007-01-10 17:25 ` James [this message]
2007-01-11 14:19 ` [gentoo-user] " sean
2007-01-11 16:35 ` Neil Bothwick
2007-01-11 17:54 ` Sean
2007-01-11 22:35 ` James
2007-01-12 17:29 ` sean
2007-01-12 23:47 ` James
2007-01-14 21:49 ` sean
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=loom.20070110T135311-576@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@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