Nightly Build Gets black screen on RaspberryPi 1/Zero/B+

Question

Nightly Build Gets black screen on RaspberryPi 1/Zero/B+

NF3RN0 opened this issue 8 years ago · comments

I get a back screen with a cursor after the boot messages. I first tried changing the webpage in fullpageos.txt to no avail.

I can ssh to the Pi and can ping google from it so I know that I have internet connection to the pi.

If I kill Xorg and then try to restart the service from ./run_onepageos I get a list of several error messages that it cannot open the display.

xset: unable to open display ""
xset: unable to open display ""
xset: unable to open display ""
matchbox: can't open display! check your DISPLAY variable.
14/01/2016 04:40:36 passing arg to libvncserver: -rfbauth
14/01/2016 04:40:36 passing arg to libvncserver: /home/pi/.vnc/passwd
14/01/2016 04:40:36 x11vnc version: 0.9.13 lastmod: 2011-08-10 pid: 953
14/01/2016 04:40:36 XOpenDisplay("") failed.
14/01/2016 04:40:36 Trying again with XAUTHLOCALHOSTNAME=localhost ...
14/01/2016 04:40:36
14/01/2016 04:40:36 *** XOpenDisplay failed. No -display or DISPLAY.
14/01/2016 04:40:36 *** Trying ":0" in 4 seconds. Press Ctrl-C to abort.
14/01/2016 04:40:36 *** 1 2 3 4
14/01/2016 04:40:40 XOpenDisplay(":0") failed.
14/01/2016 04:40:40 Trying again with XAUTHLOCALHOSTNAME=localhost ...
14/01/2016 04:40:40 XOpenDisplay(":0") failed.
14/01/2016 04:40:40 Trying again with unset XAUTHLOCALHOSTNAME ...
14/01/2016 04:40:40

14/01/2016 04:40:40 ***************************************
14/01/2016 04:40:40 *** XOpenDisplay failed (:0)

*** x11vnc was unable to open the X DISPLAY: ":0", it cannot continue.
*** There may be "Xlib:" error messages above with details about the failure.

This is with the latest nightly build, I'll try the october build to see if I can get that working.

I think it might be trivial to note that I am using a Pi Zero.

Cheers.

Guy Sheffer · Answer 1 · Sun Jan 31 2016 23:29:36 GMT+0800 (China Standard Time)

Hey,
There is a new nightly that might fix this issue. It waits for the an internal webserver to start before starting chromium.

jorgeiglesiasca · Answer 2 · Sat Feb 13 2016 05:17:52 GMT+0800 (China Standard Time)

In the nithtly from 31 of Jan (lite version around 600mb) take ages to load in Pi2 (around 10 minutes) and does not load in PiB

If i unplug the pi when it hangs loading (happens allways in Pi B ) next boot gets into a loop and at the end i get a kernel panic.

Tried to write 3 or 4 SD cards to check if was product of casuality and i always end in kernel panic. This does not happen on Pi2

Guy Sheffer · Answer 3 · Sat Feb 13 2016 10:07:19 GMT+0800 (China Standard Time)

Hey, you wrote Pi2 twice, did you mean a different version on the first mention?

Sam Jordan · Answer 4 · Mon Feb 29 2016 22:34:46 GMT+0800 (China Standard Time)

I am also seeing the OP's issue on a Pi B with the latest nightly.

tlietz · Answer 5 · Sun Mar 13 2016 16:46:13 GMT+0800 (China Standard Time)

Same issue here with all nighty builds, X11 starting with black screen and mouse but no chrome comes up, but has PID. Only stable version with wheezy and chromium 22 is working for me on Pi B+ v1 2. Any ideas?

Guy Sheffer · Answer 6 · Wed Mar 16 2016 04:40:39 GMT+0800 (China Standard Time)

It seems like everyone experiencing this has a Pi 1/B+/zero. It might be anything slower than a Pi2 is too slow for the recent distro.

luedm · Answer 7 · Thu Mar 24 2016 08:14:45 GMT+0800 (China Standard Time)

I'm using a Pi 3 and it is stuck on the colored screen when I boot. Unable to connect via SSH.

Guy Sheffer · Answer 8 · Thu Mar 24 2016 18:01:11 GMT+0800 (China Standard Time)

Regarding the Pi 3, I need to make a build using the new base image released, reports on OctoPi says that fixes the issue. Regarding Pi 1/b+/Zero, I need to see, it might be booting times are different. Or they have not enough power to run Chromium, or the Armv6 is not behaving well with chromium build. I am not in a hurry to test all these hypotheses because I am not sure how Chromium would behave on those device, they are not likely to handle modern versions of Chromium. But thanks for the reports, and reports on my guesses would be welcome.

Guy Sheffer · Answer 9 · Thu Jun 02 2016 17:30:51 GMT+0800 (China Standard Time)

Hey, if anyone wants to try the recent RC, it seems to work far more better and has a chance on the RaspberryPi 1/Zero/B+.
This is a release candidate that I tested, if it works then great, if not, I am thinking about closing this as "wontfix"

Rodrigo Costa · Answer 10 · Sat Jun 04 2016 01:26:44 GMT+0800 (China Standard Time)

I tried the last nightly with a Raspberry Pi B and still have the black screen problem. Looks like this can't be fixed.

Guy Sheffer · Answer 11 · Wed Jun 15 2016 21:51:30 GMT+0800 (China Standard Time)

So the reason FullPageOS does not work on these devices ie since they use ARMv6, please see #43

Guy Sheffer · Answer 12 · Mon Oct 23 2017 16:08:34 GMT+0800 (China Standard Time)

Fixed, it works now, its slow as hell and takes 5-10 minutes to boot. Might work as a digital picture frame.