Skip to main content
Topic: Startx opens black screen  (Read 1669 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Startx opens black screen

Okay, before I say anything about my issue, I just want to say that I’m a newbie to this forum and to be honest linux in general, so please don’t go too hard on me. I probably don’t know a lot of the lingo. I’ve only been at this for a year or so.

I’m running Artix runit base on an HP Omen desktop computer. It's a fresh install. All I have on it is some basic command-line utilities and the zen kernel. I also have an nvidia RTX 3080, so I installed the nvidia-dkms package. Obviously, I also have the xorg, xterm, and twm packages installed. For some reason, when I attempt to start xorg with startx (the basic xterm setup copied from /etc/X11/xinit/.xinitrc) it opens a blank screen with no cursor of any kind. I can’t shortcut out of this black screen with ctrl_alt_Fx or ctrl_alt_del. I have to turn off my computer entirely with the button on the case to get back into TTY. I’d send the xorg logs and output of startx if I could, but I honestly don’t know how to send any of that stuff when I only have TTY. Help would be greatly appreciated. Thanks in advance!

UPDATE: playing around in the terminal today, I found that if I uninstalled all the nvidia-dkms packages and installed the nouveau driver, startx worked flawlessly after a reboot. This is clearly an issue relating to nvidia's drivers. In the meantime, I also added the universe and arch repositories. I'd like to use the normal nvidia drivers as I am aware they are superior to the nouveau ones, so what should my course of action be? Will this simply resolve itself next time the nvidia drivers are updated, or can I fix this myself?

Re: Startx opens black screen

Reply #1
Well with dkms you need package versions to match up with kernel versions (you mention the Zen kernel - that could be a question re dkms being supported or going out of version sync, perhaps try with the regular one?) and make sure that you are not mixing Arch and Artix repos when sourcing the dkms and kernel packages. Then the dkms modules have to build against the correct stuff when you install them. As for the nvidia drivers being "superior" personally I've always used nouveau and it's fine unless you really need to get the maximum performance from your graphics. It effectively just means some of the proprietary performance enhancing secret features of your GPU won't get used, but everything displays and works. Nouveau is open source, the Nvidia drivers are closed source, closed source is bad and should be avoided whenever possible.  ;D  Nouveau usually works OOTB too! Probably someone who actually uses nvidia drivers can give you better advice to get them working.  ;)

Re: Startx opens black screen

Reply #2
Well with dkms you need package versions to match up with kernel versions (you mention the Zen kernel - that could be a question re dkms being supported or going out of version sync, perhaps try with the regular one?) and make sure that you are not mixing Arch and Artix repos when sourcing the dkms and kernel packages. Then the dkms modules have to build against the correct stuff when you install them. As for the nvidia drivers being "superior" personally I've always used nouveau and it's fine unless you really need to get the maximum performance from your graphics. It effectively just means some of the proprietary performance enhancing secret features of your GPU won't get used, but everything displays and works. Nouveau is open source, the Nvidia drivers are closed source, closed source is bad and should be avoided whenever possible.  ;D  Nouveau usually works OOTB too! Probably someone who actually uses nvidia drivers can give you better advice to get them working.  ;)

Thanks! That might just work. I want to use the nvidia drivers because I'm gaming on this pc, and the arch wiki says that nvidia-dkms is the preferred package if using the zen kernel. Now, just to be sure, do you mean that I have to make the version number of the kernel the same as the version number of my nvidia drivers, or do I have to research which driver versions are compatible with my kernel? Also, how might I downgrade to an earlier version of the drivers/kernel. Keep in mind that I'm trying to keep my system fairly minimal despite being a gaming setup, so I want to avoid too many fancy tools.

Re: Startx opens black screen

Reply #3
The point to dkms kernel modules is that they don't need to be pre-matched to to the current installed kernel.
Normally when the kernel is updated by a distro the nvidia drivers (and all other distro packaged out of kernel drivers) need to be recompiled and repackaged by the distros devs. Otherwise they don't work.

dkms solves this by moving the recompilation to your local system. Every time the kernel updates all the dkms kernel modules get updated automatically and everything continues to work (in theory).

dkms can have it's advantages even if you are using the standard distro supplied kernel as it can happen that if you upgrade your system while, or soon after the devs, have been updating the kernel package and third party drivers you can get an older version of one and a newer version of another. Another update later should fix this, or a temporary downgrade, but dkms (again in theory) avoids this scenario.

If I was you the first thing I would do would be to look at /var/log/Xorg.0.log after a failed startx with the nvidia driver.

If you want more eyes on it then install pastebinit and run this command
Code: [Select]
cat /var/log/Xorg.0.log | pastebinit -b paste.debian.net
Post the link.
Or copy the file to a usb or send over the network etc. and post the file here on a device with a GUI.

The second thing I would be trying is using the standard Artix kernel with both the normal and dkms nvidia driver and seeing what works. If anything. Try to narrow things down.

Do you have any other errors ? Look in dmesg straight after a boot.

Edit:
I just read your post properly (bad habit of mine).
If you managed to switch to the zen kernel you should be able to switch back.
But therein might lie your nvidia problem if you didn't do it correctly.

Generally imho it's better to stick to the distro supplied kernel and drivers unless you both know how to switch them around and solve problems that may occur.
On the other hand we learn by trying, and breaking, things.

Re: Startx opens black screen

Reply #4
Yes, you are right about the version thing but there are sometimes limits on major version updates I think, and some -Ss searches reveal that there is a 6 series linux-zen kernel on the way in "gremlins" and already in the Arch repo "extra" so at this moment versions could perhaps be relevant, especially as the nvidia-dkms and nvidia-open-dkms packages currently display quite a variety of version numbers looking in gremlins, world and Arch extra repos. Also Artix dkms packages won't work with Arch kernels I have been told, although those will work in other respects, only relevant if you have Arch repos enabled and installed one from there of course. You can install multiple kernels at once and then configure grub (or other bootloader) to boot one by default or pick one from the boot menu screen.

Re: Startx opens black screen

Reply #5
Just another thought:
If your using the linux-zen kernel then you would also need the linux-zen-headers to compile the dkms module.
I'm pretty sure if you didn't install the headers the dkms module would fail to build.  But haven't tested that.

And also an admission that, not for the first time, I'd forgotten linux-zen is packaged by Artix.

Re: Startx opens black screen

Reply #6
The point to dkms kernel modules is that they don't need to be pre-matched to to the current installed kernel.
Normally when the kernel is updated by a distro the nvidia drivers (and all other distro packaged out of kernel drivers) need to be recompiled and repackaged by the distros devs. Otherwise they don't work.

dkms solves this by moving the recompilation to your local system. Every time the kernel updates all the dkms kernel modules get updated automatically and everything continues to work (in theory).

dkms can have it's advantages even if you are using the standard distro supplied kernel as it can happen that if you upgrade your system while, or soon after the devs, have been updating the kernel package and third party drivers you can get an older version of one and a newer version of another. Another update later should fix this, or a temporary downgrade, but dkms (again in theory) avoids this scenario.

If I was you the first thing I would do would be to look at /var/log/Xorg.0.log after a failed startx with the nvidia driver.

If you want more eyes on it then install pastebinit and run this command
Code: [Select]
cat /var/log/Xorg.0.log | pastebinit -b paste.debian.net
Post the link.
Or copy the file to a usb or send over the network etc. and post the file here on a device with a GUI.

The second thing I would be trying is using the standard Artix kernel with both the normal and dkms nvidia driver and seeing what works. If anything. Try to narrow things down.

Do you have any other errors ? Look in dmesg straight after a boot.

Edit:
I just read your post properly (bad habit of mine).
If you managed to switch to the zen kernel you should be able to switch back.
But therein might lie your nvidia problem if you didn't do it correctly.

Generally imho it's better to stick to the distro supplied kernel and drivers unless you both know how to switch them around and solve problems that may occur.
On the other hand we learn by trying, and breaking, things.

the Xorg log file is as follows:

Code: [Select]
[    19.012] 
X.Org X Server 1.21.1.4
X Protocol Version 11, Revision 0
[    19.012] Current Operating System: Linux HP-Omen 5.19.13-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Thu, 06 Oct 2022 06:14:55 +0000 x86_64
[    19.012] Kernel command line: BOOT_IMAGE=/vmlinuz-linux-zen root=UUID=3fbe32a7-9e92-4573-8ddf-8b917fddcc51 rw loglevel=3 quiet
[    19.012] 
[    19.012] Current version of pixman: 0.40.0
[    19.012] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[    19.012] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    19.013] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 13 15:54:31 2022
[    19.014] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    19.014] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    19.015] (==) No Layout section.  Using the first Screen section.
[    19.015] (==) No screen section available. Using defaults.
[    19.015] (**) |-->Screen "Default Screen Section" (0)
[    19.015] (**) |   |-->Monitor "<default monitor>"
[    19.015] (==) No device specified for screen "Default Screen Section".
Using the first device section listed.
[    19.015] (**) |   |-->Device "Nvidia Card"
[    19.015] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[    19.015] (==) Automatically adding devices
[    19.015] (==) Automatically enabling devices
[    19.015] (==) Automatically adding GPU devices
[    19.015] (==) Automatically binding GPU devices
[    19.015] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    19.016] (WW) The directory "/usr/share/fonts/misc" does not exist.
[    19.016] Entry deleted from font path.
[    19.016] (WW) The directory "/usr/share/fonts/OTF" does not exist.
[    19.016] Entry deleted from font path.
[    19.016] (WW) The directory "/usr/share/fonts/Type1" does not exist.
[    19.016] Entry deleted from font path.
[    19.016] (WW) The directory "/usr/share/fonts/100dpi" does not exist.
[    19.016] Entry deleted from font path.
[    19.016] (WW) The directory "/usr/share/fonts/75dpi" does not exist.
[    19.016] Entry deleted from font path.
[    19.016] (==) FontPath set to:
/usr/share/fonts/TTF
[    19.016] (==) ModulePath set to "/usr/lib/xorg/modules"
[    19.016] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[    19.016] (II) Module ABI versions:
[    19.016] X.Org ANSI C Emulation: 0.4
[    19.016] X.Org Video Driver: 25.2
[    19.016] X.Org XInput driver : 24.4
[    19.016] X.Org Server Extension : 10.0
[    19.016] (++) using VT number 1

