Wireless card doesn't work (airo module)

I switched back to a working kernel and here is my dmesg output regarding airo:
[4294691.296000] airo: Found an MPI350 card
[4294692.374000] airo: MAC enabled eth1 xxxxxxxxxxxxx
[4294692.374000] airo: Finished probing for PCI adapters

I also didn't notice any log like that:
[4294670.533000] pnp: PnPACPI: METHOD_NAME__CRS failure for PNP0303
[4294670.533000] pnp: PnPACPI: unknown resource type 7

The are not in
uname -r
2.6.15-16-686

but they are in 2.6.15-18

My computer is IBM Thinkpad T40.

(in the future, please include lengthy output as an attachment rather than as a comment; it makes the bug difficult to read)

Rejecting spurious bug task; bug remains open

I have a aironet minipci 350 (seen in lspci as Unknown 5000) which is also not working with Dapper kernel 2.6.15-20-686 and wpa_supplicant. I noticed that following patch exists, and am wondering if this has been added. and whether this is the cause of recent problems with airo module, WEP encryption and wpa_supplicant.

Patch: http://mail.gnome.org/archives/networkmanager-list/2006-January/msg00204.html

Any information will be appreciated.

Same problem here, using an Aironet 350 PCMCIA card. The card is detected and visible via ifconfig, however cannot doesn't get an IP via DHCP. This used to work in Breezy and also in earlier releases of Dapper (iirc).

Grepping in Syslog:
May 25 09:35:07 localhost kernel: [4295528.632000] airo: BAP setup error too many retries
May 25 10:54:48 localhost kernel: [4294698.989000] airo: Probing for PCI adapters
May 25 10:54:48 localhost kernel: [4294698.990000] airo: Finished probing for PCI adapters
May 25 10:54:48 localhost kernel: [4294699.424000] Modules linked in: irtty_sir af_packet sir_dev nsc_ircc irda usbhid crc_ccitt airo_cs airo parport_pc parport snd_cs46xx gameport snd_rawmidi snd_seq_device snd_ac97_codec snd_ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_timer ehci_hcd tsdev snd soundcore snd_page_alloc ohci_hcd floppy pcspkr pcmcia psmouse serio_raw e100 i2c_piix4 mii shpchp pci_hotplug i2c_core yenta_socket rsrc_nonstatic pcmcia_core ltserial ltmodem intel_agp agpgart evdev ext3 jbd ide_generic uhci_hcd usbcore ide_cd cdrom ide_disk piix generic thermal processor fan capability commoncap vga16fb vgastate fbcon tileblit font bitblit softcursor
May 25 10:54:48 localhost kernel: [4294700.201000] airo: cmd= 111
May 25 10:54:48 localhost kernel: [4294700.201000] airo: status= 7f11
May 25 10:54:48 localhost kernel: [4294700.201000] airo: Rsp0= 2
May 25 10:54:48 localhost kernel: [4294700.201000] airo: Rsp1= 0
May 25 10:54:48 localhost kernel: [4294700.201000] airo: Rsp2= 0
May 25 10:54:48 localhost kernel: [4294700.201000] airo: Doing fast bap_reads
May 25 10:54:48 localhost kernel: [4294700.278000] airo: MAC enabled eth1 0:7:e:b4:1f:bc

Similar problem; I have an IBM Thinkpad 42p with Cisco aironet minipci 350 (built into laptop).

Upon booting kernel 2.6.15-23-686, the airo module is loaded but does not detect the card. Here's what I get from dmesg:

[4294695.574000] airo: Probing for PCI adapters
[4294695.679000] airo: Found an MPI350 card
[4294696.703000] airo: Couldn't register_netdev
[4294696.705000] airo: Finished probing for PCI adapters

But my ethernet (e1000) works just fine.

After logging in, I can run these commands:

$ sudo modprobe -r airo
$ sudo modprobe airo

And now the aironet card is detected and DHCP works just fine. The card now works.

This time, dmesg shows this:

[4294786.961000] airo: Probing for PCI adapters
[4294786.962000] ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
[4294786.962000] airo: Found an MPI350 card
[4294787.916000] airo: MAC enabled eth1 0:e:9b:cb:d4:de
[4294787.916000] airo: Finished probing for PCI adapters
[4294788.017000] Setting key 0
[4294792.317000] NET: Registered protocol family 10

Is anybody successfully using an Aironet 350 with Dapper? It still doesn't work for me.

As I described in my posting, I can use it after boot up if I remove
the airo module and then re-insert it:

$ sudo modprobe -r airo
$ sudo modprobe airo

In fact, I'm typing this e-mail over my airo minipci 350 wireless
connection from my laptop, using Dapper.

--gilbert

On 6/10/06, Jonathan Blue <email address hidden> wrote:
> Is anybody successfully using an Aironet 350 with Dapper? It still
> doesn't work for me.
>
> --
> Wireless card doesn't work (airo module)
> https://launchpad.net/bugs/34998
>
>

