Posts by darkstar

Quote from chewitt

darkstar Chainloading mainline u-boot is not a "solution" it is a "workaround" and the root cause of the problem is still not known. AFAIK the .ext file should not need to be recompiled for SD card boot because it is the unsigned u-boot.bin binary with no embedded device-tree, and thus to run it you've already booted (via vendor u-boot) past the point where SD/eMMC selection is in play. As there is no device-tree embedded the file should be usable on more than one device, but is probably SoC generation specific, e.g. GXBB, GXL/GXM, G12A/SM1, G12B might need different files. I'm personally not too interested in using this approach although the current LE "box" image will see/use the file if present. NB: I've also upstreamed support for GT-King/Pro allowing people to run mainline u-boot from eMMC on these devices, particularly for Armbian where people are more keen/willing/able to do that. Those patches will be in-tree once the merge window for U-Boot 2021.04 opens, and they are included in my 2021.01 fork. I'm still hopeful that one of the kernel maintainers we shipped hardware too will be able to pinpoint the real problem and solution.

Thank you for your reply, we can use it as a workaround till we get a real solution that you mentioned.

Quote from balbes150

Show the link to the original source, I want to look at the "author".

I don't know the sources link. I guessed that it is compiled by chewit or you and just wanted to ask.

Quote from chewitt

The Beelink devs have no more/less of a clue what the issue could be as anyone else. I've looked at their boot sources (with git history) and there's no smoking gun; the sources have the same Amlogic BSP baseline that Khadas and Hardkernel use with fairly minimal hacking to account for the normal things that are different between board vendors. I've also had them ship samples to people with the skills to hopefully figure the issue out, but those folks are full-time developers and we're asking them to investigate our weird problem for $free, so we'll have to be patient until they have some time to spare. I see "Beelink doesn't care" as a wrong statement. If they didn't care they wouldn't courier $240 products to people, or provide schematics and sources to developers who haven't signed an NDA, to help customers run an OS they don't ship and don't support.

Dear chewitt ,

@JFL from Beelink's forum found a solution to kernel panic of mainline version.

With u-boot.ext file linked below gtking pro boots and runs properly from usb on otg port.

I would like to inform you, but I think you already knew it.

Did you compiled this u-boot.ext, if yes how can we re-compile it for sdcard boot?

for_linux-vim-5101.tar — Yandex.Disk

Kind regards,

Quote from chewitt

It's an image for emmc install (overwriting factory u-boot) not an image for SD/USB boot.

