Posts: 47
Threads: 3
Joined: Apr 2021
Reputation:
0
Hi,
I'm a happy new Moode user. It's running with
-a RPi 3
-an Audiophonics Evo Sabre
-a raspberry touch screen
-a local network on my router, with cable
-up to date last Moode version
Everything works fine, but after ~1h idle, it doesn't respond anymore, the touchscreen light on after some taps, but remains unresponsive, ssh and web iterface stop working.
Is the issue known?
thank you!
Posts: 54
Threads: 15
Joined: Jun 2018
Reputation:
2
I had a similar problem, but it took longer than an hour to occur and seems to have been caused by my moving /var/cache into RAM to save wear on the SD card. I reverted that change to the standard moode setup and it has worked fine ever since. Have you changed anything like that, if so that might be the problem: I was getting kernel error messages relating to trouble allocating memory, so the 1GB RAM on the Pi 3s isn't enough for such changes, it seems.
Posts: 47
Threads: 3
Joined: Apr 2021
Reputation:
0
I didn't moved directories, I only executed "expand filesystem", but the bug used to occur before that.
Posts: 47
Threads: 3
Joined: Apr 2021
Reputation:
0
Here is my syslog: it represent a ~2 hours session without playing anything. When I shut it down it was stuck...
(there is no attachment: wrong type... ?!? It's just plain text, doesn't work even if I add .txt)
Posts: 13,416
Threads: 304
Joined: Mar 2018
Reputation:
543
Have you installed any 3rd party software or tweaks?
Posts: 6,022
Threads: 176
Joined: Apr 2018
Reputation:
235
As configured, the Forum software doesn't permit appending text files.
You could zip it up before appending or you can cut-n-paste the syslog output into a codebox in a post.
Don't forget to give us the System info output as well. You can get this either from the moOde WebUI (m>Configure>System>m>System info) or by logging into the command line and running moodeutl -s
Are you driving that Audiophonics EVO-Sabre as a USB device or an I2S device?
Regards,
Kent
Posts: 13,416
Threads: 304
Joined: Mar 2018
Reputation:
543
Are you using stock moOde image or an OEM modified image created by the device manufacturer?
Posts: 13,416
Threads: 304
Joined: Mar 2018
Reputation:
543
Try to isolate the problem. Boot the device with a fresh, stock moOde image without any 3rd party software or tweaks. Leave the configuration at stock defaults (audio set to HDMI, etc).
Test to see if the problem occurs. If it does it would suggest some sort of incompatibility between moOde software and the device. Contact the manufacturer to see if they can repro.
If problem does not occur then add one configuration at a time and retest. This may possibly isolate the problem to a particular configuration or component.
- Configure I2S audio device
- Retest
- Configure Pi 7" touch screen
- Retest
- Configure 3rd party software
- Retest
.
.
.