I want to try it and see if the Kodi menu will not be faster. Now that menu in kodi is jerky with late response.
It will be the same on eMMC and SD card. What needs to be done is to enable GPU dynamic frequency scaling, which is actually already possible but not enabled, because it's untested. In order to enable it, DT patch is needed. This way, higher frequency can be set, which allows for smoother animations.
It's hard to determine correct RX and TX delays, which are needed for good or even stable performance, due to different PHY drivers in various forks.
Can you please test this update? http://jernej.libreelec.tv/test/cec/
I removed kernel patch which produces dw_hdmi_cec_hardirq: stat=11 LOW_DRIVE. I'm not sure if it's really needed.
Probably not for all hardware
They are in default patch set. So yeah, not applicable for RPi and amlogic, but for everyone else.
They are not in RPi, but I pulled the rtw88 USB patches + fixups in and tested them.
Where did you pulled them from? You should apply rtw88 patches from https://github.com/LibreELEC/L…ges/linux/patches/default
The USB drivers cause lock-ups and performance (~100Mbps via iperf) is worse than out-of-tree modules (~270Mbps).
In aforementioned patches is a lot of locking fixes but hard to tell if a additional fix is needed without dmesg output. Performance is lower, since USB (and SDIO) transport part of RTW88 driver is community driven, but you have to start somewhere. In any case, this is best that you'll get, out of tree drivers are rejected for a reason.
dootsie5times USB rtw88 drivers were merged in 6.2 and were backported to 6.1 in LE, so they are present in current LE11 nightly images.
No problem. Fortunately, LE11 stable is not too far in the future. No ETA though.
malat can you try LE11 nightly?
Yes, you just need to add additional CPU operation point, either by editing DTB file or via DT overlays. Why would you want overclock your board? It doesn't give you much benefit for LE purposes.
I could use a nudge to to understand how to get VFD working on Tanix TX6. I understood openvfd is not an option for LE anymore.
I suggest that you take a look at this snippet:
Randomly at reboot (the very first one after resize for instance)
I hoped nobody will experience that. I got such issues when RSB bus was clocked at 4 MHz. I lowered that to 100 kHz and never observed such issue again. I guess I could lower it still. I'll prepare test dtb file, which you can just replace on SD card for testing purposes.
Analog audio output not available.
It's stated in OP that H6 image doesn't support analogue audio. Driver is missing. I wrote one, but due to configuration issues, I never PRed it. I guess it's LE12 material.
Just for my understanding, if the WiFi chip get supported in the mainline Linux kernel in the future, should it be supported by LE?
Yes, but chances for that are low.
I obviously found time today, check: RE: Nightly images for A64, H3, H5, H6 and R40 boards
Here is test image for OrangePi 3 LTS. It doesn't and it won't support wifi, but ethernet should work fine. Please test:
From tomorrow on, there will be nightly images too.
From previous answer I have understood that in case of TX6 Libreelec uses 64 bit kernel for aarch64 architecture and 32 bit userspace for running 32-bit widevine library needed fo netflix/amazon etc. Am I right?
Yes.
I'm curious how to use widevine with pure aarch64 kernel and system. The purpose is very simple: I want to do the same for archlinuxarm TX6 project. They released 6.1 aarch64 kernel and uboot which run quite well on Tanix TX6. The only one problem that kodi can't run widevine with "Unsupported 64-bit userspace found. User needs 32-bit userspace on arm64".
You can't use 32-bit widevine with pure 64-bit system. You would need to build or install 32-bit Kodi and all needed libraries by Kodi and their dependencies and so on, down to glibc. So in short, you would have 32-bit system along 64-bit one. Under Linux, you can't mix 32-bit and 64-bit apps and libraries. Same thing is true on x86.
Not sure what you want to know. It's only difference of building LE with PROJECT=Allwinner ARCH=arm DEVICE=H6 UBOOT_SYSTEM=tanix-tx6 make image for 32-bit and PROJECT=Allwinner ARCH=aarch64 DEVICE=H6 UBOOT_SYSTEM=tanix-tx6 make image for 64-bit. This only changes compiler and adjust compiler flags, so 32-bit compiler is used instead of 64-bit.
1) Sure, you can use whatever USB wifi is otherwise supported on Linux. Note that it's good to do a little research before you buy wifi dongle. Dongles, which have no mainline driver, are not supported in LE. If in doubt, tell here which chip is used and I can check.
I have LTS version. I'll try to fix ethernet before LE11 stable is released, but no promises.
tested latest LibreELEC-H6.arm-11.0-nightly-20221203-164bd92-beelink-gs1.img.gz, still unable to boot, same error.
Sorry for late response, but obviously I took some time off LE. I'll surely work on this issue before stable is released.
Is openvfd module included in kernel for Tanix TX6 in development release?
No, but I2C bus is exposed and you can write script to drive display. I have some python script example, but it wasn't tested on LE. I can provide it to you as example, if you want.
Do the nightly images for the H6 include phy ethernet driver support for the Orange Pi 3 LTS?
No.
How it can be possible? What mechanism or tricks do you use?
Simple. While kernel is really 64-bit, userspace in 32-bit. In fact, widevine is the only reason why we release all ARM images with 32-bit userspace.
I'm not expert in passthrough at all and I only test it with video playback. I suggest you ask this in more general subforum.
