No acceleration with ati-drivers

Message

m0p · Post by **m0p** » Tue Feb 27, 2007 1:15 am

No matter what I try, I'm still not succeeding at getting fglrx working. I've followed both the main ATi HOWTO on the Gentoo Wiki, and the ATi AMD64 HOWTO, as well as trying a few other things, and still I'm not getting acceleration. For the record, I'm using a Radeon X1950XTX and a DFI LP NF4 Ultra-D (I'm aware they've had problems working on Gentoo in the past).

Code: Select all

joe@m0pc0pter ~$ 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.5.1)

Code: Select all

joe@m0pc0pter ~$ lsmod | grep fglrx
fglrx               614200  11
agpgart              29924  2 fglrx,amd64_agp

There are no errors in my Xorg logs, just 4 warnings (2 of which are related to acpi and its highly doubtful those ones are related), fglrx warnings:

Code: Select all

(WW) fglrx: No matching device section for instance (BusID PCI:5:0:1) found
(WW) fglrx(0): GetVBEMode failed

My config is as follows:

Code: Select all

Section "ServerLayout"
        Identifier  "Layout1"
        Screen      "Screen1"
        InputDevice "Mouse1" "CorePointer"
        InputDevice "Keyboard1" "CoreKeyboard"
EndSection

Section "Files"
        FontPath    "/usr/share/fonts/misc/"
        FontPath    "/usr/share/fonts/Type1/"
        FontPath    "/usr/share/fonts/100dpi/"
        FontPath    "/usr/share/fonts/75dpi/"
EndSection

Section "Module"
        Load        "dbe"
        SubSection "extmod"
                Option    "omit xfree86-dga"
        EndSubSection
        Load        "freetype"
        Load        "glx"
EndSection

Section "ServerFlags"
        Option      "AIGLX" "off"
EndSection

Section "Extensions"
        Option      "Composite" "Disable"
EndSection

Section "InputDevice"
        Identifier  "Keyboard1"
        Driver      "kbd"
        Option      "AutoRepeat" "500 30"
        Option      "XkbRules" "xorg"
        Option      "XkbModel" "pc101"
        Option      "XkbLayout" "gb"
EndSection

Section "InputDevice"
        Identifier  "Mouse1"
        Driver      "evdev"
        Option      "CorePointer"
        Option      "Device" "/dev/input/event2"
EndSection

Section "Monitor"
        Identifier  "DPro930SB"
        HorizSync   "30.0 - 110.0"
        VertRefresh "50.0 - 160.0"
EndSection

Section "Device"
        Identifier  "X1950XTX"
        Driver      "fglrx"
        Option      "UseInternalAGPGART" "no"
        Option      "VideoOverlay" "on"
EndSection

Section "Screen"
        Identifier  "Screen1"
        Device      "X1950XTX"
        Monitor     "DPro930SB"
        DefaultDepth        24
        SubSection "Display"
                Viewport    0 0
                Depth       8
                Modes       "640x480" "800x600" "1024x768" "1152x864" "1280x1024" "1600x1200"
        EndSubSection
        SubSection "Display"
                Viewport    0 0
                Depth       16
                Modes       "640x480" "800x600" "1024x768" "1152x864" "1280x1024" "1600x1200"
        EndSubSection
        SubSection "Display"
                Viewport    0 0
                Depth       24
                Modes       "640x480" "800x600" "1024x768" "1152x864" "1280x1024" "1600x1200"
        EndSubSection
EndSection

Section "DRI"
        Mode 0666
EndSection

One more thing, I'm using ati-drivers-8.34.8, xorg-x11-7.1, and I've tried using both ck-sources-2.6.20_p1 and gentoo-sources-2.6.19-r5. I've also tried using the "stable" version of ati-drivers (can't remember which, but the newest version that isn't masked with ~amd64). I just can't see what could be causing the problem >.<

spielc · Post by **spielc** » Tue Feb 27, 2007 9:13 am

I had to add alot more options to the device section to get 3d-acceleration on my x1600pro.

