Armbian for Amlogic S9xxx kernel 5.x

[Z11ntal33r]

19 minutes ago, balbes150 said:

This patch is for an old kernel, I don't work with this old kernel.

 

I understand. It's an unfortunate situation as the USB3.0 interface for meson-g12b devices is broken and neither Amlogic or Hardkernel devs want to send the patch upstream to mainline and follow it up (https://forum.odroid.com/viewtopic.php?f=176&t=33993&p=268688#p268598)...  One should absolutely avoid using meson-g12b devices if you want to use USB3 then. At the current state, my VIM3 is pointless as I can't move files between my micro SD and USB Harddrives. So I guess I've to build my own kernel and include this patch

[balbes150]

1 hour ago, Z11ntal33r said:

USB3.0 interface for meson-g12b devices

Try this version, it has a kernel with all the latest changes.

https://yadi.sk/d/ixLCvgeXlW4-1w

[Z11ntal33r]

6 hours ago, balbes150 said:

Try this version, it has a kernel with all the latest changes.

https://yadi.sk/d/ixLCvgeXlW4-1w

Unfortunately, with the build above I'm in a boot loop. I tried both booting from mSD slot and booting from a USB 3.0 mSD card reader. The latest line I can see on my TV is "OK Mounted /tmp." before it boots again. So I guess that the next line where it fails is "Found device /dev/...." etc. 

This is what I did:

1. Installed the build to a brand new mSD card and changed both /extlinux/extlinux.conf and uEnv.ini to meson-g12b-a311d-khadas-vim3.dtb.
2. Activated multi-boot and booted to mSD card. No other devices were connected expect from a keyboard.

PS: Which means that both Android VIM3_Pie_V190907 and my current Armbian_5.95_Aml-g12_Debian_buster_default_5.3.0-rc6_20190904 build is installed to eMMC.

I think it's easier to just upgrade kernel with my current system, so I will build the latest kernel files tomorrow both with and without the patch. I'll let you know when I've tested this, balbes150

[KrishIsola]

22 hours ago, KrishIsola said:

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

 

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
 

[dbsharpe]

32 minutes ago, KrishIsola said:

 

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 !!!).

 

 

I had issues with hostapd but I don't recall the exact problem. I got it down to the armbian kernel being a bit too new and perhaps a bug had crept in. The .config feature that wasnt working might have been multiple ssid's or higher speed wireless 802.11n.
Work around was to get hostapd sources a couple of years old and compile it.

I use rt2xxx based hardware and don't recommend  the internal wifi devices.

[balbes150]

14 hours ago, Z11ntal33r said:

Unfortunately, with the build above I'm in a boot loop. I tried both booting from mSD slot and booting from a USB 3.0 mSD card reader. The latest line I can see on my TV is "OK Mounted /tmp." before it boots again. So I guess that the next line where it fails is "Found device /dev/...." etc. 

Use the DTB from the previous image. There is an error in the current DTB for VIM3.

 

 

[balbes150]

New image 5.96_20190918

 

fix wifi

[KrishIsola]

4 hours ago, balbes150 said:

New image 5.96_20190918

 

fix wifi

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

[KrishIsola]

22 hours ago, dbsharpe said:

 

I had issues with hostapd but I don't recall the exact problem. I got it down to the armbian kernel being a bit too new and perhaps a bug had crept in. The .config feature that wasnt working might have been multiple ssid's or higher speed wireless 802.11n.
Work around was to get hostapd sources a couple of years old and compile it.

I use rt2xxx based hardware and don't recommend  the internal wifi devices.

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

[Z11ntal33r]

13 hours ago, balbes150 said:

Use the DTB from the previous image. There is an error in the current DTB for VIM3.

 

Yeah, that did the trick! With the build Armbian_5.96_Aml-g12_Ubuntu_bionic_dev_5.3.0_20190917 you uploaded, I'm finally able to copy/move files over the USB3.0 interface without any IO errors. Did you actually include the patch i referred to into this build or is it pure kernel 5.3.0?

One more thing. I tried to build the kernel files by following your guide at https://github.com/150balbes/Build-Armbian, but when I was building, I faced an error as seen from the picture attached. I've only followed your guide and selected "U-boot and kernel packages" -> "Do not change the kernel configuration" -> "aml-g12" -> "next". I want to upgrade my current installed build to the latest kernel with the patch. Any ideas why it fails? Let me know if you want the whole output or any logs.

Spoiler

 

 

