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.
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.
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.
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?
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.
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?
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.
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
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
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.
hostkit how did you managed to crash Kodi? Was it by using some addon? Currently addons are very unstable.
They will be rebuild for next update and that should eliminate most (all?) addon related crashes.
wifi and temp won't be addressed in near future.
Is there anything speaking against getting a nanopi a64 as a libreelec "player"?
It's powered through microUSB, which is not recommended by me and some others, like Armbian team.
Anyway, board is not yet supported by LE build system, but I think that is easily fixed by one line entry.
I suggest you start from GitHub - jernejsk/LibreELEC.tv: Just enough OS for KODI
1. Add A20 specific subfolder here: https://github.com/jernejsk/libreelec.tv/tree/hw_dec_ffmpeg/projects/allwinner/devices Check H3 subfolder what it has to contain. You can just copy H3 folder as a starting point and check every file what needs to be changed. You have to definitely remove all Linux patches and add A20 specific ones. You have to add patches from Paul Kocialkowski where he added support for YUV (kernel/git/next/linux-next.git - The linux-next integration testing tree - everything from 2018-11-27 and newer) and support for DRM format modifiers (patches are somewhere on some mailing list, probably dri-devel). Remove all U-Boot patches.
2. Enable A20 specific drivers in kernel config: linux.arm.conf
3. Add boards to U-Boot helper script: LibreELEC.tv/uboot_helper at hw_dec_ffmpeg · jernejsk/LibreELEC.tv · GitHub
4. Extend FFmpeg support for using modifiers in V4L2 request codec. But if you come to this point, ping me and me and others could assist you.
After that, there are various small tasks, but most important one - hw video playback, will be already done.
In general, make bootable image first (points 1 - 3). However, to do that, you don't need any Linux patches, so that should be really easy.
What about bluetooth? I see it's disabled?
OrangePi One doesn't have bluetoth on board. Are you using a dongle?
What was the problem exactly?
I just rebuild addon using allwinner project. Currently repository is actually shared with amlogic devices. I though it would work for all addons, but obviously works only for some.
I'll rebuild all addons and soon upload another update which switches repository to those rebuild addons.
BleedingYou can you test this variant: pvr.dvbviewer-3.7.8.2.zip ?
thanks for images, but there is no possible to add wifi driver for Pi Lite?
It is but not something worth doing. Realtek drivers are pain to maintain and with different wifi manager in LE10 it won't work anyway. Besides, Lite has only 512 MiB of RAM, which means it won't be maintained for very long. At least not actively.
Do you have plan to add script?
At some point. I want to fix some decoding issues first.
New updates are uploaded for H3 and A64:
- rebased on latest LibreELEC master (notably Kodi 18 RC4)
- A64 analog audio is now supported
- HDMI CEC fixes added (not necessarily stable)
- new A64 board is added - OrangePi Win
- support for AP6212 WIFI (OrangePi Win, BananaPi M2+)
- USB is now disabled in U-Boot, which is a workaround for times when connected USB device prevents booting.
NOTE: U-Boot is not updated with image updates linked in first post. U-Boot is board specific, which means that update file would have to be board specific too to also update U-Boot and that is just not feasible with so many supported boards. But you can pull sources and build your own board specific update or even clean image.
