Jump to content

Anyone Gotten Wifi to Work?

Quantum

By Quantum
in Beginners

 Share

Recommended Posts

Quantum

Quantum

Posted
Posted (edited)

Tinker Board S, Armbian 5.75, 4.19.20

 

I've spent a week now full-time trying to make this busted thing work.  The closest I've come is setting everything for roaming.

 

/etc/network/interfaces.d/wlan0 

iface wlan0 inet manual
        wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf

        wpa-driver wext

iface mercury inet dhcp

iface home inet static
        address 10.2.1.22
        netmask 255.255.255.0
        network 10.2.1.0
        gateway 10.2.1.1
        #post-up

#Schnittstelle automatisch aktivieren
auto wlan0

 

/etc/wpa_supplicant/wpa_supplicant.conf 

# Will automatically select the best network based on the order of network blocks,
# network security level (WPA/WPA2 is preferred), and signal strength.

ctrl_interface=/run/wpa_supplicant
ap_scan=2       # Go directly to the hidden SSID

network={
        ssid="mercury"
        id_str="mercury"
        psk={ ... }
}

network={
        ssid="sirius24"
        id_str="home"
        scan_ssid=1
        proto=RSN
        key_mgmt=WPA-PSK
        pairwise=CCMP
        group=TKIP CCMP
        psk="{ ... }"
        #psk={ ... }
}

  

# dmesg

...

[Tue Feb 12 14:49:18 2019] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[Tue Feb 12 14:49:18 2019] cfg80211: failed to load regulatory.db

... even though I've put regulatory.db, regulatory.db.5, and regulatory.db.p7s into /lib/firmware.

Spoiler

  


...

Tue Feb 12 15:06:21 2019] RTL8723BS: start auth
[Tue Feb 12 15:06:21 2019] RTL8723BS: auth success, start assoc
[Tue Feb 12 15:06:21 2019] RTL8723BS: sta recv deauth reason code(11) sta:dc:9f:db:1c:a0:1a, ignore = 0
[Tue Feb 12 15:06:25 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:06:25 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:06:25 2019] RTL8723BS: set ssid [mercury] fw_state = 0x00000008
[Tue Feb 12 15:06:30 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:06:30 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:06:30 2019] RTL8723BS: set ssid [sirius24] fw_state = 0x00000008
[Tue Feb 12 15:06:32 2019] RTL8723BS: start auth
[Tue Feb 12 15:06:32 2019] RTL8723BS: auth success, start assoc
[Tue Feb 12 15:06:32 2019] RTL8723BS: sta recv deauth reason code(11) sta:dc:9f:db:1c:a0:1a, ignore = 0
[Tue Feb 12 15:06:35 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:06:35 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:06:35 2019] RTL8723BS: set ssid [mercury] fw_state = 0x00000008
[Tue Feb 12 15:06:41 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:06:41 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:06:41 2019] RTL8723BS: set ssid [sirius24] fw_state = 0x00000008
[Tue Feb 12 15:06:42 2019] RTL8723BS: start auth
[Tue Feb 12 15:06:42 2019] RTL8723BS: auth success, start assoc
[Tue Feb 12 15:06:42 2019] RTL8723BS: sta recv deauth reason code(11) sta:dc:9f:db:1c:a0:1a, ignore = 0
[Tue Feb 12 15:06:46 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:06:46 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:06:46 2019] RTL8723BS: set ssid [mercury] fw_state = 0x00000008
[Tue Feb 12 15:06:51 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:06:52 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:06:52 2019] RTL8723BS: set ssid [sirius24] fw_state = 0x00000008
[Tue Feb 12 15:06:53 2019] RTL8723BS: start auth
[Tue Feb 12 15:06:53 2019] RTL8723BS: auth success, start assoc
[Tue Feb 12 15:06:53 2019] RTL8723BS: sta recv deauth reason code(11) sta:dc:9f:db:1c:a0:1a, ignore = 0
[Tue Feb 12 15:06:57 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:06:57 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:06:57 2019] RTL8723BS: set ssid [mercury] fw_state = 0x00000008
[Tue Feb 12 15:07:02 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:07:02 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:07:02 2019] RTL8723BS: set ssid [sirius24] fw_state = 0x00000008
[Tue Feb 12 15:07:04 2019] RTL8723BS: start auth
[Tue Feb 12 15:07:04 2019] RTL8723BS: auth success, start assoc
[Tue Feb 12 15:07:04 2019] RTL8723BS: sta recv deauth reason code(11) sta:dc:9f:db:1c:a0:1a, ignore = 0
[Tue Feb 12 15:07:07 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:07:07 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:07:07 2019] RTL8723BS: set ssid [mercury] fw_state = 0x00000008
[Tue Feb 12 15:07:13 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:07:13 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:07:13 2019] RTL8723BS: set ssid [sirius24] fw_state = 0x00000008
[Tue Feb 12 15:07:14 2019] RTL8723BS: start auth
[Tue Feb 12 15:07:14 2019] RTL8723BS: auth success, start assoc
[Tue Feb 12 15:07:14 2019] RTL8723BS: sta recv deauth reason code(11) sta:dc:9f:db:1c:a0:1a, ignore = 0
[Tue Feb 12 15:07:18 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:07:18 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:07:18 2019] RTL8723BS: set ssid [mercury] fw_state = 0x00000008
[Tue Feb 12 15:07:23 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:07:23 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:07:23 2019] RTL8723BS: set ssid [sirius24] fw_state = 0x00000008
[Tue Feb 12 15:07:25 2019] RTL8723BS: start auth
[Tue Feb 12 15:07:25 2019] RTL8723BS: auth success, start assoc
[Tue Feb 12 15:07:25 2019] RTL8723BS: sta recv deauth reason code(11) sta:dc:9f:db:1c:a0:1a, ignore = 0
[Tue Feb 12 15:07:28 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:07:29 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:07:29 2019] RTL8723BS: set ssid [mercury] fw_state = 0x00000008
[Tue Feb 12 15:07:34 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:07:34 2019] RTL8723BS: set bssid:00:00:00:00:00:00
[Tue Feb 12 15:07:34 2019] RTL8723BS: set ssid [sirius24] fw_state = 0x00000008
[Tue Feb 12 15:07:36 2019] RTL8723BS: start auth
[Tue Feb 12 15:07:36 2019] RTL8723BS: auth success, start assoc
[Tue Feb 12 15:07:36 2019] RTL8723BS: sta recv deauth reason code(11) sta:dc:9f:db:1c:a0:1a, ignore = 0

 

