[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Tap tap tap, this thing on?



> so when I do boot fd0:linux.gz root=/dev/fd0 load_ramdisk it should work?
> Trouble is that it doesen't here!  boot fd0:linux.gz root=/dev/fd0
> load_ramdisk=1 dies with  You didn't specify the type of your ufs file
> system
> mount -t ufs -o
> ufstype=sun|sunx86|44bsd|old|nextstep|nextstep-cd|opensep...

I'm thinking there are 3 possibilities now:

1). The built milo floppy has problems: MS-DOS formatted a floopy, copied 
linload.exe onto it, and then copied the pc64 version of milo onto it ? Are 
you absolutely, positively sure your system is a pc64 (the wrong build of 
milo could definately cause all these problems you're seeing).

If this disk is built and loaded correctly, milo will give you a nice command 
prompt where you can manually enter the boot parameters (ie, boot 
fd0:/linux.gz root=/dev/fd0 load_ramdisk=1).

2. If you can past stage 1) just fine, then maybe it is that the rescue.bin 
binary is just not getting cleanly written to your floppy. 

When I was installing debian on alpha, I ran into some wierdness (or maybe 
just a lack in confidence) with making sure the rescue.bin was getting copied 
properly from the alpha system, so I used rawrite2.exe on a Intel-MS-DOS box 
to build the rescue.bin and root.bin floppies.

3). There is a bug with the generic rescue.bin with the pc64 milo. 

I don't understand how this works, but there is a coupling between a milo 
version and a linux kernel. It doesn't work to get a random version build of 
milo for the pc64 and hope it will work with your kernel - and vice versa as 
well.

Hope this helps,
geoff Brimhall



Reply to: