Re: [opensuse-kde] Wifi management problem
On Saturday 11 Sep 2010 14:08:09 Alin Marin Elena wrote:
Dear Anne,
Let us tackle the issues one at a time. Let me summarise first. 1. You have two wireless cards a "on board" one and an usb one? Yes
2. onboard one never worked. (it did not work in fedora either) Correct. It may also be relevant that at one point I got a strange message from logwatch, and was told to report it to the kernel bugzilla. They indicated that it was connected with the wireless, and told me to apply a patch and recompile the kernel (as far as I can remember correctly). I told them that that was beyond my expertise unless they could point me to documentation. They didn't.
3. the usb one worked and now seems to have stopped?
To be honest, I never tried shutting off the wired, so I don't know whether wpa-supplicant was doing its thing or not. At some point this afternoon the green light came on again on the usb one. ifconfig now shows its mac address, but both RX and TX are 0 packets.
by the way half of the people that replied to this are on #opensuse-kde it may be helpful to ask there too.
Good idea. I'll do that, thanks. Anne -- KDE Community Working Group New to KDE Software? - get help from http://userbase.kde.org
On 09/11/2010 08:05 PM, Anne Wilson wrote:
On Saturday 11 Sep 2010 14:08:09 Alin Marin Elena wrote:
Dear Anne,
Let us tackle the issues one at a time. Let me summarise first. 1. You have two wireless cards a "on board" one and an usb one? Yes
2. onboard one never worked. (it did not work in fedora either) Correct. It may also be relevant that at one point I got a strange message from logwatch, and was told to report it to the kernel bugzilla. They indicated that it was connected with the wireless, and told me to apply a patch and recompile the kernel (as far as I can remember correctly). I told them that that was beyond my expertise unless they could point me to documentation. They didn't.
3. the usb one worked and now seems to have stopped?
To be honest, I never tried shutting off the wired, so I don't know whether wpa-supplicant was doing its thing or not. At some point this afternoon the green light came on again on the usb one. ifconfig now shows its mac address, but both RX and TX are 0 packets.
by the way half of the people that replied to this are on #opensuse-kde it may be helpful to ask there too.
Good idea. I'll do that, thanks.
Anne
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 :-) -- Bruno Friedmann bruno@ioda-net.ch Ioda-Net Sàrl www.ioda-net.ch openSUSE Member User www.ioda.net/r/osu Blog www.ioda.net/r/blog fsfe fellowship www.fsfe.org (bruno.friedmann (at) fsfe.org ) tigerfoot on irc GPG KEY : D5C9B751C4653227 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
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
On 09/12/2010 05:16 PM, Anne Wilson wrote:
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
Normally, if everything works (as always in this world) you didn't need to have those typical file in /etc/modprobe.d They are used when the chip need some special options. It seems that are the case with yours. so I would export the available options for iwlagn module ( I think this is one used ) modinfo iwlagn | grep "parm:" > /etc/modprobe.d/50-iwlagn.conf (You edit the file and comment each line, they are just there as reminder ) parm: swcrypto50:using software crypto engine (default 0 [hardware]) parm: queues_num50:number of hw queues in 50xx series (int) parm: 11n_disable50:disable 50XX 11n functionality (int) parm: amsdu_size_8K50:enable 8K amsdu size in 50XX series (int) parm: fw_restart50:restart firmware in case of error (int) parm: antenna:select antenna (1=Main, 2=Aux, default 0 [both]) (int) parm: swcrypto:using crypto in software (default 0 [hardware]) (int) parm: disable_hw_scan:disable hardware scanning (default 0) (int) parm: queues_num:number of hw queues. (int) parm: 11n_disable:disable 11n functionality (int) parm: amsdu_size_8K:enable 8K amsdu size (int) parm: fw_restart4965:restart firmware in case of error (int) parm: debug50:50XX debug output mask (deprecated) (uint) parm: debug:debug output mask (uint) I would use to start. options iwlagn debug=100 fw_restart4965=1 Now there's something interesting in the iwlwifi website. The ucode offered by intel is not the same than those contained in opensuse. They have updated it the 18 June .... Check here http://intellinuxwireless.org/?n=Downloads to grab : http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-6000-ucode-9.221.4.1... and http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-6050-ucode-9.201.4.1... You can rename existing file in /lib/firmware and place the new one here. (Two years ago, I have to do that to make my iwl3945 working) Sorry Anne, nothing fun, crappy admin manipulation that would send your husband to china :-) when you have the new ucode in place and the modprobe.d file ( I would recommand to restart the computer by powering it off ). After that check the log in dmesg, the iwlagn should be very more verbose. If everything goes well ( I cross my fingers ), just remove the debug option to avoid filling /var/log ... Hope & Fun. -- Bruno Friedmann bruno@ioda-net.ch Ioda-Net Sàrl www.ioda-net.ch openSUSE Member User www.ioda.net/r/osu Blog www.ioda.net/r/blog fsfe fellowship www.fsfe.org (bruno.friedmann (at) fsfe.org ) tigerfoot on irc GPG KEY : D5C9B751C4653227 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Sunday 12 Sep 2010 16:41:56 Bruno Friedmann wrote:
On 09/12/2010 05:16 PM, Anne Wilson wrote:
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
Normally, if everything works (as always in this world) you didn't need to have those typical file in /etc/modprobe.d They are used when the chip need some special options.
It seems that are the case with yours. so I would export the available options for iwlagn module ( I think this is one used ) modinfo iwlagn | grep "parm:" > /etc/modprobe.d/50-iwlagn.conf (You edit the file and comment each line, they are just there as reminder )
The brain doesn't seem to be working well today. I got as far as creating the 50-iwlagn.conf and seeing the list of parameters.
parm: swcrypto50:using software crypto engine (default 0 [hardware]) parm: queues_num50:number of hw queues in 50xx series (int) parm: 11n_disable50:disable 50XX 11n functionality (int) parm: amsdu_size_8K50:enable 8K amsdu size in 50XX series (int) parm: fw_restart50:restart firmware in case of error (int) parm: antenna:select antenna (1=Main, 2=Aux, default 0 [both]) (int) parm: swcrypto:using crypto in software (default 0 [hardware]) (int) parm: disable_hw_scan:disable hardware scanning (default 0) (int) parm: queues_num:number of hw queues. (int) parm: 11n_disable:disable 11n functionality (int) parm: amsdu_size_8K:enable 8K amsdu size (int) parm: fw_restart4965:restart firmware in case of error (int) parm: debug50:50XX debug output mask (deprecated) (uint) parm: debug:debug output mask (uint)
I would use to start. options iwlagn debug=100 fw_restart4965=1
was that 'modprobe options iwlagn debug=100 fw_restart4965=1'? or something else. Everything I tried gave me an error. Sorry, but I'm obviously not understanding you on this.
Now there's something interesting in the iwlwifi website. The ucode offered by intel is not the same than those contained in opensuse. They have updated it the 18 June .... Check here http://intellinuxwireless.org/?n=Downloads to grab : http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-6000-ucode-9.221.4. 1.tgz and http://intellinuxwireless.org/iwlwifi/downloads/iwlwifi-6050-ucode-9.201.4 .1.tgz
OK, got them. Reading the README, it seems that the 6000 one is the correct one for my card. I've extracted both, to be on the safe side, and put them both into /lib/firmware.
You can rename existing file in /lib/firmware and place the new one here. (Two years ago, I have to do that to make my iwl3945 working)
Sorry Anne, nothing fun, crappy admin manipulation that would send your husband to china :-)
:-D I don't mind the work, but sometimes feel a bit out of my depth - you know how it is - we all know more about some things than others.
when you have the new ucode in place and the modprobe.d file ( I would recommand to restart the computer by powering it off ).
I powered down, waiting long enought to ensure that nothing is cached (is that still sometimes a problem?) then rebooted. No network at all. Nothing I could do would make it work. In the end I used yast2 to take it out of NM control, then rebooted again. This time the D-Link USB gadget fired up. ifconfig lists it, with its address and a small number of RX and TX. The built-in Intel still isn't working.
After that check the log in dmesg, the iwlagn should be very more verbose.
Yes indeed, I can see the output when the dongle got its address. For wlan0, though, I see Sep 12 19:14:01 linux-4gz6 dhcpcd[5746]: wlan0: dhcpcd 3.2.3 starting Sep 12 19:14:01 linux-4gz6 dhcpcd[5746]: wlan0: ioctl SIOCSIFFLAGS: Unknown error 132 Sep 12 19:14:01 linux-4gz6 dhcpcd[5746]: wlan0: exiting twice. The only useful thing I found by googling was the suggestion that the wrong type of encryption was being sent. I know my router is set to accept WPA-1 and 2 - the passphrase is TKIP - is there anywhere I can check what encryption method is being used at this end?
If everything goes well ( I cross my fingers ), just remove the debug option to avoid filling /var/log ...
Hope & Fun.
:-) Well, at least I learn something with great regularity. Anne -- KDE Community Working Group New to KDE Software? - get help from http://userbase.kde.org
2010/9/12 Anne Wilson
was that 'modprobe options iwlagn debug=100 fw_restart4965=1'? or something else. Everything I tried gave me an error. Sorry, but I'm obviously not understanding you on this. It is 'modprobe iwlagn debug=100 fw_restart4965=1' The only useful thing I found by googling was the suggestion that the wrong type of encryption was being sent. I know my router is set to accept WPA-1 and 2 - the passphrase is TKIP - is there anywhere I can check what encryption method is being used at this end? The interface is still down, encryption does not matter here, since you just cannot connect to any AP. -- Regards, Minton. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Sunday, September 12, 2010 17:16:29 Anne Wilson wrote:
On Saturday 11 Sep 2010 19:47:30 Bruno Friedmann wrote: 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!
The ucode should get loaded automatically (and your earlier supplied logs suggest that that happens). My iwlagn adapter (also in an i5-based laptop) sometimes stops letting packages through. The following (admittedly a bit brutal) method makes it work again in those cases: # modprobe -r iwlagn && sleep 1 && modprobe iwlagn That essentiall reloads the kernel module. Networkmanager picks that up automatically and reconnects after a few seconds. I, too, wish the times of modprobe were over. Cheers, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
participants (4)
-
Anne Wilson -
Bruno Friedmann -
Sebastian Kügler -
Александр Мелентьев