Using an eGPU in an enclosure was the conclusion/solution they came to, to circumvent the power issue:
I didn’t know about this. (Never had an enclosure)
From skimming over it, it seems more like negligence, rather than actively trying to prevent that use case, though i guess that could also have been on purpose.
I assumed the GPU could not “see” what kind of PCIe slot it sits in, but of course the enclosure also needs some sort of controller, firmware and drivers which would be visible to nvidia, so I stand corrected. They could prevent their GPUs to be used in enclosures with laptops, although I don’t understand why they would do that.
But who knows what anti-consumer tactics they come up with next, and why
It more like the prevention of another use case also impacted egpu use. Error 43 was afaik to prevent consumer cards from being used in virtualization to not cannibalize the virtualization card sales. However it was still a deliberate choice not to fix it for so long.
Gotta buy the 5090 egpu edition, only performs 50% worse and costs 3 times as much XD. A little less joking, egpus could potentially eat into the very high margin mobile gpu busyness (they aren’t really now cause egpus are extremely nice but they could if they became too convenient).
That’s another reviewer disappointed with the keyboard. I am curious how bad is it compared to Framework 13. Hopefully someone in Batch 1 can compare the two once they receive theirs.
My guess would be, that the midplate plays a big role in the feel of the keyboard (as Alex also says in LTT’s video). So some variations in review units could lead to some of the outlets comlplaining about the keyboard, while others don’t.
If LTT’s fix with the thermal pads really works that well, early Batches could do the same and Framework could implement a little less janky solution long term (and offer the fix for free for the early units)
In fairness, I have friends with gaming laptops and under load they are also loud. I think this is fairly par for the course. I’ll withhold judgement on the fans until I get my hands on my own, but for me this is not a deal breaker.
“There’s no dedicated headphone jack on the Framework Laptop 16, so you’ll need to take up one of your ports with an Audio card if you want one.”
That surprised me, because when I was ordering my FW16 I read the following text on the “details” for the audio expansion card:
The Audio Expansion Card contains a 3.5mm headphone jack, which supports audio input and output. This Expansion Card provides increased dynamic range and improved signal to noise ratio in comparison to the Framework Laptop 13 built-in audio jack.
Now that I’m looking for it, I see the “13” hiding in there, but the first time I read this I didn’t see that and thought that audio was built in. I guess I’m going to have to email support and add the audio module to my order, since I definitely use the wired jack for zoom meetings & etc.
Maybe @Framework could update the audio expansion module text on the FW16 order page to make it more obvious that the “built-in audio jack” is not present in the FW16?
Thanks for your feedback. Do you feel like it is hard to understand that Framework Laptop 16 does not have a built-in audio jack from that description or you missed it when you read it for the first time? It looks clear to me but I would be happy to inform the internal teams if people think it is confusing.
Was very clear to me, and I personally prefer not having a built-in jack. Any port that is difficult to replace would be a problem for me. I would however like something like a USB-C | 3.5mm expansion card.
Sorry for getting off-topic, but for anyone else who uses Firefox, there is an indispensable addon by firefox itself which translates pages on your system instead of sending the data to google/cloud services. It isn’t as accurate as Google etc, but good enough for most cases.
while you’re reading this !
