Can't update to 5.15.15 but can work with linux-image-edge-arm64 (5.15.16) (on SD-Card)

[MX10-AC2N]

Hi @ophub I'm opening a new issue because I'm not sure you've seen my last posts in https://github.com/ophub/amlogic-s9xxx-armbian/issues/72#issuecomment-1016577181 So long story short, I managed to install and boot linux-image-edge-arm64 (kernel 5.15.16) from my sd card and so I wonder why "armbian-update 5.15.15" is giving me a problem during boot, there is a problem in the config since linux-image-edge-arm64 works well.. Hope this can help, I can still test if needed.. Thanks again..

[ophub]

In order to test the firmware of gtk pro, I just bought this gt-king pro box(SN: 6B9HH2D...) last week. I just saw your feedback that 5.15.16 cannot be used, so I upgraded it (I used 5.15.15 before). Currently I'm running on USB, the box has been powered on for a week, and I haven't found any problems with it so far.

[ophub]

I downloaded the firmware generated today, tested it on TF and it works fine. This is the HG680P box that has just been flashed with new firmware.

[MX10-AC2N]

I could boot 5.15.15 from usb without problem but from sd card it doesn't work.. but with linux-image-edge-arm64 it works.. Since I have a resistor in place between Rx and GND I can now use u-boot-gtking-pro.bin as u-boot.ext Do you think I can try an "armbian-update 5.15.16" ?

[ophub]

I've been using armbian-update for kernel updates, never installed linux-image-edge-arm64 via apt.

That resistor is no longer needed now. It was when the 5.10 kernel first came out. Since the u-boot of individual boxes would interfere, it was necessary to add a resistor. This matter has been solved by the new u-boot reloading solution half a year ago. Since the problem of resistance basically does not exist, I will revise the article, and everyone in the province thinks it is necessary.

Adding resistors is harmless and helpful, but is no longer an option.

The 5.15.16 kernel, I have no problem upgrading, and the new firmware can also be used normally. But I'm not sure if there will be a problem after you install other kernels with apt. You find a new sd card for testing, don't delay the officially used system.

[ophub]

I tested it on the s905d and s905x3 boxes again, and there is no problem. This is the system installed in the emmc.

[ophub]

You can upgrade the local kernel update script, the latest update script can directly input armbian-update to find the latest kernel update.

wget -O /usr/sbin/armbian-update git.io/armbian-update

Through the test of multiple boxes, whether it is used in emmc or usb and tf card, whether it is to upgrade the kernel to 5.15.16 or directly install the firmware of today's newly generated 5.15.16 kernel, it can be used normally.

[MX10-AC2N]

I'm not sure I understand correctly, in my case adding the resistor finally allows you to be able to use u-boot-gtking-pro.bin as u-boot.ext without there being a freeze at the start of the boot, without this resistance impossible to use u-boot-gtking-pro.bin and unfortunately the u-boot-gtking-pro-rev_a.bin only works if I boot from a USB medium, for my part j I need to install the system on SD Card in order to keep my USB inputs (used by 2 HDD, 1 SSD and the remote control receiver) So for the moment this addition of resistance is very useful to me.. I still specify that I kept an Android system on my Emmc (this probably explains why the addition of the resistor is useful to me..) would it be possible to create a command allowing the reboot to android as we can have under Coreelec. I will try an update to 5.15.16 to see if it works. Thank you again for your investment in this project. You're great..

[MX10-AC2N]

root@armbian:~# wget -O /usr/sbin/armbian-update git.io/armbian-update
--2022-01-22 10:56:21--  http://git.io/armbian-update
Résolution de git.io (git.io)… 52.204.242.176, 18.205.36.100, 54.157.58.70, ...
Connexion à git.io (git.io)|52.204.242.176|:80… connecté.
requête HTTP transmise, en attente de la réponse… 301 Moved Permanently
Emplacement : https://git.io/armbian-update [suivant]
--2022-01-22 10:56:21--  https://git.io/armbian-update
Connexion à git.io (git.io)|52.204.242.176|:443… connecté.
requête HTTP transmise, en attente de la réponse… 302 Found
Emplacement : https://raw.githubusercontent.com/ophub/amlogic-s9xxx-armbian/main/build-armbian/common-files/files/usr/sbin/armbian-update [suivant]
--2022-01-22 10:56:22--  https://raw.githubusercontent.com/ophub/amlogic-s9xxx-armbian/main/build-armbian/common-files/files/usr/sbin/armbian-update
Résolution de raw.githubusercontent.com (raw.githubusercontent.com)… 185.199.108.133, 185.199.109.133, 185.199.110.133, ...
Connexion à raw.githubusercontent.com (raw.githubusercontent.com)|185.199.108.133|:443… connecté.
requête HTTP transmise, en attente de la réponse… 200 OK
Taille : 16608 (16K) [text/plain]
Sauvegarde en : « /usr/sbin/armbian-update »

