Interesting though. The dGPU will still go to sleep when not actively using firefox. Then when switching back to firefox, there is a 2 second delay where firefox is unresponsive while it waits for the dGPU to wake up again. Not ideal.
Minecraft does not use it for me with only DRI_PRIME=1, not sure how you are getting that to work. But the above works for Minecraft for me, not that it needs the dGPU.
There was a major bug in the recent egl-wayland package on Arch. But Arch should have rolled it back few days ago, so if you haven’t updated try to update and see if you see a “new” package for egl-wayland.
My dGPU crashes when I try to plug the power adapter in while it’s in D3cold. This is really strange… Also it doesn’t want to go into D3cold while the adapter is plugged in. I made a post about this Here, but it appears that I have forgotten that Arch isn’t an official distro, heh… There’s also my post on the Arch BBS and I do not know what to do anymore.
The “bad” commit is somewhere between 6.8.9 and 6.9. Will test further and update. However, even on 6.8.9, the GPU refuses to go into D3cold on external power.
I’m not sure how helpful this is, but I’m on Arch with Kernel 6.9.10 with a dGPU and mine doesn’t experience any issues relating to switching states. I’ve never experienced a panic either.
I’m currently on external power (included USB-C adapter) with my dGPU in the D3cold state. I did have an issue previously, but it was found to be software trying to access sensor data that was the cause; removing that fixed it.
Have you tried running it on a live-environment external to your current install?
Where are you plugging in the USB-C adapter? I’m powering my laptop via a USB-C Expansion Card (middle on the left or right in my case)
It could also be a hardware thing; I know it sounds lame, but testing Windows might not be a half bad idea, or at least a supported Ubuntu variant, just to see what happens.
This makes the GPU not crash on plug-ins, although the GPU still stays in D0 while the power adapter is in and I cannot for the life of me see anything that’s using it.
I tried putting my Framework charger in the same port, and while I did get the same GET_CABLE_PROPERTY error, I did not observe issues with the dGPU going into D0.
I really think this is a software thing, but I don’t think this is a kernel issue. A kernel issue would likely be more wide-spread since there’s plenty of people on the same kernel using Arch. Since you said it doesn’t happen in Fedora, it’s not likely a hardware thing.
I still think testing in a bare/new Arch install with 0 extras installed would be a good next step.
A clean install took a little longer than expected but works like a charm now, no D0 nonsense. I just nuked the old one and installed everything anew. Thanks for the help!
I’m assuming by this message you didn’t mean that the usci_acpi messages also went away? It seems like you were saying your other issues were fixed, just wanted to check.
The USCI_ACPI issue (and another similar kernel message) is being reported/tracked here and here
Hi all! My FW16 is arriving next week so I’m doing some prep work to get ready for setup. I’m considering setting it up with CachyOS as I’ve had multiple vanilla Arch machines in the past and want to try something newish. Does anyone have experience with Cachy on the FW16? Any weird quirks I should watch out for other than the already listed tweaks for Arch?