here's my device section

Code: Select all

Section "Device"
	Identifier  "ATI Graphics Adapter 0"
	Driver      "fglrx"
	BusID       "PCI:2:0:0"
	# ### generic DRI settings ###
	# === disable PnP Monitor ===
	#Option "NoDDC"
	# === disable/enable XAA/DRI ===
	Option "no_accel" "no"
	Option "no_dri" "no"
	# === misc DRI settings ===
	Option "mtrr" "off" # disable DRI mtrr mapper, driver has its own code for mtrr
	# ### FireGL DDX driver module specific settings ###
	# === Screen Management ===
	#Option "DesktopSetup" "0x00000000"
	#Option "MonitorLayout" "AUTO, AUTO"
	#Option "IgnoreEDID" "off"
	#Option "HSync2" "unspecified"
	#Option "VRefresh2" "unspecified"
	#Option "ScreenOverlap" "0"
	# === TV-out Management ===
	Option "NoTV" "no"
	Option "TVStandard" "NTSC-M"
	Option "TVHSizeAdj" "0"	
	Option "TVVSizeAdj" "0"
	Option "TVHPosAdj" "0"
	Option "TVVPosAdj" "0"
	Option "TVHStartAdj" "0"
	Option "TVColorAdj" "0"
	Option "GammaCorrectionI" "0x06419064"
	Option "GammaCorrectionII" "0x00b02c0b"
	# === OpenGL specific profiles/settings ===
	Option "Capabilities" "0x00000000"
	# === Video Overlay for the Xv extension ===
	Option "VideoOverlay" "on"
	# === OpenGL Overlay ===
	# Note: When OpenGL Overlay is enabled, Video Overlay
	# will be disabled automatically
	Option "OpenGLOverlay" "off"
	# === Center Mode (Laptops only) ===
	Option "CenterMode" "off"
	# === Pseudo Color Visuals (8-bit visuals) ===
	Option "PseudoColorVisuals" "off"
	# === QBS Management ===
	Option "Stereo" "off"
	Option "StereoSyncEnable" "1"
	# === FSAA Management ===
	Option "FSAAEnable" "no"
	Option "FSAAScale" "1"
	Option "FSAADisableGamma" "no"
	Option "FSAACustomizeMSPos" "no"
	Option "FSAAMSPosX0" "0.000000"
	Option "FSAAMSPosY0" "0.000000"
	Option "FSAAMSPosX1" "0.000000"
	Option "FSAAMSPosY1" "0.000000"
	Option "FSAAMSPosX2" "0.000000"
	Option "FSAAMSPosY2" "0.000000"
	Option "FSAAMSPosX3" "0.000000"
	Option "FSAAMSPosY3" "0.000000"
	Option "FSAAMSPosX4" "0.000000"
	Option "FSAAMSPosY4" "0.000000"
	Option "FSAAMSPosX5" "0.000000"
	Option "FSAAMSPosY5" "0.000000"
	# === Misc Options ===
	Option "UseFastTLS" "0"
	Option "BlockSignalsOnLock" "on"
	Option "UseInternalAGPGART" "no"
	Option "ForceGenericCPU" "no"
EndSection

Try out the options above maybe you can make it work with these settings!

m0p · Post by **m0p** » Wed Feb 28, 2007 2:18 am

Just tried the majority of those, still nothing. Is agpgart supposed to be this silent?

Code: Select all

root@m0pc0pter ~# cat /var/log/dmesg | grep gart
Linux agpgart interface v0.101 (c) David Jones

Could it be that my card, whilst being detected by fglrx and as a PCI device, isn't being detected by agpgart? I'm seriously gonna consider going back to x86 if I can't solve this :<

blotto · Post by **blotto** » Wed Feb 28, 2007 10:28 am

Hi what does Xorg log say about dri?

Have you tried

Code: Select all

    Load	"dri"

in the Modules section of xorg.conf

Heres the bits from my xorg.conf

Code: Select all

