On 04-Jun-2000 Robert D. Crawford opined: > -----BEGIN PGP SIGNED MESSAGE----- > > I have just compiled a new kernel and done all the associated things > (perhaps I missed something VERY important) and am having a bit of a > problem. Here is what I did: > > 1. dl the source from kernel.org (2.2.15) > 2. unpack in /usr/src > 3. mv linux linux-2.2.15 > 4. ln -s linux-2.2.15 linux > 5. cd /usr/src/linux > 6. make mrproper > 7. make xconfig > 8. make dep ; make clean ; make bzImage > 9. make modules ; make modules_install > 10. cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.2.15 > 11. edit lilo.conf to reflect current kernel and create plan b > (label=old) > 12. /sbin/lilo > 13. reboot > > Everything went fine right up to the point where I rebooted. I got the > LILO prompt and hit enter to boot the new kernel. Next I see a LOT of > text scrolling REALLY fast down the screen. I could only decipher the > words 'request' and 'kmod', and I think 'failed'. What have I done wrong > to get me into this situation? Any pointers to relevant links will be > appretiated, but I have read the README, and the kernel HOWTO. Let's see: how about copying System.map to /boot? IF, like me, you need SCSI early, maybe you need an initial ramdisk (mkinitrd). Possibly something missed in the compile that is essential to the early stages of booting. IDE support would do it, though that isn't likely here since you get booted some of the way. Couldn't rule it out, either. I'd reboot to the old kernel, delete the modules and stuff you moved to /boot and recompile without the mrproper stage. That lets you look at the configuration you used originally. Then you can see exactly what you DID do and compare it with what you INTENDED to do. -- Never trust a computer bigger than you can lift. -- To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject.
