On 2/10/22 17:40, joea- lists wrote:
On 2022-02-10 22:00, joea- lists wrote:
Originally installed a test 15.3 system as a simple server, no graphics environment. It's been maybe a decade since I had to install and configure an X system from scratch.
You need to install one of the graphical environment patterns. Perhaps "patterns-base-x11", maybe "patterns-base-basic_desktop" too.
Added X11 via Yast. Accepted the required additions.
systemctl start xdm.service fails. Due to "dependencies". Did find a few services it needed that were not installed by YAST.
Still failed to start.
Eventually I found it was failing due to "not configured". Suse docs seem to say it does "not normally need to be configured"
That's because the X server by default no longer uses xorg.conf. It has the smarts to detect the devices. There are xorg.conf segments in /etc/X11/xorg.conf.d/, but the commands are all commented out, i.e., these are for overrides only.
and should just work.
I've so far found no configuration utilities to assist. At least none seem to be installed. Any assistance is appreciated. Run "startx" on a console, and paste here the result.
If you need it, you could run "gpm" service to get mouse support in text mode.
-- Cheers / Saludos,
Carlos E. R. (from 15.3 x86_64 at Telcontar) I got "systemctl start xdm.service" to start after installing many more x items via YAST. No idea which specific thing it was that "fixed it".
startx is unhappy. Below is the screen output. I suspect I still need to run a setup/config for this specific machine, as the config file I copied from another is old and has bad keywords. I've not found one as yet.
This could be the problem. X will use the xorg.conf file, if there is one. The error below indicates that X is using an xorg.conf file in /etc/X11/xorg.conf.d/. It should not be there. Especially if you copied it from another machine.
X.Org X Server 1.20.3 X Protocol Version 11, Revision 0 Build Operating System: openSUSE SUSE LINUX Current Operating System: Linux fletch 5.3.18-150300.59.46-default #1 SMP Tue Feb 1 16:19:33 UTC 2022 (fb6d1ec) x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.3.18-150300.59.46-default root=UUID=d50aa705-efa7-4634-88d8-21b94d2bc0c6 splash=silent resume=/dev/sda3 mitigations=auto quiet Build Date: 14 December 2021 12:00:00PM
Current version of pixman: 0.34.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Thu Feb 10 17:35:04 2022 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" Parse error on line 44 of section Files in file /etc/X11/xorg.conf.d/xorg.conf Ignoring obsolete keyword "InputDevices". Parse error on line 45 of section Files in file /etc/X11/xorg.conf.d/xorg.conf Ignoring obsolete keyword "InputDevices". VMware: No 3D enabled (0, Success). (EE) Fatal server error: (EE) failed to create screen resources(EE) (EE) 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. (EE) (EE) Server terminated with error (1). Closing log file. xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error ------------------------------------------------------------------------------------------- xinit failed. /usr/bin/Xorg is not setuid, maybe that's the reason? If so either use a display manager (strongly recommended) or adjust /etc/permissions.local and run "chkstat --system --set" afterwards
This indicates A first place to look therefore is whether there still is an xorg.conf on your system, and if so, do you actually need that and what is it doing? You m