[    19.017] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[    19.017] (II) xfree86: Adding drm device (/dev/dri/card0)
[    19.017] (II) Platform probe for /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card0
[    19.017] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 13 paused 0
[    19.017] (**) OutputClass "nvidia" ModulePath extended to "/usr/lib/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib/xorg/modules"
[    19.018] (--) PCI:*(1@0:0:0) 10de:2206:103c:88b9 rev 161, Mem @ 0xb2000000/16777216, 0xa0000000/268435456, 0xb0000000/33554432, I/O @ 0x00004000/128, BIOS @ 0x????????/524288
[    19.018] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[    19.018] (II) LoadModule: "glx"
[    19.018] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[    19.022] (II) Module glx: vendor="X.Org Foundation"
[    19.022] compiled for 1.21.1.4, module version = 1.0.0
[    19.022] ABI class: X.Org Server Extension, version 10.0
[    19.022] (II) LoadModule: "nvidia"
[    19.022] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[    19.024] (II) Module nvidia: vendor="NVIDIA Corporation"
[    19.024] compiled for 1.6.99.901, module version = 1.0.0
[    19.024] Module class: X.Org Video Driver
[    19.025] (II) NVIDIA dlloader X Driver  515.76  Mon Sep 12 19:18:09 UTC 2022
[    19.025] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[    19.025] (II) systemd-logind: releasing fd for 226:0
[    19.025] (II) Loading sub module "fb"
[    19.025] (II) LoadModule: "fb"
[    19.025] (II) Module "fb" already built-in
[    19.025] (II) Loading sub module "wfb"
[    19.025] (II) LoadModule: "wfb"
[    19.026] (II) Loading /usr/lib/xorg/modules/libwfb.so
[    19.026] (II) Module wfb: vendor="X.Org Foundation"
[    19.026] compiled for 1.21.1.4, module version = 1.0.0
[    19.026] ABI class: X.Org ANSI C Emulation, version 0.4
[    19.026] (II) Loading sub module "ramdac"
[    19.026] (II) LoadModule: "ramdac"
[    19.026] (II) Module "ramdac" already built-in
[    19.026] (II) NVIDIA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[    19.026] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[    19.026] (==) NVIDIA(0): RGB weight 888
[    19.026] (==) NVIDIA(0): Default visual is TrueColor
[    19.026] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[    19.027] (II) Applying OutputClass "nvidia" options to /dev/dri/card0
[    19.027] (**) NVIDIA(0): Option "AllowEmptyInitialConfiguration"
[    19.027] (**) NVIDIA(0): Enabling 2D acceleration
[    19.027] (II) Loading sub module "glxserver_nvidia"
[    19.027] (II) LoadModule: "glxserver_nvidia"
[    19.027] (II) Loading /usr/lib/nvidia/xorg/libglxserver_nvidia.so
[    19.046] (II) Module glxserver_nvidia: vendor="NVIDIA Corporation"
[    19.046] compiled for 1.6.99.901, module version = 1.0.0
[    19.046] Module class: X.Org Server Extension
[    19.046] (II) NVIDIA GLX Module  515.76  Mon Sep 12 19:14:20 UTC 2022
[    19.047] (II) NVIDIA: The X server supports PRIME Render Offload.
[    19.897] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0
[    19.897] (--) NVIDIA(0):     DFP-0 (boot)
[    19.897] (--) NVIDIA(0):     DFP-1
[    19.897] (--) NVIDIA(0):     DFP-2
[    19.897] (--) NVIDIA(0):     DFP-3
[    19.897] (--) NVIDIA(0):     DFP-4
[    19.897] (--) NVIDIA(0):     DFP-5
[    19.897] (--) NVIDIA(0):     DFP-6
[    19.898] (II) NVIDIA(0): NVIDIA GPU NVIDIA GeForce RTX 3080 (GA102-A) at PCI:1:0:0
[    19.898] (II) NVIDIA(0):     (GPU-0)
[    19.898] (--) NVIDIA(0): Memory: 10485760 kBytes
[    19.898] (--) NVIDIA(0): VideoBIOS: 94.02.26.08.17
[    19.898] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[    19.942] (--) NVIDIA(GPU-0): LG Electronics 27GN7 (DFP-0): connected
[    19.942] (--) NVIDIA(GPU-0): LG Electronics 27GN7 (DFP-0): Internal TMDS
[    19.942] (--) NVIDIA(GPU-0): LG Electronics 27GN7 (DFP-0): 600.0 MHz maximum pixel clock
[    19.942] (--) NVIDIA(GPU-0):
[    19.942] (--) NVIDIA(GPU-0): DFP-1: disconnected
[    19.942] (--) NVIDIA(GPU-0): DFP-1: Internal DisplayPort
[    19.942] (--) NVIDIA(GPU-0): DFP-1: 2670.0 MHz maximum pixel clock
[    19.942] (--) NVIDIA(GPU-0):
[    19.942] (--) NVIDIA(GPU-0): DFP-2: disconnected
[    19.942] (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
[    19.942] (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[    19.942] (--) NVIDIA(GPU-0):
[    19.942] (--) NVIDIA(GPU-0): DFP-3: disconnected
[    19.942] (--) NVIDIA(GPU-0): DFP-3: Internal DisplayPort
[    19.942] (--) NVIDIA(GPU-0): DFP-3: 2670.0 MHz maximum pixel clock
[    19.942] (--) NVIDIA(GPU-0):
[    19.943] (--) NVIDIA(GPU-0): DFP-4: disconnected
[    19.943] (--) NVIDIA(GPU-0): DFP-4: Internal TMDS
[    19.943] (--) NVIDIA(GPU-0): DFP-4: 165.0 MHz maximum pixel clock
[    19.943] (--) NVIDIA(GPU-0):
[    19.943] (--) NVIDIA(GPU-0): DFP-5: disconnected
[    19.943] (--) NVIDIA(GPU-0): DFP-5: Internal DisplayPort
[    19.943] (--) NVIDIA(GPU-0): DFP-5: 2670.0 MHz maximum pixel clock
[    19.943] (--) NVIDIA(GPU-0):
[    19.943] (--) NVIDIA(GPU-0): DFP-6: disconnected
[    19.943] (--) NVIDIA(GPU-0): DFP-6: Internal TMDS
[    19.943] (--) NVIDIA(GPU-0): DFP-6: 165.0 MHz maximum pixel clock
[    19.943] (--) NVIDIA(GPU-0):
[    20.021] (==) NVIDIA(0):
[    20.021] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[    20.021] (==) NVIDIA(0):     will be used as the requested mode.
[    20.021] (==) NVIDIA(0):
[    20.027] (II) NVIDIA(0): Validated MetaModes:
[    20.027] (II) NVIDIA(0):     "DFP-0:nvidia-auto-select"
[    20.027] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[    20.101] (--) NVIDIA(0): DPI set to (79, 76); computed from "UseEdidDpi" X config
[    20.101] (--) NVIDIA(0):     option
[    20.102] (II) NVIDIA: Reserving 24576.00 MB of virtual memory for indirect memory
[    20.102] (II) NVIDIA:     access.
[    20.103] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[    20.103] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[    20.103] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[    20.103] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[    20.103] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[    20.103] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[    20.103] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[    20.103] (II) NVIDIA(0):     Config Options in the README.
[    20.115] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select"
[    39.141] (==) NVIDIA(0): Disabling shared memory pixmaps
[    39.141] (==) NVIDIA(0): Backing store enabled
[    39.141] (==) NVIDIA(0): Silken mouse enabled
[    39.141] (==) NVIDIA(0): DPMS enabled
[    39.141] (II) Loading sub module "dri2"
[    39.141] (II) LoadModule: "dri2"
[    39.141] (II) Module "dri2" already built-in
[    39.141] (II) NVIDIA(0): [DRI2] Setup complete
[    39.141] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[    39.142] (II) Initializing extension Generic Event Extension
[    39.142] (II) Initializing extension SHAPE
[    39.142] (II) Initializing extension MIT-SHM
[    39.142] (II) Initializing extension XInputExtension
[    39.142] (II) Initializing extension XTEST
[    39.142] (II) Initializing extension BIG-REQUESTS
[    39.142] (II) Initializing extension SYNC
[    39.142] (II) Initializing extension XKEYBOARD
[    39.142] (II) Initializing extension XC-MISC
[    39.142] (II) Initializing extension SECURITY
[    39.142] (II) Initializing extension XFIXES
[    39.142] (II) Initializing extension RENDER
[    39.142] (II) Initializing extension RANDR
[    39.142] (II) Initializing extension COMPOSITE
[    39.142] (II) Initializing extension DAMAGE
[    39.142] (II) Initializing extension MIT-SCREEN-SAVER
[    39.142] (II) Initializing extension DOUBLE-BUFFER
[    39.142] (II) Initializing extension RECORD
[    39.142] (II) Initializing extension DPMS
[    39.142] (II) Initializing extension Present
[    39.142] (II) Initializing extension DRI3
[    39.143] (II) Initializing extension X-Resource
[    39.143] (II) Initializing extension XVideo
[    39.143] (II) Initializing extension XVideo-MotionCompensation
[    39.143] (II) Initializing extension GLX
[    39.143] (II) Initializing extension GLX
[    39.143] (II) Indirect GLX disabled.
[    39.143] (II) GLX: Another vendor is already registered for screen 0
[    39.143] (II) Initializing extension XFree86-VidModeExtension
[    39.143] (II) Initializing extension XFree86-DGA
[    39.143] (II) Initializing extension XFree86-DRI
[    39.143] (II) Initializing extension DRI2
[    39.143] (II) Initializing extension NV-GLX
[    39.143] (II) Initializing extension NV-CONTROL
[    39.143] (II) Initializing extension XINERAMA
[    39.170] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[    39.170] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    39.170] (II) LoadModule: "libinput"
[    39.170] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[    39.172] (II) Module libinput: vendor="X.Org Foundation"
[    39.172] compiled for 1.21.1.3, module version = 1.2.1
[    39.172] Module class: X.Org XInput Driver
[    39.172] ABI class: X.Org XInput driver, version 24.4
[    39.172] (II) Using input driver 'libinput' for 'Power Button'
[    39.173] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 41 paused 0
[    39.173] (**) Power Button: always reports core events
[    39.173] (**) Option "Device" "/dev/input/event2"
[    39.177] (II) event2  - Power Button: is tagged by udev as: Keyboard
[    39.177] (II) event2  - Power Button: device is a keyboard
[    39.177] (II) event2  - Power Button: device removed
[    39.177] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[    39.177] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[    39.177] (II) event2  - Power Button: is tagged by udev as: Keyboard
[    39.177] (II) event2  - Power Button: device is a keyboard
[    39.178] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[    39.178] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    39.178] (II) Using input driver 'libinput' for 'Power Button'
[    39.178] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 44 paused 0
[    39.178] (**) Power Button: always reports core events
[    39.178] (**) Option "Device" "/dev/input/event1"
[    39.178] (II) event1  - Power Button: is tagged by udev as: Keyboard
[    39.178] (II) event1  - Power Button: device is a keyboard
[    39.178] (II) event1  - Power Button: device removed
[    39.178] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
[    39.178] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[    39.178] (II) event1  - Power Button: is tagged by udev as: Keyboard
[    39.179] (II) event1  - Power Button: device is a keyboard
[    39.179] (II) config/udev: Adding input device Sleep Button (/dev/input/event0)
[    39.179] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[    39.179] (II) Using input driver 'libinput' for 'Sleep Button'
[    39.179] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 45 paused 0
[    39.179] (**) Sleep Button: always reports core events
[    39.179] (**) Option "Device" "/dev/input/event0"
[    39.179] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[    39.179] (II) event0  - Sleep Button: device is a keyboard
[    39.179] (II) event0  - Sleep Button: device removed
[    39.179] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0/event0"
[    39.179] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[    39.180] (II) event0  - Sleep Button: is tagged by udev as: Keyboard
[    39.180] (II) event0  - Sleep Button: device is a keyboard
[    39.180] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=11 (/dev/input/event10)
[    39.180] (II) No input driver specified, ignoring this device.
[    39.180] (II) This device may have been added with another device file.
[    39.180] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=12 (/dev/input/event11)
[    39.180] (II) No input driver specified, ignoring this device.
[    39.180] (II) This device may have been added with another device file.
[    39.180] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event5)
[    39.180] (II) No input driver specified, ignoring this device.
[    39.180] (II) This device may have been added with another device file.
[    39.180] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event6)
[    39.180] (II) No input driver specified, ignoring this device.
[    39.180] (II) This device may have been added with another device file.
[    39.180] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event7)
[    39.180] (II) No input driver specified, ignoring this device.
[    39.180] (II) This device may have been added with another device file.
[    39.181] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event8)
[    39.181] (II) No input driver specified, ignoring this device.
[    39.181] (II) This device may have been added with another device file.
[    39.181] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=10 (/dev/input/event9)
[    39.181] (II) No input driver specified, ignoring this device.
[    39.181] (II) This device may have been added with another device file.
[    39.181] (II) config/udev: Adding input device HP TracerLED (/dev/input/event18)
[    39.181] (II) No input driver specified, ignoring this device.
[    39.181] (II) This device may have been added with another device file.
[    39.181] (II) config/udev: Adding input device SONiX USB DEVICE (/dev/input/event21)
[    39.181] (**) SONiX USB DEVICE: Applying InputClass "libinput keyboard catchall"
[    39.181] (II) Using input driver 'libinput' for 'SONiX USB DEVICE'
[    39.181] (II) systemd-logind: got fd for /dev/input/event21 13:85 fd 46 paused 0
[    39.181] (**) SONiX USB DEVICE: always reports core events
[    39.181] (**) Option "Device" "/dev/input/event21"
[    39.182] (II) event21 - SONiX USB DEVICE: is tagged by udev as: Keyboard
[    39.182] (II) event21 - SONiX USB DEVICE: device is a keyboard
[    39.182] (II) event21 - SONiX USB DEVICE: device removed
[    39.182] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/0003:0C45:7697.0004/input/input22/event21"
[    39.182] (II) XINPUT: Adding extended input device "SONiX USB DEVICE" (type: KEYBOARD, id 9)
[    39.182] (II) event21 - SONiX USB DEVICE: is tagged by udev as: Keyboard
[    39.183] (II) event21 - SONiX USB DEVICE: device is a keyboard
[    39.183] (II) config/udev: Adding input device SONiX USB DEVICE Keyboard (/dev/input/event22)
[    39.183] (**) SONiX USB DEVICE Keyboard: Applying InputClass "libinput keyboard catchall"
[    39.183] (II) Using input driver 'libinput' for 'SONiX USB DEVICE Keyboard'
[    39.183] (II) systemd-logind: got fd for /dev/input/event22 13:86 fd 47 paused 0
[    39.183] (**) SONiX USB DEVICE Keyboard: always reports core events
[    39.183] (**) Option "Device" "/dev/input/event22"
[    39.184] (II) event22 - SONiX USB DEVICE Keyboard: is tagged by udev as: Keyboard
[    39.184] (II) event22 - SONiX USB DEVICE Keyboard: device is a keyboard
[    39.184] (II) event22 - SONiX USB DEVICE Keyboard: device removed
[    39.184] (II) libinput: SONiX USB DEVICE Keyboard: needs a virtual subdevice
[    39.184] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.1/0003:0C45:7697.0005/input/input23/event22"
[    39.184] (II) XINPUT: Adding extended input device "SONiX USB DEVICE Keyboard" (type: MOUSE, id 10)
[    39.184] (**) Option "AccelerationScheme" "none"
[    39.184] (**) SONiX USB DEVICE Keyboard: (accel) selected scheme none/0
[    39.184] (**) SONiX USB DEVICE Keyboard: (accel) acceleration factor: 2.000
[    39.184] (**) SONiX USB DEVICE Keyboard: (accel) acceleration threshold: 4
[    39.184] (II) event22 - SONiX USB DEVICE Keyboard: is tagged by udev as: Keyboard
[    39.184] (II) event22 - SONiX USB DEVICE Keyboard: device is a keyboard
[    39.185] (II) config/udev: Adding input device SONiX USB DEVICE Wireless Radio Control (/dev/input/event23)
[    39.185] (**) SONiX USB DEVICE Wireless Radio Control: Applying InputClass "libinput keyboard catchall"
[    39.185] (II) Using input driver 'libinput' for 'SONiX USB DEVICE Wireless Radio Control'
[    39.185] (II) systemd-logind: got fd for /dev/input/event23 13:87 fd 48 paused 0
[    39.185] (**) SONiX USB DEVICE Wireless Radio Control: always reports core events
[    39.185] (**) Option "Device" "/dev/input/event23"
[    39.185] (II) event23 - SONiX USB DEVICE Wireless Radio Control: is tagged by udev as: Keyboard
[    39.185] (II) event23 - SONiX USB DEVICE Wireless Radio Control: device is a keyboard
[    39.185] (II) event23 - SONiX USB DEVICE Wireless Radio Control: device removed
[    39.185] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.1/0003:0C45:7697.0005/input/input24/event23"
[    39.185] (II) XINPUT: Adding extended input device "SONiX USB DEVICE Wireless Radio Control" (type: KEYBOARD, id 11)
[    39.186] (II) event23 - SONiX USB DEVICE Wireless Radio Control: is tagged by udev as: Keyboard
[    39.186] (II) event23 - SONiX USB DEVICE Wireless Radio Control: device is a keyboard
[    39.186] (II) config/udev: Adding input device SONiX USB DEVICE (/dev/input/event24)
[    39.186] (II) No input driver specified, ignoring this device.
[    39.186] (II) This device may have been added with another device file.
[    39.186] (II) config/udev: Adding input device Glorious Model O (/dev/input/event19)
[    39.186] (**) Glorious Model O: Applying InputClass "libinput pointer catchall"
[    39.186] (II) Using input driver 'libinput' for 'Glorious Model O'
[    39.239] (II) systemd-logind: got fd for /dev/input/event19 13:83 fd 49 paused 0
[    39.239] (**) Glorious Model O: always reports core events
[    39.239] (**) Option "Device" "/dev/input/event19"
[    39.240] (II) event19 - Glorious Model O: is tagged by udev as: Mouse
[    39.240] (II) event19 - Glorious Model O: device is a pointer
[    39.240] (II) event19 - Glorious Model O: device removed
[    39.240] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/0003:258A:0036.0002/input/input26/event19"
[    39.240] (II) XINPUT: Adding extended input device "Glorious Model O" (type: MOUSE, id 12)
[    39.240] (**) Option "AccelerationScheme" "none"
[    39.240] (**) Glorious Model O: (accel) selected scheme none/0
[    39.240] (**) Glorious Model O: (accel) acceleration factor: 2.000
[    39.240] (**) Glorious Model O: (accel) acceleration threshold: 4
[    39.240] (II) event19 - Glorious Model O: is tagged by udev as: Mouse
[    39.240] (II) event19 - Glorious Model O: device is a pointer
[    39.241] (II) config/udev: Adding input device Glorious Model O (/dev/input/mouse0)
[    39.241] (II) No input driver specified, ignoring this device.
[    39.241] (II) This device may have been added with another device file.
[    39.241] (II) config/udev: Adding input device Glorious Model O Keyboard (/dev/input/event20)
[    39.241] (**) Glorious Model O Keyboard: Applying InputClass "libinput keyboard catchall"
[    39.241] (II) Using input driver 'libinput' for 'Glorious Model O Keyboard'
[    39.241] (II) systemd-logind: got fd for /dev/input/event20 13:84 fd 50 paused 0
[    39.241] (**) Glorious Model O Keyboard: always reports core events
[    39.241] (**) Option "Device" "/dev/input/event20"
[    39.242] (II) event20 - Glorious Model O Keyboard: is tagged by udev as: Keyboard
[    39.242] (II) event20 - Glorious Model O Keyboard: device is a keyboard
[    39.242] (II) event20 - Glorious Model O Keyboard: device removed
[    39.242] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1/0003:258A:0036.0003/input/input27/event20"
[    39.242] (II) XINPUT: Adding extended input device "Glorious Model O Keyboard" (type: KEYBOARD, id 13)
[    39.242] (II) event20 - Glorious Model O Keyboard: is tagged by udev as: Keyboard
[    39.242] (II) event20 - Glorious Model O Keyboard: device is a keyboard
[    39.243] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event12)
[    39.243] (II) No input driver specified, ignoring this device.
[    39.243] (II) This device may have been added with another device file.
[    39.243] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event13)
[    39.243] (II) No input driver specified, ignoring this device.
[    39.243] (II) This device may have been added with another device file.
[    39.243] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event14)
[    39.243] (II) No input driver specified, ignoring this device.
[    39.243] (II) This device may have been added with another device file.
[    39.243] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event15)
[    39.243] (II) No input driver specified, ignoring this device.
[    39.243] (II) This device may have been added with another device file.
[    39.243] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event16)
[    39.243] (II) No input driver specified, ignoring this device.
[    39.243] (II) This device may have been added with another device file.
[    39.243] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event17)
[    39.243] (II) No input driver specified, ignoring this device.
[    39.243] (II) This device may have been added with another device file.
[    39.243] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
[    39.243] (II) No input driver specified, ignoring this device.
[    39.243] (II) This device may have been added with another device file.
[    39.244] (II) config/udev: Adding input device HP WMI hotkeys (/dev/input/event4)
[    39.244] (**) HP WMI hotkeys: Applying InputClass "libinput keyboard catchall"
[    39.244] (II) Using input driver 'libinput' for 'HP WMI hotkeys'
[    39.245] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 51 paused 0
[    39.245] (**) HP WMI hotkeys: always reports core events
[    39.245] (**) Option "Device" "/dev/input/event4"
[    39.245] (II) event4  - HP WMI hotkeys: is tagged by udev as: Keyboard Switch
[    39.245] (II) event4  - HP WMI hotkeys: device is a keyboard
[    39.245] (II) event4  - HP WMI hotkeys: device removed
[    39.245] (**) Option "config_info" "udev:/sys/devices/virtual/input/input4/event4"
[    39.245] (II) XINPUT: Adding extended input device "HP WMI hotkeys" (type: KEYBOARD, id 14)
[    39.245] (II) event4  - HP WMI hotkeys: is tagged by udev as: Keyboard Switch
[    39.245] (II) event4  - HP WMI hotkeys: device is a keyboard
[    39.247] (**) SONiX USB DEVICE Keyboard: Applying InputClass "libinput keyboard catchall"
[    39.247] (II) Using input driver 'libinput' for 'SONiX USB DEVICE Keyboard'
[    39.247] (II) systemd-logind: returning pre-existing fd for /dev/input/event22 13:86
[    39.247] (**) SONiX USB DEVICE Keyboard: always reports core events
[    39.247] (**) Option "Device" "/dev/input/event22"
[    39.247] (II) libinput: SONiX USB DEVICE Keyboard: is a virtual subdevice
[    39.247] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.1/0003:0C45:7697.0005/input/input23/event22"
[    39.247] (II) XINPUT: Adding extended input device "SONiX USB DEVICE Keyboard" (type: KEYBOARD, id 15)
[    65.191] (II) event23 - SONiX USB DEVICE Wireless Radio Control: device removed
[    65.191] (II) event21 - SONiX USB DEVICE: device removed
[    65.191] (II) event20 - Glorious Model O Keyboard: device removed
[    65.191] (II) event19 - Glorious Model O: device removed
[    65.192] (II) event0  - Sleep Button: device removed
[    65.192] (II) event2  - Power Button: device removed
[    65.192] (II) event4  - HP WMI hotkeys: device removed
[    65.192] (II) event22 - SONiX USB DEVICE Keyboard: device removed
[    65.192] (II) event1  - Power Button: device removed
[    65.192] (**) Option "fd" "41"
[    65.192] (**) Option "fd" "44"
[    65.192] (**) Option "fd" "45"
[    65.192] (**) Option "fd" "46"
[    65.192] (**) Option "fd" "47"
[    65.192] (**) Option "fd" "48"
[    65.193] (**) Option "fd" "49"
[    65.193] (**) Option "fd" "50"
[    65.193] (**) Option "fd" "51"
[    65.193] (**) Option "fd" "47"
[    65.194] (II) UnloadModule: "libinput"
[    65.194] (II) systemd-logind: not releasing fd for 13:86, still in use
[    65.194] (II) UnloadModule: "libinput"
[    65.194] (II) systemd-logind: releasing fd for 13:68
[    65.194] (EE) systemd-logind: failed to release device: Connection was disconnected before a reply was received
[    65.204] (II) UnloadModule: "libinput"
[    65.204] (II) systemd-logind: releasing fd for 13:84
[    65.204] (EE) systemd-logind: failed to release device: Connection is closed
[    65.212] (II) UnloadModule: "libinput"
[    65.212] (II) systemd-logind: releasing fd for 13:83
[    65.212] (EE) systemd-logind: failed to release device: Connection is closed
[    65.226] (II) UnloadModule: "libinput"
[    65.226] (II) systemd-logind: releasing fd for 13:87
[    65.226] (EE) systemd-logind: failed to release device: Connection is closed
[    65.234] (II) UnloadModule: "libinput"
[    65.234] (II) systemd-logind: releasing fd for 13:86
[    65.234] (EE) systemd-logind: failed to release device: Connection is closed
[    65.240] (II) UnloadModule: "libinput"
[    65.240] (II) systemd-logind: releasing fd for 13:85
[    65.240] (EE) systemd-logind: failed to release device: Connection is closed
[    65.246] (II) UnloadModule: "libinput"
[    65.246] (II) systemd-logind: releasing fd for 13:64
[    65.246] (EE) systemd-logind: failed to release device: Connection is closed
[    65.252] (II) UnloadModule: "libinput"
[    65.252] (II) systemd-logind: releasing fd for 13:65
[    65.252] (EE) systemd-logind: failed to release device: Connection is closed
[    65.258] (II) UnloadModule: "libinput"
[    65.258] (II) systemd-logind: releasing fd for 13:66
[    65.258] (EE) systemd-logind: failed to release device: Connection is closed

