recompling a kernel--kernel panic!

wiwengweng · #1 20th February 2009, 09:31 AM

i got a time consuming job~~!And it seems to be wired~
i installed fedora 8 (2.6.18.1 version)from my DVD rom ,and it goes well .some days ago ,i tried to complie 2.6.18.*,and everything went well,but things differ as i try to complie 2.6.19.* or 2.6.23.*-----nothing but "kernel panic!!!"
i wonder what's going on,and as i boot the machine,the message goes:
*********************
creating root device
mounting root filesystem
mount: could not find fileysstem ‘/dev/root’
setting up other filesystem
setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys,mounting internal default
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
switching to new root and run init
switchroot: mount failed: No such file or directory
kernel panic********

what's up??? one thing i have to mention,is that ,my hard-disk is a SATA disk.As there is no panic in 2.6.18.*version,so i suppose the 2.6.23.*goes well too~~~~however,it doesn't ~~

any idea???pl help

aleph · #2 20th February 2009, 09:50 AM

Did you create the initial ramdisk after you compiled a new kernel? Mkinitrd?

wiwengweng · #3 24th February 2009, 01:55 AM

is it necessary to mkdir ??
it seems of no importance when i read the installation pages from the web~~~so i never do that~~thanks ,i will try first and then report it later~!!

wiwengweng · #4 27th February 2009, 03:16 PM

it seemed not to work at all .as i know ,it doesn't need to "mkdir" when compling a 2.6.24 version,i am still troubled by this issue ~~~~help~!!

sideways · #5 27th February 2009, 03:32 PM

hard disk dev nodes changed from 2.6.18 to 2.6.19, so that /dev/hdx is no longer used.

Check in grub.conf and /etc/fstab that there are no references to /dev/hda

wiwengweng · #6 28th February 2009, 12:42 AM

jif i have to delete the referrence about /dev/hda ,what should i do to replace this mark ??
this is my grub :

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,7)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda
default=1
timeout=5
splashimage=(hd0,7)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.24)
root (hd0,7)
kernel /vmlinuz-2.6.24 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.24.img
title Fedora Core (2.6.18-1.2798.fc6)
root (hd0,7)
kernel /vmlinuz-2.6.18-1.2798.fc6 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.18-1.2798.fc6.img
title other
rootnoverify (hd0,0)
chainloader +1

i cannot boot the new 2.6.24,what changes should i make??PL~!!!leave some steps to rescue my 2.6.24~

sideways · #7 28th February 2009, 05:10 AM

Can you boot into old 2.6.18 kernel?

That's an old fc6 kernel, if you want to update the kernel and nothing is available in the repos then download an rpm and install that, otherwise you'll probably miss a whole load of dependencies. A lot changed from fc6. When you compiled you own kernel did you build an rpm to install it or type 'make install'. If you built an rpm using 'make rpm' then installed that the initrd is not installed and you must do it yourself manually using mkinitrd. Check /boot, is there a matching initrd for your 2.6.24 kernel?

wiwengweng · #8 28th February 2009, 07:24 AM

Quote:

Originally Posted by sideways

Can you boot into old 2.6.18 kernel?

That's an old fc6 kernel, if you want to update the kernel and nothing is available in the repos then download an rpm and install that, otherwise you'll probably miss a whole load of dependencies. A lot changed from fc6. When you compiled you own kernel did you build an rpm to install it or type 'make install'. If you built an rpm using 'make rpm' then installed that the initrd is not installed and you must do it yourself manually using mkinitrd. Check /boot, is there a matching initrd for your 2.6.24 kernel?

yes,i did anything i can to compile it .make menuconfig,make ,make modules_install,make install ~~~~ i do have 2.6.24.img,vmlinuz-2.6.24 and system.map-2.6.24 in /boot. so i think no need to mkdir~~~and so it failed though i did "mkdir"
so what is wrong??some one said it due to the differences between 2.6.18 and 2.6.24,but,what is the differences~~??anyone tell me ~??

sideways · #9 28th February 2009, 07:31 AM

is it 2.6.24.img or initrd-2.6.24.img?

A lot changed between 2.6.18 and 2.6.24, that's why it's safer to download a prebuilt fedora rpm and install using rpm or yum, that way you''ll see if there are dependency conflicts.

You seem to have a system which has been updated since FC6, is there any reason why you can't do a fresh install of F10, or why you have to install a 2.6.24 kernel on the old system?

(F8 repos are still available, though getting slower to access, you could just try a yum update)

stevea · #10 28th February 2009, 07:47 AM

Go back to post #2

it's mkinitrd NOT mkdir

you must do this

wiwengweng · #11 28th February 2009, 08:00 AM

Quote:

Originally Posted by sideways

is it 2.6.24.img or initrd-2.6.24.img?

A lot changed between 2.6.18 and 2.6.24, that's why it's safer to download a prebuilt fedora rpm and install using rpm or yum, that way you''ll see if there are dependency conflicts.

You seem to have a system which has been updated since FC6, is there any reason why you can't do a fresh install of F10, or why you have to install a 2.6.24 kernel on the old system?

(F8 repos are still available, though getting slower to access, you could just try a yum update)

i was just curious about why it failed to boot~~.yes i just downloaded the 2.6.24.tar.ba2 from kernel.org ,and complie it in my Fc8 ,of 2.6.18 version~~~i was angry that the 2.6.24 version had just shut me out of the door,on the other hand,poeple do complie this version successfully ~~which make me upset~~
so ,i do hope to work it out~!

wiwengweng · #12 28th February 2009, 08:00 AM

Quote:

Originally Posted by sideways

is it 2.6.24.img or initrd-2.6.24.img?

A lot changed between 2.6.18 and 2.6.24, that's why it's safer to download a prebuilt fedora rpm and install using rpm or yum, that way you''ll see if there are dependency conflicts.

You seem to have a system which has been updated since FC6, is there any reason why you can't do a fresh install of F10, or why you have to install a 2.6.24 kernel on the old system?

(F8 repos are still available, though getting slower to access, you could just try a yum update)

i was just curious about why it failed to boot~~.yes i just downloaded the 2.6.24.tar.bz2 from kernel.org ,and complie it in my Fc8 ,of 2.6.18 version~~~i was angry that the 2.6.24 version had just shut me out of the door,on the other hand,poeple do complie this version successfully ~~which make me upset~~
so ,i do hope to work it out~!

Transformer · #13 28th June 2009, 07:33 AM

Hi

I have a big problem at my hand , atleast for me.

Yesterday I was trying to install the broadcom-wl package for my F9 for wireless network.

In due process I got errors of kernel updates required.

So , I did that but I accidentally installed two new kernels onto my system .

Then I had 3 kernels. Out of which two could access only the text mode, they could not load the screen .

So I logged in using the 3rd kernel and tried removing the other two as this third kernel was now not recognising the wireless card which before the installation of broadcom-wl package was recognised by the OS .

I out of my clumsiness accidentally removed the best working kernel ie the 3rd kernel . Now the next two work only in text mode and I need the graphical mode for some urgent work .

I didnt take note of which I was removing

. I removed by the "yum" .

Please help me out . I m in desperate need.