Section "Module"
    Load	"i2c"
    Load	"bitmap"
    Load	"ddc"
    Load	"dri"
    Load	"extmod"
    Load	"freetype"
    Load	"glx"
    Load	"int10"
    Load	"type1"
    Load	"vbe"
    Load	"record"
    Load	"dbe"
EndSection

Section "Device"
    Identifier  "PCI"
    Driver      "fglrx"
    BusID       "PCI:1:0:0"
    Option "UseInternalAGPGART"         "no"
    Option "mtrr"                       "off"
EndSection

dnadesign · Post by **dnadesign** » Wed Feb 28, 2007 10:51 am

Additionally add a section to xorg.conf (a suitable place could be at the end of file) that will allow you to use DRI as a normal user:

Code: Select all

Section "dri"
    Mode 0666
EndSection

EDIT: And one more thing. You're using the binary drivers so:

Code: Select all

# eselect opengl set ati

would be sufficient.

m0p · Post by **m0p** » Wed Feb 28, 2007 11:34 am

I added all of that to my config yesterday and it still wouldn't work, I've done eselect multiple times and even tried manually overwriting mesa libGL.* files, and yet for some reason it still reports that I'm using mesa. This is just crazy >.< I'll try it again later and see if DRI is mentioned anywhere in my xorg log.

blotto · Post by **blotto** » Wed Feb 28, 2007 9:09 pm

Hi again forgot about your AGP thingy! stupid of me cos I've had bother with my new M/B (Asrock AM2NF3-VSTA) and a 4200+ X2.
Graphics is AIW 9800 SE

I have the agpgart built in - I tried it as modules (using info in other threads) but could not get it to work with ATI driver, the upshot is that when I cold boot the agpgart does not get detected but if I then reboot the agpgart is detected and the ATI driver works and I get DRI as well.

So here's what I get

coldboot

$ dmesg | grep -i agp
AGP bridge at 00:00:00
Aperture from AGP @ f8000000 size 4096 MB (APSIZE 0)
agpgart: Detected AGP bridge 0
agpgart: Aperture conflicts with PCI mapping.
agpgart: Aperture from AGP @ f8000000 size 4096 MB
agpgart: Aperture too small (0 MB)
agpgart: No usable aperture found.
agpgart: Consider rebooting with iommu=memaper=2 to get a good aperture.
Linux agpgart interface v0.101 (c) Dave Jones
[fglrx] Internal AGP is not supported in 2.6 kernel.

reboot

$ dmesg | grep -i agp
agpgart: Detected AGP bridge 0
agpgart: Setting up Nforce3 AGP.
agpgart: AGP aperture is 64M @ 0xf8000000
Linux agpgart interface v0.101 (c) Dave Jones
[fglrx] Internal AGP support requested, but kernel AGP support active.
[fglrx] Have to use kernel AGP support to avoid conflicts.
[fglrx] AGP detected, AgpState = 0x1f00420b (hardware caps of chipset)
agpgart: Found an AGP 3.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
[fglrx] AGP enabled, AgpCommand = 0x1f004302 (selected caps)
[fglrx] total GART = 67108864
[fglrx] free GART = 51113984
[fglrx] max single GART = 51113984
[fglrx] total LFB = 134217728
[fglrx] free LFB = 116387840
[fglrx] max single LFB = 116387840
[fglrx] total Inv = 0
[fglrx] free Inv = 0
[fglrx] max single Inv = 0
[fglrx] total TIM = 0

If you think fglrx and xorg are OK then maybe the AGP thing is your problem. As you can see mine is a little strange!

Im using gentoo-sources 2.6.20 but it was the same with 2.6.19-r5

blotto · Post by **blotto** » Wed Feb 28, 2007 9:30 pm

Hmm just noticed that your M/B is PCIE so I dont know how this works with AGPGART maybe dont use it?
Dont know how it is reported in dmesg since I dont have any systems with PCIE.
Certainly I would expect it to have a PCI ID: rather than an AGP ID:(usually 1:0.0)