Edited by Tido
added spoiler.. shorted quote - please add a spoiler nexttime yourself, thx
Link to comment
Share on other sites
TonyMac32

TonyMac32

Posted
Posted

"Anyone Gotten Wifi to Work?"

 

Perhaps the proper question is:  Has anyone else had difficulty with wifi?  No, not as of last time I built it.  I will test the current image again just to see, we've had wifi working on Tinker mainline images for over a year.

Link to comment
Share on other sites
Quantum

Quantum

Posted
  • Author
Posted

I tried first the armbian-setup, but it has no provision for WPA2 so it can't connect.  WPA2 is the hard part.  Also, being in Washington and after setting my timezone to L.A., I try to change my repository from Estonia, but my only other choices are China and Bulgaria.

 

Then I tried NetworkManager, but apparently it's GUI only and there doesn't seem to be an app for LXQt. 

 

Then I stopped/disabled NM and installed ConnMan.  I couldn't make that work and I can't remember why, I believe it was because it would not allow me to set a static IP, which is necessary. 

 

So I was left with trying to do it manually, which I've now failed with.

 

I'm installing the Armbian image into eMMC, and then updating with the Armbian cli/ascii system, and then installing LXQt.

 

I was aware of armbianmonitor -u, but: 

# armbianmonitor -u



Network/firewall problem detected. Not able to upload debug info.
Please fix this or use "-U" instead and upload whole output manually

System diagnosis information will now be uploaded to gzip: /var/log/armbian-hardware-monitor.log.1.gz: No such file or directory
curl: (6) Could not resolve host: ix.io

Please post the URL in the forum where you've been asked for.

(For some reason the forum software would not allow me to put the above two into the same code block)

 

I'm coming in on eth0 which does not have gateway set, as wlan0 is supposed to be doing that.  I can no longer bring up wlan0 with the current manual config, as above.

 

I can't imagine why this is so difficult.

Link to comment
Share on other sites
Igor

Igor

Posted
Posted
26 minutes ago, Quantum said:

but it has no provision for WPA2 so it can't connect.  WPA2 is the hard part


