wg511 pccard not loaded (regression: dapper -> edgy)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Fix Released
|
Medium
|
|||
linux-source-2.6.17 (Ubuntu) |
Fix Released
|
High
|
Ben Collins |
Bug Description
I have a Netgear WG511v1 wifi PC Card that worked with dapper but does not work with edgy - the module (prism54) is not loaded, the device has no entry in lspci (lspcmcia gives: 'CardBus card -- see "lspci" for more information')
I am currently running the latest version of edgy and have tested this with the dapper (worked) and knot 2 (didn't work) live CDs. This is all on a Thinkpad R30 with the 'acpi=noirq' kernel option (to enable boot).
on dapper, lspci shows:
0000:02:00.0 Network controller: Intersil Corporation Intersil ISL3890 [Prism GT/Prism Duette] (rev 01)
Here is a snippet of the dmesg output on dapper:
[4294818.047000] Loaded prism54 driver, version 1.2
[4294818.047000] PCI: Enabling device 0000:02:00.0 (0000 -> 0002)
[4294818.048000] eth1: uploading firmware...
...
[4294819.055000] eth1: firmware version: 1.0.4.3
[4294819.055000] eth1: firmware upload complete
[4294820.925000] eth1: resetting device...
[4294820.925000] eth1: uploading firmware...
[4294821.020000] eth1: firmware version: 1.0.4.3
[4294821.020000] eth1: firmware upload complete
[4294821.273000] eth1: interface reset complete
Under edgy, loading the module after boot doesn't seem to remedy the problem - dmesg only gives: 'Loaded prism54 driver, version 1.2' (no firmware loaded and no lspci entry besides).
I suspect this relates to changes in udev and perhaps some kernel changes, but am not sure where to look next (I tried changing some udev scripts and their order to no avail).
Changed in linux: | |
status: | Unknown → Confirmed |
Changed in linux-source-2.6.17: | |
assignee: | nobody → ben-collins |
status: | In Progress → Fix Committed |
Changed in linux: | |
status: | Confirmed → Rejected |
Changed in linux: | |
status: | Invalid → Fix Released |
Changed in linux: | |
importance: | Unknown → Medium |
Ok, I've attached some more info. At this stage I'm thinking it is kernel-related: firmware is not being loaded (from: /lib/firmware/ 2.6.17- 10-generic/ isl3890) and the device not being enabled, despite the same module version.
I also found some confirmation of 2.6.17+ issues here: http:// www.prism54. org/punbb/ viewtopic. php?pid= 6624