Need to switch kernel in vim3 profile.
No. It is upstream kernel with patches maintained by khadas. You can check their fenix Project on their git.
Hi @spikerguy,
I just install linux-aml 5.12.0-1 on the freshly burn Manjaro-XFCE-v21.04 upgraded to mainline linux-5.12.4-1 installation when through but it will not boot.
[jfl@MNJROGTKPro ~]$ sudo pacman -U http://mirror.easyname.at/manjaro/arm-unstable/core/aarch64/linux-aml-5.12.0-1-aarch64.pkg.tar.zst http://mirror.easyname.at/manjaro/arm-unstable/extra/aarch64/mesa-21.1.1-1-aarch64.pkg.tar.xz
[sudo] password for jfl:
linux-aml-5.12.0... 50.2 MiB 2.81 MiB/s 00:18 [######################] 100%
linux-aml-5.12.0... 310.0 B 0.00 B/s 00:00 [######################] 100%
mesa-21.1.1-1-aa... 14.5 MiB 3.62 MiB/s 00:04 [######################] 100%
mesa-21.1.1-1-aa... 566.0 B 0.00 B/s 00:00 [######################] 100%
loading packages...
resolving dependencies...
looking for conflicting packages...
:: linux-aml and linux are in conflict. Remove linux? [y/N] Y
Packages (3) linux-5.12.4-1 [removal] linux-aml-5.12.0-1 mesa-21.1.1-1
Total Installed Size: 140.29 MiB
Net Upgrade Size: -37.51 MiB
:: Proceed with installation? [Y/n] Y
(2/2) checking keys in keyring [######################] 100%
(2/2) checking package integrity [######################] 100%
(2/2) loading package files [######################] 100%
(2/2) checking for file conflicts [######################] 100%
(3/3) checking available disk space [######################] 100%
:: Processing package changes...
(1/1) removing linux [######################] 100%
(1/2) installing linux-aml [######################] 100%
Optional dependencies for linux-aml
crda: to set the correct wireless channels of your country
(2/2) upgrading mesa [######################] 100%
:: Running post-transaction hooks...
(1/4) Arming ConditionNeedsUpdate...
(2/4) Updating module dependencies...
(3/4) Updating linux-aml module dependencies...
(4/4) Updating linux-aml initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux-aml.preset: 'default'
-> -k 5.12.0-1-MANJARO-ARM -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 5.12.0-1-MANJARO-ARM
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [plymouth]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [filesystems]
-> Running build hook: [keyboard]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
It does not boot with the linux-aml-5.12.0-1, it give the similar errors as earlier. What could be the issue?
Edit:
The same SD Card with Manjaro-XFCE-mainline-linux-5.12.y never had any boot up issue or I/O error on “dev mmcblk0”.
Not clear what you meant by “Need to switch kernel in vim3 profile”. Appreciate if you can clarify.
Now this is interesting. With the Khadas upstream mainline with patches kernel 5.12.0, I currently sometimes encounter kernel during boot up process or right after login. But with Manjaro mainline linux 5.11.y or linux-5.12.y it is very stable, NO kernel panic so far. Thanks for the good work. Somehow still cannot get Manjaro linux-aml 5.12.0-1 to boot up.
Hi @spikerguy,
Had to reburn Manjaro-Arm-XFCE using Manjaro-20.12 as a base as Manjaro 21.04 with linux-vim 5.11.7-1 had kernel panic during system update. After switching to linux-aml 5.12.0-1 seems to render the SD Card NOT bootable. Now using the Stable Branch with mainline linux 5.12.4-1.
Encounter two issues. The dmesg is fill up with the following errors:
[ 43.764330] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.765303] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.765474] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.765604] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.765933] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.766250] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.766934] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.766983] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.767017] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.767252] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.767500] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.767986] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.768033] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.768066] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.768295] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.768530] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.769369] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.769493] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.769595] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.769874] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.770147] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.770973] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.771109] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.771235] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.771524] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.771810] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.786381] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 43.786431] fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
And also mirrors errors:
[sudo] password for jfl:
:: Synchronizing package databases...
error: failed retrieving file 'core.db' from uk.mirrors.fossho.st : Failed to connect to uk.mirrors.fossho.st port 443: Connection refused
core is up to date
error: failed retrieving file 'extra.db' from uk.mirrors.fossho.st : Failed to connect to uk.mirrors.fossho.st port 443: Connection refused
extra is up to date
error: failed retrieving file 'community.db' from uk.mirrors.fossho.st : Failed to connect to uk.mirrors.fossho.st port 443: Connection refused
community is up to date
sudo pacman-mirrors -g
::INFO Downloading mirrors from Manjaro
::INFO => Mirror pool: https://repo.manjaro.org/mirrors.json
::INFO => Mirror status: http://repo.manjaro.org/status.json
::INFO Using default mirror file
::INFO Querying mirrors - This may take some time
1.871 Australia : https://manjaro.lucassymons.net/
1.887 Australia : https://mirror.aarnet.edu.au/pub/manjaro/
1.641 Australia : http://mirror.aarnet.edu.au/pub/manjaro/
1.437 Austria : http://mirror.easyname.at/manjaro/
..... Austria : ftp://mirror.easyname.at/manjaro/
0.499 Bangladesh : http://mirror.xeonbd.com/manjaro/
..... Belarus : http://mirror.datacenter.by/pub/mirrors/manjaro/
1.545 Belgium : http://ftp.belnet.be/mirrors/manjaro/repos/
..... Belgium : ftp://ftp.belnet.be/mirrors/manjaro/repos/
1.655 Belgium : https://mirror.futureweb.be/manjaro/
1.181 Belgium : http://mirror.futureweb.be/manjaro/
..... Brazil : https://manjaro.c3sl.ufpr.br/
..... Brazil : http://linorg.usp.br/manjaro/
1.768 Bulgaria : https://mirrors.netix.net/manjaro/
2.076 Bulgaria : https://mirror.telepoint.bg/manjaro/
1.275 Bulgaria : http://mirror.telepoint.bg/manjaro/
..... Bulgaria : ftps://mirror.telepoint.bg/manjaro/
::ERROR unknown url type: ftps
0.001
2.265 Bulgaria : https://manjaro.ipacct.com/manjaro/
..... Bulgaria : http://manjaro.telecoms.bg/
2.588 Canada : https://mirror.csclub.uwaterloo.ca/manjaro/
2.304 Canada : https://mirror.0xem.ma/manjaro/
..... Canada : http://mirror.0xem.ma/manjaro/
..... Canada : https://osmirror.org/manjaro/
::ERROR Connection: HTTPSConnectionPool(host='osmirror.org', port=443): Max retries exceeded with url: /manjaro/arm-stable/core/aarch64/core.db.tar.gz (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0xffff98f068e0>, 'Connection to osmirror.org timed out. (connect timeout=4)'))
..... Chile : http://manjaro.dcc.uchile.cl/
..... Chile : https://mirror.ufro.cl/manjaro/
::ERROR Connection: HTTPSConnectionPool(host='mirror.ufro.cl', port=443): Read timed out. (read timeout=4)
..... Chile : https://mirror1.cl.netactuate.com/manjaro/
..... Chile : http://mirror1.cl.netactuate.com/manjaro/
..... Chile : ftp://mirror1.cl.netactuate.com/manjaro/
..... China : https://mirrors.huaweicloud.com/manjaro/
..... China : http://mirrors.huaweicloud.com/manjaro/
2.113 China : https://mirrors.ustc.edu.cn/manjaro/
..... China : https://mirrors.tuna.tsinghua.edu.cn/manjaro/
::ERROR Connection: HTTPSConnectionPool(host='mirrors.tuna.tsinghua.edu.cn', port=443): Read timed out.
..... China : https://mirrors.tuna.tsinghua.edu.cn/manjaro/
::ERROR Connection: HTTPSConnectionPool(host='mirrors.tuna.tsinghua.edu.cn', port=443): Read timed out. (read timeout=4)
After the pacman-mirrors, mirrors errors still persist.
Any suggestions how to resolve the “fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0” and mirrors errors. Thanks.
Edit: The “fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0” is due to “sound” issue. Resolved by editing “g12_sound.sh” to enable Amlogic OLD CONF…
Appreciate tips how to resolve “pacman mirrors” issue.
Edit2: “sudo pacman-mirrors -f 5” resolved the mirrors errors issue. My ignorance. Sorry to trouble you.
I have got a X96AIR_Q1000 / sm1_ac213_4g. I found a dts on the Armbian forum that has enabled me to get gig ethernet, wifi and HDMI audio working, so now its just the BT (bluetoothctl doesn’t list any bt controllers) and onboard analogue audio , AML-AUGESOUND, to work.
Has anyone had any success getting either of of these to work under Manjaro on a S905X3 TV box?
1 Like
see also:
Have you searched on armbian forum
Sure. No success.
Well, there’s a thread about mt7668rsn, but I’m not sure if it’s relevant as my chip (mt7661rsn, don’t even try to google lol) has mt7603 as its wifi part. Android uses same driver for mt76x3 and mt76x8 chips, though…
The last poster basically says that wifi is not working, but thread is almost year old so things might have changed.
They always need some random extra blobs
What about .bin files from stock android firmware (I’m not uploading them as it might be illegal or something)? It’s not enough to simply put them under /usr/lib/firmware, at least it didn’t work for me, so perhaps they should be explicitly required by kernel/driver and then handled by its code in some way, so should I patch the driver and recompile it? Or it’s not about blobs at all, and I should start with setting up my dts? Some guy up the thread told me that communication over the bus the chip is located on is not functional (whatever it means):
so perhaps I should first change one of those <0xffee00shit> in dts somehow? But I’m not very good at that low-level C stuff. I guess some addresses should be same for all meson-sm1 (and compatible meson-g12a) boards, but which ones? And which ones should I change? And what to substitute them with?
Anyway, how do I tell if that communication is functional or not? SDIO device corresponding to WiFi chip can be found under /sys/bus/sdio/devices and udevadm correctly determines vendor (“Mediatek, Inc” or something like that) and ID (0x7603), does it mean it’s functional?
(I’d share udevadm output but my usb is dead now so cannot boot the system)
See? Too many questions, and if I try to find all the answers myself, it’s gonna take years, given that I don’t have all the time in the world. I guess, people like you have much better understanding of kernel guts. Not asking to solve everything for me — I know it’s not as simple as ./do-zaebis.sh — but at least I want these questions answered (I mean, about dts, firmware, etc). It’d be nice if you could help.
I got the onboard bluetooth working on my X96 Air Q1000 today. It works with my BT keyboard and trackpad under both KDE and GNOME. You can download the dts and dtb from here:
This dts doesn’t enable the onboard audio for me but HDMI audio works as does wifi and gigabit ethernet.
I have been speaking to amlogic kernel dev Neil Armstrong and it sounds like we should be able to get the onboard audio working for boxes like the X96 Air because the Banana PI BPI-M5 has working onboard audio and it uses the same audio codec:
3 Likes
Great! Just checked with the .dtb and HDMI-sound is working with my X96AIR P3.
But still no-Wifi & no-BT for my box.
1 Like
That’s a shame. I don’t have an X96 Air P3 but I should be getting a X96 Max Plus in the next few weeks.
I only ordered a max plus because I didn’t think my Air had gigabit ethernet. Well I was wrong and I probably should’ve bought another X96 Air Q1000 instead because they have 3 USB ports and I’ve got everything working now except the onboard audio.
I’ll hopefully get a chance to try building a kernel with the BPi 5 dts today. I want to try that using that first else I may be adding the onboard audio patches into the latest sei610 dts.
1 Like
Good work with the dtb tuning 
2 Likes
Using @TheMojoMan rtl8822cs-aml-2020.11.20-1-any.pkg.tar.zst with linux-aml 5.12.0.1, wifi works for me, on my X96AIR P3.
meson-sm1-sei610-qca9377-bt.dtb doesn’t enable Bluetooth on the X96AIR P3 (the chip must be different from X96 AIR Q1000)
2 Likes
I got and tried it.
Just tried again with linux-vim 5.12.1-1 and HDMI-sound is now working,
but still no-wifi, no-BT
firmware for BT seems to be in the release:
sudo find / -name rtl8822cs*
/usr/lib/firmware/rtl_bt/rtl8822cs_fw.bin
/usr/lib/firmware/rtl_bt/rtl8822cs_config.bin
FYI.
My box is reported by Android “Device Info HW”
- Manufacturer: Droidlogic
- Brand: Amlogic
- Device: franklin
- modell: X96AIR_P3
- board: sm1_ac213_4g
with Termux also sm1_ac213_4g
I use with:
CoreElec : sm1_s905x3_4g_1gbit.dtb w/o problems, everything works
LibreElec: meson-sm1-x96-air-1000.dtb w/ screen color problem
Manjaro Arm: meson-sm1-x96maxplus-100M-vim.dtb no-wifi, no-BT
Armbian : I never got it working, wasting massive time
Khadas-Ubuntu Kernel 4.9 : sm1_s905x3_4g_1gbit.dtb from CE w/ high cpuload
Khadas-Ubuntu Kernel 5.12 : meson-sm1-x96-air-1000.dtb from LE only wayland
What a mess!
Search in android termux for your wifi.
Try to find brcm, bcm, wlan0 … You have the compatible firmware in some OS, search in them.
Need some assistance on how to set Manjaro-Arm-XFCE to auto login. I tried to edit /etc/lightdm/lightdm.conf
autologin=jfl
but it still prompt to enter password during boot up.
I think to remember that you have to add your user to the autologin group as well. There is a good description in LightDM - ArchWiki
1 Like
Enabling autologin
only 3 steps with manjaro:
Edit the LightDM configuration file and ensure these lines are uncommented and correctly configured:
/etc/lightdm/lightdm.conf
- autologin-user=username
You must be part of the autologin group to be able to login automatically without entering your password:
- groupadd -r autologin
- gpasswd -a username autologin
1 Like