i am using the hdplex with cpu @176w max tdp. no issuses !
ps: I measured the power consumption at the wall socket with a multimeter, even running FurMark, CPU Burner, and even DiskMark. The maximum power draw was 268w at the wall socket, and that only lasted for a few seconds. No problems at all! The HDPlex 250W handles peak loads very well.
btw… Power consumption in idle mode has dropped from 20W to 15W! The HDPlex is also very efficient!
That say I have a simple MB (128Gb of RAM) with 1 ssd (4To Samsung 990Pro…) did not see more than 230W at the socket when max power (160W for a few sec..) (using sudo tuned-adm profile hpc-compute) (and it was with a old “80 PLUS Gold” …)
If you do not use other elements it may be good for the 250W DC-HDPLEX with max power…
@Matt_Hartley Is there any news on this issue?
To be honest, I find it incomprehensible that customers are left alone with such an annoying bug for three months.
At present, I would describe Linux support for the Framework desktop as poor.
I also find communication on this issue on GitHub to be poor or non-existent.
I have reason to believe (which I do not think I am at liberty to elaborate on) that the 15W and long boot issues will be addressed and resolved in the next update, and it should be forthcoming relatively shortly.
As “aLostEngineer” said … on GitHub it is asked for Beta tester and you got no response when you offer to test. The release should be after Chinese new year … and nothing … that is disappointing …
I can imagine that something can take a long time to solve or is difficult to solve, but the communication around these BIOS issues has been very poor. I would have be nice that have had communicated that they are beta testing, but the issue has not been solved and that they are working on it. Or something like that, It has been nearly 3 months now.
I can assure you: this is not specifically related to the Desktop product. The BIOS on the FW 16 has serious issues, related to the same USB-PD, and here as well communication and progress is basically zero.
Still the communication was very minimal for such an issue. I luckily did not upgrade to the 3.04 version, but for people who have it is a very annoying issue to have your boot time increase. Let’s hope we have a fix soon.