On Sat, Nov 23, 2024 at 02:45:46AM -0600, Richard Owlett wrote: > On 11/22/24 5:33 PM, Andrew M.A. Cater wrote: > > You misinterpreted my post. > > I meant to convey that I have been using Debian since release 6. > I liked my experience with Debian 9. > > I now have a machine with a clean initial install of Debian 12. > I'm not happy with it's configuration. > To find answers and pose intelligent questions I need to know definitions of > sleep/suspend/hibernate/etc as used in the Debian sub-culture. >
"As used in the Debian sub-culture" : it's as used by the * The firmware and chipset in your machine * The kernel interface * Whatever the tools are in your chosen GUI/desktop environment The first two are much more important - and largely common to all Linux distributions, though these may vary as to kernel version. There are threads around on "Windows suspend", "S3" and so on which relate largely to what the behaviour of physical hardware is when you perform an action and what is reported to the firmware and the kernel. (For example: What sleep state does your laptop go into when you shut the lid / does it ever truly shut down?) Some of these have changed in more recent laptops, not always for the better maybe. The last one is a matter of learning the tools to set the options in MATE these days, I presume. > Can you be more specific as to the issue(s) you are seeing here? Is it making sense of observed behaviour that is not causing you a problem? [You want to find out what is actually going on but what you see is fine] Is it that you desire one outcome but you get another? [I want my hardware to save state and shutdown when I hit the power button but it just suspends / I want my laptop to suspend and resume when the lid is shut but it goes into a weird sleep state I don't understand.] > Is it that you don't know where to set a desired option to get the behaviour you want? > All the very best, as ever, Andy (amaca...@debian.org)
