Version 3.05 here, release date 08/23/2022 … very new.
I don’t have any thunderbolt equipment. The only thing I’m noticing here is I don’t seem to be getting turbo boost under loads, it maxes out at about 3.3 GHz. Nowhere near the 4.7 GHz maximum possible. That could be heat related though with the climate and building I’m in.
I’m set up to re-paste the CPU with some thermal grizzly kryonaut and check if the performance improves. It will be at least a few more days before I get to re-pasting so I’ll keep an eye on this thread for a while before going ahead. I didn’t realize that I had the 3.05 BIOS till I checked after reading this thread. Edit: Batch 4 (to Australia), arrived 13th October.
So I’m in the 3.05 club as well. Same batch as yetiman_64. Only major problem I’ve had is the crash during sleep/hibernation Windows 11 issue, which seems resolved after applying workarounds.
That’ll teach me to go looking at random threads - would have been blissfully unaware but no, had to go looking for trouble
Although, I am not saying at all that the BIOS v3.05 is causing problems!!
It’s just that I have TB dock problems, and another user with the same laptop and the same dock had not such problems, and as their BIOS was v3.04 I spotted it as a possible root cause to investigate…
Maybe it’s just my mainboard that is faulty! Or an other problem I haven’t imagined at all. I really don’t know.
Completely understandable. I assumed I was on 3.04 as that was what is listed as the current stable BIOS. If I had done my due diligence and double checked I would have realized I was on 3.05 and then that would have been an avenue for additional troubleshooting. While many of the issues on the forums are more likely kernel or driver issues, thunderbolt issues tend to by and large be a firmware issue. Now I am wondering if any of my very minor issues are actually realted to this and not something else. So in short thank you.
My Batch 3 12th Gen also is running 3.05, I wonder if that is why I am having problems with a portable projector over HDMI that works with every other laptop that I have (11th Gen HP from work, and my older 4th Gen laptop).
The silence on the matter is a little telling. @Matt_Hartley since this is going to impact Linux users, any chance of an update regarding LVFS, or at least if it will be available directly as a cab file for local install without having to use a WIndows related workaround?
Hey everyone, it’s been a very busy Monday, so I appreciate everyone’s patience. Looks like this thread was created 14 hours ago, so anytime there is a weekend (PST time) - it will take me bit to catch up to any future Sat and Sunday posts.
When it comes to rolling back BIOS to 3.04, I would ask you to create a support ticket as tracking this would be very helpful. If it came with 3.05 from the factory, then it means it was tested working with this and unless there is a clear reason to change this, I’d keep it there. But if you’re seeing issues relating to the BIOS, please open a ticket so we can better assist.
While we continue to dial in our LVFS support, the above linked guide has a method for Linux users in the near-term.
Now the guide is still marked as 3.04. I expect this to reflect any upcoming changes from the appropriate team.
Which distro, Wayland vs Xorg and have you run xandar to see what the Framework “sees”? I can tell you that each of things can affects the outcome. Additionally, we can have you open a support ticket and gather logs to see what is failing where as well.
I’ve reached out the appropriate members of the team for a deeper understanding on what is happening between 3.04 and 3.05 - 3.05 is shipping on new 12th Gen systems. However, no customer facing updates have been issued as of yet - this is why we still have 3.04 on existing systems.
Based on our internal testing there is no advantage to rolling back to 3.04, it is doable.
@Matt_Hartley
Hi Matt, thank you very much for looking into this!!
I submitted a ticket to Support on my specific problem, which is the one that led me to suspect a BIOS issue.
An other FrameWork user with the same Linux kernel, the same CPU, and the same TB dock, (but with BIOS v3.04), reported that it worked flawlessly (except a minor issue for the power on button).
Moreover I tried a USB key with a live Linux on my previous 11th-gen, and the dock works on it, and with the same live Linux key and the 12th-gen it doesn’t work, so an OS issue is unlikely, which is why I started to think about hardware issues.
I would like to try to downgrade to the BIOS v3.04 to see if it changes anything, but right now there is no file at all to download for BIOS v3.04.
Would it be possible to get such file?
I also asked the same to the Support person in contact with me yesterday, so I am expecting a reply any time soon.
Edit: Got a reply! I’m continuing this with the Support staff by email.
So, I followed the advice from Support and I booted one of the Linux distros the most supported on the FrameWork: Ubuntu 22.04.
I just used dd to copy the official ubuntu-22.04.1-desktop-amd64.iso on a USB stick, booted that, plugged-in my TB dock… and the RGB keyboard connected to it lightened up!! So, it was working!
Then, the real surprise: I rebooted on my normal distro on the SSD (Artix Linux), with the dock still plugged in. And again it worked!
So now the issue is solved, for any purpose of using the laptop with the dock!
However I am quite sure that I had tried before to boot (Artix) with the TB dock plugged-in, so something must have happened, maybe a forced reinstall of some Intel thunderbolt firmware during the Ubuntu boot?
It is also possible (even if doubtful) that I had not tried to boot while the TB plugged-in.
Right now, the TB dock works, but if I unplug and replug it, it doesn’t work anymore.
So, don’t worry anymore folks, I think that the BIOS v3.05 had nothing to do with my issue!
@nadb
Although now I have the same Power Delivery problem as yours.
All the other functions of the dock (i.e. except PD) work, and if I boot while the TB eGPU plugged its PD works, while if both are plugged-in nothing is charging the battery…
It took me some time to get aware that the battery was not charging, literally the time for the battery to discharge while the TB dock was functional!
Edit: Nevermind, it works as intended on Ubuntu 22.04.
The problem above was on Artix. It is on me to solve it as it is a non-officially supported distro.
Let me know if you have any instability with that power delivery. I know mine was working for a while, and then stopped working again a day or two later.
