From nobody Sun Nov 13 17:53:00 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4N9KmV03mVz4hml5 for ; Sun, 13 Nov 2022 17:53:14 +0000 (UTC) (envelope-from sr@genyosha.net) Received: from ns4.genyosha.net (ns4.genyosha.net [50.53.250.75]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "float.home.genyosha.net", Issuer "float.home.genyosha.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4N9KmT4KZXz3wkV for ; Sun, 13 Nov 2022 17:53:13 +0000 (UTC) (envelope-from sr@genyosha.net) Authentication-Results: mx1.freebsd.org; none Received: from dragon.home.genyosha.net (ops.genyosha.net [50.53.250.77]) by ns4.genyosha.net (8.16.1/8.16.1) with ESMTPS id 2ADHr5Tp050075 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 13 Nov 2022 09:53:06 -0800 (PST) (envelope-from sr@genyosha.net) Received: from dragon.home.genyosha.net (localhost [127.0.0.1]) by dragon.home.genyosha.net (8.14.7/8.14.7) with ESMTP id 2ADHr0g4003749; Sun, 13 Nov 2022 09:53:00 -0800 Received: (from sr@localhost) by dragon.home.genyosha.net (8.14.7/8.14.7/Submit) id 2ADHr037003748; Sun, 13 Nov 2022 09:53:00 -0800 Date: Sun, 13 Nov 2022 09:53:00 -0800 From: Steve Rikli To: louis.freebsd@xs4all.nl Cc: freebsd-current@FreeBSD.org Subject: Re: DESPARATE: How to stop FreeBSD form sleeping / disable ACPI? (on FreeBSD14 CURRENT) Message-ID: References: <202211130022.2AD0MYiW023709@chez.mckusick.com> <000d01d8f777$42eb10a0$c8c131e0$@xs4all.nl> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <000d01d8f777$42eb10a0$c8c131e0$@xs4all.nl> X-Greylist: inspected by milter-greylist-4.6.4 (ns4.genyosha.net [50.53.250.75]); Sun, 13 Nov 2022 09:53:06 -0800 (PST) for IP:'50.53.250.77' DOMAIN:'ops.genyosha.net' HELO:'dragon.home.genyosha.net' FROM:'sr@genyosha.net' RCPT:'' X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.4 (ns4.genyosha.net [50.53.250.75]); Sun, 13 Nov 2022 09:53:06 -0800 (PST) X-Rspamd-Queue-Id: 4N9KmT4KZXz3wkV X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:20055, ipnet:50.53.0.0/16, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Sun, Nov 13, 2022 at 04:47:40PM +0100, louis.freebsd@xs4all.nl wrote: > I noticed that after disabling gdm in /etc/rc.conf ^"gdm_enable="N"^ the system stays active. > However ..... that is also the end the GUI .... in this case GNOME. > > Since I could not work which a machine hibernating every ^10 minutes^, I have disabled gdm for the moment. > That does not take away that that is ...... ridiculous !! Seems like you aren't alone in that opinion -- there are several threads for multiple OSes about this same topic. Kirk's findings below match my recollection -- this is Gnome default behavior nowdays. In any case, since we obviously can't use the Linux systemD settings to control the behavior in FreeBSD, a few folks mentioned other workarounds with things like dconf; e.g. this suggestion which came originally from the Arch linux folks: https://twitter.com/_neelc/status/1487200568149831681 https://wiki.archlinux.org/title/GDM#GDM_auto-suspend_(GNOME_3.28) Something like: sudo -u gdm dbus-launch gsettings set \ org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing' From the threads, it sounds like part of the problem is this behavior and settings are per-user, so making a system-wide change is hard. Not sure how this workaround will play in your situation. My FreeBSD servers don't run a gui display manager; my Debian laptop runs gdm3 display manager but I switched to Xfce for the window manager around the time Gnome3 came out (too many changes for my taste). Fwiw the Xfce Power Manager has controls for system power save / sleep mode for "On battery" and "Plugged in", including "never". Cheers, sr. > There should be a way to disable ACPI in FreeBSD so that even gdm can not "kill" the machine !! > I say ^kill^ because there is also another bug, the machine is not properly restarting form hibernation, > Even not from S1. > > Louis > > -----Original Message----- > From: Kirk McKusick > Sent: Sunday, November 13, 2022 1:23 AM > To: louis.freebsd@xs4all.nl > Cc: freebsd-current@FreeBSD.org > Subject: Re: DESPARATE: How to stop FreeBSD form sleeping / disable ACPI? (on FreeBSD14 CURRENT) > > > From: > > To: > > Subject: DESPARATE: How to stop FreeBSD form sleeping / disable ACPI? > > (on FreeBSD14 CURRENT) > > Date: Thu, 10 Nov 2022 21:29:21 +0100 > > > > I am still desperately trying to stop FreeBSD from sleeping, but I > > simply do not manage. > > > > It is really very annoying that I have to restart the machine every > > 10 minutes, when I am working via SSH. > > > > So if any one has a solution, it would be very much appreciated! > > > > It should ….. be possible to kill / stop ACPI some how 😊 > > > > If absolutely not possible in the actual build 😊, a cron job > > restarting the timer every 5 minutes perhaps !!??? > > > > It is possible perhaps … that GNOME is initiating this, despite that > > the GUI powersetting is screenblank β€œNEVER”. > > > > Whatever is causing the problem, the settings should be such that ^no > > whatever program^ should not be capable to initiate the sleepmode. > > > > Louis > > If you are using Gnome, Gnome suspends the machine after 20 minutes if there is no mouse or keyboard activity. I went into settings, but there is no way to adjust this feature. Some web searching brought me to this page: > > https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/22 > > Apparently the 20-minute suspend was made unchangable (at least not without changing the source code for Gnome and rebuilding it). > Apparently this change was made to comply with EU power regulations. > Anyway, this ruled out Gnome for me. > > Kirk McKusick