Please make GT-king Pro compatible with armbian ..

JFL

Hi @gtkingpro.ac2n,

Not sure whether you faced this issue with Armbian latest updates v21.08.6.  I updated both Bullseye and Focal to latest version 21.08.6 (kernel 5.10.81-meson64) on SD Card.  The updates/upgrades was successful but when Reboot/Restart it does NoT start up anymore I/O Error (NOT Bad SD Card Issue as far as I can tell.)  I/O Error.  Effectively cannot boot anymore.  
Becareful if your are updating to latest Armbian v21.08.6.
The previous updates/upgrades to Armbian v21.08.4 with kernel 5.10.79-meson64 no issue.


Reburn balbes150 Armbian-Bullseye 20.10 with kernel 5.9.0 but Bullseye Upgrade issue.  Somehow cannot get pass Bullseye Updates.  Any ideas to resolve the Bullseye Updates issues.

1. <div>Get:1 http://deb.debian.org/debian bullseye/main arm64 libteamdctl0 arm64 1.31-1 [11.6 kB]</div><div>Err:1 http://deb.debian.org/debian bullseye/main arm64 libteamdctl0 arm64 1.31-1</div><div>  File has unexpected size (252 != 11616). Mirror sync in progress? [IP: 151.101.158.132 80]</div><div>  Hashes of expected file:</div><div>   - SHA256:4576fc2ec438507ccfb0dac02b0b5331ffb59f8593b1ef90df0fcc9c073a5d4b</div><div>   - MD5Sum:a301d4a5614a147eea4e897da51ff443 [weak]</div><div>   - Filesize:11616 [weak]</div><div>E: Failed to fetch http://deb.debian.org/debian/pool/main/libt/libteam/libteamdctl0_1.31-1_arm64.deb  File has unexpected size (252 != 11616). Mirror sync in progress? [IP: 151.101.158.132 80]</div><div>   Hashes of expected file:</div><div>    - SHA256:4576fc2ec438507ccfb0dac02b0b5331ffb59f8593b1ef90df0fcc9c073a5d4b</div><div>    - MD5Sum:a301d4a5614a147eea4e897da51ff443 [weak]</div><div>    - Filesize:11616 [weak]</div><div>E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?</div>

Copy the Code

gtkingpro.ac2n

Hi @JFL

Thanks for the warning, I've been working more with Coreelec for a few days now, so I haven't seen this update yet, I might freeze the system just to be on the safe side.
Anyway I am still under armbian buster and everything is working fine .. Initially I started from the image of Balbes150 and I had installed the .deb in addition .. maybe this can help you. .

https://users.armbian.com/balbes150/arm-64/deb/

JFL

gtkingpro.ac2n replied at 2021-11-27 02:26
Hi @JFL

Thanks for the warning, I've been working more with Coreelec for a few days now, so I haven ...

Hi @gtkingpro.ac2n,

The new latest linux-image-current-meson64 (5.10.81-meson64 v21.08.6) installation structure might have change that render it not compatible with bables150 base image.  I am able to reinstall balbes150 focal and upgraded it to linux-image-current-meson64 v21.08.4 (5.10.79-meson64) but unfortunately cannot get to Balbes150 Bullseye (testing/development) to update to the current stable Bullseye.

I suppose it is possible to start with Balbes150 Buster server image and dist upgrade to Bullseye.

gtkingpro.ac2n

Hi @JFL
I thought of something that had happened to me on my other box which used the station-m1 image of balbes150
During an update the DTB folder had disappeared and therefore I no longer had the dtb for gt-king pro, I had to replace the dtb file, maybe check that .. And also /boot/armbianEnv .txt
Regarding the upgrade from buster to bullseye I'm not sure what that can give.
Good luck..

JFL

gtkingpro.ac2n replied at 2021-11-27 18:02
Hi @JFL
I thought of something that had happened to me on my other box which used the station-m1 ima ...

Hi @gtkingpro.ac2n,

During an update the DTB folder had disappeared and therefore I no longer had the dtb for gt-king pro, I had to replace the dtb file, maybe check that .. And also /boot/armbianEnv .txt

This happen to the Balbes150 Armbian-Focal/Bullseye if I "sudo apt install linux-image-edge-meson64" all the newly created initrd.img, uInitrd, Image, etc will be in EXT4 /boot and not on the FAT32 /BOOT which I had earlier reported in this forum.  Took me a while to figure that out. You can only see that if you use another linux image to boot up.

This time around it cause error sthat render it not bootable and I made a stupid mistake by not backing up the Bullseye image or at least back-up the uInitrd.img-5.10.79-meson64 and Image-5.10.79-meson64 on the FAT32 /BOOT partition before upgrading to 5.10.81-meson64 v21.08.6.  The bottomline is the image is no longer bootable.  
Started a fresh installation of Balbes150 Armbian-Bullseye but Bullseye on Balbes150 image is very old and could not be upgraded to current stable Bullseye when I tried it two days ago.  This route is not an option for now.  

Regarding the upgrade from buster to bullseye I'm not sure what that can give.

