Bug 54196
| Summary: | Davicom ethernet identified as Tulip | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Ecmel Ercan <ecmel> | ||||
| Component: | kernel | Assignee: | Jeff Garzik <jgarzik> | ||||
| Status: | CLOSED ERRATA | QA Contact: | David Lawrence <dkl> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 9 | CC: | jsolomon, peterm | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i386 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2003-06-05 11:53:35 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Ecmel Ercan
2001-10-01 14:15:46 UTC
lspci output? Created attachment 33080 [details]
lspci
The tulip driver lists that PCI id as supported by the tulip driver, so that's what we use. Does that not work for you? It works, but after sometime (randomly) it stops working at all. I have to hard-reset the machine to get it working again. That would be a driver bug; assigning to the kernel. And dmfe does work ? dmfe works perfect for the last 9 months and working now in Roswell beta. The Dell Dimension 4300 (heavily advertised on UK TV) comes with
a Davicom DM9102 NIC when purchased in the UK as part of the
bundle (funnily, the NIC section of dell.co.uk only lists 3com
cards, but you get Davicom if you ask for the NIC to be bundled).
When I went through the 7.2 installer, it recognised it as
tulip and I duly got the symptoms the original poster described
("ifconfig eth0" reported many receive errors, the network card
would either not init at all on bootup, init at 1 *second* pings
to another local machine or init with plenty of receive errors).
I changed /etc/modules.conf to use dmfe instead of tulip and it
worked perfectly with no errors.
I would urge a rapid fix of this because Dell PCs are hit very,
very badly by this, at least in the UK.
Tip - there's a nice Tulip diag tool in the tulip 1.1.8 package
at http://sourceforge.net/projects/tulip/ - this was the only
"easy" way to actually find out what card I had without opening
the case up (yet again :-) ).
Just a note that this applies to Dell 8200's as well. We've bought them both in October and this month and both boxes had the same NIC as the 4300 that rkl.uk describes. A knowlegde base article should really be created that would match on "Dell 4300 8200 Davicom" that would explain the fix to this problem. In case you're wondering: Edit /etc/modules.conf. Replace the word "tulip" with "dmfe" and reboot. SmartStep 100D bundle from Dell includes this NIC as well. In a default 7.2 install, the NIC will ultimately fail. Message logs will report this during boot up... Feb 13 14:27:13 mailhub kernel: Linux Tulip driver version 0.9.15-pre6 (July 2, 2001) Feb 13 14:27:13 mailhub kernel: PCI: Found IRQ 11 for device 01:0a.0 Feb 13 14:27:13 mailhub kernel: tulip0: EEPROM default media type Autosense. Feb 13 14:27:13 mailhub kernel: tulip0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block. Feb 13 14:27:13 mailhub kernel: tulip0: Index #1 - Media 10baseT (#0) described by a 21140 non-MII (0) block. Feb 13 14:27:13 mailhub kernel: tulip0: Index #2 - Media 100baseTx (#3) described by a 21140 non-MII (0) block. Feb 13 14:27:13 mailhub kernel: tulip0: Index #3 - Media 10baseT-FDX (#4) described by a 21140 non-MII (0) block. Feb 13 14:27:13 mailhub kernel: tulip0: Index #4 - Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) block. Feb 13 14:27:13 mailhub kernel: tulip0: MII transceiver #1 config 3100 status 7809 advertising 01e1. Feb 13 14:27:13 mailhub kernel: eth0: Davicom DM9102/DM9102A rev 49 at 0xc8882000, 00:80:AD:7B:0A:98, IRQ 11. And eventually fail with... Feb 27 10:20:17 mailhub kernel: NETDEV WATCHDOG: eth0: transmit timed out Feb 27 10:20:17 mailhub kernel: eth0: 21140 transmit timed out, status fc540000, SIA ffffff49 00000000 00000000 00000000, resetting... Feb 27 10:20:17 mailhub kernel: eth0: transmit timed out, switching to 100baseTx-FDX media. Feb 27 10:20:25 mailhub kernel: NETDEV WATCHDOG: eth0: transmit timed out Feb 27 10:20:25 mailhub kernel: eth0: 21140 transmit timed out, status fc540000, SIA ffffff49 00000000 00000000 00000000, resetting... Feb 27 10:20:25 mailhub kernel: eth0: transmit timed out, switching to 100baseTx-FDX media. Feb 27 10:20:33 mailhub kernel: NETDEV WATCHDOG: eth0: transmit timed out Feb 27 10:20:33 mailhub kernel: eth0: 21140 transmit timed out, status fc540000, SIA ffffff49 00000000 00000000 00000000, resetting... Feb 27 10:20:33 mailhub kernel: eth0: transmit timed out, switching to MII media. Feb 27 10:20:35 mailhub kernel: eth0: Setting half-duplex based on MII#1 link partner capability of 0021. Feb 27 10:20:41 mailhub kernel: NETDEV WATCHDOG: eth0: transmit timed out Does this still occur, when the latest kernel errata rpm is installed? No response in several months. Closing as it seems to be fixed |