03:59sparky4: there is rendering isssues in quake4
04:06sparky4: let me dd it to the bug report
05:59damo22: https://i2.paste.pics/ILC48.png this is from the schematic for a T530/W530 thinkpad. I think GPIO12 from the nv card is *not* being used to control power settings because of the default configuration of R22 and R23. Does anyone know what mechanism could be used to set a low power state of the dGPU ?
06:01damo22: would it be VIDEO_THERM_OVERT or VIDEO_THERM_ALERT ?
06:11sparky4: karolherbst: ill test some more after i sleep
11:49karolherbst: damo22: what usually happens on laptops is, that firmware can ping some GPIOs on the GPU in order for the driver to react to it
11:50karolherbst: damo22: https://nvidia.github.io/open-gpu-doc/DCB/DCB-4.x-Specification.html#_gpio_assignment_table_entry
11:51karolherbst: there is a list of functions
11:51karolherbst: those are declared in the GPUs VBIOs
12:25karolherbst: sparky4: btw, is this a regression in quake4? and did you test with main?
15:36sparky4: karolherbst: ? test with main? regression?
17:40sparky4: quake 1 is broken white screen
18:16karolherbst: sparky4: right.. I was wondering if that's because you built the main branch and tried that or just used your distribution packages
19:32sparky4: i used game-data-package hmmmm
22:45pabs: sparky4: I think karolherbst is asking if you used distro packages of mesa and Linux, or if you built the main branches of upstream mesa/Linux and tested them
22:45sparky4: i used packaged versions
22:45pabs: (IIRC the answer is sparky4 only used the Debian bullseye/bookworm packages so far)
22:46sparky4: i need some help if we gonna compile mesa and such
22:47karolherbst: yeah.. that's unedrstandable, but as we already might have fixed those issues there is really no point bringing those issues up to us. If debian thinks those fixes are important enough they should backport them and include it in their packaging. We have fixed support cycles for mesa and do backport all fixes. Anything beyond that is the job of distributions.
22:47karolherbst: But if your issues still exist on the main branch, then it's our job to figure out what's wrong and broken
22:48pabs:notes some compile/install instructions are at https://nouveau.freedesktop.org/InstallNouveau.html
22:48karolherbst: anyway.. as long as you don't need to test mesa system wide, you can compile and install it inside a local prefix
22:48karolherbst: and launch quake from that
22:49karolherbst: pabs: ehh.. sadly those are super outdated and we should just point to the mesa docs :D
22:49karolherbst: sparky4: https://docs.mesa3d.org/install.html#
22:49pabs: time to delete most of the page then :)
22:50karolherbst: I hoped others would do that, now that the wiki can be changed by literally anybody creating a gitlab account, but as it turns out, we are still left with that job :(
22:51karolherbst: if building mesa, just make sure you also pass "nouveau" to gallium-drivers
22:51pabs: the wiki does seem to be outdated in general. I wonder if it is better to have docs maintained in and built from the mesa source instead
22:51sparky4: thats okay time to install the drivers! :D
22:51karolherbst: like -Dgallium-drivers="swrast,nouveau"
22:51sparky4: karolherbst: how?
22:52karolherbst: just change the part where it states '-Dgallium-drivers=swrast' in the doc by what I've written above
22:54damo22: karolherbst: thanks for the gpio docs, congrats on rust mesa
22:59sparky4: i see
23:32sparky4: FileNotFoundError: [Errno 2] No such file or directory: '/home/sparky4/p/mesa/include/KHR/khrplatform.h' shit
23:34karolherbst: sparky4: set -Dvulkan-drivers=''
23:34karolherbst: though that file really should be there...
23:34karolherbst: oh well