I updated from F42 to F43, completed OK and said to reboot now. The boot fails after quite a bit of activity with no message. Screen flashes twice and goes blank. Looking at similar questions I added ‘3’ to the “linux” boot line and it will start but I have no GUI available. Used to be ‘startx’ to get it but that was in a previous era. What should I do next to:
Sounds like maybe the video driver is not working properly. I would say to boot into verbose mode where you see all the information coming up. Not sure the best way to do that. I believe you have to edit the line in grub.
Does the Fedora logo come up with the spinning thing? I used to just hit the esc key and that would do it. I believe there is another way as well.
Just copied this from a forum post…
When grub appears, hit “e” to edit the kernel line and erase “rhgb quiet”. You will then see all the glorious scrolling that Linux offers.
You can look for details with journalctl. If you are not familiar with it, look at Fedora’s introduction. You could start with journalctl —no-hostage -b -p3. Also post the output from running inxi -Fzxx as pre-formatted web searchable text so others with similar hardware can find this topic. Often one of them knows a solution.
Dec 03 20:44:17 systemd-udevd[318]: /etc/udev/rules.d/65-brother-libsane-type1-inst.rules:14 Invalid key 'SYSFS'.
Dec 03 20:44:29 systemd-udevd[582]: /etc/udev/rules.d/65-brother-libsane-type1-inst.rules:14 Invalid key 'SYSFS'.
Dec 03 20:44:33 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-14:09:24.827477-11865' is not a problem directory
Dec 03 20:44:33 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:14.914105-1083' is not a problem directory
Dec 03 20:44:33 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:17.451503-1786' is not a problem directory
Dec 03 20:44:34 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-14:09:00.787224-11523' is not a problem directory
Dec 03 20:44:34 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:18.872886-1871' is not a problem directory
Dec 03 20:44:35 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:18.898599-1913' is not a problem directory
Dec 03 20:44:35 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-14:09:10.478507-11674' is not a problem directory
Dec 03 20:44:36 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:20.425167-2048' is not a problem directory
Dec 03 20:44:36 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-14:09:13.673982-11733' is not a problem directory
Dec 03 20:44:36 libvirtd[1053]: Unable to open /dev/kvm: No such file or directory
Dec 03 20:44:37 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:21.727166-2172' is not a problem directory
Dec 03 20:44:37 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:20.448968-2093' is not a problem directory
Dec 03 20:44:38 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:16.365921-1648' is not a problem directory
Dec 03 20:44:38 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-14:09:04.26552-11571' is not a problem directory
Dec 03 20:44:38 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:14.232036-1479' is not a problem directory
Dec 03 20:44:39 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-14:09:07.279354-11624' is not a problem directory
Dec 03 20:44:39 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:16.104227-1603' is not a problem directory
Dec 03 20:44:40 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:20.18400-2003' is not a problem directory
Dec 03 20:44:40 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:22.396379-2215' is not a problem directory
Dec 03 20:44:41 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-14:09:21.603383-11824' is not a problem directory
Dec 03 20:44:41 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-14:09:16.851436-11458' is not a problem directory
Dec 03 20:44:42 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:16.626022-1694' is not a problem directory
Dec 03 20:44:42 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-14:09:28.41426-11913' is not a problem directory
Dec 03 20:44:43 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:21.222147-1848' is not a problem directory
Dec 03 20:44:43 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:22.804019-2260' is not a problem directory
Dec 03 20:44:44 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:15.419122-1560' is not a problem directory
Dec 03 20:44:44 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:17.195189-1741' is not a problem directory
Dec 03 20:44:44 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:13.648317-1430' is not a problem directory
Dec 03 20:44:45 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:18.92071-1536' is not a problem directory
Dec 03 20:44:45 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:19.641687-1958' is not a problem directory
Dec 03 20:44:46 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:12.687956-1333' is not a problem directory
Dec 03 20:44:46 abrtd[840]: '/var/spool/abrt/ccpp-2025-12-03-20:40:13.389040-1382' is not a problem directory
Dec 03 20:44:55 login[1105]: PAM unable to dlopen(/usr/lib64/security/pam_lastlog.so): /usr/lib64/security/pam_lastlog.so: cannot open shared object file: No such file or directory
Dec 03 20:44:55 login[1105]: PAM adding faulty module: /usr/lib64/security/pam_lastlog.so
Dec 03 20:53:25 su[1407]: PAM unable to dlopen(/usr/lib64/security/pam_lastlog.so): /usr/lib64/security/pam_lastlog.so: cannot open shared object file: No such file or directory
Dec 03 20:53:25 su[1407]: PAM adding faulty module: /usr/lib64/security/pam_lastlog.so
Not sure why the Security references since it runs as “Selinux permissive”
I also tried to start the rescue O/S but it fails with “unsupported legacy cgroup hierarchy, Refuse execution”
I tried to start the old F42 version but the same problem occurs that the boot runs for a while then the screen flashes twice and goes blank. At this point it appears to be in a loop because the disk light is flashing and it continues the same pattern for more than an hour with no result. The disks appear to still be correct so the old data is there as before (by doing a ‘ls’ on ones I know what should be there and by running ‘lsblk’.
Searching around a bit gives this similar issue on RedHat which seemed to be caused by McAfee deleting needed files as “malware”. Is there any chance you have some anti-virus software that might be doing that?
Yes, but only when I edit the boot menu to add delete ‘rgbh’ and add ‘3’ to the end. Then I get a command line only and I can’t start gnome. There is graphic capability since the screen goes all grey during boot unless I hit ‘’
@pg-tips
No antivirus software installed. I thought PAM was the internal name of Selinux since it pops up in that context so often. It is an internal workstation used mostly for development with not much that is confidential on it and two firewalls to the Inet so it is much easier to just leave Selinux in permissive mode.
This is still unresolved and the previous version (F42) on the grub menu will no longer boot, failing with same symptoms at boot time. Is it possible to back out the upgraded without doing a full reinstall? If so how? DNF notes have a back out process but that appears to be only related to single item installs. Never seen a general release of Fedora that was this buggy and apparently untested!
Thanks very much Vladislav. Surprisingly I had found this when I was searching and didn’t realize that it applied to my problem. Took a while to get it right, traced to the example having a fingerprint reader which I don’t have.
Also, thank you to everyone who commented; very much appreciated.