WiFi adapter using prism drivers stops working, requires reboot

Bug #117400 reported by Jguy101
6
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Brian Murray

Bug Description

My old D-Link DWL-122 (which uses the Prism chipset, requiring the wlan-ng drivers) had been working fine in Edgy, but when I upgraded to Feisty, it started going haywire. I'll boot up and everything will be fine, but eventually, I just can't visit any sites (it'll eventually time out). I open up network-admin, and guess what? wlan0 is now a wired connection.

WTH?

So, yeah, I have to reboot, and that doesn't always work the first (or second) time.

Revision history for this message
Kees Cook (kees) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.

Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at http://wiki.ubuntu.com/KernelTeamBugPolicies

Thanks in advance!
Thanks in advance.

Revision history for this message
andy_js (andyjstormont) wrote :

I'd like to confirm this.

My machine has a fresh install of feisty with linux-wlan-ng installed.

My D-link DWL-122 shows up in both the network applet and the network config gui as a wired connection,
'iwconfig' says the device has no wireless extensions.

I was lucky enough to find out by accident that if I reconfigure the device using 'wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable', it's wireless extensions seem to start working.

You can then configure the device using the network gui by turning off roaming mode (when you try to connect via the applet the device reverts back to a wired device).

So now I can connect with 'sudo ifup wlan0'.

I'll see what additional info I can get for you.

Kees Cook (kees)
Changed in linux-source-2.6.20:
assignee: keescook → nobody
status: Incomplete → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

Awaiting detail information asked for in the comment by Kees Cook.

Changed in linux-source-2.6.20:
assignee: nobody → brian-murray
status: Confirmed → Incomplete
Revision history for this message
Brian Murray (brian-murray) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.

Changed in linux-source-2.6.20:
status: Incomplete → Invalid
Revision history for this message
konsty (for-labuda) wrote :

Actually sometimes I am experiencing the same problem.
"uname -a" gives
Linux aldan 2.6.20-16-generic #2 SMP Fri Aug 31 00:55:27 UTC 2007 i686 GNU/Linux

find log files in attachment

Revision history for this message
konsty (for-labuda) wrote :
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug does not meet the criteria for a stable release update and is being marked as Won't Fix for the kernel version the bug was submitted about. You can learn more about the stable release update process at https://wiki.ubuntu.com/StableReleaseUpdates .
However, the issue that you reported is one that should be possible to test with the live environment of the Desktop CD of the development release - Gutsy Gibbon. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed kernel. You can find out more about the development release at http://www.ubuntu.com/testing/ .
If you do decide to test with the development release of Ubuntu please comment on this bug report and include at least the minimal information requested at http://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help.

Changed in linux-source-2.6.20:
status: Invalid → Won't Fix
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.