-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > VFS: Unable to mount root fs on 08:03 > Please append a correct "root=" boot option > Kernel Panic: VFS: Unable to mount root fs on 08:03
I have this same problem now that I'm trying to install a new kernel. I've tried gentoo-sources, gaming-sources, and vanilla-sources, and I constantly get this problem. I've tried using genkernel, which generated a new kernel that worked, however it was generic and didn't have agpgart compiled in. I did a genkernel --config and added in all the usual options, and now the kernel doesn't work. It's amazingly frustrating. Thank goodness I keep a fallback kernel. I tried installing Gentoo on a friend's machine and the same thing happened - so either I have issues or the new kernels do. heh. All I'm doing now is constantly building kernels with new options and trying to figure out what is killing my new kernels. I don't know if it matters, but I'm using grub. Here's my grub.conf, just in case: - ------------------------ default 0 timeout 10 splashimage=(hd0,0)/boot/grub/splash.xpm.gz title=Fallback Kernel root (hd0,0) kernel (hd0,0)/boot/bzImage.fallback root=/dev/hda3 title=Linux Autokernel root (hd0,0) kernel (hd0,0)/boot/kernel-2.4.20-gaming-r3 root=/dev/hda3 intrid (hd0,0)/boot/initrd-2.4.20-gaming-r3 title=New Kernel root (hd0,0) kernel (hd0,0)/boot/bzImage-neue root=/dev/hda3 hd2=ide-scsi - -------------------------------- Rich On Wednesday 06 August 2003 01:02 pm, Mark Johanson wrote: > The funny thing is I didn't make any config changes to the > Kernel when I was in the configmenu. I just saved it and went > along with the compile. Figured its general base setting would > be enough to make it a working kernel. But I was wrong. when I > went to boot the system I got the following error msg: > > ds: no socket drivers loaded > kmod: failed to exec /sbin/modprobe -s -k block-major-8, error = > 2 > VFS: Unable to mount root fs on 08:03 > Please append a correct "root=" boot option > Kernel Panic: VFS: Unable to mount root fs on 08:03 > > now the boot is pointed to /dev/sda3 like the example in the > install instructions show. (example for /dev/hda3 but the system > I am using is a scsi). Thoughts? Or am I doomed to start over > from the begining? > > > From: "David H. Askew" <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Content-Type: multipart/signed; micalg=pgp-sha1; > > protocol="application/pgp-signature"; > > > boundary="=-scGAzJHpVWkuF+5MBUNe" > > Message-Id: <[EMAIL PROTECTED]> > > Mime-Version: 1.0 > > Date: 05 Aug 2003 16:51:30 -0500 > > Subject: Re: [gentoo-user] Kernel compile issue?? > > > > > > > > That looks normal. Assuming you configured it correctly, you > > should be > > > good to go once you install it. > > > > On Tue, 2003-08-05 at 16:47, Mark Johanson wrote: > > > I'm not sure if my kernel compile is finishing correctly. I > > am > > > > setting up from a stage 3 tarball, and when I get to the > > end > of > > > > what the compile is doing and gives me a command prompt I > > get > > > > no > > > indication the compile finished correctly. The last line > > before > > > > the command prompt reads: > > > > > > if [ -r System.map ]; then /sbin/depmod -ae -F System.map > > > 2.40.20-xfs-r3; fi > > -- > [EMAIL PROTECTED] mailing list -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/MyagmGzAh8yQ/jERAvX5AKC+/i2iXt9nJoU54flnQ4hEdglOJwCgpgcY NVF9SenWBS8djz6YmGKkj7Y= =mg5z -----END PGP SIGNATURE----- -- [EMAIL PROTECTED] mailing list
