This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Problems with VNC und display driver
#1
Hello,
My name is Jürgen and I try to adapt Openplotter for my needs.
Sorry for my English, I come from Deuschtland and must write everything with Google translator.  Smile
I am running Openplotter OpenPlotter RPI v0.8.0 from May 23, 2016 on an RPI3
Connected is a
RTL-SDR Stick
WIFI dongle
Wireless keyboard
Monitor or HDMI

The installation and setup of Openplotter is done at home. On the boat, this display is installed.

Http://www.waveshare.com/wiki/10.1inch_H...n_settings

PROBLEM: If I install the drivers for this display, I can not reach the Pi via VNC.

Error message:
The port on which the computer is listening for a connection could not be contacted.  Huh

Copy config.txt after driver installation

# For more options and information see
http://www.raspberrypi.org/documentation/configuration/config-txt.md
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output

hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
dtparam=i2c_arm=on
#dtparam=i2s=on
dtparam=spi=on
enable_uart=1
# Uncomment this to enable the lirc-rpi module
#dtoverlay=lirc-rpi

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on
display_rotate=0
hdmi_group=2
hdmi_mode=1
hdmi_mode=87
hdmi_cvt 1024 600 120 6 0 0 0
dtoverlay=ads7846,cs=1,penirq=25,penirq_pull=2,speed=50000,keep_vref_on=0,swapxy=0,pmax=255,xohms=150,xmin=200,xmax=3900,ymin=200,ymax=3900




How can I ran debug mode?  Huh

I hope I can be helped. Thanks in advance.
Angel  Entschuldigung für mein Englisch. Es ist "deepl.com english"
PN bitte auf german.  Big Grin
Reply
#2
I think it's a raspbian problem. Have you tried to connect via RDP Remote Desktop (on windows pc mstsc)?

You can change your config.txt that only if the monitor is switched on and connected the settings and drivers are started.
(raspberry pi documentation https://www.raspberrypi.org/documentatio...fig-txt.md "The [EDID=*] filter")

You need to know the name of your monitor(xxxx). In terminal put in:
tvservice -n
Output should be something like:
device_name=xxxx

change the end of your config.txt to:
# Enable audio (loads snd_bcm2835)
[EDID=xxxx]
dtparam=audio=on
display_rotate=0
hdmi_group=2
hdmi_mode=1
hdmi_mode=87
hdmi_cvt 1024 600 120 6 0 0 0
dtoverlay=ads7846,cs=1,penirq=25,penirq_pull=2,speed=50000,keep_vref_on=0,swapxy=0,pmax=255,xohms=150,xmin=200,xmax=3900,ymin=200,ymax=3900
[all]
Reply
#3
Thank you @ e-sailing
Unfortunately your tips did not succeed.
Problem still exists.
Angel  Entschuldigung für mein Englisch. Es ist "deepl.com english"
PN bitte auf german.  Big Grin
Reply
#4
Hello,
I've done everything and entered. With RDP I can access the Pi.
VNC does not continue.
I also noticed that no adjusted Autostarts are executed. No OpenCPN, No full screen. (Set in the OpenPlotter menu)

Does anyone have any ideas for this problem

Greetings Jürgen
Angel  Entschuldigung für mein Englisch. Es ist "deepl.com english"
PN bitte auf german.  Big Grin
Reply
#5
I don't know what you did that vnc doesn't work.
OpenPlotter images work with x11vnc don't install any other vnc program.
To check which vnc process is started put in:

ps aux | grep vnc

Output should be something like this:
pi 2044 0.9 1.9 42500 18556 ? S 14:49 0:29 x11vnc -forever -shared
pi 10148 0.0 0.1 4280 1808 pts/1 S+ 15:43 0:00 grep --color=auto vnc

Do you have the same (numbers can be different)?

You can start:
killall vnc
x11vnc

At the end of the long text there should be a line "PORT=5900"
Check if you can connect now.
Reply
#6
Hello e-sailing,
Thank you for your help. Yes, now I can establish a connection with VNC.
If I understand now correctly the process was not started automatically, right?
Can it be that it is not the only process that is not started? OpenCPN also does not start when I put the hook in OpenPlotter.
How can I check this and change it if necessary?
Thank you very much for your cooperation. thank you

Sorry for my english, it is "Google-english" Smile
Angel  Entschuldigung für mein Englisch. Es ist "deepl.com english"
PN bitte auf german.  Big Grin
Reply
#7
On the last tab / page (Reiter) Startup you can select vnc to be started also opencpn.
Reply
#8
Hello e-sailing,
That's what I meant. I have the hook set but it has no effect.
I suspect that the installation of the graphics driver several processes do not start.
Greetings Jürgen

edit:
An internet connection to the VNC client is not connected. Despite 2 wlan adapter and correct settings.
It is not the settings. Before the driver installation ran everything flawlessly.
Angel  Entschuldigung für mein Englisch. Es ist "deepl.com english"
PN bitte auf german.  Big Grin
Reply
#9
Ok now I understand. Sometimes there are problems with the start procedure. (There are and will be changes in the startup.)
You should set Delay (seconds) to 20 on Startup tab. Restart and wait for about 2 minutes after you see the desktop. Check with "ps aux | grep vnc" if x11vnc has started.
Reply
#10
The problem is still there. I need to start x11vnc manually.
In which file or directory do I find the Autostarts of Openplotter?
Greetings Jürgen
Angel  Entschuldigung für mein Englisch. Es ist "deepl.com english"
PN bitte auf german.  Big Grin
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)