G GhostViper New Member May 3, 2020 3 0 1 27 May 3, 2020 #1 Proxmox - NVidia Issues Hi All, I am trying to move from Hyper-V to proxmox but I can’t even get past installing the program, below is the error message, it looks like it’s having issues with my NVidia graphics card but I have no onboard graphics to use instead... Thanks all, GV
Proxmox - NVidia Issues Hi All, I am trying to move from Hyper-V to proxmox but I can’t even get past installing the program, below is the error message, it looks like it’s having issues with my NVidia graphics card but I have no onboard graphics to use instead... Thanks all, GV
oguz Proxmox Retired Staff Retired Staff Nov 19, 2018 5,207 813 118 May 4, 2020 #2 hi, what graphics card do you have? can you tell us a bit about the hardware? we try to test our ISO on a variety of hardware, but unfortunately we can't test it on everything... if it keeps being a problem you can try installing regular debian first[0] [0]: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster
hi, what graphics card do you have? can you tell us a bit about the hardware? we try to test our ISO on a variety of hardware, but unfortunately we can't test it on everything... if it keeps being a problem you can try installing regular debian first[0] [0]: https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Buster
G GhostViper New Member May 3, 2020 3 0 1 27 May 4, 2020 #3 Hi Oguz, sorry for the delay in replying. please see below. regards, Dell Precision 7810 Workstation Dual Intel Xeon E5 CPU 64GB 128GB RAM HDD SSD & NVidia Quadro K5200.
Hi Oguz, sorry for the delay in replying. please see below. regards, Dell Precision 7810 Workstation Dual Intel Xeon E5 CPU 64GB 128GB RAM HDD SSD & NVidia Quadro K5200.
oguz Proxmox Retired Staff Retired Staff Nov 19, 2018 5,207 813 118 May 4, 2020 #4 maybe you can try deactivating UEFI in your BIOS and see if it helps (one user had a similar problem and was able to workaround this way)
maybe you can try deactivating UEFI in your BIOS and see if it helps (one user had a similar problem and was able to workaround this way)
G GhostViper New Member May 3, 2020 3 0 1 27 May 4, 2020 #5 I’ve disabled secure boot and switched to legacy and that’s when I get the attached error