Wetek Play 2 no Wifi with Box Image

rdorsch · April 2, 2023 at 1:56 PM

Hi,

I have trouble getting a wifi connection with the box image on a Wetek Play 2. I don't see any wifi network at all (I do if I boot the stock (Android) firmware on the device). I connected an ethernet cable and iw list at least shows a phy. Is there something I am doing wrong?

kodi.log:

http://ix.io/4suB

dmesg output:

http://ix.io/4suC

Code

Mediacenter:~ # iw list

Wiphy phy0

wiphy index: 0
max # scan SSIDs: 10
max scan IEs length: 2048 bytes
max # sched scan SSIDs: 16
max # match sets: 16
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports roaming.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP-128 (00-0f-ac:4)
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* P2P-client
* P2P-GO
* P2P-device
Band 1:
Capabilities: 0x1020
HT20
Static SM Power Save
RX HT20 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 16 usec (0x07)
HT TX/RX MCS rate indexes supported: 0-7
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm)
* 2472 MHz [13] (20.0 dBm)
* 2484 MHz [14] (20.0 dBm)
Band 2:
Capabilities: 0x1020
HT20
Static SM Power Save
RX HT20 SGI
No RX STBC
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 16 usec (0x07)
HT TX/RX MCS rate indexes supported: 0-7
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 5170 MHz [34] (20.0 dBm)
* 5180 MHz [36] (20.0 dBm)
* 5190 MHz [38] (20.0 dBm)
* 5200 MHz [40] (20.0 dBm)
* 5210 MHz [42] (20.0 dBm)
* 5220 MHz [44] (20.0 dBm)
* 5230 MHz [46] (20.0 dBm)
* 5240 MHz [48] (20.0 dBm)
* 5260 MHz [52] (20.0 dBm)
* 5280 MHz [56] (20.0 dBm)
* 5300 MHz [60] (20.0 dBm)
* 5320 MHz [64] (20.0 dBm)
* 5500 MHz [100] (20.0 dBm)
* 5520 MHz [104] (20.0 dBm)
* 5540 MHz [108] (20.0 dBm)
* 5560 MHz [112] (20.0 dBm)
* 5580 MHz [116] (20.0 dBm)
* 5600 MHz [120] (20.0 dBm)
* 5620 MHz [124] (20.0 dBm)
* 5640 MHz [128] (20.0 dBm)
* 5660 MHz [132] (20.0 dBm)
* 5680 MHz [136] (20.0 dBm)
* 5700 MHz [140] (20.0 dBm)
* 5720 MHz [144] (disabled)
* 5745 MHz [149] (20.0 dBm)
* 5765 MHz [153] (20.0 dBm)
* 5785 MHz [157] (20.0 dBm)
* 5805 MHz [161] (20.0 dBm)
* 5825 MHz [165] (20.0 dBm)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* join_ibss
* set_pmksa
* del_pmksa
* flush_pmksa
* remain_on_channel
* frame
* set_wiphy_netns
* set_channel
* start_sched_scan
* start_p2p_device
* connect
* disconnect
* crit_protocol_start
* crit_protocol_stop
* update_connect_params
software interface modes (can always be added):
valid interface combinations:
* #{ managed } <= 1, #{ P2P-device } <= 1, #{ P2P-client, P2P-GO } <= 1,
total <= 3, #channels <= 1
* #{ managed } <= 1, #{ AP } <= 1, #{ P2P-client } <= 1, #{ P2P-device } <= 1,
total <= 4, #channels <= 1
Device supports scan flush.
max # scan plans: 1
max scan plan interval: 508
max scan plan iterations: 0
Supported TX frame types:
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
Supported extended features:
* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
* [ 4WAY_HANDSHAKE_STA_PSK ]: 4-way handshake with PSK in station mode
* [ 4WAY_HANDSHAKE_STA_1X ]: 4-way handshake with 802.1X in station mode
* [ DFS_OFFLOAD ]: DFS offload
Mediacenter:~ #

Display More

Any hint or advice is welcome

Many thanks

Rainer

**chewitt** · April 2, 2023 at 2:30 PM

The dmesg log looks fine, the WiFi NIC is probed without errors. Some German users (a guess based on your name) need to have the 80211 regdomain configured in LE settings (under Network) before networks can be seen. See if setting to 'DE' makes a difference?

