openSUSE 12.2 - No Plymouth!

Hi all,

Installed 12.2 yesterday, and most things are definitely an improvement - but I have yet to get Plymouth to show at either startup or shutdown. After the GRUB2 menu appears (which is looking a lot nicer than in 12.1) I just get a bright green 8bit progress bar along the bottom of the screen, which AFAIK is shown when Plymouth doesn’t support your driver/resolution.

I’m running the nVidia proprietary driver, and the maximum res I can get GRUB2 to do is 1280x800 (my monitor is 1920x1080). I tried running:

plymouthd; plymouth --show-splash

just to test it and nothing appears on screen, or output in the console. I have also ran

mkinitrd

after every change to GRUB2, but to no avail.

I’ve read on the net that Plymouth takes little wrangling to get working under nVidia’s proprietary driver, but I’ve only seen this in relation to other distros that refer to files in /etc that I don’t have. So is there a proper openSUSE guide around, or am I missing something obvious?

Thanks,
Cam

So I get the correct screen (it is 1600x1200 even though I too support your same resolution) and I have the nVIDIA driver loaded. I do have a blog on Grub configuration with a nice bash script you can find here:

GNU Grub2 Command Help/Config Editor - Version: 1.75 - Blogs - openSUSE Forums

Not sure how you loaded the NVIDIA driver, but I have a lot of stuff for it here:

Installing the nVIDIA Video Driver the Hard Way - Blogs - openSUSE Forums

AND

LNVHW - Load NVIDIA (driver the) Hard Way from runlevel 3 - Version 1.46 - Blogs - openSUSE Forums

AND

S.A.N.D.I. - SuSE Automated NVIDIA Driver Installer - Version 1.47 - Blogs - openSUSE Forums

So I suggest you might use my Gruib2cmd program to try a grub resolution of 1600x1200 your self.

Thank You,

Thanks for you response, but I can’t see how it can help…

I’ve set up GRUB2 using the Boot Loader config in Yast, this works fine in the sense that GRUB2 launches correctly and loads openSUSE correctly - just without Plymouth. Of which there are no settings for.

It’s been a long time since I’ve had to manually compile the driver into the kernel. I’ve installed nvidia-gfxG02-kmp-desktop driver from the Software Manager, I know the driver itself is fine as I can play games through WINE+Steam perfectly well. I also uninstalled the nouveau driver, I didn’t think that would cause a problem as the module is blacklisted by the nVidia driver anyway.

And you have visited this screen in YaST / System / Boot Loader / Type - Boot Loader Options / Use Graphics Console - Console Resolution and setup the bootloader resolution and graphic mode?

http://paste.opensuse.org/view/download/70479224

Thank You,

