I rawritten milo\images\xl.img to a disk, and got everything setup to boot
MILO.  MILO apears to be working correctly.

I've 'rawritten' images\generic.img to a disk. and rawrite.img to another
disk.
when I use the command boot fd0:vmlinux.gz root=/dev/fd0 load_ramdisk=1 it
gives me the error message unknown file system, kernel not loaded.

So I tried the command:
boot scd0:kernels/generic.gz root=/dev/scd0 load_ramdisk=1
it boots teh kernel, then tells me that it can not init, and to use the
init= parameter of the boot command (for which I can find no documentation)

Then I tried boot scd0:kernels/generic.gz root=/dev/sda1 and that started
booting too, only gave me the error can not load fs at 10:08

So then I tried boot scd0:kernels/generic.gz root=/dev/fd0 load_ramdisk=1
and this gets me to a prompt for a root disk.  Now on x86 I know that is
files such as color.gz,etc.  However I see no file which even remotely
resemble that on the Alpha CD.

Please Help
Thank you much,
Jim

on the CD you should find /images/ramdisk.img "rawrite" or "dd" this one.

Good luck. If you should succeed, please let me know and send me your exact
command line. Maybe it'll help me...

Ingo

"Ingo T. Storm" <i...@computerbild.de> wrote in message
news:880e4k$l473$1@fu-berlin.de...

Please wait while seeting up devices.................
Major devices are: fd (0002) sd (0008) sr (000B)
VFS: disk change detected on device: 2/0
DMA crossing 64-K boundry fffffc00000dc000-fffffc00000e0400
end_request: I/O error, dev 02/00, sector 2
block_read: read failed (after 0 bytes)

gave the same error for the other 2 file systems it tried (iso9660 and
MSDOS).  Then gave the error
MILO:FILESYSTEM UNKNOWN
MILO:Can not boot kernel.

I tried just copying the generic.img file to a disk... but it's too big.
Could that be a problem too with rawriting it?
*sigh*
Thanks for your help, but any other suggestions?

news:lj6p4.15386$Uz3.190033@typhoon.midsouth.rr.com...

setup should start from there.

you do not need to add the extra aguemts to start the install kernel, boot
fd0 is sufficient.

news:w9Oo4.1814$68.42842@typhoon.nyroc.rr.com...

As to the previous conversations, I have also done similar, but my error is
different.

I have adjusted AlphaBios to boot from a floppy
I do have MILO up, and I can see the contents of all drives.
I run "boot fd0:vmlinux.gz root=/dev/fd0 load_ramdisk=1" or "boot
fd0:vmlinux.gz root=/dev/fd0" or "boot fd0:" then "linux"
Gzipped starts uncompressing.......no problem.....
The final notice I get is:
Now the system seems to do a "warm" boot, (but not AlphaBIOs, just same info
as MILO starts) just boots back into MILO, the information displayed is:

If you hit "enter" you get the MILO prompt, if you boot immediately, or let
the countdown expire, you will just keep "warm" booting back to this notice.

Whats going on here?

I've tried every possible combination/location, from the CD, from the
floppy, all end up here.

Can anyone help?  I'm really stuck now.

Thanks.

"Stephen C. Hailey" <haile...@nospam.mmcable.com> wrote in message
news:VT7q4.20618$Mp2.330664@typhoon2.kc.rr.com...

When I installed RH 6.1 onto my 164LX, the boot command that worked for me was "boot scd0:kernels/generic.gz root=/dev/scd0" (no quotes.) Have you tried that? (Booting from the ramdisks didn't work for me either.) I also had to run another (or the same) command in MILO to read from the CD before running the boot command, otherwise I would get some error message saying that it couldn't read the CD.

However, since this is a Digital PWS433a, I would reccommend an SRM installation. (Supposedly, SRM installations don't work on 164LXs.) Did you try booting using the aboot program on the cd?

Hope it helps.

--
        "The music is hot and the music is loud!" - Marc Storace
        http://www.efn.org/~amunk/griogair.cgi

Scott

rawrite -d ramdisk.img a: -n

rawrite -f ramdisk.img -d a: -n

Mohan