[deuce868]

I built a new 2.6.6 kernel, but I am having a kernel panic on booting to it. Below is all the info I can think of. I copied most of the info from the existing kernel I am using right now, which is the Debian package for 2.6.6

If you have any ideas I would appreciate it.

__________________________________________________________________________
boot error:
NET: Registered Protocol Family 2
IP: routeing cache hash table 8192 buckets, 64kbytes
NET: Registered Protocal Family 8
NET: Registered Protocal Family 20
speedstep centrino: found “Intel......max frequency 1600000”
Kernel Panic: VFS: Unable to mount fs on hda4

TechieIBM:/usr/src/kernel-source-2.6.6# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/hda4 13333632 1614724 11718908 13% /
tmpfs 388364 0 388364 0% /dev/shm
/dev/hda3 91619 14312 72419 17% /boot


/boot folder
-rw-r--r-- 1 root root 548511 Apr 14 13:39 System.map-2.4.25-1-386
-rw-r--r-- 1 root root 802220 May 12 07:30 System.map-2.6.6-1-686
-rw-r--r-- 1 root root 880925 Jun 3 07:58 System.map-2.6.6-R50
-rw-r--r-- 1 root root 1708097 Jun 3 07:58 bzimage-2.6.6-R50
-rw-r--r-- 1 root root 44109 Apr 14 05:36 config-2.4.25-1-386
-rw-r--r-- 1 root root 52718 May 12 00:45 config-2.6.6-1-686
drwxr-xr-x 2 root root 1024 Jun 2 07:58 grub
-rw-r--r-- 1 root root 3825664 Jun 1 04:26 initrd.img-2.4.25-1-386
-rw-r--r-- 1 root root 4583424 Jun 2 07:57 initrd.img-2.6.6-1-686
drwxr-xr-x 2 root root 12288 Jun 1 04:23 lost+found
-rw-r--r-- 1 root root 808860 Apr 14 13:39 vmlinuz-2.4.25-1-386
-rw-r--r-- 1 root root 1129935 May 12 07:30 vmlinuz-2.6.6-1-686


menu.lst – (top is custom, bottom is the current kernel I boot into right now)

title Debian 2.6.6 R50 Custom
root (hd0,2)
kernel /bzimage-2.6.6-R50 root=/dev/hda4 ro
savedefault
boot

title Debian GNU/Linux, kernel 2.6.6-1-686
root (hd0,2)
kernel /vmlinuz-2.6.6-1-686 root=/dev/hda4 ro
initrd /initrd.img-2.6.6-1-686
savedefault
boot


TechieIBM:/usr/src/kernel-source-2.6.6# fdisk -l

Disk /dev/hda: 40.0 GB, 40007761920 bytes
16 heads, 63 sectors/track, 77520 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 48765 24577528+ 7 HPFS/NTFS
/dev/hda2 48766 50850 1050840 82 Linux swap
/dev/hda3 50851 51044 97776 83 Linux
/dev/hda4 51045 77520 13343904 83 Linux

[tsunam]

I assume since you have 2.6.6 you are running debian sid or the really really experimental debian client.

did you download the kernel from kernel.org and build it from there. Or did you grab it from debian's tree? if so debian makes it really nice to update and install a new kernel because they have preconfigured isntalls and all you have to do is modify your grub and lilo packages after it installs. (rereading it appears you did get it from the tree)

hmm is it possible that somehow you said yes to it rewritting your fstab file along the way? I believe the last time i had that particular kernel panic that's exactly what happened to me.

[deuce868]

I got the kernel-source package from debian. I got a custom config from the linux-thinkpad mailing list. A guy has my exact laptop and had a custom config for it. I checked and all the filesystems and such are enabled in the kernel.

I don't think it is an fstab problem because I can load up the kernel package from debian I am running on now. I am already running on 2.6.6 from the debian package. I need to do a custom kernel though to get alsa and my wireless working on this laptop.

Thanks for the ideas though.

[tsunam]

which wireless card is it? alsa is easy to configure if you want to do it though. I can walk you thru the process of setting that up. Which laptop is it?

[deuce868]

It is a IBM thinkpad R50. I was working on alsa, but from what I found I was missing some kernel modules (thus the custom kernel)

The wireless is the built in Centrino. In order to build the ipw2100 code for it you need a working kernel source directory.

It sucks because since this other guy has the custom kernel all working, I know if I can figure out what is causing me the error I think I can get it from there. grrr.... well playing on the techie side of things is never easy.

[tsunam]

initrd /initrd.img-2.6.6-1-686 <--why is that on the old kernel config and not the new? just for curriosity

Also you might just want to try a slightly different format for the config file...can't hurt can it?

try..

title=Debian 2.6.6 R50 Custom
root (hd0,2)
kernel (hd0,2)/bzimage-2.6.6-R50 root=/dev/hda4 ro

I'm not exactly sure about the ro...but that particular set is how i have it boot up my kernel (minus the ro)...slightly different format so it might work...weirder things have been known to happen.

[deuce868]

thanks, but no go on that.

Do you know any way to see what sort of file system the system is running. fdisk just shows Linux, but I want to make sure to see if it is EXT3, XFS, etc...

[tsunam]

cfdisk will show you that . other then that i'm not sure.

[deuce868]

I got it working. I had XFS compiled as a loadable module. I had to actually compile it into the kernel.

Now that the new kernel is working alsaconf says:
modinfo: could not find module snd

this is my lsmod:
TechieIBM:/home/rharding# lsmod
Module Size Used by
snd_seq 47760 0
snd_seq_device 6536 1 snd_seq
radeon 111088 30
ipv6 223520 8
af_packet 16136 2
ohci1394 30916 0
hw_random 4308 0
evdev 7296 0
ext2 61032 1
rtc 9592 0
unix 21744 246

any idea where I should start on getting alsa going?

Thanks

[Whiteskin]

modprobe.d

It works just like the old modules.d did, however, this one applies to 2.6.* series kernels.