home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!enterpoop.mit.edu!eru.mt.luth.se!lunic!sunic!corax.udac.uu.se!corax.udac.uu.se!ewerlid
- From: ewerlid@ida.docs.uu.se (Ove Ewerlid)
- Newsgroups: comp.os.linux
- Subject: The 3c503-ALPHA-DRIVER (WAS: [NET]: Problems with 0.99)
- Message-ID: <EWERLID.92Dec19032033@ida.docs.uu.se>
- Date: 19 Dec 92 02:20:33 GMT
- References: <1992Dec18.215333.28838@ultb.isc.rit.edu>
- Organization: University of Uppsala, Sweden
- Lines: 28
- NNTP-Posting-Host: ida.csd.uu.se
- In-reply-to: axi0349@ultb.isc.rit.edu's message of Fri, 18 Dec 1992 21:53:33 GMT
-
-
- On the 3c503 side this problem may be due to a problem
- I stumbled on. Since Donald Becker (who wrote the driver)
- seems to be away I might as well answer.
- (A similar message has already been sent to the net-channel.)
-
- The probe that detects the 3c503 card fails to properly check
- the shared memory. This means that shared memory is
- detected and given an address even though it is disabled by the
- onboard shared memory jumper. There are MSDOS 3c503 drivers that can
- use a 3c503 card with the shared memory disabled.
- So things may work great under MSDOS.
-
- This problem is detected by a header consitency check in the 3c503
- driver and the result are card restarts. In my case all headers
- had all bits set to all ones. E.g. the error status
- reported by the consistency check was all 0xff.
- (This may be different though.)
-
- THUS, check the memory jumper on the 3c503 card and
- make SURE it is positioned to select shared memory at an
- address that doesn't collide with something else.
- (I use 0xc8000.)
- On the 3c503 card I use the memory jumper is the one
- with 5 positions. The IO-base jumper has 8 positions.
- Disabled shared memory was indicated with the address 0
- printed on the PCB (Printed Circuit Board).
- (This may be different for you though.)
-