RE: mkbootdisk fails

["Adrian Saidac" <adrian saidac now-online com>]

mkbootdisk --device /mnt/fd0

> -----Original Message-----
> From: Mark Gray [mailto:markgray iago nac net]
> Sent: Sunday, December 06, 1998 10:48 AM
> To: rruth computer org
> Cc: redhat-list redhat com
> Subject: Re: mkbootdisk fails
>
>
> Richard <richard studio disney com> writes:
>
> >
> >
> > I am attempting to create a new boot diskette on my Red Hat 5.2 Intel
> > system, because I just compiled a new kernel.
> >
> > In /boot I have a symbolic link from zImage-2.0.36 (my new boot file) to
> > vmlinuz-2.0.36, the boot file that mkbootdisk seems to look for.
> >
> > Here is the session:
> >
> > # /sbin/mkbootdisk 2.0.36
> > Insert a disk in /dev/fd0. Any information on the disk will be lost.
> > Press <Enter> to continue or ^C to abort:
> > No module BusLogic found for kernel 2.0.36
> > open /vmlinuz-2.0.36: No such file or directory
> >
> > I have a BusLogic scsi adapter, however, it is compiled into
> the kernel, not
> > as a module.
> >
> > How do I create a new boot diskette?
>
> I think the problem is in /etc/conf.modules -- if there is still a
> reference to your old BusLogic module there, mkinitrd tries to find it
> in order to make an initial ramdisk image.  (This is just a guess.)
> Remove that reference and try again I'd say.
>
> > Richard
> > rruth computer org
> >
> >
> >
> > --
> >   PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING
> LIST ARCHIVES!
> > 		http://www.redhat.com http://archive.redhat.com
> >          To unsubscribe: mail redhat-list-request redhat com with
> >                        "unsubscribe" as the Subject.
> >
> >
>
>
> --
>   PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
> 		http://www.redhat.com http://archive.redhat.com
>          To unsubscribe: mail redhat-list-request redhat com with
>                        "unsubscribe" as the Subject.
>