It happens that Tinkerboard is lying on the table. I only have WPA2 network and (stock) Armbian works fine: http://ix.io/1Bj0 (with nmtui-connect)

Link to comment
Share on other sites
Quantum

Quantum

Posted
  • Author
Posted
57 minutes ago, Igor said:


It happens that Tinkerboard is lying on the table. I only have WPA2 network and (stock) Armbian works fine: http://ix.io/1Bj0 (with nmtui-connect)

Yup your system is running, looks like about 10 times armbianmonitor got run.  But it doesn't say anything about wifi setup.

 

I can't get into LXQt using X2Go due to an auth failure which only happens in X2Go, no matter with SSH key automatic, manual, or password.  With command-line no problem.  SSH is set to accept either, but X2Go won't have it.  This TB is headless.

Link to comment
Share on other sites
Igor

Igor

Posted
Posted
3 minutes ago, Quantum said:

But it doesn't say anything about wifi setup.


It's stock Armbian desktop and connection was made by using Network manager. It is the same by using desktop or via CLI.

 

3 minutes ago, Quantum said:

I can't get into LXQt


Let's move this topic elsewhere since it has nothing to do with Tinkerboard.

Link to comment
Share on other sites
Igor

Igor

Posted
Posted
9 minutes ago, Quantum said:

No idea what forums are available here.  Going to https://forum.armbian.com/forum/ I get, "The page you requested does not exist".  My only other option is Active Threads, and I feature there already.


https://forum.armbian.com/

 

You posted it into correct forum. Initially. But since this is most likely not related to this specific board, it gets moved elsewhere.

Link to comment
Share on other sites
Quantum

Quantum

Posted
  • Author
Posted

I now remember discovering nmtui in the past two weeks and trying that too.

 

I can add and set up the wifi interface just fine.  But when I go to Activate it...

it's not there.

 

Stop/restart nmtui and the interface is still in Add...

but only eth0 is in Activate.

 

Maybe this Armbian is impractical/impossible.  Why does everyone say that nmtui works for wifi when it doesn't?  Or is it that it doesn't work on the current release?

Link to comment
Share on other sites
Igor

Igor

Posted
Posted
25 minutes ago, Quantum said:

Maybe this Armbian is impractical/impossible.  Why does everyone say that nmtui works for wifi when it doesn't?


If you messed up network settings and/or use different tools at the same time, it might cause troubles. Start from a clean image and use nmtui tool. It must work that way. If you want to use some other way, you are on your own.

Link to comment
Share on other sites
TonyMac32

TonyMac32

Posted
Posted
48 minutes ago, Quantum said:

Or is it that it doesn't work on the current release?

 

When I tested this to verify it was not an issue, I burnt a fresh SD card, booted, went to command line, started nmtui, found my WPA2 wifi  (Why use less?), put in the necessary bits, activated it, done.  So, impractical?  I think not.  Please, your frustration is noted, but this has nothing to do with Armbian.

Link to comment
Share on other sites
Quantum

Quantum

Posted
  • Author
Posted

Most current Armbian Armbian_5.75_Tinkerboard_Debian_stretch_next_4.19.20, sha256sum verified.

Plug USB cable between TB and laptop, and /dev/sdb appears in dmesg.

# dd if=Armbian_5.75_Tinkerboard_Debian_stretch_next_4.19.20.img of=/dev/sdb bs=4M status=progress

 

Take to testbed, plug into eth0 and USB power, it boots to command-line with no fluctuation of red light or power-sag messaged. (3A wall wart)

 

Boots.  Set wlan0 up like the attached, save, but it is NOT in Activate.  Reboot and wlan0 has no static IP and in nmtui it is NOT in activate.

 

I am confident now that this is because I have a TB S.  And none of the rest of you has an S.  So Armbian is busted with the TB S.

 

Can I help with a lshw?  I'd love to, but after the clean install and nmtui, eth0 gets the right IP but is incommunicado.  That is enough.

 

 

snap.jpg

Link to comment
Share on other sites
Igor

Igor

Posted
Posted
8 hours ago, Quantum said:

Can I help with a lshw? 


Not really. We have own tool which tells more: armbianmonitor -u

 

It looks like a bug in the driver. When fixed IPs are set, it doesn't work (while it works with first USB based wifi that I have found on the table) ... welcome to the dungeons of single board computers :) 

 

We are usually very happy if those shitty chip/drivers(s) connect and works without too much hassle.

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept