Yoda--: hi ppl
Yoda--: I have a "Detected an RV610 on a Dell Radeon HD 2400 XT" and a dual output (VGA) using a splitter (is this what is called dualvga?)
Yoda--: I would like to know if there is a way to have xinerama like display (for the moment I have a clone display)
Vanzetti___: good job for this driver !
Vanzetti___: it works well and easyli
Vanzetti___: just something i don't find, how can I make dual screen ?
Yoda--: both screen are detected by xorg (DELL E198FP and DELL E197FP on DVI-I 1 and DVI-I 2)
Vanzetti___: ho xrandr is funny :)
Vanzetti___: good job !
Vanzetti___: thank you
Vanzetti-: i'm back :)à
Vanzetti-: someone is there ?
Vanzetti-: i have a little "problem"
Vanzetti-: all works well, but when I move a window it's a little slow
Vanzetti-: why ?
mjg59: Because there's no acceleration
Vanzetti-: and we can't get it ?
mjg59: Not currently, no
mjg59: If you have an r500, then the radeon driver will provide some acceleration
Vanzetti-: ok, I have a FireGL v3400 (i think it's r560)
gusta1: does r500 work with the readeon driver?
Vanzetti-: but radeon driver doesn't work, i think
mjg59: The atombios branch, yes
Vanzetti-: atombios ?
Vanzetti-: what is it ?
gusta1: "Note that R500/R600 series chips (X1300, X1800 etc) do not have a Radeon 2D core, and are not supported by the "radeon" driver."
gusta1: from the wiki
mjg59: gusta1: That's out of date
gusta1: like everything else on the web, it seems...
gusta1: wow... lots of work there..
Vanzetti-: but does it work with xrandr ?
Vanzetti-: oh cool, i'll try it so !
gusta1: as good as radeonhd? i.e. with dual-head output etc?
mjg59: It should be, roughly
mjg59: But there are always bugs in software
gusta1: i mean, do they interpret the names of monitors/outputs the same, so that my specialized monitor definitions work with the same xorg.conf
mjg59: No clue
gusta1: 'cause from what I've understood, this is up to each driver to decide, and is not central to Xorg (for some weird reason)
Yoda--: any clue for my problem ?
airlied: it supports both old-stlye dual-head and xrandr..
airlied: it doesn't use the same names..
Vanzetti-: and I had another question, if I configure my screens with xrandr, does it save the config if I restart X ?
airlied: it uses the names radeon has always used..
airlied: Vanzetti-: nope..
airlied: you need to configure it..
Vanzetti-: airlied: How ?
gusta1: i won't test it then. i'm so sick and tired of hacking these ugly names in xorg.conf...
gusta1: maybe someone someday in some part of the galaxy, should *standardize* these names... perhaps this is one of the things for randr 1.3
Vanzetti-: airlied: ok in the xorg.conf
Vanzetti-: Well guys ! Thanks a lot for the information, and follow your good work !
Yoda--: mhhh.... Xorg is segfaulting when commenting the Option "NoRandR" "true" line
Yoda--: mhhh... is there any nighly build of radeonhd driver ?
udovdh: do a git pull
udovdh: ndim sometimes makes rpms afaik
Yoda--: oki, would have love a tar.bz2 ;)
Yoda--: wille make my own make dist ;)
Yoda--: much better with latest git pull
Yoda--: while it seems that moving window is WAY more slow
Yoda--: ok my fault have enable a couple of thing to test
Yoda--: speed is now ok
Yoda--: to have dual screen should I hqve only one Screen ?
Yoda--: if yes maximum resolution is 1280x1280 that is too small for left/right dual screen
Yoda--: oki works with virtual :)
udovdh: how did you fix that?
ndim: The console switch really seems to work now.
ndim: libv: Great work! :)
ndim: That makes radeonhd better than radeon gain. suspend/resume: radeonhd OK, radeon fails. VT/X11 switch flicker: radeonhd OK, radeonhd 30% failure rate. backlight brightness change: radeonhd fails, radeon OK.
ndim: I love tradeoffs. :)
udovdh: be back soon...
libv: ndim: great :)
Yoda--: udovdh: I've added the Virtual
Yoda--: as it is explained in radeonhd wiki on xorg page
udovdh: ah, ok
Yoda--: it works fine except that one screen is always at the left of the other
Yoda--: (configuration in Xorg.conf)
Yoda--: I can only switch them by using xrandr (changing configuration in xorg.conf does not have any effect)
udovdh: is tha ta feature?
udovdh: or a bug?
udovdh: various updates to driver since my last pull (ddc hacking..)
udovdh: must compile!
udovdh: the warnings about the GCC extensions are harmless?
ndim: libv: Uhm. I'm sorry, but I still have that flicker-and-broken-sync on switching from X11 to text. But not in 60% of cases any more.
ndim: Not it is more like 5%.
ndim: udovdh: yes.
udovdh: thanks ndim
udovdh: any way to get rid of them?
udovdh: (and not play with -Wall)
ndim: That is code from AMD, and we're trying to change not too much about it.
udovdh: from AMD? oh... must have a look...
libv: udovdh: did you look at the register specs as well?
udovdh: which? where?
udovdh: it might be interesting, but informational?
udovdh: it might give me a clue about modern graphics cards
udovdh: versus ye ole VIC-II in the Commodore 64
libv: udovdh: well, i was going to explain the use of the atombios code in relation to the register specs
libv: udovdh: both are useful in some cases, but it's not a good read for the average onlooker at all
libv: which is what most of the hundreds and thousands of downloaders of the register specifications discovered
udovdh: atombios versus registers is a slightly more `overviewish` way of appraoching this matter?
udovdh: if so: interesting!
libv: none are interesting really
libv: at least, not for a general look
libv: they are good if you need specific knowledge of very specific things
libv: otherwise it is a rather impenetrable maze
udovdh: well, then we must first get some reading on the machine, he chip itself
udovdh: how it works
udovdh: while seeing the registers as buttons and knobs on that machine
udovdh: then, afterwards, we can thread into more detail
libv: udovdh: whatever, it's your time, you do not have to believe me
udovdh: oh, I also readarthur schopfenhauer or whatever is his name
udovdh: and have to deal with peopel still not being able to write proper dutch or simple english at 'higher' places than where I work
udovdh: so I don't mind ;-)
carldani: udovdh: ping
udovdh: carldani, icmp reply ;-)
udovdh: what's up?
carldani: udovdh: sorry for the late answer. you said you have a r6xx chipset?
udovdh: rv630 if I am correct
udovdh: from gigabyte
udovdh: RV630 it is
carldani: udovdh: can I mail a tarball with a first attempt at a linux flashing tool to you?
udovdh: sure; how safe is it?
udovdh: of course I'd rather not wreck the card
carldani: it will only read stuff from registers, most of them known
carldani: it may crash, but it should not wreck
udovdh: crash the program, not the system?
udovdh: ok, take your time
FlyingSpaghetti: when a game uses opengl-type descriptors and sends it to the graphics card, is it rendered by ray-tracing? or is the surface of the object calculated and then only the surfaces facing you are displayed?
udovdh: carldani, I can test your tool tomorrow morning
udovdh: so no hurry, I am in CET (UTC+1)
libv: udovdh: so is carldani :)
carldani: udovdh: to make sure the tool runs on your machine, can you paste (privately) a lspci -vvnn?
Fry-kun: oookay, so I'm back.. trying to figure out how to get my external monitor running on proper resolution
udovdh-afk: carldani done
cockroach: hi. small question: on a dual-monitor setup (both DVI) i get weird, fast moving horizonatl distortions (lines) on one of the displays as soon as a switch from cloned mode to non-cloned (eg. --right-of) with my x1950pro (rv570). any idea?
libv: cockroach: horizontal, or vertical?
cockroach: very thin
cockroach: (maybe 1 pixel)
libv: cockroach: ok, can you mail this in? we can try this tomorrow and see if we can reproduce it with our x1950pro
libv: cockroach: which brand is it?
cockroach: libv: club3d
libv: cockroach: did you run fglrx right before, or did you have a powercycle in between?
cockroach: i'll see whether i can capture the effect with a camera, just for fun :)
cockroach: libv: i had a reboot, not sure whether i did a power cycle
cockroach: but i can try that
libv: cockroach: well, i cannot look into this right away anyway, i am busy reviewing rv670
cockroach: okay, i'll send an e-mail, then
cockroach: power cycle didn't help, btw
cockroach: okay, filed as #13755
libv: cockroach: ok, thanks
rbmorse: Hello! Who am I now?
rbmorse: Ah...I'm me. For a change.
rbmorse: Sorry, still tying to get IRC straight in my head.
nooop: hi all
nooop: the new ati-drivers out
dli: nooop, just another joke :)
nooop: dli, u r right.
nooop: dli, it changes nothing.
nooop: dli, I give up.
nooop: dli, and decide to use radeonhd now.
dli: nooop, try radeon driver also, radeon currently has drm support already
nooop: dli, the radeon support hd2400 ?
dli: nooop, should be, r5xx/r6xxx
nooop: that would be great.
dli: nooop, you need the r500-support branch from mesa/drm also
nooop: dli, okay, that's cool.
nooop: David Airlie is cool