Nightwulf|work: hi all
federico_: I was here yesterday asking about enabling radeonhd. Now that i installed it from the tormodvolden repository I wanted to say 2D desktop works, video playback is fine both fullscreen and windowed. Enabling DRI makes it slow down a lot (moving windows around) so no DRI. I'm using IGP HD3200 which is supported since 1.2.2.
Zajec: federico_: there isn't 3D nor Xv for radeonhd yet
federico_: I know. This is the only open driver that works with this radeon chip. The radeon driver shows everything greenish and crappy.
Temujin_: hello, trying to solve problem with glxinfo saying "direct rendering: no" and segfaulting unless started with root/sudo
Temujin_: (yes, mode 0666 in the DRI section is set in xorg.conf)
Temujin_: "libGL error: dlopen /usr/lib/dri/r300_dri.so failed (/usr/lib/dri/r300_dri.so: undefined symbol: _glapi_tls_Context)"
yangman: Temujin_: sounds like a version mismatch between the various components
Temujin_: hmm, as long as direct rendering works for non-root apps, this doesn't bother me. is there a good way to test this?
yangman: Temujin_: actually, look at the permission on /usr/lib/dri/r300_dri.so
Temujin_: already did that, it's 664
adamk: Temujin_, Can you run the apps as root or with sudo, set LIBGL_DEBUG to verbose, and see if it's using the same r300_dri.so file?
adamk: And check which libGL.so file it's being linked against as both root and non-root with the 'ldd' command.
Temujin_: ah, using glxgears as an example:
Temujin_: without sudo: libGL.so.1 => /usr/lib64/xorg/libGL.so.1 (0x00007fab1c798000)
Temujin_: with sudo: libGL.so.1 => /usr/lib/libGL.so.1 (0x00007ff939ae0000)
adamk: Are you running two different versions of glxgears? A 32-bit version and a 64-bit version? That would be my first guess.
adamk: It's also possible that you have LD_LIBRARY_PATH setup differently.
Temujin_: well, you've given me food for thought, thank you, will report back if i figure it out
yangman: Temujin_: you probably have a broken LD_LIBRARY_PATH for your user set somewhere. someone else's had this issue in the past as well
Temujin_: echo $LD_LIBRARY_PATH /usr/lib32/xorg:/usr/lib64/xorg:/usr/lib32
Temujin_: btw, adamk, the above output was from ldd /usr/bin/glxgears , so it's the same file
yangman: Temujin_: where is /usr/lib symlinked to?
Temujin_: this is ubuntu64, os /usr/lib is the main (64-bit) directory, /usr/lib64 is linked there and /usr/lib32 is for 32-bit libs
Temujin_: hmm, it looks that /usr/lib/libGL.so.1.2 is different than /usr/lib/xorg/libGL.so.1.2
yangman: oh, I missed that part
yangman: Temujin_: something in your profile is adding /usr/lib*/xorg to your LD_LIBRARY_PATH, and it shouldn't be
Temujin_: copyiing /usr/lib/libGL.so.1.2 to /usr/lib/xorg/libGL.so.1.2 fixed it
Temujin_: the old libGL.so.1.2 was from June. i'm guessing it was from fglrx
yangman: Temujin_: that's probably it. it does things like that
Temujin_: thanks for the help, folks
dacm: Hi guys.
dacm: Is there any news yet on when ATI/AMD will release the docs for 3D support in R6xx?
yangman: dacm: no
dacm: They really seem to be dragging their feet on this.
yangman: er, not really
dacm: 11-07-2008 <= Is that american or british format?
dacm: I mean was that post from July or a few days ago?
dacm: yangman: I said that they seem to be dragging their feet as it's been over a year since AMD announced they would release specifications.
yangman: dacm: this is from last week
yangman: dacm: yes, and they did. several of them
dacm: Yeah not all of it has been released yet has it?
yangman: dacm: depends on your definition of "all of it". you can't release things you don't have, for example ;)
dacm: But AMD clearly have enough docs to have written fglrx.
yangman: in any case, yes, the r600/r700 acceleration work has been delayed, but it _is_ being done.
yangman: dacm: you'd think that. comments from people involved suggest otherwise
dacm: Anyway, it's good to hear that 3D support on the R6XX might be available soon. Thanks for posting that link. :-)
yangman: internal documentation is a mixed bag. unless there are very strict guidelines on producing them (ala Google), they usually get pushed aside for "Real Work"
yangman: posterity isn't usually high on the priority list in a fast moving industry
dacm: Maybe. But I would think that the people who write the drivers and the people who designed the hardware would be different groups, hence the need for documentation. But I could be wrong.
airlied: dacm: they are but they sit beside each other.
airlied: so its just scraps of documentation, notthing reall coherent.
dacm: ah, fair enough
yangman: it's easier to walk across the hall and say "hey, how do I make X work?" as issues come up than ask "can you document X, Y and Z so I can make them work?"