On Sun, 21 Nov 1999, Mike Smith wrote:
> >
> > I spent about 2 to 3 hours last night futzing with sysinstall and
> > getting the amr.ko file onto the 4.0 install disk (using the
> > 4.0-19991114 SNAP) I tried adding the amr disks to devices.c in
> > sysinstall but had no luck.
>
> Bah. I knew I forgot something there. That should just about have
> done it.
>
> > After booting the install disks and loading the amr kld (the probe
> > messages showed that it was detected) I escaped to the prompt
> > (alt+f4). I saw that the amrd0 /dev/ entries had been created,
> > but attempts to access them gave "unit 0 not available" (as far as
> > i remeber)
>
> That's not an error message that the driver can produce. It'd be
> helpful to know what it actually said, and whether you have actually
> created an array yet.
>
> > What exactly needs to be done to get 4.0 installed with a amr disk
> > as root?
>
> Sysinstall needs the patch you supplied; apart from that I'm not aware
> of anything else. I haven't, obviously, had time to work on this yet.
> A better diagnostic from you above would save me at least one release
> build...
Unfortunatly all the amr systems I have are now in production, I can
not test a new install on them.
The way I did manage to do the install was nfs mounting another
machine's /, /usr, and /var then using dump/restore to init the
system over a hand done disklabel on the amr (disklabel, not sysinstall).
I'm sorry.
-Alfred
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
