12.2 - Fresh Install - boot messages are gone

English Install/Boot/Login
1

Hello.
During boot time, boot message are gone due to this error message I suppose :

Starting Show Plymouth Boot Screen... 
Failed to start Show Plymouth Boot Screen                             [FAILED]
See 'systemctl status plymouth-start.service' for details.

Systemctl show :

linux:~ # systemctl status plymouth-start.service
plymouth-start.service - Show Plymouth Boot Screen
          Loaded: loaded (/lib/systemd/system/plymouth-start.service; static)
          Active: failed (Result: exit-code) since Fri, 09 Nov 2012 10:35:18 +0100; 59min ago
         Process: 429 ExecStart=/usr/sbin/plymouthd --mode=boot --pid-file=/var/run/plymouth/pid --attach-to-session (code=exited, status=69)
          CGroup: name=systemd:/system/plymouth-start.service
linux:~ #

Seems to be a bug which seems to be still alive
Found this :
[Bug 780976] New: Systemd fails to start plymouth
from
Mailinglist Archive: opensuse-bugs

What can I do ?

.

2

Thread is closed.
Have reinstall for other reasons and now boot messages are alive.

3

If configuring the boot loader that way :
yast

  • System
    [LIST]
  • Boot Loader
    [LIST]
  • Boot Loader Options
    [LIST]
  • Optional Command Line Parameter

[/LIST]
[/LIST]
[/LIST]
[INDENT=5]Replace splash=silent by splash=verbose
You loose the splash screen but you get the booting message
[/INDENT]

4

On 2012-11-17 14:56, jcdole wrote:
> Replace splash=silent by splash=verbose
> You loose the splash screen but you get the booting message

That’s what you wanted? I did not answer that, because there is another
combination that produces better results with systemd, but I don’t
remember it. With systemv “verbose” is fine, but with systemd you need
something else.

Try one of these - I found them in a bugzilla report of mine:



> splash=verbose console=tty1 systemd.log_level=debug systemd.log_target=kmsg
>
> splash=verbose console=tty1 loglevel=3

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))

5

You probably chose a resolution your system isn’t capable off during boot.

6

I re-explain my problem.
Until 12.2, I used to use ALT+F2 to show up the boot message during start-up in place of the splash screen.
This is not working any more.

7

It seems that boot messages aren’t trendy anymore,
because they seem to confuse unexperienced users
and obviously aren’t Windows-like.

I’ve 2 different systems running under openSUSE 12.1 currently:

One system with an intel Core i5 with openSUSE 12.1 64bit - no boot messages.

The other system with an old Pentium Katmai at 500 MHz (0.5 GHz) - yes, boot messages.

This isn’t a bug.

Yours
Mike

8

I should add:

the old system is running with old KDE3 desktop (for obvious reasons),

the newer system is running with KDE4 of openSUSE 12.1.

9

On 2012-11-18 00:36, ratzi wrote:
>
> It seems that boot messages aren’t trendy anymore,
> because they seem to confuse unexperienced users
> and obviously aren’t Windows-like.

True, but the modifications I posted get them back. Try.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” (Minas Tirith))

10

Hi Carlos,

That’s a nice hint.
I’ll try that later, and will post the result.

To be fair - there is one point:

On a modern system (like a recent quad core),
booting Linux (or openSUSE) takes place that fast,
that it would be very hard to read the startup messages
anymore,
at least as a human.

So, to not display these makes sense, in a certain way,
except for one single aspect:
If the startup should fail, then the startup messages would still
clearly hint to the process that failed,
even if the desktop wasn’t activated yet at that point.

Dear jcdole,
you can still see the startup messages if you open a console/terminal window,
and say ‘dmesg’.

Wish all of you the best
Mike

11

After 30 years in computing I think it is a sufficient reason to leave the possibility to the operator to show up the booting message. But this is only my little point of view.

I know that, but it suppose you can log in !

For the moment this is my boot loader config and I can look after the booting messages.

Optional Kernel Command Line Parameter :

 resume=/dev/disk/by-id/ata-HDT722516DLA380_VDB71BTCDG0BGC-part8  splash=verbose showopts

I think we can close my question.

12

Thank you to everybody for helping.