@Budgie2 the 32bit ones should not be needed. So what files are in /etc/X11/ and /etc/X11/xorg.conf.d?
Here they are:-
alastair@HP-Z640-1:~> cd /etc/X11/
alastair@HP-Z640-1:/etc/X11> ls
xinit xorg.conf.d xorg.conf.install
alastair@HP-Z640-1:/etc/X11> cd xorg.conf.d
alastair@HP-Z640-1:/etc/X11/xorg.conf.d> ls
00-keyboard.conf
alastair@HP-Z640-1:/etc/X11/xorg.conf.d>
And here is what the xorg.conf.install has:-
alastair@HP-Z640-1:/etc/X11> cat xorg.conf.install
Section "Device"
Identifier "modesetting"
Driver "modesetting"
Option "PreferCloneMode" "true"
Option "AccelMethod" "none"
EndSection
Section "Screen"
Identifier "modesetting"
Device "modesetting"
EndSection
Section "Device"
Identifier "fbdev"
Driver "fbdev"
EndSection
Section "Screen"
Identifier "fbdev"
Device "fbdev"
EndSection
Section "Device"
Identifier "vesa"
Driver "vesa"
EndSection
Section "Screen"
Identifier "vesa"
Device "vesa"
EndSection
Section "ServerLayout"
Identifier "Layout"
Screen "modesetting"
Screen "fbdev"
Screen "vesa"
EndSection
alastair@HP-Z640-1:/etc/X11>
Hope it means more to you than me and hope it explains what is missing.
@Budgie2 and in /usr/share/X11/xorg.conf.d/?
A post was split to a new topic: Login problems with the system
For most users, the default modesetting Xorg DDX driver is all that is required.
Here are the contents.
alastair@HP-Z640-1:~> cd /usr/share/X11/xorg.conf.d
alastair@HP-Z640-1:/usr/share/X11/xorg.conf.d> ls
10-amdgpu.conf 10-libvnc.conf 11-evdev.conf 50-device.conf 50-extensions.conf 50-screen.conf 70-wacom.conf
10-evdev.conf 10-quirks.conf 40-libinput.conf 50-elotouch.conf 50-monitor.conf 70-vmmouse.conf
alastair@HP-Z640-1:/usr/share/X11/xorg.conf.d>
I can look at all these but which is the likely candidate problem?
Hi Dean,
Interesting but I couldnât see any reference to this in my system. Browsing through other candidates the only references to DDX I found searching âxorgâ were for AMD devices.
Should I be looking for your suggestion elsewhere and is it needed here?
Sorry, I donât understand your reply. You previously mentioned that âxf86-video-amdgpuâ was not installed, and you then installed it. I was pointing out that it is not required. Your previous inxi output had showed that the modesetting driver is in use in any case. (Not the source of your Plasma X11 issue anyway.)
Hi Dean and thanks. Sorry but I am not familiar with the subject but you have explained now that I have installed something which was not needed, does not relate to and does not solve my problem anyhow. Many thanks.
Do you have any suggestions which might help solve my problem?
Not beyond what Iâve already shared. Returning to your statement you made earlierâŚ
The only way I can get in (because I am not sufficiently knowledgeable on commands required,) is to set the desktop to X11 at the login screen, when I cannot then login. Then reboot and start init 3, login on cli and then run startx. This gets me into my desktop with X11 running.
I had missed thisâŚso you can consistently get a working Plasma X11 session using this method?
I used to make that mistake regularly. Is there still an SDB: somewhere that says so?
DIX (Device Independent X) driver:
modesetting: works with AMD, Intel, NVidia and other GPUs for which KMS support exists; not separately packaged; provides full function; often works even when KMS is disabled
fbdev: provides only vastly reduced function, should work with anything, when KMS is disabled (nomodeset, *.modeset=0)
vesa: provides significantly reduced function, should work with anything, when KMS is disabled (nomodeset, *.modeset=0)
DDX (Device Dependent X) drivers; most function only when KMS is enabled:
amdgpu: works only with AMD GPUs; xf86-video-amdgpu
intel: works only with Intel GPUs; xf86-video-intel
nouveau: works only with NVidia GPUs; xf86-video-nouveau
radeon: works only with old AMD/ATI GPUs; xf86-video-ati
others: xf86-video-mga for Matrox; xf86-video-sis for SiS; xf86-video-openchrome for VIA; several more xf86-video-* for relics; some may not be supported when KMS is kept enabled
I suspect that if you switch VT at the SDDM login screen, you could login (as user) via the VT, and running startx would work as you described with booting to runlevel 3. I wonder if this is more about SDDM somehow?
Well, not a distro-specific thing of course. Perhaps start withâŚ
man modesettingI recall this Phoronix articleâŚ
In short yes. The performance was a bit slow once my desktop was up and running but it worked.
The rest is over my head.
Do you want me to try something else, in laymanâs terms please.
You could try comparing behaviour with another display manager perhaps eg GDM.
Hi Dean, that didnât work very well. I tried switching to lightdm but that didnât work because the installation was only manual so login auto took me back to Wayland.
Forced the issue by logging in as init 3 and then startx and it gave me a blank black screen with a blinking cursor and no control at all. Nothing. Rebooting just repeated bringing me back to the black screen.
It is a good job I spend some time setting up snapshots on this sytem as I had to jump back several hops before I could get back to a desktop.
There is now some more info buried in my log files but will need help please in what commands to get the info I can share here.
Nothing there I recognize as suggesting worth trying.
Those are ancient. Modesetting in particular has evolved, now able to be used in some nomodeset configurations.
IME WRT to performance with Intel GPUs, intel and modesetting Glmark2 results have differed, either insignificantly, or radically, with the radicals from tests in which specific tests obviously failed using intel (black window instead of expected content and/or error messages: score 5583 vs. 2950 using modesetting).
@mrmazda: Youâve misunderstood. I was simply answering your questions. These were not suggestions to try. It only came up because the OP mentioned that theyâd added âxf86-video-amdgpuâ, and that (not surprisingly) it hadnât helped. Anyway, letâs try to keep this thread on track.
I specifically suggested GDM to start with. It should allow choosing of the Plasma X11 session.
https://en.opensuse.org/SDB:Change_Display_Manager
Ok but I shall have too install gdm first as it is not in my sytem. I shall try that now but to change my display manager I had been using the command:-
sudo update-alternatives --set default-displaymanager /usr/lib/X11/displaymanagers/lightdm
I can do this and substitute gdm for lightdm but please can you explain why this is then shown as âmanualâ
How else should I change the dm?