Regarding the HDMI issue: I build Manjaro arm for my pine64+ and have the same issue there, no sound through hdmi. Analogue works just fine. Manjaro is running on linux kernel 5.2.
Lakka doesn't have sound either trough hdmi but analogue is OK. I don't know about armbian but armbian is on 4.19.
According the picture: A64 with 2GB ram is a pine64+
Yes,
indeed, hdmi is not enabled as it uses the same sun50i-h6-orangepi.dtsi as the orangpi_one_plus so it should be the same patch as the orangepi_one_plus minus the ethernet stuff.
I will have to find out again how diff works, it's already a long time ago I did this kind of stuff...
Honestly, currently I don't have any plans to do that, as I don't consider these devices to be popular choice for LibreELEC. But now that I think a bit, they could be considered as portable movie players.
However, I don't have any of them, but if there is enough interest, something can be arranged. Maybe you can make another thread with poll to see how much interest there is?
Maybe I will do a poll on the pine64 forum, probably there is more people interested in the pinetab.
So if I want to build a image for the orange pi lite2, I only have to add
'orangepi-lite2': {
'dtb': 'sun50i-h6-orangepi-lite2.dtb',
'config': 'orangepi_lite2_defconfig'
in the uboot_helper script under H6?
Jernej,
any idea if you will add support for pinetab or even pinephone?
OK,
found it myself, Should be checked in the kernel tree according the "release" file in projects->chipset->devices->bootloader
Where can I find the file where is specified which boards are supported? It's already a long time ago I did a libreelec build, but now I want to build a Allwinner H3 with lima support, just for testing. In that days all specific board where in projects -> chipset -> devices. In devices you can chose no the different cpu's but I don't find a file with the supported devices in this category.
In Lakka for example, it is specified in in the "options" file.
So I had some time to test more on the MK808C
- I did switchoff CEC option to turn of the TV, now OK, TV doesn't switch off anymore.
- Analog out doesn't work, I have no sound.
- Wifi chip seems not to be recognised. I should ad a usb network hub to login through ssh and check dmesg and lsmod-> Didn't do it yet!
- Mpeg2 starts to play but suddenly the picture is paused although the time goes on, probably the audio keeps on goiing also.
- H264 doesn't play at all, I keep having the spinning wheel.
Jernej,
MK808c: it boots, it expands, it reboots I see the kodi screen and the initialisation screens but then my TV switches off and I can't switch it on again. I have to pull the plug and reboot and then my TV starts to work again. Probably something with CEC, because on my pc screen it works OK.
Sounds does not work through HDMI, didn't try the 3.5mm jack yet. I will do that together with the testing of video.
I will try it this evening.
Yes, it's a MK808C.
I have a cubieboard A10 and a mele A1000 (and somewhere a MK808 A20), although I don't know anymore about how much ram they have. I can test and maybe help with development, but I don't know if I will be much of a help...
Can you please update to Leia 18 final version.. waiting since Nov. 2018.
Alexelec has a Leia build for S812 -> Releases · AlexELEC/AE-AML · GitHub. You probably should use that one so Balbes can concentrate at the LE builds with mainline kernel for S905.
What do you mean by "used"? Lima definitively won't be included in Linux 5.1. I'm also unsure if I want to fiddle with patches since it will probably be in 5.2, which is just ~4 months away and I rather spend time on HW decoding.
Just a question as I read on phoronix lima was on the merging list, but it seems it's for 5.2.
Will the lima driver be used with kernel 5.1?
You should do it with dmesg. Did you read this post: Create remote.conf from scratch
Otherwise which remote do you use? Probably there is already a remote.conf for your remote. Look here: remote.conf repository
To all,
meson-ir is not enabled on the Wetek core and I assume also not on the wetek play 1. The kernel is to old and I assume they don't want to implement it. IR-remotes still work the old fashion way with the remote.conf. But I assume you guys are talking about the original remote that is RF 2,4 GHz as far as I now, so your problems will be somewhere else. Maybe you should give detailed problems of the remote and start a new thread.
