Summary: | gentoo-sources-r6 -> VFS Unable to mount root fs on 03:03 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | bugs |
Component: | [OLD] Core system | Assignee: | x86-kernel (DEPRECATED) <x86-kernel> |
Status: | RESOLVED INVALID | ||
Severity: | critical | CC: | mholzer |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | This was my r5 config |
Description
bugs
2003-08-30 09:10:55 UTC
Created attachment 16818 [details]
This was my r5 config
This config worked in r5, cause kernel panic when compiled in r6 (even tried
rm -rf r6 and /lib/modules and reemerging)
Please try this with LILO: GRUB is not the very best to when you're using "non-standard" kernel configs, such as those with framebuffers.
-----------------------------------------------------------------------
> FAT: bogus logical sector size 0
Run whatever program fixes FAT filesystem corruption bugs
VFAT filesystem is not corrupted. With kernel compilation linked above mounts fine. Think it is irrelevant. Not certain how I got that error though. Couldn't see anything I added that would cause it to occur. GRUB worked fine for months, several recompiles of r5. I find that unlikely. Furthermore, unless you have some truly bizaare theory about grub not handing off the boot params correctly, the crash occurred after grub had handed off everything to the kernel. But, will create a lilo boot disk and try it out, just to eliminate the variable. *sheepishly* Can invalidate this one. Don't know what I did, or if that config is even untampered with, but tried dropping back to r5 and had the same problems. Will try tracking down later, if I have energy to go throw all those damn reboots... Might just give up on frame buffer for now. how about -r7 ? wrong kernel config causes this |