Spyre

New Features

This section provides information on new features introduced in the latest release of the ATI Proprietary Linux driver. This include:

* New Product Support
* Xorg 7.0 Support
* Display Power Management Signaling Support

New Product Support

This release of the ATI Proprietary Linux driver introduces support for the following ATI products:

* FireGL™ V7350
* FireGL™ V7300
* FireGL™ V7200
* FireGL™ V5200
* FireGL™ V3400
* FireGL™ V3350
* FireGL™ V2200

Xorg 7.0 Support

Xorg 7.0 is now supported by the ATI Proprietary Linux installer.
Display Power Management Signaling Support

This release of the ATI Proprietary Linux driver now enables Display Power Management Signaling (DPMS) support in the software display driver by default. The option to disable DPMS support is still available to users by referring to aticonfig --help.
Resolved Issues

The following section provide a brief description of resolved issues with the latest version of the ATI Proprietary Linux driver. These include:

• Running two X servers simultaneously no longer results in the system failing to respond. Further details can be found in topic number 737-220
• X Server no longer fails to load when using an ATI Radeon® X1x00, 512MB product with certain motherboards. Further details can be found in topic number 737-22056
• Toggling between console mode and X Server graphical mode no longer results in a system hang. Further details can be found in topic number 737-22058
• Executing the command aticonfig --tv-format-type=NTSC-M no longer results in NTSC-M being detected as an invalid TV standard. Further details can be found in topic number 737-22386
• The option --get-supported for the ATI installer has been replaced by the option --listpkg. Further details can be found in topic number 737-22387
• User page lock is no longer available for AGP products resulting in a number of options (--agpl, --agp-locked-userpages, --agplock, --iagp, and --internal-agp) being removed from aticonfig and being replaced by the option --locked-userpages. The internal agp GART is no longer provided. Further details can be found in topic number 737-22388
• Attempting to enable clone mode or extended desktop mode no longer results in the secondary display device failing to activate when using the ATI Control Panel. Further details can be found in topic number 737-22392
• Using aticonfig --resolution to configure the display resolution no longer results in the user defined resolution failing to take effect. Further, using the option of aticonfig --resolution2 to configure the secondary display resolution no longer results in the user defined resolution failing to take effect. The option of --resolution2 is now obsolete but its functionality can still be obtained by referring to the --resolution part of the aticonfig --help. Further details can be found in topic number 737-22393
• The software driver now supports Linux kernels that have NUMA support enabled on x86_64 machines. Further details can be found in topic number 737-22394
• A segmentation fault no longer occurs when attempting to initialize an incomplete X Server configuration file using aticonfig -f. Further details can be found in topic number 737-22395
• aticonfig --initial now fills in the VendorName and ModelName sections of the X Server configuration file for increased compatibility for SuSE's SaX2. Further details can be found in topic number 737-22396

Known Issues

The following section provides a brief description of known issues associated with the latest version of ATI Proprietary Linux driver. These issues include:

• Attempting to install the ATI Proprietary Linux driver on distributions that have updated certain 3D components outside of the stock XOrg 6.8.2 may result in the driver not initializing 3D applications properly. Further details can be found in topic number 737-20868
• TV display is corrupt after switching resolutions. Further details can be found in topic number 737-1086
• TV Out is currently not supported on the ATI Radeon® X1x00 products. Further details can be found in topic number 737-22057
• A system hang may occur when attempting to resume from hibernation mode. Further details can be found in topic number 737-22059

__________________
ATI Beta Tester
game.AMD.Moderator

rob2687

About time....Now lets see if the x1900 will finally work.

grog

Greg likes!


Direct link to image
http://img222.imageshack.us/img222/6...apshot28oi.jpg

Fedora Core 5 x86_64 version is running very well with the new drivers.

I did have to comment out the (Load "extmod") in the "xorg.conf" file and I have not had time yet to find out why yet.

I am running the 2.6.16.18 stock kernel from kernel.org!

So far this looks sweet.

__________________
Dell UltraSharp 2405FPW 24" LCD
Philips 47" 1080p 47pfl7422d/37 LCD
ASUS M3A32-MVP Deluxe/WiFi BIOS 1406, AMD Phenom 9600 Agena 2.3GHz, G.SKILL 8GB(4 x 2GB) 240-Pin DDR2 (PC2 6400)
ASUS EAH4850 TOP/HTDI/512M PCI Express 2.0
Creative Sound Blaster X-Fi Elite Pro Sound Card, 1TB Hard Disk storage
Thermaltake Tai-Chi VB5001SNA Black/ Silver Computer Case with liquid cooling
AeroCool GateWatch-SV Silver GateWatch with LCD display, PC Power & Cooling 510 SLI-PFC 510W
APC Back-UPS XS 1000 UPS, 1000 VA, 600 Watts
Microsoft Windows Vista Ultimate SP1 64-bit
VM's (Fedora, RHEL4..etc)
Klipsch ProMedia Ultra 5.1

