On Saturday 11 Sep 2010 19:47:30 Bruno Friedmann wrote:
Just one important point, the /var/log/NetworkManager.log & wpa_supplicant related log can explain lot's of things.
Also you can check with modinfo iwl6xx ( don't knows the exact real name of your kernel module ) the complementary option you can pass to it.
for example : increasing debug output
after that you should edit the corresponding /etc/modprobe.d/50-iwlxxxx file
For example for my iwl3945 I use that # options from modinfo iwl3945 #parm: antenna:select antenna (1=Main, 2=Aux, default 0 [both]) (int) #parm: swcrypto:using software crypto (default 1 [software]) #(int) #parm: debug:debug output mask (uint) #parm: disable_hw_scan:disable hardware scanning (default 0) (int) #parm: fw_restart3945:restart firmware in case of error (int)
options iwl3945 disable_hw_scan=0 fw_restart3945=1 #debug=100 when trouble appear
Hope this help you a bit. I've found in my case that the fw_restart was very usefull in many situation. It help me also to fix my AP which was changing it's channel too fast :-)
There, it seems, is the nub. In /etc/modprobe.d/50- I have only modules for ipw2200 and iwl3495 - neither of which is going to work with a 6200 card. Zypper tells me that I have iwl6000-ucode and I've just installed iwl6050- ucode to cover all bases. What do I need to do with them now? It's years since I had to manually insert modules, and I simply can't remember how! Anne -- KDE Community Working Group New to KDE Software? - get help from http://userbase.kde.org