Ok you say you compiled the kernel manually, all you need to do is include support for the VFS file system in your kernel preferably built in rather than a module. That should do the job. As for the options for your kernel you dont need all the ram disk stuff that genkernel uses. Yours can simply be: title=Gentoo Linux 2.6.11 R10 root (hd0,*) kernel /kernel-2.6.11-gentoo-r10 root=/dev/hda*
And that should do the trick, if you have enabled the vesa frame buffers than there are a couple other parameters that you need to enable but not to worry bout that just yet. Cheers Rav On 6/22/05, Fernando Meira <[EMAIL PROTECTED]> wrote: > Ok, still unsolved! > > I know that this can happen due to 2 reasons: > 1) wrong boot parameters, > 2) compiled fs as module. > > I've been checking the first reason, and I couldn't solve through it... I > use grub, and the first time I compiled the kernel using genkernel. Now I > compiled it manually. The boot parameters differ from each type of kernel > compiling, right? I tried to remove all the root=/dev/ram0... leaving just > the /boot/vmlinuz root=/dev/hda4, but it didn't work (though the error > message said now "unknown-block(3,4)" instead of "(1,0)". > Note: before I had kernel-2.6.11-r9" and now I have "vmlinuz"... > > For the second reason, I'm sure that I compiled ReiserFS in the kernel, and > not as module. However, it was the only one I compiled! Did I need ext2, > even though I don't have ext2? > > Any ideas before I recompile the kernel again? > And, if I have to recompile it, do I start with previous the configuration, > where I would just need to check this fs detail, or will I have to pass > through all the items again? > > thanks!! > > > On 6/22/05, Fernando Meira <[EMAIL PROTECTED]> wrote: > > I should have read this mail before I rebooted.. :P > > > > I end up with a > > > > VDF-fs: No partition found (1) > > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(1,0) > > > > I will need to use the livecd to fix the prob.. after I find what's going > on... > > > > > > > > On 6/22/05, Ryan Viljoen <[EMAIL PROTECTED] > wrote: > > > > My problem is that I assume that the new configuration replaces the > > > > previous one. So, I would need to replace all files. > > > > > > You dont need to replace your old kernel files you can simply copy > > > them over to /boot under a different name so use: > > > My previous kernel has: > > > /boot/kernel-2.6.11-gentoo-r10 > > > /boot/initrd-2.6.11-gentoo-r10 > > > /boot/System.map-2.6.11-gentoo-r10 > > > or what ever your new kernel is. Than just add a new option in your > > > grub.conf much like the old one for you newly compiled kernel. This > > > probably the best thing to do especially if your new kernel has errors > > > when loading, you can easily revert back to the old one and fix the > > > problem. > > > > > > Cheers > > > Rav > > > > > > -- > > > "When you play a Microsoft CD backwards you can hear demonic Voices... > > > that's nothing - when you play it forward it installs Windows" > > > Are you fearing my mouse? <:3___)~~~~ > > > > > > -- > > > gentoo-user@gentoo.org mailing list > > > > > > > > > > > > -- "When you play a Microsoft CD backwards you can hear demonic Voices... that's nothing - when you play it forward it installs Windows" Are you fearing my mouse? <:3___)~~~~ -- gentoo-user@gentoo.org mailing list