Red Hat Bugzilla – Bug 30818
kudzu not recognizing bcm5700
Last modified: 2014-03-16 22:19:36 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0; DigExt)
The installation program doesn't recognize bcm5700.
After installed RC2, kudzu couldn't recognize bcm5700 also.
However, I can manually load bcm5700.o driver and It worked fine.
Steps to Reproduce:
1. Install RC2
2. Run kudzu
3. Kudzu will not recognize bcm5700
Actual Results: Kudzu did not recognize bcm5700
Expected Results: Kudzu should recognize bcm5700 and allow for its
Here is the info from /proc/pci, so that you have the PCI IDs...
Bus 3, device 8, function 0:
Ethernet controller: PCI device 14e4:1644 (BROADCOM Corporation) (rev 16).
Master Capable. Latency=32. Min Gnt=64.
Non-prefetchable 64 bit memory at 0xfea00000 [0xfea0ffff].
Please file bugs against the correct product.
(i.e., don't file RC2 bugs against the public beta.)
In any case, this *should* currently work. What does the /etc/sysconfig/hwconf
We (Red Hat) should really try to fix this before next release.
I've tried this with the provided card; it worked OK once I booted a
kernel with the correct module. What exact version of kudzu do you have
installed, and what does your /etc/sysconfig/hwconf look like?
Is the bcm5700 listed in your /usr/share/kudzu/pcitable?
Created attachment 12024 [details]
Created attachment 12025 [details]
Created attachment 12026 [details]
What kernel are you running?
Created attachment 12027 [details]
I'm running on 2.4.2-0.1.19 kernel. This is a single processor server.
What happens if you remove the broadcom entry from /etc/sysconfig/hwconf
and re-run kudzu?
After I remove the broadcom entry from /etc/sysconfig/hwconf, kudzu is working.
What kernel was running on this machine the first time it was installed/kudzu
Basically, all I can guess that happened is that when kudzu first saw the
broadcom card, it didn't find the bcm5700 module for it, so it ignored it.
*** Bug 31070 has been marked as a duplicate of this bug. ***
Just tested with today's tree; it works OK.
The bits to recognize it in the installer have been committed to CVS; will
be in the next anaconda build.