Ati releases new linux driver

[Steltek]

Hmm... then I have to guess. Have you got the patch and grep packages installed? ... All of these should be on a basic install but you never know.

[libb]

Powered by ATI solution:
http://delltalk.us.dell.com/supportf...ssage.id=61184

[Steltek]

Interesting thread. Here's the bit that people here are probably looking for:

you need hack file

/usr/X11R6/lib/modules/drivers/fglrx_drv.o

let it accept non-ATI board, hexedit offset 0x626e: 74 44 --> 90 90

What's really weird is that my HIS card gets accepted with the stock driver even though it is 'only' a 'powered by' card and not an original ATI one. (I can't even get the latter here in Europe)

[mutombo]

thx steltek
thats really
works for me

[Steltek]

Don't thank me, thank libb (for posting the link here) and SAMUEL_LEO (for posting the quoted part on the Dell boards)!

[darktyco]

Compiling the module got the 3D acceleration going, thanks Steltek. UT2k3 runs now, though not really fast enough to seriously play it in Linux. I haven't played games in Linux before though, so I don't know if the low performance is due to the 3d driver, the sound driver, the software, etc. I'm going to try tweaking a bit, but otherwise thanks to ATI for getting these drivers out!

[LightsOut]

Originally posted by libb
Powered by ATI solution:
http://delltalk.us.dell.com/supportf...ssage.id=61184

Thank you!! You are now my personal hero. My 9000 PRO works just fine that to that mod.

Although I'd rather annoyed that I had to do this to get my card working. I wouldn't have tod o anything like this if I had another vendor's cards.....

[Greek Geek]

Hi yall & Steltek,

thanx again for that hunch. I wish it was that too, but....

<snip>
haralambos@haralambos:~$ grep --version
grep (GNU grep) 2.4.2

Copyright 1988, 1992-1999, 2000 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

haralambos@haralambos:~$
<snip>

Dang!

Keep 'em comming guys, I will get these drivers in!

Greek Geek :-)

[mutombo]

check for patch
this is sometimes not included.

if this dont help insert a
set -xvn
at the beginning of the make.sh.
it will give you better debugging output.
remember so remove this when you've found the error.

[Bodeanicus]

Originally posted by Steltek
I don't know the output but you can try checking the output of glxinfo.

If it states 'Direct rendering: yes' the 3D support is up.

If it states 'Direct rendering: no' the 3D support isn't running.

Did you compile and load the fglrx kernel module? If that one isn't loaded you'll get the symptoms you describe namely only 2D support and no 3D. It's sitting in /lib/modules/fglrx in precompiled versions for RedHat (and Mandrake? Can't remember.) ... run make_install.sh there and it'll tell you what to do to compile it for other distros. (For Debian sarge and sid see teufs fix if it fails... it probably also applies to other distros with GCC 2)

Feel free to hit me via ICQ if you can.

i'm having the 2d, no 3d problem. being a total linux newbie, i need to ask how do i load the fglrx module? i'm running redhat 8.0, so i have a module compiled, but how do i install it? thanks.

[darktyco]

Did you reboot yet?

[Greek Geek]

Hi all & mutombo

thanx for the tip re de-bug info. :-)

Filled up a few screens too. It found a syntax error!

I will post only the later part of the screen dump, as I think this is the relivant bit?

<snip>

# check for 240 API compatibility
${CC} -I$linuxincludes $tmp_src_file -c -o $tmp_obj_file_240 &>
./make.sh: line 671: syntax error near unexpected token `&>'
./make.sh: line 671: ` ${CC} -I$linuxincludes $tmp_src_file -c -o $tmp_obj_file_240 &>'
haralambos:/lib/modules/fglrx/build_mod#
<snip>

Um, how to correct?

Greek Geek :-)

[Steltek]

Do you have these lines in your make.sh?

# check for 240 API compatibility
${CC} -I$linuxincludes $tmp_src_file -c -o $tmp_obj_file_240 &> $tmp_log_file_240

My first guess would be that either $tmp_log_file_240 is missing on that line or that it isn't defined. It gets initialized here:

# create a helper source file and try to compile it into an objeckt file
tmp_src_file=tmp_vmasrc.c
tmp_obj_file_240=tmp_vma240.o
tmp_obj_file_253=tmp_vma253.o
tmp_log_file_240=tmp_vma240.log
tmp_log_file_253=tmp_vma253.log
cat > $tmp_src_file <<-begin_end

Something else you might try: Are you compiling as root? If not, do you have write access to that build_mod directory? (Yet another guess)

Update: Here's a hack that might work for you:

First delete everything from "# check for 240 API compatibility" to "# classify and act on results"
Then, just under "# (the check is designed so that exactly one version should succeed"
and before "def_vma_api_version=" insert either

cc_ret_vma_240=1
cc_ret_vma_253=0

(if you have a 2.4 Kernel) or

cc_ret_vma_240=0
cc_ret_vma_253=1

for a 2.5.3-pre1 or later kernel. That should bypass the check and force the script to use whatever you specified. Of course I don't give any warranty whatsoever on this.

[Greek Geek]

Hi All & Steltek,

