The tvheadend43 plugin 12.80.6 could not be found in the arch64 repository.
Hi, if you want to install the TVHeadEnd server (service.tvheadend43), indeed at this moment isn't at the libreelec addons server for ARMv8/aarch64 location. Interesting, the version for ARMv7/arm is present on that server...
Switch my NAS to nfs is like buying a new car because the windscreen got dirty (or, for smokers, because the ashtray is full). Not an option because of this.
The problem with that "windscreen" isn't the "got dirty", was made for another car (SMB -> Windows) and probably doesn't fit perfectly for that car (Linux-LibreElec). 
That's like the eternal NTFS vs. EXT4 debate. When you use something linux based, NTFS drives can be used, but if you don't want trouble, the EXT4 is better. As the LibreElec it's linux based, the NFS probably perform better. The difference probably is "visible" only when the performance is pushed to the limit... Another thing is, most of the NAS able to use the both, SMB and NFS, so no need to change, just to enable a second option...
What are its flaws and does it run the CAM directly or does it require programming, because I do not have enough information about programming?
Hi, Why you don't try it? And if not working provide log. Maybe someone will "see" something in log and would help you.
It’s for non technical users. Asking them to install a program and how to use it is an added complication.
The samba connection, with the latest security updates, user and password, isn't that was years ago. For "non technical users", an option would be to keep the backup file in an USB-stick. Then you could include in the image an autostart.sh file with something like if exist at the mounted USB-stick a specific folder with the backup inside, to start the restore process... I mean once somebody to start the LE with the "backup-stick" connected, and will do the restoring without any remote connection.
BTW, the Filezilla have "removable" package, just unzip and run. Almost the same as a simple file browser.
I’d like to build LibreELEC with preconfigured settings to allow users to access their device via SMB. They could then immediately copy a backup file and restore LE/Kodi completely configured with required add-ons, skin configuration, custom menu nodes etc.
Hi, I'm just wondering, why need to be used the SMB? An SFTP connection with FileZilla, wouldn't do the same job, without the complication of enabling the SMB?
I assume this means I could format the drive as EXT4 on the Libreelec machine by accessing the command interface?
Or just boot from USB a live-linux (ex. any Ubuntu flavour) and use the GParted GUI.
Is there a fix or an older version of libreelec that doesn't have this problem?
Hi, unfortunately perfect solution isn't exist (yet?). It's few options you can try (if you want).
Older LE version. The huge advantage of the RPi is running OS from a SD card. So, take an anther card and try an older release.
Switching to another format type. The best compatibility for linux is the EXT4, but in that case that HDD will be a bit harder accessible with Windows. Workaround exist, like EXT4 "driver" for Windows, or using Linux on the PC: Dual boot or just a live linux from USB. You probably isn't "walk" with that HDD daily between RPi and PC. I'm using EXFAT for this purpose as it's a "portable format" type and didn't had any serious problem with that.
So here too I am forced to use something I don't need. You're one of the funny kind. Not use? Like if I can't disable it?
Nobody forced you to use the LibreElec. It's only your choice if you use it or not. Also it's open source, if you don't like something, you are free to make your own version.
I do not how to install LibreELEC generic in a specific ext4 partition. I do not want to use the hole disk because I have other OSes on it. I use rEFInd as boot manager.
Hi, I think you should think a bit about this. The LibreElec is a minimal Linux OS to be able to run the KODI, intended to be used with devices with limited resources (SBC, mini-PC). So, if you already have a working OS on that PC, why you don't just install the KODI? That would have some advantages, including the far better driver support, simple launching instead of rebooting the PC.
And hey, here I am again. Yes, it's getting slow. However, I have a few questions. Why can't anyone here integrate a translator? I mean, manually it's a bit tricky because my translator is different and therefore another translator translates in a different way than the one from support or moderator, right???
Do you have any real issue with the LibreElec, or just do you like to write many-many rows...
What I already done in the meantime is to also try it at my desk monitor (ThinkVision P27q-10). The problem also occurs there regardless of the connection type (tried DisplayPort->HDMI and DisplayPort directly).
Hi, you should try to run some LE versions directly from USB-stick, and check which is working. Also you can do that with some Live-Linux too. Hint: try the Ventoy and just "drop" the "ISO" or "IMG" file to the USB-stick.
Would be weird to have a hardware issue, but I wouldn't exclude that possibility.
Question is .... what should I look at and where to start?
That issue is known, looks like it's a combination of the weak built-in antenna of the RPi's and probably some bug in the connman or IWD codes. Log files probably should help, but with problematic network isn't easy to make it.
The rock solid solution is to use LAN cable if you can. If not, the second is to use a Wifi-Lan adapter, no needs any driver, it just "translate" the Wifi to LAN cable net. If you have around a Wifi-USB dongle, with a "real size" antenna, you could try it, the question is if the LE have the right driver for it... And if you are already using LE 12.2 version, should try the latest 12.2 nightly. Have included the latest updates.
I have an RPi3B with Wifi connection, modded for external antenna (for this need a very good soldering skill!), latest LE 12.2 nightly, and working fine.
I have all my stuff on a NAS, so apart from librelec/kodi itself there is not much on the sd either way
For LE installation in that case enough 1-2GB space... a 128GB or bigger SSD isn't a waste for this? The gain? 1-2 seconds of booting time? When comparing with the SSD, I talking about a good SD card like a Samsung EVO Plus or Kingston Canvas Go Plus. To repeat myself: But this is only my point of view...
As i reconfigure stuff at home i bought a new case for the space to connect a poe/m2 hat in it (main reason was to try the poe part) and as i have a spare nvme i want to install libreelec onto it and remove the existing sd card.
Hi, usually I like to have the "system" and "data" in two different device. And who had trouble with saving/restoring or even loosing huge amount of data after a "problematic" update/upgrade, would agee with me. I would let the OS (LE) in a good and fast SD card, and storing all of media files on that SSD. But this is only my point of view...
I think another path forward could be git bisecting between 12.0.2 and 12.2.1, although there are ~950 commits between the two tags and I would need to rebuild the image for each bisect step.
Two things you should maybe think about:
1. It's a very big number of users using different RPi versions with LE. If would be a serious bug in LE (connman or IWD) code, here should be a lot of complains about it. But there many people who have working wifi connection. So, if you can't connect at all, maybe the main problem isn't in the LE code.
2. What encryption mode is set on that AP? In the past the RPi wasn't able to handle the WPA3-SAE. I made yesterday a short test because theoretically was improved something in that matter. So, when I tried to connect my RPi3B (latest LE12.2 nightly) to a WPA3-SAE encrypted wifi, ends after some "thinking" time with connection failure. Changed back to WPA2-PSK and LE reboot got connection... I have no time for more test now and I'm fine with WPA2...
AFAIK that's been fixed (worked-around) in RPi kernel code.
The WPA3 should work with the latest 12.2 nightly (LibreELEC-RPi2.arm-12.2-nightly-20260118-553081d.img.gz) or only with the 13.0? (Sorry for off topic)
Any other ideas?
Could be the Wifi encryption "thing"? With the RPi was something that doesn't support the WPA3 encryption, maybe here to be the same? Just for test, try to change in the router to the WPA2 and a strong password.
But I want the device started at boot time and prioritized over the the internal wifi, so i've been trying to increase the open files limit at startup.
Hi, try to add to the config.txt the "dtoverlay=disable-wifi" - that should disable the internal wifi. Also you could increase the "wait for network" time at the System -LibreElec - Network - Maximum wait time.
