Kernel reboot problem

Kernel reboot problem

[J.S.S.]

What in the world am I doing wrong?
Whenever I try and compile a kernel, my computer reboots after the message:

Loading Linux.......................

Here's what I do, tell me if it's wrong:

-Download kernel into home dir
-Unpack
-Rename and make symbolic link "linux"
-cd linux
-make mrproper
-make menuconfig
-make dep && make clean && make bzImage && make modules && make
modules_install
-cp bzImage to /boot/vmlinuz-2.4.17
-cp System.map /boot/System.map-2.4.17
-cd /boot
-create symbolic link to System.map -> System.map-2.4.17
-edit lilo.conf:

===========================
prompt
timeout=50
default=linux
boot=/dev/hda
map=boot/map
install=/boot/boot.b
message=/boot/message
lba32

image=/boot/vmlinuz-2.4.7-10
	label=linux
	initrd=/boot/initrd-2.4.7-10.img
	read-only
	root=/dev/hda5

#Add this part for new kernel
image=/boot/vmlinuz-2.4.17
	label=Linux-2.4.17
	read-only
	root=/dev/hda5
===========================
-Run /sbin/lilo

Lilo installs fine without any complaints and EVERYTIME I reboot
and choose the new kernel the computer reboots after the "Loading
Linux..................."
message. It never gets to the "Uncompressing" part of the boot message.
It's obviously got to
be something i'm doing wrong.  If redhat and slackware can get their kernels
to load, then there's no reason
I shouldn't be able to do my own.  Here's my setup:

Pentium 233
Intel Chipset
192 megs RAM
Maxtor 10g ATA/66

Some help would be much, much appreciated.  I've followed all the examples
and tried this dozens of times with no success to date.  I've downloaded
2.4.16 and it did the same thing.  I've tried putting the source and
unpacking it in the /usr/src directory. I've tried using initrd and
modifying lilo to reflect it.  The kernel ALWAYS compiles without any error
codes at the end and none of this seems to matter because in the end it just
reboots and reboots, etc...

Re: Kernel reboot problem

[Todor Todorov]

Hi,

>-cp bzImage to /boot/vmlinuz-2.4.17
>

do you really mena bzImage or arch/i386/bootbzImage ? And it would be 
very helpful if you can provide the compile options. Without them or 
only with the information from your mail is hard to tell what is going 
wrong. Your compile settings are stored in the $LINUX_SRC/.config file. 
The way you did it though is correct. You culd skip mproper on a newly 
untarred kernel and the make clean after the first config but it doesn't 
hurt if you do it. The failure is in your .config probably.

Greets,
        Todor

Re: Kernel reboot problem

[Drew P. Vogel]

What does the initrd= line do, and how does initrd-2.4.17-10.img get in
/boot?

--Drew Vogel

On Wed, 20 Feb 2002, J.S.S. wrote:

