No, unfortunately not 
Completely missed this post. I’m on 6.13.9 and this happened today. See (Fedora Kinoite) Framework 16 7040 dGPU Disconnects After Wake from Sleep. Seems like my post is basically a duplicate.
1 Like
All good, my post ended up getting merged into this one as well because I did the same thing.
It looks like you collected some additional logs and also provided a confirmation that 6.13.9 doesn’t work (I haven’t felt courageous enough to try yet). Thanks for sharing
No problem. I’ll be updating to the latest kernels as soon as kinoite drops them so I’ll reply to this post as soon as I see issues (or not). I’ve also noticed that I’m running into the same /dev/kfd errors mentioned in this Gitlab issue with ollama.
I’ve seen some mentions of disabling secure boot making things better? I’m giving that a shot, and games are still working after a few sleep/wake cycles, but the /dev/kfd problem still persists.
1 Like
Today a new update came with Fedora with the following packages, since then I have in gnome every x minutes the sound that something is mounted; the following is then always in the log:
amdgpu 0000:03:00.0: [drm] Cannot find any crtc or sizes
rpm-ostree db diff 50cc3b76 b803be87
ostree diff commit from: 50cc3b76 (50cc3b76069e43408e60c0e246e27ff0ffdfce3357a75180890b78b532b26d96)
ostree diff commit to: b803be87 (b803be87e87a1b19ec791fe9de5cc15e371ca33dabe4d6b5dca75a167229fd05)
Upgraded:
alsa-sof-firmware 2025.01-1.fc41 -> 2025.01.1-1.fc41
bluez 5.79-1.fc41 -> 5.81-2.fc41
bluez-cups 5.79-1.fc41 -> 5.81-2.fc41
bluez-libs 5.79-1.fc41 -> 5.81-2.fc41
bluez-obexd 5.79-1.fc41 -> 5.81-2.fc41
epiphany-runtime 1:47.2-1.fc41 -> 1:47.4-1.fc41
hwdata 0.393-1.fc41 -> 0.394-1.fc41
ibus-typing-booster 2.27.29-1.fc41 -> 2.27.30-1.fc41
javascriptcoregtk4.1 2.48.0-1.fc41 -> 2.48.1-2.fc41
javascriptcoregtk6.0 2.48.0-1.fc41 -> 2.48.1-2.fc41
libldb 2:4.21.4-1.fc41 -> 2:4.21.5-1.fc41
libsmbclient 2:4.21.4-1.fc41 -> 2:4.21.5-1.fc41
libwbclient 2:4.21.4-1.fc41 -> 2:4.21.5-1.fc41
libxcrypt 4.4.38-6.fc41 -> 4.4.38-7.fc41
openvpn 2.6.13-1.fc41 -> 2.6.14-1.fc41
python3-boto3 1.37.25-1.fc41 -> 1.37.29-1.fc41
python3-botocore 1.37.25-1.fc41 -> 1.37.29-1.fc41
samba-client 2:4.21.4-1.fc41 -> 2:4.21.5-1.fc41
samba-client-libs 2:4.21.4-1.fc41 -> 2:4.21.5-1.fc41
samba-common 2:4.21.4-1.fc41 -> 2:4.21.5-1.fc41
samba-common-libs 2:4.21.4-1.fc41 -> 2:4.21.5-1.fc41
spirv-tools-libs 2024.4-1.fc41 -> 2025.1-1.fc41
upower 1.90.7-1.fc41 -> 1.90.8-1.fc41
upower-libs 1.90.7-1.fc41 -> 1.90.8-1.fc41
vim-data 2:9.1.1227-1.fc41 -> 2:9.1.1275-1.fc41
vim-minimal 2:9.1.1227-1.fc41 -> 2:9.1.1275-1.fc41
vulkan-loader 1.4.304.0-1.fc41 -> 1.4.309.0-1.fc41
webkit2gtk4.1 2.48.0-1.fc41 -> 2.48.1-2.fc41
webkitgtk6.0 2.48.0-1.fc41 -> 2.48.1-2.fc41
I’ve never had secure boot enabled and have this issue, so I doubt it’ll help.
So it works for me with Secure Boot and kernel 6.13.5
I’m also running 6.13.5 and planning to not update my system until this is resolved.
i thought it would be enough if i didn’t update the kernel, but now a problem has crept in via another package…
That’s good to know… and something that going to make me paranoid.
Arch has recently upgraded to 6.14.1 and since restarting my system on the new kernel, I have not had amdgpu crash. I will continue to monitor that, but sleep and checking it in my system info panel have not triggered a crash as they did in 6.13.8
If that’s true, then it’s possible we won’t see a fix on Fedora until Fedora 42. I picked a hell of a time to switch Arch → Fedora
Not only you 
The 6.14.1 kernel is even available for F41:
I have just installed 6.14.1 and cannot use my graphics card.
I can confirm this as well. Arch on 6.14.1 has been great so far. 3 external monitors work fine on the dgpu and I have not lost it or any crashes yet…knock on wood.
Having the same thing, same kernel message and annoying connect/disconnect sounds after system update. Lot of the same packages, not sure what. My GPU has been mostly working though, interestingly, even though I’m on 6.13.9. I say mostly because sometimes it’s not accessible but it’ll work again after a restart. On Fedora/KDE. Also possibly in games there seems to be a slight graphical artifact (like a white rectangle on the bottom of the screen) for a frame when I hear the connect/disconnect sound.
I will say, while on 6.14.1 I have not had any amdgpu crashes anymore. I do still get the annoying connect/disconnect noises. I turned off my system notification noises so I didn’t notice until now. So I guess not all fixed, just mostly.
I’m thinking the connect/disconnect noises is an unrelated issue then. Played some more tho and I’m def getting white flashes in game whenever it happens which is real annoying. Gonna see if I can find what exactly the bad package update is (side note - anyone know if there’s an easy way to do a bisection for a DNF update? Like how you can do with kernel commits, but instead binary search through all the packages that you updated in a certain update)
It seems to be at least a little bit related though, I did not update my computer between it working without the gpu and installing the gpu for the first time. So the existence of the gpu seems to be at least partially a cause.
Oh it’s certainly related to the gpu, cause there’s an amdgpu log in the kernel that is associated with the sounds/graphical glitches. I just don’t think its related to the issue of the graphics card not being available that the thread started with. Could be wrong tho, still investigating.
so just based off of this list of updates, I’m currently suspecting that vulkan-loader could be the issue. Problem is, when I try to downgrade to the older version, it only lets me if I uninstall like a bunch of necessary stuff (mesa, for example) so I’m a little lost on how to test this…