rpi-4-debian-bookworm-6.1.54-rt15-arm64-ext4-2023-11-17-1731.img - TigerVNC?

More
08 Apr 2024 14:51 - 09 Apr 2024 01:24 #297816 by rdtsc
Good day.  Installed tigervnc-standalone-server on title iso.  Lots of examples of how to install it, tried all, none worked.  Big issue here is the vncserver will not start.  Unsure if this is due to the windowing system or what.  Could get the server to start against /usr/bin/xfce-terminal, but viewer couldn't connect to it.

Has anyone gotten any remote-control software to work on this Debian Bookworm (aarch64) release?

Edit1: after booting the system today, the display goes black right when the logon prompt would appear.  Can SSH into it, and lo and behold, tigervncserver just worked!  Could remotely view it just fine.  However, no local display.  So reloading the .iso and trying again.

Edit 2: after retry, can confirm that vncserver will work, but only for root.  Here is as far as I've gotten:
sudo apt update  # note, have NOT updated any packages yet!
sudo apt install ssh tigervnc-standalone-server
vncpasswd  # this is for the cnc account only
sudo vncpasswd  # apparently this will allow root to login as well
vncserver -localhost no  # does not work, our cnc user
sudo vncserver -localhost no  # no error, but note this is root!
# try remotely connecting to the machine's IPaddress:5901

This was the bare minimum to get any sort of VNC connection to stay running.  Of course, not done yet, as the client window displays a big, fat Unable to contact settings server. Failed to execute child process "dbus-launch" (No such file or directory.)

Checking, package dbus-user-session is installed, but not dbus-x11.  Installed the latter, tried VNC again, and BAM, works!  Except that the root account is served.  Attempting (non-root) vncserver -localhost no gives the following:
cnc@raspberrypi:~$ vncserver -localhost no

New Xtigervnc server 'raspberrypi:1 (cnc)' on port 5901 for display :1.
Use xtigervncviewer -SecurityTypes VncAuth,TLSVnc -passwd /tmp/tigervnc.xtgF1d/passwd raspberrypi:1 to connect to the VNC server.


=================== tail /home/cnc/.vnc/raspberrypi:1.log ===================
[mi] mieq: warning: overriding existing handler (nil) with 0x557683ad10 for event 2
[mi] mieq: warning: overriding existing handler (nil) with 0x557683ad10 for event 3
X connection to :1 broken (explicit kill or server shutdown).

Mon Apr  8 20:35:30 2024
 ComparingUpdateTracker: 0 pixels in / 0 pixels out
 ComparingUpdateTracker: (1:nan ratio)
Killing Xtigervnc process ID 5967... success!
=============================================================================

Session startup via '/etc/X11/Xtigervnc-session' cleanly exited too early (< 3 seconds)!

Maybe try something simple first, e.g.,
    tigervncserver -xstartup /usr/bin/xterm
The X session cleanly exited!
The Xtigervnc server cleanly exited!

Any ideas why the sudoed command would work, while the non-sudoed does not?

