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

[Gary Grobe <Gary Grobe aspentech com>]

Actually, I believe the hda is my cd-rom as shown in the output below.

> 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
>

As far as missing info after the unzip of the kernel, there are no error
messages that I can tell, but I do see this:

after the unzipping of the kernel (and after clearing the screen) ...
dev_config: fixing up latency from 0 to 32 for 8086:484
NVRAM is not supported on this system
Linux/Alpha Miniloader (MILO)
MILO:
	Build against Linux version 2.0.30 (rsuling@linux.reo.dec.com) (gcc
version 2.7.2.1) #12 Fri Sep 26 20:26:27 GMT 1997
	Video is Digital BIOS Emulation (VGA), Zlxp (TGA)
	Loaded from WNT ARC
	Device drivers are IDE, SCSI (NCR 810, Qlogic ISP, AHA2940UW),
Floppy
	Memory size is 128MBytes
Calibrating delay loop.. ok - 495.98 BogoMIPS
MILO: About to reboot fd:vmlinux.gz.
Hit any key to enter command mode, ESC to boot immediately
Seconds remaining: 0

... and it hangs


> 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

The kernel never boots up so I don't ever get the prompt for the ramdisk,
and I understand what your saying about using root=/dev/fd0, but same
results.

 
-----Original Message-----
From: W Bauske [mailto:wsb@paralleldata.com]
Sent: Wednesday, March 01, 2000 11:24 AM
To: axp-list@redhat.com
Subject: Re: can't install image for miata ...


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 would assume /dev/hda is your boot hard disk, not something
you should be specifying on the boot command for the install.
You tell the installer later that you want to install on
that drive.

> 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:
> 

It would seem you're missing some information here. Are you
positive there is no error message right after the unzip??

Also, try 3 floppies:

1. your current milo disk
2. kernel image disk
3. ramdisk image disk

Boot up to the milo prompt and after inserting
the kernel disk, put:

boot fd0:vmlinux.gz root=/dev/fd0 load_ramdisk=1

If the kernel does boot up, it will ask you to insert
the ramdisk floppy. If you don't get that, you must be
getting some sort of error from the kernel. 

I've noticed sometimes floppies don't work even though
the machine they were written on sees things fine. So, also
try another floppy for your kernel image, preferably fresh.


Wes

-- 
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