rob2687

How do you get the ATI control panel thing?

UberLord

About time

Removing the GART is a good move as that encorages GART development to happen in the kernel which is where it belongs.

This should be next on the hit-list imo as more and more laptops are coming onto the market. I didn't really want an ATI card in my laptop because of this (ok, and a few other) reasons, but the laptops I wanted all had ATI cards in em - lol.

Now if they could fix using the fglrx driver AND the radeonfb driver as using the VESA fb driver sucks for 1600x1050x24 as it can't do it
OK, it means that they'll probably have to donate code to the kernel, but it would be a good move as AFAIK nVidia don't support nvfb either.

All in all, with the above bugs fixed this is probably the best release since ATI gave us 64-bit goodness I'll get around to actually playing some games later

__________________
Gentoo Linux - Developer (baselayout)
Read my blog

"I contend that we are both atheists. I just believe in one fewer god than you do. When you understand why you dismiss all the other possible gods, you will understand why I dismiss yours."
Stephen Roberts

beerad

I tried to install the rpm yesterday on Fedora 4 w/ 2.6.16.16 kernel, and it failed immediately (didn't even install the 2d drivers) due to a failed dependency on libextmod.so.1. I checked around a little, and it is provided by extmod 2.0, which I couldn't find packaged for x86_64 fc4 or fc5. I'll have to check into this more.. Thanks for the status report!

RIV@NVX

I just installed this from rpm.livna.org. I didn't expect much, but when I read this... Wow, this is getting strange... So many fixes in a single release? And so many good fixes (X.org 7, removal of internal GART...)?

I'm very happy about it! What else to say, way to go, ATI!

Now if they could only fix the "A system hang may occur when attempting to resume from hibernation mode. Further details can be found in topic number 737-22059" too...

/me goes to install NWN to test new drivers and "new" NWN patch a bit...

__________________
-- Vedran

UberLord

Yeah, strange. Let's hope they keep it up

BTW, the xorg 7 "fix" is just their installer which most distros probably don't use. The fglrx driver has always worked with xorg 7

__________________
Gentoo Linux - Developer (baselayout)
Read my blog

"I contend that we are both atheists. I just believe in one fewer god than you do. When you understand why you dismiss all the other possible gods, you will understand why I dismiss yours."
Stephen Roberts

RIV@NVX

Yeah, I know, I have been using rpm.livna.org RPMs for a while with X.org 7. But, still, it's nice to see it "officially" supported.

__________________
-- Vedran

mansanlop

I may not appreciate all the details and marvels of the latest driver, but cannot but be disapointed.
My reason: 3D accelleration works in my Xpress200M only after disabling all memory for sideport
and using only system memory. As it works for XP, this seems a never-to-be-solved problem with ATI's driver... System: Compaq Presario R4000 AMD64, Suse9.3 kernel 2.6.11.4-21-12. x86-64

RIV@NVX

Does this problem happen in 32-bit mode as well?

__________________
-- Vedran

mansanlop

I can't say. I use my laptop for everyday work and have a lot of data there. I'm thus
reluctant to undertake any big change as going back to 32bit. Why would this depend
on that, being there the (less than satisfactory) workaround of changing BIOS settings?

After all, 64bit systems have been there already for more than 2 years, Xpress200M for more than 1yr and AMD is delivering only 64bit cores now...

BDR518

Ok I will admit I am pretty new to this whole thing, but I'm on the edge of pulling out my hair. I read the following line in the fixed column and I don't know if this is the problem or not, but it's so far the closest thing I can figure.

"X Server no longer fails to load when using an ATI Radeon® X1x00, 512MB product with certain motherboards. Further details can be found in topic number 737-22056"

Since there is no more topic 737-22056 (at least that you can search for at support.ati.com) I can't tell. But here is the issue. I'm running a Pent4 3ghz processor on a Foxxconn 915 series Mainboard, and a Asus EAX1600PRO PCIE 16 w/ 512 mb of vidram. System ram is at 2GB and I'm running the 64bit SuSE 10.1 distro. When I install the drivers (tried multiple methods from multiple walkthroughs incl ATI's directions) The result is always the same. On reboot xWindows will not load. It gives me a huge log file and I can't make ends meet out of it other than the ChipID IS correct (read about that problem w/ asus too). I am lost, if anyone can help or point me to a post (in my search of the forums this is the closest I've found), or website it would save me from premature baldness :-P