[solved] WiFi - no carrier

ignas · 2017-11-30 20:37:22

I'm using the

broadcom-wl-dkms

driver with the appropriate dkms and linux-header packages. Running

ip link

yields me this:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp7s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 74:86:7a:2b:50:57 brd ff:ff:ff:ff:ff:ff
3: wlp8s0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state DORMANT mode DORMANT group default qlen 1000
    link/ether 9c:2a:70:d8:d0:c7 brd ff:ff:ff:ff:ff:ff

I've also set up wpa_supplicant to work, and running it tells me that it completed its task successfully. Running

sudo dhcpcd wlp8s0

will leave it stuck on

wlp8s0: waiting for carrier

, until it times out.
What's really weird is that the same setup worked in my previous installation of Arch.
Any help would be appreciated.

Last edited by ignas (2017-12-20 16:28:16)

boojum · 2017-12-02 08:55:17

ignas wrote:

I've also set up wpa_supplicant to work

I'm assuming that you're connecting manually (as per wiki)? Have you tried running dhcpcd with the --debug option? What's the the output?

Oh, and welcome to Arch Linux Forums!

Last edited by boojum (2017-12-02 08:55:55)

lo1 · 2017-12-02 10:12:21

Also, try to reboot the router before you go any further. Yesterday I spent half an hour troubleshooting my connection, just to find out the router I was trying to connect to was the culprit.
If that doesn't help, try to increase dhcpcd timeout delay.

ignas · 2017-12-02 12:07:32

boojum wrote:

ignas wrote:
I've also set up wpa_supplicant to work
I'm assuming that you're connecting manually (as per wiki)? Have you tried running dhcpcd with the --debug option? What's the the output?
Oh, and welcome to Arch Linux Forums!

Thanks for your answer! Yes, I am connecting manually. Here is the output from dhcpcd:

dhcpcd-6.11.5 starting
wlp8s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' PREINIT
wlp8s0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks' NOCARRIER
wlp8s0: waiting for carrier
timed out
dhcpcd exited

lo1 wrote:

Also, try to reboot the router before you go any further. Yesterday I spent half an hour troubleshooting my connection, just to find out the router I was trying to connect to was the culprit.
If that doesn't help, try to increase dhcpcd timeout delay.

I have restarted the router, no dice. All other devices connect to it just fine.

ignas · 2017-12-02 12:11:43

Also, output from "lspci -k", describing the network controller:

08:00.0 Network controller: Broadcom Limited BCM43142 802.11b/g/n (rev 01)
        Subsystem: Dell Wireless 1704 802.11n + BT 4.0
        Kernel driver in use: wl
        Kernel modules: bcma, wl

boojum · 2017-12-02 12:13:17

Try removing old lease:

rm /var/lib/dhcpcd/dhcpcd-wlp8s0.lease

and try again.

ignas · 2017-12-02 12:20:17

boojum wrote:

Try removing old lease:
rm /var/lib/dhcpcd/dhcpcd-wlp8s0.lease
and try again.

There is only a lease file for Ethernet controller. Should I remove it?

boojum · 2017-12-02 12:25:00

ignas wrote:

There is only a lease file for Ethernet controller. Should I remove it?

No, leave it alone.
After the wpa_supplicant command, but before the dhcpcd command, check the output of iw wlp8s0 info to ensure you are associated with an access point.

As well, check if dhcpcd is not running already.

Last edited by boojum (2017-12-02 12:26:50)

ignas · 2017-12-02 12:27:36

boojum wrote:

ignas wrote:
There is only a lease file for Ethernet controller. Should I remove it?
No, leave it alone.
After the wpa_supplicant command, but before the dhcpcd command, check the output of iw wlp8s0 info to ensure you are associated with an access point.

# wpa_supplicant -B -i wlp8s0 -c /etc/wpa_supplicant.conf
Successfully initialized wpa_supplicant
# iw wlp8s0 info
Interface wlp8s0
        ifindex 3
        wdev 0x1
        addr 9c:2a:70:d8:d0:c7
        type managed
        wiphy 0

boojum · 2017-12-02 12:40:18

Can you post the output of /etc/dhcpcd.conf?

ignas · 2017-12-02 12:53:18

boojum wrote:

Can you post the output of /etc/dhcpcd.conf?

# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

# Allow users of this group to interact with dhcpcd via the control socket.
#controlgroup wheel

# Inform the DHCP server of our hostname for DDNS.
hostname

# Use the hardware address of the interface for the Client ID.
#clientid
# or
# Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361.
# Some non-RFC compliant DHCP servers do not reply with this set.
# In this case, comment out duid and enable clientid above.
duid

# Persist interface configuration when dhcpcd exits.
persistent

# Rapid commit support.
# Safe to enable by default because it requires the equivalent option set
# on the server to actually work.
option rapid_commit

# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
# Most distributions have NTP support.
option ntp_servers
# Respect the network MTU. This is applied to DHCP routes.
option interface_mtu

# A ServerID is required by RFC2131.
require dhcp_server_identifier

# Generate Stable Private IPv6 Addresses instead of hardware based ones
slaac private
noipv4ll

boojum · 2017-12-02 13:03:01

Right, we can start with setting your correct hostname in dhcpcd.conf.

Try again :-)

Comment out duid and enable clientid instead. Try again.

Another thing that comes to mind is to stop requesting / claiming the address by ARP - after wpa_suppcilant command try:

sudo dhcpcd --noarp wlp8s0

If that won't work try only IPv4 addresses:

sudo dhcpcd --ipv4only wlp8s0

I'm assuming that you did not enable dhcpcd.service? Just to be safe, you could check with

systemctl status dhcpcd.service

Wich version of dhcpcd are you running?

ignas · 2017-12-02 13:11:10

boojum wrote:

Right, we can start with setting your correct hostname in dhcpcd.conf.
Try again :-)
Comment out duid and enable clientid instead. Try again.
Another thing that comes to mind is to stop requesting / claiming the address by ARP - after wpa_suppcilant command try:
sudo dhcpcd --noarp wlp8s0
If that won't work try only IPv4 addresses:
sudo dhcpcd --ipv4only wlp8s0
I'm assuming that you did not enable dhcpcd.service? Just to be safe, you could check with
systemctl status dhcpcd.service
Wich version of dhcpcd are you running?

systemctl output:

● dhcpcd.service - dhcpcd on all interfaces
   Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; disabled; vendor preset: disabled)
   Active: inactive (dead)

I assume I haveto change the hostname like this?:
hostname DESIRED_HOSTNAME

dhcpcd-6.11.5

Last edited by ignas (2017-12-02 13:12:14)

boojum · 2017-12-02 13:15:19

ignas wrote:

hostname DESIRED_HOSTNAME

Yup.

ignas · 2017-12-02 13:35:47

boojum wrote:

ignas wrote:
hostname DESIRED_HOSTNAME
Yup.

Still nothing.

boojum · 2017-12-02 13:50:25

If you tried duid/clientid, --noarp, and --ipv4only then I almost out of ideas...

There's ticket d189b2a5ef for dhcpcd which might be relevant. Try changing time out from default 30s to, let say, 60:

sudo dhcpcd -t 60 wlp8s0

You could try connecting do your wireless either with netctl or The Systemd Way™ . Or you could always do

pacman -S dhclient

as use that as a workaround.
Other than that I dunno. I had problems with dhcpcd in the past, and broadcom cards are notorious for being $%?#!...

lo1 · 2017-12-02 13:57:29

lo1 wrote:

try to increase dhcpcd timeout delay.

...
If it doesn't work

cat /etc/wpa_supplicant/wpa_supplicant.conf

Also, I'd not assume dhcpcd is doing bad. So, instead of getting a dhcp ip address, *IF* wpa_supplicant.conf has no syntax error, start wpa_supplicant, try to assign an ip and a subnet mask (e.g.: /24), and check if you can ping the router.

EDIT: here you posted:

# wpa_supplicant -B -i wlp8s0 -c /etc/wpa_supplicant.conf

and I'm starting to think this was the problem...are you starting wpa_supplicant on purpose, with a configuration file which is not inside /etc/wpa_supplicant/ ?
If not:

wpa_supplicant -B -i wlp8s0 -c /etc/wpa_supplicant/yourconfiguration.conf

Last edited by lo1 (2017-12-02 14:07:05)

boojum · 2017-12-02 14:04:41

lo1 wrote:

try to increase dhcpcd timeout delay.

My bad, I missed it.

lo1 · 2017-12-02 14:07:35

boojum wrote:

lo1 wrote:
try to increase dhcpcd timeout delay.
My bad, I missed it.

Nevermind, but also check my last post: there's an edit you really can't miss

boojum · 2017-12-02 14:13:51

Io1 wrote:

are you starting wpa_supplicant on purpose, with a configuration file which is not inside /etc/wpa_supplicant/ ?

I be damd...
You're very much spot on here! Good catch.
(I might need more coffee...)

ignas · 2017-12-02 14:17:50

boojum wrote:

If you tried duid/clientid, --noarp, and --ipv4only then I almost out of ideas...
There's ticket d189b2a5ef for dhcpcd which might be relevant. Try changing time out from default 30s to, let say, 60:
sudo dhcpcd -t 60 wlp8s0
You could try connecting do your wireless either with netctl or The Systemd Way™ . Or you could always do
pacman -S dhclient
as use that as a workaround.
Other than that I dunno. I had problems with dhcpcd in the past, and broadcom cards are notorious for being $%?#!...

Oh well.

boojum · 2017-12-02 14:26:41

Io1 wrote:

