05:40titou: does this error message is understood by someone:
05:40titou: NOUVEAU(0): [drm] failed to set drm interface version
05:43pmoreau: titou: Not sure about it, but I would say that Nouveau was build against a version A of DRM, and you're running it against a version B, with B != A
05:44pmoreau: How did you get that?
05:45titou: i tried to use nouveau driver instead of proprietary ones on a fresh mageia 5 RC installation
05:46pmoreau: Hum, probably not the issue then.
05:46pmoreau: Could you paste the whole content of the Xorg.log file please?
05:48titou: hum I lost it sorry
05:48titou: I will switch to nouveau again and give it to you after that
05:49pmoreau: Ok, thanks
06:59titou: pmoreau: ok so I restarded and now it works... I don't understand but it's a good thing
06:59titou: however when I enable desktop effects under KDE display bugs
07:00titou: i only can see a huge horizontal lines which blinks
07:00titou: if I disable them I can see perfectly
07:00titou: desktop effects only works with xrender composite mode (OpenGL 1.2, 2.0 and 3.1 don't work :()
07:01pmoreau: titou: Could you paste the output from dmesg please?
07:05pmoreau: titou: You need to prevent the nvidia module from loading
07:06pmoreau: By blacklisting it in /etc/modprobe.d/*.conf, or uninstalling it
07:06titou: but it seems it is not loaded
07:06titou: it tried but failed
07:08pmoreau: Right, but it could still have messed with some Nouveau parts
07:08pmoreau: So blacklist it when using Nouveau, and unblacklist it if you want to go back to it
07:09titou: do you think it will solve the opengl problem?
07:11pmoreau: Could you paste the new Xorg.log to see if there are any errors in it?
07:13titou: ok it's the same
07:18pmoreau: Nothing obvious :/
07:19pmoreau: titou: You should open a bug report at bugs.freedesktop.org and attach a dmesg, Xorg.log and an image of what you see with desktop effects on.
07:19pmoreau: (Product: xorg, component: Driver/nouveau)
07:19pmoreau: Which Mesa version do you have btw?
07:20titou: Mesa 10.4.7-1
07:35richardlm: (how) can I activate triple buffering in nouveau?
07:55imirkin: richardlm: not sure, but with xf86-video-nouveau 1.0.11 there should be no tearing
07:56imirkin: titou: one obvious thing is that you're using nv4b. sorry, but that 3d driver is... not great. (uses the nv30 gallium driver).
07:56imirkin: i guess the kde compositor tickles one of many problems with it
08:01titou: imirkin: hm ok and how can I change that?
08:01imirkin: change the driver's suckiness? you could go in and fix it up :)
08:02titou: you lost me :)
08:02imirkin: tobijk: http://patchwork.freedesktop.org/patch/46476/
08:02imirkin: tobijk: you killed it :(
08:03imirkin: titou: wasn't sure what question you were asking...
08:03imirkin: titou: what are you looking to change?
08:03titou: imirkin: in fact I don't understand what is nv4b or nv30 and what is the best etc.
08:04imirkin: titou: nv4b is the codename of your card (also maps to G72 or something along those lines)
08:05imirkin: nv30 is the name of the gallium driver that handles nv3x and nv4x hardware
08:05imirkin: gallium driver is what provides 3d acceleration
08:05imirkin: hm, i was close -- nv4b == G73
08:05titou: ok and 3D driver for my kind of gpu is not well supported?
08:06imirkin: i has a number of known deficiencies
08:06imirkin: [i also do, but that's irrelevant]
08:07titou: ok so as far as i understand the best thing for me is to not use nouveau driver?
08:07titou: (because i won't buy a new graphic card :)
08:08imirkin: titou: or don't use kde's opengl compositor
08:08titou: currently I can't use it because I can't see anything with it..
08:08imirkin: that opengl driver works for light use... i guess kde must have started doing something fancy
08:08titou: I'm using wrender..
08:08imirkin: uhm, it should work just fine with xrender
08:09imirkin: are you saying that it doesn't?
08:09titou: it's sometimes slow
08:09titou: yes it works
08:10imirkin: anyways, this is the current state of nouveau's support for your hw... if you don't like it, you can not use nouveau, or if you're a developer, contribute fixes to improve the situation
08:11imirkin: tobijk: your inverted condition patch
08:11titou: I don't have time to try to debug unfortunately
08:11titou: I guess I will use proprietary driver instead..
08:11imirkin: titou: well, i largely know what the problems are, just haven't had time/etc to work on them
08:11titou: ok :(
08:12imirkin: titou: whatever works best for you
08:12titou: but thank you for your help
08:12tobijk: imirkin: you rejected a patch like that from me a while ago, do we really need it after all?
08:12tobijk: there was o indication for it back then
08:13imirkin: tobijk: yes, we really need it
08:13imirkin: if i rejected that patch, then i'm an idiot
08:13tobijk: should have forced you to commit in the first place ;-)
08:13imirkin: it accesses q->data/, which means that each chunk needs to be 32 bytes, not 16 bytes
08:14tobijk: well if you commit that patch like that, i'm allright with it, just the comment as already noted
08:15tobijk: the you cann add my rb as well :)
08:15imirkin: ok thanks
08:16imirkin: tobijk: were you still trying to figure out ARB_cull_distance?
08:17imirkin: Brian Paul wrote the extension, so you could just ask him directly
08:17tobijk: i played with it yesterday evening a bit, had not that much time lately
08:19tobijk: writing thesis takes way too much time ;-)
08:20imirkin: bleh, you did send me that same patch, "nv50: Fix allocation size for querys"
08:20imirkin: but... without any of the explanation!
08:20imirkin: it's not enough to be right, you have to also explain why you're right :)
08:21tobijk: i remember darkly: a irc conversaion
08:22imirkin: where i probably asked "why are you doing this", and you said "coz nvc0 does it", and i said "that's not enough of a reason"
08:22tobijk: i'd like to prove you wrong but, dont have the logs, so lets say that was the actual conversation :D
08:22imirkin: i have logs, but i have no idea what to search for ;)
08:23tobijk: inverted_render i guess
08:23tobijk: or render inverted
08:23imirkin: i'm also not sufficiently interested :)
08:23tobijk: yeah does as long as its fixed
08:36tobijk: good :)
09:14richardlm: imirkin: but if it does not fix tearing?
09:14richardlm: also isn't triple buffering superior?
09:40imirkin: richardlm: quite honestly i don't really understand all the single/double/triple buffering implications
09:41imirkin: looks like you can set SwapLimit to 2 in the Device section of your xorg.conf
09:41imirkin: which will enable triple-buffering
09:42richardlm: I've read about and triple buffering in some random internet article and ofc while in search for tearing soluitons...
09:43imirkin: do you have a kepler gpu and are seeing tearing on videos?
09:44richardlm: I have nVidia G92 [GeForce 9800 GTX+]
09:44imirkin: oh ok. iirc my vdpau impl totally dies on G92's in the first place :(
09:46richardlm: and yeah its on video
09:46richardlm: but IIRC I don't use vdpau
09:48imirkin: try using opengl output instead of xv
09:48imirkin: oh, and what kernel do you have?
09:48imirkin: iirc you need 3.17 or so for all the various fixes re tearing
09:48imirkin: and xf86-video-nouveau 1.0.11
09:49richardlm: check, check and check
09:49richardlm: opengl, 3.18.3 and nouveau 1.0.11
09:51imirkin: pastebin your xorg log? want to make sure you don't have something in there where you tried to "fix" it
09:54richardlm: imirkin: http://paste.opensuse.org/30680284
09:56imirkin: richardlm: yeah, all looks fine =/
09:56imirkin: set swaplimit to 2 if you want to try triple-buffering
10:00richardlm: is it safe?
10:04imirkin: it can cause some issues since the api's don't expect triple buffering to be going on
10:10richardlm: and how exactly would look such a .conf file?
10:10richardlm:has no clue of the xorg.conf syntax ... :-(
10:11imirkin: richardlm: google :)
10:15richardlm: imirkin: what exactly?
10:15richardlm: tried https://duckduckgo.com/?q=xorg.conf%20set%20swap%20limit%20to%202%20nouveau
10:15richardlm: no success...
10:17imirkin: richardlm: something like this: http://hastebin.com/gagorapela.css
10:17imirkin: obviously instead of 'NoLogo', use 'SwapLimit'
10:24richardlm: the 2 in quotation marks?
12:05pmoreau: mwk: Ok, I pushed a few more commits for the EVO documentation. I should have answered all of your concerns apart from the naming for BLOCK_LINEAR & co. Any progress on that?
12:13pmoreau: mwk: I haven't documented PDISP regs related to EVO yet, and will probably do that in a separate pull request as some of them are still unknown and I don't have enough time to RE them now.
12:20fairc: hmm, didn't help ... :-(