Installing ATI Drivers on SW9

Saffsd · 09-07-2003, 09:31 AM

Hey all. Now that my kernels are up and running, I've got another problem. I'd like to install linux drivers for my radeon 8500. I got them off the ATI site as an .rpm, and when i try to install it i get the following:

Code:

name
fglrx-glc22
summary
XFree86 display driver for the ATI graphics accelerators 
version
4.3.0 -3.2.5 
group
Servers 
size
11076013 
description
Display driver files for the ATI Radeon 8500, 9700, Mobility M9 and the FireGL 8700/8800, E1, Z1/X1 graphics accelerators. This package provides 2D display drivers, precompiled kernel modules, kernel module build environment, control panel source coude and hardware accellerated OpenGL. 
unsatisfied dependencies
/bin/sh , /bin/sh , /bin/sh , /bin/sh , ld-linux.so.2 , libc.so.6 , libdl.so.2 , libICE.so.6 , libm.so.6 , libpthread.so.0 , libSM.so.6 , libX11.so.6 , libXaw.so.7 , libXext.so.6 , libXmu.so.6 , libXpm.so.4 , libXt.so.6 , /bin/bash , libc.so.6(GLIBC_2.0) , libc.so.6(GLIBC_2.1) , libc.so.6(GLIBC_2.1.3) , libdl.so.2(GLIBC_2.0) , libdl.so.2(GLIBC_2.1) , libm.so.6(GLIBC_2.0) , libpthread.so.0(GLIBC_2.0) 
depends
/bin/sh , /bin/sh , /bin/sh , /bin/sh , rpmlib(PayloadFilesHavePrefix) (<= 4.0-1), rpmlib(CompressedFileNames) (<= 3.0.4-1), ld-linux.so.2 , libc.so.6 , libdl.so.2 , libfglrx_gamma.so.1 , libGL.so.1 , libICE.so.6 , libm.so.6 , libpthread.so.0 , libSM.so.6 , libX11.so.6 , libXaw.so.7 , libXext.so.6 , libXmu.so.6 , libXpm.so.4 , libXt.so.6 , /bin/bash , libc.so.6(GLIBC_2.0) , libc.so.6(GLIBC_2.1) , libc.so.6(GLIBC_2.1.3) , libdl.so.2(GLIBC_2.0) , libdl.so.2(GLIBC_2.1) , libm.so.6(GLIBC_2.0) , libpthread.so.0(GLIBC_2.0) 
provides
fglrx_dri.so, libfglrx_gamma.so.1, libGL.so.1, fglrx-glc22
install time
Sun 07 Sep 2003 10:11:29 PM SGT 
distribution
(none) 
vendor
(none) 
packager
(none) 
build-time
Wed 06 Aug 2003 11:08:51 PM SGT

How do I... erm... satisfy these dependencies? Thanks!

Tinkster · 09-07-2003, 02:04 PM

Firstly, you try to avoid RPMs ... secondly,
if you get an RPM you try to convert the
package to a tgz. As for the dependencies:
you'll have to check yourself :}

Cheers,
Tink

Saffsd · 09-07-2003, 10:16 PM

Quote:

Originally posted by Tinkster
Firstly, you try to avoid RPMs ... secondly,
if you get an RPM you try to convert the
package to a tgz. As for the dependencies:
you'll have to check yourself :}

Cheers,
Tink

Haha. Oh shit. Well I dont really have a choice RPM wise. Ive used KPackage to force it to install, but I can't seem to find any of the dependencies it wants... I have glibc package from slackware installed for example, but its still listing many glibc files as missing?

How would i go about converting to tgz anyhow?

galalleni · 09-08-2003, 12:37 AM

The kernel includes the latest drivers from the DRI project, but ATI only distributes their drivers in binary rpm format - when installing drivers in rpm format they are built for a specific kernel (in this case the Redhat kernel) and libc (from the redhat distro); sorry to burst your bubble. If you want to email them asking for a src.rpm I'm sure they could work something out, using a src.rpm you can do "rpm --rebuild <src.rpm>" and the driver will be rebuilt for your kernel. If you have a kernel < 2.4.22 you can try to recompile your kernel (which has the latest drivers) - or use the DRI project drivers from http://dri.sourceforge.net/.

Note: The drivers from ATI are considered closed source, and because of this repackaging for different distro's is hampered. The DRI project ATI drivers work just as well, if not better than, the ATI drivers (these are included in the bare.i kernel).

If you use the source DRI drivers, remember to cd to the source directory and "./configure && make && make install".

ramen · 09-08-2003, 02:52 PM

