The new 4.19 kernel does not work the message is “failed to star x display manager”
That is what I call ‘minimal info’. As you know we need as much info as possible. I can guess that you have an NVIDIA card ( driver build not ready yet ), but guessing is not a method the detect malfunctions, checking proper info, output etc. is
On Wed 14 Nov 2018 05:36:03 PM CST, enziosavio wrote:
The new 4.19 kernel does not work the message is “failed to star x
display manager”
Hi
Not if your running the nvidia driver… boot to the older kernel.
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.25-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Sorry, yes Nvidia, in the messages says to check systemctl status display-manager.service
enziosavio@linux-area51:~> sudo systemctl status display-manager.service
● display-manager.service - X Display Manager
Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2018-11-14 18:22:46 CET; 21min ago
Process: 822 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS)
Main PID: 1021 (lightdm)
Tasks: 5 (limit: 4915)
CGroup: /system.slice/display-manager.service
├─1021 /usr/sbin/lightdm
└─1041 /usr/bin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
nov 14 18:22:45 linux-area51 systemd[1]: Starting X Display Manager...
nov 14 18:22:45 linux-area51 display-manager[822]: /etc/vconsole.conf available
nov 14 18:22:45 linux-area51 display-manager[822]: KEYMAP: it
nov 14 18:22:45 linux-area51 display-manager[822]: Command: localectl set-keymap it
nov 14 18:22:45 linux-area51 display-manager[822]: I: Using systemd /usr/share/systemd/kbd-model-map mapping
nov 14 18:22:45 linux-area51 root[893]: /etc/init.d/xdm: No changes for /etc/X11/xdm/Xservers
nov 14 18:22:45 linux-area51 root[893]: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config
nov 14 18:22:46 linux-area51 display-manager[822]: Starting service lightdm..done
nov 14 18:22:46 linux-area51 systemd[1]: Started X Display Manager.
Now I’m with the Kernel 4.18
sudo hwinfo --gfxcard
[sudo] password di root:
16: PCI 100.0: 0300 VGA compatible controller (VGA)
[Created at pci.386]
Unique ID: VCu0.LRIsrTxKBxC
Parent ID: _Znp.+eZipJdga28
SysFS ID: /devices/pci0000:00/0000:00:02.0/0000:01:00.0
SysFS BusID: 0000:01:00.0
Hardware Class: graphics card
Model: "nVidia GF119 [GeForce GT 610]"
Vendor: pci 0x10de "nVidia Corporation"
Device: pci 0x104a "GF119 [GeForce GT 610]"
SubVendor: pci 0x3842 "eVga.com. Corp."
SubDevice: pci 0x2615
Revision: 0xa1
Driver: "nvidia"
Driver Modules: "nvidia"
Memory Range: 0xfd000000-0xfdffffff (rw,non-prefetchable)
Memory Range: 0xf0000000-0xf7ffffff (ro,non-prefetchable)
Memory Range: 0xf8000000-0xf9ffffff (ro,non-prefetchable)
I/O Ports: 0xdc00-0xdc7f (rw)
Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled)
IRQ: 30 (75613 events)
I/O Ports: 0x3c0-0x3df (rw)
Module Alias: "pci:v000010DEd0000104Asv00003842sd00002615bc03sc00i00"
Driver Info #0:
Driver Status: nouveau is not active
Driver Activation Cmd: "modprobe nouveau"
Driver Info #1:
Driver Status: nvidia_drm is active
Driver Activation Cmd: "modprobe nvidia_drm"
Driver Info #2:
Driver Status: nvidia is active
Driver Activation Cmd: "modprobe nvidia"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #30 (PCI bridge)
Primary display adapter: #16
Forgive me Knurpth but using the translator I’m slow and awkward, I always have to double check what I want to say and sometimes I can not
Thanks Malcolm I was already using it 
Nvidia driver from Repo?
Up to now, there is no build driver for kernel 4.19 in the Repo:
https://download.nvidia.com/opensuse/tumbleweed/x86_64/
SInce this has happened before, shouldn’t those packages have some dep re. kernel version?
Just my impression but major kernel version updates seem to cause the same old X does not start posts here and on the MLs.
Yes , Nvidia Repo
To be honest it is from the beginning of 2018 that I did not have an X problem caused by the Nvidia Driver from Repo, and there have been many Kernel updates
On Wed 14 Nov 2018 07:16:03 PM CST, Knurpht wrote:
Sauerland;2886357 Wrote:
> Nvidia driver from Repo?
> Up to now, there is no build driver for kernel 4.19 in the Repo:
> Index of /opensuse/tumbleweed/x86_64
SInce this has happened before, shouldn’t those packages have some dep
re. kernel version?
Just my impression but major kernel version updates seem to cause the
same old X does not start posts here and on the MLs.
Hi
Always happens… either need patches to build or build locally the
hard way. Users running proprietary stuff always get bitten as some
point in the rolling release cycle.
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.25-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Matches my experiences, except for major kernel version bumps. This is definitely an NVIDIA issue.
I’ll offer my suggestion, for what it’s worth.
In “/etc/zypp/zypp.conf”, look for the line “multiversion.kernels” and add “oldest” (I put it at the beginning).
That way, the oldest kernel is not automatically removed. So there’s a guaranteed fallback that should work.
When you have current kernels that are working, you can manually remove the oldest kernel, so that a newer one becomes the oldest.
For example, having “oldest” on one of my systems kept the most recent 4.17 kernel around. Today, I removed that. So it will now be keeping a 4.18 kernel around. And I’ll keep that around until I know that I am not having any problems with 4.19 kernels.
I don’t have nvidia graphics, so I really don’t need this. But for those who do have nvidia, it is a good safety move.
The Nvidia driver update has solved
I can confirm that. After a
zypper dup
it works again.