[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: Kernel Panic - no init found...
- From: bala chandar <mbchandar gmail com>
- To: General Red Hat Linux discussion list <redhat-list redhat com>
- Subject: Re: Kernel Panic - no init found...
- Date: Tue, 7 Dec 2004 20:46:43 +0530
I think you need not install lilo or grub. boot the system with the
previsous kernel and then configure the grub and specify the root path
correctly in that.
On Tue, 7 Dec 2004 15:14:32 +0000 (GMT), Anish Mathew
<nedumannilanish yahoo co uk> wrote:
> hi bob
> u need to create a ram disk image for ur new kernel.
> if ur kernel version is 2.6.0
> create the image using
> mkinitrd /boot/initrd.2.6.0.img 2.6.0
>
> if ur using lilo as boot loader edit /etc/lilo.con and add
> initrd=/boot/initrd.2.6.0.img for ur new kernel
> save and exit
> run lilo -v to reinstall lilo.
>
> anish.
>
>
>
> Bob Metelsky <bobmetelsky comcast net> wrote:
> Im having a difficult time implementing a new kernel
>
> I do
> bzip2 -dc linux-2.6.0.tar.bz2 | tar xvf -
> make menuconfig
> make bzImage
> make modules
> make modules_install
> make install
>
> Researching my error I found this
> http://www.redhat.com/archives/fedora-list/2004-November/msg03120.html
>
> "
> 2. Navigate through the menus: "Device Drivers -> Block Devices"
> 3. Enable "RAM disk support", and "Initial RAM disk (initrd) support"
> 4. Enable any other kernel stuff you want/need.
> 5. Run "make", then (as root) "make modules_install", and "make install"
>
> The "make install" will create your initrd and add the appropriate
> stanza in your /boot/grub/grub.conf.
> make install
> "
> I do not run the original "make" but rather make bzImage
>
> This does exactly that
> the new kernel and image are copied to /boot
> grub is "automagically" edited
> but... I still end up with the "kernel panic no init found - Try
> passing init= to kernel"
>
> Any Ideas what i may be doing wrong?
>
> Thanks
> Bob
>
> --
> "Oracle error messages being what they are, do not
> highlight the correct cause of fault, but will identify
> some other error located close to where the real fault lies."
>
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request redhat com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>
>
> ---------------------------------
> Win a castle for NYE with your mates and Yahoo! Messenger
>
>
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request redhat com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>
--
bala> balachandar muruganantham
bala> lynx http://chandar.blogspot.com
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]