I think I have the latest one extracted to a usb drive . . . .
No swap needed:
erlangen:~ # free -h
total used free shared buff/cache available
Mem: 27Gi 10Gi 6.2Gi 247Mi 11Gi 16Gi
Swap: 0B 0B 0B
erlangen:~ #
No UEFI update needed:
erlangen:~ # inxi -zM
Machine:
Type: Desktop System: Micro-Star product: MS-7C56 v: 2.0 serial: N/A
Mobo: Micro-Star model: B550-A PRO (MS-7C56) v: 2.0 serial: <filter>
UEFI: American Megatrends LLC. v: A.90 date: 03/17/2022
erlangen:~ #
In the KDE System Settings I assigned sleep to the power button:
The power button toggles between Active and Sleep:
erlangen:~ # journalctl -S 11:00 -u systemd-suspend.service
May 21 11:33:58 erlangen systemd[1]: Starting System Suspend...
May 21 11:33:58 erlangen systemd-sleep[735473]: Successfully froze unit 'user.slice'.
May 21 11:33:58 erlangen systemd-sleep[735475]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend
May 21 11:33:58 erlangen systemd-sleep[735473]: Performing sleep operation 'suspend'...
May 21 11:34:08 erlangen systemd-sleep[735473]: System returned from sleep operation 'suspend'.
May 21 11:34:08 erlangen systemd-sleep[735529]: INFO: Skip running /usr/lib/systemd/system-sleep/grub2.sleep for suspend
May 21 11:34:08 erlangen systemd-sleep[735473]: Successfully thawed unit 'user.slice'.
May 21 11:34:08 erlangen systemd[1]: systemd-suspend.service: Deactivated successfully.
May 21 11:34:08 erlangen systemd[1]: Finished System Suspend.
erlangen:~ #
1 Like
How do you know the newer BIOS he has didnât actually make something worse?
How do you know yours wouldnât be better off with newer?
I donât know. I presume sleep is working. I would double check before updating the UEFI. @non_space did not detail âno resume from suspendâ.
During 3 years of daily operation and upgrades the system with the 5700G never failed to sleep and resume. Thus I never tried to upgrade.
OK gents, appreciate the feedbacks on it . . . .
Iâll have to check the power management settings to see what is the default. Less is more, but then the whole point of this thread and this new build was to get the machine to work with the newest kernels . . . to be able to resume from suspend, etc.
Itâs not show-stopper, maybe itâs a BUG in the 6.14.6 kernel??? : - ))
But, not sure if the power button to âsleepâ is what I want, or does that mean quick press to sleep and longer press to power down?? Two things I do while using the machine, suspend . . . and then later, turn it off; sometimes I need the power button to shut down.
@non_space No issues here with automatic suspend on two test machines (Intel/Nvidia) no swapâŚ
1 Like
Thanks for checking . . . . In my case, fresh install, machine wouldnât resume w/o clicking power button (external) . . . .
Havenât checked the prefs on it yet . . . .
@non_space I can press any key on the keyboard to resume?
Was that a statement or a question? You can resume by pressing any key, or you are asking me?? So far the machine is not resuming with any keystroke or mouse click.
# journalctl -S 11:00 -u systemd-suspend.service
-- No entries --
I guess that is a script that you created??
@non_space A question⌠So I have my keyboard running through a powered USB switch, only the keyboard works for me. Now I do have a Logitech wireless keyboard, let me test that as it has a specific power buttonâŚ
You might have to check the system BIOS for settings as I imagine it needs a trigger to come out of suspend since there maybe no power to your keyboard?
Edit: It came back out of suspend on the wireless keyboard on any key pressâŚ
Hmm . . . well my keyboard is wired and plugged into what would be the âtopâ most usb port, standard port.
It has the usb3 type port with the blue wafer in there, perhaps I could over it over to one of those ports to see if that makes a difference??
But, back over to the BIOS . . . havenât spent too much time there yet, just took a look at it . . . wouldnât know how to change anything to âtriggerâ resuming there?
@non_space I always use USB 2.0 for keyboards and mice, let me swap the Logitech dongle to USB 3.0 and test. Oh and this keyboard has a trackpad, those keys responded and brought system out of suspendâŚ
Edit, confirmed, not working on USB 3.0. So in the BIOS make sure there is USB Legacy support turned on⌠The manual may advise which ones can be configured as legacy?
1 Like
OK, I also use usb 2 for keyboards and mice, no reason to waste a 3 port on it.
But I did move the keyboard over to the 3 type ports and that also did not resume from suspend. So back over to the 2.
Not too much time to play today, but, OK, Iâll have to look into the BIOS settings and see if I can figure out how to include âlegacyâ support and see if that makes the difference.
I went into the BIOS >advanced mode and into >Settings and found the >usb configuration and in there âlegacy supportâ was already âenabledâ . . . just for kicks I changed it to âautoâ . . . .
Iâll test that out in a minute, not holding my breath since it was already enabled, etc.
@non_space Wired keyboard in USB 3.0 worked, just testing this wireless one again⌠it may not have connected properly in the last test.
1 Like
OK, as I did discover in my assembling of the parts, the first time I installed the RAM it âclickedâ into place, but one of them didnât show up in the BIOS . . . took them both out and switched them and the second time ws the charm, the first time it wasnât seated properly??
But this might be âapples to orangesâ in that your machine is Intel/Nvidia and mine is MSI/Ryzen . . . no graphics card, etc.
PS: The change to âautoâ didnât bring resume function . . . for now quick click on the power button brings me to log in. I would prefer keystroke . . . another item added to âto doâ list. Machine runs fast, and quiet . . . which is good.
In UEFI navigate to Advanced â Wake up Event Setup > enable the âResume by USB Deviceâ.
1 Like
Wanted to catch up with the thread, expect my reply in ~6 weeks
2 Likes
That almost sounds like a âsense of humorâ is in play, but I know that is out of character . . . .
Once the âresume from suspendâ issue is resolved in the new machine, the thread will be marked as solved, and 30 days after that it will auto-close. That might be within ~6 weeks, or might not.