Linksys WUSB54G won't connect to wireless network with karmic kernel

Bug #472953 reported by Don C Stokes
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Hardware:
HP laptop model ze4210
Linksys WUSB54G USB wireless G adapter
  Bus 001 Device 002: ID 13b1:000d Linksys WUSB54G Wireless Adapter
Kernel: (output from "uname -a")
  Linux ze4210 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686
GNU/Linux
Problem:
This hardware worked fine with Jaunty.
I did a clean install of Karmic and can no longer connect to my wireless router. I can see
the router on the wireless network list and select it. After a few moments it times out and
is not connected.
As a trouble shooting test, I installed a Jaunty kernel and the adapter SUCCESSFULLY
connected. The kernel that worked was installed from:
linux-image-2.6.28-16-generic_2.6.28-16.55_i386.deb

ProblemType: Bug
Architecture: i386
Date: Tue Nov 3 11:36:37 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/yelp
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: yelp 2.28.0-0ubuntu2
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: yelp
Uname: Linux 2.6.31-14-generic i686
XsessionErrors:
 (gnome-settings-daemon:1386): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1386): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:1421): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:1437): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-panel:1420): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 24

Revision history for this message
Don C Stokes (doncstokes) wrote :
Philip Muškovac (yofel)
affects: ubuntu → linux (Ubuntu)
Revision history for this message
JewelsAndBinoculars (nicktulett) wrote :

I had the same problem after upgrading today (2.6.31-15-386).

I emptied /etc/modprobe.d/blacklist and cleared the driver entries from System > Administration > Windows Wireless Drivers and my WUSB54G was recognised after the next reboot.

Revision history for this message
rickliner (rickliner) wrote :

I just did a clean install of Karmic on a system with the Linksys WUSB54G. I booted from the install CD and was able to use the wireless fine from that environment. Once I performed the install and booted from it, wireless no longer worked - same symptoms as above. I could see my network but not connect.

I just tried the advice at this page, which seems to have worked for me:
http://tredosoft.com/rt2870_ubuntu

"
Ok so you just installed Ubuntu 9.10 (Karmic Koala). The OS booted fine and you plugged in your RT2870 based USB wireless card (e.g. Alpha 802.11 n, Belkin etc.). Unfortunately, everytime you attempt to connect to a wireless network the Network-Manager app takes forever to connect but never succeeds. What to do?

There has been a bug report in the Release Candidate which interestingly didn't get fixed in the release version of Karmic Koala (Available here)

Apparently, RT2800usb and RT2870sta drivers compete to operate your wireless card resulting in no wireless connectivity. This from what I remember was a problem I faced with 9.04 as well.

The solution is to simply add the line
blacklist rt2800usb

in the file "/etc/modprobe.d/blacklist.conf"

Restart Ubuntu and voala! Its alive!
"

ID 13b1:000d Linksys WUSB54G Wireless Adapter
Kernel 2.6.31-14 fresh from the install CD, no updates.
Motherboard: Gigabyte GA-MA78GM-S2HP 780G

Revision history for this message
JewelsAndBinoculars (nicktulett) wrote :

Further to my previous comment, I had to endure a weak signal, unacceptable packet loss and frequent connection drops until I uninstalled Rutilt and replaced it with wicd - so it all now seems to be working fine with the stock rt2500usb module (rt2570 was a no-go as was ndiswrapper).

Revision history for this message
rickliner (rickliner) wrote :

And to further my previous comment, the reported fix does not work consistently for me. Sometimes I get a good connection on boot, and sometimes it appears to be connecting but fails as before.

FWIW, my System -> Administration menu does not contain an entry about Windows Wireless Drivers as mentioned by the other poster.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Don,

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? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

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

apport-collect -p linux 472953

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
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.