Apologies if I’ve missed this elsewhere, but is it possible to:
Always display the BIOS/firmware setup/boot messages on an external monitor (connected via HDMI adapter or USB C)
Turn off the Framework’s own display?
[Moderators, could you please move this into the Framework 13 category, and add the “amd” tag? The forum is misconfigured and is not allowing me to add a post with the right tag there]
I think there is an option for this on the Intel BIOS but seems the AMD bios is missing this.
I stumbled also upon this when i received my FW13 as my display was broken out of the box. I had to disconnect the internal display from the motherboard so I could get the bios screen to show up on my external monitor.
Sigh. Thanks.
Just wanted to +1 this. IMHO, I think a “display preference” option in BIOS should be the goal, rather than forcing one particular monitor. At the same time, I think clarity from FW Support on whether this is something within their control would be helpful.
I did find a Reddit thread, for Tuxedo Computers, where one of their support staff claims it is totally an AMD issue, and beyond Tuxedo’s control: https://www.reddit.com/r/tuxedocomputers/comments/1abfdgg/show_bios_on_external_monitor/ That suggests, but doesn’t confirm, that the issue is also beyond Framework’s control (for now, at least).
It seems to actually be an issue with AMD and not totally on the bios.
So it seems that on AMD this will not be possible currently, which is a really shame. Only way to do it to unlatch the eDP cable/display cable from the motherboard. Then the picture will be routed to an external display.
Got it, Intel/Apple for laptops in future, AMD for everything else. Well spotted @wjs.
It’s a pity.
I wonder whether display mirroring by default is possible - this would solve using the Framework from a KVM.
@inffy - My working assumption is that this is first a limitation of AMDgpu, the Linux driver for AMD Raedon cards. IF AMD were to modify that to make a “display preference” option available, then (and only then) would Framework be able to modify its BIOS to include that option. And if it is actually an AMD hardware issue, then transparency on that would be helpful. It could significantly influence future purchasing decisions.
@voltagex - I’m not sure the issue is that binary … especially if this is just an AMD driver issue. I’m also skeptical that introducing another device (i.e., a KVM switch) into the mix would really address the main issue in a sustainable way. Exactly why AMD has made this (apparent) driver design choice is unclear to me … unless it was aiming for sheer simplicity, or just hasn’t gotten around to implementing the option? I don’t know … but I would like to make noise with the right people at both AMD and Framework to get this addressed.
amdgpu isn’t involved in displaying the UEFI firmware interface.
as far as i understood on some posts on the great internets ( i might have understood it completely wrong) the amdgpu driver can’t be used as its only loaded after the bootloader.
But i am not anyway familiar with this and don’t know how Intel does it differently
@voltagex So you’re saying this isn’t an AMD issue at all … and the fault for the absence of this capability rests entirely with Framework?
Perhaps it isn’t amdgpu; perhaps it is an AMD firmware issue? In any case, I would expect Framework Support to say “we can’t do this until AMD makes these other modifications.” If that’s not the case, and the fault lies entirely with Framework … well, I suppose that would explain why they’ve been silent on the issue? 
AMD and Insyde are responsible for the firmware design to the best of my knowledge, but you are best to wait for someone with more expertise to weigh in here.
All I am saying is that a Linux driver is not running… when Linux hasn’t started yet.