White screen after running installer (possible graphics/driver issues)

[exklamationmark]

Hi,

I pieced some old parts together for a mini-ITX server and tried to install Proxmox on it, but saw a white screen (with movable cursor) and nothing else after running the installer.
It seems the problem might be graphics controller/driver related since I have the similar issues when installing Ubuntu on the box.

System:

Motherboard: Asus Q87T/CSM (LGA1150)
CPU: Intel Core i7-4770K
Memory: 2 x 8 GB DDR3-1600 CL9
Storage:  480 GB 2.5" SSD

I also tried editing grub with a few options:

debug nomodeset
It failed after getting an IP, plus there is no /tmp/install.log to check

bound to 192.168.1.62 -- renewal in 36089 seconds.
done

\nInstallation aborted - unable to continue (type exit or CTRL-D to reboot)

debug vga=normal noapic noacpi mem=512M
After getting an IP (same as nomodeset), it showed the blank, white screen again.

******
On the other hand, I had similar issues when testing by installing Ubuntu on it
- Ubuntu server 20.04: installed and working with the onboard graphics
- Ubuntu desktop 20.04: failed to start properly (during installation, I had to switch to the Safe graphics). The kernel still start and I can launch the terminal, but parts of the GNOME UI (dock, status bar, login screen, etc) didn't show up.

******
The board is using integrated graphics:

$> lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integerated Graphics Controller (rev 06)

Would these info be enough to guess what happened?

Thanks for looking 八(＾□＾*)

 

[Moayad]

Hi,

Have you checked the output on the console and in journalctl -r and dmesg in debug mode? however, you still can install Proxmox VE on Debian Buster [1]


[1] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_install_proxmox_ve_on_debian

 

[exklamationmark]

Hi,

Thanks for the prompt reply.

I was able to get to this point using debug mode:

/ # Startting Proxmox installation
EFI boot mode detected, mounting efivars filesystem
Installing additional hardware drivers
[ ok ] Starting hotplug events dispatcher: systemd-udevd.
[ ok ] Synthesizing the initial hotplug events (subsystems)...done.
[ ok ] Synthesizing the initial hotplug events (devices)...done.
[....] Waiting for /dev to be fully populated...[   19.742980] snd_hda_intel 000
ding with gfx driver
[   19.752921] hdaudio hdaudioC1D0: Unable to bind the codec
done.
mount: devpts mounted on /dev/pts.
Dropping in debug shell inside chroot before starting installation

dmesg showed some possible problems related to hdaudio (which I believe might not be important here)

...
snd_hda_intel 0000:00:03.0: HSW/BDW HD-audio HDMI/DP requires binding with gfx driver
hdaudio hdaudioC1D0 Unable to bind the codec

and after that:

systemdd-udevd[1091]: Using default interface naming scheme 'v240'.
fb0: switching to inteldrmfb from EFI VGA
Console: switching to colour dummy device 80x25
i915 0000:00:02.0: vgaarb: deactivate vga console
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013)
[drm] Driver supports precise vblank timestamp query.
i915 0000:00:02.0] vgaarab:changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
i915 0000:00:02.0 [drm:intel_dp_aux_init_backlight_funcs [i915]] Panel advertises DPCD backlight support, but VBT disagrees. If your backlight controls don't work try booting with i915.enable_dpcd_backlight=1. If your machine needs this, please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/intel
[drm] Initialized i915 1.6.0 20190822 for 0000:00:02.0 on minor 0
ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
input: Video Bus as /ddevices/LNXSYSTM:00/LNXSYSBUS/:00/PNP0A08:00/LNXXXXVIDEO:00/input/input9
fbcon: i915drmfb (fb0) is primary device
Console: switching to colour framae buffer device 240x67
i915 0000:00:02.0: fb0: i915dddrmfb frame buffer device

The screen did change resolution to 240x67 at this point.

There was nothing for journalctl -r:

No journal files were found.
-- No entries --

After continuing (Ctrl-D), I got to the white screen and can't get a shell anymore.

I will try to install from Debian and report back.

 

[truthTM]

