Posts by chewitt

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.

Not possible as 100% (255) is the maximum allowed value. There are probably ways to use alsa plugins to reroute and boost the audio signal in some way, but that's not something I have any experience with or want to research; Google searching alsa config topics is always a rather miserable task.

List audio devices:

RPi5:~ # aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: vc4hdmi0 [vc4-hdmi-0], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: vc4hdmi1 [vc4-hdmi-1], device 0: MAI PCM i2s-hifi-0 [MAI PCM i2s-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

In my case this is an RPi5 and I'm using the HDMI-0 connector (nearest the PSU) which is vc4-hdmi-0 .. so 0 is the card.

List simple controls available on the device:

RPi5:~ # amixer
Simple mixer control 'PCM',0
  Capabilities: pvolume
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 255
  Mono:
  Front Left: Playback 255 [100%] [0.00dB]
  Front Right: Playback 255 [100%] [0.00dB]

Using amixer to reduce the volume to 80%:

amixer sset 'PCM' 80%

Checking:

RPi5:~ # amixer
Simple mixer control 'PCM',0
  Capabilities: pvolume
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 255
  Mono:
  Front Left: Playback 204 [80%] [-10.20dB]
  Front Right: Playback 204 [80%] [-10.20dB]

More granular control is achieved using amixer set commands and using amixer controls and amixer contents to understand what can be set and what current values are. The alsamixer tool just provides a console GUI onto the same capabilities.

I'm not sure we can set/store the changes in a persistent way, but the workaround is to use /storage/autostart.sh scripts or (better) a systemd service to run commands on boot. The example WireGuard service in /storage/.config/system.d/ shows an example of running connmanctl commands to start a connection. You can adapt that to run amixer commands, and schedule dependencies so the service runs after alsa is setup (sound.target) and before Kodi runs (kodi.target).

I got rather distracted with some recent discoveries on the hardware decoders. I need to circle back and cherry-pick the older device tree and then do some fixups for changes; some of the kernel bindings have evolved since LE11 days.

Quote from Cissou

it works, but I need to do the command every boot

Then you need to script the commands to execute on each boot. This is best done via a systemd service as this gives you precise control over dependencies and scheduling, e.g. after bluetooth is up, and before Kodi runs.

(
DATETIME=$(date +%Y%m%d%H%M)
sleep 60
journalctl -b 0 --no-pager > /storage/journal-${DATETIME}.log
}&

Create /storage/autostart.sh with that ^ content and reboot, and it will dump the systemd journal to /storage/journal-xxxxxxxx.log one minute after booting. If it fails to connect, note the minute, then reboot until it does connect and then login to pastebing the log from the console. I doubt the log(s) will show anything useful though.

The LE settings add-on can be accessed from Kodi settings if using the default skin, else it can be found under: Add-ons > Program Add-ons > LibreELEC settings > Network > Wireless Regulatory Domain.

No errors reported in the log so I'd assume rtw89 is working to the best of its abilities. The one thing to check is setting the Wireless regulatory domain in the LE settings so the radio properties are aligned to the domain set in your router. Sometimes (but not always) the router advertises it and the driver auto-adjusts to match, but I don't see that in the system log, so either the driver doesn't support that kernel capability yet or the router doesn't advertise.

"lspci -nnk | paste"

TBH i've no idea what "internal volume" means. I'm not all-knowing on Kodi topics, but in all the years I've been hanging around this project i've never come accross that term/concept, and I don't recall any similar report in the forum. I also use Airplay several times per week (for many years, currently on RPi5, before on RPi4, before on RPi3B, etc.) and I've never experienced that. That's not to say it can't happen, but if it was a common thing we'd know about it through user complaints.

On some minimal remotes you need to press the OK/Enter key to bring up the OSD and then navigate to stop. The solution to that is using a less minimal remote with an actual stop button.

The only update in recent weeks is LE 12.0.0/1 to 12.0.2 and testing whether that changed anything (not impossible but unlikely) is easy to test by rolling back to the earlier version.