05:24 Arguggi: I don't seem to be able to use my 970 with nouveau on arch (up to date and everything), can anyone confirm that it should work?
05:34 imirkin: Arguggi: you should be able to get modesetting with 3.19+ and basic acceleration with 4.6+
05:35 Arguggi: imirkin, thanks I guess I'm doing something wrong then
05:36 imirkin: for the latter, you also need nvidia's signed firmware, available from linux-firmware
05:37 imirkin: pastebin dmesg + xorg log, should show what's going wrong
05:41 Arguggi: problem is my screen just turns off last time I tried and then I forgot to save my xorg log. If I still have problems I'll pastebin it, thank you
09:22 pmoreau: karolherbst_work: I started integrating the EVO stuff back in Feb. 2015, so it was released more than a year ago now. It got merged in envytools in Nov.-Dec. 2015. :-)
09:22 karolherbst_work: yeah
09:22 karolherbst_work: I saw the modification date
15:23 lawll: so the actuall improvements are done in kernel and mesa for this?
15:23 imirkin_: what is "this"?
15:24 lawll: nouvou+
15:25 imirkin_: yes, the main components under development are kernel and mesa. although there are bits of the nouveau stack elsewhere, but they see few updates and are considered to be largely stable.
15:25 lawll: k
16:23 loonycyborg: oh wow you guys already have gl 4.3 in latest mesa
16:24 imirkin_: for fermi and kepler, yeah
16:24 loonycyborg: soon there will be no difference whatsoever with blob
16:24 imirkin_: doubtful
16:26 loonycyborg: hmm but anyway those versions aren't supposed to be supported by hardware below fermi anyway right?
16:30 imirkin_: loonycyborg: right
16:31 imirkin_: but we're still at GL 3.3 for maxwell
16:31 imirkin_: and no pascal support yet
16:31 imirkin_: [if ever]
16:32 loonycyborg: what is interfering with pascal support?
16:32 Yoshimo: nvidia
16:33 imirkin_: dunno ... lack of time, hw, nvidia hasn't released redistributable fw, etc
16:33 Yoshimo: what about everything older than fermi and kepler, where do they stand at?
16:34 imirkin_: Yoshimo: got a specific generation in mind?
16:35 Yoshimo: no it was just a more general question. Is everything supported in nouveau that the hardware can do?
16:35 imirkin_: nope
16:35 Yoshimo: oh i see, i still have a tesla card, how about those?
16:36 imirkin_: outside of random failures that happen, tesla is moderately well supported. we don't expose the compute functionality at all though.
16:36 Yoshimo: what is its opengl level?
16:36 imirkin_: OpenGL 3.3
16:37 imirkin_: with varyious additional extensions, depending on whether it's a D3D10 tesla or D3D10.1 tesla
16:37 imirkin_: Yoshimo: https://people.freedesktop.org/~imirkin/glxinfo/glxinfo.html
16:37 Yoshimo: NVA0 if that helps
16:38 imirkin_: ah, that one's like D3D10.05 :)
16:38 imirkin_: that one should even have reclocking btw
16:38 imirkin_: but yeah, it's reasonably well-supported. those also have some basic fp64 which is not exposed.
16:39 Yoshimo: 10 and a half? sounds weird ;)
16:39 imirkin_: but it doesn't have the D3D10.1 features of the GT21x series. but it does have something ... tf related... i think it can pause/unpause tf queries, while earlier tesla's cant?
16:40 imirkin_: oh, and i think it might also have actual seamless cubemap support, while earlier GPU's don't (and it's just fake-reported in GL, since it's required for GL 3.2)
18:07 t-ask: Hi, I read mesa 12 is about to be released. I have some odd graphics effects with Guild Wars 2. Like http://storage1.static.itmages.com/i/16/0708/h_1468000894_2463758_b9d0d32260.png or http://storage2.static.itmages.com/i/16/0708/h_1468000914_5672096_b5c4d9c77e.png and I can also look through walls. While this is helpful for PvP, this shouldn't be possible ;)
18:07 t-ask: Now is the question where to put this info?
18:07 t-ask: Here an example of 'looking through walls': http://storage3.static.itmages.com/i/16/0708/h_1468001169_9396249_75493012bc.png
18:07 imirkin_: bugs.freedesktop.org, Mesa -> DRI/nouveau
18:07 imirkin_: make sure to mention what hw you have, and also ideally record an apitrace which reproduces the issue
18:08 t-ask: welll, actually I'm quite short in time currently.
18:08 imirkin_: k
18:12 t-ask: I'm using Arch Linux, 4.6.3-1-ARCH #1 SMP PREEMPT, local/mesa-git 83028.04d93ea-1, GTX 780ti, local/xf86-video-nouveau-git 2447.12f7734-1 with v5 reclocking patches applied.
18:12 imirkin_: k
18:13 imirkin_: it's highly unlikely that i'll look at the bug without an apitrace provided
18:14 t-ask: reclocking works somehow now, but performance is maybe 60% of Wine-Staging 1.9.13 ones.
18:14 t-ask: Yes, I guess so. how can I apitrace it? any short introductions on this somewhere?
18:15 imirkin_: https://github.com/apitrace/apitrace
18:15 imirkin_: they have a wiki with some helpful info too
18:18 t-ask: LOoks like this may take some time. I'm starting GW with "env WINE_DEBUG=-all DRI_PRIME=1 wine Gw2-64.exe" .. if you are able to provide me with the apitrace syntax for this, I'll fire it up
18:18 karolherbst: t-ask: 60% compared to nvidia?
18:18 karolherbst: t-ask: "apitrace trace" before wine
18:18 t-ask: karolherbst: yes, with 0f set, fan runs wild but FPS is around 22-28FPS
18:19 karolherbst: t-ask: how is the temperature?
18:19 karolherbst: t-ask: check sensors
18:19 t-ask: can You provide the command?
18:19 karolherbst: I did
18:19 karolherbst: sensors
18:20 karolherbst: t-ask: you can further reclock your card through the boost file where the pstate file is
18:21 karolherbst: t-ask: but if you set anything besides 0, you should keep your temperature in check, because we currently have no software downclock on high temperature
18:21 karolherbst: only the hardware downclocks at some point
18:25 t-ask: fan1: 2070 RPM temp1: +60.0°C power1: 15.22 W
18:26 t-ask: looks ok, I wonder that it may be louder than with nv driver
18:26 t-ask: Bump mapping looks like it is very pixalated
18:30 karolherbst: well
18:30 karolherbst: it will be louder for sure
18:30 karolherbst: because we don't calculate the required fan speed right
18:31 imirkin_: karolherbst: if you have guild wars, you could double-check and make a trace
18:31 imirkin_: could be a SM35-specific issue though, dunno
18:33 karolherbst: don't have it
18:33 t-ask: actually everything looks like "washed" http://storage5.static.itmages.com/i/16/0708/h_1468002804_8447495_ff302547d8.png and white aura around props and chars http://storage8.static.itmages.com/i/16/0708/h_1468002831_7940488_4f44be8e61.png
18:33 t-ask: GW2 is free to play
18:36 t-ask: starnge now I have 64FPS
18:37 t-ask: on one of the new maps with suposedly new grphics engine 17FPS
18:49 t-ask: I get "ERROR: ld.so: object '/usr/bin/../$LIB/apitrace/wrappers/glxtrace.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored."
18:49 imirkin_: is this a 32-bit or 64-bit application?
18:50 t-ask: GW2 is both somehow. I can force the 32.Bit client... I assume it is running in 64 now
18:50 imirkin_: well, by default apitrace will execute as 64-bit
18:50 imirkin_: you need to do special things to trace a 32-bit app
18:50 karolherbst: with apitrace trace it shouldn't matter though
18:50 imirkin_: i believe they have some helpful comments
18:50 karolherbst: but it depends on how it was installed
18:57 t-ask: I installed the package https://www.archlinux.org/packages/community/x86_64/apitrace/ ... btw sometimes the border is black http://storage1.static.itmages.com/i/16/0708/h_1468004214_8573317_db6f967632.png
18:57 t-ask: I think it depends on the main light position
19:07 t-ask: ok, I think that's the last screenshot for now: http://storage9.static.itmages.com/i/16/0708/h_1468004854_6453055_caf650247d.png
19:08 imirkin_: yeah, so screenshots are useful to show what's wrong, but they're not useful to diagnose the actual issue
19:08 imirkin_: btw, i assume that you've tried this on other drivers with the same setup other than that, and it did not show those artifacts?
19:08 t-ask: I did "apitrace trace --output ./gw2.trace env WINE_DEBUG=-all DRI_PRIME=1 wine Gw2-64.exe" but where is the trace file?
19:08 imirkin_: it should be in the current directory... i've never used --output btw
19:09 imirkin_: it might actually be in some random dir though... i think it gets created in the cwd at the time that the first GL context is initialized or something
19:10 karolherbst: mhh
19:10 karolherbst: if wine is selfcompiled
19:10 karolherbst: then it is where wine-preloader is
19:10 karolherbst: usually
19:10 t-ask: argh, where is that? .)
19:10 karolherbst: nvm then
19:11 karolherbst: isn't it in your current dir?
19:11 karolherbst: also
19:11 karolherbst: did you get apitrace messages?
19:11 t-ask: no nothign happened there
19:11 karolherbst: I never run apitrace ontop of env
19:11 t-ask: I thin there were some... not many
19:11 karolherbst: mhh
19:12 t-ask: I tried it without any env, too. nothing
19:12 t-ask: I assume it is likewhoa imirkin_ said, stored somewhere else
19:12 karolherbst: try an absolute path
19:14 t-ask: just a snippet of what I see https://pastee.org/qwdt3
19:14 karolherbst: well
19:15 karolherbst: in that case nothing was traced
19:15 karolherbst: did you set LD_PRELOAD?
19:16 t-ask: I only installed the pkg... and it did that https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/apitrace
19:18 imirkin_: t-ask: oh, you're using gallium-nine
19:18 imirkin_: t-ask: you might want to ask in #d3d9
19:19 imirkin_: they are, btw, under the impression that there are no nouveau users of gallium-nine.
19:19 karolherbst: huh
19:19 karolherbst: I use it...
19:19 karolherbst: and they know
19:19 imirkin_: hm, perhaps that's not what was said
19:19 karolherbst: mhh I think they know I hope
19:20 imirkin_: maybe they said that there are no testers? dunno.
19:20 karolherbst: anyway, I complaint often enough :D
19:20 t-ask: you ahve one more tester, hehe :)
19:20 t-ask: not very capablie so far, but well .)
19:20 karolherbst: I can understand if nvidia doesn't take nouveau serious enough, but at least I thought it was different for those gallium-nine guys :p
19:21 imirkin_: well, i think the deal is that mannerov doesn't have an nvidia gpu, so he doesn't test on it often? not sure.
19:22 t-ask: ok, lets try the LD_PRELOAD setting as a last one. becasue I actually spend too much time on it already. Any Idea what to ste then?
19:22 imirkin_: won't help
19:22 imirkin_: you're not using GL
19:22 imirkin_: you're using d3d9
19:23 karolherbst: exactly
19:23 karolherbst: you need to run a windows version of apitrace under wine
19:23 karolherbst: and trace the d3d9 stuff
19:23 imirkin_: which will get you a d3d trace
19:23 imirkin_: you could try disable gallium-nine and using wined3d gl impl
19:23 imirkin_: and seeing if the issues persist
19:24 imirkin_: if they do, that likely points to an issue in gallium-nine
19:24 t-ask: with staging everything looks fine
19:24 imirkin_: you should let #d3d9 know
19:24 karolherbst: well, I have a wine-staging installation with gallium-nine :3
19:24 t-ask: well, I postet my initial stuff there
19:24 imirkin_: this is their issue tracker: https://github.com/ixit/mesa-3d/issues
19:25 t-ask: oh they have one at github, nice.
19:25 t-ask: then I maybe paste our conversition there? What do you think?
19:26 imirkin_: this chan is logged
19:26 imirkin_: you can just give a pointer to the logs
19:26 imirkin_: (see topic for log location)
19:29 t-ask: got it. Ok, then I wait for the logs and do the bugreport then. While I hope someone will pick it up and try GW2 then.
19:30 t-ask: thank you all, I must tale a break to do my other stuff ;)
20:59 Yoshimo: imirkin i think the amount of users of gallium-nine is rather small so it is a natural consequence that the amount of users with nvidia cards using it is close to 0, especially when the performance with the binary driver is a lot better than nine&nouveau for the time being