umtc: i posted a problem earlier, that both my screens had their resolutions locked together when specifying the second monitor section
umtc: it turns out that commenting the horizsync line on the monitor section for the secondary monitor solves it. vertrefresh doesn't cause any issue
umtc: is there an application that can dump or show xinerama configuration? i'd like to know why mozilla starts up correctly on my primary screen, but always pops the download a file dialog centered in the second screen
umtc: i've heard that dual screens makes 3d not work, and that xv on 780g needs 3d support. does that mean i won't be able to use xv with dual screens?
adamk: If you want to use two separate screens, then yes, 3D acceleration will not work. If you want one screen across two monitors, that is supported with 3D acceleration (on r100-r500 GPUs)
libv: umtc: 780 is r6xx class 3d engine
libv: umtc: so nothing there yet
libv: dual screen or not, you won't get dri or xv
adamk: D'oh.
umtc: i'm asking if xv with dual monitors would work, since it would require 3d
adamk: Thanks for the clarifications. That's why I specified r100-r500... I wasn't sure where the 780 fell :-)
umtc: i'm referring to the future
adamk: In the future, as long as you are using one screen across two monitors, it will work fine.
adamk: Once 3D acceleration is available.
libv: adamk: rs780; rs = igp, so 3d wise it's r6xx (one 100 difference)
libv: ati marketing likes that sort of thing
umtc: i have no use for 3d, but it seems you can't get away from it any more
adamk: umtc: Well, bear in mind that all r600 and higher GPUs don't have separate 2D components any more, as I understand it, anyway.
adamk: libv, Yeah, it can be really quite confusing at times :-)
libv: umtc: well, the video overlay is too limited on this hardware, and the colour conversion/scaling engine, we have no info on, nor don't we expect to get info on it
libv: described here btw: http://en.wikipedia.org/wiki/AVIVO
libv: so the 3d engine needs to be used to do colour conversion and scaling
libv: so no 3d engine == no xv
libv: adamk: rs740 is a funny one that just came out
libv: adamk: it's an updated rs690
libv: so -2xx engine wise *rolls eyes*
libv: i wonder what was wrong with rs695
adamk: lol
umtc: since that, is there no more difference between using xv and gl video output?
libv: umtc: oh, there is, the code in xv is written to do just this one task, and might be faster, but YMMV
umtc: if there is no 2d component, how do things like vesa driver still work?
libv: vesa is just some very rudimentary modesetting
libv: getting framebuffer content to shop on a screen near is far from a trivial task
libv: near you even
umtc: i guess the danger of these new 3d-only video chips is diminishing, i was worried that we would be stuck in console mode until full 3d support was done, and that we'd all have to use those 3d window mangers
x1550: for x1550 is better radeonhd or radeon ?
libv: radeonhd of course :)
chainsawbike: :/ i finally got dri working now it will only work as root
chainsawbike: any ideas?
yangman: chainsawbike: look up DRI-setup instructions for your particular distro. usually it's a matter of not being in the right group, or /dev/dri* devices having the wrong permission, but the latter should be handled automatically by xorg-server nowadays
lordnoid: I got x1950pro and 3D works excellent
lordnoid: in radeonhd :)
chainsawbike: distro is gentoo
chainsawbike: afaikt the device has the correct permissions
yangman: chainsawbike: make sure your user account is in the 'video' group
chainsawbike: yep
yangman: what's the permission on /dev/dri0/card0 ?
chainsawbike: crw-rw-rw- 1 root video 226, 0 Oct 16 04:22 /dev/dri/card0
yangman: yeah, make sure you're in the video group, and re-login if it's just been added
chainsawbike: ill re-login for good measure but i was there
chainsawbike: no change
yangman: just for completeness, can you paste your output of `groups`?
chainsawbike: as long as you dont ask why i am in some :P
chainsawbike: http://pastebin.com/m1650c015
yangman: heh
chainsawbike: yea...
yangman: hm...
yangman: so, glx info reports working DRI only with root, or are you seeing a different issue?
chainsawbike: thats it :)
chainsawbike: hmm... i can run compiz via a su'd terminal
yangman: that's bizzare
yangman: xorg-server-1.4.* or 1.5.*?
chainsawbike: 1.5.2
yangman: ok. tried using a minimal xorg.conf?
chainsawbike: ill try
yangman: from the looks of it, you're explicitly setting dri chmod to 666
chainsawbike: yep
chainsawbike: ive been playing with this for a while now...
yangman: with 1.5.*, you only really need a device section and the accompanying screen section to point to it
chainsawbike: i have dual screens so a bit more for me
chainsawbike: nope... ill take out the xrandr stuff
chainsawbike: still nope
yangman: give it a reboot for good measure ;)
yangman: but, really, it should just work
yangman: the defaults are sensible
chainsawbike: ok :)
chainsawbike: no change
yangman: pastebin the output of glxinfo as user and as root
chainsawbike: k
chainsawbike: http://pastebin.com/m19bf1b1d
chainsawbike: user
chainsawbike: http://pastebin.com/m1bb434ca
chainsawbike: root
yangman: yeah, bizzare
yangman: maybe LIBGL_DEBUG=verbose will give you the answer
yangman: I gotta get to work now, though. gl
chainsawbike: thanks :)
chainsawbike: libGL error: dlopen /usr/lib64/dri/r300_dri.so failed (/usr/lib64/dri/r300_dri.so: undefined symbol: _glapi_Dispatch)
chainsawbike: hmm...
chainsawbike: i dont get that as root
chainsawbike: that makes no sense
chainsawbike: well i g2g pm me if anyone has any ideas
yangman: chainsawbike: check the permission on /usr/lib64/dri/r300_dri.so
Obscene_CNN: who ever the idiot was that decided to depreciate the settings in xorg.conf and favor the hal detected hardware should be shot!! instead of having one nice readable file we now need several cryptic xml files. :(
masa^: what??
masa^: since when and what settings?
masa^: all of them?
Obscene_CNN: in xorg-server 1.5.2
Obscene_CNN: its totally hosed my touchpad
Obscene_CNN: this has an explanation http://gentoo-wiki.com/Synaptics_Touchpad/Xorg_7.3
Obscene_CNN: well, I have mesa working..... but I only get a frame rate of 300 as root and 80 as a user. Also I have the screen lockup when I exit X.
Obscene_CNN: I'm not certain I have xorg-server-1.5.2 installed 100% right though
Obscene_CNN: has anybody gotten DRI to work on an RS780 ?
MostAwesomeDude: Obscene_CNN: Which GPU core is that?
Obscene_CNN: either a 610 or a 630
airlied_: Obscene_CNN: no 6xx has DRI.
Obscene_CNN: but its an rs6xx
Obscene_CNN: supposedly
airlied_: no its not, its an rs7xx, some of which are like rs6xx some aren't.
airlied_: rs740s are like rs6xx
airlied_: rs780s are r600 based
Obscene_CNN: okay, that explains why dri isn't working then
Obscene_CNN: drat... and so many people here have told me it was an rs6xx core
libvde: Obscene_CNN: ati marketing is not there to make things clear and simple
Obscene_CNN: thats for sure.
Obscene_CNN: Ever since I bought this laptop I have been scrambling to try and find info on the video chip.
Obscene_CNN: I still am guessing as to what the real difference is between the radeon 3100 and the radeon 3200 other than you are supposed to be able to use another graphics processor in parallel with the 3200 and the 3200 supports up to 512Meg of video ram instead of just 256Meg
chainsawbike: yangman, it was an environment variable stopping it working - `env -u LD_LIBRARY_PATH glxinfo` works
chainsawbike: now to find what is setting it
J2000_ca: Does the RROutputOption not work on some configs? I have a Radeon HD 2600XT. I have dual head working but RROutput won't switch what side gdm is on.