Is the Framework capable of WOL functionality? I would like to use a VNC connection to operate the Framework laptop from a remote computer but as soon as the Framework laptop shuts off the display, the connection is interrupted. Of course you can’t establish a VNC connection at all if the Framework is blanked.
I suppose I can configure the Framework to not shut off the display but then it would also stay logged in which is not useful.
1 Like
Thanks for correcting me - I didn’t know there was a particular sub-category for wireless.
bump
(and bump bump bump to satisfy the minimum character requirement)
Assuming you are running GNOME…
First of all you need to configure Ubuntu to lock instead of going to sleep when you close the lid. In dconf editor, set org.gnome.settings-daemon.plugins.power.lid-close-ac-action and/or org.gnome.settings-daemon.plugins.power.lid-close-battery-action to “blank”. You may also wish to open the Settings app and under Privacy / Screen change the automatic screen lock display to “Screen Turns Off”, if you want the screen to lock when you close the lid.
Next, you also need to disable suspend on lid close in systemd-logind. In /etc/systemd/logind.conf, add HandleLidSwitch=lock in the [Login] section of the file, then reboot.
Finally you need to install my Allow Locked Remote Desktop extension from extensions.gnome.org so you can connect to via remote desktop even when the screen is locked. Note that this extension works whether you are connecting via VNC or via RDP which is what’s supported in Jammy and Kinetic.
Oh, I forgot to mention, yes, wake on LAN/WLAN works under Ubuntu, at least under Kinetic which is what I’m using and probably earlier releases as well. To use it, you need to set the wake-on-land or wake-on-wlan setting in NetworkManager for the ethernet or WiFi connection you want it to be active on. I have it set to 8 which means only a magic packet will cause it to wake up, and I use the etherwake tool from one of my other machines to send a magic packet when I want it to wake up. If you’re using tlp, you also need to set WLP_DISABLE to N in /etc/tlp.conf, because otherwise TLP will disable both wake-on-lan and wake-on-wlan. However, full disclosure: in my experience it only works sporadically; I’m about to post another community topic asking about that to see if anyone has any suggestions.
Thanks for the reply. I honestly can’t remember the exact details of what I was having problems with but I am sure the answer will come in handy for anybody else running into the issue.