GT King Pro-Ubuntu 21.10 Impish Indri Firmware with Panfrost-5.14.15 Kernel

JFL

darkstar replied at 2022-02-14 22:05
Yesterday I booted this firmware without u-boot.ext from usb drive, but somehow it did not boot from ...

Hi @darkstar,

Looking forward to your new build.

JFL

darkstar replied at 2022-02-14 22:05
Yesterday I booted this firmware without u-boot.ext from usb drive, but somehow it did not boot from ...

Hi @darkstar,

So far, from my testing on SD Card with kernels 5.15.y and 5.16.y, so far the kernel built by @meveric (example 5.15.10-arm64, 5.16.0-arm64 and 5.16.4-arm64) can boot up on SD Card.

According to @gtkingpor.ac2n kernel 5.10.y-flippy (from Armbian for S9xxx ophub) also can boot from SD Card too.

The kernels that fails to boot from SD Card include linux-image-current-meson64 >= 5.10.81-meson64, linux-khadas-5.16.2-2, kernel by 5.15.y-flippy (from Armbian for S9xxx ophub) and I suspect also 5.16.y-flippy but not tested.

gtkingpro.ac2n

JFL replied at 2022-02-19 07:49
Hi @darkstar,

So far, from my testing on SD Card with kernels 5.15.y and 5.16.y, so far the kernel ...

Can boot linux-image-edge-arm64 5.15.y and 5.16.y and a new try that also boot with linux-image-arm64 5.15.y always on my sd-card (A2 witch is maybe problematic)

JFL

gtkingpro.ac2n replied at 2022-02-22 00:45
Can boot linux-image-edge-arm64 5.15.y and 5.16.y and a new try that also boot with linux-image- ...

Hi @gtkingpro.ac2n,

Thanks for sharing the info.  Good to know linux-image-edge-arm64 5.15.y and 5.16.7 works and also the Debian maintained kernel linux-image-arm64 5.15.y can boot from SD Card.

By the way, were you able to get sound and wifi working using the Debian maintained kernel linux-image-arm64 5.15?  

Long time ago I tried Debian mainteined kernel 5.10 (March 2021 timeframe) but then sound, wifi and bluetooth does NOT work on GT King Pro.

JFL

gtkingpro.ac2n replied at 2022-02-22 00:45
Can boot linux-image-edge-arm64 5.15.y and 5.16.y and a new try that also boot with linux-image- ...

Hi @gtkingpro.ac2n,,

I read on your https://github.com/ophub/amlogic-s9xxx-armbian/issues/116 you mentioned:

On the other hand, if linux-image-arm64 (debian) is installed, the installation proceeds correctly on the FAT /BOOT partition, only the symbolic link problem is reported.

What is "only the symbolic link problem is reported" ?

gtkingpro.ac2n

JFL replied at 2022-02-23 10:00
Hi @gtkingpro.ac2n,,

I read on your https://github.com/ophub/amlogic-s9xxx-armbian/issues/116 you ...

Hi @JFL
when updating to linux-image-arm64 there is no unmounting of the /BOOT (fat) partition and no update of boot script (boot.scr) unlike the update to linux-image-edge-arm64 kernel wich causes me some problems..
There is however the creation of symlink between uInitrd and zImage towards the image files used. In our case with a partition under FAT instead of making a symlink, there should be just a copy of file renamed as it should be. But I don't know how to set it up, so you have to do it manually.
It is also necessary to copy the meson-g12b-gtking-pro.dtb in the folder /boot/dtb/amlogic taken in /usr/lib/linux-image-5.15.0-0.bpo.3-arm64/amlogic/ (for for my part I renamed it with the addition-arm64, to test the dtb taken from the ophub release but it does not work. we can keep the official name meson-g12b-gtking-pro.dtb)
as a reminder I added a resistor and I therefore use u-boot.ext from u-boot-gtkingpro.bin (and not the rev_a version)

JFL

gtkingpro.ac2n replied at 2022-02-23 18:32
Hi @JFL
when updating to linux-image-arm64 there is no unmounting of the /BOOT (fat) partition and  ...

Hi @gtkingpro.ac2n,

when updating to linux-image-arm64 there is no unmounting of the /BOOT (fat) partition and no update of boot script (boot.scr)

Same experience the last time I tried in March 2021 timeframe. Good.  Just wonder sound and wifi working wit the latest Debian linux-image-arm64.

unlike the update to linux-image-edge-arm64 kernel wich causes me some problems..

Armbian is changing/updating their build (kernel) and from what I read, Armbian is making their new builds more and more difficult to update for non-supported boards/hardware.

There is however the creation of symlink between uInitrd and zImage towards the image files used

I am not sure I understand you correctly.  But example, balbes150 original image (20.10 kernel 5.9.0) with linux-image-current-arm-64 the boot requirement is uInitrd and zImage.

linux-image-current-meson64 generate uInitrd and Image for booting.

another example current Manjaro-Arm for GT King Pro using bootscript method to boot use uInitrd and uImage for booting (u-boot.ext is NOT required).

I used the same manual method to rename newly generated initrd, uInitrd, Image, zImage or vmlinuz to match the extlinux.conf or uEnv.ini.

gtkingpro.ac2n

With armbian from ophub as a starting release, I use u-boot.ext and I configure uEnv.txt to launch the img file that I rename as I want Image, uImage, zImage whatever since I create it and I 'indicates in uEnv.txt
when installing linux-image-arm64 the fat /BOOT partition is not unmounted the new image files are directly copied to the correct partition but there remains this symbolic link created at the end "uInitrd" "Image" .. Is there a way to specify to make a copy for uInitrd and Image rather than attempting a symbolic link (fat does not allow symbolic links) and also for the .dtb file where I still have to manually intervene ( /usr/lib/linux-image-arm64/amlogic to /boot/dtb/amlogic)
I also specify that I start from an A2 sd card and that I have all the USB inputs used (1SSD, 2HDD, and the remote control "for when I start Android")

pspablo

Hello.  After installing Ubuntu from both SD card and USB stick, Beelink GT_King does not start up.  There are "timeout" errors. Maybe I have to change something after installation, eg dtb?  My device is GT King.  Please help, I'm a newbie.  Thanks in advance.

JFL

pspablo replied at 2022-03-31 22:06
Hello.  After installing Ubuntu from both SD card and USB stick, Beelink GT_King does not start up.  ...

This firmware by default uses the meson-g12b-gtking-pro.dtb.  Edit uEnv.ini:

FDT=/dtb/amlogic/meson-g12b-gtking.dtb

See whether it will boot.