xplash logo not well display

[davidetkarine]

Binary package hint: xsplash

At each boot and just after the grub ubuntu selection I get a black screen for 20s and a fsck message and the Ubuntu logo not well displayed. The progress dot are also not well displayed and there some text across the screen.
The screen become normal when gdm start.

ProblemType: Bug
Architecture: i386
Date: Wed Mar 24 18:11:45 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: nvidia
Package: xsplash 0.8.5-0ubuntu1
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
SourcePackage: xsplash
Uname: Linux 2.6.32-17-generic i686

[davidetkarine (saveurlinux)]

My machine is a thinkpad R61 with nvidia nvs140 card and the screen resolution is 1680x1050

[davidetkarine (saveurlinux)]

I've got this message at boot:
plymouth main proces (385) terminated with status 2
could not connect to Plymouth
fsck from util-linux-ng 2.17.2 ... clean
init: ureadahead other main process (901) terminated status 4
init: ureadahead other main process (906) terminated status 4
init: ureadahead other main process (919) terminated status 4
init: Failes du spawn plymouth-log main process: unable to execute: No such File directory

[Cody Russell (bratsche)]

I can't tell what your actual problem is here from the description, but if there is one then it sounds like it's probably related to Plymouth.

[Steve Langasek (vorlon)]

This appears to be a complaint about the use of the text plugin due to the VGA16 framebuffer being the only one available, and is fixed in plymouth 0.8.1-1.

If you still encounter problems after upgrading to the current plymouth, please reopen the bug and provide more information.

[davidetkarine (saveurlinux)]

Dear you,
I reopened this bug as I updated plymouth and I don't have anymore all this message but
As I think Ubuntu is running a check disk at each boot.
I didn't find the way to get the message of what happened during this time.
What I've done:
1st I remove the nvidia drivers (I think the nouveau one is use now) so:
   - Usplash plymouth (ubuntu logo) appears at the correct resolution for about 1s just before gdm and after the black screen
during the boot process and while the screen is black I can see a hight disk activity that make me things that check disk is under precess.
Once logged I've got the cpu frequency set to Performance instead of Ondemand

When closing session I've got this message:
 - avahi-deamon main process terminated with status 255
and
 - usplash terminated with status 2

2nd I reinstall nvidia drivers
  - Rebooting and after grub, I still get the black screen then Usplash runs in very low quality and display a message:
    Your disk drive need to be checked for errors
Once logged I've got the CPU frequency set to Ondemand and running fine.

[Steve Langasek (vorlon)]

> 1st I remove the nvidia drivers (I think the nouveau one is use now) so:
> - Usplash plymouth (ubuntu logo) appears at the correct resolution for about
> 1s just before gdm and after the black screen

The delay in showing the splash screen is bug #540801.

> during the boot process and while the screen is black I can see a hight disk
> activity that make me things that check disk is under precess.

This is ureadahead, not a disk check. This is the expected behavior.

> Once logged I've got the cpu frequency set to Performance instead of Ondemand

The frequency governor is set by a script with a delay after startup, to prevent slowing down the initial boot.

> When closing session I've got this message:
> - avahi-deamon main process terminated with status 255
> and
> - usplash terminated with status 2

Some messages may be shown on shutdown before the splash screen reappears due to bug #540816.

> 2nd I reinstall nvidia drivers
> - Rebooting and after grub, I still get the black screen then Usplash runs in very low quality and display a message:
> Your disk drive need to be checked for errors

The low resolution of the splash screen is currently unavoidable with when using the nvidia binary driver.

Reclosing this report, then, as there don't appear to be any new bugs here.