07:50RSpliet: imirkin_: f->allWarp in emitFlow() on gk110, is that the flag used for "only jump if all warps unanimously shouldn't take the if-codepath and execute the else-path instead"?
08:11gnurou: mmm, anyone knows if there is a way to make xserver recognize a new device which module has been inserted *after* it was started?
08:12gnurou: i.e. I start X, run "modprobe nouveau", and "xrandr --listproviders" lists it
08:12gnurou:discovers the joys of Optimus
08:14karolherbst: gnurou: I do it all the time :p
08:14karolherbst: gnurou: use DRI3
08:15karolherbst: xrandr wont show it, but that doesnt matter
08:15karolherbst: gnurou: https://nouveau.freedesktop.org/wiki/Optimus/ "DRI3"
08:16karolherbst: gnurou: and if you want to unload nouveau, use this config: https://gist.github.com/karolherbst/1f1bdd1a3822df74097f
08:17karolherbst: that was Xorg wont even claim the device
08:18gnurou: karolherbst: mmm I think I meet all these requirements, yet the Intel driver is used even when using DRI_PRIME=1
08:18karolherbst: with that you can rmmod nouveau even while X is running
08:18karolherbst: gnurou: you need to tell intel to use dri3
08:18karolherbst: see the xorg.conf
08:18gnurou: ah, I see
08:18gnurou: thought it would do this by default...
08:19karolherbst: apperantly, there are many users with issues
08:19karolherbst: (dri3 works better here than dri2 actually)
08:19karolherbst: but the dummy ddx hack is really handy
08:19gnurou: wow, I haven't messed with an Xorg config file in *ages* :)
08:20karolherbst: if you load nouveau at runtime, xorg claims the device immediatly
08:20gnurou: oooh they are now using a xorg.conf.d!
08:20karolherbst: which makes unloading it impossible
08:21karolherbst: chances are that your kernel crashes when you unload nouveau, but it happens with a <1% chance
08:21karolherbst: but at least I know why :/
08:26gnurou: thanks, restarting X to try this...
08:27karolherbst: do you have the dummy ddx installed
08:27karolherbst: forgot about that, sometimes it is missing
08:28gnurou: that was missing, thanks!
08:30karolherbst: with that it is actually possible to switch between Prime-nouveau/bumblebee-nvidia without restarting X :3 makes things a lot easier for development on the same machine
08:30gnurou: annnd working perfectly! thanks a lot
08:30gnurou: interesting that DRI3 needs to be explicitly enabled
08:31karolherbst: I think it got enabled later
08:31karolherbst: but distributions default to 2
08:31karolherbst: there is a compile flag actually
08:32karolherbst: and some distribution set this to 2
08:35gnurou: mm? suddently it ceased working
08:36karolherbst: mhh odd
08:36gnurou: ah, that's because nouveau failed to probe my chip after I inserted/removed the proprietary driver
08:37karolherbst: pro tip: install bbswitch
08:37karolherbst: and turn off/on the gpu manually
08:38gnurou: ah, seems like things went south after bbswitch got inserted (probably by optirun)
08:38gnurou: that should be easy to handle
08:38karolherbst: it turns the gpu off
08:38karolherbst: echo ON or OFF
08:39karolherbst: nouveau only powers on the gpu for me the first time
08:39karolherbst: never really investigated why, but the saved pci stuff changed later
08:40gnurou: again, problem solved
08:40gnurou: now I feel guilty
08:40karolherbst: why :D
08:40gnurou: I wish we were as fast to answer your questions >_<
08:40karolherbst: I should have created a wiki page for that
08:41karolherbst: "pro tips for nouveau develpment on prime setups " :p
08:41gnurou: you should open a github issue tracker for me, and only allow yourself to make 1 post every second week
08:42karolherbst: well, at least you got the gp100 firmware out pretty fast, allthough it is pretty much useless too :D
08:43gnurou: yeah, I may just as well posted the output of /dev/random, nobody would have noticed
08:44gnurou: well except skeggsb
08:44karolherbst: ohh, I doubt that :D
08:44karolherbst: well, no clue what he has anyway
08:44karolherbst: so maybe he would have
08:45karolherbst: gnurou: anyhow, did you get any reply rearding the thanks from my side regarding the super usefull vpstate table :p
08:46gnurou: thanks anyway, I don't know what more I can do to make the Kepler reclocking advance, but I will wave my whip next week
08:46gnurou: I made sure to transmit your feelings on the topic... with my own words
08:47karolherbst: so something like "we knew it all along" became "many thanks for the documentation, so that we could verify our theories and guesses on that topic" :p
08:52gnurou: the slide was actually towards the opposite end of the courtesy spectrum
08:58karolherbst: XDC will be much fun, if we have time, we could even inclue benchmarks where we are pertty close to nvidia :p :D
08:58karolherbst: but I doubt this is the general idea of the nouveau XDC talk
08:58gnurou: by all means, do it
08:59karolherbst: allthough... showing off with working reclocking might fit actually
09:06karolherbst: gnurou: but you know what? I doubt they really looked into the stuff I wrote, because that should have at least create one big wtf moment, especially if they think that giving us the vpstate table is "enough" for us
09:06karolherbst: or they think, this is clearly what we need now
09:07karolherbst: because thats like the very core of gpu boost as far as I can understand all that stuff related to turbo boost
09:07karolherbst: *gpu boost
09:08karolherbst: well, + the "max" entries in the other table, but I wont ask for trivial stuff like that :p
09:22karolherbst: gnurou: actually, releasing the vpstate docs caused _more_ work for me now, because I have to rename stuff :/
10:23Tom^: karolherbst: you were right cs:go 64bit client fixed bunch of stuff
10:24Tom^: now im only facing a tiny issue where a texture on the arms dissapears after a while but that i can live with :p
10:31Lekensteyn: What is the appropriate category on bugs.fdo for DRM/nouveau bugs? There is only a Xorg Driver/nouveau and DRI DRM/other (even the new amdgpu got its own category :/)
10:31karolherbst: Tom^: yay
10:32karolherbst: Lekensteyn: https://nouveau.freedesktop.org/wiki/Bugs/
10:33Lekensteyn: karolherbst: thanks, and applied the category :)
13:33Tom^: this is boring, no issues in all my games. and nouveau simply just works :(
13:33Tom^: what todo!
13:35inglor: karolherbst: the latest HEAD of the stable branch with the patch for the sensors = reduced the power about 1W \o/
13:36karolherbst: it shouldnt
13:36karolherbst: Tom^: :D
13:36karolherbst: Tom^: buy games?
13:37karolherbst: inglor: I guess this is just random
13:37karolherbst: inglor: also, the higher the temperature of the gpu, the higher the power consumption
13:38inglor: well one of the cores came down to 14.96W but temp still @ the forties..
13:38inglor: this is with the nvapoke -c1 0x20200 0x60 27722455 in place
13:38karolherbst: yeah, well
13:38karolherbst: the more idle your gpu, the higher the power savings too
13:39inglor: yeah maybe I should start using the i7 gpu :D
13:39inglor: then can become really idle
13:39inglor: (but then again then it's losing the point of a dedicated gpu..)
13:57Tom^: karolherbst: hm shouldnt the * in the boost file be after the entries a bit like the pstate file?
13:58Tom^: karolherbst: so they are uh aesthetically similiar :p
13:58Calinou: I just donated to Mesamatrix :)
14:03imirkin: gnurou: fwiw my recommendation is that unless you're looking to flip between nouveau and nvidia, to not use bumblebee at all.
14:04imirkin: Tom^: get different games. the stuff i'm procrastinating debugging are things that just hang my whole system =/
14:04Tom^: heh those sucks
14:05imirkin: esp without a separate for-debug-only system
14:06Tom^: get a rpi and a monitor :D
14:06imirkin: ... and plug an nvidia gpu into it?
14:06Tom^: well i thought more you needed a system to netconsole / ssh but fair enough.
14:07imirkin: i want a system that i don't care if it hangs and reboots
14:08Tom^: i wonder how well it would work to have two nvidia cards in the system non sli, and passthrough the second in kvm and run linux and nouveau on that and debug
14:08imirkin: i have 3 cards :)
14:09imirkin: i've thought about pushing stuff through to kvm
14:09imirkin: but haven't gotten that past the thought stages
14:09Tom^: its an interesting concept atleast if it works
14:09imirkin: i have a GK208, GT215, and NV34 plugged in right now :)
14:15inglor: imirkin: I hope someone else pays the electric bill ;)
14:16imirkin: RSpliet: tbh i have no clue what allWarp does. i don't think it's ever set (by nouveau). pretty sure it's not what you said - for that nvidia generally does a "vote" to determine whether everyone has the same value for the predicate.
14:16imirkin: inglor: meh ... they're not super-powerful gpu's
14:16imirkin: the a/c tends to dominate my power bill
14:16Tom^: i bet my 780ti wastes more power then all of your three combined.
14:18inglor: probably my 690 is more than your three combined..
14:19imirkin: seems eminently likely
14:19imirkin: the GT215 is actually semi-beefy - it's a GT 240 with GDDR5 vram, but ... not in comparison to actual beefy gpu's :)
14:21karolherbst: Tom^: huh, why?
14:21karolherbst: Tom^: :D
14:21imirkin: Tom^: btw, in re "what to do", now you can enjoy playing the various games :)
14:22imirkin: [reminds me of the world of warcraft south park...]
14:24Tom^: imirkin: haha
14:24Tom^: karolherbst: oh it itches my OCD
14:25Tom^: karolherbst: http://i.imgur.com/qSFmokN.png see! im going insane.
14:25karolherbst: start a petition if that's so important for you :p
14:25karolherbst: well having the * in front is the better design anyway
14:25karolherbst: imagine having checkboxes _after_ the sentence
14:30Tom^: karolherbst: https://www.change.org/p/karolherbst-unified-design-of-pstate-and-boost-file-in-nouveau
14:31karolherbst: yeah well, I won't care anyway :p
14:31Tom^: =D =D
14:31karolherbst: maybe more like 100.000
14:32karolherbst: you have to expect that 95% being only "followers", and those I ignore anyway
14:33inglor: if you get more than 5 signs I will sign as well!
14:33karolherbst: like there are only bs petitions on that site...
14:33inglor: I will even suggest a patch to fix that :D
14:33Tom^: karolherbst: haha i googled "create free petition" or similiar
14:34inglor: Tom^: I wanted to do the same for a joke for a friend
14:34inglor: but almost all of them want paypal and email
14:34karolherbst: yeah well, they have to make money somehow
14:38karolherbst: mupuf: do you think this patch makes sense at all? https://github.com/karolherbst/nouveau/commit/774dd8d7c31bca61af63ecfae747d34c073434ba
14:38karolherbst: mupuf: I could also just get the last cstate in the list and get the baseclock domain clock out of that
14:38karolherbst: *vpstate now anyway
14:39karolherbst: but I guess this is a cleaner design, because it removes the for loop we would need without that
15:48imirkin: Lekensteyn: thanks for doing the analysis. i guess we were both right - the hdmi audio device does come up a lot, but hardly always. and never with _PR3 (or at least not sufficiently often)
15:48imirkin: Lekensteyn: you can consider my objection lifted
15:52imirkin: Lekensteyn: one small suggestion, if it's easy, detect the situation where you're breaking runpm, and notify about it. it's pretty hard to tell why runpm isn't working, and this would be a nice simplification. dunno if it's easy though.
15:53Lekensteyn: imirkin: the user can tell this my checking the runtime_status and runtime_usage fields in sysfs
15:53imirkin: that tells them *why* it's not suspending?
15:53Lekensteyn: in the case of PR3, it is because the pcieport is busy and cannot suspend
15:53Lekensteyn: in other cases, it should always suspend using the DSM method
15:54imirkin: what will runtime_status/runtime_usage say?
15:54imirkin: just "i'm not working, and i won't tell you why", right?
15:54Lekensteyn: if runtime_usage drops to 0, then runtime_status might show "suspended" if "control" is set to auto (done by default in nouveau)
15:54Lekensteyn: and starting with (probably) 4.8, this will also be the case for the pcieport devices
15:55imirkin: my point is, most users aren't experts in runpm
15:55Lekensteyn: unfortunately it is a bit harder to track down why the runtime_usage count might be non-zero
15:55imirkin: hence my suggestion for the print saying "i'm breaking your shit"
15:55Lekensteyn: btw, are you considering the case where an audio device is present?
15:56imirkin: you didn't find one in your db, but that's hardly exhaustive
15:56Lekensteyn: it could probably be detected while nouveau is suspending, check the runtime usage count of the audio client (registered via switcheroo)
15:56Lekensteyn: and print a warning if this is non-zero
15:57imirkin: anyways, if it's easy, i'd recommend doing it
15:57karolherbst: but that's a really rare corner case, isn'T it?
15:57imirkin: since it'll make users' life easier
15:57imirkin: karolherbst: hard to tell - Lekensteyn's analysis only saw 20 examples
15:57karolherbst: I mean
15:57karolherbst: hdmi audio in use, but not the nvidia gpu
15:57imirkin: karolherbst: from the sounds of it, it's "audio subfunction exists"
15:57karolherbst: that would mean I plug an audio system on the nvidia gpu on the hdmi port
15:58imirkin: not "audio is in use"
15:58karolherbst: I see
15:58imirkin: so either your setup hits it or doesn't, depending on decisions the platform integrators made
15:58Lekensteyn: let me see if the switcheroo infrastructure allows me to get the audio client
15:58karolherbst: I think the proper fix would be to unregister the audio subfunction from alsa and suspend completly
15:58karolherbst: or is that, what you plan?
15:59Lekensteyn: I think it seemed more logical not to suspend when the audio device is busy (e.g. playing hdmi audio)
15:59karolherbst: Lekensteyn: read again^^
16:00imirkin: Lekensteyn: agreed
16:00imirkin: Lekensteyn: actually i'm not 100% sure nouveau will allow you to play hdmi audio without a video signal
16:00imirkin: i believe it's technically possible, but in practice it's a sub-usecase of a sub-usecase
16:00Lekensteyn: karolherbst: I read it again, what is the point? Removing a device from alsa will result in nobody managing the device
16:01karolherbst: will the nvidia gpu suspend if the display goes into suspend mode except audio?
16:01Lekensteyn: I read the HDMI spec, but it seems that a video signal is mandatory for the audio to function
16:01imirkin: if a link is up, nouveau shouldn't suspend it
16:01karolherbst: Lekensteyn: yeah well. How much sense does it make to have the gpu suspended, but a display with audio system plugged in playing audio, when the display isn't in use
16:01Lekensteyn: or, it suggests that the bandwidth available for audio depends on the clock/bandwidth for video
16:01karolherbst: and the only case this happens is, when the link is down anyway
16:01imirkin: although ... if the crtc isn't going, i think it will
16:01imirkin: since you might have a monitor plugged in but not be using it
16:02karolherbst: but can you use the displays audio in that case?
16:02karolherbst: or are there audio only HDMI devices?
16:02imirkin: karolherbst: i think you have to have a dummy video signal if you want that
16:03imirkin: and i don't think nouveau supports creating such a dummy signal
16:03karolherbst: anyway, I don't see the use case for this
16:03imirkin: karolherbst: audio receiver
16:03karolherbst: so audio only hdmi devices?
16:04imirkin: yes. although technically they'd have to support video as well
16:04imirkin: just wouldn't have to do antyhign with that video
16:04imirkin: i believe they come up as a regular ol' monitor as far as the video card is concerned
16:04karolherbst: if I would have such a device I could have at least check how mac os x does in that situation, sadly I don't
16:04imirkin: there might be an EDID bit that indicates they're audio-only, dunno
16:05karolherbst: Lekensteyn: you know what I would do? Unregister the audio device when video goes into suspend and wait for user to complain, that they actually need this use case, because I am sure it doesn't exist at all
16:05karolherbst: anyway, you won't connect an audio system via hdmi but S/PDIF
16:06karolherbst: and also not on your gpu
16:06imirkin: most laptops don't have a S/PDIF output
16:06karolherbst: breaking suspend is worse than supporting audio only hdmi is good for in my opinion
16:06imirkin: but most laptops *do* have HDMI/DP outputs
16:08karolherbst: mhh right, didn't thought about that, because like every laptop of mine had at least one S/PDIF :/
16:08Lekensteyn: I wonder how radeon/i915 handles this stuff
16:08karolherbst: it fact it shouldn't matter with a proper design
16:08karolherbst: if hdmi is in use the ref count goes up on the subdevice
16:08imirkin: Lekensteyn: i believe "poorly"
16:09karolherbst: and the parent device only goes into suspend if the parent has no use, and all its subdevs
16:10Lekensteyn: the parent device is the pcie port, the subdevices are video and audio functions of the nvidia device
16:10karolherbst: I think hacking around for that in alsa or nouveau is just a really bad solution to this problem
16:10karolherbst: Lekensteyn: so the audio isn't a subdevice of the gpu?
16:10Lekensteyn: have you seen Lukas's post about vga switcheroo vs audio?
16:10karolherbst: not yet
16:10Lekensteyn: unfortunately no :(
16:10karolherbst: Lekensteyn: "[Nouveau] vga_switcheroo audio runpm"?
16:11imirkin: Lekensteyn: anyways, my main goal here is to reduce the situation where people come here and say "my gpu isn't autosuspending", and me being "uhhh, no clue why"
16:11Lekensteyn: l1k basically proposes to use (a not yet merged) "device links" functionality to make the video device the "supplier" (of power) and the audio device a "consumer"
16:11Lekensteyn: yes tht one
16:12Lekensteyn: imirkin: I would always suggest sudo sh -c 'echo 1 > /sys/bus/pci/devices/0000:01:00.1/remove'
16:12Lekensteyn: my main monitor (connected via miniDP anyway) does not even have hdmi audio, so no functionality is lost
16:12Lekensteyn: not ideal, but it is a workaround
16:13karolherbst: this really should be implemented in the kdev runpm area and not in the drivers :/
16:14Lekensteyn: what exactly? The dependency between two PCI functions?
16:14karolherbst: if it is the same device, but reported as two, then this information should be known on a deeper layer
16:15karolherbst: and if one of those reported ones is unused but the other not, no suspend
16:15karolherbst: but ...
16:16karolherbst: somehow the kernel would have to detect such dependencies. Allthough the audio driver could tell it
16:17karolherbst: but I guess that's also the idea of the device links
16:19Lekensteyn: device links are a generic idea, but if PCI somehow can somehow treat multi-function PCI devices in an automatic way that would also be great
16:20Lekensteyn: currently reading through the PCI specs if I can find something on this
16:20karolherbst: yeah, it would be much better if we could detect this out of the pci devices directly without needing to detect that in the drivers
16:21karolherbst: but isn't the gpu at like 01:00.0 and the audio device at 01:00.1?
16:21karolherbst: or would the audio be at 02:00.0?
16:21karolherbst: I don't have 02:00.0, but 03:00.0
16:22Lekensteyn: the audio is a subfunction at .1 (video is at .0 indeed)
16:22karolherbst: ahh okay
16:22karolherbst: at least something
16:22Lekensteyn: and if you happen to have a separate bus or device ID, then it is probably a separate device
16:23karolherbst: so the topology is somehow there already
16:25karolherbst: for me "01:00.0" is a subdev of 00:01.0 anyway
16:26karolherbst: Lekensteyn: can you check the output of "ls -lah /sys/bus/pci/devices" ?
16:26Lekensteyn: yes, 00:01.0 is the pcie port
16:26Lekensteyn: you can see the topology with lspci -tvv
16:26karolherbst: can I see your output of tvv?
16:27Lekensteyn: http://sprunge.us/YLGG (also added -nn to lspci)
16:27karolherbst: ohh you don't have an audio thing...
16:28karolherbst: funny that tvv doesn't show the "00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller"
16:28karolherbst: it always removes the controller
16:28karolherbst: yeah well
16:28Lekensteyn: I do have the audio thing if I runtime resume, remove and rescan (and keep the pcie port non-suspended while doing that)
16:28karolherbst: ahh nice
16:29karolherbst: would be interessting to know how it looks like in that case
16:29karolherbst: Lekensteyn: "echo 1 > /sys/bus/pci/devices/0000\:01\:00.0/rescan" is enough?
16:31Lekensteyn: no, remove eis needed first, see https://bugs.freedesktop.org/show_bug.cgi?id=75985
16:33karolherbst: why do I remove my nvidia gpu while it is turned off
16:33Lekensteyn: this is my lspci -xxxxnnvvv when booting in discrete-only mode http://sprunge.us/bUhH (tip: you can use lspci -F lspci.txt ... to read it)
16:33Lekensteyn: removing while it is off with nouveau should work?
16:34karolherbst: yeah well, without nouveau
16:34Lekensteyn: oh, bbswitch?
16:34karolherbst: can't handle the situation
16:35karolherbst: would have to make the acpi call by hand or something
16:35karolherbst: or I just remove those pci calls
16:36Lekensteyn: weird formatting. If you run kernel 4.6 or newer with acpi debugger enabled, you can also use "acpidbg" in the kernel tools tree
16:36karolherbst: Lekensteyn: okay, both devices are bound to 01
16:36karolherbst: not 01.00 as I would have thought
16:36karolherbst: but maybe they are
16:36Lekensteyn: after executing "acpidbg" you can execute something like "Eval \_SB.PCI ..." (not sure if it handles arguments though)
16:36karolherbst: and lspci only prints it wierd
16:36karolherbst: yeah, I would need to pass arguments
16:37Lekensteyn: not 01:00.0 and 01:00.1? can you post the output?
16:37karolherbst: I mean, their parent is 01
16:38Lekensteyn: that seems to work?
16:38Lekensteyn: or well, that is what I currently expect
16:38karolherbst: so the audio chip isn't a chile of 00:01.0, but 01: indeed
16:38Lekensteyn: 01 is the shared bus id
16:39karolherbst: maybe that lspci outout is just silly and tries to visualize smart
16:39karolherbst: that's why I asked for that ls -la output :p
16:39Lekensteyn: I think it should be read as child of 00:01.0, bus 01 with subdevices 00.0 and 00.1
16:39karolherbst: make that ls call and we will know for sure
16:39Lekensteyn: see also the top level [0000:00] (domain 0000, bus 00)
16:43karolherbst: guess I have to reboot
16:51karolherbst: Lekensteyn: okay, so bbswitch cant handle it, when the pci device gets removed
16:51Lekensteyn: ah right
16:51Lekensteyn: indeed it should not be done
16:52Lekensteyn: bbswitch keeps a struct pci_dev * around, but that is invalidated when you remove it..
16:52Lekensteyn: I have a branch where I turn bbswitch into a pci device driver so it is basically nouveau without video handling
16:53Lekensteyn: not finished yet since I want to focus on nouveau first
16:53karolherbst: can it be loaded alongside nouveau in that case
16:53Lekensteyn: yes, no problem
16:54Lekensteyn: the new version?
16:54Lekensteyn: only if it is ON
16:54Lekensteyn: if it is off, then it will be claimed (I think it is a nice feature)
16:54karolherbst: ahh okay
16:54karolherbst: then it is fine
16:54karolherbst: I dont have nouveau loaded while the gpu is off
16:55Lekensteyn: one pain point at the moment is to provide backwards compatibility via the /proc/acpi/bbswitch interface
16:55Lekensteyn: the new pci device works best when using the bind, unbind (and maybe new_id) interfaces in sysfs
16:57karolherbst: well, I dont have any nvidia audio device no matter how hard I try
16:58karolherbst: still I have no 02:00 device at all+
16:58Lekensteyn: but you do have an hdmi port? What laptop do you have?
16:58karolherbst: all my ports are on intel
16:59Lekensteyn: ... well then it makes sense that you cannot get an audio function :P
16:59karolherbst: clevo p150sm or something like that
16:59karolherbst: well, the device could be still there
16:59karolherbst: in the nvidia vbios I also have 10 connectors and one signal thing
17:00karolherbst: and in xrandr I have on intel already 7 ports :D
17:00Lekensteyn: insane :p
17:00karolherbst: and nouveau really treats my gpu as if it had displays partly
17:01karolherbst: fun fact, allthough my display+ is connected via a DVI to miniDP adapter, it is listed under HDMI1
17:02karolherbst: not DP1 or DP2 as you might would think
17:03Lekensteyn: euhh, parsing error?
17:03karolherbst: no clue
17:05karolherbst: Lekensteyn: maybe you know this
17:06Lekensteyn: dunno how nouveau parses this information
17:07karolherbst: Lekensteyn: any ida what PX5.0 is
17:08Lekensteyn: Power Express?
17:08Lekensteyn: AMD's hybrid graphics solution
17:09karolherbst: because in my vbios it is called+ PX 5.0 and there is a BACO and another mode
17:10karolherbst: well BACO is a mode where the bus is still active, even when the gpu should be turned off (to enable temp readings and stuff)
17:10Lekensteyn: BACO is an abbreviation of BACON
17:12Lekensteyn: nvm not sure, maybe I have read too many specs today
17:36Lekensteyn: karolherbst: where did you see PX 5.0 btw? In the vbios of nvidia..?
17:36Lekensteyn: or in ACPI?
18:03t-ask: hi, how yould I determine GPU temp again?
18:07t-ask: I think texture issue is better today, CPU is only 3ß-50% running with all threads
18:07t-ask: temp: 62Ĉ
18:09t-ask: bump mapping resolutions still looks like lower resolution.
18:46optraz: hi, when i run optirun glxgears -info
18:46optraz: i got the followings
18:46optraz: [ 1107.643951] [ERROR]Cannot access secondary GPU - error: [XORG] (EE) Unknown chipset: NV117
18:46optraz: [ 1107.643969] [ERROR]Aborting because fallback start is disabled.
18:46optraz: anyone can help here?
18:48imirkin: optraz: what's your goal?
18:48imirkin: (whatever that is, chances are using optirun is your first mistake)
18:50optraz: this new laptop (which i got today) has two vga, the intel and nvidia and i woudl like to use the nvidia vga
18:50imirkin: vga like "db-15 vga port", or vga like "video graphics adapter"
18:51optraz: well, i just want to use the 3d driver.
18:51optraz: right now it is using intel vga which is very slow in games
18:52imirkin: either way, without reclocking, chances are that your intel gpu will be just as fast as the nvidia gpu. so your choices are to load nouveau and let it auto-suspend the gpu (so you get the powersavings), or deal with one of the ways to get the nvidia blob working in an optimus setup
18:52imirkin: if you really want to get nouveau going so that you can use it for offloading, start by reading https://nouveau.freedesktop.org/wiki/Optimus/
18:53imirkin: (note - you do not have a hardware mux, so ignore those bits)
18:54optraz: chances are that your intel gpu will be just as fast as the nvidia gpu. // i have not try the nvidia gpu, so i cannot tell you if this is the case.
18:54optraz: load nouveau // yes, module nouveau is loaded i believe
18:54optraz: yes, it does
19:02optraz: An updated graphic stack (Kernel, xserver and mesa).
19:02optraz: KMS drivers for both GPUs loaded.
19:02optraz: DDX drivers for both GPUs loaded.
19:02optraz: what are the equivalent package name in debian?
19:03Lekensteyn: KMS is the nouveau kernel module (ok)
19:03imirkin: the nouveau ddx does not support your GPU anyways, and with DRI3 you don't even need a DDX in the first place
19:04optraz: imirkin: how do you mean does not support my gpu?
19:05Lekensteyn: the latest maxwell cards are not supported by the nouveau DDX driver (xserver-xorg-video-nouveau)
19:06Lekensteyn: you have to use xserver-xorg-video-modesetting instead
19:06imirkin: ... which is built into xorg
19:06imirkin: although for all i know it might be distributed as a separate package by your distro of choice
19:06Lekensteyn: ...but since we are talking about debian, we have split packages.
19:06imirkin:doesn't do distro support
19:07Lekensteyn: oh, now debian has merged it into xserver-xorg-core
19:07Lekensteyn: (in stretch and sid, not wheezy stable)
19:07optraz: so i have xserver-xorg-core and xserver-xorg-video-nouveau install
19:08imirkin: and that's why i don't do distro support :)
19:10imirkin: karolherbst: if you get a chance, mind testing https://patchwork.freedesktop.org/patch/99103/ on your kepler gpu?
19:11t-ask: Looks like not setting "thread_submit=false" hides all NPC names. Setting it to flase, shows all names even if covered by wall.
19:12imirkin: t-ask: i think you want to be reporting this stuff in #d3d9
19:12t-ask: yes, I'm experimenting a bit more and then I add this to the issue report
19:13imirkin: t-ask: nothing you've provided indicates there's any bug in nouveau
19:13t-ask: What I did I patched the latest nouveau patch of KArol
19:14imirkin: hakzsam: if you're around, check https://patchwork.freedesktop.org/patch/99103/ on your fermi (using the test i refer to in that patch)
19:14t-ask: new kernel version and newest nouve git
19:34t-ask: How to determine the Nvidia VideoPciDeviceId?
19:35Lekensteyn: t-ask: don't know the context, but you can see the numeric device id using lspci -nnd10de:
19:39t-ask: SO I assume the first number is the vendorID NVIDIA Corporation GK110B [GeForce GTX 780 Ti] [10de:100a] (rev a1)
19:40imirkin: 10de is the vendor id, 100a is the device id
19:43t-ask: ahh, Segmentation fault (core dumped)
19:47Lekensteyn: imirkin: I was mistaken with the year btw, the BIOS cutoff date for using _PR3 in Linux is not 2013 (Windows 8) but >= 2015 (Windows 10)
19:48Lekensteyn: officially 2013 should also be working, but the Linux PCI devs seem conservative here
19:55t-ask: I guess this si d3d9 related https://pastee.org/e2qz3
19:56imirkin: i'd definitely start with that.
20:12TA5K: Slowly I think the "dx9single" option of GW2 is improving graphics quality as it should be.
20:15TA5K: ok, NO .)
20:46karolherbst: imirkin: do you still need somebody to test this
20:50karolherbst: skeggsb: yeah, I think I will change my code to follow at least the nvkm_clk_tstate idea, because it makes actually more sense than what I do
20:51karolherbst: in the end we should also save the current voltage and only change that, same as the temperature
20:51imirkin: karolherbst: would be great, yeah. on SM30 and SM20
20:51imirkin: i guess you only have SM30 at hand
20:52karolherbst: I also have my mcp79
20:52karolherbst: no idea if thats sm20
20:52imirkin: don't worry about that - only affects fermi+
20:52imirkin: SM20 = fermi
20:52karolherbst: so sm20 is fermi
20:52imirkin: SM30 = kepler1
20:52imirkin: SM35 = kepler2
20:52imirkin: SM50 = maxwell
20:52imirkin: SM60 = pascal
20:52karolherbst: yeah, the last things I knew
20:52imirkin: SM1x = teslas
20:53karolherbst: I wasnt sure about below sm30
20:54karolherbst: I hope I will be finished with the reclocking stuff tomorrow :/ though I highly doubt ben will pull it for 4.8 and pulling it partially doesnt make much sense
20:54imirkin: anyways, i only have a GK208 plugged in, so i can only test SM35. pretty sure it'll work the same on SM30, but worth checking
20:54karolherbst: except some minor things, which wont change a thing
20:54imirkin: SM20 is the bigger question mark, but ... should work ;)
20:55imirkin: [famous last words]
20:55karolherbst: will anybody care before reclocking works on fermi
20:55imirkin: when pbo downloads break - i assume so :)
20:55karolherbst: ohh right
20:55karolherbst: thats pretty basic functionality
20:56imirkin: besides, i regard any sort of breakage to be serious for kepler and below
20:57imirkin: or at least worth understanding
20:57Yoshimo: what is this SM stuff about ?
20:57karolherbst: its maxwell2 we dont care much about :p
20:57karolherbst: shader model
20:57imirkin: karolherbst: dunno about 'we', but definitely 'i'
20:58karolherbst: will be fun
20:58imirkin: and sadly, maxwell1 also falls into that group. i might change my mind if we get reclocking going on it.
20:58karolherbst: okay, so what does your patch change
20:58imirkin: but at least i feel bad about ignoring maxwell1 :)
20:58karolherbst: yeah :D you should
20:59karolherbst: reclockings works on maxwell1
20:59imirkin: mem reclock?
20:59karolherbst: and also on maxwell2
20:59imirkin: i was unaware
20:59karolherbst: it is the same as kepler
20:59karolherbst: imirkin: this is the needed patch: https://github.com/karolherbst/nouveau/commit/3bd7ebb11cd0a329dc63c4403a3241e2858bd835
20:59imirkin: so ... GM10x reclocking fully works on your branch? (or at least as well as kepler)?
20:59karolherbst: if I would fix it
21:00imirkin: i thought you only did core
21:00karolherbst: there are little differences, but there are also differences between kepler cards
21:00karolherbst: look at the patch
21:00imirkin: ok, but not in the stable_reclocking_v5 or whatever
21:00karolherbst: no, but that maxwell_reclocking branch +is based on it
21:01karolherbst: and only contains this
21:01karolherbst: and a cleanup patch
21:01karolherbst: so basically it just works
21:01karolherbst: and I think ben would merge it too
21:01karolherbst: ... yeah, I try to get this merged in 4.9 then
21:01imirkin: you should try to get people to test it
21:01karolherbst: I already did
21:01imirkin: i've been telling people there was no GM10x reclocking
21:02karolherbst: huh, I am telling that it works for 3 or 4 months already :P
21:02karolherbst: the patch is from end of february
21:02imirkin: i guess i'm behind the times
21:02karolherbst: those 4 cards
21:03imirkin: optraz: once you get prime going on your setup, might want to check karol's repo out - should help you achieve higher gpu performance levels.
21:03imirkin: karolherbst: anwyays, for that patch, just run the one test i reference in the comments
21:06karolherbst: imirkin: I pushed the maxwell cards on the kepler branch too now
21:07karolherbst: imirkin: well, it passes without and with the patch
21:08imirkin: karolherbst: ok thanks for checking
21:08imirkin: now just have to get some sucker with a fermi...
21:11karolherbst: well at least I know that pascal reclocking wont work easily because a lot of display stuff got moved around and the SEQ scripts are competly different :/
21:12karolherbst: mupuf: also, it would be nice if a maxwell2 gpu would be in reator, I might want to try some things out on that one
21:14karolherbst: well, at least pascal will be a lot of fun
21:15orbea: karolherbst: is this still useful for your stable reclocking branch? https://github.com/karolherbst/nouveau/commit/ad52418a53a8196605650e38829c01989ac7e0f8
21:16karolherbst: well, this is usefull if you want to get the right value out of the power sensor
22:15imirkin: skeggsb: any suggestions on filling http://hastebin.com/xuvodovaga.scala >
22:15imirkin: skeggsb: totals are easy, do we have a way to get the other stuff?