Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 3453 - Tulip-based network cards are disabled
Tulip-based network cards are disabled
Status: CLOSED DUPLICATE of bug 2744
Product: Red Hat Linux
Classification: Retired
Component: netcfg (Show other bugs)
i386 Linux
low Severity low
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1999-06-14 09:56 EDT by nrhudy
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-06-14 13:32:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description nrhudy 1999-06-14 09:56:51 EDT
I have noticed with all users running Hedwig that some
network cards based off the Tulip driver (most notably
LinkSys EtherFast cards) do not function.  This is
characterized by a lack of network card initialization at
startup, followed by an inability to open eth0 (and the
message "Delayed eth0 initialization").  In addition to
that, issuing "insmod tulip" returns only that the device is
busy and does not elaborate.  Both the standard tulip.c
within the kernel and the LinkSys-provided tulip.c have been
tested, and both have returned the same results.  The only
conclusion that I can arrive at is that Hedwig contains some
sort of bug which interferes with the operation of
Tulip-based cards; it is also notable that such activity is
not present in Apollo.
Comment 1 nrhudy 1999-06-14 09:59:59 EDT
By the way, I forgot to mention that I have been reading reports of
similar happenings on LinkSys mailing lists and the like, if that
helps any.
Comment 2 Jeff Johnson 1999-06-14 13:32:59 EDT
This appears to be the same issue as #2744, so I'm duplicating

*** This bug has been marked as a duplicate of 2744 ***

Note You need to log in before you can comment on or make changes to this bug.