PDA

View Full Version : ATI Support Under Fedora Core 2



gotmonkey
18th May 2004, 02:28 PM
This is what I did to get my 9700 pro working in Fedora Core 2. This allowed me to have direct rendering support under xorg with ATI drivers.

Here is a step-by-step installation. Make sure you have the "kernel-source" package installed.

Thanks to the guys in the Linux Forum @
http://www.rage3d.com/board/showthread.php?s=&threadid=33757007

1. Download the Fedora Core 2 patches in /tmp (for example)

http://rambo.its.tudelft.nl/~ewald/patches/fglrx-3.7.6-fedora.patch
http://www.kaseorg.com/fglrx-3.7.6-regparm.patch

Download the rpm from ATI Drivers. I used version 4.3.0


2. Open /etc/X11/xorg.conf
# get your mouse location '/dev/input/mice'
# get your monitor Freq H&R
# ie Horizontal 30.0-130 Vertical 48.0-170.0)

3. open terminal window and su to root.

4. Install the fglrx rpm (replaces file from xorg-x11-Mesa-libGL)
cd /path/to/ati/file
rpm --replacefiles -ivh fglrx-4.3.0-3.7.6.i386.rpm

5. Change directory, apply patches for Fedora Core 2
cd /lib/modules/fglrx/buld_mod
patch -p1 -i /path/to/patch_files/fglrx-3.7.6-fedora.patch
patch -p1 -i /path/to/patch_files/fglrx-3.7.6-regparm.patch

6. Build and install the kernel module
cd /lib/modules/fglrx/buld_mod
sh make.sh
cd cd ..
sh make_install.sh

7. Config the drivers:
# Back up original xorg.conf
mv /etc/X11/xorg.conf /etc/X11/xorg.conf.org

fglrxconfig

# Use xorg.conf to get Keyboard, Monitor, Mouse info
# Be mindful of the questions

XF86Config-4 will be created [y]

cd /etc/X11/
ln -sf XF86Config-4 xorg.conf

cd /etc/X11/xkb/rules
ln -sf xorg xfree86
ln -sf xorg.lst xfree86.lst
ln -sf xorg.xml xfree86.xml

8: Reboot X
# open terminal

glxinfo | grep direct

# Should read "direct rendering: Yes
# Should have ATI Control Panel with Ati drivers (not Mesa)

9: open terminal
'glxgears'
# a window will open with 3 colored gears.
# framerate will be displayed in terminal.
# My 9700pro generated 3800+ framerate

## If for some reason you are not able to get a graphical boot.

logon: root
password: *******
cd /etc/X11
cp xorg.conf.org xorg.conf
startx
## this will allow you back into x windows
## chances are issues are settings based in XF86Config-4

If this guide does not work for you, refer to the original forurm link at the top of the post for support.

micha
18th May 2004, 02:35 PM
Excellent howto !

Ug
18th May 2004, 02:42 PM
Yea - I'm currently involved in updating the FedoraFAQ with Foolish and came to pretty much that conclusion. I kind of strung it all together from all the posts in that thread.

Don't forget that Xorg does have 2D support for ATI cards but not 3D. ;) So it might not apply to all of you.

Malt0meal
19th May 2004, 12:02 AM
I'm giving yer instructions on a shot with my Mobility Radeon 9000

Bana
19th May 2004, 01:03 AM
Worked for me :D

theurge
19th May 2004, 02:04 AM
Installation failed on brand new Fedora Core 2 install due to the ATI drivers telling me I need kernel 2.4.x when Fedora Core 2 is using 2.6.5 something.

Any ideas?

gotmonkey
19th May 2004, 04:26 AM
Originally posted by theurge
Installation failed on brand new Fedora Core 2 install due to the ATI drivers telling me I need kernel 2.4.x when Fedora Core 2 is using 2.6.5 something.

Any ideas?
When I installed the ati driver, It did give me an error and told me that I would have 2d support. I just followed the rest of patches and configs and it seemed to work. I don't believe I had an error regarding kernel 2.4.x.

I am uber noob at linux. You might want to try the forum link in rage3d.org and see if they have better info for you. They provided excellent support to me and others setting up the drivers under core 2.

Thanks micha, I tried to put in as much info as I could to make it as simple as possible

theurge
19th May 2004, 05:08 AM
Thanks for the response and the suggestion, I'll see what information I can muster over there.

Bana
19th May 2004, 05:15 AM
Worked for me in FC2 Final fresh (the previous was about Test 3).

theurge
19th May 2004, 06:06 AM
ATI Control Panel is loaded, but it is still using the Mesa drivers and not the ATI drivers:



[root@antec root]# glxinfo | grep direct
direct rendering: No
OpenGL renderer string: Mesa GLX Indirect
[root@antec root]#


I have the following:
Fedora Core 2 (kernel 2.6.5-1.358smp)
ATI Radeon 9500 Pro
Athlon XP 2800+

Here is the output of every step I did following your directions. Any ideas are most welcome.



[root@antec atidrivers]# rpm --force -ivh fglrx-4.3.0-3.7.6.i386.rpm
Preparing... ########################################### [100%]
1:fglrx ########################################### [100%]
*** Trying to install a precompiled kernel module.
*** WARNING ***
Tailored kernel module for fglrx not present in your system.
You must go to /lib/modules/fglrx/build_mod subdir
and execute './make.sh' to build a fully customed kernel module.
Afterwards go to /lib/modules/fglrx and run './make_install.sh'
in order to install the module into your kernel's module repository.
(see readme.txt for more details.)

As of now you can still run your XServer in 2D, but hardware acclerated
OpenGL will not work and 2D graphics will lack performance.

failed.
*** Found kernel module build environment, generating kernel module now.
ATI module generator V 2.0
==========================
initializing...
Error:
XFree86 drm includes at /lib/modules/2.6.5-1.358smp/build/include/../drivers/char/drm do not fit this driver.
This driver is designed to only work with X4.1.0 or higher.
You can match this by getting Linux kernel 2.4.8 or higher.
*** WARNING ***
Tailored kernel module for fglrx not present in your system.
You must go to /lib/modules/fglrx/build_mod subdir
and execute './make.sh' to build a fully customed kernel module.
Afterwards go to /lib/modules/fglrx and run './make_install.sh'
in order to install the module into your kernel's module repository.
(see readme.txt for more details.)

As of now you can still run your XServer in 2D, but hardware acclerated
OpenGL will not work and 2D graphics will lack performance.

failed.
Installed: qt3 (gcc 3.2) based control panel application
===
ATI display drivers successfully installed
please run 'fglrxconfig' now
===
[root@antec atidrivers]#




[root@antec build_mod]# patch -p1 -i /tmp/fglrx-3.7.6-fedora.patch
patching file 2.6.x/Makefile
patching file make.sh
[root@antec build_mod]# patch -p1 -i /tmp/fglrx-3.7.6-regparm.patch
patching file firegl_public.c
patching file firegl_public.h
patching file make.sh
[root@antec build_mod]#




[root@antec build_mod]# sh make.sh
ATI module generator V 2.0
==========================
initializing...
Error:
XFree86 drm includes at /usr/src/linux-2.6.5-1.358smp/drivers/char/drm do not fit this driver.
This driver is designed to only work with X4.1.0 or higher.
You can match this by getting Linux kernel 2.4.8 or higher.
[root@antec build_mod]#




[root@antec fglrx]# sh make_install.sh
*** WARNING ***
Tailored kernel module for fglrx not present in your system.
You must go to /lib/modules/fglrx/build_mod subdir
and execute './make.sh' to build a fully customed kernel module.
Afterwards go to /lib/modules/fglrx and run './make_install.sh'
in order to install the module into your kernel's module repository.
(see readme.txt for more details.)

As of now you can still run your XServer in 2D, but hardware acclerated
OpenGL will not work and 2D graphics will lack performance.

failed.
[root@antec fglrx]#




[root@antec root]# glxinfo | grep direct
direct rendering: No
OpenGL renderer string: Mesa GLX Indirect
[root@antec root]#

DaNewB
19th May 2004, 10:42 AM
Yay! My ATI radeon 9600 SE (from Saphire) is now installed and working! Thanks!

(This really should be added to some official faq somewhere...)

Beloth
19th May 2004, 11:39 AM
hi,

i only could compile the ati module with the 'normal' kernel. the smp-kernel didn't work. (used 3.7.6 for 4.3.x)

@theurge

if you get this message:

ATI module generator V 2.0
==========================
initializing...
Error:
XFree86 drm includes at /usr/src/linux-2.6.5-1.358smp/drivers/char/drm do not fit this driver.
This driver is designed to only work with X4.1.0 or higher.
You can match this by getting Linux kernel 2.4.8 or higher.

then try to use the 'normal' kernel then it will work...

all i did afterward was to set 'fglrx' as drivermodule in the driver section of xorg.conf. All worked fine and i got around 4500 fps in glxgears.

glxinfo | grep direct results in direct rendering: yes

hope that could help you

theurge
19th May 2004, 01:23 PM
Beloth

Thanks, your suggestion finally made the compile with make.sh work under the non-smp kernel here.

Unfortunately, I still don't get direct rendering and it still uses the Mesa driver.

After more research, it appears I need to install the nVidia AGPGART module because the included internal AGPGART on the ATI driver doesn't work with my nForce motherboard (ASUS A7N8X-Deluxe).

Then I find out the nVidia nForce AGPGART module is only (and they mean only) for the 2.4.x kernel.

This is ridiculous and frustrating. This isn't like I have obscure hardware. Sigh.

gotmonkey
19th May 2004, 02:00 PM
Originally posted by theurge
Beloth

Thanks, your suggestion finally made the compile with make.sh work under the non-smp kernel here.

Unfortunately, I still don't get direct rendering and it still uses the Mesa driver.

After more research, it appears I need to install the nVidia AGPGART module because the included internal AGPGART on the ATI driver doesn't work with my nForce motherboard (ASUS A7N8X-Deluxe).

Then I find out the nVidia nForce AGPGART module is only (and they mean only) for the 2.4.x kernel.

This is ridiculous and frustrating. This isn't like I have obscure hardware. Sigh.

I would check your XF86Config-4 file. Try setting the 'use external agpgart to 'no' and see if that helps. I didn't install any nvidia drivers after I installed Core 2. I am assuming that it used the forcedeth drivers at install.

What is the difference between the normal kernel and the smp-kernel? How would an user distinguish between the two?

Thoreau
19th May 2004, 02:07 PM
Symetric Multiprocessing (SMP)

more than one proc. You'd know the difference, now that you know what it means :)

swag
19th May 2004, 02:18 PM
Sorry for my stupidity, but what do you mean by "normal" kernel?

Thoreau
19th May 2004, 02:22 PM
the normal everyday kernel that we with one proc have to use.

swag
19th May 2004, 02:25 PM
How do I change from the smp kernel to the normal one? I think I have the smp one, since I got the same errors yesterday.

Again, thank you for your patience.

Thoreau
19th May 2004, 02:27 PM
holy carp, i miss read your question

at the command line use this code



uname -rvp


that will give you the version, release and type of processor

swag
19th May 2004, 03:50 PM
It says: 2.6.5-1.358smp #1 SMP

How do I change it to the normal one? Reinstall?

Thoreau
19th May 2004, 04:02 PM
*i'm confused*

if you have 2 proc's why would you want to use the 1 proc kernel?

Are you sure you have 2 procs? If you're in KDE go to "control panel" then hit processors what does it say?

:mods: can we split this?:

swag
19th May 2004, 04:18 PM
I only have one, but it is a P4 with Hyperthreading, so it acts like two. The problem is that I really want to install the ATI drivers and it dont seem to work with the SMP kernel.

EDIT: I think i'm just gonna deactivate Hyperthreading and reinstall Fedora until I can sort this out.

Thoreau
19th May 2004, 04:41 PM
you can download thenon-smp kernel from www.kernel.org

that way you wouldn't have to reinstall

swag
19th May 2004, 05:10 PM
Thanks. :-)

EDIT: Yes, now it's working!

23202 frames in 5.0 seconds = 4640.400 FPS
23524 frames in 5.0 seconds = 4704.800 FPS
23528 frames in 5.0 seconds = 4705.600 FPS
23506 frames in 5.0 seconds = 4701.200 FPS
23422 frames in 5.0 seconds = 4684.400 FPS
23519 frames in 5.0 seconds = 4703.800 FPS
23523 frames in 5.0 seconds = 4704.600 FPS
23504 frames in 5.0 seconds = 4700.800 FPS
23517 frames in 5.0 seconds = 4703.400 FPS


