From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040312
Description of problem:
There seems to be a problem optaining DHCP IPv4 addresses for the
2.6.* kernels in the Fedora Core 2 Test1. Giving the machine a
permanent IPv4-address works fine.
The netcard that I have is
01:09.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T
Subsystem: Dell Computer Corporation: Unknown device 8127
Flags: bus master, fast devsel, latency 64, IRQ 17
Memory at fe9fe000 (32-bit, non-prefetchable) [size=8K]
Expansion ROM at fea00000 [disabled] [size=16K]
Capabilities:  Power Management version 2
The b44 module loads just fine, and I do get a "Link is up".
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot a system with a BCM4401 card in a network with a DHCP server
Actual Results: Network startup, and getting a IP-address fails.
Expected Results: Network startup and getting an IP-address succesfull.
I have searched the mailing lists without any results. Please contact
me if you want a tcpdump of a service network start, or ifup eth0.
Seems to me like this problem is fixed in the FC2 release, i.e. kernel
2.6.5-1.358. However in RHEL 3 U2, kernel 2.4.21-15.ELBOOT the same
Could we please move the product tag?
David: please open a new bug instead; while the symptom might be the
same the cause most likely isn't and keeping the same bug for that
just makes things really confusing and messy.
Bug 123558 created. Also I think my it might be realted to bug 105787
this bug should be fixed in the final release btw...