thanx heaps for going to this trouble of debugging this beastie of a thing!!!! :-)

Oh, & thanx Mr B, for setting up this forum too, else myself in New Zealand, could not get help from a coder with much skill, from way up

I corrected the original line, to your suggestion & that hack worked too.

It almost completes, but then.... I get this error message & I've included something from the "Make.log," as follows.


<snip>
echo ==============================

if [ $OPTIONS_HINTS -ne 0 ]; then

if [ $TERMINAL_HINT -eq 1 ];
then
echo "You must change your working directory to $target_dir"
echo "and then call ./make_install.sh in order to install the built module"
echo ==============================
fi

fi

#EOF
./make.sh: line 1022: unexpected EOF while looking for matching `"'
./make.sh: line 1029: syntax error: unexpected end of file
haralambos:/lib/modules/fglrx/build_mod#
<snip>

Also, the Make.log, has this error message....

<snip>
CC=gcc
cc_version=
ls -l libfglrx_ip.a*
-rwxr-xr-x 1 root src 165908 Nov 22 08:53 libfglrx_ip.a.GCC2.96
-rwxr-xr-x 1 root src 165876 Nov 22 08:53 libfglrx_ip.a.GCC3.2
Error: could not resolve matching ip-library.
<snip>

Isn't the echo stuff, just information, in case something fails? I tried commenting it out, but I can't figure the method that creates it.

Um????

Greek Geek :-)

[Steltek]

Yes, the echo stuff is just for outputting text however you problem states that somewhere a " was opened and never closed (when it reaches the EOF = end of file it complains because only then it is sure that the closing won't happen)

For the other error: It looks like it has problems creating a symlink. To repeat my question: Are you SURE that you have write access to that directory? If you are not 100% sure, please become root (use su) and try to compile the module then. (that might actually fix all of the problems seen before as well)

[ParagonXLS]

I don't get these drivers to work: this is the output when installing the drivers:

rpm -i --force fglrx-glc22-4.2.0-2.4.3.i586.rpm
*** Trying to install a precompiled kernel module.
- creating symlink
- recreating module dependency list
depmod: *** Unresolved symbols in /lib/modules/2.4.18-14/kernel/drivers/char/drm/fglr200.o
- trying a sample load of the kernel module
Warning: loading /lib/modules/2.4.18-14/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
Module fglrx loaded, with warnings
done.
depmod: *** Unresolved symbols in /lib/modules/2.4.18-14/kernel/drivers/char/drm/fglr200.o
 ===
ATI display drivers successfully installed
please run 'fglrxconfig' now
 ===

and after this: /sbin/depmod -e /lib/modules/2.4.18-14/kernel/drivers/char/drm/fglr200.o

I get this:

depmod: *** Unresolved symbols in /lib/modules/2.4.18-14/kernel/drivers/char/drm /fglr200.o
depmod: sys_call_table
/lib/modules/2.4.18-14/kernel/drivers/char/drm/fglr200.o:

# module id=string
# pci module vendor device subvendor subdevice class clas s_mask driver_data
# isapnp module cardvendor carddevice driver_data vendor function ...
# usb module match_flags idVendor idProduct bcdDevice_lo bcdDevice_hi bD eviceClass bDeviceSubClass bDeviceProtocol bInterfaceClass bInterfaceSubClass bI nterfaceProtocol driver_info
# module pattern
# ieee1394 module match_flags vendor_id model_id specifier_id version
# module id

the problem seems to be: "depmod: sys_call_table" how to solve this?

[Steltek]

One question: What Linux distribution are you running?

Anyway: First thing to note ... fglr200.o is NOT the driver module from ATI. The module you need to load is fglrx. (The warning about it tainting the kernel should probably be ignored)

Something you might try first: Reboot. Reading the previous comments I conclude that this seems to do the trick on RedHat.

If all else fails, you could try to compile the module yourself by running make.sh in /lib/modules/fglrx/build.mod (make sure you have the kernel sources installed and configured the same as the currently running kernel otherwise it will fail)

[ParagonXLS]

Well I have RH8, but when to do the reboot. Because i tried it manytimes but without succes. Also what do you mean with "configured the same as the currently running kernel" I never made changes to the kerenl as i am a linux noob but I do think that I have the kernel headers installed.

[Steltek]

Hmm... something else to try: cd to the directory with the fglrx.o module and try 'insmod -f fglrx.o' It might work... (Use lsmod to check that no other Radeon related modules are already loaded ... if they are try getting rid of them with rmmod)

Once you see fglrx as being loaded (check with lsmod) you're ready to go, no matter how many errors you got while loading it.

'Configured like your running kernel': usually the kernels that come with Linux distributions have a different configuration than the default. Thus, just installing and unpacking the kernel sources won't be enough as these sources will then have a different configuration than the kernel you're currently using. There's 2 ways to solve this:

1. configure, compile and install your own kernel.
2. try to get the sources tree configured with the same settings than your kernel. (See the /boot/config* files which should contain the respective configurations for the installed kernels)

[hardcoresidd]

Unreal Tournament 2003 works fine in Linux! Check out the OS forums for some help with UT2003 and linux.