I'm in the process of getting my Home Assistant environment up and running, and decided to run a test: it turns out that my gaming PC (custom 5800X3D/7900XTX build) uses more power just sitting idle, than both of my storage freezers combined.
Background: In addition to some other things, I bought two "Eightree" brand Zigbee-compatible plugs to see how they fare. One is monitoring the power usage of both freezers on a power strip (don't worry, it's a heavy duty strip meant for this), and the other is measuring the usage of my entire desktop setup (including monitors and the HA server itself, a Lenovo M710q).
After monitoring these for a couple days, I decided that I will shut off my PC unless I'm actively using it. It's not a server, but it does have WOL capability, so if I absolutely need to get into it remotely, it won't be an issue.
Pretty fascinating stuff, and now my wife is completely on board as well; she wants to put a plug on her iMac to see what it draws, as she uses it to hold her cross-stitch files and other things.
how do you deal with kb+trackpad not working after wake?
Depends on the driver. Usually for finicky ones you can do an rmmod at suspend and a modprobe on resume. What distro, and are you using the default suspend mechanism?
yes, i'm on ubuntu, using all the default drivers.
and i would guess its finnicky because its an old laptop.
is it a matter of scripting rmmod and modprobe to run on suspend/wake?
There are a couple of ways:
Or
I usually do 2 because I like the hotkey method for desktops, and it keeps things the same for both. Also allows me to close a lid on a laptop and leave it on. But 1 is more "formal".
Happy to share some scripts if you'd like, on my phone now, though.
how do i do 1? having timeout to suspend and lid close to suspend would be great. and id like to see some example scripts!
i had pretty much given up on standby with this one.
Will grab some when I back, but assuming you are using
systemd, it's easy if you follow this old but good method: https://blog.christophersmart.com/2016/05/11/running-scripts-before-and-after-suspend-with-systemd/If that doesn't work out of the box, it's likely because you're hitting S1 instead of S3, but give that test script a shot and let me know how it goes!
what kind of driver could the keyboard be using? lsmod shows nothing beyond the HID driver, but thats being used by the external mouse which works normally after sleep.
lshw shows it going by /dev/input/event6 or something like it?
Could be internal to kernel? Try updating
/etc/default/grubto include:GRUB_CMDLINE_LINUX_DEFAULT="quiet splash atkbd.reset"and runsudo update-grub. This will cause a full keyboard reset on resume.If you have not run BIOS updates, that could be it, too.
ok it worked! thanks a lot! can't believe it was that easy. Gnome spazzes out a little bit after wake sometimes, is that something i can work around?
do you happen to know a thing or two about diagnosing trackpad issues? or at least the right direction? 😂
Glad that worked out for you 😉 What is Gnome doing exactly?
What kind of issues, and which trackpad driver?
i was about to send a screenshot, but i can't reproduce it now. it freezes and stops responding to some or all input, and all the dock+appmenu icons are gone. its one of these or all symptoms, and i can usually reproduce it when coming back from sleep. logs say 'broken pipe, error reading events from display' i can update if it happens again.
I'm using the same generic ps2 driver for the touchpad. its an old alps glidepoint, i can get it to work perfectly with all features on windows 7 with the proper drivers, needless to say thats a bit unworkable.
on linux it works initially with multitouch scroll and everything, then gradually starts to behave like a wet touchscreen. ive tried different kernel versions, livebooted a couple different distros and tried a few very old solutions i found floating around, like using the synaptics driver for some reason. found it for cheap and replaced the hardware. nothing seems to do the trick.
edit: it did the thing, its usually functional enough for screenshots:
Is this a Thinkpad? And of so, is the BIOS s3 on "Linux" or "Windows and Linux"?
Also are you running Wayland? If so ot might be worth trying to log in with Xorg instead (bottom right when logging in).
i will test that out later today, thanks!