MrCooper: hi peterz, thanks for your help with tracking down those 2.6.24 scheduler issues
peterz: MrCooper: Sure, no problem
MrCooper: any idea if the fixes will make it to 2.6.24.x?
peterz: MrCooper: no, I guess they might be candidates for a .1, but I don;t know if/when gregkh will spin one
ciss0r: im having a problem with xorg radeon driver.. its not reading my modes and defaulting my screen to something like 800x600 and no matter what i do my gui and text stays huge
MrCooper: ciss0r: with RandR 1.2 you need to associate modes with a monitor section and that with an output
ciss0r: ok well i thought i had it like that
berniyh: i managed to switch over to the open source driver, took me some time to get familiar with xrandr 1.2, but it works now
berniyh: but i have a problem, on my external monitor a bit (about 5-10 px) is cut off on the right side
berniyh: or actually i think the output has moved a few pixels to the right
berniyh: ah, wait, it works now
berniyh: thank you for the good work on that driver ;-)
dcotruta: hello all
dcotruta: any ideas of radeon supports the ES1000 embedded chipset?
agd5f: dcotruta: yes, it does
dcotruta: agd5f: you still there?
dcotruta: agd5f: this is the thing of it: when I use the radeon driver in my X config, I get a super bright, washed out screen
dcotruta: I don't really know what the problem is, or what Option I could set to fix it
agd5f: dcotruta: what version of the driver are you using?
dcotruta: agd5f: the resolution is right, but I can barely see anything, unless I switch to VESA
dcotruta: agd5f: forgive my idiocy, but I don't know - I originally tried the one that comes with fedora 8
dcotruta: then I tried the one from livna
agd5f: dcotruta: it should say in your /var/log/Xorg.0.log
loswillios: should be printed in /var/log/Xorg.0.log
dcotruta: let me have a quicky look there then
dcotruta: agd5f, loswillios: I will have to enable the driver - I'm just going to sign on to another machine so I don't lose the session when I restart X
loswillios: screen usually helps a lot :)
dcotruta_: loswillios: i know, I know,
dcotruta_: right, X has restarted
dcotruta_: is it the part that says X.org video driver?
dcotruta_: that says 1.2
loswillios: should something like 6.6.* or 6.7.*
agd5f: it'll be 6.7.*
dcotruta_: ah right
dcotruta_: and indeed there is the ES1000 on the list
dcotruta_: but why this messed up screen?
dcotruta_: and what can I try to do to fix it?
agd5f: dcotruta_: there was a problem with the dac setup at one point
agd5f: I don't recall when I fixed it
dcotruta_: agd5f: dac?
agd5f: you might try 6.7.197 or git
agd5f: digital analog converter
agd5f: it's what drives your monitor
dcotruta_: what is the latest version of the radeon driver?
agd5f: latest release is 6.7.197. git has additional new stuff
agd5f: but I'm pretty sure 6.7.197 has the fix
dcotruta_: where could I download this driver - and do you know if I can grab it from a fedora repo?
agd5f: probably. not sure off hand
agd5f: maybe rawhide?
dcotruta_: what about a source download?
agd5f: sure. just grab the latest source from git, although you'll have to get all the build reqs and such
dcotruta_: erm - i'll still need the address for git
agd5f: git clone git://anongit.freedesktop.org/git/xorg/driver/xf86-video-ati
agd5f: I gotta run. bbl
dcotruta: agd5f: I thank you!
mcgreg: hey, I dont remeber if I asked already .. I have DVI on my x1300pro, and HDMI-inpit on my monitor, can I use a simple DVI/HDMI adapter use and this kind of digital connection? since I read with resolution like 1680x1050 it is recommended to use digital connections
kasukka: hi, a Qst: does the current xf86-video-ati support tv-out of radeon 9100 (R200 QM i suppose)? my driver version (ubuntu 7.10's) doesn't even show the "S-video" output on xrandr.
MrCooper: mcgreg: yes that should work, the signalling is compatible
agd5f: kasukka: IGP chips have a 14 Mhz ref clock usually which doesn't work with teh current tv-out coe
kasukka: agd5f: does IGP mean laptop stuff? mine's a regular agp card
agd5f: IGP is integrated ships
agd5f: kasukka: oh you have an R200 discrete chip
agd5f: tv-out isn't supported on that one as it uses an external tv-encoder
kasukka: is this called some "theatre" this external encoder? i see theatre200 files on current xf86-video-ati sources and is giving me (false?) hopes
agd5f: kasukka: yeah it uses the theatre chip for tv-out, but the current theatre code in the driver is only for tv-in
kasukka: ah, i see
kasukka: do you know if there's any near or less-near plans for the theatre tv-out?
agd5f: kasukka: I would, but I have no HW with a theatre chip, and more importantly, no spare time to do it
kasukka: agd5f: ok. in general, would you say there were enough docs available for someone new on driver coding (like me) to try it out? if yes, got a good starting point(s) to show?
kasukka: and cool talking with you!
agd5f: kasukka: there is a gatos patch floating around to enable it on older versions of the driver. you'd just have to dig out the appropriate bits and port them over
kasukka: sounds like i've got some chance
stiangutt: Hello, wonder if there is anny known problems with xorg and ATI cards while using fbsplash
dan__: Anyone here?
dan__: maybe you can help me
OipOS: Maybe. I'm not a develloper, though I'll try my best.
dan__: I'm trying to get a radeon 9250 to work in Ubuntu
OipOS: It doesn't?!
dan__: It works up until it trys to load the Ubuntu desktop
dan__: it freezes on the splash screen, and it freezes in the "safe mode" start up too
OipOS: Eh, reading Xorg.0.log and looking at the output when manually starting X would supply you with more information.
dan__: where is that located?
OipOS: And well, starting X manually would be on your terminal.
dan__: what would I be looking for?
OipOS: Every line in Xorg.0.log is started by this:
OipOS: (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
OipOS: Search for (EE)
OipOS: Oh, and particularly the end of the file. As it should say why it crashed/didn't start. Also, starting the safe mode X might change Xorg.0.log to Xorg.0.log.old.
dan__: (WW) VESA(0): Bad V_BIOS checksum (WW) VESA(0): Failed to set up write-combining range (0xc0000000,0x7b0000) (WW) VESA(0): Option "UseFBDev" is not used (EE) AIGLX: Screen 0 is not DRI capable
dan__: are the only warnings and errors I got
OipOS: Yeh, that's the safe mode.
OipOS: Check /var/log/Xorg.0.log.old
dan__: that's where I got it from
OipOS: Try starting X in normal mode, and check /var/log/Xorg.0.log again
dan__: I'm not sure what you mean
OipOS: Just start the xserver again.
OipOS: Tell it to use the oss radeon drivers.
OipOS: And re-check the logs.
dan__: lspci says 01:04.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon 9200 PRO] (rev 01)
dan__: does that mean it's not actually a 9250?
OipOS: I believe the 9200 PRO is a 9250.
OipOS: Anyways, I'm off to bed now. Good luck with your problem. You could also try to mail to the ati maillist.
a_villacis: Hello. Does anybody know whether the next batch of documentation for radeon cards will include information to fix bug #12048, about DRI not being supported on RN50/RC410 cards?
agd5f: a_villacis: yeah the 3D stuff we are releasing soon should help
rx__: 3d is next up?
a_villacis: agd5f: In the particular case of RC410, will it be required to update mesa and libdrm as well? At airlied.livejournal.com it was announced that rs690 support required mesa/libdrm updates. I am currently testing with xf86-video-ati git, but with stock Fedora 8 libdrm and mesa.
agd5f: a_villacis: yes, once someone fixes the code :)
a_villacis: Thanks. I will be waiting for the release.