Quantu
Posts: 18
Joined: Sat Nov 19, 2016 4:13 pm

no wireless interface when clicking on dhcpcd icon in top

Sat Feb 04, 2017 12:18 pm

when i click the dhcpcd's "Wireless & Wired network" icon i get "No wireless interfaces found"


this is my interfaces file:


# interfaces(5) file used by ifup(8) and ifdown(8)

# Please note that this file is written to be used with dhcpcd
# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'

# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d

auto lo
allow-hotplug lo
iface lo inet loopback

allow-hotplug eth0
auto eth0
iface eth0 inet manual

allow-hotplug wlan0
auto wlan0
iface wlan0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

allow-hotplug wlan1
iface wlan1 inet manual
wpa-conf /etc/wpa_supplicant/wpa_supplicant.co

my dhcpcd config file:
# 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.
#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.
# Some interface drivers reset when changing the MTU so disabled by default.
#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

# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname

interface wlan0
static routers= [ i know the ip ]
inform [ i know what it automaticly configures to ]

interface eth0
static routers=[ i know the ip ]

wpa_supplicant config file:
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=NL

network={
ssid=" [not an ssid for sure] "
psk=" [this is not the password i wont show it] "
key_mgmt=WPA-PSK
disabled=0
}

i have no clue what is going on i have hostapd installed and i tried to make an AP but i think i screwed up real bad
as you can see i also removed some private stuff
update before post: i removed hostapd

update2:
heres some console output of dmesgh | tail
pi@RaspPi:~ $ dmesg | tail
[ 709.647653] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 709.647695] brcmfmac: power management disabled
[ 709.798867] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 709.863959] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 709.864333] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 710.079009] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 710.183964] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 710.184144] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 726.443663] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 726.448831] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

