Posts by vaughng

blueribb thanks for pointing that out! Didn't even know that was still there.

I've enabled debug logging and persistent logs to try to catch the error. I will remove that pesky repo and update with new logs soon.

When idle for too long, the device hangs. It is unable to take input from the IR remote nor am I able to SSH into it. Here is the pastekodi output that I ran after disconnecting and reconnecting the power cable (the only way I am able to get the device running again). The issue happens at seemingly random time intervals. I am able to watch Movies, YouTube etc. in full HD perfectly fine with no crashes. The issue (so far) has only occurred while the device was idle.

I'm at a loss here, any assistance is appreciated.

Quote from LybsterKodi

Not quite - I just continued running W7. I do have one PC dual booting into W10 or W11 so I can test the s/w written on my W7 PC.

Oh dear. Not judging, but I would hope you at least know the risks involved with running Windows 7 in 2023. Especially if you are connected to the internet or regularly transfer files to and from the machine. I too wish I could run Windows 7 without risk. Commenting because I care about your security. I shall not comment further to avoid saturating this thread.

Glad you got it working!

About this:

Quote from hectobar

My box allready proposes a WireGuard VPN server. And I assume that my LAN is managed by SMB on Kodi.

Do I have simply to install a Wireguard VPN client on Kodi ? What about ports redirections ? Are they no longer usefull ?

"My box" meaning your router or a server on your LAN has a WireGuard VPN server? If I am correct then no don't install VPN clients on Kodi.

Instead of forwarding ports 8080 or 8096, forward your VPN port (51820 by default for WireGuard). The client in this case would be the device you are connecting from (example: your laptop). Then, when you connect to your WireGuard VPN remotely from your laptop (using your external IP or DDNS) you will have full access to your LAN as if you were at home. To use Kodi you would then use your internal I.P address (example: 192.168.0.20:8080) to reach Kodi. Which is secure because the VPN creates the encrypted tunnel, no need for certificates.

However, if you are confused about this, since you have it working already you may be better off looking into the certificates option.

Port forwarding is a bad idea unless you have your instance secured. Please look into the following before forwarding any ports:

1) Adding certificates to Kodi (self-signed or using letsencrypt)

2) Disabling SSH OR adding SSH keys and disabling SSH password (not an issue if you aren't forwarding port 22)

3) Setting a secure password for the web interface (changing the username is also a good idea)

If you don't set up certificates, your password will be sent in plain text (unencrypted).

Alternatively (and probably the safer option) look into setting up a WireGuard (VPN) server on your local network and port forward to that instead, then you have remote access to your entire local network, secured by a keypair. I haven't tried using Kodi over WG so I cannot speak for performance.

Quote from petediscrete

And that’s exactly how a project like LE continues to evolve. Research and contribute. Maybe you should research a little deeper before asking the question in the first place.

I always try to do this. I end up doing more research than I have time for, posting the question because I'm at my wits end and then solving the problem immediately after posting the question.

To be fair, I was even more confused by the difference in behaviour between devices and found many instances online of people who never solved similar issues this gracefully, or at all. The only solutions I found were messy retry scripts (what I was trying to avoid). Maybe I was asking the wrong questions? I have noted your comment and will try harder next time, but I'm kind of glad I didn't for this one because at least it's on the internet now and not just in my head.

Long live LibreElec!

I have a history of answering my own questions on this forum but here goes.

I found this in the Linux man-pages. It's not quite a retry in the sense that it will continuously retry until a connection is made. However, it does work as intended and here's why:

Because we enable the automount service, we can disable the mount service. Which in turn allows the system to boot without errors, even if the network share is not available (it will still show the files as missing until the share is available, but this is expected). What the automount does is try to connect to the network share when the local mount folder is accessed by the filesystem. So when trying to play media from the mount folder, or trying to update the library (assuming the mounted folder is in your media library). Including instructions below in case this helps someone.

After following the LibreElec documentation for mounting network shares here you end up with an enabled systemd service called storage-recordings.mount (following the example from the docs).

You need to disable this service:

systemctl disable storage-recordings.mount

Create the automount service:

nano .config/system.d/storage-recordings.automount

With the following contents:

[Unit]

Description=NFS Automount for Recordings


[Automount]

Where=/storage/recordings

TimeoutIdleSec=0


[Install]

WantedBy=multi-user.target

Enable the service:

systemctl enable storage-recordings.automount

Finally reload the daemon to apply changes (or alternatively, reboot the system):

systemctl daemon-reload

Voila! No more fuss about network shares.

To preface, I am running LE 11.01 on 2 devices being a Tanix TX6-A and a Raspberry Pi 4. I am experiencing 2 different issues but I believe they fall in the same category.

I have 2 NFSv4 shares exported from a server on my network. I am from an area that experiences regular power outages and the server that exports the NFS shares does not turn on immediately (there is a delay after power returns due to a surge protector). These shares are mounted using mount files and systemd as per the LibreElec documentation.

The Raspberry Pi 4 halts boot after the NFS shares fail to mount and stays in text output (Kodi doesn't start) until the server is running and I reboot.

The Tanix TX6-A boots successfully into Kodi but reports that the files are missing (even after the server is turned on - I presume it does not retry the mount) until the server is running and I reboot.

Even if the server did turn on immediately I'm fairly certain LibreElec will fail to mount the shares before the server completes it's boot sequence. Is there any way to combat this? My only solution would be to script something to check whether or not the server is exporting the shares before connecting but I'm not sure how well that would work. I'd like Kodi to start regardless (like how the Tanix TX6 behaves and mount the share when it's available (if that's possible).

Found this post by jernej that answers my question. Sorry for spam, will just have to wait for mainline kernel support!

My mistake!!! This does not seem to be a TX6 Mini but rather a TX6-A. Did not realize they shared the same WiFi chip. Mods please assist in changing the title.

Also disregard anything I've said in the post regarding previous TX6 Mini threads as this obviously is no longer relevant. The WiFi chip seems to be the main not working thing they have in common.

Hi,

I've seen much older threads discussing the topic but nothing conclusive. Is there official support coming for the TX6 Mini? It's not in the list of downloads and the only image I found is referenced from another thread (marked as experimental). I would like to load LibreElec on the EMMC and be able to get updates without flashing again, is this possible?

Tested with the official TX6 image and it seems to work fine just no WiFi (have not tested the remote as I can't seem to find it... but I suspect I will have the same issues another user outlined here as I presume the TX6 remote config has to be overwritten).

Also is DT patch still needed to get higher GPU frequency? Not that I know what the DT patch is or how to apply it, just wondering if it made it's way into a release yet.

My device is actually a replica, branded "BAOBAB". Seems to be mostly the same as the TX6 Mini (sticker says TX6-A as well). The main difference I could see from an image someone else linked is the little LED type screen on the front. Attached some images.

Apologies if I've missed something, new to LibreElec. Just wanted to breathe some safe open source life into what was probably a virus filled TV Box. Figured I'd post here to see if we can get WiFi working before I start running cables through the ceiling...