On 09/07/2012 04:06 PM, jdmcdaniel3 wrote:
>
> cbamber85;2484583 Wrote:
>> Thanks for you response, but I can’t see how it can help…
>>
>> I’ve set up GRUB2 using the Boot Loader config in Yast, this works fine
>> in the sense that GRUB2 launches correctly and loads openSUSE correctly
>> - just without Plymouth. Of which there are no settings for.
>>
>> It’s been a long time since I’ve had to manually compile the driver
>> into the kernel. I’ve installed nvidia-gfxG02-kmp-desktop driver from
>> the Software Manager, I know the driver itself is fine as I can play
>> games through WINE+Steam perfectly well. I also uninstalled the nouveau
>> driver, I didn’t think that would cause a problem as the module is
>> blacklisted by the nVidia driver anyway.
>
> And you have visited this screen in YaST / System / Boot Loader / Type
> - Boot Loader Options / Use Graphics Console - Console Resolution and
> setup the bootloader resolution and graphic mode?
>
> [image: http://paste.opensuse.org/view/download/70479224]

The Plymouth documentation says the following:

"Plymouth primarily uses KMS (Kernel Mode Setting) to display graphics. If you
can’t use KMS (e.g. because you are using a proprietary driver) you will need to
use framebuffer instead. Uvesafb is recommended as it can function with
widescreen resolutions.

If you have neither KMS nor a framebuffer, Plymouth will fall back to text-mode."

That 3-colow sliding bar is text mode. On the one machine where nouveau works,
I get the openSUSE theme, which is the “fireflies” scheme. On one that does not
run X, and the other where nv is the graphics driver, I get the text version.

See https://wiki.archlinux.org/index.php/Plymouth for some documentation.
Although it is specifically for Arch Linux, everything seems to apply to
openSUSE. If you use the comand “sudo plymouth-set-default-theme details”, you
will get no splash screen, i.e. the same as hitting escape.

After trying just about every permutation of settings, it seems that setting the

Vga Mode

to anything other than

Unspecified

causes Plymouth to fallback to text mode. I imagine this is a ‘quirk’ between Plymouth and nVidia, whereas just about all other settings work fine.

So thanks jdmcdaniel3 for nudging me in the right direction!

Happy to be the helping nudger anytime.

Thank You,

cbamber85 wrote:

>
> After trying just about every permutation of settings, it seems that
> setting the
> Code:
> --------------------
> Vga Mode
> --------------------
> to anything other than
> Code:
> --------------------
> Unspecified
> --------------------
> causes Plymouth to fallback to text mode. I imagine this is a ‘quirk’
> between Plymouth and nVidia, whereas just about all other settings work
> fine.
>
> So thanks jdmcdaniel3 for nudging me in the right direction!

I’ve been trying the ugrade here on a couple of Nvidia-equipped boxes with
similar results. I finally got things straight by installing the Nvidia
driver after which all went well. I can either use ALT-F1 to get to a
command prompt from where it hangs up or ssh into the box if ssh is enabled.
Either way, I run yast from the command line (as root), add the Nvidia repo
then install the needed driver - G02 in my cases. Reboot and off we go.

I get the same general problems no matter how I install - clean, upgrade
from 11.4, or upgrade from 12.1 and the Nvidia driver resolves the problems
with Plymouth as well as X11/KDE crashes.


Will Honea

Sounds like this needs to go to bugzilla

gogalthorp wrote:

>
> Sounds like this needs to go to bugzilla

My problem is whether it is a bug or an Nvidia issue. The box I do most of
my work on has been a PITA since I got it - Lenovo with AMD AthlonX2-64 and
Nvidia MP51 chipset - with minor ACPI bugs, default IRQ assignments from the
BIOS, etc.

I guess we could expect better error messages and more info from those boot-
time crashes which would greatly simplify debugging the issue. Basically,
you have to read between the lines to figure out the actual basis for the
crash.


Will Honea

I have the same problem, plymouth does not show up and grub meny is really slow(by that I mean that it takes 1-2 seconds for it to react on keyboard press). After I choose what to boot some kind of green blocky artifact screen appears, I cant make anything on it but I guess it is supposed to show boot animation. I use gtx 570 with nouveau driver, fresh install.
Vga mode is unspecified in grub settings in yast, suse boot options are video=1920x1080 splash quiet showopts. Console resolution is autodected by grub2. My screen is 1920x1080 but it does not look like it is using this resolution during boot. After booting everything works fine, all effects in kde work as supposed, better than with propietary drivers in fact.
Can anyone help me configure plymouth to work? Thanks in advance.

If everything works fine after openSUSE has loaded, you have the best you can get without loading the nVIDIA proprietary video driver. You can leave well enough alone, or load the external driver. I have a blog on the subject you can find here:

Installing the nVIDIA Video Driver the Hard Way - Blogs - openSUSE Forums

This blog is on loading the driver the hard way as it is called, which is not hard, but the repository method has a link at the end you can read.

Thank You,

Thanks for reply. As I recall, plymouth should not work well with propietary driver because it doesn’t support kms?

Change the “vga=xxx” from “Unspecified” to one of the settings that are lower than your screen’s resolution.
It will affect the quality of the Plymouth during the boot up.

Start up Yast2-Boot Loader and click on the Boot Options button, change the framebuffer setting.
Click on the dropdown arrow and from the list select one of the preset settings.

NO, it does work, but after all of the lights come together, the screen goes blank except right in the center, for less than a second. Meaning, with the nVIDIA driver loaded, it works 99% through.

Thank You,

Well sir, I have the nvidia proprietary driver loaded - with the help of your excellent lnvhw script - and I also get the text progress bar. I no longer see the plymouth animation. I did see it with the nouveau driver but I prefer nvidia’s own driver. My vga was ‘unspecified’. As an experiment I changed vga to one of the pre-sets but it made no difference.
I am using legacy grub.

Best wishes,

Hugh

On further investigation, with reference to another distro I use which I also boot with grub legacy/legacy grub, I took the vga number from the end of that menu.lst and added it to the menu.lst (before showopts) of my 12.2 brand new openSUSE install.

I now have the animated boot splash again with the white circular dots fading gracefully towards the centre

The VGA number I added manually is this: VGA=791. I looked this up in wikipedia and VGA=791 produces a resolution of 16 bit 1024x768

It still looks a bit chunky to me but at least it works. My nvidia driver was installed the ‘hard way’ and it is GeForce310

My wish is that this might this help some other person seeking a return of their eye candy.

Best wishes,

Hugh

I’ve had good success with a setup that looks like this, leaving the VGA option as “unspecified”, setting console resolution to “autodetect by grub2” and feeding the resolution to the kernel via the kernel command line parameters:


resume=/dev/linux/swap splash=silent quiet video=1440x900 showopts

This is also with nVidia proprietary drivers (and on Tumbleweed, but that doesn’t matter right now).

Booting used to cost 5 seconds, now it is 5 minutes.

I tried to remove plymouth with
zypper rm plymouth
That gave no errors.

But now I get the the message:
plymouthd: could not start boot splash: No such file or directory.

Has anyone an idea how the get rid of this plymouth disaster?

Kind regard,
Ben

openSUSE has had this kind of big problems in years!

Hi, welcome.

99% sure plymouth is not the cause. It’s no more than a boot splash program. And, of course you get errors when you remove plymouth. The initrd contains a pointer to it, and it’s no longer there, so in a way you broke the system.
Which brings me to: how did you install, was this an upgrade of ???
Do you want help on this one, or do you just want to express your disappointment with plymouth ?