We didn’t see anything like that, we’ll need more information to know what’s going on.
You’ll have to enable persistent logging, so after the system crashes, the logs are still available:
sudo nano /etc/systemd/journald.conf
Edit the file, so that #Storage=auto line looks like this:
Storage=persistent
Hit Ctrl+X, to exit, press Y to confirm saving your changes.
Then restart the system (sudo reboot), and once the crash occurs, on the very next boot after the crash occurred, you can access the log of that session by running:
journalctl -b 1
It can be saved to a file by doing:
journalctl -b 1 > crash.log
Then you may share the crash log here for us to investigate what’s going on.
Hi,
What a great job you have done here !
Have build a Modep pedal with a Pi 3B + Pisound + the case + the the last Patchbox image => it works fine on the first start… - Thank you for all !
Just find this issue while loading a pedalboard : as saving a pedalwork, it is ok, no error message - but when loading it, Modep refuse and display an error => can’t load the pedalboard because plugin missing
My Patchbox is 100% stock, no change
If the pedalboard is empty (no modification on the defalt empty pedalboard), error is still the same
Only the 4 default pedalboard can be loaded, not a modified and saved one
Ok, I tried the same - saving an empty pedalboard, and got the same errors as you do. But at least saving and loading a pedalboard that does contain some plugins seems to work fine.
Is there still an issue with the Pimoni Fan Shim and the Pisound. It seems like following the instructions on then Pimoni page " a script to install a daemon (a service that runs in the background) that runs the fan in automatic mode, triggering it on or off when the CPU reaches a threshold temperature, with a manual override via the tactile switch." should be able to get around this. Is this what folks have been using? TIA
it’s been a while since I last used my py, and recently I encountered the same problem as before, so I looked at the logs as you told me, but I don’t understand why, I have the impression that there is no recent eventcrash.log (1.3 MB) .
Can you tell me what’s your point of view please?
As the Raspberry Pi’s system clock gets synchronized to network time only some time after boot, it’s a bit difficult to follow the timeline, so just to be safe, earlier logs might help.
the problem just happened when i was looking at youtube video… these are the log , i give youcrash11.log (1.3 MB) crash21.log (88.3 KB) crash31.log (257.0 KB)