Support, but poor support, added for WUSB54Gv2 - wifi problem

Bug #322592 reported by sem
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I have a problem with wireless that didn't exist in 8.04.

I use a linksys wusb54gv2, and in 8.04 I used ndiswrapper and network manager to connect. But when I went to 8.10 (first by updating, but a second time with a fresh install and no custom setup of ndiswrapper), network manager connects to my network automatically, stays connected for a few minutes, and then disconnects unable to reconnect

Right now I am downloading Jaunty Alpha 3 to see if the problem has already been fixed; will report back.
If there is any more information I could give or tests I could do, please let me know.

Tags: kj-expired
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thanks phix,

After you've tested and confirmed the issue to exist in Jaunty, Per the kernel team's bug policy, can you please attach the following information. Please be sure to attach each file as a separate attachment.

* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

It would also be best to wait and capture the dmesg output after you witness the disconnect just so any error messages may get logged. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

Changed in linux:
status: New → Incomplete
Revision history for this message
sem (semitones) wrote :
Revision history for this message
sem (semitones) wrote :
Revision history for this message
sem (semitones) wrote :
Revision history for this message
sem (semitones) wrote :

Problem reproduced in jaunty. The network stayed connected for a little while longer, but did not reconnect when I tried.

Revision history for this message
sem (semitones) wrote :
Revision history for this message
sem (semitones) wrote :
Changed in linux:
importance: Undecided → Medium
status: Incomplete → Triaged
Revision history for this message
AceLan Kao (acelankao) wrote :

Can you please try installing the linux-backports-modules-jaunty package. The linux-backports-modules-jaunty package contains and updated compat-wireless stack which may help. Be sure to reboot after installing this package in order to test. Please let us know your results.

If the issue remains even after installing and testing linux-backports-modules-jaunty, could you then please try the latest upstream compat-wireless stack. See http://wireless.kernel.org/en/users/Download for more info. If the issue exists upstream, we'll want to work with the upstream developers to try to get this resolved. Also, after confirming the issue remains with the latest upstream compat-wireless stack, be sure to also 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-image-`uname -r` 322592

AceLan Kao (acelankao)
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
sem (semitones) wrote :

I was unable to work on this computer for some time, but in october, I installed 9.10 to see if the problem had been fixed. Wireless functionality was still broken, so I'll get new logs as soon as I can.

One question -- on an installation without networking, is it possible to download apt packages elsewhere, and then copy and install them to the affected installation?

Revision history for this message
AceLan Kao (acelankao) wrote :

Really sorry to hear the driver is still not working, Please upload the new logs for karmic, this' really important for us to diagnosis the problem. The log collected command is the same as the previous comment.

I didn't have that experience, so I don't know how to do that.
I think during the installation, it doesn't need the network enabled. You can install the whole system without network and then install/update package after installed by .deb package from USB disk.

Revision history for this message
sem (semitones) wrote :

Here are the logs. I turned on the computer, put in my keychain password when prompted by nm-manager, waited, put in my WPA passkey when prompted, waited, put in my passkey when prompted again, waited, and the third time, clicked cancel instead of putting in my passkey.

I disabled WPA and attempted to connect to the unsecured network. This would not work either. I tried twice.

I ran the apport command but it couldn't work without an internet connection.
I included /var/log/syslog because I looked at it and it seemed relevant.

Let me know what I should try next. Thanks.

Revision history for this message
sem (semitones) wrote :
Revision history for this message
sem (semitones) wrote :
Revision history for this message
sem (semitones) wrote :
Revision history for this message
Anzenketh (anzenketh) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Lucid. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/. Thanks again and we appreciate your help.

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.