icebrain: hi! do you know if that bug that occurs when using 3D or KDE effects as been corrected? I mean bug 24131 in radeon drivers in mesa
yangman: if the bug entry hasn't been updated, most likely no
icebrain: yangman: it's strange, 'cause in ubuntu they seem to have it fixed: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/446578
icebrain: they say it was fixed in 7.6.0...
yangman: then maybe it is
yangman: mesa is mesa. we don't really deal with that here
yangman: most of the mesa radeon discussion happens in #dri-devel or #radeon
icebrain: sure, but it affects radeonhd users, I though someone could have experienced it
icebrain: yangman: thanks anw
MostAwesomeDude: icebrain: If it's closed in Ubuntu, either the bug reporter gave up, or I didn't notice the fix get pushed.
icebrain: MostAwesomeDude: they say it's working now, also: fix released :|
MostAwesomeDude: Okay, looks like they fixed it by reverting a Mesa patch.
MostAwesomeDude: Boy, it'd sure be nice if downstream talked to us occasionally. :T
icebrain: MostAwesomeDude: exactly, I thought it was strange it was corrected in ubuntu but nothing appeared in freedesktop bug reports...
icebrain: they didn't even inform debian, damn freeloaders :)
lab: Hi. I have installed the radeon driver for a x1200 card. unfortunately I can only set the 640x480 resolution. what could I do ?
lab: [15:53]
lab: [15:54]
adamk_: lab, Wrong channel.
adamk_: You are using the radeon driver not the radeonhd driver.
adamk_: You could, if you wanted, try the radeonhd driver, certainly.
adamk_: Alright, I'm off to a meeting. bbl.
Diablo-D3: hey guys
Diablo-D3: I have a 4850
Diablo-D3: can radeon or radeonhd display any 3D on it?
bridgman: Diablo-D3; either driver will work with 3D, but the 3D isn't actually done by radeon or radeonhd, it's a combination of mesa and drm code
bridgman: the radeon and radeonhd drivers handle initialization, modesetting and EXA/Xv acceleration
bridgman: (although with KMS the initialization and modesetting move into drm as well)
Diablo-D3: okay, maybe I should ask it this way
Diablo-D3: what can I _not_ do
bridgman: you can't run anything that needs >OpenGL 1.4-ish, and you can't run anything that needs to use S3TC-compressed textures
bridgman: text entry under Compiz is corrupted unless you are also running KMS
bridgman: other than that, it's just the usual bugs & quirks I think
Diablo-D3: so.... I cant do much.
bridgman: depends on what you want to do ;)
Diablo-D3: I want fglrx to die a horrible death.
bridgman: ahh, so you're looking for a high performance workstation driver then
Diablo-D3: I dont even care about the performance, really
Diablo-D3: I just want it to actually work
bridgman: of course you do, 3d performance is why we have fglrx
Diablo-D3: actually, thats a lie
Diablo-D3: I played with radeonhd a few months back
Diablo-D3: the 2D... it is so fast ;_;
bridgman: yep; having EXA certainly helps
agd5f: Diablo-D3, bridgman: compiz bug is fixed now
bridgman: woo hoo !
bridgman: now we just need to ask the nice ubuntu folks to pick up drm & mesa changes ;)
agd5f: bridgman: already pinged
bridgman: tx
Diablo-D3: does anything in mesaland support shaders?
agd5f: Diablo-D3: r300 and r600 drivers support ARB_fp/vp
Diablo-D3: well thats an improvement
agd5f: Diablo-D3: r300 has supported that for years
agd5f: r600 was just written
Diablo-D3: I remember when nothing did shaders
agd5f: Diablo-D3: r300+ have to since there is no fixed function pipeline
Diablo-D3: I meant exposed through arb_fp/vp
Diablo-D3: mesaland had no shader compilers
rozzo: we
rozzo: hello
rozzo: i have fixed a radeon bug
rozzo: but anyone have interest?
agd5f: rozzo: sure
agd5f: what bug?
rozzo: mmmm
rozzo: i don't remember exact error waith
rozzo: (WW) RADEONHD(0): DRMCPIdle: DRM CP IDLE returned BUSY!
rozzo: (WW) RADEONHD(0): DRMCPIdle: DRM CP IDLE returned BUSY!
rozzo: this
rozzo: the bastard
rozzo: agd5f, the solution is very simple
agd5f: rozzo: what was it?
rozzo: in the section of display
rozzo: set
rozzo: Modes "1440x900"
rozzo: or your resolution
rozzo: and this work
rozzo: if i remove this the bug return
rozzo: bhahaahahha
rozzo: fuck'ing bug
rozzo: agd5f, http://lists.opensuse.org/radeonhd/2008-11/msg00149.html
rozzo: or in the mail list ati radeonhd
rozzo: bhaahahaha
rozzo: i hate the auto config of xorg but is the future
rozzo: agd5f, http://www.radeonhd.org/?page=archive_display&c=radeonhd&m=10&y=2008&d=2008-10-29
agd5f: rozzo: bizarre. not sure how adding a modes line would affect an engine hang
yangman: bizzare indeed
rozzo: agd5f, mmm i think the secret is in the message "cannot set the corret resolution"
rozzo: correct*
rozzo: yangman, have this problem?
rozzo: do you have this problem?
yangman: not your problem, which isn't the same as the bug entry you commented on
rozzo: yangman, mmmm but try my solution
rozzo: if the problem is similar
rozzo: asd worked for me :D
rozzo: byez
shivraj: whats the most supported and powerful video card available for linux ?
shivraj: how about one that is supported
shivraj: actually I have an unboard video card that is not supported
agd5f: shivraj: all ATI cards are supported by open drivers. HD5xxx is not yet, but will be eventually
shivraj: agd5f: ok
break19: RHDDRIVersionCheck: drmOpen("radeon", "pci:0000:01:00.0") failed. <-- getting this, also getting "reverting back to shadowfb" - erm: also i have a file named: /dev/.udev/firmware-missing/radeon\x2fRV730_pfp.bin