[syslinux] Memdisk and USB Floppy
Andy Wray
awray at nc.rr.com
Tue Feb 4 21:47:46 PST 2003
Anything to help... Here are the messages:
Loading memdisk....
Loading BRJT17A.IMG.........................
Ready.
MEMDISK 2.01 2.01-pre3 Copyright 2001-2002 H. Peter Anvin
Ramdisk at 0x1fe50000, length 0x00168000
command line: initrd=BRJT17A.IMG BOOT_IMAGE=memdisk
Disk is floppy, 1440K, C/H/S = 80/2/18
dos_mem = 0x9d000 (628 K)
low_mem = 0xf00000 (15360 K)
high_mem = 0x1efec380 (507824 K)
Total size needed = 1212 bytes
Old dos memory at 0x9d000 (map says 0x9d000), loading at 0x9c800
dos_mem = 0x9c800 (626 K)
low_mem = 0xf00000 (15360 K)
high_mem = 0x1ee50000 (506176 K)
1588: 0xffff 15E801: 0x3c00 0x1ee5
INT 13 08: Success, count = 0, BPT = 0000:0000
old: int13 = f00080fa int15 = f000f859
new: int13 = 9c800008 int15 = 9c800230
Booting...
Non-System disk or disk error
Replace and press any key when ready
I can try debug builds if you'd like also...
Thanks again,
--Andy
-----Original Message-----
From: syslinux-admin at zytor.com [mailto:syslinux-admin at zytor.com] On
Behalf Of H. Peter Anvin
Sent: Monday, February 03, 2003 1:39 AM
To: H. Peter Anvin
Cc: Andy Wray; syslinux at zytor.com
Subject: Re: [syslinux] Memdisk and USB Floppy
H. Peter Anvin wrote:
> Andy Wray wrote:
>
>> I just wanted to chime in and mention that I'm running into the
problem
>> with getting a "Non-system disk..." error on a system using a USB
floppy
>> when the floppy is not attached when I try to boot the system over
the
>> network using memdisk to boot a floppy image. Its actually fairly
>> important to be able to do this, as the architecture of the hardware
>> that I'm working with utilizes a single USB floppy that is shared
across
>> multiple machines and there is no way to add a normal floppy. So to
use
>> memdisk right now, I have to boot the floppy image over the network
>> serially, rather than in parallel.
>>
>> I had been using bpbatch without this problem on these systems, but
I'm
>> trying to move off of it (it won't boot the installation kernel from
the
>> SuSE 8.1 CDs). Of course, I know bpbatch is not open-source, so
>> figuring out how it does things is probably difficult at best.
>>
>
> This is pretty much impossible to diagnose without access to the
hardware.
>
I should say, there probably are things I could guess at. It would
really help to get all the messages MEMDISK spits out at the beginning
-- that's kind of the whole point of them.
I make no promises... after all, I don't get paid for this work.
(Although I appreciate the donations I've gotten so far -- thanks guys
-- it's not even close to offsetting my costs.)
-hpa
_______________________________________________
SYSLINUX mailing list
Submissions to SYSLINUX at zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.
More information about the Syslinux
mailing list