I have several computers here all running openSUSE Leap 15.4. When the system boots (after the initial bootloader menu), all of them except one shows a black screen with the “Leap” logo at the center bottom, and a spinning circle above it while the system comes up. Then the graphical login screen appears.
On the one odd system, instead of the black background, “Leap” logo and spinning circle, I get a grey background and three green dots instead. The system does come up to the graphical login screen, but what causes it to show the three green dots rather than the “Leap” screen?
That’s from the plymouth splash screen that is supposed to show during boot. The plymouth software is apparently having problems with your graphic display, so it is instead showing the plain text version of its splash screen.
I think you misread (sorry). But he does not report text, he reports green dots (I assume the squares I have seen also earlier).
When they are the small green squares, I think I got them in earlier Leap versions. But as I have removed Plymouth already for some releases, I can not provide details.
Yes. But, as far as I know, that is all done with the display of ASCII (or extended ASCII) characters. So it is using text-mode rather than graphics mode.
:messed: Oops, that is a new idea for me. Would never have thought about that possibility (that is, as we talk about the same phenomenon). In that case, you will be right.
OK, here are the specifics about the machine in question. It has a Asrock 970M Pro3 motherboard with an AMD FX-6300 6-core CPU and 32GB of RAM. It has no onboard video, so a EVGA 02G-P3-1733-KR (with GeForce GT730) PCI-e video card is installed. The system is running the nvidiaG05 470.141.03 proprietary video driver. It works fine with the X11 graphical environment (KDE in 2560x1440 resolution).
Is there something in this setup that would prevent the plymouth graphical boot from working?
It took me some days to schedule a reboot, because this is a live system with active users most of the time. Anyway, here is what grub2 “videoinfo” shows:
Then when the system boots, the screen looks like this with the three green dots rather than the “Leap” logo and spinning circle. After a moment, the graphical desktop login screen appears.
Nice, I wish I have all those video options.
First start with as “su”
plymouth-set-default-theme --list
That will show the installed themes
This will show your current plymouth theme
plymouth-set-default-theme
To set your new theme you do this
plymouth-set-default-theme --your-new-theme -R
The -R is for rebuilding the initrd
If memory serves the one that appears in your boot is the tribar-theme I could be wrong. appears when their is a video problem.
Additionally when you able to work things out:
Base from your videoinfo grub is using 1280x1024 (see the asterisk before the video resolution)
but you can still go higher than that. You can simply choose it in yast2-boot loader-kernel parameters-console resolution.
You can add your video resolution in the optional kernel command line parameter like so: video=your_resolution base from what is available in the videoinfo. In yast2-boot loader settings-kernel parameters also.
The post #4 from nrickert also has to be considered, he might be able to guide you with that.
# plymouth-set-default-theme --list
bgrt
breeze
breeze-text
details
fade-in
script
solar
spinfinity
spinner
text
tribar
This will show your current plymouth theme
plymouth-set-default-theme
This is the output:
# plymouth-set-default-theme
bgrt
Looks like my setting is already what I want - the one with the “Leap” logo and spinning circle. Hmm.
To set your new theme you do this
plymouth-set-default-theme --your-new-theme -R
The -R is for rebuilding the initrd
Since my setting is already “correct” I didn’t do this.
If memory serves the one that appears in your boot is the tribar-theme I could be wrong. appears when their is a video problem.
This is probably why the theme with the 3 green dots (“tribar”?) appears instead of the selected “bgrt”.
Additionally when you able to work things out:
Base from your videoinfo grub is using 1280x1024 (see the asterisk before the video resolution)
but you can still go higher than that. You can simply choose it in yast2-boot loader-kernel parameters-console resolution.
You can add your video resolution in the optional kernel command line parameter like so: video=your_resolution base from what is available in the videoinfo. In yast2-boot loader settings-kernel parameters also.
In my “Yast > Bootloader > Kernel paramters” the Console resolution was set to “Auto”. I just changed it to 2560x1440. It automacially ran the mkinitrd. I noted that the /boot/grub2/grub.cfg file now has the line “set gfxmode=2560x1440” instead of the previous “set gfxmode=auto”. On the next reboot I’ll see if this makes any difference.
loglevel=2 prevents annoying messages being displayed on the screen, but they are still visible in journal:
**erlangen:~ #** journalctl --dmesg --priority err
Sep 05 06:30:44 erlangen kernel: **kvm: support for 'kvm_amd' disabled by bios**
Sep 05 06:30:44 erlangen kernel: **kvm: support for 'kvm_amd' disabled by bios**
Sep 05 06:30:44 erlangen kernel: **kvm: support for 'kvm_amd' disabled by bios**
Sep 05 06:30:44 erlangen kernel: **kvm: support for 'kvm_amd' disabled by bios**
Sep 05 06:30:44 erlangen kernel: **kvm: support for 'kvm_amd' disabled by bios**
Sep 05 06:30:45 erlangen kernel: **kvm: support for 'kvm_amd' disabled by bios**
Sep 05 06:30:45 erlangen kernel: **kvm: support for 'kvm_amd' disabled by bios**
Sep 05 06:30:45 erlangen kernel: **kvm: support for 'kvm_amd' disabled by bios**
Sep 05 06:30:45 erlangen kernel: **kvm: support for 'kvm_amd' disabled by bios**
Sep 05 06:30:45 erlangen kernel: **kvm: support for 'kvm_amd' disabled by bios**
**erlangen:~ #**
**erlangen:~ #** journalctl -b -g 'Show Plymouth'
Sep 05 06:30:42 erlangen systemd[1]: Show Plymouth Boot Screen was skipped because of a failed condition check (ConditionKernelCommandLine=!plymouth.enable=0).
Sep 05 06:30:43 erlangen systemd[1]: Show Plymouth Boot Screen was skipped because of a failed condition check (ConditionKernelCommandLine=!plymouth.enable=0).
**erlangen:~ #**
[FONT=monospace]**#** journalctl -b -g 'Show Plymouth'
Sep 03 02:25:45 quattro systemd[1]: Starting Show Plymouth Boot Screen...
Sep 03 02:25:45 quattro systemd[1]: Started Show Plymouth Boot Screen.
Sep 03 02:25:51 quattro systemd[1]: Stopped Show Plymouth Boot Screen.
Sep 03 02:25:52 quattro systemd[1]: Starting Show Plymouth Boot Screen...
Sep 03 02:25:52 quattro systemd[1]: Started Show Plymouth Boot Screen.
[/FONT]
You may save /etc/default/grub to a copy, add the option to the current file, run ‘update-bootloader’ and reboot. You may undo the changes made by replacing current /etc/default/grub by the saved version, updating bootloader and rebooting.
I believe in you.