Posts by dmladenov

I missed the first test

Now I updated with the new .tar and again no sound

Although I have selected sound via HDMI on the analogue output there is sound but it is distorted.

Just in case I switched to Android and no sound problem.

https://paste.libreelec.tv/settled-warthog.log

Done

Sorry, but I put it here because I had to delete my PVR settings

Thank you

https://paste.libreelec.tv/able-lemming.log

Still no sound from HDMI. Not tested analog.

ir-keytable -t shows the (NEC) scan codes on all buttons and will be able to do working keymap.

HDMI CEC works.

In Video info screen (the O key) - System rendering speed =10-15fps. The Video stream is h264 codec SD and HD. Screen Resolution 1920x1080@50Hz. Video decoder = ff-h264_v4l2m2m-drm_prime (HW). System CPU0-3 usage 2-25%

HNY 2024 to all

I succeeded

On LibreELEC-AMLGX.aarch64-12.0-nightly-20231210-e521363-box.img.gz

With device-tree-compiler I decompiled (dtb->dts) meson-gxl-s905x-p212.dtb and edited only mali section (gpu@c0000) as I saw from here https://github.com/hexdump0815/li…905l2-x7-5g.dts - just deleted pp2 and ppmmu2 and left only pp0,ppmmu0,pp1,ppmmu1. Тhen I compiled it (dts->dtb) with the same tool.

And the magic happened The Libreelec booted and no kernel panic !

There is no sound, no remote, no WiFi at the moment but LAN works. I have installed Stalker PVR Client and the SD/HD TV channels are playing fine.

Quote from chewitt

The only odd thing in dmesg (other than references to missing SYSTEM file) is there's no sign of the GPU driver (lima) loading, but how that might factor into anything is anyone's guess.

I searched the web and found this https://github.com/hexdump0815/li…-pp-cores.patch. As you suggested, it is very likely that the problem is the GPU driver. So my S905L? GPU may be 2 cores instead of 3. And the Armbian, which I tried a long time ago, was without a desktop !

I tried meson-gxl-s905l-venz-v10.dtb and the result is the same - kernel panic.

It turned out that this DTB was in the archive https://test.libreelec.tv/11.0/Amlogic/b…3cd2-box.img.gz

Thanks for the clarifications. I have tried many versions of LE and CE. I keep the UART log from Legacy CE 9.2.8 (kernel 4.9.113) and again it ends in kernel panic. If you keep device-tree for a "Venz V10" S905L box I would try it.

I forgot to mention that the only thing I was able to run successfully was armbian.

Hi all

From two years I have a cheap fake TV box Q96 4K Ultra HD 5G (1+8GB instead 2+16GB) with unknown SOC S905? (probably S905L), WiFi/BT Mediatek 7668, w/o SD slot with Android 10.

When trying to boot Libreelec (10, 11, 12 or Coreelec...) from USB using device tree meson-gxl-s905x-p212.dtb (I tried many others but only gxl works on this box), it only reaches to kernel panic. I am attaching the UART Log of the working Android, Android DTB partition, photos of the box and Libreelec boot process.

In the log file it is seen that the platform is p271 ?! Is there any chance that this TV box will boot Libreelec.

EDIT: After I deleted SYSTEM file, I was able to get to the console and run dmesg. Now I also attached dmesg.log

Quote from jaum20

It's possible to add a custom remote? I am tryng to add one and getting No devices found. Any ideas?

Look my post #360

Hi @ilmich

hallelujah

Finally all the buttons are working. That was the goal. Now I can customize and precise the actions of each button in Kodi with a Keymap Editor Add-on as I always could with the other LibreELECs, CoreELECs ...

Thank You very super many hyper mega ultra much @ilmich

@ilmich the things are terribly bad

The KEY_XXXX assignment of all problem buttons (RED, GREEN, YELLOW, BLUE, PREVIOUS, NEXT, 1/A/a, MOUSE) are not recognized in Kodi. I'm starting to think they should correspond to keyboard buttons.

May be the last try:

    ir_key5 {
        rockchip,usercode = <0x1dcc>;
        rockchip,key_table =
            <0xee KEY_ENTER>,
            <0xf0 KEY_BACK>,
            <0xf8 KEY_UP>,
            <0xbb KEY_DOWN>,
            <0xef KEY_LEFT>,
            <0xed KEY_RIGHT>,
            <0xf1 KEY_VOLUMEUP>,
            <0xfd KEY_VOLUMEDOWN>,
            <0xff KEY_POWER>,
            <0xf3 KEY_MUTE>,
            <0xbf KEY_C>,
            <0xbe KEY_1>,
            <0xba KEY_2>,
            <0xb2 KEY_3>,
            <0xbd KEY_4>,
            <0xb9 KEY_5>,
            <0xb1 KEY_6>,
            <0xbc KEY_7>,
            <0xb8 KEY_8>,
            <0xb0 KEY_9>,
            <0xb6 KEY_0>,
            <0xb5 KEY_BACKSPACE>,
            <0xfe KEY_M>,
            <0xfa KEY_T>,
            <0xf6 KEY_E>,
            <0xf2 KEY_A>,
            <0xf9 KEY_PAGEDOWN>,
            <0xf5 KEY_PAGEUP>,
            <0xfc KEY_HOME>,
            <0xb3 KEY_I>,
            <0xb7 KEY_O>;
    };

ilmich thanks for the detailed explanations.

Тhis is the result of the buttons not working before:

button HOME = KEY_HOME

button MOUSE = KEY_O

buttons PREVIOUS, NEXT, 1/A/a - they are not touched as you said

buttons RED, GREEN, YELLOW, BLUE - something is wrong here. LED flashes but no reactions in Kodi. I installed an Add-on Keymap Editor and it shows the same longer code 16839168 for all four buttons. For comparison, the HOME button is 61622 - only five digits like all other buttons.