Looks like i am one the same trail....
Fujitsu D3674-D could not install from stick with same error stuck after install start with white screen and moveable mouse. Tries all kinds of BIOS settings no success. Stick works on other machines pretty well.
16GB RAM single bank, I5-9600T, PCI-SSD 250GB, latest BIOS, All checks are ok. Is new a board.
Debian Buster is running great, so followed the advice to install on Debian. But install fails:

Job for pvestatd.service failed because the control process exited with error code. See "systemctl status pvestatd.service" and "journalctl -xe" for details. dpkg: Fehler beim Bearbeiten des Paketes pve-manager (--configure): »installiertes pve-manager-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück dpkg: Abhängigkeitsprobleme verhindern Konfiguration von proxmox-ve: proxmox-ve hängt ab von pve-manager; aber: Paket pve-manager ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes proxmox-ve (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert

journalctl -xe shows:
oot@debian:/etc# journalctl -xe Apr 09 19:04:32 debian pveproxy[24900]: worker 9525 finished Apr 09 19:04:32 debian pveproxy[24900]: starting 1 worker(s) Apr 09 19:04:32 debian pveproxy[24900]: worker 9528 started Apr 09 19:04:32 debian pveproxy[9527]: /etc/pve/local/pve-ssl.key: failed to load local Apr 09 19:04:32 debian pveproxy[9528]: /etc/pve/local/pve-ssl.key: failed to load local Apr 09 19:04:32 debian kernel: pcieport 0000:00:1c.0: AER: Corrected error received: 000 Apr 09 19:04:32 debian kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected Apr 09 19:04:32 debian kernel: pcieport 0000:00:1c.0: device [8086:a33c] error status/ Apr 09 19:04:32 debian kernel: pcieport 0000:00:1c.0: [ 0] RxErr (Fi Apr 09 19:04:37 debian pveproxy[9526]: worker exit Apr 09 19:04:37 debian pveproxy[9527]: worker exit Apr 09 19:04:37 debian pveproxy[24900]: worker 9526 finished Apr 09 19:04:37 debian pveproxy[24900]: starting 1 worker(s) Apr 09 19:04:37 debian pveproxy[9528]: worker exit Apr 09 19:04:37 debian pveproxy[24900]: worker 9529 started Apr 09 19:04:37 debian pveproxy[9529]: /etc/pve/local/pve-ssl.key: failed to load local Apr 09 19:04:37 debian pveproxy[24900]: worker 9527 finished Apr 09 19:04:37 debian pveproxy[24900]: starting 1 worker(s) Apr 09 19:04:37 debian pveproxy[24900]: worker 9530 started Apr 09 19:04:37 debian pveproxy[24900]: worker 9528 finished Apr 09 19:04:37 debian pveproxy[24900]: starting 1 worker(s) Apr 09 19:04:37 debian pveproxy[24900]: worker 9531 started Apr 09 19:04:37 debian pveproxy[9530]: /etc/pve/local/pve-ssl.key: failed to load local Apr 09 19:04:37 debian pveproxy[9531]: /etc/pve/local/pve-ssl.key: failed to load local Apr 09 19:04:37 debian kernel: pcieport 0000:00:1c.0: AER: Corrected error received: 000 Apr 09 19:04:37 debian kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected Apr 09 19:04:37 debian kernel: pcieport 0000:00:1c.0: device [8086:a33c] error status/ Apr 09 19:04:37 debian kernel: pcieport 0000:00:1c.0: [ 0] RxErr (Fi Apr 09 19:04:32 debian pveproxy[24900]: worker 9525 finished Apr 09 19:04:32 debian pveproxy[24900]: starting 1 worker(s) Apr 09 19:04:32 debian pveproxy[24900]: worker 9528 started Apr 09 19:04:32 debian pveproxy[9527]: /etc/pve/local/pve-ssl.key: failed to load local p Apr 09 19:04:32 debian pveproxy[9528]: /etc/pve/local/pve-ssl.key: failed to load local p Apr 09 19:04:32 debian kernel: pcieport 0000:00:1c.0: AER: Corrected error received: 0000 Apr 09 19:04:32 debian kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, Apr 09 19:04:32 debian kernel: pcieport 0000:00:1c.0: device [8086:a33c] error status/m Apr 09 19:04:32 debian kernel: pcieport 0000:00:1c.0: [ 0] RxErr (Fir Apr 09 19:04:37 debian pveproxy[9526]: worker exit Apr 09 19:04:37 debian pveproxy[9527]: worker exit Apr 09 19:04:37 debian pveproxy[24900]: worker 9526 finished Apr 09 19:04:37 debian pveproxy[24900]: starting 1 worker(s) Apr 09 19:04:37 debian pveproxy[9528]: worker exit Apr 09 19:04:37 debian pveproxy[24900]: worker 9529 started Apr 09 19:04:37 debian pveproxy[9529]: /etc/pve/local/pve-ssl.key: failed to load local p Apr 09 19:04:37 debian pveproxy[24900]: worker 9527 finished Apr 09 19:04:37 debian pveproxy[24900]: starting 1 worker(s) Apr 09 19:04:37 debian pveproxy[24900]: worker 9530 started Apr 09 19:04:37 debian pveproxy[24900]: worker 9528 finished Apr 09 19:04:37 debian pveproxy[24900]: starting 1 worker(s) Apr 09 19:04:37 debian pveproxy[24900]: worker 9531 started Apr 09 19:04:37 debian pveproxy[9530]: /etc/pve/local/pve-ssl.key: failed to load local p Apr 09 19:04:37 debian pveproxy[9531]: /etc/pve/local/pve-ssl.key: failed to load local p Apr 09 19:04:37 debian kernel: pcieport 0000:00:1c.0: AER: Corrected error received: 0000

... Job for pve-firewall.service failed because the control process exited with error code. ... Job for pve-ha-lrm.service failed because the control process exited with error code. See "systemctl status pve-ha-lrm.service" and "journalctl -xe" for details. Job for pve-ha-crm.service failed because the control process exited with error code. See "systemctl status pve-ha-crm.service" and "journalctl -xe" for details. ... pve-manager (6.3-6) wird eingerichtet ... ipcc_send_rec[1] failed: Connection refused ipcc_send_rec[2] failed: Connection refused ipcc_send_rec[3] failed: Connection refused Unable to load access control list: Connection refused

systemctl status pve-cluster.service ● pve-cluster.service - The Proxmox VE cluster filesystem Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enab Active: failed (Result: exit-code) since Fri 2021-04-09 18:59:03 CEST; 44min ago Process: 9310 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION) Apr 09 18:59:03 debian systemd[1]: pve-cluster.service: Service RestartSec=100ms expired Apr 09 18:59:03 debian systemd[1]: pve-cluster.service: Scheduled restart job, restart c Apr 09 18:59:03 debian systemd[1]: Stopped The Proxmox VE cluster filesystem. Apr 09 18:59:03 debian systemd[1]: pve-cluster.service: Start request repeated too quick Apr 09 18:59:03 debian systemd[1]: pve-cluster.service: Failed with result 'exit-code'. Apr 09 18:59:03 debian systemd[1]: Failed to start The Proxmox VE cluster filesystem.

