scott Following Tanix TX6 image should have working multitouch HID driver. Can you test it?
libreelec-h6.arm-9.80-devel-20190706153642-8d13dbf-tanix_tx6.img.gz
Posts by jernej
-
-
pinexxx Difference with Armbian and LibreELEC is that here we always use latest kernel, while Armbian is often a release or two behind.
If you spot any possible solution on any forum, please tell me and I'll prepare test image before including it in official LE. Ethernet drivers are one of those things which I don't have much knowledge about and I can only hope someone will publish a fix or at least a workaround.
-
gamma-271 logs are fine (no indication of any issue) and another developer confirmed latest nightly works with his OPi One+ board.
I have a feeling there is some kind of issue with 1080p resolution. My 1080p PC monitor sometimes doesn't work well with H6 boards, while my 4k TV never had any problems, including with 1080p resolution.
Can you test this board on any other TV/monitor, preferably with different native resolution (doesn't matter if lower or higher)?
-
I don't think you can do much else, unless you would like to help developing kernel drivers.
-
My source from git did not have this edit. So I also modified line 137 in the patch as shown above and rebuild the image.
That change is not needed anymore due to upgraded libdrm.
As I actually don't own any A20 board and have no experiences with that SoC I can't really help you much more. Maybe majorkalina can push a changes needed for BananaPi Pro?
-
sun7i-a20-bananapro.dts
I forgot to mention, it has to end with .dtb, which is compiled version of .dts
-
Just be aware that there is a reason why A20 images are not included in LibreELEC master github repository - it seems that display driver has a major bug, which in certain situations garbles image on screen.
With that out of the way, let's continue with BananaPi Pro. I didn't add support for it yet, but you can easily edit uboot_helper and add similar line like that I marked. Name doesn't really matter, but it's nice to be consistent with board name, like bananapi_pro. Second field is the name of device tree file in Linux kernel for your device and third one is U-Boot defconfig file name for your device.
Anyway, command for building A20 images is similar to H3. Just replace SoC name and board name (assuming you used bananapi_pro):
CodePROJECT=Allwinner ARCH=arm DEVICE=A20 UBOOT_SYSTEM=bananapi_pro make image -
warchild Can you tell which resolution is used in both cases?
-
warchild I flashed above image again and it works for me. Can you try with another TV or monitor first? Then try another HDMI cable. If it still doesn't work, it would be great if you can provide log from serial port.
I wouldn't recommend overwriting Android just yet. There is pretty high chance it won't work either.
-
-
Display More
I think, in the file
https://github.com/jernejsk/libre…ces/a20/options
the line 41
https://github.com/jernejsk/libre…a20/options#l41
ADDITIONAL_DRIVERS="$ADDITIONAL_DRIVERS gpu-sunxi"
is obsolete.
Fixed and rebased on latest master, which brings Kodi 18.3.
-
That was already asked and has answer here: LibreELEC (Leia) 9.2 ALPHA1 with Raspberry Pi 4B Support
-
The only problems I have found, is that the eth isn't working; or It's very very slow when It tries to connect on internet. I can ping any IP and domain name; on my LAN it works properly, but for example It can't download any addon updates because It's very slow and than goes into some error.I fixed this problem by using an usb eth adapter.
Are you sure that you're using image for Pine64+? In the past, people mixed up Pine64 and Pine64+ images, which mostly differ just in ethernet settings. However, I vaguely remember that some Pine64 boards had ethernet issues, which was connected with Realthek PHY chip used on board. There is workaround, but it never made to mainline kernel and I didn't include it here. Maybe it would help you, but any change like that might break other boards...
The second problem It occurred to me is that every time I shutdown my tv, or I switch the tv source, libreelec crashes completely. In order to avoid this problem I'm forced to stop the kodi.service unit, from ssh, before shutting down my tv. Of course, when I want to use it again, i have to start the kodi.service. I'm using termux on my phone, so It's a very easy task.
What you really need to do is to change your HDMI CEC settings in Kodi Input options. Just disable hibernation on source switch or TV shutdown and you'll be fine. This would be a feature if we would have an ability to wake up from CEC, which BTW is possible, but it's in distant future (using AR100 coprocessor).
Anyone know is the H6 faster than the BCM processor the RPI 4 has?
If you mean raw CPU speed, then RPI4 is faster. However, H6, for example, supports HW decoding 4K H264 videos and it's able to HW decode more codecs.
You also have to know that a lot more people work on RPI4 than H6, so yes, you will get features faster. Although I already made HDR demo for H6
-
how far away do you think panfrost is for H6?
It will still take some time. T720 is still not really supported by panfrost. Anyway, this issue doesn't seem to be driver related but more like power related, e.g. find correct mix of frequency and voltage. I'm using that from Android, but for some reason, it doesn't work well... But I might be completely wrong about that and may be indeed driver related...
-
gamma-271 Can you test: libreelec-h6.arm-9.80-devel-20190701201203-8a8e6a1-orangepi_one_plus.img.gz ?
It seems that Mali causes system lockups if it doesn't run on lowest setting... I'll need to investigate this further.
-
djnice you actually don't need anything special to combine U-Boot with rest of the image, just SD card reader/writer.
But for sake of simplicity, here is latest Tanix TX6 image, which should work with most cheap H6 STBs (ethernet and few other things still don't work):
libreelec-h6.arm-9.80-devel-20190701192544-71813d9-tanix_tx6.img.gz
-
A64 and other images will be rebuild in in several hours, so wait until then. H6 images are slightly broken and I'm working to fix this, but it will probably take few days.
-
OK, its working now.
Maybe it was the VM or the laptop, but after reboot it is how supposed to be.
Kodi started, so all good.
Ok, great! Thanks for your patience.