Following your instructions this is what ir_key5 should look like specific to my needs:

(can you make rk3229-box-v884k.dtb)

    ir_key5 {
        rockchip,usercode = <0x1dcc>;
        rockchip,key_table =
            <0xee KEY_ENTER>,
            <0xf0 KEY_BACK>,
            <0xf8 KEY_UP>,
            <0xbb KEY_DOWN>,
            <0xef KEY_LEFT>,
            <0xed KEY_RIGHT>,
            <0xf1 KEY_VOLUMEUP>,
            <0xfd KEY_VOLUMEDOWN>,
            <0xff KEY_POWER>,
            <0xf3 KEY_MUTE>,
            <0xbf KEY_MENU>,
            <0xbe KEY_1>,
            <0xba KEY_2>,
            <0xb2 KEY_3>,
            <0xbd KEY_4>,
            <0xb9 KEY_5>,
            <0xb1 KEY_6>,
            <0xbc KEY_7>,
            <0xb8 KEY_8>,
            <0xb0 KEY_9>,
            <0xb6 KEY_0>,
            <0xb5 KEY_BACKSPACE>,
            <0xfa KEY_RED>,
            <0xfe KEY_GREEN>,
            <0xf6 KEY_EPG>,
            <0xf2 KEY_BLUE>,
            <0xf9 KEY_PREVIOUS>,
            <0xf5 KEY_NEXT>,
            <0xfc KEY_HOME>,
            <0xb3 KEY_INFO>,
            <0xb7 KEY_SUBTITLE>;
    };

Quote from ilmich

Please explain what happens specifically (which keys don't work or just if you want to remap them).

Compiling a dtb is easy (you can find guides on google). But I can also compile it for you.

I only have 2 or 3 remotes, so if something new comes up that I can include in the build it would help others too.

Keep in mind that regardless of the driver I will use in libreelec 11, the starting configurations will be that of libreelec 10.

Thanks

Michele

Display More

I am attaching a picture of my remote.

The buttons outlined in red don't work for me and when I pressed them even the LED does not blink.

I just want to be able to use them too.

But I can't deal with the missing button codes.

I don't know how to debug them in your LE 10 with legacy driver.

With LibreELEC 9 (knaerzche) with working ir-keytable it was easier to see scancodes but they are absolutely different. I attached rc_keymap file V88.txt for example.

Quote from ilmich

Hi @dmladenov,

for remotes, in libreelec 10 the driver used is the legacy one because it integrates switching off/on. Which you can't do with the mainline driver (you can manage the suspension, but not with which key/remote control to reactivate everything).

The legacy driver is taken as-is from the 4.4.x kernel and therefore the mapping is not easily modifiable through the official libreelec guide because they reside in the device tree (like android os).

You can modify as you saw the dts with the scancodes you prefer (the module has a debug mode where you can view them).

In libreelec 11 I plan to use a mix of opensource drivers/legacy suspension system, but I don't have much time for new developments these days

I'm sorry

Michele

Display More

OMG. Now I need to learn how to compile the whole LibreELEC...

Is there an easy way to compile only my rk3229-box-v884k.dtb ? Do you have a guide ready for this job from scratch ?

Or if i make the changes for my remote (ir_keyXX {}...) in rk322x-box.dtsi can you compile it for me ?

SCISHION V88 4K andriod TV BOX (1G/8G)

https://ilmich.libreelec.tv/libreelec-10/LibreELEC-RK322x.arm-10.0-nightly-20230525-43c4ed8-rk322x.img.gz

rk3229-box-v884k.dtb

boot from SD Card

Why I can't customize my IR remote keytable/scancodes with putting relevant files in /storage/.config/rc_maps.cfg and /storage/.config/rc_keymaps/ (Infra-Red Remotes - LibreELEC.wiki)

Тhe problem is that some buttons don't work.

LibreELEC:~ # ir-keytable
No devices found

Should it be fixed here ? :

LibreELEC.tv/linux-9000-rk322x-dts.patch at libreelec-10.0 · ilmich/LibreELEC.tv · GitHub

Quote from samura

I bought a TAPI or TAP1 S905X 1G. I've booted to android and I'm trying to extract its DTB, but is impossible because I don't have the /dev/dtb folder. Is this normal?

Try this script I made to backup these partitions. Go to recovery and select install from ext. Then select this zip. The image files will then be saved on the SD card. I have not tested with USB.

Hello,

Android box: X96mini

CPU: Amlogic S905W

PCB: Q6X v2.2 17355

WLAN chip: SV6051

8GB eMMC 5.1: Hynix H26M41103HPR

1GB RAM

From SD card all works, but can't install to internal

LibreELEC:~ # installtointernal

One of BOOT, SYTEM, DATA or DTB partitions is missing.

Make sure that you are using a correct device tree and a device with internal memory!

Tested with device trees from Index of /s905/8.2/device_trees/S905X

gxl_p212_1g.dtb

gxl_p212_1g_nand.dtb

gxl_p212_1g_slowemmc.dtb

Tested LibreELEC-S905.arm-8.90.6 with new gxl_p281_1g.dtb and now boot, system, data, dtb ... are visible.

Tested Generic-8.0.2.1 - Update 29.05.2017 on my box Wintel CX-W8 - (CPU Z3735F, 2GB DDR3. 32GB EMMC, WiFi Realtek 8723, Windows + Android)

Wifi, LAN, Audio - works

With Stalker Client and SD channels I need to change Deinterlace method for smooth.

On HD channels - unsatisfactory results.

But with Android and Windows - the same results.

May be the Intel HD Graphics on Atom is no good.