Thanks for the great help BTW! It's awesome when someone from the community aid much more support than the actually support team who released the SBC...

[balbes150]

12 hours ago, Z11ntal33r said:

-> "next".

Build version NEXT is very naughty and is intended for experienced users who know the process of kernel build and the build Armbian (used source code directly from GIT Linux), also requires additional manual operations to configure a shared build (disable wireguard, etc.).  You'd better use the "default" option.

 

13 hours ago, KrishIsola said:

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

Current fixes address only a few model specific errors.

[Z11ntal33r]

14 hours ago, balbes150 said:

Build version NEXT is very naughty and is intended for experienced users who know the process of kernel build and the build Armbian (used source code directly from GIT Linux), also requires additional manual operations to configure a shared build (disable wireguard, etc.).  You'd better use the "default" option.

 

Current fixes address only a few model specific errors.

The reason for why I did not choose "default" was that it states: "Vendor provided / legacy". I do not want a vendor kernel, I want to update my 5.3RC6 kernel to 5.3.0.

I ask again: Your build Armbian_5.96_Aml-g12_Ubuntu_bionic_dev_5.3.0_20190917 you uploaded fixed the IO errors over USB3.0 interface for g12 devices. Did you actually include the patch i referred to into this build or is it pure kernel 5.3.0?

[balbes150]

5 minutes ago, Z11ntal33r said:

The reason for why I did not choose "default" was that it states: "Vendor provided / legacy".

This text is outdated and it is not necessary to pay attention to it.

 

7 minutes ago, Z11ntal33r said:

I ask again: Your build Armbian_5.96_Aml-g12_Ubuntu_bionic_dev_5.3.0_20190917 you uploaded fixed the IO errors over USB3.0 interface for g12 devices. Did you actually include the patch i referred to into this build or is it pure kernel 5.3.0?

Many additional patches are included in this kernel.

[Z11ntal33r]

On 9/19/2019 at 10:22 AM, balbes150 said:

This text is outdated and it is not necessary to pay attention to it.

Good to know! Choosing "default" worked perfectly and I built kernel 5.3.0 with the latest commit v20190918. I can see from GH source that you did include the patch dwc3/core: xHCI host not responding to stop endpoint command into commit v20190918. Thanks! 

For meson-g12 users: If you want to upgrade kernel to 5.3.0 with balbes150 v20190918 patches, the .deb files can be downloaded at: Armbian 5.96 and kernel 5.3.0 for meson-g12 devices (v.20190918)

[balbes150]

New image 5.96_20190920

[KrishIsola]

Hello @balbes150,

 

I have the following observations to share.

Observation with X96Max (S905x2 2gb ram 16gb eMMC). Request for your help to resolve.

1. Flashed 5.96 (& also latest dated 20-Sep) image on SD card.
2. 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
3. Successfully booted with Armbian Linux
4. 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:

1. 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
2. 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

 

[maachifx]

hello! 

first thank you for your hard work...

now i installed arndian ubuntu version desktop bionic 5.89 ,5.90 and 5.96 i had no problem with boot or installation ...

however when i try to install programs like vlc , kodi , google chrome , ext.... i cant get it to work 

my question is : is it possible to install programs in this ubuntu or not ?

ps  i am using USB drive of 16g and my tv box is almogic tanix tx3 max s905w

thanks again and plz help

[NicoD]

9 hours ago, maachifx said:

my question is : is it possible to install programs in this ubuntu or not ?

It should work fine. Do you have an internet connection? How are you trying to install them? Best way is to use the terminal.

sudo apt install vlc kodi chromium

You give very little useful info. Please show what's the result of your installation efforts.

[balbes150]

The launch of the current images Armbian with 5.3.0 kernel for Odroid C2.

Download image, unzip, burn image to SD card. Change the DTB name to  for odroid c2 (extlinux/extlinux.conf). Replace u-boot on the SD card on the version 20190923.

 

https://yadi.sk/d/M9TottOZuM5WLA

[balbes150]

New image 5.97

 

[qstaq]

7 hours ago, balbes150 said:

New image 5.97

 

Hi @balbes150

 

Just tried your new 5.97 image on an Odroid N2. All the basic hardware seems to work but Im getting a display saturated in green colour.  It looks like the blue colour is missing from the RGB signal, the same as when you have a faulty display cable. Its not an X11 problem, the display is green coloured in the framebuffer too, infact its green right from the point the kernel initialises. Any ideas as to what might be causing this?

 

