psteyn: anyone know if support for 4850/4870 is implemented yet?
m-c_: psteyn: The wiki says no
m-c_: Keep checking it, and I am sure the status will change soon.
psteyn: ive checked the wiki now, soz for asking first
walder: hi, is there anybody who can help me with radeonhd loosing sync sometimes ?
walder: emmes: hi, here ?
rafi: What's the current status on rotation support
rafi: I have a tablet with a x1250, and I'd like to do what I can to get that working
aneas: i'm using radeonhd-git with my ati mobility x1700 (r500, M66), a 1280x800 laptop panel and a 1680x1050 external dvi monitor. because of the different vertical resolutions i have some invisible area below the smaller monitor. is there any way right now to get rid of it or at least block it for the cursor?
aneas: xserver 1.4.2
aneas: i wrote a small app that prevents the mosue cursor to enter that area, but something tells me thats not the way it should be done
g-zu: aneas I can't figure out what you were trying to say
g-zu: can you be more descriptive
aneas: ill make a screenshot
aneas: not exactly a screenshot, but this is what i mean:
aneas: i dont see the black area
aneas: but i can click on it
aneas: g-zu *highlight* :)
agd5f: aneas: randr should take care of it and prevent the mouse from going there
aneas: randr 1.2
aneas: do i have to setup randr to do this?
agd5f: aneas: no. should take care of this by itself
aneas: no errors in Xorg.0.log and the only warning is:
aneas: (WW) RADEONHD(0): DRI support has been disabled at compile time
agd5f: although it looks like radeonhd doesn't hook in any of the xrandr crtc cursor functions
aneas: and (WW) RADEONHD(0): No monitor size info, assuming 96dpi.
agd5f: aneas: unrelated
aneas: this is quite important for me, so should i try video-ati instead?
agd5f: aneas: it should work
aneas: then i must be doing something wrong
agd5f: aneas: ati should work. I need to check radeonhd. the problem may be that it doesn't register randr crtc cursor hooks
aneas: ok, thank you
aneas: agd5f, now thats interesting ... ati driver doesnt constrain the cursor either
aneas: if it should work, is there any way i could provide information to solve this?
agd5f: aneas: what window manager are you using?
agd5f: does openbox support xinerama hints?
agd5f: you might try metacity or another wm with xinerama support and see if it works there
aneas: yes, it supports xinerama
aneas: agd5f, same with metacity :/
dvandyk: aneas: i used to have the same problem with kde and 2 monitors with different resolutions. that was on -ati though, not -radeonhd
dvandyk: aneas: and: when i tried to maximize a window, it was spread across the whole of both monitors, including that black area.
agd5f: aneas: are you using gentoo by any chance? if so, make sure you add xinerama to your build flags
udovdh: why use xinerama?
udovdh: I was told that is old
udovdh: and it works without xinerama and xrandr
buggs: udovdh, how that?
udovdh: xinerama being old?
udovdh: or dual mons and xrandr?
udovdh: my other pc, like this one, has a HD2600pro
udovdh: but the otehr one has dual screens
udovdh: and they work well
udovdh: as one big desktop
agd5f: udovdh: randr announces xinerama geometry hints for window managers
agd5f: nothing to do with the xinerama protocol for combining screens
udovdh: didn't know that
udovdh: but do I need it?
udovdh: and is it automagically enabled when building from git?
udovdh: (yes, I am not a developer)
agd5f: udovdh: yes. gentoo has the option to build various X apps with xinerama support without it
udovdh: I am not on gentoo
udovdh: but build from git on Fedora
agd5f: udovdh: you should be fine
frojnd: hello anyone here uses radeonhd drivers ?
m-c: I sure do
frojnd: I have r5xx chipset
frojnd: and somehow when I watch movies there is flickering and pricture isn't sharp..
frojnd: how can I check what version of ati drivers do I have and if it's borken ?
m-c: How did you install them?
frojnd: m-c: they were installed with suse 11 but then I added ati's repo and I've installed 2 more packages for ati
m-c: Your X log will tell you what drivers you are using, if the SUSE tools do not.
frojnd: m-c: I think I use radeonhd, but correct me if I'm wrong: http://pastebin.com/m1c1e1c7d
frojnd: m-c: With default installation I had: radeonhd driver installed, but than I've added ati's repo and I've installed those 2 packages: installed ati-fglrxG01-kmp-pae x11-video-fglrxG01 Did I messed something ? :S
yangman: frojnd: the flickering is most likely due to the frame refresh not maching the monitor refresh. there's not much you can do there, as vsync tweaking isn't something that's handled yet, iirc
yangman: frojnd: as for image quality, that shouldn't have anything to do with the driver, as it doesn't have support for video acceleration yet
frojnd: there is nothing I can do about flickering and/or image quality
yangman: frojnd: depends on your media player, I suppose. there's no hardware video decoding/acceleration involved, so if there is a solution, it's somewhere in the application stack
yangman: that, or the video itself has some issues
frojnd: yangman: I'll try VLC now
frojnd: What about those 2 packages I mentioned ?
yangman: I don't run Suse, so I have no idea what those are
yangman: if you do have fglrx installed, though, make sure it's not being automatically loaded
yangman: having fglrx loaded will do bad things to radeonhd and radeon drivers functioning properly
frojnd: yangman: where can I do that ?
frojnd: I don't wanna have fglrx, just radeonhd or raden
yangman: in that case, just uninstall it
frojnd: yangman: I will
frojnd: fglrx isn't open
m-c_: I uninstalled all the video drivers except VESA (for fallback) and radeonHD. Works okay here. (Hope I never have to switch video cards. :)
frojnd: m-c_: what card do u own ?
frojnd: well I have to reboot comptuer since It downloaded new kernel due to deleting the fglrx driver
frojnd: I heard somewhere that radeon driver supports a little 3d for r5xx chipsets ?
frojnd: what's the name of the package for raden... now I have radeonhd but I'd like to try radeon too
m-c_: Read the wiki - all your questions answered there
frojnd: let see if fglx was the reason for flickering and bad quality
frojnd: nop :S
frojnd: How cacn I help improving of drivers, with just using it ?
frojnd: Because I really wish to have good drivers.
yangman: testing, filing bug reports, etc
buggs: udovdh, i meant dual screen without xrandr, how that?
frojnd: yangman: well I don't know if this is a bug that I have flickering and bad image quality...
frojnd: yangman: does pasting x log helps ?
yangman: frojnd: well, you need to be more descriptive than that
yangman: does it happen with all video files?
yangman: what's the media player? media player options? does it happen with the radeon driver? etc, etc
yangman: and what do you mean by "bad image quality"?
frojnd: yangman: 1) all 3 players I have (kaffeine, mplayer, vlc) with different settings, don't know if I tryed all diff settings but most of them. 2) bad qulaity is with formats like: avi (all kind of xvids...) DVD, BUT not HD, .mkv files... flickering is however with all files.... 3) I haven't tryed radeon driver - don't know the package name of it. 4) bad image quality like image isn't sharp, clean as it should be the pixels can
udovdh: I use dual screens w/ xrandr. why avoid it?
yangman: fullscreen or windowed?
yangman: frojnd: also, if "bad quality" doesn't apply to HD, I think you're expecting too high of a quality from your media files
frojnd: yangman: just fullscreen
yangman: so no flickering in windows mode?
frojnd: yangman: no :) before I upgraded to suse 11 I had fglrx drivers from ati home page and there wasn't any "bad quality"
frojnd: yangman: no flickering in windows mode
yangman: right, but with fglrx, the media player would have been running in a completely different rendering path
yangman: through Xv
frojnd: yangman: yes just to tell, that videos aren't "normal"
frojnd: yangman: that iamge isn't clean, squares little tiny squares can be seen..
yangman: those are called artifacts
yangman: and it's entirely normal
frojnd: yangman: oh..
yangman: depending on the codec and compression level used
frojnd: the moment I resize window's player I get those articats
yangman: you always have them
frojnd: yangman: yes I have artifects :S
yangman: it's just that they're not always noticible at closer to actual video resolution
frojnd: yangman: no just now when I'm using radeonhd drivers
yangman: trust me on this. if it's mpeg compressed in a reasonable way, there will be artifacts ;)
yangman: very, very small ones, but they'll be there
frojnd: yangman: ok :) but it's the drivers I think..
yangman: no, no it's not
yangman: that's what I've been telling you
da1l6: what about testing with fglrx and video output set to x11?
da1l6: that will show if its a driver issue
frojnd: da1l6: there is no artifects with fglrx..
frojnd: I've just moved to radeonhd :)
da1l6: but with fglrx it uses Xvideo output
da1l6: that means there are (at least) TWO changes. it can't be said which one causes the problems
frojnd: what if I would first try radeon drivers ?
frojnd: I've also just deleted the fglrx drivers
da1l6: why not
frojnd: is radeon in suse 11 ?
frojnd: for radeonhd drivers, the name of the package is xorg-x11-driver-video-radeonhd
frojnd: and if I search for raden, I only get radeontool, rovclock and xorg-x11-driver-video-radeonhd
da1l6: not using suse. maybe its -ati
yangman: it should be xorg-x11-driver-video-ati, then
yangman: also, what's the original video size for the videos that you see artifacts after resizing?
frojnd: yangman: RESOLUTiON : 640x352
frojnd: xorg-x11-driver-video-ati can't be found :S
libv: frojnd: it's in the main video drivers package
libv: frojnd: only unichrome and radeonhd are separate rpms
frojnd: libv: in the main video drivers package ?
libv: i just said: 18:35 < libv> frojnd: it's in the main video drivers package
libv: so _yes_
frojnd: xorg-x11-driver-video-ivtv - The X11 video driver for the PVR-350 frame buffer
frojnd: when searching for video driver ?
frojnd: could that be it ?
libv: frojnd: did you install X when you installed opensuse 11?
frojnd: libv: no, it came with correct resolution
libv: frojnd: if so, the main package is installed.
libv: frojnd: ?
libv: this is where i give up.
frojnd: is something in general wrong with xorg.conf ? http://pastebin.com/m29a90b5
BigBrain: hi Tch23 :D
aneas: agd5f, 3 hours ago you commited a change for randr crtc. anything connected to my problem and should i retest? (dual head with different resolutions)
agd5f: aneas: nope not related
Tch23: Hi i'll make the same joke
Tch23: than the other channel
Tch23: Guess what? I got a problem with radeonHD drivers!
Tch23: I'm on fedora 9 with an ATI radeon mobility X1300
Tch23: i installed the radeon HD from the official repository
Tch23: And nothing happend...
Tch23: even after a reboot
m-c__: Did you modify your xconfiguration?
m-c__: Read through the wiki -- see if it helps
BigBrain: Tch23: what do you mean with "nothing happened"?
Tch23: I guessed that I should do such thing
Tch23: but no
BigBrain: the X server did not start, or there were no changes?
lupine_85: you should s/[fglrx|ati|vesa|etc]/radeonhd/
m-c__: Check your log to make sure you are using the driver you think you are
BigBrain: Tch23: /var/log/Xorg.0.log
BigBrain: just do a case insensitive fulltext search for "radeonhd"
Tch23: Thanks I really love people who make clear explanations with the exact line
Tch23: One day i'll be yours!
Tch23: among you
Tch23: not not
Tch23: fuck, I'm french
Tch23: Well you were right, I don't have any radeonHD in my log
lupine_85: I, for one, welcome our new French underdogs
BigBrain: Tch23: /etc/X11/xorg.conf <-- search for the "Device" section and check the "driver" line ;-)
BigBrain: though it's possible that there are multiple device sections
Tch23: I got a frelling lot of "device" an "driver"
Tch23: a ok
Tch23: forget that
Tch23: driver : radeon
Tch23: should I put radeonhd?
m-c__: How well do you expect the radeonHD driver to support openGL 2.0 or even the potential of a new openGL 3.0 ?
lupine_85: as well as mesa does
lupine_85: aiui, they're just missing shaders?
m-c__: Are enabling those specifications tied to the radeonHD, or independent?
Tch23: let's restart X!!!!
lupine_85: or a specific type of shadeR?
BigBrain: Tch23: good luck Tch23!
lupine_85: m-c__: no, all (well, sort of) the drivers use mesa for their OGL
m-c__: Thanks lupine_85
Tch23: Hi again
BigBrain: does it work?
Tch23: I don't know but my system ain't screwed
Tch23: that's a good point
BigBrain: just take a look at /var/log/Xorg.0.log again
m-c__: and what does your log file say?
BigBrain: Tch23: yeah, whenever I tried out a new fglrx version I was happy when I could at least start the x server itself
Tch23: When you get only the terminal that's so frustrating
BigBrain: Tch23: Oh, then you could at least immediately check what's wrong
BigBrain: Tch23: whereas a hardlock is really just _frustrating_
Tch23: well what should I see in my log?
BigBrain: radeonhd, somewhere
Tch23: I see it
BigBrain: That's good :D
Tch23: many many times
BigBrain: That's even better
Tch23: But if I set my terminal to have an hollow background, my graphic card dosn't seem to follow
Tch23: I mean that I have a little lag and I don't see the windows, only the background...
Tch23: It dosen't look good, ain't it?
da1l6: this is "faked" transparency
da1l6: it just grabs the backgound image
Tch23: yeah but it lags
Tch23: how can I see the performances?
BigBrain: Tch23: guess that's normal as the background image is not updated very often
Tch23: anyhow desktop effects won't start
Tch23: I don't even know if it changed something
Tch23: but you were really efficiente
da1l6: radeonhd stable releases don't support any 3d
da1l6: thus no compiz
Tch23: I just don't want my CPU to be over loaded by graphical stuff
BigBrain: okay, I'm off then
BigBrain: cya all
Tch23: Well I'm glad to see that this IRC channel is kind and alive
frojnd: anyone here have R5xx chipset ?
frojnd: r5xx chipset
hellsing: yes frojnd , i've got one
hechz: quick question, Are DRM and FrameBuffer support mutually exclusive?
airlied: hechz: like all things it depends.
airlied: kernel based modesetting should let you have both.
hechz: That is what I thought...
airlied: you can do both now, I've used it before, but its a house of cards.
hechz: rhgb quiet vga=0x31b video=radeonfb:2560x1024-24@75,map:01,dfp splash
hechz: -that seem valid?
airlied: hechz: radeonfb? that won't do anything on a radeonhd supporting card
dmb: indeed it won't
dmb: you would have to stick to vesa
hechz: Ok, I wasn't sure how the various radion projects were inter-related. If at all
dmb: have fun finding the correct mode though :P
dmb: airlied, does anyone maintain radeonfb anymore?
dmb: i say it should be removed :/
hechz: Yeah getting the FBDev etc support working was fun
airlied: dmb: radeonfb will be removed when we have radeon kernel modesetting
hechz: None of the framebuffer support is documented very well...
hechz: I'll switch over to the vesafb driver and see if that makes things a bit better
hechz: donkey churn.
hechz: (danke schön)
airlied: hechz: setting vga= uses vesafb
dmb: i was able to get vesafb working, can't remember which mode i used
yangman: works okay-ish here on uvesafb, although I didn't discover the option that makes it work for months
dmb: some weird non-standard resolution
hechz: that I can fiddle with that bit.
airlied: radeonfb is mainly just there for powerpcs really
dmb: you are forced to use that
dmb: i don't think there is any way not to use a framebuffer console driver in mac ppc world
hechz: That is quite true...
dmb: airlied, so you cannot use X with the vesa driver, or any basic vga driver with ppc mac at all?
airlied: dmb: nope.
agd5f: there's offb