Nightwulf|work: hi all
girrr: I'm having trouble getting the driver to drive my two new monitors correctly and I'm experiencing anomalities and image movements.
girrr: I've tried to specify sync rates manually but that doesn't seem to help
matteo: when the CS branch will be merged into master?
zhasha: I'd kinda like to know if there is any chance what-so-ever to have my X1400 perform close to what it does in Windows because honestly, if not I'm probably never gonna buy ATI again. It was definitely a mistake this time
MostAwesomeDude: zhasha: If you want performance, buy nVidia, but don't be surprised when you get subtle instabilities.
MostAwesomeDude: Also, yes, we're getting quite close to Win32/fglrx levels of performance. Please be patient.
zhasha: My friend with a GeForce 5100 has better performance than me
zhasha: and I am using fglrx currently but due to a bug thats been in the latest 3 versions (8.6-8.8) I'm using a patched version 8.5
zhasha: or the screen will corrupt completely when using pretty much any 3d application
MostAwesomeDude: Have you tried Mesa 7.1?
zhasha: no I have not. I only learned of it yesterday
MostAwesomeDude: Ah.
zhasha: I'm not that demanding. I'll take simple features like the ability to watch video while running compiz, but fglrx can't do that either
MostAwesomeDude: So, when you say "perform close to Windows," you mean, "has 3D acceleration." :#
MostAwesomeDude: Yeah, Mesa 7.1 has acceleration for your card.
zhasha: well I'd prefer having Windows like performance
zhasha: but I'll settle for a lot less
MostAwesomeDude: I've got xf86-video-ati 6.9, Mesa 7.1, and Xserver 1.5, and everything works. Games, compiz, mplayer, etc.
zhasha: So should i check Mesa out of git?
MostAwesomeDude: Well, you don't need to; Mesa 7.1 packages are already out.
MostAwesomeDude: Which distro are you on?
zhasha: Arch
zhasha: its in testing i see
MostAwesomeDude: Ah. Um, you'll have to ask the Arch guys for a pkgbuild.
MostAwesomeDude: Also, make sure you've got kernel 2.6.26 and libdrm 2.3.1, or you won't get very much speed.
zhasha: aw snap. libdrm is only 2.3.0
MostAwesomeDude: I'm sure you can find an updated build somewhere.
MostAwesomeDude: needs to try Arch at some point
zhasha: would i need to have Xserver 1.5?
MostAwesomeDude: Only for AIGLX.
MostAwesomeDude: And the only thing (that I know of) that needs AIGLX is compiz.
zhasha: Xserver 1.4.2 has AIGLX?
MostAwesomeDude: Yeah, but it's not going to work with Mesa 7.1. (Or, at least, nobody's gotten it to work.)
MostAwesomeDude: The AIGLX API has changed a bit.
zhasha: ugh, so I will need to update that too at some point :P
zhasha: does mesa need to link against Xserver?
zhasha: stupid question...
MostAwesomeDude: No, Xserver opens a DRI module itself during the AIGLX startup, so Xserver can call DRI stuff directly.
MostAwesomeDude: That's how it accelerates indirect GLX calls.
zhasha: So will direct rendering be available if I use mesa?
MostAwesomeDude: Yeah.
zhasha: Looking at the pkgbuild here: --with-dri-drivers=swrast
zhasha: I get the feeling I'll need to change that
MostAwesomeDude: Direct rendering: App -> Mesa -> DRM -> Card
MostAwesomeDude: Yeah, try --with-dri-drivers=swrast,r300
zhasha: my card is r500
MostAwesomeDude: Indirect rendering: App -> Xserver -> DRI -> DRM -> Card
MostAwesomeDude: zhasha: r3xx, r4xx, and r5xx cards are in the r300 driver. :3
zhasha: I guess I have a valid excuse for not understanding this before
zhasha: --disable-ttm-api <- is what?
MostAwesomeDude: Disables TTM. Old memory manager, not needed.
zhasha: and finally: --disable-glut
MostAwesomeDude: Most systems like to use freeglut instead.
zhasha: oh, so mesa comes with its own glut version?
MostAwesomeDude: Yeah.
MostAwesomeDude: But, really, any GLUT will do.
MostAwesomeDude: They've all got the same API.
zhasha: well I don't use GLUT
MostAwesomeDude: Mm, you probably have programs that use it. It's not a big deal, though, because you probably already have freeglut.
zhasha: indeed i do
zhasha: okay I'm starting the make
MostAwesomeDude: And, http://mesa3d.org/relnotes-7.1.html
MostAwesomeDude: To do: Switch to freeglut :3
zhasha: checklist: libdrm 2.3.1, mesa 7.1
MostAwesomeDude: kernel 2.6.26
zhasha: got it already
MostAwesomeDude: xf86-video-ati 6.9 or xf86-video-radeon ???
zhasha: got it looong ago :)
MostAwesomeDude: *radeonhd, even.
MostAwesomeDude: I don't know which radeonhd version you need for DRI.
zhasha: i built a git version of radeonhd yesterday
MostAwesomeDude: Ah, okay, that should work.
zhasha: but it's gonna be deleted
zhasha: son of a... I'll need xf86-video-ati 6.9 too
MostAwesomeDude: Well, one or the other. I personally recommend -ati, but yeah.
zhasha: seriously I should just enable testing :P
MostAwesomeDude: Be back in ~15.
zhasha: thanks a lot for the help
teite: hi
teite: any suggestions regarding (II) RADEONHD(0): The detected amount of videoram exceeds the PCI BAR aperture?
teite: how can i use 3c accel feature?
MostAwesomeDude: teite: Which card?
MostAwesomeDude: zhasha: How's it going?
teite: ati x1650
MostAwesomeDude: teite: Get Mesa 7.1, libdrm 2.3.1, kernel 2.6.26, and a recent xf86-video-ati or xf86-video-radeonhd.
teite: what about xorg?
Gatonegro: Hello everyone. I'm trying to set up DRI (for Compiz) in my iMac with Debian (ATI Radeon X1600), but without success. Is this supported? Can anyone help with the setup?
MostAwesomeDude: teite: Xserver 1.4 or newer. 1.5 if you want AIGLX and compiz.
MostAwesomeDude: Gatonegro: PPC?
Gatonegro: MostAwesomeDude, Intel, the first generation.
Gatonegro: MostAwesomeDude: http://apple-history.com/?page=gallery&model=imac_coreduo&performa=off&sort=family&order=DESC
teite: MostAwesomeDude: its 1.4.2, well i'm more concerned about the PCI BAR aperture stuff
MostAwesomeDude: teite: Try -ati. :3
teite: after some infighting i got to run a dualscreen setup ;)
MostAwesomeDude: Gatonegro: I don't know if radeonhd supports compiz. Does anybody know?
teite: MostAwesomeDude: dont understand that -ati :3 ;)
MostAwesomeDude: teite: xf86-video-ati, sorry.
yangman: Compiz is kinda supported. YMMV, though
teite: who needs compiz :)
Gatonegro: yangman, What is required to run it?
yangman: I *think* I had it working at one point, but something was buggy and I didn't stick with it
MostAwesomeDude: compiz requires AIGLX, which means Mesa 7.1, Xserver 1.5.
MostAwesomeDude: Works beautifully with xf86-video-ati here on my X1700 and X1950. :3
yangman: Gatonegro: do you have DRI working at all atm?
Gatonegro: yangman, No --- that was my original question. I can't get DRI to work.
teite: well i have debian/lenny, and would rather stay with xorg
MostAwesomeDude: teite: Xserver is part of Xorg.
MostAwesomeDude: ...Gotta go
Gatonegro: yangman, How can I check which Mesa version I am running?
yangman: Gatonegro: mesa-7.1, 2.6.26 kernel, libdrm 2.3.1, xorg-server-1.5 (and dependencies) and radeonhd from git
teite: do i need a kernel module for dri with radeonhd?
yangman: Gatonegro: if you don't already know, you're not running a new enough version. 7.1 was released just last week, and I'm not aware of any distros that put 7.1rc* into stable trees
Gatonegro: yangman, Ah, radeonhd from git.
Gatonegro: yangman, I am running Debian Sid, and I just did a dist-upgrade today.
yangman: teite: yes, the r300 DRI module
Gatonegro: yangman, But I will check.
teite: yangman: thx gonna check ;)
teite: what about libmesa-drm?
Gatonegro: yangman, Hurm. Seems that I am running Mesa 7.0.
yangman: teite: I'm going to say yes. I've no idea how distros package these things
teite: debian/lenny has mesa 7.3
Gatonegro: teite, Strange. How do you check that?
zhasha: it runs fairly well but there is a rendering bug in gtk
teite: Gatonegro: apt-show-versions | grep -i mesa ;)
teite: xlibmesa-gl/lenny uptodate 1:7.3+15
teite: but maybe i'm wrong
teite: thats just a transitional package
teite: real libmesa seems to be 7.0
Gatonegro: teite, That's what I thought. :o)
Gatonegro: Well, I think I will wait till 7.1 makes it into Sid, and then try to compile radeonhd from git.
Gatonegro: Thanks all!
teite: yangman: any ideas why radeonhd only uses 256mb of 512mb from the video ram_
teite: ?
teite: (II) RADEONHD(0): Using only 262144kB of the total 524288kB.
glisse: teite: pci bar are often limited to 256Mo or 128Mo
teite: and what about: (WW) RADEONHD(0): rhdAtomAllocateFbScratch: FW FB scratch area 536850432 (size: 20480) extends beyond available framebuffer size 268435456
yangman: teite: just means the driver itself can't address the entirety of video ram. it's a non-issue; the hardware will still access it fine
teite: glisse: can i change that somehow?
glisse: so cpu can only view 128Mo or 256Mo depending on bar restriction
glisse: teite: no
glisse: teite: but with memory manager such kind of limitation won't matter
teite: (II) RADEONHD(0): Cannot get VRAM scratch space. Allocating in main memory instead
teite: what does that mean_
teite: ?
teite: nothing to concern about? :)
yangman: if it's not (EE), don't worry about it ;)
glisse: i don't know enough radeonhd to know when and why it does print such message
glisse: anyway given today driver 256Mo shopuld be more than enough
teite: yangman: ok
teite: just sad that dri isn't working, zattoo doesn't run anymore
teite: it worked with the internal shared i910 :(
cxo: There is a bug, which causes the Xserver to freeze when you issue, shutdown/reboot
cxo: Its definitely due to the ati video card/driver
cxo: since i didnt have it with my nvidia card
cxo: I built everything (X, radeonhd, mesa, drm, 2.6.27rc5 etc..) fresh out of git last weekend, and the bug is still there
cxo: This bug doesnt exist with the vesa driver
cxo: It also exists with the closed source fglrx driver
cxo: heh.. nice to see fglrx and radeonhd share the same bugs :)
Obscene_CNN: or your hardware has a bug
cxo: (fedora 9 x86_64, hd4870)
cxo: Windows shuts down just fine
cxo: brb
dudeman: hello
cxo: ola
dudeman: I am using this driver on debian/lenny and even though my native resoultion is 1680x1050 I can't get past 1024x1200 according to xrandr
dudeman: any troubleshooting tips/advice?
cxo: what do you mean "can't get past" (you mean passed?) does it crash or something when you change res?
dudeman: never shows up
dudeman: here
cxo: when you type, xrandr it doesnt show up?
dudeman: http://paste.debian.net/16701/]
dudeman: http://paste.debian.net/16701/
dudeman: its supposed to be 19xx-12xx and native it runs at 16:10
dudeman: but those modes never show up
dudeman: http://paste.debian.net/16702/ <-- xorg.conf
dudeman: Package: xserver-xorg-video-radeonhd (1.2.1-2)
adamk: dudeman, You can add new modes via xrandr, too.
cxo: hmm could be bad EDID info, not sure, do you have the same problem with the "radeon" or "ati" driver?
dudeman: yes sir
dudeman: both radeon and radeonhd give problem
dudeman: same problem
adamk: dudeman, You can use cvt to create a modeline, and then use "xrandr --newmode" and then "xrandr --addmode"
adamk: dudeman, Or you can add the mode directly to the Monitor section of your xorg.conf file.
dudeman: Modeline "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync
dudeman: like th is?
dudeman: ok
dudeman: I will use xrandr
yangman: dudeman: post your xorg.log as well
dudeman: ok
adamk: Yes. Add that to the Monitor section of your xorg.conf file (assuming you have only one monitor) and then restart X. That mode should show up in the xrandr output.
adamk: Or you can create that mode with xrandr and then bind it to the port on your video card that you are using.
dudeman: http://paste.debian.net/16703/
dudeman: i don't want to keep restarting
adamk: Probably completely unrelated to the resolution issue, but you seem to have fglrx installed and the kernel module loaded,.
yangman: dudeman: you seem to still have the fglrx module loaded. make sure that's unloaded, and isn't loaded automatically first
yangman: dudeman: it causes issues
dudeman: oh ok
dudeman: no luck
dudeman: Modeline "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync
dudeman: this is in my monitor section of xorg.conf
dudeman: I do xrandr and this mode does not show up
adamk: Did you restart X?
dudeman: yes
adamk: Hmmm...
dudeman: I also modprobe -r fglrx
dudeman: and restarted X
adamk: Very odd. I thought that's all you needed to do to force a mode to show up.
yangman: dudeman: you need to do a reboot
yangman: dudeman: can't trust fglrx to leave the card in a good state
dudeman: hey dudes
dudeman: good luck
dudeman: I mean
dudeman: I had the good luck. I changed from radeonhd to radeon and now my resolution is ok
dudeman: but I have the debian lanny and the 1900xt video card r500 is it possible to run a compiz?
adamk: dudeman, Not without updating a lot of packages.. In fact, I would guess that most of what's needed is not available packaged for Debian at all.
dudeman: its ok
adamk: If you are not using kernel 2.6.25 or higher, you need to update the DRM kernel modules. You need at least 7.1, and probably Xserver 1.5
dudeman: I can try to build from source/git
adamk: Errr... Mesa 7.1
dudeman: uhhuh
dudeman: well debian lenny is close to sid and I been on sid for 7 years but that machine has a old card works on 3d with oss ati
dudeman: but you have maybe a link or guide on how to build from git so i can get maybe 3d?
dudeman: I meah ow hard could it be
dudeman: you tupe a few commands and let it build and if it works it works, if not no big deal
dudeman: last time few months ago I tried to compile from git but it had problems, man pages was missing and the whole thing wouldn't compile
dudeman: btw
dudeman: for the xv mplayer video driver output, do you need to enable zoom=yes?
adamk: dudeman, One second.
adamk: dudeman, This is the only one I know about http://www.x.org/wiki/Development/git
adamk: dudeman, For xv, you do not need to enable zoom=yes
adamk: dudeman, You do need that for scaling with the x11 output, though.
dudeman: I see thats the one
dudeman: ok cool thanks my stomach hurts i'll probably do it after I go to bathroom
dudeman: thanks man
Necos: i managed to get 3d acceleration working with the new dri driver and mesa... but for some reason, quake4 is using s3tc, which, from what i read, is software mode...
Necos: hmmm, wait a second... it's a texture compression... oops
dudeman: hey
dudeman: I'm at the same problem again i restarted X and now i can't get my resolution again
dudeman: radeon/radeonhd both won't go past a small res, while I have a proper modeline from before
dudeman: xrandr still doesn't show the mode
Necos: ?
Necos: what you mean it's not going past a small res?
Necos: what does your xorg.conf look like?
dudeman: no matter which driver of the two I use
dudeman: and with the proper modeline generated with cvt
dudeman: I can't get it to go past 1024x768
Necos: notes that wasn't the question he asked
dudeman: my monitor is natively 16:10 resolution
dudeman: Necos, you asked me 2 questions
dudeman: wait for the 2nd answer
Necos:
dudeman: http://pastebin.com/deab126b
Necos: use pastebin.ca please :(
dudeman: use whats been pasted already
dudeman: if you don't want to help me nicely no problem
dudeman: I'm already frustrated enough as it is
dudeman: kindly don't add to it.
Necos: pastebin.com is blocked by my job, that's why
dudeman: ok
dudeman: http://pastebin.ca/1197444
yangman: dudeman: is fglrx unloaded properly now?
dudeman: yes
dudeman: not that it has anything to do with it
dudeman: I modprobed -r that long ago
yangman: did you reboot?
dudeman: I switched to radeon driver, retarted X, my resolution came up fine
dudeman: I had to restart X, get back into X, and no more native res
dudeman: I tried to switch to the radeonhd driver again
DeadToo: you really do need to reboot after unloading fglrx
dudeman: no luck, switch back to radeon, no luck
yangman: but, did you reboot?
dudeman: no I did not
DeadToo: do that
yangman: 10:28 < yangman> dudeman: you need to do a reboot
dudeman: are you joking?
dudeman: you are asking me to restart a linux machine?
dudeman: to unload a module?
dudeman: !?
DeadToo: no, fglrx does not leave the card in a proper state for readeon/radeonhd to take over
yangman: no, to reinitialize the hardware
yangman: I also said that 2 hours ago
dudeman: ok
dudeman: I must have missed it
dudeman: let me try
yangman: make sure fglrx doesn't get loaded automatically
Temujin_: blacklist the b!tch
dudeman: fglrx isn't installed
dudeman: radeonhd is still giving a problem
dudeman: just like last time
dudeman: 'radeon' driver gives me a 16:10
Temujin_: blacklisting fglrx is therapeutic though
dudeman: I switch to radeonhd
dudeman: restart X
dudeman: voila, fuckup again
dudeman: :(
dudeman: so what is the real diff between radeon and radeonhd
dudeman: which one is for my X1900 XTX r500
dudeman: ?
yangman: different modesetting code
dudeman: apparantly radeonhd seems to give me issues while radeon makes it work
yangman: post your xorg.log again please
dudeman: ok
DeadToo: I think radeon should be the most stable for your card
dudeman: http://paste.debian.net/16715/
dudeman: I'd use fglrx cuz of 3d
dudeman: but debian sid has a problem with the packages right now
dudeman: reported bug which I am experiencing
yangman: xorg.log. you put up .conf there :)
dudeman: oh
dudeman: sorry my bad the log file is too big how to paste it
dudeman: it gets truncated
yangman: it shouldn't be that big on a fresh boot
yangman: how big is it?
dudeman: http://paste.debian.net/16717/
dudeman: nm
dudeman: i fit it
yangman: that one's for radeon
dudeman: yeh
dudeman: i just started X as radeon
dudeman: you wanted one for radeonhd
dudeman: ok i'll do it later
dudeman: let me enjoy my resolution while it lasts
yangman: yeah, I can't help you with radeon
dudeman: thanks a bunch buddy
dudeman: btw
dudeman: women suck
dudeman: mumbles incoherently about his woman
dudeman: leave me alone woman! I'm trying to fix a comptuer
dudeman: oof!
dudeman: bye bye guys
Necos: lol
sytse: dudeman.. dude-man... dude man... mandude.... hmmmmmm... what is he, a man, a dude, a dudedude, a manman, or both? Or all four? Or none of the above.. maybe he could be overcompensating for not being a man, by stating that he is -twice-, in his nick no less..
sytse: some things just make a man wonder.
sytse: ah well
sytse: time to get some sleep :)
yangman: sytse: sounds like you need it ;)
sytse: ;)
sytse: let's just keep it at that it's the beer ;-)
sytse: btw, that wasn't rambling incoherently, what I did just now.. it might -seem- like rambling to the untrained eye, but actually it was quite a thorough theory, stated in just one line
sytse: ..
sytse: oh jeez
sytse: I -do- need that sleep ;-)
sytse: later
Darth753: Hi there!
Darth753: I'm having some problems using RadeonHD with a Mobility HD3450
Darth753: Install, edit xorg.conf, reboot, but when the X server gets initialised I get a black screen which gradually turns white in weird patches
Darth753: the only error in Xorg.0.log is
Darth753: (EE) RADEONHD(0): RHDVGASave: VGA FB Offset (0xC0000000) is out of range of the Cards Internal FB Address (0xE0000000)
Darth753: can anyone help?
ndim: Darth753: Is your radeonhd version current?
matteo: Darth753: intel mobo?
matteo: i have this on two laptops
matteo: an intel gma915
matteo: and a radeon x1600 with an intel 945 mobo
Darth753: radoenhd is fresh from git
Darth753: let me check the mobo...
Darth753: yeah, intel mobo
Darth753: intel 965 PM/GM express
matteo: maybe it's a chipset isssue, who knows
matteo: but I have it with an intel VGA as well
matteo: Darth753: does all gets blank except the borders?
matteo: screen is black and then goes gradually white
matteo: from center
matteo: leaving only the corners black?
Darth753: well, mine starts in the top left
Darth753: then one or two other patches appear
Darth753: i've never left it long enought to let it get fully white
Darth753: chipset seems probable, but then with the intel card...
Darth753: what driver are you using for it?