Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: Patches/Updates 16th March 2018 - X-Server dies - need to use recovery mode

  1. #1
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,569

    Exclamation Patches/Updates 16th March 2018 - X-Server dies - need to use recovery mode

    Following today's patches and updates, KDE SDDM doesn't present the login screen any more: I have to use the SysRq reboot to recover and then choose the Recovery Mode at the Boot screen to be able to login to a KDE session.

    The packages updated/patched today were: libsolv-tools; python-solv; zypper-log; libzypp; zypper; zypper-aptitude; kernel-firmware; libsystemd0; libsystemd0-32bit; libudev1; messagelib; systemd-32bit; systemd-bash-completion; ucode-amd; wireless-regdb; messagelib-lang; systemd; udev; systemd-sysvinit; systemd-logger.

    Haven't yet worked out which one is causing the issue -- will update later assuming that, no one else discovers the culprit …

    The journal entry for the "bad" boot is:
    Code:
    Mär 16 12:16:10 eck001 systemd[1]: Started Locale Service.
    Mär 16 12:16:10 eck001 systemd[1]: Received SIGRTMIN+21 from PID 246 (plymouthd).
    Mär 16 12:16:10 eck001 sddm[2622]: Initializing...
    Mär 16 12:16:10 eck001 sddm[2622]: Starting...
    Mär 16 12:16:10 eck001 sddm[2622]: Adding new display on vt 7 ...
    Mär 16 12:16:10 eck001 sddm[2622]: Display server starting...
    Mär 16 12:16:10 eck001 sddm[2622]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{4526d8ea-5a20-479a-85ac-aadeb9d3544f} -background none -noreset -displayfd 18 vt7
    Mär 16 12:16:10 eck001 SuSEfirewall2[1990]: Firewall rules successfully set
    Mär 16 12:16:10 eck001 systemd[1]: Started SuSEfirewall2 phase 2.
    Mär 16 12:16:11 eck001 sddm[2622]: Setting default cursor
    Mär 16 12:16:11 eck001 sddm[2622]: Running display setup script  "/etc/X11/xdm/Xsetup"
    Mär 16 12:16:11 eck001 sddm[2622]: Display server started.
    Mär 16 12:16:11 eck001 sddm[2622]: Socket server starting...
    Mär 16 12:16:11 eck001 sddm[2622]: Socket server started.
    Mär 16 12:16:11 eck001 sddm[2622]: Greeter starting...
    Mär 16 12:16:11 eck001 sddm[2622]: Adding cookie to "/run/sddm/{4526d8ea-5a20-479a-85ac-aadeb9d3544f}"
    Mär 16 12:16:11 eck001 display-manager[2368]: Starting service sddm/usr/bin/xauth: (stdin):1:  bad "remove" command line
    Mär 16 12:16:11 eck001 display-manager[2368]: /usr/bin/xauth: (stdin):2:  bad "add" command line
    Mär 16 12:16:11 eck001 sddm[2622]: Display server stopped.
    Mär 16 12:16:11 eck001 sddm[2622]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
    Mär 16 12:16:11 eck001 sddm[2622]: Socket server stopping...
    Mär 16 12:16:11 eck001 sddm[2622]: Socket server stopped.
    Mär 16 12:16:11 eck001 sddm[2622]: Removing display "" ...
    Mär 16 12:16:11 eck001 sddm[2622]: Adding new display on vt 7 ...
    Mär 16 12:16:11 eck001 sddm[2622]: Display server starting...
    Mär 16 12:16:11 eck001 sddm[2622]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{40097c77-f298-4b9d-99c6-6543011d9b45} -background none -noreset -displayfd 20 vt7
    Mär 16 12:16:11 eck001 sddm-helper[2809]: [PAM] Starting...
    Mär 16 12:16:11 eck001 sddm-helper[2809]: [PAM] Authenticating...
    Mär 16 12:16:11 eck001 sddm-helper[2809]: [PAM] returning.
    Mär 16 12:16:11 eck001 sddm[2622]: Setting default cursor
    Mär 16 12:16:11 eck001 sddm[2622]: Running display setup script  "/etc/X11/xdm/Xsetup"
    Mär 16 12:16:11 eck001 sddm[2622]: Display server started.
    Mär 16 12:16:11 eck001 sddm[2622]: Socket server starting...
    Mär 16 12:16:11 eck001 sddm[2622]: Socket server started.
    Mär 16 12:16:11 eck001 sddm[2622]: Greeter starting...
    Mär 16 12:16:11 eck001 sddm[2622]: Adding cookie to "/run/sddm/{40097c77-f298-4b9d-99c6-6543011d9b45}"
    Mär 16 12:16:11 eck001 display-manager[2368]: /usr/bin/xauth: (stdin):1:  bad "remove" command line
    Mär 16 12:16:11 eck001 display-manager[2368]: /usr/bin/xauth: (stdin):2:  bad "add" command line
    Mär 16 12:16:11 eck001 sddm[2622]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
    Mär 16 12:16:11 eck001 sddm[2622]: Display server stopped.
    Mär 16 12:16:11 eck001 sddm[2622]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
    Mär 16 12:16:11 eck001 sddm[2622]: Socket server stopping...
    Mär 16 12:16:11 eck001 sddm[2622]: Socket server stopped.
    Mär 16 12:16:11 eck001 sddm[2622]: Removing display "" ...
    Mär 16 12:16:11 eck001 sddm[2622]: Adding new display on vt 7 ...
    Mär 16 12:16:11 eck001 sddm[2622]: Display server starting...
    Mär 16 12:16:11 eck001 sddm[2622]: Running: /usr/bin/X -nolisten tcp -auth /run/sddm/{15486f61-a0e5-435c-bc36-05411930f878} -background none -noreset -displayfd 20 vt7
    Mär 16 12:16:11 eck001 sddm-helper[2824]: [PAM] Starting...
    Mär 16 12:16:11 eck001 sddm-helper[2824]: [PAM] Authenticating...
    Mär 16 12:16:11 eck001 sddm-helper[2824]: [PAM] returning.
    Mär 16 12:16:11 eck001 sddm[2622]: Setting default cursor
    Mär 16 12:16:11 eck001 sddm[2622]: Running display setup script  "/etc/X11/xdm/Xsetup"
    Mär 16 12:16:11 eck001 sddm[2622]: Display server started.
    Mär 16 12:16:11 eck001 sddm[2622]: Socket server starting...
    Mär 16 12:16:11 eck001 sddm[2622]: Socket server started.
    Mär 16 12:16:11 eck001 sddm[2622]: Greeter starting...
    Mär 16 12:16:11 eck001 sddm[2622]: Adding cookie to "/run/sddm/{15486f61-a0e5-435c-bc36-05411930f878}"
    Mär 16 12:16:11 eck001 display-manager[2368]: /usr/bin/xauth: (stdin):1:  bad "remove" command line
    Mär 16 12:16:11 eck001 display-manager[2368]: /usr/bin/xauth: (stdin):2:  bad "add" command line
    Mär 16 12:16:11 eck001 sddm[2622]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
    Mär 16 12:16:11 eck001 sddm[2622]: Display server stopped.
    Mär 16 12:16:11 eck001 sddm[2622]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
    Mär 16 12:16:11 eck001 sddm[2622]: Socket server stopping...
    Mär 16 12:16:11 eck001 sddm[2622]: Socket server stopped.
    Mär 16 12:16:11 eck001 sddm[2622]: Removing display "" ...
    Mär 16 12:16:11 eck001 sddm[2622]: Adding new display on vt 7 ...
    Mär 16 12:16:11 eck001 sddm[2622]: Display server starting...

  2. #2

    Default Re: Patches/Updates 16th March 2018 - X-Server dies - need to use recovery mode

    Quote Originally Posted by dcurtisfra View Post
    The journal entry for the "bad" boot is:
    Doesn't show much (except that plymouth is crashing, but that shouldn't cause the problem, you could try to disable it though with the "plymouth.enable=0" boot option).
    What's in /var/log/Xorg.0.log? (or /var/log/Xorg.0.log, which is the log from the previous boot)

    From the updates you mention, the most likely ones would be systemd or kernel-firmware I think.
    So try to revert them first.

    I don't have a problem here, but I haven't installed these updates yet (and if it's a problem with kernel-firmware, it may be highly hardware specific anyway).
    Last edited by wolfi323; 16-Mar-2018 at 05:54.

  3. #3
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,569

    Default Re: Patches/Updates 16th March 2018 - X-Server dies - need to use recovery mode

    Quote Originally Posted by wolfi323 View Post
    What's in /var/log/Xorg.0.log? (or /var/log/Xorg.0.log, which is the log from the previous boot)
    Something is weird with the Xorg logs:
    Code:
     > l -t /var/log/Xorg.*
    -rw-r--r-- 1 root root  19737 16. Mär 15:04 /var/log/Xorg.0.log
    -rw-r--r-- 1 root root      0 16. Mär 15:03 /var/log/Xorg.0.log.old
    -rw-r--r-- 1 root root  44113 26. Jan 10:29 /var/log/Xorg.1.log
    -rw-r--r-- 1 root root  43847 13. Dez 15:25 /var/log/Xorg.1.log.old
    -rw-r--r-- 1 root root 100518 28. Aug 2017  /var/log/Xorg.2.log
    -rw-r--r-- 1 root root  58724 28. Aug 2017  /var/log/Xorg.4.log
    -rw-r--r-- 1 root root  63245 28. Aug 2017  /var/log/Xorg.3.log
    -rw-r--r-- 1 root root  63083 23. Aug 2017  /var/log/Xorg.2.log.old
     >
    The one timestamped "16. Mär 15:04" is the one from this boot and, it doesn't have anything extraordinary marked with the 'WW' and 'EE' flags:
    Code:
     > grep -E 'WW|EE' /var/log/Xorg.0.log
            (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [    13.770] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist.
    [    13.791] (WW) Warning, couldn't open module vboxvideo
    [    13.791] (EE) Failed to load module "vboxvideo" (module does not exist, 0)
    [    13.791] (WW) Warning, couldn't open module vmware
    [    13.791] (EE) Failed to load module "vmware" (module does not exist, 0)
    [    13.817] (EE) open /dev/dri/card0: No such file or directory
    [    13.817] (WW) Falling back to old probe method for modesetting
    [    13.817] (EE) open /dev/dri/card0: No such file or directory
    [    13.818] (WW) Falling back to old probe method for vesa
    [    13.818] (EE) Screen 0 deleted because of no matching config section.
    [    13.831] (EE) AIGLX: reverting to software rendering
     >
    I've also removed the outdated Xorg logs.

    I've rolled the updates and patches back in 2 stages:
    Code:
    kernel-firmware wird heruntergeladen (Downloadgröße 42,49 MiB)
    libudev1 wird heruntergeladen (Downloadgröße 330,3 KiB)
    systemd wird heruntergeladen (Downloadgröße 3,70 MiB)
    ucode-amd wird heruntergeladen (Downloadgröße 42,9 KiB)
    udev wird heruntergeladen (Downloadgröße 1,26 MiB)
    systemd-sysvinit wird heruntergeladen (Downloadgröße 286,6 KiB)
    kernel-firmware-20170530-14.1.noarch.rpm wird installiert (Größe nach Installation 191,04 MiB)
    libudev1-228-44.1.x86_64.rpm wird installiert (Größe nach Installation 130,3 KiB)
    systemd-228-44.1.x86_64.rpm wird installiert (Größe nach Installation 20,61 MiB)
    ucode-amd-20170530-14.1.noarch.rpm wird installiert (Größe nach Installation 31,8 KiB)
    udev-228-44.1.x86_64.rpm wird installiert (Größe nach Installation 6,56 MiB)
    systemd-sysvinit-228-44.1.x86_64.rpm wird installiert (Größe nach Installation 5,3 KiB)
    
    wireless-regdb wird heruntergeladen (Downloadgröße 9,3 KiB)
    libsystemd0 wird heruntergeladen (Downloadgröße 519,6 KiB)
    libsystemd0-32bit wird heruntergeladen (Downloadgröße 522,7 KiB)
    messagelib wird heruntergeladen (Downloadgröße 5,00 MiB)
    systemd-bash-completion wird heruntergeladen (Downloadgröße 291,4 KiB)
    systemd-logger wird heruntergeladen (Downloadgröße 281 KiB)
    messagelib-lang wird heruntergeladen (Downloadgröße 705,6 KiB)
    wireless-regdb-2017.03.07-4.1.noarch.rpm wird installiert (Größe nach Installation 6 KiB)
    libsystemd0-228-44.1.x86_64.rpm wird installiert (Größe nach Installation 788,4 KiB)
    libsystemd0-32bit-228-44.1.x86_64.rpm wird installiert (Größe nach Installation 848,1 KiB)
    messagelib-17.04.2-6.1.x86_64.rpm wird installiert (Größe nach Installation 8,74 MiB)
    systemd-bash-completion-228-44.1.noarch.rpm wird installiert (Größe nach Installation 74,4 KiB)
    systemd-logger-228-44.1.x86_64.rpm wird installiert (Größe nach Installation 1 KiB)
    messagelib-lang-17.04.2-6.1.noarch.rpm wird installiert (Größe nach Installation 5,33 MiB)
    No change -- will reinstall them.

    Hope that I don't have a coincidental hardware breakage …

  4. #4

    Default Re: Patches/Updates 16th March 2018 - X-Server dies - need to use recovery mode

    Quote Originally Posted by dcurtisfra View Post
    Something is weird with the Xorg logs:
    Code:
     > l -t /var/log/Xorg.*
    -rw-r--r-- 1 root root  19737 16. Mär 15:04 /var/log/Xorg.0.log
    -rw-r--r-- 1 root root      0 16. Mär 15:03 /var/log/Xorg.0.log.old
    -rw-r--r-- 1 root root  44113 26. Jan 10:29 /var/log/Xorg.1.log
    -rw-r--r-- 1 root root  43847 13. Dez 15:25 /var/log/Xorg.1.log.old
    -rw-r--r-- 1 root root 100518 28. Aug 2017  /var/log/Xorg.2.log
    -rw-r--r-- 1 root root  58724 28. Aug 2017  /var/log/Xorg.4.log
    -rw-r--r-- 1 root root  63245 28. Aug 2017  /var/log/Xorg.3.log
    -rw-r--r-- 1 root root  63083 23. Aug 2017  /var/log/Xorg.2.log.old
     >
    The one timestamped "16. Mär 15:04" is the one from this boot and, it doesn't have anything extraordinary marked with the 'WW' and 'EE' flags:
    That's obviously the one from recovery mode, otherwise it wouldn't try to load "vmware" and "vboxvideo"...

    Xorg.0.log.old would likely be the one from the previous normal boot, but unfortunately that's empty (which means that X is apparently crashing quite early before it even writes anything to the file)

    Is there a coredump listed by coredumptctl?
    Can you get to a graphical system by running startx in text mode? (as root)

    Another thing that might be interesting is switching to a different display manager and see if that works. If it does, the Xorg log may be interesting as well.

    I've rolled the updates and patches back in 2 stages:
    No change -- will reinstall them.
    ucode-intel may be the culprit too (especially if it's an intel system), so try to revert it as well.
    Last edited by wolfi323; 16-Mar-2018 at 07:37.

  5. #5
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,569

    Unhappy Re: Patches/Updates 16th March 2018 - X-Server dies - need to use recovery mode

    Quote Originally Posted by wolfi323 View Post
    (which means that X is apparently crashing quite early before it even writes anything to the file)
    That's exactly what's happening …

    Quote Originally Posted by wolfi323 View Post
    Is there a coredump listed by coredumptctl?
    No.

    Quote Originally Posted by wolfi323 View Post
    Can you get to a graphical system by running startx in text mode? (as root)
    I'm in KDE Plasma 5 now, from the recovery mode -- no compositing …

    BTW: it's impossible to login into a TTY -- SDDM and X are consuming too much CPU … The flashing display they're producing is making the keyboard unresponsive …

    Quote Originally Posted by wolfi323 View Post
    Another thing that might be interesting is switching to a different display manager and see if that works. If it does, the Xorg log may be interesting as well.
    I'll take a look …

    Quote Originally Posted by wolfi323 View Post
    ucode-intel may be the culprit too (especially if it's an intel system), so try to revert it as well.
    I re-installed all the updates/patches, including the 'ucode-intel' patch which arrived after I hit the issue being worked here:
    Code:
    kernel-firmware wird heruntergeladen (Downloadgröße 42,49 MiB)
    Delta-RPM ./noarch/kernel-firmware-20170530-14.1_17.1.noarch.drpm wird heruntergeladen (Downloadgröße 308,2 KiB)
    Delta-RPM wird angewendet: /var/cache/zypp/packages/download.opensuse.org-oss_4/noarch/kernel-firmware-20170530-14.1_17.1.noarch.drpm
    libsystemd0 wird heruntergeladen (Downloadgröße 520 KiB)
    libsystemd0-32bit wird heruntergeladen (Downloadgröße 523,2 KiB)
    libudev1 wird heruntergeladen (Downloadgröße 330,8 KiB)
    messagelib wird heruntergeladen (Downloadgröße 5,00 MiB)
    Delta-RPM ./x86_64/messagelib-17.04.2-6.1_9.1.x86_64.drpm wird heruntergeladen (Downloadgröße 57,8 KiB)
    Delta-RPM wird angewendet: /var/cache/zypp/packages/download.opensuse.org-oss_4/x86_64/messagelib-17.04.2-6.1_9.1.x86_64.drpm
    systemd-bash-completion wird heruntergeladen (Downloadgröße 291,8 KiB)
    ucode-amd wird heruntergeladen (Downloadgröße 43 KiB)
    wireless-regdb wird heruntergeladen (Downloadgröße 14,1 KiB)
    ucode-intel wird heruntergeladen (Downloadgröße 1,20 MiB)
    messagelib-lang wird heruntergeladen (Downloadgröße 705,5 KiB)
    Delta-RPM ./noarch/messagelib-lang-17.04.2-6.1_9.1.noarch.drpm wird heruntergeladen (Downloadgröße 47,7 KiB)
    Delta-RPM wird angewendet: /var/cache/zypp/packages/download.opensuse.org-oss_4/noarch/messagelib-lang-17.04.2-6.1_9.1.noarch.drpm
    systemd wird heruntergeladen (Downloadgröße 3,70 MiB)
    Delta-RPM ./x86_64/systemd-228-44.1_47.1.x86_64.drpm wird heruntergeladen (Downloadgröße 394,8 KiB)
    Delta-RPM wird angewendet: /var/cache/zypp/packages/download.opensuse.org-oss_4/x86_64/systemd-228-44.1_47.1.x86_64.drpm
    udev wird heruntergeladen (Downloadgröße 1,26 MiB)
    Delta-RPM ./x86_64/udev-228-44.1_47.1.x86_64.drpm wird heruntergeladen (Downloadgröße 299 KiB)
    Delta-RPM wird angewendet: /var/cache/zypp/packages/download.opensuse.org-oss_4/x86_64/udev-228-44.1_47.1.x86_64.drpm
    systemd-sysvinit wird heruntergeladen (Downloadgröße 287,1 KiB)
    systemd-logger wird heruntergeladen (Downloadgröße 281,4 KiB)
    kernel-firmware-20170530-17.1.noarch.rpm wird installiert (Größe nach Installation 191,04 MiB)
    libsystemd0-228-47.1.x86_64.rpm wird installiert (Größe nach Installation 788,4 KiB)
    libsystemd0-32bit-228-47.1.x86_64.rpm wird installiert (Größe nach Installation 848,1 KiB)
    libudev1-228-47.1.x86_64.rpm wird installiert (Größe nach Installation 130,3 KiB)
    messagelib-17.04.2-9.1.x86_64.rpm wird installiert (Größe nach Installation 8,74 MiB)
    systemd-bash-completion-228-47.1.noarch.rpm wird installiert (Größe nach Installation 74,4 KiB)
    ucode-amd-20170530-17.1.noarch.rpm wird installiert (Größe nach Installation 31,8 KiB)
    wireless-regdb-2017.12.23-5.3.2.noarch.rpm wird installiert (Größe nach Installation 13 KiB)
    ucode-intel-20180312-22.1.x86_64.rpm wird installiert (Größe nach Installation 3,20 MiB)
    messagelib-lang-17.04.2-9.1.noarch.rpm wird installiert (Größe nach Installation 5,33 MiB)
    systemd-228-47.1.x86_64.rpm wird installiert (Größe nach Installation 20,61 MiB)
    udev-228-47.1.x86_64.rpm wird installiert (Größe nach Installation 6,56 MiB)
    systemd-sysvinit-228-47.1.x86_64.rpm wird installiert (Größe nach Installation 5,3 KiB)
    systemd-logger-228-47.1.x86_64.rpm wird installiert (Größe nach Installation 1 KiB)
    No change …

  6. #6
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,569

    Unhappy Re: Patches/Updates 16th March 2018 - X-Server dies - need to use recovery mode

    Forgot to mention that, "/var/lib/sddm/.local/share/sddm/xorg-session.log" contains (only 1 line):
    Code:
    QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei oder Verzeichnis nicht gefunden

  7. #7

    Default Re: Patches/Updates 16th March 2018 - X-Server dies - need to use recovery mode

    Quote Originally Posted by dcurtisfra View Post
    BTW: it's impossible to login into a TTY -- SDDM and X are consuming too much CPU … The flashing display they're producing is making the keyboard unresponsive …
    Then stop the display-manager.service (or boot to runlevel 3/multiuser.target in the first place).
    SDDM will restart again and again if X fails to start.

    Quote Originally Posted by dcurtisfra View Post
    Forgot to mention that, "/var/lib/sddm/.local/share/sddm/xorg-session.log" contains (only 1 line):
    Code:
    QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei oder Verzeichnis nicht gefunden
    Irrelevant.

    That's from the *user* session (sddm runs as user sddm and /var/lib/sddm/ is its home directory), not X itself. Also, it's from the *current* boot, not the previous one.

  8. #8
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    4,569

    Unhappy Re: Patches/Updates 16th March 2018 - X-Server dies - need to use recovery mode

    The misery is due to something which has changed in X11 with respect to an AMD OLAND card and the 'radeon' driver: the 'radeon' quirks no longer apply:
    In /etc/X11/xorg.conf.d/: "50-device.conf"; the previous setting no longer works:
    Code:
     # xrandr -q
    xrandr: Failed to get size of gamma for output default
    Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
    default connected primary 1920x1080+0+0 0mm x 0mm
       1920x1080     77.00* 
     #
    Previously, "DVI-0" was hinted -- commenting out the "Device" section in '/etc/X11/xorg.conf.d/50-device.conf' cured the issue for the moment but, compositing no longer works as it should do -- the OpenGL renderer is currently with a 'llvmpipe' in place of the AMD OLAND hardware.
    The AMD vdpau libraries are installed: libvdpau_r300; libvdpau_r600; libvdpau_radeonsi; but:
    Code:
     > vdpauinfo
    display: :0   screen: 0
    Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
    Error creating VDPAU device: 1
     >
    For what ever reason the AMD support seems to have disappeared …

    Or, the the AMD OLAND card has suddenly died -- for whatever reason …

  9. #9

    Default Re: Patches/Updates 16th March 2018 - X-Server dies - need to use recovery mode

    Quote Originally Posted by dcurtisfra View Post
    The misery is due to something which has changed in X11 with respect to an AMD OLAND card and the 'radeon' driver: the 'radeon' quirks no longer apply:
    In /etc/X11/xorg.conf.d/: "50-device.conf"; the previous setting no longer works:
    If you boot to recovery mode, 50-device.conf is ignored.
    Also, you will use a generic fallback driver, and not radeon.

    Previously, "DVI-0" was hinted -- commenting out the "Device" section in '/etc/X11/xorg.conf.d/50-device.conf' cured the issue for the moment but, compositing no longer works as it should do -- the OpenGL renderer is currently with a 'llvmpipe' in place of the AMD OLAND hardware.
    llvmpipe is Mesa's software OpenGL renderer, that's normal in recovery mode.

    The AMD vdpau libraries are installed: libvdpau_r300; libvdpau_r600; libvdpau_radeonsi; but:
    VDPAU has nothing to do with OpenGL or compositing though. That's just hardware accelerated decoding of video streams, i.e. hardware accerated movie playback.

    For what ever reason the AMD support seems to have disappeared …
    As indicated, that's normal in recovery mode.
    The question is what happens on a normal boot.

    Again, try with e.g. xdm, and/or run startx directly from text mode to test whether it works then.
    And look (or provide) the Xorg log, that should at least show which driver is used then.

    Or, the the AMD OLAND card has suddenly died -- for whatever reason …
    Might indeed be a possibility.

    FWIW, I have absolutely no problem after installing the recent updates on two different 42.3 systems (radeon and intel).
    Last edited by wolfi323; 16-Mar-2018 at 12:50.

  10. #10

    Default Re: Patches/Updates 16th March 2018 - X-Server dies - need to use recovery mode

    Quote Originally Posted by wolfi323 View Post
    The question is what happens on a normal boot.

    Again, try with e.g. xdm, and/or run startx directly from text mode to test whether it works then.
    And look (or provide) the Xorg log, that should at least show which driver is used then.
    PS: if I understand your last post correctly, removing 50-device.conf "fixed" your problem with normal boot?
    Then likely radeon cannot be loaded, and you had a line 'Driver "radeon"' in there, which would cause X to error out in that case.

    Without the file, X will fall back to a different/generic driver.

    Still strange that the X log was empty though, this should actually show up in there.
    Maybe you rebooted your system at a time when X currently tried to start, i.e. when it just had created the log but not written anything yet...

    Anyway, can you provide a log now?
    Last edited by wolfi323; 16-Mar-2018 at 12:48.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •