Posts by jernej

difference is only if CEC protocol is completely implemented in software (algorithm in kernel determines when pin goes to 1 or 0, determined by timer) or in hardware (driver only reads what message was received or sends one out). Obviously, you want hardware to do as much as possible, as that leaves CPU to do better things. Also, time sensitive events, like when pin has to go to 1 or 0, are completely done in hardware and thus not dependent on CPU load which might introduce some lag.

So, it's interesting to me that software implementation works better than hardware. Usually, it's other way around. Only explanation for that is 32k clock accuracy, which is used by HW CEC implementation for timing events. But I don't see a reason why that would be a problem. Maybe you can confirm that indeed dedicated crystal is used by executing devmem 0x01f00004 w. It should have value 1.

Best way to determine what happened would be to first find PR on github which broke HW CEC. That could be done via git bisect.

Well, I'm glad it works for you, but that's just workaround. It uses software implementation of CEC instead of HW. It would be great to figure what's wrong.

It should be able to play 4k HEVC files. In theory 4k H264 should work, but not smoothly. Note that 10-bit formats are not supported in HW. OrangePi PC has only 1 GiB of RAM, most probably that's the issue.

What do you mean by "board restarts"? Are you sure whole board restarts (there should be LibreELEC logo shown) or only Kodi restarts (only Kodi logo is shown)? Please enable Kodi debug logging, execute pastekodi via ssh after the issue is triggered and provide link here. It should provide enough information to see what the issue is.

Edit the patch (you can do that directly, just replace any board name with yours), build the image and update your current system with it.

If done properly, you should see different CEC driver name.

I have no idea what could be wrong with CEC. As you said, not much changed. Ideally, you should try to bisect changes and figured out which PR caused the issue. Most likely it will be a kernel update.

You can check if changing board name to "xunlong,orangepi-pc" at https://github.com/LibreELEC/Libr…r-H3.patch#L191 mitigates the issue.

Can you confirm that this is really Tanix TX6 with H6 chip and not Tanix TX6s with H616? First is supported, later is not. If in doubt, you can open the box and look under cooler.

Ok. Driver is in staging and it seems that it doesn't use much of linux wifi kernel side framework, on which iwd relies heavily. Sorry to say, but it seems that driver is not iwd compatible. TODO.txt in kernel says this:

A replacement for this driver with MAC80211 support is available
at https://github.com/chunkeey/rtl8192su

So it may be possible that driver mentioned above is in fact iwd compatible, but as a team policy, we won't add any out of tree wifi driver.

Quote from lomion

Error /net/connman/technology/wifi: Method "Scan" with signature "" on interface "net.connman.Technology" doesn't exist

I got same error when iwd refused to start due to some missing driver. Can you check iwd service status with systemctl?

Quote from crisofter13

So introducing only the sd already starts from libreleec automatically?

Yes, SD card has higher boot priority than eMMC, so booting from it works automatically.

Note, I got reports that USB-SD creator app doesn't properly flash images to SD card, at least in some cases. If it doesn't work for you, try alternative apps like balerina etcher or just dd (if you're using Linux).

Quote from crisofter13

Once it boots, I also want to leave libreelec installed in the device's memory, I understand that to do that I have to do it through SSH (putty)??

Yes, using install2emmc command.

USB isn't supported as boot device by SoC. You have to use SD card as intermediate solution.

GPU frequency scaling is still not enabled on LE11 for TX6...

Quote from Glennza

The RTL8821 driver has been in the nightlies for quite a while.

Generic yes, RPi, for example, no.

LE11 will keep 6.1 kernel, but master branch, what will eventually become LE12, will see kernel updates. Usually we are pretty quick to update, but 6.2 update stalled a bit (at least I have issue with network on OPi3 LTS board with 6.2).

Anyway, RTW88 USB and, for some boards, SDIO patches were backported to 6.1 and are present in LE11. Which board do you use?

Quote from frakkin64

I believe the main reason it is in Allwinner builds is because some of the boards are using the SDIO-based rtw88 chips.

That's true. However, patches are placed in such way, that driver is present in every project, except Amlogic and RPi. They use different kernel source.

Anyone can, but there is very limited documentation within build system. There is no other way than to "dig in" build system and learn by trial & error.

Main reason why LE team decided not to add each and every wifi driver to official image is because it's annoying to keep these wifi drivers buildable and working across different kernel versions. If you have luck, someone already published driver sources for currently used kernel version and all you need to do is just write package.mk file which points to those sources. If not, you have to also create patches to fix build and/or working issues.

No, I very much prefer public conversation. PMs are mainly for rare cases, like sharing video samples (some people are afraid of this due to copyrights), for example.

eh, it's blkid

That error usually indicates that your partition UUID doesn't match. Why does that happen I can't say, I don't use LE SD creator. I use dd on Linux, which writes image 1:1 on SD card and I never had any issue with it, although it's pretty dumb tool (thus not ideal) and it doesn't verify if everything has been written correctly. In any case, you can override UUID in extlinux.conf. Before you do that, get current UUID by executing "lsblk" in that emergency console. Check for ext4 partition.

While I didn't test LE11 final on OPi3 LTS, I tested clean install of beta and it worked as expected. I don't have any reason to doubt final release. Nothing changed in that regard.

EDIT: eMMC install script takes care for UUID update. So once you're able to boot SD image, installation to eMMC should be straightforward and without issues. Note that this means you'll lose everything there. No backups are made.