-
Notifications
You must be signed in to change notification settings - Fork 236
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
support for raspberry pi 4 model B #283
Comments
Naturally, when I release a new version a day after it Raspberrypi foundation release a new Pi. You can also follow the technical talks on OctoPi, where it seems to be more lively at the moment: |
Thanks for the quick reply. I didn't mean to rush you, take your time 😄 |
There is a nightly out, but I have no way to test it |
Thanks! My raspi 4 arrives tomorrow and I'll test the nightly. |
Any results? |
The raspi 4 arrived but I'm still waiting for my micro hdmi cable. |
Just tested it. Screen turn black after the boot sequence is finished. This happens on either of the HDMI port. Over VNC I can see that the weppage is displayed correctly. |
I need ananything you can give me, because I have no way to debug.
You can try the non-acceleration version. Might be they changed the GPU
stuff
|
I dont know much about linux debugging. Can I send you a raspi 4 to support the project? |
You are always welcome to send anything to support the project, at the
moment this project only goes because I am volunteering.
I have already https://piitel.co.il/ sending me a 90% discount Pi 4 as a
donation, so I will be able to test (I have no type-C or mini hdmi adapters,
so that will slow me down).
|
When I get my pi 4's in I'll test as well. |
currently building a non-accelerated version but I can confirm the above statement. Editing the boot config and commenting out dtoverlay fixes the issue. #dtoverlay=vc4-kms-v3d I'll mess around some and see if there's a combination that can be used to get 3D working. |
Per one of the raspbian engineers https://www.raspberrypi.org/forums/viewtopic.php?p=1489899&sid=a650da696bb656ba5cbf32cffbcdaa31#p1489899 gpu acceleration is enabled by default on pi4 with config.txt building fullpageos both with and without gpu acceleration added this line to my config This seems to come from the gui module in CustomPiOS. While this might be needed still for older pi's it doesn't look like this needs to be done for pi 4's any longer. So a working pi 4 config.txt after you edit the boot file should be configured at the bottom of the file as follows. [pi4] [all] Where the different sections were written from on build I'm not sure, but after a build, commenting out the very last line and leaving the others has the rpi 4 booting and displays fine on hdmi0. Another issue: To fix this on you need to run |
Thanks for the update @asdf1nit, I will try it out and update once I get my Pi. |
FWIW this worked great for us on our new RPi v4. Now I just need to get the resolution right, as I've got a FullPageDashboard app sitting in a 1024x768 window in the middle of our 4K screen. |
@johnmckeever Please share when you how what to do, I have no hardware to test yet. |
Another issue I've found is screen blanking. I have a few kiosk with touch screens that load up a web app. On all previous pi's I've set the line On the pi 4 the screen goes dark but you can still see the backlight is on. Tapping the screen does nothing and neither does any chrome keyboard shortcuts. Ctrl + w normally kills chrome and it starts back up but this doesn't work either. I did notice that if you vnc into the kiosk that you still see chrome running the page it's supposed to. This is similar to the way chrome acts on the pi before removing the line I haven't had enough time to troubleshoot yet. |
@asdf1nit Thats a kernel bug, its been reported there 6 days ago: Says:
|
Simply using @asdf1nit 's code at the bottom of config.txt did the trick, although we're still only getting a 1024x768 box in the middle of our 4K screen, so we've got some work to do on finding the right HDMI mode settings. `[pi4] [all] |
@johnmckeever While I haven't tried a 4k screen I've had no problem with getting a full 1080 screen. I have a couple 4k screens that I'll test on next week. That being said are you using the fullpage dashboard and getting that behavior or chromium on site? have you tried it on a different site? I haven't used the fullsceen dash board as it's not a part of my build so I'm not sure about it's behavior. @guysoft good to know that they're working on it. In the interim I have a few tvservice scripts that I'm using with crontab to turn the tvs/monitors off at night, not sure if they would be helpful to the project, If so I can throw them into a module. |
I would need to seem them, depends if enough people will use them. |
I am making my own builds so it's easy because my crontab file is always the same. Looking at this again, it would be difficult to create a script that could generate a crontab for others and work if they didn't understand the syntax of a crontab so it's better to leave this out of a module. For anyone wanting to know what worked I'll summarize.
contents of tvoff.sh
use |
@asdf1nit : We've got our RasPi 4 working on a 4K Sony TV without problems now. |
Ok summary: Also, we haven't tested dual screen support yet, that might take more time. |
@guysoft Just got another pi in, this time the 4gb version and I can confirm that the nightly boot's and runs with only a few issues. I flashed with etcher then I first booted into the fullpage os welcome screen all good. Trying to add a tab to the fullpage dashboard didn't work and returned google refused to connect. I find that no https sites work on the FullPageDashboard only http. I'm not sure if this was\is intended or something isn't working with it as I've never used it. I added a different site for chromium to start at boot then rebooted and it works as intended. I tested on both a 1920x1080 TV and my 2560x1440 monitors with no issues. Sound goes out the HDMI. I did try 2 screens and they both work at once but not as expected. It didn't mirror as I thought it would, though it was mirrored during boot, when chrome opened it treated them as one very large screen so that the site was split right down the middle and I had a 5120x1440 screen. I've done a little searching around but haven't seen any mention of a config.txt option. Booting into a full raspbian desktop there are a few options you can set but mirroring wasn't one of them. Side note, I did get them to mirror by accident playing with settings on the desktop but it was more of a glitch and upon reboot it was back to normal. Both screens working is possible but as what to try I'm not sure. Maybe there's a matchbox setting that needs to be set? |
Hi, Even I follow you and use the last version of FullPageOS it's not even booting of showing something. Do you have similar problem ? How did you fix it ? |
@samhqt Does normal Raspbian work for you at all? |
@guysoft I tried to install Raspbian Buster (normal and lite) but it's always saying "Resizing filesystem" and it's reboot without doing anything else. I don't know what can I do. |
Ok, if raspbian isn't working then its not a FullPageOS problem.
And I would guess hardware. so check your SD card isn't faulty and you can
write to it. And that the power supply is good, and so is the power cable.
|
I expected this. By the way do you know when the new version for FullPageOS will be out ? |
When its stable.
I just released day before the Pi 4 came out, because we were not notified.
Also the dual display is a change we might want to consider.
You can use the nightly untill we are sure no other changes should go in.
|
@samhqt You can try and update if changing the gpu mem helps: |
@guysoft I pushed until ggpu_mem=512 and it's start to be good but I would like to push to gpu_mem=1024 but it didn't boot until the end. Do you know why ? Or find a way to attribute more ? |
I could run JS application on my RasPi 4. I found out some problems, the file libGLES2.so.2 so I installed the package libgles2-mesa and the JavaScript was running. I need it to do some GPU optimization by activate some chromium flag. I found out Raspbian is limitating usage of memory to 1GB and you can set up on config.txt file a parameter to go around : total_mem=3072 Thank you for your help and your OS @guysoft :) |
Does stable release already support Pi4? Or we need to use nightly build? |
@gelinger777 No, but the nightly does. Considering just releasing it. Since I am not finding time to get the dual screen coded. |
I see you are fanatically fast on answerig things. Thank you man. We need only on 1 screen to use it. So it should work out of the box, right? |
@gelinger777 Yes. If you are using it in your business consider making a donation. I am maintaining this 100% on my spare time and it helps me make time for it. Latest nightly here: |
We are working on a demo screen. Wen it goes throught, I am sure we will. |
@guysoft The latest raspbian update had some fixes for dual screens. So as I have time to test I'll give an update on this The pi 4 runs reliably on my custom builds. I don't use the dashboard module or the prebuilt images. I have had 3 pi 4's running with FullPageOS for a few months now. The few issues it does have are screen blanking and dual screens. |
@asdf1nit I'll build a new nightly |
@PeterDKs That just looks like the css failed to load. Try |
The isser seemed to be persistent from the start. I’ll give it a shot later today. Do you plan to release a new stable release of FullpageOS that support Raspberry pi 4? |
@PeterDKs Yes, once I do that for OctoPi. I also moved build servers yesterday and didn't finish set up FullPageOS: |
Screen Blanking is now fixed
@guysoft This has now been fixed if you update to the latest test firmware via |
@asdf1nit issue was not closed though. |
Good, I think it's a great job, my English is very poor and I translate it with Google |
@Jesus080967 Its documented as not supported on the Raspberrypi 4 default graphics driver, you can try using a diffrent one:
|
Thanks for answering, as I could solve from config.txt file, would you have to disable the VC4 FKMS V3D driver ?, would you need to rotate the screen 90 degrees ?. |
Another think I came across yesterday, I hope this is the right place to mention: I was not able to activate chromium GPU support in the latest nightly image. Chromium and Raspbian seem to have received some updates / bugfixes in the last months to make it work (and I confirmed that it works using the latest Raspbian image (fully updated) using either the standard desktop environment or just x with matchbox and chromium). But within FullpageOS it didn't work (and it makes quite a difference when playing HD videos, at least with my setup). |
Release candidate out #305 |
Released |
Thanks for the awesome distro! I'm using it on 4 machines with great success.
Our internal website is quite performance hungry so I'm looking forward to upgrading to the new raspberry pi 4 model b.
Is it already supported or do you plan to support it?
The text was updated successfully, but these errors were encountered: