>I started to look around for Ethernet-Cards, too. And what I found out is the
>On the one hand there are NE2000-cards available and on the other hand they sell
>what is called NE2000-compatible-cards. The first difference one sees is the price:
>The later ones only cost about 100 Marks here in Germany, while the first cost up
>to 600 Marks.
>Now my question: Will those chaep cards really work with Linux? Has anyone any
...from the Ethernet-HOWTO, which nobody bothers to read. Perhaps you should
get the full document, as it has a recomendation for cheap cards as well.
6 Possible Problems, Questions and Troubleshooting.
This section tries to answer any unresolved questions, and not so
common solutions to common problems.
6.01 Problem with NE2000 Clones -- "DMA address mismatch"
Is the chip a real NatSemi 8390? (DP8390, DP83901, DP83902 or DP83905)?
If not, some clone chips don't correctly implement the transfer
verification register. MS-DOS drivers never do error checking,
so it doesn't matter to them.
Are most of the messages off by a factor of 2?
If so: Are you using the NE2000 in a 16 bit slot?
Is it jumpered to use only 8 bit transfers?
The Linux driver expects a NE2000 to be a 16 bit slot. A NE1000 can
be in either size slot. This problem can also occur with some clones,
notably D-Link 16 bit cards, that don't have the correct ID bytes
in the station address PROM. [[ This should be fixed in pl12.]]
Are you running the bus faster than 8Mhz?
If you can change the speed (faster or slower), see if that
makes a difference. Most NE2000 clones will run at 16Mhz, but
some may not. Changing speed can also mask a noisy bus.
What other devices are on the bus?
If moving the devices around changes the reliability, then you
have a bus noise problem -- just what that error message was
designed to detect. Congratulations, you've probably found the
source of other problems as well.
6.02 Problem with NE2000 Clones -- Machine Hangs during Boot.
Problem: The machine hangs during boot right after the "8390..." or
"WD...." message. Removing the NE2000 fixes the problem.
Solution: Change your NE2000 base address to 0x360 (or 0x340 for
pl12 or later kernels.)
Reason: Your NE2000 clone isn't a good enough clone. An active
NE2000 is a bottomless pit that will trap any driver
autoprobing in its space. The other ethercard drivers take
great pain to reset the NE2000 so that it's safe, but some
clones cannot be reset. Clone chips to watch out for:
Winbond 83C901. Changing the NE2000 to a less-popular
address will move it out of the way of other autoprobes,
allowing your machine to boot.
Problem: The machine hangs during the SCSI probe at boot.
Solution: It's the same problem as above, change the
Problem: The machine hangs during the soundcard probe at boot.
Solution: No, that's really during the silent SCSI probe, and it's
the same problem as above.
Paul Gortmaker c/o Microelectronics and Materials Technology Centre.
Royal Melbourne Institute of Technology, GPO Box 2476V, Melbourne 3001,
Victoria, Australia. Ph (61) 3 660 2601. FAX (61) 3 662 1921.