I feel like a ton of this chain issue can be solved with coreboot support tbh. Hopefully, AMD OpenSIL will make this process easier.
4 Likes
Appreciate the feedback, but I wanted to make sure you understood why this wasnât a focus at this time.
6 Likes
@nrp First of all, I (and probably a lot of others in this thread) appreciate the response.
I like the two weeks planned schedule, even though I still have some doubts coming from this first upgrade. But if 3.07 is in the pipeline, I guess there will be a chance to regain some trust.
On the goal of shipping a Windows & Linux release at the same time, personally I would also be fine releasing the upgrade before it can be installed in a convenient way. If I know I can trust the stability of the software, I am fine with taking the hard route (even if it would mean installing Windows). Especially as this is not a chore I will have to do often.
So maybe remove the beta label and state the current work on the installation procedure ? If you are worried about the risk of having a bad USB disks being used for installation, also communicate that. It would still make it easier to judge for users whether they want to upgrade
5 Likes
@p_e Thanks for the feedback. And we do appreciate everyoneâs perspective. We have an already in motion plan of action, so weâll be going forward with it.
14 Likes
I use my framework 13 with a AORUS RTX 3080 GAMING BOX. According to egpu.io, the eGPU has two JHL6340 Thunderbolt Controllers. The primary controller is for hosting the eGPU, and the secondary controller is for hosting the expansion ports.
With bios 3.06 on my laptop (i7-1280p), the ethernet port on the eGPU doesnât work, and the USB ports on the eGPU have some serious lagging issues with a mouse.
I then tested the eGPU on my friendâs framework laptop (i5-1240p) with the original bios. Everything is fine on her laptop. I suspect there are some compatibility issues for bios 3.06 that cause the secondary controller to be unstable.
1 Like
Lets do some guessingâŚ
3.19 beta for 11th gen + 15 DAYS = 15th september 11th gen release
If no problem with the beta it supposed to go to 12th genâŚ
So maybe we get it in October on 12th gen
1 Like
Out of beta for 11th gen. UEFI 11th âcoming soonâ.
They are supposed then to release the 12th gen BIOS.
2 Likes
The amount of whiteknighting in here for FW is quite embarrassing.
If the team is spread too thin to even provide one round of support for their products, then maybe donât introduce 3 more SKUs since?
They have no hope in the future if they get the reputation of dropping their products immediately after introduction.
5 Likes
The release of BIOS updates requires collaboration with our outside development partner, and those resources are shared across a number of projects. I can tell you that both 11th and 12th Gen Intel Core BIOS updates are a priority, and as @Matt_Hartley stated, weâve exited Beta for 11th Gen Intel Core for 3.19, and 12th Gen Intel Core is in the mix. This is all extremely challenging given our small team and competing priorities. While we do admit and own that these delayed releases have been a poor experience, weâve been transparent and are sharing status the moment we know where itâs at. Letâs try to be a little more constructive in how we communicate frustration please. We do read these, as do our engineers that are putting in tremendous effort across a number of products, and time zones.
Thank you.
12 Likes
@TheTwistgibber
I think one of the key issues that has contributed to some peopleâs frustration regarding bios updates has been the radio silence at times. I do definitely understand Framework is a small company with about 40 employees and that resources are shared across numerous different things as of late (e.g. AMD Framework 13 and Framework 16). The easiest compare/contrast is the delay surrounding the AMD Framework 13.
While I was disappointed that it wouldnât be ready before school started, the 3/4 emails that Iâve since August have been really helpful in allowing me to understand what were some issues and the plan going forward. And straight from the email âdelayed hardware is eventually good, but rushed hardware is forever badâ. I think this really applies to this situation. No one wants a buggy, rushed bios update and Iâm all for Frameworkâs team taking their time to work out any issues. I think whatâs important is some type of regular communication so that people understand that their issues are being heard and that thereâs a plan to address them. Iâm not asking for something like those emails to be replicate but it would be nice if the team could put out a short post every month or quarter outline some issues with bioses and things in the work. (This was mentioned back in May by Ghostlegion).
The last post specifically about the 12th gen bios update was from June mentioning that release validation was ongoing and itâs been silence until a couple weeks when the new changes regarding staffing and the plan on bios updates. Some people have reported issues with the 3.06 beta back in January/February and itâs been 8-9 months for them with no fix yet. Iâve had no issues with the update so I donât mind wait but for those that having, constantly waiting while seeing Framework announce new products must have made them feel like they were being abandoned.
Overall, Iâm cautiously optimistic that things will get better but I genuinely do hope that communication does improve going forward.
7 Likes
@Matt_Hartley I have been running bios 3.06 since beta launch and was having to reset/plug-in the HDMI module everytime I needed to use it, however after getting the version three of the module I am no longer seeing the issue. Not sure if you guys have seen something similar but might be worth having more validation than just me.
I am daily driving Pop_OS 22.04.
1 Like
Well we are about a month on from the last update any news regarding another beta or stable update for 12th gen UEFI?
2 Likes
Thank you, I also wanted to ask but was too afraid of the reaction.
Unfortunately no. Most likely the entire team has been bogged down by the AMD release but something is still in the pipelines.
I am personally not surprised by yet another unfulfilled commitment. From Frameworkâs point of view it would probably be best to admit that they will never be able to support the 12th gen properly. This will manage all our expectations and probably free up some time for them to do better with their other platforms. My trust in their products, however, has been severely shaken by this basically complete lack of support. Reminds me a bit about support I receive for the stuff I buy on Aliexpress 
.
2 Likes
wasnt there a mod/firmware update for older modules? https://dozuki-prod-us-east-1-guide-pdfs.s3.amazonaws.com/pdf/framework/guide_193_en_814.pdf
easy to write stuff, difficult to actually programm and test proper firmware. Talk is cheap, actual work⌠I feel more updates might be cool, but also understand if they have lots of resources put into the new products they are about to release in full.
A new update on the current status would be great altho i suspect not much for us has happend (maybe more tests and sad results or issues popped up, all these embedded IC with their own firmware. windows, LinuxâŚ)
Programming and testing, much like everything else, is a matter of allocating resources. While FW might be a small firm itâs not exactly a one man operation so I am not really buying the whole âthey can only do one thing at the timeâ argument. I am of the opinion that they are doing a poor job at managing the resources they have. Instead of launching several products this year they could have instead allocated some of the resources they have towards maintaining the products they already sold. This would have made people like me appreciate their products more and perhaps not look to changing their device after one year of use. This approach they are heaving towards product support seems to literally encourage people to buy a new device every year and goes against the whole environmentally friendly thing they seem to claim they are solving. Using devices longer is perhaps the most efficient way of reducing the carbon footprint in the first place.
2 Likes
after 2 years (release), my phone rarely got any updates, after 5, they consider it old. FW said they work on it, when⌠thats what we dont know (yet). why impatient? cause big firm can release updates more often? other product lines get more updates? some of this is answered already. Is your FW actively being attacked due to security issues?
Yeah, big firm can release updates more often.
Your phone rarely got any updates after two years. So I assume it got some updates during the first two years, and it still have a few updates after that.
But we got zero updates from framework. The beta doesnât count. They said they are supporting Thunderbolt 4 officially on 12th gen last year, and all we got is this half-baked beta and very little communication. Timeline? Roadmap? Zero. The promised âplanâ doesnât count because they didnât follow up on that.
âIs your FW actively being attacked due to security issues?â
The way to deal with security issues is to solve them with updates before they are actively exploited. I believe changing device after just one year of use due to valid security concerns is a valid tactic.
Someone else said they also wanted to ask but was too afraid of the reaction. How ironic that Framework has made their customers afraid of talking about valid security concerns and asking for (progress) updates politely.
7 Likes