So, back to this issue.
I've finally figured out how to make a bootable iso ( for future
search in the archives: /n/sources/contrib/maht/rc/mkiso ,
/sys/lib/dist/pc/mkfile , and
http://maht0x0r.blogspot.com/2007/11/roll-your-own-plan9-iso.html were
pretty much the only useful docs I could find on that matter).
First I made a "regular" one, which of course didn't change a thing
for this ibm machine.
Then I made one with *nobiosload=1 in the [common] section of its
plan9.ini and with the old 9load you put in your contrib, but it still
panics in the same way I described in the previous post. I'm pasting
it again, as a reminder:

ELCR: 0C80
apm ax=f000 cx=f000 dx=40 di=ffff ebx=5d84 esi=-1
initial probe, to find plan9.ini... dev A0 port 1F0 config 0040
capabilities 2F00 mwdma 0007 udma 407F
dev A0 port 170 config 85C0 capabilities 2F00 mwdma 0007 udma 0407
FLAGS=10282 TRAP=6 ECODE=0 PC=3
 AX 00000000 BX 80815d78 CX 00000000 DX 800fdfc0
 SI 00001022 DI 00000024 BP 0000746b
 CS 0010 DS 0008 ES 0008 FS 0008 GS 0008
 CR0 80000011 CR2 0000000 CR3 0000c000
panic: exception/interrupt 6

Any other suggestion please?

In the meanwhile I'm gonna try fgb's 9load and see what can be done with that.

Cheers,
Mathieu.

On Thu, Apr 24, 2008 at 2:46 PM, erik quanstrom <[EMAIL PROTECTED]> wrote:
>
> > Nope, I haven't tried yet because that requires that I make myself a
>  > new iso, and I'm uncertain as how to proceed for that.  Shall I mount
>  > the current iso, copy everything on some temporary location, locate
>  > where plan9.ini is, modify it, and just create an iso9660 fs from that
>  > temporary tree?
>  >
>  > Thx for the old 9load.
>
>  assuming you already have a fileserver, you may just want a boot floppy.
>  lacking a physical floppy, you can build an eltorito from the floppy image.
>
>  this isn't something i've done in a very long time as i find it much easier 
> to
>  find a workable nic and pxe boot.
>
>  - erik
>
>
>



-- 
GPG key on subkeys.pgp.net:

KeyID: | Fingerprint:
683DE5F3 | 4324 5818 39AA 9545 95C6 09AF B0A4 DFEA 683D E5F3

Reply via email to