root@debian:/home/ulrich# lspci 00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Desktop) 00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10) 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial IO I2C Controller (rev 10) 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10) 00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10) 00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device a303 (rev 10) 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10) 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a80a 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)

Any hint is wellcome...

 

[zurica]

It seems that I have experienced the same problem with you guys, and I finally fixed it!
One hint is that the problem caused by hardware settings rather than OS defects, that's why you cannot install Ubuntu neither. You may find that both motherboards mentioned, Asus Q87T/CSM and Fujitsu D3674-D ( for me are intel DQ77KB and ECS H310CH5-TI4 ) are thin-ITX boards designed for All-in-One computer with LVDS/eDP video output. Yes, the white screen is what LVDS "display" shows.
I shall explain it in detail later.

 

[zurica]

I used to install PVE 6.2 in my DQ77KB server in 2020 and it worked very well. But recently I've changed the OS disk so need o re-install PVE again, but it failed with the problem you described.
Since I had a similar experience when I installed Pop!_OS to another mini computer (ECS H310CH5-TI4) , "a blank screen with no installer popped up", and I finally found that there are something wrong with xserver, that on-board LVDS output was the default display ( use "xrandr --listmonitors" to see the "ghost display"), so finally I use some xorg config to turn off that output and get the right screen appearance.
Then I tried the same method but found it's a bit different for DQ77KB motherboard: if I switch off the LVDS output, it will turn totally black screen. I guess LVDS output is not set to be the default video, but something wrong with the HDMI output then LVDS came to work with improper appearance.
So I took the last resort: change the display (13.3' portable display with HDMI-miniHDMI connection) to my SONY KD-55X9500G TV. And it finally worked!
My suggestion:
1) try to switch the on-board LVDS/eDP output
2) try a better display with better HDMI connection

 

