Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 123435 - BCM4401 doesn't work
BCM4401 doesn't work
Status: CLOSED DUPLICATE of bug 123558
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Burke
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2004-05-18 11:40 EDT by David Juran
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:03:16 EST
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 David Juran 2004-05-18 11:40:27 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.2)

Description of problem:
Could we please have the fix from bug 105787 incorporatded into RHEL 3?

Version-Release number of selected component (if applicable):
kernel 2.4.21-15ELBOOT

How reproducible:

Steps to Reproduce:
1. The network interface doesn't work

Additional info:
Comment 1 Suzanne Hillman 2004-05-20 14:37:57 EDT
This is kernel, not distribution.
Comment 2 Dave Jones 2004-06-10 07:17:20 EDT
This one ?

diff -urNp linux-753/drivers/net/b44.c linux-850/drivers/net/b44.c
--- linux-753/drivers/net/b44.c
+++ linux-850/drivers/net/b44.c
@@ -870,6 +870,7 @@ static void b44_tx_timeout(struct net_de
+   b44_enable_ints(bp);
Comment 3 David Juran 2004-06-17 11:07:56 EDT
No, that fix didn't cut it )-:

ifconfig eth0 still fails with the error message
SIOCSIFFLAGS: Device or resource busy

Also, seems like I managed to report this bug twice, thus I'm marking
this one as a dup of the other one...

*** This bug has been marked as a duplicate of 123558 ***
Comment 4 Red Hat Bugzilla 2006-02-21 14:03:16 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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