root@RaspPi:/home/pi# ifconfig -a
eth0 Link encap:Ethernet HWaddr b8:27:eb:71:6c:50
inet addr:192.168.3.13 Bcast:192.168.3.255 Mask:255.255.255.0
inet6 addr: fe80::ea8f:6aac:73ef:116e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8630 errors:0 dropped:0 overruns:0 frame:0
TX packets:6608 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7595234 (7.2 MiB) TX bytes:904554 (883.3 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:1005 errors:0 dropped:0 overruns:0 frame:0
TX packets:1005 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:204718 (199.9 KiB) TX bytes:204718 (199.9 KiB)

wlan0 Link encap:Ethernet HWaddr b8:27:eb:24:39:05
inet6 addr: fe80::bb46:72dd:8193:b9e/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:497 errors:0 dropped:253 overruns:0 frame:0
TX packets:258 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:292200 (285.3 KiB) TX bytes:33448 (32.6 KiB)

root@RaspPi:/home/pi# iwconfig
wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Frequency:2.452 GHz Access Point: Not-Associated
Tx-Power=31 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on

lo no wireless extensions.

eth0 no wireless extensions.

its very weird how dmesg | tail shows that brcmfmac doesnt have power management on while iwconfig shows its on

atvpn
Posts: 10
Joined: Wed Nov 05, 2014 10:57 am
Location: Austria, Vienna

Re: no wireless interface when clicking on dhcpcd icon in to

Sat Feb 04, 2017 2:09 pm

Hi,
Quantu wrote:
---snip---

my dhcpcd config file:
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

---snip---

# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname

interface wlan0
static routers= [ i know the ip ]
inform [ i know what it automaticly configures to ]

interface eth0
static routers=[ i know the ip ]

wpa_supplicant config file:
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=NL

network={
ssid=" [not an ssid for sure] "
psk=" [this is not the password i wont show it] "
key_mgmt=WPA-PSK
disabled=0
}

---snip---
Your addenda to dhcpcd.conf make me ask, if your were not better off without them. What's your rationale to put them there?
So I would try to do without them, then toggle rfkill, then sudo ifdown wlan0 sudo ifup wlan0 and again toggle rfkill for good measure. Then reboot, back in the GUI turn off wifi and on again. This worked for me when wifi suddenly diappeared for no known reason. To be honest, I have no clue what happens EXACTLY behind dhcpc5 and the GUI. When everything else fails I even had to uninstall/purge dhcpcd5 and setup my wifi from the CLI old school as described here https://www.raspberrypi.org/documentati ... ess-cli.md
HTH
Regards

Quantu
Posts: 18
Joined: Sat Nov 19, 2016 4:13 pm

Re: no wireless interface when clicking on dhcpcd icon in to

Sat Feb 04, 2017 2:57 pm

atvpn wrote:Hi,
Quantu wrote:
---snip---

my dhcpcd config file:
# A sample configuration for dhcpcd.
# See dhcpcd.conf(5) for details.

---snip---

# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname

interface wlan0
static routers= [ i know the ip ]
inform [ i know what it automaticly configures to ]

interface eth0
static routers=[ i know the ip ]

wpa_supplicant config file:
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=NL

network={
ssid=" [not an ssid for sure] "
psk=" [this is not the password i wont show it] "
key_mgmt=WPA-PSK
disabled=0
}

---snip---
Your addenda to dhcpcd.conf make me ask, if your were not better off without them. What's your rationale to put them there?
So I would try to do without them, then toggle rfkill, then sudo ifdown wlan0 sudo ifup wlan0 and again toggle rfkill for good measure. Then reboot, back in the GUI turn off wifi and on again. This worked for me when wifi suddenly diappeared for no known reason. To be honest, I have no clue what happens EXACTLY behind dhcpc5 and the GUI. When everything else fails I even had to uninstall/purge dhcpcd5 and setup my wifi from the CLI old school as described here https://www.raspberrypi.org/documentati ... ess-cli.md
HTH
Regards
can i configure with oldschool method before i remove dhcpcd5? (without activating wlan0 yet)

update:
root@RaspPi:/home/pi# ifup wlan0 & ifdown wlan0
[2] 4890
ifdown: interface wlan0 not configured
root@RaspPi:/home/pi# modprobe: FATAL: Module p80211 not found.
Failed to load p80211.ko.
run-parts: /etc/network/if-pre-up.d/linux-wlan-ng-pre-up exited with return code 1
Failed to bring up wlan0.

atvpn
Posts: 10
Joined: Wed Nov 05, 2014 10:57 am
Location: Austria, Vienna

Re: no wireless interface when clicking on dhcpcd icon in to

Sun Feb 05, 2017 11:36 am

Quantu wrote: can i configure with oldschool method before i remove dhcpcd5? (without activating wlan0 yet)

update:
root@RaspPi:/home/pi# ifup wlan0 & ifdown wlan0
[2] 4890
ifdown: interface wlan0 not configured
root@RaspPi:/home/pi# modprobe: FATAL: Module p80211 not found.
Failed to load p80211.ko.
run-parts: /etc/network/if-pre-up.d/linux-wlan-ng-pre-up exited with return code 1
Failed to bring up wlan0.
Hi Quantu,
I made mixed experiences. So you might be able to configure your wlan from the CLI with dhcpcd5 present, but it is as likely that you might not succed. So what hinders you to uninstall dhcpcd5? You can reinstall it any time later should you want to.

If it were my Pi I'd have a closer look at /etc/network/interfaces and /etc/wpa_supplicant/wpa.supplicant.conf These files I would strip to the bare minimum e.g.

Code: Select all

auto lo
iface lo inet loopback

allow-hotplug wlan0
iface wlan0 inet dhcp
    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
and for the wpa_supplicant.conf

Code: Select all

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=AT

network={
        ssid="my AP"
        psk="my passwd"
        key_mgmt=WPA-PSK
}
With these I'd do a reboot and have a look at the output of dmesg, ifconfig.
You might want give it a try and post the outcome.
Greetings

Quantu
Posts: 18
Joined: Sat Nov 19, 2016 4:13 pm

Re: no wireless interface when clicking on dhcpcd icon in to

Sat Feb 11, 2017 5:19 pm

atvpn wrote:
Quantu wrote: can i configure with oldschool method before i remove dhcpcd5? (without activating wlan0 yet)

update:
root@RaspPi:/home/pi# ifup wlan0 & ifdown wlan0
[2] 4890
ifdown: interface wlan0 not configured
root@RaspPi:/home/pi# modprobe: FATAL: Module p80211 not found.
Failed to load p80211.ko.
run-parts: /etc/network/if-pre-up.d/linux-wlan-ng-pre-up exited with return code 1
Failed to bring up wlan0.
Hi Quantu,
I made mixed experiences. So you might be able to configure your wlan from the CLI with dhcpcd5 present, but it is as likely that you might not succed. So what hinders you to uninstall dhcpcd5? You can reinstall it any time later should you want to.

If it were my Pi I'd have a closer look at /etc/network/interfaces and /etc/wpa_supplicant/wpa.supplicant.conf These files I would strip to the bare minimum e.g.

Code: Select all

auto lo
iface lo inet loopback

allow-hotplug wlan0
iface wlan0 inet dhcp
    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
and for the wpa_supplicant.conf

Code: Select all

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=AT

network={
        ssid="my AP"
        psk="my passwd"
        key_mgmt=WPA-PSK
}
With these I'd do a reboot and have a look at the output of dmesg, ifconfig.
You might want give it a try and post the outcome.
Greetings
well i tried to de-install dhcpcd5 and it worked but for some reason no connection works anymore :/. when a new raspbian distro update comes out ill wipe my sd card (all my important files are on my usb ) and install that one.

Return to “Troubleshooting”