You sure about that? I’m able to run software that is definitely 32bit in Hiren’s BootCD PE; I quickly confirmed this with the simple stand-alone EXE program “Header Investigator” which itself predates 64bit Windows: http://www.railjonrogut.com/HeaderInvestigator.htm
Heck, according to the task manager, even the included copy of GPU-Z is 32bit (in fact it doesn’t seem like a 64bit of GPU-Z even exists on the internet).
In progress. We have a version that puts the HDMI card into a suspend state, but doesn’t put it back into a state where HDMI works, which is not so useful. We’ll share the firmware as soon as it is ready.
This is really great to hear this is being actively worked on - would it be possible in the future to share what fixes/ improvements Framework are working on/planning to work on?
Perhaps I missed it but this topic and a mention in the linux battery life thread are the first I’m aware of this even being acknowledged or actively being and worked on. Having to hunt down comments in long topics doesn’t seem a very easy way to keep abreast of the work being done.
Linux support is definitely something I would like to see for this update. I’ve been doing extensive analysis of power usage of various parts of the Framework laptop and I’d be happy to rerun those tests with a beta version…
I know this FW update was not intended to correct my specific issue but I didn’t have anything to lose.
I have been having problems with the DP card and a 12th Gen board. I have tried two DP cards and the first one would freeze and then shutdown my laptop. The second one would connect unreliably. Both cards would randomly connect and disconnect themselves from my Windows 11 install. The second card was provided after contacting Framework support.
In a “why not try it” moment, I downloaded the FW updated and applied it to the first card which gave me the most and repeatable trouble. So far, so good. No freezes or shutdowns.
One thing I would like to note. Framework provided the “original” FW in case you need to revert back. I noticed that the version currently on one card appears to be 18.104.22.168, which is odd that the revert FW provided is version 6. Seems the FW on the card is older than what is considered the original FW. Perhaps I’m reading the information incorrectly.
UPDATE: Well, I was wrong about having nothing to lose. Initially the FW update seemed to correct my problem, even though my issue was not the one listed here, as the DP card did not cause my laptop to freeze or shutdown. However, the DP card also stopped responding correctly. I figured I’d rollback to the “original” FW but the software just bricked the card instead. Now the card is not visible to the OS and so I can’t apply either FW update. Oh well, HDMI it is then!!
On the HDMI Expansion Card version of this, we are still working through it. One thing to note is that these Expansion Card firmwares are ultimately a bit of a hack to work around bad behavior on the retimers in the laptop. We have firmware work currently in progress to force the retimers to behave better, which reduces the need for changes on the Expansion Card end.
I’ve experienced the same issue as James_Adams with the DP expansion card myself. More often then not it would not be recognized and once it does it disappears as soon as a cable is being inserted.
I still don’t know what scenario will cause it to spuriously detect the card but sometimes it does. Once this was the case I checked the firmware using the above tools and it seems I was on a even older firmware: 22.214.171.124. So first I tried the “stock” 126.96.36.199 firmware which flashed fine but this did not seem to help the problem.
Currently awaiting the magic to happen for the DP adapter to be detected before I can try 188.8.131.52…
Apart from the power draw, searching the support pages indicated more people experience this issue. Is the plan for this to be resolved with the new firmware as well?
(for what it’s worth I’m on a 11th gen i5 mainboard on windows 10)
Managed to get it re-connected and showing as USB device in windows. Flashed with the 184.108.40.206 twice and now at least windows seems to be recognizing the expansion card more frequently. Unfortunately I still get a disconnect in windows when connecting the displayport cable (DP1.4 ) for my monitor to the expansion card. Cable is brand new so I don’t expect that to be the problem.
Just a couple of observations/questions on the final guide:
The guide currently seems to suggest that the expansion card needs to be plugged into a Framework Laptop for the firmware upgrading to work. I have just tested this process using a desktop computer with TB4 ports, and the process worked just fine.
In a related vein, do we need to sign up separately for guide accounts, or am I encountering some sort of login error?
I have not found a similar thread for the HDMI card firmware update, sorry for using this thread:
Once you have the new hardware revision of the HDMI cards ready will there be a clear indication in the shop about the card being “v2”?
When buying HDMI cards used (in the future), is there an easy way to figure out if you’re buying the old or the new fixed version? Maybe you could print like a “V2” next to the USB plug so it won’t be visible when plugged in, but you could still tell looking at the card. Or can there be a program that not only detects the installed firmware version but also tells you if it’s the old or the new hardware?
In the HDMI Rework Guide I can only find a download link to the new beta firmware (220.127.116.11) but no download link to the original firmware in case there’s a need to downgrade. Will that be provided as well, or do the HDMI cards not support downgrading?