Which dtb do you use? Does ethernet work?
I’ve also got a X96 Max+.
Thanks
I use this one here: 71.5 KB file on MEGA
On my box ethernet is working with the above .dtb but others have reported problems which might be due to different board revisions/different hardware.
The wiki you have cited directly links to the linux firmware files. I guess it is a better idea to start with them (but they might be identical to the ones from android).
Also: I did not find exactly how to configure the .dts for wifi for your chip but you can find detailed information about bluetooth here: Linux v6.6.1 - Documentation/devicetree/bindings/net/mediatek-bluetooth.txt were it is written that “compatible” in bluetooth section of the .dts must be set to “mediatek,mt7663u-bluetooth” for a MT7663U device.
Thanks!
I’ll try it
Great!
It worked. I’ve tried before with many dtb’s and I didn’t success.
Sound also works through hdmi but doesn’t work jack output.
Do you know any way to have jack sound?
Thanks for your help!!
Sorry for the delay, I’ve been really busy today.
Yes, and that link points to the sources of the linux-firmware package (correct me if I’m wrong), which I of course have installed. I’m not retarded, man. I really wish it was that trivial to get that damn wifi working, but… let’s just say I’m not a very lucky person.
but they might be identical to the ones from android
They are not. Some files that can be found among android firmware files (like WIFI_RAM_CODE_MT7663.bin) are not provided by linux-firmware. Perhaps I should make use of those files, just need to figure out how.
Linux v5.13-rc1 - Documentation/devicetree/bindings/net/mediatek-bluetooth.txt
Thanks, checked it out. But I still have no idea how to figure out all those 0xBytes and the page says nothing about it. Are they provided by hardware or by software? .dts extracted from android has completely different nodes hierarchy and addresses.
Hi @spikerguy,
I notice you have released linux-vim 5.12.1-1. Just checking whether this new linux-vim-5.12.1-1 is stable on GT King Pro. The previous linux-vim 5.11.y causes kernel panic on GT King Pro.
I am currently on linux-5.12.2-2 which is stable on GT King Pro but will NOT Reboot or Shutdown cleanly which need a power cycle to restart the device.
Linux-vim 5.11.y have no issue with Reboot if it doesn’t kernel panic during the reboot/booting process. Prefer to be on linux-vim 5.12.1-1 if it doesn’t have kernel panic issue on GT King Pro.
Try 5.12 as there should be not kernel panic. The shutdown and reboot is more of uboot and kernel combined.
I have not been able to test GT King Pro with linux-vim
I will try the latest kernel and see if it shutdown properly.
Hi @spikerguy,
Just installed linux-vim 5.12.1-1, Out of 5 start/boot 3 kernel panic during boot up process and 2 successful boot up. The current linux-vim 5.12.1-1 doesn’t seem to stable on GT King Pro too.
Does it looks like the linux-vim 5.11.y or linux-vim 5.12.1-1 are having conflict with the GT King Pro vendor BSP u-boot? In my experience with linux-vim 5.11.y most of the kernel panic happen during boot up process (before reaching lightdm startup) or right after successful login greeting screen. The 3 kernel panic with linux-vim 5.12.1-1 is during boot up process before login greeting screen.
Linux-vim 5.12.1-1 like linux-vim 5.11.y can Reboot or Shutdown cleanly that is if it doesn’t kernel panic.
Just bumping this as I’m still hoping to get some help.
Don’t use linux-vim I see too many kernel panic on normal use on my Khadas vim3 test. Stay on upstream kernel for now as currently that is the most stable so far.
Noted, thanks. So with current linux-vim, kernel panic is also occurring other devices not specific to GTKPro alone.
Yes, linux-5.11.y or linux-5.12.y had been stable. So far, I have not encounter any kernel panic with linux kernels and Panfrost (mesa-git) seems to work well on Xfce DE. With the new mesa 21.1.0 released, will it be better to switch to mesa 21.1.0 instead?
Yes all my S922x are on mesa only and it is very stable.
Hello, that sounds very interesting for us user of a X96AIR/MAX+ box.
Please share the “How to” of using this kernel:
linux-amlogic-512
Thanks in advanced.
@spikerguy: fits to your same intention linux-aml?
Add the following to /etc/pacman.conf, update your package lists and you can easily install the kernel using pacman or pamac.
[archlinuxdroid]
SigLevel = Optional
Server = http://archlinuxdroid.tk/archlinuxdroid/aarch64
But I am not sure if the kernel is so much different to @spikerguy’s last kernel. At least some time ago he wrote that he planned to switch from tobetter’s kernel source to chewitt’s kernel source which above kernel is based upon.
I still have to test @spikerguy’s last kernel myself …
great, it works:
uname -a
Linux X96AIRP3 5.12.0-1-ARCH #1 SMP PREEMPT Tue Apr 27 15:05:55 AST 2021 aarch64 GNU/Linux
I"m using the last unstable release 20210517 together with meson-sm1-x96-air-1000.dtb also from CHEWITT @ LIBREELEC branch.
Unfortunately the no-sound-card problem still exist:
mesg | grep sound
[ 3.244646] No soundcards found.
loaded modules are:
lsmod | grep snd
snd_soc_hdmi_codec 20480 1
snd_soc_meson_axg_sound_card 16384 0
snd_soc_meson_card_utils 16384 1 snd_soc_meson_axg_sound_card
snd_soc_meson_g12a_tohdmitx 20480 1
snd_soc_meson_axg_tdmout 24576 1
snd_soc_meson_codec_glue 16384 1 snd_soc_meson_g12a_tohdmitx
snd_soc_meson_axg_frddr 36864 3
snd_soc_meson_axg_fifo 20480 1 snd_soc_meson_axg_frddr
snd_soc_meson_axg_tdm_interface 16384 2 snd_soc_meson_axg_sound_card
snd_soc_meson_axg_tdm_formatter 16384 2 snd_soc_meson_axg_tdm_interface,snd_soc_meson_axg_tdmout
I would say the problem is in the u-boot.ext. The used doesn’t fit so perfect to the box-u-boot.
I’ve extracted/unpacked from the firmware a uboot and partition file. Could it be helpfull to get a working u-boot.ext @strit ?
Any idea or advice are warmly welcome 
You should ask @spikerguy as he is the one doing those images. Pretty sure the images for vim2 and vim3 relies on having android uboot on the eMMC.
1 Like
Hello @strit, thanks for your support and the great job!
I did unpacked with:
\AMLogicTools_V7.1.0_Donate\tmp\level1
14.05.2021 19:26 602 aml_sdc_burn.ini
14.05.2021 19:26 1.302.384 aml_sdc_burn.UBOOT
14.05.2021 19:26 9.639.936 boot.PARTITION
14.05.2021 19:26 1.301.872 DDR.USB
14.05.2021 19:26 438 dtbo.PARTITION
14.05.2021 19:26 1.118 image.cfg
14.05.2021 19:26 2.077.040 logo.PARTITION
14.05.2021 19:26 540.748 odm.PARTITION
14.05.2021 19:26 155 platform.conf
14.05.2021 19:26 3.768.396 product.PARTITION
14.05.2021 19:26 16.326.656 recovery.PARTITION
14.05.2021 19:26 1.110.630.620 system.PARTITION
14.05.2021 19:26 4.096 vbmeta.PARTITION
14.05.2021 19:26 413.401.308 vendor.PARTITION
14.05.2021 19:26 82.807 _aml_dtb.PARTITION
Hello @spikerguy, which file can you use to create a right u-boot.ext for the X96AIR-box?
I have uploaded my .dtb and u-boot.ext here: 4.98 MB folder on MEGA
Maybe it helps you …
I’m sorry to say but no improvement.
No matter how of any combination of u-boot.ext & meson-sm1-x96…dtb:
- no soundcard detected / no sound-over-HDMI
- no Wifi
- no Bluetooth
I would say the problem is in the hardwaredetection/interface of u-boot.ext.
My box is running very stable and with a good performance with both kernel 5.12 (VIM & AMLOGIC) and branch unstable.
May be @spikerguy can help: which file can you use to create a right u-boot.ext for the X96AIR-box?
Thanks in advance.
btw:
A good tutorial for compiling uboot.ext? - General Chat - Armbian forum
→ But it looks like the u-boot.ext Balbes uses is one without de binaries from Amlogic, since he is chaining his bootloader after the boards own u-boot, so memory initialization and soc initialization is already done.
Chainloaded uboot images for amlogic - Amlogic CPU Boxes - Armbian forum