[opensuse] wlan will not initialize
I have a lenovo 3000 V200 laptop using openSUSE 11.4. The wireless was working fine before, but I could not get Knetwork manager to work, which I eventually found was an unresolved bug. So I have had to do the traditional method using Yast to manage networks. The wireless card I have is: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61) as listed on the pci bus. The driver is iwlagn. When I tried ifup wlan0, I get this response: wlan0 device: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61) wlan0 starting wpa_supplicant Could not set interface wlan0 flags: Unknown error 132 Could not set interface 'wlan0' UP Failed to initialize driver interface RTNETLINK answers: Unknown error 132 Starting DHCP4 client on wlan0. . wlan0 DHCP4 client NOT running RTNETLINK answers: Unknown error 132 Cannot enable interface wlan0. interface wlan0 is not up Now here is the story of how this all started. I was using traditional method to manage the network card in Yast, and had disabled knetwork manager. It ran fine for several weeks. Then I brought my laptop to another person's house, and to connect there I went into Yast and changed the SSID and the password (which was actually an open network with no password) to match the settings there and connected. When I returned home, I went back into Yast and changed the settings back to my home setting again. But I made a mistake and had the first letter of my network password capitalized when it should have been lower case. The connection would cycle on and off repeatedly (I use knemo to monitor my connection). The next day I realized it was the capital letter that needed to be lower case, so I changed that. Now when I boot up, knemo starts and indicates that wlan0 is down. I am at a loss as to what to do next to try and get my network card back up and running. George -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/05/2011 06:00 PM, George Olson wrote:
I have a lenovo 3000 V200 laptop using openSUSE 11.4. The wireless was working fine before, but I could not get Knetwork manager to work, which I eventually found was an unresolved bug. <snip> The driver is iwlagn.
When I tried ifup wlan0, I get this response:
wlan0 device: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61) wlan0 starting wpa_supplicant Could not set interface wlan0 flags: Unknown error 132 Could not set interface 'wlan0' UP Failed to initialize driver interface RTNETLINK answers: Unknown error 132 Starting DHCP4 client on wlan0. . wlan0 DHCP4 client NOT running RTNETLINK answers: Unknown error 132 Cannot enable interface wlan0. interface wlan0 is not up
<snip>
I am at a loss as to what to do next to try and get my network card back up and running.
George
George, I use the traditional method by default. In yast -> Network Settings, I do the following: Global Options: [x] Traditional Method with ifup Overview: (select your wireless adapter and click 'Edit') General: Activate device -> At Boot Time Address: DHCP (both 4 & 6) Hardware: Module Name (Make sure you select your 'iwlagn' or proper module) Then it is just a matter of configuring your wireless access point settings and authentication. All this does is generate your /etc/sysconfig/network/ifcfg-wlan0 (or 1, etc..) file for you. In there, you should have something similar to: 18:22 alchemy:/etc/sysconfig/network> sudo cat ifcfg-wlan0 BOOTPROTO='dhcp' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='' MTU='' NAME='AR5001 Wireless Network Adapter' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' USERCONTROL='no' WIRELESS_AP='' WIRELESS_AP_SCANMODE='1' WIRELESS_AUTH_MODE='psk' WIRELESS_BITRATE='auto' WIRELESS_CA_CERT='' WIRELESS_CHANNEL='' WIRELESS_CLIENT_CERT='' WIRELESS_CLIENT_KEY='' WIRELESS_CLIENT_KEY_PASSWORD='' WIRELESS_DEFAULT_KEY='0' WIRELESS_EAP_AUTH='' WIRELESS_EAP_MODE='' WIRELESS_ESSID='skyline' WIRELESS_FREQUENCY='' WIRELESS_KEY='' WIRELESS_KEY_0='' WIRELESS_KEY_1='' WIRELESS_KEY_2='' WIRELESS_KEY_3='' WIRELESS_KEY_LENGTH='128' WIRELESS_MODE='Managed' WIRELESS_NICK='' WIRELESS_NWID='' WIRELESS_PEAP_VERSION='' WIRELESS_POWER='yes' WIRELESS_WPA_ANONID='' WIRELESS_WPA_IDENTITY='' WIRELESS_WPA_PASSWORD='' WIRELESS_WPA_PSK='notmyrealpassword' If you use wpa and your box uses wpa_supplicant, then you will also need to check that the wpa_supplicant.conf file was generated and in /etc/wpa_supplicant. It will be similar to the following at a bare minimum: 18:24 alchemy:/etc/wpa_supplicant> sudo cat wpa_supplicant.conf ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel network={ ssid="skyline" key_mgmt=WPA-PSK psk=660d3df48ac7d4e1838a5ce0f4fcca57ba8a0c98317bc31....... } Check those and then issue the sudo rcnetwork stop and sudo rcnetwork start and check the log file to see what is happening and post if unsuccessful. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/06/2011 07:28 AM, David C. Rankin wrote:
George, I use the traditional method by default. In yast -> Network Settings, I do the following:
Global Options: [x] Traditional Method with ifup
Overview: (select your wireless adapter and click 'Edit')
General: Activate device -> At Boot Time Address: DHCP (both 4 & 6) Hardware: Module Name (Make sure you select your 'iwlagn' or proper module)
Ok, I checked all those settings and they are the same. I had actually had DHCP only running on 4 (because 6 was slowing down my network before, not being available in my location), but I put it on 4 and 6. That was the only change I made on this.
Then it is just a matter of configuring your wireless access point settings and authentication. All this does is generate your /etc/sysconfig/network/ifcfg-wlan0 (or 1, etc..) file for you. In there, you should have something similar to:
18:22 alchemy:/etc/sysconfig/network> sudo cat ifcfg-wlan0 BOOTPROTO='dhcp' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='' MTU='' NAME='AR5001 Wireless Network Adapter' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' USERCONTROL='no' WIRELESS_AP='' WIRELESS_AP_SCANMODE='1' WIRELESS_AUTH_MODE='psk' WIRELESS_BITRATE='auto' WIRELESS_CA_CERT='' WIRELESS_CHANNEL='' WIRELESS_CLIENT_CERT='' WIRELESS_CLIENT_KEY='' WIRELESS_CLIENT_KEY_PASSWORD='' WIRELESS_DEFAULT_KEY='0' WIRELESS_EAP_AUTH='' WIRELESS_EAP_MODE='' WIRELESS_ESSID='skyline' WIRELESS_FREQUENCY='' WIRELESS_KEY='' WIRELESS_KEY_0='' WIRELESS_KEY_1='' WIRELESS_KEY_2='' WIRELESS_KEY_3='' WIRELESS_KEY_LENGTH='128' WIRELESS_MODE='Managed' WIRELESS_NICK='' WIRELESS_NWID='' WIRELESS_PEAP_VERSION='' WIRELESS_POWER='yes' WIRELESS_WPA_ANONID='' WIRELESS_WPA_IDENTITY='' WIRELESS_WPA_PASSWORD='' WIRELESS_WPA_PSK='notmyrealpassword'
The only difference between my settings and yours is that my WIRELESS_KEY_LENGTH is 64. I don't know if that would make any difference. I am using WPA-PSK.
If you use wpa and your box uses wpa_supplicant, then you will also need to check that the wpa_supplicant.conf file was generated and in /etc/wpa_supplicant. It will be similar to the following at a bare minimum:
18:24 alchemy:/etc/wpa_supplicant> sudo cat wpa_supplicant.conf ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel
The above 2 lines are in my wpa_supplicant.conf file also.
network={ ssid="skyline" key_mgmt=WPA-PSK psk=660d3df48ac7d4e1838a5ce0f4fcca57ba8a0c98317bc31....... }
The above lines of code are not in my wpa_supplicant.conf file. Only the first 2 lines that I mentioned above. I don't know if that is the cause that wlan0 will not come up?
Check those and then issue the sudo rcnetwork stop and sudo rcnetwork start and check the log file to see what is happening and post if unsuccessful.
Which log file do I check? I am not sure where to look.
I did a rcnetwork stop and rcnetwork start, and this is what I got:
george:/etc/wpa_supplicant # rcnetwork start
Hint: you may set mandatory devices in /etc/sysconfig/network/config
Setting up network interfaces:
eth0 device: Broadcom Corporation NetLink BCM5906M Fast
Ethernet PCI Express (rev 02)
eth0 is controlled by ifplugd
eth0 waiting
wlan0 device: Intel Corporation PRO/Wireless 4965 AG or AGN
[Kedron] Network Connection (rev 61)
wlan0 starting wpa_supplicant
Could not set interface wlan0 flags: Unknown error 132
Could not set interface 'wlan0' UP
Failed to initialize driver interface
RTNETLINK answers: Unknown error 132
wlan0 Starting DHCP4 client. .
wlan0 DHCP4 client NOT running
RTNETLINK answers: Unknown error 132
Cannot enable interface wlan0.
interface wlan0 is not up
wlan0 failed
Setting up service network . . . . . . . . . . done
SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
SuSEfirewall2: Firewall rules successfully set
After running rcnetwork stop and then rcnetwork start, my eth0
connection is no longer working. I didn't change a thing with that. It
connects to the router and gets a dhcp IP address, but will not
connect to the internet. Meanwhile my wife sits next to me with her
laptop connected to the internet without any problem at all.
And now I have just rebooted my pc, and it still won't connect to the
internet at all even by ethernet. My eth0 connection is up, and I have
an ip address, but I cannot get past my router. I just ran ifstatus
eth0, and this is what I got:
george:/home/george # ifstatus eth0
eth0 device: Broadcom Corporation NetLink BCM5906M Fast
Ethernet PCI Express (rev 02)
eth0 ifplugd is running
eth0 cable is connected
DHCP4 client (dhcpcd) is running
IP address: 192.168.0.103/24
DHCP6 client (dhclient6) is running
. . . but is still waiting for data
eth0 is up
2: eth0:
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/06/2011 07:28 AM, David C. Rankin wrote:
On 11/05/2011 06:00 PM, George Olson wrote:
I have a lenovo 3000 V200 laptop using openSUSE 11.4. The wireless was working fine before, but I could not get Knetwork manager to work, which I eventually found was an unresolved bug. <snip> The driver is iwlagn.
When I tried ifup wlan0, I get this response:
wlan0 device: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61) wlan0 starting wpa_supplicant Could not set interface wlan0 flags: Unknown error 132 Could not set interface 'wlan0' UP Failed to initialize driver interface RTNETLINK answers: Unknown error 132 Starting DHCP4 client on wlan0. . wlan0 DHCP4 client NOT running RTNETLINK answers: Unknown error 132 Cannot enable interface wlan0. interface wlan0 is not up
<snip>
I am at a loss as to what to do next to try and get my network card back up and running.
George
George, I use the traditional method by default. In yast -> Network Settings, I do the following:
Global Options: [x] Traditional Method with ifup
Overview: (select your wireless adapter and click 'Edit')
General: Activate device -> At Boot Time Address: DHCP (both 4 & 6) Hardware: Module Name (Make sure you select your 'iwlagn' or proper module)
Then it is just a matter of configuring your wireless access point settings and authentication. All this does is generate your /etc/sysconfig/network/ifcfg-wlan0 (or 1, etc..) file for you. In there, you should have something similar to:
18:22 alchemy:/etc/sysconfig/network> sudo cat ifcfg-wlan0 BOOTPROTO='dhcp' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='' MTU='' NAME='AR5001 Wireless Network Adapter' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' USERCONTROL='no' WIRELESS_AP='' WIRELESS_AP_SCANMODE='1' WIRELESS_AUTH_MODE='psk' WIRELESS_BITRATE='auto' WIRELESS_CA_CERT='' WIRELESS_CHANNEL='' WIRELESS_CLIENT_CERT='' WIRELESS_CLIENT_KEY='' WIRELESS_CLIENT_KEY_PASSWORD='' WIRELESS_DEFAULT_KEY='0' WIRELESS_EAP_AUTH='' WIRELESS_EAP_MODE='' WIRELESS_ESSID='skyline' WIRELESS_FREQUENCY='' WIRELESS_KEY='' WIRELESS_KEY_0='' WIRELESS_KEY_1='' WIRELESS_KEY_2='' WIRELESS_KEY_3='' WIRELESS_KEY_LENGTH='128' WIRELESS_MODE='Managed' WIRELESS_NICK='' WIRELESS_NWID='' WIRELESS_PEAP_VERSION='' WIRELESS_POWER='yes' WIRELESS_WPA_ANONID='' WIRELESS_WPA_IDENTITY='' WIRELESS_WPA_PASSWORD='' WIRELESS_WPA_PSK='notmyrealpassword'
If you use wpa and your box uses wpa_supplicant, then you will also need to check that the wpa_supplicant.conf file was generated and in /etc/wpa_supplicant. It will be similar to the following at a bare minimum:
18:24 alchemy:/etc/wpa_supplicant> sudo cat wpa_supplicant.conf ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel
network={ ssid="skyline" key_mgmt=WPA-PSK psk=660d3df48ac7d4e1838a5ce0f4fcca57ba8a0c98317bc31....... }
Check those and then issue the sudo rcnetwork stop and sudo rcnetwork start and check the log file to see what is happening and post if unsuccessful.
Unbelievable. Without any explanation, it started working again. I shut it down and left it for an hour and then restarted it, and the network came up and works fine now. I wonder if it could possibly be a problem with internal heat? My laptop seems to get a lot hotter than it used to. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* George Olson
Unbelievable. Without any explanation, it started working again. I shut it down and left it for an hour and then restarted it, and the network came up and works fine now.
I wonder if it could possibly be a problem with internal heat? My laptop seems to get a lot hotter than it used to. To contact the owner, e-mail: opensuse+owner@opensuse.org
take the cover off the fan compartment and clean the compartment. ps: please consider trimming your quotes. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Patrick Shanahan said the following on 11/06/2011 08:31 AM:
* George Olson
[11-06-11 01:31]: Unbelievable. Without any explanation, it started working again. I shut it down and left it for an hour and then restarted it, and the network came up and works fine now.
I wonder if it could possibly be a problem with internal heat? My laptop seems to get a lot hotter than it used to. To contact the owner, e-mail: opensuse+owner@opensuse.org
take the cover off the fan compartment and clean the compartment.
I have long-haired cats so congested fans is a perennial problem for me. Use a paper-clip to 'lock' the fan blades and prevent them spinning, then you can use a vacuum cleaner. -- My definition of an expert in any field is a person who knows enough about what's really going on to be scared. P. J. Plauger, Computer Language, March 1983 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/06/2011 10:31 PM, Anton Aylward wrote:
I have long-haired cats so congested fans is a perennial problem for me.
Use a paper-clip to 'lock' the fan blades and prevent them spinning, then you can use a vacuum cleaner.
ok, thanks guys. will do. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/06/2011 07:31 AM, Patrick Shanahan wrote:
* George Olson
[11-06-11 01:31]: Unbelievable. Without any explanation, it started working again. I shut it down and left it for an hour and then restarted it, and the network came up and works fine now.
I wonder if it could possibly be a problem with internal heat? My laptop seems to get a lot hotter than it used to. To contact the owner, e-mail: opensuse+owner@opensuse.org
take the cover off the fan compartment and clean the compartment.
Heat is most likely your culprit... Another method that works well is to turn you laptop off, unplug it and flip it over. You will generally find 1-2 fans behind plastic/metal grills on the bottom. What you need to do is shop-vac out the air flow passages in the laptop and you can do it without doing laptop brain surgery. However YOU MUST PEG THE FANS before you even think about putting the vacuum to the bottom of your laptop. (it prevents the 170 mph airflow produced by the vacuum suck from shredding the fans in your laptop) (1) take a standard paper-clip and open it up until it is roughly in the shape of a C. Locate the fans on the bottom and put each end of the C through each fan grill so that it extends through the fan and will prevent it from spinning. (if you have 2 fans, peg them both) Then, and only then, take the shop vac, and while holding the paper-clip so it doesn't get sucked out, put the full power of the shop vac over the fan grill so you are pulling all the dust/lint out of the laptop cooling path. Repeat 3-4 times on each fan. (2) now you will probably have several lumps of lint/dust (each roughly the size of a dead ferret) caught on the inside of the fan grill and your wondering "how in the heck am I ever going to get those things out?" There are two methods that work. (a) rub your thumb over the fan grill back and forth and it will grab the lint strands and work them back through the fan grill over the course of a minute or so, or (b) take a small gauge piece of wire (like the inside of a twisty-tie) and bend the last 1/8 inch back over on itself so you have made basically a tiny fishhook. (small enough so it can pass through a grill square and back out the same way) Then just dab it through and snag the fuzz and pull it out. If during either (a) or (b) the fuzz falls back into the laptop, repeat step (1). By applying the vacuum and pulling the air 'backwards' through the cooling path, you will dramatically clean the cooling path of the laptop without having to disassemble it. This will generally eliminate all cooling problems with older laptops. Just don't forget to peg the fans or they will literally reach 'take-off' velocity when you hit them with the vacuum. Good luck. Repeat every year or so or when symptoms return... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/08/2011 12:35 PM, David C. Rankin wrote:
On 11/06/2011 07:31 AM, Patrick Shanahan wrote:
Repeat every year or so or when symptoms return...
Thanks for taking time to write all that down. I will clean it out and get the machine back up and running well! George -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Anton Aylward
-
David C. Rankin
-
George Olson
-
George OLson
-
Patrick Shanahan