2002-03-22 16:21:10

by Abdij Bhat

[permalink] [raw]
Subject: Kernel Upgrade Hangs!

Hi,
I am trying to build the 2.4.17 Kernel and upgrade my existing 2.4.7-10 Red
Hat Linux System. Here is the procedure I followed ( based on Red Hat
Documentation on the same ):

1. tar -xvzf linux-2.4.17.tar.gz
2. cd linux
3. make mkproper
4. make menuconfig
5.make dep
6. make clean
7. make bzImage
8. make modules
9. make modules_install
10. cp /usr/src/linux-2.4.17/arch/i386/boot/bzImage /boot/vmlinuz-2.4.17
11. cp /usr/src/linux-2.4.17/System.map /boot/System.map-2.4.17
12. cd /boot rm System.map ln -s System.map-2.4.17 System.map
13. mkinitrd /boot/initrd-2.4.17.img 2.4.17
14. Modify the /etc/lilo.conf to add
image=/boot/vmlinuz-2.4.17
label=linux-Mine
root=/dev/hda1
initrd=/boot/initrd-2.4.17
read-only

Now when i reboot and select the linux-Mine option the screen displays
Loading vmlinuz-2.4.7
Uncompressing Linux... Ok, booting the kernel

and then HANGS!!!!!!

What might be the problem. I have followed the instruction to the T. I
tried without the initrd option too. I have enabled the RAM diak
option/disabled it....

Please help me out on the issue.

Thanks and Regards,
Abdij


2002-03-22 16:32:41

by Masoud Sharbiani

[permalink] [raw]
Subject: Re: Kernel Upgrade Hangs!

Abdij Bhat wrote:

>Hi,
> I am trying to build the 2.4.17 Kernel and upgrade my existing 2.4.7-10 Red
>Hat Linux System. Here is the procedure I followed ( based on Red Hat
>Documentation on the same ):
>
>1. tar -xvzf linux-2.4.17.tar.gz
>2. cd linux
>3. make mkproper
>4. make menuconfig
>5.make dep
>6. make clean
>7. make bzImage
>8. make modules
>9. make modules_install
>10. cp /usr/src/linux-2.4.17/arch/i386/boot/bzImage /boot/vmlinuz-2.4.17
>11. cp /usr/src/linux-2.4.17/System.map /boot/System.map-2.4.17
>12. cd /boot rm System.map ln -s System.map-2.4.17 System.map
>13. mkinitrd /boot/initrd-2.4.17.img 2.4.17
>14. Modify the /etc/lilo.conf to add
> image=/boot/vmlinuz-2.4.17
> label=linux-Mine
> root=/dev/hda1
> initrd=/boot/initrd-2.4.17
> read-only
>
> Now when i reboot and select the linux-Mine option the screen displays
> Loading vmlinuz-2.4.7
> Uncompressing Linux... Ok, booting the kernel
>
> and then HANGS!!!!!!
>
> What might be the problem. I have followed the instruction to the T. I
>tried without the initrd option too. I have enabled the RAM diak
>option/disabled it....
>
> Please help me out on the issue.
>
>Thanks and Regards,
>Abdij
>
Have you tried checking what CPU type is configured on your kernel? it
should be the same as your system's cpu.
Masoud


2002-03-22 17:03:10

by Tony Hoyle

[permalink] [raw]
Subject: Re: Kernel Upgrade Hangs!

On Fri, 22 Mar 2002 16:22:32 +0000 (UTC), Abdij Bhat
<[email protected]> wrote:

>>
> Now when i reboot and select the linux-Mine option the screen displays
> Loading vmlinuz-2.4.7
> Uncompressing Linux... Ok, booting the kernel

You aren't booting 2.4.17, so it's not the kernel that's the problem.
There's probably a way on your distro to switch kernels (it used to be
/etc/lilo.conf with all the modern GUI stuff it could be anywhere).

Tony

2002-03-22 17:57:47

by walt

[permalink] [raw]
Subject: Re: Kernel Upgrade Hangs!

Abdij Bhat wrote:

> Hi,
> I am trying to build the 2.4.17 Kernel and upgrade my existing 2.4.7-10 Red
> Hat Linux System. Here is the procedure I followed ( based on Red Hat
> Documentation on the same ):
>
> 1. tar -xvzf linux-2.4.17.tar.gz
> 2. cd linux
> 3. make mkproper
> 4. make menuconfig
> 5.make dep
> 6. make clean
> 7. make bzImage
> 8. make modules
> 9. make modules_install
> 10. cp /usr/src/linux-2.4.17/arch/i386/boot/bzImage /boot/vmlinuz-2.4.17
> 11. cp /usr/src/linux-2.4.17/System.map /boot/System.map-2.4.17
> 12. cd /boot rm System.map ln -s System.map-2.4.17 System.map
> 13. mkinitrd /boot/initrd-2.4.17.img 2.4.17
> 14. Modify the /etc/lilo.conf to add
> image=/boot/vmlinuz-2.4.17
> label=linux-Mine
> root=/dev/hda1
> initrd=/boot/initrd-2.4.17
> read-only
>
> Now when i reboot and select the linux-Mine option the screen displays
> Loading vmlinuz-2.4.7
> Uncompressing Linux... Ok, booting the kernel
>
> and then HANGS!!!!!!
>
> What might be the problem. I have followed the instruction to the T. I
> tried without the initrd option too. I have enabled the RAM diak
> option/disabled it....
>
> Please help me out on the issue.
>
> Thanks and Regards,
> Abdij
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/

You must run /sbin/lilo so lilo knows the "physical" location on the disk of
the kernel image

2002-03-22 18:24:19

by craig.howard

[permalink] [raw]
Subject: Re: Kernel Upgrade Hangs!

On (22/03/02), Masoud Sharbiani wrote:
> Abdij Bhat wrote:
>
> >Hi,
> >I am trying to build the 2.4.17 Kernel and upgrade my existing 2.4.7-10 Red
> >Hat Linux System. Here is the procedure I followed ( based on Red Hat
> >Documentation on the same ):
> >
[snip]
> >
> >Now when i reboot and select the linux-Mine option the screen displays
> > Loading vmlinuz-2.4.7
> > Uncompressing Linux... Ok, booting the kernel
> >
> >and then HANGS!!!!!!
> >
> >What might be the problem. I have followed the instruction to the T. I
> >tried without the initrd option too. I have enabled the RAM diak
> >option/disabled it....
> >
> >Please help me out on the issue.
> >
> >Thanks and Regards,
> >Abdij
> >
> Have you tried checking what CPU type is configured on your kernel? it
> should be the same as your system's cpu.
> Masoud
>

I'm having the same problem on an old Cyrix PR200+. It works fine with the
2.2 kernel that comes with Slackware 8, but _nothing_ else. I've tried the
2.4 that comes with Slackware, compiling my own 2.2, 2.4 but it always
hangs. I've tried with both 386 and Cyrix 686 kernels, but no dice.

I used _exactly_ the same procedure that I use to upgrade my two firewalls
and desktop system, so I know my process is correct.

The only quirk to my setup is that I've got /boot mounted on an old 120MB
drive as I can't boot off the 40GB because of the old BIOS.

One last thing, one of the kernels, doesn't just hang, it reboots the whole
system. I can't remember which kernel did this.
--


Craig Howard
2B Computer Science -- University of Waterloo
[email protected]