amazingproducer

I've been trying to use the device as a motion detection server, and have only installed what was required to build and run the motion daemon. It's entirely possible that...

Here's an example of what happens when I use the reset button after the device crashes like above: ``` U-Boot SPL 2017.09-h2 (Jul 06 2018 - 10:16:12) DRAM: 512 MiB...

Both partitions passed fsck. I'm not using the wifi interface for anything and haven't set it up to connect to a network. Could this be contributing to the problem?

I'm mounting a share to save video collected from rtsp streams when motion is detected.

I've commented out the stuff in /etc/network/interfaces, and deleted all the links to wpa_supplicant and hostpad in the if-up/down directories. I didn't catch the first crash because I was using...

I don't think so. Should I blacklist mali(0)?

huh. It booted after adding the ipv6 to blacklist.conf. lsmod output: ``` Module Size Used by md4 16384 0 nls_iso8859_1 16384 1 cifs 462848 2 fscache 192512 1 cifs mali...

I built out an ethernet port for it and am using that. I'll try reinstalling systemd.

Okay, systemd is reinstalled. Shall I reboot, or would you like additional data first?

``` U-Boot SPL 2017.09-h2 (Jul 06 2018 - 10:16:12) DRAM: 512 MiB Trying to boot from MMC1 BPI: skip sunxi_mmc_getcd pin 166(1) U-Boot 2017.09-h2 (Jul 06 2018 - 10:16:12 -0300)...