If your mobo has an efi bootloader, which now-a-days almost all are, make sure grub is also an efi image and don’t allow the early boot to take control of the frame buffer.
Setting these flags for the bootloader, grub in your case, should make sure the monitor only does a single initialize.
I can give that a whirl if it’s not set up like that already, but the monitor is VERY slow on its own. It basically never wakes up in time for the BIOS bootscreen and any signal interruption sends it on a wild goose chase of signal searching around its inputs that can take ten seconds at a time. It’s not a cheap monitor, either, which I assume is part of the problem, as it wants to be super smart about a bunch of things and has to contend with a bunch of options and alternatives that maybe a simpler setup wouldn’t.
Still, worth a shot to try to tune grub and double check if it’s swapping modes unnecessarily between the bios image and the menu. I hadn’t considered it. Like so many Linux features and app there’s a bunch of stuff you can config on it that I keep not looking into because it’s only surfaced in documentation, if that.
EDIT: Tried, didn’t help. The motherboard rebooting gives the monitor just enough time to search its display port input, decide it’s been unplugged and shut down, so by the time another monitor picks up the slack it’s too late and the timeout has expired unless you’re mashing down to stop it. The changes do make the second monitor come up at its native resolution instead of changing modes, but the mistake happens elsewhere.
I could just set a longer timeout, but I’d rather have a faster boot when I’m sticking to the default than wait for the whole mess to sort itself out every time. Been mashing bios entry buttons and bootloader menus since the 90s, what’s a couple decades more.
If your mobo has an efi bootloader, which now-a-days almost all are, make sure grub is also an efi image and don’t allow the early boot to take control of the frame buffer.
Setting these flags for the bootloader, grub in your case, should make sure the monitor only does a single initialize.
GRUB_TERMINAL_OUTPUT=gfxterm GRUB_GFXPAYLOAD_LINUX=keepSource: just went through something similar and was annoyed that the monitor would take forever to start.
I can give that a whirl if it’s not set up like that already, but the monitor is VERY slow on its own. It basically never wakes up in time for the BIOS bootscreen and any signal interruption sends it on a wild goose chase of signal searching around its inputs that can take ten seconds at a time. It’s not a cheap monitor, either, which I assume is part of the problem, as it wants to be super smart about a bunch of things and has to contend with a bunch of options and alternatives that maybe a simpler setup wouldn’t.
Still, worth a shot to try to tune grub and double check if it’s swapping modes unnecessarily between the bios image and the menu. I hadn’t considered it. Like so many Linux features and app there’s a bunch of stuff you can config on it that I keep not looking into because it’s only surfaced in documentation, if that.
EDIT: Tried, didn’t help. The motherboard rebooting gives the monitor just enough time to search its display port input, decide it’s been unplugged and shut down, so by the time another monitor picks up the slack it’s too late and the timeout has expired unless you’re mashing down to stop it. The changes do make the second monitor come up at its native resolution instead of changing modes, but the mistake happens elsewhere.
I could just set a longer timeout, but I’d rather have a faster boot when I’m sticking to the default than wait for the whole mess to sort itself out every time. Been mashing bios entry buttons and bootloader menus since the 90s, what’s a couple decades more.
Still dumb, though.
Sorry that didn’t help! Thanks for trying though.