[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: Loadlin problem
- From: BobGunther aol com
- To: redhat-install-list redhat com
- Subject: Re: Loadlin problem
- Date: Tue, 28 Mar 2000 01:20:27 EST
I guess I left out some information that I shouldn't have...
First, I've got a dual drive system, one SCSI, one EIDE... DOS is on the
scsi, and I've got windows 2K and linux on the EIDE.
The output from the command:
loadlin f:\loadlin\bzimage root=/dev/hda6 initrd=f:\loadlin\initrd.img ro
vga=extended
LOADLIN v1.6 (C) 1994..1996 Hans Lermen <lermen elserv ffm fgan de>
not an Image file,
Please enter name of kernel image file followed by optional
command line parameters for Linux (e.g. root=XXXX)
or @file ( file = param file ) or "empty string" to abort:
LOADLIN aborted by user
I did try replacing bzimage with bzImage, tried various path attempts .\ ./
and no path at all... loadlin just doesn't seem to see the file as a kernal
image.
I got bzImage to my dos F drive in the following manner: The F drive was
mounted as an msdos partition at /mnt/dos/f. I used cp to copy the kernal
from the build directory (/usr/src/linux/arch/i386/boot) to the
/mnt/dos/f/loadlin. I tried copying the file using both bzimage as the
destination and bzImage. I even tried using the --sparse=never option for
copy, in case it was trying to copy the kernel as a sparse file. (I didn't
think that likely, but I tried everything I could think of) Is it possible
there is some problem I'm not thinking of with transferring the kernel in
this manner?
Any help greatly appreciated.
Bob
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]