01:53imirkin: skeggsb: any thoughts on https://bugzilla.kernel.org/show_bug.cgi?id=206299 ?
01:54imirkin: sounds like something missing in the turing disp error handling
02:02skeggsb: nfi what's causing the original issue, but there's definitely a couple of things i should fix there
02:03skeggsb: window immediate exceptions would hit this, because we don't provide a method list for the debug output
02:03skeggsb: but.. even weirder
02:03skeggsb: chid 73 is the first cursor channel
02:03skeggsb: and PUSHBUFFER_ERR makes zero sense, it's a PIO channel
02:04skeggsb: i'll fix the other bits shortly, but nfi what the core issue is.. the mmio error codes are likely a sign of something more severe going on
02:05skeggsb:bbl - gym time
03:55imirkin: skeggsb: maybe chid comes from a suspect location?
10:38mbuf: Does anyone use the nouveau driver with System76 laptop models that come with Nvidia GeForce graphics cards?
10:47HdkR: Would need to be an old one since the current generation machines have Turing which won't work under Nouveau
10:55mbuf: I see. The System76 Gazelle provides GTX 1650, while the Oryx and Serval WS both use RTX 2060, and all of them are based on the Turing architecture unfortunately.
10:56mbuf: They are offering the Intel UHD Graphics for the lower-end models, unfortunately. I don't need the GPUs basically, just the latest processor, and storage will be fine.
10:57mbuf: I don't get it though. What is the point in providing coreboot open firmware, if the graphics driver is closed.
10:58HdkR: Some people are fine with that arrangement
10:59mbuf: HdkR, I see
11:03karolherbst: I don't understand having a dedicate GPU in a laptop now that we have useable TB3 :p
12:28Zevv: Hello #nouveau. I am looking for a way to get some accounting of GL memory usage per process, is there tooling for that?
12:30Zevv: or maybe any gl extensions that allow querying if this type of information
12:31karolherbst: I don't think we track it all that well and we don't report it to the applications
12:31Zevv: ok, fair enough :)
12:31Zevv: thanks for confirming
18:39maccraft123: imirkin: hey
18:39maccraft123: gpu has been running good
18:39maccraft123: but when i try to load anything vulkan
18:39maccraft123: it doesn't run because dri2
18:39maccraft123: so to fix dri2 issue
18:39imirkin_: there's no vulkan for nouveau
18:40maccraft123: and to make my life easier
18:40imirkin_: (i don't remember your setup, tbh)
18:40maccraft123: i decided to use reverse prime to make amdgpu primary gpu and to amd gpu to copy framebuffer to nouveau card
18:41imirkin_: ah ok
18:41imirkin_: you can also do like Option "DRI" "3" in the xorg config to enable dri3
18:41imirkin_: semi-expiermental, but basically fine
18:41maccraft123: imirkin_: 2 monitors, hdmi and vga connected mcp78 and headless amdgpu
18:41imirkin_: yeah, doing amdgpu as primary is ... not ideal.
18:42imirkin_: i think with Option "DRI" "3", things will work fine
18:42maccraft123: i run i3 as my wm
18:43maccraft123: imirkin_: xorg.cond.d/10-gpu.conf https://bpaste.net/QIWA
18:44imirkin_: you're welcome to do it that way :)
18:44imirkin_: but adding Option "DRI" "3" into the Device section for nouveau would allow you to use regular prime for the amd gpu
18:44maccraft123: regular prime runs without it
18:45imirkin_: yeah, i know, but you'd get DRI3
18:48maccraft123: oh hey it works with dr3
18:50maccraft123: and it broke
18:52maccraft123: ok i was doing the screens too fast
18:52maccraft123: moving screen setup from xinitrc to i3 config helped
18:53imirkin_: using nouveau as primary?
18:53imirkin_: well if you want to use nouveau as primary, with dri3, you can, using the above option.
18:53maccraft123: i used that option
18:55maccraft123: and vulkan runs fine
18:55imirkin_: using nouveau as primary, right?
18:55maccraft123: amdgpu as primary
18:55imirkin_: then that option does nothing for you.
18:55maccraft123: it fixed stuff
18:56imirkin_: if you want to use nouveua as primary, add that option, and life will be good.
18:56imirkin_: hm, surprising it would have any effect.