@jon I’m running with a SN850 and have no problem waking my machine from sleep apart from it taking longer than it seems like it should.
Thanks Ron. Good to know - I also can confirm a couple tests today (since I posted earlier here) show I can wake from sleep due to inactivity. (and +1 that it takes a strangely long time… O(10)sec… maybe 30 seconds on last success?)
I’ll report back if lid-close’s sleep suddenly start waking without issues.
I’ll report back if lid-close’s sleep suddenly start waking without issues.
Okay this actually just happened. New hypothesis: it might have to do with being plugged into a usbc doc (external display → usbc hub → laptop) at time of sleep. This is the first time I’ve closed the lid away from my desk/hub, so hadn’t made the distinction. I’ll report back how testing with the dock goes.
1 Like
The long sleep resumes seem to be with enabling mem_sleep_default=deep. Usually it’s around 10 seconds for me.
Running Manjaro KDE + the 850 ssd. I’m using the thunderbolt port of my external monitor to drive power + display + USB devices without an issue.
My only issue is SDDM/KDE related where if I yank the monitor out while the device is asleep the login manager crashes and the virtual terminals don’t always connect. So now I’m paranoid about unplugging before locking.
1 Like
On my Manjaro also with the 850 I have constant wake from sleep issues. Some times it works somtimes it doesn’t. Sometimes it wakes with the touchpad way more sensitive. Sometimes it wakes to a black screen with a blinking cursor. Sometimes when it wakes it tries to shutdown and then says “cannot find shutdown binary”.
I’ve had nothing but issues with sleep and waking and using it in clamshell with a tb4 dock.
2 Likes
Just as an example I’ve been using the laptop all day today and it has awoken just fine all day. But now however, I go to use the computer and it’s not waking up. Just has a black screen and doesn’t respond at all. All I can do is hold the power button down until it turns off and force a reboot.
2 Likes
@nomb85 I’ve had issues with the touchpad not initializing if I try to provide input before the wake cycle is complete and I get a splash screen. I also had issues with shutdown previously, but they went away when I switched drives and enabled deep sleep.
I’ve always had deep sleep enabled even though it makes it so much longer to wake and i’m using the 850 that came with it so not a cheap drive or anything I’m sure they tested this.
I left Linux on laptop 10 years ago exactly because I was fed up with sleep/awake issues. Just placed an order on Framework DIY two days ago, but reading this thread gives me PTSD 
1 Like
Hmm. I have the same wakeup issues on (non-Linux) OpenBSD, which has a completely different driver codebase for all types of “hard drives” - and my FW also boots off a WD Black SN850 (bought locally). Several previous laptops over the last decade or so have done sleep/awake nicely on this OS. At least one other person with the same OS release does not have such issues, so it’s looking like either one batch of the 850’s have a defect, or, the @Framework BIOS has an issue with these drives. Team: any thoughts?
FWIW, mine identifies as model WDS100T1X0E-00AF. Others with SN850 including @jon @Anil_Kulkarni @nomb85 or anyone else with an 850 and non-Windows OS , please reply with your full exact model number and whether suspend/resume works perfectly (i.e. every time) or not? This may help narrow the problem down. Thanks!
1 Like
@BesselFunct The touchpad not initializing has been a commonly reported issue, and disabling PS/2 emulation in the BIOS seems to be the workaround.
My worse issues have been on Manjaro. I should note that I do not have any wake issues on Windows. This issue actually made me install Windows again on my main drive and move Linux over to the 1TB USB.
I seem to only have the issues on Linux. If it is drive related that it has to be an issue in the Linux kernel.
I have worse issues plugged into a dock. The worse is when it decides to just crash on wake.
Yep while this might be better for battery drainage during sleep, it does create a longer wake time.
I’ll have to wait until I reboot again out of Windows but on Windows it identifies as: WDS200T1X0E-00AF
Full one: WDS200T1X0E-00AFY0613200WD
WDS200T1X0E-00AFY0
Running Pop!_OS, so far so good, no wake from sleep issues that I have run into. Fingers crossed.
1 Like
I remember a discussion somewhere where Linux does not play nicely with NVMe drives and sleep on some older newer systems (huh)?
Like, yes. If you have a old SATA m.2 drive lying around, try that one out. Or try running everything in “legacy mode” (a.k.a. BIOS mode instead of UEFI mode).
My last brief experiences with linux tell me that they tend to go pretty well with old protocols.
But I don’t think it’s entirely Linux or Framework’s fault. The “modern sleep” (S0 low power or whatever) is complete madness.
Like look at this. Yes, it’s on windows, but it’s not less messy for linux.
The following sleep states are available on this system:
Standby (S3)
Hibernate
Hybrid Sleep
The following sleep states are not available on this system:
Standby (S1)
The system firmware does not support this standby state.
Standby (S2)
The system firmware does not support this standby state.
Standby (S0 Low Power Idle)
The system firmware does not support this standby state.
Fast Startup
This action is disabled in the current system policy.
It’s not as if (S0 to S2 is “not supported”). It is because the system uses “hybrid sleep” which, when enabled, disables S0 to S2. However, if I remember correctly that S0 low power (as well as a thing called “S0 connected standby”, which is apparently two different things) is supposedly the new “hybrid sleep” thing.
So until it does some more janky things (like waking up because i closed the lid before i let the system sit with the lid open for 5 minute), I am going to pretend this problem did not exist. Or that nothing can fix it.
And during the brief period I tried Linux on the different machines, only the old legacy core 2 duo system (with full legacy BIOS and SATA drive) played “nicely”, but will shutdown instead of sleep (?) on seemingly random occasions (?). “Linux Sleep” on the Thinkpad does not help either.
3 Likes
Throwing my own experience at this. I’m running Manjaro, but not with the WD-Black drive, but a Samsung 980 1TB NVME drive. This is a drive I have used previously with a Lenovo T14 drive.
My issues also generally stem from sleeping the machine while it is connected to a thunderbolt dock. I’ll try to avoid that for the next few days to see if that helps the issue or not. Judging from my previous experience with the T14, it should help significantly.
1 Like
Same here. On Linux I was seeing about a 5 second delay when resuming from s2idle deep sleep. Totally acceptable for me. No issues resuming on Windows, to include hibernation.
Thanks to everyone looking into this issue. It’s the “last mile” to making this wonderful machine my primary workhorse.
I’m running the latest Pop!_OS beta (21.10) with kernel 5.15 and I’m unable to restore after closing the lid. When I open the lid, the power button’s light is on and the screen remains black for more than a minute. I’ve tried several times and it is consistently unable to awake. (I have to hold down the power button for 10+ seconds to turn off).
$ uname -r
5.15.0-76051500-generic
$ cat /sys/block/nvme0n1/device/model
WDS100T3X0C-00SJG0
$ cat /sys/block/nvme0n1/device/firmware_rev
111130WD
1 Like
@Ian_Darwin I just got my framework laptop from late batch 4 and I’m also facing resume issues on OpenBSD. It consistently fails for me with both hibernate and suspend. The disk I’m using is Samsung 960 EVO 500GB Solid State Drive (MZ-V6E500BW) m.2 NVMe.
To add another datapoint, I got my Framework yesterday and installed Debian sid on there. Both suspend and hibernate (including hibernate overnight) resume fine. I also just tried deep sleep and resume and, other than realizing I had to disable PS/2 emulation mode, it seems to work just fine (although I haven’t yet tried a resume from deep sleep after, say, an hour).
1 Like