Posts by chewitt

Quote from THRobinson

Resolved... one of those cases where it was two problems at the same time,

PEBKAC

Deprecation is normal and nothing bad (hence it's a warning in the log, not an error). It's a necessity for handling a diverse set of clients. OpenVPN won't upgrade the connection from CBC to GCM but the initial handshake exchanges a list of what's supported and then the client will negotiate with the server on what to use; generally starting from best to worst.

It's simple enough to start an OpenVPN connection on boot using a systemd service. You can crib the process from the WireGuard service sample in /storage/.config/system.d.

Quote from Elicity

That only leaves CEC afaict to get a functional kernel.

Most of the codecs aren't upstream yet either.

I'm not sure what the underlying issue is, but the workaround will be to redirect the output of sed to a new file and then move the new file to the original filename and perform the change in two steps not one.

Does the fritzbox samba server log anything?

If you have torrent file renaming issues .. Your problem is not our problem. Go read forum rules.

Renaming the Kodi folder won't delete them, but a clean install has no Docker add-on or known Docker config so they aren't going to start on boot until you reinstall the add-on and restore add-on config.

https://github.com/LibreELEC/LibreELEC.tv/pull/7864 tracks support for RK3588 and RK3568 and I guess when the kenel has some kind of meaningful support for RK3528 the scope will be expanded: right now there's the bare minimum of support upstream and nothing that would be usable with LE. As a general rule, RK releases some new fancy chip that internet reviewers fawn over for having amazing hardware specs, and then you need to wait 2-4 years for the upstream kernel to actually support all the bits that LE needs (audio, HDMI, media codecs, etc.).

If you want something that ships today with excellent software support, get an RPi5. You won't win bragging rights down the pub for hardware specs, but it'll be boringly excellent for watching movies.

Like everything related to OpenVPN, you add the line to the client conf you are using. If the whizzy add-on does some kind of magic in the background to make things easy (in reality probably making it more complicated) then you need to ask the add-on author for support. Perhaps it supports some kind of override logic? - I've no idea about it, and have no interest to explore it.

ciphers AES-256-CBC                  <= remove this
data-ciphers-fallback AES-256-CBC    <= add this

See if that ^ works?

S905W2 is a newer generation chip that has zero upstream kernel support. I've no idea if CE supports it, but LE does not.

If there's a suspicion on Goom, a couple of things to experiment with:

a) Switch to another visualisation for a few days. If the issue still happens it's not specific to Goom. If it doesn't it points the finger more firmly towards Goom.

b) Change Goom settings to manual and work your way through the list of individual visuals. Each one uses different shaders so can potentially result in different behaviour. The theory is that something in the shaders (which have seen quite a bit of change for K22 might disagree and cause issues. See if you can pinpoint specific visuals that cause problems.

NB: I've also seen the errors related to ID3 tags, but if the software is flagging those issues it suggests it's reading the file and then reporting; which suggests gracefull handling of those issues and thus (IMHO) they aren't likely to be the cause of a crash.

Feb 28 16:21:02 LibreELEC kodi.sh[1025]: ERROR: Unable to create GUI. Exiting

Something is wrong between mesa and the GPU so there's no DRM/OpenGLES surface for Kodi to render the UI into, so nothing overwrites the boot splash, thus giving the appearance of a boot hang, although that's almost never true.

See if the Generic Legacy (which uses X11 not GBM) works any better.

Quote from dikov

What filesystem for a large storage then many people use? Since I am a Linux guy, I need best compatibility with it.

LE supports all the main kernel-native filesystems and EXT4 is our "generates no support issues" default. If you want more advanced filesystem options perhaps look at XFS or BTRFS (which also has a userspace tools add-on) but very few people use them and on that basis I can't make a glowing recommendation. If you want or need software RAID or JBOD features you'll need to build a custom LE image with different kernel options set, or perhaps use sky42 community image for encrypted storage which includes the bits of devicemanager plumbing we omit from the main image.

I stopped recommending Intel hardware years ago due to the endless shenanigans involving LSPCON chips in the HDMI chain and the general inability to triage and fix issues. I've no experience with AMD chips, and anything with an nVidia card still has no clear roadmap to proper GBM support. The current no-brainer recommendation is an RPi5, but you object to that for some reason. So I'll post this again ..

I'm not seeing a specific reason for anything crashing in logs, and I'm able to play mp3 files for an extended period on an RPi5 with Goom running in the background. If there was a general issue, I'd expect to see more problems being raised, and there's nothing here or in Kodi github (haven't look at their forum, but..).

So

Completed.

Quote from dikov

I was curious lack of support of ZFS in LibreElec (is there any reason for that?)

We intentionally omit all forms of software RAID to reduce the scope of what we need to support and maintain. ZFS might interest a small number of people, but it's a small number. The remaining 99.9995% of our userbase has no clue what ZFS is or how to use or benefit from it's features. There's no objection to someone packaging ZFS as an add-on, but it's not for the core distro.

No ideas on the build issue .. not something I personally have time to look at right now, but others might comment.

There's nothing in the logs related to wireless other than rtw89 driver probe/load and some basic radio info from iwd. You can see connman cycling through some device up/down states, but that's not abnormal. I can't see any attempt to associate to a network in the log.. but that could be for a multitude of reasons.