i get this with the new 3.2.5 ati or Schnieder drivers

Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected Via Apollo Pro KT400 chipset
agpgart: unable to determine aperture size.
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected Via Apollo Pro KT400 chipset
agpgart: unable to determine aperture size.
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected Via Apollo Pro KT400 chipset
agpgart: unable to determine aperture size.
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected Via Apollo Pro KT400 chipset
agpgart: unable to determine aperture size.
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected Via Apollo Pro KT400 chipset
agpgart: unable to determine aperture size.
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected Via Apollo Pro KT400 chipset
agpgart: unable to determine aperture size.
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected Via Apollo Pro KT400 chipset
agpgart: unable to determine aperture size.
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected Via Apollo Pro KT400 chipset
agpgart: unable to determine aperture size.
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected Via Apollo Pro KT400 chipset
agpgart: unable to determine aperture size.
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected Via Apollo Pro KT400 chipset
agpgart: unable to determine aperture size.
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected Via Apollo Pro KT400 chipset
agpgart: unable to determine aperture size.
[fglrx] Maximum main memory to use for locked dma buffers: 431 MBytes.
[fglrx] module loaded - fglrx 3.2.5 [Aug 6 2003] on minor 0
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected Via Apollo Pro KT400 chipset
agpgart: unable to determine aperture size.
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected Via Apollo Pro KT400 chipset
agpgart: unable to determine aperture size.
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected Via Apollo Pro KT400 chipset
agpgart: unable to determine aperture size.
Fire GL built-in AGP-support
Based on agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 439M
agpgart: Detected a Via Apollo KT400 chipset in AGP v2 compat mode at 00:00.0
agpgart: Detected Via Apollo KT400 chipset
agpgart: unable to determine aperture size.
[fglrx:firegl_unlock] *ERROR* Process 773 using kernel context 0

display: :0.0 screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.3 Mesa 4.0.4

and i can only get the 3.2.0 drivers 2 work once i have used the fglrx-glc22-4.2.0-2.5.1.i586-kt400agp3.patch. Getting peeved off with ATI now i am seriously thinking about putting my gf4 440mx back in, not that i want 2. I suspect its something 2 do with this again agpgart: Detected a Via Apollo KT400 chipset in AGP v2 compat mode at 00:00.0, as my mobo wont let me change my agp from x8 and i can't change aperture size either, oh and my mobo is agp v3 not 2 as it states there, and Asus say i need a new bios and when 1 is available they will mail me

I will not hold my breath

devtek · 09-08-2003, 03:50 PM

Don't know if i can be of any help, but i installed my 9600 a couple of days ago, i did like this...

downloaded the drivers from ATI.com
converted the .rpm to tgz with "rpm2tgz"
"installpkg <name>.tgz"
"fglrxconfig"
a program guided me through the setup...
REBOOT

Again, I'm noob

Saffsd · 09-09-2003, 02:41 AM

Quote:

Originally posted by galalleni
The kernel includes the latest drivers from the DRI project, but ATI only distributes their drivers in binary rpm format - when installing drivers in rpm format they are built for a specific kernel (in this case the Redhat kernel) and libc (from the redhat distro); sorry to burst your bubble. If you want to email them asking for a src.rpm I'm sure they could work something out, using a src.rpm you can do "rpm --rebuild <src.rpm>" and the driver will be rebuilt for your kernel. If you have a kernel < 2.4.22 you can try to recompile your kernel (which has the latest drivers) - or use the DRI project drivers from http://dri.sourceforge.net/.

Note: The drivers from ATI are considered closed source, and because of this repackaging for different distro's is hampered. The DRI project ATI drivers work just as well, if not better than, the ATI drivers (these are included in the bare.i kernel).

If you use the source DRI drivers, remember to cd to the source directory and "./configure && make && make install".

Trying DRI drivers now. Thank you!

Locura · 09-09-2003, 02:58 AM

If you are using Slack 9, it comes with XFree 4.3.0, which has support for almost all Radeon cards. I have a 9000 Pro, and this is all I have in the Device section for my video card, in the XF86Config file:

Code:

Section "Device"
    Identifier  "Radeon"
    Driver      "radeon"
EndSection

Then in the Screen section, I just have the line:

Code:

Device      "Radeon"

You don't need anything fancy, you don't need the fglrx drivers, you can still enable DRI with no problem. It's actually quite easy to get working.

Saffsd · 09-09-2003, 03:16 AM

Well I got the latest drivers from DRI and the work a charm. Do I now have fully 2d/3d acceleration?

Obscure · 09-09-2003, 06:11 AM

You can control typing glxinfo and control if it shows DirectRendering:Yes
If not add in yr /etc/X11/XF86config file this lines:
In Section "Module" add/decomment:
Load "dri"
Load "drm"

And at the end of file add/decomment:
Section "DRI"
Mode 0666
EndSection

You can control yr /var/log/XFree86.log.0 (or similar) for checking in details....
You can also test typing glxgears for a benchmark...

I got a Radeon 9100 and DRI drivers works very fine...
Only 1thing...if you have a digital LCD monitor download the lastest version from dri site because the drivers distribuited with Xfree86 are an old version that doesn't support DVI
Bye

Obscure · 09-09-2003, 07:18 AM

Maybe can help:

http://www.tldp.org/HOWTO/XFree86-R200/index.html