This option is to see whether can circumvent the above issue, that is if I still want to continue with Balbes150 Armbian-Bullseye .  Start with Balbes150 Armbian-Buster server image (if not mistake there are no desktop image available) and from here upgrade to 5.10.79-meson64 and then dist upgrade to Bullseye.  If all goes well it should result to Armbian-Bullseye 5.10.79-meson64.

Edit: To resolve the Bullseye update error is "[backcolor=rgba(0, 0, 0, 0.075)]libteamdctl0_1.31-1_amd64.deb"  Need to resolve how to download and install this "[backcolor=rgba(0, 0, 0, 0.075)]libteamdctl0_1.31-1_amd64.deb" this file from Debian Bullseye.  Any suggestion how to rectify this.  

Tried "sudo apt update --fix-missing" does not resolve the issue.

E: Failed to fetch http://deb.debian.org/debian/poo ... l0_1.31-1_arm64.deb

Managed to download the file from [backcolor=rgba(0, 0, 0, 0.075)]http://ftp.br.debian.org/debian/pool/main/libt/libteam/libteamdctl0_1.31-1_arm64.deb.  Can I just use
[backcolor=rgba(0, 0, 0, 0.075)]"sudo dpkg -i  libteamdctl0_1.31-1_arm64.deb" ?


After installing the downloaded missing file with "sudo dpkg -i  libteamdctl0_1.31-1_arm64.deb", the Bullseye Upgrade was successfully.

gtkingpro.ac2n

Hi, this morning after using my sd card a lot with Coreelec on it I tried to restart on my Armbian sd card with my yunohost server .. But unable to boot on the system .. I do not understand much but from the beginning I had noticed that starting Coreelec blocked the reboot on my Armbian card, I forced the reboot with the "Reboot to Libreelec" application and it ended after 2 or 3 tries but this time I can't start my Armbian card anymore .. I haven't upgraded for a while so nothing to do with your @JFL concern ..
I am going to compare my 2 sd cards in order to do what is different but I am a little confused, if we have any ideas ..
I also specify that on the EMC I still have an android system from Beelink with unfortunately no OTA updates for a long time ..
the version is "galilei-userdebug 9 PPR1.180610.011 20210428 test-keys_20210428-0956"
Thank you..

JFL

gtkingpro.ac2n replied at 2021-12-10 20:00
Hi, this morning after using my sd card a lot with Coreelec on it I tried to restart on my Armbian s ...

Once a while I do use CoreElec (now upgraded to v9.2.8 if not mistaken) and Beelink Firmware 918P0.  So far no issue with booting into Linux.  But the last I use CoreElec is a month ago.

Did you try to boot up into Android and then switch to Linux by press/hold "Power" switch?  Sometimes this help resolve the issue.

gtkingpro.ac2n

Hi @JFL and thank you for your answer, I forgot this shortcut with the long press on the "power" button of the gt-king pro, but same result ..
So I connected my sd card to my pc, I use "Linux File Systems for Windows" (This is very useful to me ..), and I could therefore see that my /boot folder is completely empty (normal that this does not start anymore ..)
I'm not sure what happened, but how do I fix it because apart from the empty / boot folder the rest of my sd card tree looks healthy.
If I put everything back in my  /boot folder it should be able to restart, well I hope ..
Edit: I check /var/cache/apt/archives I can see linux-image-current-meson64_21.08.4_arm64.deb I think this is the last linux image I was using ..
Edit 2 : @JFL Have you already tried https://github.com/ophub/amlogic-s9xxx-armbian

JFL

Hi @gtkingpro.ac2n,

If I put everything back in my  /boot folder it should be able to restart, well I hope ..

If you have a backup of the /boot parition and copy it over it should work. I have tried that before that is provided the all else are intact.

Edit: I check /var/cache/apt/archives I can see linux-image-current-meson64_21.08.4_arm64.deb I think this is the last linux image I was using ..

From what I tried this version works with balbes150 Armbian image.  linux-image-current-meson64 v21.08.6 (5.10.81-meson64) renders the SD Card no longer able to boot up.

Edit 2 : @JFL Have you already tried https://github.com/ophub/amlogic-s9xxx-armbian

No. I have not tried this or knew it existed.  Thanks for sharing.  Did you try it?  It looks like has the latest kernel too.  Currently do not have a spare disk to try this image yet.  If you have to reburn the Armbian image, this might be a good time to try it out. Do share your experience if you try this image.

It will be great if this Armbian image works on GT King Pro as the Armbian seems to changing their kernel build that seems to render Balbes150 Armbian 20.10 base image not bootable.  Not sure it was just the linux-image-current-meson64 v21.08.6 or the future build too.

JFL

Hi @gtkingpro.ac2n,,

Edit 2 : @JFL Have you already tried https://github.com/ophub/amlogic-s9xxx-armbian

There are two versions Armbian_21.11.0_Aml_s922x-n2_focal_5.4.164_2021.12.13.1035.img.gz and Armbian_21.11.0_Aml_s922x_focal_5.10.84_2021.12.13.1029.img.gz.  Which will be better for is for GT King pro? Without the "n2"?