the output of "dmesg | grep nvidia" is as follows:

Code: [Select]
[    1.939152] nvidia: loading out-of-tree module taints kernel.
[    1.939161] nvidia: module license 'NVIDIA' taints kernel.
[    1.958813] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[    2.076789] nvidia-nvlink: Nvlink Core is being initialized, major device number 234
[    2.078668] nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none
[    2.163796] nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
[    2.167222] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  515.76  Mon Sep 12 19:11:54 UTC 2022
[    2.214997] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[    2.214998] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0
[    2.215090] nvidia-uvm: Loaded the UVM driver, major device number 510.

I was just about to say that I installed the zen kernel along with the zen headers from the very start, but you already noticed all that stuff. also, to clear up any confusion on the matter of versions, I'm using the packages from artix world, except of course the lib32 packages which come from lib32. Before I got your message I actually attempted to downgrade the nvidia drivers using the ALA (forgetting that the ALA is for arch repositories and not artix ones). I then noticed that the ALA drivers were actually at a later version. I then upgraded and discovered that those drivers at least let me startx, but it caused some minor screen tearing and spit me out onto the same black screen if I tried to quit out of xterm. I'm starting to wonder if those specific official artix nvidia-dkms drivers are just broken or something.

Re: Startx opens black screen

Reply #7
Nothings jumping out at me as wrong from that output.
It seems that X is running with the nvidia driver.