rdorsch · April 2, 2023 at 9:47 PM

I configured the regdomain and now it seems I can at least see the wireless network.

I managed to connect to the AP of an Android phone in tethering mode.

I did not manage to connect to an

OpenWrt 22.03.3 router, I get invalid key. I use this router since many years with many devices and I do not recall that I ever had an issue that a device did not want to connect.

dmesg has quite a few entries

ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel <number>

(not sure if that is relevant)

http://ix.io/4swH

Output of "iw dev wlan0 scan"

http://ix.io/4swW

Output of "iwlist wlan0 scanning" looks ok for me:

and the kodi.log:

http://ix.io/4swI

What is very weird: Sometimes all connections show up twice, see

PXL_20230402_194352852.jpg

Nextcloud - a safe home for all your data

nc.d5x.de

Is that expected?

Many thanks

Rainer

**chewitt** · April 3, 2023 at 5:53 AM

The "invalid-key" error is probably bugs in iwd affecting a small number of users. We've bumped iwd to the latest release in LE11 nightlies and this appears to resolve it for most users. Update to the latest nightly here: https://test.libreelec.tv/11.0/Amlogic/wetek-play2/ and report back. The issue is tracked here: https://github.com/LibreELEC/LibreELEC.tv/issues/7166

The dmesg messages are correct and harmless.

For double results; an educated guess is that connman is scanning in the background so its results are visible to the dbus agent in the LE settings add-on, and then you're running scans via iwd and its results are also visible. If you don't run the manual iwd scan do you still see duplicates?

rdorsch · April 3, 2023 at 8:18 PM

With

Code

2023-04-03 16:32:16.090 T:908      info <general>: Starting Kodi (20.1 (20.1.0) Git:20.1-Nexus). Platform: Linux ARM 32-bit
2023-04-03 16:32:16.090 T:908      info <general>: Using Release Kodi x32
2023-04-03 16:32:16.090 T:908      info <general>: Kodi compiled 2023-04-03 by GCC 12.2.0 for Linux ARM 32-bit version 6.1.19 (393491)
2023-04-03 16:32:16.091 T:908      info <general>: Running on Amlogic Meson GXBB (S905) WeTek Play 2 with LibreELEC (community): nightly-20230403-bb4c561 11.0, kernel: Linux ARM 64-bit version 6.1.19

I checked in the openwrt syslog, but did not find any entry there from the connection attempt. For successful connections, I see entries like

Code

Mon Apr  3 21:09:54 2023 daemon.info hostapd: wlan0: STA 78:11:dc:ed:a7:e3 IEEE 802.11: associated (aid 5)
Mon Apr  3 21:09:54 2023 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 78:11:dc:ed:a7:e3
Mon Apr  3 21:09:54 2023 daemon.info hostapd: wlan0: STA 78:11:dc:ed:a7:e3 WPA: pairwise key handshake completed (RSN)
Mon Apr  3 21:09:54 2023 daemon.notice hostapd: wlan0: EAPOL-4WAY-HS-COMPLETED 78:11:dc:ed:a7:e3

on the openwrt side. I conclude that the connection process aborts very early.

I see still the same behavior. I used the box image instead of the wetek-play2, since I still have the Android FW for reference testing on the emmc.

The double results I cannot deterministically reproduce. I keep an eye if the double results show up again w/o manual iwd run.

rdorsch · April 3, 2023 at 9:23 PM

I have a rock64 box with Libreelec 11.0.1 running here as well. I tried to connect to the same router to check if it is an iwd - router incompatibility.

But it seems Murphy is with me when it comes to wifi:
Realtek RTL8188EUS Wifi Adapter on Rock64 not detected

(I opened a separate thread because it is a rockchip AP and belongs then in a different section of the forum)

**chewitt** · April 4, 2023 at 11:47 AM

We aren't fans of RTL chips that have no upstream support (assuming that's the issue).

rdorsch · April 4, 2023 at 1:42 PM

I don't think it is a problem of upstream support, since it works flawless on a Debian stable system with a probably 2yr old kernel (5.10).

Wetek Play 2 no Wifi with Box Image

Similar Threads

Wetek play 2 build