You are not logged in.

Pages: 1

#1 2012-08-08 03:03:45

inkdinky
Member
Registered: 2011-12-08
Posts: 66

Wireless fails after pacman update

I had my wireless functional but after the latest set of updates it somehow broke.
It's a Broadcom wireless that uses the b43 driver.
I wrote myself a little cheater list when I first set up the wireless. The commands appear okay but when I attempt to get to the net I get a network unreachable error when I attempt to ping anything.

sudo ip link set wlan0 up
sudo iwlist wlan0 scan | grep ESSID

I see the available wireless. 2WIRE824 is my router.

      
        ESSID:"2WIRE824"
                    ESSID:"Enforcer24GHz"
                    ESSID:"2WIRE409"
                    ESSID:"2WIRE907"
                    ESSID:"BAMFs"

I submit my key and attempt to connect to my router

sudo iwconfig wlan0 essid "2WIRE824" key **mykey**
sudo dhcpcd wlan0

returns --> dhcpcd[797]: sending commands to master dhcpcd process
now when I try to ping anything I get network unreachable.
What has changed (or what am I missing) that broke the wireless?
I have all my wireless profiles that haven't changed and they are still listed in /etc/rc.conf

I've even tried 

sudo iwconfig wlan0 channel auto

despite my cheatsheet stating to use that only if the dhcpcd times out.


snippet from dmesg

[   10.204558] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
[   12.331304] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   12.333498] e100 0000:02:08.0: eth0: NIC Link is Up 100 Mbps Full Duplex
[   12.480083] b43-phy0: Loading firmware version 508.1084 (2009-01-14 01:32:01)
[   12.547890] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   12.548137] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   23.096727] eth0: no IPv6 routers present
[arch-nicky@arch-nicky ~]$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 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
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:ff:ff:ff:8b:78 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.82/24 brd 192.168.1.255 scope global eth0
    inet6 fe80::fff:ffff:fe1e:8b78/64 scope link 
       valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether 00:14:a5:0d:64:e5 brd ff:ff:ff:ff:ff:ff
[arch-nicky@arch-nicky ~]$  ip link set wlan0 up
RTNETLINK answers: Operation not permitted

I feel like the above output has something to do with it. Is wlan0 still down? Why didn't it go up? And why no error message that it didn't successfully go up?



from
sudo less /var/log/messages.log

Aug  7 18:52:59 localhost kernel: [    6.942500] b43-phy0: Broadcom 4318 WLAN found (core revision 9)
Aug  7 18:52:59 localhost kernel: [    6.957385] e100 0000:02:08.0: eth0: addr 0xdfdfd000, irq 20, MAC addr 00:12:3f:1e:8b:78
Aug  7 18:52:59 localhost kernel: [    6.996832] Broadcom 43xx driver loaded [ Features: PMNLS ]
Aug  7 18:52:59 localhost kernel: [    7.310498] [drm] initialized overlay support

Aug  7 18:52:59 localhost kernel: [   12.437978] ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug  7 18:52:59 localhost kernel: [   12.440172] e100 0000:02:08.0: eth0: NIC Link is Up 100 Mbps Full Duplex
Aug  7 18:52:59 localhost kernel: [   12.586739] b43-phy0: Loading firmware version 508.1084 (2009-01-14 01:32:01)
Aug  7 18:52:59 localhost kernel: [   12.659863] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Aug  7 18:52:59 localhost kernel: [   12.660131] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Aug  7 18:52:59 localhost dhcpcd[281]: eth0: sending IPv6 Router Solicitation
Aug  7 18:52:59 localhost dhcpcd[281]: eth0: rebinding lease of 192.168.0.6
Aug  7 18:52:59 localhost dhcpcd[281]: wlan0: sending IPv6 Router Solicitation
Aug  7 18:52:59 localhost dhcpcd[281]: wlan0: broadcasting for a lease


