HP PS/2 style keyboard preventing suspend:
I have openSUSE Tumbleweed running on this machine. I had attached a USB wireless HP keyboard to the machine and suspend worked well from what I could tell (the machine went to sleep and resumed when asked). The issue is the keyboard is/was not taking keystrokes correctly, quite alot of the time. It became very very frustrating for me to use. It seems sometimes freshly charged Panasonic Eneloop batteries may help a little but is unknown for certain still. When an older HP PS/2 style keyboard is attached to the machine. It’s solid and never misses a keystroke. :~> /usr/sbin/hwinfo --keyboard 25: PS/2 00.0: 10800 Keyboard [Created at input.226] Unique ID: nLyy.+49ps10DtUF Hardware Class: keyboard Model: "AT Translated Set 2 keyboard" Vendor: 0x0001 Device: 0x0001 "AT Translated Set 2 keyboard" Compatible to: int 0x0211 0x0001 Device File: /dev/input/event0 Device Files: /dev/input/event0, /dev/input/by-path/platform-i8042-serio-0-event-kbd Device Number: char 13:64 Driver Info #0: XkbRules: xfree86 XkbModel: pc104 Config Status: cfg=no, avail=yes, need=no, active=unknown :~> This keyboard now is preventing suspend from working fully. Yes, suspend does shut off the monitor but it leaves the machine in a running state (power supply fan still spinning). I have investigated the bios settings and can not find anything pertaining to the PS/2 style keyboard in there. There is a feature option in the machines bios for PS/2 style mouse though. What can I do to try to get the sleep/suspend feature to work correctly with the PS/2 style keyboard attached now? Suspend working normally on this setup is machine goes into a sleep state, quiet, with flashing power button. Resume activates by pressing the power button. As I do not have hibernation configured. Is this somehow related something 'udevadm' would help track down at all? -Best Wishes
On 2024-02-12 21:27, -pj via openSUSE Users wrote:
I have openSUSE Tumbleweed running on this machine. I had attached a USB wireless HP keyboard to the machine and suspend worked well from what I could tell (the machine went to sleep and resumed when asked). The issue is the keyboard is/was not taking keystrokes correctly, quite alot of the time. It became very very frustrating for me to use. It seems sometimes freshly charged Panasonic Eneloop batteries may help a little but is unknown for certain still.
When an older HP PS/2 style keyboard is attached to the machine. It’s solid and never misses a keystroke.
:~> /usr/sbin/hwinfo --keyboard 25: PS/2 00.0: 10800 Keyboard [Created at input.226] Unique ID: nLyy.+49ps10DtUF Hardware Class: keyboard Model: "AT Translated Set 2 keyboard" Vendor: 0x0001 Device: 0x0001 "AT Translated Set 2 keyboard" Compatible to: int 0x0211 0x0001 Device File: /dev/input/event0 Device Files: /dev/input/event0, /dev/input/by-path/platform-i8042-serio-0-event-kbd Device Number: char 13:64 Driver Info #0: XkbRules: xfree86 XkbModel: pc104 Config Status: cfg=no, avail=yes, need=no, active=unknown :~>
This keyboard now is preventing suspend from working fully. Yes, suspend does shut off the monitor but it leaves the machine in a running state (power supply fan still spinning). I have investigated the bios settings and can not find anything pertaining to the PS/2 style keyboard in there. There is a feature option in the machines bios for PS/2 style mouse though.
What can I do to try to get the sleep/suspend feature to work correctly with the PS/2 style keyboard attached now? Suspend working normally on this setup is machine goes into a sleep state, quiet, with flashing power button. Resume activates by pressing the power button. As I do not have hibernation configured.
Maybe the machine keeps the keyboard powered (so that you can press a key to awake it) and this requires the PSU to run in another state. So perhaps disable keyboard wake up. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 02-12-2024 02:43PM, Carlos E. R. wrote:
On 2024-02-12 21:27, -pj via openSUSE Users wrote:
I have openSUSE Tumbleweed running on this machine. I had attached a USB wireless HP keyboard to the machine and suspend worked well from what I could tell (the machine went to sleep and resumed when asked). The issue is the keyboard is/was not taking keystrokes correctly, quite alot of the time. It became very very frustrating for me to use. It seems sometimes freshly charged Panasonic Eneloop batteries may help a little but is unknown for certain still.
When an older HP PS/2 style keyboard is attached to the machine. It’s solid and never misses a keystroke.
:~> /usr/sbin/hwinfo --keyboard 25: PS/2 00.0: 10800 Keyboard [Created at input.226] Unique ID: nLyy.+49ps10DtUF Hardware Class: keyboard Model: "AT Translated Set 2 keyboard" Vendor: 0x0001 Device: 0x0001 "AT Translated Set 2 keyboard" Compatible to: int 0x0211 0x0001 Device File: /dev/input/event0 Device Files: /dev/input/event0, /dev/input/by-path/platform-i8042-serio-0-event-kbd Device Number: char 13:64 Driver Info #0: XkbRules: xfree86 XkbModel: pc104 Config Status: cfg=no, avail=yes, need=no, active=unknown :~>
This keyboard now is preventing suspend from working fully. Yes, suspend does shut off the monitor but it leaves the machine in a running state (power supply fan still spinning). I have investigated the bios settings and can not find anything pertaining to the PS/2 style keyboard in there. There is a feature option in the machines bios for PS/2 style mouse though.
What can I do to try to get the sleep/suspend feature to work correctly with the PS/2 style keyboard attached now? Suspend working normally on this setup is machine goes into a sleep state, quiet, with flashing power button. Resume activates by pressing the power button. As I do not have hibernation configured.
Maybe the machine keeps the keyboard powered (so that you can press a key to awake it) and this requires the PSU to run in another state. So perhaps disable keyboard wake up.
Thank you for your advice. I proceeded to review this website for more information in my search for an answer. https://shallowsky.com/blog/linux/kernel/no-mouse-kbd-wakeup.html I then opened Konsole and passed the following command: cat /proc/acpi/wakeup Device S-state Status Sysfs node LAN S5 *enabled pci:0000:00:19.0 USB4 S3 *enabled pci:0000:00:1a.0 USB5 S3 *enabled pci:0000:00:1a.1 USB7 S3 *enabled pci:0000:00:1a.2 ESB2 S3 *enabled pci:0000:00:1a.7 EXP1 S4 *disabled EXP2 S4 *disabled EXP3 S4 *disabled EXP4 S4 *disabled EXP5 S4 *disabled EXP6 S4 *disabled USB1 S3 *enabled pci:0000:00:1d.0 USB2 S3 *enabled pci:0000:00:1d.1 USB3 S3 *enabled pci:0000:00:1d.2 USB6 S3 *disabled ESB1 S3 *enabled pci:0000:00:1d.7 PCIB S5 *disabled pci:0000:00:1e.0 COM1 S4 *disabled pnp:00:02 COM2 S4 *disabled pnp:00:03 KBC0 S4 *enabled pnp:00:06 *enabled serio:serio0 MSE0 S4 *disabled PWRB S3 *enabled platform:PNP0C0C:00 I see KBC0 listed as enabled above and passed: Thinkcentre-M57p:~ # echo KBC0 >/proc/acpi/wakeup Suspend works well now with machine PSU shut off and only a flashing monitor and machine case power button light! Unsuspend works by only depressing the machines power button now also. :] When I powercycle and complete login, attempting to suspend the machine again results into a semi-failure suspend state as prior. My question for you now is which file to modify in openSUSE Tumbleweed in order to get this wonderful command persistent between boots and upgrades? Am I able to modify a certain file by inserting just "echo KBC0 >/proc/acpi/wakeup" in it? /etc/rc.local is not shown in the current filesystem, maybe because it was system IV related. -Thanks
My question for you now is which file to modify in openSUSE Tumbleweed in order to get this wonderful command persistent between boots and upgrades? Am I able to modify a certain file by inserting just "echo KBC0 >/proc/acpi/wakeup" in it?
Hi, You can set up the command to run when the system boots using a cron job. To use this method, do the following: 1. Run this command: crontab -e 2. Add the following line to that file: @reboot echo KBC0 >/proc/acpi/wakeup 3. Save the file The command needs root privileges. If you're not root, you can use sudo crontab -e in (1). This will make the command run whenever the system boots.
On 02-12-2024 10:35PM, Goblin Invader wrote:
My question for you now is which file to modify in openSUSE Tumbleweed in order to get this wonderful command persistent between boots and upgrades? Am I able to modify a certain file by inserting just "echo KBC0 >/proc/acpi/wakeup" in it?
Hi,
You can set up the command to run when the system boots using a cron job. To use this method, do the following:
1. Run this command: crontab -e 2. Add the following line to that file: @reboot echo KBC0 >/proc/acpi/wakeup 3. Save the file
The command needs root privileges. If you're not root, you can use sudo crontab -e in (1).
This will make the command run whenever the system boots.
Hello Goblin Invader, Some of what I was reading spoke of a crontab possibility which you explain above. The issue for me right now is my lack of knowledge of the vi editor. Is reversing what you suggest above basically just removing "@reboot echo KBC0 >/proc/acpi/wakeup" and then saving the file? It looks like if I knew more about vi this would possibly be a very straightforward and universal way to implement this. Thanks for this excellent suggestion.
On 2024-02-14 00:01, -pj via openSUSE Users wrote:
On 02-12-2024 10:35PM, Goblin Invader wrote:
Some of what I was reading spoke of a crontab possibility which you explain above.
The issue for me right now is my lack of knowledge of the vi editor.
Do: EDITOR=/usr/bin/mcedit crontab -e or EDITOR=/usr/bin/joe crontab -e instead of joe you can use jstar, jpico, jmacs, and joe will emulate those editors. Any one you like. Or use any other editors you like. pico, nano... But joe is installed by default on opensuse. When you find one that you like, then edit ".bashrc": export EDITOR=/usr/bin/mcedit and that will be the editor used by system tools instead of vi ;-) -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 02-13-2024 05:11PM, Carlos E. R. wrote:
On 2024-02-14 00:01, -pj via openSUSE Users wrote:
On 02-12-2024 10:35PM, Goblin Invader wrote:
Some of what I was reading spoke of a crontab possibility which you explain above.
The issue for me right now is my lack of knowledge of the vi editor.
Do:
EDITOR=/usr/bin/mcedit crontab -e
or
EDITOR=/usr/bin/joe crontab -e
instead of joe you can use jstar, jpico, jmacs, and joe will emulate those editors. Any one you like.
Or use any other editors you like. pico, nano... But joe is installed by default on opensuse.
When you find one that you like, then edit ".bashrc":
export EDITOR=/usr/bin/mcedit
and that will be the editor used by system tools instead of vi ;-)
This is really important advice on editors that I was not aware of. I have very limited knowledge of 'Kate Advanced Text Editor' and have mainly been using Kate for basic file editing tasks on this machine. For instance in order to edit /etc/default/grub I must be root in order for Kate to save any changes to the file. # kate /etc/default/grub THIS IS POTENTIALLY INSECURE! To edit files as root please use: SUDO_EDITOR=kwrite sudoedit <file> Then Kate opens the the *correct* grub file for editing. - kwrite looks pretty interesting. - Trying the following to open Kate does not seem to work so great anymore, as it opens Kates GUI into very strange files i.e. grub.09D0g681 file . :~> SUDO_EDITOR=kate sudoedit /etc/default/grub [sudo] password for root: sudoedit: /etc/default/grub unchanged Do you know what's going on with that by chance? - I recently asked about Kate in KDE and became informed on the following way to correctly open file for editing from the traditional starter. Workaround GUI Kate as root: Open the starter (alt+f2) enter user password - kdesu -c "kate -b /your/file/here" - -Best Regards
On 2024-02-14 23:49, -pj via openSUSE Users wrote:
On 02-13-2024 05:11PM, Carlos E. R. wrote:
On 2024-02-14 00:01, -pj via openSUSE Users wrote:
On 02-12-2024 10:35PM, Goblin Invader wrote:
Some of what I was reading spoke of a crontab possibility which you explain above.
The issue for me right now is my lack of knowledge of the vi editor.
Do:
EDITOR=/usr/bin/mcedit crontab -e
or
EDITOR=/usr/bin/joe crontab -e
instead of joe you can use jstar, jpico, jmacs, and joe will emulate those editors. Any one you like.
Or use any other editors you like. pico, nano... But joe is installed by default on opensuse.
When you find one that you like, then edit ".bashrc":
export EDITOR=/usr/bin/mcedit
and that will be the editor used by system tools instead of vi ;-)
This is really important advice on editors that I was not aware of. I have very limited knowledge of 'Kate Advanced Text Editor' and have mainly been using Kate for basic file editing tasks on this machine.
For instance in order to edit /etc/default/grub I must be root in order for Kate to save any changes to the file.
# kate /etc/default/grub THIS IS POTENTIALLY INSECURE! To edit files as root please use: SUDO_EDITOR=kwrite sudoedit <file>
Then Kate opens the the *correct* grub file for editing. - kwrite looks pretty interesting. - Trying the following to open Kate does not seem to work so great anymore, as it opens Kates GUI into very strange files i.e. grub.09D0g681 file .
:~> SUDO_EDITOR=kate sudoedit /etc/default/grub [sudo] password for root: sudoedit: /etc/default/grub unchanged
Do you know what's going on with that by chance?
No. I do not use graphical editors for admin work. I only use terminal editors for those things. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 2024-02-13 00:13, -pj via openSUSE Users wrote:
On 02-12-2024 02:43PM, Carlos E. R. wrote:
On 2024-02-12 21:27, -pj via openSUSE Users wrote:
Maybe the machine keeps the keyboard powered (so that you can press a key to awake it) and this requires the PSU to run in another state. So perhaps disable keyboard wake up.
Thank you for your advice. I proceeded to review this website for more information in my search for an answer. https://shallowsky.com/blog/linux/kernel/no-mouse-kbd-wakeup.html
I then opened Konsole and passed the following command: cat /proc/acpi/wakeup
Device S-state Status Sysfs node LAN S5 *enabled pci:0000:00:19.0 ... KBC0 S4 *enabled pnp:00:06 *enabled serio:serio0 MSE0 S4 *disabled PWRB S3 *enabled platform:PNP0C0C:00
I see KBC0 listed as enabled above and passed: Thinkcentre-M57p:~ # echo KBC0 >/proc/acpi/wakeup
Suspend works well now with machine PSU shut off and only a flashing monitor and machine case power button light! Unsuspend works by only depressing the machines power button now also. :]
Nice :-)
When I powercycle and complete login, attempting to suspend the machine again results into a semi-failure suspend state as prior.
My question for you now is which file to modify in openSUSE Tumbleweed in order to get this wonderful command persistent between boots and upgrades? Am I able to modify a certain file by inserting just "echo KBC0 >/proc/acpi/wakeup" in it?
Certainly.
/etc/rc.local is not shown in the current filesystem, maybe because it was system IV related.
It would be "/etc/init.d/", and there I still have: after.local boot.localhw boot.local Not sure if they still work, and I am on Leap. you can create your own systemd service to do things. Mine (calls a script): Telcontar:~ # cat /etc/systemd/system/helloworld.service [Unit] Description=Plays a welcome sound when target multi-user is reached After=multi-user.target # graphical.target - multi-user.target [Service] Type=oneshot RemainAfterExit=true StandardOutput=tty ExecStart=-/root/ThingsNeededForBoot/helloworld [Install] WantedBy=multi-user.target WantedBy=graphical.target Telcontar:~ # -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [02-13-24 07:01]:
On 2024-02-13 00:13, -pj via openSUSE Users wrote:
/etc/rc.local is not shown in the current filesystem, maybe because it was system IV related.
It would be "/etc/init.d/", and there I still have:
after.local boot.localhw boot.local
and current tumbleweed installs do not contain "/etc/init.d/" nor "/usr/etc/init.d"
Not sure if they still work, and I am on Leap.
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On 02-13-2024 07:51AM, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [02-13-24 07:01]:
On 2024-02-13 00:13, -pj via openSUSE Users wrote:
/etc/rc.local is not shown in the current filesystem, maybe because it was system IV related.
It would be "/etc/init.d/", and there I still have:
after.local boot.localhw boot.local
and current tumbleweed installs do not contain "/etc/init.d/" nor "/usr/etc/init.d"
drwxr-xr-x 1 root root 0 Jan 6 01:12 init.d is still in /etc on Tumbleweed here.
Not sure if they still work, and I am on Leap.
On dinsdag 13 februari 2024 20:57:10 CET -pj via openSUSE Users wrote:
On 02-13-2024 07:51AM, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [02-13-24 07:01]:
On 2024-02-13 00:13, -pj via openSUSE Users wrote:
/etc/rc.local is not shown in the current filesystem, maybe because it was system IV related.
It would be "/etc/init.d/", and there I still have:
after.local boot.localhw boot.local
and current tumbleweed installs do not contain "/etc/init.d/" nor "/usr/etc/init.d"
drwxr-xr-x 1 root root 0 Jan 6 01:12 init.d is still in /etc
on Tumbleweed here.
Not sure if they still work, and I am on Leap. On up-to-date TW:
knurpht@Lenovo-P16:~> locate /etc/init.d /etc/init.d -- Gertjan Lettink a.k.a. Knurpht openSUSE Board openSUSE Forums Team
* Knurpht-openSUSE <knurpht@opensuse.org> [02-13-24 15:04]:
On dinsdag 13 februari 2024 20:57:10 CET -pj via openSUSE Users wrote:
On 02-13-2024 07:51AM, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [02-13-24 07:01]:
On 2024-02-13 00:13, -pj via openSUSE Users wrote:
/etc/rc.local is not shown in the current filesystem, maybe because it was system IV related.
It would be "/etc/init.d/", and there I still have:
after.local boot.localhw boot.local
and current tumbleweed installs do not contain "/etc/init.d/" nor "/usr/etc/init.d"
drwxr-xr-x 1 root root 0 Jan 6 01:12 init.d is still in /etc
on Tumbleweed here.
Not sure if they still work, and I am on Leap. On up-to-date TW:
knurpht@Lenovo-P16:~> locate /etc/init.d /etc/init.d
system new 16 June 22 locate /etc/init.d no output aside from /var/lib/flatpack hits another system new 12 Oct 22 locate /etc/init.d no output another system new 14 June 22 locate /etc/init.d no output another system new 8 June 19 locate /etc/init.d /etc/init.d another system new 15 Nov 2007 locate /etc/init.d /etc/init.d seems to be related to tw install date key workds: seems to be and notice, "on thread topic". -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
And FWIW, on a brand-new shiny slow roll install done today, in a virtualbox, they're not there. On a machine which, IIRC, was a fresh install of 15.5, not there. On two machines which were upgraded from 15.4, they're there and dated Jul 27 2021. Every one of them is empty with ".." dated Nov 5. That's 3 days after I got back, and was sitting in front of them with the upgrade media in my grubby mitt.
On dinsdag 13 februari 2024 22:15:02 CET Patrick Shanahan wrote:
* Knurpht-openSUSE <knurpht@opensuse.org> [02-13-24 15:04]:
On dinsdag 13 februari 2024 20:57:10 CET -pj via openSUSE Users wrote:
On 02-13-2024 07:51AM, Patrick Shanahan wrote:
* Carlos E. R. <robin.listas@telefonica.net> [02-13-24 07:01]:
On 2024-02-13 00:13, -pj via openSUSE Users wrote:
/etc/rc.local is not shown in the current filesystem, maybe because it was system IV related.
It would be "/etc/init.d/", and there I still have:
after.local boot.localhw boot.local
and current tumbleweed installs do not contain "/etc/init.d/" nor "/usr/etc/init.d"
drwxr-xr-x 1 root root 0 Jan 6 01:12 init.d is still in /etc
on Tumbleweed here.
Not sure if they still work, and I am on Leap.
On up-to-date TW:
knurpht@Lenovo-P16:~> locate /etc/init.d /etc/init.d
system new 16 June 22
locate /etc/init.d no output aside from /var/lib/flatpack hits
another system new 12 Oct 22
locate /etc/init.d no output
another system new 14 June 22
locate /etc/init.d no output
another system new 8 June 19
locate /etc/init.d /etc/init.d
another system new 15 Nov 2007
locate /etc/init.d /etc/init.d
seems to be related to tw install date
key workds: seems to be
and notice, "on thread topic". knurpht@Lenovo-P16:~> ls -ld /etc/init.d/ drwxr-xr-x 1 root root 0 dec 3 03:20 /etc/init.d/ knurpht@Lenovo-P16:~> rpm -qf /etc/init.d/ aaa_base-84.87+git20231023.f347d36-1.2.x86_64
TW installed on Nov 8 2023 -- Gertjan Lettink a.k.a. Knurpht openSUSE Board openSUSE Forums Team
On 02-13-2024 05:59AM, Carlos E. R. wrote:
On 2024-02-13 00:13, -pj via openSUSE Users wrote:
On 02-12-2024 02:43PM, Carlos E. R. wrote:
On 2024-02-12 21:27, -pj via openSUSE Users wrote:
Maybe the machine keeps the keyboard powered (so that you can press a key to awake it) and this requires the PSU to run in another state. So perhaps disable keyboard wake up.
Thank you for your advice. I proceeded to review this website for more information in my search for an answer. https://shallowsky.com/blog/linux/kernel/no-mouse-kbd-wakeup.html
I then opened Konsole and passed the following command: cat /proc/acpi/wakeup
Device S-state Status Sysfs node LAN S5 *enabled pci:0000:00:19.0 ... KBC0 S4 *enabled pnp:00:06 *enabled serio:serio0 MSE0 S4 *disabled PWRB S3 *enabled platform:PNP0C0C:00
I see KBC0 listed as enabled above and passed: Thinkcentre-M57p:~ # echo KBC0 >/proc/acpi/wakeup
Suspend works well now with machine PSU shut off and only a flashing monitor and machine case power button light! Unsuspend works by only depressing the machines power button now also. :]
Nice :-)
When I powercycle and complete login, attempting to suspend the machine again results into a semi-failure suspend state as prior.
My question for you now is which file to modify in openSUSE Tumbleweed in order to get this wonderful command persistent between boots and upgrades? Am I able to modify a certain file by inserting just "echo KBC0 >/proc/acpi/wakeup" in it?
Certainly.
/etc/rc.local is not shown in the current filesystem, maybe because it was system IV related.
It would be "/etc/init.d/", and there I still have:
after.local boot.localhw boot.local
Not sure if they still work, and I am on Leap.
you can create your own systemd service to do things. Mine (calls a script):
Telcontar:~ # cat /etc/systemd/system/helloworld.service [Unit] Description=Plays a welcome sound when target multi-user is reached After=multi-user.target # graphical.target - multi-user.target
[Service] Type=oneshot RemainAfterExit=true StandardOutput=tty ExecStart=-/root/ThingsNeededForBoot/helloworld
[Install] WantedBy=multi-user.target WantedBy=graphical.target Telcontar:~ #
Hi, thanks for this information. I believe I have been able to create a working systemd service that persists (after powercycle), on this machine to allow the HP PS/2 Keyboard to power off, when suspend is envoked. The following is what I have done: I reviewed this article: https://www.suse.com/support/kb/doc/?id=000019672 Do you think the Type=simple (in article above) is adequate for this keyboard situation? Do you think the Type=oneshot is better for this situation? Why is # graphical.target - multi-user.target not active in your example? I then looked at your example provided above. I decided to implement your example above. Shown below is what I have done. >:| --------------------------------------------------------------------- Thinkcentre-M57p:/etc/systemd/system> ls -lah -rwxr-xr-x 1 root root 312 Feb 13 15:15 HP-PS2-Keyboard.service --------------------------------------------------------------------- Thinkcentre-M57p:/etc/systemd/system> locate HP-PS2-Keyboard.service /etc/systemd/system/HP-PS2-Keyboard.service /etc/systemd/system/graphical.target.wants/HP-PS2-Keyboard.service /etc/systemd/system/multi-user.target.wants/HP-PS2-Keyboard.service -------------------------------------------------------------------- Thinkcentre-M57p:/etc/systemd/system> cat HP-PS2-Keyboard.service [Unit] Description=Disable PS/2 style keyboard power when sleep state is envoked on this machine After=multi-user.target # graphical.target - multi-user.target [Service] Type=oneshot RemainAfterExit=true StandardOutput=tty ExecStart=-/usr/sbin/HP-PS2-Keyboard.sh [Install] WantedBy=multi-user.target WantedBy=graphical.target ---------------------------------------------------------------------- Thinkcentre-M57p:/usr/sbin> locate HP-PS2-Keyboard.sh /usr/sbin/HP-PS2-Keyboard.sh ------------------------------------------------------------------------ Thinkcentre-M57p:/usr/sbin> ls -lah -rwxr-xr-x 1 root root 93 Feb 13 15:28 HP-PS2-Keyboard.sh <- Should this script file have to have a .sh extension? The other files in /usr/sbin do not have .sh extensions shown. ------------------------------------------------------------------------ Thinkcentre-M57p:/usr/sbin> cat HP-PS2-Keyboard.sh #!/bin/bash echo KBC0 >/proc/acpi/wakeup echo "the script works" >> /tmp/HP-PS2-Keyboard.txt ----------------------------------------------------------------------- Thinkcentre-M57p:/tmp> ls -lah -rw-r--r-- 1 root root 17 Feb 13 15:41 HP-PS2-Keyboard.txt ----------------------------------------------------------------- Thinkcentre-M57p:/tmp> cat HP-PS2-Keyboard.txt the script works ----------------------------------------------------------
On 02-13-2024 04:34PM, -pj via openSUSE Users wrote:
On 02-13-2024 05:59AM, Carlos E. R. wrote:
On 2024-02-13 00:13, -pj via openSUSE Users wrote:
On 02-12-2024 02:43PM, Carlos E. R. wrote:
On 2024-02-12 21:27, -pj via openSUSE Users wrote:
Maybe the machine keeps the keyboard powered (so that you can press a key to awake it) and this requires the PSU to run in another state. So perhaps disable keyboard wake up.
Thank you for your advice. I proceeded to review this website for more information in my search for an answer. https://shallowsky.com/blog/linux/kernel/no-mouse-kbd-wakeup.html
I then opened Konsole and passed the following command: cat /proc/acpi/wakeup
Device S-state Status Sysfs node LAN S5 *enabled pci:0000:00:19.0 ... KBC0 S4 *enabled pnp:00:06 *enabled serio:serio0 MSE0 S4 *disabled PWRB S3 *enabled platform:PNP0C0C:00
I see KBC0 listed as enabled above and passed: Thinkcentre-M57p:~ # echo KBC0 >/proc/acpi/wakeup
Suspend works well now with machine PSU shut off and only a flashing monitor and machine case power button light! Unsuspend works by only depressing the machines power button now also. :]
Nice :-)
When I powercycle and complete login, attempting to suspend the machine again results into a semi-failure suspend state as prior.
My question for you now is which file to modify in openSUSE Tumbleweed in order to get this wonderful command persistent between boots and upgrades? Am I able to modify a certain file by inserting just "echo KBC0 >/proc/acpi/wakeup" in it?
Certainly.
/etc/rc.local is not shown in the current filesystem, maybe because it was system IV related.
It would be "/etc/init.d/", and there I still have:
after.local boot.localhw boot.local
Not sure if they still work, and I am on Leap.
you can create your own systemd service to do things. Mine (calls a script):
Telcontar:~ # cat /etc/systemd/system/helloworld.service [Unit] Description=Plays a welcome sound when target multi-user is reached After=multi-user.target # graphical.target - multi-user.target
[Service] Type=oneshot RemainAfterExit=true StandardOutput=tty ExecStart=-/root/ThingsNeededForBoot/helloworld
[Install] WantedBy=multi-user.target WantedBy=graphical.target Telcontar:~ #
Hi, thanks for this information. I believe I have been able to create a working systemd service that persists (after powercycle), on this machine to allow the HP PS/2 Keyboard to power off, when suspend is envoked. The following is what I have done:
I reviewed this article: https://www.suse.com/support/kb/doc/?id=000019672
Do you think the Type=simple (in article above) is adequate for this keyboard situation?
Do you think the Type=oneshot is better for this situation?
Why is # graphical.target - multi-user.target not active in your example?
I then looked at your example provided above. I decided to implement your example above. Shown below is what I have done. >:| --------------------------------------------------------------------- Thinkcentre-M57p:/etc/systemd/system> ls -lah -rwxr-xr-x 1 root root 312 Feb 13 15:15 HP-PS2-Keyboard.service --------------------------------------------------------------------- Thinkcentre-M57p:/etc/systemd/system> locate HP-PS2-Keyboard.service /etc/systemd/system/HP-PS2-Keyboard.service /etc/systemd/system/graphical.target.wants/HP-PS2-Keyboard.service /etc/systemd/system/multi-user.target.wants/HP-PS2-Keyboard.service -------------------------------------------------------------------- Thinkcentre-M57p:/etc/systemd/system> cat HP-PS2-Keyboard.service [Unit] Description=Disable PS/2 style keyboard power when sleep state is envoked on this machine After=multi-user.target # graphical.target - multi-user.target
[Service] Type=oneshot RemainAfterExit=true StandardOutput=tty ExecStart=-/usr/sbin/HP-PS2-Keyboard.sh
[Install] WantedBy=multi-user.target WantedBy=graphical.target ---------------------------------------------------------------------- Thinkcentre-M57p:/usr/sbin> locate HP-PS2-Keyboard.sh /usr/sbin/HP-PS2-Keyboard.sh ------------------------------------------------------------------------ Thinkcentre-M57p:/usr/sbin> ls -lah -rwxr-xr-x 1 root root 93 Feb 13 15:28 HP-PS2-Keyboard.sh <- Should this script file have to have a .sh extension? The other files in /usr/sbin do not have .sh extensions shown. ------------------------------------------------------------------------ Thinkcentre-M57p:/usr/sbin> cat HP-PS2-Keyboard.sh #!/bin/bash echo KBC0 >/proc/acpi/wakeup echo "the script works" >> /tmp/HP-PS2-Keyboard.txt ----------------------------------------------------------------------- Thinkcentre-M57p:/tmp> ls -lah -rw-r--r-- 1 root root 17 Feb 13 15:41 HP-PS2-Keyboard.txt ----------------------------------------------------------------- Thinkcentre-M57p:/tmp> cat HP-PS2-Keyboard.txt the script works ----------------------------------------------------------
I sent the above to soon. If I rename the systemd service file to more generic (PS2-Keyboard.service), do I need to do anything to the systemd service as far as stopping and starting the service again? -Thanks for your help on this.
On 2024-02-13 23:42, -pj via openSUSE Users wrote:
On 02-13-2024 04:34PM, -pj via openSUSE Users wrote:
I sent the above to soon. If I rename the systemd service file to more generic (PS2-Keyboard.service), do I need to do anything to the systemd service as far as stopping and starting the service again?
-Thanks for your help on this.
systemctl daemon-reload perhaps. You can also disable or enable a new/old service. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 2024-02-13 23:34, -pj via openSUSE Users wrote:
On 02-13-2024 05:59AM, Carlos E. R. wrote:
On 2024-02-13 00:13, -pj via openSUSE Users wrote:
...
you can create your own systemd service to do things. Mine (calls a script):
Telcontar:~ # cat /etc/systemd/system/helloworld.service [Unit] Description=Plays a welcome sound when target multi-user is reached After=multi-user.target # graphical.target - multi-user.target
[Service] Type=oneshot RemainAfterExit=true StandardOutput=tty ExecStart=-/root/ThingsNeededForBoot/helloworld
[Install] WantedBy=multi-user.target WantedBy=graphical.target Telcontar:~ #
Hi, thanks for this information. I believe I have been able to create a working systemd service that persists (after powercycle), on this machine to allow the HP PS/2 Keyboard to power off, when suspend is envoked. The following is what I have done:
I reviewed this article: https://www.suse.com/support/kb/doc/?id=000019672
Do you think the Type=simple (in article above) is adequate for this keyboard situation?
Do you think the Type=oneshot is better for this situation?
I don't know, I am not an expert on this :-)
Why is # graphical.target - multi-user.target not active in your example?
That is just a comment. I could use: After=multi-user.target or After=graphical.target I decided that multi-user.target was better for my purpose, it would work both on runlevels 3 or 5.
I then looked at your example provided above. I decided to implement your example above. Shown below is what I have done. >:| --------------------------------------------------------------------- Thinkcentre-M57p:/etc/systemd/system> ls -lah -rwxr-xr-x 1 root root 312 Feb 13 15:15 HP-PS2-Keyboard.service --------------------------------------------------------------------- Thinkcentre-M57p:/etc/systemd/system> locate HP-PS2-Keyboard.service /etc/systemd/system/HP-PS2-Keyboard.service /etc/systemd/system/graphical.target.wants/HP-PS2-Keyboard.service /etc/systemd/system/multi-user.target.wants/HP-PS2-Keyboard.service -------------------------------------------------------------------- Thinkcentre-M57p:/etc/systemd/system> cat HP-PS2-Keyboard.service [Unit] Description=Disable PS/2 style keyboard power when sleep state is envoked on this machine After=multi-user.target # graphical.target - multi-user.target
[Service] Type=oneshot RemainAfterExit=true StandardOutput=tty ExecStart=-/usr/sbin/HP-PS2-Keyboard.sh
[Install] WantedBy=multi-user.target WantedBy=graphical.target ----------------------------------------------------------------------
One comment. Better place your script in /usr/local/sbin/, that's the standard place for scripts done by the administrator of the machine. /usr/sbin is used by the distribution, and when upgrading/migrating the machine it is easier to just backup and copy the entire /usr/local/ structure.
Thinkcentre-M57p:/usr/sbin> locate HP-PS2-Keyboard.sh /usr/sbin/HP-PS2-Keyboard.sh ------------------------------------------------------------------------ Thinkcentre-M57p:/usr/sbin> ls -lah -rwxr-xr-x 1 root root 93 Feb 13 15:28 HP-PS2-Keyboard.sh <- Should this script file have to have a .sh extension? The other files in /usr/sbin do not have .sh extensions shown.
It is irrelevant, whatever you are happy with. If you always set the extension, it makes easier for you to locate scripts.
------------------------------------------------------------------------ Thinkcentre-M57p:/usr/sbin> cat HP-PS2-Keyboard.sh #!/bin/bash echo KBC0 >/proc/acpi/wakeup echo "the script works" >> /tmp/HP-PS2-Keyboard.txt
Trick: logger -t Mine -p local1.info "The script works." (local "one") Or logger -t Mine -p local1.info "Disabling wakeup in PS2 keyboard" and you will see that line printed in "journalctl" output.
----------------------------------------------------------------------- Thinkcentre-M57p:/tmp> ls -lah -rw-r--r-- 1 root root 17 Feb 13 15:41 HP-PS2-Keyboard.txt ----------------------------------------------------------------- Thinkcentre-M57p:/tmp> cat HP-PS2-Keyboard.txt the script works ----------------------------------------------------------
-- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 02-13-2024 04:49PM, Carlos E. R. wrote:
On 2024-02-13 23:34, -pj via openSUSE Users wrote:
On 02-13-2024 05:59AM, Carlos E. R. wrote:
On 2024-02-13 00:13, -pj via openSUSE Users wrote:
...
you can create your own systemd service to do things. Mine (calls a script):
Telcontar:~ # cat /etc/systemd/system/helloworld.service [Unit] Description=Plays a welcome sound when target multi-user is reached After=multi-user.target # graphical.target - multi-user.target
[Service] Type=oneshot RemainAfterExit=true StandardOutput=tty ExecStart=-/root/ThingsNeededForBoot/helloworld
[Install] WantedBy=multi-user.target WantedBy=graphical.target Telcontar:~ #
Hi, thanks for this information. I believe I have been able to create a working systemd service that persists (after powercycle), on this machine to allow the HP PS/2 Keyboard to power off, when suspend is envoked. The following is what I have done:
I reviewed this article: https://www.suse.com/support/kb/doc/?id=000019672
Do you think the Type=simple (in article above) is adequate for this keyboard situation?
Do you think the Type=oneshot is better for this situation?
I don't know, I am not an expert on this :-)
:|
Why is # graphical.target - multi-user.target not active in your example?
That is just a comment. I could use:
After=multi-user.target
or
After=graphical.target
I decided that multi-user.target was better for my purpose, it would work both on runlevels 3 or 5.
Ok
I then looked at your example provided above. I decided to implement your example above. Shown below is what I have done. >:| --------------------------------------------------------------------- Thinkcentre-M57p:/etc/systemd/system> ls -lah -rwxr-xr-x 1 root root 312 Feb 13 15:15 HP-PS2-Keyboard.service --------------------------------------------------------------------- Thinkcentre-M57p:/etc/systemd/system> locate HP-PS2-Keyboard.service /etc/systemd/system/HP-PS2-Keyboard.service /etc/systemd/system/graphical.target.wants/HP-PS2-Keyboard.service /etc/systemd/system/multi-user.target.wants/HP-PS2-Keyboard.service -------------------------------------------------------------------- Thinkcentre-M57p:/etc/systemd/system> cat HP-PS2-Keyboard.service [Unit] Description=Disable PS/2 style keyboard power when sleep state is envoked on this machine After=multi-user.target # graphical.target - multi-user.target
[Service] Type=oneshot RemainAfterExit=true StandardOutput=tty ExecStart=-/usr/sbin/HP-PS2-Keyboard.sh
[Install] WantedBy=multi-user.target WantedBy=graphical.target ----------------------------------------------------------------------
One comment. Better place your script in /usr/local/sbin/, that's the standard place for scripts done by the administrator of the machine. /usr/sbin is used by the distribution, and when upgrading/migrating the machine it is easier to just backup and copy the entire /usr/local/ structure.
I moved the file. That's good to know. locate PS2-Keyboard.sh /usr/local/sbin/PS2-Keyboard.sh I think it's important to 'updatedb' when/if moving these files and changing their names is that correct? I made an error initially by the naming approach of "HP-PS2-Keyboard" then decided PS2-Keyboard would be a better approach in this situation.
Thinkcentre-M57p:/usr/sbin> locate HP-PS2-Keyboard.sh /usr/sbin/HP-PS2-Keyboard.sh ------------------------------------------------------------------------ Thinkcentre-M57p:/usr/sbin> ls -lah -rwxr-xr-x 1 root root 93 Feb 13 15:28 HP-PS2-Keyboard.sh <- Should this script file have to have a .sh extension? The other files in /usr/sbin do not have .sh extensions shown.
It is irrelevant, whatever you are happy with. If you always set the extension, it makes easier for you to locate scripts.
Yes, I see .sh is easier to see in a way than a file without that extension.
------------------------------------------------------------------------ Thinkcentre-M57p:/usr/sbin> cat HP-PS2-Keyboard.sh #!/bin/bash echo KBC0 >/proc/acpi/wakeup echo "the script works" >> /tmp/HP-PS2-Keyboard.txt
Trick:
logger -t Mine -p local1.info "The script works."
(local "one")
When you speak of "(local "one")" I do not understand what you are referring to very well. Can you please explain this a bit more perhaps?
Or
logger -t Mine -p local1.info "Disabling wakeup in PS2 keyboard"
Does this below look like the correct way to implement what you suggest in your second 'trick example' directly above? I probably don't need the "echo "the script works" >> /tmp/PS2-Keyboard.txt", it is informative though. - #!/bin/bash echo KBC0 >/proc/acpi/wakeup echo "Disabling wakeup in PS2 keyboard" >> /tmp/PS2-Keyboard.txt logger -t Mine -p local1.info "Disabling wakeup in PS2 keyboard" - It's nice to have this so functional now. Many Thanks
and you will see that line printed in "journalctl" output.
On 2024-02-14 03:40, -pj via openSUSE Users wrote:
On 02-13-2024 04:49PM, Carlos E. R. wrote:
On 2024-02-13 23:34, -pj via openSUSE Users wrote:
On 02-13-2024 05:59AM, Carlos E. R. wrote:
On 2024-02-13 00:13, -pj via openSUSE Users wrote:
...
One comment. Better place your script in /usr/local/sbin/, that's the standard place for scripts done by the administrator of the machine. /usr/sbin is used by the distribution, and when upgrading/migrating the machine it is easier to just backup and copy the entire /usr/local/ structure.
I moved the file. That's good to know. locate PS2-Keyboard.sh /usr/local/sbin/PS2-Keyboard.sh
I think it's important to 'updatedb' when/if moving these files and changing their names is that correct? I made an error initially by the naming approach of "HP-PS2-Keyboard" then decided PS2-Keyboard would be a better approach in this situation.
Not important. That file is only used in your searches, not by tools in the system. ...
------------------------------------------------------------------------ Thinkcentre-M57p:/usr/sbin> cat HP-PS2-Keyboard.sh #!/bin/bash echo KBC0 >/proc/acpi/wakeup echo "the script works" >> /tmp/HP-PS2-Keyboard.txt
Trick:
logger -t Mine -p local1.info "The script works."
(local "one")
When you speak of "(local "one")" I do not understand what you are referring to very well. Can you please explain this a bit more perhaps?
That the "1" in the name is a one, not a lower case "L". There are local1, local2,...local7. I don't remember if more. I can give you tomorrow the rest of the names (I have to find them). See the man page. Ah, found them: #CER docs, from syslog(2) #define KERN_EMERG "<0>" /* system is unusable */ #define KERN_ALERT "<1>" /* action must be taken immediately */ #define KERN_CRIT "<2>" /* critical conditions */ #define KERN_ERR "<3>" /* error conditions */ #define KERN_WARNING "<4>" /* warning conditions */ #define KERN_NOTICE "<5>" /* normal but significant condition */ #define KERN_INFO "<6>" /* informational */ #define KERN_DEBUG "<7>" /* debug-level messages */ #CER: facility syslog(3) and /usr/include/sys/syslog.h #define LOG_KERN (0<<3) /* kernel messages */ kernel messages (these can't be generated from user processes) #define LOG_USER (1<<3) /* random user-level messages */ (default) #define LOG_MAIL (2<<3) /* mail system */ mail subsystem #define LOG_DAEMON (3<<3) /* system daemons */ system daemons without separate facility value #define LOG_AUTH (4<<3) /* security/authorization messages */ security/authorization messages #define LOG_SYSLOG (5<<3) /* messages generated internally by syslogd */ messages generated internally by syslogd(8) #define LOG_LPR (6<<3) /* line printer subsystem */ line printer subsystem #define LOG_NEWS (7<<3) /* network news subsystem */ USENET news subsystem #define LOG_UUCP (8<<3) /* UUCP subsystem */ UUCP subsystem #define LOG_CRON (9<<3) /* clock daemon */ clock daemon (cron and at) #define LOG_AUTHPRIV (10<<3) /* security/authorization messages (private) */ security/authorization messages (private) #define LOG_FTP (11<<3) /* ftp daemon */ ftp daemon #/* other codes through 15 reserved for system use */ reserved for local use #define LOG_LOCAL0 (16<<3) /* reserved for local use */ #define LOG_LOCAL1 (17<<3) /* reserved for local use */ #define LOG_LOCAL2 (18<<3) /* reserved for local use */ #define LOG_LOCAL3 (19<<3) /* reserved for local use */ #define LOG_LOCAL4 (20<<3) /* reserved for local use */ #define LOG_LOCAL5 (21<<3) /* reserved for local use */ #define LOG_LOCAL6 (22<<3) /* reserved for local use */ #define LOG_LOCAL7 (23<<3) /* reserved for local use */ #define LOG_NFACILITIES 24 /* current number of facilities */ #define LOG_FACMASK 0x03f8 /* mask to extract facility part */ /* facility of pri */ #define LOG_FAC(p) (((p) & LOG_FACMASK) >> 3)
Or
logger -t Mine -p local1.info "Disabling wakeup in PS2 keyboard"
Does this below look like the correct way to implement what you suggest in your second 'trick example' directly above? I probably don't need the "echo "the script works" >> /tmp/PS2-Keyboard.txt", it is informative though. - #!/bin/bash echo KBC0 >/proc/acpi/wakeup echo "Disabling wakeup in PS2 keyboard" >> /tmp/PS2-Keyboard.txt logger -t Mine -p local1.info "Disabling wakeup in PS2 keyboard" -
Certainly. Maybe "-t HP-PS2-Keyboard.sh", though. Up to you. :-)
It's nice to have this so functional now. Many Thanks
Welcome :-)
and you will see that line printed in "journalctl" output.
-- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 2024-02-14 03:40, -pj via openSUSE Users wrote:
On 02-13-2024 04:49PM, Carlos E. R. wrote:
On 2024-02-13 23:34, -pj via openSUSE Users wrote:
On 02-13-2024 05:59AM, Carlos E. R. wrote:
On 2024-02-13 00:13, -pj via openSUSE Users wrote:
...
One comment. Better place your script in /usr/local/sbin/, that's the standard place for scripts done by the administrator of the machine. /usr/sbin is used by the distribution, and when upgrading/migrating the machine it is easier to just backup and copy the entire /usr/local/ structure.
I moved the file. That's good to know. locate PS2-Keyboard.sh /usr/local/sbin/PS2-Keyboard.sh
I think it's important to 'updatedb' when/if moving these files and changing their names is that correct? I made an error initially by the naming approach of "HP-PS2-Keyboard" then decided PS2-Keyboard would be a better approach in this situation.
Not important. That file is only used in your searches, not by tools in the system. I see
...
------------------------------------------------------------------------ Thinkcentre-M57p:/usr/sbin> cat HP-PS2-Keyboard.sh #!/bin/bash echo KBC0 >/proc/acpi/wakeup echo "the script works" >> /tmp/HP-PS2-Keyboard.txt
Trick:
logger -t Mine -p local1.info "The script works."
(local "one")
When you speak of "(local "one")" I do not understand what you are referring to very well. Can you please explain this a bit more perhaps?
That the "1" in the name is a one, not a lower case "L". There are local1, local2,...local7. I don't remember if more. I can give you tomorrow the rest of the names (I have to find them). See the man page. I apologize for not seeing the clarity which you presented in "(local "one")" initially. I for some reason was thinking something else was
On 02-13-2024 09:57PM, Carlos E. R. wrote: possibly meant by this.
Ah, found them:
The syslog (2) on this machine here contains the similar if not same to displayed below. I was completely oblivious to the connection of syslog and journalctl output before. I see now there is a sort of connection at least.
#CER docs, from syslog(2)
#define KERN_EMERG "<0>" /* system is unusable */
Is this what you are refering to by "local1" (below)?
#define KERN_ALERT "<1>" /* action must be taken immediately */
#define KERN_CRIT "<2>" /* critical conditions */ #define KERN_ERR "<3>" /* error conditions */ #define KERN_WARNING "<4>" /* warning conditions */ #define KERN_NOTICE "<5>" /* normal but significant condition */ #define KERN_INFO "<6>" /* informational */ #define KERN_DEBUG "<7>" /* debug-level messages */
#CER: facility syslog(3) and /usr/include/sys/syslog.h #define LOG_KERN (0<<3) /* kernel messages */ kernel messages (these can't be generated from user processes) #define LOG_USER (1<<3) /* random user-level messages */ (default) #define LOG_MAIL (2<<3) /* mail system */ mail subsystem #define LOG_DAEMON (3<<3) /* system daemons */ system daemons without separate facility value #define LOG_AUTH (4<<3) /* security/authorization messages */ security/authorization messages #define LOG_SYSLOG (5<<3) /* messages generated internally by syslogd */ messages generated internally by syslogd(8) #define LOG_LPR (6<<3) /* line printer subsystem */ line printer subsystem #define LOG_NEWS (7<<3) /* network news subsystem */ USENET news subsystem #define LOG_UUCP (8<<3) /* UUCP subsystem */ UUCP subsystem #define LOG_CRON (9<<3) /* clock daemon */ clock daemon (cron and at) #define LOG_AUTHPRIV (10<<3) /* security/authorization messages (private) */ security/authorization messages (private) #define LOG_FTP (11<<3) /* ftp daemon */ ftp daemon
#/* other codes through 15 reserved for system use */ reserved for local use #define LOG_LOCAL0 (16<<3) /* reserved for local use */ #define LOG_LOCAL1 (17<<3) /* reserved for local use */ #define LOG_LOCAL2 (18<<3) /* reserved for local use */ #define LOG_LOCAL3 (19<<3) /* reserved for local use */ #define LOG_LOCAL4 (20<<3) /* reserved for local use */ #define LOG_LOCAL5 (21<<3) /* reserved for local use */ #define LOG_LOCAL6 (22<<3) /* reserved for local use */ #define LOG_LOCAL7 (23<<3) /* reserved for local use */
#define LOG_NFACILITIES 24 /* current number of facilities */ #define LOG_FACMASK 0x03f8 /* mask to extract facility part */ /* facility of pri */ #define LOG_FAC(p) (((p) & LOG_FACMASK) >> 3)
Or
logger -t Mine -p local1.info "Disabling wakeup in PS2 keyboard"
Does this below look like the correct way to implement what you suggest in your second 'trick example' directly above? I probably don't need the "echo "the script works" >> /tmp/PS2-Keyboard.txt", it is informative though. - #!/bin/bash echo KBC0 >/proc/acpi/wakeup echo "Disabling wakeup in PS2 keyboard" >> /tmp/PS2-Keyboard.txt logger -t Mine -p local1.info "Disabling wakeup in PS2 keyboard" -
Certainly. Maybe "-t HP-PS2-Keyboard.sh", though. Up to you. :-) Yes, I made a somewhat dumb error (please see below for update). :[
It's nice to have this so functional now. Many Thanks
Welcome :-)
Ok, I really do not want to push my luck here with the great help you have provided so far but I really do want to ask a few more questions about this situation here with the keyboard. PS2-Keyboard.sh is changed to as follows: - Thinkcentre-M57p:/usr/local/sbin> cat PS2-Keyboard.sh #!/bin/bash echo KBC0 >/proc/acpi/wakeup echo "Disabling wakeup in PS2 keyboard" >> /tmp/PS2-Keyboard.txt echo logger -t PS2-Keyboard.sh -p local1.info "Disabling wakeup in PS2 keyboard" - Is, "echo logger -t PS2-Keyboard.sh -p local1.info "Disabling wakeup in PS2 keyboard" what i'm actually after here (for kernel alerts)?
and you will see that line printed in "journalctl" output.
I have powercycled the machine. Then complete two suspend/unsuspend cycles. Then in Konsole pass: journalctl | grep -i "PS2\|Keyboard" Scrolling down to today's date. Shows what seems to me as somewhat sporatic results for: PS2-Keyboard.sh (meaning each time a suspend/unsuspend cycle completes), does not add a fresh log entry, (viewable in Konsole) even after journalctl | grep -i "PS2\|Keyboard" is passed yet again (after unsuspend completes). See sporatic displayed entry below. Feb 13 22:27:18 Thinkcentre-M57p PS2-Keyboard.sh[1820]: Disabling wakeup in PS2 keyboard Why is a fresh entry of the above "PS2-Keyboard.sh[1820]: Disabling wakeup in PS2 Keyboard" not created every suspend/unsuspend cycle completion? ------------------------------------------------------------------------- Finally, there are many errors displayed (from one source) by journalctl output, about 'executable permissions' as follows: Thinkcentre-M57p systemd[1]: Configuration file /etc/systemd/system/PS2-Keyboard.service is marked executable. Please remove executable permission bits. Proceeding anyway. -rwxr-xr-x 1 root root 331 Feb 13 17:38 PS2-Keyboard.service My mind starts thinking to pass the following: chmod ugo-x PS2-Keyboard.service All the other directories *and* entries in /etc/systemd/system have 'ugo+x' permissions set. What's going on here with that? -------------------------------------------------------------------------- Is this thinking of mine correct about "PS2-Keyboard.service"? Can you suggest a journalctl command that could be more ideal in monitoring the keyboard messages, getting things set up? Thanks again for your insight.
On 2024-02-14 07:45, -pj via openSUSE Users wrote:
On 02-13-2024 09:57PM, Carlos E. R. wrote:
On 2024-02-14 03:40, -pj via openSUSE Users wrote:
On 02-13-2024 04:49PM, Carlos E. R. wrote:
On 2024-02-13 23:34, -pj via openSUSE Users wrote:
On 02-13-2024 05:59AM, Carlos E. R. wrote:
On 2024-02-13 00:13, -pj via openSUSE Users wrote:
...
Trick:
logger -t Mine -p local1.info "The script works."
(local "one")
When you speak of "(local "one")" I do not understand what you are referring to very well. Can you please explain this a bit more perhaps?
That the "1" in the name is a one, not a lower case "L". There are local1, local2,...local7. I don't remember if more. I can give you tomorrow the rest of the names (I have to find them). See the man page. I apologize for not seeing the clarity which you presented in "(local "one")" initially. I for some reason was thinking something else was possibly meant by this.
Ah, found them: The syslog (2) on this machine here contains the similar if not same to displayed below. I was completely oblivious to the connection of syslog and journalctl output before. I see now there is a sort of connection at least.
Journal is a redesign of syslog, but many admins prefer syslog. You can have both.
#CER docs, from syslog(2)
#define KERN_EMERG "<0>" /* system is unusable */ Is this what you are refering to by "local1" (below)?
Below. It took me some time, long ago, to find the exact definitions.
#define KERN_ALERT "<1>" /* action must be taken immediately */
...
#/* other codes through 15 reserved for system use */ reserved for local use #define LOG_LOCAL0 (16<<3) /* reserved for local use */ #define LOG_LOCAL1 (17<<3) /* reserved for local use */
This one. The actual one you use is arbitrary. But the facility and level you select are used in the syslog filtering (/etc/rsyslog.conf or equivalent) to choose what file the entry is filed in. In journalctl it is a single file, but you can filter the output: -p, --priority= Filter output by message priorities or priority ranges. Takes either a single numeric or textual log level (i.e. between 0/"emerg" and 7/"debug"), or a range of numeric/text log levels in the form FROM..TO. The log levels are the usual syslog log levels as documented in syslog(3), i.e. "emerg" (0), "alert" (1), "crit" (2), "err" (3), "warning" (4), "notice" (5), "info" (6), "debug" (7). If a single log level is specified, all messages with this log level or a lower (hence more important) log level are shown. If a range is specified, all messages within the range are shown, including both the start and the end value of the range. This will add "PRIORITY=" matches for the specified priorities. --facility= Filter output by syslog facility. Takes a comma-separated list of numbers or facility names. The names are the usual syslog facilities as documented in syslog(3). --facility=help may be used to display a list of known facility names and exit.
#define LOG_LOCAL2 (18<<3) /* reserved for local use */ #define LOG_LOCAL3 (19<<3) /* reserved for local use */
...
#!/bin/bash echo KBC0 >/proc/acpi/wakeup echo "Disabling wakeup in PS2 keyboard" >> /tmp/PS2-Keyboard.txt logger -t Mine -p local1.info "Disabling wakeup in PS2 keyboard" -
Certainly. Maybe "-t HP-PS2-Keyboard.sh", though. Up to you. :-) Yes, I made a somewhat dumb error (please see below for update). :[
It's nice to have this so functional now. Many Thanks
Welcome :-)
Ok, I really do not want to push my luck here with the great help you have provided so far but I really do want to ask a few more questions about this situation here with the keyboard. PS2-Keyboard.sh is changed to as follows: - Thinkcentre-M57p:/usr/local/sbin> cat PS2-Keyboard.sh #!/bin/bash echo KBC0 >/proc/acpi/wakeup echo "Disabling wakeup in PS2 keyboard" >> /tmp/PS2-Keyboard.txt echo logger -t PS2-Keyboard.sh -p local1.info "Disabling wakeup in PS2 keyboard"
No. logger -t PS2-Keyboard.sh -p local1.info "Disabling wakeup in PS2 keyboard" It is a command. Echo prints it, not runs it.
- Is, "echo logger -t PS2-Keyboard.sh -p local1.info "Disabling wakeup in PS2 keyboard" what i'm actually after here (for kernel alerts)?
I don't know what you are looking for "kernel alerts", I'm lost now. "logger" simply enters some arbitrary text into the system logs (and journal), so that the human administrator can read them and find out what was going on when.
and you will see that line printed in "journalctl" output.
I have powercycled the machine. Then complete two suspend/unsuspend cycles. Then in Konsole pass: journalctl | grep -i "PS2\|Keyboard"
Scrolling down to today's date. Shows what seems to me as somewhat sporatic results for: PS2-Keyboard.sh (meaning each time a suspend/unsuspend cycle completes), does not add a fresh log entry, (viewable in Konsole) even after journalctl | grep -i "PS2\|Keyboard" is passed yet again (after unsuspend completes). See sporatic displayed entry below.
You disabled the log entry by using "echo" in the line.
Feb 13 22:27:18 Thinkcentre-M57p PS2-Keyboard.sh[1820]: Disabling wakeup in PS2 keyboard
Why is a fresh entry of the above "PS2-Keyboard.sh[1820]: Disabling wakeup in PS2 Keyboard" not created every suspend/unsuspend cycle completion? ------------------------------------------------------------------------- Finally, there are many errors displayed (from one source) by journalctl output, about 'executable permissions' as follows:
Thinkcentre-M57p systemd[1]: Configuration file /etc/systemd/system/PS2-Keyboard.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Do as it says.
-rwxr-xr-x 1 root root 331 Feb 13 17:38 PS2-Keyboard.service
My mind starts thinking to pass the following: chmod ugo-x PS2-Keyboard.service
All the other directories *and* entries in /etc/systemd/system have 'ugo+x' permissions set. What's going on here with that?
Directories have +x, not files. The meaning of 'x' is different for directories. And links have all flags.
-------------------------------------------------------------------------- Is this thinking of mine correct about "PS2-Keyboard.service"? Can you suggest a journalctl command that could be more ideal in monitoring the keyboard messages, getting things set up?
Thanks again for your insight.
-- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 02-14-2024 06:56AM, Carlos E. R. wrote:
On 2024-02-14 07:45, -pj via openSUSE Users wrote:
On 02-13-2024 09:57PM, Carlos E. R. wrote:
On 2024-02-14 03:40, -pj via openSUSE Users wrote:
On 02-13-2024 04:49PM, Carlos E. R. wrote:
On 2024-02-13 23:34, -pj via openSUSE Users wrote:
On 02-13-2024 05:59AM, Carlos E. R. wrote: > On 2024-02-13 00:13, -pj via openSUSE Users wrote:
...
Trick:
logger -t Mine -p local1.info "The script works."
(local "one")
When you speak of "(local "one")" I do not understand what you are referring to very well. Can you please explain this a bit more perhaps?
That the "1" in the name is a one, not a lower case "L". There are local1, local2,...local7. I don't remember if more. I can give you tomorrow the rest of the names (I have to find them). See the man page. I apologize for not seeing the clarity which you presented in "(local "one")" initially. I for some reason was thinking something else was possibly meant by this.
Ah, found them: The syslog (2) on this machine here contains the similar if not same to displayed below. I was completely oblivious to the connection of syslog and journalctl output before. I see now there is a sort of connection at least.
Journal is a redesign of syslog, but many admins prefer syslog. You can have both.
#CER docs, from syslog(2)
#define KERN_EMERG "<0>" /* system is unusable */ Is this what you are refering to by "local1" (below)?
Below. It took me some time, long ago, to find the exact definitions. See *88* below. Ok I see.
#define KERN_ALERT "<1>" /* action must be taken immediately */
...
#/* other codes through 15 reserved for system use */ reserved for local use #define LOG_LOCAL0 (16<<3) /* reserved for local use */ #define LOG_LOCAL1 (17<<3) /* reserved for local use */
This one. I see, I was not looking closely enough again.
The actual one you use is arbitrary. But the facility and level you select are used in the syslog filtering (/etc/rsyslog.conf or equivalent) to choose what file the entry is filed in. Quick thought to ask you. Do you typically modify "/etc/rsyslog.conf"?
In journalctl it is a single file, but you can filter the output:
-p, --priority= Filter output by message priorities or priority ranges. Takes either a single numeric or textual log level (i.e. between 0/"emerg" and 7/"debug"), or a range of numeric/text log levels in the form FROM..TO. The log levels are the usual syslog log levels as documented in syslog(3), i.e. "emerg" (0), "alert" (1), "crit" (2), "err" (3), "warning" (4), "notice" (5), "info" (6), "debug" (7). If a single log level is specified, all messages with this log level or a lower (hence more important) log level are shown. If a range is specified, all messages within the range are shown, including both the start and the end value of the range. This will add "PRIORITY=" matches for the specified priorities.
This gets very detailed.
--facility= Filter output by syslog facility. Takes a comma-separated list of numbers or facility names. The names are the usual syslog facilities as documented in syslog(3). --facility=help may be used to display a list of known facility names and exit.
#define LOG_LOCAL2 (18<<3) /* reserved for local use */ #define LOG_LOCAL3 (19<<3) /* reserved for local use */
...
#!/bin/bash echo KBC0 >/proc/acpi/wakeup echo "Disabling wakeup in PS2 keyboard" >> /tmp/PS2-Keyboard.txt logger -t Mine -p local1.info "Disabling wakeup in PS2 keyboard" -
Certainly. Maybe "-t HP-PS2-Keyboard.sh", though. Up to you. :-) Yes, I made a somewhat dumb error (please see below for update). :[
It's nice to have this so functional now. Many Thanks
Welcome :-)
Thanks again. :|
Ok, I really do not want to push my luck here with the great help you have provided so far but I really do want to ask a few more questions about this situation here with the keyboard. PS2-Keyboard.sh is changed to as follows: - Thinkcentre-M57p:/usr/local/sbin> cat PS2-Keyboard.sh #!/bin/bash echo KBC0 >/proc/acpi/wakeup echo "Disabling wakeup in PS2 keyboard" >> /tmp/PS2-Keyboard.txt echo logger -t PS2-Keyboard.sh -p local1.info "Disabling wakeup in PS2 keyboard"
No.
logger -t PS2-Keyboard.sh -p local1.info "Disabling wakeup in PS2 keyboard"
It is a command. Echo prints it, not runs it.
You have clarified my mind on this and again, thank you. I have made the critical needed adjustments and saved file, /usr/local/sbin/PS2-Keyboard.sh as follows: #!/bin/bash echo KBC0 >/proc/acpi/wakeup echo "Disabling wakeup in PS2 keyboard" >> /tmp/PS2-Keyboard.txt logger -t PS2-Keyboard.sh -p local1.info "Disabling wakeup in PS2 keyboard" Current Permissions for the file: -rwxr-xr-x 1 root root 182 Feb 14 14:55 PS2-Keyboard.sh
- Is, "echo logger -t PS2-Keyboard.sh -p local1.info "Disabling wakeup in PS2 keyboard" what i'm actually after here (for kernel alerts)?
I don't know what you are looking for "kernel alerts", I'm lost now.
Do not be lost please. I was once again mistaken in the above comment. It was referring to my incorrect thought on.> #define KERN_ALERT "<1>" /* action must be taken immediately */ Please see *88* above.
"logger" simply enters some arbitrary text into the system logs (and journal), so that the human administrator can read them and find out what was going on when.
Ok, very good explanation.
and you will see that line printed in "journalctl" output.
I have powercycled the machine. Then complete two suspend/unsuspend cycles. Then in Konsole pass: journalctl | grep -i "PS2\|Keyboard"
Scrolling down to today's date. Shows what seems to me as somewhat sporatic results for: PS2-Keyboard.sh (meaning each time a suspend/unsuspend cycle completes), does not add a fresh log entry, (viewable in Konsole) even after journalctl | grep -i "PS2\|Keyboard" is passed yet again (after unsuspend completes). See sporatic displayed entry below.
You disabled the log entry by using "echo" in the line.
Yes, I have corrected that "echo" mistake now, please see above. I have also altered the journalctl syntax being used to the following: journalctl -b -1 | grep "PS2\|Keyboard" now. Is this similar to what you would recommend?>
Feb 13 22:27:18 Thinkcentre-M57p PS2-Keyboard.sh[1820]: Disabling wakeup in PS2 keyboard
Why is a fresh entry of the above "PS2-Keyboard.sh[1820]: Disabling wakeup in PS2 Keyboard" not created every suspend/unsuspend cycle completion? ------------------------------------------------------------------------- Finally, there are many errors displayed (from one source) by journalctl output, about 'executable permissions' as follows:
Thinkcentre-M57p systemd[1]: Configuration file /etc/systemd/system/PS2-Keyboard.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Do as it says.
I have done as it says with the current permissions set now to the following: -rw-r--r-- 1 root root 331 Feb 13 17:38 PS2-Keyboard.service
-rwxr-xr-x 1 root root 331 Feb 13 17:38 PS2-Keyboard.service
My mind starts thinking to pass the following: chmod ugo-x PS2-Keyboard.service
All the other directories *and* entries in /etc/systemd/system have 'ugo+x' permissions set. What's going on here with that?
Directories have +x, not files. The meaning of 'x' is different for directories. And links have all flags.
Thinking back I did make PS2-Keyboard.service executable after creating the file that was obviously a mistake which I corrected now. -Best Regards :|
On 2024-02-14 22:17, -pj via openSUSE Users wrote:
On 02-14-2024 06:56AM, Carlos E. R. wrote:
On 2024-02-14 07:45, -pj via openSUSE Users wrote:
On 02-13-2024 09:57PM, Carlos E. R. wrote:
On 2024-02-14 03:40, -pj via openSUSE Users wrote:
On 02-13-2024 04:49PM, Carlos E. R. wrote:
On 2024-02-13 23:34, -pj via openSUSE Users wrote: > On 02-13-2024 05:59AM, Carlos E. R. wrote: >> On 2024-02-13 00:13, -pj via openSUSE Users wrote:
...
Trick:
logger -t Mine -p local1.info "The script works."
(local "one")
When you speak of "(local "one")" I do not understand what you are referring to very well. Can you please explain this a bit more perhaps?
That the "1" in the name is a one, not a lower case "L". There are local1, local2,...local7. I don't remember if more. I can give you tomorrow the rest of the names (I have to find them). See the man page. I apologize for not seeing the clarity which you presented in "(local "one")" initially. I for some reason was thinking something else was possibly meant by this.
Ah, found them: The syslog (2) on this machine here contains the similar if not same to displayed below. I was completely oblivious to the connection of syslog and journalctl output before. I see now there is a sort of connection at least.
Journal is a redesign of syslog, but many admins prefer syslog. You can have both.
#CER docs, from syslog(2)
#define KERN_EMERG "<0>" /* system is unusable */ Is this what you are refering to by "local1" (below)?
Below. It took me some time, long ago, to find the exact definitions. See *88* below. Ok I see.
#define KERN_ALERT "<1>" /* action must be taken immediately */
...
#/* other codes through 15 reserved for system use */ reserved for local use #define LOG_LOCAL0 (16<<3) /* reserved for local use */ #define LOG_LOCAL1 (17<<3) /* reserved for local use */
This one. I see, I was not looking closely enough again.
Notice that what is important is the names. That there are "syslog facilities" named "local0, local1, ..., local7. And others. I did not find a man page listing the exact names of all the facilities and priorities, what I found were the source definition names, which are similar but not exactly the same. So the source has "KERN_ALERT", but the actual name you can use is "alert". ...
You disabled the log entry by using "echo" in the line.
Yes, I have corrected that "echo" mistake now, please see above. I have also altered the journalctl syntax being used to the following: journalctl -b -1 | grep "PS2\|Keyboard" now. Is this similar to what you would recommend?>
Yes. Possibly you can also search for this one faster: -t, --identifier=SYSLOG_IDENTIFIER Show messages for the specified syslog identifier SYSLOG_IDENTIFIER. This parameter can be specified multiple times. Which I /think/ corresponds to the -t in logger: logger -t PS2-Keyboard.sh -p local1.info "Disabling wakeup in PS2 keyboard" -t, --tag tag Mark every line to be logged with the specified tag. The default tag is the name of the user logged in on the terminal (or a user name based on effective user ID). ... -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 02-14-2024 03:40PM, Carlos E. R. wrote:
On 2024-02-14 22:17, -pj via openSUSE Users wrote:
On 02-14-2024 06:56AM, Carlos E. R. wrote:
On 2024-02-14 07:45, -pj via openSUSE Users wrote:
On 02-13-2024 09:57PM, Carlos E. R. wrote:
On 2024-02-14 03:40, -pj via openSUSE Users wrote:
On 02-13-2024 04:49PM, Carlos E. R. wrote: > On 2024-02-13 23:34, -pj via openSUSE Users wrote: >> On 02-13-2024 05:59AM, Carlos E. R. wrote: >>> On 2024-02-13 00:13, -pj via openSUSE Users wrote:
...
> Trick: > > > logger -t Mine -p local1.info "The script works." > > (local "one")
When you speak of "(local "one")" I do not understand what you are referring to very well. Can you please explain this a bit more perhaps?
That the "1" in the name is a one, not a lower case "L". There are local1, local2,...local7. I don't remember if more. I can give you tomorrow the rest of the names (I have to find them). See the man page. I apologize for not seeing the clarity which you presented in "(local "one")" initially. I for some reason was thinking something else was possibly meant by this.
Ah, found them: The syslog (2) on this machine here contains the similar if not same to displayed below. I was completely oblivious to the connection of syslog and journalctl output before. I see now there is a sort of connection at least.
Journal is a redesign of syslog, but many admins prefer syslog. You can have both.
#CER docs, from syslog(2)
#define KERN_EMERG "<0>" /* system is unusable */ Is this what you are refering to by "local1" (below)?
Below. It took me some time, long ago, to find the exact definitions. See *88* below. Ok I see.
#define KERN_ALERT "<1>" /* action must be taken immediately */
...
#/* other codes through 15 reserved for system use */ reserved for local use #define LOG_LOCAL0 (16<<3) /* reserved for local use */ #define LOG_LOCAL1 (17<<3) /* reserved for local use */
This one. I see, I was not looking closely enough again.
Notice that what is important is the names. That there are "syslog facilities" named "local0, local1, ..., local7. And others.
I did not find a man page listing the exact names of all the facilities and priorities, what I found were the source definition names, which are similar but not exactly the same. So the source has "KERN_ALERT", but the actual name you can use is "alert".
... Ok
You disabled the log entry by using "echo" in the line.
Yes, I have corrected that "echo" mistake now, please see above. I have also altered the journalctl syntax being used to the following: journalctl -b -1 | grep "PS2\|Keyboard" now. Is this similar to what you would recommend?>
Yes.
Possibly you can also search for this one faster:
-t, --identifier=SYSLOG_IDENTIFIER Show messages for the specified syslog identifier SYSLOG_IDENTIFIER.
This parameter can be specified multiple times.
Which I /think/ corresponds to the -t in logger:
logger -t PS2-Keyboard.sh -p local1.info "Disabling wakeup in PS2 keyboard"
-t, --tag tag Mark every line to be logged with the specified tag. The default tag is the name of the user logged in on the terminal (or a user name based on effective user ID).
... Ok
I believe the configuration is functioning now to how it has been set up now.
Thinkcentre-M57p:/tmp> journalctl -b -0 | grep "PS2\|Keyboard\|keyboard" Feb 14 18:57:57 Thinkcentre-M57p kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0 Feb 14 18:58:14 Thinkcentre-M57p systemd[1]: Starting Apply settings from /etc/sysconfig/keyboard... Feb 14 18:58:15 Thinkcentre-M57p systemd[1]: Finished Apply settings from /etc/sysconfig/keyboard. Feb 14 18:58:16 Thinkcentre-M57p systemd-logind[1265]: Watching system buttons on /dev/input/event0 (AT Translated Set 2 keyboard) Feb 14 18:58:24 Thinkcentre-M57p display-manager[1797]: XKBLAYOUT is already set. Better don't touch X11 keyboard configuration. Feb 14 18:58:24 Thinkcentre-M57p systemd[1]: Starting Disable PS/2 style keyboard power when sleep state is envoked on this machine... Feb 14 18:58:24 Thinkcentre-M57p PS2-Keyboard.sh[1806]: Disabling wakeup in PS2 keyboard Feb 14 18:58:24 Thinkcentre-M57p systemd[1]: Finished Disable PS/2 style keyboard power when sleep state is envoked on this machine. Feb 14 18:58:33 Thinkcentre-M57p sddm-greeter[1839]: Hunspell dictionary is missing for "en_GB" . Search paths ("/usr/share/qt5/qtvirtualkeyboard/hunspell", "/usr/share/hunspell", "/usr/share/myspell/dicts") Feb 14 18:59:23 Thinkcentre-M57p kscreenlocker_greet[3498]: qt.virtualkeyboard.hunspell: Hunspell dictionary is missing for "en_GB" . Search paths ("/usr/share/qt5/qtvirtualkeyboard/hunspell", "/usr/share/hunspell", "/usr/share/myspell/dicts") Feb 14 18:59:50 Thinkcentre-M57p kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input13 Feb 14 18:59:50 Thinkcentre-M57p systemd-logind[1265]: Watching system buttons on /dev/input/event0 (AT Translated Set 2 keyboard) Feb 14 19:09:54 Thinkcentre-M57p kscreenlocker_greet[4095]: qt.virtualkeyboard.hunspell: Hunspell dictionary is missing for "en_GB" . Search paths ("/usr/share/qt5/qtvirtualkeyboard/hunspell", "/usr/share/hunspell", "/usr/share/myspell/dicts") Feb 14 19:12:33 Thinkcentre-M57p kscreenlocker_greet[4912]: qt.virtualkeyboard.hunspell: Hunspell dictionary is missing for "en_GB" . Search paths ("/usr/share/qt5/qtvirtualkeyboard/hunspell", "/usr/share/hunspell", "/usr/share/myspell/dicts") Thinkcentre-M57p:/tmp>
Feb 14 18:58:24 Thinkcentre-M57p PS2-Keyboard.sh[1806]: Disabling wakeup in PS2 keyboard What is the [1806] meaning? If I suspend/unsuspend multiple times within a brief period of time. how do I get the logs from that action? Additional information does not display in Konsole for the additional suspend/unsuspend cycles when passing: journalctl -b -1 | grep "PS2\|Keyboard\|keyboard" (I have not powercycled since then either). -Regards
On 2024-02-15 02:29, -pj via openSUSE Users wrote:
On 02-14-2024 03:40PM, Carlos E. R. wrote:
On 2024-02-14 22:17, -pj via openSUSE Users wrote:
On 02-14-2024 06:56AM, Carlos E. R. wrote:
On 2024-02-14 07:45, -pj via openSUSE Users wrote:
On 02-13-2024 09:57PM, Carlos E. R. wrote:
On 2024-02-14 03:40, -pj via openSUSE Users wrote: > On 02-13-2024 04:49PM, Carlos E. R. wrote: >> On 2024-02-13 23:34, -pj via openSUSE Users wrote: >>> On 02-13-2024 05:59AM, Carlos E. R. wrote: >>>> On 2024-02-13 00:13, -pj via openSUSE Users wrote:
...
Possibly you can also search for this one faster:
-t, --identifier=SYSLOG_IDENTIFIER Show messages for the specified syslog identifier SYSLOG_IDENTIFIER.
This parameter can be specified multiple times.
Which I /think/ corresponds to the -t in logger:
logger -t PS2-Keyboard.sh -p local1.info "Disabling wakeup in PS2 keyboard"
-t, --tag tag Mark every line to be logged with the specified tag. The default tag is the name of the user logged in on the terminal (or a user name based on effective user ID).
... Ok
I believe the configuration is functioning now to how it has been set up now.
The test would be that: journalctl -t PS2-Keyboard.sh should find all the entries, if I am correct. ...
Feb 14 19:12:33 Thinkcentre-M57p kscreenlocker_greet[4912]: qt.virtualkeyboard.hunspell: Hunspell dictionary is missing for "en_GB" . Search paths ("/usr/share/qt5/qtvirtualkeyboard/hunspell", "/usr/share/hunspell", "/usr/share/myspell/dicts") Thinkcentre-M57p:/tmp>
Feb 14 18:58:24 Thinkcentre-M57p PS2-Keyboard.sh[1806]: Disabling wakeup in PS2 keyboard
What is the [1806] meaning?
The PDI of the process.
If I suspend/unsuspend multiple times within a brief period of time. how do I get the logs from that action? Additional information does not display in Konsole for the additional suspend/unsuspend cycles when passing: journalctl -b -1 | grep "PS2\|Keyboard\|keyboard" (I have not powercycled since then either).
No, this service only runs once after boot. If you want that, it is a different one. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 14.02.2024 01:34, -pj via openSUSE Users wrote:
Thinkcentre-M57p:/etc/systemd/system> ls -lah -rwxr-xr-x 1 root root 312 Feb 13 15:15 HP-PS2-Keyboard.service ...
ExecStart=-/usr/sbin/HP-PS2-Keyboard.sh ... Thinkcentre-M57p:/usr/sbin> cat HP-PS2-Keyboard.sh #!/bin/bash echo KBC0 >/proc/acpi/wakeup ...
No service is needed. echo 'w! /proc/acpi/wakeup - - - - KBC0` > /etc/tmpfiles.d/HP-PS2-Keyboard.conf That's all.
On 02-13-2024 11:42PM, Andrei Borzenkov wrote:
On 14.02.2024 01:34, -pj via openSUSE Users wrote:
Thinkcentre-M57p:/etc/systemd/system> ls -lah -rwxr-xr-x 1 root root 312 Feb 13 15:15 HP-PS2-Keyboard.service ...
ExecStart=-/usr/sbin/HP-PS2-Keyboard.sh ... Thinkcentre-M57p:/usr/sbin> cat HP-PS2-Keyboard.sh #!/bin/bash echo KBC0 >/proc/acpi/wakeup ...
No service is needed.
echo 'w! /proc/acpi/wakeup - - - - KBC0` > /etc/tmpfiles.d/HP-PS2-Keyboard.conf
That's all.
This appears to be very easy to implement indeed. Can you tell me how you found out about this? - The /etc/tmpfiles.d/ directory is empty by default I believe (as is here). Is this folder read by default during boot? Can you tell me what this directory is mainly set to be used for? Obviously you suggest the above. Is there a recommended way to disable the command if eventually a configuration is changed or something like that? - The openSUSE wiki does not seem to have much of anything on PS/2 keyboards from my search. Do you think even though PS/2 keyboard is not very popular now that it would help to put a wiki page in there? -Thanks
On Wed, 14 Feb 2024 17:01:53 -0600 -pj via openSUSE Users <users@lists.opensuse.org> wrote:
On 02-13-2024 11:42PM, Andrei Borzenkov wrote:
No service is needed.
echo 'w! /proc/acpi/wakeup - - - - KBC0` > /etc/tmpfiles.d/HP-PS2-Keyboard.conf
That's all.
This appears to be very easy to implement indeed. Can you tell me how you found out about this? - The /etc/tmpfiles.d/ directory is empty by default I believe (as is here). Is this folder read by default during boot? Can you tell me what this directory is mainly set to be used for? Obviously you suggest the above. Is there a recommended way to disable the command if eventually a configuration is changed or something like that?
Have you tried google? The first hit is https://www.freedesktop.org/software/systemd/man/devel/tmpfiles.d.html which seems like a good place to start.
The openSUSE wiki does not seem to have much of anything on PS/2 keyboards from my search. Do you think even though PS/2 keyboard is not very popular now that it would help to put a wiki page in there?
-Thanks
-pj composed on 2024-02-12 17:13 (UTC-0600):
/etc/rc.local is not shown in the current filesystem, maybe because it was system IV related.
/etc/*.local are optional files that an admin may choose to create to add to or modify the defaults provided by a corresponding /etc/*. or /usr/etc/*. file. Typically it is preferred to create a systemd unit file instead of an /etc/*.local file, as support for the particular /etc/*.local file may be discontinued in the future. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Hello, In the Message; Subject : HP PS/2 style keyboard preventing suspend: Message-ID : <9d9c81e4-32ab-456b-9b8f-0a24f58eac38@gmx.com> Date & Time: Mon, 12 Feb 2024 14:27:22 -0600 [-pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written: -pj> I have openSUSE Tumbleweed running on this machine. I had attached a USB -pj> wireless HP keyboard to the machine and suspend worked well from what I -pj> could tell (the machine went to sleep and resumed when asked). The issue -pj> is the keyboard is/was not taking keystrokes correctly, quite alot of -pj> the time. It became very very frustrating for me to use. It seems -pj> sometimes freshly charged Panasonic Eneloop batteries may help a little -pj> but is unknown for certain still. -pj> When an older HP PS/2 style keyboard is attached to the machine. It’s -pj> solid and never misses a keystroke. :~> /usr/sbin/hwinfo --keyboard -pj> 25: PS/2 00.0: 10800 Keyboard -pj> [Created at input.226] -pj> Unique ID: nLyy.+49ps10DtUF -pj> Hardware Class: keyboard -pj> Model: "AT Translated Set 2 keyboard" -pj> Vendor: 0x0001 -pj> Device: 0x0001 "AT Translated Set 2 keyboard" -pj> Compatible to: int 0x0211 0x0001 -pj> Device File: /dev/input/event0 -pj> Device Files: /dev/input/event0, -pj> /dev/input/by-path/platform-i8042-serio-0-event-kbd -pj> Device Number: char 13:64 -pj> Driver Info #0: -pj> XkbRules: xfree86 -pj> XkbModel: pc104 -pj> Config Status: cfg=no, avail=yes, need=no, active=unknown -pj> :~> [...] -pj> Is this somehow related something 'udevadm' would help track -pj> down at all? Could you show the result of; $ cat /sys/module/usbcore/parameters/autosuspend Kind Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "As Google fights for positioning in a new AI boom and an era where some consumers are turning to TikTok or ChatGPT instead of Google Search, some employees now worry product development could become dangerously hasty. The restructuring of RESIN has increased those concerns, the sources say." -- Google Splits Up a Key AI Ethics Watchdog --
Hello, In the Message; Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <513bae0f-eb2a-406b-959c-3bcf23e6199a@gmx.com> Date & Time: Tue, 13 Feb 2024 20:53:57 -0600 [-pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written: -pj> On 02-13-2024 08:48PM, Masaru Nomiya wrote: -pj> > cat /sys/module/usbcore/parameters/autosuspend -pj> Yes absolutely, -pj> cat /sys/module/usbcore/parameters/autosuspend -pj> 2 Thanks. Please try as follows; 1. remove all your added *.service files 2. 2-1. edit /etc/default/grub as follows; GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1" 2-2. # grub2-mkconfig -o /boot/grub2/grub 3．reboot How about this? Best Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Maddox hopes that empowering users to pick their own algorithms will get them to think more about what’s involved in making them. " -- Bluesky's Custom Algorithms Could Be the Future of Social Media --
On 02-13-2024 09:03PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <513bae0f-eb2a-406b-959c-3bcf23e6199a@gmx.com> Date & Time: Tue, 13 Feb 2024 20:53:57 -0600
[-pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written:
-pj> On 02-13-2024 08:48PM, Masaru Nomiya wrote: -pj> > cat /sys/module/usbcore/parameters/autosuspend
-pj> Yes absolutely,
-pj> cat /sys/module/usbcore/parameters/autosuspend -pj> 2
Thanks.
Please try as follows;
1. remove all your added *.service files
2.
2-1. edit /etc/default/grub as follows;
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1"
2-2.
# grub2-mkconfig -o /boot/grub2/grub Are you certain of this? In Tumbleweed I thought: # update-bootloader --refresh
3．reboot
How about this? I will attempt this.
Best Regards.
--- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Maddox hopes that empowering users to pick their own algorithms will get them to think more about what’s involved in making them. "
-- Bluesky's Custom Algorithms Could Be the Future of Social Media --
On 02-13-2024 09:10PM, -pj via openSUSE Users wrote:
On 02-13-2024 09:03PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <513bae0f-eb2a-406b-959c-3bcf23e6199a@gmx.com> Date & Time: Tue, 13 Feb 2024 20:53:57 -0600
[-pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written:
-pj> On 02-13-2024 08:48PM, Masaru Nomiya wrote: -pj> > cat /sys/module/usbcore/parameters/autosuspend
-pj> Yes absolutely,
-pj> cat /sys/module/usbcore/parameters/autosuspend -pj> 2
Thanks.
Please try as follows;
1. remove all your added *.service files
2.
2-1. edit /etc/default/grub as follows;
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1"
Ok, I have performed the following steps here so far. - 1. Backed up /etc/default/grub to /etc/default/grub.bak 2. Edited /etc/default/grub as follows: GRUB_CMDLINE_LINUX_DEFAULT="resume=/dev/system/swap nosimplefb=1 splash=0 plymouth.enable=0 mitigations=auto usbcore.autosuspend=-1" 3. saved the file. 4. # update-bootloader --refresh 5. # systemctl disable PS2-Keyboard.service 6. # systemctl status PS2-Keyboard.service
PS2-Keyboard.service - Disable PS/2 style keyboard power when sleep state is envoked on this machine Loaded: loaded (/etc/systemd/system/PS2-Keyboard.service; disabled; preset: disabled) Active: active (exited) since Tue 2024-02-13 19:10:50 CST; 2h 16min ago Main PID: 1825 (code=exited, status=0/SUCCESS) CPU: 4ms
Feb 13 19:10:50 paul-Thinkcentre-M57p systemd[1]: Starting Disable PS/2 style keyboard power when sleep state is envoked on this machine... Feb 13 19:10:50 paul-Thinkcentre-M57p systemd[1]: Finished Disable PS/2 style keyboard power when sleep state is envoked on this machine.
7. Waiting for a 'zypper dup' to complete 8. Will powercycle the machine now. 9. Logged into KDE, waited for everything to load. 10. No joy, when system sleep is attempted. Monitor shuts off with machines PSU still active. 11. I have attached a screenshot to display current PS2-Keyboard.service *and* acpi wakeup status in my response located here: https://paste.opensuse.org/pastes/bbcca3133fd2 12. What are your thoughts about this situation? -Thanks
Hello, Sorry for very late reply. Today was the day to go to the hospital for the case I had the other day. In the Message; Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <271805dc-d353-4681-8915-4343f71cd70c@gmx.com> Date & Time: Tue, 13 Feb 2024 21:53:54 -0600 [pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written: [...] pj> 6. # systemctl status PS2-Keyboard.service pj> > PS2-Keyboard.service - Disable PS/2 style keyboard power when sleep state is envoked on this machine pj> > Loaded: loaded (/etc/systemd/system/PS2-Keyboard.service; disabled; preset: disabled) pj> > Active: active (exited) since Tue 2024-02-13 19:10:50 CST; 2h 16min ago pj> > Main PID: 1825 (code=exited, status=0/SUCCESS) pj> > CPU: 4ms pj> > pj> > Feb 13 19:10:50 paul-Thinkcentre-M57p systemd[1]: Starting Disable PS/2 style keyboard power when sleep state is envoked on this machine... pj> > Feb 13 19:10:50 paul-Thinkcentre-M57p systemd[1]: Finished Disable PS/2 style keyboard power when sleep state is envoked on this machine. Hmm...? how me this result after the reboot; # systemctl status PS2-Keyboard.service Kind Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "In his book Survival of the Richest, media theorist Douglass Rushkoff describes meeting with a group of billionaire preppers who bombarded him with questions about how best to configure their bunkers to survive the end times." -- Inside Mark Zuckerberg’s Top-Secret Hawaii Compound --
Hello,
Sorry for very late reply.
Today was the day to go to the hospital for the case I had the other day. My apologies for your hospital visit. on January 4 2004 my clean 2001 Toyota Camry was rearended, in the middle of a 4 car pileup. I went to
On 02-14-2024 03:14AM, Masaru Nomiya wrote: the hospital for scanning. I now go to physical therapy and mental health counseling.
In the Message;
Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <271805dc-d353-4681-8915-4343f71cd70c@gmx.com> Date & Time: Tue, 13 Feb 2024 21:53:54 -0600
[pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written:
[...] pj> 6. # systemctl status PS2-Keyboard.service pj> > PS2-Keyboard.service - Disable PS/2 style keyboard power when sleep state is envoked on this machine pj> > Loaded: loaded (/etc/systemd/system/PS2-Keyboard.service; disabled; preset: disabled) pj> > Active: active (exited) since Tue 2024-02-13 19:10:50 CST; 2h 16min ago pj> > Main PID: 1825 (code=exited, status=0/SUCCESS) pj> > CPU: 4ms pj> > pj> > Feb 13 19:10:50 paul-Thinkcentre-M57p systemd[1]: Starting Disable PS/2 style keyboard power when sleep state is envoked on this machine... pj> > Feb 13 19:10:50 paul-Thinkcentre-M57p systemd[1]: Finished Disable PS/2 style keyboard power when sleep state is envoked on this machine.
Hmm...?
how me this result after the reboot;
# systemctl status PS2-Keyboard.service
After powercycle: - systemctl status PS2-Keyboard.service ○ PS2-Keyboard.service - Disable PS/2 style keyboard power when sleep state is envoked on this machine Loaded: loaded (/etc/systemd/system/PS2-Keyboard.service; disabled; preset: disabled) Active: inactive (dead) - cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.7.4-1-default root=/dev/mapper/system-root resume=/dev/system/swap nosimplefb=1 splash=0 plymouth.enable=0 mitigations=auto quiet splash usbcore.autosuspend=-1 PSU keeps running when sleep is envoked. -Best Wishes
Hello, In the Message; Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <d4e70dde-2403-47dc-98e7-49dea8a763b3@gmx.com> Date & Time: Wed, 14 Feb 2024 16:06:39 -0600 [pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written: [...] pj> > # systemctl status PS2-Keyboard.service pj> After powercycle: pj> - pj> systemctl status PS2-Keyboard.service pj> ○ PS2-Keyboard.service - Disable PS/2 style keyboard power when sleep pj> state is envoked on this machine pj> Loaded: loaded (/etc/systemd/system/PS2-Keyboard.service; pj> disabled; preset: disabled) pj> Active: inactive (dead) pj> - pj> cat /proc/cmdline pj> BOOT_IMAGE=/boot/vmlinuz-6.7.4-1-default root=/dev/mapper/system-root pj> resume=/dev/system/swap nosimplefb=1 splash=0 plymouth.enable=0 pj> mitigations=auto quiet splash usbcore.autosuspend=-1 pj> PSU keeps running when sleep is envoked. Thanks. Please show the result of this; $ cat /sys/module/usbcore/parameters/autosuspend $ ls /etc/modprobe.d/disable-usb-autosuspend.conf Best Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Maddox hopes that empowering users to pick their own algorithms will get them to think more about what’s involved in making them. " -- Bluesky's Custom Algorithms Could Be the Future of Social Media --
On 2024-02-15 00:56, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <d4e70dde-2403-47dc-98e7-49dea8a763b3@gmx.com> Date & Time: Wed, 14 Feb 2024 16:06:39 -0600
[pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written:
[...] pj> > # systemctl status PS2-Keyboard.service
pj> After powercycle: pj> - pj> systemctl status PS2-Keyboard.service
pj> ○ PS2-Keyboard.service - Disable PS/2 style keyboard power when sleep pj> state is envoked on this machine pj> Loaded: loaded (/etc/systemd/system/PS2-Keyboard.service; pj> disabled; preset: disabled) pj> Active: inactive (dead) pj> - pj> cat /proc/cmdline
pj> BOOT_IMAGE=/boot/vmlinuz-6.7.4-1-default root=/dev/mapper/system-root pj> resume=/dev/system/swap nosimplefb=1 splash=0 plymouth.enable=0 pj> mitigations=auto quiet splash usbcore.autosuspend=-1
pj> PSU keeps running when sleep is envoked.
Thanks.
Please show the result of this;
$ cat /sys/module/usbcore/parameters/autosuspend
$ ls /etc/modprobe.d/disable-usb-autosuspend.conf
Remember his keyboard is not on USB. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
Hello, In the Message; Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <0ad872d7-a427-4553-83ac-228b015f40f0@telefonica.net> Date & Time: Thu, 15 Feb 2024 01:07:10 +0100 [CER] == "Carlos E. R." <robin.listas@telefonica.net> has written: CER> [1 <multipart/mixed (7bit)>] CER> [1.1 <text/plain; UTF-8 (base64)>] CER> On 2024-02-15 00:56, Masaru Nomiya wrote: [...] CER> > Please show the result of this; CER> > CER> > $ cat /sys/module/usbcore/parameters/autosuspend CER> > CER> > $ ls /etc/modprobe.d/disable-usb-autosuspend.conf CER> Remember his keyboard is not on USB. Thanks, Carlos. I was totally mistaken. (^^;; He has got the i8042 controller's bug. How about this? 1. edit the /etc/default/grub as follows: 1-1. remove 'usbcore.autosuspend=-1' entry. 1-2. add the 'i8042.nomux=1 i8042.reset' entry, instead. 2. # update-bootloader --refresh where PS2-Keyboard.service is still disabled. Kind Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Companies have come to view generative AI as a kind of monster that must be fed at all costs―even if it isn’t always clear what exactly that data is needed for or what those future AI systems might end up doing." -- Generative AI Is Making Companies Even More Thirsty for Your Data --
On 02-14-2024 07:45PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <0ad872d7-a427-4553-83ac-228b015f40f0@telefonica.net> Date & Time: Thu, 15 Feb 2024 01:07:10 +0100
[CER] == "Carlos E. R." <robin.listas@telefonica.net> has written:
CER> [1 <multipart/mixed (7bit)>] CER> [1.1 <text/plain; UTF-8 (base64)>] CER> On 2024-02-15 00:56, Masaru Nomiya wrote: [...] CER> > Please show the result of this; CER> > CER> > $ cat /sys/module/usbcore/parameters/autosuspend CER> > CER> > $ ls /etc/modprobe.d/disable-usb-autosuspend.conf
CER> Remember his keyboard is not on USB.
Thanks, Carlos.
I was totally mistaken. (^^;;
He has got the i8042 controller's bug.
How about this?
1. edit the /etc/default/grub as follows:
1-1. remove 'usbcore.autosuspend=-1' entry. 1-2. add the 'i8042.nomux=1 i8042.reset' entry, instead.
2.
# update-bootloader --refresh
I completed the above suggestions then powercycled the machine: cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.7.4-1-default root=/dev/mapper/system-root resume=/dev/system/swap nosimplefb=1 splash=0 plymouth.enable=0 mitigations=auto i8042.nomux=1 i8042.reset
where PS2-Keyboard.service is still disabled.
systemctl status PS2-Keyboard.service ○ PS2-Keyboard.service - Disable PS/2 style keyboard power when sleep state is envoked on this machine Loaded: loaded (/etc/systemd/system/PS2-Keyboard.service; disabled; preset: disabled) Active: inactive (dead) Thinkcentre-M57p:/tmp> - I attempted to suspend the machine. The machine suspended and PSU turned off. I pressed power button and machine powered on and I logged into KDE. :] - This is excellent work. Please note: It seems like possibly an open window application in a workspace could have/be, been jamming the suspend process up. I minimized the running application processes in 1 of the 2 currently used workspaces and suspend completed without incident. Since I have have implemented the above suggestion, I have had suspend fail to follow through and display message output in TTY and revert back to SDDM window. I logged into KDE and then attempted suspend again, then same events. I was going to take a photo of the messages but cannot with suspend completing. Are you aware of something like this occuring previously (in other cases) by chance? -Best Wishes
On 02-14-2024 08:17PM, -pj via openSUSE Users wrote:
On 02-14-2024 07:45PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <0ad872d7-a427-4553-83ac-228b015f40f0@telefonica.net> Date & Time: Thu, 15 Feb 2024 01:07:10 +0100
[CER] == "Carlos E. R." <robin.listas@telefonica.net> has written:
CER> [1 <multipart/mixed (7bit)>] CER> [1.1 <text/plain; UTF-8 (base64)>] CER> On 2024-02-15 00:56, Masaru Nomiya wrote: [...] CER> > Please show the result of this; CER> > CER> > $ cat /sys/module/usbcore/parameters/autosuspend CER> > CER> > $ ls /etc/modprobe.d/disable-usb-autosuspend.conf
CER> Remember his keyboard is not on USB.
Thanks, Carlos.
I was totally mistaken. (^^;;
He has got the i8042 controller's bug.
How about this?
1. edit the /etc/default/grub as follows:
1-1. remove 'usbcore.autosuspend=-1' entry. 1-2. add the 'i8042.nomux=1 i8042.reset' entry, instead.
2.
# update-bootloader --refresh
I completed the above suggestions then powercycled the machine:
cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.7.4-1-default root=/dev/mapper/system-root resume=/dev/system/swap nosimplefb=1 splash=0 plymouth.enable=0 mitigations=auto i8042.nomux=1 i8042.reset
where PS2-Keyboard.service is still disabled.
systemctl status PS2-Keyboard.service ○ PS2-Keyboard.service - Disable PS/2 style keyboard power when sleep state is envoked on this machine Loaded: loaded (/etc/systemd/system/PS2-Keyboard.service; disabled; preset: disabled) Active: inactive (dead) Thinkcentre-M57p:/tmp> - I attempted to suspend the machine. The machine suspended and PSU turned off. I pressed power button and machine powered on and I logged into KDE. :] - This is excellent work.
Please note: It seems like possibly an open window application in a workspace could have/be, been jamming the suspend process up. I minimized the running application processes in 1 of the 2 currently used workspaces and suspend completed without incident. Since I have have implemented the above suggestion, I have had suspend fail to follow through and display message output in TTY and revert back to SDDM window. I logged into KDE and then attempted suspend again, then same events. I was going to take a photo of the messages but cannot with suspend completing. Are you aware of something like this occuring previously (in other cases) by chance?
Hi, after my last message I decided to powercycle the machine and it *locked* for over 2 minutes (then I hard reset with power button). I have attached a photo to imgbb of the displayed errors: https://ibb.co/H4tttXv -Thanks
Hello, In the Message; Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <6f6c15da-bbaf-43d3-a283-c32098517b5b@gmx.com> Date & Time: Wed, 14 Feb 2024 20:42:41 -0600 [pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written: [...] pj> > Please note: It seems like possibly an open window application in a pj> > workspace could have/be, been jamming the suspend process up. I pj> > minimized the running application processes in 1 of the 2 currently used pj> > workspaces and suspend completed without incident. Since I have have pj> > implemented the above suggestion, I have had suspend fail to follow pj> > through and display message output in TTY and revert back to SDDM pj> > window. I logged into KDE and then attempted suspend again, then same pj> > events. I was going to take a photo of the messages but cannot with pj> > suspend completing. Are you aware of something like this occuring pj> > previously (in other cases) by chance? pj> > pj> Hi, after my last message I decided to powercycle the machine and it pj> *locked* for over 2 minutes (then I hard reset with power button). pj> I have attached a photo to imgbb of the displayed errors: pj> https://ibb.co/H4tttXv I suspect memory but did you run memtest86+? In this case, you should check the /var/log/messages. If you are lucky, you may find the cause. Kind Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "As Google fights for positioning in a new AI boom and an era where some consumers are turning to TikTok or ChatGPT instead of Google Search, some employees now worry product development could become dangerously hasty. The restructuring of RESIN has increased those concerns, the sources say." -- Google Splits Up a Key AI Ethics Watchdog --
On 02-15-2024 05:42PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <6f6c15da-bbaf-43d3-a283-c32098517b5b@gmx.com> Date & Time: Wed, 14 Feb 2024 20:42:41 -0600
[pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written:
[...] pj> > Please note: It seems like possibly an open window application in a pj> > workspace could have/be, been jamming the suspend process up. I pj> > minimized the running application processes in 1 of the 2 currently used pj> > workspaces and suspend completed without incident. Since I have have pj> > implemented the above suggestion, I have had suspend fail to follow pj> > through and display message output in TTY and revert back to SDDM pj> > window. I logged into KDE and then attempted suspend again, then same pj> > events. I was going to take a photo of the messages but cannot with pj> > suspend completing. Are you aware of something like this occuring pj> > previously (in other cases) by chance? pj> > pj> Hi, after my last message I decided to powercycle the machine and it pj> *locked* for over 2 minutes (then I hard reset with power button). pj> I have attached a photo to imgbb of the displayed errors: pj> https://ibb.co/H4tttXv
I suspect memory but did you run memtest86+?
I have ran memtest86+ on this machine for 9 passes (I believe) about 1 month ago now. I will do this again. I think it may be the filesystem as this just occurred again today after a zypper dup then an attempt to shutdown the machine.
In this case, you should check the /var/log/messages.
I am not certain which log file but thanks for advising also.
If you are lucky, you may find the cause.
Thanks for the tip on the keyboard issue I think this lockup problem probably is not related to the keyboard bug. -Best wishes
On 02-16-2024 06:15PM, -pj via openSUSE Users wrote:
On 02-15-2024 05:42PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <6f6c15da-bbaf-43d3-a283-c32098517b5b@gmx.com> Date & Time: Wed, 14 Feb 2024 20:42:41 -0600
[pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written:
[...] pj> > Please note: It seems like possibly an open window application in a pj> > workspace could have/be, been jamming the suspend process up. I pj> > minimized the running application processes in 1 of the 2 currently used pj> > workspaces and suspend completed without incident. Since I have have pj> > implemented the above suggestion, I have had suspend fail to follow pj> > through and display message output in TTY and revert back to SDDM pj> > window. I logged into KDE and then attempted suspend again, then same pj> > events. I was going to take a photo of the messages but cannot with pj> > suspend completing. Are you aware of something like this occuring pj> > previously (in other cases) by chance? pj> > pj> Hi, after my last message I decided to powercycle the machine and it pj> *locked* for over 2 minutes (then I hard reset with power button). pj> I have attached a photo to imgbb of the displayed errors: pj> https://ibb.co/H4tttXv
I suspect memory but did you run memtest86+?
I have ran memtest86+ on this machine for 9 passes (I believe) about 1 month ago now. I will do this again. I think it may be the filesystem as this just occurred again today after a zypper dup then an attempt to shutdown the machine.
In this case, you should check the /var/log/messages.
I am not certain which log file but thanks for advising also.
If you are lucky, you may find the cause.
Thanks for the tip on the keyboard issue I think this lockup problem probably is not related to the keyboard bug.
I'm taking back my last statement about the lockup issues (more testing is needed here). I believe that since I have done the following:
1. edit the /etc/default/grub as follows:
1-1. remove 'usbcore.autosuspend=-1' entry. 1-2. remove the 'i8042.nomux=1 i8042.reset' entry, instead.
2.
# update-bootloader --refresh
Then I enabled the systemd.PS2-Keyboard service once again. I then powercycled the machine. Lockups have not been occurring as of yet. More testing will be done of course. -Thanks
On 2024-02-17 02:17, -pj via openSUSE Users wrote:
On 02-16-2024 06:15PM, -pj via openSUSE Users wrote:
On 02-15-2024 05:42PM, Masaru Nomiya wrote:
Hello,
Thanks for the tip on the keyboard issue I think this lockup problem probably is not related to the keyboard bug.
I'm taking back my last statement about the lockup issues (more testing is needed here). I believe that since I have done the following:
1. edit the /etc/default/grub as follows:
1-1. remove 'usbcore.autosuspend=-1' entry. 1-2. remove the 'i8042.nomux=1 i8042.reset' entry, instead.
2.
# update-bootloader --refresh
Then I enabled the systemd.PS2-Keyboard service once again.
I think the intention is to have it disabled. The idea is that the boot parameter change makes unnecessary to disable keyboard wakeup feature.
I then powercycled the machine. Lockups have not been occurring as of yet. More testing will be done of course.
-Thanks
-- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 02-16-2024 08:10PM, Carlos E. R. wrote:
On 2024-02-17 02:17, -pj via openSUSE Users wrote:
On 02-16-2024 06:15PM, -pj via openSUSE Users wrote:
On 02-15-2024 05:42PM, Masaru Nomiya wrote:
Hello,
Thanks for the tip on the keyboard issue I think this lockup problem probably is not related to the keyboard bug.
I'm taking back my last statement about the lockup issues (more testing is needed here). I believe that since I have done the following:
> > 1. edit the /etc/default/grub as follows: > > 1-1. remove 'usbcore.autosuspend=-1' entry. > 1-2. remove the 'i8042.nomux=1 i8042.reset' entry, instead. > > 2. > > # update-bootloader --refresh
Then I enabled the systemd.PS2-Keyboard service once again.
I think the intention is to have it disabled.
The idea is that the boot parameter change makes unnecessary to disable keyboard wakeup feature.
I have tried the following: 1. Add "i8042.nomux=1 i8042.reset" to /etc/default/grub 2. # update-bootloader --refresh 3. systemctl disable PS2-Keyboard.service 4. Powercycle You think to leave PS2-Keyboard.service enabled while appending the additional "i8042.nomux=1 i8042.reset" boot parameters (without quotes of course?
I then powercycled the machine. Lockups have not been occurring as of yet. More testing will be done of course.
-Thanks
On 2024-02-17 03:22, -pj via openSUSE Users wrote:
On 02-16-2024 08:10PM, Carlos E. R. wrote:
On 2024-02-17 02:17, -pj via openSUSE Users wrote:
On 02-16-2024 06:15PM, -pj via openSUSE Users wrote:
On 02-15-2024 05:42PM, Masaru Nomiya wrote:
Hello,
Thanks for the tip on the keyboard issue I think this lockup problem probably is not related to the keyboard bug.
I'm taking back my last statement about the lockup issues (more testing is needed here). I believe that since I have done the following:
> > 1. edit the /etc/default/grub as follows: > > 1-1. remove 'usbcore.autosuspend=-1' entry. > 1-2. remove the 'i8042.nomux=1 i8042.reset' entry, instead. > > 2. > > # update-bootloader --refresh
Then I enabled the systemd.PS2-Keyboard service once again.
I think the intention is to have it disabled.
The idea is that the boot parameter change makes unnecessary to disable keyboard wakeup feature.
I have tried the following:
1. Add "i8042.nomux=1 i8042.reset" to /etc/default/grub 2. # update-bootloader --refresh
AFAIK it is: grub2-mkconfig -o /boot/grub2/grub.cfg as documented in "/etc/default/grub" itself.
3. systemctl disable PS2-Keyboard.service 4. Powercycle
You think to leave PS2-Keyboard.service enabled while appending the additional "i8042.nomux=1 i8042.reset" boot parameters (without quotes of course?
disabled, disabled, disabled... Both changes are intended to solve the same problem. You can not find out which one works best if you use both.
I then powercycled the machine. Lockups have not been occurring as of yet. More testing will be done of course.
-Thanks
-- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
Hello, In the Message; Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <86e886d4-6ef6-4a33-b2c0-e85b510c04c1@gmx.com> Date & Time: Fri, 16 Feb 2024 20:22:01 -0600 [pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written: [...] pj> You think to leave PS2-Keyboard.service enabled while appending pj> the additional "i8042.nomux=1 i8042.reset" boot parameters pj> (without quotes of course? No, in the state of DISABLE. As I mentioned in my previous email, re-configure as follows; i8042.nomux=1 i8042.reset i8042.noloop --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "In his book Survival of the Richest, media theorist Douglass Rushkoff describes meeting with a group of billionaire preppers who bombarded him with questions about how best to configure their bunkers to survive the end times." -- Inside Mark Zuckerberg’s Top-Secret Hawaii Compound --
On 02-16-2024 09:00PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <86e886d4-6ef6-4a33-b2c0-e85b510c04c1@gmx.com> Date & Time: Fri, 16 Feb 2024 20:22:01 -0600
[pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written:
[...] pj> You think to leave PS2-Keyboard.service enabled while appending pj> the additional "i8042.nomux=1 i8042.reset" boot parameters pj> (without quotes of course?
No, in the state of DISABLE.
As I mentioned in my previous email, re-configure as follows;
i8042.nomux=1 i8042.reset i8042.noloop
Hi, I have added the above (/etc/default/grub) with PS2-Keyboard.service disabled. Seems to be working very well. I do notice than pressing a key on the keyboard will bring the system out of suspend now VS. being only able to press the power button in order to unsuspend. - :~> cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.7.4-1-default root=/dev/mapper/system-root resume=/dev/system/swap nosimplefb=1 splash=0 plymouth.enable=0 mitigations=auto i8042.nomux=1 i8042.reset i8042.noloop=1 - Note: # grub2-mkconfig -o /boot/grub2/grub.cfg seems to have updated bootloader fine. Do not know the difference between #update-bootloader --refresh and the latter yet. Are you saying each machine manufactured with this controller type can have a variety of bug inflicted chip used? So this is a 'per machine situation' possibly? Performing a few more powercycles and reboots as of now. This looks to be very promising. No lockups as of yet. Will try and follow up. -Thanks
On 02-16-2024 09:12PM, -pj via openSUSE Users wrote:
On 02-16-2024 09:00PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <86e886d4-6ef6-4a33-b2c0-e85b510c04c1@gmx.com> Date & Time: Fri, 16 Feb 2024 20:22:01 -0600
[pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written:
[...] pj> You think to leave PS2-Keyboard.service enabled while appending pj> the additional "i8042.nomux=1 i8042.reset" boot parameters pj> (without quotes of course?
No, in the state of DISABLE.
As I mentioned in my previous email, re-configure as follows;
i8042.nomux=1 i8042.reset i8042.noloop
Hi, I have added the above (/etc/default/grub) with PS2-Keyboard.service disabled. Seems to be working very well. I do notice than pressing a key on the keyboard will bring the system out of suspend now VS. being only able to press the power button in order to unsuspend. - :~> cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.7.4-1-default root=/dev/mapper/system-root resume=/dev/system/swap nosimplefb=1 splash=0 plymouth.enable=0 mitigations=auto i8042.nomux=1 i8042.reset i8042.noloop=1 - Note: # grub2-mkconfig -o /boot/grub2/grub.cfg seems to have updated bootloader fine. Do not know the difference between #update-bootloader --refresh and the latter yet.
Are you saying each machine manufactured with this controller type can have a variety of bug inflicted chip used? So this is a 'per machine situation' possibly?
Performing a few more powercycles and reboots as of now. This looks to be very promising. No lockups as of yet. Will try and follow up.
-Thanks
Bad news to report. Attempted a shutdown and machine locked up hard, after exiting KDE at TTY. Similar messages displayed as before, before this lockup. What are your thoughts about this? -Wishes
Hello, In the Message; Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <c78fc489-cbd9-4047-84e2-b22296cc6874@gmx.com> Date & Time: Fri, 16 Feb 2024 21:54:36 -0600 [pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written: [...] pj> > Are you saying each machine manufactured with this controller type can pj> > have a variety of bug inflicted chip used? So this is a 'per machine pj> > situation' possibly? There are various types of i8042 controllers, and it is said that the i8042 controler driver has been broken since the kernel about 5 years ago, even though it was fine on older kernels. So I use my PS2 keyboard with a ps2-usb conversion adapter. [...] pj> Bad news to report. Attempted a shutdown and machine locked up hard, pj> after exiting KDE at TTY. Similar messages displayed as before, before pj> this lockup. What are your thoughts about this? Please show the results of the following; 1. $ inxi -Fxxz 2. $ wdctl Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Maddox hopes that empowering users to pick their own algorithms will get them to think more about what’s involved in making them. " -- Bluesky's Custom Algorithms Could Be the Future of Social Media --
On 02-16-2024 10:45PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <c78fc489-cbd9-4047-84e2-b22296cc6874@gmx.com> Date & Time: Fri, 16 Feb 2024 21:54:36 -0600
[pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written:
[...] pj> > Are you saying each machine manufactured with this controller type can pj> > have a variety of bug inflicted chip used? So this is a 'per machine pj> > situation' possibly?
There are various types of i8042 controllers, and it is said that the i8042 controler driver has been broken since the kernel about 5 years ago, even though it was fine on older kernels.
So I use my PS2 keyboard with a ps2-usb conversion adapter.
[...] pj> Bad news to report. Attempted a shutdown and machine locked up hard, pj> after exiting KDE at TTY. Similar messages displayed as before, before pj> this lockup. What are your thoughts about this?
Please show the results of the following;
1. $ inxi -Fxxz 2. $ wdctl
Ok, - Thinkcentre-M57p:/> inxi -Fxxz System: Kernel: 6.7.4-1-default arch: x86_64 bits: 64 compiler: gcc v: 13.2.1 Desktop: KDE Plasma v: 5.27.10 tk: Qt v: 5.15.12 wm: kwin_x11 dm: SDDM Distro: openSUSE Tumbleweed 20240214 Machine: Type: Desktop System: LENOVO product: 9088A83 v: ThinkCentre M57p serial: <superuser required> Chassis: type: 3 serial: <superuser required> Mobo: LENOVO model: LENOVO serial: <superuser required> BIOS: LENOVO v: 2RKT64BUS date: 01/08/2014 CPU: Info: quad core model: Intel Core2 Quad Q8400 bits: 64 type: MCP arch: Penryn rev: A cache: L1: 256 KiB L2: 4 MiB Speed (MHz): avg: 2195 high: 2283 min/max: 2000/2667 cores: 1: 2269 2: 2283 3: 2235 4: 1995 bogomips: 21285 Flags: ht lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx Graphics: Device-1: NVIDIA GK107GL [Quadro K600] driver: nvidia v: 470.223.02 arch: Kepler pcie: speed: 2.5 GT/s lanes: 16 ports: active: none off: DVI-I-1 empty: DP-1 bus-ID: 01:00.0 chip-ID: 10de:0ffa Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.4 compositor: kwin_x11 driver: X: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 101 Monitor-1: DVI-I-1 note: disabled model: LG (GoldStar) IPS FULLHD res: 1920x1080 dpi: 102 diag: 551mm (21.7") API: EGL v: 1.5 platforms: device: 0 drv: nvidia device: 2 drv: swrast gbm: drv: kms_swrast surfaceless: drv: swrast x11: drv: nvidia inactive: wayland,device-1 API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 470.223.02 glx-v: 1.4 direct-render: yes renderer: Quadro K600/PCIe/SSE2 API: Vulkan v: 1.3.275 surfaces: xcb,xlib device: 0 type: discrete-gpu driver: N/A device-ID: 10de:0ffa device: 1 type: cpu driver: N/A device-ID: 10005:0000 Audio: Device-1: Intel 82801I HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:293e Device-2: NVIDIA GK107 HDMI Audio driver: snd_hda_intel v: kernel pcie: speed: 2.5 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0e1b API: ALSA v: k6.7.4-1-default status: kernel-api with: aoss type: oss-emulator Server-1: JACK v: N/A status: off Server-2: PipeWire v: 1.0.3 status: active with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin Network: Device-1: Intel 82566DM-2 Gigabit Network vendor: Lenovo driver: e1000e v: kernel port: 1820 bus-ID: 00:19.0 chip-ID: 8086:10bd IF: enp0s25 state: up speed: 100 Mbps duplex: full mac: <filter> Device-2: Ralink RT2561/RT61 802.11g PCI driver: rt61pci v: 2.3.0 bus-ID: 11:0a.0 chip-ID: 1814:0301 IF: wlp17s10 state: down mac: <filter> Drives: Local Storage: total: 940.91 GiB used: 128.67 GiB (13.7%) ID-1: /dev/sda vendor: Western Digital model: WDS100T2B0A-00SM50 size: 931.51 GiB speed: 3.0 Gb/s serial: <filter> ID-2: /dev/sdb model: N/A size: 7.46 GiB type: USB rev: 2.0 spd: 480 Mb/s lanes: 1 serial: <filter> ID-3: /dev/sdc model: USB 2.0 Flash Disk size: 1.94 GiB type: USB rev: 2.0 spd: 480 Mb/s lanes: 1 serial: <filter> Partition: ID-1: / size: 924.98 GiB used: 127.38 GiB (13.8%) fs: btrfs dev: /dev/dm-1 mapped: system-root ID-2: /home size: 924.98 GiB used: 127.38 GiB (13.8%) fs: btrfs dev: /dev/dm-1 mapped: system-root ID-3: /opt size: 924.98 GiB used: 127.38 GiB (13.8%) fs: btrfs dev: /dev/dm-1 mapped: system-root ID-4: /var size: 924.98 GiB used: 127.38 GiB (13.8%) fs: btrfs dev: /dev/dm-1 mapped: system-root Swap: ID-1: swap-1 type: partition size: 6.52 GiB used: 266.8 MiB (4.0%) priority: -2 dev: /dev/dm-2 mapped: system-swap Sensors: System Temperatures: cpu: 57.0 C mobo: N/A gpu: nvidia temp: 59 C Fan Speeds (rpm): N/A gpu: nvidia fan: 29% Info: Memory: total: 8 GiB note: est. available: 7.51 GiB used: 5.69 GiB (75.8%) Processes: 286 Power: uptime: 0h 26m wakeups: 0 Init: systemd v: 254 default: graphical Packages: Compilers: gcc: 13.2.1 Shell: Bash v: 5.2.26 running-in: konsole inxi: 3.3.33 - - - Thinkcentre-M57p:/> wdctl Device: /dev/watchdog0 Identity: iamt_wdt [version 1] Timeout: 120 seconds Pre-timeout: 0 seconds Pre-timeout governor: noop Available pre-timeout governors: noop FLAG DESCRIPTION STATUS BOOT-STATUS KEEPALIVEPING Keep alive ping reply 0 0 SETTIMEOUT Set timeout (in seconds) 0 0 ALARMONLY Not trigger reboot 0 0 Thinkcentre-M57p:/> -Thankful Regards
Hello, In the Message; Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <c53b188d-4a02-41d6-b59f-52daf2f197bd@gmx.com> Date & Time: Fri, 16 Feb 2024 23:00:35 -0600 [pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written: [...] MN> > Please show the results of the following; MN> > 1. $ inxi -Fxxz MN> > 2. $ wdctl pj> Ok, pj> Thinkcentre-M57p:/> inxi -Fxxz [...] pj> Machine: pj> Type: Desktop System: LENOVO product: 9088A83 v: ThinkCentre M57p pj> serial: <superuser required> Chassis: type: 3 serial: <superuser pj> required> I thought yours would be lenovo. [..] pj> Swap: pj> ID-1: swap-1 type: partition size: 6.52 GiB used: 266.8 MiB (4.0%) pj> priority: -2 dev: /dev/dm-2 mapped: system-swap [...] pj> Info: pj> Memory: total: 8 GiB note: est. available: 7.51 GiB used: 5.69 GiB pj> (75.8%) [...] The swap size is too small. As it is too small, it will lockup under stress. If you want to use hibernate, the swap size should be at least 12GB (8x1.5). So, create a swap file. Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Companies have come to view generative AI as a kind of monster that must be fed at all costs―even if it isn’t always clear what exactly that data is needed for or what those future AI systems might end up doing." -- Generative AI Is Making Companies Even More Thirsty for Your Data --
On 02-16-2024 11:21PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <c53b188d-4a02-41d6-b59f-52daf2f197bd@gmx.com> Date & Time: Fri, 16 Feb 2024 23:00:35 -0600
[pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written:
[...] MN> > Please show the results of the following;
MN> > 1. $ inxi -Fxxz MN> > 2. $ wdctl
pj> Ok,
pj> Thinkcentre-M57p:/> inxi -Fxxz [...] pj> Machine: pj> Type: Desktop System: LENOVO product: 9088A83 v: ThinkCentre M57p pj> serial: <superuser required> Chassis: type: 3 serial: <superuser pj> required>
I thought yours would be lenovo.
[..] pj> Swap: pj> ID-1: swap-1 type: partition size: 6.52 GiB used: 266.8 MiB (4.0%) pj> priority: -2 dev: /dev/dm-2 mapped: system-swap [...] pj> Info: pj> Memory: total: 8 GiB note: est. available: 7.51 GiB used: 5.69 GiB pj> (75.8%) [...]
The swap size is too small. As it is too small, it will lockup under stress. If you want to use hibernate, the swap size should be at least 12GB (8x1.5). So, create a swap file.
So basically expand system-swap lvm for suspend to 12 GB (this is why machine is jamming up sometimes lately)? Can I leave the *btrfs filesystem* in system-root expanded 100% (as is now) and shrink system-root lvm then expand system-swap lvm? Any benefits to make system-swap 20GB not only 12GB? - Also create a 12 GB swapfile in order to use hibernate otherwise hibernate will never work? - You have a recommendation for setting 'swappiness' on this machine? - - Thinkcentre-M57p:/> df -Th Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/system-root btrfs 925G 128G 797G 14% / devtmpfs devtmpfs 4.0M 8.0K 4.0M 1% /dev tmpfs tmpfs 3.8G 0 3.8G 0% /dev/shm tmpfs tmpfs 1.6G 1.8M 1.6G 1% /run tmpfs tmpfs 3.8G 24K 3.8G 1% /tmp /dev/mapper/system-root btrfs 925G 128G 797G 14% /.snapshots /dev/mapper/system-root btrfs 925G 128G 797G 14% /boot/grub2/i386-pc /dev/mapper/system-root btrfs 925G 128G 797G 14% /boot/grub2/x86_64-efi /dev/mapper/system-root btrfs 925G 128G 797G 14% /home /dev/mapper/system-root btrfs 925G 128G 797G 14% /opt /dev/mapper/system-root btrfs 925G 128G 797G 14% /root /dev/mapper/system-root btrfs 925G 128G 797G 14% /srv /dev/mapper/system-root btrfs 925G 128G 797G 14% /usr/local /dev/mapper/system-root btrfs 925G 128G 797G 14% /var tmpfs tmpfs 770M 92K 770M 1% /run/user/1000 /dev/dm-3 vfat 2.0G 1.1G 910M 54% /run/media/paul/WORLDWIDE1 - - -
Thinkcentre-M57p:/> lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS fd0 2:0 1 4K 0 disk sda 8:0 0 931.5G 0 disk ├─sda1 8:1 0 8M 0 part └─sda2 8:2 0 931.5G 0 part └─Lenovo_M57p-openSUSE_Tumbleweed 254:0 0 931.5G 0 crypt ├─system-root 254:1 0 925G 0 lvm /var │ /usr/local │ /srv │ /root │ /opt │ /home │ /boot/grub2/x86_64-efi │ /boot/grub2/i386-pc │ /.snapshots │ / └─system-swap 254:2 0 6.5G 0 lvm [SWAP] sdc 8:32 1 1.9G 0 disk └─luks-fd28e551-c765-461e-aab0-a2c49bb786b9 254:3 0 1.9G 0 crypt /run/media/paul/WORLDWIDE1 sr0 11:0 1 1024M 0 rom Thinkcentre-M57p:/>
-Regards
Hello, In the Message; Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <a7e12b89-3c23-48ec-ad7c-2094e60ce955@gmx.com> Date & Time: Fri, 16 Feb 2024 23:58:11 -0600 [pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written: [...] MN> > So, create a swap file. pj> So basically expand system-swap lvm for suspend to 12 GB (this is why pj> machine is jamming up sometimes lately)? Can I leave the *btrfs pj> filesystem* in system-root expanded 100% (as is now) and shrink pj> system-root lvm then expand system-swap lvm? No, just make a swap file, like this; https://linuxize.com/post/create-a-linux-swap-file/#:~:text=How%20to%20add%2... pj> Any benefits to make system-swap 20GB not only 12GB? You could set to 20GB, but 12GB should be enough. pj> Also create a 12 GB swapfile in order to use hibernate otherwise pj> hibernate will never work? No, you can hibernate with a small swap space, but it causes sudden reboots, system lockups and hang up. pj> You have a recommendation for setting 'swappiness' on this machine? [...] You can create a swap file, but there is no need to change the partition. This is the easiest way for you. Isn't it time for bed? Kind Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Companies have come to view generative AI as a kind of monster that must be fed at all costs―even if it isn’t always clear what exactly that data is needed for or what those future AI systems might end up doing." -- Generative AI Is Making Companies Even More Thirsty for Your Data --
On 02-17-2024 12:36AM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <a7e12b89-3c23-48ec-ad7c-2094e60ce955@gmx.com> Date & Time: Fri, 16 Feb 2024 23:58:11 -0600
[pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written:
[...] MN> > So, create a swap file.
pj> So basically expand system-swap lvm for suspend to 12 GB (this is why pj> machine is jamming up sometimes lately)? Can I leave the *btrfs pj> filesystem* in system-root expanded 100% (as is now) and shrink pj> system-root lvm then expand system-swap lvm?
No, just make a swap file, like this;
https://linuxize.com/post/create-a-linux-swap-file/#:~:text=How%20to%20add%2...
pj> Any benefits to make system-swap 20GB not only 12GB?
You could set to 20GB, but 12GB should be enough.
pj> Also create a 12 GB swapfile in order to use hibernate otherwise pj> hibernate will never work?
No, you can hibernate with a small swap space, but it causes sudden reboots, system lockups and hang up.
pj> You have a recommendation for setting 'swappiness' on this machine? [...]
You can create a swap file, but there is no need to change the partition. This is the easiest way for you.
Isn't it time for bed?
Thank you for your assistance and thoughts with this (I see this article). I believe this is the same article I reviewed some time ago for swappiness. I do now am tired and will try to sleep very soon. What I have done before reading your message was reviewing some threads here: https://forums.opensuse.org/t/questions-about-resizing-swap-partition-and-sw... I will hopefully work on this more with your help soon. -Best Regards
On 2024-02-17 06:58, -pj via openSUSE Users wrote:
On 02-16-2024 11:21PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <c53b188d-4a02-41d6-b59f-52daf2f197bd@gmx.com> Date & Time: Fri, 16 Feb 2024 23:00:35 -0600
[pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written:
[...] MN> > Please show the results of the following;
MN> > 1. $ inxi -Fxxz MN> > 2. $ wdctl
pj> Ok,
pj> Thinkcentre-M57p:/> inxi -Fxxz [...] pj> Machine: pj> Type: Desktop System: LENOVO product: 9088A83 v: ThinkCentre M57p pj> serial: <superuser required> Chassis: type: 3 serial: <superuser pj> required>
I thought yours would be lenovo.
[..] pj> Swap: pj> ID-1: swap-1 type: partition size: 6.52 GiB used: 266.8 MiB (4.0%) pj> priority: -2 dev: /dev/dm-2 mapped: system-swap [...] pj> Info: pj> Memory: total: 8 GiB note: est. available: 7.51 GiB used: 5.69 GiB pj> (75.8%) [...]
The swap size is too small. As it is too small, it will lockup under stress. If you want to use hibernate, the swap size should be at least 12GB (8x1.5). So, create a swap file.
So basically expand system-swap lvm for suspend to 12 GB
For hibernate, not for suspend. If you don't hibernate, then swap is not needed (yet) Notice that swap has no effect on your power-off problem.
(this is why machine is jamming up sometimes lately)? Can I leave the *btrfs filesystem* in system-root expanded 100% (as is now) and shrink system-root lvm then expand system-swap lvm? Any benefits to make system-swap 20GB not only 12GB? - Also create a 12 GB swapfile in order to use hibernate otherwise hibernate will never work?
I prefer a swap partition, but if the disk is already partitioned, I understand a swapfile will do. But then the existing swap space will be superfluous.
- You have a recommendation for setting 'swappiness' on this machine?
I never touch it. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 02-17-2024 07:06AM, Carlos E. R. wrote:
On 2024-02-17 06:58, -pj via openSUSE Users wrote:
On 02-16-2024 11:21PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <c53b188d-4a02-41d6-b59f-52daf2f197bd@gmx.com> Date & Time: Fri, 16 Feb 2024 23:00:35 -0600
[pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written:
[...] MN> > Please show the results of the following;
MN> > 1. $ inxi -Fxxz MN> > 2. $ wdctl
pj> Ok,
pj> Thinkcentre-M57p:/> inxi -Fxxz [...] pj> Machine: pj> Type: Desktop System: LENOVO product: 9088A83 v: ThinkCentre M57p pj> serial: <superuser required> Chassis: type: 3 serial: <superuser pj> required>
I thought yours would be lenovo.
[..] pj> Swap: pj> ID-1: swap-1 type: partition size: 6.52 GiB used: 266.8 MiB (4.0%) pj> priority: -2 dev: /dev/dm-2 mapped: system-swap [...] pj> Info: pj> Memory: total: 8 GiB note: est. available: 7.51 GiB used: 5.69 GiB pj> (75.8%) [...]
The swap size is too small. As it is too small, it will lockup under stress. If you want to use hibernate, the swap size should be at least 12GB (8x1.5). So, create a swap file.
So basically expand system-swap lvm for suspend to 12 GB
For hibernate, not for suspend.
If you don't hibernate, then swap is not needed (yet)
I would like to be able to use the hibernate feature also.
Notice that swap has no effect on your power-off problem.
I am noticing that swap has no effect on my power-off problem.
(this is why machine is jamming up sometimes lately)? Can I leave the *btrfs filesystem* in system-root expanded 100% (as is now) and shrink system-root lvm then expand system-swap lvm? Any benefits to make system-swap 20GB not only 12GB? - Also create a 12 GB swapfile in order to use hibernate otherwise hibernate will never work?
I prefer a swap partition, but if the disk is already partitioned, I understand a swapfile will do. But then the existing swap space will be superfluous.
I didn't want to take the route described in the following link here yet if possible: https://linuxize.com/post/create-a-linux-swap-file/#:~:text=How%20to%20add%2... Check out what I have done as follows please: 1. # btrfs filesystem resize -9g / Resize device id 1 (/dev/mapper/system-root) from 924.98GiB to 915.98GiB - 2. # lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root system -wi-ao---- 924.98g swap system -wi-a----- 6.52g - 3. # lvresize -L -9G /dev/system/root File system btrfs found on system/root. File system size (915.98 GiB) is equal to the requested size (915.98 GiB). File system reduce is not needed, skipping. Size of logical volume system/root changed from 924.98 GiB (236796 extents) to 915.98 GiB (234492 extents). Logical volume system/root successfully resized. - 4. # lvresize -L +9G /dev/system/swap Size of logical volume system/swap changed from 6.52 GiB (1668 extents) to 15.52 GiB (3972 extents). Logical volume system/swap successfully resized. - 5. # # df -Th Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/system-root btrfs 916G 128G 788G 14% / devtmpfs devtmpfs 4.0M 0 4.0M 0% /dev tmpfs tmpfs 3.8G 0 3.8G 0% /dev/shm tmpfs tmpfs 1.6G 1.8M 1.6G 1% /run tmpfs tmpfs 3.8G 668K 3.8G 1% /tmp /dev/mapper/system-root btrfs 916G 128G 788G 14% /.snapshots /dev/mapper/system-root btrfs 916G 128G 788G 14% /boot/grub2/i386-pc /dev/mapper/system-root btrfs 916G 128G 788G 14% /boot/grub2/x86_64-efi /dev/mapper/system-root btrfs 916G 128G 788G 14% /home /dev/mapper/system-root btrfs 916G 128G 788G 14% /opt /dev/mapper/system-root btrfs 916G 128G 788G 14% /root /dev/mapper/system-root btrfs 916G 128G 788G 14% /srv /dev/mapper/system-root btrfs 916G 128G 788G 14% /usr/local /dev/mapper/system-root btrfs 916G 128G 788G 14% /var tmpfs tmpfs 770M 104K 770M 1% /run/user/1000 - 6. # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS fd0 2:0 1 4K 0 disk sda 8:0 0 931.5G 0 disk ├─sda1 8:1 0 8M 0 part └─sda2 8:2 0 931.5G 0 part └─Lenovo_M57p-openSUSE_Tumbleweed 254:0 0 931.5G 0 crypt ├─system-root 254:1 0 916G 0 lvm /var │ /usr/local │ /srv │ /root │ /opt │ /home │ /boot/grub2/x86_64-efi │ /boot/grub2/i386-pc │ /.snapshots │ / └─system-swap 254:2 0 15.5G 0 lvm sdb 8:16 1 1.9G 0 disk sr0 11:0 1 1024M 0 rom - 7. Note how swap is now displayed at 15.5G in size. - 8. I believe that it may not have been necessary to pass the following at all: # btrfs filesystem resize -9g / - 9. Do you have any recommendations on setting the machine up for hibernation? - 10. I commented out in /etc/fstab the following# /dev/system/swap swap swap defaults 0 0 I am going to revert that above now (and powercycle).
- You have a recommendation for setting 'swappiness' on this machine?
I never touch it.
Thanks for your thoughts on "swappiness". -Best Regards
On 2024-02-17 18:37, -pj via openSUSE Users wrote:
On 02-17-2024 07:06AM, Carlos E. R. wrote:
On 2024-02-17 06:58, -pj via openSUSE Users wrote:
On 02-16-2024 11:21PM, Masaru Nomiya wrote:
[...]
The swap size is too small. As it is too small, it will lockup under stress. If you want to use hibernate, the swap size should be at least 12GB (8x1.5). So, create a swap file.
So basically expand system-swap lvm for suspend to 12 GB
For hibernate, not for suspend.
If you don't hibernate, then swap is not needed (yet)
I would like to be able to use the hibernate feature also.
Ah. Well, then you need swap to be a bit bigger than your used RAM size. I think you can add two swap areas; but for recovering the kernel only uses one, the one that is cited in the kernel boot line. A while ago you had: BOOT_IMAGE=/boot/vmlinuz-6.7.4-1-default root=/dev/mapper/system-root resume=/dev/system/swap nosimplefb=1 splash=0 plymouth.enable=0 mitigations=auto i8042.nomux=1 i8042.reset i8042.noloop=1 So you have to change that "resume=..." section. Hum, you like is strange to me, I don't know what /dev/system is.
Notice that swap has no effect on your power-off problem.
I am noticing that swap has no effect on my power-off problem.
(this is why machine is jamming up sometimes lately)? Can I leave the *btrfs filesystem* in system-root expanded 100% (as is now) and shrink system-root lvm then expand system-swap lvm? Any benefits to make system-swap 20GB not only 12GB? - Also create a 12 GB swapfile in order to use hibernate otherwise hibernate will never work?
I prefer a swap partition, but if the disk is already partitioned, I understand a swapfile will do. But then the existing swap space will be superfluous.
I didn't want to take the route described in the following link here yet if possible: https://linuxize.com/post/create-a-linux-swap-file/#:~:text=How%20to%20add%2...
Check out what I have done as follows please:
I'm not an expert on btrfs or lvm, sorry.
1. # btrfs filesystem resize -9g / Resize device id 1 (/dev/mapper/system-root) from 924.98GiB to 915.98GiB -
...
- 7. Note how swap is now displayed at 15.5G in size.
Yes, I did.
- 8. I believe that it may not have been necessary to pass the following at all: # btrfs filesystem resize -9g / -
I can't say.
9. Do you have any recommendations on setting the machine up for hibernation?
It either works or not :-) Sometimes I suspect some application conflicts, then I stop the app in advance. For example, vmware/virtualbox.
- 10. I commented out in /etc/fstab the following# /dev/system/swap swap swap defaults 0 0
But you have to declare swap both in fstab and in grub's kernel line.
I am going to revert that above now (and powercycle).
- You have a recommendation for setting 'swappiness' on this machine?
I never touch it.
Thanks for your thoughts on "swappiness".
:-} -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 02-17-2024 12:02PM, Carlos E. R. wrote:
On 2024-02-17 18:37, -pj via openSUSE Users wrote:
On 02-17-2024 07:06AM, Carlos E. R. wrote:
On 2024-02-17 06:58, -pj via openSUSE Users wrote:
On 02-16-2024 11:21PM, Masaru Nomiya wrote:
[...]
The swap size is too small. As it is too small, it will lockup under stress. If you want to use hibernate, the swap size should be at least 12GB (8x1.5). So, create a swap file.
So basically expand system-swap lvm for suspend to 12 GB
For hibernate, not for suspend.
If you don't hibernate, then swap is not needed (yet)
I would like to be able to use the hibernate feature also.
Ah.
Well, then you need swap to be a bit bigger than your used RAM size.
I think you can add two swap areas; but for recovering the kernel only uses one, the one that is cited in the kernel boot line.
A while ago you had:
BOOT_IMAGE=/boot/vmlinuz-6.7.4-1-default root=/dev/mapper/system-root resume=/dev/system/swap nosimplefb=1 splash=0 plymouth.enable=0 mitigations=auto i8042.nomux=1 i8042.reset i8042.noloop=1
So you have to change that "resume=..." section.
Hum, you like is strange to me, I don't know what /dev/system is.
I think /dev/system/swap is the LV the way the block device communicates with it. I believe that was in there when the OS was initially installed. I have not changed "resume=..." section. I have not even removed any "i8042..." entries yet either. Please see the current output: - # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.7.4-1-default root=/dev/mapper/system-root resume=/dev/system/swap nosimplefb=1 splash=0 plymouth.enable=0 mitigations=auto i8042.nomux=1 i8042.reset i8042.noloop=1 -
Notice that swap has no effect on your power-off problem.
I am noticing that swap has no effect on my power-off problem.
(this is why machine is jamming up sometimes lately)? Can I leave the *btrfs filesystem* in system-root expanded 100% (as is now) and shrink system-root lvm then expand system-swap lvm? Any benefits to make system-swap 20GB not only 12GB? - Also create a 12 GB swapfile in order to use hibernate otherwise hibernate will never work?
I prefer a swap partition, but if the disk is already partitioned, I understand a swapfile will do. But then the existing swap space will be superfluous.
I didn't want to take the route described in the following link here yet if possible: https://linuxize.com/post/create-a-linux-swap-file/#:~:text=How%20to%20add%2...
Check out what I have done as follows please:
I'm not an expert on btrfs or lvm, sorry.
1. # btrfs filesystem resize -9g / Resize device id 1 (/dev/mapper/system-root) from 924.98GiB to 915.98GiB -
...
- 7. Note how swap is now displayed at 15.5G in size.
Yes, I did.
Please note that 'free -m' output displays only what appears to be the previous swap size. I just noticed this. # free -m total used free shared buff/cache available Mem: 7693 5655 350 130 2076 2037 Swap: 6671 10 6661
- 8. I believe that it may not have been necessary to pass the following at all: # btrfs filesystem resize -9g / -
I can't say.
9. Do you have any recommendations on setting the machine up for hibernation?
It either works or not :-)
:| Ok.
Sometimes I suspect some application conflicts, then I stop the app in advance. For example, vmware/virtualbox.
- 10. I commented out in /etc/fstab the following# /dev/system/swap swap swap defaults 0 0
But you have to declare swap both in fstab and in grub's kernel line.
Ok.
I am going to revert that above now (and powercycle).
- You have a recommendation for setting 'swappiness' on this machine?
I never touch it.
Thanks for your thoughts on "swappiness".
:-} :|
On 2024-02-17 19:15, -pj via openSUSE Users wrote:
On 02-17-2024 12:02PM, Carlos E. R. wrote:
On 2024-02-17 18:37, -pj via openSUSE Users wrote:
On 02-17-2024 07:06AM, Carlos E. R. wrote:
On 2024-02-17 06:58, -pj via openSUSE Users wrote:
On 02-16-2024 11:21PM, Masaru Nomiya wrote:
[...]
The swap size is too small. As it is too small, it will lockup under stress. If you want to use hibernate, the swap size should be at least 12GB (8x1.5). So, create a swap file.
So basically expand system-swap lvm for suspend to 12 GB
For hibernate, not for suspend.
If you don't hibernate, then swap is not needed (yet)
I would like to be able to use the hibernate feature also.
Ah.
Well, then you need swap to be a bit bigger than your used RAM size.
I think you can add two swap areas; but for recovering the kernel only uses one, the one that is cited in the kernel boot line.
A while ago you had:
BOOT_IMAGE=/boot/vmlinuz-6.7.4-1-default root=/dev/mapper/system-root resume=/dev/system/swap nosimplefb=1 splash=0 plymouth.enable=0 mitigations=auto i8042.nomux=1 i8042.reset i8042.noloop=1
So you have to change that "resume=..." section.
Hum, you like is strange to me, I don't know what /dev/system is.
I think /dev/system/swap is the LV the way the block device communicates with it. I believe that was in there when the OS was initially installed.
I have not changed "resume=..." section. I have not even removed any "i8042..." entries yet either. Please see the current output: - # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.7.4-1-default root=/dev/mapper/system-root resume=/dev/system/swap nosimplefb=1 splash=0 plymouth.enable=0 mitigations=auto i8042.nomux=1 i8042.reset i8042.noloop=1 -
Ok, you have simply enlarged the previous swap space, so it should work. There is no references to uuids or labels.
Notice that swap has no effect on your power-off problem.
I am noticing that swap has no effect on my power-off problem.
(this is why machine is jamming up sometimes lately)? Can I leave the *btrfs filesystem* in system-root expanded 100% (as is now) and shrink system-root lvm then expand system-swap lvm? Any benefits to make system-swap 20GB not only 12GB? - Also create a 12 GB swapfile in order to use hibernate otherwise hibernate will never work?
I prefer a swap partition, but if the disk is already partitioned, I understand a swapfile will do. But then the existing swap space will be superfluous.
I didn't want to take the route described in the following link here yet if possible: https://linuxize.com/post/create-a-linux-swap-file/#:~:text=How%20to%20add%2...
Check out what I have done as follows please:
I'm not an expert on btrfs or lvm, sorry.
1. # btrfs filesystem resize -9g / Resize device id 1 (/dev/mapper/system-root) from 924.98GiB to 915.98GiB -
...
- 7. Note how swap is now displayed at 15.5G in size.
Yes, I did.
Please note that 'free -m' output displays only what appears to be the previous swap size. I just noticed this.
Huh? [...] Right, you need to call "mkswap" on the device. Disable swap, run mkswap on it, enable swap.
# free -m total used free shared buff/cache available Mem: 7693 5655 350 130 2076 2037 Swap: 6671 10 6661
- 8. I believe that it may not have been necessary to pass the following at all: # btrfs filesystem resize -9g / -
I can't say.
9. Do you have any recommendations on setting the machine up for hibernation?
It either works or not :-)
:| Ok.
When hibernation fails, there is little one can do, short of dancing around the computer with a magic wand and incense sticks. Ok, no, there are things one can do, but after it fails. ... -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 02-17-2024 12:32PM, Carlos E. R. wrote:
On 2024-02-17 19:15, -pj via openSUSE Users wrote:
On 02-17-2024 12:02PM, Carlos E. R. wrote:
On 2024-02-17 18:37, -pj via openSUSE Users wrote:
On 02-17-2024 07:06AM, Carlos E. R. wrote:
On 2024-02-17 06:58, -pj via openSUSE Users wrote:
On 02-16-2024 11:21PM, Masaru Nomiya wrote:
> [...] > > The swap size is too small. > As it is too small, it will lockup under stress. > If you want to use hibernate, the swap size should be at least 12GB > (8x1.5). > So, create a swap file.
So basically expand system-swap lvm for suspend to 12 GB
For hibernate, not for suspend.
If you don't hibernate, then swap is not needed (yet)
I would like to be able to use the hibernate feature also.
Ah.
Well, then you need swap to be a bit bigger than your used RAM size.
I think you can add two swap areas; but for recovering the kernel only uses one, the one that is cited in the kernel boot line.
A while ago you had:
BOOT_IMAGE=/boot/vmlinuz-6.7.4-1-default root=/dev/mapper/system-root resume=/dev/system/swap nosimplefb=1 splash=0 plymouth.enable=0 mitigations=auto i8042.nomux=1 i8042.reset i8042.noloop=1
So you have to change that "resume=..." section.
Hum, you like is strange to me, I don't know what /dev/system is.
I think /dev/system/swap is the LV the way the block device communicates with it. I believe that was in there when the OS was initially installed.
I have not changed "resume=..." section. I have not even removed any "i8042..." entries yet either. Please see the current output: - # cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-6.7.4-1-default root=/dev/mapper/system-root resume=/dev/system/swap nosimplefb=1 splash=0 plymouth.enable=0 mitigations=auto i8042.nomux=1 i8042.reset i8042.noloop=1 -
Ok, you have simply enlarged the previous swap space, so it should work. There is no references to uuids or labels.
Notice that swap has no effect on your power-off problem.
I am noticing that swap has no effect on my power-off problem.
(this is why machine is jamming up sometimes lately)? Can I leave the *btrfs filesystem* in system-root expanded 100% (as is now) and shrink system-root lvm then expand system-swap lvm? Any benefits to make system-swap 20GB not only 12GB? - Also create a 12 GB swapfile in order to use hibernate otherwise hibernate will never work?
I prefer a swap partition, but if the disk is already partitioned, I understand a swapfile will do. But then the existing swap space will be superfluous.
I didn't want to take the route described in the following link here yet if possible: https://linuxize.com/post/create-a-linux-swap-file/#:~:text=How%20to%20add%2...
Check out what I have done as follows please:
I'm not an expert on btrfs or lvm, sorry.
1. # btrfs filesystem resize -9g / Resize device id 1 (/dev/mapper/system-root) from 924.98GiB to 915.98GiB -
...
- 7. Note how swap is now displayed at 15.5G in size.
Yes, I did.
Please note that 'free -m' output displays only what appears to be the previous swap size. I just noticed this.
Huh?
[...]
Right, you need to call "mkswap" on the device.
Disable swap, run mkswap on it, enable swap.
I am very glad you responded to this above. I have never done this before (enlarging swap). I see in 'man swap' the following might accomplish this. 1. # swapoff -all - passing: lsblk -f -> system-swap swap 1 e736498b-60e5-4f99-99c2-8a6850a78ca9 [SWAP] I see in 'man mkswap' the following may be what I am looking for to enlarge the actual swap file. 2. # mkswap --uuid e736498b-60e5-4f99-99c2-8a6850a78ca9 /dev/system/swap - Then enable swap partition again. 3. # swapon /dev/system/swap - What will happen if no "uuid" is specified in mkswap? Does this look correct to you what I am considering to do above? I do not believe that a new uuid needs to be generated by default. .....
# free -m total used free shared buff/cache available Mem: 7693 5655 350 130 2076 2037 Swap: 6671 10 6661
- 8. I believe that it may not have been necessary to pass the following at all: # btrfs filesystem resize -9g / -
I can't say.
9. Do you have any recommendations on setting the machine up for hibernation?
It either works or not :-)
:| Ok.
When hibernation fails, there is little one can do, short of dancing around the computer with a magic wand and incense sticks.
Ok, no, there are things one can do, but after it fails.
...
On 2024-02-17 20:58, -pj via openSUSE Users wrote:
On 02-17-2024 12:32PM, Carlos E. R. wrote:
On 2024-02-17 19:15, -pj via openSUSE Users wrote:
On 02-17-2024 12:02PM, Carlos E. R. wrote:
On 2024-02-17 18:37, -pj via openSUSE Users wrote:
On 02-17-2024 07:06AM, Carlos E. R. wrote:
On 2024-02-17 06:58, -pj via openSUSE Users wrote: > On 02-16-2024 11:21PM, Masaru Nomiya wrote:
>> [...] >>
...
7. Note how swap is now displayed at 15.5G in size.
Yes, I did.
Please note that 'free -m' output displays only what appears to be the previous swap size. I just noticed this.
Huh?
[...]
Right, you need to call "mkswap" on the device.
Disable swap, run mkswap on it, enable swap.
I am very glad you responded to this above. I have never done this before (enlarging swap).
I see in 'man swap' the following might accomplish this.
1. # swapoff -all - passing: lsblk -f -> system-swap swap 1 e736498b-60e5-4f99-99c2-8a6850a78ca9 [SWAP]
I see in 'man mkswap' the following may be what I am looking for to enlarge the actual swap file.
2. # mkswap --uuid e736498b-60e5-4f99-99c2-8a6850a78ca9 /dev/system/swap -
Ah, good idea, keeping the uuid. In my case, as I use labels, I would have to try to keep it.
Then enable swap partition again.
3. # swapon /dev/system/swap - What will happen if no "uuid" is specified in mkswap?
A new random uuid is created. So if the uuid was specified in fstab or elsewhere, things stop working.
Does this look correct to you what I am considering to do above? I do not believe that a new uuid needs to be generated by default.
mkswap is a format; all format tools create things afresh. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 02-17-2024 02:26PM, Carlos E. R. wrote:
On 2024-02-17 20:58, -pj via openSUSE Users wrote:
On 02-17-2024 12:32PM, Carlos E. R. wrote:
On 2024-02-17 19:15, -pj via openSUSE Users wrote:
On 02-17-2024 12:02PM, Carlos E. R. wrote:
On 2024-02-17 18:37, -pj via openSUSE Users wrote:
On 02-17-2024 07:06AM, Carlos E. R. wrote: > On 2024-02-17 06:58, -pj via openSUSE Users wrote: >> On 02-16-2024 11:21PM, Masaru Nomiya wrote:
>>> [...] >>>
...
7. Note how swap is now displayed at 15.5G in size.
Yes, I did.
Please note that 'free -m' output displays only what appears to be the previous swap size. I just noticed this.
Huh?
[...]
Right, you need to call "mkswap" on the device.
Disable swap, run mkswap on it, enable swap.
I am very glad you responded to this above. I have never done this before (enlarging swap).
I see in 'man swap' the following might accomplish this.
1. # swapoff -all - passing: lsblk -f -> system-swap swap 1 e736498b-60e5-4f99-99c2-8a6850a78ca9 [SWAP]
I see in 'man mkswap' the following may be what I am looking for to enlarge the actual swap file.
2. # mkswap --uuid e736498b-60e5-4f99-99c2-8a6850a78ca9 /dev/system/swap -
Ah, good idea, keeping the uuid.
In my case, as I use labels, I would have to try to keep it.
Then enable swap partition again.
3. # swapon /dev/system/swap - What will happen if no "uuid" is specified in mkswap?
A new random uuid is created. So if the uuid was specified in fstab or elsewhere, things stop working.
Does this look correct to you what I am considering to do above? I do not believe that a new uuid needs to be generated by default.
mkswap is a format; all format tools create things afresh.
Ok, very good advice. I passed the following commands: # swapoff -a - # mkswap --uuid e736498b-60e5-4f99-99c2-8a6850a78ca9 /dev/system/swap - # swapon /dev/system/swap This is 'free -m' output now after powercycle: # free -m total used free shared buff/cache available Mem: 7693 3067 2851 63 2163 4625 Swap: 15887 1828 14059 I believe swap is working again. Are you aware of any other testing to ensure that swap is working? Another question for you is that currently attempting to 'Hibernate' (tried twice), the machine goes through the process...halts/poweroff completely for about a second. Then powers up in a poweron at bios where after entering the LUKS passphrase some boot information is displayed. Is it best to start a new post about this? -Great Thanks :]
On 2024-02-17 22:10, -pj via openSUSE Users wrote:
On 02-17-2024 02:26PM, Carlos E. R. wrote:
On 2024-02-17 20:58, -pj via openSUSE Users wrote:
On 02-17-2024 12:32PM, Carlos E. R. wrote:
On 2024-02-17 19:15, -pj via openSUSE Users wrote:
On 02-17-2024 12:02PM, Carlos E. R. wrote:
...
I see in 'man swap' the following might accomplish this.
1. # swapoff -all - passing: lsblk -f -> system-swap swap 1 e736498b-60e5-4f99-99c2-8a6850a78ca9 [SWAP]
I see in 'man mkswap' the following may be what I am looking for to enlarge the actual swap file.
2. # mkswap --uuid e736498b-60e5-4f99-99c2-8a6850a78ca9 /dev/system/swap -
Ah, good idea, keeping the uuid.
In my case, as I use labels, I would have to try to keep it.
Then enable swap partition again.
3. # swapon /dev/system/swap - What will happen if no "uuid" is specified in mkswap?
A new random uuid is created. So if the uuid was specified in fstab or elsewhere, things stop working.
Does this look correct to you what I am considering to do above? I do not believe that a new uuid needs to be generated by default.
mkswap is a format; all format tools create things afresh.
Ok, very good advice. I passed the following commands:
# swapoff -a - # mkswap --uuid e736498b-60e5-4f99-99c2-8a6850a78ca9 /dev/system/swap - # swapon /dev/system/swap
This is 'free -m' output now after powercycle:
# free -m total used free shared buff/cache available Mem: 7693 3067 2851 63 2163 4625 Swap: 15887 1828 14059
I believe swap is working again. Are you aware of any other testing to ensure that swap is working?
Just that you see it in "used". Yes, there are other commands, for instance: Telcontar:~ # swapon NAME TYPE SIZE USED PRIO /dev/nvme0n1p2 partition 100G 696.5M -2 Telcontar:~ # (I haven't hibernated after booting a while ago). Try "swapon -s". Top is another command, which also displays swap among many other things. Oh, by the way, I pass "-h" to free. I like to see the units :-)
Another question for you is that currently attempting to 'Hibernate' (tried twice), the machine goes through the process...halts/poweroff completely for about a second. Then powers up in a poweron at bios where after entering the LUKS passphrase some boot information is displayed. Is it best to start a new post about this?
Yep. It really powers down, stops fans and all leds? Then starts on its own? Weird day you have. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 02-17-2024 05:34PM, Carlos E. R. wrote:
On 2024-02-17 22:10, -pj via openSUSE Users wrote:
On 02-17-2024 02:26PM, Carlos E. R. wrote:
On 2024-02-17 20:58, -pj via openSUSE Users wrote:
On 02-17-2024 12:32PM, Carlos E. R. wrote:
On 2024-02-17 19:15, -pj via openSUSE Users wrote:
On 02-17-2024 12:02PM, Carlos E. R. wrote:
...
I see in 'man swap' the following might accomplish this.
1. # swapoff -all - passing: lsblk -f -> system-swap swap 1 e736498b-60e5-4f99-99c2-8a6850a78ca9 [SWAP]
I see in 'man mkswap' the following may be what I am looking for to enlarge the actual swap file.
2. # mkswap --uuid e736498b-60e5-4f99-99c2-8a6850a78ca9 /dev/system/swap -
Ah, good idea, keeping the uuid.
In my case, as I use labels, I would have to try to keep it.
Then enable swap partition again.
3. # swapon /dev/system/swap - What will happen if no "uuid" is specified in mkswap?
A new random uuid is created. So if the uuid was specified in fstab or elsewhere, things stop working.
Does this look correct to you what I am considering to do above? I do not believe that a new uuid needs to be generated by default.
mkswap is a format; all format tools create things afresh.
Ok, very good advice. I passed the following commands:
# swapoff -a - # mkswap --uuid e736498b-60e5-4f99-99c2-8a6850a78ca9 /dev/system/swap - # swapon /dev/system/swap
This is 'free -m' output now after powercycle:
# free -m total used free shared buff/cache available Mem: 7693 3067 2851 63 2163 4625 Swap: 15887 1828 14059
I believe swap is working again. Are you aware of any other testing to ensure that swap is working?
Just that you see it in "used". Yes, there are other commands, for instance:
Telcontar:~ # swapon NAME TYPE SIZE USED PRIO /dev/nvme0n1p2 partition 100G 696.5M -2 Telcontar:~ #
(I haven't hibernated after booting a while ago).
Why is "swapon' reporting 100G there? Why do you have such a large swap size?
Try "swapon -s".
Top is another command, which also displays swap among many other things.
Ok.
Oh, by the way, I pass "-h" to free. I like to see the units :-)
Ok, thanks.
Another question for you is that currently attempting to 'Hibernate' (tried twice), the machine goes through the process...halts/poweroff completely for about a second. Then powers up in a poweron at bios where after entering the LUKS passphrase some boot information is displayed. Is it best to start a new post about this?
Yep.
It really powers down, stops fans and all leds? Then starts on its own?
Yes, that is what the machine does. I have created a new post now.
Weird day you have.
Yes, nothing comes easily.
On 2024-02-18 03:50, -pj via openSUSE Users wrote:
On 02-17-2024 05:34PM, Carlos E. R. wrote:
On 2024-02-17 22:10, -pj via openSUSE Users wrote:
On 02-17-2024 02:26PM, Carlos E. R. wrote:
On 2024-02-17 20:58, -pj via openSUSE Users wrote:
On 02-17-2024 12:32PM, Carlos E. R. wrote:
On 2024-02-17 19:15, -pj via openSUSE Users wrote: > On 02-17-2024 12:02PM, Carlos E. R. wrote:
Just that you see it in "used". Yes, there are other commands, for instance:
Telcontar:~ # swapon NAME TYPE SIZE USED PRIO /dev/nvme0n1p2 partition 100G 696.5M -2 Telcontar:~ #
(I haven't hibernated after booting a while ago).
Why is "swapon' reporting 100G there? Why do you have such a large swap size?
Because I can :-) RAM is 64 gigs. Easier to format big now than resize later on, a decade in the future. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
Good Morning & Hello, pj, did you sleep well last night? In the Message; Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <627f8feb-5648-405c-9d26-48225cc14582@telefonica.net> Date & Time: Sat, 17 Feb 2024 14:06:48 +0100 [CER] == "Carlos E. R." <robin.listas@telefonica.net> has written: [...] CER> For hibernate, not for suspend. hebernate = suspend to disk. Best Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "As Google fights for positioning in a new AI boom and an era where some consumers are turning to TikTok or ChatGPT instead of Google Search, some employees now worry product development could become dangerously hasty. The restructuring of RESIN has increased those concerns, the sources say." -- Google Splits Up a Key AI Ethics Watchdog --
On 02-16-2024 08:10PM, Carlos E. R. wrote:
On 2024-02-17 02:17, -pj via openSUSE Users wrote:
On 02-16-2024 06:15PM, -pj via openSUSE Users wrote:
On 02-15-2024 05:42PM, Masaru Nomiya wrote:
Hello,
Thanks for the tip on the keyboard issue I think this lockup problem probably is not related to the keyboard bug.
I'm taking back my last statement about the lockup issues (more testing is needed here). I believe that since I have done the following:
> > 1. edit the /etc/default/grub as follows: > > 1-1. remove 'usbcore.autosuspend=-1' entry. > 1-2. remove the 'i8042.nomux=1 i8042.reset' entry, instead. I used Masaru's layout see 1-2. > > 2. > > # update-bootloader --refresh
Then I enabled the systemd.PS2-Keyboard service once again.
I think the intention is to have it disabled.
The idea is that the boot parameter change makes unnecessary to disable keyboard wakeup feature.
I then powercycled the machine. Lockups have not been occurring as of yet. More testing will be done of course.
-Thanks
Hello, In the Message; Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <2696d8cd-36d7-4621-84c7-ae37c1baa866@gmx.com> Date & Time: Fri, 16 Feb 2024 19:17:19 -0600 [PJ] == -pj via openSUSE Users <users@lists.opensuse.org> has written: [...] PJ> I'm taking back my last statement about the lockup issues (more testing PJ> is needed here). I believe that since I have done the following: MN> > 1. edit the /etc/default/grub as follows: MN> > MN> > 1-1. remove 'usbcore.autosuspend=-1' entry. MN> > 1-2. remove the 'i8042.nomux=1 i8042.reset' entry, instead. MN> > MN> > 2. MN> > MN> > # update-bootloader --refresh PJ> Then I enabled the systemd.PS2-Keyboard service once again. PJ> I then powercycled the machine. Lockups have not been occurring as of PJ> yet. More testing will be done of course. Ah, I see. It is probably due to the fact that each compatible chip has a slightly different cause and handling. That is, it's a nasty bug. It would be nice if systemd.PS2-keybord service could solve it, but how about this? add the 'i8042.nomux=1 i8042.reset i8042.noloop=1' entry Of course, without systemd.PS2-keyboard service. Kind Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Companies have come to view generative AI as a kind of monster that must be fed at all costs―even if it isn’t always clear what exactly that data is needed for or what those future AI systems might end up doing." -- Generative AI Is Making Companies Even More Thirsty for Your Data --
On 02-16-2024 08:08PM, Carlos E. R. wrote:
On 2024-02-17 01:15, -pj via openSUSE Users wrote:
In this case, you should check the /var/log/messages.
I am not certain which log file but thanks for advising also.
That's the name of the file.
I do not see that file on this machine: Thinkcentre-M57p:/var/log> locate /var/log/messages Thinkcentre-M57p:/var/log> Thinkcentre-M57p:/var/log> ls -lah total 75M drwxr-xr-x 1 root root 1.6K Feb 16 19:09 . drwxr-xr-x 1 root root 148 Feb 7 13:59 .. -rw-r--r-- 1 root root 19K Feb 16 17:42 alternatives.log drwxr-xr-x 1 root root 0 Feb 7 13:23 apparmor drwxr-x--- 1 root audit 106 Feb 2 11:33 audit -rw------- 1 root root 0 Feb 2 00:00 boot.log -rw------- 1 root root 2.9K Dec 21 14:10 boot.log-20231222.xz -rw------- 1 root root 2.9K Dec 24 17:42 boot.log-20231225.xz -rw------- 1 root root 3.0K Dec 25 14:11 boot.log-20231226.xz -rw------- 1 root root 3.4K Dec 27 18:52 boot.log-20231228.xz -rw------- 1 root root 3.2K Dec 30 06:11 boot.log-20231231.xz -rw------- 1 root root 3.4K Dec 31 16:50 boot.log-20240101.xz -rw------- 1 root root 3.1K Feb 1 12:35 boot.log-20240202.xz -rw-rw---- 1 root utmp 21K Feb 14 20:30 btmp drwxr-x--- 1 chrony chrony 0 Feb 2 18:12 chrony drwxr-xr-x 1 root lp 38 Feb 4 15:46 cups -rw-r----- 1 root root 29K Jan 10 18:19 firewalld drwxrwxr-x 1 root lp 6 Feb 2 22:58 hp drwxr-sr-x 1 root systemd-journal 64 Sep 18 2021 journal drwx------ 1 root root 0 Feb 2 11:33 krb5 lrwxrwxrwx 1 root root 18 Oct 10 2020 log -> /run/initramfs/log drwx------ 1 mysql mysql 0 Feb 2 14:33 mysql -rw------- 1 root root 311K Feb 16 18:43 pbl.log -rw-r----- 1 root root 1.1M Feb 16 19:29 pk_backend_zypp -rw-r----- 1 root root 14M Feb 6 18:18 pk_backend_zypp-1 -rw------- 1 root root 119K Feb 1 12:35 plymouth-debug.log -rw------- 1 root root 11K Feb 1 17:31 plymouth-shutdown-debug.log drwx------ 1 root root 0 Oct 10 2020 private drwxr-x--- 1 root root 0 Feb 2 19:59 samba -rw-r----- 1 root root 7.8M Feb 16 20:01 snapper.log drwx------ 1 root root 0 Feb 2 19:46 speech-dispatcher drwxr-x--- 1 tor tor 0 Feb 6 10:03 tor drwxr-x--- 1 root root 0 Feb 2 11:56 tuned -rw-r--r-- 1 root root 498 Feb 11 16:40 update-messages drwxr-xr-x 1 root root 582 Feb 14 17:17 updateTestcase-2024-02-14-17-17-31 drwxr-xr-x 1 root root 582 Feb 16 17:35 updateTestcase-2024-02-16-17-35-50 -rw-r----- 1 root root 2.7M Feb 16 20:21 wpa_supplicant.log -rw-rw-r-- 1 root utmp 114K Feb 16 19:09 wtmp -rw-rw-r-- 1 root utmp 11K Jan 12 22:28 wtmp-20240113.xz -rw-r--r-- 1 root root 33K Feb 16 19:28 Xorg.0.log -rw-r--r-- 1 root root 25K Feb 16 19:08 Xorg.0.log.old -rw-r--r-- 1 root root 47K Nov 28 10:44 Xorg.1.log -rw-r--r-- 1 root root 8.1K May 10 2022 Xorg.1.log.old drwx------ 1 root root 1.3K Feb 13 17:47 YaST2 drwxr-x--- 1 root root 90 Feb 9 17:46 zypp -rw-r----- 1 root root 11M Feb 16 18:44 zypper.log -rw-r----- 1 root root 33M May 9 2022 zypper.log-20220510 -rw-r----- 1 root root 336K Dec 16 00:00 zypper.log-20231216.xz -rw-r----- 1 root root 381K Dec 24 20:37 zypper.log-20231225.xz -rw-r----- 1 root root 576K Jan 6 12:17 zypper.log-20240108.xz -rw-r----- 1 root root 414K Jan 13 20:22 zypper.log-20240114.xz -rw-r----- 1 root root 485K Jan 18 23:26 zypper.log-20240119.xz -rw-r----- 1 root root 422K Jan 25 13:31 zypper.log-20240126.xz -rw-r----- 1 root root 328K Jan 30 20:16 zypper.log-20240131.xz -rw-r----- 1 root root 369K Feb 5 22:42 zypper.log-20240206.xz -rw-r----- 1 root root 2.1M Feb 7 18:27 zypper.log-20240208.xz -rw-r----- 1 root root 346K Feb 12 21:15 zypper.log-20240213.xz Thinkcentre-M57p:/var/log> --
On 2024-02-17 03:26, -pj via openSUSE Users wrote:
On 02-16-2024 08:08PM, Carlos E. R. wrote:
On 2024-02-17 01:15, -pj via openSUSE Users wrote:
In this case, you should check the /var/log/messages.
I am not certain which log file but thanks for advising also.
That's the name of the file.
I do not see that file on this machine:
Thinkcentre-M57p:/var/log> locate /var/log/messages Thinkcentre-M57p:/var/log>
Don't use locate. You already know where the file is supposed to be, just do an ls: ls -l /var/log/messages locate is for finding files that you do not know where they are.
Thinkcentre-M57p:/var/log> ls -lah total 75M
Don't list the entire directory! Just the single file we want. If the file is not there, you simply are not running syslog, and must use journalctl instead. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
Hello, In the Message; Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <1c64771f-b4b6-4007-b101-feb19f849f15@gmx.com> Date & Time: Fri, 16 Feb 2024 20:26:31 -0600 [pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written: pj> I doo not see that file on this machine: pj> Thinkcentre-M57p:/var/log> locate /var/log/messages pj> Thinkcentre-M57p:/var/log> [...] WHAT! What is the result of; $ which logger Kind Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computer. Not with Me!" "No....., with money."
On 02-16-2024 09:11PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <1c64771f-b4b6-4007-b101-feb19f849f15@gmx.com> Date & Time: Fri, 16 Feb 2024 20:26:31 -0600
[pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written:
pj> I do not see that file on this machine:
pj> Thinkcentre-M57p:/var/log> locate /var/log/messages pj> Thinkcentre-M57p:/var/log> [...]
WHAT!
What is the result of;
$ which logger
Thinkcentre-M57p:~> which logger /usr/bin/logger -Wishes
Hello, In the Message; Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <68d693a0-8288-4ced-a3c6-6fe3035389be@gmx.com> Date & Time: Fri, 16 Feb 2024 21:13:47 -0600 [pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written: [...] MN> > What is the result of; MN> > $ which logger pj> Thinkcentre-M57p:~> which logger pj> /usr/bin/logger OK. How about these? $ rpm -q syslog-ng and, $ locate syslog-ng.conf Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "No Windows, no gains!" ... "Why, I am wrong?" -- Bill --
Hello, In the Message; Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <8ed9c982-c214-4362-8a1a-1d8606fc4ed8@gmx.com> Date & Time: Fri, 16 Feb 2024 21:49:46 -0600 [pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written: [...] MN> > locate syslog-ng.conf pj> Thinkcentre-M57p:~> rpm -q syslog-ng pj> package syslog-ng is not installed pj> Thinkcentre-M57p:~> locate syslog-ng.conf pj> Thinkcentre-M57p:~> Install syslog-ng. Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ " Hassabis says that no one really knows for sure that AI will become a major danger. But he is certain that if progress continues at its current pace, there isn’t much time to develop safeguards. "I can see the kinds of things we're building into the Gemini series right, and we have no reason to believe that they won't work," he says." -- "Google DeepMind's CEO Says Its Next Algorithm Will Eclipse ChatGPT" --
On 02-16-2024 09:53PM, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <8ed9c982-c214-4362-8a1a-1d8606fc4ed8@gmx.com> Date & Time: Fri, 16 Feb 2024 21:49:46 -0600
[pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written:
[...] MN> > locate syslog-ng.conf
pj> Thinkcentre-M57p:~> rpm -q syslog-ng pj> package syslog-ng is not installed pj> Thinkcentre-M57p:~> locate syslog-ng.conf pj> Thinkcentre-M57p:~>
Install syslog-ng.
Ok, # zypper in syslog-ng Refreshing service 'NVIDIA'. Refreshing service 'openSUSE'. Loading repository data... Reading installed packages... Resolving package dependencies... The following 4 NEW packages are going to be installed: libevtlog-4_6-0 libnet9 syslog-ng syslog-service 4 new packages to install. Overall download size: 1.1 MiB. Already cached: 0 B. After the operation, additional 4.3 MiB will be used. Continue? [y/n/v/...? shows all options] (y): y - # zypper se syslog* Refreshing service 'NVIDIA'. Refreshing service 'openSUSE'. Loading repository data... Reading installed packages... S | Name | Summary | Type ---+--------------------------+----------------------------------------------------+-------- i+ | syslog-ng | Enhanced system logging daemon i | syslog-service | Syslog service files & scripts Thinkcentre-M57p:~ # - I edited out some of the output displayed contents above (to make shorter). -Greater Wishes
Hello, In the Message; Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <6442e60e-8ab3-400a-8200-64160703a979@gmx.com> Date & Time: Fri, 16 Feb 2024 22:01:42 -0600 [pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written: [...] MN> > Install syslog-ng. pj> Ok, pj> # zypper in syslog-ng [...] pj> S | Name | Summary pj> | Type pj> ---+--------------------------+----------------------------------------------------+-------- pj> i+ | syslog-ng | Enhanced system logging daemon pj> i | syslog-service | Syslog service files & scripts pj> Thinkcentre-M57p:~ # [...] Are you in this state now? $ systemctl status syslog-ng.servic ● syslog-ng.service - System Logging Service Loaded: loaded (/usr/lib/systemd/system/syslog-ng.service; enabled; preset> Active: active (running) since Sat 2024-02-17 11:01:22 JST; 2h 47min ago TriggeredBy: ○ syslog.socket Process: 1773 ExecStartPre=/usr/sbin/syslog-ng-service-prepare (code=exited> Main PID: 1789 (syslog-ng) Tasks: 3 (limit: 4915) CPU: 1.313s CGroup: /system.slice/syslog-ng.service └─1789 /usr/sbin/syslog-ng -F If not, do the following; $ sudo systemctl enable syslog-ng.service $ sudo systemctl start syslog-ng.service Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Companies have come to view generative AI as a kind of monster that must be fed at all costs―even if it isn’t always clear what exactly that data is needed for or what those future AI systems might end up doing." -- Generative AI Is Making Companies Even More Thirsty for Your Data --
On 02-16-2024 10:57PM, Masaru Nomiya wrote:
systemctl status syslog-ng.servic
Yes, I believe so. Thinkcentre-M57p:/> systemctl status syslog-ng.service ● syslog-ng.service - System Logging Service Loaded: loaded (/usr/lib/systemd/system/syslog-ng.service; enabled; preset: disabled) Active: active (running) since Fri 2024-02-16 22:28:27 CST; 32min ago TriggeredBy: ○ syslog.socket Process: 1486 ExecStartPre=/usr/sbin/syslog-ng-service-prepare (code=exited, status=0/SUCCESS) Main PID: 1490 (syslog-ng) Tasks: 3 (limit: 4915) CPU: 1.326s CGroup: /system.slice/syslog-ng.service └─1490 /usr/sbin/syslog-ng -F Feb 16 22:28:27 Thinkcentre-M57p systemd[1]: Starting System Logging Service... Feb 16 22:28:27 Thinkcentre-M57p systemd[1]: Started System Logging Service. -Thanks
On 2024-02-17 04:53, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <8ed9c982-c214-4362-8a1a-1d8606fc4ed8@gmx.com> Date & Time: Fri, 16 Feb 2024 21:49:46 -0600
[pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written:
[...] MN> > locate syslog-ng.conf
pj> Thinkcentre-M57p:~> rpm -q syslog-ng pj> package syslog-ng is not installed pj> Thinkcentre-M57p:~> locate syslog-ng.conf pj> Thinkcentre-M57p:~>
Install syslog-ng.
This is not a requirement :-) It could also be rsyslog, or none (just use the persistent journal). -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 02-17-2024 07:10AM, Carlos E. R. wrote:
On 2024-02-17 04:53, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <8ed9c982-c214-4362-8a1a-1d8606fc4ed8@gmx.com> Date & Time: Fri, 16 Feb 2024 21:49:46 -0600
[pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written:
[...] MN> > locate syslog-ng.conf
pj> Thinkcentre-M57p:~> rpm -q syslog-ng pj> package syslog-ng is not installed pj> Thinkcentre-M57p:~> locate syslog-ng.conf pj> Thinkcentre-M57p:~>
Install syslog-ng.
This is not a requirement :-)
It could also be rsyslog, or none (just use the persistent journal).
Hi there, do you know what this journalctl line output means and or how it can be prevented? It seem like that keyboard bug that was mentioned earlier but none of the kernel entries that were tried is this one. Feb 26 18:36:22.867510 Thinkcentre-M57p kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp -Thanks
Hello, Sorry for mistake. In the Message; Subject : Re: HP PS/2 style keyboard preventing suspend: Message-ID : <877cj7agrn.wl-nomiya@lake.dti.ne.jp> Date & Time: Wed, 14 Feb 2024 12:03:56 +0900 [MN] == Masaru Nomiya <nomiya@lake.dti.ne.jp> has written: MN> Hello, MN> In the Message; MN> Subject : Re: HP PS/2 style keyboard preventing suspend: MN> Message-ID : <513bae0f-eb2a-406b-959c-3bcf23e6199a@gmx.com> MN> Date & Time: Tue, 13 Feb 2024 20:53:57 -0600 MN> [-pj] == -pj via openSUSE Users <users@lists.opensuse.org> has written: -pj> On 02-13-2024 08:48PM, Masaru Nomiya wrote: -pj> > cat /sys/module/usbcore/parameters/autosuspend -pj> Yes absolutely, -pj> cat /sys/module/usbcore/parameters/autosuspend -pj> 2 MN> # grub2-mkconfig -o /boot/grub2/grub # grub2-mkconfig -o /boot/grub2/grub.cfg Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Companies have come to view generative AI as a kind of monster that must be fed at all costs―even if it isn’t always clear what exactly that data is needed for or what those future AI systems might end up doing." -- Generative AI Is Making Companies Even More Thirsty for Your Data --
participants (11)
-
-pj -
Andrei Borzenkov -
Bill Swisher -
Carlos E. R. -
Carlos E.R. -
Dave Howorth -
Felix Miata -
Goblin Invader -
Knurpht-openSUSE -
Masaru Nomiya -
Patrick Shanahan