01:01mlankhorst: RSpliet: dims in general, but easy to just add WARN_ON near every -ERANGE
01:03mlankhorst: afk :)
01:26Justice: does nouveau have issues with nvidia 7000M ?
01:26Justice: seems im getting graphical corruption in unity.
01:41karolherbst: Justice: 7000M or 700M?
01:41Justice: 7000M the old one
02:07karolherbst: and with unity you mean this fairly modern game engine?
02:08Justice: ubuntu unity
02:09Justice: gonna try mate since the laptop just cries when I tried legacy nvidia drivers.
02:10karolherbst: ohh that unity
02:10karolherbst: maybe better go with xfce then?
02:10karolherbst: though I don't know the footprint of mate in general
02:11Justice: I heard mate is quite small "based on gnome 2"
02:12Justice: xfce is my next bet
02:13Justice: after that i will just install arch with openbox or something.
02:14Justice: laptop came with Vista.....and had 800MB RAM...
02:15karolherbst: I never unterstood this, why save RAM if RAM is really cheap
02:16karolherbst: even nowdays some laptops get like 2GB ram
02:16karolherbst: Justice: but I would really go with xfce, because this is intented to run on old systems
02:17karolherbst: mate is just gnome 2 only modern and fancy, because some disliked the gnome 3 style
02:17karolherbst: so don't expect mate to run well on old hardware, cause that's not the target
02:17karolherbst: even compositing with xfce runs pretty well on ancient hardware
02:20karolherbst: I once installed xfce on a old power mac g4 with dual 867MHz, but I also got a radeon 9700 Pro :D so that's not so fair to compare with yours
02:20karolherbst: but it still run pretty good
02:20gordan: XFCE is overrated.
02:20karolherbst: gordan: howso?
02:20gordan: I have run KDE reasonably comfortably on Toshiba AC100 with only 500MB of RAM.
02:20karolherbst: it's not a problem of RAM
02:21karolherbst: what gpu do you have?
02:21gordan: On the AC100? Framebuffer.
02:21karolherbst: yeah well
02:21karolherbst: so no hw accell at all
02:21gordan: The graphical performance will be affected by the app, not the desktop environment.
02:21karolherbst: not true
02:21Justice: if the desktop is composited it will
02:21gordan: Depending on how many fancy effects you are running (I always disable them all anyway, they're disabled by default).
02:22karolherbst: because the window manager is important
02:22karolherbst: gordan: with a fb you can't do something else anyway
02:22karolherbst: which is exactly the point why kde is not good for yours :D
02:22gordan: As I said, KDE on AC100 with FF works just fine.
02:22karolherbst: yeah, with a crappy kwin config
02:22gordan: I tried XFCE at one point and it made no perceivable difference.
02:23karolherbst: its like saying: yeah my gpu does run bioshock infite, just on lowest settings
02:23karolherbst: I know what you mean
02:23karolherbst: but having a composited window manager makes a difference
02:23karolherbst: and I won't tell a user to use kwin, but just disable everything cause your gpu won't make it otherwise
02:23gordan: I have no drivers for my GPU for soft-float distributions anyway (I maintain a soft-float ARM port of EL). :p
02:24gordan: But even the dumb FB has reasonable-ish basics covered, e.g. it can do video scaling. I can play videos on it just fine.
02:24karolherbst: I would also try out kde on low end systems first just to see how they will drive
02:24gordan: EL as in RHEL without the RH.
02:24karolherbst: but tearing is really a bad thing for me
02:24karolherbst: can't stand tearing
02:24karolherbst: when windows are tearing, it's a nogo for me
02:24Justice: hm but your CPU is better to take the load I guess
02:24gordan: If you are sensitive to things like that, get a fat laptop.
02:25gordan: Horses for courses.
02:25karolherbst: yeah I have
02:25Justice: this one is Athlon 64 X2
02:25karolherbst: i7 + GTX 770M :D
02:25Justice: pretty akward when my phone has 4times the memory of this laptop
02:25gordan: I am typing this on an i7 with a 970M, but I mainly use that for the 4K screen as it makes having tons of terminals open for work more pleasant.
02:26karolherbst: Justice: well I would advise you to try out xfce and if you are disappointed with the effects you can also try out mate or KDE (if you want to have a full solution)
02:26gordan: For when I want something light, I use my ARM laptops, fraction of the weight, multiple of the battery life.
02:26Justice: heh effects :P
02:26karolherbst: yeah I know
02:26Justice: Just want somewhat smooth desktop, not 2 minutes to open unity menu and have graphical corruption =)
02:26karolherbst: the window shadow effect is pretty good though with xfwm
02:27karolherbst: yeah I know
02:27karolherbst: I installed unity once (not on ubuntu)
02:27karolherbst: it was pain
02:27karolherbst: got also corruptions
02:27Justice: This laptop is for a child so as long as firefox and vlc plays somewhat smooth im good with it.
02:28karolherbst: yeah then go with xfce
02:28karolherbst: its easy, small
02:28Justice: Running my desktop with 9590 + 970 on arch and kde5
02:28gordan: I can highly recommend Chromebooks for that sort of thing. :)
02:28karolherbst: maybe lxqt, but I never tried that
02:28karolherbst: I would never use lxde anymore though :D
02:29karolherbst: Justice: or install kde + xfwm
02:29karolherbst: and just don't use kwin
02:29karolherbst: but the only reasons for this would be to get all those applications and the desktop
02:30karolherbst: xfwm doesn't even need OpenGL for compositing
02:30karolherbst: which is I think a big advantage
02:32karolherbst: I think xfce is also the oldest compositor generally
02:34karolherbst: mupuf: wanna take a look at this? https://github.com/karolherbst/nouveau/commit/6663eecc837a3840d5a07ee78945f05298f25ab1
02:36karolherbst: I don't know if I also should check the fsrm div set in cfg_5, but we got a cut by 80% already even when the value is 0
02:41karolherbst: gordan: ohh, do you want to try to reproduce an issue I have with plasma5? when the screen is locked and I (un)plug an external monitor, my plasma session sometimes goes boom
02:42gordan: I don't use external monitors so don't have one handy.
02:42gordan: Most likely RandR interaction issue.
02:42karolherbst: yeah most likely
03:40Justice: just got mate running
03:40Justice: it runs pretty well
03:44BanHammor: Hello people. Does anyone know what part of Nouveau was realized as xf86-video-nouveau
03:50karolherbst: BanHammor: the ddx
03:54BanHammor: Just found xf86-video-modesetting. It finally makes sense.
03:55BanHammor: thank you
04:31karolherbst: weird, my fans can't even cool down my cpu beneath 50°C even when the package just consumes 2W :/
04:31karolherbst: at full speed
04:42karlmag: karolherbst: fan with thermal isolation? :-P
04:59karolherbst: no clue
05:00karolherbst: even when I manually speed up my fans, the temperature doesn't differe much
05:00karolherbst: yeah like no change
05:00Justice: btw is reclocking enabled by default now or?
05:01karlmag: hence thermal isolation theory.. (ie. cooler is thermally isolated from what it's supposed to cool down)
05:02karlmag: Have heard stories... Stuffz stops working for some (overheating) reason...
05:02karlmag: Not really saying that's the thing for you though. :-)
05:12karolherbst: it works okayish on higher temps/loads
05:12karolherbst: Justice: not yet, we are working on it though :p
05:13Justice: sweet maybe this 7000 will be able to run atleast some mobile games well :P
05:13karolherbst: what do you want to reclock on this gpu?
05:14Justice: the gpu?
05:15karolherbst: yeah well, you can only reclock when you have different performance states
05:15karolherbst: you can check in your vbios
05:15karolherbst: but I don't think those old cards are reclocked in general
05:18karolherbst: Justice: or can you switch the pstates with nouveau.pstate=1 booted?
05:21Justice: havent tried
05:22karolherbst: then you should :)
05:22karolherbst: because when manually reclocking doesn't work, automatic reclocking won't either
07:34Tom^: freeeedooooom, no more work until the 4th.
07:34Tom^: karolherbst: still need those uh regs checked?
07:35karolherbst: Tom^: yes
07:36Tom^: https://gist.github.com/karolherbst/1854da8068b510d4cc14 so uh nvapeek 204c0 , etc ?
07:36Tom^: im learning \o/
07:36karolherbst: all of them D:
07:49Tom^: karolherbst: https://gist.github.com/anonymous/c41562ea9a21ce094d0b
07:54karolherbst: Tom^: I think i need the url again, my kernel just crashed
07:56karolherbst: Tom^: the values are values, not regs :D
07:57karolherbst: so it is different for nvf1 cards
07:57karolherbst: a big meh :O
07:57karolherbst: mupuf: the fsrm stuff is different for Tom^s nvf1 card
07:57Tom^: i was about to ask about it but meh just peeked it all :P
07:57Tom^: or am i using to old envytools?
08:09karolherbst: Tom^: its not good if that what you expect is not helpful :D
08:24imirkin: gnurou: well, i combined the fact that it didn't seem to work on GK208 or GK106 with the fact that it was unlikely that you were maliciously lying -- that pointed to the formats only being on GK20A. also they're mobile-focused formats, and GK20A is mobile-focused...
08:26imirkin: gnurou: all this has caused me to resuscitate my TK1 -- booted it last night, but into an older kernel and the older firmware was gone. rebuilt the new one which loads the diff fw but didn't have time to test anything.
08:44mlankhorst: well, my radeon card died on me
08:44imirkin: back to nvidia? :)
08:44mlankhorst: nah, its a macbook
08:44mlankhorst: modprobing causes a panic or something
08:44mlankhorst: but it boots with efifb on radeon
08:45mlankhorst: but as soon as I modprobe radeon it crashes
08:45imirkin: i think you want #radeon :)
08:45mlankhorst: shrug, older kernels that used to work crash now
08:46mlankhorst: did a hack in apple-gmux to disable radeon on probing, then modprobe i915 after so it detects the internal display
08:46mlankhorst: battery live improved so its not all bad :)
08:50karolherbst: mlankhorst: you are so lucky, that it is easy now :p
08:51mlankhorst: try running links on a macbook, the orientation sensor or w/e is used as mouse cursor
08:51mlankhorst: that one was fun to find out
08:54imirkin: gpm can't be taught to look at other devices?
08:54imirkin: you could also use lynx...
08:55mlankhorst: i just rmmod joydev
09:26josla972: RSpliet: I looked at the patches you submitted in september: "[Nouveau] All-round reclocking improvements". Could the reclocking part work if enabled for G84 by changing 0x94 -> 0x84 as per the last patch or would such an attempt only be stupid and riskful?
09:26imirkin: josla972: what kind of vram do you have?
09:26imirkin: ddr2 or gddr3?
09:27josla972: [ 0.647364] nouveau 0000:01:00.0: fb: 256 MiB GDDR3
09:27josla972: [ 0.697996] nouveau 0000:01:00.0: DRM: VRAM: 256 MiB
09:27josla972: according to dmesg
09:27imirkin: well, there's a chance it could work, but unlikely
09:27imirkin: (if it were ddr3, then it def wouldn't work)
09:27josla972: imirkin: ok
09:28josla972: imirkin: risky?
09:28imirkin: shouldn't be dangerous though... it'll just hang your box if it fails
09:28josla972: famous last words
09:28josla972: i'll try it
09:28imirkin: i'm assuming you have a way of rebooting the box, i.e. this isn't some idiotic mac situation where you have to wait for the battery to drain :)
09:29josla972: no no just a regular hp laptop
09:29josla972: i will monitor the temperature with gkrellm or something as well
09:29josla972: (should the reclocking work)
09:29imirkin: most of the time there's not a dedicated fan on laptops
09:29imirkin: i.e. it'll just be your system firmware that decides on fanspeed
09:30josla972: that is my impression too of this laptop
09:31josla972: only one fan that sucks air and blows it over the heatpipes
09:31josla972: ok kernel is built
09:31josla972: brb :)
09:31imirkin: if you don't come back, we'll know why :)
09:32josla972: imirkin: lol
09:36josla972: imirkin_: one setting hanged the system, two did not, and one did not work
09:37josla972: imirkin_: I think I managed to set the most extreme setting though.
09:37josla972: ~ # cat /sys/class/drm/card0/device/pstate
09:37josla972: 20: core 169 MHz shader 338 MHz memory 100 MHz
09:37josla972: 21: core 275 MHz shader 550 MHz memory 301 MHz
09:37josla972: 22: core 475 MHz shader 950 MHz memory 702 MHz AC DC *
09:37josla972: AC: core 475 MHz shader 950 MHz memory 280 MHz
09:38josla972: setting 20 and 22 works, 21 hanged the system, and AC does not work.
09:52imirkin_: josla972: AC = current (well, when plugged into AC)
09:52imirkin_: josla972: note that 22 didn't quite work though
09:52imirkin_: the core reclocked, but memory stayed put
09:52josla972: imirkin_: Hmm I do not think any option really worked though. I noticed this output from dmesg nouveau 0000:01:00.0: fb: invalid/missing rammap entry
09:53imirkin_: josla972: put up your vbios somewhere, maybe RSpliet will have a chance to look at it
09:53imirkin_: vbios available from /sys/kernel/debug/dri/0/vbios.rom
09:54imirkin_: he might also be able to provide mmiotrace instructions to get the necessary info
10:00josla972: imirkin_: I am sorry, I had to fix some file system errors as a result of my system hanging :P
10:00josla972: imirkin_: you said something about vrom
10:04josla972: I dumped it at http://188.8.131.52/vbios.rom
10:09josla972: imirkin_: thanks for the guidance
10:20imirkin_: josla972: sounds like your core/shader clocks change ok... iirc you can boot with nouveau.config=NvMemExec=0 to disable the actual memory reclocking piece
10:21imirkin_: but obviously the memory clock is pretty important to performance :)
10:39josla972: imirkin_: I'll try that and see if things are stable
10:40imirkin_: what kernel are you on?
10:40imirkin_: actually doesn't matter -- looks like that's still around in the latest too
10:40josla972: 4.3.3 with all the 9 patches submitted by rspliet
10:40josla972: (I applied them manually)
10:41imirkin_: ah ok. i think they should be in 4.4-rc5 as well
10:43josla972: imirkin_: yeah probably, I just picked the latest unstable kernel available in the gentoo portage system since I do not know if 4.4-rc5 would run ok.
10:43imirkin_: no worries
10:43josla972: as long as I am not missing out on other dependencies it should be fine I guess
10:43imirkin_: not a lot of changes in 4.4 which would affect your situation... conceivable that roy's patches were massaged a bit though, dunno
10:44josla972: I actually picked them with git format-patch :)
10:44imirkin_: right, but either roy or ben might have futzed with them without resending to list
10:44imirkin_: iow i'm not 100% sure that what's on-list is what ended up in 4.4-rc
10:44imirkin_: but... it very well could have.
10:45josla972: yes but I picked the patches from the git master branch
10:45imirkin_: ah ;)
10:45josla972: seemed easier than downloading the patches from the mailing archive
10:47imirkin_: mwk: i'm inclined to just merge gnurou's new TIC stuff and deal with any fallout later. what do you think?
10:47josla972: anyway, I'll try a reboot with your last suggested option and see what it does when changing pstate
10:47imirkin_: josla972: should be that the core clock changes, but mem stays put
10:48josla972: imirkin_: how I will I know if I succeed? Just by outputting the contents of pstate?
10:48imirkin_: josla972: look at the AC line of pstate
10:48imirkin_: that indicates the current state
10:48josla972: imirkin_: ah!
10:48imirkin_: josla972: also shader-limited things should go faster
10:49imirkin_: (probably *not* glxgears)
10:49josla972: I'll fire up dota 2 and see if it runs equally badly
10:49imirkin_: you might want the non-reborn version
10:50imirkin_: i think reborn wants more than 256MB of vram
10:54josef_: imirkin_: I still got the dmesg output: nouveau 0000:01:00.0: fb: invalid/missing rammap entry
10:54imirkin_: hmmm right
10:54josef_: imirkin_: core and shader are reclocked though
10:54imirkin_: did it change the shader clock though?
10:54imirkin_: k :)
11:04josef_: I think performance is somewhat better
11:04imirkin_: placebo effect? :)
11:04josef_: but I got some errors after fiddling around with graphic settings
11:04josef_: could be
11:04josef_: [ 759.697189] nouveau 0000:01:00.0: gr: 00100000  ch 9 [000f2e4000 dota2] subc 3 class 8297 mthd 1510 data 00000001
11:05josef_: [ 759.894389] nouveau 0000:01:00.0: dota2: nv50cal_space: -16
11:05imirkin_: that means either gpu hung, or you're submitting commands a lot faster than it can process them
11:05josef_: the only sensible way I can think of comparing before and after is to measure fps
11:05imirkin_: perhaps you got that on the lowest perf level?
11:06josef_: yeah I have pretty much the lowest settings
11:06imirkin_: btw, i've made a number of modest improvements to nv50 lately, i'd def recommend trying mesa-git and seeing if it's any faster
11:06josef_: not merged into linux yet?
11:07imirkin_: mesa is the piece of software that provides libGL
11:07imirkin_: and it is all pushed out... just not in a release
11:07josef_: ah, I am running mesa-11.0.6
11:08josef_: the latest "unstable" mesa available in gentoo portage is 11.1.0 (but one could run even more experimental versions of cours
11:08imirkin_: there should be a 9999 version, no?
11:09imirkin_: which iirc pulls from git
11:09josef_: it probably does :)
11:09josef_: I can try that and see if it improves things
11:09imirkin_: anyways, i doubt it'd be really noticeable
11:09imirkin_: just a bit faster
11:09imirkin_: like... a few percent at most
11:09imirkin_: not 2x :)
11:09josef_: worst case scenario is that it pulls in a lot of boring dependencies or doesn't work
11:10imirkin_: oh, and we precompile all shaders now, so hopefully less stuttering
11:10josef_: I suppose memory reclocking would improve things much more
11:10josef_: that llvm stuff?
11:10imirkin_: nouveau doesn't use llvm
11:10josef_: ah, only radeon does?
11:10imirkin_: and llvmpipe (surprise surprise)
11:10josef_: I read briefly about this stuff
11:11imirkin_: llvmpipe uses llvm as a JIT
11:11imirkin_: to compile shader code
11:11imirkin_: into (optimized) CPU instructions
11:12imirkin_: it's unbearably slow for any actual game, but performs fairly well for regular desktop use
11:12josef_: I see
11:12imirkin_: oh, and be sure to let me know if you see any misrendering
11:12imirkin_: i don't actually play many games, so tend not to notice issues
11:12josef_: imirkin_: sure
11:13josef_: I do not know very much about GPUs
11:13imirkin_: don't need to notice anything to notice that something's clearly not looking the way it ought to :)
11:13josef_: nah, just interesting
11:14josef_: I have a fairly good picture of how CPUs work, but not GPUs
11:14imirkin_: well, if you're interested in learning more by contributing to nouveau, i could get you started :)
11:15josef_: do you ah[ 759.697189] nouveau 0000:01:00.0: gr: 00100000  ch 9 [000f2e4000 dota2] subc 3 class 8297 mthd 1510 data 00000001any good material to read?
11:15josef_: [ 759.894389] nouveau 0000:01:00.0: dota2: nv50cal_space: -16
11:15josef_: do you have any good meterial to read?
11:15imirkin_: wrong key? :)
11:15josef_: I think so
11:15imirkin_: mmmm... not REALLY. but i tend not to be a "let me read a book" kind of guy...
11:15imirkin_: more of a "let me try to do this" style learner
11:16josef_: I suppose I am more that kind of guy too
11:16imirkin_: there's http://envytools.readthedocs.org/en/latest/ but it'll be VERY difficult to understand
11:16josef_: learning by doing
11:16imirkin_: i still don't get like 50% of it :)
11:17imirkin_: and remember being totally mystified when i first looked at it
11:17imirkin_: do you know compilers? or alternatively, h264?
11:18josef_: I know how to compile and program
11:18josef_: h264 is just a codec to me
11:18imirkin_: how about programming compilers? :)
11:18josef_: I have never done that
11:19imirkin_: is that something you're interested in?
11:19josef_: it could be interesting to try out
11:19imirkin_: do you know any GL?
11:19imirkin_: so... you're basically where i was 2 years ago.
11:20imirkin_: there's a moderately simple task available herE:
11:20imirkin_: i've purposefully not done it because it's not that big of a deal, and it's a good starter task
11:21imirkin_: the basic idea is that there's a code segment
11:21imirkin_: where we store shader code
11:21imirkin_: but every so often we've uploaded too many shaders and there's no more room
11:21imirkin_: we could be all clever and use some sort of LRU dealie
11:21imirkin_: but instead we just say "fuck it" and evict everything
11:21imirkin_: and then upload the shader we were trying to upload
11:22imirkin_: a single pipeline is composed of multiple stages
11:22imirkin_: and so if we've uploaded the first 3 stages
11:22imirkin_: and then evict everything
11:22imirkin_: and upload the next 2 stages
11:22imirkin_: then... the first 3 stages are gone
11:22imirkin_: oops :)
11:22imirkin_: it's reasonable to assume that the whole pipeline can fit
11:23imirkin_: so we just have to go back and reupload the current pipeline on eviction
11:23imirkin_: the relevant logic is here: http://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/drivers/nouveau/nv50/nv50_program.c#n430
11:24josef_: I'll have a look at it and see if I can learn something
11:24imirkin_: sgtm. and feel free to ask questions
11:24josef_: ok :)
11:26imirkin_: i haven't *fully* thought about this, but i think the simplest thing is to have something in nv50_state_validate after going through the dirty state that forces the upload of all programs
11:59josef_: imirkin_: hmm, another thing I notice is, once the eviction is done, one tries the heap alloc again, and if it fails the shader is considered too large... but is it not possible for the shader to be too large in the first place?
11:59josef_: (thus causing unnecessary eviction)
11:59imirkin_: i mean... impossible is a strong word
12:00imirkin_: but in practice, it's highly unlikely
12:00josef_: I am a total newbie here, so bear with me
12:00imirkin_: error handling is generally sorta fubar in nouveau too
12:00imirkin_: it's not your task to fix it
12:34mwk: imirkin_: you have my blessing
12:37imirkin_: i'm going to do it when i have time to deal with the fallout
12:37imirkin_: probably over the weekend
12:38imirkin_: and i'll take the opportunity to teach demmt about TIC/TSC on kepler+
12:38imirkin_: mwk: btw, how do 32-bit gmem addresses work on kepler?
12:38imirkin_: [or fermi for that matter]
12:41karolherbst: slowly I begin to get annoyed by nvidia changing stuff the entire time :D
12:42karolherbst: now the question why that doesn't work on my kepler card
12:53josef_: imirkin_: nv50_state_validate?
12:54imirkin_: josef_: yeah, in nv50_state_validate.c
12:54imirkin_: all the way at the bottom
12:58josef_: hmm no such file in v4.4-rc5?
12:59mwk: imirkin_: uh... I think they're just zero-extended?
12:59mwk: doesn't sound like rocket science
13:00imirkin_: mwk: yeah, you're probably right
14:25imirkin_: hakzsam: btw, i think we can just do "and b16 $c0 $r0l $r0l $r0l" for that first opcode
14:34imirkin_: hakzsam: and something like st b128 g15[$r5] $r0q
14:34imirkin_: oh, but it might not be aligned... doh
14:34imirkin_: can we align it?
14:52imirkin_: hakzsam: why not make the stride 0x20?
15:00etnk: hello, i've got a machine (hp touchsmart iq775 w/ geforce go 7600) that has a dual-link display and when using nouveau i get image corruption, the freedesktop faq states i should come here for help/advice. the proprietary nvidia driver doesn't have this prob, but it's really outdated for this card and pretty buggy
15:04imirkin_: etnk: can you describe the image corruption?
15:05etnk: yeah looks almost like inverted colors, a light thru the screen (vert not horizontal) and like almost snow flickering
15:05imirkin_: snow tends to indicate underclocking
15:05imirkin_: can you pastebin your dmesg?
15:05etnk: i've added drm.debug=14 and log_buf_len=10M to my kernel
15:06imirkin_: (i.e. memory can't keep up with scanout engine, or vice versa)
15:08imirkin_: that.... did not have what i was expecting
15:09etnk: is it due to the kernel lines i added?
15:09imirkin_: skeggsb: did you kill the clk print in 4.3?
15:09imirkin_: ah yeah, looks like it's gone
15:09imirkin_: etnk: no, not your fault... mine =/
15:10imirkin_: etnk: can you boot with nouveau.pstate=1
15:10imirkin_: etnk: and pastebin /sys/class/drm/card0/device/pstate
15:10etnk: sure, i'm on the machine right now so lemme just cut and paste this and get back in a moment
15:15etnk: there you go
15:16imirkin_: can you try to, as root, echo 22 > /sys/class/.../pstate ?
15:18imirkin_: does the AC line change after you do that?
15:18imirkin_: oops, apparently not
15:19etnk: yeah that hard locked the machine
15:19imirkin_: i guess that didn't work out so hot?
15:19etnk: ha no
15:20etnk: i should be on another machine for chat..
15:20imirkin_: bleh, so... i thought reclocking for nv4x used to basically work :(
15:21etnk: screen started to fade white and the boot screen was kinda flickery when it rebooted, seems ok now tho
15:21etnk: i'd like to not kill the display if possible, but i wouldn't be like totally heartbroken if that happened
15:21imirkin_: that's extremely unlikely to happen
15:22imirkin_: hangs, on the other hand... definitely possible, as you've witnessed
15:22etnk: oh ok cool, i have little understanding of driving display hardware etc
15:23karolherbst: imirkin_: "Mesa: User error: GL_INVALID_ENUM in glTexImage2DMultisample(internalformat=GL_RGB9_E5)" any reason to take care of that?
15:23imirkin_: karolherbst: that's wine doing stupid shit iirc
15:24karolherbst: I get that with bioshock :D
15:24karolherbst: but that's also not "real" native
15:24karolherbst: eon I think
15:24imirkin_: actually RGB9_E5 should be legal
15:24glennk: as a render target in GL? don't think so
15:25glennk: texture format only afaik
15:25imirkin_: ah yeah. def texture-only with nouveau
15:25imirkin_: irrespective of anything GL might say :)
15:25glennk: radeon i think supports it as a RT
15:26glennk: but it also allows weird stuff like bptc as vertex data
15:26imirkin_: looking at GL 4.5, rgb9_e5 is not required for rendering
15:26imirkin_: so what nouveau/mesa is doing is fine
15:27imirkin_: and what bioshock is doing is fine
15:27imirkin_: karolherbst: so ignore the warning and move on
15:27glennk: wonder if its a typo and they meant the other 3 component 32 bit float format
15:28imirkin_: etnk: unfortunately i'm not entirely sure what to say about your issues... you could try an older kernel and see if we broke reclocking somehow
15:28glennk:looks up GL_R11F_G11F_B10F
15:28imirkin_: etnk: or the issue could be entirely unrelated :(
15:28imirkin_: glennk: yeah, r11g11b10 is required for rendering
15:28glennk: don't remember if it supported texturing
15:28imirkin_: well, it's required
15:28imirkin_: according to GL 4.5
15:29imirkin_: and i suspect according to GL_EXT_packed_float
15:29etnk: what version would you recommend? i'm on 4.3 now, 4.2 was same
15:29imirkin_: etnk: well, there was a big rewrite for 4.3, so if 4.2 worked...
15:30imirkin_: if 4.2 *didn't* work
15:30etnk: maybe i should file a bug report with a pic of screen
15:30etnk: do you think that should be my next course of action?
15:32imirkin_: etnk: pic of the screen could be good
15:32imirkin_: bugs.freedesktop.org xorg -> Driver/nouveau
15:32imirkin_: but this is the sort of thing that's difficult to debug
15:32imirkin_: since it requires very specific hw to trigger
15:33imirkin_: and i can't remember last time i tried reclocking a nv4x...
15:33imirkin_: i've def done it, but it was with desktop gpu's, so... more tested
15:34etnk: i understand, i appreciate any help and am willing to do whatever i can for others who may have the same hardware/issue
15:34etnk: thank you for your time on this
15:35imirkin_: if you have the blob set up, you could try to get an mmiotrace of what it's doing
15:35imirkin_: this is a general guide: https://wiki.ubuntu.com/X/MMIOTracing
15:36etnk: yeah that would be no prob
15:36etnk: tho i prob should do that in a bug report and not over irc here, would prob be more efficent?
15:37imirkin_: the mmiotrace? yeah. if it's too big, send it to email@example.com
15:38imirkin_: it should be on the order of 10-100MB uncompressed
15:38imirkin_: [please compress before sending it. xz -9 works quite well]
15:41etnk: gonna reboot w/nvidia now
15:43etnk: ahh my eyes, they don't burn!
15:44etnk: (screen corruption gone on nvidia, will get on looking up how to mmiotrace)
15:51imirkin_: etnk: another thing to check if whether the issues go away at lower resolutions
15:51imirkin_: (should have thought of that up front...)
15:51etnk: for the mmiotrace, so i assume i should do the steps FOR RESOLUTION / DISPLAY BUGS, that is xinit "sleep 10"
15:52etnk: i don't remember if i tried lower res' on nouveau
15:52etnk: so i'll def do again
15:53etnk: does it matter if i use xrandr for res change or does it have to be a kernel line
15:53imirkin_: doesn't matter
15:53imirkin_: btw... another stupid question...
15:53imirkin_: you're not using something like gnome-shell are you?
15:54etnk: openbox atm, gnome-shell over x is same tho
15:54imirkin_: well, something that's not a GL compositor would be best with that hw :)
15:56etnk: i'm hoping to set this machine up as kodi a media center for my family, would really love to a. use nouveau over nvidia driver as its a bit buggy b. help others who might be stuck w/same hardware
15:57imirkin_: it doesn't have hw h264 (or mpeg4) decoding
15:57imirkin_: and the cpu inside is probably not too speedy
15:57imirkin_: and while you can use xvmc for mpeg2 decoding accel, i think kodi has likely dropped that by now
15:57imirkin_: (works fine with mplayer though)
15:57etnk: yeah i no, but i'm hoping for the best, and won't be too disappoint if it don't work out
15:58etnk: if it can play/rip dvds and take svid in alright i'll be happy
15:59imirkin_: yeah... dvd decoding should work fine. you can use the accel or just say screw it and decode on cpu
15:59imirkin_: the accel becomes more useful for ATSC/DVB streams
15:59imirkin_: where the cpu's of the day couldn't keep up but the hw could
16:01etnk: for me that'd just be a plus if it works, that'd only work for ota chans as i have cable am in the us where all the providers encrypt chans now
16:02etnk: anyway i need to figure out how to boot w/o x on arch for the mmiotrace, i haven't done that since pre systemd
16:02etnk: looking that up..
16:11karlmag: Hmmm.... GTS 250... nv92?
16:12karlmag: I guess the older stuff I find is really a bit older than I might hope.. Oh well :-P
16:12imirkin_: karlmag: what's the question?
16:13karlmag: not really sure there was one. I guess "usefulness" might be one though.
16:13imirkin_: usefulness to...
16:13imirkin_: getting reclocking working well on G92 would be nice
16:14imirkin_: they were pretty beefy cards
16:14karlmag: in general and to this project I suppose.
16:18karlmag: Have a christmas to get through and a bit of act to get together, but hope to eventually "set up shop" so that I (sanely) can help do some testing at the very least.
16:21karlmag: I guess having a range of cards might be helpful then.
16:41imirkin: karlmag: yep
16:50etnk: imirkin_: if you're still around, i couldn't get x to run via nvidia with mmiotrace, it hard locks the machine and i'm left with a log with only 33 lines, figure there should prob be more.. when i enable mmiotrace i did get some message about irq not being avail, i can't remember, trying to look thru journalctl for the msg but not sure if it ever got logged
16:51imirkin: hmmmm weird
16:51imirkin: you did start out without nvidia loaded right?
16:53etnk: tried several time, if i didn't enable the tracer x would start fine, with it hard locks with a cursor on the screen (seems to change the screen mode iirc)
16:53imirkin: if you're willing to forego all acceleration, you could try using xf86-video-nv
16:56etnk: well i'm still willing to be a monkey for you and other nouveau devs if you guys are interested in working on this with me, not now i've done enough for tonight i think but i'll def file a bug report (what do you think?)
16:56imirkin: go for it
16:57etnk: figure i'm capable of doing this kind of thing where other ppl with the hardware trying to run linux might get discouraged
16:57etnk: anyway, thank you so much for your time on this
16:58etnk: i'll try to post a bug report with some info in a few days, though imma try to swith res real quick before i go
16:58imirkin: what resolution were you running again?
17:00imirkin: errrr that should def have been fine
17:01imirkin: as for discouraging people from trying linux... not a lot we can do
17:01imirkin: there's probably 200-500x more manpower that goes into the nvidia proprietary driver, and they have documentation
17:02imirkin: (not to mention hw access)
17:03etnk: yeah i remember when amd merged with ati way back when, such a shock as back then it was always nvidia+amd that ppl prefered for linux
17:04etnk: i dunno if true but iirc they approached nvidia first but due to company/ceo politics and/or some deal with microsoft
17:08etnk: ok just checked, switching res does nothing, anyway will file a bug report
17:08etnk: ty for your time
17:10imirkin: gnurou: btw, i see [ 12.257617] nouveau 57000000.gpu: DRM: failed to create ce channel, -22 with kernel 4.4-rc5, otherwise seemingly-loaded firmware
17:11imirkin: aaaan there's some kind of watchdog
18:03sarnex: dumb question, does this mean the card isnt supported by nouveau at all? [ 12.889] (EE) Unknown chipset: NV124
18:03sarnex: have a user having trouble with gallium nine, turns out hes using llvmpipe
18:33imirkin: sarnex: GM20x doesn't have any accel with nouveau for now
18:34imirkin: that's most of the GTX 9xx series
18:35sarnex: imirkin: thanks alot