Thank you so much.



:)

theurge
19th May 2004, 07:28 PM
No, it doesn't work when I use the internal GART, I have to somehow get the nvidia-agp module, by either patching it, bugging nvidia to update it, or go back to Fedora Core 1.

Oh yeah, speaking of the SMP kernel, that's just the one Fedora always installs on my machine for some reason along with the single processor one. My GRUB looks like this:

Fedora Core 2 2.6.5-1.358smp
Fedora Core 2-up 2.6.5-1.358
Windows XP

...on a Athlon XP 2800+

But that's another story.

theurge
19th May 2004, 07:43 PM
Originally posted by gotmonkey
I would check your XF86Config-4 file. Try setting the 'use external agpgart to 'no' and see if that helps. I didn't install any nvidia drivers after I installed Core 2. I am assuming that it used the forcedeth drivers at install.

What is the difference between the normal kernel and the smp-kernel? How would an user distinguish between the two?

gotmonkey, I noticed by your signature you're using a Shuttle board that has the nforce2 chipset! That's nVidia! And yours works! Argh!

:(

I think I'm going to start over.

Seehund
21st May 2004, 12:08 PM
Originally posted by Beloth

then try to use the 'normal' kernel then it will work...


Yeah, anything else would be odd.

But for us with SMP machines, the SMP kernel IS the "normal" kernel. Degrading to a uniprocessor kernel, and only being able to use one CPU, is not an acceptable compromise to get hardware accelerated 3D.

The compile error message complains about incompatible includes in /usr/src/linux-[version]smp. This dir does not exist (SMP and UP have the same source, with no "smp" in the dir name). Looks like there's something wrong in how the compilation extracts the running kernel version.

Is this a bug in the ATI files, or in the patches? Is there anything we mere mortals can do (forcefeed the correct kernel source path, ...?), apart from waiting for ATI's musculus sphincter ani to loosen its grip from around their thumbs?

chamberl
22nd May 2004, 01:56 AM
Try this:

login as root
cd /usr/src/
ln -s linux-2.6.5-1.358 linux-2.6.5-1.358smp

Then compile the ati driver. Thats how I got around it.

Seehund
22nd May 2004, 10:37 AM
Originally posted by chamberl

ln -s linux-2.6.5-1.358 linux-2.6.5-1.358smp


DOH!

*Slaps forehead*

Thank you! Yes, that worked!

Robyams
22nd May 2004, 04:37 PM
Hello all,

Getting back to the thread prior to the SMP problem, Bana posted a reply saying that he was able to get gotmonkey's patch instruction to work with FC2 final, but when I run the "sh make.sh" I get this error:

\\\\[root@doctor build_mod]# sh make.sh
ATI module generator V 2.0
==========================
initializing...
Error:
XFree86 drm includes at /usr/src/linux-2.6.5-1.358/drivers/char/drm do not fit this driver.
This driver is designed to only work with X4.1.0 or higher.
You can match this by getting Linux kernel 2.4.8 or higher.

Any help would be appreciated...

postlogic
23rd May 2004, 02:03 AM
hey..

I just stumbled upon this page after days trying to figure out how to get 3D acceleration working with ATI drivers..
so I tried the walkthrough I found in this thread, and got through it pretty much unharmed. I did not get any errors running the makefiles and so on.

But when I try glxinfo | grep direct, it still reports that it's not running direct rendering, not to mention it's still using the mesa stuff..

I'm not using the SMP kernel either.

any ideas?

*newbie*

Redsand189
23rd May 2004, 06:36 PM
In the instructions it keeps saying "open terminal". I cant even get into x-windows. When I boot up, the screen flickers a few times and I get an error with the vesa driver. It lets me login to the shell though.

I am using an nforce 2 chipset and an ati 9600 pro. I seem to have the worse possible setup for this OS. I have already lost my windows xp partition when trying to get a dual boot. I am thinking that Fedora Core 2 was a bad idea.

Redsand189
23rd May 2004, 06:53 PM
Well, I followed the instructions and managed to get it into x-windows. Unfortunately, it only stayed at 640x480 resolution and I was still using the MESA drivers. I guess I will keep trying.

hellraiser_rob
23rd May 2004, 07:42 PM
Ensure that you are entering all the correct details when you are configuiring the settings, e.g if you don't enter the exact vertical and horizontal refresh rates this will probably lead to your resolutions being locked on a low setting.

the tutorial worked fine for me on 9600XT

FAO Redsand189 are you certain the xp installation is lost? There is a thread started by me in the general help area which might help you out :)

Redsand189
23rd May 2004, 08:11 PM
Thanks hellraiser, I have calmed down a bit now. I still am using the MESA drivers, but at least I can now use X-windows at a good resolution.

I am not quite sure what caused only allowing a low resolution (I did set the refresh rates as they were set originally in xorg.conf). To give me a higher resolution I did the following:

Went into XF86Config-4, under the screens section and under modes it only had "640x480". I added "1024x768" "800x600" in front of that and restarted and now everything looks good.

I will check your post on windows. I ended up throwing in my knoppix CD and burning all my info I wanted to keep on my windows partition, then reformatting.

hellraiser_rob
23rd May 2004, 08:59 PM
the original refresh rates states in the original xorg.conf will still only be best guesses. An idea might be to go to the manafacturer's website and check for the specifications of your model.

Sorry to hear you had to format, i myself was about 5 minutes away from doing this......oh well :)

JoNaHLoMu
25th May 2004, 07:29 AM
i hope it work with me...i read it all and i'm ready now to fight XD with that gpu (ati9800pro)

thanks for the info...here is the only place with rage3d where i did found a solution for ati's with fc2

:D :D :D

JoNaHLoMu
26th May 2004, 09:52 AM
$ glxinfo | grep direct
direct rendering: Yes

$ glxgears
18290 frames in 5.0 seconds = 3658.000 FPS
21255 frames in 5.0 seconds = 4251.000 FPS
34389 frames in 5.0 seconds = 6877.800 FPS
26980 frames in 5.0 seconds = 5396.000 FPS
21377 frames in 5.0 seconds = 4275.400 FPS
21372 frames in 5.0 seconds = 4274.400 FPS

it work's !!! thank you!!!

my gpu is an Ati 9800pro

i'm so happy :D :D

bye

pamindic
26th May 2004, 06:46 PM
[QUOTE]Originally posted by Robyams

Getting back to the thread prior to the SMP problem, Bana posted a reply saying that he was able to get gotmonkey's patch instruction to work with FC2 final, but when I run the "sh make.sh" I get this error:

\\\\[root@doctor build_mod]# sh make.sh
ATI module generator V 2.0
==========================
initializing...
Error:
XFree86 drm includes at /usr/src/linux-2.6.5-1.358/drivers/char/drm do not fit this driver.
This driver is designed to only work with X4.1.0 or higher.
You can match this by getting Linux kernel 2.4.8 or higher.


Good point. That's precisely where I've got to with this patch, and then I notice that someone has posted his observation that Gotmonkey has a NVidia card, not and ATI, which I presume explains whiy its not working for we long-suffering ATI card owners.

Anyone, anyone, got ATI card to work with FC2 i386 version?

hellraiser_rob
26th May 2004, 10:32 PM
yeah mine works fine, is everyone sure they have got the kernel source rpm installed?

yum install kernel-source

theurge
27th May 2004, 03:29 AM
New ATI drivers are out, 3.9.0, check their site.

Any news on this? I still can't get the above instructions to work on the old drivers.

Heon2574
27th May 2004, 10:24 AM
ATI Proprietary Linux Release Notes

http://www2.ati.com/drivers/linux/Linux_390.html



New Features

The latest version of the ATI proprietary Linux driver introduces the following new features:

* Explicit regparm support for newer Redhat, Fedora and SuSE kernels
* VIA KT400 motherboard chipsets now recognized properly



I gave the ATI Proprietary Linux Driver 3.9.0 a spin and I still had the error during the module compile


ATI module generator V 2.0
==========================
initializing...
Error:
XFree86 drm includes at /usr/src/linux-2.6.5-1.358/drivers/char/drm do not fit this driver.
This driver is designed to only work with X4.1.0 or higher.
You can match this by getting Linux kernel 2.4.8 or higher.

hmmm... anyone else had success with these new ati drivers?

/edit

found this thread on the new drivers

http://rage3d.com/board/showthread.php?threadid=33760878

postlogic
27th May 2004, 11:38 AM
anyone knows if these intructions would work on another distro? I'd like to try it on slackware, too.

JoNaHLoMu
29th May 2004, 05:42 AM
I translated in spanish the tutorial

http://usuarios.vtr.net/~spetsnaz/linux/ati_fc2.html

bye

mwallin
29th May 2004, 06:45 PM
Well, it worked fine but I cant seem to get ATI Control to run. I get the error "./fireglcontrol: error while loading shared libraries: libpng10.so.0: cannot open shared object file: No such file or directory" but when i run "yum install libpng10" i get "libpng10 is installed and is the latest version." Any ideas?

pamindic
29th May 2004, 10:03 PM
Originally posted by hellraiser_rob
yeah mine works fine, is everyone sure they have got the kernel source rpm installed?

yum install kernel-source


Nope. I didn't know how to do that. Now I've done it, though, Gotmonkey's patch works -at least on the 3.7.6 patch; I tried the 3.9.0, omitting Gotmonkey's regparm patch, but couldn't get a result.

Incidentally, I've got a TFT screeen, and my first attemp at starting X after applying the patch failed. I then re-booted into a Console putting "nofb" on the boot command line (as the FC2 Release Notes suggest). It's been working ever since (direct rendering: Yes).

Thank you, thank you, Gotmonkey et.al. !!

dnar
7th June 2004, 07:20 PM
Thanks heaps, worked a treat on my HP ZE4201 with M340 chipset.

glxgears increased from approx 150 to 500 fps, I can now run all the GL screensavers, tuxracer etc.

Not as high a fps as many are posting, I am guessing this is due to my setup using shared memory for the video chipset? Any thoughts?

vecnix
8th June 2004, 11:33 PM
Hello ,
I have an ATI Rage Mobility 8 mb and still having problems to get tvout to work under X, do you think those drivers would work for me and allow me to do tv out?

any help with atitvout would be really welcome

micha
9th June 2004, 12:31 AM
You should look at the Gatos project:
http://gatos.sourceforge.net/

manub
10th June 2004, 08:31 AM
I can't get them to work ... followed various procedures, the only thing I've got is a correct display positioning (I've a LCD display, so when TV out is enabled I can't display screen properly and now I can), but still it doesn't work:

glxinfo | grep direct
direct rendering: No
OpenGL renderer string: Mesa GLX Indirect

using FC2 with 3.9.0 drivers ... any ideas ?

