If "reboot" command works from SSH, then it's probably just a configuration issue.
Posts by Da Flex
-
-
If I grab a modern pci-e card is it likely to just work?
If it's too modern, then it might fails. Something like Intel AX200 should work:
https://www.intel.com/content/www/us/en/support/articles/000005511/wireless.html#primary-content
-
We don't have a whitelist for WiFi dongles. If a WiFi dongle works on other Linux distributions, then our devs often find a way to import the driver.
So if you want to spend more time, try the dongle on other Linux OS, like Ubuntu.
If you want to buy something new, get an Ethernet-to-WiFi adapter. The Ethernet driver is universal, and just works.
-
Looking over the code, I do not think those settings should have an impact. Visualizations are essentially a secondary sink at a fixed 44.1khz, with the audio buffer being resampled if required.
I think you're right. After looking at x86-64 and RPi crash logs again, both have segmentation faults:
CodeCore was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --audio-backend=alsa+pulseaudio'. Program terminated with signal SIGSEGV, Segmentation fault.So probably the memory stack of the audio was corrupted by bad MP3, and later GUI sounds lead to a crash on RPi.
-
If i disable crossfade my Kodi does not crash immediately on end of crashsong but if i press some keys after it played and navigate e.g. to main menu then Kodi crashes and restarts.
And that i can reproduce on my x86 AND on Raspy3 V2.Please post the crash log from RPi. What's your audio output device?
-
Since nobody can reproduce the issue, smf007 is maybe on the right track.
-
When something complex just works on LE, then it's truly a miracle.
Yes, Anynet+ is HDMI-CEC, and commands go from TV to RPi.
-
That log isn't helpful.
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
There is a chance that this sound card works now:
-
valdan Please test LE version 9.2.8 on RPi3B+. If I remember correctly, that version is working.
-
-
OK, I've been tested your files in the right order, with and without Goom visualization. 5s crossfade activated in music settings.
All three files are played without a crash. When "Earth, Wind & Fire" starts to fade out, I hear a short interruption, but that's all.
So I guess it's an x86-specific issue of the Kodi player. Your options:
- re-encode everything to 44.1kHz
- don't use the crossfade option in music settings
- write an x86-specific bug report at Kodi forum
-
Sounds good. BTW: RPi with HAT needs a special case.
-
This is tricky. Maybe a Docker container works:
-
My current 5.1 surround system has optic audio input.
How would one get proper surround sound from the RPi4 (I found one almost free
)My setup is RPi --HDMI--> TV --TOSLINK--> AVR.
If your TV has no TOSLINK output, buy an HDMI audio extractor. You can use the second RPi4 HDMI output (HDMI-1) for that.
-
Please describe the process of your MP3 playback for song 1-3.
I want to reproduce the bug on my RPi3B+ by playing:
- 44.1kHz
- 48kHz
- 44.1kHz
Not sure whether it's a bug in Kodi player or FFMPEG.
-
Samba on Fritzbox is super slow. Most Raspberry Pi devices will provide better performance.
-
From where dou you get the information in the log, that the crash is related to FFMPEG.
That's not a fact, just a theory. Kodi crashes by "segmentation fault", so I guess the FFMPEG error "[mp3float] Header missing" leads to wrong memory management. The other errors in the log are more common, and well known.
If you can separate an MP3, which generates the error, try to play it as a loop, until it crashes the system. That's the MP3 we need to reproduce the bug. It's probably copyright protected, so I guess we have to share the file in private mode. Don't post it here.