Though there is this. I have
Code: [Select]
[251902.917] (II) NVIDIA: Reserving 24576.00 MB of virtual memory for indirect memory
[251902.917] (II) NVIDIA:     access.
[251902.936] (II) NVIDIA(0): Setting mode "DP-2:1920x1080_75+1920+0,DP-0:1920x1080_75+0+0,DP-4:1920x1080_75+3840+0"

You have
Code: [Select]
[    20.102] (II) NVIDIA: Reserving 24576.00 MB of virtual memory for indirect memory
[    20.102] (II) NVIDIA:     access.
[    20.103] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[    20.103] (II) NVIDIA(0):     may not be running or the "AcpidSocketPath" X
[    20.103] (II) NVIDIA(0):     configuration option may not be set correctly.  When the
[    20.103] (II) NVIDIA(0):     ACPI event daemon is available, the NVIDIA X driver will
[    20.103] (II) NVIDIA(0):     try to use it to receive ACPI event notifications.  For
[    20.103] (II) NVIDIA(0):     details, please see the "ConnectToAcpid" and
[    20.103] (II) NVIDIA(0):     "AcpidSocketPath" X configuration options in Appendix B: X
[    20.103] (II) NVIDIA(0):     Config Options in the README.
[    20.115] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select"

It's showing as informational (II) not an error (EE)

