[SOLVED] Install Times Out After DHCP

[area51tazz]

G'day!

I'm installing VE 6.1-2 (latest ISO on the site) on an Intel NUC i7 with 32gb RAM and 2 512gb nvme drives which I've removed the partitions from (used to be a vmware host). I have another identical NUC running Proxmox already, which worked flawlessly. I've updated the BIOS and reset to defaults on the one I'm trying to install on.

Problem 1: black screen on normal install.
Solution: run with nomodeset

Problem(?) 2: sometimes doesn't get DHCP response. Not sure why, but it's not every time. This is not my biggest problem.

Main Problem: Once I get the system to boot past the video issue and it gets an IP, it just sits there for a few minutes before failing. There's also no log in /tmp/install.log

I'm happy to gather anything I can to help, but I'm not making it very far before failing. Thank you in advance for any direction you can provide.

 

[area51tazz]

I'll post updates as I go to hopefully help someone in the future.

I found these and tried both in the same go:
<lower RAMDISK size> (not sure why I thought this might help, but :shrugged:
https://forum.proxmox.com/threads/6...ed-after-binding-dhcp-lease.57321/post-279042

Since I wasn't getting a log file I ran xinit after the install failed and found the following...
https://forum.proxmox.com/threads/installation-aborted-after-dhcp-lease.62116/post-284583

"Failed server error:
Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices

Please also check the log file at "/var/log/Xorg.0.log" for additional information"

 

[area51tazz]

Based on that log, it looks like a display issue for me. I'm using a Samsung TV in a corporate apartment while all of my normal gear is shipped from another country. I've just ordered 3 800x480 screens specifically for computers, so we'll see if that works.

 

[area51tazz]

So I had one of my engineers bring over a monitor, and Proxmox installed flawlessly. I didn't even have to use nomodeset.

Lesson: What kind of monitor you're using matters...even when not loading the driver (nomodeset)