/dev/dri/renderD128 disappear when switching to kernel 6.8.4-3

jsapede

New Member
Jun 12, 2024
4
0
1
Hello all,

strange problem this morning after upgrading form 6.5.13-5 to 6.8.4-3.

Impossible to have intel HD passthrough in lxc containers. After seeking i found that there's no more /dev/dri and especially no /dev/dri/renderD128 i usually map in the LXCs.

reverting back to 6.5.13-5 and everything works fine and /dev/dri appears and intel_gpu_top works

On 6.5.13-5 :

Bash:
root@pve:/dev#  lspci -nnk
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
        Subsystem: Hewlett-Packard Company Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [103c:84f5]
        Kernel driver in use: skl_uncore
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 [8086:5916] (rev 02)
        DeviceName:  Onboard IGD
        Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:84f5]
        Kernel driver in use: i915
        Kernel modules: i915

and

Code:
root@pve:/dev# ls /dev/dri
by-path  card0  renderD128

On 6.8.4-3 i got :

Code:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
        Subsystem: Hewlett-Packard Company Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [103c:84f5]
        Kernel driver in use: skl_uncore
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 [8086:5916] (rev 02)
        DeviceName:  Onboard IGD
        Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:84f5]
        Kernel modules: i915

Code:
root@pve:~# ls /dev/dri
ls: cannot access '/dev/dri': No such file or directory

Code:
root@pve:~# intel_gpu_top
No device filter specified and no discrete/integrated i915 devices found
 
Hi,

can you post the complete output of 'dmesg' ? maybe we can see there why the driver is not loaded
also you can try to manually load the driver with
Code:
modprobe i915
 
Hi,

can you post the complete output of 'dmesg' ? maybe we can see there why the driver is not loaded
also you can try to manually load the driver with
Code:
modprobe i915
modprobe gave results :

Code:
root@pve:/dev/dri# ls
by-path  card0  renderD128
 

Attachments

  • dmesg.txt
    75.9 KB · Views: 7
mhmm ok interesting, dmesg shows simply nothing in relation to the i915 driver, so it simply does not load it automatically anymore on your system...

you can force it to load by putting 'i915' in the file '/etc/modules' then it should load it on boot
 
that was i was looking,
/etc modules was modifed according to https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_pci_passthrough

Code:
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.
vfio
vfio_iommu_type1
vfio_pci

and /etc/default/grub with :

Code:
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on iommu=pt"

but it was working since ages until i uprgraded to 6.8.4-3. And it also works when i revert back to 6.5.13-5.
 
yeah it seems with some kernel change the i915 driver does not autoload anymore for some
 
yes exactly

EDIT: sorry i misread it should be /etc/modules not /etc/modprobe
 
  • Like
Reactions: jsapede
Hello, I am reusing this thread as I have a similar problem as OP, and I am unable to solve it.

I am on 6.8.12-1-pve, but /dev/dri/renderD128 simply is not there. I suspect something fishy is going on as I have renderD129 and I do have a second GPU on the system, so I believe the device is created and then somehow removed.

Code:
$ lspci -nnk

00:02.0 VGA compatible controller [0300]: Intel Corporation Raptor Lake-S GT1 [UHD Graphics 770] [8086:a780] (rev 04)
        DeviceName: Onboard - Video
        Subsystem: ASUSTeK Computer Inc. Raptor Lake-S GT1 [UHD Graphics 770] [1043:8694]
        Kernel driver in use: i915
        Kernel modules: i915, xe

The complete output of dmesg can be found here: https://0x0.st/XvRa.txt

At [ 5.151777] it seems that the kernel loads i915 but then it blows up. Can anyone help debugging this?

I tried to downgrade the kernel a few weeks ago but that did not seem to solve the issue for me.
 
Hello, I am reusing this thread as I have a similar problem as OP, and I am unable to solve it.

I am on 6.8.12-1-pve, but /dev/dri/renderD128 simply is not there. I suspect something fishy is going on as I have renderD129 and I do have a second GPU on the system, so I believe the device is created and then somehow removed.

Code:
$ lspci -nnk

00:02.0 VGA compatible controller [0300]: Intel Corporation Raptor Lake-S GT1 [UHD Graphics 770] [8086:a780] (rev 04)
        DeviceName: Onboard - Video
        Subsystem: ASUSTeK Computer Inc. Raptor Lake-S GT1 [UHD Graphics 770] [1043:8694]
        Kernel driver in use: i915
        Kernel modules: i915, xe

The complete output of dmesg can be found here: https://0x0.st/XvRa.txt

At [ 5.151777] it seems that the kernel loads i915 but then it blows up. Can anyone help debugging this?

I tried to downgrade the kernel a few weeks ago but that did not seem to solve the issue for me.
Same here, I dont have /dev/dri at all.

Code:
$ lspci -nnk

00:02.0 VGA compatible controller [0300]: Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630] [8086:3e92]
        DeviceName: Onboard IGD
        Subsystem: Hewlett-Packard Company CoffeeLake-S GT2 [UHD Graphics 630] [103c:8595]
        Kernel driver in use: vfio-pci
        Kernel modules: i915