Aug  7 18:52:59 localhost kernel: [    6.957385] e100 0000:02:08.0: eth0: addr 0xdfdfd000, irq 20, MAC addr 00:12:3f:1e:8b:78
Aug  7 18:52:59 localhost kernel: [    6.996832] Broadcom 43xx driver loaded [ Features: PMNLS ]
Aug  7 18:52:59 localhost kernel: [    7.310498] [drm] initialized overlay support

Aug  7 18:52:59 localhost kernel: [   12.437978] ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug  7 18:52:59 localhost kernel: [   12.440172] e100 0000:02:08.0: eth0: NIC Link is Up 100 Mbps Full Duplex
Aug  7 18:52:59 localhost kernel: [   12.586739] b43-phy0: Loading firmware version 508.1084 (2009-01-14 01:32:01)
Aug  7 18:52:59 localhost kernel: [   12.659863] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Aug  7 18:52:59 localhost kernel: [   12.660131] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Aug  7 18:52:59 localhost dhcpcd[281]: eth0: sending IPv6 Router Solicitation
Aug  7 18:52:59 localhost dhcpcd[281]: eth0: rebinding lease of 192.168.0.6
Aug  7 18:52:59 localhost dhcpcd[281]: wlan0: sending IPv6 Router Solicitation
Aug  7 18:52:59 localhost dhcpcd[281]: wlan0: broadcasting for a lease

Aug  7 18:52:59 localhost dhcpcd[281]: eth0: NAK: from 192.168.1.254
Aug  7 18:53:00 localhost dhcpcd[281]: wlan0: carrier lost
Aug  7 18:53:00 localhost dhcpcd[281]: eth0: sending IPv6 Router Solicitation
Aug  7 18:53:00 localhost dhcpcd[281]: eth0: broadcasting for a lease
Aug  7 18:53:01 localhost dhcpcd[281]: eth0: offered 192.168.1.82 from 192.168.1.254
Aug  7 18:53:01 localhost dhcpcd[281]: eth0: acknowledged 192.168.1.82 from 192.168.1.254
Aug  7 18:53:01 localhost dhcpcd[281]: eth0: checking for 192.168.1.82
Aug  7 18:53:03 localhost dhcpcd[281]: wlan0: sending IPv6 Router Solicitation
Aug  7 18:53:04 localhost dhcpcd[281]: eth0: sending IPv6 Router Solicitation
Aug  7 18:53:06 localhost dhcpcd[281]: eth0: leased 192.168.1.82 for 86400 seconds
Aug  7 18:53:06 localhost dhcpcd[281]: forked to background, child pid 339
Aug  7 18:53:07 localhost dhcpcd[339]: wlan0: sending IPv6 Router Solicitation
Aug  7 18:53:08 localhost dhcpcd[339]: eth0: sending IPv6 Router Solicitation
Aug  7 18:53:11 localhost dhcpcd[339]: wlan0: sending IPv6 Router Solicitation
Aug  7 18:53:11 localhost dhcpcd[339]: wlan0: no IPv6 Routers available
Aug  7 18:53:12 localhost dhcpcd[339]: eth0: sending IPv6 Router Solicitation
Aug  7 18:53:12 localhost dhcpcd[339]: eth0: no IPv6 Routers available

Any thoughts/ideas/ or add'l info to help debug?

Thanks!

Offline

#2 2012-08-08 03:46:41

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,690

Re: Wireless fails after pacman update

Have you changed from initscripts to systemd?

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Offline

#3 2012-08-08 23:33:54

inkdinky
Member
Registered: 2011-12-08
Posts: 66

Re: Wireless fails after pacman update

Nope. Still using initscripts as far as I know.
"which systemd" didn't return anything.

Last edited by inkdinky (2012-08-09 00:01:26)

Offline

#4 2012-08-09 00:30:23

nomorewindows
Member
Registered: 2010-04-03
Posts: 3,542

Re: Wireless fails after pacman update

