I know the stable kernel is 2.4.9-31... but I thought I would make you
all aware that
I had problems with running the stock RH 7.2 mkbootdisk in creating a
boot floppy
for this kernel 2.4.19-pre2.
mkbootdisk successfully creates the standard boot files as noted below:
[root@f1j rpms]# mkbootdisk
usage: mkbootdisk [--version] [--noprompt] [--mkinitrdargs <args>]
[--device <devicefile>] [--verbose -v] [--compact] <kernel>
(ex: mkbootdisk --device /dev/fd1 2.0.31)
[root@f1j rpms]# mkbootdisk --device /dev/fd0 -v 2.4.19-pre2
Insert a disk in /dev/fd0. Any information on the disk will be lost.
Press <Enter> to continue or ^C to abort:
Formatting /dev/fd0... done.
Copying /boot/vmlinuz-2.4.19-pre2... done.
Creating initrd image... done.
Setting up syslinux... done.
Files created:
[root@f1j rpms]# ls -l /mnt/floppy
total 1057
-rwxr-xr-x 1 root root 203 Mar 3 20:40 boot.msg
-rwxr-xr-x 1 root root 343262 Mar 3 20:40 initrd.img
-r-xr-xr-x 1 root root 6192 Mar 3 20:40 ldlinux.sys
-rwxr-xr-x 1 root root 121 Mar 3 20:40 syslinux.cfg
-rwxr-xr-x 1 root root 730748 Mar 1 20:35 vmlinuz
BUT when booting the system and having the diskette load yields :
Boot failed
I was able to boot this kernel 2.4.19-pre2 using the cat
arch/i386/bzImage >/dev/fd0
command and then shutting down and rebooting.. Of course this is
unacceptable since
it loads ext2 instead of my EXT3.
Again I have built many kernels almost weekly for the last year or so
and this is the first
time I have seen this behavior.
I also downloaded from speakeasy.rpmfind.net the bleeding-edge
mkbootdisk-1.4.2-4.src.rpm,
built it and the results were exactly the same.
Any ideas here. I'm using the grub boot loader and don't want to create
a boot diskette using lilo.
Thanks,
Frank
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
