This is verifiable in manufactures data sheets.
Efficiency at less than 20% and greater than 80% loads isn’t great relative to in between those ends.
This is compounded by lower wattage PSUs being more limited with regard to features and benefits.
If you end up with a 650w PSU and your system idles at 80 watts for the bulk of a working day you spend long periods of time in this less efficient window.
We need to see some quality 300w to 600w designs come back onto the market.
From Chinese parts
That’s what anti islanding is.
Prevents power from going into the grid when it’s down.
Way I read it is it puts surplus into the grid to keep you elec bills down.
800 watts isn’t exactly going to set an outlet on fire.
2 is fine.
I know where you’re coming from, I use a closed notebook with external display sometimes.
I might need to be more specific. If the notebook is used as a typical notebook, and one closes it with the intent of putting it to sleep, once sleep has been reached an external mouse should not wake it.
However if you do toggle the power settings to allow the machine to function with the lid closed and/or machine docked then you do want to mouse to wake it keep awake the machine.
This used to be so much easier back in win 95,98,xp days.
There was a startup folder in the start menu and all you needed to do was drag what you wanted into it.
This is an example of something that got harder.
Had this issue for years over 2 machines.
One had some shit in the background the prevented standby.
Other was so simple it pissed me off… … the damn mouse jostling around in the laptop bag was walking it up.
I’m still going to point the finger at windows because 1) there should be a better tool for identifying what is keeping a system awake and 2) should be default for a mouse to not wake a portable machine who’s lid is shut.
The most simple answer.
Ads or commercials are typically an interruption to the content I was wishing to watch.
If it has anti islanding at least it’s unlikely to be a shock hazard.
That said are there any other concerns I’m missing?
Claims to describe the claimed issues with the framework display but instead literally outlines the issues with the chosen OS instead.
Like… fine, be annoyed, but at least be honest. The framework display has no faults.
Linux had issues with DPI.
It’s still an issue, still legit, not it’s not a faulty display.
Is nice, but 2GB less RAM and missing OIS that the previous model has.
About damn time.
Trying to find your way around an unfamiliar system where everything started with K was enough to put me off desktop Linux.
On liftoff here and spoiler tags not working.
All of this skills the point. This is a second drive that failed, it was the replacement for an earlier drive that failed.
That’s what the article is all about.
A high, unexpected and unreasonable failure rate.
My pending or existing projects.
A software defined radio server. Lives up top of an antenna mast running off PoE with an RTL tuner connected.
ADSB receiver, similar to above, but on a fixed frequency.
The above 2 could be virtualised in theory, but there is an advantage in having the cable to the antenna short and thus the sbcs live up antenna masts in an enclosure.
MMDVM hotspot for ham radio (this might not count as it HAS TO use the gpio pins on the pi, this can’t be visualised even with a USB port passed through.
As an audio server that would bitstream 24bit/96kHz to an amp.
Even then you’d still want 100% with encoding running at a lower priority.