Date: Sun, 06 Nov 2022 16:59:15 -0600 From: Mike Karels <mike@karels.net> To: Alexander Motin <mav@FreeBSD.org> Cc: louis.freebsd@xs4all.nl, freebsd-current@FreeBSD.org Subject: Re: How to disable ACPI? (on FreeBSD14 CURRENT) Message-ID: <CF561AD0-B6C1-417F-9794-C395ED9AD5B1@karels.net> In-Reply-To: <277f029d-828b-74c3-ab38-862c7959df55@FreeBSD.org> References: <000501d8f1e8$c0442df0$40cc89d0$@xs4all.nl> <277f029d-828b-74c3-ab38-862c7959df55@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6 Nov 2022, at 16:47, Alexander Motin wrote: > Hi Louis, > > You should not try to disable ACPI these days. It was a recommendation= in some cases probably ~15 years ago, but for many years now modern syst= ems depend on ACPI for proper operation. I have no idea what causes cras= h in your case, but I would not expect it to end up good any way. > > I know nothing about GNOME, haven't touched it for many years, but it m= ust be it what makes your laptop to sleep. FreeBSD itself does not imple= ment such automatic policies. It could the BIOS also if this is a laptop. Mike > On 06.11.2022 09:04, louis.freebsd@xs4all.nl wrote: >> I need to disable acpi and the indicated method for that is to add ^hi= nt.acpi.0.disabled=3D"1"^ in /boot/loader.conf . >> >> However that crashes my system !!!!!! >> >> Not only that, to make it work again I have to edit loader.conf on a s= ystem which does ^not start^. >> >> After a lot of searching Internet came to the help with, I could start= the system again: >> >> 1. Select 3. Escape to loader prompt at the splash screen >> >> 2. Type set hint.acpi.0.disabled=3D"0" on the loader prompt >> >> 3. Then type boot on the loader prompt >> >> edit the loader.conf >> >> Very very glad with that fix however >> >> However the problem is still there, no idea how to prevent the system = from going to sleep (after about 10 minutes). >> >> No idea how to change those 10 minutes to a much longer time as well .= =2E.. >> >> Note that I have gnome as gui and use the system more or less as serve= r and manage the machine partly local via the GUI and partly remote via S= SH. >> >> Related to GNOME I did try ^gsettings set org.gnome.settings-daemon.pl= ugins.power sleep-inactive-ac-timeout 0^, however that did not solve the = problem as well. >> >> In the end there seems to two problems >> >> a) A BSD-issue ACPI-turn off in the bootloader is crashing the system = ! ! and >> >> b) a GNOME issue (switching the system off during user inactivity, whi= ch is bullshit for a server / for ssh-login / with multiple users). >> >> What IMHO apart from the screen lock, this is not a GNOME task but an = OS=C2=A0 function to be configured by the system administrator. >> >> A third problem, not to be addressed here, is that recovery from sleep= mode does not work on my system as well (even not S1). >> >> Most important for the moment is that the system keeps running / is no= t going down after x-time ! > > -- = > Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CF561AD0-B6C1-417F-9794-C395ED9AD5B1>