Upgraded this evening and the system seemed broken but did start the boot process after about 2 minutes. All normal thereafter. It doesn't make any difference if I boot to level 3. After leaving the boot menu, the screen simply displays a single underline character and nothing happens at all for 2 min. Then things get underway at normal speed.
Previous kernel is still installed and boots up quite normally.
Any ideas? Anyone else getting the same behaviour? I use the nvidia drivers but they are up to date and in any case shouldn't be used for a level 3 boot.
On Tue, 29 Dec 2009 00:32:07 +0000 N James Bridge wrote:
Any ideas? Anyone else getting the same behaviour?
I didn't have a problem, but you can see it spew a lot of info about what is happening if you remove the "quiet" option from the kernel boot line. That might give a clue where it is spending time.
2009/12/29 Tom Horsley tom.horsley@att.net:
I didn't have a problem, but you can see it spew a lot of info about what is happening if you remove the "quiet" option from the kernel boot line. That might give a clue where it is spending time.
Or run bootchart.. http://www.bootchart.org
-c
On Tue, 2009-12-29 at 00:32 +0000, N James Bridge wrote:
Upgraded this evening and the system seemed broken but did start the boot process after about 2 minutes. All normal thereafter. It doesn't make any difference if I boot to level 3. After leaving the boot menu, the screen simply displays a single underline character and nothing happens at all for 2 min. Then things get underway at normal speed.
Previous kernel is still installed and boots up quite normally.
Any ideas? Anyone else getting the same behaviour? I use the nvidia drivers but they are up to date and in any case shouldn't be used for a level 3 boot. -- N James Bridge james@xmas.demon.co.uk
Thanks for tips. Without "quiet" I still get no output at all for 2min 35sec, then normal rush of messages. Bootchart (very nice!) shows that the boot process itself is running normally, once it starts, about 45sec overall. The initial wait isn't shown on the chart. Once running, everything seems to be working. The entries in grub.conf are identical, except for version numbers.
So what causes the wait?
On Tue, 2009-12-29 at 20:00 +0000, N James Bridge wrote:
Without "quiet" I still get no output at all for 2min 35sec, then normal rush of messages. Bootchart (very nice!) shows that the boot process itself is running normally, once it starts, about 45sec overall. The initial wait isn't shown on the chart. Once running, everything seems to be working. The entries in grub.conf are identical, except for version numbers.
So what causes the wait?
You haven't provided any details. *Exactly* what text appears before the wait, and after the resumption?
On Wed, 2009-12-30 at 10:19 +1030, Tim wrote:
On Tue, 2009-12-29 at 20:00 +0000, N James Bridge wrote:
Without "quiet" I still get no output at all for 2min 35sec, then normal rush of messages. Bootchart (very nice!) shows that the boot process itself is running normally, once it starts, about 45sec overall. The initial wait isn't shown on the chart. Once running, everything seems to be working. The entries in grub.conf are identical, except for version numbers.
So what causes the wait?
You haven't provided any details. *Exactly* what text appears before the wait, and after the resumption?
Before: nothing. Just the flashing underline character, in the same large typeface as the boot menu.
After: flashing underline switches to a smaller size, then a message from plymouth (exactly the same for both versions of the kernel). plymouthd: ply_keyboard.c:450: ply_keyboard_add_input_handler: 'Assertion !=((void*)0)' failed. After this it continues as expected.
-
Chris Smart -
James Bridge -
Tim -
Tom Horsley