Cannot connect to WPA2 WiFi signals.

[Parham D.]

Ubuntu 10.04 and 9.10 cannot connect to WPA2 signals when using a US Robotics USR5420. I have tried WiCD but that doesn't work either. WiCD gets stuck at validation and Network Manager keeps asking for the passphrase.

[connor6892 (connor6892)]

Hi,

This bug report needs a little bit more information so that someone can look into what is causing what seems to be a driver issue.
Could you please run in terminal:

apport-collect -p linux <573273>

which will attach this data to this report.

Thanks!

[connor6892 (connor6892)]

Sorry, that does assume that you have another working connection, which I appreciate is probably not the case.

[Parham D. (parhamdibajnia)]

parham@parham-desktop:~$ apport-collect -p linux <573273>
bash: syntax error near unexpected token `573273'
parham@parham-desktop:~$

[connor6892 (connor6892)]

Hi,

I'm sorry about that, I think I may have made a mistake there.

sudo apport-collect 573273

Could you try that, if you have some form of internet connection? Hopefully this will give us the necessary data.

That aside, are you using ndiswrapper to make this card work?

[Parham D. (parhamdibajnia)]

Hey Connor,
I see that this "code" or input you gave me needs to be connected to the internet. sadly, the only computer with Ubuntu in this house is mine and I need to switch over to XP or go on my PS3 to go on the internet. Can you give me inputs instead (lusb) etc.?

[Parham D. (parhamdibajnia)]

parham@parham-desktop:~$ sudo lshw -C network
[sudo] password for parham:
  *-network
       description: Ethernet interface
       product: RTL-8139/8139C/8139C+
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: c
       bus info: pci@0000:01:0c.0
       logical name: eth0
       version: 10
       serial: 00:11:09:70:58:f8
       size: 10MB/s
       capacity: 100MB/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=8139too driverversion=0.9.28 duplex=half latency=32 link=no maxlatency=64 mingnt=32 multicast=yes port=MII speed=10MB/s
       resources: irq:23 ioport:c800(size=256) memory:ed000000-ed0000ff memory:20000000-2000ffff(prefetchable)
  *-network DISABLED
       description: Wireless interface
       physical id: 1
       logical name: wlan0
       serial: 00:c0:49:dd:38:99
       capabilities: ethernet physical wireless
       configuration: broadcast=yes driver=rndis_wlan driverversion=22-Aug-2005 firmware=Wireless RNDIS device, BCM4320a usb-0000:00:1d.7-6 link=no multicast=yes wireless=IEEE 802.11bg
parham@parham-desktop:~$

[Parham D. (parhamdibajnia)]

parham@parham-desktop:~$ cat/etc/resolv.conf
bash: cat/etc/resolv.conf: No such file or directory
parham@parham-desktop:~$

parham@Ubuntu:~$ lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0baf:0111 U.S. Robotics
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
parham@Ubuntu:~$

[connor6892 (connor6892)]

Thanks, you beat me to it with the debug info! Okay, I think I've spotted at least a first issue which may be causing that problem. For some reason, the device has been configured to use a very old driver, and in the release of 10.04 there was actually an update to a brand new open source driver for the Broadcom chipset that's in your wifi stick.

Could you:

sudo rmmod rndis_wlan (this can be undone if we have no success using insmod)

Then, go to Hardware Drivers under System -> Administration, and see if it is possible to activate the B43 driver for the wifi chip. Apparently some people are having issues with this, but it's perfectly possible to install it using the software centre/synpatic too.

Failing that, install package b43-fwcutter using synaptic.

Then go back to hardware drivers, and see if it is possible to install the B43 driver again.

If not, then please run:

sudo sh /usr/share/b43-fwcutter/install_bcm43xx_firmware.sh

and reboot.

Hopefully, this will work. If not, we can try proprietary Broadcom drivers. What's caused it to install such an old driver is quite beyond me though, presumably something to do with how the USB stick identifies itself. Let us know what happens!

@ other affected user, could you please run:

sudo lshw -C network

and copy and paste the output?

Thanks!

[connor6892 (connor6892)]

And Parham D, as I didn't really say clearly, after all that only if you have no success try

sudo insmod rndis_wlan

and reboot.

[Parham D. (parhamdibajnia)]

parham@parham-desktop:~$ sudo rmmod rndis_wlan
[sudo] password for parham:
parham@parham-desktop:~$ There were no Hardware Drivers found in System>Administration>Hardware Drivers
There: command not found
parham@parham-desktop:~$ sh/usr/share/b43-fwcutter/install_bcm43xx_firmware.sh
bash: sh/usr/share/b43-fwcutter/install_bcm43xx_firmware.sh: No such file or directory
parham@parham-desktop:~$

[connor6892 (connor6892)]

Okay.

Could you unplug the device from your machine, then do the sudo rmmod command from above again.

Then, go to synaptic and install package "bcmwl-kernel-source". Did you install the b43-fwcutter package from the synaptic program too?

Plug the device back in and tell me if it works. Fingers crossed this will.

[connor6892 (connor6892)]

*****Do this first******

I see what went wrong above. After removing the device and sudo rmmod rndis_wlan, could you also retry

sudo sh /usr/share/b43-fwcutter/install_bcm43xx_firmware.sh

The sudo is imperative, and so is the space between sh and /usr...

Then, plug it back in. If that doesn't work, try the instructions in the above post from the very start again.

I'm really sorry that I've made this so mixed up, but I'm confident there's a way to make this work! We need to try it before formalising the bug, anyway. Thanks for your help!

[Parham D. (parhamdibajnia)]

parham@parham-desktop:~$ *Wireless Adaptor Unplugged*
*Wireless: command not found
parham@parham-desktop:~$ sudo rmmod rndis_wlan
[sudo] password for parham:
parham@parham-desktop:~$ I'm in synaptic now and it says they're both installed. The have a green box and when I left click it gives me no install option but actually a removal option
parham@parham-desktop:~$ sh/usr/share/b43-fwcutter/install_bcm43xx_firmware.sh
bash: sh/usr/share/b43-fwcutter/install_bcm43xx_firmware.sh: No such file or directory
parham@parham-desktop:~$

parham@parham-desktop:~$ sudo sh /usr/share/b43-fwcutter/install_bcm43xx_firmware.sh
[sudo] password for parham:
--2010-05-04 16:16:01-- http://downloads.openwrt.org/sources/wl_apsta-3.130.20.0.o
Resolving downloads.openwrt.org... failed: Name or service not known.
wget: unable to resolve host address `downloads.openwrt.org'
parham@parham-desktop:~$

