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?
just received my FW16 laptop w/ 64 GB RAM and the iGPU. Moved over my NVMe and was ready to go in no time. Unfortunately, only 60 GB of 64 GB are available despite the VRAM being set to “Auto” in the UEFI setup. Has anyone else seen this and is there a way to reclaim 2 GB?
/sys/class/drm/card1/device/mem_info_vram_used shows that only 1.4 GB of VRAM are actually in use.
Is anyone else having problems with Libreoffice? It appears to be gpu related as the following messages appear in dmesg:
[ 945.733441] amdgpu: Queue memory allocated to wrong device