Please make GT-king Pro compatible with armbian ..

darkstar

JFL replied at 2021-12-27 15:35
Good to know ophub's firmware can boot quite reliably on GT King Pro with kernel >5.10.

Wondered  ...

Boot loader works like bios, it is booting device and it is parsing rest-device properties etc. to the operating system.
There is nothing wrong to use it or not, second stage boot loader is designed to solve incompatibility issues.

If your device boot successfully it does not matter how it booted (bios,efi,uefi, grub, lilo u-boot). Because kernel takes control after boot process.

gtkingpro.ac2n

Hi @JFL and darkstar
Hope you had a good Christmas ..
Nice to share what I'm testing, linux-image-edge-arm64 seems to work, but I had some issues with the /boot partion in fat, I'm not very sure anymore and since I had several trials between meson64, meveric , that maybe compromised things a bit, so I'll try again from scratch.
I am happy to learn that the release> 5.10 from ophub starts easily on your @darkstar box. Can you tell us what serial number, and if you still have android on the mmc?
Can't wait for the next @darkstar build...

gtkingpro.ac2n

Come on it's good,
we can start linux-image-edge-arm64 but there is this problem with the / boot partition
So I reflashed Armbian_20.10_Arm-64_bullseye_current_5.9.0.img on my sd card I used u-boot.ext you linked to me previously and manjaro's dtb file.
First boot OK with ssh access via putty (on the other hand no hdmi signal .. either ..) I continue with "armbian-config" to switch to nightly mode then return to the console.
Here is a copy of what I had to do > https://paste.yunohost.org/nokegorepo.rb
then edit extlinux.conf for pointing  LINUX /arm64_Image

How can solve this problem with /boot partition ?



and for use the 5.15.11 dtb..

1. root@arm-64:/lib/linux-image-edge-arm64/amlogic# cp meson-g12b-gtking-pro.dtb /boot/dtb/amlogic/meson-g12b-gtking-pro_5.15.11.dtb

Copy the Code

gtkingpro.ac2n

After a reboot I do "apt update" and "apt upgrade"
357 packages a big upgrade with some asking task (always says Yes)
here is the long log. > https://paste.yunohost.org/gefojevota.erl

Reboot is OK and here is the dmesg log >  https://paste.yunohost.org/akutimihab.vbs
Now all packages is up to date.. Nice..

JFL

gtkingpro.ac2n replied at 2021-12-28 00:29
After a reboot I do "apt update" and "apt upgrade"
357 packages a big upgrade with some asking task  ...

Yes, glad you are able to install linux-image-edge-meson64 on balbes Armbian-Bullseye.   Is it running stable with the new 5.15.11-meson64 trunk#22.02?

Figured out in http://forum.bee-link.com/forum. ... p;extra=&page=6 that whenever you install the newer linux-image-edge-meson64 kernel using apt install or dpkg -i, the new image will only be installed/written on the rootfs /boot and NOT on the /BOOT partition where the balbes Armbian boot from.  The /BOOT partition never get updated.

Need to copy from the rootfs /boot newly created files/images related to the linux-image-edge-meson64 over to /BOOT  partition in order to boot with the edge-meson64.

The difference is that you know your way around how to mount rootfs to circumvent the issue.  I am not so well verse with linux commands so I use another linux image to copy these files over.

But now I know how to mount the rootfs /boot.  Will try it out when the needs arise. Thank you.

JFL

darkstar replied at 2021-12-27 17:44
Boot loader works like bios, it is booting device and it is parsing rest-device properties etc. to ...

Hi @darkstar,
Thanks for the taking the time to clarify.

Per my understanding, the current chainloader u-boot.ext if the boot image is on USB Flash, it can only boot from OTG USB Port only and with NO other USB Stick or HDD connected.  If Boot image is on SD Card with the chainloader it doesn't have this limitation.  

Was hoping without the chainloader, USB Flash image might be able to boot from any other GT King Pro USB Ports.  Not sure whether this is true. That is the reason I enquired about booting without the chainloader.

And if kernel 5.4 works with Panfrost (with good performance) on our device like kernel >5.10 then we have another kernel option.

gtkingpro.ac2n

Hi @JFL and @darkstar

Is it running stable with the new 5.15.11-arm64 trunk#22.02?

Yes, it's running stable. I launch the script for yunohost installation without any issues.
Only strange thing I am still under the armbian version 20.10? while there should have marked armbian 22.02.
probably related to the fact that I use the u-boot.ext of the armbian version 20.10? from balbes ...
I flashed on usb key the last release of Ophub which is also in armbian 22.02 and kernel 5.10.88 but I still have this problem of freeze at startup, and even by forcing a restart it always freezes (I have SlimBoxTV present on my Emmc with already 2 OTA updates since I did the install)
  @darkstar can you tell us if you still have Android on the Emmc and also where the serial number begins under your GtKing_Pro

JFL

gtkingpro.ac2n replied at 2021-12-27 23:41
Come on it's good,
we can start linux-image-edge-arm64 but there is this problem with the / boot par ...

Hi @gtkingpro.ac2n,

How can solve this problem with /boot partition ?

Not sure whether this is a good suggestion for a temporary solution.  Write a script of what you did to copy the rootfs /boot newly created files related to the new linux-image-edge-meson64 to FAT32 /BOOT.

I flashed on usb key the last release of Ophub which is also in armbian 22.02 and kernel 5.10.88 but I still have this problem of freeze at startup, and even by forcing a restart it always freezes (I have SlimBoxTV present on my Emmc with already 2 OTA updates since I did the install)

Looks like Ophub Armbian for Amlogic S9xxx does not support GT King Pro Rev A well.  Did you use the dtb from the image itself?

darkstar

gtkingpro.ac2n replied at 2021-12-29 16:26
Hi @JFL and @darkstar

Yes, it's running stable. I launch the script for yunohost installation witho ...

I tested on Wifi6 version, will check it on normal version and GTKing.
At first boot is stuck after second or third boot it worked normally.

Ophubs fstab file is little bit weird you need to modify-change /etc/fstab file to mount boot partition properly.

root@HP-250-G7:~# cat /mnt/loop1/etc/fstab  
/dev/root       /       ext4    defaults,noatime,errors=remount-ro  0 1
LABEL=BOOT      /boot   vfat    defaults                            0 0
tmpfs           /tmp    tmpfs   defaults,nosuid                     0 0

I will modify and share new fstab on weekend.

gtkingpro.ac2n

Happy new year..  
Truth, Love, and Unity