00:30sparky4: karolherbst: include/meson.build:34:4: ERROR: File KHR/khrplatform.h does not exist.
00:30sparky4: not there is there a push?
00:31karolherbst: ohh that's a GL header... I mistook it for a vulkan one
00:31karolherbst: but is the file really not there?
00:31sparky4: let me check
00:32karolherbst: maybe something went wrong cloning the repo? Because the file should really be there: https://gitlab.freedesktop.org/mesa/mesa/-/blob/main/include/KHR/khrplatform.h
00:32sparky4: it's not there xD
00:32karolherbst: is "git status" listing it as removed?
00:32sparky4: lets see
00:33sparky4: ah yeah it's not there
00:33sparky4: yeah it got deleted
00:33sparky4: let me .... re clone
00:33karolherbst: okay.. well just use "git checkout ."
00:33karolherbst: this will restore all deleted files
00:34sparky4: shit i removed the directory xD
00:34sparky4: link to the repo?
00:34sparky4: oh i see it
00:40sparky4: okay compiling! :D
01:03sparky4: Installing /home/sparky4/p/mesa/include/KHR/khrplatform.h to /home/sparky4/p/mesa/include/KHR .... what....
01:14sparky4: cant compile it
01:27karolherbst: why not?
01:27karolherbst: anyway.. I need sleep 😪
02:22sparky4: this is why "Installing /home/sparky4/p/mesa/include/KHR/khrplatform.h to /home/sparky4/p/mesa/include/KHR" it breaks here
02:33HdkR: I don't have that. What is your meson, build commands, and environment?
02:35HdkR: `git clone --depth=1 https://gitlab.freedesktop.org/mesa/mesa.git; cd mesa; mkdir build; cd build; meson ..; ninja;`
02:35HdkR: That works on my end with the requirements already setup
02:43sparky4: let me check
03:21sparky4: how do i "make install" ?
03:33sparky4: oh it worked with sudo ninja -C . install
06:04damo22: does anyone here know what would happen in nouveau if the ACPI in DSDT is mostly missing for NV optimus
06:06damo22: i mean, its not your bug if the bios is buggy, but im wondering if there are any hard assumptions on presence of ACPI methods
13:12sparky4: quake 4 still has some rendering issues
13:12sparky4: it is lighting issues
13:13karolherbst: but did the situation improve?
13:13karolherbst: and what about the other issues?
13:16sparky4: nope xD
13:17sparky4: buuut quake1 works now
13:17sparky4: but the original issue of quake4 lighting issues are around
13:17karolherbst: at least some progress
13:17sparky4: and zandronum crashes and eduke32 crashes with opengl
13:17karolherbst: what would help is, if you could file bugs for all the issues you have on the current main branch
13:17karolherbst: and for crashes please include the stacktraces if possible
13:20sparky4: oh! like file all the bugs? dindivirually or group them together
13:20karolherbst: if you see the same issue on multiple applications it's safe to create one
13:21karolherbst: but normally we want to be able to close issues once they are resolved and mixing multiple problems into one makes that hard
13:23sparky4: oh okay
13:27sparky4: ill make a few issues soon
13:35sparky4:waits for her drugs to kick in
14:41sparky4: gi cant to the issue reports soon as i am out of time ><
16:31aron: hi, I know it is not related to nouveau, but last time you had excellent ideas that fixed my GUI -- I have an unfortunate bug with i915: if kernel executes modesetting, the driver crashes, leaving the display in an awful blinking state
16:31aron: on the other hand, if I set both nomodeset and i915.modeset=0, kernel boots fine
16:32aron: but obviously resolution is limited
16:32aron: do you have any idea what to do, what kernel parameters to set, etc
16:32aron: device is an N4500 based BRIX
16:37hell__: aron: have you tried asking in #intel-gfx ?
16:37aron: here on oftc.net?
16:38aron: good idea
16:39aron: sorry for offtopic :)
18:02sparky4: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7264 updated
22:21damo22: i am trying to debug a buggy optimus ACPI driver in coreboot, which kernel version should i be using for a less buggy nouveau?
22:53damo22: in nouveau_acpi.c there is a flag "has_pr3", why are you skipping _DSM for optimus if _PR3 is present on the root PEG port?
22:54damo22: doesnt that mean the bios cannot set the link down and turn off the dgpu using _PR3 inside the NVOP function?
23:36HdkR: win 18
23:56karolherbst: damo22: because the kernel is calling it