Posts by kszaq

I didn't say it's fixed. I simply suggested that there is a patch that might help.

Quote from Hauke

I had some exchange with the very helpful Armbian team - they had the same issue and it is solved. Here are the mainline kernel patches that adressed the issue:

[net] net: stmmac: enable EEE in MII, GMII or RGMII only - Patchwork

[net,v3] net: phy: meson-gxl: detect LPA corruption - Patchwork

kszaq & GDPR-2: Is it possible to somehow incorporate this into the LibreELEC kernel?

These mainline kernel patches cannot be applied to 3.14 kernel. For the first issue there is already a fix in LE kernel. There is also another patch that is present in LE master but not in the kernel that GDPR-2 uses: PD#147897(146205): eth: fix eth stop · LibreELEC/linux-amlogic@08c964a · GitHub

Please note that I don't support these builds.

To remove all network settings: rm -rf /storage/.cache/connman

You might give MakeMKV a go: MakeMKV into the repository?

base_08 Don't worry, Leia is coming.

dmtt Try using noram version. This is because your box has only 1GB of RAM and there is insufficient space to copy whole SYSTEM image to tmpfs.

wappi Switch to CrazyCat drivers in Addons menu.

Quote from toe-kne3

kszaq I know you've discontinued this build but was wondering if you are still providing support?

A while ago, I had asked you about the differences in the dtbs posted, you replied that they're purely cosmetic and either would work.

While testing other builds on different devices (i.e LE9 on x96) it was mentioned that using the wrong dtb would mean that either WiFi, Ethernet, IR etc wouldn't work.

Flashed an sdcard for my MXQ Pro 4k running 8.2.3.1 and used mxq_pro_4k dtb. Booted fine from sdcard, but after copying it to internal installation using ssh commands in OP and rebooting to internal, I'm getting a blank screen. The box is powered on, the TV picks the signal (shows 1080p input) but no MXQ Pro logo and the network (Ethernet) is down so can't ssh in. Any way to get it to work when copied to internal?

Your box has a NAND chip (meaning not eMMC) and there is a bug in Amlogic bootloader that prevents repartitioning the drive. You can try using a standard device tree but if it doesn't work, you're out of lack and have to run LE from SD card.

S905 doesn't support 10 bit output. You can decode 10bit H.265 but they will be scaled to 8bit output.

I haven't looked at your package.mk but this error is most common if you try to run aarch64 or x86_64 binary on arm system. Make sure that you compiled it with correct arch.

Edit: try removing this line from the Makefile: gpio_lib_c/Makefile at sbc/tinkerboard/c · TinkerBoard/gpio_lib_c · GitHub

pipsen disable AC3 transcoding in Kodi options.

Quote from Manuel

Is "576cvbs" PAL progressive?

As far as I can tell it's PAL interlaced.

Quote from Manuel

Are these modes/parameters documented anywhere? I searched for "setenv libretech" but couldn't find anything useful.

No, this is a custom boot configuration file based on what was already provided for Odroid-C2.

Quote from Manuel

Is there also a Kodi 18 build available for this board? AFAIK the Amazon video plugins don't work in 17, right?

Yes, GDPR-2 provides builds for LePotato based on LE master + community patches.

Quote from wrxtasy

The one that is also used for alpha versions of AML LE Kodi Leia 8.9.x that adamg is releasing.

This is not true - Adam still uses the kernel from my Krypton builds.

Manuel It should be possible but I cannot test if for the moment. What you need to do is replace this line in boot.ini:

setenv libretech "no_console_suspend logo=osd1,loaded,0x3f800000,${hdmimode} vout=${hdmimode},enable hdmimode=${hdmimode} cvbsmode=nocvbs consoleblank=0"

with

setenv libretech "no_console_suspend logo=osd1,loaded,0x3f800000,576cvbs vout=576cvbs,enable hdmimode=${hdmimode} cvbsmode=576cvbs consoleblank=0"

Try

echo 1 > /sys/module/di/parameters/bypass_all

Thank you vpeter!

I was using my MK808B+ with 2011, 2012 and 2013 models with no issues. Please try using a different HDMI cable. It is also possible that your MK808B+ is a bit faulty.

Unfortunately there is no point in grabbing logs, I did a pretty intensive CEC debugging session back in 2016 and in current state it's the best what I can get.

Please also look at the first post: I am not working on these builds any more (lack of time). The only update S805 devices will get is a bump to Kodi Leia (soonish).

It would be nice if the patches to kernel config go upstream (to LE master).