verbose on startup with Karmic

[antistress]

At startup i 1st see a black screen with
usb_id[418]: unable to access '/devices/pci0000:00/0000:00:1d.0/udb2/2-2'

then another black screen with :
fsck from util-linux-ng 2.16
fsck from util-linux-ng 2.16
fsck from util-linux-ng 2.16
/dev/sda1: clean, 200234/549440 files, 920520/2196880 blocks
stockage: clean, 4641/30531584 files, 68133400/122096000 blocks
/dev/sda3: clean, 16297/14655488 files, 14841986/58607128 blocks
 * Setting preliminary keymap...
 * Starting AppArmor profiles
 * Setting up console font and keymap...

Then i have the new Ubuntu brown screen with progress bar (note that i see the throbber/pointer at the same time than the progress bar which doesn't make sense)

ProblemType: Bug
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC888 Analog [ALC888 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: tb 1555 F.... pulseaudio
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfe938000 irq 16'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,18491e01,00100001'
   Controls : 28
   Simple ctrls : 16
Date: Tue Oct 6 23:23:03 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=177764e0-03fa-45ed-82a8-d34d485092c0
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: linux-image-2.6.31-12-generic 2.6.31-12.39
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-12-generic root=UUID=bb4e22b5-0b07-4b9a-bb5e-18b89231089a ro quiet splash
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-12.39-generic
RelatedPackageVersions: linux-firmware 1.21
RfKill:

SourcePackage: linux
Uname: Linux 2.6.31-12-generic i686
dmi.bios.date: 01/18/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.10
dmi.board.name: ConRoe1333-DVI/H.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd01/18/2008:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvn:rnConRoe1333-DVI/H.:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 439648, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

[Mathieu Marquer (slasher-fun)]

I don't agree this a duplicate : this bug is about the xsplash being displayed too late in the boot process, while bug 439648 is about a specific message regarding a PCI device at the beginning of the boot process.

[kulight (kulight)]

this bug is describing 2 different issues
1. is the usb device error
2. the actual display of text before xsplash. (i think ,from the description, he meant to report this one and it's dupe of 438335)

[Séverin Lemaignan (skadge)]

I do have a similar problem, but without any of the usb_id issues.
I get a blank screen, then

fsck from util-linux-ng 2.16
fsck from util-linux-ng 2.16
fsck from util-linux-ng 2.16
/dev/sda1: clean, 200234/549440 files, 920520/2196880 blocks
stockage: clean, 4641/30531584 files, 68133400/122096000 blocks
/dev/sda3: clean, 16297/14655488 files, 14841986/58607128 blocks
 * Setting preliminary keymap...
 * Starting AppArmor profiles
 * Setting up console font and keymap...
[...]

Then the new Ubuntu brown startup screen.

It's not a duplicate of bug 439648

[Robbie Williamson (robbiew)]

We have addressed these console printing issues and will be checking in
the changes soon.

On Thu, 2009-10-08 at 14:33 +0000, Séverin Lemaignan wrote:
> I do have a similar problem, but without any of the usb_id issues.
> I get a blank screen, then
>
> fsck from util-linux-ng 2.16
> fsck from util-linux-ng 2.16
> fsck from util-linux-ng 2.16
> /dev/sda1: clean, 200234/549440 files, 920520/2196880 blocks
> stockage: clean, 4641/30531584 files, 68133400/122096000 blocks
> /dev/sda3: clean, 16297/14655488 files, 14841986/58607128 blocks
> * Setting preliminary keymap...
> * Starting AppArmor profiles
> * Setting up console font and keymap...
> [...]
>
> Then the new Ubuntu brown startup screen.
>
> It's not a duplicate of bug 439648
>
> ** This bug is no longer a duplicate of bug 438335
> Boot messages show before xsplash kicks in
>

--
Robbie Williamson twitter/identi.ca: undacuvabrutha
Ubuntu Foundations & Security Team Manager robbiew[irc.freenode.net]
http://wiki.ubuntu.com <email address hidden>

"You can't be lucky all the time, but you can be smart everyday"
 -Mos Def

"Arrogance is thinking you are better than everyone else, while
Confidence is knowing no one else is better than you." -Me ;)

[antistress (antistress)]

bug seems to be more or less fixed for me

1°) i don't have anymore verbose before the white ubuntu logo on black screen

2°) there is only some line that very quickly appear & disappear after the white ubuntu logo on black screen (i can't even read them)

[GaryW (gnubyexample)]

Bug is still there for me and I have to say this gives a very poor impression.

There has been a lot of effort put into "making ubuntu more polished" and then
some update comes through* and its back to end user console output.

*This console behaviour did not exist on my machine in first two weeks
of running Karmic official release

My unqualified suspicion is that this console output began on my machine when an update was
made to readahead/sreadahead in the second week of November.

The console output I see is somewhat similar to as described in the bug report,
but does not report anything meaningful other
than telling me that it has kindly run "fsck from util-linux-ng 2.16"

My comment fits closest with comment #5 by Séverin Lemaignan as in my case no
errors are reported.

I am hoping that if I wait a couple of weeks, then the fix can be checked in as referrred to in
comment #6 (Robbie Williamson) and the problem will go away :)

[zasq (zasq)]

I suppose my system is affected by this bug too, because every once in a while the boot procedure stops completely with a blank screen. With a verbose boot I can see that this seems to happen when fsck is checking the hard disk. I have to press the on/off button to turn the system off and then, after one or a few times trying to boot again, the system boots normally... I am posting this here because I also suppose this bug appeared after installing/upgrading readahead...
If I can provide any additional informatione please let me know...

[Brad Figg (brad-figg)]

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.