[syslinux] ISOLinux and OpenBSD?

[ganapathy murali krishnan]

Well...... This works on new machines, but on old machines (with a buggy 
BIOS) it doesn't. So either I need to upgrade the BIOS on these machines 
and/or hope that the bug is ironed out of memdisk.

- Murali

ganapathy murali krishnan wrote:

> That worked! Instead of typing
>
> "memdisk initrd=openbsd.img", if I type "openbsd.img" then it works 
> and drops me into the boot prompt.
>
> So I guess this might qualify as a bug-report for memdisk. Would be 
> interesting to see what BIOS does but memdisk doesn't.
>
> A successful example
> --------------------------------
> boot: openbsd.img
> reading boot......
> probing: pc0 apm mem[633K 126M a20=on]
> disk: fd0
> >> OpenBSD/i386 BOOT 2.02
> boot>
>
> A failed example
> -----------------------
> boot: memdisk initrd=openbsd.img
> Loading memdisk.....
> Loading openbsd.img.....
> Ready.
> MEMDISK 2.08 <snip>
> <snip e20 details>
> Ramdisk at 0x07e60000, length 0x00168000
> command line: initrd=openbsd.img BOOT_IMAGE=memdisk
> Disk is floppy, 1440 K, C/H/S = 80/2/18
> Total size needed = 1455 bytes, allocating 2K
> old dos memory at 0x9f400 (map says 0x9f400), loading at 0x9ec00
> 1588: 0xffff 15E801: 0x3c00 0x06e6
> INT 13 08: Failure, assuming this is the only drive   # Yes, there are 
> no floppy drives on this system
> old: int13 = e23f780d int15 = f000f859
> new: int13 = 9ec00008 int 15 = 9ec00272
> Loading boot sector.... booting...
> reading boot......
> probing: pc0 apm mem[631K 125M a20=on]
> disk: fd0 (hangs here)
> ---------------------------
>
> - Murali
>
> Blaauw,Bernd B. wrote:
>
>>> + booting floppy34.fs image from the CD works correctly (no 
>>> ISOLinux, in built BIOS emulates the floppy)
>>>   
>>
>>
>> Hi,
>>
>> have you tried the following (Isolinux direct emulation):
>> KERNEL 34FS.IMG should function the same as if direct 1.44MB eltorito 
>> emulation was used.
>>
>> but using MEMDISK it fails?
>> KERNEL MEMDISK
>> APPEND INITRD=34FS.IMG
>>
>> that's all I can come up with .
>>