Normally I'd suggest using the "box" image to boot, then erase the emmc or use "emmctool" to write the image to emmc storage. However there's an issue when booting from vendor u-boot and the mainline kernel under high I/O load (e.g. when writing the image) where the kernel deadlocks and this can leave you with broken u-boot. It's not impossible to recover from, but needs Amlogic burning tool or UART cables (the UART port is on the rear of the pro box) and a lot of faffing about to kill vendor u-boot to force boot from SD card. I've not tested it, but a possible workaround is booting from CE (which doesn't have the lockup issue) and using 'dd' to write the image to emmc.

In general, anything with vendor u-boot should use the box image. I've mostly built the -beelink image to help the Armbian/Manjaro folks boot/run on the box using mainline u-boot to avoid the deadlock problem. LE still has the same issue, but since we are ultra-lightweight seem to mostly-avoid the problem. I had a sample shipped to one of the kernel maintainers to see if they can figure the issue out, it's beyond me, but it's a busy time of year so nothing was looked at yet. The same issue exists on all the Beelink S922X boxes.

Thank you for kind reply, but I dont want to brake u-boot.

I don't understand why Beelink doesn't care about this problem, they are aware of it.

Dear chewitt I tried your LibreELEC-AMLGX.arm-9.80.7-beelink-s922x.img.gz image on my gt-king-pro but no luck, it did not boot.

I tried to change dtb setting to pro and again didn't boot.

Is there anything special thing I must do to run it?

Quote from chewitt

amlogic-boot-fip/gtking at beelink · chewitt/amlogic-boot-fip · GitHub

^ These are the FIP files that I am using, which can be used to sign a mainline u-boot image. I built mainline u-boot using the VIM3 defconfig and the signing recipe from the N2. You can use the same process to write u-boot to eMMC as any other Amlogic device.

Dear chewitt ,

Please forgive me for asking too much questions,

I couldn't find bl33.bin file in your beelink/fip branch, am I missing something or should I build it from u-boot mainline repo?

Thanks again,

Quote from chewitt

amlogic-boot-fip/gtking at beelink · chewitt/amlogic-boot-fip · GitHub

^ These are the FIP files that I am using, which can be used to sign a mainline u-boot image. I built mainline u-boot using the VIM3 defconfig and the signing recipe from the N2. You can use the same process to write u-boot to eMMC as any other Amlogic device.

Thanks a lot, I appreciate your work .

Regards,

Quote from chewitt

I haven't figured out the root cause and I don't have the code-level skills needed to, but I was able to build and boot mainline u-boot on a GT-King Pro and this works without the lock-ups; which points the finger at something in the vendor u-boot code; which we have incomplete sources and no git history for (to understand how Beelink modified it). The GT-King Pro also has an RS232 port on the rear of the box which makes the UART based processs of disrupting then erasing vendor u-boot less complex, but this is a million miles from a "solution" for users - it's fiddly as hell and GT-King (non-Pro) and GS-King-X need dismantling and soldering of UART pins to their boards to get equivalent access.

Dear chewitt

Could you share your mainline u-boot image and information how you run it?

We can try it too on Debian & Ubuntu images with mainline kernel.

It will help us to release Debian & Ubuntu images with mainline kernel.

Thanks a lot,

Kind Regards,

Quote from spikerguy

This is confirmed to be a android BSP Uboot issue and not linux kernel issue.

We should hopefully have Mainline uboot images to test which should not cause any kernel panic anymore, but for this to work user's will have to erase android bsp uboot from the emmc.

Finally chewitt was able to figure out the issue. We will have a working linux OS on GT King & Pro and GS King X

Goog news, thanks lets see how it will work.

Quote from phlp11

Got a new Ugoos AM6 box;

tried the 20.10 aarch64 g12; kodi segfaults;

I am able to start the box using the aarch64 g12 build from 12.10. There I get occasional system freezes after a period of time (depending on my interaction with the UI).

On both releases I get buggy u-boot.ext HDMI attempts (vertical random color lines) and no kernel issues in dmesg.

Anyone else have these issues or I'm doing something wrong?

Display More

Same here with GT King Pro, mainline kernel is not stable for GT King Pro too.

Quote from phlp11

Recently I found out that HEVC does not work (I'm not 100% sure when did it stop, or was it working previously at all). The following is observable on

• LibreELEC-ARMv8.aarch64-9.80-devel-20201006082248-fe4b097-amlgx.img
• LibreELEC-ARMv8.aarch64-9.80-devel-20200923122613-36bc7e3-amlgx.img

using s905w HW:

Code

2020-10-06 21:35:14.952 T:1671     INFO <general>: Creating InputStream
2020-10-06 21:35:14.976 T:1671     INFO <general>: Creating Demuxer
2020-10-06 21:35:15.440 T:1671     INFO <general>: Opening stream: 0 source: 256
2020-10-06 21:35:15.440 T:1671     INFO <general>: Whitelist search for: width: 1920, height: 1080, fps: 23.976, 3D: false
2020-10-06 21:35:15.441 T:1671     INFO <general>: Display resolution ADJUST : 1920x1080 @ 60.000000 Hz (18) (we_ight: 0.000)
2020-10-06 21:35:15.453 T:1671     INFO <general>: Creating video codec with codec id: 173
2020-10-06 21:35:15.453 T:1671     INFO <general>: CDVDVideoCodecDRMPRIME::Open - using decoder V4L2 mem2mem HEVC decoder wrapper
2020-10-06 21:35:15.454 T:1671     INFO <general>: CDVDVideoCodecDRMPRIME::Open - unable to open codec
2020-10-06 21:35:15.454 T:1671     INFO <general>: CDVDVideoCodecDRMPRIME::Open - using decoder HEVC (High Efficiency Video Coding)
2020-10-06 21:35:15.457 T:1671     INFO <general>: Creating video thread
2020-10-06 21:35:15.458 T:1677     INFO <general>: running thread: video_thread
2020-10-06 21:35:15.458 T:1671     INFO <general>: Opening stream: 1 source: 256
2020-10-06 21:35:15.459 T:1671     INFO <general>: Finding audio codec for: 86018
2020-10-06 21:35:15.463 T:1671     INFO <general>: CDVDAudioCodecFFmpeg::Open() Successful opened audio decoder aac
2020-10-06 21:35:15.463 T:1671     INFO <general>: Creating audio thread
2020-10-06 21:35:15.464 T:1678     INFO <general>: running thread: CVideoPlayerAudio::Process()
2020-10-06 21:35:15.466 T:1677     INFO <general>: CVideoPlayerVideo - Stillframe left, switching to normal playback
2020-10-06 21:35:15.468 T:1673    ERROR <general>: CDVDVideoCodecDRMPRIME::GetFormat - unsupported pixel format
2020-10-06 21:35:15.478 T:1678     INFO <general>: Creating audio stream (codec id: 86018, channels: 6, sample rate: 48000, no pass-through)
2020-10-06 21:35:15.480 T:1289     INFO <general>: CActiveAE::ApplySettings - Forcing samplerate to 48000
2020-10-06 21:35:15.535 T:1677    ERROR <general>: CDVDVideoCodecDRMPRIME::AddData - send packet failed: Operation not permitted (-1)
2020-10-06 21:35:15.778 T:1677    ERROR <general>: CDVDVideoCodecDRMPRIME::GetPicture - videoBuffer:nullptr format:yuv420p10le
2020-10-06 21:35:15.779 T:1677    ERROR <general>: CDVDVideoCodecDRMPRIME::AddData - send packet failed: Invalid data found when processing input (-1094995529)
....

Display More

Found out these related issues:

popcornmix/gbm branch unable to playback 4k HEVC 10-bit video but LE can

kodi-git build script for mainline hwaccel media decoding

Does anyone else experience this ?

Display More

it is still in development stage, this is beta version of Libreelec.

Dear balbes150

I can not see your new build images for g12b boards did you merge g12 with amlgx ?

Regards

Dear chewitt I tried your Bifrost image on my GT King pro but no luck it ended with a bootloop.

What is the Bifrost image for, could you mention about it?

Quote from chewitt

erbas experiment with the images in Index of / too .. I lost track of what Oleg is doing with boot scripts in his images and it's another point of reference on any issues that you see.

Eested LibreELEC-AMLG12.arm-9.80-nightly-20200324-aeb6e84-box.img.gz image on my gt king pro.

Boot Ok

Sound Ok

Video ok but Green-Blue Colour Problem still exist.

Network Ok

Tested Enigma 2 plugin too and it doesn't worked.

Quote from crazyturk

New images do not have meson-g12b-beelink-gt.dtb file.

Previous image include it you can use it or use attached dtb file. Just copy it to dtb folder.

LibreELEC-ARM-ALL.arm-9.80-devel-20200220134951-569f834-amlg12.img.gz

meson-g12b-gtking.dtb.zip

Quote from crazyturk

How will I run GT King Pro in nightly images? There is no dtb file in dtb/meson in nightly version.
(meson-g12b-gtking.dtb)

you can use gtkings dtb file.

Quote from clarkss12

Followed Erbas's instructions, but new problem erupted. When I insert the microSD card, and depress the "reset" button, my box boots into TWRP. Same thing if I type "reboot update" from a terminal emulator.

I am using Alvatech's ATV ROM, which has a builtin TWRP. Just did a clean install yesterday.

[ROM] Beelink GT-King ALVATECH Android TV - ATV (9.0 Pie) S922X - FreakTab

Dear clarkss12,

I'm using beelinks official firmware, if it doesn't boot to a sd/usb image just use "switch os" reboot option under android then it works for all third party firmwares.

Quote from chewitt

I have LE booting on a Khadas VIM3L with 5.4 kernel which is the same S905X3 (SM1) chipset, but the changes needed for that aren't in LE master branch nightly builds yet and due to rework on video decode and my real-world job schedule the master branch won't be usable for a while. I'll send an email to Beelink for the Android dts file and schematics. The dts won't be usable with LE but S905X3 and S922X are pin-compatible and comparing against the GT-King/Pro dts will reveal any changes. I have the GT-King/Pro devices booting the same (not quite functional) LE image. I need to find time to finish checking the schematics before sending the device-tree file upstream to the kernel. The Beelink u-boot is a sh1t to work with though. It's simple to trip into update mode but it doesn't allow enough time to detect alternative media so 9/10 times it won't boot into LE for install. Once it does it's fine, but getting to first boot is unreliable.

Dear chewitt,

I'm a GT King Pro user, your work is really important for us.

Because you are the only one who works with mainstream kernel for it.

We will patiently wait for your support thank you very much.

Regards,

I tried 03/12/2019 on my Beelink GT-King Pro, it booted.

Screen was Blue/Green my MX3 airmouse did not act as normal, mouse function is ok but keyboard doesnt work.

Tried a few Hevc movies but none of them was successfully showed.

As a start I'm happy to see LE booted with GT King Pro.