Orinoco_pci affected by re-enabled prism2 drivers

[ChristofferS]

Using edgy here.

From this bug https://launchpad.net/distros/ubuntu/+source/wpasupplicant/+bug/37396

I learned that I had to do the following to get my orinoco_pci wireless card to work:

$ sudo modprobe -r orinoco_pci
$ sudo modprobe -r hostap_pci
$ sudo modprobe -r prism2_pci
$ sudo modprobe orinoco_pci

My wireless card:

02:02.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01)

[Christoph Wolk (spikespiegel-gmx)]

Similar here, with the same wireless card. I haven't tried these steps yet, but I get wireless with 2.6.17-8, and none with 2.6.17-10.

[Michael R. Head (burner)]

My T30 has a MiniPCI-based wireless card and I have to do the same to get a functioning wireless connection.

[Mark Florian (markrian)]

Me too - Netgear MA311 wireless card, got to do the whole rmmod/modprobe malarkey.

[Sitsofe Wheeler (sitsofe)]

Just found this after an upgrade the other day too. In the short term you can probably add prism2_pci to /etc/modprobe.d/blacklist if you are already using orinoco_pci.

[Sitsofe Wheeler (sitsofe)]

This is in fact a duplicate of Bug 62685 (only difference is that orinoco is being masked rather than hostap)

[Michael R. Head (burner)]

Bug 62685 was about a problem with the hostap driver. That problem being that it no longer works. This problem is not connected to that one. There is something in common, though. In order to get the hostap driver to drive the hardware, orinoco must be blacklisted. However, once orinoco (and prism2) are blacklisted, hostap still doesn't work.

In this bug, we have the simple problem that the newly built prism2 driver masks the (working) orinoco driver.

[JasonVenkiteswaran (jjvenky)]

Allow me to reconfirm on an older Compaq Presario 2100:
Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01)

$ sudo modprobe -r orinoco_pci
$ sudo modprobe -r hostap_pci
$ sudo modprobe -r prism2_pci
$ sudo modprobe orinoco_pci

Works like a charm after this in edgy. The blackilist works too.

Perhaps the details of lshw could be used to check whether the prism2_pci diver should be used. Note that with the prism2_pci driver the output of lshw does NOT have a "serial" field. With the orinoco_pci driver it does.

[Aualin (aualin-deactivatedaccount)]

Mark Florian:
i got the exact same network card as you! can you please say what commands you run? As those is not working with mine...

[Mark Florian (markrian)]

$ sudo rmmod prism2_pci hostap_pci hostap orinoco_pci orinoco hermes
$ sudo modprobe orinoco_pci

But a better solution is to create a file like in /etc/modprobe.d/blacklist-for-ma311 and put the following lines in it:

# This makes sure only orinoco/_pci gets loaded for my prism2.5 card
blacklist prism2_pci
blacklist hostap_pci
blacklist hostap

This makes sure only the orinoco drivers are loaded and there are no conflicts over the hardware, so everything works at boot.

[ChristofferS (ubuntu-curo)]

This affects 2.6.19 as well. Is it possible to fix this for feisty?

[JasonVenkiteswaran (jjvenky)]

This problem still affects Feisty Fawn Herd 2.

[K.Mandla (k.mandla)]

I found that by blacklisting prism2_cs in /etc/modprobe.d/blacklist my WPC11 works again with Herd 3.

[Matthew Garrett (mjg59)]

prism2_cs has been disabled for the next feisty upload - we'll look at the _pci situation. Could people please describe the exact way in which it doesn't work?

[ChristofferS (ubuntu-curo)]

If prism2 is enabled, the prism2_cs driver gets loaded when orinoco_pci cards are used.

The wireless connection does work with this driver.

The correct driver is orinco_pci.

[Michael R. Head (burner)]

This continues to be a problem in feisty. If prism2_pci isn't blacklisted somewhere in /etc/modprobe.d, the prism2_pci driver loads, takes over my hardware and prevents orinoco_pci or hostap_pci from controlling the hardware. I must manually "sudo modprobe -r prism2_pci && sudo modprobe -r orinoco_pci && sudo modprobe -r hostap_pci && sudo modprobe orinoco_pci" to get wireless to work again.