>What in the world am I doing wrong?
>Whenever I try and compile a kernel, my computer reboots after the message:
>
>Loading Linux.......................
>
>Here's what I do, tell me if it's wrong:
>
>-Download kernel into home dir
>-Unpack
>-Rename and make symbolic link "linux"
>-cd linux
>-make mrproper
>-make menuconfig
>-make dep && make clean && make bzImage && make modules && make
>modules_install
>-cp bzImage to /boot/vmlinuz-2.4.17
>-cp System.map /boot/System.map-2.4.17
>-cd /boot
>-create symbolic link to System.map -> System.map-2.4.17
>-edit lilo.conf:
>
>===========================
>prompt
>timeout=50
>default=linux
>boot=/dev/hda
>map=boot/map
>install=/boot/boot.b
>message=/boot/message
>lba32
>
>image=/boot/vmlinuz-2.4.7-10
>	label=linux
>	initrd=/boot/initrd-2.4.7-10.img
>	read-only
>	root=/dev/hda5
>
>#Add this part for new kernel
>image=/boot/vmlinuz-2.4.17
>	label=Linux-2.4.17
>	read-only
>	root=/dev/hda5
>===========================
>-Run /sbin/lilo
>
>Lilo installs fine without any complaints and EVERYTIME I reboot
>and choose the new kernel the computer reboots after the "Loading
>Linux..................."
>message. It never gets to the "Uncompressing" part of the boot message.
>It's obviously got to
>be something i'm doing wrong.  If redhat and slackware can get their kernels
>to load, then there's no reason
>I shouldn't be able to do my own.  Here's my setup:
>
>Pentium 233
>Intel Chipset
>192 megs RAM
>Maxtor 10g ATA/66
>
>Some help would be much, much appreciated.  I've followed all the examples
>and tried this dozens of times with no success to date.  I've downloaded
>2.4.16 and it did the same thing.  I've tried putting the source and
>unpacking it in the /usr/src directory. I've tried using initrd and
>modifying lilo to reflect it.  The kernel ALWAYS compiles without any error
>codes at the end and none of this seems to matter because in the end it just
>reboots and reboots, etc...
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>

Re: Kernel reboot problem

[Todor Todorov]

Drew P. Vogel wrote:

>What does the initrd= line do, and how does initrd-2.4.17-10.img get in
>/boot?
>
It's a compressed file containing the compiled modules which is needed 
if a driver should be initialized before mounting the root file system, 
eg a driver for the root system. As it is in the 2.4.7 image section it 
refers only to the 2.4.7 kernel and not 2.4.18 (or whatever he tries to 
compile).

And speaking of it - J.S.S., did you take the options from the Red Hat's 
stock kernel as an example to choose your options? (From your mail I 
recon that this is one of your first attempts to compile an own kernel, 
am I correct?) If you did that, you rpobably included the fs driver for 
your root system as a module and not hardlinked in the kernel - just as 
Red Hat does? In such case you would need either to provide an initrd 
image too (`man initrd`), or recompile your kernel with the driver for 
the root filesystem ( ext2 or/and ext3 or reiserfs, don't know how you 
formated your linux partition(s) ) with <y> as option for it instead of 
<m>.....

Stupid me for not suggesting to check that in the first mail :-/

Hope you will locate the error quickliy.

Cheers 

-- 

Todor Todorov           <ttodorov@web.de>
Networkadministration   <todor.todorov@skr-skr.de>
SKR GmbH & Co. KG       http://www.skr-skr.de

-----------------
"Only two things are infinite, the universe and the
 human stupidity, and I'm not sure about the former"
                               - Einstein

Re: Kernel reboot problem

[Drew P. Vogel]

Well, not having the proper fs drivers compiled in would not cause the
machine to reboot at that point. The lack of an initrd-2.4.17-10.img file
probably would though.

--Drew Vogel

On Thu, 7 Feb 2002, Todor Todorov wrote:

>Drew P. Vogel wrote:
>
>>What does the initrd= line do, and how does initrd-2.4.17-10.img get in
>>/boot?
>>
>It's a compressed file containing the compiled modules which is needed
>if a driver should be initialized before mounting the root file system,
>eg a driver for the root system. As it is in the 2.4.7 image section it
>refers only to the 2.4.7 kernel and not 2.4.18 (or whatever he tries to
>compile).
>
>And speaking of it - J.S.S., did you take the options from the Red Hat's
>stock kernel as an example to choose your options? (From your mail I
>recon that this is one of your first attempts to compile an own kernel,
>am I correct?) If you did that, you rpobably included the fs driver for
>your root system as a module and not hardlinked in the kernel - just as
>Red Hat does? In such case you would need either to provide an initrd
>image too (`man initrd`), or recompile your kernel with the driver for
>the root filesystem ( ext2 or/and ext3 or reiserfs, don't know how you
>formated your linux partition(s) ) with <y> as option for it instead of
><m>.....
>
>Stupid me for not suggesting to check that in the first mail :-/
>
>Hope you will locate the error quickliy.
>
>Cheers
>
>--
>
>Todor Todorov           <ttodorov@web.de>
>Networkadministration   <todor.todorov@skr-skr.de>
>SKR GmbH & Co. KG       http://www.skr-skr.de
>
>-----------------
>"Only two things are infinite, the universe and the
> human stupidity, and I'm not sure about the former"
>                               - Einstein
>
>
>
>

