If I open my laptop within 24hrs then it is already ready by the time I finish opening the lid. This immediacy means I don’t lose my train of thought (ie; the reason I grabbed my laptop in the first place).
I’m a hard Linux lover, and begrudgingly use a MacBook, but sleep has a lot of value, and the Mac stuff seems to work a lot more consistently than what windows is offering. (Linux too, in a number of circumstances: though my old precision 5520 never had an issue with suspend)
Okay, I'll bite. Care to expand? What behavior, and why is it bad? Why should users not expect a "suspend" state to work (more or less) as advertised?
edit: Or are you arguing that the only "correct" states are running and complete shutdown? Why would that be preferred?
This is all described towards the end of the video, for those who don't want to watch the whole ~11 minute thing.
It's a real crapshoot whether the dock will properly or fully connect upon cold startup or reboot. Sometimes everything is dead. Sometimes the monitors get signal but Ethernet and the mouse are down. Sometimes only the mouse is down; very occasionally, only Ethernet is down.
About a year ago, I spent multiple hours on the phone in a looong call with a CalDigit support rep. Essentially, we used my system to troubleshoot. We never solved the problem.
With time and observation, I've learned it's best to cold boot (with power connected, my daily work configuration) with this CalDigit Thunderbolt dock physically disconnected. After Windows has booted and gotten to its desktop, I then wait 90 - 100 seconds or a bit longer before I plug in the dock. Doing this, my success at having everything come up working is 50% or even a bit more.
If dock isn't fully functional, repeated warm rebooting is not too likely to correct this. The best bet is to hard shutdown, maybe wait a bit for whatever capacitors to discharge, and then start the above procedure over.
The CalDigit rep thought it was maybe the Thunderbolt support/configuration in my X1C6 that was/is to blame, but I have since formed the impression that Thunderbolt, for all its vaunted power, is actually kind of a shitshow.
The X1C6 did initially have a problem: It rewrote its Thunderbolt configuration upon every boot, into a kind of physically memory not designed to have a lifespan of that many writes. About a year, as I understand it, was what it took for many users to start having problems. Lenovo did eventually ship a firmware update to stop this behavior, and through circumstances I'll skip I ended up de facto avoiding the problem. My point in mentioning this being, maybe the X1C6's Thunderbolt support is still/also borked in some manner that causes my problem with the CalDigit dock.
But, I'm not too convinced of this. And I suspect CalDigit is using the same chipset that many other brands are using for similar docks.
For all the premium they charge for it, Thunderbolt designers/implementors should... be induced to provide a better result. IMHO.
Heh, that's such a Lenovo problem. I hard bricked my old ThinkPad W520 four times (and got warranty replacements) just by hitting F12 to bring up the BIOS boot menu. It did some sort of write that wore out the BIOS flash chip. I don't think they ever fixed that problem.
I hadn't heard of this problem, so thanks for the heads up! I'll be very planful and sparing in my BIOS config access/writes.
I think CoreBoot has made it to some if not all of the -20 series. I wonder whether it would make any difference, although I can't see how if you're still writing to that storage.
The speed and reliability with which a Mac sleeps and wakes and how well it maintains battery is insanely good. My Windows laptop was more like a portable desktop, as I always had to plug it in and would walk around with the lid open rather than risk a sleep/wake attempt between meetings.
Also I have had this issue with Macbook Pro 15 (2019), so it can't be guaranteed every-time for any OS I guess; not sure of the reason though. To me closing the lid should take preference over everything.
My previous, older Mac wouldn't sleep at all for more than a few seconds unless I unplugged the external monitor.
The "modern standby" feature on macs is called power nap: https://support.apple.com/en-ie/guide/mac-help/mh40773/mac
It already has different behavior depending on whether it's on battery or mains.
You can turn it off but it's not the option that Linus mentioned. It's elsewhere: https://support.apple.com/en-ie/guide/mac-help/mh40774/mac
On Apple Silicon Macs, the machine is never going into that deep a sleep to wake up from (it's basically a huge iPhone, remember?) and Wake for network access is not for Wake on LAN but rather if you want it to keep WiFi running to get push notifications etc while in "sleep" (the description under it in Settings even says it's for iMessage and iCloud updates).
Marcan has talked about Apple Silicon sleep states wrt to implementing it in Asahi Linux and IIRC they never put the machine to sleep, they just stop all the processes and hardware like the display and let the CPU idle normally (which it's extremely efficient at)
The solution to this is to install noclamshell via brew or just get in the habit of disconnecting your mac first before closing the lid.
I noticed this because previously it was sleeping completly fine and the problems started only recently which is inline then I started using the dock.
shutdown /s /f /t 0
Stop-Computer -ForceFor myself, I prefer not to force application closures. If something's stuck, I'd rather look into it and avoid potential data loss. I'm seldom in that much of a hurry, these days (but I understand others can be).
For anyone who's curious:
shutdown:
https://learn.microsoft.com/en-us/windows-server/administrat...
Stop-Computer:
https://learn.microsoft.com/en-us/powershell/module/microsof...
Someone in Microsoft has a KPI related to the percentage of machines updated with the latest patches every month.
He or she can best meet their KPIs at the low, low cost of the occasional destroyed laptop, fire, or -- very rare -- customer death.
People just have to accept the risk of burning to death so that this person can meet their KPIs by forcefully updating laptops even if they're hibernating, in a laptop bag, and in the cargo hold of an airliner.
Those passengers knew what they were signing up for when they boarded that plane together with a Windows user.
The good thing is, once a fix for this is pushed, even laptops in cargo holds will get it. Win win!
With millions of users it's less likely to be rare. As tragic as it sounds, Microsoft likely won't brought to heel until it too experiences a Boeing 737MAX-type incident of its own making.
Such is the arrogance of those who run Microsoft.
"PS: one would hope that this bad unsafe design would already be under investigation by various safety regulators/authorities. Perhaps this story may awaken them."
Save to to swap and hibernate (turn all the way off) on lid close.
It's like 8 seconds longer to boot back up - but It uses no battery and produces no heat.
Crazy how fast machines boot these days. I'm low 30s and still vividly remember the days of waiting 3 to 5 minutes for a machine to come up. Those days are gone - The value proposition of sleep is just really, really low right now.
Generally speaking - I'd rather have the extra 10% battery life per day over saving 15 seconds basically always - even when sleep works perfectly.
I can leave a machine for 5 to 10 days, and it comes right back up at the same battery I left it. A machine in sleep will be completely dead.
There was one really obscure docking station problem which was the real last straw.
I think it was a Dell which updated itself while docked.
After that update, the laptop would not work undocked.
Reinstalling was of no use as every update would reinstall the same problem.
Moved to Intel MacBooks and Bootcamp. I don't remember when I last needed anything Windows specific.
I don't run around enough to care about quick/instant startup. Despite using the Windows 10 Windows menu Power command to "Shut down" my Thinkpad X1C6, I took it out of its bag the following day, on a few not too infrequent occasions, to find it warm and "doing stuff" (Windows Update sticks in my mind). Moreso than a lowered charge, the idea of it cooking itself inside its padded sleeve and bag caused me concern.
After a bit of investigation, I settled on training myself to always open/use a command window to issue "shutdown /s".
No more warm or hot, drained laptop since then.
I agree with Linus: Microsoft's behavior and indifference WRT this problem is reprehensible. For me, it is another example of how Microsoft has not -- fundamentally -- changed since its E3 days. The 900 pound gorilla that we will, per force, accommodate. Amazing how entrenched such cultural mindsets are.
By the way, the X1C6 as configured by Lenovo does not support S3. Since Linus, in his demo of a possible BIOS configuration change, was using a Thinkpad, maybe I'll get lucky with that option -- watch the video to see whether you might have such a fix for your system.