Dnia 10-06-2006, sob o godzinie 11:57 +0000, Gilbert Ramirez napisał(a):
> As I described in my posting, I can use it after boot up if I remove
> the airo module and then re-insert it:
>
> $ sudo modprobe -r airo
> $ sudo modprobe airo

I can confirm that - it works juest like this. I have to unload and load
airo module to make this card work in Dapper.

cayco

I see this issue on my T40 thinkpad. It doesn't keep wireless networking from working if I'm using the standard networking configuration tools, but in combination w/ bug #42861 (network-manager doesn't detect new devices) it makes it impossible to use network-manager on my laptop.

Hello,

First of all: Mr. Matt Zimmerman, can this bug be activated again instead of listed as rejected? As you can see, others are having this same problem.

Bug confirmed on a Thinkpad X31. This has been happening since around Dapper release and now in Edgy. I do not know with what kernel this started to happen.

It appears that I suffer from exactly the same bug as Mr. Gilbert Ramirez with the same, or similar, card.

$ uname -a
Linux x31 2.6.17-10-generic #2 SMP Fri Oct 6 00:36:14 UTC 2006 i686 GNU/Linux

$ lspci
02:02.0 Network controller: AIRONET Wireless Communications Cisco Aironet Wireless 802.11b

Network is not detected upon boot. However, it only happens once in a while (maybe around 1 in 5 bootups). dmesg during bootup:
[17179602.580000] airo(): Probing for PCI adapters
[17179602.580000] airo(eth1): Found an MPI350 card
[17179603.612000] airo(eth1): Couldn't register_netdev
[17179603.916000] airo(): Finished probing for PCI adapters

To fix this, I do:
sudo /etc/init.d/network stop
sudo rmmod airo
sudo modprobe airo

dmesg after the fix above:
[17179771.984000] airo(): Probing for PCI adapters
[17179771.988000] airo(eth0): Found an MPI350 card
[17179772.948000] airo(eth0): MAC enabled 0:2:8a:78:41:dc
[17179772.948000] airo(): Finished probing for PCI adapters

My /etc/network/interfaces:
iface lo inet loopback

iface eth0 inet static
address *****
netmask *****
gateway *****
wireless-essid *****
wireless-key *****

auto lo
auto eth0

Not exactly sure why Mr. Matt Zimmerman rejected this bug based on it being spurious, as it does exist. Please see posts after Matt Zimmerman's comment for more information.

Original comment was *very* long and made this bug difficult to follow. I split the original comment and added the logs in an attachment.

I would like to follow up on this and say that the module is not loaded properly after EVERY boot. Previously (in Dapper?), this was not the case. Sometimes it would load correctly, and sometimes it would not.

This problem is probably caused by the newer boot sequence. This module may need to be loaded at a later stage for it to work.

Notice that the bug is not rejected, only the "ubuntu" task. This bug only needs one task (linux-source).

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 linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

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.

I have a IBM X31 with airo MPI350 wireless card. I had everything working perfectly with gutsy 7.04, even hibernating! Since its end of life, I've been through all the other releases looking for one that works without success.

In respect to the wireless card/driver, the LTS 8.04 release still works well. Nevertheless I had to change due to other issues.
In 8.10 and 9.04, the card just isn't usable. Starts well, listing all the available networks but is only able to connect to one of them, randomly! I have 3 that I can use and I can't choose. After a few minutes connected, network manager only lists one, the one it can connect to. Wired connection always works.

When I reboot, usually lists all the visible networks again, but will most of the time connect to the previously used, until the day it decides to change. Is out of control. After a few minutes the list is always reduced to the current network.

I have tried Wicd, which shows the same behavior. It even has a disadvantage, it can't be connected to wired and wireless at the same time.

I have then tried Ndiswrapper. It looks like working perfectly. It even lists more visible networks than before! Only it just can't connect to any of them!

I tried two other solutions that weren't the good ones. One was blacklisting two conflicting modules: "aes" and something else, and the other was turning off a lot of airo-related lines in a file "modules.alias". They didn't work either.

One last test:
If I connect manualy doing
$ sudo iwconfig eth1 essid accesspoint
$ sudo iwconfig eth1 enc wepkey
$ sudo dhclient eth1
it connects to the one I want, as long as nm-manager shows being connected to whatever other access point. If nm-manager is disconnected, this doesn't work.
When it connects to the desired one, nm-manager shows being connected to the previous one still.
After a while, it also LISTS the one to which is really connected.
Eventually, after a while more, nm-manager will finally show being connected to the correct one.

I don't know if it's the driver that changed, nm-manager or the kernel, I don't know what to do. It's really bad. I'm starting to see many regressions on ubuntu, on older computers. I even consider going back to windows after a couple of years just because I can't afford an unstable PC.

Unassigned from Ben Collins. Marked Invalid. Please report issues like this for a current release in a new bug with the apport data attached.

-JFo