/usr/sbin/armbian-update     100%[=============================================>]  16,22K  --.-KB/s    ds 0,007s

2022-01-22 10:56:23 (2,37 MB/s) — « /usr/sbin/armbian-update » sauvegardé [16608/16608]

root@armbian:~# armbian-update
Ready to update, please wait...
current version: 5.15.16, Latest version: 5.15.16
Already the latest version, no need to update.

And damn I'm going to have to re-flash my sd-card, isn't there a way to force armbian-update?

[ophub]

Can't force update

When the box was just bought back last week, I made a ddbr backup, and then wrote emmc. I used u-boot-gtking-pro-rev_a.bin, and did not write the mainline u-boot, after writing emmc It works normally. I used it for a few days, and then ddbr went back to the Android system. Now I use it with the usb plugged into the usb port of the OTG.

I also tested u-boot-gtkingpro.bin, and also tested writing the mainline u-boot to emmc. I tried various combinations of several u-boots for s922x in the warehouse and flashed them into bricks. But in the end, there is only one solution that my gt-king pro box(SN: 6B9HH2D...) can write to emmc, that is, do not use the mainline u-boot, use u-boot-gtking-pro-rev_a.bin as the boot, and use the meson-g12b-gtking-pro.dtb file .

The two points shown in the figure below are the shorting points of the recovery android tv system.

[MX10-AC2N]

Well we can say that Beelink has added a large heat sink, on my GT-King Pro card there is none.. We don't have the same SBC at all. => https://imgur.com/a/rm0KPhR Either I did armbian-update 5.10.93 like that I went back to kernel 5.10.93, the reboot was successful and I therefore launched armbian-update 5.15.16 and again I have this problem I/O error, dev mmcblk1 => https://imgur.com/a/F6eSJUq There must be some setting wrong with flippy kernel 5.15 since linux-image-edge-arm64 kernel 5.15.16 boots fine from the same SD card without me changing the u-boot.ext (u- boot-gtking-pro.bin)

[ophub]

Then you have been using the 5.10 kernel. After 93 revisions, it is very stable. 5.15 kernel and so on. In the use of openwrt, 5.10 and 5.4 are also the most stable. I thought about it for a long time, and only changed the document to 5.15 last night. I just decided to use 5.15 as the default kernel, which seems to be hasty.

[MX10-AC2N]

I'm really not an expert with this but if my feedback can help you I would be delighted. It's a fair return for everything you do. I take this opportunity to add a little thing, would it be possible to keep a 5.10.y backup during the update to 5.15.y so as to be able to return to 5.10.y if there was a problem with 5.15.y because for the moment when I do the update the files relating to 5.10.y are deleted from /BOOT and therefore I have to re-flash my sd-card from scratch.. thank you very much again

[ophub]

I think if updating the kernel fails, what is the simple and easy to use fallback recovery method

[MX10-AC2N]

I just managed to boot kernel 5.15.16 only once from my SD card, I managed to boot just using gtking-pro.dtb from linux-image-edge-arm64 successful boot but loss of hdmi signal just after starting the kernel, I was able to connect in SSH unfortunately the reboot did not work. And despite several attempts I can no longer have SSH access. It seems that the problem is related to the dtb file.. Here is a copy of gtking-pro.dtb taken from linux-image-edge-arm64 maybe that will help find the problem meson-g12b-gtking-pro-arm64.zip .

[ophub]

There are small version differences in the box, you still use the 5.10 kernel, it is stable

[JFLim1]

The two points shown in the figure below are the shorting points of the recovery android tv system.

A large heatsink in addition to full aluminium casing. Good. Is your model come with Wifi 6 and Wifi 6 driver available for mainline kernel?

[MX10-AC2N]

Is your model come with Wifi 6 and Wifi 6 driver available for mainline kernel? Hi @ophub No, unfortunately my GTKing-pro is not Wifi6 it is one of the first versions of the SBC with an RS232 port which one wonders what it could be used for... For Wifi6 drivers it seems to me that @pulpoff must know, he uploaded https://vp5.net/king/BCM4362A2.hcd https://4pda.to/forum/index.php?showtopic=948258&view=findpost&p=111152414

Another thing, I went back to kernel 5.10.93 but when I do the reboot command the box restarts well but loses the hdmi signal at the start of the kernel while with the poweroff command and a restart by pressing the button on the box works well without losing the hdmi signal.. are there a few things to modify in the reboot command? have a nice day..