This took me a bit longer to track down since I had tried tweaking my kernel between r5 and r6 - removing unnecessary bits, converting some bits I used continually out of modules, testing out ati fb support. 30 odd compiles later I finally tried my r5 .config with r6. And it *still* crashed. So, started poking around to find out why. Found that I did not get: Kernel panic: VFS Unable to mount root fs on 03:03 If I started up without framebuffer support. So, tentatively labeling it as a problem in that area. Reproducible: Always Steps to Reproduce: 1. make mrproper 2. rm -rf /lib/modules just to be paranoid (tried this with and without) 3. make dep && make clean bzImage modules modules_install 4. copy kernel over, reboot with kernel=(hd0,0)/boot/bzImage root=/dev/hda3 video=vesa:ywrap,mtrr vga=0x31A hdd=ide-scsi as per fb FAQ Actual Results: Kernel panic Expected Results: Gentoo Linux starts Had a couple of other odd messages on startup in prior experiments. such as FAT: bogus logical sector size 0 But fact that it didn't work with identical config seems most telling to me.
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
