Iwlwifi problem with networkmanager

Bug #200907 reported by LEVIS Cyril
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

There is yet a problem with iwlwifi,
I have a m1330 , I use iwl4965 module.

After killswitch or resume hibernate, networkmanager don't work directly sometimes.

iwl4965 seems to don't wake up.

I must stop network manager, unload the module, reload the module, and restart networkmanager.

I think you must the unload and re-load the module for it re-scan the network.

When I only restart networkmanager this don't work.

ps: I have firmware-addon-dell installed.

You also must to modify this package for put a symlink of /usr/bin/dellWirelessCtl in /usr/sbin/dellWirelessCtl.

Networkmanager search dellWirelessCtl in /usr/sbin, not /usr/bin.

Revision history for this message
ashes (axis-vo) wrote :

My wifi is atheros ar5007ag with madwifi drivers and i have some problem.

Revision history for this message
Franco Sirovich (franco-sirovich) wrote :

Hello everybody!
I work with 8.04 beta on a VAIO VGN-SZ3XP/C, Core 2 duo T7200, and use the following modules:
franco@sonyfranco:~$ lsmod|grep iw
iwl3945 89844 0
iwlwifi_mac80211 219108 1 iwl3945
cfg80211 15112 1 iwlwifi_mac80211

With "Ubuntu hardy (development branch), kernel 2.6.24-11-generic" I had the same reported problem, but now with "Ubuntu hardy (development branch), kernel 2.6.24-12-generic" both suspend and hibernate work well with network manager.
Franco

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. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments 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 '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 https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

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:
status: Incomplete → Invalid
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.