You would have to have init=/bin/systemd in your kernel boot parameters.
Which would require systemd to be installed.

I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

Offline

#5 2012-08-09 03:11:43

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,690

Re: Wireless fails after pacman update

I had asked about systemd because I have noticed it sometimes starts things that have been installed and are lying around dormant if they were not in the DAEMONS array.  I have been bitten...
So, you said...

inkdinky wrote:

...
I submit my key and attempt to connect to my router

sudo iwconfig wlan0 essid "2WIRE824" key **mykey**
sudo dhcpcd wlan0

I would like to see the output of a second iwconfig without any switches or parameters performed a few seconds after that first one, just as you wrote it.  I want to establish if you are actually associating with the AP.  You should see the MAC of the AP in that output.

Then, you said

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:ff:ff:ff:8b:78 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.82/24 brd 192.168.1.255 scope global eth0
    inet6 fe80::fff:ffff:fe1e:8b78/64 scope link 
       valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether 00:14:a5:0d:64:e5 brd ff:ff:ff:ff:ff:ff

Okay, the wlan has no address, as expected.  The carrier, however should be up.  

[arch-nicky@arch-nicky ~]$  ip link set wlan0 up
RTNETLINK answers: Operation not permitted

But you have to run that as root tongue

So, put the interface up as root.
Try to associate with sudo iwconfig wlan0 essid "2WIRE824" key **mykey**
Pause.  Run iwconfig
If it associates, then run dhcpcd wlan0  .  Don't waste your time if it does not associate. 
If you are still having trouble, look at the output of rfkill list

One last thought.  Are you trying to connect to the same router as you are wired to?  You should be able to associate, but you may have routing issues later.

Last edited by ewaller (2012-08-09 03:12:10)

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Offline

#6 2012-08-11 15:24:33

stevepa
Member
From: Texas USA
Registered: 2012-02-12
Posts: 113

Re: Wireless fails after pacman update

Curious if this issue got solved and what it was.
thanks
steve.

Arch - LVM - ext4 - gnome (T60p 14.1 1400p  x86_64), (T60 15 flexview 1400p i686)

Offline

#7 2012-09-11 02:05:47

inkdinky
Member
Registered: 2011-12-08
Posts: 66

Re: Wireless fails after pacman update

No this was never resolved sad
I just completely updated (via ethernet) the system after not working on this since my last post.
I'm now running systemd.

[arch-nicky@arch-nicky ~]$ sudo iwconfig wlan0 essid "2WIRE824" key **my key**
[arch-nicky@arch-nicky ~]$ iwconfig
wlan0     IEEE 802.11bg  ESSID:"2WIRE824"  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          
lo        no wireless extensions.

eth0      no wireless extensions.

[arch-nicky@arch-nicky ~]$ dhcpcd wlan0
dhcpcd[737]: open_control: Permission denied
dhcpcd[737]: dhcpcd will not work correctly unless run as root
dhcpcd[737]: open `/run/dhcpcd-wlan0.pid': Permission denied
dhcpcd[737]: version 5.6.0 starting
dhcpcd[737]: ipv6rs: Operation not permitted
dhcpcd[737]: wlan0: if_init: Permission denied
dhcpcd[737]: wlan0: interface not found or invalid
[arch-nicky@arch-nicky ~]$ sudo dhcpcd wlan0
dhcpcd[740]: sending commands to master dhcpcd process
[arch-nicky@arch-nicky ~]$ rfkill list
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

This is what I get.

Offline

#8 2012-09-11 02:12:42

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,690

Re: Wireless fails after pacman update

The dhcpcd command must be run as root

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Offline

#9 2012-09-11 02:26:08

inkdinky
Member
Registered: 2011-12-08
Posts: 66

Re: Wireless fails after pacman update

I ran it both as root and as user. Neither seems to get me anywhere.

Offline

Pages: 1

Board footer

Powered by FluxBB