When I try to boot fedora it gets stuck at a black screen with just an underscore. So I removed rgbh quiet option and this is the output: However 2 seconds after this output it gets blank with just a cursor again.
Can anyone help me please?
Try typing Ctrl-Alt-F3 and see if you get a login prompt.
If that does work try booting the previous kernel, assuming you just did an update.
If you can login then you can look in the system journal for clues as to what is wrong.
I would also suggest running Memtest86+ or a similar tool to check the memory. Does the live CD/USB work normally? However, definitely check the logs if you can, as the other poster suggested.
There are a lot of crashes in fundamental system components, which is not normal at all.
Either the distribution is broken (for example, due to filesystem corruption), or there is something wrong with the hardware.
So strg + alt + F3 did nothing, and I don’t think that it’s a memory issue because windows on a secondary SSD works just fine.
Thank you for trying to help me.
Try booting with a Live USB - if that works, then there is something wrong with your current install.
If it does not work, then something else is wrong…
Yep booting into a live USB works. Can I fix it from there?
If you can boot a Live USB environment you can mount the internal drive to use journlctl --directory ... to get detals of the problem.
1 Like
Alright I mounted it and with Christ and used journalctl --directory ... first it showed no such file or directory, then no journal files were found when I remove a dot.
You need to replace ... with the actual path where your logs are located in the original root partition.
I think if you used chroot, then you can just remove the --directory ... part.
Since their system is largely broken and crashing, I think it is better not to chroot into it. Additionally, journalctl may complain unless it is done properly, which involves bind mounting /dev, /proc, /sys, etc.
Right, but I think they already did. (I assume “Christ” was a typo for “chroot” but maybe that’s a stretch…)
Oh yeah sorry I meant that. Stupid autocorrection.
Should I give you the entire output of just journalctl?
OT: If not, I would like to know more. xD
Here are the logs of the last boot:
This might be a long shot, but you could try booting with autorelabel=1 (see Changing SELinux States and Modes :: Fedora Docs). There are a bunch of SELinux-related errors in the boot process.
1 Like
Thank you so much stranger on the Internet. It actually worked.
1 Like