LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (http://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   Unabale to use XF86 4.3.0 with ATI Radeon 9600XT/Pro (http://www.linuxquestions.org/questions/linux-hardware-18/unabale-to-use-xf86-4-3-0-with-ati-radeon-9600xt-pro-129900/)

tarballedtux 12-29-2003 06:35 PM

Unable to use XF86 4.3.0 with ATI Radeon 9600XT/Pro
 
I'm having trouble getting my ATI Radeon 9600XT to work with Slackware 8.1 (but with some 9.1 updates like XF86 4.3.0). THis is an official "Built by ATI card" I using kernel 2.4.23 compiled from source. AGPGART driver is a module not yet loaded(actually unloadable as of now) and the ATI driver that came with the kernel compiled in. I've tried these drivers. ATI's driver from the website (even the newest one). the driver included with XF86, and the Schneider's Digital driver. All to no avail. Here is the output of "X -verbose": http://tarballedtux.tripod.com/Xoutput.txt
and the my XF86Config file: http://tarballedtux.tripod.com/XF86Config.txt
I've tried both BusID "PCI:1:0:0" and BusID "PCI:1:0:1" in XF86Config.
And lspci:

00:00.0 Host bridge: Intel Corp.: Unknown device 2560 (rev 01)
Subsystem: Intel Corp.: Unknown device 2560
Flags: bus master, fast devsel, latency 0
Memory at f0000000 (32-bit, prefetchable) [size=128M]
Capabilities: [e4] #09 [0105]
Capabilities: [a0] AGP version 2.0

00:01.0 PCI bridge: Intel Corp.: Unknown device 2561 (rev 01) (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, fast devsel, latency 32
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: ff800000-ff8fffff
Prefetchable memory behind bridge: ae900000-ee9fffff

00:1d.0 USB Controller: Intel Corp.: Unknown device 24c2 (rev 01) (prog-if 00 [UHCI])
Subsystem: Intel Corp.: Unknown device 5247
Flags: bus master, medium devsel, latency 0, IRQ 11
I/O ports at e800 [size=32]

00:1d.1 USB Controller: Intel Corp.: Unknown device 24c4 (rev 01) (prog-if 00 [UHCI])
Subsystem: Intel Corp.: Unknown device 5247
Flags: bus master, medium devsel, latency 0, IRQ 5
I/O ports at e880 [size=32]

00:1d.2 USB Controller: Intel Corp.: Unknown device 24c7 (rev 01) (prog-if 00 [UHCI])
Subsystem: Intel Corp.: Unknown device 5247
Flags: bus master, medium devsel, latency 0, IRQ 9
I/O ports at ec00 [size=32]

00:1d.7 USB Controller: Intel Corp.: Unknown device 24cd (rev 01) (prog-if 20 [EHCI])
Subsystem: Intel Corp.: Unknown device 5247
Flags: bus master, medium devsel, latency 0, IRQ 10
Memory at ffaffc00 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] #0a [2080]

00:1e.0 PCI bridge: Intel Corp. 82801BA/CA PCI Bridge (rev 81) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: ff900000-ff9fffff
Prefetchable memory behind bridge: eea00000-eeafffff

00:1f.0 ISA bridge: Intel Corp.: Unknown device 24c0 (rev 01)
Flags: bus master, medium devsel, latency 0

00:1f.1 IDE interface: Intel Corp.: Unknown device 24cb (rev 01) (prog-if 8a [Master SecP PriP])
Subsystem: Intel Corp.: Unknown device 5247
Flags: bus master, medium devsel, latency 0, IRQ 9
I/O ports at <unassigned>
I/O ports at <unassigned>
I/O ports at <unassigned>
I/O ports at <unassigned>
I/O ports at ffa0 [size=16]
Memory at 20000000 (32-bit, non-prefetchable) [size=1K]

00:1f.3 SMBus: Intel Corp.: Unknown device 24c3 (rev 01)
Subsystem: Intel Corp.: Unknown device 5247
Flags: medium devsel, IRQ 3
I/O ports at e480 [size=32]

01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 4152 (prog-if 00 [VGA])
Subsystem: ATI Technologies Inc: Unknown device 0002
Flags: bus master, 66Mhz, medium devsel, latency 255, IRQ 11
Memory at d0000000 (32-bit, prefetchable) [size=256M]
I/O ports at c800 [size=256]
Memory at ff8f0000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at ff8c0000 [disabled] [size=128K]
Capabilities: [58] AGP version 2.0
Capabilities: [50] Power Management version 2

01:00.1 Display controller: ATI Technologies Inc: Unknown device 4172
Subsystem: ATI Technologies Inc: Unknown device 0003
Flags: bus master, 66Mhz, medium devsel, latency 32
Memory at c0000000 (32-bit, prefetchable) [size=256M]
Memory at ff8e0000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [50] Power Management version 2

02:03.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 04)
Subsystem: Creative Labs CT4850 SBLive! Value
Flags: bus master, medium devsel, latency 32, IRQ 5
I/O ports at d880 [size=32]
Capabilities: [dc] Power Management version 1

