papirus-set binary stuck at "systemctl start epd-fuse"

[GeiserX]

If you execute the command papirus-set with the size of the screen you have,

It sets it correctly, but in the end, it always errors (I've tested this always in a PaPiRus 2.0'')

After a long time waiting for the binary to finish, this is what appears:

A dependency job for epd-fuse.service failed. See 'journalctl -xe' for details.

If you do that, then the logs say:

Dec 24 15:41:35 XXX systemd[1]: dev-spidev0.0.device: Job dev-spidev0.0.device/start timed out.
Dec 24 15:41:35 XXX systemd[1]: Timed out waiting for device dev-spidev0.0.device.
-- Subject: Unit dev-spidev0.0.device has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit dev-spidev0.0.device has failed.
-- 
-- The result is timeout.
Dec 24 15:41:35 XXX systemd[1]: Dependency failed for A Fuse driver for the Repaper.org EPD.
-- Subject: Unit epd-fuse.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit epd-fuse.service has failed.
-- 
-- The result is dependency.
Dec 24 15:41:35 XXX systemd[1]: epd-fuse.service: Job epd-fuse.service/start failed with result 'dependency'.
Dec 24 15:41:35 XXX systemd[1]: dev-spidev0.0.device: Job dev-spidev0.0.device/start failed with result 'timeout'.

I am using the latest Raspbian image with a Pi Zero W

After all, it is working as expected after a reboot, but I am programming all of this through Ansible and I don't want to be waiting for it to fail.

[tvoverbeek]

@DrumSergio Smells like you have not enabled SPI on your PiZero W.
Check if /dev/spidev0.0 and /dev/spidev0.1 exist.
Based on your error messages they do not seem to exist.
Enable SPI with e.g. the raspi-config utility:
sudo raspi-config
Select Item 5 Interfacing Options
Then select SPI and enable SPI
Check again for existence of /dev/spidev0.0 and /dev/spidev0.1.
They should now exist and the epd-fuse service should start when you execute papirus-set.