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 systems
> depend on ACPI for proper operation. I have no idea what causes crash 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 must be
> it what makes your laptop to sleep. FreeBSD itself does not implement such
> automatic policies.
It could the BIOS also if this is a laptop.
Mike
> On 06.11.2022 09:04, [email protected] wrote:
>> I need to disable acpi and the indicated method for that is to add
>> ^hint.acpi.0.disabled="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 system
>> 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="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 ....
>>
>> Note that I have gnome as gui and use the system more or less as server and
>> manage the machine partly local via the GUI and partly remote via SSH.
>>
>> Related to GNOME I did try ^gsettings set
>> org.gnome.settings-daemon.plugins.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, which 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
>> 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 not
>> going down after x-time !
>
> --
> Alexander Motin
