Nightwulf|work: hi all
slavka: hello all!
Kaapa: hey there, having an error compiling latest mesa
Kaapa: can some tell me if this rings any bell?
glisse: Kaapa: issue is more than likely on your side
Kaapa: mainly because yesterday I compiled correctly
Kaapa: missing include GL/glxint.h
Kaapa: isnt this part of mesa?
glisse: don't remember :)
Kaapa: do you have on your system glxint.h? If yes, can you see what package provided it?
Kaapa: this compiled yesterday; is it possible something is broken in latest git? (I doubt it, but not much can be wrong in what I'm doing - git clone; autogen.sh; configure; make)
chithead: glxint.h is not part of mesa. your build environment is broken.
Kaapa: then what am I missing?
chithead: some proto package probably
Kaapa: glcontexmodes.c explictly calls for it
chithead: for debian this is x11proto-gl-dev http://packages.debian.org/search?searchon=contents&keywords=glxint.h&mode=path&suite=stable&arch=any
Kaapa: indeex, on slack that' s glproto
Kaapa: damn fglrx!
Kaapa: chithead: thanks mate!
chithead: if you want to use the radeon driver, make sure that all traces of fglrx have been removed from your system
Kaapa: now it shuold be wasy to fix
Kaapa: chithead: yeah, but that' s a problem! that think is too intrusive
Kaapa: one of the reasons I want to ditch it
Kaapa: compile done!
Kaapa: I need to manually read radeon module, right?
Kaapa: guess the best way is to setup an entry in modules.conf
Kaapa: I have X!
Kaapa: I spoke too early
Kaapa: crashes after crashes :(
aszlig: okay, back at my console-only kms system now with rc6-git3 and -ati, mesa and dri at latest git, fixes some framebuffer glitches but still gives a blank screen with x and no errors in any log
Kaapa: in x logs I have a getversion failed
aszlig: oh, but wait, i haven't checked kernel log *checking*
aszlig: ah, mkay, no errors
Kaapa: kernel mod 2.0.0, expecting 1.17 or higher
Kaapa: disabled dri
aszlig: any possible thing which could be the case, like pae or kernel options which could cause that problem?
Kaapa: my system is crashing all over the place
glisse: Kaapa: your ddx is not built with kms suport
Kaapa: glisse: how can I fix it? (what is ddx?)
Kaapa: sorry for this questions, this is all new for me
Kaapa: I've been a linux user for >10 years but never followed kernel/driver development
Kaapa: and it's soo hard to google with console only :(
adamk: Check the wiki listed in the topic. Make sure that libdrm is built with KMS support, and then rebuild xf86-video-ati after you install the new libdrm.
Kaapa: I did that
Kaapa: the module works, X starts
Kaapa: but after a few secs of usage, just hangs
adamk: Clearly it wasn't compiled against the new libdrm.
Kaapa: why you say that?
adamk: Run ./configure in the DDX directory again and see if it says that kernel modesetting is enabled.
adamk: Because of the error you mentioned above.
Kaapa: hum, ok. since 2.0 is actually higher than 1.17 I didn't assume I had something outdated
adamk: The error message is very misleading.
Kaapa: hum, I can't even find any ddx directory
Kaapa: looking in kernel tree now
zhasha: the DDX isn't in the kernel
Kaapa: /usr/src/linux doesn't point to the .32 kernel
Kaapa: feels stupid
Kaapa: I'm sorry, only now, after using links against that page in the topic, I realized that ddx == xf86-video-ati
Kaapa: adamk: yes, it reports kernel modesetting on
Kaapa: question: Should I be loading the radeon kernel module?
Kaapa: last line of dmesg says: [drm] Initialized radeon 2.0.0 20080528 for ....
adamk: That's the kernel driver.
Kaapa: should I be using that one?
adamk: What kernel are you using?
Kaapa: maybe I'm just doing things wrong
Kaapa: I load the radeon module, remove xorg.conf and startx
adamk: I'm not sure why you'd be getting the version mismatch error if xf86-video-ati was built with KMS support. Are you sure it installed that driver to the correct directory?
Kaapa: that is an error reported by ddx regarding libdrm version, right?
Kaapa: starting again, storing logs
zhasha: adamk: libdrm not compiled with --enable-experimental-api maybe?
Kaapa: I also cleaned and recompiled
zhasha: or whatever the correct flag is
Kaapa: no, it' s there
zhasha: I knew it was --some-super-long-flag-with-experimental-in-it
Kaapa: failed to load module fbdev, is that normal?
Kaapa: I can't see that error anymore
Kaapa: lemme play a bit with X and see if I don't crash
zhasha: MostAwesomeDude: holy patchell!
aszlig: hm, or maybe some xorg config options i could try? =)
Kaapa: this is so frustrating
Kaapa: I saw this working in fedora core
Kaapa: now it's crashing less than a minute after I start it
Kaapa: any other tips, pages to read, etc?
Kaapa: could it be that I need to remove some 3d feature or experimental thing so that it can be more stable?
adamk: Well bear in mind that KMS is still quite experimental.
adamk: You could try booting with KMS disabled.
Kaapa: but it worked nice in the fedora nightly
Kaapa: at least I expected to get the same stability
adamk: Sorry, but I have no idea what is different between Fedora and your installation :-)
Kaapa: yeah, I know. Appreciate the help
Kaapa: just to be sure, should I load radon kernel module?
Kaapa: or just drm?
chithead: the x server will attempt to load the module if it is not already loaded
Kaapa: chithead: when I don' t load manually the driver, for some reason doesn't work
Kaapa: I think it doesn't load drm module
Kaapa: I get a screwed display
Kaapa: ok, froze again
Kaapa: actually, just notice the system doesnt hang
Kaapa: I can ssh to it
Kaapa: X is 100% cpu
Kaapa: any idea how I can find whats happening?
Kaapa: I was reading http://www.linuxquestions.org/questions/slackware-14/radeon-kms-works-760963/; theres a post where it shows a dmesg output
Kaapa: after [drm] ib test succeeded in 0 usecs
Kaapa: I can see a drm] radeon: kernel modesetting successfully initialized
Kaapa: I don't get that line on my dmesg, though
Kaapa: do you guys?
wirry: hmm, my no i have nothing in my dmesg
adamk: Kaapa: What's the output of 'cat /proc/fb' ?
kkuno: hi Xorg crashes very often
kkuno: always when I write something and press enter
kkuno: I have xserver 184.108.40.2061
DanielSenat: Hi I have some problems whit the visual effect on Ubuntu Karmic Koala 9.10
DanielSenat: 01:00.0 VGA compatible controller: ATI Technologies Inc M22 [Mobility Radeon X300]
eosie: MostAwesomeDude: your commit "r300g: Fix is_buffer_referenced" breaks these piglit tests: stencil-drawpixels, vbo-map-remap, vbo-subdata-sync
adamk: DanielSenat: Well, we can't help you unless you let us know what the problems are :-)
DanielSenat: adamk I don't have the drive routines for my card
adamk: Sorry, I don't understand that.
DanielSenat: I know... I guess the swedish word drivrutiner is Drivers
adamk: Are you saying that you don't have drivers for that card? Ubuntu 9.10 should install the open source drivers by default and enable that for that card.
DanielSenat: but it doesn't work
DanielSenat: I am downloading a package from ATI now
adamk: DanielSenat: Use http://pastebin.com/ to show us the output of 'glxinfo' and your /var/log/Xorg.0.log file.
adamk: No, you can't use the drivers from ATI.
DanielSenat: do i need to install pastebin?
wirry: no, its a website
wirry: just click the link, copy the output from "glxinfo" into the textbox on that side, click enter and paste the url here
DanielSenat: yes i see but how can i post it here?
dileX_: cut-and-paste is your freiend
wirry: it looks like this then: http://pastebin.com/f2a62ccd5
dileX_: or use e.g. wgepaste packages locally: wgetpaste $file
DanielSenat: does look rather empty
logari81: DanielSenat: what kind of practical problem makes you looking for other drivers than the ones preinstalled. You said that you have _some_ problems with Visual Effects. What is "some"??
DanielSenat: I can't activate compiz
DanielSenat: apperence - visual effects
adamk: DanielSenat: Please do the same with your /var/log/Xorg.0.log
adamk: DanielSenat: Somehow you've managed to screw up your glx extension :-)
DanielSenat: that command is not possible
adamk: It's not a command, it's a file.
DanielSenat: in the terminal
DanielSenat: ok... but i should write it in the terminal?
adamk: You need to open it with something like 'gedit' (if you are using gnome) or 'kate' (if you are using KDE.
adamk: So something like 'gedit /var/log/Xorg.0.log'
DanielSenat: more text there:)
adamk: DanielSenat: You've somehow managed to install the nvidia driver.
adamk: DanielSenat: Use synaptic to remove any packages with 'nvidia' in the name.
DanielSenat: it was there from the beginning
adamk: No, it wasn't.
adamk: Ubuntu does not install that package by default.
DanielSenat: maybe not..
adamk: So remove those packages and restart your X server.
DanielSenat: restart my X server , is that the sama as restarting computer?
DanielSenat: I have had Ubuntu for 2 days...
DanielSenat: I have uninstalled everything with nividia in
DanielSenat: how do i restart my X server?
Kaapa: adamk: sorry. got d/c. Was that output something normal?
adamk: DanielSenat: Just log out and log back in.
adamk: Kaapa: I didn't see it.
Kaapa: 0 radeondrmfb, output of /proc/fb
adamk: Kaapa: Then you are using KMS.
adamk: It's certainly enabled in the radeon drm.
adamk: Whether or not X is using it is another story.
Kaapa: is there any minimum x server version?
Kaapa: I didn't upgrade it
Kaapa: just libdrm, mesa and ddx
DanielSenat: well i rebooted my computer
DanielSenat: adamk what would be my next step?
adamk: DanielSenat: Try enabling Desktop Effects now.
DanielSenat: adamk failure
DanielSenat: the computer is searching for drivers... then message says that i can't activate
logari81: DanielSenat: run
logari81: sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri xserver-xorg-core
logari81: sudo apt-get install --reinstall xserver-xorg-video-ati xserver-xorg-video-radeon
logari81: sudo dpkg-reconfigure -phigh xserver-xorg
logari81: and restart again
Kaapa: adamk: my server version is 1.6.3; can that be too old? The one in fedora is 1.7.1
adamk: Kaapa: I've had KMS working on 1.6.3.
adamk: Kaapa: I must have missed it, but what's the problem you are having?
Kaapa: after a small amount of time using X, display freezes
Kaapa: I can log into the server via ssh and see X is taking 100% cpu
Kaapa: using fedora nightly everything seems to be workgin fine
adamk: Sorry, I don't have any other ideas now.
Kaapa: fedora uses 220.127.116.11
Kaapa: in what kernel version was kms introduced?
adamk: Well, other then enabling DRM debugging and opening a bug report, anyway.
adamk: I'm fairly certain that the 18.104.22.168 kernel in Fedora is considerably different than a stock 22.214.171.124 kernel.
Kaapa: true enough
Kaapa: I enable that setting during ddx compile time?
adamk: KMS? You shouldn't need to enable it. You already checked that the configure script is detecting kernel modesetting, right?
Kaapa: no, debugging output
adamk: Ahhh.. No, it's a flag you pass to the kernel.. let me see if I can find it.
adamk: I *think* you just need to add drm.debug=1 to the kernel boot line.
DanielSenat: still the same problem
DanielSenat: desktop effects doesn't work
Kaapa: never did that; where I pass that option in lilo?
adamk: DanielSenat: Pastebin your new /var/log/Xorg.0.log file and the new output of 'glxinfo'
adamk: Kaapa: You can hit tab when lilo comes up with the menu selection. Then type the name of the kernel you want to use and add ' drm.debug=1' to the end.
adamk: Or you can edit /etc/lilo.conf and add 'drm.debug=1' to the appent line.
DanielSenat: adamk /var/log/Xorg.0.log acces denied
Kaapa: adamk: where will the log go to? /var/log/messages?
adamk: Kaapa: Your console and, yes, I think /var/log/messages
Kaapa: 1 day of work wasted with this... at least I hope that in the end I can claim success :S
Kaapa: I'm sure I'm just missing something obvious...
adamk: DanielSenat: And /var/log/Xorg.0.log?
DanielSenat: acces is denied
DanielSenat: adamk acces is denied
adamk: You can't open it like you did before with gedit ?
DanielSenat: no I don't think so
DanielSenat: I can't because I don't know how to get to gedit..
Kaapa: sudo less /var/log/Xorg.0.log ?
adamk: DanielSenat: Just run 'gedit /var/log/Xorg.0.log' in a terminal.
DanielSenat: thanks now it worked adamk
adamk: Then select the entire file, copy it, and paste it at http://pastebin.com/
adamk: It looks like you somehow managed to break the kernel module. What's the output of 'dmesg | grep drm'?
adamk: Run 'sudo modprobe radeon' in a terminal and show us any error messages you get.
DanielSenat: or should i post them separatly in the termianl?
Kaapa: what is the "record" module for?
Kaapa: anyone knows?
DanielSenat: adamk sudo modprobe radeon doesn't work
Kaapa: adamk: I was comparing the logs from fc and my system
DanielSenat: here is the reslut for dmesg ; http://pastebin.com/m61a2d27a
Kaapa: there's something that maybe it' s not right in my xorg.log
adamk: Kaapa: No idea.
Kaapa: (II) Setting vga for screen 0..
adamk: DanielSenat: That 'dmesg' output you just posted, was that before or after you ran 'sudo modprobe radeon' ?
adamk: Log out of gnome and log back in. Then show us the output of 'glxinfo | grep -i render' .
Kaapa: adamk: should I have the module fbdev? Is it important?
DanielSenat: back agan
DanielSenat: adamk could you send me that command again
DanielSenat: my fan is running real fast now... strange
adamk: Kaapa: No, I don't believe fbdev is necessary.
Kaapa: I just switched on the option on kernel to output lots of info for radeon
Kaapa: just because this is too new for me, what exactly are the roles of the kernel radeon module and ddx?
Kaapa: radeon is the low/level driver and ddx is the xf86 driver that allows X to use it?
aszlig: hm, maybe now someone can point whats wrong in my case, as mentioned before: blank screen on startx - no errors in logs so far:
aszlig: dmesg: http://pastebin.org/52127 - xorg log: http://pastebin.com/d51bdb1fa
adamk: Kaapa: There are a few documents on the web that go into detail. I only have a basic understanding of it myself, so I'm not the best one to answer that.
DanielSenat: adamk had to reboot my system again.. something was strange
DanielSenat: so could you give me the command again?
Kaapa: ok, but long story short, both of them are used and this channel focus only on the ddx, is that right? Or also on the kernel module?
Kaapa: DanielSenat: what command do you want?
Kaapa: the gedit /var/log/Xorg.0.log ?
DanielSenat: the coman he told me to type just now
Kaapa: glxinfo | grep -i render
aszlig: maybe: glxinfo | grep -i render
DanielSenat: but i send that one again
DanielSenat: that one
adamk: Kaapa: This channel is really for dicussion of all aspects of the open source radeon driver. The kernel module, 3D mesa and gallium drivers, and the 2D Xorg driver.
adamk: DanielSenat: And what's the output of 'lsmod | grep radeon'?
DanielSenat: nothing at all
DanielSenat: should i put them separatly?
DanielSenat: i pasted lsmod | grep radeon
DanielSenat: gave nothing
adamk: Alright, now run 'sudo modprobe radeon'
adamk: Do you get any errors from that?
Kaapa: now that's weird
Kaapa: I booted into fluxbox instead of xfce
DanielSenat: adamk nothing
Kaapa: and I am still here
DanielSenat: it ask for password then nothing
Kaapa: no, I'm not here, just crashed :S
DanielSenat: so is my kernel module broken?
adamk: DanielSenat: That's good.
adamk: Now logout and log back in and check the output of 'glxinfo | grep -i render' again.
adamk: You didn't reboot?
DanielSenat: yes i did
adamk: I didn't tell you to reboot :-)
adamk: I told you to logout and log back in.
adamk: Now run 'sudo modprobe radeon'
adamk: Log in.
DanielSenat: but that i havn't done yet
adamk: Do not reboot.
DanielSenat: log in and out
DanielSenat: thats it
DanielSenat: next time i will
Kaapa: is type mismatch during the drm logs anything to worry about?
Kaapa: adamk: somewhat stupid question... after enabling debug, how do I get the logs if my system crashes?
DanielSenat: adamk I can't log out, the computer starts to get mad and nothing happens.. just black and lots of noise from the fan
DanielSenat: but i can change user? is that ok?
adamk: I'm not really sure.
adamk: I'm honestly not sure what's going on with your computer now.
DanielSenat: I hade a virus that killed my XP a couple f days ago
DanielSenat: but now the computer works ok
DanielSenat: but how long time should t take to log of?
DanielSenat: much longer than rebbot?
DanielSenat: adamk should it take a long time to log out?
adamk: Sorry, I do have other things going on.
DanielSenat: ok take care
adamk: No, just logging out and logging in should do it. I want to restart the X server.
DanielSenat: so the x server is not restarting on a reboot?
adamk: It is, but I don't want you to reboot.
adamk: If you reboot, you unload the radeon module. I'm trying to figure out if direct rendering works if you manually load the radeon kernel module.
DanielSenat: well we can take it at another time
remu: I have an ATI X1300 that I am using with Archlinux. It is a low profile graphics card, so it only has one DVI port, but it is supposed to be dual-link. Will the dual-link work with the open-source ATI drivers?
agd5f: remu: yes
remu: the x1300 will? is there a guide or something of that nature to get it working?
ajax: sure. a) plug it in. b) you're done, get a beer.
ajax: i'm not sure you think dual-link means what it actually means though.
ajax: what do you think it means?
agd5f: remu: assuming your oem actually wired it up for dual-link
remu: i think it means that with one DVI port, I can run two monitors.
remu: And not just a mirror image.
[Enrico]: agd5f: hi! do you remeber me? don't ask me why but radeon.agpmode=-1 or 4 is no more working here i still have strange colors in glxgears (for example the red gears is yellow O_O)
agd5f: remu: nope
remu: agd5f, I see...is what I want to do possible?
agd5f: dual link means 2 tmds links so it can run modes with clocks > 165Mhz
ajax: remu: with something like http://www.matrox.com/graphics/en/products/gxm/dh2go/ , yes.
ajax: assuming "what you want" is "two monitors from one DVI source"
remu: Yes, that is what I want.
agd5f: [Enrico]: can you bisect what change broke it?
[Enrico]: agd5f: i didn't update !!!
[Enrico]: agd5f: it is exactly the same system of some days ago!!
[Enrico]: that's the strange thing
aszlig: hm, i guess at least one of you who are here now is maybe a dev for the ati drivers, right?
aszlig: and hi, btw :-)
remu: ajax, Is that because of the driver, or is the hard ware just unable to do what I want by itself? IIRC, the functionality I am looking for works with windows.
agd5f: [Enrico]: I dunno. hw problem maybe?
aszlig: i've posted a problem with KMS about 44 minutes ago, should i post it again for ref? =)
Kaapa: I'm comparing Xorg logs for the fedora nightly and my current system, and found a difference that may be relevant
agd5f: remu: is it actually a dvi connector or is it a dms-59 connector?
aszlig: errr, 50 minutes =)
remu: agd5f, it is a dvi connecter
Kaapa: while fedora uses swrast_dri.so, mine is using r600_dri.so
[Enrico]: agd5f: mhm i don't think so, but ok it can be possible, but quite strange. the fedora 12 live cd do the same. but composite is working perfectly, only glxgears is... strange lol
agd5f: remu: because if it's just a sinlge dvi port, it's not possible with any os or driver
remu: oh, okay, good to know, thanks
Kaapa: does this mean that my current installation is trying to use hardware accelleration?
jcristau: Kaapa: yes
Kaapa: this is a very experimental feature, correct?
agd5f: [Enrico]: mght be faulty agp. does radeon.agpmode=-1 work?
Kaapa: can I turn it off?
[Enrico]: agd5f: i'm trying but seems to have no effect now :'(
Kaapa: I can def. live w/o it provided I can actually ... well, work with my system
[Enrico]: agd5f: well i tried driconf to enable hyperz then i delete .drirc that's the only change i did
agd5f: Kaapa: works fine for most things
agd5f: [Enrico]: hyperz isn't supported with kms, but it shouldn't get used in that case anyway
[Enrico]: agd5f: eheh i guessed it :D
Kaapa: agd5f: how can I turn it off to see if that' s what causing my system to break?
agd5f: Kaapa: 3d accel? just don't start any GL apps
cxo: ooooh lots of yummy gallium updates
Kaapa: agd5f: I don' t start anything and my system still crashes (well, apart from terms and eventually firefox, if I have time for it)
agd5f: Kaapa: do you have desktop effects enabled?
cxo: would gallium drivers automatically be super fast or do they need to be worked on like the mesa ones to get faster?
Kaapa: agd5f: Tested with and without, both crashes. Tried in fluxbox too
agd5f: cxo: same as any driver
mjr: there's no automagic superfastness
aszlig: hm, anyway, i'll post again:
aszlig: 16:13 < aszlig> hm, maybe now someone can point whats wrong in my case, as mentioned before: blank screen on startx - no errors in logs so far:
aszlig: 16:13 < aszlig> dmesg: http://pastebin.org/52127 - xorg log: http://pastebin.com/d51bdb1fa
aszlig: the logs seem to look okay, right? or did i miss something?
[Enrico]: agd5f: i'm installing nexuiz to take a test
[Enrico]: ETA: 20 minutes for a full download
MostAwesomeDude: zhasha: What'd I do now?
MostAwesomeDude: eosie: Well, is_buffer_referenced was causing lots of extraneous flushes. Now it's not flushing as much, and that's going to change behavior elsewhere.
zhasha: you sent it a truckload of patches :P
MostAwesomeDude: Just gotta figure out *why* the flushes worked.
MostAwesomeDude: zhasha: It's not that many, is it?
MostAwesomeDude: Besides, there's still one missing; it breaks gears so I left it out.
MostAwesomeDude: zhasha: If you can figure out why http://paste.pocoo.org/show/149549/ doesn't work, you get a cookie.
MostAwesomeDude: Or a beer, whichever.
Kaapa: I give up.... just can't make this work, keeps crashing
Kaapa: one last attempt of using only radeon dri driver at compile time but I'm not very confident
dileX: MostAwesomeDude: hi, I can start oa - with psychodelic colours, but anyway :-)
MostAwesomeDude: dileX: Heh, awesome.
MostAwesomeDude: dileX: Could you check if there's any funky debug messages?
MostAwesomeDude: Things like "unsupported format PIPE_FORMAT_R32_G32_SSCALED" for example?
dileX: for you awesome guy, always
MostAwesomeDude: Or other unsupported formats.
Kaapa: how often do we see changes in [libdrm|mesa|ddx
Kaapa: how often do we see changes in [libdrm|mesa|ddx] mainline code? is it possible that I' m only experiencing some trasient effect?
Kaapa: and if I try later this could be ok?
aszlig: Kaapa: hm, you said that you got it working already, or was that specific to redhat?
Kaapa: aszlig: in the fedora core nightly cd it works
dileX: MostAwesomeDude: oa.log is 55M (extracted)
aszlig: Kaapa: the same system?
Kaapa: aszlig: yeah, same laptop
aszlig: hm, maybe you could diff/bisect the redhat changes with the version you're currently running
Kaapa: I did that on the logs
[Enrico]: agd5f: nexuiz runs at horrible framerate (but seems ok, colors are good) so i guess it is only a glxgears problems
Kaapa: I have no clue what version fedora uses, though.....
aszlig: Kaapa: you're using an r300, right?
agd5f: [Enrico]: maybe there's a problem with your gears binary
MostAwesomeDude: dileX: Thanks, I'll go over this.
[Enrico]: agd5f: likely
[Enrico]: agd5f: i think it is old
Kaapa: aszlig: M76, I think it's r300 indeed
agd5f: Kaapa: m76 is r6xx
dileX: MostAwesomeDude: LIBGL_DEBUG=verbose RADEON_DEBUG=fp,cs,draw,surf,tex,fall GALLIUM_NOSSE=1 ST_DEBUG=mesa GALLIUM_DUMP_FS=1 openarena 2>openarena.log
[Enrico]: agd5f: btw is there some tweak for the 3d performance i can use? with mesa 7.4 (and without kms) nexuiz was playable, now it is not. btw i already disabled GLSL in nexuiz
MostAwesomeDude: dileX: Could you not use RADEON_DEBUG? I'm looking for errors which show up when RADEON_DEBUG is disabled.
Kaapa: agd5f: yeah, sorry.
agd5f: [Enrico]: if you have pci mode enabled, switch back to agp
dileX: MostAwesomeDude: OK
[Enrico]: agd5f: well i used radeon.agpmode=4 now i hope it changes something eheheh
aszlig: Kaapa: you're using the latest git version of ddx, right?
[Enrico]: agd5f: oh btw is pageflipping working with kms? this is my last question and i don't bother you anymore
[Enrico]: agd5f: indeed thanks for all the help :D
agd5f: [Enrico]: no pageflipping with kms yet
[Enrico]: agd5f: ok no problem, anyway i don't play 3d games on that pc eheheh, and composite works like a charm so it's ok for me. thanks again :D
agd5f: [Enrico]: no problem
cxo: Is there a way we can support driver development if we can't write any code? Like, can we make donations towards features, kinda like the system that winehq uses. Except donations aren't virtual scores but $$$ and things like cheesecake and hardware and... yeah
MostAwesomeDude: dileX: Thanks. This is with master, right?
dileX: MostAwesomeDude: yepp
dileX: commit bc9d51bb0eab90c47e7b07756e9eba9575f80ffc
dileX: Author: Jos├ę Fonseca
dileX: llvmpipe: Ensure stack variables in unit tests are properly aligned.
MostAwesomeDude: dileX: Awesome. So I think that most of the rendering problems are purely problems with textures now.
Kaapa: aszlig: yes. Latest version of ddx, drm and mesa
dileX: MostAwesomeDude: unfortunately, I have no camcorder, OA looks awesome, like the neon-colours in the 80ies.
aszlig: Kaapa: mhm, trying to figure out what patches fedora uses...
Kaapa: is there any pastebin where I can upload files?
Kaapa: found one
MostAwesomeDude: dileX: I have a feeling I can reproduce it if I try. :3
dileX: MostAwesomeDude: try with anholts oa-benchmark
dileX: $ openarena +exec anholt 2>&1 | egrep -e '[0-9]+ frames'
dileX: 840 frames 37.3 seconds 22.5 fps 15.0/44.4/93.0/13.2 ms
MostAwesomeDude: We can do better.
Kaapa: this is the fedora logs - http://pastebin.ca/1663610 and this is my log: http://pastebin.ca/1663612
Kaapa: apart from fc using sw accell and my installation using r600, cant find a lot of differences
aszlig: Kaapa: and xorg... fedora: 1.7.1, yours: 1.6.3
Kaapa: aszlig: ah, yes.
Kaapa: I followed a post in LQ for a guy that made it work with the same system (slack 13)
Kaapa: so it works with - of course, the video cards are different
adamk: I have KMS working on Slackware 13, so I know it works fine with that X server.
adamk: But I haven't updated it in a while.
aszlig: Kaapa: you get random lockups but everything seems to work including 3d stuff?
Kaapa: aszlig: random as in < 1 minute
Kaapa: but yes
Kaapa: composite, glxgears...
aszlig: Kaapa: did you try to sync with sysrq during the lockup and check the kernel log?
spreeuw: maybe the dri devs could write their own benchmark
Kaapa: another important difference is kernel - I'm trying .32
spreeuw: with fixed res and features
Kaapa: aszlig: no, I don't know how to do that. if you have a link, that'd be great
Kaapa: at a point in time I was able to ssh to my machine
aszlig: Kaapa: try alt+sysrq+s
Kaapa: I noticed X was 100%
aszlig: Kaapa: or you could do it with ssh, too
aszlig: Kaapa: that's even better as you could try to attach a debugger to your x server
Kaapa: doesn happen everytime, though
Kaapa: what kernel do you guys recommend?
aszlig: haha, i can't recommend any at the moment as x isn't working at all
aszlig: but did you try with .31?
aszlig: the only thing i noticed is that in .32 some fb palette issues were fixed (at least with my graphics adapter, an r300)
Kaapa: I did not
Kaapa: .30 is not an option, right?
aszlig: nope, as this doesn't involve kms
Kaapa: just checking
aszlig: except if you don't care if you have kms
Kaapa: I do care since suspension and everything seems to work
Kaapa: but I care even more that I wasted an entire day with this :(
Kaapa: I'll ju
Kaapa: amn keyboar
aszlig: Kaapa: haha, one day isn't that long
Kaapa: aszlig: tell that to my customers when they ask me why my job isnt done ;)
aszlig: started using kms with the intel drivers and had almost the same problem...
aszlig: took me about four weeks
aszlig: almost: as the implementation isn't the same
aszlig: Kaapa: yah, same problem here, as this is my workstation at the office =)
aszlig: so with kms disabled it works, did you check?
Kaapa: you mean the same version?
Kaapa: I rolled back and used an older kernel
Kaapa: but if I can test with the same version but without kms...
Kaapa: I need to compile libdrm without kms, is that correct?
aszlig: yah, and you need to boot without modesetting enabled
aszlig: try nomodeset for the kernel cmdline
aszlig: at least that works with intel, should work with radeon, too (i guess)
aszlig: Kaapa: and it should work without recompiling
Kaapa: that's what I was about to ask
aszlig: so you should at least have a fallback until your issue possibly gets fixed, but providing more debugging info to the devs could speed things up of course :-)
Kaapa: perfectly reasonable
Kaapa: aszlig: what exctly are the benefits of kms? hw accel? more than that?
agd5f: Kaapa: mainly better memory management. which means more 3d features among other things
aszlig: Kaapa: and faster vt <-> x switching =)
aszlig: and there is just one driver codebase, which makes maintaining a lot easier
Kaapa: and about suspension?
Kaapa: this seems to be working
Kaapa: lemme see if suspension works...
cxo: what is suspension?
twnqx: i suspect suspend/resume.
cxo: Are there any 3d games I can play with my R700 at the moment?
agd5f: cxo: lots. nexiuz, openarena, quakelive, etc.
agd5f: xmoto, neverball, neverputt
Kaapa: as expected, doesnt work
Kaapa: anyway, better than crashing
Kaapa: does this indicate a problem in kernel rather than in ddx or am I jumping to conclusions?
cxo: agd5f, i tried Alien Arena (dont know if thats the same engine), but it was ridiculously slow. Totally unplayable
cxo: Is it meant to be that slow?
cxo: I think I must be getting 10fps
cxo: I only tried it in a windowed mode. I have compiz enabled
agd5f: cxo: kms?
agd5f: IIRC, worked fine last time I tried, but that was a while ago
cxo: how do i know if I have kms?
soreau: grep -i kms /var/log/Xorg.0.log
soreau: glxinfo|grep -i dri2
aszlig: Kaapa: could be both
cxo: (II) [KMS] Kernel modesetting enabled.
cxo: (II) RADEON(0): KMS Color Tiling: disabled
cxo: OpenGL renderer string: Mesa DRI R600 (RV770 9440) 20090101 TCL DRI2
soreau: cxo: That means you are using kms :)
cxo: So why is so slow then?
cxo: I get this error when i run glxinfo, do_wait: drmWaitVBlank returned -1, IRQs don't seem to be working correctly. | Try adjusting the vblank_mode configuration parameter.
adamk: That's normal.
adamk: IRQs are not supported yet.
adamk: Opengl applications under DRI2 are still often slower than under DR1. And the r6xx driver still has lots of room for improvement.
cxo: But agd5f said it worked fine for him
adamk: What exactly works "fine"? And is his definition of fine different from yours?
agd5f: cxo: irqs aren't supported yet
agd5f: so that message is normal
cxo: agd5f, whats you're definition of "fine"?
adamk: cxo: Well that problem are you having?
cxo: Its too slow, must be near 10fps
adamk_: From what you said above, you tried Alien Arena.
adamk_: Which is not in the list of games agd5f mentioned.
adamk_: Try something like neverball and see.
cxo: Well he said, Open Arena, Nexiuz and Quake Live, which I thought were the same engine
adamk: I have no idea what engine Alien Arena uses. However, different games, all using the Q3 engine, could have different performance.
adamk: I know, for example, nexuiz is slower than OA.
adamk: At least here.
agd5f: cxo: I don't remember what the framerate was or what chip I tried it on, but it was playable.
cxo: I'll try Open Arena then
adamk: rnoland_: Just checking to see if you have any new patches that haven't been merged to -CURRENT recently? :-)
rnoland_: adamk: i think radeon support is all current except for interrupt code...
adamk: Ahh, cool.
rnoland_: which isn't released and i don't have working anyway....
EruditeHermit: airlied, hi
amarks: EruditeHermit: it's 5:33am, he is probably not awake yet
EruditeHermit: yeah figured
cxo: adamk_, yeah you were right, openarena is fine
cxo: i wonder why alienarena is so slow then
cxo: The graphics on alien arena look better though
MostAwesomeDude: At risk of stating the obvious... :3
cxo: lighting and shadows looks more realistic on alienarena
MostAwesomeDude: Maybe it's slower because higher-quality graphics take longer to render? :3
taiu: alienarena uses CopyTeximage, which is not accelerated
cxo: Why isn't it accelerated?
cxo: would totally be on that if he knew anything about blitzing and stuff
MostAwesomeDude: Because it's tricky to do.
soreau: cxo: GL2.x is not supported yet
MostAwesomeDude: Basically, 2D blits.
taiu: in theory it's not
cxo: In theory time travel is rather simple too
taiu: it's basic render from texture, but it's vice versa from framebuffer to texture
taiu: osiris is hacking on this for r500
cxo: so basically you need to take something from the framebuffer and use it as a texture?
cxo: like those old winamp skins you cut portions of in a bitmap and use on different buttons?
cxo: Why is that tricky to do?
MostAwesomeDude: osiris: Any insight into why http://paste.pocoo.org/show/149549/ doesn't work?
osiris: MostAwesomeDude: checking...
MostAwesomeDude: Basically, it moves the vbo PSC setup into the derived state setup and refactors the code there into HW TCL and SW TCL versions.
MostAwesomeDude: But it somehow completely screws the facing bits and glxgears stops drawing correctly.
osiris: MostAwesomeDude: first you create draw context only for swtcl but call draw_* for swtcl and hwtcl
MostAwesomeDude: osiris: I'm pretty sure I caught all of those.
osiris: MostAwesomeDude: in r300_vertex_psc I don't see vformat->vap_prog_stream_cntl[_ext] being cleared, you always OR the new value
MostAwesomeDude: osiris: That structure is CALLOC'd every time we do derived state.
MostAwesomeDude: I already checked the RS and PSC tables; this patch doesn't actually change their output.
MostAwesomeDude: That output is identical.
osiris: MostAwesomeDude: try reverting the change from r300_update_derived_state
osiris: MostAwesomeDude: does it break hwtcl or swtcl?
MostAwesomeDude: osiris: SW TCL has been broken for a while; I'm trying to unbreak it by cleaning up the Draw path.
MostAwesomeDude: This breaks HW TCL.
osiris: MostAwesomeDude: if I had to guess I would say that the derived state isn't always recalculated
MostAwesomeDude: osiris: Maybe. I'm wondering if I somehow changed the way facing state is done, or changed the vert shader compile.
Pallokala: is there a way to take a glimpse to gallium without recompiling mesa every time when switching between KMS+DRI2 and gallium??
cxo: i think you could build separate versions and have them in different environments, tricky stuff though
agd5f: cxo: it's tricky because you have to do all the state setup for the blit internal to the driver rather than using mesa
amarks: mesa cgit page is rather stale
MostAwesomeDude: amarks: Yeah, we kicked it a couple times but it doesn't wanna refresh.
soreau: you have to rotate the screen 180
amarks: MostAwesomeDude: how stubborn of it
OLiverr: hello just a short question again concerning my radeon 9800pro: is a performance of ~10fps normal in games like extreme tux racer?
kkuno: uhm If I want xserver with debug symbols I just need to configure with --enable-debug ?
happycube: OLiverr: nope
OLiverr: happycube, because i have some such errors, don't know if they have anything to do with the problem: [ 1878.285497] etracer:2817 freeing invalid memtype e0102000-e0112000
OLiverr: in demsg
airlied: Kaapa: you need to pull drm-next as per the wiki page
airlied: if no-one has suggested it yet
glisse: airlied: did you got a t60 to play with ?
airlied: glisse: I'll try and grab it today, they are in meetings all day
airlied: glisse: just trying to fix EruditeHermit's M10 resume have post traces + bios, now to find some magic registers
glisse: so you need to use your ninja skills to sneak in and steal it :)
glisse: M10 is ?
agd5f: glisse: rv350
Zajec: glisse: ring info patch, please? http://bugs.freedesktop.org/show_bug.cgi?id=24837
Kaapa: airlied: oh, thanks, will look into that!
Kaapa: I'm compiling .31 to see if has any difference
glisse: airlied: v3 patch at http://bugs.freedesktop.org/show_bug.cgi?id=24837 is good
glisse: i ack it
glisse: do you want me to send it to lkml + dri-devel
Zajec: glisse: thanks, i'll just post it on dri-devel to "obey the rules" :)
glisse: dri-devel + cc lkml
glisse: or lkml + cc dri-devel
airlied: glisse: yup I have to go to a meeting today so maybe i can steal it :-)
Zajec: glisse: do i need subscription to post lklm?
glisse: Zajec: maybe posting to lkml is bit too much
glisse: after all i think their was discussion at KS about lkml getting too much mails
airlied: dri-devel is good enough
airlied: lkml for big nthings
osiris: airlied: my solution for the bo space not accounted problem is only partial (buffers need to be validated before every radeon_firevertices call) and dirty solution
osiris: airlied: any suggestions how to fix it properly?
spreeuw: any idea why gamma is broken on ioquake3?
spreeuw: dri1 git current
spreeuw: beenliked this since a few weeks
airlied: osiris: as I said it seemed wrong
airlied: firevertices should get called more often maybe
airlied: we should have emitted all the CB state for the current vertices in advance
osiris: airlied: but what if there were many CB state changes before the render command came?
airlied: I'll try and look today but I'm a long way from mesa at the moment so it mightn't page in well
airlied: osiris: if you get no rendering you can ignore all the CB state changes
airlied: state without rendering isn't useful
airlied: the only thing that should trigger state emission is rendering
glisse: i think best solution would be to emit states when we get vertex to render
osiris: glisse: that's what we do
glisse: then their would be 2 case either states are already present in cs due to previous vertex rendering using same state, or state are not present and you reemit all
osiris: glisse: or maybe not
glisse: osiris: right now AFAIK we emit state to cs at each state change
glisse: but i keep forgeting about things i don't touch for month
osiris_: glisse: no, we emit state during every render operation (r300_draw.c) but also during radeonFlush(I'm not sure why)
osiris_: any idea why we emit state in radeonFlush?
glisse: osiris_: flush call firevertex too iirc
osiris_: glisse: yes
osiris_: glisse: there's one more radeonEmitState in rcommonBeginBatch
osiris_: glisse: actually it's the firevertices that calls the radeonFlush
osiris__: airlied: looks like removing the radeonEmitState call from radeonFlush fixes all the bo space accounting problems :)
glisse: osiris_: 1 liner fix are always good :)
agd5f: osiris__: cool!
MostAwesomeDude: osiris__: I wonder if that has other side effects, though. :T
osiris__: MostAwesomeDude: if you'll think about it, you'll understand that it's the right thing to do. as airlied said we should emit state only when we are rendering something
MostAwesomeDude: osiris__: I agree on that point, yet.
MostAwesomeDude: *yes, even.
DanielSenat: hi everyone
agd5f: osiris__: I wonder if it fixes bug 24131 as well
DanielSenat: still the same problem. Can't activate desktop effects
osiris__: agd5f: I don't think so
soreau: DanielSenat: Can you pastebin the output of 'compiz &'?
soreau: DanielSenat: Sorry, which distro are you using first?
DanielSenat: using Ati mobil radeon x300
soreau: ubuntu, debian ect
DanielSenat: karmic koala
soreau: DanielSenat: Can you pastebin /var/log/Xorg.0.log file too?
DanielSenat: my system went down
DanielSenat: not nice...
soreau: DanielSenat: Can you pastebin your /var/log/Xorg.0.log file?
DanielSenat: soreau can't acces denied
DanielSenat: file bash...
soreau: DanielSenat: It's a file, not a command
DanielSenat: yes but I type it in the terminal
soreau: If you have curl installed you can use the following to paste it easily:
soreau: cat /var/log/Xorg.0.log | curl -F 'sprunge=<-' http://sprunge.us
DanielSenat: don't have that program
soreau: install it
soreau: because that paste is incomplete
soreau: though the error message there is interesting
DanielSenat: yes something is not right
DanielSenat: soreau can't get sprunge
soreau: DanielSenat: sudo apt-get install curl && cat /var/log/Xorg.0.log | curl -F 'sprunge=<-' http://sprunge.us
DanielSenat: I am sure that installed sprunge, but how to use it
DanielSenat: I am very new whit Ubuntu, my windows died 2 days ago due to virus
soreau: DanielSenat: You don't install sprunge, you install curl
biotube: DanielSenat: does 'apt-cache policy libgl1-mesa-glx' show any entries marked with stars?
_entropy: Hi! Is the taskbar corruption thing in KDE 4 considered to be fixed? Using latest linux-next with latest libdrm, mesa and radeon from master I still see random corruption like this http://imagebin.org/71137. GPU is a Radeon 4850, xorg-server-1.7.1 (KMS)
soreau: but yea, we're gonna have to make sure you have glx and dri installed at all or correctly
chi: hrm anyone know whose site sprunge.us is?
DanielSenat: yes three stars:)
biotube: that means that verison's installed
biotube: which makes the linking error more mysterious
DanielSenat: yes my problem is that i can't activate 3D accelerator or Desktop effects
biotube: that's because the necessary libraries aren't loaded
soreau: DanWe need to see the complete X log to help you fix that
DanielSenat: I have no drivers for my ATI Mobile Radeon x300
soreau: DanielSenat: ^^
DanielSenat: ok how do i send a complete log?
soreau: DanielSenat: If you have curl installed, this command should give you a link containing your complete X log: cat /var/log/Xorg.0.log | curl -F 'sprunge=<-' http://sprunge.us
adamk: DanielSenat: You can either run that command from soreau, or open the file in gedit just like you did this morning.
soreau: Yes, that may be even more fool proof :P
DanielSenat: adak, i didn't open gedit it just poped up
DanielSenat: that was the answer
DanielSenat: to that text
DanielSenat: guess it was installed then:)
soreau: DanielSenat: You have parts of fglrx installed
soreau: You need to remove all fglrx packages completely
DanielSenat: so i search in synopsis
soreau: Whatever you have to do, use fire if necessary
biotube: it's a joke
DanielSenat: when i search the synaptic i find except the fglrx stuff jockey gtk, jockey common, xserver-xorg-video-radeon
DanielSenat: should they be uninstalled too?
soreau: DanielSenat: Were your drivers not working to begin with? Because you shouldn't have had to install anything, they should have already been working as soon as you started ubuntu
DanielSenat: no they didn't work
biotube: any package with fglrx in the name needs to go
soreau: Only remove packages with 'fglrx' in the name
DanielSenat: from start
biotube: and reinstall any package with mesa or glx in its name
soreau: Let's not get too confusing yet ;)
DanielSenat: I am not yet there biotube..
DanielSenat: ok fglrx gone
DanielSenat: what is my next step?
DanielSenat: thanks for helping!
biotube: like I said, search for installed packages with 'mesa' and 'glx' in their names and reinstall them
DanielSenat: should they have both in the name?
biotube: i'm not sure
DanielSenat: mesa and glx
DanielSenat: mesa i find alot
biotube: that's the core of 3d
biotube: glx is how mesa is talked to
soreau: DanielSenat: Reinstall libgl1-mesa-glx libgl1-mesa-dri
DanielSenat: soreau done
DanielSenat: only those two?
soreau: those are the pertinent packages on ubuntu
soreau: After you do that, cold boot the machine by turning off the machine, waiting 5 seconds or more, then turning it back on
biotube: DanielSenat: my mass reinstallation advice was due to not knowing which packages were affected
Kaapa: airlied: I was reading about your suggestion of using drm-next
airlied: Kaapa: don't build it directly use git pull to pull the patches
Kaapa: airlied: isn't that patched in .32 already?
DanielSenat: biotube anyway i am so slow i didn't manage to do a massinstall:)
airlied: Kaapa: no not the last few patches
Aaron`: So what is the support like for Radeon Mobility HD 3650?
DanielSenat: soreau so i turn off the system and reboot in 10 sek
Kaapa: airlied: that assumes I need to grab the kernel from git too?
Aaron`: I'm having some issues trying to find an ideal radeon setup for my card.
airlied: Kaapa: yup, or wait I'll be pushing fixes in a day or so tro Linus
Kaapa: I can wait. You think that explains my crashing issue?
_entropy: btw, does linux-next pull from drm-next?
airlied: Kaapa: yes its a knwn bug
soreau: 'wait 10 seconds, then turn off your machine. done.'
Kaapa: why weren't you here before? :D
Kaapa: I assume .32-rc6 then?
Kaapa: airlied: then I gain nothing in trying .31.5 ? DOes that one show the same behavior?
DanielSenat: back on
airlied: or maybe
Kaapa: great. I assume the fedora core nighly has those patches, since it works there
DanielSenat: soreau what is my next step?
Kaapa: thanks a lot mate! I was getting desperate that I didn't know where to look for anymore.
soreau: DanielSenat: Now, what does 'glxinfo|grep renderer' say?
DanielSenat: soreau It says ; OpenGL renderer string: Mesa DRI R300 (RV380 5460) 20090101 x86/MMX/SSE2 TCL
soreau: DanielSenat: That's great news
soreau: DanielSenat: Now try to enable effects in sys>prefs>Appearance>Visual Effects <- set to Extra
DanielSenat: i will try
DanielSenat: i did
DanielSenat: it worked
DanielSenat: but nothing changed or maybe it did
soreau: DanielSenat: If it didn't say 'desktop effects could not be enabled' and it stays on extra, then it's working
DanielSenat: yes it's working
DanielSenat: thank u very much
DanielSenat: take care
cxo: "They don't work, but at least they're clean now." - thats funny
MostAwesomeDude: That's life.
MostAwesomeDude: If you can't get a delinquent cleaned, shaven, and in a suit, how will you get him employed?
soreau: MostAwesomeDude: Good point.
soreau: But he doesn't need a suit, shaved and clean clothes should work ;)
airlied: I got a contract job once because I had a pony tail so I must have known something about computers
airlied: I never questioned the logic as long as I got paid.
MostAwesomeDude: Yeah, the tail appears to be a giveaway for me when I meet new people.
MostAwesomeDude: "Oh, you're a programmer."
MostAwesomeDude: I'm thinking of chopping it off though. :T
hnsr: maybe i should grow one
hnsr: or maybe go for a unix beard instead
hnsr: or both!
Luzipher: hm, is there an easy way to switch between kms (dri2) and non-kms (dri) ? If I append "nomodeset" or "radeon.modeset=0", I don't get KMS, but then dri fails to load on X startup (I do have the stagining option radeon modeset by default compiled in)
soreau: Luzipher: Do you have aiglx on?
soreau: Can you pastebin the X log from dri1?
Luzipher: soreau: aiglx is a xor.conf option, right ? Give me a moment for the xorg.log
Luzipher: grrrr ... is there any pastebin-service where i can upload a file ... that allows for 163KB ? ...
Luzipher: soreau: ok, this seems to have worked: http://sprunge.us/XMQc
biotube: (WW) RADEON(0): Direct rendering is not supported when VGA arb is necessary for the device
Luzipher: soreau: and i can't find anything about aiglx in my xorg.conf
Luzipher: ah ... thanks, biotube
soreau: (II) RADEON(0): [dri] Found DRI library version 1.3.0 and kernel module version 1.31.0
Luzipher: soreau: should they match ?
XenoPL: airled ping
soreau: i dislike 64bit very much
Luzipher: soreau: why ? :)
soreau: because they always seem to have the strangest problems
soreau: If I had a 64bit machine, I'd install 32bit OS on it
Luzipher: if you had a 64bit machine with 6GB Ram ... ? :)
chithead: 32 bit on 6gb machine will mean that you have 1 gb ram and 5 gb fast swap space (aka. highmem)
soreau: idk, maybe if I had one it would just work for me like everything else does for me :P
Luzipher: swap ... /me despises
soreau: Luzipher: Basically it looks like it's failing because kms isn't enabled. Typically that error either means fbcon wasn't loaded before the radoen module or that ddx wasn't compiled against libdrm with kms support. But if it works with kms enabled, I don't see why this would be the case
Luzipher: soreau: biotube already spotted the problem: (WW) RADEON(0): Direct rendering is not supported when VGA arb is necessary for the device
MostAwesomeDude: Hm. Which chipset needs VGA arb?
Luzipher: i guess vga arbitration makes dri2 necessary or sth like that
Luzipher: MostAwesomeDude: I have two cards in my rig
soreau: Luzipher: Do you have two cards there btw?
fax8: hi guys, is this bug known or should I report it? http://bbs.archlinux.org/viewtopic.php?pid=653167
Luzipher: actually i wanted to try to get my third monitor workig on the second card ... but I still have no idea how to do that :)
MostAwesomeDude: Luzipher: Ah. I need to ask airlied about that, then; I really would like to have multicard working w/DRI.
soreau: fax8: which card, dri1 or 2, composite manager enabled, if so which one etc?
Luzipher: fax8: is that with KMS on r600/r700 ?
fax8: Luzipher: see my second post on that forum thread
soreau: Luzipher: Did you say dri works with kms though?
Luzipher: MostAwesomeDude: I'd really like to help with that, but the only thing I could come up with so far was to have two device sections in xorg.conf ... but xrandr still reports only two monitors
Luzipher: soreau: yes, vga arbitration / dri2 works
Luzipher: fax8: i think it's probably a known problem, it doesn't look very differently for me :)
Luzipher: fax8: ah, wait ... Mobility X1600 ... isn't that r500 ? (I'll check ...)
fax8: Luzipher: r300.. not sure though
adamk: soreau: Great job earlier :-)
soreau: adamk: I thought I would never get that log. Thanks! ;)
Luzipher: fax8: well, it's definitely not r600 ... then i'm not sure if it's known ... maybe someone else here knows ?
fax8: Luzipher: https://bugs.freedesktop.org/show_bug.cgi?id=23387
EruditeHermit: airlied, you about?
EruditeHermit: sorry it was really late last night when I got here
EruditeHermit: but I am available now if you need any more debug info
airlied: EruditeHermit: no just trying to figure out what might be happening from what I have
XenoPL: Hi airlied, I've dumped the regs you've asked, bu there's a problem they seems to be identical both when screen comes up and when it's not
soreau: EruditeHermit: What problem are you working on now?
XenoPL: Kind suspected it might happend as turining off/onn the display is enough to get it working
XenoPL: Is there anything else I can try?
airlied: XenoPL: oh wierd
EruditeHermit: soreau, https://bugs.freedesktop.org/show_bug.cgi?id=23103
airlied: XenoPL: might be a monitor issue, some timing thing
soreau: agd5f: ping? You might feel that I'm flogging the dead horse here so to speak, but if I wanted to attempt to dump regs while using fglrx tv-out @ 1024x768 would you be able to provide me with a complete list of interesting regs I would need to gather in order to get the pertinent info needed (to get S-video 1024x768 out working with correct timings on r3xx)
XenoPL: I guess it's possible, but i've seen lots of black display reports recently, maybe it's not just me .
XenoPL: Still want those regs?
airlied: XenoPL: if they are the same probalby no use
soreau: EruditeHermit: What method are you using to s/r btw?
XenoPL: that was my assumption too, but it's no harm to ask
EruditeHermit: soreau, pm-suspend
EruditeHermit: soreau, or the gnome suspend
soreau: EruditeHermit: I happen to be using kde atm, but weird when I try pm-suspend, it acts like it's going to do it but then resumes after say 5 seconds
soreau: tries with the kde de tool
soreau: same thing
soreau: I was able to do it before with some other tool though
soreau: tries to remember
EruditeHermit: they are all wrappers for pm-suspend
EruditeHermit: soreau, note this is kms suspend
ezzieyguywuf: I am trying to build mesa on a LFS 6.5 system. My video card in an ATI FireGL V5200. I need to know if the r600_cmdbuf.c file is necessary for me to have a usable mesa, as it is currently giving me the following error on make http://linuxfromscratch.pastebin.com/m1055f4b5
XenoPL: OK my contingency plan is to add 1s delay to grub and observe, maybe it get fixed with some other changes.
soreau: EruditeHermit: I don't really use dri1 at all and I have viewed your report
biotube: ezzieyguywuf: AFAIK, there aren't any unnecessary files in the driver
XenoPL: 'tho' it would be good if there was some kind of note of this problem in faq or sowhere, it might be confusing when you se blank screen @ boot
ezzieyguywuf: that's what I was worried of
ezzieyguywuf: biotube: did you take a look at the pastebin? it doesn't seem to be an issue local to my build environment but rather something wrong with the function itself
airlied: XenoPL: well I'd like to reproduce it locally, its sort of wierd
airlied: it could be a reg programming ordering issue
adamk: ezzieyguywuf: Is your libdrm up-to-date?
soreau: EruditeHermit: Trying to figure out which args to s2ram I was using last time, but even with -f it's the same behavior
soreau: used to work last time I tried a month or so ago
MostAwesomeDude: airlied: I has r600 IGP and
ezzieyguywuf: adamk: version 2.4.14
biotube: you need 2.4.15
XenoPL: Most likely, kernel boots faster every release, some hardware might not get enouht rtime for init,
soreau: EruditeHermit: There is s2ram and s2disk which both certainly seem to be binaries. Maybe you could test with them?
airlied: MostAwesomeDude: it works with DRI2
airlied: MostAwesomeDude: DRI1 = no
airlied: running s2ram with kms is probably a bad plan
MostAwesomeDude: airlied: That's fine; neither does Gallium. :3
soreau: airlied: Well any way I try, it seems to act like it's going down but then comes right back up after a couple seconds
MostAwesomeDude: looks up multicard xorg.conf incantations
airlied: MostAwesomeDude: system-config-display --reconfig
airlied: might generate a multi-card conf
airlied: on Fedora
MostAwesomeDude: I don't have system-config-display. :T
MostAwesomeDude: Ah, it can be installed.
Luzipher: also checks out system-config-display ...
MostAwesomeDude: airlied: I think that'll do what I want. Just need to enable the second card.
Luzipher: hmpf ... removed from gentoo in august, it seems ... :-/
soreau: airlied: The worst that happened was some corruption when trying s2ram variations. but neither s2ram nor pm-suspend successfully suspend then machine. It just bounces right back
soreau: oh well
soreau: I don't use suspend anyway
XenoPL: ok gotta get some sleep, g'night all
EruditeHermit: soreau, if you had a laptop it would be useful
EruditeHermit: I would choose it over 3d
EruditeHermit: I have bad driver karma
Vash63: Has it been figured out yet why Firefox is so slow with KMS on, at least with r600? Is there a fix?
soreau: EruditeHermit: Yes, I know and I was going to test it here to see if I could reproduce the same issue you're having since we have similar chipsets but as you can see, it doesntwork(TM) here
EruditeHermit: soreau, yeah =p
EruditeHermit: soreau, do your logs say anything?
happycube: the new r300g changes look nice - trying to figure out how to keep CS from overflowing tho
happycube: (maybe i should just... make it bigger!)
happycube: (or not :P )
dmb: good work MostAwesomeDude (from the phoronix article) :)
Luzipher: they wrote you finished r300g and started r600g
MostAwesomeDude: dri is DONE, which means that glxinfo works.
MostAwesomeDude: But mesa is still a WIP.
MostAwesomeDude: So the hooks are there, but it doesn't render right.
MostAwesomeDude: JUST LIKE LAST WEEK.
Luzipher: well, it's phoronix ;)
MostAwesomeDude: To be fair, I *did* start r600g, and I'm glad he didn't link to it...
Luzipher: btw ... while we're at it ... there were many articles about OpenGL state trackers and one for OpenGL coming up ... does anybody know the status of that ?
airlied: we have an OpenGL state tracker, do you mean GL3?
Luzipher: ahh ... there is something in the public already ? */me begins to search for that to trash my computer ...*
Luzipher: maybe it was GL3, right ... can't remember exactly, it's so long ago :)
dmb: MostAwesomeDude, time to start r8xx :)
Luzipher: dmb: according to the wiki r8xx is included in r600g :)
dmb: from what i heard from some amd people, r8xx was going to be completely different
dmb: but i could of heard wrong
Luzipher: not as far as i know ... i read the generation after r800 shall be different
Vash63: If I was to compile r600g and use it, how would it compare to mesa's old swrast?
airlied: it would probably crash
dmb: airlied, will amd open up register guide for r8xx at some point?
dmb: or will they beef out a driver first
airlied: dmb: probably a driver first
airlied: I think the analog modesetting is the same
dmb: analog modesetting as in vga?
dmb: oh, but digital modesetting (dvi hdmi displayport) is different
dmb: is there any open source driver that supports displayport?
airlied: its probably similiar, but there is a lot more displayport
dmb: for any card
airlied: I've got all the code written just needs debugging
airlied: and I think nouveau is the same
dmb: oh, cool
dmb: i want to buy a display port monitor :)
airlied: I can start X on DP and xrandr it once and stuff appears
airlied: hopefully get back to it in a few weeks
MostAwesomeDude: Vash63: r600g currently does not build.
Vash63: lol, ok. Just saw it as an option in my package manager.
MostAwesomeDude: If you revert the tip commit from my r600g branch, it'll build and then crash if you run it.
MostAwesomeDude: Wait, what.
Vash63: Not really expecting it to be useful.
MostAwesomeDude: Your package manager is offering r600-gallium?!
Vash63: For the -scm of course.
MostAwesomeDude: That's just.
Luzipher: dmb: do you have a displayport card ?
Vash63: My only current issue with KMS is the slow EXA or pixman or whatever it is that makes Firefox hate KMS. I'm pretty happily watching Gallium progress, wasn't expecting it to be usable.
airlied: uses firefox all day and it doesn't annoy me
Vash63: And I'm in Exherbo, the package manager has options for pretty much everything that exists, even if it's still in testing or not ready to use. Which is why I asked here.
airlied: I should try google reader I hear thats bad
Vash63: Firefox is terrible on my system.
airlied: you can als otry turning off firefox smooth scrolling
Vash63: Really laggy. I'm using Chromium right now.
Vash63: Is it a ddx issue?
Vash63: I've noticed it's pixman taking most of teh CPU time.
airlied: no its a combination of things, mostly firefox being shit
airlied: what X server you using?
airlied: pretty similiar then
Vash63: It doesn't happen when in DRI1.
airlied: yes its a completely different driver