Black screen after fresh install Proxmox 8 on Intel Nuc 13

[rikshomelab]

Hi,
I'm using Proxmox 7.4.17 for a while now on my Intel Nuc 10th generation. I want to extend my HomeLab with a second Intel Nuc from the 13th generation but I'm running in some problems after the installation of Proxmox 8.1.3. The installation is going fine but when I reboot the NUC I will get a black screen and I can't ping Proxmox. CTRL+ALT+DEL won't work so I need to use the power button.
Sometimes I need to turn the NUC on and of for 3 times before Proxmox starts loading.

I tried the following

* Bios upgrade
* Memtest > Passed
* switched the memory for another one
* Installing Debian Bookworm which gives me the same behavior.
* Installing Windows 11 which gives my no problems at all

So I thought there was a hardware malfunction on my NUC so I switched it with another one. But after doing the same procedure (installing Proxmox 8.1.3., installing updates en rebooting) I have the same problems.


Hardware:


* Intel NUC 13 Pro Kit i3 Arena Canyon NUC13ANKi3
* Crucial 32GB 3200MHz DDR4 SODIMM (1x32GB)
* Samsung 970 EVO PLUS M.2 2TB

Does anyone have any idea how I can fix this problem?

 

[esi_y]

Hi,
I'm using Proxmox 7.4.17 for a while now on my Intel Nuc 10th generation. I want to extend my HomeLab with a second Intel Nuc from the 13th generation but I'm running in some problems after the installation of Proxmox 8.1.3. The installation is going fine but when I reboot the NUC I will get a black screen and I can't ping Proxmox. CTRL+ALT+DEL won't work so I need to use the power button.
Sometimes I need to turn the NUC on and of for 3 times before Proxmox starts loading.

So you do get it working (i.e. get past the blank screen) all the way to boot screen and login at least sometimes? Or even it starts loading it eventually ends with blank screen?

I tried the following

* Bios upgrade
* Memtest > Passed
* switched the memory for another one
* Installing Debian Bookworm which gives me the same behavior.

Out of curiousity, I would try to install Ubuntu Server and see if I get the same behaviour (in terms of not even booting). Or at least I would make myself Debian Live USB and boot through that and see that goes well (every time) to begin with. Another question, what happens if you e.g. manually press F10 to get boot menu on that PVE EFI install and manually select it? Also goes blank sometimes?

* Installing Windows 11 which gives my no problems at all

That would sound like a graphics driver issue. Can you check bootlogs of the previous boot attemps?

So I thought there was a hardware malfunction on my NUC so I switched it with another one. But after doing the same procedure (installing Proxmox 8.1.3., installing updates en rebooting) I have the same problems.


Hardware:


* Intel NUC 13 Pro Kit i3 Arena Canyon NUC13ANKi3
* Crucial 32GB 3200MHz DDR4 SODIMM (1x32GB)
* Samsung 970 EVO PLUS M.2 2TB

Does anyone have any idea how I can fix this problem?

Complete shot in the dark, I would disable, in EFI, everything that I do not need for that PVE, e.g. Audio, etc. and set only one video output as primary and be sure I am using that one. For the sake of testing, I would also disable C-states, disable HT.

 

[rikshomelab]

Thank you tempacc346235 for your response. I'm having a kind of solution for my problem.

As reply to your question. Most of the times Proxmox starts and all is working fine. Sometimes when a do a reboot a black screen appears.
Your suggestion for a live CD was also my idea but I did it a little different. I installed Proxmox on an external USB HDD and it was working fine. So I thought it was the M.2 drive. But unfortunately a normal SSD didn't fix the problem.

When I connected the USB HDD I accidentally connected my monitor to the HDMI 2 port. When I removed the USB HDD for building in the normal SSD I put the monitor back in the HDMI 1 again. So when problems were starting again I switched the monitor cable to HDMI 2 and the problems were gone. Now when I don't connect a monitor at al which is fine for proxmox all the (re)boots are successful.

So I'm guessing it has something to do whit the graphics driver like you said but I follow the instructions for Intel Graphics on https://wiki.debian.org/GraphicsCard but that didn't fix the problem.