On Fri, Jul 3, 2015 at 11:58 AM, Theo de Raadt <dera...@cvs.openbsd.org> wrote: >> FWIW, I just tried shutting the lid on this netbook, to see what would >> happen. >> >> Disks went quiet quickly enough to assume it was sleep and not hibernate. >> >> I waited maybe a minute, then opened the lid. No response. On keyboard >> activity, i could hear the disks spin up.
Tried it again, and lifting the lid spun the disks up. >> Tried ssh from outside, but I had disabled password access and hadn't >> copied the relevant tokens to the other box. Did get a Permission >> denied (publickey, keyboard-interactive) response once, but a few >> minutes later, there was no route to host. I woud guess it went back >> to sleep and wouldn't wake up, except this time the disks did not go >> quiet. >> >> Ended up with a long press on the power button. After that, a short press on the power button started the power-down sequence properly, so there was no need of fsck on the next boot. If one refrains from trying too many things in the dark, it looks like one can avoid losing control, so it's just a matter of figuring out what gets the screen fired back up. > Congratulations. > > You have a laptop that suspend/resume does not work on. It needs > to be fixed. I'll try to find the threads and dig in, but I'd kind of like to focus on WIFI and dual-boot with GPT-only MSWindows for this beast first. Lots of unsupported fun on it. Hopefully, I'll be able to make some time for something useful next week. (I'd almost say that when I bought this box about a month and a half ago, I should have gone for an older box, but I need the motivation to dig in. :) -- Joel Rees
