home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.bsd
- Path: sparky!uunet!mcsun!Germany.EU.net!news.netmbx.de!zrz.tu-berlin.de!math.fu-berlin.de!hrz.tu-chemnitz.de!wutcd
- From: wutcd@chemnitz.guug.de (Joerg Wunsch)
- Subject: Re: [386BSD] Ethernet problem
- Message-ID: <wutcd.716231452@hadrian>
- Sender: bin@hrz.tu-chemnitz.de (Owner of all binaries)
- Organization: tu-chemnitz
- References: <18mo7tINN71h@usenet.INS.CWRU.Edu>
- Date: Fri, 11 Sep 1992 17:10:52 GMT
- Lines: 24
-
-
- Hi,
- seems to be a problem for a FAQ, i guess. Of course, the kernel could
- accept only that h/w it knows about. If _you_ don't know which kind
- of card your Ethernet adapter is compatible to, why do you suspect
- the tiny kernel would make this better? The four drivers included in
- the kernel make some tests during the probe routines in autoconfig stuff,
- thus they (hopefully) will find the boards the're written for. But, if
- you are using a packet driver on DOS, can't you configure out what this
- board is related to??? If you find it, configure your card the way
- described in INSTALL.NOTES, i.e. jumpering the correct IRQ, I/O address,
- and (if available) shared memory address. If your card is _really_ com-
- patible to one of the four, the drivers should probe it okay. If not,
- find a running 386BSD, write the device driver for your card:-)
- Sorry, but this would be the only way (except buying one of the supported
- ones).
-
- J"org
-
- --
- J"org Wunsch, TCD GmbH Dresden, R"ahnitzgasse 18, D-O-8060 Dresden
- \ ~.~.
- joerg_wunsch%bonnie@hadrian.hrz.tu-chemnitz.de \ ~ | ~
- voice: +49-351-5965 137 \ ===
-