Mailinglist Archive: radeonhd (300 mails)

< Previous Next >
Re: [radeonhd] State of DRI on r5xx
  • From: Marvin <marvin24@xxxxxx>
  • Date: Wed, 21 May 2008 16:36:37 +0200
  • Message-id: <200805211636.37752.marvin24@xxxxxx>

Hi again,

Am Mittwoch 21 Mai 2008 12:48:19 schrieb Matthias Hopf:
Ok, Marvin, I'll continue debugging with you first, because your
hardware is much closer to mine than Sebastian's.

First, I'll analyze your config and command outputs:

On May 20, 08 17:05:43 +0200, Marvin wrote:
- xorg.conf

Section "ServerFlags"
Option "IgnoreABI" "on"

Did you verify that you need this option? If yes, then you're compiling
the driver with a wrong (old) SDK, and you have to update it. It's in
package xorg-x11-server-sdk. That would certainly explain the behavior
you're experimenting.

no need - maybe I (or openSUSE) put it there to be able to load the fglrx
driver.

Section "Device"
Option "AccelMethod" "EXA"

Just for notice: this is irrelevant, because ATM it's downgraded to
noaccel.

Section "DRI"
Group "video"
Mode 0660

Just to make sure - is your user in group video?

of course it is.

(II) RADEONHD(0): ATOM BIOS Rom:
SubsystemVendorID: 0x1002 SubsystemID: 0x791e

So you're having the other variant of the RS690. Mine is a 0x791f.
Not that this should change anything WRT visuals.

yes it's a 690V with no digital output

- output of glxinfo

OpenGL renderer string: Mesa DRI R300 20060815 NO-TCL

I got
OpenGL renderer string: Mesa DRI R300 20060815 x86/MMX+/3DNow!+/SSE2 NO-TCL

So you're compiling Mesa w/o optimization? Probably good idea for
debugging, I don't see how this should change behavior here.

this may be a difference - are you using x86 or x86-64 ?
I use x86-64 with:
make -j2 linux-dri-x86-64 DRI_DRIVER_INSTALL_DIR=/usr/lib64/dri
DRI_DIRS="r300"

0x61 32 tc 1 0 0 c . . 0 0 0 0 0 0 0 0 0 0 0 0 0 None

This is the only other difference - this broken entry has visual 0x51
for me - and I don't know where this one is coming from. But it is in
the same uninitialized state as the ones of the second call.

the funny thing is, that the glxinfo of Factory reports the error in the
second call, but the self compiled version from the mesa branch does not.
Sadly, the self compiled version of glxgears still aborts.

- version of radeonhd (sha1id) (be sure to have checked 6425a86b13)

6425a86b1309bdf0deccfa04300b04e2c6042bef

- version of mesa (branch, sha1id)

master branch: c6b36e5498cf6593daf001123cacec4ccaf305ca

- version of Xserver (version or sha1id)

openSUSE_Factory from today

- version of drm kernel module (sha1id)
- version of libdrm

both from master branch: 83996561061b99bb490fa0692a491ac9e51245a1

I'm running the same versions as you now. Except for libdrm, which isn't
involved in visuals at all...

I compared the two runs using ltrace -Sf, but couldn't see any difference
(except the failing glxChooseVisual). What could be the reason for this
behavior? I don't know much about X, but I'm able to use a debugger...

Marvin

--
To unsubscribe, e-mail: radeonhd+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups