Keyboard and Mouse not functioning
JFLim1 opened this issue · comments
Hi @ophub,
Installed Armbian_22.02.0_Aml_s922x_bullseye_5.4.171_2022.01.12.0851.img.gz on SD Card. Somehow the newly burned image on SD Card using Etcher or Rufus, the SD Card cannot seems to be recognised when I try to inspect the newly burned SD Card image using another linux image on USB Flash. Basically with "Disks" or "Gparted" the SD Card is NOT Allocated. Cannot mount or show up on File Manager.
But the funny thing is, managed to boot up on second try on GT King Pro Rev A. After boot up, performed the following:
sudo apt update
sudo apt upgrade "had dpkg warning ...linux-image-current-meson64 missing..." but it upgraded successfully.
armbian-tf e (to expand the SD Card)
sudo mv u-boot.ext to u-boot.ext-none (per my understanding u-boot.ext is not require with kernel 5.4.y)
reboot successfully
The issue is during boot up I noticed:
Failed ...keymap....
On TTY session keyboard works without issue.
Proceeded to install GNOME 41 following the instructions from https://www.linuxcapable.com/how-to-install-gnome-41-desktop-unstable-on-debian-11-bullseye/
Installed GNOME 41 successfully.
Reboot a success to gdm3 login greeting screen. But the issue is keyboard and mouse not functioning/working. Cannot enter the password to proceed to Desktop Environment! Unplug and replug keyboard or mouse make NO difference.
Cannot go back to TTY session with "ctl+alt+F1" or "ctl+alt+F2" so basically stuck and not usable now.
Any advice? How to get Armbian_22.02.0_Aml_s922x_bullseye_5.4.171_2022.01.12.0851.img.gz (kernel 5.4.y without u-boot.ext) to work on DE (i.e. keyboard and mouse working).
what box? What interface is your keyboard and mouse? Check if the kernel has driver support.
#for had dpkg warning... linux-image-current-meson64
sudo apt-get remove -y linux-image-current-meson64
It is recommended to keep u-boot.ext
try updating other kernels: armbian-update 5.15.14
look at this: #31
what box?
Beelink GT King Pro (Revision A).
What interface is your keyboard and mouse?
USB Keyboard and USB Mouse.
Check if the kernel has driver support.
Appreciate your guidance on how to check? Currently the SD Card can only boot up to GDM3 Greeter Login Screen but stuck there. Keyboard and Mouse does not work for me to proceed further. What commands to check whether kernel keyboard and mouse driver support?
#for had dpkg warning... linux-image-current-meson64
sudo apt-get remove -y linux-image-current-meson64
sudo apt-get install -y linux-image-current-meson64
Noted.
FYI, "apt list linux-image* --installed" return that "linux-image-current-meson64" has been installed.
uname -a output kernel 5.4.171-flippy-69+ and not 5.4.171-meson64.
Willl sudo apt-get install -y linux-image-current-meson64
results in kernel install 5.4.171-meson64 or 5.4.171-flippy-69+? Just curious.
It is recommended to keep
u-boot.ext
Noted.
But the u-boot-gtkingpro.bin does not always consistently boot up per my understanding and actual usage. This u-boot.ext from https://disk.yandex.ru/d/ZMQW85B-P6QejA seems to boot up consistently.
try updating other kernels:
armbian-update 5.15.14
Cannot upgrade to other kernel as the boot up stuck at Login Greeter Screen and no longer able to do anything.
Will have to burn a new image:
#Armbian_22.02.0_Aml_s922x_bullseye_5.15.14_2022.01.13.1524.img.gz
Thank you.
Out of curiosity why would the newly burn SD Card image not being able to be recognized by Ubuntu or Manjaro?
Burn Armbian_22.02.0_Aml_s922x_bullseye_5.15.14_2022.01.13.1524.img.gz on SD Card (Samsung Evo Plus 64GB) with Rufus.
Boot up stuck at "initramfs". A lot of I/O Errors, dev mmcblk1...
Again the SD Card cannot be recognized by Ubuntu or Manjaro. "Disks" or "Gparted" return SD Card as unallocated.
what box are you? model?
If the SD card is not recognized, you can format it first and change the burning tool, such as https://rufus.ie/
what box are you? model?
Beelink GT King Pro (Revision A, Serial # SA9HH.....)
If the SD card is not recognized, you can format it first and change the burning tool, such as https://rufus.ie/
Yes, I did format the SD Card first and then use Rufus as burning tool. Also tried with Balena Etcher as burning tool. Same issue.
With kernel 5.4.171 image it boot up successfully but after install Gnome Desktop keyboard and mouse not recognized or functioning.
With kernel 5.15.14 image, it cannot boot up successfully stuck at "initramfs" and with a lot of I/O Errors.
Could it be related to u-boot-gtkingpro.bin as u-boot.ext and kernel 5.15.14 not compatible with my device? But I cannot swap the u-boot.ext from the one that I use regularly as I cannot access to SD Card with another Linux OS.
I have the same problem with Armbian_22.02.0_Aml_s912_bullseye_5.4.171_2022.01.12.2339.img.
Tanix tx92 (3gb ddr3, 32gb emmc, s912).
I installed to emmc, same warning about linux-image-current-meson64 missing.
Then I installed XFCE and the mouse and keyboard didn't work.
I tried using ssh, and tried
sudo apt-get remove -y linux-image-current-meson64
sudo apt-get install -y linux-image-current-meson64
On reboot, the tv box went into a bootloop (bad CRC, unable to initialize ethernet due to TIMEOUT).
Tanix tx92 is currently unclear.
Not all boxes support writing to emmc, and the ones that can be written have a special serial number in the armbian-install list. If you are not sure about writing, it is recommended to use on SD/usb/tf.
There are many types of TV boxes, and the boxes that are not in the known list need to be tested by yourself. If you find a good uboot and dtb matching solution, you can share it and help other users.
Tanix tx92 is currently unclear.
Not all boxes support writing to emmc, and the ones that can be written have a special serial number in the armbian-install list. If you are not sure about writing, it is recommended to use on SD/usb/tf.
There are many types of TV boxes, and the boxes that are not in the known list need to be tested by yourself. If you find a good uboot and dtb matching solution, you can share it and help other users.
It was working perfectly from CLI, using h96 pro plus installation profile.
The problem is the DE that don't recognize mouse and keyboard.
The tv box model is TX92-LP.
After installing the desktop, the mouse and keyboard are not recognized. It should be a lack of drivers. What model of USB keyboard are you using?
After installing the desktop, the mouse and keyboard are not recognized. It should be a lack of drivers. What model of USB keyboard are you using?
Peripherals aren't recognized after the desktop environment install (Xfce).
When I have installed armbian on emmc, and rebooted, the keyboard works.
I use this keyboard, by the way https://www.amazon.it/dp/B00W102J5Q/
The Nsc Tanix TX92 S912 3GB RAM 32GB ROM 1000M LAN 5G WIFI you used is the first friend to give feedback, can you use it when you write emmc? Can you share which U-BOOT and DTB file you used? Will kernel 5.10 work?
#Are you using this configuration?
Tanix TX92
s912
meson-gxm-octopus-planet.dtb
u-boot-zyxq.bin
Is the product this? https://www.tokopedia.com/nevishopcom/nsc-tanix-tx92-s912-3gb-ram-32gb-rom-1000m-lan-5g-wifi?whid=0
The
Nsc Tanix TX92 S912 3GB RAM 32GB ROM 1000M LAN 5G WIFIyou used is the first friend to give feedback, can you use it when you write emmc? Can you share whichU-BOOTandDTBfile you used? Will kernel 5.10 work?Is the product this? https://www.tokopedia.com/nevishopcom/nsc-tanix-tx92-s912-3gb-ram-32gb-rom-1000m-lan-5g-wifi?whid=0
I used the same configuration of h96 pro plus, zyxq uboot and octopus planet dtb (this is the only dtb in which ethernet works correctly, wifi doesn't work).
When I write to emmc it works, even on reboot.
I didn't test 5.10 yet.
Model is in your link, and it's a rebranded Vorke Z6 Plus, so I would add that as well.
I used the same configuration of h96 pro plus, zyxq uboot and octopus planet dtb (this is the only dtb in which ethernet works correctly, wifi doesn't work). When I write to emmc it works, even on reboot. I didn't test 5.10 yet.
Model is in your link, and it's a rebranded Vorke Z6 Plus, so I would add that as well.
armbian-update 5.10.91
You can try updating the kernel to version 5.10. Thank you for your sharing, I will add the installation option of this box to armbian-install, and I will record your sharing in CONTRIBUTOR.md
VORKE Z6 Plus Amlogic S912 3GB DDR3 32GB: https://www.tokopedia.com/mbitabn/vorke-z6-plus-android-7-1-2-smart-tv-box-amlogic-s912-3gb-ddr3-32gb?whid=0
I use armbian to access through ssh on my laptop, using the server version mode, and have not installed the desktop. Seeing that everyone connects the mouse and keyboard to use the desktop version, I will buy an external device to try.
Could it be related to u-boot-gtkingpro.bin as u-boot.ext and kernel 5.15.14 not compatible with my device? But I cannot swap the u-boot.ext from the one that I use regularly as I cannot access to SD Card with another Linux OS.
According to your message above, maybe serial number 44 is your box
There are several different versions of this box that you modify according to your own version.
After img is flashed into sd, double-click to open, you can modify the files under /boot
Modify the dtb file to
meson-g12b-gtking-pro-rev_a.dtb in uEnv.txtNoted. But the u-boot-gtkingpro.bin does not always consistently boot up per my understanding and actual usage. This u-boot.ext from https://disk.yandex.ru/d/ZMQW85B-P6QejA seems to boot up consistently.
According to the documents you provided, I specially made a firmware for you, you can try if it can be used. dc23f3b
In releases, like Armbian_22.02.0_Aml_s922x-reva_focal_xxx.img.gz
armbian-install number 45
I used the same configuration of h96 pro plus, zyxq uboot and octopus planet dtb (this is the only dtb in which ethernet works correctly, wifi doesn't work). When I write to emmc it works, even on reboot. I didn't test 5.10 yet.
Model is in your link, and it's a rebranded Vorke Z6 Plus, so I would add that as well.
armbian-update 5.10.91You can try updating the kernel to version 5.10. Thank you for your sharing, I will add the installation option of this box to armbian-install, and I will record your sharing in CONTRIBUTOR.md
VORKE Z6 Plus Amlogic S912 3GB DDR3 32GB: https://www.tokopedia.com/mbitabn/vorke-z6-plus-android-7-1-2-smart-tv-box-amlogic-s912-3gb-ddr3-32gb?whid=0
I use armbian to access through ssh on my laptop, using the server version mode, and have not installed the desktop. Seeing that everyone connects the mouse and keyboard to use the desktop version, I will buy an external device to try.
I tried this kernel and now mouse and keyboard work, shouldn't it be the default kernel for s912?
I tried this kernel and now mouse and keyboard work, shouldn't it be the default kernel for s912?
Did you test a kernel that supports version 5.10?
Which version of the kernel supports your mouse and keyboard?
I tried this kernel and now mouse and keyboard work, shouldn't it be the default kernel for s912?
is the default.
Did you test a kernel that supports version 5.10?
Which version of the kernel supports your mouse and keyboard?
The s912 downloadable release was using 5.4, and mouse not working.
I updated to 5.10 and now it works.
In order to save space on github, I only compiled the 5.4 kernel. It seems that different versions need to be compiled by default.
When it is convenient, please test whether the 5.15 kernel supports mouse and keyboard.
armbian-update 5.15.14
According to your message above, maybe serial number 44 is your box
There are several different versions of this box that you modify according to your own version.
After img is flashed into sd, double-click to open, you can modify the files under /boot
Modify the dtb file tomeson-g12b-gtking-pro-rev_a.dtbinuEnv.txt
Thanks noted. Did not know that there is a difference in gtking-pro.dtb between regular and Rev A in mainline kernel. I understand in CoreElec (kernel 4.9.y legacy) or linux image with kernel 4.9.y I need to use Rev A dtb but on mainline kernel I have always use the regular meson-g12b-gtking-pro.dtb. Good to know there is a Rev A dtb for GT King Pro. Thank you.
According to the documents you provided, I specially made a firmware for you, you can try if it can be used. dc23f3b
Thank you very much.
In releases, like Armbian_22.02.0_Aml_
s922x-reva_focal_xxx.img.gz
Great. Do you have Bullseye build with s922x-reva?
armbian-installnumber45
What is this command "armbian-install number 45"? I am not familiar.
What is this command "armbian-install number 45"? I am not familiar.
From releases: https://github.com/ophub/amlogic-s9xxx-armbian/releases/tag/Armbian_Aml_focal_2022.01.15.0035
Download: Armbian_22.02.0_Aml_s922x-reva_focal_5.15.14_2022.01.15.0007.img.gz
when install to emmc: armbian-install
select 45
when write to emmc:
armbian-install
select45
Understood. Currently prefer to run Linux on SD or USB Flash. Look forward your "Releases" with Aml_s922x-reva_bullseye_xxx.img.gz.
Hi @JFLim1 & @ophub
I have the same gtking_pro as @JFLim1 and so I tested the latest release Armbian_22.02.0_Aml_s922x-reva_focal_5.15.14_2022.01.15.0007.img.gz on usb pen but unfortunately the u-boot.ext (719kb) creates a boot-loop... For now only kernel 5.4.y starts without using no file in u-boot.ext..
Give feedback on the effect of this adjustment after testing
Give feedback on the effect of this adjustment after testing
Good news. After editing uEnv.txt to use "meson-g12b-gtking-pro-rev_a.dtb". It boot up successfully with the new u-boot.ext you have included. Thank you.
I noticed there is also a "meson-g12b-gtking-pro-rev_a-oc.dtb" in the /boot/dtb/amlogic folder. Is this the over clock rev_a dtb? What CPU speed it over clock to? A73 to 2208 MHz and A53 to 1900 MHz?
Next is to install a Desktop to check whether keyboard and mouse works. I have the hunch it will work. No "Failed ...Keymap..." warning during boot up.
Standard Edition: 1800/1908
Standard Edition-OC: 1992/1992
Version H: 1800/2208
H-OC version: 2016/2208
Rev A: 1800/1908
Rev A - OC version: 1992/1992
Non-pro version: 1800/1908
Now the Armbian_22.02.0_Aml_s922x-reva_focal_5.15.14.img.gz firmware has been configured according to the test results, and can be used directly without modification in the future.
Hi @ophub
Standard Edition: 1800/1908
Standard Edition-OC: 1992/1992
Version H: 1800/2208
H-OC version: 2016/2208
Rev A: 1800/1908
Rev A - OC version: 1992/1992
Non-pro version: 1800/1908
Thanks for the information. So for GT King Pro revision A device and Standard Edition, the maximum speed is 1992/1992.
After installing "ubuntu-desktop-minimal" and On boot up the maximum speed is 1.5GHz only.
Modified /etc/default/cpufrequtils:
ENABLE=true
MIN_SPEED=500000
MAX_SPEED=2208000
GOVERNOR=ondemand
By the way, "Reboot" does not work. Reboot will reboot into Android.
Need to shutdown and press power button to restart/boot up again.
After resart CPU Max Speed is 1.91GHz for A73 and 1.8GHz for A53 according to HTOP which match with Rev A specs as pointed out by you.
Can Revision A device use meson-g12b-gtking-pro-h.dtb
Now the Armbian_22.02.0_Aml_
s922x-reva_focal_5.15.14.img.gz firmware has been configured according to the test results, and can be used directly without modification in the future.
For your information Wifi does NOT seems to be available!
Use armbian-config to activate Bluetooth. Successful. Shutdown and Restart, Bluetooth is Activated but Wifi still NOT avaiable.
How do I activate WIFI on this image? Appreciate your guidance.
Use armbian-config to activate Bluetooth. Successful. Shutdown and Restart, Bluetooth is Activated but Wifi still NOT avaiable.
The way to overclock is editing uEnv.txt to use meson-g12b-gtking-pro-rev_a.dtb
The overclocked dtb is determined by the flippy test, it is not recommended that you modify it to a higher level, it may be unstable.
Great, you can use a usb or bluetooth keyboard and mouse.
Is this box wifi6? what chip? do you know what drives he needs?
The way to overclock is editing
uEnv.txtto usemeson-g12b-gtking-pro-rev_a.dtb
You mean "meson-g12b-gtking-pro-rev_a-oc.dtb"
Great, you can use a usb or bluetooth keyboard and mouse.
Yes.
Is this box wifi6? what chip? do you know what drives he needs?
Yes, GT King Pro comes 2.4GHz and 5GHz Wifi.
As far as I know the wifi drivers are:
brcmfmac4356-sdio.bin
brcmfmac4356-sdio.txt
and may be brcmfmac4356-sdio.clm_blob
These firmware are on this image /lib/firmware/brcm. So I am not sure why WIFI is NOT available.
May be I have to activate WIFI. How to activate WIFI on this image?
On other linux image with the usual mainline "meson-g12b-gtking-pro.dtb", Wifi and Bluetooth are available by default. And the CPU MAX Speed Available is 1992/1992 by default.
How to activate WIFI on this image?
armbian-config
armbian-config
Don't seems to find the option to Activate Wifi on armbian-config.
Not familiar with armbian-config as the image I have before WIFI, Ethernet, and Bluetooth all are available on boot up by default.
Would appreciate some guidances on how to use armbian-config to activate WIFI.
dmesg errors:
brcmfmac: brcmf_chip_recognition: chip backplane type 15 is not supported
[ 13.436166] brcmfmac: brcmf_sdio_probe_attach: brcmf_chip_attach failed!
[ 13.443608] brcmfmac: brcmf_sdio_probe: brcmf_sdio_probe_attach failed
[ 13.449675] brcmfmac: brcmf_ops_sdio_probe: F2 error, probe failed -19...
[ 13.458881] usbcore: registered new interface driver brcmfmac
27.223332] fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
[ 27.224652] fe.dai-link-1: ASoC: dpcm_fe_dai_prepare() failed (-22)
[ 27.231106] fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
[ 27.237911] fe.dai-link-1: ASoC: dpcm_fe_dai_prepare() failed (-22)
[ 27.244285] fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
[ 27.251078] fe.dai-link-1: ASoC: dpcm_fe_dai_prepare() failed (-22)
[ 27.257687] fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
[ 27.264272] fe.dai-link-1: ASoC: dpcm_fe_dai_prepare() failed (-22)
[ 27.270854] fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
[ 27.277470] fe.dai-link-1: ASoC: dpcm_fe_dai_prepare() failed (-22)
[ 27.284765] fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
[ 27.290671] fe.dai-link-1: ASoC: dpcm_fe_dai_prepare() failed (-22)
[ 27.297312] fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
[ 27.303858] fe.dai-link-1: ASoC: dpcm_fe_dai_prepare() failed (-22)
[ 27.310257] fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
[ 27.317056] fe.dai-link-1: ASoC: dpcm_fe_dai_prepare() failed (-22)
[ 27.323636] fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
[ 27.330247] fe.dai-link-1: ASoC: dpcm_fe_dai_prepare() failed (-22)
[ 27.336872] fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
[ 27.343459] fe.dai-link-1: ASoC: dpcm_fe_dai_prepare() failed (-22)
[ 27.351065] fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
[ 27.356656] fe.dai-link-1: ASoC: dpcm_fe_dai_prepare() failed (-22)
[ 27.363129] fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
[ 27.369844] fe.dai-link-1: ASoC: dpcm_fe_dai_prepare() failed (-22)
[ 27.376319] fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
[ 27.383034] fe.dai-link-1: ASoC: dpcm_fe_dai_prepare() failed (-22)
[ 27.389677] fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
[ 27.396230] fe.dai-link-1: ASoC: dpcm_fe_dai_prepare() failed (-22)
[ 27.402893] fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
[ 27.409427] fe.dai-link-1: ASoC: dpcm_fe_dai_prepare() failed (-22)
[ 27.416973] fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
[ 27.422620] fe.dai-link-1: ASoC: dpcm_fe_dai_prepare() failed (-22)
[ 27.429125] fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
[ 27.435817] fe.dai-link-1: ASoC: dpcm_fe_dai_prepare() failed (-22)
[ 27.442327] fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
[ 27.449010] fe.dai-link-1: ASoC: dpcm_fe_dai_prepare() failed (-22)
[ 27.455741] fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
[ 27.462227] fe.dai-link-1: ASoC: dpcm_fe_dai_prepare() failed (-22)
[ 27.468907] fe.dai-link-1: ASoC: no backend DAIs enabled for fe.dai-link-1
[ 27.475407] fe.dai-link-1: ASoC: dpcm_fe_dai_prepare() failed (-22)
[ 27.557194] hdmi-audio-codec hdmi-audio-codec.2.auto: Not able to map channels to speakers (-22)
[ 27.560374] hdmi-audio-codec hdmi-audio-codec.2.auto: ASoC: error at snd_soc_dai_hw_params on i2s-hifi: -22
[ 27.570026] axg-sound-card sound: ASoC: PRE_PMU: be.dai-link-8-playback event failed: -22
[ 27.590988] hdmi-audio-codec hdmi-audio-codec.2.auto: Not able to map channels to speakers (-22)
[ 27.594158] hdmi-audio-codec hdmi-audio-codec.2.auto: ASoC: error at snd_soc_dai_hw_params on i2s-hifi: -22
[ 27.603837] axg-sound-card sound: ASoC: PRE_PMU: be.dai-link-8-playback event failed: -22
If you don't see the option, it's not supported, use wired Internet.
rmmod brcmfmac
Hi @ophub,
If you don't see the option, it's not supported, use wired Internet.
WIFI issue is resolved by using the correct mainline "meson-g12b-gtking-pro.dtb".
An update. If you use /boot/dtb/amlogic/meson-g12b-gtking-pro.dtb, WIFI is Available! And the CPU Max Speed is 1.91/1.8 GHz..
"meson-g12b-gtking-pro-oc.dtb" does NOT Boot Up.
If I use "meson-g12b-gtking-pro.dtb" from linux-image-edge-meson64 or /lib/linux-image-current-meson64/amlogic/, WIFI is Available and CPU Max Speed default to 1.99/1.99 GHz.
Thank you for your great support and impressive work.
Congratulations you confirmed your dtb options.
Armbian_22.02.0_Aml_s922x_focal_5.15.14.img.gz The default configuration is your box.
Congratulations you confirmed your dtb options. Armbian_22.02.0_Aml_s922x_focal_5.15.14.img.gz The default configuration is your box.
It only work with the u-boot.ext from Armbian_22.02.0_Aml_s922x-reva_focal_5.15.14.img.gz but NOT the default u-boot-gtkingpro.bin.
Yes the default mainline meson-g12b-gtking-pro.dtb works. Thank you.
Lines 292 to 312 in 976e300
The boxes of several different variants of gtk-pro use the same u-boot-gtkingpro.bin, but the dtb file is different.
so, Armbian_22.02.0_Aml_s922x_focal_5.15.14.img.gz The default configuration is your box.
Hi @ophub
The boxes of several different variants of gtk-pro use the same u-boot-gtkingpro.bin, but the dtb file is different.
so, Armbian_22.02.0_Aml_s922x_focal_5.15.14.img.gz The default configuration is your box.
Might have confused you. I actually used this image.
From releases: https://github.com/ophub/amlogic-s9xxx-armbian/releases/tag/Armbian_Aml_focal_2022.01.15.0035
The u-boot.ext (files size: 735,459 bytes) consistently boot up.
Then the configuration used by your box is like this
meson-g12b-gtking-pro.dtb
u-boot-gtkingpro-rev-a.bin #copy to u-boot.ext
The configuration file is recorded in the /etc/ophub-release file. Since yours is customized, you need to correct it manually. This configuration is used when updating the kernel.
files size: 735,459 bytes, this is the u-boot file you share on https://disk.yandex.ru/d/ZMQW85B-P6QejA. Can you find an online link to your box? If this box is a rev-a model, he should use this meson-g12b-gtking-pro-rev_a.dtb for Rev A normally, the meson-g12b-gtking-pro.dtb for Rev B, is this another new variant?
Another question, is it possible to boot from the SD card with the SD card inserted in the gtk pro box by default? Unplug and boot from EMMC? No need for adb shell reboot update?
Hi @ophub
Can you
find an online link to your box?
The device Beeling GT King Pro was purchased in July or August 2020.
The serial number start with SA9HH with the normal WIFI.
WIFI Driver:
brcmfmac4356-sdio.bin
brcmfmac4356-sdio.txt
Bluetooth driver:
BCM4356A2.hcd
On Linux with legacy kernel 4.9.xxx I have to use the legacy kernel g12b_s922x_beelink_gt_king_rev_a.dtb from CoreElec if not mistaken.
On Linux with mainline kernel use meson-g12b-gtking-pro.dtb (for your information meson-g12b-ugoos-am6.dtb also work on my GT King Pro).
With meson-g12b-gtking-pro-rev_a.dtb and meson-g12b-gtking-pro-rev_a-oc.dtb, WIFI NOT available do know why.
With u-boot-gtkingpro.bin it boot up sometimes (low percentage of booting up) but not all the time. I have tried u-boot-gtkingpro.bin on Manjaro-Arm and the behave the same.
With so called u-boot-gtkingpro-rev-a.dtb boot up consistently with armbian meson64 kernel and others.
But there are some mainline kernels it will kernel panic randomly or during booting up process.
Another question, is it possible to boot from the SD card with the SD card inserted in the gtk pro box by default? Unplug and boot from EMMC? No need for
adb shell reboot update?
Yes it can boot up from SD Card on other image I have. But have not tried Armbian for s922X on SD Card yet. I guess it should work with u-boot-gtkingpro-rev-a.bin
Reboot works on SD Card.
But with USB Flash - Reboot work on some mainline kernels (example Armbian linux-image-current-meson64 5.10.y) but kernel 5.15.y does not. With USB Flash - normally Shutdown and Restart to replace Reboot.
The drawback of using chainloader u-boot.ext is as follows:
With chainloader u-boot-gtkingpro-rev-a.bin on USB Flash it will only boot up on GT KIng Pro with OTG Port an NO other USB Drive (Flash or HDD) attach to GT King Pro. USB Flash can also boot from the USB 3.0 Hub inserted into one of the GT King Pro USB 3.0 port and NO other USB Drive attached.
That is whey I am interested to check out kernel 5.4.y where it does not need the chainloader u-boot.ext but unfortunately keyboard and mouse are NOT recognized when a Desktop Environment is installed so not suitable for my use case. Do you have any idea how to resolve this issue?
The options for several kernels are basically the same, maybe 5.4 is suitable for old models of boxes, and your new model is suitable for 5.10 and above.
Hi @ophub and @JFLim1
I flashed with Balena-etcher on my sd-card the latest Bullseye release Armbian_22.02.0_Aml_s922x-reva_bullseye_5.15.14_2022.01.16.1511.img.gz
First after the flash the u-boot.ext present on the /BOOT partition seems to be taken from u-boot-gtking-pro.bin so I deleted this u-boot.ext and renamed it u-boot-gtking-pro-reva.bin to u-boot.ext
I use meson-g12b-gtking-pro.dtb taken from linux-image-current-meson64 repository present on /ROOTFS partition, copy and paste to /BOOT/dtb/amlogic
So unfortunately the boot doesn't work correctly with the image flashed on the SD card, I tried booting from my SD card with the USB inputs completely free and also partially or completely used but that didn't change anything..
https://imgur.com/a/it5hZhP
Re-download the newly packaged s922x-reva firmware, do not modify anything, test it
I did exactly the same thing again but this time flashed on a USB key, and I can start without problem by plugging into the USB OTG, I did a reboot by having connected the USB receiver of my dinovo keyboard-mouse and therefore it starts I can connect in SSH on the other hand I lose the HDMI signal on my tv at the time of kernel startup.. So I reuse the gtking-pro.dtb directly taken from the /BOOT partition and cool I recover the hdmi signal throughout boot process.
So the same image file Armbian_22.02.0_Aml_s922x-reva_bullseye_5.15.14_2022.01.16.1511.img.gz works very well on USB media but not at all on SD-card media..
Do not modify anything, test it
Okay so I flashed this new release on my sd-card, and just plug on my gtking-pro box => boot failed like as I post on imgur > https://imgur.com/a/it5hZhP
Is it possible to boot from usb?
If it cannot be started, rename /boot/u-boot-gtkingpro.bin to u-boot.ext under the test.
https://github.com/ophub/amlogic-s9xxx-armbian/releases/download/Armbian_Aml_bullseye_2022.01.16.1816/Armbian_22.02.0_Aml_s922x-reva_bullseye_5.15.14_2022.01.16.1745.img.gz
Flashed on usb key, without any modification, just connect to the USB OTG input with my keyboard / mouse receiver plugged into one of the other USB ports.
The startup takes place without any problem.
Just need a good clean of my usb key before..
Kernel 5.4.y boot fine with sd-card but without any u-boot.ext
Thanks for sharing your test results, the armbian system works fine on usb flash.
Congratulations, you found a solution, close this post, it's too long to display.
@ophub
I put a resistor between Rx and GND as stipulated in https://github.com/ophub/amlogic-s9xxx-openwrt/blob/main/router-config/README.md#109-if-you-cant-startup-after-using-the-mainline-u-boot
Suddenly I no longer have the freeze at startup when I use u-boot-gtking-pro.bin as u-boot.ext on the SD-card, however I lose the HDMI signal after starting the kernel and no connection SSH possible.. Misery, I was hoping to finally be able to start the 5.15.y kernel from my sd card, it's still not good..
I try meson-g12b-gtking-pro.dtb from /BOOT and also from /ROOTFS/usr/lib/linux-image-current-meson64/amlogic/ same result = black screen after starting kernel and no ssh connection
I also try meson-g12b-gtking-pro-rev_a.dtb but always same result..
If you have any idea ?
Thank again for all.
@ophub
I flashed Armbian_22.02.0_Aml_s922x_bullseye_5.15.15_2022.01.16.2138.img.gz on my sd-card, without any modification
This time I have signal on my TV but lot of error I/O
see https://imgur.com/a/F6eSJUq
I/O error, dev mmcblk1
The serial number of the sd card is mmcblk1, emmc is mmcblk2, and usb is sda
I asked flippy teacher to use on sd card. He said gtk does not support SD-UHS. The high speed sd standard requires a 3.3/1.8 variable IO voltage, but most boxes only have a fixed 3.3v.
Thank @ophub
It's strange because I've been using this same sd card for quite a while now, first with the firmware from @balbes150 (uses u-boot.ext the 719kb one) but also with your firmware kernel 5.4.y it starts very well from it but without using u-boot.ext.
Strange no?
This is not surprising, because balbes150 is a boutique product. has magical properties
This u-boot.ext can also be used in kernels below 5.10. If it works in a 5.4 kernel, it turns out that it can also work with a 5.10+ kernel. So I have it enabled by default. But many friends think it is unnecessary, so let's cancel it in the 5.4 kernel.
I tested and used u-boot-gtkingpro-rev-a.bin today. The first 10 seconds of booting, the screen was unresponsive and completely black. But it starts after 10 seconds.
Other boxes will start quickly.
According to many tests, this uboot can always be successfully started, but if it is replaced by something else, it cannot be started, which may be related to the model of the box.
Hi @ophub
I tested and used u-boot-gtkingpro-rev-a.bin today. The first 10 seconds of booting, the screen was unresponsive and completely black. But it starts after 10 seconds.
Based on feedback from other Manjaro-Arm users this u-boot-gkkingpro-rev-a.bin works on many amlogic tv boxes not just s922x tv boxes.
This is not surprising, because balbes150 is a boutique product. has magical properties
Hahaha..., With balbes150 image it can be used on SD Card without issue except when I update from 5.10.79-meson64 to 5.10.81-meson64. Once updated to 5.10.81-meson64 kernel, SD Card will NOT boot up, many I/O Error dev mmcblk1. If I install for example kernel 5.15.10-arm64 from another source, on SD Card same balbes150 image as a base. Interesting.
Thanks you for your support. Currently editing this message using Armbian_22.02.0_Aml_s922x_bullseye_5.15.15_2022.01.16.2138.img.gz on USB Flash on GT King Pro Revision A.
Hi @ophub
the screen was unresponsive and completely black. But it starts after 10 seconds.
Also experience "black screen" after boot up successful to desktop and within 5 minutes later "black screen".
Resolved this by renaming/disabling hdmi.rules in /etc/udev/rules.d/
Hi @ophub and @JFLim1
Just to share, now with my gtking-pro box (s/n:SA9HH..) and with the resistor placed in Rx and Gnd, I can use u-boot-gtking-pro as u-boot.ext it works Good..
So I flashed my SD card again, this time with the latest release Armbian_22.02.0_Aml_s922x_bullseye_5.4.172_2022.01.19.1857.img.gz
So I renamed u-boot-gtking-pro.bin to u-boot.ext and started booting from my SD card with all USB inputs used (hard drive, ssd, and remote control receiver..) everything worked..
So I did "armbian-tf -e" and launched "armbian-update 5.10.92 stable yes"
At the reboot I had no signal on my TV but I was able to connect in SSH, I went to rename hdmi.rules.bak in hdmi.rules
I launched a reboot and I had the signal again hdmi.. 5.10.92 works fine from my SD card..!
So I try the update to 5.15.15 and there is this famous problem..
@ophub I flashed Armbian_22.02.0_Aml_s922x_bullseye_5.15.15_2022.01.16.2138.img.gz on my sd-card, without any modification This time I have signal on my TV but lot of error I/O see https://imgur.com/a/F6eSJUq
Hi @MX10-AC2N
Just to share, now with my gtking-pro box (s/n:SA9HH..) and with the resistor placed in Rx and Gnd, I can use u-boot-gtking-pro as u-boot.ext it works Good..
Can you provide details on this modification. Resistor size extra. If there is a picture it will be great. One day when courage strike might try it. Hahaha...
Is there any benefit/difference in using u-boot-gtkingpro.bin versus u-boot-gtkingpro-rev-a.bin?
@ophub I flashed Armbian_22.02.0_Aml_s922x_bullseye_5.15.15_2022.01.16.2138.img.gz on my sd-card, without any modification This time I have signal on my TV but lot of error I/O see https://imgur.com/a/F6eSJUq
I had the same issue/errors (I/O Errors dev mmcblk1...) with balbes150 Armbian-Bullseye on SD Card when I upgrade 5.10.79-meson64 v21.08.4 to 5.10.81-meson64 v21.08.6. Could be due to the 3.3V vs 1.8V @ophub pointed out earlier.
Hi @JFLim1 @ophub
Can you provide details on this modification. Resistor size extra. If there is a picture it will be great. One day when courage strike might try it. Hahaha...
Indeed, I was not very reassured to make this addition of resistance but who tries nothing has nothing...
So I followed what Flippy gave as an indication https://github.com/ophub/amlogic-s9xxx-openwrt/blob/main/router-config/README.md#109-if-you-cant-startup-after-using-the-mainline-u-boot
So I needed a resistor with a value between 5Kohm and 10Kohm, so I looked through the pile of old resistors I had and I found one of a little over 8Kohm, so I soldered this between the Rx and GND terminals clearly visible on the board.
https://imgur.com/a/rm0KPhR
Is there any benefit/difference in using u-boot-gtkingpro.bin versus u-boot-gtkingpro-rev-a.bin?
I can't really say, I'm not sure what it changes but now I can use u-boot-gtking-pro.bin directly without freeze problem when booting it seems less hacky to me than using the u- boot-gtking-pro-rev_a.bin, which was not part of the Ophub builds before we told him about it.
I had the same issue/errors (I/O Errors dev mmcblk1...) with balbes150 Armbian-Bullseye on SD Card when I upgrade 5.10.79-meson64 v21.08.4 to 5.10.81-meson64 v21.08.6. Could be due to the 3.3V vs 1.8V @ophub pointed out earlier.
I don't really know, I have trouble understanding why we manage to start kernel 5.10.y and even as you remind me on the Beelink forum we managed to start https://oph.mdrjr.net/meveric/pool/main/l/linux-upstream/linux-image-5.15.10-arm64_5.15.10-20211220-odroid_arm64.deb starting from the Balbes image..
Suddenly I no longer have the impression that there is a problem in the system parameters but there for once I am completely floundering..
I don't really know, I have trouble understanding why we manage to start kernel 5.10.y and even as you remind me on the Beelink forum we managed to start https://oph.mdrjr.net/meveric/pool/main/l/linux-upstream/linux-image-5.15.10-arm64_5.15.10-20211220-odroid_arm64.deb starting from the Balbes image..
Hi @MX10-AC2N
Suddenly I no longer have the impression that there is a problem in the system parameters but there for once I am completely floundering..
I suspect the kernel config setting had something to do with it. kernel-5.10.79-meson64 NO issue on SD Card and 5.10.81-meson64 I/O Errors on SD Card. Meveric's kernel no issue for the time being.
Hi @ophub
Sorry to ping you like that, but I would like to know if you had been able to see my last messages since #72 (comment) and especially to know what you think of that ??
Thank again..
Edit: Here is the copy of "dmesg" when I boot kernel 5.10 from my sd-card => https://paste.yunohost.org/jarujumexa.vbs
@ophub @JFLim1
Salvation,
Well this time I have something new, so I start kernel 5.10 from my sd card I run the "armbian-config" command in the system menu I launch the switch to the "nightly" version, from the nightly sources I have access to linux-image-edge-arm64 which uses kernel 5.15.16
So I ran "apt install linux-image-edge-arm64"
This unmounted the /BOOT (Fat) partition and installed all new files in the /boot (ROOTFS) directory.
By copying the new 5.15.16-arm64 files from /boot (ROOTFS) to /BOOT (fat) which must necessarily be remounted..
I also had to redo the dtb folder in /BOOT
and that I rename uInitrd-5.15.16-arm64 to uInitrd and of course vmlinuz-5.15.16-arm64 to uImage in order to keep zImage which corresponds to kernel 5.10.93
Change in uEnv.txt to direct to uImage
Here is a copy of what I do and the reboot.. => https://paste.yunohost.org/ficuzaxuwo.scala
Now I wonder why linux-image-edge-arm64 works without problem while I couldn't successfully armbian-update to 5.15??
Hoping this can help you @ophub
Then I ran "apt update && apt upgrade"
armbian-bsp-cli-lepotato/bullseye 22.02.0-trunk.0016 arm64 [pouvant être mis à jour depuis : 22.02.0-trunk]
armbian-config/bullseye,bullseye 22.02.0-trunk.0004 all [pouvant être mis à jour depuis : 22.02.0-trunk]
armbian-firmware/bullseye,bullseye 22.02.0-trunk.1 all [pouvant être mis à jour depuis : 22.02.0-trunk]
armbian-zsh/bullseye,bullseye 22.02.0-trunk.0016 all [pouvant être mis à jour depuis : 22.02.0-trunk]
hostapd/bullseye 3:2.9-102~armbian20.05.2+1 arm64 [pouvant être mis à jour depuis : 3:2.9-102~armbian20.05.2+1]
linux-libc-dev/bullseye 22.02.0-trunk.0016 arm64 [pouvant être mis à jour depuis : 21.08.6]
Reboot is OK and now I have
Here is dmesg output => https://paste.yunohost.org/egicesucat.sql