m0p · Post by **m0p** » Thu Mar 01, 2007 3:38 pm

For some reason, it's working now (I thought at first that commenting out Load "glx" fixed it, as I was messing around with different combinations of configuration to see if I could get it working, but when I uncommented it, it was still working). Though, despite glxinfo reporting that Direct Rendering is working, and glxgears running at 10,000fps, no games seem to be working. At first I tried my old favorite, Enemy Territory. Though when I tried to run it, I was confronted with an error that I was using Mesa and needed to run ET with +r_AllowSoftwareGL 1, which I tried, though the performance was horrendous. Because ET is 32-bit, I assumed it was a compatability problem, so I tried a game I could compile from source (ppracer). This time I had a different error, though it most likely means the same thing, and was along the lines of "No devices detected, SDL cannot run", despite the fact that at the very same time, glxinfo was telling me that direct rendering was on and my renderer string was "ATI Radeon X1900 series". I don't really know where to go from here, I've got DRI working fine, but nothing other than glxinfo and glxgears seem to take notice of that.

blotto · Post by **blotto** » Fri Mar 02, 2007 12:12 am

Hi did you install the ati-drivers-extra package - if you did you could try the ati utilities

Code: Select all

$ fglrxinfo

and

Code: Select all

fgl_glxgears

and see what they give you

m0p · Post by **m0p** » Fri Mar 02, 2007 9:18 am