If it doesn't work
cat /etc/wpa_supplicant/wpa_supplicant.conf
Also, I'd not assume dhcpcd is doing bad. So, instead of getting a dhcp ip address, *IF* wpa_supplicant.conf has no syntax error, start wpa_supplicant, try to assign an ip and a subnet mask (e.g.: /24), and check if you can ping the router.
EDIT: here you posted:
# wpa_supplicant -B -i wlp8s0 -c /etc/wpa_supplicant.conf
and I'm starting to think this was the problem...are you starting wpa_supplicant on purpose, with a configuration file which is not inside /etc/wpa_supplicant/ ?
If not:
wpa_supplicant -B -i wlp8s0 -c /etc/wpa_supplicant/yourconfiguration.conf

This.

ignas · 2017-12-02 14:35:34

lo1 wrote:

lo1 wrote:
try to increase dhcpcd timeout delay.
...
If it doesn't work
cat /etc/wpa_supplicant/wpa_supplicant.conf
Also, I'd not assume dhcpcd is doing bad. So, instead of getting a dhcp ip address, *IF* wpa_supplicant.conf has no syntax error, start wpa_supplicant, try to assign an ip and a subnet mask (e.g.: /24), and check if you can ping the router.
EDIT: here you posted:
# wpa_supplicant -B -i wlp8s0 -c /etc/wpa_supplicant.conf
and I'm starting to think this was the problem...are you starting wpa_supplicant on purpose, with a configuration file which is not inside /etc/wpa_supplicant/ ?
If not:
wpa_supplicant -B -i wlp8s0 -c /etc/wpa_supplicant/yourconfiguration.conf

Moved the .conf into the /etc/wpa_supplicant folder and reinitialized wpa_supplicant, everything is still the same.

lo1 · 2017-12-02 14:45:36

ignas wrote:

Moved the .conf into the /etc/wpa_supplicant folder and reinitialized wpa_supplicant, everything is still the same.

And what's inside it?

cat /etc/wpa_supplicant/wpa_supplicant.conf

P.S. pay more attention when someone gives you support and asks you a question, or the topic is going to become huge and full of noise.

ignas · 2017-12-02 14:51:47

lo1 wrote:

ignas wrote:
Moved the .conf into the /etc/wpa_supplicant folder and reinitialized wpa_supplicant, everything is still the same.
And what's inside it?
cat /etc/wpa_supplicant/wpa_supplicant.conf
P.S. pay more attention when someone gives you support and asks you a question, or the topic is going to become huge and full of noise.

To answer your previous question: yes.
The guts of wpa_supplicant.conf:

network={
        ssid="REDACTED"
        scan_ssid=1
        proto=WPA2
        key_mgmt=WPA-PSK
        psk=REDACTED                                                         
}

Arch Linux

#1 2017-11-30 20:37:22

[solved] WiFi - no carrier

#2 2017-12-02 08:55:17

Re: [solved] WiFi - no carrier

#3 2017-12-02 10:12:21

Re: [solved] WiFi - no carrier

#4 2017-12-02 12:07:32

Re: [solved] WiFi - no carrier

#5 2017-12-02 12:11:43

Re: [solved] WiFi - no carrier

#6 2017-12-02 12:13:17

Re: [solved] WiFi - no carrier

#7 2017-12-02 12:20:17

Re: [solved] WiFi - no carrier

#8 2017-12-02 12:25:00

Re: [solved] WiFi - no carrier

#9 2017-12-02 12:27:36

Re: [solved] WiFi - no carrier

#10 2017-12-02 12:40:18

Re: [solved] WiFi - no carrier

#11 2017-12-02 12:53:18

Re: [solved] WiFi - no carrier

#12 2017-12-02 13:03:01

Re: [solved] WiFi - no carrier

#13 2017-12-02 13:11:10

Re: [solved] WiFi - no carrier

#14 2017-12-02 13:15:19

Re: [solved] WiFi - no carrier

#15 2017-12-02 13:35:47

Re: [solved] WiFi - no carrier

#16 2017-12-02 13:50:25

Re: [solved] WiFi - no carrier

#17 2017-12-02 13:57:29

Re: [solved] WiFi - no carrier

#18 2017-12-02 14:04:41

Re: [solved] WiFi - no carrier

#19 2017-12-02 14:07:35

Re: [solved] WiFi - no carrier

#20 2017-12-02 14:13:51

Re: [solved] WiFi - no carrier

#21 2017-12-02 14:17:50

Re: [solved] WiFi - no carrier

#22 2017-12-02 14:26:41

Re: [solved] WiFi - no carrier

#23 2017-12-02 14:35:34

Re: [solved] WiFi - no carrier

#24 2017-12-02 14:45:36

Re: [solved] WiFi - no carrier

#25 2017-12-02 14:51:47

Re: [solved] WiFi - no carrier

Board footer