tulip driver doesn't work for Davicom

I ran into the same issue when upgrading from 5.10 to Dapper. I added dmfe to /etc/modules and "blacklist tulip" to /etc/modprobe.d/blacklist and rebooted and all was well. I actually ran into this same problem with the current Gentoo release also so yinz are all pulling from the same defective device database.

Same problem here. System was loading both tulip and dmfe. Just blacklisting tulip solves the problem.

I'm using Dapper with all the updates, but problem is present since flight 5, first dapper I tried.

Same problem here with Davicom Semiconductor ethernet hardrware.

Adding "blacklist tulip" to /etc/modprobe.d/blacklist and rebooting solved the problem.

I was testing some cards for Bug #82927 including a Davicom DM9102AF PCI adapter with on Gutsy with kernel 2.6.22-14-generic. The card functioned immediately without additional intervention.

According to the syslog it used
dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)

This bug has had no activity for a considerable period. This is a check to see if there is still interest in investigating this bug report.
It appears to have been corrected at or before Gutsy.

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

hi, when i reboot my machine all times tulip and dmfe load, but i have tulip on blacklist on /etc/modprobe.d/blacklist.conf

maximi89@Maximiliano:~$ cat /etc/modprobe.d/blacklist.conf
# This file lists modules which will not be loaded as the result of
# alias expansion, with the purpose of preventing the hotplug subsystem
# to load them. It does not affect autoloading of modules by the kernel.
# This file is provided by the udev package.

# This directive blacklists all devices which are members of the display class.
# It has the main effect of preventing udev from autoloading the fb drivers.
# vendor, device, subsystem_vendor, subsystem_device, class, class, class
install pci:v*d*sv*sd*bc03sc*i* /bin/true

# evbug is a debug tool and should be loaded explicitly
blacklist evbug

# these drivers are very simple, the HID drivers are usually preferred
blacklist usbmouse
blacklist usbkbd

# replaced by e100
blacklist eepro100
blacklist tulip

# replaced by tulip
blacklist tulip
blacklist de4x5

# replaced by tmscsim
blacklist am53c974

# watchdog drivers should be loaded only if a watchdog daemon is installed
blacklist acquirewdt
blacklist advantechwdt
blacklist alim1535_wdt
blacklist alim7101_wdt
blacklist booke_wdt
blacklist cpu5wdt
blacklist eurotechwdt
blacklist hpwdt
blacklist i6300esb
blacklist i8xx_tco
blacklist ib700wdt
blacklist ibmasr
blacklist indydog
blacklist ixp2000_wdt
blacklist ixp4xx_wdt
blacklist it8712f_wdt
blacklist iTCO_wdt
blacklist machzwd
blacklist mixcomwd
blacklist mpc8xx_wdt
blacklist mpcore_wdt
blacklist mv64x60_wdt
blacklist pc87413_wdt
blacklist pcwd
blacklist pcwd_pci
blacklist pcwd_usb
blacklist s3c2410_wdt
blacklist sa1100_wdt
blacklist sbc60xxwdt
blacklist sbc7240_wdt
blacklist sbc8360
blacklist sbc_epx_c3
blacklist sc1200wdt
blacklist sc520_wdt
blacklist scx200_wdt
blacklist shwdt
blacklist smsc37b787_wdt
blacklist softdog
blacklist w83627hf_wdt
blacklist w83697hf_wdt
blacklist w83877f_wdt
blacklist w83977f_wdt
blacklist wafer5823wdt
blacklist wdt285
blacklist wdt977
blacklist wdt
blacklist wdt_pci

here i'm needed to make:
rmmod tulip dmfe
modprobe dmfe

and when i put this commands i get "Operation not Supported"...

maximi89@Maximiliano:~$ uname -a
Linux Maximiliano 2.6.29-1-686 #1 SMP Fri Apr 17 14:35:16 UTC 2009 i686 GNU/Linu...

Without any change when reboot:

maximi89@Maximiliano:~$ sudo ethtool -i eth0
driver: tulip
version: 1.1.15-NAPI
firmware-version:
bus-info: 0000:01:0a.0

maximi89@Maximiliano:~$ sudo mii-tool
eth0: negotiated 100baseTx-FD, link ok

maximi89@Maximiliano:~$ sudo mii-diag
Using the default interface 'eth0'.
Basic registers of MII PHY #1: 1000 782d 0181 b841 01e1 4de1 0001 0000.
 The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
 Basic mode control register 0x1000: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
 Your link partner advertised 4de1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD 10baseT, w/ 802.3X flow control.
   End of basic transceiver information.