Is anybody else not able to see the BIOS configuration on a DisplayPort connection? I could have sworn prior to this latest firmware update I was booting into my BIOS no problem. Maybe I am hallucinating, but I have to resort to an HDMI connection these days.
1 Like
I just ran into this recently now that I’ve started playing with Linux installs. I had been using HDMI and had no problem with bios screens, but Linux can’t see my full monitor resolution (5120x1440) over HDMI so I started to try DisplayPort. Now I can’t see my refind boot screen any more. Occasionally I’ve gotten it to show by randomly playing with the arrow keys, but it doesn’t always work. So, it appears that DP display can happen during the boot sequence, but it is flaky.
I have had some success since, like the one time I unplugged the DP connection and plugged it back in. But this whole thing is really annoying, hoping Framework addresses this on the next release because I don’t wanna open a ticket. It’s def a software/firmware issue.
My screen goes blank and every once in a while my monitors will say it can’t support the signal since it expects 1080p at 60Hz.
I had this problem since the original BIOS, but its gotten worse with the update.
My primary screen has a high chance of not displaying in the BIOS (and then flickering on and off), often i’ve had to power it off so the BIOS displays on my secondary monitor instead…
Config:
FW Desktop 128GB
LS28AG700N **
Dell Inc. DELL P2425 ***
** This monitor breaks very often over displayport in the BIOS
*** This monitor has no issues
Both monitors work fine in an OS, the Samsung screen only misbehaves in the BIOS screens
We should probably be opening tickets so that Framework is aware of the issue.
I have a Samsung 49" (the regular one, does not have the smart OS that is usually the culprit in this manner) which has no trouble showing the UEFI/Refind screen from my DIY PC and also has no problem showing the UEFI/Refind screen from the HDMI port on my Framework Desktop, but I’ve seen it maybe once since I switched to using DisplayPort.
I figured before I submitted a ticket I’d try something first (am I holding this right?)
I switched the cable from the “top” DP port to the “bottom” one (while Linux Mint was running). The video switched just fine.
Then I restarted and Refind showed up just fine.
Then I shut down, waited 10 seconds after the PSU click and pressed the power button - again Refind showed up just fine.
So, perhaps it is finicky about which DP port you use? Or maybe it just works OK if the monitor is still somewhat non-groggy due to the quick turnaround in restarting the machine? I’ll keep using it this way to see if the problems return.
In any case, I just had some luck with using what I’m calling the “bottom” DP port - the one closer to the side of the machine - the one that is closer to the motherboard - the one that lines up with the bottom row of ports that includes the HDMI port, the 2 USB-C ports, one of the USB-A ports and the audio socket.