Display errors OpenCPN RPI

[verkerkbr]

Sometimes I get strange errors on my Raspberry Pi with the screen display.

Chart movement slows down and black squares on the Debian taskbar and the OpenCPN screen locks-up.

Restarting OpenCPN then these errors are stil present. Also after restarting the system the errors are the same.

Most of the time the errors appear with zooming in with the Dutch ENC charts.

The only solution is to wipe the opencpn.conf and restart the settings. Then the errors are gone and all worked as before.

Something must be changed in the config file.

Attached is the config file present with the screen errors.

Regards,


Bram

file is too large

[bdbcat]

Bram...
You can safely delete the logfile, and start OCPN over. A new shorter logfile will be produced with just the latest info logged.

2 logfiles, one with error, one without, are most useful.

Dave

[verkerkbr]

Originally Posted by bdbcat

Bram...
You can safely delete the logfile, and start OCPN over. A new shorter logfile will be produced with just the latest info logged.

2 logfiles, one with error, one without, are most useful.

Dave

Good morning Dave,

I will make the two logfiles and also compair the working opencpn.conf with the changed one. A first quick look at these config files I see a lot of changes.

I only have this problem on my home RPI and not on the boat RPI with another screen.

Both running the same software.

Regards,


Bram

[verkerkbr]

Here 2 configs. One with latest kernel 4.14.66 and one with 4.14.62.

This problem is with the recent kernels;

[bdbcat]

Bram...

Confused.
Are we looking for errors in the chart drawing, or the settings dialog? Or both?

Dave

[verkerkbr]

Originally Posted by bdbcat

Bram...

Confused.
Are we looking for errors in the chart drawing, or the settings dialog? Or both?

Dave

Good Morning Dave,

The black squares are not only in the setup screen, there are display errors in the charts (grey area's) and errors in the taskbar. Sometimes black parts of the Raspian taskbar can be seen in other places.

Screen movements slow down and finally freezes.

A simple remedy is to remove the opencpn.conf and do the settings again. Then all works quick again untill the screen corruption which appears after some time.

I can copy the opencpn.confs, to see if there are the errors generated.

If I let the RPI simply standing for a long time with O open and without use. Then the screen is also locked up.

Is it a kind of memory leak ?

Raspian appears to work normal without the use of OpenCPN.

All files are the latest updates and the latest kernel versions.

Regards,


Bram

[bdbcat]

Bram...

Lets start here:

"If I let the RPI simply standing for a long time with O open and without use. Then the screen is also locked up."

Is the GPS connected running?

Can you run the CLI program "top", in another window, and monitor the OpenCPN memory use and processor load?

Dave

[verkerkbr]

Originally Posted by bdbcat

Bram...

Lets start here:

"If I let the RPI simply standing for a long time with O open and without use. Then the screen is also locked up."

Is the GPS connected running?

Can you run the CLI program "top", in another window, and monitor the OpenCPN memory use and processor load?

Dave

Hi Dave,


did some trials and used the Top display. It now appaers that the windows size has some influence. If I use a small window with OpenCPN running together with the Top display. The systeem stays working. If I make a large window with OpenCPN then the system locks up after some time. And after a restart the problem is still present.

But if I delete the opencpn.conf then the problem is solved.

The problem does not appear on my boat system which has a small 10" screen.

I will send you the screen dumps later from my RPI.

Does a large window with O use more memory then a small one ?

Or is it a problem in the latest kernels versions ?

Regards,


Bram

[seandepagnier]

maybe the driver has bug with fbo that with textures above a certain size.

You are using the vc4 driver? With the hardware acceleration off it is ok or?

[verkerkbr]

Originally Posted by boat_alexandra

maybe the driver has bug with fbo that with textures above a certain size.

You are using the vc4 driver? With the hardware acceleration off it is ok or?

Hi BA,

I'am using the VC4 driver and in OpenCPN the OpenGL set to on. Worked well before.

And now having left the standard Raspian (OpenPlotter) open for some time, I now see that also this screen is "frozen" without the OpenCPN window.

The conclusion must drawn, it has to do with the latest kernel updates. I'am using the kernel 4.14.62 and 4.14.66 and the latest updated files.

Regards,


Bram

[bdbcat]

Bram...

We should try the large screen without the VC4 driver, OpenGL OFF, if possible.
We know from earlier bug reports that the VC4 driver is fragile under high memory pressure....

Dave

[verkerkbr]

Originally Posted by bdbcat

Bram...

We should try the large screen without the VC4 driver, OpenGL OFF, if possible.
We know from earlier bug reports that the VC4 driver is fragile under high memory pressure....

Dave

Good Morning Dave,

after trying several settings I probably have found the error.

Raspian Stretch updated with the latest kernel 4.14.67.

But stil the same problem. Raspian (Stretch) finds the right screen format of my monitor.

However OpenCPN does seem to find the screen value in the "auto" setting.

After setting the vertical length of the screen, all problems seem to be solved.

OpenCPN is running now with the VC4 driver on and OpenGL in O also on.

Until now no lockups or screen problems.


Regards,




Bram

[verkerkbr]

Originally Posted by verkerkbr

Good Morning Dave,

after trying several settings I probably have found the error.

Raspian Stretch updated with the latest kernel 4.14.67.

But stil the same problem. Raspian (Stretch) finds the right screen format of my monitor.

However OpenCPN does seem to find the screen value in the "auto" setting.

After setting the vertical length of the screen, all problems seem to be solved.

OpenCPN is running now with the VC4 driver on and OpenGL in O also on.

Until now no lockups or screen problems.


Regards,




Bram

OpenCPN on the RPI 3B+ is running now for several hours with OpenCPN and chart open. No more locks ups or screen errors.


VC4 driver on and in OpenCPN also OpenGL to on. Fast screen movements.



Something seems to go wrong with the auto screen detection in OpenCPN.



Screen is an DVI with a conversion plug DVI > HDMI.

[verkerkbr]

Originally Posted by verkerkbr

Good Morning Dave,

after trying several settings I probably have found the error.

Raspian Stretch updated with the latest kernel 4.14.67.

But stil the same problem. Raspian (Stretch) finds the right screen format of my monitor.

However OpenCPN does seem to find the screen value in the "auto" setting.

After setting the vertical length of the screen, all problems seem to be solved.

OpenCPN is running now with the VC4 driver on and OpenGL in O also on.

Until now no lockups or screen problems.


Regards,




Bram

OpenCPN on the RPI 3B+ running now for several hours with O open.


No more locks ups or screen errors.

[bdbcat]

Bram...

On the screen physical size:
We can only use what the underlying window manager/OS tells us, right or wrong.

That is why we have the manual setting mode available...

Dave