Here is the journalctl of a working (root) tigervnc startup:
Apr 08 21:14:05 raspberrypi sudo[6345]: pam_unix(sudo:session): session closed for user root
Apr 08 21:14:11 raspberrypi sudo[6354]: cnc : TTY=pts/1 ; PWD=/home/cnc/.vnc ; USER=root ; COMMAND=/usr/bin/vncserver -localhost no
Apr 08 21:14:11 raspberrypi sudo[6354]: pam_unix(sudo:session): session opened for user root(uid=0) by cnc(uid=1000)
Apr 08 21:14:12 raspberrypi dbus-daemon[6416]: [session uid=0 pid=6414] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=0 pid=6437 comm="systemctl --user list-jobs")
Apr 08 21:14:12 raspberrypi dbus-daemon[6416]: [session uid=0 pid=6414] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Apr 08 21:14:12 raspberrypi dbus-daemon[6416]: [session uid=0 pid=6414] Activating service name='org.a11y.Bus' requested by ':1.3' (uid=0 pid=6371 comm="xfce4-session")
Apr 08 21:14:12 raspberrypi dbus-daemon[6416]: [session uid=0 pid=6414] Successfully activated service 'org.a11y.Bus'
Apr 08 21:14:12 raspberrypi dbus-daemon[6416]: [session uid=0 pid=6414] Activating service name='org.xfce.Xfconf' requested by ':1.5' (uid=0 pid=6371 comm="xfce4-session")
Apr 08 21:14:12 raspberrypi dbus-daemon[6416]: [session uid=0 pid=6414] Successfully activated service 'org.xfce.Xfconf'
Apr 08 21:14:12 raspberrypi org.a11y.Bus[6446]: dbus-daemon[6446]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=0 pid=6371 comm="xfce4-session")
Apr 08 21:14:12 raspberrypi org.a11y.Bus[6446]: dbus-daemon[6446]: Successfully activated service 'org.a11y.atspi.Registry'
Apr 08 21:14:12 raspberrypi org.a11y.Bus[6455]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Apr 08 21:14:12 raspberrypi dbus-daemon[6416]: [session uid=0 pid=6414] Activating service name='org.gtk.vfs.Daemon' requested by ':1.8' (uid=0 pid=6467 comm="xfwm4")
Apr 08 21:14:12 raspberrypi dbus-daemon[6416]: [session uid=0 pid=6414] Successfully activated service 'org.gtk.vfs.Daemon'
Apr 08 21:14:14 raspberrypi dbus-daemon[6416]: [session uid=0 pid=6414] Activating service name='org.freedesktop.thumbnails.Thumbnailer1' requested by ':1.13' (uid=0 pid=6503 comm="xfdesktop")
Apr 08 21:14:14 raspberrypi sudo[6354]: pam_unix(sudo:session): session closed for user root
Apr 08 21:14:14 raspberrypi dbus-daemon[6416]: [session uid=0 pid=6414] Activating service name='ca.desrt.dconf' requested by ':1.17' (uid=0 pid=6526 comm="light-locker")
Apr 08 21:14:14 raspberrypi polkitd[464]: Registered Authentication Agent for unix-session:4 (system bus name :1.99 [/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1], object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
Apr 08 21:14:14 raspberrypi dbus-daemon[6416]: [session uid=0 pid=6414] Successfully activated service 'ca.desrt.dconf'
Apr 08 21:14:15 raspberrypi dbus-daemon[6416]: [session uid=0 pid=6414] Activating service name='org.gtk.vfs.UDisks2VolumeMonitor' requested by ':1.22' (uid=0 pid=6509 comm="/usr/lib/aarch64-linux-gnu/tumbler-1/tumblerd")
Apr 08 21:14:15 raspberrypi dbus-daemon[6416]: [session uid=0 pid=6414] Successfully activated service 'org.gtk.vfs.UDisks2VolumeMonitor'
Apr 08 21:14:15 raspberrypi dbus-daemon[6416]: [session uid=0 pid=6414] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
Apr 08 21:14:15 raspberrypi dbus-daemon[6416]: [session uid=0 pid=6414] Activating service name='org.gtk.vfs.Metadata' requested by ':1.13' (uid=0 pid=6503 comm="xfdesktop")
Apr 08 21:14:15 raspberrypi dbus-daemon[6416]: [session uid=0 pid=6414] Successfully activated service 'org.gtk.vfs.Metadata'

And a non-working (cnc) tigervnc startup:
Apr 08 21:04:21 raspberrypi dbus-daemon[1327]: [session uid=1000 pid=1327] Activating service name='org.xfce.Xfconf' requested by ':1.150' (uid=1000 pid=6253 comm="xfce4-session")
Apr 08 21:04:21 raspberrypi dbus-daemon[1327]: [session uid=1000 pid=1327] Successfully activated service 'org.xfce.Xfconf'
Apr 08 21:04:21 raspberrypi systemd[1306]: Started gpg-agent.service - GnuPG cryptographic agent and passphrase cache.
Apr 08 21:04:21 raspberrypi gpg-agent[6323]: gpg-agent (GnuPG) 2.2.40 starting in supervised mode.
Apr 08 21:04:21 raspberrypi gpg-agent[6323]: using fd 3 for browser socket (/run/user/1000/gnupg/S.gpg-agent.browser)
Apr 08 21:04:21 raspberrypi gpg-agent[6323]: using fd 4 for std socket (/run/user/1000/gnupg/S.gpg-agent)
Apr 08 21:04:21 raspberrypi gpg-agent[6323]: using fd 5 for extra socket (/run/user/1000/gnupg/S.gpg-agent.extra)
Apr 08 21:04:21 raspberrypi gpg-agent[6323]: using fd 6 for ssh socket (/run/user/1000/gnupg/S.gpg-agent.ssh)
Apr 08 21:04:21 raspberrypi gpg-agent[6323]: listening on: std=4 extra=5 browser=3 ssh=6
Apr 08 21:04:21 raspberrypi systemd[1306]: Started gpg-agent.service - GnuPG cryptographic agent and passphrase cache.
Apr 08 21:04:21 raspberrypi gpg-agent[6326]: gpg-agent (GnuPG) 2.2.40 starting in supervised mode.
Apr 08 21:04:21 raspberrypi gpg-agent[6326]: using fd 3 for browser socket (/run/user/1000/gnupg/S.gpg-agent.browser)
Apr 08 21:04:21 raspberrypi gpg-agent[6326]: using fd 4 for std socket (/run/user/1000/gnupg/S.gpg-agent)
Apr 08 21:04:21 raspberrypi gpg-agent[6326]: using fd 5 for extra socket (/run/user/1000/gnupg/S.gpg-agent.extra)
Apr 08 21:04:21 raspberrypi gpg-agent[6326]: using fd 6 for ssh socket (/run/user/1000/gnupg/S.gpg-agent.ssh)
Apr 08 21:04:21 raspberrypi gpg-agent[6326]: listening on: std=4 extra=5 browser=3 ssh=6
Last edit: 09 Apr 2024 01:24 by rdtsc. Reason: Added tons more info, removed cruft...

Please Log in or Create an account to join the conversation.

More
10 Apr 2024 16:24 #297940 by rdtsc
Hmm, and there is no /dev/spidev0.0 and 0.1, so this .iso is unable to "see" the Mesa 7c80 card. Is there a way to enable it?

Please Log in or Create an account to join the conversation.

More
10 Apr 2024 16:34 #297941 by PCW
The following user(s) said Thank You: rdtsc

Please Log in or Create an account to join the conversation.

More
10 Apr 2024 18:35 - 10 Apr 2024 18:36 #297945 by rdtsc
I'd love to, but `raspi-config` was replaced with `menu-config` on this .iso and spi enable is no longer available. Currently have two flash drives (one from last year with 2.9.0pre0 which won't update to 2.9.1 or later, and the titled .iso.) Just want the 7C80 to work with something... anything.
Last edit: 10 Apr 2024 18:36 by rdtsc.

