Not asking for assistance, but I would like to report what appears to be an anomaly. After using garuda-update, I rebooted my system and got the following message on a black screen: setfont KDFOnTop: function not implemented. The system then booted into CLI-only interface. I rebooted twice more and got the same behavior. I checked out dmesg but found nothing unusual. Tried matching the error name to some entries in various configuration files in the sys folder, but nothing of note was found. I finally just went back to my most recent snapshot and am holding off on any new updates pending any similar experiences from other users. I am not sure what was happening and I am certainly not sure if it had anything to do with the recent update, but I am just passing on the information. About my system:
Operating System: Garuda Linux
KDE Plasma Version: 5.27.3
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.8-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 570 Series
Happend to me as well. Went back a snapshot and reupdating my system and going through my update logs carefully told me Plymouth decided to rename it's modules. It gave a bunch of instructions for everyone to enable corresponding services and adding modules to mkinitcpio if needed.
For me all I needed to do was
sudo systemctl enable sddm
And then reboot.
Though it could be different for you do check that message.
Plus for the KDFONTOP message add setfont
To binaries in mkinitcpio.conf
Followed by the the command mentioned above by @bluishhumility
Yep, the KDFONTOP thing is a harmless warning, it just happens to be the first message printed and that apparently misleads to think it's the cause of some unrelated problem.
The fact plymouth immediately proceeds to hide the console messages makes it go unnoticed until something happens.
I had the same problem, and without knowing how to address it I've made a fresh reinstall; ones the the reinstall has updated, I've gone back to the same problem.... It seams the updater is causing the issue.
I've accessed the forum via my Rpi, and now proceeding with my second fresh install, knowing how to solve the issue. Thanks @NaN for providing the solution.
You didn't need to make a fresh install going back a snapshot would have been fine. Well garuda has implemented the automated fix now so it shouldn't be a problem anymore after you update this time you should receive the message at the end regarding the fix being implemented.
Oh that's easy. Login to the tty with your username and password. They type the command reboot. It would restart the computer and bring you to grub menu. Go to snapshot and select one that works for you.
Or if that sounds too complicated just pull the plug on your desktop or long press the power button on your laptop till it decides to turn itself off and then again turn on the device. Reach the grub menu --> snapshot and restore select the snapshot that works for you.