ATI IGP 320M, Xorg 7 . . . still no DRI

lydgate · 2006-01-20 00:26:48

Okay, I know this is a topic that has been beaten to death, and I've tried hard in the last week to solve this on my own, but I am still unable to get DRI working. I knew it was a pain with Xorg 6.8, but I thought with 7.0 it might be easier. I also was waiting to switch away from XFCE, as it seems it has some problems with the DRI module. Now I'm using OpenBox, so hopefully it should work.

xorg.conf:

Section "Module"
        Load  "ddc"  # ddc probing of monitor
        Load  "GLcore"
        Load  "dbe"
        Load  "dri"
        Load  "extmod"
        Load  "glx"
        Load  "bitmap" # bitmap-fonts
        Load  "type1"
        Load  "freetype"
        Load  "record"
EndSection
...
Section "Device"
        Identifier  "Card0"
        Driver      "radeon"
        VendorName  "All"
        BoardName   "All"
EndSection

In Xorg.0.log, I see

(II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon QD (AGP),
...
ATI Radeon IGP320 (A3) 4136, ATI Radeon IGP320M (U1) 4336,

which is the card in my laptop, so I am hoping I can get it to work.

grep "^(EE)" Xorg.0.log

(EE) Failed to load /usr/lib/xorg/modules/extensions/libGLcore.so
(EE) Failed to load module "GLcore" (loader failed, 7)
(EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI.

So, obviously that is a problem but I'm not sure how to fix it.

grep "^(WW)" Xorg.0.log

(WW) xf86OpenConsole: Could not save ownership of VT
(WW) xf86OpenConsole: chown /dev/tty0 failed: No such file or directory
(WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode disabled
(WW) RADEON(0): [agp] AGP not available
(WW) RADEON(0): Direct rendering disabled

Looks like a related problem, or maybe the source of the problem? I can post my whole log if that will help.

I'm not sure why it's saying no AGP, lsmod grepped for stuff (I think) is relevant stuff looks like this:

ati_agp                 7692  1
agpgart                29904  2 ati_agp,drm

radeonfb               89792  0
i2c_algo_bit            8968  1 radeonfb
i2c_core               18176  2 radeonfb,i2c_algo_bit
radeon                108448  0
drm                    67476  1 radeon

In my kernel, which I have compiled myself based on 2.6.15-ARCH, I have agpgart, ATI stuff, DRI, all compiled as modules, and they seem to load okay (I have agpgart before radeon in my rc.conf).

Obviously I get
glxinfo | grep render

direct rendering: No
OpenGL renderer string: Mesa GLX Indirect

I think that Mesa might be the problem too?

Any help would be greatly appreciated, I've tried a bunch of guides and no luck . . .

patroclo7 · 2006-01-22 13:11:32

I have the same card and dri is functioning here with modular xorg 7.0 (it was functioning also in xorg 6.8.0, but not in 6.8.2). I have your same kernel configuration. However, there are some details in xorg.conf you did not mention; thus I post them here, so you can investigate any difference. Firstly, my section "Device" for the video card is the following:

Section "Device"
    Identifier  "Card0"
    Driver      "radeon"
    VendorName  "ATI Technologies Inc"
    BoardName   "Radeon Mobility U1"
    BusID       "PCI:1:5:0"
        Option      "AGPMode" "4"
#        Option      "SubPixelOrder" "BGR"
    Option      "AGPFastWrite" "True"
        Option      "DynamicClocks" "True"
        Option      "EnablePageFlip"   "True"
        Option      "BIOSHotkeys"   "On"
        Option      "ColorTiling" "True"
#        Option      "AccelMethod" "EXA"
        Option       "LVDSProbPLL" "off" 
        Option      "VGAAccess"   "off"
EndSection

The possibly relevant options are "AGPMode", "AGPFastWrite", "DynamicClocks" and "EnablePageFlip", "ColorTiling": see "man radeon" for details. You can also try to change the acceleration method, replacing the default XAA with the new EXA: in my case, there is no performance difference, but EXA works better with the composite extension, but is also much less stable than XAA; thus I decided not to use composite and to choose XAA.

Secondly, you should define mode (and permissions) for the dri module, with a specific section like this:

Section "dri"
    Mode 0666
EndSection

lydgate · 2006-01-22 20:10:42

Okay, I reinstalled Xorg 7 due to some weird stuff, and set the xorg.conf to the way you mentioned. I read the manpage but I'm still not sure I understand LVDSProbPLL and VGAAccess. Why do you have these set to off?

Anyway, now I get direct rendering: Yes.

Two things: with EXA I get 260 or so fps in glxgears, in XAA I get 283, but with XAA dragging/scrolling isn't very smooth, is this because I use xcompmgr? Also, aren't these very low values for glxgears?

The second thing: when I first open an openGL thing, like glxgears or a GL screensaver, it sometimes displays only on the left half of the screen or window. If I close it and reopen it, usually it displays normally. Does this happen to you?

patroclo7 · 2006-01-22 22:05:31

1) LVDSProbPLL and VGAAccess should have no bearing with dri and should anyway be harmless in general: I disable them only because I do not really need them;
2) In glxgears I get around 200 fps with both the acceleration methods. If you google around, you can see that nobody else gets more than 300 fps in glxgears with this card. However, glxgears reliability is often questioned and, when I try something like tuxracer or emilia-pinball, performances does not seem to me so bad;
3) XAA and composite extension determine very slow dragging/scrolling. I think this is the main motivation why the new EXA is being developed. However, I had serious issues with EXA: when hardware acceleration was in use, my system hanged suddenly (very often with accelerated screensavers). But it is my problem: I read around that other people use EXA with this card without any particular issue.
4) I did never encounter the "half screen" issue you describe, thus I can not help you from this point of view.

Jacek Poplawski · 2006-01-24 15:57:14

I think that you need AGP, make sure you have correct AGP module loaded (agpgart and agp for your chipset).

ugh, no I am wrong, I haven't noticed "PCI" in post

patroclo7 · 2006-01-24 19:00:08

It was saying NO AGP because he did not activate agp in xorg.conf, his kernel configuration should be fine (see above the lsmod output).

JGC · 2006-03-25 12:55:59

One note: never load GLCore from the modules section, since it breaks for sure. Load glx instead.

Snowman · 2006-03-25 17:32:19

naryga wrote:

modules section of xorg.conf or rc.conf?

xorg.conf

Arch Linux

#1 2006-01-20 00:26:48

ATI IGP 320M, Xorg 7 . . . still no DRI

#2 2006-01-22 13:11:32

Re: ATI IGP 320M, Xorg 7 . . . still no DRI

#3 2006-01-22 20:10:42

Re: ATI IGP 320M, Xorg 7 . . . still no DRI

#4 2006-01-22 22:05:31

Re: ATI IGP 320M, Xorg 7 . . . still no DRI

#5 2006-01-24 15:57:14

Re: ATI IGP 320M, Xorg 7 . . . still no DRI

#6 2006-01-24 19:00:08

Re: ATI IGP 320M, Xorg 7 . . . still no DRI

#7 2006-03-25 12:55:59

Re: ATI IGP 320M, Xorg 7 . . . still no DRI

#8 2006-03-25 17:32:19

Re: ATI IGP 320M, Xorg 7 . . . still no DRI

Board footer