I think I broke plymouth, I was trying to debug why my AMD card fails at suspending, so I read somewhere that I should edit
/etc/suspend.conf like this in order to get more verbose output:
loglevel = 255
splash = n
After that my plymouth splash was replaced with a black screen, so I changed back to "splash = y", rebooted but still a black screen.
Sorry can’t help but I would like to gently point out for the future that any time you make a change to a config file always make a backup first. In fact many editors do make backups often named the same but ending in a ~ character. You might check.
suspend is not used at all by default any more, and in 13.2 it even does not support any splash at all.
Still, try to comment out both options, by adding a ‘#’ at the beginning of the lines.
You could try to uninstall pm-utils too though, maybe that helps.
After that my plymouth splash was replaced with a black screen, so I changed back to "splash = y", rebooted but still a black screen.
You mean the splash screen during boot?
/etc/suspend.conf should have no influence at all on that.
So I ran:
sudo plymouth-set-default-theme -R openSUSE
Without success again.
Do you actually have plymouth-branding-openSUSE installed?
Those posts are are about Tumbleweed.
Also, they talk about seeing the text mode plymouth screen (i.e. 3 dots, or 3 question marks), not a completely blank screen.
But, what driver/module should I put here? the explanation says it should be an KMS video driver, I’m using the proprietary AMD one (fglrx)
In that case, none.
You could try fglrx, but I have no idea whether that works.
When I say backup I mean make a copy of the file you don’t have to go to the trouble of doing a full backup. It allows one to return to a known good state without having to remember all the changes. Just copy the file to a file called thefilename.bak
suspend is not used at all by default any more, and in 13.2 it even does not support any splash at all.
Still, try to comment out both options, by adding a ‘#’ at the beginning of the lines.
Got it, I did commented back those lines
Do you actually have plymouth-branding-openSUSE installed?
I do, and also the Plymouth splash was working just fine.
Those posts are are about Tumbleweed.
Also, they talk about seeing the text mode plymouth screen (i.e. 3 dots, or 3 question marks), not a completely blank screen.
Yes, but I though they may help, here’s some other post I found:
Try to reinstall it.
Also, try to run “sudo mkinitrd”. I’m not sure whether plymouth-set-default-theme actually does anything if you set the same theme that’s already set.
And please clarify:
You see a completely black screen, right? No text messages or similar?
Does pressing ESC have any effect?
You’re not using plymouth.enable=0 or similar on the kernel command line?
cat /proc/cmdline
Yes, but I though they may help, here’s some other post I found:
Rather not.
It’s something completely different whether plymouth falls back to text mode (because it cannot load the graphics driver), or it displays a black screen.
Try to reinstall it.
Also, try to run “sudo mkinitrd”. I’m not sure whether plymouth-set-default-theme actually does anything if you set the same theme that’s already set.
And please clarify:
You see a completely black screen, right? No text messages or similar?
Does pressing ESC have any effect?
I had reinstalled it with no effect but after that I ran **sudo plymouth-set-default-theme -R openSUSE **instead mkinitrd (but I think the first command also runs mkinitrd).
I see a black screen during the time (aprox.) it should be the splash screen, then I see the boot log and then the login screen.
You’re not using plymouth.enable=0 or similar on the kernel command line?
You are using some non default options: “elevator=deadline
libata.force=noncq acpi_sleep=s3_bios”. Why? :-?
Maybe to solve your initial problem with suspend?
Just to be sure - do you see GRUB boot menu? What exactly “boot log” is - is it kernel output, is it output of services that are starting? Do you have normal 80x25 text console at this point or is it frame buffer (which usually has more lines/columns)?
elevator=deadline is a good scheduler for SSDs.
I have to use libata.force=noncq with my Samsung EVO 840 SSD otherwise I got a lot of CRC errors.
Yes I was trying to debug why my AMD card doesn’t work when suspending to RAM. I guess I can remove acpi_sleep=s3_bios (because it didn’t work).
GRUB2 menu shows up fine, the boot log is the list of the services starting (the same you see when you do: cat /var/log/boot.log). I see this in a “graphical” way, I mean is not the 80x25 text console.
I found that running **plymouthd; plymouth --show-splash **works from a text console.
I Finally solved it!!!
The file /etc/plymouth/plymouthd.conf contains
[Daemon]
Theme=openSUSE
but there’s another file called /etc/plymouth/plymouthd.conf.rpmnew, this is the default configuration when you reinstall plymouth, and it has:
# Distribution defaults. Changes to this file will get overwritten during
# upgrades.
[Daemon]
Theme=openSUSE
ShowDelay=5
So I added the delay line into /etc/plymouth/plymouthd.conf, however this didn’t work either, so I modified like ShowDelay=0 and now the splash is back!
Thank you all for helping me out!
I have the same problem on two PCs (one desktop and one laptop) running Tumbleweed.
I looked at the whole thread, tried all given solutions/workarounds but I still see the black screen when the plymouth splash should be shown.
