Prism 2.5 Wireless Card not recognised as a wireless device

Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at http://wiki.ubuntu.com/DebuggingKernelProblems . Thanks in advance!

uname -a -> "Linux ubuntu 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux"

Output of dmesg

lspci -vvnn

And as a sidenote: On Edgy this card works "out of the box"

And here are those three command run on Edgy:

http://www.kauhajoki.fi/~peti/log.txt

It seems to work with the 7.04 live cd when I first manually remove all the wireless modules. That is "orinoco, orinoco_pci, prism2_pci, hostap and hostap_pci" and after that manually load hostap_pci again. After that I manually edit /etc/network/interfaces -file and do a "ifdown wlan0 && ifup wlan0".

And some more investigation. I removed old kernel-versions completely (Edgy's 2.6.17-10 and 2.6.17-11) and after restarting WLAN wouldn't work with any of the drivers delivered with Feisty. Then I shut down the computer and restarted and the card worked. Then I restarted and card wouldn't work. Once again I shut down and restarted and it worked.

So something weird is going on. Don't know if it's just my hardware wanting to give up or what. I'm guessing that the card isn't properly reset during a restart or similar.

I also got same problem with this wireless.

 uname -a
 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux

I have this problem as well.
When I first installed Feisty it came with this kernel Ubuntu, kernel 2.6.17-10-generic
That kernel detected the wireless card as eth1 and sometimes it wouldn't detect the ethernet driver.
After upgrading to the next kernel release I noticed that it was detected as wlan0 but that it could no longer
connect to any wireless AP's and didn't respond to iwlist scan.

My working solution has been to utilize the 2.6.17-10 kernel for times I want to utilize wifi, but some change that happened with 2.6.17-11 caused it to quit working, even though it was never detected by Gnome wifi manager and indeed that wasn't installed and still doesn't appear to work.

I thought it might be helpful if I added the information from the kernel in which wifi works the 2.6.17-10 generic. So here again are the two files. Starting with the lspci

Here is the dmesg from the working kernel. I'm not sure if there is any difference between them.

I noticed that running lspci -vvnn it was saying access denied for the prism0 capabilities, so I ran it as root and got this output from the 2.6.17.10 kernel.

01:0d.0 Network controller [0280]: Intersil Corporation Prism 2.5 Wavelan chipset [1260:3873] (rev 01)
        Subsystem: Fujitsu Limited. Unknown device [10cf:1169]
        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 11
        Region 0: Memory at e0300000 (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-

Here is the lspci from the version in which it is not able to scan and/or detected as a wireless.
I see no difference in the output.

01:0d.0 Network controller [0280]: Intersil Corporation Prism 2.5 Wavelan chipset [1260:3873] (rev 01)
        Subsystem: Fujitsu Limited. Unknown device [10cf:1169]
        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 11
        Region 0: Memory at e0300000 (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-

Hi,

This bug was opened a while ago but there hasn't been any recent activity. Just curious if this is still an issue with the latest Hardy Heron 8.04 Alpha release which is currently under development and contains an updated version of the kernel. It would be helpful if you could test the latest Hardy Alpha release: http://www.ubuntu.com/testing . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. We'll keep this report open against the actively developed kernel but against 2.6.20 this will be closed. Thanks.

Hi,

You need to rely on someone else testing this, because the laptop I used is
now broken, so I cannot test it.

On Wed, Mar 12, 2008 at 1:30 AM, Leann Ogasawara <email address hidden> wrote:

> Hi,
>
> This bug was opened a while ago but there hasn't been any recent
> activity. Just curious if this is still an issue with the latest Hardy
> Heron 8.04 Alpha release which is currently under development and
> contains an updated version of the kernel. It would be helpful if you
> could test the latest Hardy Alpha release:
> http://www.ubuntu.com/testing . You should be able to then test the new
> kernel via the LiveCD. If you can, please verify if this bug still
> exists or not and report back your results. We'll keep this report open
> against the actively developed kernel but against 2.6.20 this will be
> closed. Thanks.
>
> ** Also affects: linux (Ubuntu)
> Importance: Undecided
> Status: New
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: linux-source-2.6.20 (Ubuntu)
> Status: Confirmed => Won't Fix
>
> --
> Prism 2.5 Wireless Card not recognised as a wireless device
> https://bugs.launchpad.net/bugs/91385
> You received this bug notification because you are a direct subscriber
> of the bug.
>

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Looking at the attachments in this bug report, I noticed that "dmesg.log" was flagged as a patch. A patch contains changes to an Ubuntu package that will resolve a bug, however that attachment doesn't appear to be one. Subsequently I've unchecked the patch flag for it. In the future keep in mind the definition of a patch. Thanks!

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.

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.