I ran into the same problem, a CTRL-C allowed me to continue the boot process
with no apparent difficulties. That does not answer your questions nor mine
but it does allow me to use the system.
-jon-
On Tue, 18 Jan 2000, Michael Hobgood babbled on with the following:
> Hi All,
> I have tried to compile my kernel. I need to disable IDE-ATAPI CD Rom
> support and add SCSI support to use my CDR drive. This is what happened:
>
> make mrproper no problems here
>
> make menuconfig no problems here
>
> make dep no problems here
>
> make bzImage no problems here
>
> make modules no problems here
>
> make modules_install no problems here
>
> cp bzImage to /boot
> edit lilo.conf to include the new kernel
> run sbin/lilo to update lilo
>
> shutdown and try to reboot
>
> Now comes the problems. The new kernel boots but dies on "finding module
> dependencies" during startup.
>
> Trying to boot the old kernel resulting in the system hanging at the same spot
>
> Booting from my bootdisk made from my original system install faile. Got a
> kernel panic saying no initial tty found. Oh well, just do a complete
> re-install and get going again.
>
> Have reread the Kernel Howto and don't see anything I'm missing. Have also read
> instructions about setting up a CDR. These always have the same procedure for
> recompiling the kernel as the ones I followed. By the way, the ones I followed
> are the same as I used when I ran Slackware 4.0 and I had no problems at all.
>
> After a new install, this is what lilo.conf looks like
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=50
> image=/boot/vmlinuz-2.2.13-7mdk
> label=man61
> root=/dev/hda1
> read-only
>
> What I attempted was to add the following to lilo.conf
> image=/boot/bzImage
> label=man61new
> root=/dev/hda1
> read-only
>
> I am guessing the problem has something to do with the map=/boot/map and the
> install=/boot/boot.b commands.
>
> This is what my /boot directory looks like after a clean install
> total 3809
> lrwxrwxrwx 1 root root 28 Jan 18 06:17 System.map ->
>/boot/System.map-2.2.13-7mdk
> -rw-r--r-- 1 root root 167501 Sep 15 11:30 System.map-2.2.13-7mdk
> -rw-r--r-- 1 root root 155775 Sep 15 10:57 System.map-2.2.13-7mdkBOOT
> -rw-r--r-- 1 root root 175931 Sep 15 12:07 System.map-2.2.13-7mdkfb
> -rw-r--r-- 1 root root 178198 Sep 15 10:02 System.map-2.2.13-7mdksmp
> -rw-r--r-- 1 root root 186628 Sep 15 10:29 System.map-2.2.13-7mdksmp-fb
> drwxr-xr-x 2 root root 1024 Jan 17 16:35 bg
> -rw-r--r-- 1 root root 512 Jan 17 17:03 boot.0300
> -rw-r--r-- 1 root root 4552 Aug 22 11:41 boot.b
> -rw-r--r-- 1 root root 612 Aug 22 11:41 chain.b
> -rw-r--r-- 1 root root 444 Jul 22 12:04 chos.bsect
> -rw-r--r-- 1 root root 2560 Jul 22 12:04 chos.loader
> -rw-r--r-- 1 root root 192 Jul 22 12:04 chos.loader-bsect
> -rw-r--r-- 1 root root 812 Jul 22 12:04 chos.loader-linux
> -rw------- 1 root root 9728 Jan 17 17:03 map
> lrwxrwxrwx 1 root root 29 Jan 18 06:17 module-info ->
>/boot/module-info-2.2.13-7mdk
> -rw-r--r-- 1 root root 11773 Sep 15 12:10 module-info-2.2.13-7mdk
> -rw-r--r-- 1 root root 620 Aug 22 11:41 os2_d.b
> lrwxrwxrwx 1 root root 19 Jan 17 16:42 vmlinuz ->
>vmlinuz-2.2.13-7mdk
> -rw-r--r-- 1 root root 586968 Sep 15 11:30 vmlinuz-2.2.13-7mdk
> -rw-r--r-- 1 root root 518604 Sep 15 10:57 vmlinuz-2.2.13-7mdkBOOT
> -rw-r--r-- 1 root root 614373 Sep 15 12:07 vmlinuz-2.2.13-7mdkfb
> -rw-r--r-- 1 root root 610125 Sep 15 10:02 vmlinuz-2.2.13-7mdksmp
> -rw-r--r-- 1 root root 638135 Sep 15 10:29 vmlinuz-2.2.13-7mdksmp-fb
>
> After I did the make modules_install I noticed that the module-info-2.2.13-7mdk
> had changed. I didn't notice the map file changing or anything else.
>
> So here are my questions:
>
> What am I doing wrong?
> What are the /boot entries that have ...mdkBOOT or ...mdkfb etc.
> What are the /boot entries starting with chos. etc
> And finally, how do I make a bootdisk that I can use to rescue me if my next
> kernel compile kills my system. To say the least, I was disappointed that the
> one created during the original install failed to save my bacon.
>
> Thanks for taking the time to assist.
>
> Cordially,
> Michael Hobgood
