Hans du Plooy wrote:
On Sun, 2006-09-03 at 17:54 -0800, John Andersen wrote:
The issue was whether ATI cards work with Linux. I know firsthand they do. In fact, I'm running one right now and haven't had a problem with it. Sax should work as well as the ATI cards. Yes, I understand that. But if he JUST purchased it, its probably new enough to require the proprietary drivers, which are available but Not necessarily bundled.
The ATI driver I needed *was* bundled with Suse 9.3. If a driver is available but isn't bundled with the distribution, this is a question to ask the distributor and doesn't reflect on ATI.
The installation becomes different and somewhat more problematic than you are used to.
(1) This depends on what "you are used to" is. (2) This mailing list operates quite differently from what I'm used to and, for many, problematic, but all you need to do is change your email client. :) (Let's talk about that again.) Cowboys like when things are inconvenient. And there seems to be ever more cowboys. (3) Before buying a machine to run Linux on (or any other OS), check to make sure that the components support the OS. (4) ATI's web site has *very* thorough documentation on installing and upgrading their drivers.
Exactly like nVidia. Better even, because it's only the newer cards that need the driver. With nVidia it's *all* their cards, and to make matters worse, they've dropped support for their older cards from the driver.
The ATI cards I have used have worked since SuSE 7.1, but then the chipset is the 7900, not the newer ones.
The ones after 7x00 do work. Load the driver, just like you would do with nVidia, and it will work.
The biggest problem seems to be Sax2 having trouble with it. On all my machines it misdetects the screen properties. This is not the driver's fault, I haven't experienced the same problem in other distros.
Same here. Is, however, the problem really just with Suse? I get a wrong card designation with lspci. This isn't Suse-specific. I don't know... is the problem with sax or is it some other app/utility which sax is calling? More importantly, why is it taking so long to fix this? (I reported this problem a year ago.) ken