search

Screenly / Anthias

The world's most popular open source digital signage project.
https://anthias.screenly.io
Other
2.48k stars 618 forks source link

Not booting from »Other specific-purpose OS« with Raspberry Pi 3+ #1717

Open sheydin opened 1 year ago

sheydin commented 1 year ago

After flashing the SD card with Anthias from »Other specific-purpose OS« it doesn't boot up. The screen remains black, the green light flashes quickly at beginning. An SD card flashed with Raspberry PI OS boots up properly. Any idea?

vpetersson commented 1 year ago

Hmm that's odd. Are you able to reproduce this @nicomiguelino?

sheydin commented 1 year ago

Just installed full Raspberry PI OS with GUI and then executed:

$ bash <(curl -sL https://install-anthias.srly.io)

No I cannot access the web interface via the http://[raspi-ip]

Any idea for this workaround?

vpetersson commented 1 year ago

Just installed full Raspberry PI OS with GUI and then executed:

You need to use the Raspberry Pi OS Lite, not the desktop version.

nicomiguelino commented 1 year ago

@vpetersson, I've not replicated the issue. It currently takes a while for the Anthias splash screen to finish ('cause during that time, images are being downloaded). After 11 minutes, the splash screen (with the IP address) showed up. After a minute, the black Screenly loading page (with Screenly logo at the center) showed up.

@sheydin, I was not able to access the web interface as well. I'll investigate the issue further.

nicomiguelino commented 1 year ago

@sheydin & @vpetersson, the issue where I'm not able to access the web UI via browser is a false positive on my end. My Raspberry Pi and my laptop (which I use for development) are connected to different networks, that's why I can't access the web interface.

@sheydin, is your display still stuck on a black screen?

sheydin commented 1 year ago

@nicomiguelino I screen is stuck black after installing Pi OS Lite and installing Anthias over it. Next I'll try to flash Anthias directly into the SD via »Other specific-purpose OS« and give it more time to boot.

ealmonte32 commented 1 year ago

@sheydin

@nicomiguelino I screen is stuck black after installing Pi OS Lite and installing Anthias over it. Next I'll try to flash Anthias directly into the SD via »Other specific-purpose OS« and give it more time to boot.

sheydin this comment is for you: Dont need to do all that, if you installed the OS Lite and anthias on it via bash but get a black screen, try to just recreate the containers again with this script: ./screenly/bin/upgrade_containers.sh , run that and see if after it finishes you get the anthias screen with IP.. it has been an issue with many other users and myself included, cant really pinpoint why sometimes the containers get built and sometimes they dont, but it definitely has to do with docker.

sheydin commented 1 year ago

The initial problem is solved basically by being more patient. Flashed the SD card again via »Other specific-purpose OS« and it boots now. During booting the screen remains black. A loading indicator would be helpful to recognize it's booting.

After booting I see the Screenly logo only. The Raspberry Pi is not connected via Network. How can I give it Wifi credentials so that it connects to Wifi and I am able to access to web interface?

Much thanks for your help.

ealmonte32 commented 1 year ago

After booting I see the Screenly logo only. The Raspberry Pi is not connected via Network. How can I give it Wifi credentials so that it connects to Wifi and I am able to access to web interface?

In the console, type in sudo raspi-config and in there you have all the options for the Pi, including connecting to wireless in the network options.

sheydin commented 1 year ago

In the console, type in sudo raspi-config and in there you have all the options for the Pi, including connecting to wireless in the network options.

Sorry, this might be a stupid question, bit I do not find any hint how to open console when Anthias is up and running.

ealmonte32 commented 1 year ago

In the console, type in sudo raspi-config and in there you have all the options for the Pi, including connecting to wireless in the network options.

Sorry, this might be a stupid question, bit I do not find any hint how to open console when Anthias is up and running.

on a keyboard connected directly on the Pi, press ctrl+alt+f1

agawley commented 1 year ago

I am having a similar problem. Fresh install of Anthia from the Raspberry Pi Imager on Pi 3 B+. It boots and shows the Anthia splash screen, then a Web View with a 500 Server Unavailable error. Then a very dark Screenly splash screen. The Pi is unresponsive to keyboard.

