kernel compiled - boot hangs - keybd blinks

[frankh@terra.com.br]

It is not the first time I compiled a kernel, so I upgraded from
2.4.21 to 2.4.22. Compiled and installed kernel and modules, edited
lilo.conf and ran lilo. Now the boot process is as follows:
- BIOS messages
- Lilo menu
- 'loading Linux 2.4.22 ..........'
- black screen, blinking keyboard (const.frequ., no morse code).
The only button the system responds to is Reset :-(

There is no reason to panic, because I can still boot the old
kernel. So:

1. Anybody knows what the blinking LEDs mean?

2. I verified the kernel configuration with respect to processor
type (AMD Athlon/K7) and file systems (ext2 and ext3 compiled into
kernel). What other options could prevent from booting at that
early stage?

--
-------------------------------------------------
Frank Hrebabetzky Tel.: +55 / 48 / 235 1106
Florianopolis +55 / 48 / 9998 7686
Brazil email: [email]frankh@terra.com.br[/email]

[Peter T. Breuer]

[email]frankh@terra.com.br[/email] wrote:

> It is not the first time I compiled a kernel, so I upgraded from
> 2.4.21 to 2.4.22. Compiled and installed kernel and modules, edited
> lilo.conf and ran lilo. Now the boot process is as follows:
> - BIOS messages
> - Lilo menu
> - 'loading Linux 2.4.22 ..........'
> - black screen, blinking keyboard (const.frequ., no morse code).
> The only button the system responds to is Reset :-(

> There is no reason to panic, because I can still boot the old
> kernel. So:

> 1. Anybody knows what the blinking LEDs mean?

Kernel panic.

> 2. I verified the kernel configuration with respect to processor
> type (AMD Athlon/K7) and file systems (ext2 and ext3 compiled into
> kernel). What other options could prevent from booting at that

Faulty compilation. Mobo issues. It's actually ram as far as I can see,
if you have the number of dots recorded right above. If you have, it's
died in the boot loader. So I'd rerun lilo and try it again.

If, otoh, there were a lot more dots, it would have failed as it
started to execute itself, which would be setup code.

> early stage?

Peter

[Peter T. Breuer]

[email]frankh@terra.com.br[/email] wrote:

> It is not the first time I compiled a kernel, so I upgraded from
> 2.4.21 to 2.4.22. Compiled and installed kernel and modules, edited
> lilo.conf and ran lilo. Now the boot process is as follows:
> - BIOS messages
> - Lilo menu
> - 'loading Linux 2.4.22 ..........'
> - black screen, blinking keyboard (const.frequ., no morse code).
> The only button the system responds to is Reset :-(

Recompile for i386 and try it again.

> 2. I verified the kernel configuration with respect to processor
> type (AMD Athlon/K7) and file systems (ext2 and ext3 compiled into
> kernel). What other options could prevent from booting at that
> early stage?

Peter

[Jeff S]

I don't know what the blinking lights mean, but the last time something similar happened to me, it was because I had defined the wrong processor type: I have a P150MMX, but had specified "Coppermine" by mistake.

On Sat, 6 Sep 2003 12:37:55 -0300
[email]frankh@terra.com.br[/email] wrote:

> It is not the first time I compiled a kernel, so I upgraded from
> 2.4.21 to 2.4.22. Compiled and installed kernel and modules, edited
> lilo.conf and ran lilo. Now the boot process is as follows:
> - BIOS messages
> - Lilo menu
> - 'loading Linux 2.4.22 ..........'
> - black screen, blinking keyboard (const.frequ., no morse code).
> The only button the system responds to is Reset :-(
>
> There is no reason to panic, because I can still boot the old
> kernel. So:
>
> 1. Anybody knows what the blinking LEDs mean?
>
> 2. I verified the kernel configuration with respect to processor
> type (AMD Athlon/K7) and file systems (ext2 and ext3 compiled into
> kernel). What other options could prevent from booting at that
> early stage?
>
> --
> -------------------------------------------------
> Frank Hrebabetzky Tel.: +55 / 48 / 235 1106
> Florianopolis +55 / 48 / 9998 7686
> Brazil email: [email]frankh@terra.com.br[/email]

[frankh@terra.com.br]

In article <8b7djb.q9t.ln@news.it.uc3m.es>, Peter T. Breuer wrote:

>
> Recompile for i386 and try it again.
>

Just recompiling for i386 didn't help. I followed exactly the kernel
README, incl. the hint to make mrproper, with the result that I lost my
config file. I went through the hole config process again, with the
result that

- it works now,

- I still don't have the faintest idea what was wrong before.

Excuse for the inconvenience.

-------------------------------------------------
Frank Hrebabetzky Tel.: +55 / 48 / 235 1106
Florianopolis +55 / 48 / 9998 7686
Brazil email: [email]frankh@terra.com.br[/email]

[Lars-Göran Andersson]

I have a recommendation to save the settings in menuconfig at a separate
file before exiting menuconfig.

You can then copy this file to another kernel-directory or just keep it to
reload it when you are regenerating the kernel. Then you are sure using the
same setting from kernel to kernel.

/Lars-Göran

[email]frankh@terra.com.br[/email] wrote:

> It is not the first time I compiled a kernel, so I upgraded from
> 2.4.21 to 2.4.22. Compiled and installed kernel and modules, edited
> lilo.conf and ran lilo. Now the boot process is as follows:
> - BIOS messages
> - Lilo menu
> - 'loading Linux 2.4.22 ..........'
> - black screen, blinking keyboard (const.frequ., no morse code).
> The only button the system responds to is Reset :-(
>
> There is no reason to panic, because I can still boot the old
> kernel. So:
>
> 1. Anybody knows what the blinking LEDs mean?
>
> 2. I verified the kernel configuration with respect to processor
> type (AMD Athlon/K7) and file systems (ext2 and ext3 compiled into
> kernel). What other options could prevent from booting at that
> early stage?
>

--
Remove xxx, yyy and zzz from the mail address below:
[email]xxxlarand@yyytelia.zzzc[/email]om
to get the correct email to me. ;)

[Nico Kadel-Garcia]

Lars-Göran Andersson wrote:

> I have a recommendation to save the settings in menuconfig at a separate
> file before exiting menuconfig.
>
> You can then copy this file to another kernel-directory or just keep it to
> reload it when you are regenerating the kernel. Then you are sure using the
> same setting from kernel to kernel.
>
> /Lars-Göran
>
> [email]frankh@terra.com.br[/email] wrote:

After running "make menuconfig" or "make xconfig", I tond to run "make
oldconfig" first, and save the results of *that* .config elsewhere as
being easier to compare to other kernel config files.