Out of range video output at start of install

R

ratcliff

New Member
May 19, 2016
3
0
1
31
Hi,

I'm trying to install 4.2 on to a desktop (foxconn A88GMX) and get an issue almost immediately on boot where the video output goes to a setting not supported by the monitor. I've tried a couple of different monitors and get the same on both.

I have verified the boot media on a spare laptop and this comes up with the Proxmox menu fine.

Any suggestions? I'm using the onboard grapics to the mobo.

Of course the desktop boots fine in to the old windows 7 OS.

Ben
 
Hi,

Is a part of the installer screen just cut off or do you get nothing at all?

Further, do you use UEFI? If yes try to find in the UEFI settings a video/graphic related setting, you may even set the resolution there (depends on EFI implementation).

And if only the button row is cut off you may use M^KEY to press them (M normally is the 'Alt' key, so M^N would be Alt + N):

M^G for agreeing the EULA
M^N for going a step further in the installer
M^A for aborting the installation process
 
Hi Thomas,

Pretty certain the box doesn't have UEFI/EFI
I get an error pop up just before the screen resolution change:

error : file '/boot/grub/i386-pc/efi/gop.mod' not found
error : file '/boot/grub/i386-pc/efi/uga.mod' not found

which obviously has something to do with efi

After this the display indicates that the input is 'out of range' and then because of this is completely blank.

Any ideas?
Kr,
Ben
 
Okay, so attaching to a very new monitor solved it, it looks like it was as suggested running in a resolution not supported by the monitor. Connected via HDMI to a LED TV which was able to run at 1920x1080@60Hz, It's now installed.

Was expecting to be able to hook up an older monitor over VGA.
 
Hmm quite strange, but seems so, uga and gop are the graphical modules from UEFI.

It could be that the BIOS/UEFI has a "legacy" setting for Boot or Video (the name can differ quite, but the meaning would be the same).
If yes setting that to legacy/enabled could have helped here. It can simply also be that the mainboard vendor is a little lax with the specification and only ensured that Windows works, if there are BIOS updates you may want to try them.

But glad you resolved that!
 
I'm getting the same result. Proxmox 7.2. R710 server. I can boot to the initial setup screen, but after selecting "Install Proxmox VE" the screen goes blank, and then the monitor displays the message "frequency out of range." Tried both VGA outputs, no luck.
 
ttt said:
I'm getting the same result. Proxmox 7.2. R710 server. I can boot to the initial setup screen, but after selecting "Install Proxmox VE" the screen goes blank, and then the monitor displays the message "frequency out of range." Tried both VGA outputs, no luck.
Click to expand...
Please search the forum, there have been at least 10 threads about the same problem.

Gist: Try another monitor, or installing via integrated management console or install on top of Debian.
 
I found that if I installed Proxmox to the boot drives for a Dell R710 and then set nomodeset as a boot flag, I could boot Proxmox 7.2 all the way. The way I installed Proxmox to the R710's perc sas controller was to use a Dell Optiplex 7010 as a bootstrapping machine with the Dell R710 acting as power to the sas array while the install happened from the 7010. This was all with UEFI mode enabled. Once the install was done, I powered everything off, put the perc back in the R710 and booted. Manually setting the boot flag the first time and then editing /etc/kernel/cmdline to include the flag.

I did try a handful of pci express 16x-4x adapters that would allow me to plug into a low profile video card into the risers and I got zero response from the few video cards I did try.
 
You must log in or register to reply here.
Top Bottom