Wireless Intersil Prism2.5 doesn't work in Feisty

Bug #76026 reported by Lennart Hansen
8
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

After updating to Feisty my Wireless Card didn't work.

It was however detected.

I found prism2_pci was preventing orinoco_pci from using my device.

After blacklisting prism2_pci in /etc/modprobe.d/blacklist it works!

lspci -vv

02:05.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01)
        Subsystem: Actiontec Electronics Inc Unknown device 0406
        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: 64, Cache Line Size: 32 bytes
        Interrupt: pin A routed to IRQ 9
        Region 0: Memory at f0000000 (32-bit, prefetchable) [size=4K]
        Capabilities: <access denied>

Revision history for this message
Andrew Jorgensen (ajorg) wrote :

I have the same problem only with prism2_cs. Perhaps linux-wlan-ng is very broken?

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for your bug report. As Feisty is moving quickly I am curious to know if this is still an issue with the latest kernel in Feisty. Please let us know. Thanks in advance.

Revision history for this message
Andrew Jorgensen (ajorg) wrote :

I at least still have this problem in Feisty. More specifically if the prism2_cs module is handling the card then wlan0 claims to not support the wireless extensions.

I don't know why linux-wlan-ng is in our kernel but it's completely broken. Or rather it's probably not broken but requires it's own tools to configure it as it always has.

orinoco_cs and hostap_cs both work to some degree. At the moment unless you need WPA orinoco is probably your best bet. If you need WPA hostap is the best but doesn't work with NM (because NM / wpa_supplicant chooses the wrong backend driver, wext, rather than hostap). orinoco works w/ NM but only supports WEP.

If prism2_* must still be included in our kernel the priority for prism-based cards should be orinoco, hostap, prism2.

Revision history for this message
Lennart Hansen (lahansen) wrote :

After updating today my setting was overwritten and I again had to add the blacklist.

Kernel : 2.6.20-9-generic

Thanks

Changed in linux-source-2.6.20:
assignee: brian-murray → nobody
status: Needs Info → Confirmed
Changed in linux-source-2.6.20:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
Revision history for this message
Tormod Volden (tormodvolden) wrote :

FYI, at least the linux-wlan-ng prism2_usb must be included in the kernel because it is the only driver to support the usb versions.

Revision history for this message
Matthew Buckett (buckett) wrote :

I have a very similar card to the original requestor (PCI)

00:09.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev
01)
        Subsystem: Actiontec Electronics Inc HWP01170-01 802.11b PCI Wireless Ad
apter
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV+ VGASnoop- ParErr- Step
ping- SERR+ FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort
- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 22
        Region 0: Memory at dffff000 (32-bit, prefetchable) [size=4K]
        Capabilities: [dc] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot
+,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

which on a defaults install is controlled by hostap_pci and doesn't work blacklisting prism2_pci and hostap_pci results in a working system.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.