sporadic, first time this happens daily driving, updated to F43 last month
mini PC with Display Port monitor, I do not remember this happening with the same monitor on HDMI but that was before updating to F43
AMD GPU, see below
I could log in to console using Ctrl-Alt-F2 and the system was otherwise fine
The following from /var/log/messages seems relevant:
sddm-helper-start-wayland[2498]: "No backend specified, automatically choosing drm\n"
sddm-helper-start-wayland[2498]: "Accepting client connections on sockets: QList(\"wayland-0\")\n"
sddm-helper-start-wayland[2498]: "qt.qpa.wayland: qtvirtualkeyboard currently is not supported at client-side,
...
kernel: amdgpu 0000:76:00.0: [drm] enabling link 0 failed: 15
...
kernel: fbcon: Taking over console <- Ctrl-Alt-F2 I suspect
...
kernel: Console: switching to colour frame buffer device 240x67
...
sddm-helper-start-wayland[2498]: "qt.qpa.wayland: There are no outputs - creating placeholder screen\n"
sddm-greeter-qt6[2504]: There are no outputs - creating placeholder screen
sddm-greeter-qt6[2504]: Loading file:///usr/share/sddm/themes/01-breeze-fedora/Main.qml...
sddm-greeter-qt6[2504]: QQuickView(0x556b8eb6e140) already has a shell integration. Call QWindow::close() first and show it again
sddm-helper-start-wayland[2498]: Stopping... "kwin_wayland"
I see some reports about the amdgpu driver failing on 6.19 kernels.[1] Is that what you are using? Does using an older (or newer) kernel work around the problem?
I’ve found a temp fix. Just downgrading your Refresh rates to a lower value than the max make the job. I’m currently at 120Hz instead of 165Hz. Reload BIOS to default, Disabel secure boot (in my case), Enabled EXPO1. All is working perfectly. I’m suspecting that since DisplayPort 1.4 lot of manufacturer use DSC to have lower latency and better refresh rates. May be the firmware doesnt handle very well the retrocompatibility with 1.2 version. Like I was wondering how I dont have more log like my computer/firmware didnt handle any problem and found on reddit that G27QCA monitor have terrible problems with DP2.1 Graphic Cards. To be more clear the problem is happening on both Windows and Linux and when switching to HDMI the problem doesnt exist anymore. Same when I plugged my monitor to my old 3070 the problem is gone with Display Port cable. So yeah there are a problem with the link and I guess we have no way to fix it
It might be. It looks like there is an interesting power management patch that has been pushed to the kernel recently (14 hours ago): Fix CPU hotplug activation race in the timer migration code. I wonder if that could be related to this problem?
With the problem occurring twice over about 20 days, once that patch is in effect I would have to observe the system for another 20 before calling it effective, wouldn’t I?
Yeah, you might run something like sudo journalctl --since=-3weeks -g "enabling link 0 failed" to get an idea about how often the problem is occurring now, then rerun that command a few weeks after that power management patch has arrived and see if the problem is still occurring with the same frequency.
Did you check for the same “link failed” messages? Some failures are race conditions which can be mitigated with more checking that early tasks have completed, but it is all too easy to overlook something, so could help others if you can find relevant details.
i having this problem soon as i boot the system after a upgrade from fedora 43 to 44, workstation edition, the booting system start the gdm to a bliking screen in tty1, as if gdm didnt installed correctly. when i commando the distro-sync this outputs: A operação resultaria na remoção dos seguintes pacotes protegidos: grub2-efi-ia32, grub2-efi-x64, grub2-tools-minimal, setup, shim-ia32, shim-x64, sudo
Você pode tentar adicionar à linha de comando:
–skip-broken para ignorar pacotes desinstaláveis
i have added the --skip-broken and --allowerasing parameters, but outputs that the operation would remoe this protected pkgs, is there a solution to this without new installation of the system?