KrishIsola

Hello! May I know of the Android TV box device models of Amlogic S905/S905x/S912, Armbian is supported without any issues? The n/w functionality required is: LAN, Wifi (Hotspot), WebRTC (Codecs: VP8, H.264) If possible (VP9, H.265 too). After going through various posts in this forum, came to an opinion that X96 (S905x) and X96Max (S905x2) works good. But, facing different issues with wifi and configuring as AP. On S905x2, wlan itself is not detected with 5.96 Debian buster image

Hello! I appreciate of any help with X96Max (S905x2) issue mentioned above.

Hello @balbes150, I have the following observations to share. Observation with X96Max (S905x2 2gb ram 16gb eMMC). Request for your help to resolve. Flashed 5.96 (& also latest dated 20-Sep) image on SD card. Edited uEvn.ini and set the dtb_name=/dtb/meson-g12a-x96-max-rmii.dtb Also tried with dtb_name=/dtb/meson-g12a-x96-max.dtb Successfully booted with Armbian Linux However, only ethernet is shown. Wireless lan (wlan0) is not detected at all. Not detecting usb wifi adapter too Few other observations from 5.96 Armbian_Buster_desktop: dhcpcd, dnsmasq are not available by default Specific to Ubuntu_Bionic image: When tried to install with "apt-get install", gets an error like "ports.ubuntu.com" is not available Tried this for few days assuming the portal is down. But unable to install packages on ubuntu builds Chrome: I'm trying a webrtc solution and browser show errors like video codecs are not available I remember the same webrtc solution worked with 5.91 build The codecs are VP8, H.264. Not sure of why the webrtc library complains that codecs are missing Regards, Krishna

Thanks for the response. I'm not sure of what to do next.

Just curious, what "wifi" issues are fixed in this build?

