I tried editing the topic title to reflect that the issue has been “solved”, but I can’t. Maybe some forum admin can do it for me? Thanks.
The gen 1 module works fine if replugged after booting though right? I’m guessing pre Linux environment is putting it into a weird state. Seems like something framework will fix eventually if so.
I’ve had a similar issue come up on Fedora 41 (Silverblue) with a 3rd gen HDMI expansion card. I plug in some monitors (that worked with this card previously) and they refuse to connect, though others seem to work. I noticed it starting on kernel 6.12.7. I’ve reverted to 6.12.5 and 6.11.11 and I still have the same issue. I’ve used the expansion card from a separate Windows machine and it works there, so it doesn’t seem to be a hardware issue. This issue also occurs when using 3rd party USB-C dongles.
dmesg output is the same amdgpu 0000:c1:00.0: [drm] Alt mode has timed out after 217 ms
I also had to update kargs with amdgpu.dcdebugmask=0x10 to deal with some stuttering issues introduced recently as well.
Random thought just in case. I had this issue before as well and ended up resolving it through a BIOS update. I found that weird because same BIOS was working before (literally same boot). The Arch Linux post from kriestof linked to earlier shows that it’s related to some internal state, which in their case was at some point restored by running another OS. The topic got bumped again by kriestof last month with BIOS/firmware being significant once again. Any chance you can reinstall the latest BIOS (which I assume you already have) to see if that helps?
Thanks for the reply - I am already on JFP30.03.05 and I think it came that way from the factory. I suppose I could try reinstalling BIOS via USB…
I reflashed my BIOS and it did fix the issue, thanks! I saw on some other machines where similar issues happened, that they were fixed by booting a live USB of another Linux distribution as well (unfortunately I’ve lost the link to the post). That might be an easier alternative if anyone else comes across this issue.
Great news. If anyone knows what kind of hidden state can be affected by booting a different OS or re-flashing the BIOS, maybe the issue can be narrowed down a bit.
This post here has some similar symptoms: Reddit - Dive into anything
Hopefully not the same though, seeing as their motherboard eventually failed.