AMD 8.38.6 Display Driver Released -- The Least To Report On Driver In Two Years

[fangorious]

modelines?

Did custom modelines ever get put back in? I gave up and stopped paying attention a while back. I can't use any non-native widescreen resolutions with my 1920x1200 screen with fglrx. The OSS drivers used to work for this without custom modelines, but in Ubuntu 7.04 X crashes when I change resolution with the OSS driver.

[yoshi314]

i'd rather have ati release their drivers after they change something, instead of rushing them to catch up with the deadlines.

e.g. release new driver after some serious bugfix has been commited, or after new functionality has been introduced. instead of releasing once per month, no matter what got broken in the meantime.

[d2kx]

The point is that AMD is doing some weird things and you'll should forget about the AMD release cycle. I'd like to tell you more about it but I don't have any proofs or information.

[Raven3x7]

d2kx whats your point?

[d2kx]

Okay, ATI just released 8.39 for Windows Vista. They say it's because of a Lost Planet bug. No, they just wanted to release a newer driver. Don't believe me? Then wait until Catalyst 7.7 is out. I bet it doesn't take long after that and they release hotfixes for WinXP and WinVista again with any false reason again.

[d2kx]

Okay there were 2 (!) driver updates for Windows since 8.38 was released. They do that every month now... both driver updates are officially released "because of a Crossfire bug". But no, they just need a reason to release NonWHQL driver updates... two hotfixes for the same problem that would be addressed if they really test the drivers... why don't they do the same with Linux? I know! Because the Linux coder instead of the 50 Windows coders doesn't even know what gcc is, at least it looks so.

[uhoh]

So if this release doesn't work with xserver 1.3, I guess that means it's broken for Debian Unstable as well?

What a f***ing joke! Who cares about "video tearing" when the driver doesn't even START on recent distributions?

And what is the point of a 3 month long QA test if the current drivers aren't usable? How is it possible to have a 3 month long QA test for each release and still not do anything about all the extremely annoying bugs in the unofficial bugzilla, such as the screen corruption and mouse corruption? Do they spend 3 months to make sure the problems are still there?

Is there a place where we can get beta drivers 3 months early? I couldn't care less about the poor excuse for "QA" that ATI is so proud of.

I'm almost considering quitting my current job just to get rid of the piece of s**t ATI laptop I'm being forced to use.

[yoshi314]

the thing is - we are not ati's customers. we buy our gfx cards off 3rd party companies that use ati's chips. (e.g. gigabyte or sapphire).

and that sucks.

my card isn't even recognized as an original ati card, and instead as an 3rd party card by fglrx (gigabyte x1300pro). might become unsupported at any moment if something snaps in ati's management heads.

[lowlands]

There will be no special driver release out in the next week or two.

Yeah that's what I learned from the roadmap you published (thanks!) so hell will prolly freeze over before ATI will deviate from their development cycle. Nevertheless I wanted to get my opinion out on this subject. Who knows, maybe one day ATI will actually listen to their customers.

[domzanator]

I've just got it up and running on Fedora 7 after afew alterations:-

Had to downgrade my x server-
rpm -U --oldpackage xorg-x11-server-Xorg-1.2.0-6.fc7.i386.rpm

Ran the ati.run file; installed custom with kernel modules:-

Then there was a dependency that i was missing; which i grabbed with yum -
yum install compat-libstdc++-33

Once that is all done just add fglrx into you xorg file and away you go.

So far i haven't tried enabling DRI. I'm using a Mobility X1700... So far so good. Once the open-source ati driver kicks it to second gear with AIGLX support i'm gonna swap over. Until then i would say stick with what you've got.

Peace out,
Dom

Hey guys,

Just a quicky for all you FC7 lovers out there...
I stumbled upon a hickup when i did a yum update; it updated my xorg-x11-org from 1.2 back to 1.3. Good way to avoid this is:-

vi /etc/yum.conf

[main]
cachedir=/var/cache/yum
keepcache=0
debuglevel=2
logfile=/var/log/yum.log
exactarch=1
obsoletes=1
gpgcheck=1
plugins=1
exclude=xorg-x11-server-Xorg*
metadata_expire=1800
xorg-x11-server-Xorg*
# PUT YOUR REPOS HERE OR IN separate files named file.repo
# in /etc/yum.repos.d

-----------

adding the exclude=xorg-x11-server-Xorg*


however i was too late and my yum update over wrote my xorg server...

now that yum has updated it all; there will be a dependency with ati fc7 driver with the update xorg... best was to fix this is with the following line:-

rpm -U --oldpackage xorg-x11-server-Xorg-1.2.0-6.fc7.i386.rpm --nodeps


And thats my 2 cents,

Peace...
Dom