On 1/27/22 10:06, (K.K.Paradox)T.Kobayashi wrote:
Thank you for your advice. I haven't solved the problem, but I will continue
to investigate this problem.
You're welcome.
I suspect your setup [/usr/share/X11/xorg.conf.d/ ?] is some default for
systems with a physical frame buffer and with whatever procedure you start xdm
(some system service?), it tries to start something automatically like on a
typical x86 desktop [VT7, fbdev]. If you want to go with this method of
starting up X, you probably need to teach it to use Xvnc instead of Xorg as X
server. I haven't done such config since roughly 2 decades. Maybe:
https://manpages.ubuntu.com/manpages/bionic/en/man1/xdm.1.html#local%20server%20specification
I'm not very familiar with Ubuntu so I could not find any more detailed
documentation other than the Xvnc man page which briefly alludes to a few
different setup variants:
http://manpages.ubuntu.com/manpages/bionic/man1/Xvnc4.1.html
You might be able to translate docs of other distros to your Ubuntu environment:
https://documentation.suse.com/sles/15-SP3/html/SLES-all/cha-vnc.html#sec-vnc-persistent
Vncpassword and vncserver is what I often use, but without a display manager.
The other doc parts seem to depend on YaST as config frontend which is SUSE
specific.
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/using_the_desktop_environment_in_rhel_8/accessing-the-desktop-remotely_using-the-desktop-environment-in-rhel-8#remotely-accessing-the-desktop-as-multiple-users_accessing-the-desktop-remotely
This shows how to edit config files and parts of it might also apply to vnc
server on Ubuntu.
----- Original Message -----
From: "Steffen Maier" <ma...@linux.ibm.com>
To: <LINUX-390@VM.MARIST.EDU>
Sent: Wednesday, January 26, 2022 11:01 PM
Subject: Re: X Windows System setup on Ubuntu Server 18.04.
On 1/26/22 14:11, Robert J Brenneman wrote:
you don't run the X server process on the remote system, the X Server
runs
on the system with the video card in it - which is generally the
workstation/pc/laptop you are looking at. the programs running on the
remote server are the X Clients, and you tell them where the server is by
setting the DISPLAY variable. Generally you also enable SSH X11
tunneling
on the remote server by setting it in the ssh_server.conf file and
restarting sshd, and when you ssh into the server you use the -X switch
on
the ssh command to tell the ssh client to create an X11 tunnel through
your
ssh session.
Workstation-local X server, optionally with ssh X11 forwarding, is one
option.
Running an X server on Z with the VNC backend, instead of a framebuffer,
is
another option. In that case the local workstation would run a VNC client
and
connect to the remote VNC server on the Z-side to show the virtual
framebuffer
of the remote X server. I prefer it when I need to access GUI over
anything
non-LAN, especially over long haul internet paths, because VNC over the
long
haul path behaves much better than the good old verbose X window protocol.
Usually that would be a setup without any X display manager (such as XDM,
GDM,
KDM, ...) in my case, but I've seen distros setup a full display manager
setup
with Xvnc on Z.
Unfortunately, I cannot tell from the given information why the latter did
not
work, despite having x11vnc installed.
On Wed, Jan 26, 2022 at 4:09 AM (K.K.Paradox)T.Kobayashi <
kobaya...@paradox.jp> wrote:
Hello,
I'm setting up X Windows System on Ubuntu Server 18.04.
I installed the some packages with the following command:
$ sudo apt-get -y install xserver-xorg
$ sudo apt-get -y install x11-apps
$ sudo apt-get -y install xdm
$ sudo apt-get -y install x11vnc
And rebooted the system.
But, the xdm and Xorg issued following messges:
(EE) xf86OpenConsole: Cannot open virtual console 7 (No such file or
directory)
[ 530.421] (EE) Failed to load module "fbdev" (module does not exist,
0)
Is there a way to resolve this error?
The details of the xdm and Xorg logs are shown below.
$ cat xdm.log
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for
additional information.
$ cat /var/log/Xorg.0.log
[ 523.499] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 526.423] (==) Using system config directory
"/usr/share/X11/xorg.conf.d"
[ 526.626] (==) No Layout section. Using the first Screen section.
[ 526.627] (==) No screen section available. Using defaults.
[ 526.628] (**) |-->Screen "Default Screen Section" (0)
[ 526.630] (**) | |-->Monitor "<default monitor>"
[ 526.926] (==) No monitor specified for screen "Default Screen
Section".
Using a default monitor configuration.
[ 527.011] (==) Automatically adding devices
[ 527.012] (==) Automatically enabling devices
[ 527.015] (==) Automatically adding GPU devices
[ 527.016] (==) Automatically binding GPU devices
[ 527.457] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 528.090] (++) using VT number 7
So xdm invoked the Xorg (instead of Xvnc) server with VT 7 as option on the
invocation command line. I'm not aware of an easy single config file to find this.
https://manpages.ubuntu.com/manpages/bionic/en/man1/xdm.1.html#local%20server%20specification
(https://manpages.ubuntu.com/manpages/bionic/man1/Xorg.1.html#options)
[ 528.486] (II) no primary bus or device found
[ 529.971] (==) Matched modesetting as autoconfigured driver 0
[ 529.978] (==) Matched fbdev as autoconfigured driver 1
[ 530.263] (II) LoadModule: "fbdev"
[ 530.413] (WW) Warning, couldn't open module fbdev
Best regards,
Toyokazu Kobayashi
--
Jay Brenneman
--
Mit freundlichen Gruessen / Kind regards
Steffen Maier
Linux on IBM Z and LinuxONE
https://www.ibm.com/privacy/us/en/
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Gregor Pillen
Geschaeftsfuehrung: David Faller, Dirk Wittkopp
Sitz der Gesellschaft: Boeblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390
