System boots only in recovery mode

I’ve install the latest Nvidia drivers (Hard Way) 384.90 and system boots only in recovery mode. Everything seems to be working, but it’s strange. When I try to boot in regular way, the system freeze after few seconds. The last output on terminal is:

SP5100_tco: I/O adress 0x0cd6 already in use

Do you know, what might be wrong?

Graphics card: Nvidia 1060
System: Tumbleweed
CPU: AMD Ryzen 5

See the Logs.



journlactl -b

The Journalctl contains entries only from the last boot (recovery mode), which is OK. I don’t know, how to get the log from the previous regular boot, which stuck.

I’ve notice just one suspisious part of the Xorg log:


    53.406] (II) NVIDIA(0):     "nvidia-auto-select+0+0{ForceFullCompositionPipeline=On}"
    53.406] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1200
    53.415] (--) NVIDIA(0): DPI set to (93, 95); computed from "UseEdidDpi" X config
    53.415] (--) NVIDIA(0):     option
    53.415] (--) Depth 24 pixmap format is 32 bpp
    53.417] (II) NVIDIA: Using 24576.00 MB of virtual memory for indirect memory
    53.417] (II) NVIDIA:     access.
    53.421] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
    53.421] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
    53.421] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
    53.421] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
    53.421] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
    53.421] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
    53.421] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
    53.421] (II) NVIDIA(0):     Config Options in the README.
    53.447] (II) NVIDIA(0): Setting mode "nvidia-auto-select+0+0{ForceFullCompositionPipeline=On}"
    53.489] (==) NVIDIA(0): Disabling shared memory pixmaps
    53.489] (==) NVIDIA(0): Backing store enabled
    53.489] (==) NVIDIA(0): Silken mouse enabled
    53.489] (==) NVIDIA(0): DPMS enabled

What’s a difference between the regular and recovery boot. The recovery works fine, the KDE starts, nvidia driver works.

hwinfo --gfxcard

43: PCI 2600.0: 0300 VGA compatible controller (VGA)            
  [Created at pci.378]
  Unique ID: UU1w.P8I4afAkJjA
  Parent ID: w+J7.0TU4LKoL980
  SysFS ID: /devices/pci0000:00/0000:00:03.1/0000:26:00.0
  SysFS BusID: 0000:26:00.0
  Hardware Class: graphics card
  Model: "nVidia GP106 [GeForce GTX 1060 6GB]"
  Vendor: pci 0x10de "nVidia Corporation"
  Device: pci 0x1c03 "GP106 [GeForce GTX 1060 6GB]"
  SubVendor: pci 0x3842 " Corp."
  SubDevice: pci 0x6161 
  Revision: 0xa1
  Driver: "nvidia"
  Driver Modules: "nvidia"
  Memory Range: 0xf6000000-0xf6ffffff (rw,non-prefetchable)
  Memory Range: 0xe0000000-0xefffffff (ro,non-prefetchable)
  Memory Range: 0xf0000000-0xf1ffffff (ro,non-prefetchable)
  I/O Ports: 0xf000-0xf07f (rw)
  Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled)
  IRQ: 43 (135677 events)
  Module Alias: "pci:v000010DEd00001C03sv00003842sd00006161bc03sc00i00"
  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=no, avail=yes, need=no, active=unknown
  Attached to: #31 (PCI bridge)

Primary display adapter: #43

It has to do something with the Plymouth (boot splash). When I disable it in the Grub config, it boots OK.

I have run into the same condition where installation of the NVIDIA 384.98-29.1 (recommended way) does not work from the default boot selection in GRUB2. I also end up with a blank screen. However, if I use the Advanced Recovery boot option (kernel 4.4.92-31-default) it boots fine. This was sending me around in circles for a few days…

I did just note that nvidia-gfxG04-kmp-default (which was also installed the recommended way) is tagged as 384.98_k4.4.76_1-29.1.

Does anyone know if this kernel version mismatch might be causing the issue?

Right now I have a system that is usable, and I need to get some productivity going after the last few days, so not really looking at chasing that rabbit hole right now, but I thought that I’d throw that out there for others to consider…

Graphics card: Nvidia GeForce GTX 1060
System: Leap 42.3 (new install)
MB: ASRock X399 Fatal1ty
CPU: AMD Ryzen Threadripper 1950X
RAM: Corsair 64 GB DDR4 2667