Re: Kernel reboot problem

[Drew P. Vogel]

Forgive me. It is early :]

--Drew Vogel

On Thu, 7 Feb 2002, Drew P. Vogel wrote:

>Well, not having the proper fs drivers compiled in would not cause the
>machine to reboot at that point. The lack of an initrd-2.4.17-10.img file
>probably would though.
>
>--Drew Vogel
>
>On Thu, 7 Feb 2002, Todor Todorov wrote:
>
>>Drew P. Vogel wrote:
>>
>>>What does the initrd= line do, and how does initrd-2.4.17-10.img get in
>>>/boot?
>>>
>>It's a compressed file containing the compiled modules which is needed
>>if a driver should be initialized before mounting the root file system,
>>eg a driver for the root system. As it is in the 2.4.7 image section it
>>refers only to the 2.4.7 kernel and not 2.4.18 (or whatever he tries to
>>compile).
>>
>>And speaking of it - J.S.S., did you take the options from the Red Hat's
>>stock kernel as an example to choose your options? (From your mail I
>>recon that this is one of your first attempts to compile an own kernel,
>>am I correct?) If you did that, you rpobably included the fs driver for
>>your root system as a module and not hardlinked in the kernel - just as
>>Red Hat does? In such case you would need either to provide an initrd
>>image too (`man initrd`), or recompile your kernel with the driver for
>>the root filesystem ( ext2 or/and ext3 or reiserfs, don't know how you
>>formated your linux partition(s) ) with <y> as option for it instead of
>><m>.....
>>
>>Stupid me for not suggesting to check that in the first mail :-/
>>
>>Hope you will locate the error quickliy.
>>
>>Cheers
>>
>>--
>>
>>Todor Todorov           <ttodorov@web.de>
>>Networkadministration   <todor.todorov@skr-skr.de>
>>SKR GmbH & Co. KG       http://www.skr-skr.de
>>
>>-----------------
>>"Only two things are infinite, the universe and the
>> human stupidity, and I'm not sure about the former"
>>                               - Einstein
>>
>>
>>
>>
>
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>

RE: Kernel reboot problem [solved]

[J.S.S.]

Well, it's a beautiful thing when something finally works that you've been
struggling with for a while.
I loaded the Redhat default .config for i586 and modified it taking out
things I knew I didn't want, especially all the extra modules they select.
Anyway, the install went great - although it didn't work when I tried to use
the initrd image for some reason.  But, I took that line out of lilo.conf,
ran lilo, rebooted and it ran through like it should have.  Now to play
around with the .config file to streamline it more to my machine
configuration.  Thanks everyone for the help! You guys are great.

					JSS

-----Original Message-----
From: Drew P. Vogel [mailto:dvogel@intercarve.net]
Sent: Thursday, February 07, 2002 7:42 AM
To: Todor Todorov
Cc: J.S.S; Linux Kernel Mailing List
Subject: Re: Kernel reboot problem


Forgive me. It is early :]

--Drew Vogel

On Thu, 7 Feb 2002, Drew P. Vogel wrote:

