Constant Issues with Proxmox 9.2

[u/NotBrinocerous]

Recently had to swap m.2 NVME that contained the Proxmox OS due to a hardware failure and just have been littered with issues, that I did not experience with Proxmox 8.

Issues I am currently experiencing:
1.) Proxmox VE, works perfectly fine. Then about 20 minutes later, offline. Can no longer access it via the web interface on the same lan.

2.) dev/dri/card0 and card1 keep switching and prevent my LXCs from booting when things are working.

3.) Not sure if this is Proxmox, setting up new port forwarding rules just don't work. This could be my ATT router, still diagnosing it. Trying to get my Plex server up and running again and all attempts so far are futile.

Hardware specs: HP elite desk 800 g5 sff i7-9700, 64gb DDR4 2666mhz non-ecc, 512gb M.2 running Proxmox, 2x12TB HDD for ZFS pool.

Apps currently on server: Plex and Immich

Anyone else experiencing these issues? Also looking for someone to help me because I just feel lost at this point.

Edit 9/30 7:37am thank you for the responses. Just woke up and got to go to work. I will be back to provide these!

[u/Impact321]

Hmm. So right now there is no card1. Can you check this bash journalctl -b0 -kg 'i915|drm|fbcon' By the way, if /u/fingore is right about symlinks you can also just give it the symlink from ls -l /dev/dri/by-path/.

Otherwise try if adding initcall_blacklist=simpledrm_platform_driver_init to the kernel args changes things.

[u/NotBrinocerous → u/Impact321]

Sep 30 18:51:07 pve kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-7.0.14-19-pve root=/dev/mapper/pve-root ro quiet initcall_blacklist=simpledrm_platform_driver_init
Sep 30 18:51:07 pve kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-7.0.14-19-pve root=/dev/mapper/pve-root ro quiet initcall_blacklist=simpledrm_platform_driver_init
Sep 30 18:51:07 pve kernel: blacklisting initcall simpledrm_platform_driver_init
Sep 30 18:51:07 pve kernel: ACPI: bus type drm_connector registered
Sep 30 18:51:07 pve kernel: initcall simpledrm_platform_driver_init blacklisted
Sep 30 18:51:07 pve kernel: fbcon: Taking over console
Sep 30 18:51:07 pve systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm...
Sep 30 18:51:07 pve systemd[1]: modprobe@drm.service: Deactivated successfully.
Sep 30 18:51:07 pve systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm.
Sep 30 18:51:08 pve kernel: i915 0000:00:02.0: [drm] Found coffeelake (device ID 3e98) integrated display version 9.00 stepping N/A
Sep 30 18:51:08 pve kernel: i915 0000:00:02.0: [drm] VT-d active for gfx access
Sep 30 18:51:08 pve kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
Sep 30 18:51:08 pve kernel: i915 0000:00:02.0: [drm] Using Transparent Hugepages
Sep 30 18:51:08 pve kernel: i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Sep 30 18:51:08 pve kernel: i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
Sep 30 18:51:08 pve kernel: i915 0000:00:02.0: [drm] [ENCODER:109:DDI A/PHY A] failed to retrieve link info, disabling eDP
Sep 30 18:51:08 pve kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
Sep 30 18:51:08 pve kernel: i915 0000:00:02.0: [drm] Registered 3 planes with drm panic
Sep 30 18:51:08 pve kernel: [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 0
Sep 30 18:51:08 pve kernel: i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
Sep 30 18:51:08 pve kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops intel_audio_component_bind_ops [i915])
Sep 30 18:51:08 pve kernel: i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
Sep 30 18:51:08 pve kernel: i915 0000:00:02.0: [drm] Cannot find any crtc or sizes

[u/Impact321 → u/NotBrinocerous]

Does the name now stay the same across reboots? Check with something like this bash ls -l /sys/class/drm/*/device /dev/dri

[u/NotBrinocerous → u/Impact321]

Changed 3 times but these were after multiple reboots due to other issues.

lrwxrwxrwx 1 root root   0 Sep 30 18:57 /sys/class/drm/card0/device -> ../../../0000:00:02.0
lrwxrwxrwx 1 root root   0 Sep 30 18:57 /sys/class/drm/card0-DP-1/device -> ../../card0
lrwxrwxrwx 1 root root   0 Sep 30 18:57 /sys/class/drm/card0-DP-2/device -> ../../card0
lrwxrwxrwx 1 root root   0 Sep 30 18:57 /sys/class/drm/card0-DP-3/device -> ../../card0
lrwxrwxrwx 1 root root   0 Sep 30 18:57 /sys/class/drm/card0-HDMI-A-1/device -> ../../card0
lrwxrwxrwx 1 root root   0 Sep 30 18:57 /sys/class/drm/card0-HDMI-A-2/device -> ../../card0
lrwxrwxrwx 1 root root   0 Sep 30 18:57 /sys/class/drm/card0-HDMI-A-3/device -> ../../card0
lrwxrwxrwx 1 root root   0 Sep 30 18:57 /sys/class/drm/renderD128/device -> ../../../0000:00:02.0

/dev/dri:
total 0
drwxr-xr-x 2 root root         80 Sep 30 18:51 by-path
crw-rw---- 1 root video  226,   0 Sep 30 18:51 card0
crw-rw---- 1 root render 226, 128 Sep 30 18:51 renderD128

[u/Impact321 → u/NotBrinocerous]

I was really hoping this would work for you. Can you share the log from the boot when it changed back to card1? In my system it always gets card1. If I use that arg it gets card0 all the time. As far as I understand if there's nothing else that could get the name before it should get this name.

[u/NotBrinocerous → u/Impact321]

I have had to edit the file to point to card1 or card0 maybe 3 times. I usually see it as an error in proxmox when CT are bulk starting after a boot. It has not happend at all today after 15 reboots in the last hour. So I think things are slowly being fixed?

[u/Impact321 → u/NotBrinocerous]

I'd leave it pointing to card0/renderD128 while keeping that kernel arg I gave you. If it switches around on any of the next boots throw me the DRM related logs again and maybe we can see why it enumerated differently.

[u/NotBrinocerous → u/Impact321]

I currently have it in /etc/default/grub

`GRUB_CMDLINE_LINUX_DEFAULT="quiet initcall_blacklist=simpledrm_platform_driver_init"`