If your SD card does not accept Sailoog's img file due to size reasons, you can try this other one which is the same version but cutting the empty space to fit on cards smaller than 8.1 GB.
Its download size is 1.56 Gb and unzipped is 5.9 GB.
https://mega.nz/#!BJQDWTCD!aKWMQdO7V0Nui...Qn7hkBroI4
OpenPlotter works great with the OpenGl driver switched on. With latest kernel the GLXgears without the effect of
the display runs at around 1000 Frames per Second (FPS).
I only had a small problem with the startup. The startup sometimes halted at: checking display 800x480. Then the system lock-up and had to reboot..
Perhaps the startup is going too fast.
In the OpenPlotter config I have set the delay at 1 or 2instead of 0. And now with this delay the systems seems to starts without this problem.
Regards,
Bram
I have the same problem using the Full KMS driver so I switched to using the software openGL driver and it doesn't hang at the "checking 800x480 display".
I'll try your suggestion and add in a delay.
Thank you
(2018-06-03, 06:24 PM)baltika_no_9 Wrote: [ -> ]I have the same problem using the Full KMS driver so I switched to using the software openGL driver and it doesn't hang at the "checking 800x480 display".
I'll try your suggestion and add in a delay.
Thank you
2 seconds delay worked best here. No longer hang-ups at the start of OpenPlotter with full OpenGL driver on.
Latest kernel 4.14.44.
Another small problem arises. Sometimes the network (DHCP) does not start. It appears that the Eth0 setting is gone. Changing to a fixed IP addres then the networks starts
as usual.
All on a RPI3B+ and OpenGL driver to full.
Unfortunately mine will not boot reliably even with the delay added. Sometimes it works and sometimes not. I will have to keep using the fake KMS.
Same thing happens to me half the times. It freezes when display checking resolution screen. I have chosen to override the corresponding lines in the startup script and it seems to be working. It could be a problem related to the monitor we are using because when I have tested it on a headless system it never fails.
I think you're right, it is to do with the monitor. I forced the preferred HMDI resolution of my monitor by making a change in /boot/config.txt and it boots ok every time now with the full KMS driver.
A result!
wahouu !!! I am very impressed about all the work you have done and still doing ! Thank you very much !!!
Updated to the new build, Problem is I cannot connect to it with either VNC or SSH...... Bug
when I vnc I get:
Connected to RFB server, using protocol version 3.3
No configured security type is supported by 3.3 VNC Viewer
ssh just keeps asking for a password...whats the password???
Buggy build?
I've tried using default passwords like "pi" "raspberry" "root" none work.