I'm trying to install over the up-talk machine RH 5.2.

I've done the disk-image using dd and mikasa-s.img file from images dir
over the CD, the same way i've done the ramdisk disk and have copied over
a new blanck formatted disk the mikasa-s.gz kernel file.

with the command

boot dva0 -file mikasa-s.img -flags "root=/dev/fd0 load_ramdisk=1"

directly from the SRM console i've booted the first disk (the one with
over mikasa-s.img) but after booting going on Linux/ALPHA bootloader it
tell me: mikasa-s.img: file no found.
Well fine.. trying to go on ... at the aboot promp it ask me the kernel
name and arguments so i type

mikasa-s.gz root=/dev/fd0 load_ramdisk=1 changing the disk on the floppy.

It can read the kernel gzip file but when talk about "ok, now booting the
kernel..."
it fails with

halt code = 6
double error halt
PC = fffffc00003198b4
and then again the SRM promp

What should i do !? I've no exeprience with alpha at all... so i'm like a
newbie.

Thanks for the help.

 This is incorrect. There is no mikasa-s.img in the  boot diskette. The boot
diskette has ext2 file system and contains kernel image file and the boot
loader: aboot.  The correct boot command should be:
     boot dva0 -file mikasa-s.gz -fl "root=/dev/fd0 load_ramdisk=1
prompt_ramdisk=1"

  Try using RH6's boot disk image. Download it from
ftp://ftp.cc.gatech.edu/pub/linux/distributions/redhat/current/alpha/...
generic.img

Xiaozhou Qiu
Linux Consortium
Interoperability Lab
UNH

Well... i've 3 diskettes:
1) Made with dd and the mikasa-s.img file which i use to boot (is the only
one capable in all my try) and does not contain any ext2 filesystem
2) Made with dd and ramdisk (never used since now) and does not contain
any ext2 filesystem
3) The kernel disk wich contain ext2 filesystem and the mikasa-s.gz file.

Right now, which one i should use to boot from SRM console prompt ?
When i start my machine i got >>> as prompt of SRM, what kind of command
and diskette i should use ?

If i use the diskette with the kernel with the command you show up me with
generic.gz RH6 kernel i receive:
------
block 0 of dva0.0.0.0.1 is not a valid boot block
boostrap failure
------
and then the SRM prompt again, with the generic.img dd diskette:
"it go through bootstrap -> initializing -> jumping -> swithching to OSF/1
PAL code version 1.35 and then"
------
aboot: Linux/Alpha SRM bootloader version 0.5
aboot: switching to OSF/1 PALcode version 1.35
aboot: no disklabel found.
aboot: booted_dev=`dva 1 0 0 0 0 0 0', guessing boot_device=`fd0'
generic.gz: file not found
Enter kernel name and arguments:
aboot>
------

So... i'm hoping all of you have understand mor then me :)

I've tried also this one with no success.

Thanks for the help and hints.

Massimo

I had the same problems with my As1000/333 (using aboot).
i can boot but only when do a line like
boot dva0 -file /vmlinux.gz -flags "bootdevice=/dev/fd0 root=/dev/fd0 load_ramdisk=1"
(see SuSE support page i wrote this from my memories).  

        walter

--
-----
"That is the dematerializing control, and that over yonder is the horizontal
 hold.  Up there is the scanner, those are the doors, that is a chair with a
 panda on it, sheer poetry dear boy!"
-----

: I had the same problems with my As1000/333 (using aboot).
: i can boot but only when do a line like
: boot dva0 -file /vmlinux.gz -flags "bootdevice=/dev/fd0 root=/dev/fd0 load_ramdisk=1"
: (see SuSE support page i wrote this from my memories).  

:       walter

Which is a bit weird because if you look how things are really booting
and an aboot code then you find out that above should be "bootdevice=fd0"
and not "/dev/fd0".  OTOH I cannot find anything which would use that
information so you can probably write "bootdevice=my_doodads" as well.
I simply always skip that piece.

  Michal

So if this is "no sense" what should i try ?

CiauZ!