Yes and No, plymouth was installed and the theme was set up but the installer didn’t set it up to load on boot.
You’ll need to edit /etc/default/grub and and add splash to the end of this line like this:
OK, I’ve got as far as here but here’s the output from the above command:
[martin@sgc ~]$ sudo mkinitcpio -p linux
[sudo] password for martin:
==> ERROR: Preset not found: `/etc/mkinitcpio.d/linux.preset'
[martin@sgc ~]$
If I look in /etc/mkinitcpio.d I can see linux310.preset so I’m assuming that the correct command should be sudo mkinitcpio -p linux310. As I don’t want to trash my new setup, I’ll await your comments before proceeding, thanks.
[quote]
If I look in /etc/mkinitcpio.d I can see linux310.preset so I’m assuming that the correct command should be sudo mkinitcpio -p linux310. As I don’t want to trash my new setup, I’ll await your comments before proceeding, thanks.[/quote]
Looks like I may have marked this topic as solved a bit too soon:
Switched on the PC this morning and got the grub boot menu, followed by the plymouth boot splash, followed by a tty login screen which very quickly changed to a completely blank black screen and that was the end of that. The only way out was to switch off the PC and wait a few minutes before switching back on. This time though, I got the graphical login screen instead of the tty login screen/blank screen and I was able to log in OK. I’ll have to see what happens when I switch on tomorrow morning :-/
Yes, it’s a display adapter / driver issue. if you switch consoles the log-in in screen should appear (example: ctrl+alt+f1 then ctrl+alt+f7). I’m not sure what causes this exactly, it is an intermittent issue and happens with all display managers and graphics cards.
OK, thanks for that and just to keep you updated, the system booted just fine this morning but the transition between plymouth and the graphical login screen was not seamless. A tty login screen briefly appeared followed by a blank screen with a flashing cursor in the top-left-hand corner and, after a few seconds, the graphical login screen appeared. I was then able to login and I then got the KSplash screen which transitioned smoothly to the KDE desktop. Anyway, my original question has been answered and thank you both very much for your help.
[hr]
Just had a thought …
Up until very recently I’d always used the nVidia proprietary drivers but I’m now using the nouveau drivers, as they seem to have improved greatly since I last tried them. Perhaps I should try using the nVidia drivers again just to see what happens?
Selfishly, I’d be very interested to see your results.
I’m running the proprietary drivers, and I’d noticed that I had no plymouth bootsplash. BUT, under Ubuntu (and derivatives) I have a script that always fixes that for me, and I hadn’t dug into things enough to have any idea whether it could be the same problem for me here as crops up on Ubuntu derivaties - I checked my pacman.log after reading your post, and sure enough I actually have the same issue you started with.
I really hadn’t planned to mess with Plymouth because of my proprietary drivers, and because I don’t understand how Plymouth functions well enough to troubleshoot it at all. (Despite about a year on arch in the not too distant past - I never bothered with Plymouth there, either.)
So if you do it, please post here regarding how it goes, and I may ride your coattails
If you followed the prior instructions for KMS I don’t know if that will be something you have to undo when you switch to proprietary or not…
The blank tty screen is SDDM waiting for Plymouth to stop before it tries to load, this is normal when using Plymouth.
Yes if you switch to the proprietary drivers you will need to remove the modules line from /etc/mkinitcpio.conf and run sudo mkinitcpio -p linux*** again.
I spent quite some time on this yesterday and, after almost trashing my system, I came to the conclusion that it wasn’t worth the hassle, as there was no noticable difference
I managed to install the nvidia drivers without any problems but I got in a bit of a mess configuring everything because I hadn’t realised that things are done differently to what I’ve been accustomed to. I only found out after reading the Manjaro wiki after I got in a mess (should have read it first!)
As you already have the proprietary drivers installed and working, you may have more success than I did.
Yes, Manjaro has it’s own tools for managing the systems hardware and software, these tools should be listed and/or demonstrated on the tutorial read me page. There should be a link to the Manjaro Wiki on this page as well as to the forums and blog pages.
I decided to do a fresh clean install of “Rolling” this morning with a view to trying all this again because I discovered that I’d overlooked two very important steps:
sudo systemctl disable sddm.service
and …
sudo systemctl enable kdm-plymouth.service
I now have it all working smoothly with the “nouveau” drivers
When I have a bit more time(tomorrow), I’ll post a detailed account of exactly what I did
[2] Added plymouth to the hooks array in /etc/mkinitcpio.confafterbase and udev
[3] Changed MODULES=“” to MODULES =“nouveau” in /etc/mkinitcpio.conf
[4]
sudo mkinitcpio -p linux310
[5]
sudo update-grub
[6]
sudo systemctl disable sddm.service
[7]
sudo systemctl enable kdm-plymouth.service
[8] Reboot
I don’t see any reason why this shouldn’t work with the proprietary nvidia drivers providing step3 is skipped but I haven’t tried it. If anyone does try it, I would be interested to hear the outcome.
Yes, Plymouth works just fine with the proprietary drivers, only the Nvidia driver does not support KMS so the size will be larger, other than that it’s fine. The plymouth package doesn’t have a sddm-plymouth.service in it yet but I have created one myself, if you wish to try it extract it to /usr/lib/systemd/system and run: sudo systemctl enable sddm-plymouth.service
