Posts by jernej

psyapathy Sorry, no time to actually debug that. You can however try to build your own image and your own addon. Use following repository:

GitHub - jernejsk/LibreELEC.tv: Just enough OS for KODI

Command to build OrangePi Win image:

PROJECT=Allwinner ARCH=arm DEVICE=A64 UBOOT_SYSTEM=orangepi_win make image

Command to build addon:

PROJECT=Allwinner ARCH=arm DEVICE=A64 scripts/create_addon <addon name>

andreabak OpenELEC image used kernel which doesn't consider EDID at all. This was one of the pain points. You had to change fex file if your monitor didn't support 1080p. Besides, only 1080p, 720p and few other patched-in resolutions were supported. Here, on mainline kernel, a lot of stuff is based on EDID. Can you post output of following command?

edid-decode /sys/class/drm/card0-HDMI-A-1/edid

There are some other possible differences. AFAIK, mainline HDMI driver doesn't set correctly metadata like colorimetry, aspect ratio, etc. This might also be the problem.

andreabak Can you make some photo or video what it is and what it should be? I played video you referenced, but with that latest test update, it works same regardless DRM or GPU rendering (both HW decoded) or even completely SW decoded and GPU rendered. I can see flashing bars from 16 to 235. That's on PC monitor.

Quote from psyapathy

I install Gamestarer. I try to run it, it hangs on the splash screen and goes back to Kodi.

This is possible?

Did you updated to latest version which uses rebuilt addons so they shouldn't crash anymore? If yes then it might be an actual bug in addon. Note that I don't test addons nor fix bugs in them.

andreabak Please test this:

libreelec-h3.arm-9.1-devel-20190130174140-064c56c.tar

Full range is forced here and I think it should work well for monitors, but not TVs.

The issue here I think it's mix up between input range and output range. DRM property description doesn't explain it very well. If this works for you, I'll have a talk about it with other developers to find acceptable solution.

Quote from marcins

It is hard to test anything because system is write protected..

Depends what you want to do. Usually you have to update build system (mostly by adding patches), build update file and update board with it. It takes minute or few at most once you have good setup. That's the way I develop LE.

Quote from marcins

Any plans to run Passthrough?

Eventually, yes, but not by me since I don't have AVR.

andreabak It turns out that color range and color encoding are pretty easy to implement. Can you test following update:

libreelec-h3.arm-9.1-devel-20190129185238-064c56c.tar

You can see what encoding & range is used for video, if you run "modetest -M sun4i-drm" command during video playback via ssh. Both properties are set by Kodi to values based on video metadata and AFAIK you can't override them.

It seems that driver used BT601 full range transformation till now.

Quote from LubMich

Someone has already modified the dtb / dts file for the i2s sound on gpio?

I've already decompiled the file ... but this is a new file for me ... so I'm looking for an example ...

I don't have any experience with external I2S codecs, but I can give you few pointers. First you have to make sure that wanted I2S node is enabled. It should be already present in decompiled DT, you just have to change status from "disabled" to "okay" (with quotes). Secondly, you have to define I2S pins (ARM: dts: sun8i-h3: Add pin settings for I2S0. · codekipper/linux-sunxi@b397fd0 · GitHub) and assign pins to I2S node. Thirdly, you have to integrate codec into DT (for example, connect control interface to I2C and create simple soundcard node for audio interface).

Here you have example for uda1380 (driver needs one patch if you also have this codec): DEMO - i2s on H3 with uda1380 for OPi2 · codekipper/linux-sunxi@d1c85a6 · GitHub

marcins

Passthrough doesn't work yet, currently only linear PCM (LPCM) works. So if you can't get EDID to show more than 2 channels for LPCM, it won't work (EDID is source of information for driver to know what audio capabilities TV/AVR has).

andreabak

BT601/BT709 to full/limited range conversion is not implemented in display driver yet. I'm not sure which conversion is currently used. I took a look what needs to be done and it doesn't seem too complicated. Wait for it a bit.

marcins check your edid decode output. It has following data:

Audio data block
    Linear PCM, max channels 2

Which means only 2 channels are supported for linear PCM on your device. Do you use AVR? If yes, how it is connected? board <-> AVR <-> TV ? Using HDMI ARC may not work correctly.

Quote from marcins

Have you any idea how resolve this?

Make sure that HDMI audio output is selected (name of your TV or audio device should be mentioned in the name). If you did this already, please provide following info:

