Karmic: Boot up problem, after usplash logo is a blank screen for about 14 seconds before xsplash appears briefly.

Bug #453337 reported by philinux
86
This bug affects 18 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Martijn Bastiaan

Bug Description

There are no error messages, usplash logo is on screen for a few seconds then a blank screen. No flashing cursor or errors. Then xsplash starts but appears only briefly before the gdm.

ProblemType: Bug
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: philinux 1875 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xf7ff4000 irq 16'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10ec0883,1043829f,00100002'
   Controls : 35
   Simple ctrls : 20
Date: Fri Oct 16 18:51:03 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=/dev/sdb2
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-14-generic 2.6.31-14.47
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=e1b4ae39-b02b-4d56-953d-63d5cbbef801 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.47-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.23
RfKill:

SourcePackage: linux
Uname: Linux 2.6.31-14-generic x86_64
dmi.bios.date: 01/23/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0304
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M3A78-EH
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0304:bd01/23/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3A78-EH:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
philinux (philcb) wrote :
Revision history for this message
philinux (philcb) wrote :

Wish I could edit the above. After the latest usplash update the timings have changed. I just checked with my phones stopwatch.

Usplash logo is on screen for 12.5 secs.

Blank screen for 9.4 secs.

xsplash to gdm for 6.6 secs.

Revision history for this message
fossfreedom (fossfreedom) wrote :

Can also confirm the above but with the following values...

Usplash logo is on screen for 25 secs.

Blank screen for 25 secs.

xsplash to gdm for 25 secs.

enclosed is my boot chart.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Martijn Bastiaan (hmb1) wrote :

I can confirm this behaviour. I'm not sure what the problem is.

Changed in linux (Ubuntu):
assignee: nobody → Martijn Bastiaan (hmb1)
Revision history for this message
philinux (philcb) wrote :

I've attached a bootchart.

Revision history for this message
godhika (godhika) wrote :

Same thing here. Looking at my bootchart it seems like my cpu is waiting most of the time and the disk throughput seems also quite low to me (28 mb/s - hell thats the max speed of my internet connection) . Bootchart attached

Revision history for this message
Martijn Bastiaan (hmb1) wrote :

> 28 mb/s - hell thats the max speed of my internet connection
28 mini-bits? :-). Your hard disk reads 28 MB/s and your internet connection downloads with 28 Mb/s (8 times less).

Revision history for this message
philinux (philcb) wrote :

Is there a solution being worked on? If so can we have a progress report. Cheers.

Revision history for this message
philinux (philcb) wrote :
Revision history for this message
TheFinePrint (rolmol) wrote :

I am starting to suspect that this is the bug I too have been experiencing on a laptop I set up for a friend. Unfortunately I don't think I ever let the computer sit for long enough (10s according to #2 here) before trying something else.

I changed from GDM to XDM, and while I still didn't get xsplash (sweeping progression bar), I got to a working login screen at the expected time. Boot from the live-CD worked as intended, with the proper splash screens etc, but of course with no login-screen (since it went directly to a working desktop).

I posted my experience here:
http://ubuntuforums.org/showthread.php?t=1293255&highlight=thefineprint&page=3

Revision history for this message
philinux (philcb) wrote :

Three days to go and I'm a bit surprised there is no progress on this bug. The boot experience is the worst I've ever seen.

philinux (philcb)
tags: added: ubuntu-boot-experience
Revision history for this message
Dannis (dbclist) wrote :

I am installing Karmic Koala on an HP IQ 506t Touchscreen. NVidea vidio. Intel chipset with onboard sound. I have had silence except for headphones and no recording capability since installing my first taste of Ubuntu, Jaunty. I can put up with that because I dual-boot with Vista and I understand that Intel doesn't share info so y'all can program drivers for the sound chips. I had absolutely no problem with video until now. I am about 30 mins from the finish, and my screen goes blank, then asks for my password. About every 15 secs. This is driving me nuts. I am scared I'll have the dreaded black screen when it installs completely. Help! I need my Ubuntu, and I don't want to have to wipe the HD and start over. National Novel Writing Month starts at midnight and I had plans to write for a couple hours....

Revision history for this message
Dannis (dbclist) wrote :

Install aborted, now get blank screen with login about every 30 secs. What do I do now? Which logs do I send you? I'm including an excerpt of errors from Syslog. Thanks!

Dannis

Revision history for this message
Dannis (dbclist) wrote :

Here's a log excerpt. Tell me if you need more, or a different log than syslog. I'm new to Ubuntu since Jaunty, and cross-eyed now.

Revision history for this message
Dannis (dbclist) wrote :

Update: Ubuntu fixed itself and I'm back to happily working Jaunty. Should I attempt a reinstall?

Revision history for this message
Iain Buclaw (iainb) wrote :

Not sure if this helps you philinux, but removing stop on starting-dm seemed to shorten the "inbetween" black screen between 1-2 seconds depending on reboot/startup from cold. At least, on first impressions (admittedly, it could just be a placebo working here).

File edited: /etc/init/usplash.conf

Change made:
#stop on (starting-dm
# or stopped rc RUNLEVEL=[2345]
stop on (stopped rc RUNLEVEL=[2345]
         or starting rcS
         or starting mountall-shell)

After change: sudo update-initramfs -u -k all

Updating the initrd is needed because quote from the file:
"On boot, this is nominally started by the initramfs so the pre-start script, script and post-start script parts are actually not run."

Regards
Iain

Revision history for this message
Iain Buclaw (iainb) wrote :

OK, after several reboots, 1-2 seconds is a bit of an exaggeration (4-5 seconds on my watch, not on my counting skills).

Only notable difference between before and after is that before there was a blinking _ on the tty which added about 3 seconds, now there is just a plain black screen. I suppose that could be counted as an improvement...

Revision history for this message
philinux (philcb) wrote :

Tries this on Lucid and it does indeed shave about 4 seconds of the boot time. Confirmed with bootchart.

However I was getting graphics artifacts at the desktop. Now this could be lucid not the changes to usplash.conf

Revision history for this message
philinux (philcb) wrote :

I've changed the file back to the default and the graphics problem has gone so it's nothing to do with lucid.

Bootchart on last boot was 1.04.

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.