[zurica]

Looks like i am one the same trail....
Fujitsu D3674-D could not install from stick with same error stuck after install start with white screen and moveable mouse. Tries all kinds of BIOS settings no success. Stick works on other machines pretty well.
16GB RAM single bank, I5-9600T, PCI-SSD 250GB, latest BIOS, All checks are ok. Is new a board.
Debian Buster is running great, so followed the advice to install on Debian. But install fails:

Job for pvestatd.service failed because the control process exited with error code. See "systemctl status pvestatd.service" and "journalctl -xe" for details. dpkg: Fehler beim Bearbeiten des Paketes pve-manager (--configure): »installiertes pve-manager-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück dpkg: Abhängigkeitsprobleme verhindern Konfiguration von proxmox-ve: proxmox-ve hängt ab von pve-manager; aber: Paket pve-manager ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes proxmox-ve (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert

journalctl -xe shows:
oot@debian:/etc# journalctl -xe Apr 09 19:04:32 debian pveproxy[24900]: worker 9525 finished Apr 09 19:04:32 debian pveproxy[24900]: starting 1 worker(s) Apr 09 19:04:32 debian pveproxy[24900]: worker 9528 started Apr 09 19:04:32 debian pveproxy[9527]: /etc/pve/local/pve-ssl.key: failed to load local Apr 09 19:04:32 debian pveproxy[9528]: /etc/pve/local/pve-ssl.key: failed to load local Apr 09 19:04:32 debian kernel: pcieport 0000:00:1c.0: AER: Corrected error received: 000 Apr 09 19:04:32 debian kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected Apr 09 19:04:32 debian kernel: pcieport 0000:00:1c.0: device [8086:a33c] error status/ Apr 09 19:04:32 debian kernel: pcieport 0000:00:1c.0: [ 0] RxErr (Fi Apr 09 19:04:37 debian pveproxy[9526]: worker exit Apr 09 19:04:37 debian pveproxy[9527]: worker exit Apr 09 19:04:37 debian pveproxy[24900]: worker 9526 finished Apr 09 19:04:37 debian pveproxy[24900]: starting 1 worker(s) Apr 09 19:04:37 debian pveproxy[9528]: worker exit Apr 09 19:04:37 debian pveproxy[24900]: worker 9529 started Apr 09 19:04:37 debian pveproxy[9529]: /etc/pve/local/pve-ssl.key: failed to load local Apr 09 19:04:37 debian pveproxy[24900]: worker 9527 finished Apr 09 19:04:37 debian pveproxy[24900]: starting 1 worker(s) Apr 09 19:04:37 debian pveproxy[24900]: worker 9530 started Apr 09 19:04:37 debian pveproxy[24900]: worker 9528 finished Apr 09 19:04:37 debian pveproxy[24900]: starting 1 worker(s) Apr 09 19:04:37 debian pveproxy[24900]: worker 9531 started Apr 09 19:04:37 debian pveproxy[9530]: /etc/pve/local/pve-ssl.key: failed to load local Apr 09 19:04:37 debian pveproxy[9531]: /etc/pve/local/pve-ssl.key: failed to load local Apr 09 19:04:37 debian kernel: pcieport 0000:00:1c.0: AER: Corrected error received: 000 Apr 09 19:04:37 debian kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected Apr 09 19:04:37 debian kernel: pcieport 0000:00:1c.0: device [8086:a33c] error status/ Apr 09 19:04:37 debian kernel: pcieport 0000:00:1c.0: [ 0] RxErr (Fi Apr 09 19:04:32 debian pveproxy[24900]: worker 9525 finished Apr 09 19:04:32 debian pveproxy[24900]: starting 1 worker(s) Apr 09 19:04:32 debian pveproxy[24900]: worker 9528 started Apr 09 19:04:32 debian pveproxy[9527]: /etc/pve/local/pve-ssl.key: failed to load local p Apr 09 19:04:32 debian pveproxy[9528]: /etc/pve/local/pve-ssl.key: failed to load local p Apr 09 19:04:32 debian kernel: pcieport 0000:00:1c.0: AER: Corrected error received: 0000 Apr 09 19:04:32 debian kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, Apr 09 19:04:32 debian kernel: pcieport 0000:00:1c.0: device [8086:a33c] error status/m Apr 09 19:04:32 debian kernel: pcieport 0000:00:1c.0: [ 0] RxErr (Fir Apr 09 19:04:37 debian pveproxy[9526]: worker exit Apr 09 19:04:37 debian pveproxy[9527]: worker exit Apr 09 19:04:37 debian pveproxy[24900]: worker 9526 finished Apr 09 19:04:37 debian pveproxy[24900]: starting 1 worker(s) Apr 09 19:04:37 debian pveproxy[9528]: worker exit Apr 09 19:04:37 debian pveproxy[24900]: worker 9529 started Apr 09 19:04:37 debian pveproxy[9529]: /etc/pve/local/pve-ssl.key: failed to load local p Apr 09 19:04:37 debian pveproxy[24900]: worker 9527 finished Apr 09 19:04:37 debian pveproxy[24900]: starting 1 worker(s) Apr 09 19:04:37 debian pveproxy[24900]: worker 9530 started Apr 09 19:04:37 debian pveproxy[24900]: worker 9528 finished Apr 09 19:04:37 debian pveproxy[24900]: starting 1 worker(s) Apr 09 19:04:37 debian pveproxy[24900]: worker 9531 started Apr 09 19:04:37 debian pveproxy[9530]: /etc/pve/local/pve-ssl.key: failed to load local p Apr 09 19:04:37 debian pveproxy[9531]: /etc/pve/local/pve-ssl.key: failed to load local p Apr 09 19:04:37 debian kernel: pcieport 0000:00:1c.0: AER: Corrected error received: 0000

... Job for pve-firewall.service failed because the control process exited with error code. ... Job for pve-ha-lrm.service failed because the control process exited with error code. See "systemctl status pve-ha-lrm.service" and "journalctl -xe" for details. Job for pve-ha-crm.service failed because the control process exited with error code. See "systemctl status pve-ha-crm.service" and "journalctl -xe" for details. ... pve-manager (6.3-6) wird eingerichtet ... ipcc_send_rec[1] failed: Connection refused ipcc_send_rec[2] failed: Connection refused ipcc_send_rec[3] failed: Connection refused Unable to load access control list: Connection refused

systemctl status pve-cluster.service ● pve-cluster.service - The Proxmox VE cluster filesystem Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enab Active: failed (Result: exit-code) since Fri 2021-04-09 18:59:03 CEST; 44min ago Process: 9310 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION) Apr 09 18:59:03 debian systemd[1]: pve-cluster.service: Service RestartSec=100ms expired Apr 09 18:59:03 debian systemd[1]: pve-cluster.service: Scheduled restart job, restart c Apr 09 18:59:03 debian systemd[1]: Stopped The Proxmox VE cluster filesystem. Apr 09 18:59:03 debian systemd[1]: pve-cluster.service: Start request repeated too quick Apr 09 18:59:03 debian systemd[1]: pve-cluster.service: Failed with result 'exit-code'. Apr 09 18:59:03 debian systemd[1]: Failed to start The Proxmox VE cluster filesystem.

root@debian:/home/ulrich# lspci 00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Desktop) 00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10) 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH Serial IO I2C Controller (rev 10) 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10) 00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10) 00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device a303 (rev 10) 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10) 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a80a 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)

Any hint is wellcome...

hope that my answer can help you

 

[throwawayonetime]

Man, I registered just to tell you thanks, it was indeed for me too an issue with eDP vs HDMI: after I switched the HDMI input, it worked !!
I suppose proxmox, if they wanted to fix this non-critical issue, could try to set the display in mirror mode if it detects two during the install ?

 

[maciej_kawala]

Hello, thanks for suggestion. I was have the similar problem. After change cable/connection (DVI->VGA) installation ran.