I did try fglrxinfo (it came with the ati-drivers package for me), but I haven't tried fgl_glxgears yet. I'll give it a try in a bit. fglrxinfo gave me the same info for "renderer string" and such, "ATI Radeon X1900 series", or something along those lines, though. It's still puzzling me though how glxgears works fine but everything else complains that I'm still using Mesa (I've done eselect opengl set ati multiple times, so I don't think that's the problem :/).

dnadesign · Post by **dnadesign** » Fri Mar 02, 2007 10:21 am

It's probably not the case, but: are you still running with Load "glx" commented out?

m0p · Post by **m0p** » Fri Mar 02, 2007 11:12 am

Nope, I uncommented it.

dnadesign · Post by **dnadesign** » Sat Mar 03, 2007 11:43 am

Well I do have an idea. Run two commands and paste their output here. Try this first:

Code: Select all

$ ldd $(which glxgears)

And then, try the same with an app, that doesn't detect your ATI accel (that Enemy Territory would do nicely):

Code: Select all

$ ldd $(which APP_NAME)

Make sure, that the file your giving instead of APP_NAME is a binary file (or a symlink to it).

m0p · Post by **m0p** » Sat Mar 03, 2007 4:01 pm

The output for both "ldd $(which glxgears)" and "ldd $(which ppracer)" both contain "libGL.so.1 => /usr/lib64/opengl/ati/lib/libGL.so.1 (0x00002ae4e2f08000)". It didn't work with ET, it claimed et.x86 and et weren't "dynamic executables". One strange thing, in ET's console output before it tells me I'm using Mesa, Xlib complains that extensions "XFree86-VidModeExtension" and "XFree86-DGA" are missing on display :0.0. Since glxgears works, yet ET and ppracer don't, maybe the problem is that they can't change the display resolution? This would make sense looking at ET's console output.

EDIT: Managed to stop ET complaining about the extensions by uncommenting the extmod section in my xorg config but leaving the "omit xfreex86-dga" line commented. ET and ppracer still complain that there is no device, yet glxgears is working fine.

loftwyr · Post by **loftwyr** » Sat Mar 03, 2007 4:22 pm

You may already have tried this but try changing away from ati and back

Code: Select all

eselect opengl set xorg-x11
eselect opengl set ati

dnadesign · Post by **dnadesign** » Sun Mar 04, 2007 9:44 am

Yeah, ET could get ldd confused (espacially if it's 32 bit), but try running ldd on a game, that was compiled on your arch (no binary download) and reports Mesa.

m0p · Post by **m0p** » Mon Mar 05, 2007 8:55 am

I did try ppracer (Tuxracer) too, which is compiled from source. Also tried switching OpenGL from xorg-x11 then back to ati, ET still claims I'm using Mesa and ppracer still crashes with the message "Cannot initialize SDL: No availible video device". Note that glxgears and glxinfo are both working as intended before and after trying ET and ppracer. Maybe the problem could be that fglrx doesn't want to work in fullscreen? That's the only thing I can think of now. At the moment, whenever I startx, it's throwing me into a 640x480 displaymode, but I can scroll around it and it's about there is about 1600x1200 worth of space on there. Maybe the problem could be related to display modes? I posted my entire config (including displaymodes) above if anyone wants to see.

EDIT: Just thought I'd try revdep-rebuild --pretend, and it seems to think there is something broken.

Code: Select all

Checking dynamic linking consistancy...
 broken /usr/lib32/dri/fglrx_dri.so (requires  libstdc++.so.5)

Then it tells me that it would merge ati-drivers again without --pretend, so I gave that a go, it rebuilt them. I ran revdep-rebuild --pretend again to see if it had fixed it, and nope it hadn't. Maybe this could be causing the problem with ET?

dnadesign · Post by **dnadesign** » Wed Mar 07, 2007 9:21 am

Seems to me that your emulated 32bit Gentoo environment is not complete. You should try emerging the emul packages. Your best bet is the emul-linux-x86-compat package, which contains libstc++.

m0p · Post by **m0p** » Sun Mar 18, 2007 8:51 pm

Sorry for the late reply, but emerging "emul-linux-x86-compat" worked great, thanks dna! ppracer still isn't working but ET is doing fine, however there is one problem, when I close ET it doesn't reset back to my desktop resolution, it stays at 1024x768. Changing my ET resolution to match my desktop resolution isn't an option, that's how I play and that's how it'll stay, before anybody suggests that.. wondering if there is any other way to fix this? It's pretty annoying having to change my resolution every time I want to close ET.

dnadesign · Post by **dnadesign** » Tue Mar 20, 2007 12:31 pm

Well, the ATI linux drivers have many different bugs and buggies about them. Resolution changing is one of them. For example I have a Radeon Xpress 1100 and the screen freezes when I shutdown X. I guess we just have to wait until the quality of those drivers goes up do a decent level, but this may take some time.

m0p · Post by **m0p** » Tue Mar 20, 2007 2:27 pm

Last time I used the drivers when I was using plain x86 Gentoo (a year and a bit ago), there was NO problem with resolution changing. I played ET every day at 1024x768 and had my desktop running at 1600x1200, and the transition was flawless. Maybe it's a problem with my Xorg config or Xorg itself and not the drivers?

dnadesign · Post by **dnadesign** » Tue Mar 27, 2007 7:50 am

Well, it kind of seems to be a problem with the drivers running on AMD64, they're far from stable in my opinion. Of course many people say that they don't have that kind of issues, but on the other hand many say they do. You're right about those drivers on x86, everything there runs almost flawlessly (seems that the problems from AMD64 don't exist there).

superwutze · Post by **superwutze** » Fri Mar 30, 2007 8:24 am

the x1950 series is still not supported on linux. i had some trouble to get my x1950pro agp card to work. when i used 8.34 i could watch videos but had no glx or dri, with v 8.33 i had dri and glx but caould not watch videos (x server terminates the instance mplayer or xine start). the new 8.35 don't even compile on my box. so for now i stick to 8.33. maybe you try different versions of the ati-driver package.

dnadesign · Post by **dnadesign** » Tue Apr 03, 2007 9:51 pm

I have a X300 and the support on AMD64 is far from what I could call decent. For the time being my problems with "a strange black screen fading slowly to white, then to purple, and then I don't know, because I reset the computer before I get a heart attack out of the stress" are gone, the X server this hangs the display on exit (ATI's Linux drivers, at least it doesn't bother me that much, because I only shutdown X when I shutdown my notebook and the system still shuts down normally). Besides it sucks twice, as of the DRI project not supporting this chipset (yet... I hope).