![](https://seccdn.libravatar.org/avatar/065b1b1774363493af32c0a6ce9ff07c.jpg?s=120&d=mm&r=g)
Hi, this is a little above my pay grade to try and solve, so need a kind guru! I am running OpenSuSE Leap 15.4 x64 along with the x11vnc server version 0.9.16 and TigerVNC/vncviewer version 1.10.1 Until relatively recently I have been able to make VNC connections between my systems, but recently one system got sick and no longer allows a vnc session to be created. The Xorg.1.log file is showing a bunch of surprising errors, so my questions are, 1. What happened? and 2. How do I fix this? I am happy to provide any additional info and thanks in advance for your help... Marc... bigbang:/var/log # grep "(EE)" Xorg.1.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [2293287.320] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied [2293287.344] (EE) Failed to load module "intel" (module does not exist, 0) [2293287.368] (EE) Screen 0 deleted because of no matching config section. [2293287.556] (EE) modeset(0): drmSetMaster failed: Device or resource busy [2293287.556] (EE) [2293287.556] (EE) AddScreen/ScreenInit failed for driver 0 [2293287.556] (EE) [2293287.556] (EE) [2293287.556] (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information. [2293287.556] (EE) [2293287.556] (EE) Server terminated with error (1). Closing log file. bigbang:/var/log # ll /dev/dri/card0 crw-rw----+ 1 root video 226, 0 Oct 15 22:15 /dev/dri/card0 Information about my system is shown below - lspci -nnk 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:191f] (rev 07) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5000] Kernel driver in use: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] Kernel driver in use: i915 Kernel modules: i915 00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5007] Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31) Subsystem: Gigabyte Technology Co., Ltd Device [1458:1c3a] Kernel driver in use: mei_me Kernel modules: mei_me 00:17.0 SATA controller [0106]: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] [8086:a102] (rev 31) Subsystem: Gigabyte Technology Co., Ltd Device [1458:b005] Kernel driver in use: ahci Kernel modules: ahci 00:1b.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #17 [8086:a167] (rev f1) Kernel driver in use: pcieport 00:1b.2 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #19 [8086:a169] (rev f1) Kernel driver in use: pcieport 00:1b.3 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #20 [8086:a16a] (rev f1) Kernel driver in use: pcieport 00:1c.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 [8086:a110] (rev f1) Kernel driver in use: pcieport 00:1c.2 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #3 [8086:a112] (rev f1) Kernel driver in use: pcieport 00:1c.3 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #4 [8086:a113] (rev f1) Kernel driver in use: pcieport 00:1c.4 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 [8086:a114] (rev f1) Kernel driver in use: pcieport 00:1d.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 [8086:a118] (rev f1) Kernel driver in use: pcieport 00:1f.0 ISA bridge [0601]: Intel Corporation Z170 Chipset LPC/eSPI Controller [8086:a145] (rev 31) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001] 00:1f.2 Memory controller [0580]: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller [8086:a121] (rev 31) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001] 00:1f.3 Audio device [0403]: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller [8086:a170] (rev 31) Subsystem: Gigabyte Technology Co., Ltd Device [1458:a182] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1f.4 SMBus [0c05]: Intel Corporation 100 Series/C230 Series Chipset Family SMBus [8086:a123] (rev 31) Subsystem: Gigabyte Technology Co., Ltd Device [1458:5001] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 02:00.0 PCI bridge [0604]: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge [1b21:1080] (rev 04) 03:00.0 Ethernet controller [0200]: Intel Corporation 82541PI Gigabit Ethernet Controller [8086:107c] (rev 05) Subsystem: Intel Corporation PRO/1000 GT Desktop Adapter [8086:1376] Kernel driver in use: e1000 Kernel modules: e1000 06:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15) Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet [1458:e000] Kernel driver in use: r8169 Kernel modules: r8169 --
![](https://seccdn.libravatar.org/avatar/a836ff90f492078f494adcf0c6059fc6.jpg?s=120&d=mm&r=g)
Marc Chamberlin via openSUSE Users composed on 2023-10-16 17:05 (UTC-0700):
Hi, this is a little above my pay grade to try and solve, so need a kind guru! I am running OpenSuSE Leap 15.4 x64 along with the x11vnc server version 0.9.16 and TigerVNC/vncviewer version 1.10.1
I have no familiarity with using any kind of VNC.
[2293287.320] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
Trouble with /dev/dri/* is bad news.
[2293287.344] (EE) Failed to load module "intel" (module does not exist, 0)
This is normal for any Intel graphics user using upstream's default Xorg display driver modesetting. The intel DDX driver has been on life support for around a decade, mainly used for comparisons, troubleshooting, and ancient hardware. Some users seem to like it better than Xorg's modesetting DIX, which comes in the Xorg server rpm. The intel comes from xf86-video-intel rpm.
[2293287.368] (EE) Screen 0 deleted because of no matching config section.
I see commonly see this with no ill effect attached.
[2293287.556] (EE) AddScreen/ScreenInit failed for driver 0
This is merely a summary statement that something went badly wrong. Picking pieces out of Xorg.0.log usually doesn't help a lot without the context that is most of the log. Usually its only the input/output keyboard/mouse/USB devices that don't matter in diagnosing.
bigbang:/var/log # ll /dev/dri/card0 crw-rw----+ 1 root video 226, 0 Oct 15 22:15 /dev/dri/card0
This is one of the keystones to success.
Information about my system is shown below -
lspci -nnk
Lots of info but little useful. Inxi does a better job of highlighting what matters. Read its man page so that you only use relevant options. Dmesg may have useful clues. Grep it for failures, and same with journalctl -b. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
![](https://seccdn.libravatar.org/avatar/27aacf61a13c66fcc083fcf8a84823bc.jpg?s=120&d=mm&r=g)
On 10/16/23 19:05, Marc Chamberlin via openSUSE Users wrote:
/dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
Weird libdrm regression -- like this nearly 10 year old bug? Cannot access secondary GPU: [drm] failed to set drm interface version: Permission denied #580 https://github.com/Bumblebee-Project/Bumblebee/issues/580 Or the 7 year old bug: "failed to set DRM interface version 1.4: Permission denied" after resume for... https://bugs.freedesktop.org/show_bug.cgi?id=109150 Migrated to freedesktop gitlab and apparently resolved/closed 3 years ago: "failed to set DRM interface version 1.4: Permission denied" after resume for lock screen https://gitlab.freedesktop.org/mesa/drm/-/issues/26 Or last years opensuse turn in the ring: optirun fails: failed to set DRM interface version 1.4: Permission denied https://forums.opensuse.org/t/optirun-fails-failed-to-set-drm-interface-vers... Or Debian's 2023 user-change issue (that has some workarounds noted) changing user leads to "session is locked" https://forums.debian.net/viewtopic.php?t=154638 So it looks like that crops up every so often and there is no one-thing that fixes it. Some are kernel issues, some are libdrm, all are a pain. I think Felix nailed it with: "Trouble with /dev/dri/* is bad news." What is confusing is this is VNC, yes you need Xorg, but presumably you are just accessing over ssh with some port-forwarding setup. The issue seems to be when the libdrm permission denied occurs, it's fatal to Xorg which kills your session. I have used tigerVNC (vncviewer/vncserver) with the server on an Arch box and the viewer being my 15.4 laptop. I just fired it up to make sure it works (and it failed and I had to reconfigure due to changes in the tigervnc template service file) Tigervnc changed from requiring you copy the vncserver.service file as a drop-in service file to, e.g. /etc/systemd/system/vncserver@:1.service for display :1 to providing a template /usr/lib/systemd/system/vncserver@.service that takes the display as an argument passed by calling systemctl start vncserver@:1.service now -- pain to figure out after not running for 6 months or so... All good now though, e.g. after starting the server on the arch box and creating the ssh tunnel from port 5901 on the arch box to -L (local) port 9901 and connecting with "vncviewer localhost:9901"` VNC is up and running great: 00:13 wizard:~> vncviewer localhost:9901 TigerVNC Viewer 64-bit v1.10.1 Copyright (C) 1999-2019 TigerVNC Team and many others (see README.rst) See https://www.tigervnc.org for information on TigerVNC. Wed Oct 18 00:29:36 2023 DecodeManager: Detected 4 CPU core(s) DecodeManager: Creating 4 decoder thread(s) CConn: Connected to host localhost port 9901 CConnection: Server supports RFB protocol version 3.8 CConnection: Using RFB protocol version 3.8 CConnection: Choosing security type VeNCrypt(19) CVeNCrypt: Choosing security type VncAuth (2) Wed Oct 18 00:29:43 2023 CConn: Using pixel format depth 24 (32bpp) little-endian rgb888 CConnection: Enabling continuous updates Hope you get it sorted either by one of the bugs/workarounds above or by checking you don't have any stale drop-in service file biting you like it bit me.... -- David C. Rankin, J.D.,P.E.
participants (3)
-
David C. Rankin
-
Felix Miata
-
Marc Chamberlin