1. Kodi debug log

2. Output of command "edid-decode /sys/class/drm/card0-HDMI-A-1/edid"

Some devices doesn't support multichannel audio for linear output, only for passthrough.

Quote from Kristian

Would it make sense to provide you with some of these files for you to test?

No need, because I have some too. Until these are fixed, there is no point.

Quote from PeterSz

I have OPi plus 2e and some problems with network connections. Sometimes it takes more than minute to connect by wire Sometimes it also drop connection at random moments and i must wait for next connection. I'm trying to compile your code on ubuntu bash on windows, but without success yet.

I'm using OPi plus 2e during testing and I have never had any wired network issues. Did you check settings? sorry, I can't be more helpful here. Regarding image building - you should try to build it in virtual machine. Bash on windows is not supported method.

Quote from rix81

will your image be compatible with beelink gs1? can't wait to test it, thank you for your effort!

It's possible, if someone writes DT for that specific box and make sure that mainline U-Boot works on that. If it uses LPDDR3 RAM chips, then it's easy. Everything else will need some more effort to add correct RAM initialization code.

hostkit Current method for IR configuration is described here: Infrared Remotes [LibreELEC.wiki] lircd is still supported but not recommended. I haven't found time to check your config though.

lumpi Please note that LE build system has multiple patches for kernel. Some of them touch DT too. For example, HDMI audio is not mainlined yet (but we are working on that). There is Beelink X2 DT specific patch too (to avoid random MAC address). You have two options:

- Decompile DT, patch it, compile it again.

- Create a kernel patch and build your own image/update file

H34TW Sorry, but you'll have to fix and build WiringPi yourself for LE if you want to use it. It's too board specific (or at least manufacturer specific) and such things are extremely low on priority list.

andreabak Currently there are no automatic updates. This will change when allwinner project becomes part of master branch. But it's still some work to do until then (mainly to fix H264 and HEVC bugs).

Vovanys I'm pretty sure USB keyboard should work out of the box. But since I didn't test images on PC Plus specifically, it may be that there is some issue with DT. I doubt switching to newer image will change anything. I'll test in hopefully near future.

BTW, LibreELEC 8 images are not from me, so I really don't know what is contained there. Current images are based on 4.20 kernel.

H6 support is worked on. Just two days ago I managed to fix HDMI audio support. HW video decoding is next - it is very similar to older variants, just updated with new features, so I don't expect much work, but you never know.

Gendo check files under /sys/class/drm/ I'm pretty sure you'll find correct file to trigger enable/disable there.

hostkit can you provide content of your lircd.conf which crashes Kodi? BTW, do you know that lircd is deprecated since LE 9?

Regarding your RTL8188EU wifi issue, I can't say anything. It could be that issue is in some other part of wifi stack. Can you test with different wifi dongle, which doesn't have RTL8188EU chip?

Quote from thc013

building it what feedback do you need will test it on both a pc2 and zero2 +

H5 is not supported currently due to known GPU rendering issue. Until it is solved, there's no point having H5 images.

Quote from hostkit

Know issue 2 last build. Wifi dongle not working very well. Connect disconnect connection every time and auto connect not working show i always mannual connect

which dongle? Do you know which driver it uses? Or at least USB ID?

Quote from hostkit

what about the video showing block / blurred videos some position randomly? Display setting egl and plane to direct

Video decoding is not perfect and at this point it's hard to find any issue.

Quote from hostkit

I have been trial install to emmc using emmc_install.sh but install failed. Without edit mmcbkl1, mmcbkl1 not found. only mmcbkl0 and mmcbkl2 load.

mmcbkl2 flash success but opi not booting because uboot sunxi not found. Trying download from internet device can boot but stack black screen, kodi not startup

That install script is not usable here. Too much things changed.

New update uploaded. Changes:

- Rebased on master (Kodi 18 rc5)

- Changed addon repository (hopefully much less crashes)

- Added bluetooth drivers

Quote from thc013

your switching to libmali and gbm and included h6 just building and will try

There is no HW acceleration and audio of any kind for H6, booting is unstable and HDMI might blink occasionally, so very early stages

Quote from thc013

a PC2 and zero 2+ are standby

For some reason, there is an issue with mali for at least 1080p resolution on H5. I tried hard to find an issue, but I had no luck. As soon as it is fixed, support should be on H3 level.