I get the installation loaded on, but then the following - after pressing
the halt button after a successful setup from the cd:
>>> show device
dka0.0.0.4.0 DKA0 TOSHIBA CD-ROM XM-57 3476 //my cdrom
dkc0.0.0.1009.0 DKC0 RZ1CC-BA 883F // i believe my hd
dva0.0.0.1 DVA0 // my floppy
ewa0.0.0.3.0 EWA0 00-00-F8-75-5E-57 // network card
pkc0.7.0.1009.0 PKC0 SCSI Bus ID 7 5.54
pqa0.0.0.4.0 PQA0 PCI EIDE
pqb0.0.1.4.0 PQB0 PCI EIDE
>>> set boot_file
>>> set bootdef_dev dkc0
>>> set boot_osflags 0
>>> boot
(boot dkc0.0.0.1009.0 -flags0)
block 0 of dkc0.0.0.1009.0 is not a valid boot block
bootstrap failure
>>>
And of course I've tried many other combinations, sometimes I can get to the
'aboot>' prompt, but then can't find a correct image to use. Even using
'boot -fl 1' only got me to the 'aboot>' prompt.
Once again, any help much appreciated.
-----Original Message-----
From: Jamesvi@asu.edu [mailto:Jamesvi@asu.edu]
Sent: Wednesday, March 01, 2000 4:29 PM
To: Gary Grobe
Subject: RE: can't install image for miata ...
Yes. this is only the boot command for the install. After aboot is
installed
on your harddrive, then the boot command can just be 'boot -fl 1' or
whatever.
There is a way to get it to boot automatically from the SRM. I have never
had
time to get it to do this, plus I like being able to pass variables or boot
with different kernels from the command line (in case I really screw things
up
and need to get in without being able to boot the machine to begin with and
don't want to wipe my harddrive). So there are a number of ways to boot
without booting from the floppy or typing in the full boot string every
time.
I hope that helps some.
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:
> Is this how your normally boot your machine all the time, or is there > another way to configure it after the install where you don't have to keep > doing this? Your constantly getting the kernel on floppy this way, not the > one on the filesystem. Maybe I misunderstood this. > > -----Original Message----- > From: Jamesvi@asu.edu [mailto:Jamesvi@asu.edu] > Sent: Wednesday, March 01, 2000 1:47 PM > To: axp-list@redhat.com > Subject: RE: can't install image for miata ... > > > I boot my by typing > boot dva0 -fi vmlinux.gz -fl "root=/dev/fd0 load_ramdisk=1" > > Then have the ramdisk image on a floppy, the updated one (unless you are > installing 5.2). Also, I have never been able to get my miata to boot from > the CD or even to look at the CD except to get the RPMs inside the > installer. > 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: > > > Woooohooooooo! > > > > Pplz, I'd just like to say thanks for your patience and help. SRM is > > definately the way to go. I'd say the SRM faq needs to be re-worded to not > > say "... this doc is not for you.". > > > > Once again, Big thnxs. > > > > -- > > 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
This archive was generated by hypermail version 2a22 on Sat Apr 1 04:14:59 2000 PST
Send any problems or questions about this archive to webmaster@alphalinux.org.