uugh... ati...

thelastknowngod · 02-01-2007, 07:53 PM

note to self... buy an nvidia card next time...

ok so im trying to install the ati drivers and its giving me a hell of a time... ive got it installed and i have the basic support for my 1680x1050 monitor but i want to give beryl a shot and cannot get direct rendering running.

i ran the installer from ati and everything was fine... brought my desktop right up to the right resolution. then on the "this is how i do everything" thread i followed the instructions, basically. when i ran the sh make.sh set it was referencing the wrong kernel source so i had to follow these instructions to get it looking in the right place...

Post #8
http://www.linuxquestions.org/questi...62#post2451662

so now back to the original howto.. i run sh make.sh and it works fine. it says to cd .. and run sh make_install.sh however, that says...

Code:

- recreating module dependency list
- trying a sample load of the kernel modules
FATAL: Error inserting fglrx (/lib/modules/2.6.17.13-smp/kernel/drivers/char/drm/fglrx.ko): Invalid module format
failed.

once again... not sure where to go from here. haha

please let me know if you have any idea what im talking about.

oh and if it matters... im using a PCI-Express x300se and, obviously, Slackware 11.

swampdog2002 · 02-02-2007, 03:47 PM

I've run into a similar situation in the past with the dazuko module. After reading an extensive FAQ, I was able to find the solution, which was that another module needed to be loaded prior to inserting and probing for the dazuko module. It seems sort of misleading with the "incorrect module format" error, when .ko is correct for a 2.6X kernel, and .o for a 2.4x kernel. Perhaps there is also something with the fglrx.ko module that needs to be loaded prior to inserting it. If this were AGP, I would suggest looking for agpgart, but PCI xpress I am unsure. Of course, I believe that ATI has its own implementation for AGP (for these types of bus cards), and disables agpgart if I remember correctly.

And yes, it does seem somewhat more straightforward with NVIDIA cards, but since you have the ATI, hopefully you can come to some sort of resolve shortly.

thelastknowngod · 02-02-2007, 05:06 PM

here is the relevent section of my xorg.conf. something about it just doesnt look right to me but im not exactly sure what should change.

Code:

Section "Monitor"
	Identifier   "My Monitor"
	HorizSync    31.5 - 50.0
	VertRefresh  40.0 - 90.0
EndSection

Section "Monitor"
	Identifier   "aticonfig-Monitor[0]"
	Option	    "VendorName" "ATI Proprietary Driver"
	Option	    "ModelName" "Generic Autodetecting Monitor"
	Option	    "DPMS" "true"
EndSection

Section "Device"

	Identifier  "VESA Framebuffer"
	Driver      "vesa"
EndSection

Section "Device"
	Identifier  "aticonfig-Device[0]"
	Driver      "fglrx"
EndSection

Section "Screen"

	Identifier "Screen 1"
	Device     "VESA Framebuffer"
	Monitor    "My Monitor"
	DefaultDepth     24
	SubSection "Display"
		Depth     8
		Modes    "1024x768" "800x600" "640x480"
	EndSubSection
	SubSection "Display"
		Depth     16
		Modes    "1024x768" "800x600" "640x480"
	EndSubSection
	SubSection "Display"
		Depth     24
		Modes    "1024x768" "800x600" "640x480"
	EndSubSection
	SubSection "Display"
		Depth     32
		Modes    "1024x768" "800x600" "640x480"
	EndSubSection
EndSection

Section "Screen"
	Identifier "aticonfig-Screen[0]"
	Device     "aticonfig-Device[0]"
	Monitor    "aticonfig-Monitor[0]"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection

thelastknowngod · 02-02-2007, 10:46 PM

heres an update if anyone can make sense of this.... i run

glxinfo | grep rendering

and it returns

Code:

Xlib:  extension "XFree86-DRI" missing on display ":0.0".
direct rendering: No

any ideas?

hyphae · 02-03-2007, 01:32 AM

Try not to down ATI too much, they're still great folks (i think). I encountered the EXACT same error message as you have now. I read through some forums of historyabout the issue, and a lot of users who report ATI cards working well were using earlier kernels. I do believe 2.6.12 or 13 or maybe lateest 15 or 16 will work with ATI fine. In order to install the ATI drivers, there are these patches you gotta get frist. However, when I foudnt he patches, they weren't for the kernel version I had -- what you have now. Well, I'm getting rdy to go back a lil bit to 2.6.12.2 because I'm pretty sure the ATI will work with it, and that's the version I see of the patches. THe main thing that only really matters to me with the kernel is that highmem.o benefit. Good luck.. We'll Both Need It.

thelastknowngod · 02-03-2007, 08:13 AM

what would i look for to find the patches? currently im running 2.6.17.13-smp on slack 11. didnt know if you came across it in the past... thanks for the help.

H_TeXMeX_H · 02-03-2007, 01:47 PM

Quote:

Originally Posted by hyphae

Try not to down ATI too much, they're still great folks (i think).

Oh yeah, they are great ... at making POS hardware and software for all platforms, but especially for *nix.

diskoe · 02-04-2007, 10:19 PM

I have always used ATI video cards on my Slackware boxes for years and years without any problems.

I use Slackware 11, 2.6.18.

1. Make sure the radeon kernel module is loaded

Code:

# modprobe radeon

You could put the above in /etc/rc.d/rc.modules

2. Make sure you have the following in the /etc/X11/xorg.conf

Code:

# This loads the GLX module
    Load       "glx"
# This loads the DRI module
    Load       "dri"

and

Code:

Section "DRI"
   Mode 0666
EndSection

silencestone · 02-13-2007, 09:38 PM

Quote:

Originally Posted by diskoe

1. Make sure the radeon kernel module is loaded

Code:

# modprobe radeon

You could put the above in /etc/rc.d/rc.modules

Actually, just add "radeon" to the /etc/X11/xorg.conf, in the Device section:

Code:

Section "Device"
	Identifier  "aticonfig-Device[0]"
	Driver      "radeon"
EndSection

...like that! And restart X.

Blitzkreig75 · 02-14-2007, 09:50 PM

Can the above be done from the command line you get when booting into Slack, before the X launch?

I'm using an x800XL and having display problems, too.

go to run X and get a black screen with the little 'x' icon for my mouse.....

H_TeXMeX_H · 02-14-2007, 10:46 PM

Quote:

Originally Posted by Blitzkreig75

Can the above be done from the command line you get when booting into Slack, before the X launch?

of course ... in fact, that's the best time to do it. Use vim or nano or pico. (I recommend nano or pico)

Blitzkreig75 · 02-15-2007, 12:08 AM

Well, all I get with that command is "Permission denied".....geez....

I'm going to start my own thread sos not to hijack this one.

H_TeXMeX_H · 02-15-2007, 01:07 AM

remember to be root to edit it