Re: new kernel panics
- From: Wackojacko <wackojacko32@xxxxxxxxxxxx>
- Date: Mon, 30 Apr 2007 15:38:28 +0100
steve downes wrote:
Just compiled my 1st kernel.
Using sources from 2.6.18-4 (((((((((same as present kernel to keep it
simple)
Compiled ext3 & ext2 into the kernel (not as modules)
installed kernel & modules
installed into grub
root (hd0,0)
kernel /vmlinux root=dev/hda2 ro noinitrd
save default
The stock kernel was
root (hd0,0)
kernel /vmlinux-2.6.18-4-686 root=/dev/hda2 ro
initrd /initrd.img-2.6.18-4-686
savedefaults
The stock kernel works, the new kernel fails after 20 lines (or so)
with:-
please append correct "root=" boot optopns
kernel panic - not syncing: VFS: unable to mount root fs on
unknown-block(0,0)
I have tried all combinations of (hd0,0) & 0,1 & root=/dev/hda1
& 2. There is no initrd for the new kernel which is what I want
file systems hda1 is /boot & hda2 is / & both are ext3
I have been presuming it to be a grub menu.lst problem but it could be
a kernel compile problem. I would have thought that if so it would
have to be around the ext3 file system but it seems to load something
before it panics so I would think that is OK
Can anybody suggest anything else - PLEASE
Steve
Have you compiled the driver for your motherboard IDE/SATA controller into the kernel. If its a module and no initrd then grub will not be able to see the disks, let alone the partitions :)
HTH
Wackojacko
--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
- Follow-Ups:
- Re: new kernel panics
- From: steve downes
- Re: new kernel panics
- References:
- new kernel panics
- From: steve downes
- new kernel panics
- Prev by Date: Re: hda:lost interrupt!!!
- Next by Date: Re: ibm T40 and xorg.conf
- Previous by thread: new kernel panics
- Next by thread: Re: new kernel panics
- Index(es):
Relevant Pages
|