vecnix
10th June 2004, 08:52 AM
if someone can help use the files from the gatos project ( I fear those don't work with FC2) , I can find the right path to extract the driver and I get error about the options when I specify it, if you have a good xorg.conf sample please paste it

lightismagic
12th June 2004, 05:33 AM
Hi there,
someone has posted in this thread that he was able to install the ATI drivers on an x86_64 system... really? AFAIK these drivers are designed for a standard x86 system and the last time I tried to install them on my amd64 box I got an error saying something like "architecture not supported" (was some months ago, ATI driver version 3.7.0 on a Fedora Core 1 x86_64). Is anybody able to confirm this?

regards

manub
12th June 2004, 08:33 PM
there isn't any tip to install ATI 3.9.0 drivers with the new kernel ?

micha
13th June 2004, 03:13 AM
Yep. You have to use the mm patch for the new stock kernel 2.6.6. Here is the patch:

diff -uprN build_mod-mreg_new/agpgart_be.c build_mod-mreg_new-mm/agpgart_be.c
--- build_mod-mreg_new/agpgart_be.c 2004-05-15 03:45:48.000000000 +0300
+++ build_mod-mreg_new-mm/agpgart_be.c 2004-05-15 03:18:30.000000000 +0300
@@ -1402,7 +1402,8 @@ unsigned long agp_generic_alloc_page(voi
}
#endif

- atomic_inc(&page->count);
+ //atomic_inc(&page->count);
+ get_page(page);
set_bit(PG_locked, &page->flags);
atomic_inc(&agp_bridge.current_memory_agp);

@@ -4413,7 +4414,8 @@ static unsigned long ali_alloc_page(void
if (page == NULL)
return 0;

- atomic_inc(&page->count);
+ //atomic_inc(&page->count);
+ get_page(page);
set_bit(PG_locked, &page->flags);
atomic_inc(&agp_bridge.current_memory_agp);

diff -uprN build_mod-mreg_new/firegl_public.c build_mod-mreg_new-mm/firegl_public.c
--- build_mod-mreg_new/firegl_public.c 2004-05-15 03:45:06.000000000 +0300
+++ build_mod-mreg_new-mm/firegl_public.c 2004-05-15 03:25:13.000000000 +0300
@@ -2066,7 +2066,8 @@ static vm_nopage_ret_t vm_shm_nopage(str
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",
Copy this code to a file, e.g. /tmp/fglrx-3.9.0-mm.patch.

Then you go the ATI driver source directory and apply the patch (as root obviously):

cd /lib/modules/fglrx/build_mod
patch -p1 < /tmp/fglrx-3.9.0-mm.patch
Finally, install the driver with the classical procedure.

As usual, you can find more information on the http://rage3d.com linux forum.

--Micha

manub
13th June 2004, 11:42 AM
Finally, install the driver with the classical procedure.

What do you mean by "classical procedure" ? I've found a lot of HOW-TOs about this. Because I'm not so experienced I would be glad if you can show me what's the right way. Thanks a lot.

micha
13th June 2004, 12:16 PM
Originally posted by manub
What do you mean by "classical procedure" ? I've found a lot of HOW-TOs about this. Because I'm not so experienced I would be glad if you can show me what's the right way. Thanks a lot. See the first post of this thread. Everything is explained clearly. My previous post is just another patch for the ATI driver due to the new kernel. Also there is a thread on the http://rage3d.com linux forum dedicated to Fedora Core 2:
http://rage3d.com/board/showthread.php?s=&threadid=33757007

--Micha

manub
13th June 2004, 09:00 PM
I can't get it to work :(

[root@manub build_mod]# patch -p1 -i /home/manub/system/fglrx-3.9.0-mm.patch
patching file agpgart_be.c
patching file firegl_public.c
Hunk #1 succeeded at 2010 (offset -56 lines).

-- EDIT

I get on rage3d.com a fc2.patch file that works ... however:

[root@manub build_mod]# sh make.sh
ATI module generator V 2.0
==========================
initializing...
Error:
XFree86 drm includes at /lib/modules/2.6.6-1.427/build/include/../drivers/char/drm do not fit this driver.
This driver is designed to only work with X4.1.0 or higher.
You can match this by getting Linux kernel 2.4.8 or higher.

micha
14th June 2004, 04:18 AM
Originally posted by manub
[root@manub build_mod]# sh make.sh
ATI module generator V 2.0
==========================
initializing...
Error:
XFree86 drm includes at /lib/modules/2.6.6-1.427/build/include/../drivers/char/drm do not fit this driver.
This driver is designed to only work with X4.1.0 or higher.
You can match this by getting Linux kernel 2.4.8 or higher.
Modify the /lib/modules/fglrx/build_mod/make.sh on line 176:

#drmincludes=${linuxincludes}/../drivers/char/drm
drmincludes=/usr/src/linux-${uname_r}/drivers/char/drm
This changes the DRM include path. And now it should work...

--Micha

manub
14th June 2004, 06:26 AM
yeah, that worked, but still having troubles.

/lib/modules/fglrx/build_mod/2.6.x/agpgart_be.c: In function `agp_generic_alloc_page':
/lib/modules/fglrx/build_mod/2.6.x/agpgart_be.c:1405: error: structure has no member named `count'
/lib/modules/fglrx/build_mod/2.6.x/agpgart_be.c: In function `ali_alloc_page':
/lib/modules/fglrx/build_mod/2.6.x/agpgart_be.c:4416: error: structure has no member named `count'
make[2]: *** [/lib/modules/fglrx/build_mod/2.6.x/agpgart_be.o] Error 1
make[1]: *** [_module_/lib/modules/fglrx/build_mod/2.6.x] Error 2
make[1]: Leaving directory `/lib/modules/2.6.6-1.427/build'
make: *** [kmod_build] Error 2
build succeeded with return value 0

I'm really going mad with this :(

micha
14th June 2004, 07:31 AM
You have to apply the "mm patch" I have posted above...

--Micha

zulaica
15th June 2004, 04:42 PM
unfortunately the gatos drivers will not work with fc2. as of right now gatos is only available for xfree86 and not x.org. so until gatos supports x.org, we're all up a creek without a paddle. :(

i imagine, however, that they may do this soon-ish: pretty much all the major distros are using x.org and not xfree86.




Originally posted by vecnix
if someone can help use the files from the gatos project ( I fear those don't work with FC2) , I can find the right path to extract the driver and I get error about the options when I specify it, if you have a good xorg.conf sample please paste it

bednar
9th July 2004, 09:24 AM
Hi all interested in TVout problem with FC2.

Look at the thread http://rage3d.com/board/showthread.php?t=33762649
I started on rage3d.com

Bednar

N6546R
21st July 2004, 04:49 AM
IBM T42, Radeon 9600 Mobility (M9), kernel 2.6.6-1.435.2.3.stk16 (stock 2.6.6 with 16k stack patch).

I followed gotmonkey's (and misha's) howto and still had this problem. My solution was to first make certain that I had the correct kernel source installed, then:

1. Edit /lib/modules/fglrx/build_module/make.sh and comment out the section of code that tests for Xfree (it starts around line 310 with a test for $drmdefines)

2. In the same file, around line 177, $drmincludes is set...I just hardcoded the value to the location of the drm directory in my source tree (/usr/src/linux/drivers/char/drm in my case).

This allowed me to build and install the modules. xgears went from around 250fps to 2500 fps.

Perry



Hello all,

Getting back to the thread prior to the SMP problem, Bana posted a reply saying that he was able to get gotmonkey's patch instruction to work with FC2 final, but when I run the "sh make.sh" I get this error:

\\\\[root@doctor build_mod]# sh make.sh
ATI module generator V 2.0
==========================
initializing...
Error:
XFree86 drm includes at /usr/src/linux-2.6.5-1.358/drivers/char/drm do not fit this driver.
This driver is designed to only work with X4.1.0 or higher.
You can match this by getting Linux kernel 2.4.8 or higher.

Any help would be appreciated...

imdeemvp
21st July 2004, 07:58 AM
i installed ut2003 and i also install the linux ati driver for my ATI Redeon 8500...i followed the ati website for installation procedure and when i tried to run ut2003 i get this message:

[imdeemvp@localhost imdeemvp]$ ut2003
fcntl: Invalid argument
fcntl: Invalid argument
Xlib: extension "XiG-SUNDRY-NONSTANDARD" missing on display ":0.0".

and then i typed:

[imdeemvp@localhost imdeemvp]$ glxinfo | grep direct
direct rendering: No
OpenGL renderer string: Mesa GLX Indirect
[imdeemvp@localhost imdeemvp]$

now i want to know if installation worked? I AM USING THIS DRIVER FROM ATI fglrx-4.3.0-3.9.0.i386

Xerantius
22nd July 2004, 02:39 AM
I have completed the steps and it worked! :)

But after a reboot MESA is loaded again and Direct Render is set to false. I have checked the Xorg logs (see below) and is see that the kernel module is automaticly unloaded..

Pls assiist /LOL

Specs:
- Connect3D Radeon 9600 256 MB RAM
- Intel(R) Pentium(R) 4 CPU 2.40GHz

# /sbin/lspci
00:00.0 Host bridge: Silicon Integrated Systems [SiS] SiS645DX Host & Memory & AGP Controller
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS962 [MuTIOL Media IO] (rev 04)
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600]
01:0


# glxinfo | grep direct
Xlib: extension "XFree86-DRI" missing on display ":0.0".
direct rendering: No
OpenGL renderer string: Mesa GLX Indirect

# dmesg | grep fglrx
fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
[fglrx] Maximum main memory to use for locked dma buffers: 433 MBytes.
[fglrx] module loaded - fglrx 3.7.6 [Mar 5 2004] on minor 0
[fglrx] module unloaded - fglrx 3.7.6 [Mar 5 2004] on minor 0

Xerantius
22nd July 2004, 02:40 AM
Xorg Log

Release Date: 18 December 2003
X Protocol Version 11, Revision 0, Release 6.7
Build Operating System: Linux 2.4.21-14.ELsmp i686 [ELF]
Current Operating System: Linux ws-01.hmse.nl 2.6.5-1.358 #1 Sat May 8 09:04:50 EDT 2004 i686
Build Date: 07 May 2004
Build Host: tweety.build.redhat.com

Before reporting problems, check http://wiki.X.Org
to make sure that you have the latest version.
Module Loader present
OS Kernel: Linux version 2.6.5-1.358 (bhcompile@bugs.build.redhat.com) (gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7)) #1 Sat May 8 09:04:50 EDT 2004 P
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul 21 14:23:11 2004
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "single head configuration"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Videocard0"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(**) Option "XkbModel" "pc105"
(**) XKB: model: "pc105"
(**) Option "XkbLayout" "us"
(**) XKB: layout: "us"
(==) Keyboard: CustomKeycode disabled
(**) FontPath set to "unix/:7100"
(**) RgbPath set to "/usr/X11R6/lib/X11/rgb"
(==) ModulePath set to "/usr/X11R6/lib/modules"
(WW) Open APM failed (/dev/apm_bios) (No such device)
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.2
X.Org Video Driver: 0.7
X.Org XInput driver : 0.4
X.Org Server Extension : 0.2
X.Org Font Renderer : 0.4
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor="X.Org Foundation"
compiled for 6.7.0, module version = 1.0.0
Module class: X.Org Font Renderer
ABI class: X.Org Font Renderer, version 0.4
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor="X.Org Foundation"
compiled for 6.7.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.7
(++) using VT number 7

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 1039,0646 card 0000,0000 rev 00 class 06,00,00 hdr 80
(II) PCI: 00:01:0: chip 1039,0001 card 0000,0000 rev 00 class 06,04,00 hdr 01
(II) PCI: 00:02:0: chip 1039,0962 card 0000,0000 rev 04 class 06,01,00 hdr 80
(II) PCI: 00:02:1: chip 1039,0016 card 0000,0000 rev 00 class 0c,05,00 hdr 00
(II) PCI: 00:02:5: chip 1039,5513 card 1039,5513 rev 00 class 01,01,80 hdr 00
(II) PCI: 00:03:0: chip 1039,7001 card 1039,7001 rev 0f class 0c,03,10 hdr 80
(II) PCI: 00:03:1: chip 1039,7001 card 1039,7001 rev 0f class 0c,03,10 hdr 00
(II) PCI: 00:03:2: chip 1039,7001 card 1039,7001 rev 0f class 0c,03,10 hdr 00
(II) PCI: 00:03:3: chip 1039,7002 card 1039,7002 rev 00 class 0c,03,20 hdr 00
(II) PCI: 00:08:0: chip 1131,7134 card 11bd,002b rev 01 class 04,80,00 hdr 00
(II) PCI: 00:0a:0: chip 1102,0004 card 1102,2002 rev 04 class 04,01,00 hdr 80
(II) PCI: 00:0a:1: chip 1102,7003 card 1102,0040 rev 04 class 09,80,00 hdr 80
(II) PCI: 00:0a:2: chip 1102,4001 card 1102,0010 rev 04 class 0c,00,10 hdr 80
(II) PCI: 00:0c:0: chip 10ec,8139 card 10ec,8139 rev 10 class 02,00,00 hdr 00
(II) PCI: 01:00:0: chip 1002,4150 card 17ee,2002 rev 00 class 03,00,00 hdr 80
(II) PCI: 01:00:1: chip 1002,4170 card 17ee,2003 rev 00 class 03,80,00 hdr 00
...

(II) Primary Device is: PCI 01:00:0
(--) Assigning device section with no busID to primary device
(WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found
(--) Chipset ATI Radeon 9600 AP (AGP) found
(II) resource ranges after xf86ClaimFixedResources() call:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX(B)
[1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0xdfffbb00 - 0xdfffbbff (0x100) MX[B]
[6] -1 0 0xdfff4000 - 0xdfff7fff (0x4000) MX[B]
[7] -1 0 0xdfffb000 - 0xdfffb7ff (0x800) MX[B]
[8] -1 0 0xdfffbc00 - 0xdfffbfff (0x400) MX[B]
[9] -1 0 0xdffff000 - 0xdfffffff (0x1000) MX[B]
[10] -1 0 0xdfffe000 - 0xdfffefff (0x1000) MX[B]
[11] -1 0 0xdfffd000 - 0xdfffdfff (0x1000) MX[B]
[12] -1 0 0xdfffc000 - 0xdfffcfff (0x1000) MX[B]
[13] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[B]O
[14] -1 0 0xdfee0000 - 0xdfeeffff (0x10000) MX[B](B)
[15] -1 0 0xb0000000 - 0xbfffffff (0x10000000) MX[B](B)
[16] -1 0 0xdfec0000 - 0xdfedffff (0x20000) MX[B](B)
[17] -1 0 0xdfef0000 - 0xdfefffff (0x10000) MX[B](B)
[18] -1 0 0xc0000000 - 0xcfffffff (0x10000000) MX[B](B)
[19] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[20] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[21] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]
[22] -1 0 0x0000dc00 - 0x0000dc07 (0x8) IX[B]
[23] -1 0 0x0000d800 - 0x0000d83f (0x40) IX[B]
[24] -1 0 0x0000ff00 - 0x0000ff0f (0x10) IX[B]
[25] -1 0 0x00000c00 - 0x00000c1f (0x20) IX[B]
[26] -1 0 0x0000b800 - 0x0000b8ff (0x100) IX[B](B)
(II) Loading sub module "radeon"
(II) LoadModule: "radeon"
(II) Reloading /usr/X11R6/lib/modules/drivers/radeon_drv.o
(II) resource ranges after probing:
[0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B)
[1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
[2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[5] -1 0 0xdfffbb00 - 0xdfffbbff (0x100) MX[B]
[6] -1 0 0xdfff4000 - 0xdfff7fff (0x4000) MX[B]
[7] -1 0 0xdfffb000 - 0xdfffb7ff (0x800) MX[B]
[8] -1 0 0xdfffbc00 - 0xdfffbfff (0x400) MX[B]
[9] -1 0 0xdffff000 - 0xdfffffff (0x1000) MX[B]
[10] -1 0 0xdfffe000 - 0xdfffefff (0x1000) MX[B]
[11] -1 0 0xdfffd000 - 0xdfffdfff (0x1000) MX[B]
[12] -1 0 0xdfffc000 - 0xdfffcfff (0x1000) MX[B]
[13] -1 0 0xe0000000 - 0xdfffffff (0x0) MX[B]O
[14] -1 0 0xdfee0000 - 0xdfeeffff (0x10000) MX[B](B)
[15] -1 0 0xb0000000 - 0xbfffffff (0x10000000) MX[B](B)
[16] -1 0 0xdfec0000 - 0xdfedffff (0x20000) MX[B](B)
[17] -1 0 0xdfef0000 - 0xdfefffff (0x10000) MX[B](B)
[18] -1 0 0xc0000000 - 0xcfffffff (0x10000000) MX[B](B)
[19] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B]
[20] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B]
[21] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B]
[22] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[23] -1 0 0x00000000 - 0x000000ff (0x100) IX[B]
[24] -1 0 0x0000d400 - 0x0000d4ff (0x100) IX[B]
[25] -1 0 0x0000dc00 - 0x0000dc07 (0x8) IX[B]
[26] -1 0 0x0000d800 - 0x0000d83f (0x40) IX[B]
[27] -1 0 0x0000ff00 - 0x0000ff0f (0x10) IX[B]
[28] -1 0 0x00000c00 - 0x00000c1f (0x20) IX[B]
[29] -1 0 0x0000b800 - 0x0000b8ff (0x100) IX[B](B)
[30] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B]
[31] 0 0 0x000003c0 - 0x000003df (0x20) IS[B]
(II) Setting vga for screen 0.
(II) RADEON(0): MMIO registers at 0xdfef0000
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/X11R6/lib/modules/libvgahw.a
(II) Module vgahw: vendor="X.Org Foundation"
compiled for 6.7.0, module version = 0.1.0
ABI class: X.Org Video Driver, version 0.7
(II) RADEON(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) RADEON(0): PCI bus 1 card 0 func 0
(**) RADEON(0): Depth 24, (--) framebuffer bpp 32
(II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
(==) RADEON(0): Default visual is TrueColor
(==) RADEON(0): RGB weight 888
(II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
(II) Loading sub module "int10"
(II) LoadModule: "int10"
(II) Loading /usr/X11R6/lib/modules/linux/libint10.a
(II) Module int10: vendor="X.Org Foundation"
compiled for 6.7.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.7
(II) RADEON(0): initializing int10
(II) RADEON(0): Primary V_BIOS segment is: 0xc000
(--) RADEON(0): Chipset: "ATI Radeon 9600 AP (AGP)" (ChipID = 0x4150)
(--) RADEON(0): Linear framebuffer at 0xc0000000
(--) RADEON(0): BIOS at 0xdfec0000
(--) RADEON(0): VideoRAM: 262144 kByte (128 bit DDR SDRAM)
(II) RADEON(0): AGP card detected
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Loading /usr/X11R6/lib/modules/libddc.a
(II) Module ddc: vendor="X.Org Foundation"
compiled for 6.7.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.7
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Loading /usr/X11R6/lib/modules/libi2c.a
(II) Module i2c: vendor="X.Org Foundation"
compiled for 6.7.0, module version = 1.2.0
..
[B](WW) RADEON(0): Direct rendering not yet supported on Radeon 9500/9700 and newer cards
(II) RADEON(0): Memory manager initialized to (0,0) (1280,8191)
(II) RADEON(0): Reserved area from (0,1024) to (1280,1026)
(II) RADEON(0): Largest offscreen area available: 1280 x 7165
(II) RADEON(0): Acceleration enabled
(II) RADEON(0): Using hardware cursor (scanline 1026)
(II) RADEON(0): Largest offscreen area available: 1280 x 7161
(**) RADEON(0): DPMS enabled
(II) RADEON(0): Direct rendering disabled
(==) RandR enabled
(II) Mouse0: ps2EnableDataReporting: succeeded
(II) RADEON(0): Wrote: rd=12, fd=96, pd=1
AUDIT: Wed Jul 21 15:06:22 2004: 6173 X: client 6 rejected from local host

System boot log [Modules found after installing ATI RPM]
Jul 21 13:59:06 ws-01 mdmonitor: mdadm succeeded
Jul 21 13:59:06 ws-01 mdmpd: mdmpd failed

Xerantius
22nd July 2004, 02:41 AM
xorg.conf
# File: XF86Config-4
# File generated by fglrxconfig (C) ATI Research, a substitute for xf86config.
...

Section "dri"
# Access to OpenGL ICD is allowed for all users:
Mode 0666
# Access to OpenGL ICD is restricted to a specific user group:
# Group 100 # users
# Mode 0660
EndSection


Section "Module"

# This loads the DBE extension module.

Load "dbe" # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection

# This loads the Type1 and FreeType font modules
Load "type1"
Load "freetype"

# This loads the GLX module
Load "glx" # libglx.a
Load "dri" # libdri.a

EndSection

# ************************************************** ********************
# Files section. This allows default font and rgb paths to be set
# ************************************************** ********************

Section "Files"

RgbPath "/usr/X11R6/lib/X11/rgb"

FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
EndSection


Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Philips 170C"
DisplaySize 340 270
HorizSync 30.0 - 80.0
VertRefresh 56.0 - 76.0
Option "dpms"



EndSection


# ************************************************** ********************


# === ATI device section ===

Section "Device"
Identifier "ATI Graphics Adapter"
Driver "fglrx"
# ### generic DRI settings ###
# === disable PnP Monitor ===
#Option "NoDDC"
# === disable/enable XAA/DRI ===
Option "no_accel" "no"
Option "no_dri" "no"
# === misc DRI settings ===
Option "mtrr" "off" # disable DRI mtrr mapper, driver has its own code for mtrr
# ### FireGL DDX driver module specific settings ###
# === Screen Management ===
Option "DesktopSetup" "0x00000000"
Option "MonitorLayout" "AUTO, AUTO"
Option "IgnoreEDID" "off"
Option "HSync2" "unspecified"
Option "VRefresh2" "unspecified"
Option "ScreenOverlap" "0"
# === TV-out Management ===
Option "NoTV" "no"
Option "TVStandard" "PAL-B"
Option "TVHSizeAdj" "0"
Option "TVVSizeAdj" "0"
Option "TVHPosAdj" "0"
Option "TVVPosAdj" "0"
Option "TVHStartAdj" "0"
Option "TVColorAdj" "0"
Option "GammaCorrectionI" "0x00000000"
Option "GammaCorrectionII" "0x00000000"
# === OpenGL specific profiles/settings ===
Option "Capabilities" "0x00000000"
# === Video Overlay for the Xv extension ===
Option "VideoOverlay" "on"
# === OpenGL Overlay ===
# Note: When OpenGL Overlay is enabled, Video Overlay
# will be disabled automatically
Option "OpenGLOverlay" "off"
# === Center Mode (Laptops only) ===
Option "CenterMode" "off"
# === Pseudo Color Visuals (8-bit visuals) ===
Option "PseudoColorVisuals" "off"
# === QBS Management ===
Option "Stereo" "off"
Option "StereoSyncEnable" "1"
# === FSAA Management ===
Option "FSAAEnable" "no"
Option "FSAAScale" "1"
Option "FSAADisableGamma" "no"
Option "FSAACustomizeMSPos" "no"
Option "FSAAMSPosX0" "0.000000"
Option "FSAAMSPosY0" "0.000000"
Option "FSAAMSPosX1" "0.000000"
Option "FSAAMSPosY1" "0.000000"
Option "FSAAMSPosX2" "0.000000"
Option "FSAAMSPosY2" "0.000000"
Option "FSAAMSPosX3" "0.000000"
Option "FSAAMSPosY3" "0.000000"
Option "FSAAMSPosX4" "0.000000"
Option "FSAAMSPosY4" "0.000000"
Option "FSAAMSPosX5" "0.000000"
Option "FSAAMSPosY5" "0.000000"
# === Misc Options ===
Option "UseFastTLS" "0"
Option "BlockSignalsOnLock" "on"
Option "UseInternalAGPGART" "yes"
Option "ForceGenericCPU" "no"
BusID "PCI:1:0:0" # vendor=1002, device=4150
Screen 0
EndSection

# ************************************************** ********************
# Screen sections
# ************************************************** ********************

Identifier "Screen0"
Device "ATI Graphics Adapter"
Monitor "Monitor0"
DefaultDepth 24
#Option "backingstore"

Subsection "Display"
Depth 24
Modes "1280x1024"
ViewPort 0 0 # initial origin if mode is smaller than desktop
# Virtual 1280 1024
EndSubsection
EndSection

# ************************************************** ********************
# ServerLayout sections.
# ************************************************** ********************


Section "ServerLayout"
Identifier "Server Layout"
Screen "Screen0"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection

Alleister
22nd July 2004, 06:46 AM
doesn't works with 9600 family of ati cards... so i'm stuck with eyefriendly 60HZ on the vesa driver... this is *so* annoying... absolutly unusable. does anyone know what to do about that (apart from buying an lcd screen of course) or do i have to abandon fc2?

micha
22nd July 2004, 10:20 AM
I have a ATI Radeon Mobility 9600, and it works well. Look at the little radeon how-to at http://fedorafaq.org

shch00r
22nd July 2004, 10:27 AM
Dude, just select Ati 9600 and it should work.. it did for me... although i do not have OpenGL acceleration turned on...

imdeemvp
22nd July 2004, 10:28 AM
i can no longer get into my desktop i tried this last nite and must done something wrong...i get a message the my mouse is not configure properly....so tried reconfiguring it and still does not work after i type: init 5

i tried linux rescue....and nothing since to help....AND when i tried to edit the xorg.conf with macs or vivo i get a blank screen....

DO WE HAVE TO EMULATE THE 3 BOTTON MOUSE?

IS THERE A WAY TO INSTALL THESE DRIVERS WITHOUT EXIT THE GRAPHICAL MODE?? ATI WEBSITE DOES NOT SAY ANYTHING ABOUT TEXT MODE INSTALLATION!

GOT TERMINAL ANYONE? :mad:

shch00r
22nd July 2004, 11:00 AM
Yeah... i followed the howto on fedorafaq. No errors, no results either:

[root@Radek root]# glxinfo |grep direct
direct rendering: No
OpenGL renderer string: Mesa GLX Indirect

ATI COntrol Panel isn't working, plus, i've got 2 (yes TWO) icons theoretically directing to it... plus one in system settings. This DEFINATELY suxx... Any1 has any ideas?

imdeemvp
22nd July 2004, 11:13 AM
btw.....i also read the some mobo's chipset are not supported...ei kt400, kt600, kt800, sis 746 (946 maybe??) or higher and i845 and higher....could this be our problem???

my mobo ecs with kt600 chipset :D

Alleister
22nd July 2004, 01:21 PM
@shch00r:
you where right. i dreaded to try this, because in the release candidates this only resulted in a crashing x server... seems someone has corrected this... and i can live without hardware accelerated 3d...

DarkIce
30th July 2004, 01:11 AM
shch00r: I have the EXACT same problem.

Is there possiblity of getting the ATI 9600 Pro for direct rendering or no?

spyder24204
1st August 2004, 04:07 AM
hey im a noob, ive got the exaxt same problem with the double icons and the :mad: mesa :mad: with no dri (using a radeon 9000 pci) and this problem is the same in mandrake 9.2 and 10 as well as fc2

but after the "first" clean install of fc2 it detects my on-board s3 graphics and installs fine(as long as onboard vga is selected in bios).

when install is complete(this is how i got dri working 4 my radeon) i went into display settings, under hardware i selected "radeon 9000" as my graphics card, applyed the changes, rebooted enabled my pci graphics in bios then booted up into fc2 with dri enabled. and now tuxracer runs good and pretty much all the games. i had dri right up until i tried to install the radeon drivers after that all i can get is mesa until i go a clean install again. to check that everything was working i installed americas army it installed and actually ran(not to well but it ran). i was only getting 20fps max(which is why i tried the ati official drivers).

ive been to every forum and faq outr there and i got nada. is there ne1 out there that can help?

oh yea americas army runs great in windows xp.

lpgcn17
2nd August 2004, 12:41 AM
This looks like an awesome How-To and i hope it will work. Ive tried getting this driver working before without much success. Im running currently on:

AMD Athlon XP 2500+
ATI Radeon 9200
MSI K7N2 Delta-L
256 PC3200 Corsair RAM

I'll try following this How-To. Wish me luck.

astreyon
2nd August 2004, 09:09 AM
hy guys,
i have installed the ATI radeon driver successfully, without any bug
but i have noticed that my desktop (gnome 2.6+metacity) is now slower than before
i didn't find out what makes my desktop running slower :(

anyone has encounter the same problem ?
if yes , do you find a way to fix it ?

my installation :
fedora core 2
on
laptop asus M6000n
centrino 1.4ghz
512 mega RAM
40 Go
ati radeon 9600 64mega DDR
netgear WG511 (802.11g)

Chronos
7th August 2004, 07:41 AM
Micha, is there a patch for the regparm patch for 2.6.7 kernel? Actually does anyone have or know the patch, not just micha, but he/she seemed to be on top of that stuff. hehe.

Thanks

---- edit ----
Err, nevermind, i utilized the power of google and found this:
http://rage3d.com/board/showthread.php?threadid=33737573
no patch errors this time. ^^ Thanks anyway heh.
However, I still cannot make it.


[root@ifrit build_mod]# sh make.sh
ATI module generator V 2.0
==========================
initializing...
Error:
XFree86 drm includes at /lib/modules/2.6.7-1.494.2.2/build/include/../drivers/char/drm do not fit this driver.
This driver is designed to only work with X4.1.0 or higher.
You can match this by getting Linux kernel 2.4.8 or higher.

I think maybe i missed a patch? Both patches were successful. I know its cause im not using xfree86, but instead Xorg.

I went ahead an with the rest of the step to success, but not total. Meaning no errors but also no el worko.

This is my only error and once i fix this i can repeat and get it to work. Any suggestions?

BINGO!! I did what N6546R suggested on page 5. except i only used the patch that i found on google. Wow im really sorry for this post. I hope this helps others. Otherwise, thats for listening to my idle chatter.

So with my radeon 9800pro i get this


[root@ifrit chronos]# glxinfo | grep direct
direct rendering: Yes
[root@ifrit chronos]# glxgears
13620 frames in 5.0 seconds = 2724.000 FPS
15684 frames in 5.0 seconds = 3136.800 FPS
15682 frames in 5.0 seconds = 3136.400 FPS
15683 frames in 5.0 seconds = 3136.600 FPS
15674 frames in 5.0 seconds = 3134.800 FPS
Broken pipe
[root@ifrit chronos]#

Thank you everyone, this is great. hehe.

micha
7th August 2004, 03:43 PM
With the new ATI driver (3.11.1) you don't need any regparm or mm patch anymore, just a little Fedora patch for the DRM include patch.

Littlejia
10th August 2004, 09:02 AM
some big big err .help me

[root@Deadforg down]# rpm -Uvh --force fglrx-4.3.0-3.7.6.i386.rpm
Preparing... ########################################### [100%]
1:fglrx ########################################### [100%]
*** Trying to install a precompiled kernel module.
- creating symlink
- recreating module dependency list
- trying a sample load of the kernel module
FATAL: Error inserting fglrx (/lib/modules/2.6.5-1.358/kernel/drivers/char/drm/fglrx.ko): No such device
failed.
*** Found kernel module build environment, generating kernel module now.
ATI module generator V 2.0
==========================
initializing...
Error:
XFree86 drm includes at /lib/modules/2.6.5-1.358/build/include/../drivers/char/drm do not fit this driver.
This driver is designed to only work with X4.1.0 or higher.
You can match this by getting Linux kernel 2.4.8 or higher.
- creating symlink
- recreating module dependency list
- trying a sample load of the kernel module
FATAL: Error inserting fglrx (/lib/modules/2.6.5-1.358/kernel/drivers/char/drm/fglrx.ko): No such device
failed.
Installed: qt3 (gcc 3.2) based control panel application
===
ATI display drivers successfully installed
please run 'fglrxconfig' now
===
[root@Deadforg down]# cd /lib/modules/fglrx/build_mod/

[root@Deadforg build_mod]# patch -p1 < /usr/bak/fglrx-3.7.6-fedora.patch
patching file 2.6.x/Makefile
patching file make.sh
[root@Deadforg build_mod]# patch -p1 < /usr/bak/fglrx-3.7.6-regparm.patch
patching file firegl_public.c
patching file firegl_public.h
patching file make.sh
[root@Deadforg build_mod]# sh make.sh
ATI module generator V 2.0
==========================
initializing...
cleaning...
patching 'highmem.h'...
skipping patch for 'drmP.h', not needed
skipping patch for 'drm_os_linux.h', not needed
assuming new VMA API since we do have kernel 2.6.x...
doing Makefile based build for kernel 2.6.x and higher
make -C /lib/modules/2.6.5-1.358/build SUBDIRS=/lib/modules/fglrx/build_mod/2.6.x modules
make[1]: Entering directory `/lib/modules/2.6.5-1.358/build'
CC [M] /lib/modules/fglrx/build_mod/2.6.x/firegl_public.o
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2260: warning: initialization from incompatible pointer type
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2278: warning: initialization from incompatible pointer type
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2285: warning: initialization from incompatible pointer type
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2292: warning: initialization from incompatible pointer type
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2301: warning: initialization from incompatible pointer type
LD [M] /lib/modules/fglrx/build_mod/2.6.x/fglrx.o
Building modules, stage 2.
MODPOST
LD [M] /lib/modules/fglrx/build_mod/2.6.x/fglrx.ko
make[1]: Leaving directory `/lib/modules/2.6.5-1.358/build'
build succeeded with return value 0
duplicating results into driver repository...
done.
==============================
You must change your working directory to /lib/modules/fglrx
and then call ./make_install.sh in order to install the built module.
==============================
[root@Deadforg build_mod]# cd ..
[root@Deadforg fglrx]# sh make_install.sh
- creating symlink
- recreating module dependency list
- trying a sample load of the kernel module
FATAL: Error inserting fglrx (/lib/modules/2.6.5-1.358/kernel/drivers/char/drm/fglrx.ko): No such device
failed.

yuiol
11th August 2004, 01:49 AM
I am using the new 3.1.1 drivers. I already installed the patches, how do I unistall them?

TylerD75
22nd August 2004, 12:33 AM
1. Download the Fedora Core 2 patches in /tmp (for example)

http://rambo.its.tudelft.nl/~ewald/patches/fglrx-3.7.6-fedora.patch


Anyone else having problems downloading this? I only get the message that I don't have permissions to view the page! Damn, so close (maybe) but still so far away! :mad:
Do you know of any other place I can find the patch?

Cheers,
Tyler Durden

nlawalker
22nd August 2004, 09:05 PM
Ditto for me. I've tried one or two other procedures to no avail, and was hoping this one would work, but I cannot locate the first patch mentioned. Googling it only results in more links to the same place.

NW

lactus1
23rd August 2004, 12:41 AM
same happend to me. can anybody put that patch as post on this forum?

micha
23rd August 2004, 08:18 AM
You can find many patches here:
http://fedorafaq.org
http://www.fedoraforum.org/forum/showthread.php?t=20211
http://www.fedoraforum.org/forum/showthread.php?t=16690
http://www.rage3d.com/board/showthread.php?s=&threadid=33737573

wiz561
23rd August 2004, 03:53 PM
Hi!

It seems like a lot of people have problems with fedora core 2 and using the radeon chipset (including myself). I've tried to visit the rage3d forum and get help there, but gave up after some time because nothing was working for me. :-( (I have a radeon m9 mobility chipset)

Anyways, with all the different kernel updates out there, I was wondering if anybody had a final writeup on how to install the driver and the patches. It's somewhat confusing because it seems like there's a dozen different patches and each way is different. I know once I do get the 3d acceleration working, I'll be like "damn, it's that easy"?!? But for now, I'm left with scratching my head wondering how to get this thing to work!!!

Thanks for your help so far in trying to get this chip working! :-) Well, maybe not working...but either way, thanks for your help in helping me trying to get it working! :-)

Cosmin Banu
24th August 2004, 01:17 PM
I got rid of the Mesa thing by modifying the internal/external AGPGART thing. Maybe this is the solution. I have a Radeon 9200SE chipset. Now I've got the OpenGL ATI Display Drivers up and running.

wiz561
25th August 2004, 06:07 PM
Thanks for teh info. I followed one of the writeups on a web page from Micha, i believe. After trying that with all the latest drivers, I believe I got things finally working. The fglxinfo says that it's a radeon mobility driver instead of the generic one that comes iwth linux... thanks for your help!

asun
25th August 2004, 06:38 PM
Slightly OT here. Has anyone experience problem with mplayer after installing fglrx driver? Occassionally, I get mplayer crashing with complain that it cannot use -vo xv video output. I have to switch to -vo gl2 and everything works again. Restarting X also re-enables xv sometimes.

micha
25th August 2004, 07:07 PM
Yep, this is a little problem with Xv and Xorg. You have to add the following option in the device section (the fglrx part) of the xorg.conf file:

Option "XaaNoOffscreenPixmaps"

http://www.fedoraforum.org/forum/showpost.php?p=73516&postcount=1

wiz561
25th August 2004, 07:29 PM
I don't really use mplayer, but from the little I use xmms, I can admit that I've had my fair share of lockups. Not sure why, but I just have...

asun
25th August 2004, 10:25 PM
Yep, this is a little problem with Xv and Xorg. You have to add the following option in the device section (the fglrx part) of the xorg.conf file:

Option "XaaNoOffscreenPixmaps"

http://www.fedoraforum.org/forum/showpost.php?p=73516&postcount=1

This is more of a general question. Is it save to edit /etc/X11/xorg.conf while X is running (run level = 5)?

micha
26th August 2004, 12:02 AM
This is more of a general question. Is it save to edit /etc/X11/xorg.conf while X is running (run level = 5)?
Yep, there's no problem. Xorg reads the config file on startup only, so you can edit the config file safely after that (don't forget to backup a working xorg.conf file first). If you modify the Xorg.conf file, you have to restart Xorg (CTRL+ALT+BACKSPACE or init 3 && init 5) for the modifications to take effect.

waynev
26th August 2004, 07:57 AM
[QUOTE=gotmonkey]This is what I did to get my 9700 pro working in Fedora Core 2. This allowed me to have direct rendering support under xorg with ATI drivers.

....<stuff deleted>

1. Download the Fedora Core 2 patches in /tmp (for example)

http://rambo.its.tudelft.nl/~ewald/patches/fglrx-3.7.6-fedora.patch
http://www.kaseorg.com/fglrx-3.7.6-regparm.patch

Download the rpm from ATI Drivers. I used version 4.3.0

:mad:
The fedora patch(http://rambo.its.tudelft.nl/~ewald/patches/fglrx-3.7.6-fedora.patch) no longer seems accessible. Is there another location for it?

micha
26th August 2004, 01:08 PM
http://fedorafaq.org

asun
27th August 2004, 12:26 AM
Another question. Do I need to rebuild the fglrx module everytime there is a new kernel?

micha
27th August 2004, 01:15 AM
Yep ... :)

asun
29th August 2004, 12:45 AM
So when there's a new kernel, I need to:
Option 1:
- Edit xorg.conf and use radeon.
- Boot the new kernel.
- Compile the fglrx module against the new kernel.
- Edit xorg.conf and use fglrx. Restart X.
Option 2:
- Edit inittab to runlevel 3.
- Boot the new kernel.
- Compile fglrx module against the new kernel.
- start x.

Do I get this right?

micha
29th August 2004, 12:58 AM
Option 2's good !

Mr.Lee
2nd September 2004, 05:08 PM
allright so can someone explain in short

how to recompile the fxglr module against a new kernel ?
the module worked whilst working in 2.6.7
but now after using a new published kernel 2.6.8 the module of course
failes to start.

thx in advance .


cheers lee

sayonara
3rd September 2004, 02:39 PM
I tried installing the ATI drivers but when I ran 'fglrxconfig' it didn't list my Mobility Radeon M6 card in the list of supported cards.

I tried 'glxinfo | grep direct' and it gave me "direct rendering = No" and said that it was using Mesa.

However, when I ran 'glxgears' I saw a window with 3 rotating gears and got a frame rate of about 600. Does the fact that I can see the gears mean that 3D is working or should I be expecting a higher framerate? (It's a 3 year old 16MB card)

Any help appreciated

olivierv
3rd September 2004, 08:55 PM
Ok- I'm probably pushing my luck here but here I go.

Has anyone gotten this working with dual monitors? I'm using a Mobility 9700 and I had configured my X server to use dual head with the provided radeon drivers. Problem was, of course, no 3D (glxgears -> ~40fps).

I installed the 3.11.1 ATI drivers and cannot get my second monitor to come up looking anything other than having been passed through a blender before reaching the LCD. Now, I'm using the same timing info from my previous xorg.conf file (the one that was working) but it just refuses to be legible. I get no errors that I can see (unless they're being displayed on the blender monitor).

Odd thing, and possibly related- while my glxgears fps are now in the 1700fps range, fglrxinfo outputs to following:


[olivierv@I9100-FC2 olivierv]$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY RADEON 9700 Generic
OpenGL version string: 1.3 (X4.3.0-3.11.1)

display: :0.0 screen: 1
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.4 Mesa 5.0.2)


Which is not direct rendering as I would have expected with such a drastic 3D speed increase.

Anyone got a clue they could spare? I'm all out and I don't want to go back to the radeon driver.

Olivier

[EDIT]
Yeah, I'm an idiot: here's what the xorg log say for DRI on the 'blender' monitor:



(II) fglrx(0): Acceleration enabled
(II) fglrx(0): X context handle = 0x00000001
(II) fglrx(0): [DRI] installation complete
(II) fglrx(0): Direct rendering enabled
(II) Loading extension FGLRXEXTENSION
(II) Loading extension ATITVOUT
(==) RandR enabled
(II) fglrx(1): driver needs XFree86 version: 4.3.x
(WW) fglrx(1): could not detect XFree86 version (query_status=-3)
(II) fglrx(1): doing DRIScreenInit
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenDevice: minor is 0
.
.
[snip snip snip]
.
.
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
(II) fglrx(1): [drm] drmOpen failed
(EE) fglrx(1): DRIScreenInit failed!
(WW) fglrx(1): ***********************************************
(WW) fglrx(1): * DRI initialization failed! *
(WW) fglrx(1): * (maybe driver kernel module missing or bad) *
(WW) fglrx(1): * 2D acceleraton available (MMIO) *
(WW) fglrx(1): * no 3D acceleration available *
(WW) fglrx(1): ********************************************* *
(EE) fglrx(1): DRI initialization for 2nd screen failed - aborting!

frobroj
4th September 2004, 03:54 AM
Cant locate the fglrx-3.7.6-fedora.patch file... I have searched high and low... any ideas?

Thanks,
frobro

whiteb0x
5th September 2004, 12:34 PM
can some PLEASE post another link :)
I'm begging you... it's so infuriating when you need 1 file but can't find it :'(

_Ali
5th September 2004, 07:56 PM
I am relatively new to the Linux operating system. I am also having difficulty in successfully downloading the necessary patch from:
http://rambo.its.tudelft.nl/~ewald/....6-fedora.patch .

Since Ive just joined this forum I would appreciate any help with this problem thank you.

Ali G

dontcare
12th September 2004, 11:15 PM
I also need that file since that site is not allowing me to download it.
If anyone could give me a link or post it on their website with a link that would be great.

dontcare
14th September 2004, 09:52 PM
cmon all i need is that opne file does anyone know where i can find it?

Raja
15th September 2004, 12:55 AM
Here is the link to the patch. Good Luck

http://www.fedoraforum.org/forum/attachment.php?attachmentid=3340.com

Shadow Skill
15th September 2004, 10:40 PM
Hi I'm running a Radeon 9000 sapphire and I can't install the driver module with 2.6.8 I get this error
- creating symlink
- recreating module dependency list
- trying a sample load of the kernel module
FATAL: Error inserting fglrx (/lib/modules/2.6.8-1.521/kernel/drivers/char/drm/fglrx.ko): Invalid module format
failed.
I followed the instructions available here http://fedorafaq.org/#drivers

Do I need the regparm patch? When I click the link in the original post all I get is a text file what if anything am I supposed to do with that?

remi
16th September 2004, 06:07 PM
It seems like you are in graphical mode so module can't load...

Try reboot in level 3 (text mode) before installing the new driver.

Shadow Skill
16th September 2004, 11:27 PM
Now I get this in runlevel 3 when I do shmake_install. sh [code]fglrx version magic 2.6.8-1.521 686 regparm 4stacks 3.4 should be gcc3.3 (it repeats the regparm thing again, I'm just too lazy to type it.) I have gcc 3.4 installed should I downgrade? If so how?

foolish
17th September 2004, 02:45 PM
Thought I should let you all know:

There's work over at livna.org (http://rpm.livna.org) on creating ATI driver rpms just like we have for nvidia. See the bugzilla entry for details: http://bugzilla.livna.org/show_bug.cgi?id=237

If you really want to make installing the driver easier for Fedora users, help the process of creating the rpm.

spiffdog85
21st September 2004, 11:10 PM
Hi whenever I execture teh make.sh command in the install process, I get this error.

ATI module generator V 2.0
==========================
initializing...
Error:
XFree86 drm includes at /lib/modules/2.6.8-1.521/build/include/../drivers/char/drm do not fit this driver.
This driver is designed to only work with X4.1.0 or higher.
You can match this by getting Linux kernel 2.4.8 or higher.

Does Anyone know how to fix this?

zachias
23rd September 2004, 09:28 PM
Duplicating an earlier post, but I think I might get a better response here....

I've installed Fedora Core 2 on my Dell workstation in dual boot mode and finally got that to work. However, I have an ATI V3100 graphics card that I need to install the FireGL drivers for. I've downloaded the latest tarball from ATI which is version 3.12.0, but I don't think that it even supports the V3100. I've read several of the threads which detail an installation of older ATI drivers for Radeon cards for FC2 but I was unable to get that to work as well. I'm running kernel 2.6.8-1.521smp. Everything else works fine, but without 3D acceleration, I'm really hurting. Any ideas?

Zach

linuxxed
25th September 2004, 12:32 PM
Hi whenever I execture teh make.sh command in the install process, I get this error.

ATI module generator V 2.0
==========================
initializing...
Error:
XFree86 drm includes at /lib/modules/2.6.8-1.521/build/include/../drivers/char/drm do not fit this driver.
This driver is designed to only work with X4.1.0 or higher.
You can match this by getting Linux kernel 2.4.8 or higher.

Does Anyone know how to fix this?


I'm getting exactly the same error with FC2 - 2.6.8 kernel. I have a radeon 9100 and followed the instructions on http://fedorafaq.org/#radeon

Can anyone help?

linuxxed
25th September 2004, 04:13 PM
fixed it! For some reason the patch requires that /usr/src/linux symlink is not present. So if you have one then delete that symlink. It compiles fine after that.



linuxxed

donoghmacfadden
6th October 2004, 02:57 PM
Hi lads, i'm new to fedora, have followed the faq's etc for installing my mobility 9000 (m9). And am now getting 980 fps in gears. Does this sound reasonable? I can play cube, tux racer etc, seems to be ok. Any input would be appreciated. D.

miskopisko
6th October 2004, 04:25 PM
Ok I followed the above instructions and I installed the ATI drivers on my Toshiba A70 laptop with a Radeon Mobile 9000. I run fglrxinfo and it shows me that the correct ATI drivers are being used and all seem OK. Same goes with glxinfo.
But when i try to tun glxgears or any other opengl program (even screensavers) I have total system freeze. My mouse moves but I cannot click anything and no keyboaed functions work. The only way to get out of this is to do a hard reboot with the power button.
Ive ran the fglrxconfig a few times choosing different inputs and still the same result.
Otherwise the resolution and colors on the screen are beautiful but what good is that without opengl.

Thanks for any and all help in advance.

blarg
10th October 2004, 10:11 PM
I'm having the same issue. Anyone with a solution ?

blarg
10th October 2004, 10:14 PM
Ok- I'm probably pushing my luck here but here I go.

Has anyone gotten this working with dual monitors? I'm using a Mobility 9700 and I had configured my X server to use dual head with the provided radeon drivers. Problem was, of course, no 3D (glxgears -> ~40fps).

I installed the 3.11.1 ATI drivers and cannot get my second monitor to come up looking anything other than having been passed through a blender before reaching the LCD. Now, I'm using the same timing info from my previous xorg.conf file (the one that was working) but it just refuses to be legible. I get no errors that I can see (unless they're being displayed on the blender monitor).

Odd thing, and possibly related- while my glxgears fps are now in the 1700fps range, fglrxinfo outputs to following:


[olivierv@I9100-FC2 olivierv]$ fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: MOBILITY RADEON 9700 Generic
OpenGL version string: 1.3 (X4.3.0-3.11.1)

display: :0.0 screen: 1
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.4 Mesa 5.0.2)


Which is not direct rendering as I would have expected with such a drastic 3D speed increase.

Anyone got a clue they could spare? I'm all out and I don't want to go back to the radeon driver.

Olivier

[EDIT]
Yeah, I'm an idiot: here's what the xorg log say for DRI on the 'blender' monitor:



(II) fglrx(0): Acceleration enabled
(II) fglrx(0): X context handle = 0x00000001
(II) fglrx(0): [DRI] installation complete
(II) fglrx(0): Direct rendering enabled
(II) Loading extension FGLRXEXTENSION
(II) Loading extension ATITVOUT
(==) RandR enabled
(II) fglrx(1): driver needs XFree86 version: 4.3.x
(WW) fglrx(1): could not detect XFree86 version (query_status=-3)
(II) fglrx(1): doing DRIScreenInit
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenDevice: minor is 0
.
.
[snip snip snip]
.
.
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
(II) fglrx(1): [drm] drmOpen failed
(EE) fglrx(1): DRIScreenInit failed!
(WW) fglrx(1): ***********************************************
(WW) fglrx(1): * DRI initialization failed! *
(WW) fglrx(1): * (maybe driver kernel module missing or bad) *
(WW) fglrx(1): * 2D acceleraton available (MMIO) *
(WW) fglrx(1): * no 3D acceleration available *
(WW) fglrx(1): ********************************************* *
(EE) fglrx(1): DRI initialization for 2nd screen failed - aborting!



I'm having the exact same same issue only on AIW 9600. Anyone have a solution for this?

soupboy
11th October 2004, 11:31 AM
kernel 2.6.8 and above changed the page structure. This patch allows the fglrx 3.7.6 + regparm patches to work.



diff -ur build_mod/2.6.x/agpgart_be.c build_mod.jamie/2.6.x/agpgart_be.c
--- build_mod/2.6.x/agpgart_be.c 2004-03-04 12:25:44.000000000 -0500
+++ build_mod.jamie/2.6.x/agpgart_be.c 2004-10-11 05:55:12.556649288 -0400
@@ -1402,7 +1402,7 @@
}
#endif

- atomic_inc(&page->count);
+ atomic_inc(&page->_count);
set_bit(PG_locked, &page->flags);
atomic_inc(&agp_bridge.current_memory_agp);

@@ -1449,7 +1449,7 @@
put_page(page);
UnlockPage(page);
#else /* AGPGART_2_4_19 */
- atomic_dec(&page->count);
+ atomic_dec(&page->_count);
clear_bit(PG_locked, &page->flags);
wake_up(&page->wait);
#endif /* AGPGART_2_4_19 */
@@ -4413,7 +4413,7 @@
if (page == NULL)
return 0;

- atomic_inc(&page->count);
+ atomic_inc(&page->_count);
set_bit(PG_locked, &page->flags);
atomic_inc(&agp_bridge.current_memory_agp);

@@ -4509,7 +4509,7 @@
put_page(page);
UnlockPage(page);
#else /* AGPGART_2_4_19 */
- atomic_dec(&page->count);
+ atomic_dec(&page->_count);
clear_bit(PG_locked, &page->flags);
wake_up(&page->wait);
#endif /* AGPGART_2_4_19 */
diff -ur build_mod/2.6.x/firegl_public.c build_mod.jamie/2.6.x/firegl_public.c
--- build_mod/2.6.x/firegl_public.c 2004-10-11 05:43:39.799964312 -0400
+++ build_mod.jamie/2.6.x/firegl_public.c 2004-10-11 05:55:12.990583320 -0400
@@ -2066,7 +2066,7 @@
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 */

#if LINUX_VERSION_CODE >= 0x020400
// __KE_DEBUG3("vm-address 0x%08lx => kernel-page-address 0x%p\n",
diff -ur build_mod/agpgart_be.c build_mod.jamie/agpgart_be.c
--- build_mod/agpgart_be.c 2004-03-04 12:25:44.000000000 -0500
+++ build_mod.jamie/agpgart_be.c 2004-10-11 05:55:12.556649288 -0400
@@ -1402,7 +1402,7 @@
}
#endif

- atomic_inc(&page->count);
+ atomic_inc(&page->_count);
set_bit(PG_locked, &page->flags);
atomic_inc(&agp_bridge.current_memory_agp);

@@ -1449,7 +1449,7 @@
put_page(page);
UnlockPage(page);
#else /* AGPGART_2_4_19 */
- atomic_dec(&page->count);
+ atomic_dec(&page->_count);
clear_bit(PG_locked, &page->flags);
wake_up(&page->wait);
#endif /* AGPGART_2_4_19 */
@@ -4413,7 +4413,7 @@
if (page == NULL)
return 0;

- atomic_inc(&page->count);
+ atomic_inc(&page->_count);
set_bit(PG_locked, &page->flags);
atomic_inc(&agp_bridge.current_memory_agp);

@@ -4509,7 +4509,7 @@
put_page(page);
UnlockPage(page);
#else /* AGPGART_2_4_19 */
- atomic_dec(&page->count);
+ atomic_dec(&page->_count);
clear_bit(PG_locked, &page->flags);
wake_up(&page->wait);
#endif /* AGPGART_2_4_19 */
diff -ur build_mod/firegl_public.c build_mod.jamie/firegl_public.c
--- build_mod/firegl_public.c 2004-10-11 05:43:39.799964312 -0400
+++ build_mod.jamie/firegl_public.c 2004-10-11 05:55:12.990583320 -0400
@@ -2066,7 +2066,7 @@
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 */

#if LINUX_VERSION_CODE >= 0x020400
// __KE_DEBUG3("vm-address 0x%08lx => kernel-page-address 0x%p\n",

soupboy
11th October 2004, 11:39 AM
Kernel 2.6.8 and above changed the page structure (made count become _count) this patch fixes fglrx 3.7.6 so it compiles against 2.6.8

diff -ur build_mod/2.6.x/agpgart_be.c build_mod.jamie/2.6.x/agpgart_be.c
--- build_mod/2.6.x/agpgart_be.c 2004-03-04 12:25:44.000000000 -0500
+++ build_mod.jamie/2.6.x/agpgart_be.c 2004-10-11 05:55:12.556649288 -0400
@@ -1402,7 +1402,7 @@
}
#endif

- atomic_inc(&page->count);
+ atomic_inc(&page->_count);
set_bit(PG_locked, &page->flags);
atomic_inc(&agp_bridge.current_memory_agp);

@@ -1449,7 +1449,7 @@
put_page(page);
UnlockPage(page);
#else /* AGPGART_2_4_19 */
- atomic_dec(&page->count);
+ atomic_dec(&page->_count);
clear_bit(PG_locked, &page->flags);
wake_up(&page->wait);
#endif /* AGPGART_2_4_19 */
@@ -4413,7 +4413,7 @@
if (page == NULL)
return 0;

- atomic_inc(&page->count);
+ atomic_inc(&page->_count);
set_bit(PG_locked, &page->flags);
atomic_inc(&agp_bridge.current_memory_agp);

@@ -4509,7 +4509,7 @@
put_page(page);
UnlockPage(page);
#else /* AGPGART_2_4_19 */
- atomic_dec(&page->count);
+ atomic_dec(&page->_count);
clear_bit(PG_locked, &page->flags);
wake_up(&page->wait);
#endif /* AGPGART_2_4_19 */
diff -ur build_mod/2.6.x/firegl_public.c build_mod.jamie/2.6.x/firegl_public.c
--- build_mod/2.6.x/firegl_public.c 2004-10-11 05:43:39.799964312 -0400
+++ build_mod.jamie/2.6.x/firegl_public.c 2004-10-11 05:55:12.990583320 -0400
@@ -2066,7 +2066,7 @@
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 */

#if LINUX_VERSION_CODE >= 0x020400
// __KE_DEBUG3("vm-address 0x%08lx => kernel-page-address 0x%p\n",
diff -ur build_mod/agpgart_be.c build_mod.jamie/agpgart_be.c
--- build_mod/agpgart_be.c 2004-03-04 12:25:44.000000000 -0500
+++ build_mod.jamie/agpgart_be.c 2004-10-11 05:55:12.556649288 -0400
@@ -1402,7 +1402,7 @@
}
#endif

- atomic_inc(&page->count);
+ atomic_inc(&page->_count);
set_bit(PG_locked, &page->flags);
atomic_inc(&agp_bridge.current_memory_agp);

@@ -1449,7 +1449,7 @@
put_page(page);
UnlockPage(page);
#else /* AGPGART_2_4_19 */
- atomic_dec(&page->count);
+ atomic_dec(&page->_count);
clear_bit(PG_locked, &page->flags);
wake_up(&page->wait);
#endif /* AGPGART_2_4_19 */
@@ -4413,7 +4413,7 @@
if (page == NULL)
return 0;

- atomic_inc(&page->count);
+ atomic_inc(&page->_count);
set_bit(PG_locked, &page->flags);
atomic_inc(&agp_bridge.current_memory_agp);

@@ -4509,7 +4509,7 @@
put_page(page);
UnlockPage(page);
#else /* AGPGART_2_4_19 */
- atomic_dec(&page->count);
+ atomic_dec(&page->_count);
clear_bit(PG_locked, &page->flags);
wake_up(&page->wait);
#endif /* AGPGART_2_4_19 */
diff -ur build_mod/firegl_public.c build_mod.jamie/firegl_public.c
--- build_mod/firegl_public.c 2004-10-11 05:43:39.799964312 -0400
+++ build_mod.jamie/firegl_public.c 2004-10-11 05:55:12.990583320 -0400
@@ -2066,7 +2066,7 @@
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 */

#if LINUX_VERSION_CODE >= 0x020400
// __KE_DEBUG3("vm-address 0x%08lx => kernel-page-address 0x%p\n",

olpe
20th October 2004, 08:22 PM
Ok my problem is that I've got fglrx Version: 3.14.1, and kernel 2.6.8-1.521, Cant find patch for that... Can anyone help?

Bear Knuckle
20th October 2004, 11:51 PM
Ok my problem is that I've got fglrx Version: 3.14.1, and kernel 2.6.8-1.521, Cant find patch for that... Can anyone help?

http://www.stanford.edu/~fenn/linux/radeon.shtml

Patchdownload in the text.

olpe
21st October 2004, 09:04 PM
When I followed instructions, everything went well until this happened. I even changed back to kernel 2.6.5-1 and with both kernels I got this message...

sh make_install.sh
- creating symlink
- recreating module dependency list
- trying a sample load of the kernel module
FATAL: Error inserting fglrx (/lib/modules/2.6.5-1.358/kernel/drivers/char/drm/fglrx.ko): Operation not permitted
failed.

Any ideas?

Zako
23rd October 2004, 03:02 AM
I ran into some problems following these steps.. Im getting tons of Hunk failures in the patches.. and the .sh files will not do what they should..


Patches do this:

[root@localhost Desktop]# cd /lib/modules/fglrx/build_mod
[root@localhost build_mod]# patch -p1 -i /tmp/fglrx-3.7.6-fedora.patch
patching file 2.6.x/Makefile
patching file make.sh
Hunk #1 succeeded at 177 (offset 4 lines).
[root@localhost build_mod]# patch -p1 -i /tmp/fglrx-3.7.6-regparm.patch
patching file firegl_public.c
Reversed (or previously applied) patch detected! Assume -R? [n] y
Hunk #1 succeeded at 249 (offset 13 lines).
Hunk #2 FAILED at 685.
Hunk #3 FAILED at 702.
Hunk #4 FAILED at 716.
Hunk #5 FAILED at 755.
Hunk #6 FAILED at 763.
Hunk #7 FAILED at 792.
Hunk #8 FAILED at 841.
Hunk #9 FAILED at 854.
Hunk #10 FAILED at 877.
Hunk #11 FAILED at 908.
Hunk #12 FAILED at 961.
Hunk #13 FAILED at 969.
Hunk #14 FAILED at 1005.
Hunk #15 FAILED at 1040.
Hunk #16 FAILED at 1049.
Hunk #17 FAILED at 1060.
Hunk #18 FAILED at 1154.
Hunk #19 FAILED at 1169.
Hunk #20 FAILED at 1187.
Hunk #21 FAILED at 1212.
Hunk #22 FAILED at 1243.
Hunk #23 FAILED at 1253.
Hunk #24 FAILED at 1263.
Hunk #25 FAILED at 1277.
Hunk #26 FAILED at 1293.
Hunk #27 FAILED at 1309.
Hunk #28 FAILED at 1332.
Hunk #29 FAILED at 1359.
Hunk #30 FAILED at 1379.
Hunk #31 FAILED at 1390.
Hunk #32 FAILED at 1448.
Hunk #33 FAILED at 1461.
Hunk #34 FAILED at 1472.
Hunk #35 FAILED at 1484.
Hunk #36 FAILED at 1560.
Hunk #37 FAILED at 1582.
Hunk #38 FAILED at 1630.
Hunk #39 FAILED at 1660.
Hunk #40 FAILED at 1696.
Hunk #41 FAILED at 1705.
Hunk #42 FAILED at 1714.
Hunk #43 FAILED at 1725.
Hunk #44 FAILED at 1790.
Hunk #45 FAILED at 1810.
Hunk #46 FAILED at 1823.
Hunk #47 FAILED at 1833.
Hunk #48 FAILED at 2138.
Hunk #49 FAILED at 2162.
Hunk #50 FAILED at 2174.
Hunk #51 FAILED at 2201.
Hunk #52 succeeded at 2448 (offset 207 lines).
Hunk #53 succeeded at 2266 (offset 13 lines).
Hunk #54 succeeded at 2469 with fuzz 1 (offset 207 lines).
Hunk #55 FAILED at 2492.
Hunk #56 FAILED at 2784.
Hunk #57 FAILED at 2807.
Hunk #58 FAILED at 2915.
Hunk #59 FAILED at 2931.
Hunk #60 FAILED at 2960.
Hunk #61 FAILED at 2974.
Hunk #62 FAILED at 2984.
Hunk #63 FAILED at 2995.
Hunk #64 FAILED at 3006.
Hunk #65 FAILED at 3017.
Hunk #66 FAILED at 3034.
Hunk #67 FAILED at 3065.
Hunk #68 FAILED at 3076.
Hunk #69 FAILED at 3086.
Hunk #70 FAILED at 3173.
Hunk #71 FAILED at 3189.
Hunk #72 FAILED at 3205.
Hunk #73 FAILED at 3241.
Hunk #74 FAILED at 3328.
Hunk #75 FAILED at 3370.
71 out of 75 hunks FAILED -- saving rejects to file firegl_public.c.rej
patching file firegl_public.h
Hunk #2 FAILED at 73.
Hunk #3 FAILED at 103.
Hunk #4 FAILED at 158.
Hunk #5 FAILED at 196.
Hunk #6 FAILED at 235.
Hunk #7 FAILED at 336.
Hunk #8 FAILED at 373.
7 out of 8 hunks FAILED -- saving rejects to file firegl_public.h.rej
patching file make.sh
Hunk #1 succeeded at 991 (offset -2 lines).


The make.sh does this:


[root@localhost build_mod]# sh make.sh
ATI module generator V 2.0
==========================
initializing...
cleaning...
patching 'highmem.h'...
skipping patch for 'drmP.h', not needed
skipping patch for 'drm_os_linux.h', not needed
assuming new VMA API since we do have kernel 2.6.x...
doing Makefile based build for kernel 2.6.x and higher
make -C /lib/modules/2.6.8-1.521/build SUBDIRS=/lib/modules/fglrx/build_mod/2.6.x modules
make[1]: Entering directory `/lib/modules/2.6.8-1.521/build'
CC [M] /lib/modules/fglrx/build_mod/2.6.x/agp3.o
CC [M] /lib/modules/fglrx/build_mod/2.6.x/nvidia-agp.o
CC [M] /lib/modules/fglrx/build_mod/2.6.x/agpgart_be.o
CC [M] /lib/modules/fglrx/build_mod/2.6.x/i7505-agp.o
CC [M] /lib/modules/fglrx/build_mod/2.6.x/firegl_public.o
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2505: warning: initialization from incompatible pointer type
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2506: error: `ip_drm_vm_open' undeclared here (not in a function)
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2506: error: initializer element is not constant
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2506: error: (near initialization for `vm_pcie_ops.open')
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2507: error: `ip_drm_vm_close' undeclared here (not in a function)
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2507: error: initializer element is not constant
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2507: error: (near initialization for `vm_pcie_ops.close')
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2516: error: `ip_drm_vm_open' undeclared here (not in a function)
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2516: error: initializer element is not constant
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2516: error: (near initialization for `vm_agp_bq_ops.open')
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2517: error: `ip_drm_vm_close' undeclared here (not in a function)
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2517: error: initializer element is not constant
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2517: error: (near initialization for `vm_agp_bq_ops.close')
make[2]: *** [/lib/modules/fglrx/build_mod/2.6.x/firegl_public.o] Error 1
make[1]: *** [_module_/lib/modules/fglrx/build_mod/2.6.x] Error 2
make[1]: Leaving directory `/lib/modules/2.6.8-1.521/build'
make: *** [kmod_build] Error 2
build failed with return value 2

The make_install.sh does this:


[root@localhost fglrx]# sh make_install.sh
*** WARNING ***
Tailored kernel module for fglrx not present in your system.
You must go to /lib/modules/fglrx/build_mod subdir
and execute './make.sh' to build a fully customed kernel module.
Afterwards go to /lib/modules/fglrx and run './make_install.sh'
in order to install the module into your kernel's module repository.
(see readme.txt for more details.)

As of now you can still run your XServer in 2D, but hardware acclerated
OpenGL will not work and 2D graphics will lack performance.

failed.


I have downloaded and installed the latest 4.3 ATI driver. I have previously run "yum update" and have the latest 521 fedora core 2 kernel and kernel source installed (as far as I can tell)

What am I doing wrong here?

olpe
23rd October 2004, 08:56 AM
Which 4.3 Ati driver version do you have?

I'm not sure, but atleast I think you try to patch your fglrx with fglrx-3.7.6 which may not be the right patch for your version of fglrx. Try to use this patch ( http://www.stanford.edu/~fenn/linux/fglrx-3.14.1-fc2.patch ) ...

moZer
24th October 2004, 12:14 AM
Note that Livna (rpm.livna.org) will very soon (it's in pending as of Oct 23) release an ATI-fglrx package which is highly customized, like the Nvidia package, and will (hopefully, fingers crossed) "just work".

If you decide to use that package on top of an old ATI installation, make sure you purge the system of any ATI-related driver rpms. The "official" package does some unfortunate modifications to the system.

Check http://bugzilla.livna.org/show_bug.cgi?id=211 for progress. If you have any problems, file a bug at bugzilla.livna.org.

/Peter Backlund (maintainer of the Nvidia package at Livna)

olpe
24th October 2004, 12:38 AM
kernel 2.6.8 and above changed the page structure. This patch allows the fglrx 3.7.6 + regparm patches to work.


Do you know how livna.org has figured this out? Will there be 2 different rpms. Will there be one for 2.6.8 and above, and one for others?

esmartuek
1st November 2004, 09:12 PM
I bought a Pro-Star 8794 (ATI Radeon Mobility 9700 Pro Turbo w/256M) back in march and have attempted to dualboot it with Fedora Core 2. everything runs great but the display.

currently using the 2.6.8 kernel

I've tried all of these instructions on setting it up... but keep running into a problem with the regparm patch... 2 lines come up with errors.
anybody else getting this?

also, seeing as how I haven't touched linux in over 7 years, how do I kill or restart the X server?

toxicshock
2nd November 2004, 03:50 PM
also, seeing as how I haven't touched linux in over 7 years, how do I kill or restart the X server?

ctrl - alt - backspace will restart the X server.

micha
2nd November 2004, 08:40 PM
I bought a Pro-Star 8794 (ATI Radeon Mobility 9700 Pro Turbo w/256M) back in march and have attempted to dualboot it with Fedora Core 2. everything runs great but the display.

currently using the 2.6.8 kernel

I've tried all of these instructions on setting it up... but keep running into a problem with the regparm patch... 2 lines come up with errors.
anybody else getting this?

also, seeing as how I haven't touched linux in over 7 years, how do I kill or restart the X server?
Have a look a this thread:
http://www.fedoraforum.org/forum/showthread.php?t=25801

esmartuek
5th November 2004, 02:04 PM
Have a look a this thread:
http://www.fedoraforum.org/forum/showthread.php?t=25801
thank you, unfortunately I messed up the mouse driver and I'm considering holding off on any fixes until I get FC3 on the 8th.



ctrl - alt - backspace will restart the X server.

ahhhhh... I learn something every day.... well, re-learn it. (now I remember what that key-combo was for... I knew it had to do something.)

I'll let you know the progress in 3 days.

waldotim
26th November 2004, 05:17 PM
Hi there,
someone has posted in this thread that he was able to install the ATI drivers on an x86_64 system... really? AFAIK these drivers are designed for a standard x86 system and the last time I tried to install them on my amd64 box I got an error saying something like "architecture not supported" (was some months ago, ATI driver version 3.7.0 on a Fedora Core 1 x86_64). Is anybody able to confirm this?

regards
Has anyone heard anything new about this? After much fussing around with the kernel and driver source I got to this point:



[root@hamster build_mod]# ./make.sh
ATI module generator V 2.0
==========================
initializing...
cleaning...
patching 'highmem.h'...
skipping patch for 'drmP.h', not needed
skipping patch for 'drm_os_linux.h', not needed
assuming new VMA API since we do have kernel 2.6.x...
doing Makefile based build for kernel 2.6.x and higher
make -C /lib/modules/2.6.9-1.681_FC3/build SUBDIRS=/lib/modules/fglrx/build_mod/2.6.x modules
make[1]: Entering directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9'
CC [M] /lib/modules/fglrx/build_mod/2.6.x/agp3.o
CC [M] /lib/modules/fglrx/build_mod/2.6.x/nvidia-agp.o
CC [M] /lib/modules/fglrx/build_mod/2.6.x/agpgart_be.o
CC [M] /lib/modules/fglrx/build_mod/2.6.x/i7505-agp.o
CC [M] /lib/modules/fglrx/build_mod/2.6.x/firegl_public.o
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function `do_vm_dma_nopage':
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2135: warning: unused variable `kaddr'
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: At top level:
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2528: warning: initialization from incompatible pointer type
LD [M] /lib/modules/fglrx/build_mod/2.6.x/fglrx.o
ld: Relocatable linking with relocations from format elf32-i386 (/lib/modules/fglrx/build_mod/2.6.x/libfglrx_ip.a.GCC3(vm.o)) to format elf64-x86-64 (/lib/modules/fglrx/build_mod/2.6.x/fglrx.o) is not supported
make[2]: *** [/lib/modules/fglrx/build_mod/2.6.x/fglrx.o] Error 1
make[1]: *** [_module_/lib/modules/fglrx/build_mod/2.6.x] Error 2
make[1]: Leaving directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9'
make: *** [kmod_build] Error 2


I don't want to go back to 32 bit mode, but I'd like to be able to play doom3! :(

micha
26th November 2004, 05:30 PM
Has anyone heard anything new about this? After much fussing around with the kernel and driver source I got to this point:



[root@hamster build_mod]# ./make.sh
ATI module generator V 2.0
==========================
initializing...
cleaning...
patching 'highmem.h'...
skipping patch for 'drmP.h', not needed
skipping patch for 'drm_os_linux.h', not needed
assuming new VMA API since we do have kernel 2.6.x...
doing Makefile based build for kernel 2.6.x and higher
make -C /lib/modules/2.6.9-1.681_FC3/build SUBDIRS=/lib/modules/fglrx/build_mod/2.6.x modules
make[1]: Entering directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9'
CC [M] /lib/modules/fglrx/build_mod/2.6.x/agp3.o
CC [M] /lib/modules/fglrx/build_mod/2.6.x/nvidia-agp.o
CC [M] /lib/modules/fglrx/build_mod/2.6.x/agpgart_be.o
CC [M] /lib/modules/fglrx/build_mod/2.6.x/i7505-agp.o
CC [M] /lib/modules/fglrx/build_mod/2.6.x/firegl_public.o
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: In function `do_vm_dma_nopage':
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2135: warning: unused variable `kaddr'
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c: At top level:
/lib/modules/fglrx/build_mod/2.6.x/firegl_public.c:2528: warning: initialization from incompatible pointer type
LD [M] /lib/modules/fglrx/build_mod/2.6.x/fglrx.o
ld: Relocatable linking with relocations from format elf32-i386 (/lib/modules/fglrx/build_mod/2.6.x/libfglrx_ip.a.GCC3(vm.o)) to format elf64-x86-64 (/lib/modules/fglrx/build_mod/2.6.x/fglrx.o) is not supported
make[2]: *** [/lib/modules/fglrx/build_mod/2.6.x/fglrx.o] Error 1
make[1]: *** [_module_/lib/modules/fglrx/build_mod/2.6.x] Error 2
make[1]: Leaving directory `/usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9'
make: *** [kmod_build] Error 2


I don't want to go back to 32 bit mode, but I'd like to be able to play doom3! :(
The first x86-64 version of the ATI driver should be released in the next version of the ATI driver (coming in december, I guess).
As usual, wait and see...

waldotim
26th November 2004, 05:46 PM
grrr... oh, well. I think I'm going to start looking for a 3D card that has fully open drivers. Any ideas?

hydrocell
15th December 2004, 04:31 PM
Hi,

EDITED:

Okay, i managed to finally get the ati drivers to work with my firegl V3100 card, BUT!!! the frame rate is so ridiculously slow that it's just not worth it, the software gl is faster. (i was getting 50fps at full screen with hardware)

if anyone knows how to tweak this that would be appreciated!

FYI i used a fresh FC2 updated the kernel to 2.6.8-1.521 using an rpm from http://www.bo.cnr.it/pub/linux/fedora/

i got both the normal and smp versions and installed both

kernel-2.6.8-1.521.i686.rpm
kernel-smp-2.6.8-1.521.i686.rpm

(make sure to choose the right version from the boot prompter when you reboot after install, for safety reasons just use the normal kernel when you are installing the ati drivers)

then a really quick and easy install of the ati drivers using custom rpm files from
http://www.stanford.edu/~fenn/linux/radeon.shtml

grab the following two files and install them in the order listed here:
http://www.stanford.edu/~fenn/linux...14.1-0.i386.rpm
http://www.stanford.edu/~fenn/linux...14.1-0.i386.rpm

rpm -ivh (those files)

there are also ati drivers for FC3, but no matter what i tried i didn't get them to give me gl support.

after that you have to edit your /etc/X11/config.org file manually, follow the instructions at the stanford site.
(thanks to ~fenn at standford for rpms and instructions)

earlier post:
I also have a Dell Precision 370 with an ATI FireGL V3100 card, but so far haven't been able to get direct rendering to work with FC-2 and FC-3 using several different methods and versions of the drivers. I can get the installs all done fine, no problem. I can edit Xorg.conf etc. But I still get no accleration.