Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!inferno.mpx.com.au!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!solace!nntp.uio.no!news.cais.net!news.jsums.edu!gatech!newsxfer2.itd.umich.edu!agate!sklower
From: sklower@oboe.CS.Berkeley.EDU (Keith Sklower)
Newsgroups: comp.unix.bsd.bsdi.misc
Subject: Re: 3c509 problems w/2.1
Date: 29 Mar 1996 02:13:35 GMT
Organization: University of California, Berkeley
Lines: 20
Message-ID: <4jfh0f$bpo@agate.berkeley.edu>
References: <m0u10fA-001TNfC@ivan.iecc.com>
NNTP-Posting-Host: oboe.cs.berkeley.edu
In article <m0u10fA-001TNfC@ivan.iecc.com>,
John R Levine <johnl@iecc.com> wrote:
}
}> Anyone using a 3c509 successfully with 2.1? I can get no further
}> than mounting the root FS and death.
}
}Works fine for me. You probably have an I/O address conflict. Use the DOS
}config disk that comes with the card to move its I/O address.
It took a little doing to make it work for me; with the new 2.1 boot
you can override the choice of not only irq but port or maddr;
If you interrupt the boot, at the prompt where it says
Boot:
type
-dev ef0 irq=15 iobase=0x250
(or what ever values it was before you started the upgrade).
Once you install it on the disk, you can put the same line in
/etc/boot.default