Fix was trivial. Will be included in next system-tools. No need for six.
Some quick checking - this is the module - https://kodi.tv/addons/matrix/script.module.six/
Add six.py to the addons
cd /storage/.kodi/addons/virtual.system-tools/bin
wget https://raw.githubusercontent.com/benjaminp/six/master/six.py
Does not seem to help, as dstat seems to need some further python3 patches.
# dstat
You did not select any stats, using -cdngy by default.
Traceback (most recent call last):
File "/storage/.kodi/addons/virtual.system-tools/bin/dstat", line 2825, in <module>
main()
File "/storage/.kodi/addons/virtual.system-tools/bin/dstat", line 2684, in main
scheduler.run()
File "/usr/lib/python3.11/sched.py", line 151, in run
File "/storage/.kodi/addons/virtual.system-tools/bin/dstat", line 2782, in perform
line = line + o.show() + o.showend(totlist, vislist)
^^^^^^^^
File "/storage/.kodi/addons/virtual.system-tools/bin/dstat", line 515, in show
if isinstance(self.val[name], collections.Sequence) and not isinstance(self.val[name], six.string_types):
^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'collections' has no attribute 'Sequence'Edit dstat and change “import collections” to “import collections.abc”
And “collections.Sequence” to “collections.abc.Sequence”
dstat is unfortunately a archived project. https://github.com/dstat-real/dstat So whilst the above will get you going - not sure on longevity.
This photo probably shows it clearest.
https://www.pulse-eight.com/generated-assets/products/0000381.jpeg
Control your TV from Kodi, or vice versa! USB - CEC Adapter
HDMI IN (to PC)
HDMI OUT (to TV)
DATA - this is the USB and allows Kodi/LE/Kernel to read/write CEC.
I have the internal versions which behave exactly the same way (except the HDMI IN-OUT are on those AA pins.) the other connection in the NUC manual is for the USB 2.0 that the pulse8 is connected to. [DATA above]
It shows up here
nuc11:~ # lsusb | grep Pulse
Bus 003 Device 003: ID 2548:1002 Pulse-Eight CEC AdapterThanks - this is reminding me of IBM 4341 mainframe assembler - that made my head hurt as well.
Yup. You’re in the right mindset now 
This is probably the best answer once you deal with the hardware purchase. - “The Kodi implementation of CEC isn’t too bad - doesn’t do everything but depends on the special/corner cases you are trying to solve.”
I probably paint a more pessimistic picture than the normal use case. But I was trying to do all that crazy
Display MoreFirst, thank you for trying to help. However, as you can guess I'm not going to opt for a sat>IP tuner and I really don't care about 4KUHD (at 72 I've seen enough overhyping, but to be fair moving from SD to HD in the US was a big deal, not so much in the UK, and please do not get me started on about PC screens that need to be at 200% to have readable text).
I'll have a look at the Rock machines and see if I can find any performance comparison.
Thanks for that - it explains the very limited command set table
At least I now have some idea where I'm going and the fact that I'll need to add £40 to my budget for the Pulse8 USB adapter
Out of interest is there any usable documentation regarding CEC out there - if there is I was searching for the wrong terms.
Some reading on CEC when I was puzzling it out.
It will lead you down many rabbit holes. Note: it all “might” work (and it all doesn’t) lots of caveat. But as a project it was a good learning - though deep. And my requirements were complex. Since then I have replaced much of the AV equipment - TV, AVR, NUCs - but the other hangers on are still there and work.
My advice is if you do end up chasing the rabbit - I did. You may need to run a customised image (I have been upstreaming much - but some of my corner case automation stuff is not suitable for upstream.)
I'm going by this information for the NUCs
https://www.intel.com/content/www/us…l-nuc-kits.html
and looking only at the onboard CEC section.
How good is the Pulse8 adapter I've found mixed views about it whilst driving myself insane about CEC.
The onboard CEC is very specific [read as - limited / useless / crippled] - it is bios based. There is a WMI exposure to the operating system via ACPI. You will not see it in LE when you start LE. I have been working on CEC / HA both in a LE development capacity, home automation and commercial automation for a few years now. Yup - CEC - leaves a lot to be desired. The Kodi implementation of CEC isn’t too bad - doesn’t do everything but depends on the special/corner cases you are trying to solve. Note: LE/Kodi does turn my TV and AVR on and off - but not via CEC. Note: I also don’t use libCEC but use the kernel CEC.
But answering the question around the internal NUC “Pulse8” - it works fine. Caveats on CEC based on my commentary above - - I’d love it to make toast - but it ain’t going to.
The last sentence copied from https://www.intel.com.au/content/www/au…l-nuc-kits.html gives it away
The following Intel® NUC Kits have the above external CEC header and an onboard HDMI CEC controller that the BIOS controls. The onboard HDMI CEC controller only supports bidirectional power on/off control:Be careful on the “NUC supports CEC.” Only some do. And only fully with the pulse8 adapter. (I have a full herd of them 6,7,8,10,11,12)
Page 18 - section 3.1.1 - ref: AA in the below PDF
https://www.intel.com/content/dam/support/us/en/documents/intel-nuc/NUC11PA_TechProdSpec.pdf
Not all have this connector (my nuc12 does not have)
LibreELEC 11 uses the ntfs3 kernel driver that was mainlined in kernel 5.15 (https://lore.kernel.org/lkml/CAHk-=whF…mail.gmail.com/) Whereas LibreELEC 10 and before use NTFS-3G (Fuse) https://en.wikipedia.org/wiki/NTFS-3G
So the results will vary.
I see the error in your dmesg - it refuses to mount the disk because of “May 20 21:33:05.643108 LibreELEC kernel: ntfs3: sda2: volume is dirty and "force" flag is not set!”
The kernel ntfs3 driver if probably being more pedantic. There are no ntfs3 chkdsk tools released - thus the reason for “needing to Chkdsk /f on the windows machine.”
Note: I have test exfat and ntfs3 disk always connected to a test libreelec (and see some issues - joys of running prerelease kernels and software) but not the dirty issues being reported. Very rarely will I force shutdown my LE operating system. Plenty of reboots.
Display MoreWhen browsing a large library it should change from going through each item to jump each letter instead.
AItem 1
AItem 2
AItem 3
after 3 seconds, change to the next letter for faster browsing
B
C
D
E
I hope I´ am clear enough?
Does right, then down - not achieve this?
I can see your wlan0 device.
Can you try to see what ssid you can see.
iw dev wlan0 scan
Do this first the link is pointing wget to the read only disk.
rm /storage/.config/firmware/brcm/brcmfmac4330-sdio.oranth,tanix-tx6.txt
You can check if this changes/fixes the wireless with the bcm4330
mkdir -p /storage/.config/firmware/brcm
cd /storage/.config/firmware/brcm
ln -s /lib/firmware/brcm/brcmfmac4330-sdio.bin brcmfmac4330-sdio.oranth,tanix-tx6.bin
ln -s /lib/firmware/brcm/brcmfmac4330-sdio.txt brcmfmac4330-sdio.oranth,tanix-tx6.txt
rebootCan you please confirm the model number on the bottom.
As I believe this is not a model I have/have tested. Mine both use the rtw88 driver.
[ 5.943731] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4330-sdio for chip BCM4330/4
[ 5.943879] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac4330-sdio.oranth,tanix-tx6.bin failed with error -2
[ 5.944689] usbcore: registered new interface driver brcmfmacLooks like there is a fix/workaround patch that works with kernels 6.1+
The most recent LE12 nightly is running the 6.3 kernel and if you were going to test - I would suggest it +/- the patch.
As the iwlwifi firmwares were updated to version 74 with kernel 6.3
2 more commands please (as without the “| cat” the log isn’t showing the whole error)
ldd /usr/lib/dri/iHD_drv_video.so
systemctl status kodi | cat
LE10 won’t receive any chrome updates from the addons.
Will need to look at doing a chrome update in LE11.
I think I might have stumbled on why there are issues with older intel video cards (well I hope)
Can you please run these 2 commands (on the not working device) and share the output with me.
systemctl status kodi
ldd /usr/lib/dri/iris_dri.so