|
i had just download the driver from http://www.schneider-digital.de/html/download_ati.html and had used
rpm -i --force fglrx-glc22-4.3.0-3.2.8.rpm. After installation changed XF86Config manually, then i got Fire GL built-in AGP-support Based on agpgart interface v0.99 (c) Jeff Hartmann agpgart: Maximum main memory to use for agp memory: 816M agpgart: Detected nVidia nForce2 chipset agpgart: Bridge device is in AGP v1/v2 mode agpgart: AGP aperture is 128M @ 0xe0000000 Power management callback for AGP chipset installed [fglrx] AGP detected, AgpState = 0x00000000 (hardware caps of chipset) [fglrx:firegl_unlock] *ERROR* Process 9780 using kernel context 0 [fglrx:drm_ioremapfree] *ERROR* [mappings] Attempt to free NULL pointer from dmesg and (EE) fglrx(0): [agp] unable to acquire AGP, error "xf86_ENOMEM" (EE) fglrx(0): cannot init AGP (WW) fglrx(0): *********************************************** (WW) fglrx(0): * DRI initialization failed! * (WW) fglrx(0): * (maybe driver kernel module missing or bad) * (WW) fglrx(0): * 2D acceleraton available (MMIO) * (WW) fglrx(0): * no 3D acceleration available * (WW) fglrx(0): ********************************************* * again from XF86 log Coud you figure out what's going on here I had kernel2.4.22, redhatlinux9 with xfree86-4.3.0 |
What distro are you running? You should update your profile to include that info ;) (edit: just noticed it's redhat :) ) What does lsmod show?
You may have to recompile your kernel to include DRI support, but I may be wrong. Hopefully someone more knowlegable comes along to help. |
Also, post your monitor and graphic device sections from xf86config-4. You did run 'fglrxconfig' to create this file, right?
I can't really speak for an rpm install. I changed it from an rpm to a .tgz (slack package) and still had to cd around to a few different directories to make/make install a few things. |
What you mean by "had to cd around to a few different directories to make/make install a few things."
lsmod does show fglrx Also, i do have DRI support Can you post your kernel configuration file, so i could compare what's wrong with mine? |
I mean it took several steps to get the driver installed as shown in Shade's instructions. I posted the link on the 1st page, but here it is again: http://www.linuxquestions.org/questi...ghlight=radeon
Here's a link to my kernel config. Better I upload it to my old site than everyone have to scroll 2 miles right here ;) The kernel config is pretty well stock. I haven't gotten around to doing a proper recompile since I re-installed last week (I did a new install to make installing a new Audigy painless). All I really made sure of during this one, is that the nforce support was selected under character devices and that AGPGART was compiled in as well so I could quickly see if this was going to work. I swore I had at least changed the processor from a 486 to an Athlon, but it doesnt appear that I had :scratch: ..... Anyway, give it a look. |
Quote:
|
Quote:
Was struggling with those damn ATi drivers for hours, but I came and found your steps and I'm now enjoying full resolution, hardware accelerated, Linux goodness. :D /pats on back |
You know, I changed back to slack (used it back in the first release) after getting fed up with RedHat and the none standard builds, fedora etc. I had less problems setting up hardware acceleration - actually, was a snap after reading this post - on my Radeon 9000Pro than I ever had with RH9.
Thanks a bunch guys. Great stuff Slack. |
Wow... Glad to see that a lot of people have had success with my instructions. :)
I may put up a more thorough how-to. I've gone through a few more installs since that post, just trying things out differently and acouple of other things I noticed -- agpgart must be compiled as module -- not in the kernel. If compiled in kernel, you will get an odd message from dmesg about the fglrx module having to be inserted prior to any other DRI module -- which I deduced to be agpgart compiled in. To help with the 9600 -- Ati's newest driver released supports it. I believe you may follow the same install procedure as stated before for Slack 9.1 -- rpm2tgz fglrx-2.5.8<whatever>.rpm installpkg fglrx-2.5.8<whatever>.tgz edit XF86Config-4 to use fglrx driver. And there's the difference for the 9600 -- this is just a hunch based on the errors I saw listed in a previous post of this thread: Option "hw_cursor" Try that under the Device section for the vid card. -Shade |
Hi!
Today I installed slackware 9.1 and compiled a 2.4.23 kernel. I've downloaded the latest driver from ATI, and followed Shade's instructions, but got a very strange error: root@darkstar:/lib/modules/fglrx/build_mod# ./make -bash: ./make: No such file or directory root@darkstar:/lib/modules/fglrx/build_mod# ./make.sh ATI module generator V 2.0 ========================== initializing... probing for VMA API version... cleaning... patching 'highmem.h'... skipping patch for 'drmP.h', not needed patching 'drm_os_linux.h'... doing script based build for kernel 2.4.x and similar compiling 'agpgart_be.c'... compiling 'agp3.c'... compiling 'i7505-agp.c'... compiling 'nvidia-agp.c'... compiling 'firegl_public.c'... linking of fglrx kernel module... 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@darkstar:/lib/modules/fglrx/build_mod# cd .. root@darkstar:/lib/modules/fglrx# ./make_install.sh - creating symlink - recreating module dependency list - trying a sample load of the kernel module Warning: loading /lib/modules/2.4.23/kernel/drivers/char/drm/fglrx.o will taint the kernel: non-GPL license - Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY See http://www.tux.org/lkml/#export-tainted for information about tainted modules /lib/modules/2.4.23/kernel/drivers/char/drm/fglrx.o: init_module: Operation not permitted /lib/modules/2.4.23/kernel/drivers/char/drm/fglrx.o: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg /lib/modules/2.4.23/kernel/drivers/char/drm/fglrx.o: insmod /lib/modules/2.4.23/kernel/drivers/char/drm/fglrx.o failed /lib/modules/2.4.23/kernel/drivers/char/drm/fglrx.o: insmod fglrx failed failed. root@darkstar:/lib/modules/fglrx# ??? What the hell is this? :) Unfortunately XFREE 4.3's generic ati and radeon drivers don't work for my system, so the problem is critical, cause vesa suxx |
T-Cat --
Check to see if you maybe compiled agpgart into the kernel. Use dmesg and see what the last line is after you try a modprobe fglrx. If it says something like, fglrx must be loaded prior to any other kernel DRI manager.. then that's your problem ;) Recompile 2.4.23 with agpgart as module. -Shade |
Thx Shade!! :)
Everything went OK after I compiled agpgart and the radeon support from the DRI section as a module |
No problem;)
|
Sorry to bring back this old thread, but I was wondering if anyone could help me out. I followed the steps listed, and checked my kernel config and am positive that AGP support is builtin. I have an nForce2, and was thinking that maybe that PCI Bus ID thing might be the problem. My mobo is an NF7-S by Abit. Also, this line at the bottom of dmesg caught my eye: [fglrx:firegl_unlock] *ERROR* Process 16747 using kernel context 0. Help is much appreciated.
|
it does on my machine too. it doesn't says that when my system boots up. but after i play tux racer, there is several line which was about it.
maybe upgrade kernel to 2.6.1? i will stay with 2.4.23. just want a kernel compiling break!! |
| All times are GMT -5. The time now is 06:26 PM. |