View Full Version : New ATI graphic driver
ghaefb
16th February 2005, 10:17 PM
ATI has released new and improved ATI Proprietary Linux Driver version 8.10.19.
Mainly just bugfixes in this release.
Read the release notes - here (http://www2.ati.com/drivers/linux/linux_8.10.19.html)
Download - here (http://www.ati.com/support/driver.html)
cardinal II
17th February 2005, 12:49 AM
:edited: Stupid comment.
Anyone know how long it will take for a new set of xorg drivers compatible with the recently released 766 kernel to show up on livna?
Shadow Skill
17th February 2005, 06:26 AM
Exscuse me I have 64bit hardware specifically an x600 pro 256mb gfx card but I am running 32 bit fc3 for the moment, would it be ok for me to use Livna's rpm to get 3d acceleration?
yaconsult
17th February 2005, 08:09 AM
This new driver gives me an improvement of around 200 FPS on fgl_glxgears compared to the version released about a month ago.
This is on a Radeon 9800 XT on my 3.2 GHz system.
Yeah, I know it's a crappy benchmark, but it's all I've got to go on, except for the fact that X seems to start up faster as well.
Good job, ATI!
a50sn95
17th February 2005, 09:00 AM
Install was as simple as using ATI's instructions.
$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9600 Generic
OpenGL version string: 1.3.4893 (X4.3.0-8.10.19)
GLXgears reports
$ glxgears
7905 frames in 5.0 seconds = 1581.000 FPS
8824 frames in 5.0 seconds = 1764.800 FPS
8825 frames in 5.0 seconds = 1765.000 FPS
8823 frames in 5.0 seconds = 1764.600 FPS
This is on an AMD64 FC3 2.6.10-1.766_FC3
I did log on as root, but other than that....
Sennis
cardinal II
17th February 2005, 01:45 PM
I just installed them using ATI's instructions. Works like a charm so far *fingers crossed*
2635 frames in 5.0 seconds = 527.000 FPS
2708 frames in 5.0 seconds = 541.600 FPS
2698 frames in 5.0 seconds = 539.600 FPS
2708 frames in 5.0 seconds = 541.600 FPS
2719 frames in 5.0 seconds = 543.800 FPS
2670 frames in 5.0 seconds = 534.000 FPS
Hehe, is that decent? My system is getting long in the tooth. 2600+ Athlon Thoroughbred, 9600 XT
ghaefb
17th February 2005, 02:05 PM
Minimize glxgears window and then post results..
cardinal II
17th February 2005, 02:20 PM
Ah, that made a difference.
4667 frames in 5.0 seconds = 933.400 FPS
4662 frames in 5.0 seconds = 932.400 FPS
4658 frames in 5.0 seconds = 931.600 FPS
4661 frames in 5.0 seconds = 932.200 FPS
4664 frames in 5.0 seconds = 932.800 FPS
4660 frames in 5.0 seconds = 932.000 FPS
4663 frames in 5.0 seconds = 932.600 FPS
a50sn95
17th February 2005, 03:18 PM
Oh, minimize GLX gears?
well then:
$ glxgears
12561 frames in 5.0 seconds = 2512.200 FPS
19328 frames in 5.0 seconds = 3865.600 FPS
19328 frames in 5.0 seconds = 3865.600 FPS
19324 frames in 5.0 seconds = 3864.800 FPS
18679 frames in 5.0 seconds = 3735.800 FPS
Even better!
tpcolson
17th February 2005, 06:12 PM
Not working so well with X800 cards:
Bug 90 (http://ati.cchtml.com/show_bug.cgi?id=90) Bug 91 (http://ati.cchtml.com/show_bug.cgi?id=91)
Any one get it working in 2.6.10 with any x series card?
skoona
17th February 2005, 06:34 PM
Results from 8.8.25 on 766_FC3, Dual AMD 2400+MP, ATI 9600/128
[jscott@skoona ~]$ glxgears
3536 frames in 5.0 seconds = 707.200 FPS
4071 frames in 5.0 seconds = 814.200 FPS
4081 frames in 5.0 seconds = 816.200 FPS
9491 frames in 5.0 seconds = 1898.200 FPS
19162 frames in 5.0 seconds = 3832.400 FPS (Covered up window)
19140 frames in 5.0 seconds = 3828.000 FPS
19161 frames in 5.0 seconds = 3832.200 FPS
19173 frames in 5.0 seconds = 3834.600 FPS
19173 frames in 5.0 seconds = 3834.600 FPS
[jscott@skoona ~]$ fgl_glxgears
632 frames in 5.0 seconds = 126.400 FPS
840 frames in 5.0 seconds = 168.000 FPS
849 frames in 5.0 seconds = 169.800 FPS
827 frames in 5.0 seconds = 165.400 FPS
845 frames in 5.0 seconds = 169.000 FPS
1634 frames in 5.0 seconds = 326.800 FPS (Covered up window)
2485 frames in 5.0 seconds = 497.000 FPS
2488 frames in 5.0 seconds = 497.600 FPS
2490 frames in 5.0 seconds = 498.000 FPS
2488 frames in 5.0 seconds = 497.600 FPS
I'm about to load the update now. Let's see what the new results are.
Shadow Skill
17th February 2005, 06:56 PM
no one knows if its safe to try the 32bit rpms on 64 bit hardware? Oh well I'll go ry it and see.
Update:
It appears to work after some minor Xorg.conf edits fglrxinfo is spamming the right data, This is my glxgears output using the new drivers from ati I never installed Livna's.12012 frames in 5.0 seconds = 2402.400 FPS
12679 frames in 5.0 seconds = 2535.800 FPS
13693 frames in 5.0 seconds = 2738.600 FPS
13693 frames in 5.0 seconds = 2738.600 FPS
13698 frames in 5.0 seconds = 2739.600 FPS
13693 frames in 5.0 seconds = 2738.600 FPS
13693 frames in 5.0 seconds = 2738.600 FPS
13695 frames in 5.0 seconds = 2739.000 FPS
13693 frames in 5.0 seconds = 2738.600 FPS
13690 frames in 5.0 seconds = 2738.000 FPS
13692 frames in 5.0 seconds = 2738.400 FPS
Does this look good to you all? I have an x600 pro pci express 256mb card.
skoona
17th February 2005, 08:40 PM
# fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9600SE Generic
OpenGL version string: 1.3.4893 (X4.3.0-8.10.19)
# glxgears
4403 frames in 5.0 seconds = 880.600 FPS
4750 frames in 5.0 seconds = 950.000 FPS
4751 frames in 5.0 seconds = 950.200 FPS
4751 frames in 5.0 seconds = 950.200 FPS
4751 frames in 5.0 seconds = 950.200 FPS
9837 frames in 5.0 seconds = 1967.400 FPS (Covered Up)
19246 frames in 5.0 seconds = 3849.200 FPS
19247 frames in 5.0 seconds = 3849.400 FPS
19246 frames in 5.0 seconds = 3849.200 FPS
19246 frames in 5.0 seconds = 3849.200 FPS
# fgl_glxgears
918 frames in 5.0 seconds = 183.600 FPS
947 frames in 5.0 seconds = 189.400 FPS
949 frames in 5.0 seconds = 189.800 FPS
946 frames in 5.0 seconds = 189.200 FPS
1741 frames in 5.0 seconds = 348.200 FPS (Covered Up)
2553 frames in 5.0 seconds = 510.600 FPS
2550 frames in 5.0 seconds = 510.000 FPS
2551 frames in 5.0 seconds = 510.200 FPS
2545 frames in 5.0 seconds = 509.000 FPS
2551 frames in 5.0 seconds = 510.200 FPS
Initial results show a satisfactory result, and X/GNOME responds and starts faster. Thanks ghaefb, for keeping up with this driver.
James,
JayRx1981
17th February 2005, 10:11 PM
glxgears
20001 frames in 5.0 seconds = 4000.200 FPS
23197 frames in 5.0 seconds = 4639.400 FPS
22949 frames in 5.0 seconds = 4589.800 FPS
37018 frames in 5.0 seconds = 7403.600 FPS (covered)
40674 frames in 5.0 seconds = 8134.800 FPS
40687 frames in 5.0 seconds = 8137.400 FPS
40700 frames in 5.0 seconds = 8140.000 FPS
fgl_glxgears
4100 frames in 5.0 seconds = 820.000 FPS
4442 frames in 5.0 seconds = 888.400 FPS
4460 frames in 5.0 seconds = 892.000 FPS
4428 frames in 5.0 seconds = 885.600 FPS
5259 frames in 5.0 seconds = 1051.800 FPS (covered)
7062 frames in 5.0 seconds = 1412.400 FPS
7127 frames in 5.0 seconds = 1425.400 FPS
7116 frames in 5.0 seconds = 1423.200 FPS
I'm running an Athlon64 3000, a Radeon 9800Pro with 128MB of Ram, and 1.5GB of PC3200 RAM on FC3, with a custom compiled 2.6.10 kernel. Not bad. Granted, we probably need a better benchmark than glxgears and fgl_glxgears, but still pretty admirable.
I would be curious to see how these numbers compare with a comparable NVidia card running NVidia's latest driver release though. It's all well and good to say these are good results if they match up, but if the nvidia cards leave us ati owners in the dust, well that's kindof stinky.
Shadow Skill
17th February 2005, 10:33 PM
now I cant make my windows transparent :( and the fade in effects totally bork the browser window...blah
skoona
18th February 2005, 12:31 AM
FYI:
a '$ dmesg' on my machine HAD a 'vmalloc <size>' failed message indicating that the fglrx driver had sometype of problem during startup. I added 'vmalloc=256m' to the boot parms in grub and this took care of the problem. Don't know that I see a real difference other than the error message is gone.
256m happens to be the memory size of my ATI card.
Shadow Skill
18th February 2005, 01:23 AM
did you add it to your grub.conf? If so what does yours look like now?
sirrahd
18th February 2005, 01:57 AM
Looks good! I'd also be curious to find out what nvidia cards do with similar setups.
[drew@drew ~]$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9800 Pro Generic
OpenGL version string: 1.3.4893 (X4.3.0-8.10.19)
[drew@drew ~]$ glxgears
34924 frames in 5.0 seconds = 6984.800 FPS
40926 frames in 5.0 seconds = 8185.200 FPS (covered here down)
40938 frames in 5.0 seconds = 8187.600 FPS
40935 frames in 5.0 seconds = 8187.000 FPS
40936 frames in 5.0 seconds = 8187.200 FPS
[drew@drew ~]$ fgl_glxgears
5220 frames in 5.0 seconds = 1044.000 FPS
7272 frames in 5.0 seconds = 1454.400 FPS (covered here down)
7262 frames in 5.0 seconds = 1452.400 FPS
7273 frames in 5.0 seconds = 1454.600 FPS
7230 frames in 5.0 seconds = 1446.000 FPS
I have an AMD64 3200+, Radeon 9800 Pro, 1GB DDR400.
skoona
18th February 2005, 02:33 AM
[root@skoona ~]# fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9600SE Generic
OpenGL version string: 1.3.4893 (X4.3.0-8.10.19)
[root@skoona ~]# glxgears
4689 frames in 5.0 seconds = 937.800 FPS
4752 frames in 5.0 seconds = 950.400 FPS
4752 frames in 5.0 seconds = 950.400 FPS
4752 frames in 5.0 seconds = 950.400 FPS
9952 frames in 5.0 seconds = 1990.400 FPS (Covered up)
19235 frames in 5.0 seconds = 3847.000 FPS
19234 frames in 5.0 seconds = 3846.800 FPS
19237 frames in 5.0 seconds = 3847.400 FPS
12262 frames in 5.0 seconds = 2452.400 FPS
[root@skoona ~]# fgl_glxgears
819 frames in 5.0 seconds = 163.800 FPS
940 frames in 5.0 seconds = 188.000 FPS
951 frames in 5.0 seconds = 190.200 FPS
937 frames in 5.0 seconds = 187.400 FPS
947 frames in 5.0 seconds = 189.400 FPS
944 frames in 5.0 seconds = 188.800 FPS
943 frames in 5.0 seconds = 188.600 FPS
946 frames in 5.0 seconds = 189.200 FPS
1999 frames in 5.0 seconds = 399.800 FPS (Covered up)
2531 frames in 5.0 seconds = 506.200 FPS
2542 frames in 5.0 seconds = 508.400 FPS
2540 frames in 5.0 seconds = 508.000 FPS
2536 frames in 5.0 seconds = 507.200 FPS
[root@skoona ~]# grep vmalloc /boot/grub/grub.conf
kernel /vmlinuz-2.6.10-1.766_FC3smp ro root=LABEL=/ rhgb quiet vmalloc=256m
Yes, I added it to my grub.conf (after testing it manually first ). It mainly got rid of the error message, and a few tweaks more performance.
ghaefb
18th February 2005, 05:50 AM
Nvidia FX5200 128mb:
[ghaefb@mycomp ~]$ glxgears
22101 frames in 5.0 seconds = 4420.200 FPS
36787 frames in 5.0 seconds = 7357.400 FPS
36280 frames in 5.0 seconds = 7256.000 FPS
37079 frames in 5.0 seconds = 7415.800 FPS
36870 frames in 5.0 seconds = 7374.000 FPS
36925 frames in 5.0 seconds = 7385.000 FPS
36677 frames in 5.0 seconds = 7335.400 FPS
tpcolson
18th February 2005, 01:26 PM
Code:
--- firegl_public.c 2004-03-17 17:00:29.000000000 -0500
+++ /lib/modules/fglrx/build_mod/firegl_public.c 2004-07-18 16:09:46.000000000 -0500
@@ -2010,8 +2010,8 @@
pMmPage = virt_to_page(kaddr);
#endif /* LINUX_VERSION_CODE < 0x020400 */
- atomic_inc(&(pMmPage->count)); /* inc usage count of page */
-
+// atomic_inc(&(pMmPage->_count)); /* inc usage count of page */
+ get_page(pMmPage);
#if LINUX_VERSION_CODE >= 0x020400
// __KE_DEBUG3("vm-address 0x%08lx => kernel-page-address 0x%p\n",
// address, page_address(pMmPage));
skoona
18th February 2005, 02:07 PM
Code:
--- firegl_public.c 2004-03-17 17:00:29.000000000 -0500
+++ /lib/modules/fglrx/build_mod/firegl_public.c 2004-07-18 16:09:46.000000000 -0500
@@ -2010,8 +2010,8 @@
pMmPage = virt_to_page(kaddr);
#endif /* LINUX_VERSION_CODE < 0x020400 */
- atomic_inc(&(pMmPage->count)); /* inc usage count of page */
-
+// atomic_inc(&(pMmPage->_count)); /* inc usage count of page */
+ get_page(pMmPage);
#if LINUX_VERSION_CODE >= 0x020400
// __KE_DEBUG3("vm-address 0x%08lx => kernel-page-address 0x%p\n",
// address, page_address(pMmPage));
Is this all there is to the patch ? Which directory should i be in to apply? I think a
$cd /lib/modules/fglrx/build_mod
$ patch -p1 <this_file
$ sh make.sh
$ cd ..
$ sh make_install.sh
$ shutdown -r now
will implement the above patch correctly - Do you agree ?
PsyMan
18th February 2005, 10:04 PM
Finally got the drivers working. just needed to set the internal AGP to no after following ATI instructions and it worked. Thanks for that tip.
19393 frames in 5.0 seconds = 3878.600 FPS(moving window :P )
23455 frames in 5.0 seconds = 4691.000 FPS
23455 frames in 5.0 seconds = 4691.000 FPS
40714 frames in 5.0 seconds = 8142.800 FPS (covered)
40708 frames in 5.0 seconds = 8141.600 FPS
40713 frames in 5.0 seconds = 8142.600 FPS
Athlon 64 3000+ - 1.25Gb 400mhz DDR - Asus KV8 SE Deluxe mobo
skoona
19th February 2005, 04:07 AM
Are most people using the Drivers internal AGP, or Linux's external (regular) APG ?
ATIR350
19th February 2005, 05:34 AM
On installing the ATI driver on a fresh FC3 installation, this is wt I get:
[root@localhost ~]# rpm -Uh --force /root/Desktop/fglrx_6_8_0-8.10.19-1.i386.rpm
########################################### [100%]
########################################### [100%]
make.sh: line 46: gcc: command not found
make.sh: line 52: [: !=: unary operator expected
[root@localhost ~]#
Using Radeon 9100.....wt the heck is going on?
a50sn95
19th February 2005, 05:40 AM
You don't have all the dependecies installed. You need the GCC package.
DO a
yum install gcc....
ATIR350
19th February 2005, 07:55 AM
You don't have all the dependecies installed. You need the GCC package.
DO a
yum install gcc....
thx for your help, but when I did that and tried installing the ATI driver again, this appeared:
[root@localhost ~]# rpm -Uh --force /root/Desktop/fglrx_6_8_0-8.10.19-1.i386.rpm
########################################### [100%]
########################################### [100%]
FATAL: Error inserting fglrx (/lib/modules/2.6.9-1.667/kernel/drivers/char/drm/fglrx.ko): Operation not permitted
FATAL: Error inserting fglrx (/lib/modules/2.6.9-1.667/kernel/drivers/char/drm/fglrx.ko): Operation not permitted
[root@localhost ~]#
What should I do?
alyster
19th February 2005, 11:43 AM
Well, after much buggering around I got it working.
As a note Laptop mode seems to be causing the silly black screen problem, I thought of actually turning my TV on when the issue occured and lo and behold the video was there (still couldnt play video on it though :( )
$ glxgears
11829 frames in 5.0 seconds = 2365.800 FPS
14406 frames in 5.0 seconds = 2881.200 FPS
14406 frames in 5.0 seconds = 2881.200 FPS
14402 frames in 5.0 seconds = 2880.400 FPS
$ fgl_glxgears
2515 frames in 5.0 seconds = 503.000 FPS
2813 frames in 5.0 seconds = 562.600 FPS
2824 frames in 5.0 seconds = 564.800 FPS
2813 frames in 5.0 seconds = 562.600 FPS
tpcolson
20th February 2005, 02:29 AM
With Xorg 6.8.2
fgl_glxgears
6826 frames in 5.0 seconds = 1365.200 FPS
7582 frames in 5.0 seconds = 1516.400 FPS
7581 frames in 5.0 seconds = 1516.200 FPS
7615 frames in 5.0 seconds = 1523.000 FPS
7496 frames in 5.0 seconds = 1499.200 FPS
# glxgears
37521 frames in 5.0 seconds = 7504.200 FPS
46758 frames in 5.0 seconds = 9351.600 FPS
58527 frames in 5.0 seconds = 11705.400 FPS
62422 frames in 5.0 seconds = 12484.400 FPS
53908 frames in 5.0 seconds = 10781.600 FPS
46659 frames in 5.0 seconds = 9331.800 FPS
47143 frames in 5.0 seconds = 9428.600 FPS
65377 frames in 5.0 seconds = 13075.400 FPS
65635 frames in 5.0 seconds = 13127.000 FPS
63530 frames in 5.0 seconds = 12706.000 FPS
JayRx1981
20th February 2005, 05:13 AM
Wow, those are some nice results! What are you running on to give you those scores?
tpcolson
20th February 2005, 05:21 AM
Dual Xeon 3.2
4 GB PC3200 RAM
RAID 10, 4 70 GB WD 10K RPM Drives on a 3Ware card w/ 256 MB RAM
ATI X800XT card
64 bit version of everything.
Thing is, this is a "gamer" box, but I have, and never will, played a video game. This machine was built out to do rendering of high resolution terrain data for floodplain mapping without having to submit jobs and hope they're done in the morning.
It's still not fast enougth, thinking of going up to 12 GB RAM.
Detour
20th February 2005, 05:36 AM
I installed this version of the driver but fglrxinfo gives an error and lists the mesa driver. I checked xorg.conf and in the screen section for device it says Ati Graphic Driver.. Any ideas what might be wrong?
asun
21st February 2005, 05:30 AM
After installing the new fglrx driver and removing the old one (from livna ati-fglrx package), I cannot use xv output for mplayer. Does anyone have the same problem? Does anyone know how to fix this?
skoona
21st February 2005, 01:42 PM
/etc/X11/xorg.conf
section "Device"
...
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
...
Do you still have these setting set in your config? Until I set mine to these values I could not use tvtime or mplayer-plugin.
asun
22nd February 2005, 12:25 AM
/etc/X11/xorg.conf
section "Device"
...
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
...
Do you still have these setting set in your config? Until I set mine to these values I could not use tvtime or mplayer-plugin.
Yeah, I found out the problem right after I posted :) Apparently when I uninstall ati-fglrx from livna, the xorg.conf is backed up to xorg.conf.backup-ati-fglrx. Then it uses some weird old xorg.conf file as the xorg.conf. I have since fixed the problem.
zuiko
22nd February 2005, 04:52 PM
Code:
--- firegl_public.c 2004-03-17 17:00:29.000000000 -0500
+++ /lib/modules/fglrx/build_mod/firegl_public.c 2004-07-18 16:09:46.000000000 -0500
@@ -2010,8 +2010,8 @@
pMmPage = virt_to_page(kaddr);
#endif /* LINUX_VERSION_CODE < 0x020400 */
- atomic_inc(&(pMmPage->count)); /* inc usage count of page */
-
+// atomic_inc(&(pMmPage->_count)); /* inc usage count of page */
+ get_page(pMmPage);
#if LINUX_VERSION_CODE >= 0x020400
// __KE_DEBUG3("vm-address 0x%08lx => kernel-page-address 0x%p\n",
// address, page_address(pMmPage));
To me this looks like an old patch, and reading in firegl_public.c it looks like ATI has already applied it, but fglrx still causes a vmalloc failure.
skoona
22nd February 2005, 06:17 PM
Yea, I could not get it to apply, so I left the boot parm in place.
zuiko
22nd February 2005, 10:18 PM
Yea, I could not get it to apply, so I left the boot parm in place.
But using vmalloc=256m prevents the kernel from detecting my Promise SATA controller, and I get a kernel panic because that's where my root is.
skoona
23rd February 2005, 03:31 AM
try a smaller number, 128m , 192m, etc. Also, having the vmalloc parm got rid of the syslog message, but I don't think it boosted performance of agp that mauch - if at all. Soooo, skip the vmalloc parm altogether to make your other hardware work.
I will give this feedback to ATI, and maybe on the next release of their driver thay can resolve this vmalloc issue,,, or maybe the next release of FC3+ will resolve it.
zuiko
24th February 2005, 11:14 AM
try a smaller number, 128m , 192m, etc. Also, having the vmalloc parm got rid of the syslog message, but I don't think it boosted performance of agp that mauch - if at all. Soooo, skip the vmalloc parm altogether to make your other hardware work.
A vmalloc larger than 128m (256m, 192m, even 129m) results in a kernel panic when Linux can't find my Promise SATA II 150 TX4. Kernel output looks like this:
ACPI wakeup devices:
HUB0 HUB1 USB0 USB1 USB2 F139 MMAC MMCI UAR1
ACPI: (supports S0 S3 S4 S5)
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device "sda2" or unknown-block(0,0)
Please append a correct "root=" boot option
kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
But X and the fglrx module works with the default vmalloc. I get hardware accelleration, and the error message regarding allocation error. I suspected this error to be related to the strange behavior from a few screen savers, and the hard locks I have experienced. Maybe this is not related and I can live with this error.
This is the important lines from my grub.conf (booting edition):
root=(hd0,1)
kernel /boot/vmlinuz-2.6.10-tx4 ro root=/dev/sda2
initrd /boot/initrd-2.6.10-tx4.img
Appending vmalloc=256m and it will not boot
kernel /boot/vmlinuz-2.6.10-tx4 ro root=/dev/sda2 vmalloc=256m
skoona
24th February 2005, 03:43 PM
I am not using SATA, so maybe that explains why it worked for me. As I look at the code it looks like the vmalloc call (if the one i found is the right one) is trying to get EXTRA workspace. So a failure to get more should have little or no effect for regular desktop usage; Gameplaying or or intense graphics application may be impacted by 10 percent or so.
Certainly, you should leave off the param and ignore the error message. Thanks for the additional detail, I will pass it on to ATI.
Dog-One
26th February 2005, 10:48 PM
Tried it with a clean install FC3 (i686) and all the latest yum updates. Following ATI's instructions, everything seemed to load fine. Tried the tests and a little BZFlag with things tweaked--good performance on this 9600SE card. When I logged out, that's when trouble hit--I was greeted with the infamous black screen of death. Did a few cycles to confirm and the problem is repeatable. I suspect with all the options presented by the config program, something wasn't quite right. Of the folks that have it working properly, did you happen to document what parameters you used and would you post them. An attachment of your xorg.conf file would be useful as well.
Thanks.
skoona
27th February 2005, 01:31 AM
$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9600SE Generic
OpenGL version string: 1.3.4893 (X4.3.0-8.10.19)
I did notice one xorg.conf parm that produced a strange letterbox like effect 'Option "MonitorLayout" ' caused the letterbox effect. The only other thing was which agpart; linux vs the ati drivers agpgart - there was a black screen in that process. I recall that I had to regen the kernel to produce a agpgart module for my AMD760mpx system.
Today I am stable with an ATI 9600SE using one CRT @ 1280x1024 via the attached xorg.conf. I also use a 5-button wheel mouse so ignore that section if you don't have one. glxgears normally produces a 950FPS value, which seems low compared to other reports - but I haven't found param that affects that value very much, so I am done tweaking.
skoona
27th February 2005, 01:39 AM
Dog-One
Tried the tests and a little BZFlag with things tweaked--good performance on this 9600SE card.
What's a BZFlag? And what was your glxgears FPS number?
Dog-One
27th February 2005, 03:25 PM
What's a BZFlag? And what was your glxgears FPS number?
BZFlag is tank battle game that comes with Fedora. You can push all the eye candy settings up to max and get a good idea how well the card is doing.
My glxgears value was right around 5000 minimized.
Thanks for the feedback skoona, I'll do a little more testing and comparison with your settings.
tjmax
27th February 2005, 07:43 PM
Hmm not too shabby atall.
$ glxgears
Open
24302 frames in 5.0 seconds = 4860.400 FPS
24302 frames in 5.0 seconds = 4860.400 FPS
30399 frames in 5.0 seconds = 6079.800 FPS
Closed
40845 frames in 5.0 seconds = 8169.000 FPS
40845 frames in 5.0 seconds = 8169.000 FPS
40815 frames in 5.0 seconds = 8143.000 FPS
$ fgl_glxgears
Open
12217 frames in 5.0 seconds = 2443.400 FPS
12458 frames in 5.0 seconds = 2491.600 FPS
12458 frames in 5.0 seconds = 2491.600 FPS
Closed
14335 frames in 5.0 seconds = 2867.000 FPS
14288 frames in 5.0 seconds = 2857.600 FPS
14336 frames in 5.0 seconds = 2867.200 FPS
14339 frames in 5.0 seconds = 2867.800 FPS
ken52787
28th February 2005, 01:12 AM
Someone please enlighten me, because I've tried this over and over with no luck.
I'm running Fedora Core 3 with the latest kernel. I have a Radeon 9600SE video card.
1.) Press control+alt+F1 to leave graphical login screen
2.) Login as root
3.) init 3 (to shut down x server)
4.) install the RPM for the x.org ati driver. It has no errors, just two progress bars
5.) Run fglrxconfig, using pretty much all the default values.
6.) I answer yes when it wants to write to xorg.conf
7.) init 5 (graphical login starts back up)
8.) I run fglrxinfo in the terminal, but it still says Mesa.
I know something changed because the GUI seems to respond faster and gnome complains that the keyboard settings changed, but it still uses the Mesa OpenGL and I can't game :-(
Please, someone help.
willhunter
28th February 2005, 03:25 AM
Hello All,
Atllast my ATI radeon 9600 is working!!.
Following are the steps :
1) change your /etc/inittab as shown
id:5:initdefault:
TO
id:3:initdefault
This step is to make sure that if something happens and driver doesnt load, atleast you have prompt at your hands to uninstall ati driver.
2) First of all you need to add following in your yum.conf
[livna-pending]
name=Livna.org - Fedora Compatible Packages (pending)
baseurl=http://rpm.livna.org/pending/fedora/$releasever/$basearch/RPMS.unstable
[livna-testing]
name=Livna.org - Fedora Compatible Packages (pending)
baseurl=http://rpm.livna.org/pending/fedora/$releasever/$basearch/RPMS.testing
3) Run the foillowing command :
yum install ati-fglrx kernel-module-fglrx-`(uname -r)`
It will install respective ATI drivers.
Also do :
yum install kernel-module-fglrx-`(rpm -q --queryformat="%{version}-%{release}\n" kernel | tail -n 1)`
just to make sure that you install the newest ATI driver before you start the new kernel. To install the driver in your new kernel before you restart.
4) Add following line to your /etc/xorg.conf :
Option "UseInternalAGPGART" "no"
your device section should look like shown below.
Section "Device"
Identifier "Videocard0"
Driver "fglrx"
VendorName "Videocard vendor"
BoardName "ATI Radeon Mobility 9600 M10"
Option "VideoOverlay" "on"
Option "UseInternalAGPGART" "no"
EndSection
5) Reboot
ENjoy!!
Hope this helps you all
livn4metal
2nd March 2005, 04:10 AM
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: RADEON 9800 Generic
OpenGL version string: 1.3.4893 (X4.3.0-8.10.19)
glxgears:
19645 frames in 5.0 seconds = 3929.000 FPS
24411 frames in 5.0 seconds = 4882.200 FPS
24411 frames in 5.0 seconds = 4882.200 FPS
24411 frames in 5.0 seconds = 4882.200 FPS
26704 frames in 5.0 seconds = 5340.800 FPS
44265 frames in 5.0 seconds = 8853.000 FPS (covered)
44178 frames in 5.0 seconds = 8835.600 FPS (covered)
44186 frames in 5.0 seconds = 8837.200 FPS (covered)
fgl_glxgears
4108 frames in 5.0 seconds = 821.600 FPS
4633 frames in 5.0 seconds = 926.600 FPS
4712 frames in 5.0 seconds = 942.400 FPS
6681 frames in 5.0 seconds = 1336.200 FPS (covered)
7775 frames in 5.0 seconds = 1555.000 FPS (covered)
7783 frames in 5.0 seconds = 1556.600 FPS (covered)
I'll have to find a way to tweak this for my 9800XT, but for now i'm just happy that I have the acceleration.
lincomet
7th March 2005, 10:22 AM
I found this in relese notes:
Issues Resolved
This section provides information on issues that have been resolved with the latest release of the ATI Proprietary Linux driver. This includes the following:
Starting X on a DVI display no longer results in noisy or flickering output with some displays
The Monitor autodetect no longer finds a phantom CRT display if none is connected either RADEON™ X800, X700, X300, or FireGL™ V5100, and V5000
The ATI Proprietary Linux driver now works with Apple Cinema display flat panels in single link mode
fglrxconfig now produces a proper xorg.conf X Server configuration file
Running certain 3D applications no longer result in system hangs on x86_64 systems with RADEON™ 9100/8500 series or FireGL™ 8800 installed
Kernel Module Driver compile support for Kernel 2.6.10 <----------------------------------here
XVideo support now available in dualhead configuration
3D geometry corruption no longer occurs with Celestia and other 3d apps
A blank screen or X failing to load and returning to the console no longer occurs under X.Org 6.8 when using the config file generated by fglrxconfig
64 Bit systems with 4 or more GB of RAM no longer hang the system while loading the X Server
does it means that I need not to patch it after installation?
is it compatible with the new 2.6.11 kernel ?
lincomet
7th March 2005, 10:26 AM
It seems there are still a lot of problems out there.
skoona
8th March 2005, 01:14 AM
Don't know about 2.6.11; But I had to recompile the ATI driver for the most recent upgrade to 2.6.10-1.770_FC3smp.
elinter
9th March 2005, 03:28 AM
Skoona,
I just upgraded to 2.6.10-1.770_FC3 and the current ATI driver (fglrx_6_8_0-8.10.19-1.i386) now fails to load. How did you recomple the ATI driver?
Thanks
Mike
skoona
9th March 2005, 04:00 AM
[code] Upgrading...
$ cd /lib/modules/fglrx/build_mod
$ sh make.sh
$ cd ..
$ sh make_install.sh
Done...
I think I even did this while X was running. (i.e. no init 3 stuff)
skoona
9th March 2005, 04:58 AM
Ok, So I left out a few details...
By force of habit I re-booted to load the new kernel. ATI failed to load, but something did because X started. I immediately download the newest kernel source, removed the last kernelsource package and the symbolic links I created. Installed the newest kernel, created a symbolic link in the /usr/src dir, and THEN I recompiled the ATI driver as outlined in the previous post (and yes I was signed in as root when I did it).
I am fairly sure I that ATI removed the need for kernel source to be present when compiling and recompiling its driver. I won't sware to it though, I load kernel source for other reasons not directly related to ATI drivers.
BigBen1981
10th March 2005, 11:33 PM
4) Add following line to your /etc/xorg.conf :
Option "UseInternalAGPGART" "no"
your device section should look like shown below.
Section "Device"
Identifier "Videocard0"
Driver "fglrx"
VendorName "Videocard vendor"
BoardName "ATI Radeon Mobility 9600 M10"
Option "VideoOverlay" "on"
Option "UseInternalAGPGART" "no"
EndSection
5) Reboot
ENjoy!!
Hope this helps you all
That helped a lot! Thanks! I was trying all day to get this driver running, but without any result. Now I can go to bed. :D
Another thing: I'm kind of new to this benchmark system. Could someone tell me if my results are good or bad? :confused:
I'm running on a Ahtlon 3000+ XP /w 1GB RAM and a ATi Radeon 9800 Pro /w 128MB RAM
glxgears
13204 frames in 5.0 seconds = 2640.800 FPS (Covered up)
40962 frames in 5.0 seconds = 8192.400 FPS
40951 frames in 5.0 seconds = 8190.200 FPS
40970 frames in 5.0 seconds = 8194.000 FPS
40958 frames in 5.0 seconds = 8191.600 FPS
40965 frames in 5.0 seconds = 8193.000 FPS
40958 frames in 5.0 seconds = 8191.600 FPS
fgl_glxgears
4054 frames in 5.0 seconds = 810.800 FPS (Covered up)
6893 frames in 5.0 seconds = 1378.600 FPS
6892 frames in 5.0 seconds = 1378.400 FPS
6892 frames in 5.0 seconds = 1378.400 FPS
6893 frames in 5.0 seconds = 1378.600 FPS
6892 frames in 5.0 seconds = 1378.400 FPS
6891 frames in 5.0 seconds = 1378.200 FPS
6889 frames in 5.0 seconds = 1377.800 FPS
Thanks for any comment or advice.
Rgrds,
BigBen
Aifel
25th February 2007, 04:02 PM
Man, all you guys are making me jealous with your high glxgears results... I'm stuck with the crappy "radeon" driver... My card's not supported (Radeon 9200 PRO)...
1xused
23rd March 2007, 03:36 AM
When I try to boot, all I get is a blank screen after the 'rhgb'. I can boot to run level 3, delete xorg.conf, then go to run level 5 and be able to use the gui for that session. As soon as I reboot, I have the same problem again. I'm using the livna driver "xorg-x11-drv-fglrx-8.33.6-1.lvn5.1.i386.rpm". Would changing to the proprietary driver fix this, do you think?
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.