[8.90.6] LibreELEC 9.0 Alpha for S905/S912 devices

Quote from Paul69

I can boot with gxm_q200_2g.dtb and also with gxm_q201_2g.dtb, without any issues.

But do you know the difference between both files?

Paul

Q201 has only internal PHY, Q200 offers the possibility to choose between internal or external PHY.

Quote from adamg

Did you download the latest copy?

I have a 2GB 32 Beelink MiniMx3 2 machine which means I need the gxl_p212_2g.dtb file. The latest dtb is from 2017-10-28 11:13

Yes, I've tested both files with my H96pro+ and only the gxm_q200_2g.dtb work good, because with the gxm_q201_2g.dtb I didn't get an ethernet network connection. So for me is only the gxm_q200_2g.dtb the right dtb.img!

Paul

Quote from adamg

Did you download the latest copy?

You should probably fix the link to the latest trees in OP.

Gregoir3 I think you should try one from this folder: Index of /releases/dtb/S905X

Does anybody here use the music database? When updating from 8.90.3 to 8.90.4, I would be presented with a black screen. The log shows a failure to initialize MyMusic70. I've tried dropping it (and its predecessor) to no avail. Kodi then boots ok but as soon as I scrape something, on the next boot I get a black screen again. Error in log is

21:31:09.745 T:139727820420864   ERROR: SQL: [MyMusic70] An unknown error occurred                                            Query: SELECT idVersion FROM version
21:31:09.795 T:139727820420864   ERROR: Process error processing job

The culprit seems to be PR:13318 where I've already left a comment.

Quote from kszaq

You should probably fix the link to the latest trees in OP.

Gregoir3 I think you should try one from this folder: Index of /releases/dtb/S905X

Thanks kszaq. Didn't know this link existed.

Updated with the proper dtb but still "No device found" message no matter what procedure I follow.

Hi.

I have just updated to 8.90.4 in a Vorke Z6, but the LCD is not working properly. The last digit of the clock blinks, the pause and play icons are lit, etc.

I took the gxm_q200_3g_vorke_z6.dtb from http://libreelec.adamg.co.uk/releases/dtb/S912/

However, the one The Coolest gave in here worked perfectly in 8.90.3.

Please, could to take a look at it?

Thanks!

Quote from Gregoir3

Thanks kszaq. Didn't know this link existed.

Updated with the proper dtb but still "No device found" message no matter what procedure I follow.

Hi Gregoir,

have the same device and created my own map. Works for me. Before I had done an upgrade

using this image

LibreELEC-S905.arm-8.90.4.tar

and this device tree

gxl_p212_2g.dtb

Just rename (without the txt extension), copy and refer to it in the rc_maps.cfg

my entry in the rc_maps.cfg looks like this, just the filename without the full path:

meson-ir * minimxIII

Quote from Gregoir3

Thanks kszaq. Didn't know this link existed.

Updated with the proper dtb but still "No device found" message no matter what procedure I follow.

Your latest dtb is in /usr/share/bootloader. Submit command cp /usr/share/bootloader/gxl_p212_2g.dtb /storage/.update/

and reboot box.

Quote from Gregoir3

Updated with the proper dtb but still "No device found" message no matter what procedure I follow

If the previous advice hasn't helped, then clean install with correct dtb worked for me

darioml  GDPR-2

Apologies. The source file the new DTB was built from has the character order reversed. I'll fix and submit a PR on that ASAP.

For now here's a fixed DTB.

is there a fix for slow ir remote response? Ever since updated to 8.90.4 the key presses lag

Quote from androidguykodi

is there a fix for slow ir remote response? Ever since updated to 8.90.4 the key presses lag

[8.90.4] LibreELEC 9.0 Alpha for S905/S912 devices

8.90.4 seems to have broken the ability to use a skin shortcut to execute rebootfromnand.

The command still works if issued via SSH but not via shortcut / script.

I've tried with aeon.nox and estuary skins, both of which have no problem with this in earlier versions, but nothing happens at all with the latest build. Can anyone else who is dual booting using a rebootfromnand shortcut confirm that they are still able to with 8.90.4.

Quote from androidguykodi

is there a fix for slow ir remote response? Ever since updated to 8.90.4 the key presses lag

I set it to:

ir-keytable -D 100 -P 400

For my remote it now works faster and fewer unexpected repeating
May be somebody have another optimal values.