anom01y: I need help setting up a ati card (330m/340m/350m)
anom01y: will it work with kubuntu ??
agd5f: anom01y: it should
anom01y: hmm well the computer is running terribly slow with kubuntu installed
anom01y: and I was thinking it might be something to do with the graphics driver
anom01y: then again it only has 512 mb ram
anom01y: agd5f: are you just assuming it should or have you seen it work ?
agd5f: anom01y: kde4 has issues on most cards
anom01y: yeah its not the kde4 version
anom01y: its running kde 3.6.0 or somewhere near that
anom01y: latest 3 version anyways
anom01y: it just seems like everything is horribly slow, even though its a p4 3.2ghz
anom01y: 512mb ram
airlied: also 512MB of RAM is probably 128MB VRAM.
agd5f: anom01y: anedotal based on bug reports and IRC
airlied: so you have 384MB of real RAM
agd5f: *anecdotal
airlied: so that would really suck
anom01y: its 64mb video card
anom01y: I think like 420ish or so
anom01y: 440
anom01y: thats it
anom01y: what is kde's operating memory usually ???
hifi: huh
hifi: unknown chip id 0x7147, can't guess.
MostAwesomeDude: hifi: You need Mesa 7.1. :3
hifi: but mom :(
hifi: debian packages for that?
MostAwesomeDude: Probably not.
N00dl3z: There are in experimental.
hifi: :O
hifi: does X start with experimental packages
hifi: at the moment I mean
N00dl3z: You should be able to just pull the mesa experimental packages with a normal testing/unstable X.
hifi: what were the exact package names so I can pin them
MostAwesomeDude: libgl1-mesa-dri IIRC.
N00dl3z: Yeah. "dpkg -l | grep mesa" should show all the ones you have installed.
hifi: needs -glx also, hopefully will work
hifi: R500 support requires a newer drm.
hifi: for christ sake :D
N00dl3z: What version do you have installed? 2.3.1 is in unstable, but testing still has 2.3.0
MostAwesomeDude: DRM needs to be 1.29.
hifi: I think I have 2.3.1
MostAwesomeDude: Kernel 2.6.26 or use the modules from the package.
N00dl3z: Oh, sorry, that's libdrm, not the in kernel DRM.
hifi: so I need what, the new kernel drm modules?
N00dl3z: Yeah. I just tend to build my own kernels, but if you don't want to do that you could try the drm-modules-source package.
hifi: I dont care, the drm-modules-source package might be easier
hifi: so, how do I build the modules? :)
hifi: and you do mean the experimental package?
hifi: humm, m-a seemed to do the trick
hifi: ok, it somewhat works
hifi: I have some screen corruption after I exit quake
hifi: PACKAGE_VERSION_MAJOR undeclared, which dev package am I missing?
hifi: aside from that, do I need xorg 1.5 to test the git version
syntropy: irxxxxorg hahaaa
syntropy: hahah ddrrink--;
syntropy: is away: refulll
bobbens: mmm, weird new bug I found recently, mozilla-mplayer seems to hang the kernel, but I can still move the mouse around (laggy). Usually when kernel hangs with radeon screen gets stuck.
osiris_: agd5f: did you find out how to calculate value for STIPPLE_SCALE field?
nha: MrCooper: I believe there's a thinko in one of your recent commits to mesa/drm
nha: radeon: Post-vblank-rework-rework cleanups.
nha: you're checking crtc < 0 || crtc > 1 twice, aren't you?
MrCooper: nha: right, I meant to remove the first instance :)
MrCooper: nha: Fix pushed, thanks
glisse: airlied: libv told me about an issue he did have while reworking accel code in radeonhd, the cp reported busy and csq queue lossed count of 2 dwords
glisse: as i was debugging the issue of slowdown after a while with cp reporting busy too
glisse: i looked at csq queue and saw the same things
glisse: loss 2 dwords in the count
glisse: strange things is that updating wptr on quadword boundary seems to solve this (it don't happen after 1 hour while it used to happen at most after 5min)
libv: glisse: not for rs690.
glisse: so i guess the cp ring stuff is sensitive as the ib is about the number dwords you put in it
libv: rs690 keeps on losing count.
glisse: even if you update wptr on quadword ?
glisse: by paddingt with nop packet for instance
libv: yeah
glisse: strange for me it seems to work
libv: on rs690?
glisse: no i don't have rs690
libv: r5xx ib needs this, no question there
glisse: on rv350, rv370 and r350
libv: but rs690 direct doesn't change behaviour
glisse: what you mean by direct ?
libv: main ringbuffer
libv: no indirect buffers
glisse: did you try with drm or without ?
glisse: because with drm this means you have to change drm macro
libv: without, drm is always indirect
glisse: whish hw was less touchy....
libv: it just looks like bad QA testing, that the main CSQ cannot handle the load and therefor loses count
Phlogi: hello guys
Phlogi: I'm having a mobility X300 card, last time I tried the oss driver 2d was slow, thats a month ago I think
Phlogi: What about the possibilty to use an external monitor? Does that work flawlessly?
xAFFE: Phlogi, did you load the radeon kernel module?
jaimesilva: hi everyone!
jaimesilva: can someone please tell me how to find out which chipset does my "ATI Radeon Xpress 200" board uses?
jaimesilva: my fglrx driver went nuts and now I want to switch to the radeon driver to stop struggling with fglrx
glisse: http://en.wikipedia.org/wiki/Comparison_of_ATI_Graphics_Processing_Units
glisse: x300
jaimesilva: I am using radeon now but according to Xorg.0.log dri is disabled even when I enabled it in xorg.conf. Is something wrong with my xorg.conf or is DRI not supported for my chipset?
glisse: jaimesilva: should be supported
glisse: you need to load radeon kernel module
adamk_: jaimesilva, You need a relatively new version of mesa and drm. And you need to force DRI on (at least you needed to about a month ago).
glisse: a recent enough
adamk_: Option "DRI" "on"
jaimesilva: am using that option
jaimesilva: I am using that option but it doesn't starts
jaimesilva: my system is Debian testing/unstable
adamk_: Then I'm guessing your versions aren't new enough.
jaimesilva: I have Option "DRI" "true" and Option "AccelMethod" "EXA"
glisse: jaimesilva: lsmod and check for radeon also check that fglrx module is not loaded
jaimesilva: i removed all the fglrx packages
jaimesilva: an rebooted
jaimesilva: r/an/and
N00dl3z: It'll be kernel 2.6.25 I imagine.
jaimesilva: yes it is 2.6.25
N00dl3z: Is 2.6.26 needed for DRI on the most recent cards?
adamk_: I don't believe so.. You can always install the drm from git, though.
jaimesilva: libgl1-mesa-dri Version: 7.0.3-4
adamk_: I'm fairly certain that mesa isn't new enough.
adamk_: I think you need one of the 7.1 release candidates.
N00dl3z: You should still get DRI in the X server with 7.0.3
adamk_: But that shouldn't impact if DRI is enabled in the server.
jaimesilva: the radeon module is not loaded
N00dl3z: Try loading it. :)
jaimesilva: it doesn't load
N00dl3z: Any error?
jaimesilva: is complaining about some unknown symbols
N00dl3z: Did you use modprobe or insmod?
jaimesilva: where can I paste my dmesg?
jaimesilva: modprobe
adamk_: http://pastebin.ca/
jaimesilva: [ 222.944412] radeon: Unknown symbol drm_open
jaimesilva: and then other lines complaining aboud drm...something
N00dl3z: paste an lsmod and the drm messages from dmesg to pastebin.
jaimesilva: co http://pastebin.ca/1078477
N00dl3z: And the lsmod?
jaimesilva: http://pastebin.ca/1078479
N00dl3z: "modprobe radeon" should have loaded the drm module. "depmod -ae ; modprobe radeon"? And if that fails "modprobe drm; modprobe radeon"
adamk_: You have fglrx loaded.
N00dl3z: Aha. So he does.
jaimesilva: http://pastebin.ca/1078480
jaimesilva: ops!
jaimesilva: but why? I removed the fgrl kernel package
jaimesilva: maybe I forgot to reboot
adamk_: run 'find /lib/modules/`uname -r`/ -iname "*fglrx*" ' in a terminal.
adamk_: Make sure that fglrx.ko doesn't show up.
jaimesilva: yes it is there
jaimesilva: but it doesn't belong to any package
jaimesilva: weird
jaimesilva: there is a /lib/modules/fglrx dir
jaimesilva: it was also listed in /etc/modules
jaimesilva: must I list radeon there or it loads automatically?
N00dl3z: It should load automatically.
N00dl3z: You might want to check it's not listed in /etc/modprobe.d/blacklist though.
jaimesilva: ok, It is rebooting now
jaimesilva: ops! monitor is dead
jaimesilva: no route to host
jaimesilva: something wrong here
jaimesilva: i had to hard reboot it
jaimesilva: now it booted but I can't see anything
jaimesilva: (WW) RADEON(0): Direct rendering for RN50/RC410/RS485/RS600/R600 forced on -- This is NOT officially supported at the hardware level and may cause instability or lockups
jaimesilva: kiute
N00dl3z: Is this with xserver-xorg-video-radeon 1:6.9.0-1?
jaimesilva: Version: 1:6.9.0-1
jaimesilva: yes it is
jaimesilva: is it broken?
N00dl3z: I think there have been changes in git affecting RS480 (which I think the Xpress 200 falls under) since 6.9.0 was released.
N00dl3z: commit 72992668ca96717bf69bcea95a5deeaf7c57e826
jaimesilva: well according to the wikipedia link you people gave me, it is an RS485
jaimesilva: sorry, according to wikipedia it is an RS480
jaimesilva: so I better wait until it is solved?
jaimesilva: until next release?
jaimesilva: anyway I'm not in that urge of 3D
jaimesilva: and it is working fine with the default options
N00dl3z: Either try git (and file a bug if it's still doesn't work), or if you're happy enough with what you have at present just wait for the next release I guess.
N00dl3z: s/it's/it/
jaimesilva: sorry, but what does git means?
N00dl3z: It's the version control system that the source is stored in.
N00dl3z: ie it has the cutting edge work on the driver.
jaimesilva: well, at least xv is working fine, with fglrx i was having problems with tvtime, it was slow
jaimesilva: ok
jaimesilva: no, I'm not in the mode to compile it. I guess I'll wait
jaimesilva: thanks a lot, now I know is not a config problem
jaimesilva: and the radeon module is loading fine now ;)
jaimesilva: will radeonhd replace radeon or is it only intended for newer chipsets? Is or will be the RS480 supported by radeonhd?
jcristau: jaimesilva: no, it won't replace radeon
hk: hmm scobby Im using your xorg.conf (with no modifications), but still no go, glxinfo shows "GLX_EXT_texture_from_pixmap" , but don't know why fedora won't start compiz
hk: compiz (core) - Fatal: Root visual is not a double buffered GL visual
adamk_: hk, Are you specifying LIBGL_ALWAYS_INDIRECT=1 when starting compiz?
hk: adamk, hmm no, Im trying to use rh tool (I don't think it does that)
hk: so how is the right way to start it ? export LIBGL_ALWAYS_INDIRECT=1 and then compiz --replace ?
adamk_: Or simply 'LIBGL_ALWAYS_INDIRECT=1 compiz --replace --sm-disable --ignore-desktop-hints ccp &'
hk: adamk, tried your command, still got the same error
hk: any ideas ?
adamk_: Are you using the fedora packages?
Phlogi: googleearth does not run well here
adamk_: Phlogi, Disable low-impact fallbacks in driconf.
otaylor: kh: The red hat tool does disable direct rendering
otaylor: hk: What is the error that you are getting?
hk: compiz (core) - Fatal: Root visual is not a double buffered GL visual
hk: compiz (core) - Error: Failed to manage screen: 0
hk: compiz (core) - Fatal: No manageable screens found on display :0.0
hk: otaylor, ^ this error
otaylor: hk: Hmm. What depth is your server configured to?
hk: let me see here as I have replaced my xorg.conf by scobby one
otaylor: $ xdpyinfo | grep 'depth of root' ay
Phlogi: what versions would you recommend for an x300 based card?
Phlogi: I'm running gentoo so I can choose... not sure if I should go unstable
hk: otaylor, depth of root window: 24 planes
Phlogi: btw googleearth freezes my X
Phlogi: I'm now on xserver v. 1.3.0
Phlogi: mesa 7.0.3
Phlogi: latest x11-drm, radeon and drm module (from git)
adamk_: Phlogi, Did you do what I said above and disable low-impact fallbacks in driconf?
otaylor: hk: Ok, tnot that. Probably your X esrver isn't initialing GL properly for some reason
Phlogi: adamk_: sorry couldn't read that... system freezed
Phlogi: it is already disabled....
otaylor: hk: I'd suggest looking through your X.org logs for any messages about modules not loading or things like that
hk: k
Phlogi: adamk_: should I try to upgrade something?
Phlogi: I don't get what actually is involved, I mean what has mesa to do with radeon driver itself
Phlogi: or even X server
Phlogi: the 2d performance is better than when I last tried, but not as good as with fglrx afaik
Phlogi: my xorg.conf http://rafb.net/p/LFMPg212.html
Phlogi: glxinfo: http://rafb.net/p/tjfPOp41.html
Phlogi: what do you recommend? All fine?
Phlogi: what do you use to test 3d ?
hk: otaylor, any other log than /var/log/Xorg.0.log that I should look at ? (this one seems ok)
otaylor: No that's the log
otaylor: hk: I didn't really get the background ... what card/X packages are you using?
Phlogi: is my xorg.conf ready for using with an external monitor with xrandr?
hk: right now Im using rawhide (upgraded to see if this was fixed with newer packages) was using F9, radeon 9600 pro AGP. xorg-x11-drv-ati-6.8.0-14 m xorg-x11 xorg-x11-server 1.4.99.905-2.20080701.fc10
hk: otaylor, ^
otaylor: hk: Huh, that should really "just work", either F9 or rawhide
otaylor: hk: You should barely need an xorg.conf at all
otaylor: hk: Can you put your Xorg.log somewhere?
hk: sure
otaylor: hk: Oh, hmm. Any possibility that you might have the fglrx libGL on your system? That can cause weird problem.
hk: yes
hk: I have installed it last week or so, but I realized it did not work with f9
Phlogi: I can't get xrandr to work... my external monitor does not show anything :S
Phlogi: what shall I try?
otaylor: Check that 'ldd /usr/bin/glxgear' show libGL.so.1 => /usr/lib/libGL.so.1 (0x009ac000), that ls -l /usr/lib/libGL.so.1 points to /usr/lib/libGL.so.1.2 and that rpm -V mesa-libGL is clean
otaylor: hk: Did compiz work before you tried fglrx?
hk: otaylor, no, I tried fglrx because radeon driver was not working
hk: libGL.so.1 => /usr/lib/xorg/libGL.so.1
hk: lrwxrwxrwx 1 root root 12 2008-07-03 20:01 /usr/lib/libGL.so.1 -> libGL.so.1.2
otaylor: hk: If things were not working before, then fglrx is unlikely to be the problem. There's something odd or unusual about your setup, but I can't think of what itwould be :-)
otaylor: hk: your Xorg.log would definitely be interesting
Phlogi: hmm now it "works"
Phlogi: the monitor needs to be connected when X starts as it looks like :S
hk: otaylor, hehe ok, its a bit big. you want me to past on rafb.net ? or dcc you ? (or any other way)
Phlogi: but having different resolutions on the screens does not seem to work correctly
otaylor: hk: rafb or similar would be fine
Phlogi: w000t :)
Phlogi: now something works that I want to get working since 2 years :)
hk: otaylor, ok, just one minute... seems like ff hang up when pasting to rafb
hk: otaylor, http://rafb.net/p/hqEfeW96.html , http://rafb.net/p/PTPVjx17.html and http://rafb.net/p/yWIINz59.html
hk: it was too big for one post
Phlogi: someone there?
otaylor: hk: OK. Only the first one is really relevant. It basically looks perfect to me. Error seems more likely to be on the compiz side
hk: one thing I noticed too (at least last week, I can confirm now) is that metacity effects worked
hk: but I dont really know if they use the same X11 things
otaylor: hk: that's not realy the same
otaylor: hk: Did you do the 'rpm -V mesa-libGL' that I asked about above?
hk: hmm sorry, I missed that
hk: nothing was returned
hk: otaylor, just came back to the prompt
otaylor: hk: Can you put the output of 'glxinfo -v' on rafb?
hk: sure
hk: hmm now a strang thing happened, in the end it gave a segmentation fault, and it says Direct Rendering no
hk: otaylor, http://rafb.net/p/xcuotZ58.html
otaylor: hk: OK that's getting to your problems
otaylor: hk: Did you try setting LIBGL_VERBOSE like it says?
otaylor: (LIBGL_DEBUG, that is)
hk: no , not yet
hk: doing that
otaylor: hl: The visual are definitely screwed up there
hk: otaylor, libGL: XF86DRIGetClientDriverName: 5.3.0 r300 (screen 0)
hk: libGL: OpenDriver: trying /usr/lib/dri/r300_dri.so
hk: libGL error: dlopen /usr/lib/dri/r300_dri.so failed (/usr/lib/dri/libdricore.so: undefined symbol: _glapi_Dispatch)
hk: libGL error: unable to load driver: r300_dri.so
Phlogi: is it necessary that the second monitor is connected when I start the X-server?
Phlogi: so basically I can't setup an external monitor without restarting my X-Server?
otaylor: hk: Hmm, I'm still suspecting fglrx, even though rpm -V and ldd showed clean
otaylor: hk: Can you remove the fglrx packages and see if things are still the same?
hk: ls
hk: yes
hk: otaylor, I have removed it, I need just to restart X, or the box too ?
ssieb2: Phlogi: it may depend on how new your driver is. It works for me on my laptop with a recent version
otaylor: hk: Just restarting X should be fine
ssieb2: Phlogi: you're using the radeon driver?
hk: ok, brb
Phlogi: ssieb2: yes exactly
Phlogi: ssieb2: which version of what exactly?
Phlogi: mesa, radeon kernel module, xorg-server or the xf86-video-ati module?
ssieb2: the radeon driver, which would out of your list be xf86-video-ati module
ssieb2: but of course that would require a recent version of xorg-server as well :-)
Phlogi: version is: installed: 6.9.0* {:0}
Phlogi: is that not recent enough?
Phlogi: the monitor just does not power on...
hk: otaylor, hmm no go =/ do you know where fglrx stores files (just to check nothing is still there, the aticonfig commands , etc are not there anymore)
otaylor: hk: same issues?
Phlogi: ssieb2: what do you think? do I need a more recent?
hk: otaylor, yes, "unable to load the driver"
otaylor: hk: what I woudl suggest to you: try out the F9 live CD (write it to a USB key even), see if you can get compiz running there, that should give you some inspiration
otaylor: hk: Then catch up with airlied at some point when he is around (he is on .au time) and he might have some ideas about what is going wrong with the packages on your system
hk: ok
ssieb2: Phlogi: that's newer than mine :-) did you try xrandr?
hk: otaylor, gonna do that, thanks a lot for your help! :)
Phlogi: ssieb2: yes of course I'm trying with xrandr
ssieb2: what video card?
otaylor: Sure, no problem. Sorry it wasnt' more useful help :-)
Phlogi: ssieb2: maybe its enough to start the x-server once with an external monitor connected... and then just never restart it without one...
Phlogi: ssieb2: mobility x300
ssieb2: that's exactly what I have...
ssieb2: and I didn't need to do anything
Phlogi: ssieb2: thinkpad?
ssieb2: what distro are you using?
Phlogi: gentoo
ssieb2: no, it's a Dell
Phlogi: maybe a config issue? http://rafb.net/p/eauDSY64.html
Phlogi: thats my xorg.conf
ssieb2: I see you added the virtualsize. I had to add that, but only because otherwise I would just get clone mode (the monitor still worked)
ssieb2: what about xrandr? what does it output?
Phlogi: what I expect... its the same as when I have the monitor connected when starting x, just that it does not output anything
Phlogi: its stays black
ssieb2: could you paste it?
Phlogi: hmm then I need to restart the x-server.. I don't want to do that now...
Phlogi: maybe I just will live with that...
ssieb2: oh, you have it working right now?
Phlogi: yes of course
Phlogi: it only does NOT work when I start X without having the monitor cable already connected
ssieb2: why of course? when I'm looking for help, I try to have it in the state where it's not working if possible...
Phlogi: hmm yes I'm sorry for that
MostAwesomeDude: XD, textures are specified as #texels - 1.
MostAwesomeDude: I'm just full of fail this time around.
Phlogi: wait I'll try something weird ;) i will hibernate then unconnect the cable and see if it still works :)
ssieb2: Phlogi: all I can tell you then is that it works for me on Fedora 9 with the same "card"
ssieb2: that's a good test
Phlogi: even when you connect the monitor afterwards?
ssieb2: yes
Phlogi: maybe thats a ibm acpi related thing...
Phlogi: maybe the output is disabled from something else
Phlogi: ok I'll try it, cu soon hopefully
stefanb1: grmmbbblll. The latest libdrm updates break radeon suspend :-(
stefanb1: MrCooper: Any ideas why?
ZitZ: hello
Phlogi: ssieb2: still works
ssieb2: fun...
ZitZ: does anyone know any debian based distributions that are using xorg 7.4 and mesa 7.1 other than ubuntu?
Phlogi: ssieb2: still works
Phlogi: hmm dunno
Phlogi: I will live with that for now
ssieb2: Phlogi: did you try hibernating?
ssieb2: err, sorry, that's what you said you were doing
ssieb2: was thinking suspend
ssieb2: odd
ssieb2: maybe it's fixed now :-)
xorITor: hey hey... so i noticed last friday that glxinfo returns yes for dri for my hd3650 is anyone aware of that?
xorITor: just an FYI.\
xorITor: it does not work... not unless you call crashing X working, but it does say yes in that field
xorITor: not complaining, on the contrary its a congrats for getting that far!
xorITor: i will wait patiently, and keep doing any testing you guys want
xorITor: well... when the 8 month old lets me test
xorITor: or the wife
xorITor: or the job
xorITor: or the multiple personalities
ZitZ: can anyone help me with why the debian experimental packages aren't working?
xorITor: but again... great job on that part and the rest of it all seems to be working great 2d wise
xorITor: ZitZ, sorry... i have no experiance with them
Ke: ZitZ: ubuntu using mesa-7.1?
agd5f: xorITor: are you running fglrx? because there is no dri or accel support yet for r6xx chips
xorITor: agd5f, no i am running f9
xorITor: with the ati driver
ZitZ: The problem is I install mesa 7.1, yet glxgears tells me I'm using 7.0.4
xorITor: agd5f, i know there is not supposed to be any accel, but glxinfo says "direct rendering: Yes" and "server glx vendor string: SGI"... again no complaint here just an FYI
agd5f: xorITor: something strange must be up with your system as it shouldn't
xorITor: agd5f, its my "electric personality" that bends time/space near me to when you have already done the work to let that happen
xorITor: ;-)
xorITor: hah!
xorITor: sorry i am in a good mood
xorITor: maybe sometime this week i will have time to look at it and let you know
xorITor: but i doubt it
stefanb1: MrCooper: Seems like the new "vblank code" in libdrm is breaking suspend
stefanb1: MrCooper: git commit 7cfdba2b30e40efc688f1704bd4f4141dc6f9a6c is the last good one
stefanb1: *: does anybody else also have issues with radeon suspend?
AndrewR: stefanb1, i can only test "echo standby > /sys/power/state", because my amchine can't survive acpi s3 ... but i just run standby command and everything still work, for rv280, agp radeon card
AndrewR: *machine
stefanb1: AndrewR: Latest libdrm git?
AndrewR: stefanb1, i think yes .. -rw-r--r-- 1 guest users 128236 2008-07-21 14:50 radeon.ko commit 4be367b84b5a6691c28d9419039ea8113ebabc92
stefanb1: AndrewR: Almost, one commit behind :-)
AndrewR: stefanb1, ops, i'm lost in new gitweb interface ;) will retry in minutes ...
stefanb1: AndrewR: Well it is reported now as https://bugs.freedesktop.org/show_bug.cgi?id=16799
AndrewR: . looks like my computer can hibernate!
legume: agd5f: FWIW glxinfo says direct=yes for me on rv670 - maybe it just sees swrast as being direct?
agd5f: legume: yeah could be. what does the renderer string say?
legume: agd5f: OpenGL renderer string: Software Rasterizer
agd5f: legume: yeah, tha's swrast
legume: agd5f: unlike xorITor it works OK for me aswell.
syntropy: Wow...there are some nasty pricks in #java.
syntropy: All I asked was if there was a way to set Java's default DPI. When I discover that is impossible, some idiot tries to start a flamewar because he assumed I meant "java sucks". (It does, but I won't say that there.)
mcgreg: well, that happens :)
mcgreg: this is typical IRC... unfortunately you have to live with that ;)
airlied: summons bridgman
bridgman: airlied: why hast thou summoned me ?
bridgman: an hour ago...
airlied: bridgman: pm..
odz: lol
rbrett: summoning bridgman is now a meme
rx__: wonders what this new vblank code does..
airlied: rbrett: my RH boss does it to our team :)
rbrett: well it seems to work
rbrett: I've been recording the jokes and funny moments from the #radeon logs, and I have the antics of summoning bridgman is about a third of what I have.
rbrett: interestingly, the other 2/3 is mostly MostAwesomeDude's antics
zce: agd5f, im using radeon git master, same problem as yesterday with 6.9 (vga out monitor keeps leds flashing using xrandr on VGA-0, but strangely works if using on LVDS).. theres a difference on the registers (using radeondump), dont know if it might help
GerbilSoft: hm
GerbilSoft: some recent X update has apparently mapped "green" to what was previously "yellowgreen"
GerbilSoft: yet rgb.txt looks fine..
GerbilSoft: er not yellowgreen - "green yellow"
dli_: is r5xx + 2.6.26 kernel blank screen fixed?