It was a month ago and I recall that it was definitely a battle to get it to run.
Definitely not a rPi newbie task.
I believe I broke apart the bash installer script running it line by line in order to troubleshoot each step and see exactly where the failures lay.
I remember that I eventually had to disable all management of the wifi from within screenly and then setup wpa_supplicant manually.
Once I pulled out the screenly wifi management pieces from the script and met all the dependencies manually I could start up screenly manually just fine. I believe I might have auto-started it using rc.local instead of the installer’s method but that is probably just my old roots showing through. Hacking in rc.local is taboo of course but is an effective lazy-man’s method to get the job done.
I remember that I had to get creative and backport Buster manually on a few packages in order to meet some of the broken dependencies thereby really just breaking the system enough so it could function without grinding it all to a halt. It was a real Big Kludge the whole way but they do seem to be running just fine a month later. I doubt they could ever be updated though without pulling out my hair again. I only did it because I was buying time for an expected new version to come out that supported the rPi4.
One problem I never worked too hard to fix is that for some reason they like to recycle the wifi connection frequently after their daily reboots (Which I do with all rPi Screenly deployments) and when they get flaky like that they pull a new ip each time they cycle, sometimes every few minutes. A manual IP or reservation (in my case) fixed the problem. I am sure it can be fixed but it is something to think about, I was just happy they worked so I left well enough alone and got on with other things.
The first gen rPi4 has a defect in the boards which unless you are using the genuine rPi power supply is going to cause problems. I don’t know if I would really want to deploy such a kludged-up config and hardware bomb to a client site unless I was in real dire-straits and even then I would vlan them very far off the network to somewhere safe so they couldn’t become a security risk.
If you have a 3d printer and some smaller low voltage fans I would definitely print a case and install a fan to cool them, these rPi 4’s seem to run a lot hotter than the 3’s ever did.