Have to repeatedly hit ANY key to boot

Startup hangs when the progress bar first appears, I have to hit a key 8 times to get to the desktop.

This occurs with all recent releases of Ubuntu, Kubuntu, Mint, Debian and SuSE. It seems to affect mainly AMDs.

I have been reading/searching for days and can not find even a hint of a solution but I have found hundreds of complaints.

ANY information will help me track this “bug”. :\

AMD - Phenom 9850 Quad 2.5 GHz
ASUS - M3N-HT Deluxe
OS - SuSE 11.1 (64 bit)

You need to see what is causing it to hang. If you press esc, [iirc], this will drop you from the progress bars to the text console while booting, so you will get to see all of the issues after the first. You could also edit your GRUB menu.lst and set splash=verbose [normally splash=silent] on the system you boot, to get more ideas.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This has been seen a couple times already in this forum (search if
interested). The previous fix has been to add ‘acpi=off’ to your Grub
boot line, but do it in a one-off way while booting (rather than
changing things permanently) to see if that helps you. Also note this
may change/break other power management things you do not expect (like
your computer turning off automatically when the OS finishes shutting down).

Good luck.

NigmaToolin wrote:
> You need to see what is causing it to hang. If you press esc, [iirc],
> this will drop you from the progress bars to the text console while
> booting, so you will get to see all of the issues after the first. You
> could also edit your GRUB menu.lst and set splash=verbose [normally
> splash=silent] on the system you boot, to get more ideas.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJjEWR3s42bA80+9kRAr3AAKCA8pb9MAeoie2A6Zu6nQ4yfFxOYwCfW0BD
Xwe3lTvJyogdsCs2jyMvtgM=
=PqXp
-----END PGP SIGNATURE-----

Not all AMDs. Just the ones with more than one core. It has to do with the time stamp counter. I ran into this problem with my laptop which is a dual core AMD Turion. I fixed it by adding the following parameters to the kernel line in /boot/grub/menu.lst somewhere between the “resume=/dev/sda*” and “splash=silent” parameters:

notsc pci=assign-busses apicmaintimer idle=poll reboot=cold,hard

Oddly enough, I can boot Slackware without these parameters. But I am forced to use them for openSUSE, Fedora, and Debian. Hope this works for you.

plasmonics wrote:
> Oddly enough, I can boot Slackware without these parameters. But I am
> forced to use them for openSUSE, Fedora, and Debian. Hope this works
> for you.

What is the kernel version for your Slackware distro?

Version 2.6.29-rc3. I also use this version for Debian/Lenny.

This fix worked, SuSE now shuts down & starts up without me having to continually hit a key.:open_mouth:

Thank You Very Much plasmonics!!:):):slight_smile:

Glad it worked for you. It would also have worked if you had passed:

noapic

instead of all of the above parameters. But then you would only see one core. Right now you should see all four. Try

cat /proc/cpuinfo | grep processors

Ahem. try
cat /proc/cpuinfo | grep processor

The noapic did not work at all, system went into continual reboot.

Yes all 4 cores are running.:slight_smile:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

cough
grep processor /proc/cpuinfo

Good luck.

NigmaToolin wrote:
> plasmonics;1940511 Wrote:
>> … Try
>>
>> cat /proc/cpuinfo | grep processors
> Ahem. try
> cat /proc/cpuinfo | grep processor
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJjZl63s42bA80+9kRAgUwAJ98h5WeEzjQHDHt0rf+ukdhGtYisQCfb3Tq
Yt1Heu0TlhGhN5PfX3Bgtz4=
=7G68
-----END PGP SIGNATURE-----

[QUOTE=ab@novell.com;1940739]-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

cough
grep processor /proc/cpuinfo

Good luck.

NigmaToolin wrote:
> plasmonics;1940511 Wrote:
>> … Try
>>
>> cat /proc/cpuinfo | grep processors
> Ahem. try
> cat /proc/cpuinfo | grep processor
>
>

Neater, it is the same output however. I only posted because I found I had to take the last s off to make it work.