For my wifi hotspot authentication problem, I found the below log messages. Does this log help to identify the problem? I'm not an expert in kernel / os level. Hence, seeking for help (DESPERATE !!!). Sep 17 17:36:08 nsiod68 kernel: [ 492.907311] Modules linked in: fuse ipt_MASQUERADE iptable_nat nf_nat xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter bnep 8021q garp mrp stp llc zstd zram r8723bs(C) cfg80211 snd_soc_meson_aiu_i2s snd_soc_meson_aiu_spdif hci_uart btqca btbcm btintel meson_vdec bluetooth crct10dif_ce videobuf2_dma_contig v4l2_mem2mem dw_hdmi_cec videobuf2_memops videobuf2_v4l2 videobuf2_common ir_nec_decoder ecdh_generic videodev rfkill meson_ir snd_soc_meson_audio_core pwm_meson ao_cec media adc_keys input_polldev sch_fq_codel ip_tables x_tables ipv6 crc_ccitt Sep 17 17:36:08 nsiod68 kernel: [ 492.957945] Process RTW_CMD_THREAD (pid: 782, stack limit = 0x000000006754f26e) Sep 17 17:36:08 nsiod68 kernel: [ 492.965188] CPU: 3 PID: 782 Comm: RTW_CMD_THREAD Tainted: G C 5.1.15-aml-s905 #5.91 Sep 17 17:36:08 nsiod68 kernel: [ 492.974067] Hardware name: Khadas VIM (DT) Sep 17 17:36:08 nsiod68 kernel: [ 492.978123] pstate: 80000005 (Nzcv daif -PAN -UAO) Sep 17 17:36:08 nsiod68 kernel: [ 492.982921] pc : nl80211_send_station.isra.62+0x2d0/0xbb0 [cfg80211] Sep 17 17:36:08 nsiod68 kernel: [ 492.989198] lr : nl80211_send_station.isra.62+0xa98/0xbb0 [cfg80211] Sep 17 17:36:08 nsiod68 kernel: [ 492.995456] sp : ffff000010bdbbb0 Sep 17 17:36:08 nsiod68 kernel: [ 492.998734] x29: ffff000010bdbbb0 x28: ffff000010bdc008 Sep 17 17:36:08 nsiod68 kernel: [ 493.003995] x27: ffff000010bdbc50 x26: ffff80000dc15030 Sep 17 17:36:08 nsiod68 kernel: [ 493.009257] x25: ffff80000dc15000 x24: 0000000000000030 Sep 17 17:36:08 nsiod68 kernel: [ 493.014518] x23: ffff000010bdbcd8 x22: 0000000000000000 Sep 17 17:36:08 nsiod68 kernel: [ 493.019779] x21: ffff800074961e00 x20: ffff000012315000 Sep 17 17:36:08 nsiod68 kernel: [ 493.025040] x19: ffff80000dc15014 x18: 0000000000000000 Sep 17 17:36:08 nsiod68 kernel: [ 493.030301] x17: 0000000000000000 x16: 0000000000000000 Sep 17 17:36:08 nsiod68 kernel: [ 493.035563] x15: 0000000000000000 x14: 000af217000bdd00 Sep 17 17:36:08 nsiod68 kernel: [ 493.040827] x13: 0000000000000000 x12: 0000000000000000 Sep 17 17:36:08 nsiod68 kernel: [ 493.046088] x11: 0000000000ff1740 x10: 2d1a2d000c02ac0f Sep 17 17:36:08 nsiod68 kernel: [ 493.051350] x9 : 00000104ac0f0000 x8 : ffff80000dc15064 Sep 17 17:36:08 nsiod68 kernel: [ 493.056611] x7 : 0000000000000000 x6 : ffff80000dc15064 Sep 17 17:36:08 nsiod68 kernel: [ 493.061872] x5 : ffff80000dc15064 x4 : ffff000010bdbda0 Sep 17 17:36:08 nsiod68 kernel: [ 493.067133] x3 : 0000000000000268 x2 : 0000000000000064 Sep 17 17:36:08 nsiod68 kernel: [ 493.072394] x1 : 0000000000000008 x0 : ffff80000dc15000 Sep 17 17:36:08 nsiod68 kernel: [ 493.077657] Call trace: Sep 17 17:36:08 nsiod68 kernel: [ 493.080173] nl80211_send_station.isra.62+0x2d0/0xbb0 [cfg80211] Sep 17 17:36:08 nsiod68 kernel: [ 493.086112] cfg80211_new_sta+0x78/0xe8 [cfg80211] Sep 17 17:36:08 nsiod68 kernel: [ 493.090895] rtw_cfg80211_indicate_sta_assoc+0x6c/0x90 [r8723bs] Sep 17 17:36:08 nsiod68 kernel: [ 493.096826] rtw_stassoc_event_callback+0x194/0x1e0 [r8723bs] Sep 17 17:36:08 nsiod68 kernel: [ 493.102507] mlme_evt_hdl+0x74/0xa0 [r8723bs] Sep 17 17:36:08 nsiod68 kernel: [ 493.106817] rtw_cmd_thread+0x16c/0x360 [r8723bs] Sep 17 17:36:08 nsiod68 kernel: [ 493.111392] kthread+0x124/0x128 Sep 17 17:36:08 nsiod68 kernel: [ 493.114578] ret_from_fork+0x10/0x1c Sep 17 17:36:08 nsiod68 kernel: [ 493.118117] Code: 9b037c23 11000421 a9090fa4 8b03009c (b8636883) Sep 17 17:36:08 nsiod68 kernel: [ 493.124153] ---[ end trace c1575f5c5fb8f5a3 ]--- Sep 17 17:36:11 nsiod68 systemd[1]: serial-getty@ttyS0.service: Succeeded. Sep 17 17:36:11 nsiod68 systemd[1]: serial-getty@ttyS0.service: Service RestartSec=100ms expired, scheduling restart. Sep 17 17:36:11 nsiod68 systemd[1]: serial-getty@ttyS0.service: Scheduled restart job, restart counter is at 46. Sep 17 17:36:11 nsiod68 systemd[1]: Stopped Serial Getty on ttyS0. Sep 17 17:36:11 nsiod68 systemd[1]: Started Serial Getty on ttyS0. Sep 17 17:36:14 nsiod68 kernel: [ 498.890843] RTL8723BS: ap recv disassoc reason code(8) sta:6c:8d:c1:db:7b:0c Sep 17 17:36:14 nsiod68 hostapd: wlan0: STA 6c:8d:c1:db:7b:0c IEEE 802.11: disassociated

