WiFi adapter using prism drivers stops working, requires reboot
Bug #117400 reported by
Jguy101
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.
Changed in linux-source-2.6.20: | |
assignee: | keescook → nobody |
status: | Incomplete → Confirmed |
To post a comment you must log in.
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/KernelTeamB ugPolicies
Thanks in advance!
Thanks in advance.