I can add gpu to virtual machines but not to lxc.
 
I just realized this afternoon I also no longer have any renderD128 or renderD129. I installed intel-media-va-driver and i965-va-driver this evening in an attempt to get them back.

Bash:
❯ ls /dev/dri
Octal Permissions  Size User Group Date Modified     Name
0755  drwxr-xr-x      - root root  24-09-24 20:41:38  by-path
0660  crw-rw----  226,0 root video 24-09-24 20:41:38  card0

Bash:
❯ sudo lspci -nn | grep -Ei "3d|display|vga"
0b:00.0 VGA compatible controller [0300]: ASPEED Technology, Inc. ASPEED Graphics Family [1a03:2000] (rev 52)

Bash:
❯ sudo lshw -C display
  *-display
       description: VGA compatible controller
       product: ASPEED Graphics Family
       vendor: ASPEED Technology, Inc.
       physical id: 0
       bus info: pci@0000:0b:00.0
       logical name: /dev/fb0
       version: 52
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi vga_controller cap_list rom fb
       configuration: depth=32 driver=ast latency=0 resolution=1024,768
       resources: irq:19 memory:80000000-80ffffff memory:81000000-8103ffff ioport:3000(size=128) memory:c0000-dffff

Bash:
❯ sudo intel_gpu_top
No device filter specified and no discrete/integrated i915 devices found

Bash:
❯ sudo lsmod | grep i915
i915                 3932160  0
drm_buddy              20480  1 i915
ttm                   102400  1 i915
drm_display_helper    233472  1 i915
video                  73728  1 i915
cec                    90112  2 drm_display_helper,i915
i2c_algo_bit           16384  2 ast,i915

Bash:
❯ sudo dpkg -l | grep Intel
ii  i965-va-driver:amd64                 2.4.1+dfsg1-1                        amd64        VAAPI driver for Intel G45 & HD Graphics family
ii  intel-gpu-tools                      1.27.1-1                             amd64        tools for debugging the Intel graphics driver
ii  intel-igc-core                       1.0.17537.20                         amd64        Intel(R) Graphics Compiler for OpenCL(TM)
ii  intel-igc-opencl                     1.0.17537.20                         amd64        Intel(R) Graphics Compiler for OpenCL(TM)
ii  intel-level-zero-gpu                 1.3.30872.22                         amd64        Intel(R) Graphics Compute Runtime for oneAPI Level Zero.
ii  intel-level-zero-gpu-legacy1         1.3.30872.22                         amd64        Intel(R) Graphics Compute Runtime for oneAPI Level Zero.
ii  intel-media-va-driver:amd64          23.1.1+dfsg1-1                       amd64        VAAPI driver for the Intel GEN8+ Graphics family
ii  intel-microcode                      3.20240813.1~deb12u1                 amd64        Processor microcode firmware for Intel CPUs
ii  intel-opencl-icd                     24.35.30872.22                       amd64        Intel graphics compute runtime for OpenCL
ii  intel-opencl-icd-legacy1             24.35.30872.22                       amd64        Intel graphics compute runtime for OpenCL
ii  iucode-tool                          2.3.1-3                              amd64        Intel processor microcode tool
ii  libigdgmm12:amd64                    22.5.0                               amd64        Intel Graphics Memory Management Library -- shared library
ii  libmfx1:amd64                        22.5.4-1                             amd64        Intel Media SDK -- shared library
ii  libopenipmi0                         2.0.33-1+b1                          amd64        Intelligent Platform Management Interface - runtime
ii  openipmi                             2.0.33-1+b1                          amd64        Intelligent Platform Management Interface (for servers)

Bash:
❯ sudo intel_gpu_top
No device filter specified and no discrete/integrated i915 devices found

Bash:
❯ sudo cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.

i915


Bash:
❯ ls /etc/modprobe.d
Octal Permissions Size User Group Date Modified     Name
0644  .rw-r--r--    49 root root  24-09-24 20:01:53  i915.conf
0644  .rw-r--r--   154 root root  24-05-29 22:27:07  intel-microcode-blacklist.conf
0644  .rw-r--r--   172 root root  24-04-23 15:33:31  pve-blacklist.conf

Bash:
❯ sudo cat /etc/modprobe.d/i915.conf
options i915 enable_guc=3
options i915 modeset=1

Bash:
❯ sudo cat /etc/modprobe.d/intel-microcode-blacklist.conf
# The microcode module attempts to apply a microcode update when
# it autoloads.  This is not always safe, so we block it by default.
blacklist microcode

Bash:
❯ sudo cat /etc/modprobe.d/pve-blacklist.conf
# This file contains a list of modules which are not supported by Proxmox VE

# nvidiafb see bugreport https://bugzilla.proxmox.com/show_bug.cgi?id=701
blacklist nvidiafb

sudo dmesg | grep i915 doesn't return anything.

I tried downgrading the kernel from 6.8.12-2-pve to 6.8.8-4-pve with no luck. I also tried 6.5.13-5-pve kernel like OP, still nothing. I'm not sure what else to try.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!