RE: can't install image for miata ...

[Phillip Ezolt <ezolt perf zko dec com>]

Oh... It's very hard to find it.  I'll reboot mine and see if I can
write down the steps.

--Phil

Compaq:  High Performance Server Division/Benchmark Performance Engineering 
---------------- Alpha, The Fastest Processor on Earth --------------------
Phillip.Ezolt@compaq.com        |C|O|M|P|A|Q|        ezolt@perf.zko.dec.com
------------------- See the results at www.spec.org -----------------------

On Wed, 1 Mar 2000, Gary Grobe wrote:

> Geez, I'm starting to wonder if we're talking the same machine. 
> 
> System Type: DIGITAL Personal Workstation 500a
> 
> Processor Digital Alpha 21164, Revision 7.2
> Speed 500MHz
> Cache: No External Cache
> Memory: 128 Mb
> 
> AlphaBIOS Version: 5.65 980325.1437
> POST Code Version: v5.90
> 
> ... Which I thought was the miata. ... 
> 
> About AlphaBIOS reports:
> 
> AlphaBIOS Version 5.65
> Copyright ...
> Copyright ...
> 
> ARC Multiboot
> Copyright ...
> Copyright ...
> 
> X86 BIOS Emulation
> Copyright ...
> Copyright ...
> 
> I'll start looking to see if I can use SRM but I see nothing in the BIOS
> about it.
> 
> -----Original Message-----
> From: Jamesvi@asu.edu [mailto:Jamesvi@asu.edu]
> Sent: Wednesday, March 01, 2000 11:28 AM
> To: axp-list@redhat.com
> Subject: RE: can't install image for miata ...
> 
> 
> If you have a PWS then you should have both the SRM and the AlphaBios.  It
> is
> easy to switch between the two.  You can do it from within the Bios settings
> to get to SRM and then the set_os=unix (or something like that).  It is in
> the
> manual.  I'm not at my machine or I would look it up for you.  It took a
> long
> time before I could even find a MILO that would work on my machine.  Jay
> makes
> the best argument for using SRM.  Unless you have a particular fondness for
> AlphaBios and MILO (they even take 3 times as long to boot) I would
> recommend
> going with the SRM.
> James
> 
> ----------------------------------------------------------------------------
> --
> James Fowler
> Graduate Student Political Science & Latin America
> Arizona State University
> jamesvi@asu.edu        					ICQ: 22088266
> ----------------------------------------------------------------------------
> -
> 
> 
> On Wed, 1 Mar 2000, Gary Grobe wrote:
> 
> > I was just doing what the SRM faq says
> > (http://www.alphalinux.org/faq/srm-1.html), "... If your Alpha system
> starts
> > up with AlphaBIOS, or some other firmware, then this document is not for
> > you." Other than that, MILO seemed pretty easy and so did the alphabios
> > setup. It's just the loading of the kernel.
> > 
> > 
> > -----Original Message-----
> > From: Jamesvi@asu.edu [mailto:Jamesvi@asu.edu]
> > Sent: Wednesday, March 01, 2000 10:53 AM
> > To: axp-list@redhat.com
> > Subject: RE: can't install image for miata ...
> > 
> > 
> > I prefer to install from the SRM disks and then use milo to boot, if I am
> > going to use milo at all, after it is installed.  I never had any luck
> with
> > the MILO and installation.  I figuered it was me and just stuck with what
> > worked best - SRM.  I have a PWS433.  Why all the trouble for MILO anyway?
> > The consensus on the list seems to be pro-SRM, for what appears to be a
> long
> > list of good reason.  Just curious.
> > James
> > 
> >
> ----------------------------------------------------------------------------
> > --
> > James Fowler
> > Graduate Student Political Science & Latin America
> > Arizona State University
> > jamesvi@asu.edu        					ICQ:
> 22088266
> >
> ----------------------------------------------------------------------------
> > -
> > 
> > 
> > On Wed, 1 Mar 2000, Gary Grobe wrote:
> > 
> > > I've got a good boot disk w/ milo and that boots up fine. I've got a
> boot
> > > disk with a generic kernel and a ramdisk. After trying many combinations
> > of
> > > boot lines of the form :
> > > 
> > > boot fd0:vmlinux.gz root=/dev/hda load_ramdisk=1
> > >   (or kernelname.gz)    (or sda*)
> > > also tried many different kernels ...
> > > 
> > > I have my RH6.1 cd in the drive. The kernels always unzip (#UNZIP: this
> is
> > a
> > > zipped file) and then lot's of ###### ... while unzipping, and then the
> > > following: 
> > > 
> > > ...
> > > MILO: About to reboot fd:vmlinux.gz
> > > Hit any key to enter command mode, ESC to boot immediately
> > > Seconds remaining: 0 23
> > > 
> > > At this point, if I hit any key, it boots milo again, if I hit ESC, it
> > > always hangs (on all the different images I've tried).
> > > 
> > > In the alphabios, I've set the first partition (Disk 0, Partition 1) to
> > 7Mb
> > > and the 2nd partition (Disk 0, Partition 2) to 4084 Mb and the devices
> are
> > > show below (or as stated in the alphabios install faq on
> alphalinux.org).
> > > 
> > > MILO> show
> > > ...
> > > hda: TOSHIBA CD-ROM XM-5702B, ATAPI CDROM drive
> > > ...
> > > scsi0 : QLogic ISP1020 SCSI on PCI bus 1 device 9 irq 40 base 0x9000
> > > scsi: 1 host.
> > > 	Vender: DEC	Model: RZ1CC-BA (C) DEC Rev: 883F
> > > 	Type:	Direct-Access			ANSI SCSI revision: 02
> > > Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
> > > scsi : detected 1 SCSI disk total.
> > > SCSI device sda: hdwr sector = 512 bytes. Sectores = 8380080 [4091 MB]
> > [4.1
> > > GB]
> > > Partition check:
> > > sda: sda1 sda2 < sda5 >
> > > Devices:
> > > ramdisk (0100)	fd (0200)	ide0 (0300)	sd (0800)
> > > sda: 	sda1 sda2	sda5
> > > hda:
> > > File systems:
> > > 	ext2 iso9660 msdos
> > > 
> > > 
> > > Gary
> > > 
> > > -----Original Message-----
> > > From: Larry Snyder [mailto:larrys@lexis-nexis.com]
> > > Sent: Tuesday, February 29, 2000 7:50 PM
> > > To: axp-list@redhat.com
> > > Subject: RE: can't install image for miata ...
> > > 
> > > 
> > > Let's look at what works first:
> > > You've got a good boot disk that pulls milo in.  That's the first step,
> > > stick with it.
> > > 
> > > Next step is to load a working kernel.  IIRC, milo can handle both
> > > ext2 and msdos filesystems.  Try copying a kernel image to a 
> > > dos-formatted disk with the copy command under nt.  Then boot milo,
> > > stick the new kernel floppy in, and tell it:
> > > boot fd0:kernelname.gz (where kernelname.gz=your copied image).
> > > At this point it should gripe mightily about mounting the root
> > > partition.  That's fine.  If it says it can't load the kernel, it
> > > may well be a milo problem.  Else, continue...
> > > 
> > > Once you've gotten this far, you should be able to cold-boot back into
> > > milo, put your kernel disk back in, and at the milo prompt 
> > > say boot fd0:kernelname.gz root=/dev/hda.
> > > 
> > > A full description of your hardware would be helpful.  Also, do you
> > > have a partition roughly 2xmemory in size for swap?  axp kernels
> > > normally expect the root partition to be /dev/sda2, so you'd want
> > > your disk to have
> > > sda1=small loader ptn
> > > sda2=big root ptn
> > > sda3=2xram swap
> > > 
> > > ...and why the sda5?......
> > > HTH,
> > > -ls-
> > > 
> > >   
> > > 
> > > 
> > > 
> > > Gary Grobe <Gary.Grobe@aspentech.com> wrote:
> > > > I've got 7Mb allocated on the first partition and 4Gb on the second. 
> > > > 
> > > > 'show' on MILO presents:
> > > > Devices:
> > > > ramdisk (0100) fd (0200) ide0 (0300) sd (0800)
> > > > sda: sda1 sda2 sda5
> > > > hda:
> > > > 
> > > > I've tried hda and I get:
> > > > kernel: unaligned trap at fffffc0000d70268: fffffc0000039d69 29 2
> > > > ... more of same
> > > > MILO: Failed to load the kernel
> > > > 
> > > > I format a floppy on NT, then do rawrite w/ several different images,
> > then
> > > > use the hda device, but w/ no luck.
> > > > 
> > > > -----Original Message-----
> > > > From: Cisneros, Marco (CAP, CMS) [mailto:Marco.Cisneros@gecapital.com]
> > > > Sent: Tuesday, February 29, 2000 4:37 PM
> > > > To: axp-list@redhat.com
> > > > Subject: RE: can't install image for miata ...
> > > > 
> > > > 
> > > > Remember that you should have at least a 2 megs. partition (windows
> fat)
> > > at
> > > > the first part of your harddrive because you are going to install the
> > > miata
> > > > on that partition.
> > > > 
> > > > Boot your Alpha with milo
> > > > 
> > > > At the milo prompt Insert the generic kernel into the floppy and type:
> > > > 
> > > > boot fd0:vmlinux.gz root=/dev/hda0     
> > > > 
> > > > Lets see what happens
> > > > 
> > > > 
> > > > 		-----Original Message-----
> > > > 		From:	Gary Grobe [mailto:Gary.Grobe@aspentech.com]
> > > > 		Sent:	Tuesday, February 29, 2000 5:04 PM
> > > > 		To:	axp-list@redhat.com
> > > > 		Subject:	can't install image for miata ...
> > > > 
> > > > 		The machine I've got is a Persoanl Workstation 500a and I've
> > > > got the redhat
> > > > 		6.1-alpha cd in the cdrom (hda0). 
> > > > 		At the milo prompt I'm trying to boot with the following
> > > > line:
> > > > 
> > > > 		boot fd0:vmlinux.gz root=/dev/hda0
> > > > 
> > > > 		Theres a generic kernel image on the floppy created w/
> > > > rawrite.
> > > > 
> > > > 		This results in a prompt w/: Hit any key to enter command
> > > > mode, ESC to boot
> > > > 		immediately.
> > > > 		If I hit any key, it just goes back to milo, and ESC just
> > > > brings this choice
> > > > 		back around after unzipping the image (in a forever loop).
> > > > 
> > > > 		boot hda:/images/generic.img root=/dev/sda1
> > > > 		(after many lines of #####'s)
> > > > 		results: Bad filehdr magic number 0x0 should be 0x183
> > > > 
> > > > 		boot hda:/milo/images/miata.img root=/dev/sda1
> > > > 		results: MILO: Failed to load the kernel
> > > > 
> > > > 		boot hda:/milo/miata.gz root=/dev/sda1
> > > > 		(after one line of ####'s)
> > > > 		results: Bad filehdr magic number 0x41f should be 0x183
> > > > 
> > > > 		boot hda:/images/ramdisk.img root=/dev/sda1
> > > > 		(after one line of ####'s)
> > > > 		results: Bad filehdr magic number 0x0 should be 0x183
> > > > 		MILO: Failed to load the kernel
> > > > 
> > > > 		I've also tried the generic-up-2.2.12 image, don't remember
> > > > what I got, but
> > > > 		pretty much the same.
> > > > 
> > > > 		Any help much appreciated.
> > > > 
> > > > 		TIA 
> > > > 
> > > > 		Gary
> > > > 
> > > > 		-- 
> > > > 		To unsubscribe: send e-mail to axp-list-request@redhat.com
> > > > with
> > > > 		'unsubscribe' as the subject.  Do not send it to
> > > > axp-list@redhat.com
> > > > 
> > > > -- 
> > > > To unsubscribe: send e-mail to axp-list-request@redhat.com with
> > > > 'unsubscribe' as the subject.  Do not send it to axp-list@redhat.com
> > > > 
> > > > -- 
> > > > To unsubscribe: send e-mail to axp-list-request@redhat.com with
> > > > 'unsubscribe' as the subject.  Do not send it to axp-list@redhat.com
> > > 
> > > -- 
> > > To unsubscribe: send e-mail to axp-list-request@redhat.com with
> > > 'unsubscribe' as the subject.  Do not send it to axp-list@redhat.com
> > > 
> > > -- 
> > > To unsubscribe: send e-mail to axp-list-request@redhat.com with
> > > 'unsubscribe' as the subject.  Do not send it to axp-list@redhat.com
> > > 
> > > 
> > 
> > -- 
> > To unsubscribe: send e-mail to axp-list-request@redhat.com with
> > 'unsubscribe' as the subject.  Do not send it to axp-list@redhat.com
> > 
> > -- 
> > To unsubscribe: send e-mail to axp-list-request@redhat.com with
> > 'unsubscribe' as the subject.  Do not send it to axp-list@redhat.com
> > 
> > 
> 
> -- 
> To unsubscribe: send e-mail to axp-list-request@redhat.com with
> 'unsubscribe' as the subject.  Do not send it to axp-list@redhat.com
> 
> -- 
> To unsubscribe: send e-mail to axp-list-request@redhat.com with
> 'unsubscribe' as the subject.  Do not send it to axp-list@redhat.com
> 
>