Posts by Menion

Quote from shava_mng

I'd like to take advantage of full hardware video decoding capability. Armbian uses mainline kernel, therefore nod hw acceleration.

Latest LE amlogic is mainline with Lima/Panfrost preliminary support, that can be added also in Armbian

What is the reason why you want to use LE and not Armbian?

Should this, other, cross posting point to instruction on multi boot activation?

Quote from balbes150

I don't have that kind of equipment.

Test LibreELEC images with KODI-18 for S9xxx

Hi balbes150 each time someone ask for migrating from CE or activation of multiboot, you point to this message.

Sorry, but really I cannot see any instruction for installing such multiboot.

Is there a document describing what is really required for installing multiboot?

In the post you have pointed there is written that a firmware restore is required. Assuming that can be hard for some box to get the OEM firmware, why should it be needed? CE actually changes nothing in the original bootloader, it is the "reboot update/toothpick" method that instruct uboot to look first for a bootable media instead go for eMMC

And what happens if someone what to switch between CE and LE back and forth?

Bye

is it done automatically at first boot from SD or?

Quote from balbes150

Coreelec are using an outdated and not compatible with other new systems technology run from external media. No matter what you have in eMMC. If you are running coreelec from external media, then your eMMC has an old version of multi-boot that is not compatible with the new systems. No new system can run properly on your device anymore.

Ok

So actually in order to launch LE from the Amlogic boxes, I need to update the internal Uboot first?

balbes150

Hi. You have said

Quote

2. The launch system in Coreelec is not compatible with LibreELECE and Armbian. If you run coreelec on your TV box, you will no longer be able to run LE and Armbian normally until the full recovery of the standard firmware via the USB Burn Tool and the new activation of the universal multi-boot, which is used in all new systems.

I normally run CE but while ago I made some tests regarding the ethernet support in mainline LE release and I am planning to continue on this as soon as I have some spare time. At that time if coming from CE on SD, it was enough to reboot in android and redo one of the "boot from SD" methods (Reboot update, toothpick or whatever) to boot LE from the SD card (and again the same to eventually reboot in CE).

Now you write that it is required to restore the standard firmware. Are you talking about CE installed to internal, or it really affect any device that are currently booting CE from SD (and or USB)?

Quote from mo123

Someone can perhaps build an addon like this but for Rockchip devices?

GitHub - roidy/script.amlogic.colorformat: Amlogic color format information script.

It can be very useful to test display mode, color depth, color space, color range etc.

Does not work on mainline linux

Quote from balbes150

For all.

1. Everyone chooses for himself what systems to use it. No one is forcing you to use LE.

2. The launch system in Coreelec is not compatible with LibreELECE and Armbian. If you run coreelec on your TV box, you will no longer be able to run LE and Armbian normally until the full recovery of the standard firmware via the USB Burn Tool and the new activation of the universal multi-boot, which is used in all new systems.

Hi

Can you elaborate more on this? Some times ago it was just enough to restart in Android and do again the "reboot update" (or other methods)

Quote from balbes150

Can you check any of these images (all dtb g12) ? I'm only interested in the wired network.

https://yadi.sk/d/nfesiwb1e5xf3g

https://yadi.sk/d/nfEsiwb1E5Xf3g

One issue with wired network and DTB can be the link up irq vs polling

Not all the boards have irq line connected, it makes most sense to go for polling, since there is no real need to have an irq on it

chewitt during the CE work on amlogic kernel 4.9 we are still getting issue with ethernet connection at gigabit speed with some boards. I am pretty sure that some of the cabled ethernet issue with mainline have a common root cause. And as we discussed in the past I think it is clock delay related.

Can you try to get from amlogic the spec of PREG_ETH_REG1? Is the (in)famous register set by cali_val that disappeared in amlogic kernel 4.9 and not even taken in account in mainline kernel. I suspect that this register contains some rx related clock configuration, in kernel 3.14 we needed to remove the common 0x20000 set to make some box to work correctly at gigabit speed

Quote from chewitt

Menion Until early Jan when panfrost first started working nobody was really able to do anything practical with a mainline S912 device so the current upstream device trees are known to have fallen behind GXBB/GXL configs. I know he has VIM2(s) and a Vega S95 box, hence:

linux-9999-fix-vega-s95-dts.patch

S905D and S912 are pin compatible so some of the more proven GXL device trees might be a better starting point?

chewitt if I use an Armbian with kernel 4.19.x I get working ethernet on my H96pro+ (S912 with Realtek phy) with nexboxA1 dtb as we discussed in PMs. The armbian dtb is quite different than the LE one. I tried to use it in LE build (before I knew it was on kernel 4.20) and obviously endup in kernel panic.

What I don't understand is why USB is down while on balbes150 hardware is up. All the differences between the S912 hardware should be on sensors and little else, USB and ethernet should be just the same except for the PHY IRQ story

balbes150 do you have a S912 box on which your 4.x mainline (plus patch) kernel images run with a working network connection and USB? If so, can you please share (also pm are ok) which dts you use and the dmesg output after boot?

There is something to address here. Q201 dts use irq for phy link management, while apparently most of the box out there does not have it so polling shall be used. Also there are some box with ZTE phy that shall run default eth2 reg (the old cali_val attribute in 3.4.x amlogic kernel).

balbes150 What's the 4.xx kernel you use in your images?

I am trying on S912, I have a H96pro+ box with Realtek PHY.

I can boot LE with the nexus-a1 dtb, that I used a while ago with Armbian and kernel 4.19.0 where I managed to get ethernet connection up

With your image I get ethernel link down, no remote (but it is not a meson-ir default one, so probably I need to configure it) but also CEC is down, so basically I cannot inspect anything

I have not found yet the time to bring a 4.19 to a boot on my S912 devices. When I tried the 4.18 Ethernet was just down. Can you give a shot with CoreELEC? There are people there confirming that they solved the issue

The dtb is for CoreELEC and LibreELEC 9.xx

ok. The symptoms you have are of corrupted data after MAC. It is likely that the S912 in your t95z is defective, I suggest you to return it

describe the connection between your tv box and the network (cables, switch in between, ecc...)

Also try to connect something else to the same ethernet cable you use for the tv box (a laptop for example)