Christian_ 2 May 13, 2018 Hello. Please could someone help me to solve this issue? I have a wifi dongle recognized as: Bus 002 Device 002: ID 148f:5572 Ralink Technology, Corp. RT5572 Wireless Adapter I am trying to use it on my Rock64 and ARMBIAN 5.42 testing Debian GNU/Linux 9 (stretch) 4.4.124-rk3328 uname -a: Linux rock64 4.4.124-rk3328 #24 SMP Wed Mar 28 17:15:52 CEST 2018 aarch64 GNU/Linux It seems it is recognized correctly: Spoiler lsmod: rt2800usb 28672 0 rt2800lib 81920 1 rt2800usb rt2x00usb 20480 1 rt2800usb rt2x00lib 49152 3 rt2x00usb,rt2800lib,rt2800usb dmesg: [ 14.576374] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5592, rev 0222 detected [ 14.606007] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 000f detected [ 14.607477] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 14.610153] systemd[1]: Starting Load/Save RF Kill Switch Status... [ 14.611640] usbcore: registered new interface driver rt2800usb ... [ 14.657918] rt2800usb 2-1:1.0 wlx441ca87f7a19: renamed from wlan0 ... [ 17.964407] IPv6: ADDRCONF(NETDEV_UP): wlx441ca87f7a19: link is not ready [ 17.964729] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin' [ 17.992211] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36 [ 18.346244] IPv6: ADDRCONF(NETDEV_UP): wlx441ca87f7a19: link is not ready Using Network Manager had no luck, the device was always listed as disconnected. So I tried to configure it manually in /etc/network/interfaces, adding this entry: auto wlx441ca87f7a19 iface wlx441ca87f7a19 inet dhcp wpa-ssid mySSID wpa-psk [key removed] Still no luck, this is the log of networking service: Spoiler mag 13 15:07:43 rock64 systemd[1]: Starting Raise network interfaces... mag 13 15:07:44 rock64 wpa_supplicant[4717]: Successfully initialized wpa_supplicant mag 13 15:07:45 rock64 dhclient[4732]: Internet Systems Consortium DHCP Client 4.3.5 mag 13 15:07:45 rock64 dhclient[4732]: Copyright 2004-2016 Internet Systems Consortium. mag 13 15:07:45 rock64 ifup[4683]: Internet Systems Consortium DHCP Client 4.3.5 mag 13 15:07:45 rock64 ifup[4683]: Copyright 2004-2016 Internet Systems Consortium. mag 13 15:07:45 rock64 ifup[4683]: All rights reserved. mag 13 15:07:45 rock64 ifup[4683]: For info, please visit https://www.isc.org/software/dhcp/ mag 13 15:07:45 rock64 dhclient[4732]: All rights reserved. mag 13 15:07:45 rock64 dhclient[4732]: For info, please visit https://www.isc.org/software/dhcp/ mag 13 15:07:45 rock64 dhclient[4732]: mag 13 15:07:45 rock64 dhclient[4732]: Listening on LPF/wlx441ca87f7a19/44:1c:a8:7f:7a:19 mag 13 15:07:45 rock64 dhclient[4732]: Sending on LPF/wlx441ca87f7a19/44:1c:a8:7f:7a:19 mag 13 15:07:45 rock64 ifup[4683]: Listening on LPF/wlx441ca87f7a19/44:1c:a8:7f:7a:19 mag 13 15:07:45 rock64 ifup[4683]: Sending on LPF/wlx441ca87f7a19/44:1c:a8:7f:7a:19 mag 13 15:07:45 rock64 ifup[4683]: Sending on Socket/fallback mag 13 15:07:45 rock64 ifup[4683]: DHCPDISCOVER on wlx441ca87f7a19 to 255.255.255.255 port 67 interval 6 mag 13 15:07:45 rock64 dhclient[4732]: Sending on Socket/fallback mag 13 15:07:45 rock64 dhclient[4732]: DHCPDISCOVER on wlx441ca87f7a19 to 255.255.255.255 port 67 interval 6 mag 13 15:07:51 rock64 dhclient[4732]: DHCPDISCOVER on wlx441ca87f7a19 to 255.255.255.255 port 67 interval 14 mag 13 15:07:51 rock64 ifup[4683]: DHCPDISCOVER on wlx441ca87f7a19 to 255.255.255.255 port 67 interval 14 mag 13 15:08:05 rock64 dhclient[4732]: DHCPDISCOVER on wlx441ca87f7a19 to 255.255.255.255 port 67 interval 13 mag 13 15:08:05 rock64 ifup[4683]: DHCPDISCOVER on wlx441ca87f7a19 to 255.255.255.255 port 67 interval 13 mag 13 15:08:18 rock64 dhclient[4732]: DHCPDISCOVER on wlx441ca87f7a19 to 255.255.255.255 port 67 interval 15 mag 13 15:08:18 rock64 ifup[4683]: DHCPDISCOVER on wlx441ca87f7a19 to 255.255.255.255 port 67 interval 15 mag 13 15:08:33 rock64 dhclient[4732]: DHCPDISCOVER on wlx441ca87f7a19 to 255.255.255.255 port 67 interval 8 mag 13 15:08:33 rock64 ifup[4683]: DHCPDISCOVER on wlx441ca87f7a19 to 255.255.255.255 port 67 interval 8 mag 13 15:08:41 rock64 dhclient[4732]: DHCPDISCOVER on wlx441ca87f7a19 to 255.255.255.255 port 67 interval 5 mag 13 15:08:41 rock64 ifup[4683]: DHCPDISCOVER on wlx441ca87f7a19 to 255.255.255.255 port 67 interval 5 mag 13 15:08:46 rock64 dhclient[4732]: No DHCPOFFERS received. mag 13 15:08:46 rock64 dhclient[4732]: No working leases in persistent database - sleeping. mag 13 15:08:46 rock64 ifup[4683]: No DHCPOFFERS received. mag 13 15:08:46 rock64 ifup[4683]: No working leases in persistent database - sleeping. mag 13 15:08:46 rock64 avahi-autoipd(wlx441ca87f7a19)[4798]: Found user 'avahi-autoipd' (UID 105) and group 'avahi-autoipd' (GID 109 mag 13 15:08:46 rock64 avahi-autoipd(wlx441ca87f7a19)[4798]: Successfully called chroot(). mag 13 15:08:46 rock64 avahi-autoipd(wlx441ca87f7a19)[4798]: Successfully dropped root privileges. mag 13 15:08:46 rock64 avahi-autoipd(wlx441ca87f7a19)[4798]: Starting with address 169.254.6.79 mag 13 15:08:51 rock64 avahi-autoipd(wlx441ca87f7a19)[4798]: Callout BIND, address 169.254.6.79 on interface wlx441ca87f7a19 mag 13 15:08:51 rock64 avahi-autoipd(wlx441ca87f7a19)[4799]: client: RTNETLINK answers: Numerical result out of range mag 13 15:08:51 rock64 avahi-autoipd(wlx441ca87f7a19)[4799]: Script execution failed with return value 2 mag 13 15:08:55 rock64 avahi-autoipd(wlx441ca87f7a19)[4798]: Successfully claimed IP address 169.254.6.79 mag 13 15:08:56 rock64 systemd[1]: Started Raise network interfaces. I also tried to add: options rt2800usb nohwcrypt=y in /etc/modprobe.d/rt2800usb.conf, as I read somewhere and removed and reloaded the modules, no change Trying the scan manually I get no results: wlx441ca87f7a19 IEEE 802.11abgn ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off sudo iwlist wlx441ca87f7a19 scan wlx441ca87f7a19 No scan results I also connected the module to my laptop (running Ubuntu 17.10) to be sure it works, and from there I can connect to my wifi just fine (using Network Manager). I also can connect to wifi using another usb adapter (Realtek 8188EU USB) on Rock64 with Network Manager. Any idea? Thanks in advance. 0 Share this post Link to post Share on other sites
Igor 1900 May 13, 2018 31 minutes ago, Christian_ said: Any idea? Blacklist in-kernel driver and search around for more recent known to work drivers (sources), install headers and compile the module. Repeat until you find a working one. When you find a good working one, we can once replace them with those shipped with the kernel. Ideally: send a patch against kernel source. 0 Share this post Link to post Share on other sites
Christian_ Topic author 2 May 15, 2018 The problem was the wifi region setting unset, this prevented to tune the radio to channel 1. 1 Share this post Link to post Share on other sites
