Closed mweinelt closed 6 years ago
It worked for me when I tested it.
Maybe try with a fresh copy of the most recent image to make sure there’s nothing funny going on in your installation?
Installed the fresh image few hours ago - works for me.
Okay, works like a charm after reinstalling. Thanks!
Hi there, I'm having no luck with WiFi. The first time I tried to compile an image myself but it didn't even boot, and now the following are from the latest image linked on the RaspberryPi3 Debian Wiki page.
# uname -rv
4.14.0-3-arm64 #1 SMP Debian 4,14,12-2 (2018-01-06)
~# wpa_cli
[...]
Interactive mode
Could not connect to wpa_supplicant: (nil) - re-trying
~# iwlist wlan0 scan
wlan0 Interface doesn't support scanning : Network is down
~# iwconfig wlan0 essid Network key secret123
Error for wireless request "Set Encode" (8B2A) :
invalid argument "secret123".
Anything I'm doing wrong?
Is wlan0
actually up?
ip link set up dev wlan0
Are you sure you want to use WEP?
I'm completely unfamiliar with setting up WiFi via command prompts. Is wlan0
supposed to be up by default? This is a freshly dd
'd card, but according to dmesg
neither wlan0
nor eth0
are up.
~# ip link set up dev wlan0
[ 195.390427] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
~# dmesg | grep eth0
[ 9.444303] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:ce:64:a2
[ 11.452093] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 11.452093] IPv6: ADDRCONF(NETDEV_UP): eht0: link is not ready
~# dmesg | grep wlan0
[ 195.390427] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
... I dd
'd the image again... And this time, it stops at this console output:
[ 8.118189] random: crng init done]
Detaching and reattaching keyboard prints corresponding output, but keyboard itself is nonresponsive.
Okay, dd
'd third time, logged in, but same error as before: ip link set up dev wlan0
gives link not ready error.
Never mind, I'm sorry for wasting your time. The issue is specific to wpa_cli
, using wpa_supplicant
worked perfectly. It's a shame iw
and friends don't work and can't scan for networks though.
I installed your image in november, when we still had to drop the
.txt
file into the firmware directory. I'm not sure if WiFi worked back then. At least it hasn't been working this year for me.I have wpa-supplicant running, therefore the dmesg regularly shows scan errors:
Commands involving the wlan0 interface are sluggish and timeout