FC5 2.6.16-1.2111 Livna ATI drivers - stuck on Mesa

Cyaegha · #1 20th May 2006, 05:19 AM

Hi,

Has anyone actually got ATI 3D acceleration working in FC5 2.6.16-1.2111? I followed the instructions to install from livna. It all seemed to go ok, I have SElinux disabled, my Xorg.conf points to fglrx.
Xorg.0.log says

Code:

(II) LoadModule: "fglrx"
(II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
... Then some version info.

When I type fglrxinfo it tells me it is still using Mesa.

I can't use the installer from ATI as it doesn't supprt Xorg7.0.0

Any ideas?
What can I supply from my install to help you to help me?

fhubers · #2 23rd May 2006, 12:34 AM

Did you follow all the instructions at http://www.fedorafaq.org/#radeon especially the part about doing an init 3 and ati-fglrx-config-display enable?

Iron_Mike · #3 23rd May 2006, 02:17 AM

Quote:

Originally Posted by Cyaegha

Hi,

Has anyone actually got ATI 3D acceleration working in FC5 2.6.16-1.2111? I followed the instructions to install from livna. It all seemed to go ok, I have SElinux disabled, my Xorg.conf points to fglrx.
Xorg.0.log says

Code:

(II) LoadModule: "fglrx"
(II) Loading /usr/lib/xorg/modules/drivers/fglrx_drv.so
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
... Then some version info.

When I type fglrxinfo it tells me it is still using Mesa.

I can't use the installer from ATI as it doesn't supprt Xorg7.0.0

Any ideas?
What can I supply from my install to help you to help me?

su - to root and type aticonfig --initial

then reboot and check again.....

fhubers · #4 23rd May 2006, 01:25 PM

Also - use livna installer (http://rpm.livna.org) don't use the ATI installer - though there is a way to force it to think you are using the old version of Xorg.

Cyaegha · #5 23rd May 2006, 01:49 PM

Yeah I did use the livna installer. I tried the ATI one but got stuck when I found it would not work on Xorg7.

I did the init 3 ati-fglrx-config-display enable init 5 thing and I am still getting the same thing.
ati-fglrx-config-display did not return any errors.

aticonfig --initial returned the following.

Code:

[root@localhost aparker]# aticonfig --initial
Found fglrx primary device section
Using /etc/X11/xorg.conf
Saved back-up to /etc/X11/xorg.conf.fglrx-3

Here is my Xorg.conf just in case.

Code:

# XFree86 4 configuration created by pyxf86config

Section "ServerLayout"
	Identifier     "Default Layout"
	Screen      0  "Screen0" 0 0
	InputDevice    "Keyboard0" "CoreKeyboard"
	InputDevice    "Synaptics" "CorePointer"
	InputDevice    "Mouse0" "AlwaysCore"
EndSection

Section "Files"

# Multiple FontPath entries are allowed (they are concatenated together)
# By default, a font server independent of the X server is
# used to render fonts.
	FontPath     "unix/:7100"
EndSection

Section "Module"
	Load  "dbe"
	Load  "extmod"
	Load  "fbdevhw"
	Load  "glx"
	Load  "record"
	Load  "freetype"
	Load  "type1"
	Load  "synaptics"
	Load  "dri"
EndSection

Section "InputDevice"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#	Option	"Xleds"		"1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
#	Option	"XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#	Option	"XkbModel"	"pc102"
# If you have a US Microsoft Natural keyboard, you can use:
#	Option	"XkbModel"	"microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#	Option	"XkbLayout"	"de"
# or:
#	Option	"XkbLayout"	"de"
#	Option	"XkbVariant"	"nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#	Option	"XkbOptions"	"ctrl:swapcaps"
# Or if you just want both to be control, use:
#	Option	"XkbOptions"	"ctrl:nocaps"
#
	Identifier  "Keyboard0"
	Driver      "kbd"
	Option	    "XkbModel" "pc105"
	Option	    "XkbLayout" "us"
EndSection

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Protocol" "IMPS/2"
	Option	    "Device" "/dev/input/mice"
	Option	    "ZAxisMapping" "4 5"
	Option	    "Emulate3Buttons" "yes"
EndSection

Section "InputDevice"
	Identifier  "Synaptics"
	Driver      "synaptics"
	Option	    "Device" "/dev/input/mice"
	Option	    "Protocol" "auto-dev"
	Option	    "Emulate3Buttons" "yes"
EndSection

Section "Monitor"

 ### Comment all HorizSync and VertSync values to use DDC:
 ### Comment all HorizSync and VertSync values to use DDC:
 ### Comment all HorizSync and VertSync values to use DDC:
 ### Comment all HorizSync and VertSync values to use DDC:
	Identifier   "Monitor0"
	VendorName   "Monitor Vendor"
	ModelName    "LCD Panel 1280x800"
	HorizSync    31.5 - 90.0
	VertRefresh  60.0 - 60.0
	Option	    "dpms"
EndSection

Section "Device"
	Identifier  "Videocard0"
	Driver      "fglrx"
	VendorName  "Videocard vendor"
	BoardName   "ATI Technologies Inc RS300M AGP [Radeon Mobility 9100IGP]"
	Option	    "VideoOverlay" "on"
	Option	    "no_accel" "no"
	Option	    "no_dri" "no"
	Option	    "mtrr" "off"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Videocard0"
	Monitor    "Monitor0"
	DefaultDepth     24
	SubSection "Display"
		Viewport   0 0
		Depth     16
		Modes    "800x600" "640x480"
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Modes    "1280x800"
	EndSubSection
EndSection

Section "DRI"
	Group        0
	Mode         0666
EndSection

glrxinfo still returns this.

Code:

[root@localhost aparker]# fglrxinfo
display: :0.0  screen: 0
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.4.2)

PSY0NIC · #6 23rd May 2006, 01:55 PM

http://forum.fedoraforum.org/forum/s...d.php?t=104918

Cyaegha · #7 23rd May 2006, 02:45 PM

Ok, I've been through all of that. I removed and reinstalled kmod-fglrx, ran the ati-fglrx-config-display enable and enabledri. Still Mesa.

I tried aticonfig --initial again and still have Mesa.

i can't find anything else to try from that thread other than forcing the ATI installer to think I have Xorg6.9 which I'm not sure I know how to do anyway.

PSY0NIC · #8 23rd May 2006, 02:51 PM

back up your xorg.conf and try mine jsut to see if you can get the driver up then modify it to your specific needs. Let us know what happens. Also, what card are you using?

Cyaegha · #9 23rd May 2006, 03:02 PM

Tried you Xorg.conf PSYONIC. Had to comment out the BusID "PCI:1:0:0" line as it could not find my device there.

Still I get Mesa. This is frustrating. Other people seem to be able to get it to work or at least work and crash. I can't even get off this damn mesa.

[edit]
Sorry my card is a 9100 IGP in my Asus M6R notebook.

PSY0NIC · #10 23rd May 2006, 03:23 PM

Can you paste a copy of your /var/log/Xorg.0.log here please =D

Cyaegha · #11 23rd May 2006, 10:19 PM

Attached is with your xorg.conf

Cyaegha · #12 23rd May 2006, 10:26 PM

And this is with my xorg.conf Lots of the same errors.

fhubers · #13 24th May 2006, 01:10 AM

I found your problem - go to https://a248.e.akamai.net/f/674/9206...ux_8.24.8.html (release notes from ATI) and read the caution:
Caution: This software driver provides 2D support only for the ATI Radeon® 9100 IGP and ATI Radeon® 9100 PRO IGP.

Your board is not supported for 3D that is why you can only get 2D with the proprietary drive. Looks like you are stuck.

Cyaegha · #14 24th May 2006, 07:59 AM

Oh bugger. Thats a bit of a kick in the cods after all of that.

Thank you for pointing that out fhubers and thank you PSY0NIC for all of your time and assistance.

PSY0NIC · #15 24th May 2006, 01:05 PM

Sorry I didn't get back to you. Had to run out to a client all of the sudden yesterday. I just looked at you logs today. Sorry I couldn't help more. Wasn't aware your card was only supported up to 2D.