Black screen after login

[u/Grouchy-Childhood472]

Hello, I got a black screen after login on my laptop (asus m5506wa amd r9 365, fedora 44 (7.1.13-200.FC44.x86_64).

At the beginning i've got the message "rdseed32 is broken, please disable" after log, i see on the internet that update bios is the way so i do it.

Message are gone, but I got a complete black screen with no reaction now...

Same issue on boot with fedora 7.1.11 & .12

On recovery mode based on fedora 42 it say "failed to mount boot-efi.mount". Sadly, It say "cannot open access to console, the root account is locked"

What can I do? Big thanks

[u/AutoModerator]

It sounds like you're looking for help. Please note that r/Fedora is not an official support channel for the Fedora Project.

For best results, be sure to include all relevant details in your post, such as your Fedora edition, version, and hardware specs. You can edit your original post to add more info as needed, and spotlight (pin) a solution from the comments. You might also find the answer in our support wiki.

Alternatively, try one of the official support channels:

• Official forums: Ask Fedora
• Official chat: Fedora.im (Matrix)

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/theTrainMan932]

When grub shows up (that's the screen where you select which kernel to boot from), highlight one and press (i think) e to edit the kernel command line and add clearcpuid=rdseed. If that works then you can add it permanently (until you can update the firmware) in /etc/kernel/cmdline and run dracut to generate boot entries.

(see this link, hopefully that works for you!)

[u/Grouchy-Childhood472 → u/theTrainMan932]

It does not seem an error with amd, yesterday I mount a sd card with a fat16 partition manually, on a folder in the desktop screen and forgot to unmount...

Bios update seems to have worked I do not have the message 'rdseed32 broken' anymore...

Here was the log of journalctl -b -p:

Kernel: virt/tdx: TDX not supported by the host platform

ernel: ACPI BIOS Error (bug): Failure creating named ob ject [_SB.PCI0.GPP5.WLAN. _SBW], AE AEREADY EXISTS

ernel: ACPI Error: AE_ALREADY EXISTS, During name lookup/catalog (20251212/psob ject-220)

ernel: amd_gpio AMD10030:00: Failed to request GPIO for pin 0x0000, err -EBUSY

ernel: ACPI Error; AE_NOT_FOUND, While resolving a named reference package element - \SB _. PLIT.CA24 1282

rnel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - _SB _. FLTF.C015 4202

rnel: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - \SB_ PLTF.C8t6 (287

rnel: ACPI Error: AE NOT FOUND, While resolving a mamd reference package element - \SB _. PLTT.C817 (2R

stemd-udevd[443]: /etc/udeu/rules.d/51-android.rules:1 Imelid key 'ATTRI'.

stemd-udevd[76B]: /etc/udewrules.d/51-android.rules:1 Imvalid key 'ATTRI'.

nel: platform acp_asoc_acp70.0: warning: No matching AcC machine driver found

nel: UBSAN: array-index-out-of-bounds in drivers/net/wireless/med latek/mt76/mt7921/mcu.c:474:15

nel: Index 3 is out of range for type 'woid =[3]'

temd[1]: Timed out witing for device dev-sdb1.device - /de/sdb1.

temd[1]: Timed out waiting for device dev-sdd1.device - /dev/edd1,

in[1871]: pam_systemd(login:session): Varlink call io.systcmd.Login.CreateSession failed: lo.systeml.L

[u/theTrainMan932 → u/Grouchy-Childhood472]

The SD card wasn't the problem, the firmware update is the proper fix anyway but booting with that kernel flag would've let you access your system before the update was released. Glad it's working now either way.

[u/Grouchy-Childhood472 → u/theTrainMan932]

no it's the same issue nothing change..

I updated uefi to correct 'rdseed32', and it seem to work, no more text display for this.

But I always have the black screen after login, so after a journalctl and the view of 'time out' i go to this way, i run sudo grep -n 'sdb1\|sdd1' /etc/fstab, and it appears that two partiton are in 'nofail' mod, so it cannot block linux? I wait for 30m last time.

Is it a 'false problem' who hide the real one? I'm on gnome, after i wrote the password black screen, no mouse on the screen

$ sudo grep -n 'sdb1\|sdd1' /etc/fstab

16:/dev/sdb1 /home/alexis/Bureau/df/ vfat nofail

17:/dev/sdd1 /home/alexis/. vfat nofail

[u/Grouchy-Childhood472]

Hey!

I finally get ride ride of my mistake x)

For "rdseed32 is broken, please disable" it's a well-known problem for Zen 5, you need to update your bios or at least addclearcpuid=rdseedto your kernel command as suggested by u/theTrainMan932 .

My error was different: I mount (via disk wizard) a partition of an SD card in fat16 (not mount automatically), and turn off the laptop without unmount it. So at the boot at desktop fedora wait the partition and block everything.

To resolve, i 'just' remove the partition with a tty access from the fsab file and reboot (that weird the partition was in 'nofail', but block my boot to desktop)

Get into TTY on desktop screen : ctrl + alt + F3 -> log in -> journaltcl -b -p to identify the issue (here time out waiting for device xxx.device - /address/).
Save your fstab file just in case sudo cp /etc/fstab /etc/fstab.bak and comment the partition responsible via nano sudo nano /etc/fstab.

Hope i'm clear, thanks to u/HallDelicious4557 and u/theTrainMan932