I experienced the same problem situation:
Installing matrix-os on a Raspbian Stretch Lite installation seemed to work, but malos never launched on reboot. The service always needed manual starting. After manual starting matrix-os does actually work.
matrixio-malos status yields the following:
sudo systemctl status matrixio-malos
● matrixio-malos.service - Matrix Abstraction Layer for OS
Loaded: loaded (/lib/systemd/system/matrixio-malos.service; enabled; vendor preset: enabled)
Active: failed (Result: signal) since Sat 2018-01-27 22:17:03 UTC; 17h ago
Process: 412 ExecStart=/usr/bin/malos (code=killed, signal=FPE)
Main PID: 412 (code=killed, signal=FPE)
Jan 27 22:17:03 pixie malos[412]: **************
Jan 27 22:17:03 pixie malos[412]: You can query specific driver info using port 20012.
Jan 27 22:17:03 pixie malos[412]: Registered driver IMU with port 20013.
Jan 27 22:17:03 pixie malos[412]: Registered driver Humidity with port 20017.
Jan 27 22:17:03 pixie malos[412]: Registered driver Everloop with port 20021.
Jan 27 22:17:03 pixie malos[412]: Registered driver Pressure with port 20025.
Jan 27 22:17:03 pixie malos[412]: Registered driver UV with port 20029.
Jan 27 22:17:03 pixie systemd[1]: matrixio-malos.service: Main process exited, code=killed, status=8/FPE
Jan 27 22:17:03 pixie systemd[1]: matrixio-malos.service: Unit entered failed state.
Jan 27 22:17:03 pixie systemd[1]: matrixio-malos.service: Failed with result 'signal'.
So I took a look at /matrixio-malos.service, which contains a dependency on a different service:
sudo nano /lib/systemd/system/matrixio-malos.service
[Unit]
Description=Matrix Abstraction Layer for OS
After=matrixio-creator-firmware.service
[Service]
Type=simple
ExecStart=/usr/bin/malos
[Install]
WantedBy=multi-user.target
Examenig /lib/systemd/system/matrixio-creator-firmware.service I found that this service does not exist.
But there is a /lib/systemd/system/matrixio-devices-firmware.service.
So I changed matrix-malos.service to the follwoing:
[Unit]
Description=Matrix Abstraction Layer for OS
# After=matrixio-creator-firmware.service
After=matrixio-devices-firmware.service
[Service]
Type=simple
ExecStart=/usr/bin/malos
[Install]
WantedBy=multi-user.target
After a reboot, checking th status of matrix-malos now yields:
● matrixio-malos.service - Matrix Abstraction Layer for OS
Loaded: loaded (/lib/systemd/system/matrixio-malos.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2018-01-28 16:08:15 UTC; 16s ago
Main PID: 733 (malos)
CGroup: /system.slice/matrixio-malos.service
└─733 /usr/bin/malos
Jan 28 16:08:15 pixie malos[733]: **************
Jan 28 16:08:15 pixie malos[733]: You can query specific driver info using port 20012.
Jan 28 16:08:15 pixie malos[733]: Registered driver IMU with port 20013.
Jan 28 16:08:15 pixie malos[733]: Registered driver Humidity with port 20017.
Jan 28 16:08:15 pixie malos[733]: Registered driver Everloop with port 20021.
Jan 28 16:08:15 pixie malos[733]: Registered driver Pressure with port 20025.
Jan 28 16:08:15 pixie malos[733]: Registered driver UV with port 20029.
Jan 28 16:08:15 pixie malos[733]: Registered driver MicArray_Alsa with port 20037.
Jan 28 16:08:15 pixie malos[733]: Registered driver Servo with port 20045.
Jan 28 16:08:15 pixie malos[733]: Registered driver Gpio with port 20049.
Tada, this looks much better.
Actually it seems, there are quite some integration bugs from Matrix Creator and Voice.
Hope this helps somebody.