Boot wait time of 3 minutes after installation of Karmic

Bug #493950 reported by Frank
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

When I switch on my PC I have to look at the "Intel Pentium 4" logo for about 3 minutes before anything happens.
I can not even enter the BIOS setup.
When I keep the "DEL" button pressed I enter the BIOS setup after the mentioned 3 minutes.
Of course when I do not keep the "DEL" button pressed I enter the boot menu after the 3 minutes.
I have a dual boot menu with Windows XP.
After I have chosen Ubuntu everything is working fine.
What can I do to remove this wait time ?
This is very bad for the acceptance of Ubuntu in my family !

ProblemType: Bug
Architecture: i386
Date: Tue Dec 8 09:30:35 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/yelp
NonfreeKernelModules: nvidia
Package: yelp 2.28.0-0ubuntu2
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
SourcePackage: yelp
Uname: Linux 2.6.31-16-generic i686

Revision history for this message
Frank (frank-schreuder) wrote :
saidimu apale (saidimu)
affects: ubuntu → linux (Ubuntu)
Andy Whitcroft (apw)
tags: added: karmic
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Frank,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 493950

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Frank (frank-schreuder) wrote : Re: [Bug 493950] Re: Boot wait time of 3 minutes after installation of Karmic

Hi Jeremy,

I don't known if this bug has anything to do with Ubuntu.
I have removed Ubuntu and installed an older version of Ubuntu (version
8).
The problem still occurred, so I think there is something wrong with my
computer hardware.

What do you think?

Regards,
Frank Schreuder

On Fri, 2010-04-23 at 23:29 +0000, Jeremy Foshee wrote:

> Hi Frank,
>
> This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .
>
> If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.
>
> apport-collect -p linux 493950
>
> Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.
>
> Thanks in advance.
>
> [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]
>
>
> ** Tags added: needs-kernel-logs
>
> ** Tags added: needs-upstream-testing
>
> ** Tags added: kj-triage
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Frank,
   Is it just the first boot or are all subsequent boots the same length of time? We do quite a bit of organization on the very first boot so it tends to take a bit longer than the others should.

~JFo

Revision history for this message
Frank (frank-schreuder) wrote :

Hi Jeremy,

I don't know exactly what you mean with the first boot.
Everytime I put on the PC I have to wait for about 3 minutes before
anything happens.

Regards,
Frank

On Tue, 2010-04-27 at 13:57 +0000, Jeremy Foshee wrote:

> Frank,
> Is it just the first boot or are all subsequent boots the same length of time? We do quite a bit of organization on the very first boot so it tends to take a bit longer than the others should.
>
> ~JFo
>

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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