I have not tried any previous versions of your G12 images yet or the official Armbian K4.9 build. The devices previously ran a buildroot based firmware of my own making with HK's 4.9 and there were no colour problems under framebuffer or wayland (no x11). Ive also just tried the Manjaro N2 release and that seems to work fine.

 

armbianmonitor -u:  http://ix.io/1WzE

 

 Thanks

 

 

Update:

Just tried the normal Armbian N2 build from the main download page and the colour problem is not there, the problem is only in your Yandisk images

 

Normal Armbian:  http://ix.io/1WAf

 

Update 2:

Just tried the 5.96 image and its fine. The colour problem is only with the 5.97 image

[balbes150]

14 hours ago, qstaq said:

Any ideas as to what might be causing this?

 

u-boot-2019 has a bug when working with the new kernel. For the new image to work properly on the N2, you must use either u-boot-2015 (which is in SPI) or replace the u-boot on the SD card. I have launched a new version of SPIboot. Which includes support for direct system startup from USB (and easy setup of any order of startup from all media) and use for tests and work only USB 3.0, which works much faster than all SD cards and eMMC.

 

 

 

 

[KrishIsola]

On 9/22/2019 at 12:28 AM, KrishIsola said:

Hello @balbes150,

 

I have the following observations to share.

Observation with X96Max (S905x2 2gb ram 16gb eMMC). Request for your help to resolve.

1. Flashed 5.96 (& also latest dated 20-Sep) image on SD card.
2. 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
3. Successfully booted with Armbian Linux
4. 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:

1. 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
2. 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

 

 

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