agawley commented 1 year ago

This is my issue. https://github.com/Screenly/Anthias/issues/1734

No idea how to set the wifi though? How do I get the image to boot to terminal?

ealmonte32 commented 1 year ago

This is my issue. #1734

No idea how to set the wifi though? How do I get the image to boot to terminal?

Are you saying that pressing control+alt+f1 on your keyboard does not bring up the console screen?

agawley commented 1 year ago

Correct. The pi is unresponsive to keyboard input.

ealmonte32 commented 1 year ago

WiFi can be set in multiple ways.. one way that does not require the console is explained here: https://forums.screenly.io/t/wifi-not-working/817/2

Please read it thoroughly, that way you will have connectivity without troubleshooting why your control+alt+f1 doesnt seem to work, which is extremely rare and it is not specifically an Anthias thing, but an OS/window manager thing. Did you try ctrl+alt+f2/f3/f7/etc?

Did you add the blank ssh.txt or ssh file to the /boot/ directory of the SD card to enable SSH? which then allows you to ssh into the Pi to check if one the containers is not built and that is why you are getting the 500 error, since that would be one of the main reasons for that message..

I also recommend the alternative way to get up and running with Anthias when the Pi-Imager doesn't work as expected which you can find by searching in the screenly.io forums, you also didn't mention if you're using the Raspbian OS Lite supported version? or are you using the default balenaOS image? etc, more specific details would help..

agawley commented 1 year ago

I've tried adding the wpa_supplicant file and the ssh file. No luck improving the boot (still ends up on the error screen) or my ability to bring up a terminal (ctr+alt+fx just flips through blank screens) or my ability to SSH in :-(

Looks like the OS from RPi Imager is BalenaOS. I'll try one of the alternate install approaches.

ealmonte32 commented 1 year ago

Looks like the OS from RPi Imager is BalenaOS

There we go, this is why, balenaOS does not have ctrl+alt+f1, that's a BusyBox type operating system (as far as I know), and doesnt have this shortcut to console. I have heard nico tell other users that the reason Anthias takes a long time to load is because it is downloading stuff or building the containers in the background and some users have had to wait upwards of an hour maybe, depending their internet speed, to get it fully working. This is why I only test and work on anthias with Raspbian OS lite: https://forums.screenly.io/t/i-simply-cant-get-anthias-to-work/1005/4

agawley commented 1 year ago

Got it working by installing PiOS Lite and following your instructions. Thanks.

ealmonte32 commented 1 year ago

@agawley , good to hear.

@nicomiguelino , since this is only related to and happens with balena, shouldn't the Anthias page show some sort of progress bar or heading that lets the user know that they have loaded Anthias (balenaOS version) and that it will take a while to load, so that we don't have these back and forth with users not knowing why their screen is black and are sitting there waiting for something to happen and then go and open an issue here or post in forums.. I think all that would be avoided with such heading and/or progress bar.

agawley commented 1 year ago

FWIW I left the BalenaOS image running for several hours with no result.

On Thu, 13 Jul 2023 at 16:23, Emyll Almonte @.***> wrote:

@agawley https://github.com/agawley , good to hear.

@nicomiguelino https://github.com/nicomiguelino , since this is only related to and happens with balena, shouldn't the Anthias page show some sort of progress bar or heading that lets the user know that they have loaded Anthias (balenaOS version) and that it will take a while to load, so that we don't have these back and forth with users not knowing why their screen is black and are sitting there waiting for something to happen and then go and open an issue here or post in forums.. I think all that would be avoided with such heading and/or progress bar.

— Reply to this email directly, view it on GitHub https://github.com/Screenly/Anthias/issues/1717#issuecomment-1634442102, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAEBQSMSVOHEJ3EO6BDRN3XQAHG3ANCNFSM6AAAAAAUD7PASY . You are receiving this because you were mentioned.Message ID: @.***>

nicomiguelino commented 4 months ago

@agawley, @sheydin, @ealmonte32 Are you still having problems with this issue?

agawley commented 4 months ago

I followed these instructions to avoid the issue https://forums.screenly.io/t/i-simply-cant-get-anthias-to-work/1005/4