Description of problem:
I'm not quite sure this is the proper component for this bug, but I guess I'll
start here. This is a problem that I've been encountering since FC6, and with
my recent upgrade to F9, it still exists -- and may cause problems and confusion
for various users.
So I have the following NIC:
02:09.0 Ethernet controller: Davicom Semiconductor, Inc. 21x4x DEC-Tulip
compatible 10/100 Ethernet (rev 31)
Which out of the box, uses the 'tulip' driver. With this, I am able to get an
IP address, and working network -- for a few minutes. After a little while, the
link drops out, and nothing works.
NetworkManager: <info> (eth0): carrier now OFF (device state 8)
NetworkManager: <info> (eth0): device state change: 8 -> 2
NetworkManager: <info> (eth0): deactivating device.
For years I've had to drop 'tulip' into the /etc/modprobe.d/blacklist, which
will then cause the 'dmfe' module to be used -- and everything works again.
So, I'm wondering how we can go about fixing this so other people with this card
won't have to encounter the pain and suffering that is the tulip driver.
I have had the same problem - except that dmfe was automatically used for the Ethernet controller in Fedora 9. I did not realize this until after I discovered the solution - and supposed that the Tulip driver had also been used in the previous release. It was not until I upgraded to 22.214.171.124-170.2.24.fc10.i686 that the card lost the connection and I endured many hours of frustration going through configuration files until I finally stumbled on the simple solution at:
After looking at my backup of the old configuration files I realized that dmfe had been the default for the card in my earlier installation.
As many users have encountered this problem it may be a good idea to blacklist the Tulip driver by default in the next kernel release.
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
This is still a problem.
After upgrading my machine from Fedora 9 to 11, it loaded up both the tulip and dmfe drivers upon reboot and my network was unusable, as DHCP would timeout.
*** This bug has been marked as a duplicate of bug 236928 ***