Oh dang... Sorry. I remember writing you a response, but must not have posted (???)
Yes, it seems to be a graphics issue. Even though you would think that Server is text console based, it still is in a VGA graphics mode.
This would help if we knew the CPU and video GPU of the machine. One of the things I specialize in is supporting the Linux Graphics Layer, and in supporting Server... Without that information given by you, I'll give you generic instructions that work for most machines.
There are several ways around that:
1.) The easiest and most fool-proof way, is to put it into text-only console mode. At the initial Grub2 boot menu, press the <E> key to get into edit mode on the boot option. <Arrow-Down> to the line that starts with the word "linux" (in that case) ... On the 24.04 Live Server ISO, the boot line will say:
Code:
linux /casper/vmlinuz ---
<Arrow-Right> to the end of that line and change it to
Code:
linux /casper/vmlinuz --- 3
Press the key combination <Cntrl><X> to boot the installer. That will put it into init 3, multi-user console text only mode... Install.
On the first boot, do the same at the Grub2 menu... Edit the /etc/default/grub file with elevated permissions...
You can either uncomment this line
Code:
#GRUB_TERMINAL=console
To look this
Code:
GRUB_TERMINAL=console
Or edit this line
Code:
GRUB_CMDLINE_LINUX_DEFAULT=""
To this
Code:
GRUB_CMDLINE_LINUX_DEFAULT="--- 3"
Effectively, they do the same thing... Then save & exit... Then do
To pick up the changes
2.) Instead of using "3", use the word "nomodeset" to use safe graphics mode.
3.) This is the option I usually use, because I like to use console theming, and work out the VGA graphics modes, and set screen resolutions of the vtty consoles... I work a lot in console. Though most of my management, I do remotely via ssh.
At the Grub2 Boot Menu, press the <C> key to get to Grub commandline... Enter the command
Code:
videoinfo # <--- This command if it booted as UEFI
vbeinfo # <-- This command if it booted as BIOS legacy
Write down the graphics modes that are recognized as being capatible by the BIOS, with the connected display, without any graphics drivers... Pick one and use a "video=..." boot parameter to see if it can use Kernel KMS (kernel mode setting) to clear up the graphics, by giving it what it should expect, instead of letting it guess wrong.
For example, on one of my servers, these are the graphics parts of the kernel boot parameters I use on it:
Code:
GRUB_CMDLINE_LINUX_DEFAULT="--- video=uvesafb:1920x1080-32@60,mtrr:3,ywrap,noblank consoleblank=0"
That way, all the hints are there, and the machine just works how I want it to. When I had all my personal servers in rack with a rack mounted console display, it some wouldn't answer it's EDID query, so I had to set what the display was capable of, and the only resolution mode it would support...
Sometimes the only way to do it with weird hardware. Other times worth it to get things going straight, and happy.
EDIT: If you can post your machines spec's for more info on what you have, I can tailor that solution to your machine.
Bookmarks