-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Build Not Booting Pi 3 B+ #235
Comments
This is a nightly build that has not been tested yet, please use the released builds to test if they work first. |
Ok, will go back to stable build. |
I just tried "2018-04-22_2018-04-18-fullpageos-stretch-lite-0.9.0.zip" on 3 B+, but it does not work. It can not boot, just black screen. |
@jyy1082 try the non-acceleration version at: There are reports with 3B+ acceleration not working on some models, the fact you are based in China might give a good hit this is the issue, because you likely have access to much more diverse hardware there, which I can't test. |
The non-acceleration version works. |
The non-acceleration version just disabled the acceleration in the gui module. You can read about it here: https://github.com/guysoft/FullPageOS#building-using-vagrant |
How about I build from Debian and just set "[ -n "$FULLPAGEOS_INCLUDE_ACCELERATION" ] || FULLPAGEOS_INCLUDE_ACCELERATION=no" in this file: |
In both cases you are building from debian/raspbian. |
Got it. Thanks so much for your support! |
What were you doing?
Writing Image to new 64GB SanDisk SD Card
What did you expect to happen?
To boot to FullPageOS
What happened instead?
Boots past Rainbow landing page, Black Screen after
Was there an error message displayed? What did it say?
No Message, only black screen,
Tried a different SD card, still no boot.
Formatted the SD card first also
Version of FullPageOS?
2018-06-27-fullpageos-stretch-lite-0.10.0
[Can be found in /etc/fullpageos_version ALWAYS INCLUDE.]
Screenshot(s) showing the problem:
[If applicable. Always include if unsure or reporting UI issues.]
The text was updated successfully, but these errors were encountered: