The 9.10 boot loader progress bar

Vishnoo drkvi-a at
Mon Jan 25 20:01:08 UTC 2010

On Mon, 2010-01-25 at 11:53 -0700, Charlie Kravetz wrote: 
> I think the issue here is how old the machine is. On an older machine,
> a blank screen is difficult to deal with. When there is nothing there,
> for 5-?? seconds, how does anyone know if the system is stalled or
> working? Many of us use old hardware. That hardware is not really going
> to reach the 10 second boot anyway. It would be nice to have a way of
> knowing without waiting 5 minutes to find out the boot stalled.
> -- 
> Charlie Kravetz 
On Mon, 2010-01-25 at 21:01 +0200, Amahdy wrote:
> >>If something goes wrong, I can always hit esc to make the GRUB menu
> come up at boot and edit the entry to remove "quiet splash" to see the
> messages for debugging.
> How can you determine "If something goes wrong"? in many situations I
> can't know if something getting wrong or not maybe everything is ok
> and the system loads but there is somehting hidden there that I never
> noticed...
> For example couple of years ago, my previous laptop had "fedora 10",
> and I noticed that fedora attempt to load some bluetooth device while
> my laptop doesn't have any bluetooth in it, I'd never notice that
> without the text-loader and although everything works but there is a
> little thing out there to remove to at least make things better than
> it could be ...
> My brother (a newbie) once asked me why there is a [FAILED] in the
> fedora 11 loading, when I fixed it he told me that since months he
> thought that his modem is broken and doesn't work and he would never
> change his mind until he -as a matter of curiosity- asked me about
> this [FAILED]! the point is: he is not technical but he noticed
> something and just wanted to report it...
> -- Amahdy AbdElAziz

The *option* to display the messages was something that the design team
was interested in fixing for the the Lucid cycle. But AFAIK, i dont
think there has been any progress regarding that.[since there were
bigger issues to fix]

You might try contacting the design team...


More information about the Ubuntu-devel-discuss mailing list