Bug 220851
| Summary: | Wrong kernel module loaded for 3com 3CRWE154G72 PCMCIA wireless card | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jonathan Underwood <jonathan.underwood> | ||||||||
| Component: | system-config-network | Assignee: | Harald Hoyer <harald> | ||||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||||
| Severity: | medium | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 6 | CC: | notting, triage | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | All | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | bzcl34nup | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2008-04-04 10:41:57 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: | |||||||||||
| Attachments: |
|
||||||||||
Ah, actually, it seems the problem is due to the following auto generated entry in /etc/modprobe.conf: alias eth1 3c501 So it seems not a s-c-n problem, but rather whatever is generating the modprobe.conf entry .. pcmciautils? Reassigning to udev udev does not modify /etc/modprobe.conf Attach the output of 'kudzu -p'? The relevant part, with the corrected line in modprobe.conf: class: NETWORK bus: PCI detached: 1 device: eth1 driver: prism54 desc: "3Com Corporation 3com 3CRWE154G72 [Office Connect Wireless LAN Adapter]" network.hwaddr: 00:0d:54:a2:46:dc vendorId: 10b7 deviceId: 6001 subVendorId: 10b7 subDeviceId: 6001 pciType: 2 pcidom: 0 pcibus: 3 pcidev: 0 pcifn: 0 Created attachment 144844 [details]
Output of kudzu -p
When did that entry get added? I don't see how kudzu would add it. Bill, excuse my ignorance, but I'm not sure I understand your question in the previous comment. To recap, the automatically added entry to /etc/modprobe.conf was originally this: alias eth1 3c501 The output that I just sent was from running kudzu -p on the same system after I had changed the above line in /etc/modprobe.conf to read alias eth1 prism54 and disabled kudzu from running at boot and rebooted. I'm not sure what exactly generated the initial line in modprobe.conf though - the sequence of events that occur on inserting a pcmcia card are a mystery me, and no amount of googling is throughing up much documentation, alas. Let me know what I can do to debug further. Would it help if I removed the line from modprobe.conf, rebooted with the kudzu service started at boot? That would be good, yes - I'm just not seeing how kudzu would decide to write that, so I'm curious where it came from. So, we don't even ship the 3c501 module - there's no real way that kudzu could write a config for it. There is a reference to it in the module-info file included in system-config-network - assigning there for the moment. Created attachment 145000 [details]
Output of kudzu -p after removing alias line from modprobe.conf and rebooting
Also, after removing the eth1 line from modprobe.conf, rebooting with kudzu to run at boot, and then running system-config-network, this device is not listed in the "hardware" tab of system-config-network. When I then click "new" to add a new hardware device in s-c-n, select wireless, and select the device identified as "3come 3c501" I get the error: Command failed: /sbin/modprobe 3c501 Output: FATAL: Module 3c501 not found. So, it seems there are two (at least) bugs - s-c-n isn't properly figuring out the correct module from the hardware info, and also kudzu is somehow stopping the device being activated at boot. (NB. I believe this is a 16 bit pcmcia card, if that is of any relevance). Let me know if there's any more info I can provide. I have attached the output of lspci -vv in case that is of any use. Note also that I have tried booting with the kernel options pci=routeirq,assign -busses but that seems to have no effect on this issue. Created attachment 145002 [details]
Output of lspci -vv
why do you have to "add" at your HW tab? Because there is no automatically generated entry for the wireless card in s-c-n, presumably due to failure to recognize the card correctly. Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers I no longer have the hardware to test this, I'm afraid. Closing as WONTFIX therefore. |
Description of problem: When I plug in a 3com 3CRWE154G72 PCMCIA wireless card, the prism54 driver is (correctly) loaded. If I then start system-config-network and click on the hardware tab, click new and select the wireless card (identified in s-c-n as 3com 3c501), I get the following error message: Command failed: /sbin/modprobe 3c501 Output: FATAL: Module 3c501 not found However, if I add the following to /etc/modprobe.conf: alias eth1 prism54 when I reboot and start s-c-n, all is well and the card appears under the hardware tab correctly identified. Version-Release number of selected component (if applicable): system-config-network-1.3.95-1 How reproducible: Every time Steps to Reproduce: 1. Fresh install of FC-6 2. Install correct firmware in /lib/firmware 3. Insert 3com card 4. start s-c-n 5. Attempt to add the card under the hardware tab Actual results: Command failed: /sbin/modprobe 3c501 Output: FATAL: Module 3c501 not found Expected results: Card is correctly detected Additional info: lspci -vv output for this card: 03:00.0 Network controller: 3Com Corporation 3com 3CRWE154G72 [Office Connect Wireless LAN Adapter] (rev 01) Subsystem: 3Com Corporation 3com 3CRWE154G72 [Office Connect Wireless LAN Adapter] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency: 80 (2500ns min, 7000ns max), Cache Line Size: 128 bytes Interrupt: pin A routed to IRQ 11 Region 0: Memory at 36000000 (32-bit, non-prefetchable) [size=8K] Capabilities: [dc] Power Management version 1 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Am not sure if this is problem is really with s-c-n, or udev, or hal, or pcmciautils or what, so, thought I'd start here :)