>Well, not having the proper fs drivers compiled in would not cause the
>machine to reboot at that point. The lack of an initrd-2.4.17-10.img file
>probably would though.
>
>--Drew Vogel
>
>On Thu, 7 Feb 2002, Todor Todorov wrote:
>
>>Drew P. Vogel wrote:
>>
>>>What does the initrd= line do, and how does initrd-2.4.17-10.img get in
>>>/boot?
>>>
>>It's a compressed file containing the compiled modules which is needed
>>if a driver should be initialized before mounting the root file system,
>>eg a driver for the root system. As it is in the 2.4.7 image section it
>>refers only to the 2.4.7 kernel and not 2.4.18 (or whatever he tries to
>>compile).
>>
>>And speaking of it - J.S.S., did you take the options from the Red Hat's
>>stock kernel as an example to choose your options? (From your mail I
>>recon that this is one of your first attempts to compile an own kernel,
>>am I correct?) If you did that, you rpobably included the fs driver for
>>your root system as a module and not hardlinked in the kernel - just as
>>Red Hat does? In such case you would need either to provide an initrd
>>image too (`man initrd`), or recompile your kernel with the driver for
>>the root filesystem ( ext2 or/and ext3 or reiserfs, don't know how you
>>formated your linux partition(s) ) with <y> as option for it instead of
>><m>.....
>>
>>Stupid me for not suggesting to check that in the first mail :-/
>>
>>Hope you will locate the error quickliy.
>>
>>Cheers
>>
>>--
>>
>>Todor Todorov           <ttodorov@web.de>
>>Networkadministration   <todor.todorov@skr-skr.de>
>>SKR GmbH & Co. KG       http://www.skr-skr.de
>>
>>-----------------
>>"Only two things are infinite, the universe and the
>> human stupidity, and I'm not sure about the former"
>>                               - Einstein
>>
>>
>>
>>
>
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>

RE: Kernel reboot problem

[J.S.S.]

Well, i'm going to try this again (and again as long as it takes), but this
time I loaded the .config file from Redhat and am going to take out the
stuff I don't want.  Actually I should have done this from the beginning.
However, I can already see some of the things that I should have enabled
just from looking at their configuration.  I'll keep you posted on the
progress.

-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of Drew P. Vogel
Sent: Thursday, February 07, 2002 7:13 AM
To: Todor Todorov
Cc: J.S.S; Linux Kernel Mailing List
Subject: Re: Kernel reboot problem


Well, not having the proper fs drivers compiled in would not cause the
machine to reboot at that point. The lack of an initrd-2.4.17-10.img file
probably would though.

--Drew Vogel

On Thu, 7 Feb 2002, Todor Todorov wrote:

>Drew P. Vogel wrote:
>
>>What does the initrd= line do, and how does initrd-2.4.17-10.img get in
>>/boot?
>>
>It's a compressed file containing the compiled modules which is needed
>if a driver should be initialized before mounting the root file system,
>eg a driver for the root system. As it is in the 2.4.7 image section it
>refers only to the 2.4.7 kernel and not 2.4.18 (or whatever he tries to
>compile).
>
>And speaking of it - J.S.S., did you take the options from the Red Hat's
>stock kernel as an example to choose your options? (From your mail I
>recon that this is one of your first attempts to compile an own kernel,
>am I correct?) If you did that, you rpobably included the fs driver for
>your root system as a module and not hardlinked in the kernel - just as
>Red Hat does? In such case you would need either to provide an initrd
>image too (`man initrd`), or recompile your kernel with the driver for
>the root filesystem ( ext2 or/and ext3 or reiserfs, don't know how you
>formated your linux partition(s) ) with <y> as option for it instead of
><m>.....
>
>Stupid me for not suggesting to check that in the first mail :-/
>
>Hope you will locate the error quickliy.
>
>Cheers
>
>--
>
>Todor Todorov           <ttodorov@web.de>
>Networkadministration   <todor.todorov@skr-skr.de>
>SKR GmbH & Co. KG       http://www.skr-skr.de
>
>-----------------
>"Only two things are infinite, the universe and the
> human stupidity, and I'm not sure about the former"
>                               - Einstein
>
>
>
>



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/