LinuxQuestions.org - Kernel Upgrade causing Kernel Panic

- Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)

- - Kernel Upgrade causing Kernel Panic (https://www.linuxquestions.org/questions/linux-software-2/kernel-upgrade-causing-kernel-panic-403178/)

Ok... another update I increased the size of RAMDISK support to 20 megs (everybody said 10, so I decided to go above and beyond just to make sure) and I checked the Root Plug option, it was already disabled. Any other ideas??

Thanks
DragonM15

Hmmm ... I would've thought my idea would fix it. Are you using LVM (Logical Volume Manager) on your partitions? If so, do you have support for it compiled into your kernel? What filesystem is on the root partition?

I am not sure what LVM is.... How do I tell? As for my root partition, it is reiserfs (I did spell that right I hope). and it is compiled directly, not a module. I made sure of that :)

DragonM15

Quote:

Originally Posted by DragonM15

I read this post, and recompiled my kernel and made sure that my filesystems were set as yes rather than modules. My filesystem is reiserfs. As far as the initrd, I read in /boot/README.initrd to run the command 'mkinitrd -c -k 2.6.13 -m reiserfs' and added initrd=/boot/initrd.gz to my lilo.conf. and I still got the same error. I looked on the page that paragn recommended... and I came across 2 things. "try increasing the size of RAMDISK support, if it's loading to RAMDISK to boot, you'll need that to be bigger than your kernel, and Disable root plug option (security options) if not needed" can I change RAMDISK size in Kernel? I am going to look around when I boot into it and find out. And I have read that the root plug is in the kernel config, so I am going to take a look. Ill let you know how things work out. This is just an update on how things are coming.

Thanks,
DragonM15

You were using mkinitrd incorrectly....

Code:

$Id: mkinitrd,v 1.201 2004/05/16 22:00:48 herbert Exp $



Usage: /usr/sbin/mkinitrd [OPTION]... <-o outfile> [version]



Options:

  -d confdir  Specify an alternative configuration directory.

  -k          Keep temporary directory used to make the image.

  -m command  Set the command to make an initrd image.

  -o outfile  Write to outfile.

  -r root    Override ROOT setting in mkinitrd.conf.



See mkinitrd(8) for further details.

You need to make an initrid.img file, you would use it as such:
#mkinitrd -o <image name> <kernel name>
You can get the name by what's in your modules dir: /lib/modules/
#mkinitrd -o initrid.img-2.6.15-1-amd64-k8 2.6.15-1-amd64-k8
That's just an example based off the image I'm using now. That file will be loaded into your boot directory and then you'll have to do update-grub again. It will automatically detect what initrid.img is used for what kernel, you CAN name the initrid.img anything you want I just name it like that for simplicity and orginization. Basicially initrid.img so I know what it is and then the appended -<image name> so I know which ones are which when I want to delete older kernels. I hope this makes sense.

Ok, so I am using 2.6.13 so would I do

Code:

mkinitrd -o initrd-2.6.13.img vmlinuz-2.6.13

vmlinuz-2.6.13 is the name of my kernel in '/boot' Is this correct?

thanks,
DragonM15

Quote:

Originally Posted by DragonM15

Ok, so I am using 2.6.13 so would I do

Code:

mkinitrd -o initrd-2.6.13.img vmlinuz-2.6.13

vmlinuz-2.6.13 is the name of my kernel in '/boot' Is this correct?

thanks,
DragonM15

vmlinuz is just the kernel image, you'd probably just use 2.6.13. vmlinuz is actually added by the program, for the same reason I used the initrd.img thing. try this though:

#mkinitrd -o initrd.img-2.6.13 2.6.13
#update-grub

That should finish it.

That should work, then reboot and enjoy!

Note: There's a reason for why I named it slightly off from what you did, if you want to know PM me, though I don't think it matters, just try and stay as close to the examples. I'm not sure if the update-grub actually looks for initrid.img in file names or not, but I'd just say make sure it's initrid.img and then add whatever to the end.

What is type of you disk SCSI or IDE

Quote:

Originally Posted by ivangetov

What is type of you disk SCSI or IDE

It's not a SCSI or IDE problem. This actually happens a lot with initrd images that aren't configured properly.

Okie dokie, Ill give it a try! But I have to ask, why havent I gotten this error when updating before??

DragonM15

Hey man, that worked great!! Thanks!!

DragonM15

=) Glad to help mate, I actually had to fix that through google myself. =P

Alright, that is all fine and dandy, but now if I try to go to 2.6.15, I get the same error as I was before, and I did the mkinitrd -o initrd.img-2.6.15 2.6.15 And umm.... I get that same stupid error as before.... and one more little problem.... in 2.6.13 when I boot up blackbox, or any other gui, when I try to open xterm, or any other terminal besides konsole, it opens for a split second, and then disappears.... however in 2.4.26 everything works fine..... and it boots up in a quarter the time as 2.6..... neways.... update.... Reason I want 2.6.15 is because it has an actual option in the config for my wireless... I dont have to go through the whole 50 step process.... Well, there is my update.... any ideas???

Thanks,
DragonM15

P.S. I will go through the config, and use the same config as 2.6.13 ... you can do that with make oldconfig correct? Or do I have to specify where the old config is.... seems I have 2.4.26, and 2.6.13 before 2.6.15?

Quote:

Originally Posted by DragonM15

I don't know, I just did the config from scratch mainly and just enabled most of the default support for things. Though I used gconfig (because xconfig or kconfig wouldn't work). And really the #mkinitrd -o initrd.img-2.6.15 2.6.15 should work but if you read my earlier post then you'd understand when I say what does the /lib/modules/2.6.15 folder say, what is it's exact name? Is it /lib/modules/2.6.15 or is it /lib/modules/2.6.15-1 or something?

btmiller had it.

make xconfig

added to block devices section. ram disk support. initrd support.