Bug 602155
Summary: | broadcom.ko module missing from F-13 installer | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Adam Huffman <bloch> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | agospoda, anton, dougsland, dwmw2, gansalmon, itamar, jonathan, kernel-maint, larry, n.ahmedrobin, s.a.hartsuiker, vanmeeuwen+fedora |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-07-23 11:14:17 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Adam Huffman
2010-06-09 09:34:08 UTC
Does it work after installation? Are the required modules just missing from the install media? I haven't installed yet as there's a separate bug with partitioning (https://bugzilla.redhat.com/show_bug.cgi?id=601791) and I wanted to wait a couple of days to see if that could be fixed before wiping the disk. The tg3 module is definitely present, it just doesn't work with that particular NIC, though I haven't tried removing and reloading it yet. The broadcom.ko module is missing from the install image. Reassigning to anaconda. We add modules to the install image based on the modules being listed in the modules.networking file. If the broadcom.ko module is not being included, that's likely why. Doh, sorry -- I used to know how this worked... and I rejoiced when it was shifted to the kernel; I should have remembered. kernel-2.6.33.5-122.fc13 is building with this fixed. Not that it necessarily helps those with existing install images. It sounds like maybe broadcom.ko module (and possibly other phy modules) need to be added to the list of modules included in the installer initrd. I think that is correct. Switching component to anaconda. Sorry, I should read all the comments first. :-/ *** Bug 599712 has been marked as a duplicate of this bug. *** Fixed in 2.6.33.5-122.fc13 and 2.6.34-30.fc14 I installed 2.6.33.5-124.fc13 on this box. However, it still loaded the tg3 module for this NIC, not the broadcom one. When I removed and then re-loaded tg3, the NIC was detected. Adam, tg3 is the correct NIC driver. broadcom.ko is the driver for the PHY. The tg3 driver requires the broadcom driver and should automatically load it. Did you _need_ to remove and re-load tg3 before the NIC was detected and working properly? If so, please show your boot messages from _before_ you did so. Ah - thanks for the explanation. Wondered why I hadn't heard of it before... As I recall, yes I did need to remove and re-load it, though I won't have physical access to the machine until tomorrow. I'll try and check this for you then. Having just tried, I can report that with the -124 kernel, the NIC was detected properly and working at boot. There was no need to remove and re-load the module. I'm thinking of purchasing a Vostro 430 for CentOS 5. But sounds like this defect is in both Fedora and RedHat, so I expect it will also be in CentOS 5. Will the fix be in the RedHat libraries sometime soon ? TIA |