public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masoud Sharbiani <masouds@oeone.com>
To: Abdij Bhat <Abdij.Bhat@kshema.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Kernel Upgrade Hangs!
Date: Fri, 22 Mar 2002 11:32:20 -0500	[thread overview]
Message-ID: <3C9B5C94.9020200@oeone.com> (raw)
In-Reply-To: <91A7E7FABAF3D511824900B0D0F95D10136FA4@BHISHMA>

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



  reply	other threads:[~2002-03-22 16:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-22 16:11 Kernel Upgrade Hangs! Abdij Bhat
2002-03-22 16:32 ` Masoud Sharbiani [this message]
2002-03-22 18:19   ` craig.howard
2002-03-22 17:02 ` Tony Hoyle
2002-03-22 17:56 ` walt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3C9B5C94.9020200@oeone.com \
    --to=masouds@oeone.com \
    --cc=Abdij.Bhat@kshema.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox