Hey, could really use a Linux genius for some help... I have a Logitech Quickcam Express, and need to get it working with my RedHat 9 OS. I've tried downloading "qc-usb--0.6.3" (should be the driver for it), and when I used "make" with it, and get a load of errors saying it needs the 2.6 Kernel source, which is fair enough, but after building the Kernel, etc. I've had problems running it from lilo. Here's what's in my lilo.conf; ...etc image=/boot/vmlinux label=linux-new initrd=/boot/initrd-2.6.15.img read-only append="root=LABEL=/" image=/boot/vmlinuz label=linux-old initrd=/boot/initrd-2.4.20-6.img read-only append="root=LABEL=/" I get a kernel panic booting the new kernel "linux-new", and I believe it's due to the line "append='root=LABEL=/'" Can anyone help me out please. Thanx, Daed.

42 :D

Try root=/dev/hdaX where X is the number of your root partition. Better yet, get rid of the antiquated RH 9 and use a newer distro, which may even have the driver you want installed by default.

There could be any number of reasons, but you probably misconfigured something in the kernel. The things I screw up the most are:
1. I blow right by the part where I select the processor, and that gets me a kernel panic.
2. I use ReiserFS and I generally forget to enable support for it, so I can't boot up.

With many things, they must be built in and not modules. If this is your first kernel, then I suggest this strategy: When in doubt, build it into the kernel. When you get it working, then you can recompile with more modules than anything else. If it breaks, then you know what to change back. It's something you have to get used to, but once you have a feel for it, it's a piece of cake.

I had the exact same problem a few weeks ago.
The solution for me was as simple as it was supprising.

Remove the read-only line. Dont ask me why, but you should give it a try.

By the way, you have the line
image=/boot/vmlinuz in both your entries.
I guess the /boot/vmlinuz is a sym-link to one of the kernels. Try the command
$ ls -al /boot
and check what kernel the vmlinuz sym-link points to.

Anyway, you should change the line in lilo.conf
image=/boot/vmlinuz to
image=/boot/<whatever_the_2.6_kernel_is_called>

Make the 2.6 entry look like this:

image=/boot/<whatever_the_2.6_kernel_is_called>label=linux-new

That sould be sufficient

Try using a stripped-down entry in lilo.conf (as I mentioned above) and make sure udev is installed on your system.
I have had this problem several times lately, and that seems to solve the problem.