Date: Mon, 31 Aug 2009 21:24:51 -0400 From: Celejar <cele...@gmail.com> To: debian-user@lists.debian.org Subject: Re: Fwd: Boot problem with Kernel Package kernels Message-Id: <20090831212451.bc3e3572.cele...@gmail.com> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit
On Mon, 31 Aug 2009 17:50:45 -0700 Arthur Barlow <arthurbar...@gmail.com> wrote: ... > I'm been using Debian for over a decade now, and it's always been my > practice to build new kernel with the "kernel-package" software that is part > of Debian's toolkit. I"m noticed over the last few months that all kernels > I try to build will not boot and throw a "kernel panic." The message is as > follows: > > No filesystem could mount root, tried: > Kenel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(0,0) > > My grub menu.lst looks like this: > > title Debian GNU/Linux, kernel 2.6.30 > root (hd0,0) > kernel /boot/vmlinuz-2.6.30 root=/dev/hda1 ro ... > You can see I do not build an "initrd" image, but I've never had to in the > past. Thanks for any suggestions. I've learned the hard way that there are lots of gotchas that can generate that message, and they're not all too obvious. The basic things to look for - mobo and HDD drivers and fs support builtin to the kernel (not as modules since you aren't using an initrd? Same for lvm / luks / raid or anything else needed to get your HDD online? You should probably give us as much information as you can about your setup, with regard to the above questions, and post your kernel config somewhere, perhaps a pastebin. Celejar Celejar, You were right. I need to set my PCI drivers to be built-in instead of modular, along with the file system drivers. That fixed it.