[Ben Collins (ben-collins)]

We seem to have conflicting reports on this range of chipsets in that prism2_pci, hostap_pci and orinoco_pci are all said to work better for different ones.

Can everyone affected please attach (do not paste into comment) the output of "lspci -vv" and "lspci -vvn", make sure to name the file something like lspci-vv-<yourname>.txt

Thanks

[Sitsofe Wheeler (sitsofe)]

Ben:

It's worth noting that some cards will work work with all three drivers. However, the prism2_pci drivers can only be configured using their own special utilities (I don't believe they got around to supporting iwconfig and friends). The hostap_pci drivers used to work as well as the orinoco drivers (see bug #89464 for why that isn't the case any more) other than a small naming difference (although rumour has it they don't suspend to RAM to well). The hostap_pci driver also supports WPA. The orinoco_pci driver can't do hostap mode but has been in the kernel forever and seems to be the default on other distributions.

[Adam (adam.russell)]

Netgear MA311 here on Feisty. Got my card working just by blacklisting prism2_pci and prism2. Couldn't figure out how to get the prism2 module working to blacklist the other ones instead. I'm too used to the interfaces file. =)

[Stani (stani)]

I had the same problem with a Thinkpad X30. By blacklisting I got it working again:

blacklist prism2
blacklist prism2_pci
blacklist hostap_pci
blacklist hostap

Hopefully this get fixed by default in Feisty.

[Michael R. Head (burner)]

I think we've provided the info needed at this point.

[jsteinman (johnsteinman)]

Attached is a tar file containing output requested. I un-blacklisted the "prism2_pci" captured the output from "lspci -vv" and "lspci -vvn" than blacklisted the "prism_pci", rebooted and captured the output again.

tar vtf lspic_output-jsteinman.tar
-rw-r--r-- jsteinman/jsteinman 6545 2007-03-15 11:30 lspci-vv-jsteinman-after-blacklist
-rw-r--r-- jsteinman/jsteinman 6545 2007-03-15 11:25 lspci-vv-jsteinman-before-blacklist
-rw-r--r-- jsteinman/jsteinman 5340 2007-03-15 11:30 lspci-vvn-jsteinman-after-blacklist
-rw-r--r-- jsteinman/jsteinman 5340 2007-03-15 11:25 lspci-vvn-jsteinman-before-blacklist

[Stani (stani)]

I reinstalled Ubuntu feisty on my laptop and did a dist-upgrade. The wireless device now shows up in system>network without blacklisting but the network-manager doesn't show any available wireless network. Blacklisting the prism2 or hostap drivers doesn't help either. Anyone has a solution to get wireless working again?

[Tormod Volden (tormodvolden)]

Stani, I think that might be a network-manager problem, see bug #82335.

[Brett Clippingdale (brett-clippingdale)]

Stani, have you tried blacklisting the prism2 *and* the orinoco drivers?

I added these to /etc/modprobe.d/blacklist on my T30 and have wireless working (some nits, but it works, WPA and all):

blacklist orinoco
blacklist orinoco_pci
blacklist hermes
blacklist p80211
blacklist prism2_pci

If you have a prism card, also look into upgrading the firmware:
http://linux.junsun.net/intersil-prism/

[Stani (stani)]

Tormod,
It does not seem to be a network-manager problem. I killed the network manager and restarted network but it didn't help

Brett,
I tried it before and now again with your blacklist so that the hostap gets loaded, but it doesn't work unfortunately. Before it was working, so I prefer not to upgrade the firmware unless that is the recommended way to get this working.

Is everybody else being able to use the prism2.5 wavelan with blacklisting? I don't. "iwlist eth0 scan" gives "no scan results".

[Sitsofe Wheeler (sitsofe)]

