No splash shown,partial black screen, then X crashes on start with Plymouth

[Luke]

Binary package hint: plymouth

EXPECTED a splash screen resembling the options in the Plymouth package, GOT only a black screen plus any console messages post-invocation of Plymouth showing-and showing AGAIN if plymouth --show-splash invoked from another console. Also got failures of X to start except in failsafe mode(after plymouth had ended, presumably).

I spent a night testing Plymouth with the encrypted disks temporarily shut off for simplicity(no password calls and boot continues) and got the results below:

Desktop machine:
Video card is ECS Nvidia 6600LE (this card cannot run nv driver, only vesa or nvidia driver)
processer is AMD phenom II x4 955 BE
Board uses AMD chipset

Same or similar results (no splash, but only tested once) with MSI Wind U100 netbook using Intel Atom and Intel embedded graphics

OS: Current Lucid Lynx with netbook, Lucid Lynx with x rolled back (No nvidia-glx yet) on AMD/nvidia desktop.

Plymouth is version 0.8.0 ~-2

with boot options ro acpi_enforce_resources=no quiet splash:

default theme=uguntu-logo;

black screen until fsck messages show as console, then X either starts
in low graphics mode or refuses to start altogether.

with boot options ro acpi_enforce_resources=no quiet splash:

default theme=solar;

could not start boot splash-no such file or directory

ONCE ONLY saw "init:Plymouth main process killed by SEGV signal"

Another boot with boot options ro splash:

default theme=ubuntu-logo

console messages showed through during initramfs, then video card SHUT DOWN (no signal!)

With ro acpi_enforce_resources=no splash:

console messages showed through during initramfs, then black screen, then X starts in FAILSAFE mode(which won't restart X, a separate bug)

From CONSOLE after these boots:

running
/sbin/plymouthd --mode=shutdown
/bin/plymouth --show-splash

will re-display the console messages that showed through the otherwise black screen

X starts normally if GDM run by hand from console

Black screen on MSI U100 netbook, too, when I first downloaded and tried Plymouth.

Would like to see Plymouth working-it looks like it will be far easier to tune and customize than usplash once made to work with these kernels and this hardware. If this is not fixed I will have to pin mountall and cryptsetup at some point to mantain usplash compatability.

BOTH these machine are buggy in usplash as well, the new 2.6.31-7 kernel (ONLY this one so far) requiring vga=771 and the old Jaunty era framebuffer script in int for usplash not to give "input not supported" on Acer LCD monitor.Text will NOT display in this mode if usplash has not been run first! The MSI requires also jaunty-era "framebuffer" script in initramfs or custom splash locks up on first verbose call. The is because the newer script greys out the Ubuntustudio colors and probably matches a customized portion to the color set aside for text.

[Scott James Remnant (Canonical) (canonical-scott)]

I have no idea which of the may issues you've listed here you're trying
to report. The one that sounds like a bug is a duplicate, so I've
marked this report appropriately.

Please note that Plymouth is not yet integrated into Ubuntu; you can't
just install it and expect the same experience as you had with usplash
at this point (I'm in the process of uploading the bits now Alpha 1 is
out).

Also note that you would not expect a graphical screen on NVIDIA
hardware at this point, since the Kernel pieces (the nouveau driver)
have not yet been landed.

Once Plymouth has actually been made the default splash screen, if you
do experience particular problems, please file individual bug reports
for them.

Scott
--
Scott James Remnant
<email address hidden>

[Luke (lukekuhn)]

  The difference is that booting was not blocked unless I had cryptsetup waiting for a passphrase, there was no graphical screen and x crashed when it was time for it to start. The other report say no boot, not no splash.

Isn't Playmouth supposed to be able to fall back to using the framebuffer anyway?

> Date: Thu, 10 Dec 2009 20:23:03 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 495188] Re: No splash shown, partial black screen, then X crashes on start with Plymouth
>
> *** This bug is a duplicate of bug 495085 ***
> https://bugs.launchpad.net/bugs/495085
>
> I have no idea which of the may issues you've listed here you're trying
> to report. The one that sounds like a bug is a duplicate, so I've
> marked this report appropriately.
>
>
> Please note that Plymouth is not yet integrated into Ubuntu; you can't
> just install it and expect the same experience as you had with usplash
> at this point (I'm in the process of uploading the bits now Alpha 1 is
> out).
>
> Also note that you would not expect a graphical screen on NVIDIA
> hardware at this point, since the Kernel pieces (the nouveau driver)
> have not yet been landed.
>
> Once Plymouth has actually been made the default splash screen, if you
> do experience particular problems, please file individual bug reports
> for them.
>
> Scott
> --
> Scott James Remnant
> <email address hidden>
>
>
> ** This bug has been marked a duplicate of bug 495085
> cannot boot after installing plymouth
>
> --
> No splash shown,partial black screen, then X crashes on start with Plymouth
> https://bugs.launchpad.net/bugs/495188
> You received this bug notification because you are a direct subscriber
> of the bug.

_________________________________________________________________
Windows Live Hotmail is faster and more secure than ever.
http://www.microsoft.com/windows/windowslive/hotmail_bl1/hotmail_bl1.aspx?ocid=PID23879::T:WLMTAGL:ON:WL:en-ww:WM_IMHM_1:092009

[Scott James Remnant (Canonical) (canonical-scott)]

On Thu, 2009-12-10 at 21:08 +0000, Luke wrote:

> The difference is that booting was not blocked unless I had cryptsetup
> waiting for a passphrase
>
There has been no work in Lucid to integrate cryptsetup with Plymouth;
if you need cryptsetup, you won't be able to boot.

> there was no graphical screen
>
You say you have NVIDIA hardware? This is expected.

> and x crashed when it was time for it to start. The other report say
> no boot, not no splash.
>
X crashing is covered by the other bug and should be -3.

> Isn't Playmouth supposed to be able to fall back to using the
> framebuffer anyway?
>
There is no framebuffer for NVIDIA hardware; that's what the nouveau
driver provides.

Scott
--
Scott James Remnant
<email address hidden>