Please Log in or Create an account to join the conversation.

More
10 Apr 2024 20:53 #297962 by rodw
Peter's link also shows how to enable  by editing a text file. Note this file may be in a different folder.
The following user(s) said Thank You: rdtsc

Please Log in or Create an account to join the conversation.

More
10 Apr 2024 21:03 #297964 by PCW
Did you try
sudo apt-get install raspi-config

?

Please Log in or Create an account to join the conversation.

More
10 Apr 2024 21:06 #297966 by rodw

Did you try
sudo apt-get install raspi-config

?

I'm not sure if it is compatible with our image. Some boot files are in subfolders

Please Log in or Create an account to join the conversation.

More
11 Apr 2024 02:41 #297981 by rdtsc
Tried to satisfy the grisly requirement of old Bullseye build `python << 3.8` to update 2.9.0; gave up, moved back to new Bookworm build.  

On current Bookworm, `config.txt` was in /boot/broadcom, enabled `dtparam=spi=on` and that seems to work, thank you.  Was then able to complete upgrading `linuxcnc-uspace (1:2.9.2) over (1:2.9.1)` successfully.  

Any chance we can try to get VNC working on it?  Not for everyday use; just for setup and configuration.  It would be much easier to work on the config from a workstation rather than the touchscreen. www.waveshare.com/product/raspberry-pi/d...5.6inch-hdmi-lcd.htm

Please Log in or Create an account to join the conversation.

More
11 Apr 2024 03:44 #297982 by cornholio
I was playing around a month or so ago with a remote desktop login, once I read the docs I found out I couldn't do a remote login whilst logged at the physical console.

Can't for the life on me what remote server it was.

Please Log in or Create an account to join the conversation.

More
11 Apr 2024 04:33 #297987 by rodw
It was a long time ago but I did have XRDP running and was able to open the Pi in Windows RDP.
I tried briefly again with  no luck recently but did not stick with it.
There will most likely be some missing premissions

Please Log in or Create an account to join the conversation.

Time to create page: 0.314 seconds
Powered by Kunena Forum