stani:
My network card is a "Intersil Corporation Prism 2.5 Wavelan chipset (Netgear MA311)". The hostap drivers are currently broken for me (see bug #89464 ) but the orinoco drivers seem to work well.

[Sitsofe Wheeler (sitsofe)]

There is also a report that the firmware had to be updated on prism cards before scanning worked over in Bug #94885 .

stani:
What is the output of
dmesg | grep -i firm
shortly after boot?

[Jonathan Clarke (jooooooon)]

Cards that should use the orinoco_plx driver are also affected by this bug.

I have a 3Com Corporation 3CRWE777 PCI(PLX) Wireless Adaptor [Airconnect] (rev 02), which is a PCMCIA to PCI adapter based card. Similar to above descriptions, prism2_plx driver are automatically loaded instead of the orinoco_plx.

The requested output follows!

[John Williams (jswillms)]

Still fails on Feisty RC. Upgraded T30 Edgy (Prism pci card) today using upgrade-manager -d. Asked to keep or remove blacklist. Said remove. Reboot to no network. Re-did the blacklist of prism2_pci. Works.

[dmc (daniel-coll)]

I've Upgraded to Feisty using 'upgrade-manager -c -d' my IBM T30 minipci card, prism2.5 chip , removed blacklist, Reboot and no wifi network, Then blacklist:
prism2
prism2_pci
hostap
hostap_pci
And have wifi Working, but MN still half functionality. I can't see different hotspots/signal strength neither actual connection. Is where any configuration to have NM full working.

[Michael R. Head (burner)]

Hm... I have the same setup (T30 model 2366-97U) and NM is working here -- I can fully browse hotspots and see the signal strength (and have for quite a few releases now). The only thing is that some times the card is a bit slow and doesn't report the scanning data fast enough. Can you ever browse and sometimes not, or are you never able to browse?

You may want to check out /var/log/syslog or $HOME/.xsession-errors, which may have some output from the network-manager daemon or nm-applet program.

[dmc (daniel-coll)]

Sorry!! It was my fault! NM is working ok, I didn't check the roaming option.

On 4/21/07, Michael R. Head <email address hidden> wrote:
> Hm... I have the same setup (T30 model 2366-97U) and NM is working here
> -- I can fully browse hotspots and see the signal strength (and have for
> quite a few releases now). The only thing is that some times the card is
> a bit slow and doesn't report the scanning data fast enough. Can you
> ever browse and sometimes not, or are you never able to browse?
>
> You may want to check out /var/log/syslog or $HOME/.xsession-errors,
> which may have some output from the network-manager daemon or nm-applet
> program.
>
> --
> Orinoco_pci affected by re-enabled prism2 drivers
> https://bugs.launchpad.net/bugs/63989
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Daniel Coll
Cel. (011) 15-5470-4354
Nextel 214*2823

[koshari (holto2go)]

its a pity this bug hasnt been fixed for edgy yet, and very sad that it has migrated across to feisty.

[Jeff Trull (jetrull)]

I continue to suffer from this problem (wireless drivers stepping on each other). In my case it's prism2_pci and hostap_pci (hostap being preferred due to WPA support). Note that when both are loaded neither one operates, and I have no wireless whatsoever.

The device is 1260:3873, "Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01)"

I've experienced this since Dapper.

[rlyacht (robt)]

I hit this problem when moving from 2.6.17-10 to 2.6.17-11, and I've had to stay on the former kernel since then.

My machine is a Thinkpad T30 (2366-92U). I had been successfuly using the prism2_pci driver. I have attached the results of sudo lspc -vv

Please let me know if I can provide further information, or if there' s something I can test.

I found that if I modprobe -r prism2_pci and modprobe orinoco_pci then ifconfig will at least show my wireless device (eth1). But it still doesn't work.

[John Williams (jswillms)]

I upgraded from feisty to gutsy using the upgrade manager. No wireless upon reboot on my T30 with the Prism card. It sees my access point, and shows signal in NM but does not accept the web encryption key and will not assign an IP address. Double checked to make sure it is correct key. It is. hostap_pci is loaded...

[Brent Culp (brentculp)]

John WIllilams: was your wireless card detected at all after upgrade?

Similar to the your case I upgraded via update manager to gutsy I had no wireless card detection on A31p with the Prism card. Was running with encryption using Orinoco before, and blacklists remained unchanged with the upgrade. Notable though that there was no hostap present at all after the upgrade. Was able to get the card detected at least using the win driver and ndiswrapper, to the same point as above, i.e. signal and access points visible in NM but no successful connection to the network. Thinking it was just 'me' , I did a clean install of fiesty, added blacklist, got wireless running with no issues, upgraded again to gutsy, and end with the same problem. At least it's consistent...

Appreciate any suggestions and will watch for feeback on your case.

[John Williams (jswillms)]

Got it working!

I rebooted to 2.6.17-10 and finally got NM to accept the WEP key and it works. Mine is the IBM T30 with the Intersil Prism 2.5 pci card. So I rebooted to 2.6.22-16 and it works there also. ??? Not sure what is going on. On my router, I run 128 bit enc. I used the 64/128 Hex key option, typed in the hex string, and selected shared key and it worked.

So, seems to be working fine for me now...

[Brent Culp (brentculp)]

Thanks. Finally got the card detected and connection to the network also with 128bit encryption. I stumbled on <a href="/bugs/126220" title="[regression] wireless card does not work in gutsy, ma311">bug #126220</a> explaining that orinoco_pci was dropped in the Gutsy upgrade. So far as I understand, the workaround I used before blacklisted the other drivers, leaving orinoco_pci to handle the card, explaining why I had no detection aftter the Gutsy upgrade. So I un-blacklisted hostap, which now detects the card (as WIFI) and handles the encrypted connection ok so far. I have a second wireless entry now in Network Manager (inactive?) as I seen reported elsewhere andI have no fancy network monitors, and cannot view available networks, signal strength, etc in the top panel as I could in Fiesty, but at least it's functional.

[John Williams (jswillms)]

Brent,

You should be able to add the NM-applet to the top bar. That gives a rudimentary signal bar monitor.

Glad you got it working. I am having an occasional crash in hostap_pci upon resume. Driver still sounds a bit unstable. Good thing is the Ubuntu community will fix it quickly. Much better than the "other" OS...

John

[Tormod Volden (tormodvolden)]

I am closing the 2.6.22 task, since that kernel doesn't even ship with orinoco_pci drivers.

[Leann Ogasawara (leannogasawara)]

The Hardy Heron Alpha series 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 bug against 2.6.20 and 2.6.17 this will be closed. Thanks.

[Brent Culp (brentculp)]

In Hardy Alpha 6 (live cd) I have no issues -- wireless networking was functional on boot up without any configuration. Later I upgraded my 7.10 partition to 8.04 and also no trouble at all.

[Stani (stani)]

Hi,
In the hope wireless would work again on my IBM Thinkpad X30, I just did a fresh install of the latest Ubuntu Hardy Alpha. Unfortunately nm-applet does not show the wireless networks.

Ubuntu boots up with a spinning progress bar (moving left and right without progress) and hangs during ten seconds. Afterwards Ubuntu boots up normally. If I blacklist the hostap* drivers the hanging does not occur.

Wireless worked in Dapper before. How can I get this working again?

Thanks in advance,
Stani

PS Here is some information:
$ uname -a
Linux x30 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 GNU/Linux
$ cat /proc/version_signature
Ubuntu 2.6.24-12.22-generic
$ iwconfig
lo no wireless extensions.

eth1 no wireless extensions.

wifi0 IEEE 802.11b ESSID:" O'Reilly's" Nickname:""
          Mode:Managed Frequency:2.452 GHz Access Point: None
          Bit Rate:2 Mb/s Sensitivity=1/3
          Retry short limit:8 RTS thr:off Fragment thr:off
          Power Management:off

wlan0 IEEE 802.11b ESSID:" O'Reilly's" Nickname:""
          Mode:Managed Frequency:2.452 GHz Access Point: None
          Bit Rate:2 Mb/s Sensitivity=1/3
          Retry short limit:8 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=0/70 Signal level=-73 dBm Noise level=-73 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

irda0 no wireless extensions.
$ sudo lshw -C network
[sudo] password for stani:
  *-network:0
       description: Wireless interface
       product: Prism 2.5 Wavelan chipset
       vendor: Intersil Corporation
       physical id: 2
       bus info: pci@0000:01:02.0
       logical name: wifi0
       version: 01
       serial: 00:05:3c:06:c2:96
       width: 32 bits
       clock: 33MHz
       capabilities: pm bus_master cap_list logical wireless ethernet physical
       configuration: broadcast=yes driver=hostap firmware=1.4.9 latency=64 module=hostap_pci multicast=yes wireless=IEEE 802.11b
  *-network:1
       description: Ethernet interface
       product: 82801CAM (ICH3) PRO/100 VE (LOM) Ethernet Controller
       vendor: Intel Corporation
       physical id: 8
       bus info: pci@0000:01:08.0
       logical name: eth1
       version: 42
       serial: 00:09:6b:a0:35:5d
       size: 100MB/s
       capacity: 100MB/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=e100 driverversion=3.5.23-k4-NAPI duplex=full firmware=N/A ip=192.168.123.202 latency=66 link=yes maxlatency=56 mingnt=8 module=e100 multicast=yes port=MII speed=100MB/s

[Stani (stani)]

I'd like to know if this bug will be fixed for Hardy. Is there any more information I can give?

[Sitsofe Wheeler (sitsofe)]

stani:
Does using
/usr/bin/sudo iwlist scan
show anything useful?

[Stani (stani)]

@Sitsofe:

Unfortunately not:
$ /usr/bin/sudo iwlist scan
[sudo] password for stani:
lo Interface doesn't support scanning.

eth1 Interface doesn't support scanning.

wifi0 No scan results

wlan0 No scan results

irda0 Interface doesn't support scanning.

[Sitsofe Wheeler (sitsofe)]

Just for the record, the firmware on stani's card is Primary: 1.1.1 Secondary: 1.4.9. Nic ID is 0x8013.

[Stani (stani)]

I have just done a clean install of Hardy and upgraded the firmware of my card. Still no success.... (my other ubuntu desktop has no problems with it) Is it still possible to use the orinoco drivers on Hardy? They worked for me on Dapper & Edgy.

$ sudo hostap_diag wlan0
Host AP driver diagnostics information for 'wlan0'

NICID: id=0x8013 v1.0.0 (PRISM II (2.5) Mini-PCI (SST parallel flash))
PRIID: id=0x0015 v1.1.0
STAID: id=0x001f v1.8.2 (station firmware)

$ sudo lshw -class network
  *-network:0
       description: Wireless interface
       product: Prism 2.5 Wavelan chipset
       vendor: Intersil Corporation
       physical id: 2
       bus info: pci@0000:01:02.0
       logical name: wifi0
       version: 01
       serial: 00:05:3c:06:c2:96
       width: 32 bits
       clock: 33MHz
       capabilities: pm bus_master cap_list logical wireless ethernet physical
       configuration: broadcast=yes driver=hostap firmware=1.8.2 latency=64 module=hostap_pci multicast=yes wireless=IEEE 802.11b

$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wifi0 IEEE 802.11b ESSID:"" Nickname:""
          Mode:Managed Frequency:2.467 GHz Access Point: None
          Bit Rate:2 Mb/s Sensitivity=1/3
          Retry short limit:8 RTS thr:off Fragment thr:off
          Power Management:off

wlan0 IEEE 802.11b ESSID:"" Nickname:""
          Mode:Managed Frequency:2.467 GHz Access Point: None
          Bit Rate:2 Mb/s Sensitivity=1/3
          Retry short limit:8 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=0/70 Signal level=-73 dBm Noise level=-73 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

irda0 no wireless extensions.

$ iwlist scan
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wifi0 No scan results

wlan0 No scan results

irda0 Interface doesn't support scanning.

[Sitsofe Wheeler (sitsofe)]

stani:
Not without compiling the drivers yourself unfortunately. I'm almost tempted to say that if you have the expertise, your particular issue is worth reporting upstream...

Do you know the hardware is still good (i.e. does an old LiveCD or another OS work)?

[Andrew Jorgensen (ajorg)]

stani:
I'm getting inconsistent results. I have several prism-based cards.

Two have the 1.8.2 firmware and works, except that it's slow as snot.
One is too old to have a newer firmware so it has 1.5.6 and works with WEP but not open networks (no WPA, too old).
One is ripped from an access point and has the 1.8.2 firmware on it. Scanning doesn't work at all with this one but connecting manually sorta works (but slow).

None of them seem to really work well. I could go swapping firmwares and see if that results in some improvement but that would only help advanced users. I'm inclined to drop the issue and not worry about it anymore as I don't have any machines that really need to use one of these cards anymore. I imagine the hostap driver devs feel the same way.

Interestingly they all work very nicely with kismet.

There is a good chance the orinoco drivers will work for you but then you get no WPA.

[Tormod Volden (tormodvolden)]

You will need stationary firmware version 1.7.0 or newer in order to get WEP to work on prism2 cards. The linux-wlan-ng package has tools for loading newer firmware into the card RAM (without flashing), but I don't know how well this works for PCI cards. Generally we only recommend linux-wlan-ng for the USB cards, and the others should work better with hostap.

You could try prism2 by installing the linux-wlan-ng-source package and build for PCI (default is USB only). But I'd say you'd rather try to get hostap to work.

[Leann Ogasawara (leannogasawara)]

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.

[Ralph Janke (txwikinger)]

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks.

[Joel Stephens (jbstep)]

Still having same issues, running fuji p2120 with intrepid beta, latest updates as of 10/09/08.
$ cat /proc/version_signature
Ubuntu 2.6.27-6.9-generic
$ iwconfig
lo no wireless extensions.

eth1 no wireless extensions.

wifi0 IEEE 802.11b ESSID:"" Nickname:""
          Mode:Managed Frequency:2.437 GHz Access Point: None
          Bit Rate:2 Mb/s Sensitivity=1/3
          Retry short limit:8 RTS thr:off Fragment thr:off
          Power Management:off

wlan0 IEEE 802.11b ESSID:"" Nickname:""
          Mode:Managed Frequency:2.437 GHz Access Point: None
          Bit Rate:2 Mb/s Sensitivity=1/3
          Retry short limit:8 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=0/70 Signal level=-73 dBm Noise level=-73 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

pan0 no wireless extensions.

Output from lshw:
*-network:1
       description: Wireless interface
       product: Prism 2.5 Wavelan chipset
       vendor: Intersil Corporation
       physical id: 12
       bus info: pci@0000:00:12.0
       logical name: wifi0
       version: 01
       serial: 00:e0:00:8d:a1:90
       width: 32 bits
       clock: 33MHz
       capabilities: pm cap_list logical wireless ethernet physical
       configuration: broadcast=yes driver=hostap firmware=1.4.1 latency=64 module=hostap_pci multicast=yes wireless=IEEE 802.11b

[Leann Ogasawara (leannogasawara)]

Hi Joel,

Can you attach your dmesg output when running the latest 2.6.27-7 Intrepid kernel? Thanks.

[Launchpad Janitor (janitor)]

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.

[Leann Ogasawara (leannogasawara)]

Closing this bug until we get further feedback. Please be sure to first test and confirm if this issue remains with the latest Jaunty 9.04 release and attach the previously requested information. Thanks.

http://www.ubuntu.com/getubuntu/download

[dmc (daniel-coll)]

LinkedIn
------------

Bug:

Me gustaría añadirte a mi red profesional en LinkedIn.

- Daniel Coll

Daniel Coll
Owner en Alto Eventos SRL
Argentina

Confirma que conoces a Daniel Coll
https://www.linkedin.com/e/pu2xdv-geh26cfy-a/isd/1706778593/cFQecEZC/

--
(c) 2010, LinkedIn Corporation