02:03.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 01)
Subsystem: Creative Labs Gameport Joystick
Flags: bus master, medium devsel, latency 32
I/O ports at dc00 [size=8]
Capabilities: [dc] Power Management version 1

02:08.0 Ethernet controller: Intel Corp.: Unknown device 1039 (rev 81)
Subsystem: Intel Corp.: Unknown device 300e
Flags: bus master, medium devsel, latency 32, IRQ 11
Memory at ff9ff000 (32-bit, non-prefetchable) [size=4K]
I/O ports at d800 [size=64]
Capabilities: [dc] Power Management version 2


I'm trying to get the best 3d support possible out of this card.
If I left anything important out I'll post it.

--Thanks in advance

tricky_linux 12-29-2003 09:42 PM

i think you should still need to download a driver from www.ati.com.
i got my radeon 9600 pro working after installing the driver on 2.4.23.

tarballedtux 12-29-2003 10:27 PM

Re: Unable to use XF86 4.3.0 with ATI Radeon 9600XT/Pro
 
Quote:

Originally posted by tarballedtux
I've tried these drivers. ATI's driver from the website (even the newest one). the driver included with XF86, and the Schneider's Digital driver.

UnTamed 12-30-2003 09:18 AM

First of all you still load a nVidia glx module
Quote:

