I could be wrong, but doesn’t Plasma now enables Wayland also?
Wayland can be enabled under Plasma5, but the last time I tried to do so, it did not work at all, so I am using xorg.
1 Like
Ah, okay so it isn’t enabled by default, the search for the solution continues then.
Another kernel update this morning. Did you get the same issue again or you haven’t tried it? 5.3.1
There is another kernel update 5.3.1 you can try.
1 Like
5.3.1 is installed. Still no success with booting.
@Jeannie You say you are running Plasma. I have Cinnamon with dual boot Windows 10 running an Intel I7 8086K processor and Nvidia GTX1060 running Nvidia-DKMS drivers. I don’t have this issue maybe i will install the lts kernel and see. This doesn’t make any sense to me as i have had 3 kernels running before on DKMS with no update issues. But I’m not running plasma?
Update:
I can log in to a console in kernel 5.3. When I run “starx”, I get something like three white console windows on a black background and a working mouse pointer. I can even start programmes by typing their names into one of these terminals ( e.g. Firefox). I get a strange error message though when I try to start sddm in one of these terminals.
Wondering, if it’s sddm related. If it is, why doesn’t this happen on the lts kernel?
J.
I don’t know but maybe? I’m not big on Plasma and don’t have much experience with it although i have installed it many times and tried to set it up. 
I think you are going to have to look at some boot logs trying to boot into 5.3 kernel. Plus other logs to see why it’s not working. Does it run on xorg? or Wayland. Check the xorg log. etc dmesg? systemctl --failed? Some of these things might provide an answer?
Just to make some things sure, could you please show the output of the these commands:
lspci -vnn | grep -Pw '0300|0302|0380' pacman -Qs nvidia pacman -Q linux-headers lsmod|grep nouveau
[jeannie@p707 ~]$ lspci -vnn | grep -Pw ‘0300|0302|0380’
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev a1) (prog-if 00 [VGA controller])
[jeannie@p707 ~]$ pacman -Qs nvidia
local/libvdpau 1.3-1
Nvidia VDPAU library
local/libxnvctrl-390xx 390.129-1
NVIDIA NV-CONTROL X extension, 390xx legacy branch
local/nvidia-dkms 435.21-7
NVIDIA driver sources for linux
local/nvidia-settings 435.21-1
Tool for configuring the NVIDIA graphics driver
local/nvidia-utils 435.21-1
NVIDIA drivers utilities
local/opencl-nvidia-340xx 340.107-3
OpenCL implemention for NVIDIA
local/xf86-video-nouveau 1.0.16-1 (xorg-drivers)
Open Source 3D acceleration driver for nVidia cards
[jeannie@p707 ~]$ pacman -Q linux-headers
linux-headers 5.3.1.arch1-1
[jeannie@p707 ~]$ lsmod|grep nouveau
[jeannie@p707 ~]
It looks like you got two different drivers files? The GTX 1060 should be using the 435 series drivers on both lts and current kernel.
It’s indeed strange that the libxnvctrl390xx is installed instead of libxnvctrl.
J.
Replacing libxnvctrl390xx with libxnvctrl (version 435.whatever) indeed seems to have solved it, the system now boots into the desktop with Kernel 5.3.1.
Thanks @ricklinux for pointing me in that direction…
J.
I see 390 driver files and 340 driver files and I do not see lts headers. Your card is the same as mine GeForce GTX1060 and it takes the 435 series drivers. It doesn’t matter whether you are installing Nvidia or the nvidia-dkms it’s the same driver base. The dkms version is the one to use if you have both kernels installed. The current kernel and the lts kernel. But, you have to have linux-headers and linux-lts-headers installed also to use it. So I’m waiting for @manuel to look at it and give some instruction. He is the expert. But just from what I see I think you may end up removing all nvidia and reinstalling properly with both headers and nvidia-dkms. They have an installer now for it. I’m not sure how you originally installed it. I usually install nvidia with pacman separately then install dkms version but now with the installer I can use it. I would like to see what he thinks.
Well that was an easier fix than I thought it would be. I thought maybe you were going to have to clean out all Nvidia and reinstall. 
This is what my files show.
[rick@endeavour-os ~]$ lspci -vnn | grep -Pw '0300|0302|0380'
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP104 [GeForce GTX 1060 6GB] [10de:1b83] (rev a1) (prog-if 00 [VGA controller])
[rick@endeavour-os ~]$ pacman -Qs nvidia
local/lib32-libvdpau 1.3-1
Nvidia VDPAU library
local/lib32-nvidia-utils 435.21-1
NVIDIA drivers utilities (32-bit)
local/libvdpau 1.3-1
Nvidia VDPAU library
local/libxnvctrl 435.21-1
NVIDIA NV-CONTROL X extension
local/nvidia-dkms 435.21-7
NVIDIA driver sources for linux
local/nvidia-installer-db 2.1-2
Database for the script to setup nvidia drivers in EndeavourOS
local/nvidia-installer-dkms 2.1-8
Script to setup nvidia drivers (dkms version) in EndeavourOS
local/nvidia-settings 435.21-1
Tool for configuring the NVIDIA graphics driver
local/nvidia-utils 435.21-1
NVIDIA drivers utilities
[rick@endeavour-os ~]$ pacman -Q linux-headers
linux-headers 5.3.1.arch1-1
[rick@endeavour-os ~]$ lsmod|grep nouveau
[rick@endeavour-os ~]$
I guess the reason it doesn’t show the lts headers is because i am booted into the current kernel. So you should not have any 390 or 340 version files.
Actually it still only shows the linux headers for the current kernel even when booted into the lts because that’s what the command is asking for.
This file is not correct either. I think there is a 435 series opencl also. I’m not using it so i don’t have it installed. So it’s not necessary unless you need it for an opencl application i guess. I do have lib32-nvidia-libgl installed as it is required for some 32 bit steam games.
@Jeannie Just a thought here isn’t the 340xx file a residue from a previous system with an older Nvidia card that ran the 340xx driver?
I remember that you and I had the same problem on the Antergos forum with the Nvidia 340xx driver two years ago. (Unless I’m wrong 
)
Also xf86-video-nouveau should be removed
This system is driving me nuts.
The following happens:
If I try to boot into Kernel 5.3.1, the desktop environment won’t start, so I boot into kernel 4.19.
Here, the desktop environment starts.
I reinstall the nvidia-dkms driver and run a mkinitcpio -P afterwards and reboot into kernel 5.3.1
Now the desktop environment starts and I can use the system until I shut it down.
When I restart it and try to boot into kernel 5.3.1, the desktop environment won’t start, so I boot into kernel 4.19
Here the desktop environment starts.
I reinstall the nvidia-dkms…
J.