Search results

  1. S

    [SOLVED] Failed GPU drivers - Proxmox not booting

    The issue was solved. I remove quiet from the kernel params and it does show an issue with the GPU drivers. I tried to ping it and the machine was responsive so I ssh'd in and removed all nvidia drivers and any relevant config files and blacklists and rebooted. It went fine.
  2. S

    [SOLVED] Failed GPU drivers - Proxmox not booting

    Hello, I installed nvidia-drivers from bullseye-backports, everything looked fine since there was no errors. I rebooted and then lost connection to the machine. I forced reboot and selected the kernel (5.15.39-1-pve) recovery mode option and then it got stuck here. I rebooted it again and used...
  3. S

    Unable to load the kernel module 'nvidia.ko'

    Just installed the drivers and rebooted. Machine is unreachable :(. I plugged a screen and rebooted. It gets stuck here https://ibb.co/vDhWgbv. How can I troubleshoot this? Is it an issue with the graphics driver not loading properly?
  4. S

    Unable to load the kernel module 'nvidia.ko'

    I was not aware of that option. What is the package name? is it nvidia-driver/bullseye-backports ?
  5. S

    Unable to load the kernel module 'nvidia.ko'

    This is the relevant part - https://bpa.st/NHYA - basically a similar message to the one in the log.
  6. S

    Unable to load the kernel module 'nvidia.ko'

    I did not compile anything, I just installed the required headers (pve-headers iirc) and executed NVIDIA-Linux-x86_64-515.57.run. The nvidia-installer.log file is here - https://termbin.com/0zzv
  7. S

    Unable to load the kernel module 'nvidia.ko'

    This problem. ERROR: Unable to load the kernel module 'nvidia.ko'. This happens most frequently when this kernel module was built against the wrong or improperly configured kernel sources, with a version of gcc that differs from the one used to build the target kernel, or if another driver...
  8. S

    Unable to load the kernel module 'nvidia.ko'

    I'm having the same problem when trying to install the latest official driver. lspci -k shows the following 08:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] (rev a1) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1070 Ti] Kernel...
  9. S

    Installing Nvidia drivers on host

    I updated everything and rebooted before installing the driver. That error message was after.
  10. S

    Installing Nvidia drivers on host

    So I installed pve-headers and tried installing the drivers again, ended up with ERROR: Unable to load the kernel module 'nvidia.ko'. This happens most frequently when this kernel module was built against the wrong or improperly configured kernel sources, with a version of gcc that differs...
  11. S

    Installing Nvidia drivers on host

    I did not. But before going through this, I wanted to confirm that it is the correct way to install them. I don't want issues to arise with my current LXCs/VMs.
  12. S

    Installing Nvidia drivers on host

    Hello All, I installed docker on the Proxmox host in order to run Frigate. I have an Nvidia 1070Ti that I want to use for hardware acceleration/decoding in Frigate. How do I install the Nvidia drivers? I downloaded "NVIDIA-Linux-x86_64-515.48.07.run" from Nvidia.com and tried to run it but it...
  13. S

    Mullvad VPN Daemon issues

    Ok, I think I understand what you're saying now. I fixed the perms. LXc: # ls -nal /dev/net/tun crw-rw-rw- 1 0 0 10, 200 Jan 7 19:18 /dev/net/tun PVE: # ls -nal /dev/net/tun crw-rw-rw- 1 100000 100000 10, 200 Jan 7 19:18 /dev/net/tun Still having the same issue. # mullvad connect...
  14. S

    Mullvad VPN Daemon issues

    LXC: # ls -nal /dev/net/tun crw-rw-rw- 1 65534 65534 10, 200 Jan 7 19:18 /dev/net/tun PVE: # ls -nal /dev/net/tun crw-rw-rw- 1 0 0 10, 200 Jan 7 19:18 /dev/net/tun What perms are required exactly?
  15. S

    Mullvad VPN Daemon issues

    Anybody found a solution to this issue? I am just trying out Mullvad in a LXC and having the same problem. # cat /etc/pve/lxc/101.conf arch: amd64 cores: 2 features: nesting=1 hostname: qbit.home.lan memory: 6144 mp0: /mnt/store/downloads/,mp=/mnt/downloads mp1: /mnt/media/,mp=/mnt/media...
  16. S

    Failed to start Import ZFS pool <pool-name>

    Hello, Yes, the pool shows up in zpool list and it is working normally. I also did use the kernel version that is currently running. No need to use the -k option in the first place, it'll just use the current running version.
  17. S

    Failing to boot Home Assistant qcow2 image disk - UEFI Access Denied

    Disabling Secure boot fixed my problem. I should have updated my post earlier, sorry. Not in your host machine, but in the Proxmox VM. When you see the Proxmox logo when booting a VM, hit escape and then go to Device Manager -> Secure Boot Configuration then disable Attempt Secure Boot.
  18. S

    Failed to start Import ZFS pool <pool-name>

    Greetings, I keep getting "Failed to start Import ZFS pool hddmirror." when Proxmox is booting. The pool is just fine when the login shows up after a minute or so of waiting. I found the following in syslog: Nov 17 18:58:10 kong systemd[1]: Starting Import ZFS pool hddmirror... ... ... Nov 17...
  19. S

    Failing to boot Home Assistant qcow2 image disk - UEFI Access Denied

    Greetings, So I set up a VM in order to install Home Assistant. I download the qcow2 image from https://www.home-assistant.io/installation/alternative and import it to the new VM. The end result is the following VM conf. # cat /etc/pve/qemu-server/108.conf agent: 1 bios: ovmf boot...