[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

[funben]

Hello to all

 

Thanks to @balbes150 for creating armbian.

Here is my problem, I can't figure how to start it.

1. I have a Beelink Mini MXIII v20_20160408
2. I downloaded   Armbian_5.97_Aml-g12_Debian_buster_default_5.3.0_20190923.img (also tried with Armbian_5.90_Aml-s905_Debian_buster_default_5.1.0_20190701.img )
3. I change dtb in uenv.ini to dtb_name=/dtb/meson-gxbb-p200.dtb (and also tried with dtb_name=/dtb-5.1.0-aml-s905/meson-gxbb-p200.dtb)
   I used this DTB because @Janaboy Janaboy say it works fine for mxIII
4. I burned it on SD card using rufus & Booted with recovery mode
5. I Have now have message "Gave up waiting for root file sytem device"

For more details, here is the console capture

https://pasteboard.co/IyXxDCZ.jpg

https://pasteboard.co/IyXyjaP.jpg

 

What should I do from here ?

[balbes150]

6 hours ago, funben said:

What should I do from here ?

1. Try all options for the dtb for your group (gxbb).

2. check start from USB flash drive.

[funben]

Thanks for your answer.

 

I started armbian succesfully with  "meson-gxbb-nexbox-a95x.dtbjeedom" however how can I check that erverything is fine / that it is the right DTB.

It seem that I have a network issue, the box is plugged with ethernet cable and I have "Network is unreachable" error

I had to start manually the network service

 

With the meson-gxbb-vega-s95-meta.dtb and meson-gxbb-vega-s95-pro.dtb the network started succesfully

How do I know which DTB is the best ?

 

 

 

[balbes150]

35 minutes ago, funben said:

How do I know which DTB is the best ?

Test and compare work.

[Reddwarf]

7 hours ago, funben said:

Thanks for your answer.

 

I started armbian succesfully with  "meson-gxbb-nexbox-a95x.dtbjeedom" however how can I check that erverything is fine / that it is the right DTB.

It seem that I have a network issue, the box is plugged with ethernet cable and I have "Network is unreachable" error

I had to start manually the network service

 

With the meson-gxbb-vega-s95-meta.dtb and meson-gxbb-vega-s95-pro.dtb the network started succesfully

How do I know which DTB is the best ?

 

 

 

I'v always user the -vega-s95- dtb's for my Mini MX-III and Mini M8S and found them to work best.

[ashok]

Hi all,

I am using a HIFI Xplay Q TV Box.

Configuration is Amlogic S912, 2GB RAM and 16GB storage with WIFI, Bluetooth, and Ethernet.

The System works as desired in ANDROID. When Booted to Armbian 5.94,5.95,5.96,5.97, Bluetooth and WIFI stopps to work.

 

I searched Armbian Forum and tried /etc/module entry. tried to load drivers manually. nothing works.

Command 'lsmod' shows ath10k is loaded. Which is wrong. Android says Brcm for reference I am copying dmesg output from Android.

[    1.442709@2] aml_wifi wifi.34: [wifi_dev_probe] no power_on_pin2
[    1.448606@2] aml_wifi wifi.34: [wifi_dev_probe] set pwm as 32k output
[    1.455240@2] aml_wifi wifi.34: [wifi_dev_probe] dhd_static_buf setup
[    1.461736@2] Wifi: bcmdhd_init_wlan_mem: bcmdhd_init_wlan_mem: WIFI MEM Allocated
[    1.469256@2] aml_wifi wifi.34: [wifi_dev_probe] interrupt_pin=241
[    1.475477@2] aml_wifi wifi.34: [wifi_dev_probe] irq_num=100, irq_trigger_type=1
[    1.482913@2] aml_wifi wifi.34: [wifi_dev_probe] power_on_pin=240
[    1.489031@2] aml_wifi wifi.34: [wifi_dev_probe] clock_32k_pin=0
[    1.495419@1] aml_wifi wifi.34: [wifi_setup_dt] wifi_setup_dt
[    1.500892@1] aml_wifi wifi.34: [wifi_setup_dt] interrupt_pin(241)
[    1.507065@1] aml_wifi wifi.34: [wifi_setup_dt] power_on_pin(240)
=====================================NEXT====================
[    7.223268@1] cfg80211:  DFS Master region: unset
[    7.227703@1] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[    7.227705@1] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[    7.227708@1] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[    7.227711@1] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[    7.227715@1] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz), (300 mBi, 2000 mBm)
[    7.227718@1] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (300 mBi, 2000 mBm)
[    7.227720@1] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm)
======================================NEXT====================
[   23.141394@0] aml_wifi wifi.34: [extern_wifi_set_enable] WIFI  Disable! 240
[   23.343296@0] aml_wifi wifi.34: [extern_wifi_set_enable] WIFI  Enable! 240
[   23.565941@5] avc open
[   23.565983@5] amvenc_avc  check CMA pool sucess, max instance: 2.
[   23.568757@5] allocating phys 0x75200000, size 20480k, wq:ffffffc063655c00.
[   23.575866@5] amvenc_avc  memory config sucess, buff start:0x75200000, size is 0x1400000, wq:ffffffc063655c00.
[   23.585764@2] avc release, wq:ffffffc063655c00
[   23.587807@6] sdio: queuing unknown CIS tuple 0x01 (3 bytes)
[   23.595625@2] remove  encode_work_queue ffffffc063655c00 sucess, _destroy_encode_work_queue line 4285.
[   23.601050@7] sdio: queuing unknown CIS tuple 0x1a (5 bytes)
[   23.606479@7] sdio: queuing unknown CIS tuple 0x1b (8 bytes)
[   23.607581@7] sdio: queuing unknown CIS tuple 0x14 (0 bytes)
[   23.610495@7] sdio: clk 200000000 SDR mode tuning start
[   23.610835@5] sdio: rx_tuning_result[1] = 10
[   23.611125@5] sdio: rx_tuning_result[2] = 10
[   23.611403@6] sdio: rx_tuning_result[3] = 10
[   23.611654@6] sdio: rx_tuning_result[4] = 10
[   23.611658@6] sdio: best_win_start =1, best_win_size =4
[   23.611661@6] sdio: sd_emmc_regs->gclock=0x1000245,sd_emmc_regs->gadjust=0x32000
[   23.611672@6] sdio: gclock =0x1000245, gdelay=0x0, gadjust=0x32000
[   23.613015@6] sdio: queuing unknown CIS tuple 0x80 (1 bytes)
[   23.613082@6] sdio: queuing unknown CIS tuple 0x81 (1 bytes)
[   23.613149@6] sdio: queuing unknown CIS tuple 0x82 (1 bytes)
[   23.613185@6] sdio: new ultra high speed SDR104 SDIO card at address 0001
[   23.614157@0] sdio: clock 200000000, 4-bit-bus-width
[   23.614157@0]  
[   23.614157@0] [sdio_reinit] finish
======================================NEXT====================
[   23.620885@0] wlan: [4353:E :HDD] wlan_hdd_cfg80211_init: wiphy->bands[i] is NULL, i = 2
======================================NEXT====================
[   25.151046@0] wlan: [4353:E :SAP] dfs_init_radar_filters[201]: Unknown dfs domain 0 
[   25.158257@0] +HWT
[   25.160792@0] Target Ready! : transmit resources : 3 size:1792, MaxMsgsPerHTCBundle = 32
[   25.168237@0] HTC Service Index : 1 TX : 0x100 : alloc:3 
[   25.173573@0] HTC Service:0x0001, ULpipe:1 DLpipe:0 id:0 Ready
[   25.179325@0] -HWT
[   25.181594@0] MAILBOX SWAP Service is enabled!
[   25.185879@0] Reduced Tx Complete service is enabled!
[   25.190342@4] ionvid: info: ionvideo_stop_generating!!!!
[   25.190367@4] ionvid: info: ionvideo release
[   25.192964@5] ionvid: info: ionvideo open
[   25.205661@0] is_full_reorder_offloaded? 0
[   25.208386@0] HTC Service TX : 0x300 : allocation is zero! 
[   25.215154@0] HTC Service:0x0300, ULpipe:1 DLpipe:0 id:1 Ready
[   25.219480@0] HTC Service:0x0300 ep:1 TX flow control disabled
[   25.225398@0] htt_tx_attach:htt_desc_start:0xffffffc02cea0000 htt_desc_end:0xffffffc02cebc200
[   25.234948@0] HTC Service:0x0100, ULpipe:3 DLpipe:2 id:2 Ready
[   25.239701@0] wma_pre_start-4928: WMA --> wmi_unified_connect_htc_service - success
[   25.247396@2] wma_mc_process_msg-21188: McThread: WNI_CFG_DNLD_REQ
[   25.261381@0] HTC using TX credit flow control
[   25.261905@4] wmitlv_check_and_pad_tlvs: WARN: TLV truncated. tlv_size_diff=24, curr_tlv_len=132
[   25.268925@4] __wmi_control_rx: WMI UNIFIED SERVICE READY event
[   25.275184@4] wma_rx_service_ready_event-23912: WMA <-- WMI_SERVICE_READY_EVENTID
[   25.282794@4] wlan: [2802:E :WDA] wma_rx_service_ready_event: Firmware build version : 0000030a
[   25.291040@4] wlan: [2802:E :WDA] wma_rx_service_ready_event: Board version: 0.22014009
[   25.298937@4] wma_rx_service_ready_event-24027: WMA --> WMI_INIT_CMDID
[   25.313068@4] __wmi_control_rx:  WMI UNIFIED READY event
[   25.313116@4] wma_rx_ready_event-24056: WMA <-- WMI_READY_EVENTID
======================================NEXT====================
[  196.039205@5] wlan: [6027:E :WDA]  scan complete - scan_id a008, vdev_id 0
[  196.041720@4] wlan: [4356:E :SME] Found 2 BSS
[  196.046836@4] wlan: [4356:E :PMC] PMC: Cannot enable BMPS timer. BMPS is disabled
[  211.117522@5] wlan: [4680:E :HDD] received scan request
[  211.118843@4] wlan: [4356:E :WDA] scan_id a009, vdev_id 0, scan type 0, msg_type 1103
[  211.268276@5] wlan: [6027:E :WDA]  scan complete - scan_id a009, vdev_id 0
[  211.269796@4] wlan: [4356:E :SME] Found 1 BSS
[  211.276539@4] wlan: [4356:E :PMC] PMC: Cannot enable BMPS timer. BMPS is disabled
[  231.120904@4] wlan: [4680:E :HDD] received scan request
[  231.122129@7] wlan: [4356:E :WDA] scan_id a00a, vdev_id 0, scan type 0, msg_type 1103
[  231.271651@5] wlan: [6027:E :WDA]  scan complete - scan_id a00a, vdev_id 0
[  231.273541@6] wlan: [4356:E :SME] Found 1 BSS
[  231.278958@6] wlan: [4356:E :PMC] PMC: Cannot enable BMPS timer. BMPS is disabled
[  251.123813@6] wlan: [4680:E :HDD] received scan request
[  251.125068@7] wlan: [4356:E :WDA] scan_id a00b, vdev_id 0, scan type 0, msg_type 1103
[  251.274620@5] wlan: [6027:E :WDA]  scan complete - scan_id a00b, vdev_id 0
[  251.276513@7] wlan: [4356:E :SME] Found 1 BSS

When doing same dmesg from Armbian no reference to wifi or any related thing.

but lsmod shows ath10k is loaded but ifconfig doesnt report any wifi interface.dmesg

can any one help me here?

 

By the way i am using Meson-gxm-q201.dtb. if this helps.