(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.4191
I would suggest you uninstall any leftovers from previous setups and re-installing your xfree pkg.

If you installed the driver files manually and no errors came up when you built and installed the drm module, you can just recopy the /usr folder from the driver onto you / filesystem

If you built a pkg from the original rpm and installed as such, you'll probably need to reinstall the driver pkg you created, rebuild and reinstall the module, for /lib/modules/fglrx will be overwritten by such procedure.

Also if you want the best performance you might prefer to use the older 3.2.8 driver, I don't have much good to say about the new 3.7.0.

tarballedtux 12-30-2003 12:57 PM

Ok, I uninstalled these packages base XF86 4.2.0 and base 4.3.0. Plus the these packages for both versions: XF86-devel, XF86 fonts(100dpi,misc, and scale)

Then I reinstalled the base package the developer and those 3 font packages. All the new packages were 4.3.0. I did this all using pkgtool.
I have a feeling this nvidia stuff is from the ATI driver. If you notice in /lib/modules/fglrx/ there is a ref to nvidia, even when you build the module it says something about nvidia. Which confuses me a little.

I got the RPM from ATI's site, used rpm2tgz and then installed it. Did the ./make.sh and ./make.install. Used fglrxconfig to get the XF86Config file I have above. After doing all that I still get the same error as before.

--Thanks in advance

trey85stang 12-30-2003 02:33 PM

edit the XF86Config-4 file... and comment out the busid with a # sign in front of it.

trey85stang 12-30-2003 02:35 PM

also post up the output of:
dmesg | grep agp
&
dmesg | fglrx

tarballedtux 12-30-2003 03:17 PM

I commented out the BusID.

dmesg | grep fglrx:

[fglrx] Maximum main memory to use for locked dma buffers: 431 MBytes.
[fglrx] module loaded - fglrx 3.7.0 [Dec 18 2003] on minor 0
[fglrx] module unloaded - fglrx 3.7.0 [Dec 18 2003] on minor 0
[fglrx] Maximum main memory to use for locked dma buffers: 431 MBytes.
[fglrx] module loaded - fglrx 3.2.8 [Sep 21 2003] on minor 0
[fglrx] module unloaded - fglrx 3.2.8 [Sep 21 2003] on minor 0
[fglrx] Maximum main memory to use for locked dma buffers: 431 MBytes.
[fglrx] module loaded - fglrx 3.2.8 [Sep 21 2003] on minor 0
[fglrx] module unloaded - fglrx 3.2.8 [Sep 21 2003] on minor 0
[fglrx] Maximum main memory to use for locked dma buffers: 431 MBytes.
[fglrx] module loaded - fglrx 3.2.8 [Sep 21 2003] on minor 0


dmesg | grep agp:

agpgart: Maximum main memory to use for agp memory: 439M
agpgart: unsupported bridge
agpgart: no supported devices found.


Still errors:

Using authority file /root/.Xauthority
Writing authority file /root/.Xauthority


XFree86 Version 4.3.0
Release Date: 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.22 i686 [ELF]
Build Date: 16 September 2003
Before reporting problems, check http://www.XFree86.Org/
to make sure that you have the latest version.
Module Loader present
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/XFree86.0.log", Time: Tue Dec 30 10:16:19 2003
(==) Using config file: "/etc/X11/XF86Config"
(WW) fglrx: No matching Device section for instance (BusID PCI:1:0:1) found
Symbol __glXActiveScreens from module /usr/X11R6/lib/modules/extensions/libdri.a is unresolved!
Symbol __glXActiveScreens from module /usr/X11R6/lib/modules/extensions/libdri.a is unresolved!
Symbol __glXActiveScreens from module /usr/X11R6/lib/modules/drivers/fglrx_drv.o is unresolved!
(II) [GLX]: Initializing GLX extension

*** If unresolved symbols were reported above, they might not
*** be the reason for the server aborting.

Fatal server error:
Caught signal 11. Server aborting


When reporting a problem related to a server crash, please send
the full server output, not just the last messages.
This can be found in the log file "/var/log/XFree86.0.log".
Please report problems to xfree86@xfree86.org.

XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.



--Thanks in advance

UnTamed 12-30-2003 03:31 PM

The only reference to nVidia in ATI's driver would be in regards to nForce agpgart.
Here's my glx module,
Quote:

Module glx: vendor="The XFree86 Project"
compiled for 4.3.0.1, module version = 1.0.0
ABI class: XFree86 Server Extension, version 0.2
Your module version = 1.0.4191 matches exactly driver 1.0.4191 in nVidia's driver archive, wouldn't you think it odd?
...but if you say there's no nV graphics driver installed, I wonder where this can come from.

trey85stang 12-30-2003 03:57 PM

what happens with this command??

modprobe agpgart agp_try_unsupported=1

tarballedtux 12-30-2003 04:11 PM

Ok UnTamed maybe I should have mentioned this but I was before this using an NVidia graphics card and driver. So I would understand where it came from but I still don't see a file lying around the which tells where it's getting loaded from. Weirdly enough in my build_mod dir I have a file called nvidia_agp.c

modprobe agpgart agp_try_unsupported=1

/lib/modules/2.4.23/kernel/drivers/char/agp/agpgart.o: init_module: No such device
/lib/modules/2.4.23/kernel/drivers/char/agp/agpgart.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/agp/agpgart.o: insmod /lib/modules/2.4.23/kernel/drivers/char/agp/agpgart.o failed
/lib/modules/2.4.23/kernel/drivers/char/agp/agpgart.o: insmod agpgart failed



So is it an agpgart problem? agpgart was loading before on my previous kernel. I just upgraded to 2.4.23 to maybe fix the problem.

--tarballedtux

trey85stang 12-30-2003 04:16 PM

odd.. how about lsmod.
and could you host your rc.modules file as well?

trey85stang 12-30-2003 04:17 PM

yes i think it is an agp issue... fglrx cannot load unless agp is loaded... you are using the external agpgart in the XF86Config-4 (one of the last prompts in fglrxconfig)

tarballedtux 12-30-2003 05:32 PM


#!/bin/sh

### Update module dependencies ###
# If /usr is mounted and we have 'find', we can try to take a shortcut:
RELEASE=`uname -r`
if [ -e /lib/modules/$RELEASE/modules.dep -a /lib/modules/$RELEASE/modules.dep -nt /etc/modules.conf ]; then
NEWMODS="`/usr/bin/find /lib/modules/$RELEASE -type f -newer /lib/modules/$RELEASE/modules.dep`"
# Only rebuild dependencies if new module(s) are found:
if [ ! "" = "$NEWMODS" ]; then
echo "New kernel modules have been found in /lib/modules/$RELEASE/:"
echo "$NEWMODS"
echo "Updating module dependencies for Linux $RELEASE:"
/sbin/depmod -a
else
echo "Module dependencies up to date (no new kernel modules found)."
fi
else # we don't have find, or there is no existing modules.dep, or it is out of date.
echo "Updating module dependencies for Linux $RELEASE:"
/sbin/depmod -A
fi

### USB Host Controllers:
# Universal Host Controller Interface (Intel standard):
#/sbin/modprobe usb-uhci
# Universal Host Controller Interface (alternate JE):
#/sbin/modprobe uhci
# Open Host Controller Interface (Compaq/Microsoft/National standard):
#/sbin/modprobe usb-ohci

# Sound
/sbin/modprobe soundcore

#/sbin/modprobe sound
#/sbin/modprobe ac97_codec
#/sbin/modprobe i810_audio

if [ -x /etc/rc.d/rc.netdevice ]; then
. /etc/rc.d/rc.netdevice
fi

# IDE-SCSI Emulation
/sbin/modprobe ide-scsi

# Video Card
/sbin/modprobe agpgart
/sbin/modprobe fglrx

#Network

/sbin/modprobe eepro100




lsmod:

fglrx 165384 0 (unused)
eepro100 18612 1
mii 2304 0 [eepro100]
soundcore 3268 0 (unused)
ntfs 48768 2 (autoclean)



As of now I'm using the internal AGPgart as stated in XF86Config. If you think I should use the external one then I guess I have to fix it. Either by going back to me previous kernel where it worked or fixing the new 2.4.23. Which do you think is better? Or do you kbow what the problem is with the current AGPGART with 2.4.23

trey85stang 12-30-2003 05:40 PM

Quote:

Originally posted by tarballedtux

As of now I'm using the internal AGPgart as stated in XF86Config. If you think I should use the external one then I guess I have to fix it. Either by going back to me previous kernel where it worked or fixing the new 2.4.23. Which do you think is better? Or do you kbow what the problem is with the current AGPGART with 2.4.23

Ive never been able to get internal AGP to work.. I have always used the module. So im unsure of what to trouble shoot.

Most others i beleive use the module as well? I bet yours will work well if you use the module though.


All times are GMT -5. The time now is 09:38 AM.