Intel Wireless 4965AGN (iwl4965) & network-manager doesn't work
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
linux-backports-modules-2.6.27 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
linux-source-2.6.22 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
I have a Intel Wireless 4965 AGN chip. If I have installed a fresh copy of Ubuntu, the first time I've start Ubuntu it works fine using the Gnome Network-Manager and 4965 chip. But if I restart my computer, he doesn't connect to my network. Some other problems with it:
* If I change or disconnect a wireless network, gnome-network-
* No connection on startup
* No information about connectivity (80%, 90% and so on...)
It works only if I type in a terminal "sudo modprobe -r iwl4965" and then reinitialize the module. Then I have to type "sudo ifdown wlan0" and "sudo ifup wlan0", sometimes more than 5 times. If I type "iwlist scan" he says "No wireless networks found" or he displays nothing about my wlan-adapter. Now I use wicd instead of the gnome network-manager, but sometimes wicd get also no connection and I have to restart my computer or reinitialize the module.
System: Ubuntu Gutsy Gibbon with all updates
Toshiba Satellite P200-1E9
Changed in linux-source-2.6.22: | |
status: | Incomplete → Confirmed |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description does not yet have enough information.
Please include the following additional information, if you have not already done so (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" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo 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 [WWW] http:// wiki.ubuntu. com/KernelTeamB ugPolicies. Thanks in advance!