Hi, if the system crashes, please run the following command after the next boot to collect the previous boot’s system logs and send the generated file to us or sent it to my email(dina@icewhale.org):
sudo journalctl -b -1 -n 500 > /DATA/logs.txt
In addition, you can run the following command:
ln -s /var/log/journal/ /DATA/journal
After that, open the journal folder in Files and send us all the logs inside. These logs contain records from previous system shutdowns. Once the logs have been sent, you may delete the journal folder from Files.
So far with Frigate stopped, it’s not crashed. However that could just be luck. I couldn’t resist popping my OMV ssd in, and see the difference especally with the i915 module. It turns out OMV uses /lib/modules/6.19.11+deb13-amd64/kernel/drivers/gpu/drm/i915/i915.ko.xz where Zima uses filename: /lib/modules/6.12.25/kernel/drivers/gpu/drm/i915/i915.ko. So not a dramatic difference, yet OMV, while not being updated for months now, has a newer driver than ZimaOS that got updated last week.
As I can’t run too long without Frigate, can I somehow get the same or at least a newer i915 driver into Zima? Another approach might be I disable i915 completely, as as of yet Frigate isn’t configured to use it anyway. If it runs stable then with Frigate enabled, it might be a clue that the driver causes issues.
[edit] for now I have disabled the i915 driver, so it’s not loaded anymore, and enabled Frigate again. We’ll see
[edit2]
it turns out with i915 disabled (disabled through modprobe.d) Frigate doesn’t work at all, even when forced to not use GPU. It does receive camera streams, but can’t display them, resulting in an error. Probably no render-device at all or so? But also for example btop doesn’t work at all and just shows a black screen. So running without a graphics driver at all is not really an option either. I tried with nomodeset in cmdlines which should also disable the driver, and I think it did as I have the same issues with Frigate and btop then
Can a newer (preferably the same as the OMV one) i915 driver be implemented in ZimaOS to rule that out? Or maybe in a test-build? @pixelpusher has somewhat the same issues and is running with the same i915 driver. So maybe there’s a link there.
Thanks for your feedback. We will upgrade the system kernel to 6.18 in future versions 2-3. We hope you can assist us with testing and verify whether this issue has been resolved. Thank you in advance for your help
Certainly, I really want this to be as stable as OMV is on the same machine. For reference, there is a bit of crossposting between the previously mentioned thead and this one. I’ll keep my updates in this one from now on (I thought my answer in pixelpushers thread was actually in this thread).
In his thread Pixelpusher mentioned on another OS he used split_lock_detect=off. But split_lock_detect is not recognized by ZimaOS:
[ 0.048687] Unknown kernel command line parameters “splash BOOT_IMAGE=(hd1,gpt4)/bzImage biosdevname=0 split_lock_detect=off”, will be passed to user space.
[ 10.084135] split_lock_detect=off
So for Zima it’s not an option. As for my own setup, in bootcmd.txt i’ve set vfio_iommu_type1.allow_unsafe_interrupts to 0. That should disable certain device passthrough features if I am correct. I am quite familiar with SR-IOV on Windows Servers, specifically for passing through high-bandwidth network interfaces to VMs. But I can imagine the hardware in this somewhat cheap mini-pc doesn’t have all needed features, it’s certainly not build to be a virtualization platform.
Anyway, after setting vfio_iommu_type1.allow_unsafe_interrupts to 0 so far I’ve had no lockups anymore, almost 5 days now. GPU passthrough to Frigate still works though. Fingers crossed, and I’ll keep you informed.
Unfortunately, this morning, after about 6 days of uptime, another crash in the very same way as before. Looking forward to an updated ZimaOS with new kernel.
