Arch Linux

rzrscm

Member

Registered: 2012-11-17

Posts: 95

[S0LVED] Can't connect to wireless network...

I'm unable to connect to my wireless network.  I'm on a Thinkpad T41p and I installed the ipw2100 firmware for my chipset.  The wifi indicator is blinking, assumingly indicating activity.

When I try to use wifi-menu to connect to my network, it gives me a "failed to connect" error when I try to connect...But with netctl-auto enabled, it just tells me that my interface is controlled by netctl-auto and does nothing.  When I try to scan with "iw dev wlp2s2 scan | grep SSID", it shows...

command failed: Operation not suppored (-95)

When I run wpa_cli, I get the following messages over and over again...

<3>CTRL-EVENT-SCAN-RESULTS
<3>Trying to associate with e0:91:f5:dc:14:24 (SSID='MYSSIDE' freq=2452 MHz)
<3>Association request to the driver failed
<3>CTRL-EVENT-SCAN-RESULTS
<3> Authentication with e0:91:f5:dc:14:24 timed out.
<3>CTRL-EVENT-DISCONNECTED bssid=e0:91:f5:dc:14:24 reason=3 locally_generated=1

I tried running netctl-auto switch-to on the profile, and all it showed was  "WPA association/authentication failed for interface 'wlp2s2'".

As far as I can tell, nothing else is trying to manage my network, and I can't find anything that indicates that anything's wrong in dmesg.

lspci -nnvk | grep -A10 -i net...

02:01.0 Ethernet controller [0200]: Intel Corporation 82540EP Gigabit Ethernet Controller (Mobile) [8086:101e] (rev 03)
	Subsystem: IBM Thinkpad [1014:0549]
	Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11
	Memory at c0220000 (32-bit, non-prefetchable) [size=128K]
	Memory at c0200000 (32-bit, non-prefetchable) [size=64K]
	I/O ports at 8000 [size=64]
	[virtual] Expansion ROM at c0240000 [disabled] [size=64K]
	Capabilities: [dc] Power Management version 2
	Capabilities: [f0] MSI: Enable- Count=1/1 Maskable- 64bit+
	Kernel driver in use: e1000
	Kernel modules: e1000
--
02:02.0 Network controller [0280]: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter [8086:1043] (rev 04)
	Subsystem: Intel Corporation Device [8086:2551]
	Flags: bus master, medium devsel, latency 64, IRQ 11
	Memory at c0214000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: [dc] Power Management version 2
	Kernel driver in use: ipw2100
	Kernel modules: ipw2100

ip link...

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: irda0: <NOARP> mtu 2048 qdisc noop state DOWN mode DEFAULT qlen 8
    link/irda 00:00:00:00 brd ff:ff:ff:ff
3: enp2s1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT qlen 1000
    link/ether 00:0d:60:5f:57:cf brd ff:ff:ff:ff:ff:ff
4: wlp2s2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DORMANT qlen 1000
    link/ether 00:0c:f1:0c:c4:36 brd ff:ff:ff:ff:ff:ff

ip addr...

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: irda0: <NOARP> mtu 2048 qdisc noop state DOWN qlen 8
    link/irda 00:00:00:00 brd ff:ff:ff:ff
3: enp2s1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether 00:0d:60:5f:57:cf brd ff:ff:ff:ff:ff:ff
4: wlp2s2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether 00:0c:f1:0c:c4:36 brd ff:ff:ff:ff:ff:ff

dmesg | grep firmware usually shows nothing regarding the firmware, but sometimes it'll show the following until I restart...

[ 325.258396] ipw2100: Fatal interrupt.  Scheduling firmware restart.

Last edited by rzrscm (2013-10-22 11:59:06)

/dev/zero

Member

From: Melbourne, Australia

Registered: 2011-10-20

Posts: 1,247

Re: [S0LVED] Can't connect to wireless network...

It would help if you please copy-paste actual commands and outputs (wrapped in code tags) and also more detailed hardware info such as output from:

lspci -nnvk | grep -A10 -i net

rzrscm

Member

Registered: 2012-11-17

Posts: 95

Re: [S0LVED] Can't connect to wireless network...

It would help if you please copy-paste actual commands and outputs (wrapped in code tags) and also more detailed hardware info such as output from:

lspci -nnvk | grep -A10 -i net

Sorry...My laptop isn't connected to the internet right now and I'm working in the console since I haven't installed a WM or anything...I'll try to get that ASAP.

rzrscm

Member

Registered: 2012-11-17

Posts: 95

Re: [S0LVED] Can't connect to wireless network...

Also, here's what iwconfig gives me...Not sure if it's useful.

