Anthias icon indicating copy to clipboard operation
Anthias copied to clipboard

Screenly bootscreen shows, then blackscreen Raspberry Pi 4B

Open sl8tr opened this issue 2 years ago • 7 comments

Hey!

I’m really stuck with my Raspberry 4 installation.

So I’ve installed the developers build with no problems, but after a restart the screenly bootscreen is shown and then it switches to a black screen. Only ALT + F1 is working and gets me into the terminal.

I’ve deleted the /home/pi/screenly folder and reran the installation. Still not working. Started the Installation several times.

I used the Pi imager and preset for Pi OS Lite (Legacy) with Debian Buster and also downloaded and installed an older one.

I hope you can help me out. I have to get 2 of them done for a company. :/

sl8tr avatar Apr 06 '22 18:04 sl8tr

Same issue here, 4 Pi's in a row. Will try investigate further. I have installed one a month ago and it worked correctly. (Yes, with the rbp4)

I personally used Balena Etcher and installed the pi's official Buster image.

I believe in the other pi that I had worked I used the last 2021 buster image instead of the 2022.

Here is the link to the "older" buster images (I might've used the december one)

carlesjavierre avatar Apr 25 '22 17:04 carlesjavierre

I have tried the new installs I made with the "old" pi that I had working with its own install before: THEY WORK. However, the newer hardware I bought doesn't.

The board that is working has the following:

HW version: BCM2711 Revision: b03114 Model: RBP 4B Rev 1.4

The board not working: HW version: BCM2711 Revision: b03115 Model: RBP 4B Rev 1.5

However, it seems that the 1.5 revision is correctly added to the list on here

The admin page on the 1.5 sometimes gives internal error and if you go to system info it just crashes. I can see the container srly-ose-viewer is crashing constantly and this is the error that it throws:

srly-ose-viewer_1     | ./bin/start_viewer.sh: line 47: kill: (36) - No such process
srly-ose-viewer_1     | Traceback (most recent call last):
srly-ose-viewer_1     |   File "viewer.py", line 50, in <module>
srly-ose-viewer_1     |     media_player = VLCMediaPlayer() if get_raspberry_model(get_raspberry_code()) == 'Model 4B' else OMXMediaPlayer()
srly-ose-viewer_1     |   File "/usr/src/app/lib/diagnostics.py", line 128, in get_raspberry_model
srly-ose-viewer_1     |     return raspberry_pi_helper.lookup_raspberry_pi_revision(raspberry_pi_revision)['model']
srly-ose-viewer_1     | TypeError: string indices must be integers, not str

Doing some hacky stuff, I've managed to make it work if I comment this WHOLE try and just re-adding the media_player = OMXMediaPlayer() part. It should end up like this:

"""
try:
    media_player = VLCMediaPlayer() if get_raspberry_model(get_raspberry_code()) == 'Model 4B' else OMXMediaPlayer()
except sh.ErrorReturnCode_1:
    media_player = OMXMediaPlayer()
"""

media_player = OMXMediaPlayer()

You also need to add on the docker-compose.override.yml below line 22 a line with

- ./viewer.py:/usr/src/app/viewer.py

That involves modifying that file, the docker-compose and obviously probably damaging other stuff. This is not a production fix. The system-info tab still crashes and somehow I'm not able to retrieve my internal IP.

In order to recompile with those fixes without losing your mind, you need to edit and run this once from your default screenly install path (assuming it's /home/pi/screenly)

Edit this with the following:

up -d --force-recreate

And then run

bash bin/upgrade_containers.sh

carlesjavierre avatar Apr 25 '22 21:04 carlesjavierre

We've encountered the same issue, Raspberry Pi 4B Rev 1.5, using the Default Buster Lite image and doing a manual installation there won't be any errors during the installation, but on reboot it will show just the Splash Screen and switches to a black screen afterwards. As carlesjavierre wrote the WebUI will be reachable but going to system info will show an internal error.

I also tried to comment out line 49-51 on viewer.py but this sadly didn't change anything in my case.

I have no idea how to get this to work anymore.

paFFr avatar May 05 '22 07:05 paFFr

@paFFr it requires that you edit the docker-compose so it replaces the file inside the container (that'ts why I said i did some fiddly stuff). I'll edit the comment later on so its full, as it might help others. I just didn't want to post a nasty patch, but if you can get it to work its fine for me!

carlesjavierre avatar May 05 '22 08:05 carlesjavierre

@paFFr I have updated with full instructions. Please try it out and let me know :smile:

carlesjavierre avatar May 05 '22 10:05 carlesjavierre

@carlesjavierre Thank you for taking the effort and updating your instructions, sadly it didn't seem to change anything on my end, as I still get only a black screen after the initial splash screen :(

paFFr avatar May 05 '22 12:05 paFFr

@paFFr Feel free to join my discord and I can help you out.

https://discord.gg/msvewqSA

(edit: link expired)

carlesjavierre avatar May 05 '22 12:05 carlesjavierre