[connor6892 (connor6892)]

So, it's trying to download something when you don't have an internet connection.

I've decided to take a new angle on this. No matter how old rndis_wlan is, it should work, and it might actually be the only thing that will work. It's a bug, and it's affecting someone else.

Firstly, just to be safe, could you:

sudo insmod rndis_wlan

Then, reboot.

Please could you attach the following things as separate text files, copy and pasted out of terminal?

uname -a and save this as uname-a.log

cat /proc/version_signature and save as proc_version_signature.log

sudo lspci -vvnn and save as lspci-vvnn.log (two vs, not a w)

dmesg and save as dmesg.log

I'm going to copy your lsusb into a text file and attach it to save you a little bit of time. Then, based on the fact that no solution is apparent, someone else is apparently having this issue and there's enough debug information, it can be stepped up to confirmed and the kernel team can look at it. In order to help the bug report, it would also be good if you could connect via ethernet and download the latest development kernel so that someone from bug control can set the status to triaged. Obviously that mightn't be possible, and thank you for going through all of this to make a complete bug!

[connor6892 (connor6892)]

All of the above with it plugged in, thought I'd specify, sorry!

[connor6892 (connor6892)]

Okay, than you very much for your help in debugging this! This bug is now confirmed, your dmesg is pretty clear there. I'll mention it on the IRC channel for Bug Control and hopefully it'll be fixed. Thanks again!

[Parham D. (parhamdibajnia)]

Thank you a lot Connor. I appreciate your help with my problem. Do you know when the next kernel will be out with the bug fixed? Thanks.

[connor6892 (connor6892)]

You're very welcome. Unfortunately, there's not really any way of predicting when a particular kernel release could occur. I would hazard to guess, these being my words and not those of anything official, that it would be resolved by the next stable Ubuntu release, so before October. As ever, the best way to find out what's happening with relation to this problem is to stay subscribed to this report, as any patches created by developers would normally be attached here, and so you could try the solution as it was developed, regardless of a kernel release. The bug could be taken upstream to the actual Linux kernel project if it covers other distributions, independent of Ubuntu, and that would also be mentioned here. Hopefully a solution will be found in the near future, and that's all that can really be said. Thank you for using your time to report this, so that the distribution can be made better for everyone.

[Parham D. (parhamdibajnia)]

Long time since the last post but i've been thinking. How does a bug become fixed? Like when a bug is triaged, how does someone notice it and fix it?

[connor6892 (connor6892)]

Hi,

When a bug is triaged, it enters a list of all the triaged bugs for each particular package. Developers then work through the list systematically, based on the importance of the bugs - as you can see this one is set to Medium (simply because hypothetically you could access all of the features through ethernet, and Ubuntu still starts). This means that it isn't at the bottom of the pile, but the ratio of work to available developer time is still very high, and so unfortunately this takes time to resolve. It seems highly likely to me that this is something to do with the hardware identifying itself in a non-uniform way, specific to this US Robotics model. I'm not a developer, but this is what it looks like to me. USR probably accomodate for that in firmware (not drivers) that ship with the device - this is not provided for linux. I appreciate that doesn't make your internet work, though.

Given the nature of this, though, there is a chance it will simply begin to work in the next Ubuntu release, which comes out in October. There will be a big jump forward towards a more up to date kernel, and with it lots of new drivers and driver updates. The fact that this is logged on Launchpad means that developers across many projects can see it, too. It's possible that the hardware will react differently to the newer versions.

This will eventually be fixed in Lucid, but might be fixed already in the next release, Maverick. If you want to test it out, you could find the testing version on the ubuntu site and give it a go. Just an idea - but someone will get to this, it's just we're quite short on resources!

[penalvch (penalvch)]

Parham D., this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Parham D. (parhamdibajnia)]

Hello,
To be honest ,this adapter is approximately 10 years old and support stopped after Windows XP in terms of drivers. I think that as a result of this, the bug can be ignored/deleted.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]