wlp2s2    unassociated  ESSID:off/any  Nickname:"ipw2100"
          Mode:Managed  Channel=0  Access Point: Not-Associated   
          Bit Rate:0 kb/s   Tx-Power:16 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

I also tried to connect to an unencrypted network, and I still couldn't connect.

Last edited by rzrscm (2013-10-22 07:08:40)

/dev/zero

Member

From: Melbourne, Australia

Registered: 2011-10-20

Posts: 1,247

Re: [S0LVED] Can't connect to wireless network...

With more information, I can now say that I can't help you with everything - but I will respond to what I can.

When I try to scan with "iw dev wlp2s2 scan | grep SSID", it shows...

command failed: Operation not suppored (-95)

Did you run that command with sudo? When I try running it as a normal user I also get an error but it works if I sudoise it.

ip link...

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: irda0: <NOARP> mtu 2048 qdisc noop state DOWN mode DEFAULT qlen 8
    link/irda 00:00:00:00 brd ff:ff:ff:ff
3: enp2s1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT qlen 1000
    link/ether 00:0d:60:5f:57:cf brd ff:ff:ff:ff:ff:ff
4: wlp2s2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DORMANT qlen 1000
    link/ether 00:0c:f1:0c:c4:36 brd ff:ff:ff:ff:ff:ff

ip addr...

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: irda0: <NOARP> mtu 2048 qdisc noop state DOWN qlen 8
    link/irda 00:00:00:00 brd ff:ff:ff:ff
3: enp2s1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether 00:0d:60:5f:57:cf brd ff:ff:ff:ff:ff:ff
4: wlp2s2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether 00:0c:f1:0c:c4:36 brd ff:ff:ff:ff:ff:ff

Both of those commands say that your wifi card is in a DOWN state. Try running

sudo ip link set dev wlp2s2 up

and try again to make a connection.

rzrscm

Member

Registered: 2012-11-17

Posts: 95

Re: [S0LVED] Can't connect to wireless network...

With more information, I can now say that I can't help you with everything - but I will respond to what I can.

When I try to scan with "iw dev wlp2s2 scan | grep SSID", it shows...

command failed: Operation not suppored (-95)

Did you run that command with sudo? When I try running it as a normal user I also get an error but it works if I sudoise it.

ip link...

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: irda0: <NOARP> mtu 2048 qdisc noop state DOWN mode DEFAULT qlen 8
    link/irda 00:00:00:00 brd ff:ff:ff:ff
3: enp2s1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT qlen 1000
    link/ether 00:0d:60:5f:57:cf brd ff:ff:ff:ff:ff:ff
4: wlp2s2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DORMANT qlen 1000
    link/ether 00:0c:f1:0c:c4:36 brd ff:ff:ff:ff:ff:ff

ip addr...

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: irda0: <NOARP> mtu 2048 qdisc noop state DOWN qlen 8
    link/irda 00:00:00:00 brd ff:ff:ff:ff
3: enp2s1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether 00:0d:60:5f:57:cf brd ff:ff:ff:ff:ff:ff
4: wlp2s2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether 00:0c:f1:0c:c4:36 brd ff:ff:ff:ff:ff:ff

Both of those commands say that your wifi card is in a DOWN state. Try running

sudo ip link set dev wlp2s2 up

and try again to make a connection.

I've tried this a bunch of times with no results...This time after I tried it, I checked dmesg and the fatal interrupt message was there...So I'm guessing this error is in response to that command.

ipw2100: Fatal interrupt.  Scheduling firmware restart.

/dev/zero

Member

From: Melbourne, Australia

Registered: 2011-10-20

Posts: 1,247

Re: [S0LVED] Can't connect to wireless network...

I've tried this a bunch of times with no results...This time after I tried it, I checked dmesg and the fatal interrupt message was there...So I'm guessing this error is in response to that command.

ipw2100: Fatal interrupt.  Scheduling firmware restart.

Okay. Now try googling that error. Hint: I see a bunch of similar complaints by other people. (The bad news is I don't see any easy fixes. There is no good news.)

rzrscm

Member

Registered: 2012-11-17

Posts: 95

Re: [S0LVED] Can't connect to wireless network...

I've tried this a bunch of times with no results...This time after I tried it, I checked dmesg and the fatal interrupt message was there...So I'm guessing this error is in response to that command.

ipw2100: Fatal interrupt.  Scheduling firmware restart.

Okay. Now try googling that error. Hint: I see a bunch of similar complaints by other people. (The bad news is I don't see any easy fixes. There is no good news.)

Thanks for the help...It looks like the solution is to get a new wireless card.