I tried to install Nvidia drivers on Fedora with RPM Fusion, so I ran
dnf install akmod-nvidia
I didn’t read the manual correctly (yeah, I know) and forgot to wait until it builds, so I instantly rebooted after it was downloaded, then when trying to boot, for half a second it shows the enter passphrase screen for encryption and then the screens just turns black.
I now tried to mount it in a Live Boot and chroot into it, that worked, then I reinstalled to again, it complained about /proc not exsisting (I just mounted my main partition) so I ran this while chrooted
mount -t proc none /proc
And then removed and installed it again, but still when trying to boot it shows the encryption screen for half a second and then it’s still just a black screen.
Can anybody help me?
You can switch to console with the ESC key and enter your key, or if the system boots you will see messages. Just wait for few minutes, it should write something with akmods-
Usually system will compile the missing kernel modules and continue.
That isn’t true if root is locked.
I would edit grub on bootup and check for nouveau options on the cmdline and remove them if they exist.
hopefully that will allow the encryption dialog to function.
you don’t need plymouth to unlock root volume. If console is still functional, ESC and maybe press RETURN and the prompt asking for the key should appear.
rhgb is one of the first things to be removed from the kernel args on new installs.
I only use this guide and it always works 
there should be “rd.driver.blacklist=nouveau,nova_core modprobe.blacklist=nouveau,nova_core”
Are you sure screen isn’t doing a mode switch? That’s what I see here with plymouth activated, on screen appears the unlock root volume dialog, disappears for some reason (looks like a mode switch) and reappears after a few seconds. But it’s possible to input the key all this time.
what is the last line you can see on console? You will not see a cursor it’s just a prompt to unlock the root volume.
something like
"please enter passphrase for disk xxx (luks-yyyyyy ):
there is only one long line I would remove rhgb this will show the console instead of plymouth. Removing the blacklist should not make any difference because the drivers are loaded only after unlocking the root volume.
although maybe the nouveau driver is in the initramfs, never bothered to check this.
so if booting w/o RHGB does not work, then retry with removing both rd.driver.blacklist and modprobe.blacklist.
what worked? removing rhgb? or removing the blacklist?
Upower, that’s unexpected. how long did you wait?
pls try with removing rhgb and the blacklists. Is this a laptop or a system with a single GPU?
can you see a login prompt when you switch with CTRL + ALT + F3 or F4 to another terminal?
otherwise reboot and remove rhgb and add init=/bin/bash.
this should stop the boot process quite early, This should give you access to the FS and journal e.g. journalctl -xb-1 (-1 = previous boot attempt )
try to find clues in the journal file of previous boot attempt.
journalctl -b-1 or more verbose journalctl -xb-1
replace -1 with the index shown with journalctl --list-boots -r |head
upower.service could be a good start to look for.
you can also limit output with -p (priority) emerg =0 , alert =1 , crit 2, err 3 etc
with -g you can do a grep
-u can limit output to a service i.e upower.service
man journalctl
check with mount that / and /home are mounted as read/write
if it is a failly recent fedora installation, then it may be easier and quicker to reinstall the system. WIth btrfs there is an option in the installer to skip the reformatting of /home. Only the system in / will be reinstalled.
nethertheless, backup you important data beforehand.