Hello @balbes150 and Others, I'm able to boot my X96 (S905x) device from a SD card with linux builds (tried Armbian 5.91 and 5.96). However, when I tried to configure the device as Wifi Hotspot / Access Point (AP), facing issues with connecting or pairing to the AP. The device appears to be configured with SSID and a static IP. But, when I tried to pair another device to this SSID + Passcode, it fails - something like invalid passcode. Could you please help to resolve or provide leads to the solution? - Krish

Hello, I'm working on a solution using Raspberry Pi 3B+ which make the Pi as a WiFi hotspot (AP). All good here. I'm experimenting the same solution with X96 pro device (Amlogic S905x 2gb RAM 16gb eMMC) which has in-built wifi. I have loaded 5.91 Ubuntu image a while ago and also tired with recent 5.96 Debian Buster images. I did not try imaging to eMMC yet. - Able to boot from SD card with linux image, installed my solution etc ... - Configured wifi hotspot (wlan0 with static IP) by modifying hosted.conf, dhcpcd.conf, dnsmasq.conf etc - The wifi SSID is configured and appears when scanned from a different device - However, while joining with the defined PIN/Passcode, not accepted and unable to join I have tried different approaches by setting hostapd.conf driver to (nl80211 / rtl871xdrv / rtl8723bs) and even by removing the driver entry in the hosted.conf file. With no "driver" or "driver=nl80211" the AP is configured and able to show SSID to other devices. With other options, the AP is in disabled state. This wifi hotspot is required and important to my work. Could anyone please help in identifying a solution? I'm planning to order more units of X96 and X96 Max (S905x2). I believe that there are stable Linux images for X96 Max (S905x2). Does the above wifi hotspot issues valid here as well? Output of lshw for the n/w interfaces: *-network:0 description: Wireless interface physical id: 3 logical name: wlan0 serial: 00:0b:6a:32:4d:68 capabilities: ethernet physical wireless configuration: broadcast=yes driver=rtl8723bs ip=172.24.1.1 multicast=yes wireless=IEEE 802.11bgn *-network:1 description: Ethernet interface physical id: 4 logical name: eth0 serial: 00:15:18:01:81:31 size: 100Mbit/s capacity: 100Mbit/s capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=st_gmac driverversion=Jan_2016 duplex=full ip=192.168.1.111 link=yes multicast=yes port=MII speed=100Mbit/s Note: Attached the hostapd.conf file hostapd.conf

Thank you very much! I have followed the instructions about booting Armbian (5.91) from SD card and I'm successful able to login to desktop. I did check the chrome GPUs flags and the h/w acceleration is disabled. Is there any separate script to run? Could you please provide me a reference? I could not find a proper post related to this.

@balbes150 Kindly provide your recommendations. Does S905x (2gb 16gb) + Linux O/S supports my requirements? My requirements: I’m developing a (video) content display solution to run device in kiosk mode with Chrome browser starting in fullscreen. It is supposed to display video being received. Now, I’m looking at Amlogic S905x base board to run my solution. Ordered sample S905x based Android TV box from sztomata (OneNuts). What I need: - Reference, Docs, Scripts to remove Android and load Linux image onto S905x board (eMMC) - Any recommendations on which OS and build to load? - Can I use Khadas or corelec images directly on sztomato S905x hardware? - Must work: LAN, Wifi, BLE, USB, HDMI, Video Codecs (H.264, VP8, H.265, VP9) - I do not need Kodi or related TV functionality. There is no video encoding in my solution but does need Video decoding at hw / GPU level - I might need to display say max 4 simultaneous video playback in same browser window Note: Currently, using Raspberry Pi for development.But Chrome is taking almost 100% CPU while playing a received Video in Chrome browser. But using RPi is very simple: - Flash SD card with Raspbiain Stretch O/S and Load my software - Boot RPi and my solution is ready to use