Kernel panic after recompile in FC4

litlmary · 06-22-2005, 09:03 PM

I am trying to remedy the famous sound problem on my IBM Thinkpad 600E.

Basically the only viable solution that I can find here or on the web (there are a lot of useless ones out there to sort through) is to recompile my kernel to support the chip. The whole thing is strange. The kernel detects a cs4610/11 chip, the actual driver that other people's experience has determined to use is the alsa snd-cs4236+ driver, and the chip is really a cs4239. Nothing like a wild hardware issue to make a newbie like me want to give up on linux. Good thing I have a hard head.

I download the source for kernel 2.6.12 from kernel.org and compiled a fresh kernel, cleaning out a lot of the dead weight as I went (i.e. - my laptop doesn't have a touch screen or firewire or one of the other 200 zillion or so sound cards the kernel supports, etc. etc.).

At first I linked the sound driver directly into the kernel. When I tried to boot the new kernel, it got as far as the alsa driver and hung. I didn't know what to think, but I am a little suspicious of something that happened when I compiled the kernel. Ask me about it if you want to know.

So I tried again...

This time I compiled the kernel and loaded the driver as a module. Now I get this partway through the boot and it hangs, obviously before the filesystem gets mounted:

Code:

VFS: cannot open root device "LABEL=/" or unknown-block(0,0)

Please append a correct "root=" boot option

Kernel panic - not syncing: VFS: unable to mount root fs on unkown-block(0,0)

 <7>uhci_hcd 0000:00:07.2: suspend_hc

This looks an awful lot like a grub issue to me. My grub entry for this kernel looks like this:

Code:

title Fedora Core (2.6.12)
	root (hd0,1)
	kernel /boot/bzImage ro root=LABEL=/

(in case you were wondering, (hd0,0) is my NTFS XP partition, which I am having to write this to you from because of wireless problems that will be addressed in another thread)

Help a rookie out here, folks!

TIA guys and gals

liquidtenmilion · 06-23-2005, 12:04 PM

root (hd0,1)
kernel /boot/bzImage root=/dev/hda2

that will most likely work for you. Make sure that the file /boot/bzImage actually exists.

litlmary · 07-13-2005, 08:13 AM

Sorry I was out to lunch for so long...

OK, so that got me past the kernel panic. Good.

Now I am getting further along in the boot process and I get something else that strikes me as odd:

Code:

Warning: unable to open an initial console.
input: PS/2 Generic Mouse on isa0060/serio1

then it hangs.

I would think it would hang at the error and not go on to detecting the mouse before it hangs.

or is something else going on that I can't see?

Thanks for the help

goal-ARG · 07-28-2005, 06:17 PM

hi

my inglish is bad

I wait you believe me.

Problem:
Warning: unable to open an initial console.
input: PS/2 Generic Mouse on isa0060/serio1

Solution:
you need compile in your following section kernel:

Devices Drivers --> Block devices:

<*>RAM disk support
(16) Default numbers of RAM disk
(16384) Default RAM disk size (Kbytes)[*] Initial RAM disk (initrd) support

exit and save your kernel configuration

then:

make
make modules_install

make install <--- this code generate ram disk image and modify your /boot/grub/grub.conf

this is all

luck for you.

example of the 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,1)
# kernel /vmlinuz-version ro root=/dev/hda3
# initrd /initrd-version.img
#boot=/dev/hda

default=2
timeout=10
splashimage=(hd0,1)/grub/splash.xpm.gz

title your_kernel (2.6.12)
root (hd0,1)
kernel /vmlinuz-2.6.12 ro root=/dev/hda3 <--there write your partition root ( / )

initrd /initrd-2.6.12.img <---initial image ( / )

title fedora Core 2 (2.6.5-1.358)
root (hd0,1)
kernel /vmlinuz-2.6.5-1.358 ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.5-1.358.img

title Windows
rootnoverify (hd0,0)
chainloader +1