00:09RSpliet: gnurou: I've observed only one non-backward-compatible change in the PMU scripting language over the course of time
00:12gnurou: RSpliet: ah, good to know, thanks
00:13gnurou: probably the way to go would be to have a different PMU host driver whether we are using NVIDIA's or Nouveau's fw though... if NVIDIA introduce changes, we will still need to support the old versions because old chip's fw doesn't get updated
00:34lynxcat: Hi, maybe a stupid question. I understand that 3d acceleration is slow enough, but is it related to 2d acceleration slowness? I scroll hexdump of /dev/urandom and X takes 75% from one core, is that normal?
00:34lynxcat: I have no issues with framebuffer, hexdump with random chars inside it is fast in fb
00:34lynxcat: hardware is NVC1
05:02RSpliet: lynxcat: no, 2d and 3d accel should be... accelerated
05:03RSpliet: please check whether your entire setup is complete, correct and modern
05:04RSpliet: clocks aren't stellar, but it should be fast enough for text scrolling in a terminal
05:08pq: reminds me of the 1bpp bitmap font rendering slowness back then...
05:08lynxcat: RSpliet: may it be related to (somewhat) outdated x server? I am running 1.11.2. Otherwise I had pulled git versions of dri, xf86-video-nouveau and mesa and successfully built them
05:08RSpliet: lynxcat: start at the kernel
05:08pq: lynxcat, what terminal is it?
05:09lynxcat: pq: urxvt with terminus-xft font if that helps
05:09lynxcat: RSpliet: 3.18.0 enough?
05:09glennk: uxrvt is a great terminal to use if you want hopelessly slow drawing on a modern graphics card
05:09RSpliet: should be sufficient, checked the logs to see if it's properly intiialised?
05:09glennk: it uses some really ancient x drawing calls for some of its rendering
05:10lynxcat: RSpliet: yes the logs show fine init, 3d works, others apps pretty fast, no glitches
05:10RSpliet: the I guess it's fair to blame urxvt, tried something like gnome-terminal or a KDE/XFCE like alternative?
05:10lynxcat: glennk: hm, ok, I will try others and compare
05:11lynxcat: hm, no, I just back from blob and used urxvt for three years and have established config with it, well I will try others and compare, thanks
05:16glennk: the blob has its own acceleration and happens to accelerate the one op uxrvt uses for drawing its background that none of the exa/glamor drivers do
05:16glennk: 1bpp masked color fill or something 1980s-tastic
05:26lynxcat: ok I tested vte with -T and got only 25% load and faster scroll, so urxvt is bug :)
08:07imirkin: hm, nvidia does have a "bitmap" texture type...
08:08imirkin: thought if EXA doesn't do it, probably not worth worrying about
10:12sarnex: can someone send me the output of glxinfo on nouveau please?
10:13imirkin_: sarnex: any particular gpu and/or version?
10:14imirkin_: sarnex: most of the interesting results are available at http://people.freedesktop.org/~imirkin/glxinfo/glxinfo.html
10:14imirkin_: but i also have a GK208 handy if you need to see something else
10:14sarnex: imirkin_: well im trying to see if theres an easy way to grep glxinfo to see if someone is using mesa vs amd/nvidia blobs
10:15sarnex: originally i just grepped for Mesa but im not sure if that will work
10:15imirkin_: sure, jus tlook at the renderer
10:15sarnex: would grepping for Gallium do it?
10:15imirkin_: should work...
10:15imirkin_: OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.3.7
10:15imirkin_: it will always pop up with mesa in there
10:15imirkin_: but won't for blob drivers
10:16imirkin_: the renderer string will indeed be like Gallium on NV108 or whatever
10:16sarnex: are you skilled at regex-fu to generate a regex that will check for OpenGL core profile version string WHATEVER Mesa WHATEVER
10:16imirkin_: which is more annoying to grep for... e.g. intel is "Mesa DRI Intel(R) Haswell Desktop"
10:17buhman: OpenGL core profile version string: 5.0 (Core Profile) Mesa 52.0.1
10:17imirkin_: sarnex: glxinfo | grep 'OpenGL version string' | grep Mesa
10:17sarnex: lol wow
10:18imirkin_: you could do it in one regex, but... meh
10:18sarnex: buhman: is that on nvidia blobs?
10:18buhman: sarnex: I'm from the future
10:18imirkin_: a future where his GK106 works...
10:18buhman: that's Mesa in the year 2405
10:18sarnex: cops called
10:18buhman: imirkin_: nop
10:18sarnex: imirkin_: thanks alot this should work :)
10:18buhman: imirkin_: gk106 is still broken
11:21joe9: imirkin: you around? I am able to get the multi-gpu and multi-monitor setup working. I am not able to figure out how to get the monitor-names from xrandr output to be consistent though.
11:22joe9: imirkin: sometimes I get VGA-1 and other times I get VGA-0.
11:22imirkin_: driver load order, probably
11:22joe9: imirkin: Just want to check if there is a way to get the same name all the time .
11:22imirkin_: ask the relevant driver developers?
11:22imirkin_: i think the nouveau names tend to be consistent
11:23joe9: imirkin: oh, ok. thanks.
11:39buhman: imirkin_: are you interested in tracking ancient mesa versions on your glxinfo.html?
11:39imirkin_: buhman: not particularly... i could throw 7.10 in though since that's the last version that supported a bunch of gpu's
11:39buhman: I think pre-gl3.0 and pre-gl2.0 mesas would be fun to compare
11:40imirkin_: i've been thinking of actually cutting the versions down a bit :)
14:26fairc: hi, I need a new grapic card
14:26fairc: something with openGL > 3.0
14:27fairc: any recommendations?
14:27fairc: and with good noveau support :-)
14:27imirkin_: fairc: any DX10-level card should have GL3.3 support
14:28imirkin_: fairc: if you're specifically looking to use it with nouveau, i'd recommend a kepler-class board, since that has partial reclocking atm
14:29fairc: imirkin_: I'm not so much into overclocking, although undercloking would be nice ti keep the temperature low in desktop mode...
14:29imirkin_: overclocking != reclocking
14:29imirkin_: overclocking = pushing the card above its rated (or advertised) limits
14:29imirkin_: reclocking = changing between diff clock levels, part of a card's normal operations
14:30fairc: and there is nothing like underclocking?
14:30fairc: also why don't you name the code names here: http://nouveau.freedesktop.org/wiki/FeatureMatrix/
14:31fairc: now I have to check each one of them to see which one is kepler...
14:31mupuf: fairc: underclocking == Dynamic Voltage/Frequency scaling
14:31imirkin_: fairc: GKxxx/NVE0 is kepler
14:32imirkin_: i should probably nuke the NVF0 column
14:32imirkin_: that made sense when it wasn't really supported
14:32imirkin_: but now it's at the same level as kepler1...
14:32fairc: ye, found it
14:36fairc: damn it, just ha d a kernel panic... :-(
14:37imirkin_: fairc: although for the best support, you may want to get a radeon
14:37fairc: imirkin: http://nouveau.freedesktop.org/wiki/PowerManagement/ here is the nvf0 column (already) missing
14:37fairc: are they better nowadays?
14:38imirkin_: esp as nvidia is adding the secure bs to their latest chips, it'll become more and more painful to use in linux
14:38fairc: I've read something that they are now collaborating with mesa folks
14:38imirkin_: without commenting on actual hardware quality, the driver is probably a lot more reliable
14:39imirkin_: yes, they've been contributing support for their tegra line of chips
14:39fairc: I don't need high end anyways
14:39imirkin_: but afaik there are no plans to provide any real assistance re desktop gpu's
14:39fairc: it should just run smooth and quit
14:41imirkin_: we'll see how the secure bs they're adding shakes out later, but for now their most recent gpu line is entirely unusable by nouveau
14:46fairc: do the radeon folks have a fdo page?
14:46fairc: or a channel :)
14:49fairc: ty imirkin_, I will this channel when I have my new radeon card :-/
16:15skeggsb: imirkin: "secure bs" - i like it :)
16:15skeggsb: the name, not the "feature"
16:40buhman: RadeonStatus is way better than NouveauStatus fwiw
16:42imirkin: skeggsb: didn't really have a better way of describing it
16:42imirkin: also having a hard time recommending nvidia to anyone on linux given that situation...
16:44ArcherSeven: I had to convert.
16:45buhman: imirkin: what's "secure bs"?
16:46imirkin: buhman: starting with GM20x you can (effectively) only use signed code on the gpu
16:47buhman: what does 'use' mean?
16:47imirkin: uploading fuc firmware... it has to be signed
16:47imirkin: in order to be able to do anything useful
16:48buhman: do you think that's intentionally designed to fuck nouveau?
16:48buhman: for whatever stupid political reasons?
16:48buhman: s/nouveau/nouveau specifically/
16:48imirkin: they probably had good intentions
16:48imirkin: but went overboard
16:50buhman: imirkin: maybe they'd give you a signing key ;p
16:50imirkin: getting them to sign our fw would be cool
16:50imirkin: not sure if that'd happen
16:52buhman: maybe this guy would do it https://github.com/envytools/envytools/pull/8