It references this file /usr/share/doc/nvidia/README from which is this
Quote
Option "AcpidSocketPath" "string"

    The NVIDIA X driver attempts to connect to the ACPI daemon (acpid) via a
    UNIX domain socket. The default path to this socket is
    "/var/run/acpid.socket". Set this option to specify an alternate path to
    acpid's socket. Default: "/var/run/acpid.socket".

I do have this file /var/run/acpid.socket

That's probably a wild goose chase as I don't think the lack of acpid should stop x starting ?
But I wonder why it's missing?

I'm almost out of ideas myself.
But looking at that log I might be thinking X is starting but nothing else is.
Maybe try skipping .xinitrc https://wiki.archlinux.org/title/Xinit#Override_xinitrc . Try just running a terminal. No window manager
And even though I prefer no display manager myself, just startx and ~/.xinitrc, in your situation I'd probably try one like sddm and see what happens.



 

Re: Startx opens black screen

Reply #8
I've actually tried using startx with the path to xterm and it failed in the exact same way as it always does. black screen without access to tty unless I fully reboot. I think I might just have to wait for 520 on artix because it kind of worked when I snagged drivers from the ALA. I'm pretty thoroughly convinced nvidia-dkms-515.76-1 is just borked now. Maybe a downgrade will work for the meantime? How might I go about downgrading?

EDIT/UPDATE: i just updated my system after seeing that all the drivers have been updated. everything works flawlessly now. HOORAY!