This is not specifically a Linux issue. Neither Windows XP or Linux would fully recognise that I had the CNet PRO200WL in PCI Slot number 3. Linux partly recognised that the card was present, and SuSEconfig would even allow me to configure the network card. However, the `dmfe' driver would not 'find' the CNet PRO200WL. As a result `eth0' would fail to be established. The `tulip' driver can also be used with the CNET PRO200WL, but `tulip' also could not find the CNET card. Windows XP repeatedly crashed when trying to access the CNet PRO200WL.
The solution was to move the CNET PRO200WL to PCI slot number 5, the very `bottom' PCI slot available to me. Incidentally, on the ASUS A7V333 motherboard, I had forced the IRQ of Slot 1/5 to be `10'. Given some of the comments on the A7V motherboard support sites, I suspect the A7V333 motherboard has a lot of problems with IRQ conflict.
Sometimes either the Ethernet card or my ADSL router/modem does not seem to be automatically recognised during SuSE system boot. As a result, the Internet is not accessible from my computer, even though all the appropriate connection lights on my ADSL modem have turned green. If this has happened, `re-configuring' the Ethernet card seems to rectify the situation. This is done by using YaST2 `Network Devices -> Network Card'. I then `change' my already configured ethernet card. Press the `edit' button, but do not actually change anything before pressing the `next' button. Then press `finish', and the network card and network access will be re-started.
Alternatively, as root, type in the command