Does it mean secure boot can’t be used on manjaro?
secure boot is impossible with manjaro… Can it be solved with refind?
Apr 25 21:00:25 euki-aspirea51556 pkexec[9078]: euki: Executing command [USER=root] [TTY=unknown] [CWD=/home/euki] [COMMAND=/usr/bin/xfpm-power-backlight-helper --set-brightness 7488]
Apr 25 21:00:25 euki-aspirea51556 pkexec[9088]: euki: Executing command [USER=root] [TTY=unknown] [CWD=/home/euki] [COMMAND=/usr/bin/xfpm-power-backlight-helper --set-brightness 5568]
Apr 25 21:00:25 euki-aspirea51556 pkexec[9097]: euki: Executing command [USER=root] [TTY=unknown] [CWD=/home/euki] [COMMAND=/usr/bin/xfpm-power-backlight-helper --set-brightness 3648]
Apr 25 21:00:25 euki-aspirea51556 pkexec[9106]: euki: Executing command [USER=root] [TTY=unknown] [CWD=/home/euki] [COMMAND=/usr/bin/xfpm-power-backlight-helper --set-brightness 1728]
Apr 25 21:00:25 euki-aspirea51556 pkexec[9115]: euki: Executing command [USER=root] [TTY=unknown] [CWD=/home/euki] [COMMAND=/usr/bin/xfpm-power-backlight-helper --set-brightness 0]
So you decrease the screen brightness/backlight of the screen. Then it was suddenly black, what a surprise. Then you repeatly pressed the power button short:
Apr 25 21:00:28 euki-aspirea51556 systemd-logind[602]: Power key pressed short.
Apr 25 21:00:29 euki-aspirea51556 systemd-logind[602]: Power key pressed short.
Apr 25 21:00:29 euki-aspirea51556 systemd-logind[602]: Power key pressed short.
Apr 25 21:00:29 euki-aspirea51556 systemd-logind[602]: Power key pressed short.
Apr 25 21:00:29 euki-aspirea51556 systemd-logind[602]: Power key pressed short.
Apr 25 21:00:43 euki-aspirea51556 systemd-logind[602]: Power key pressed short.
Apr 25 21:00:46 euki-aspirea51556 systemd-logind[602]: Power key pressed short.
Then I guess you pressed it long for a forced shutdown.
Then you did a cold boot:
-- Boot e8cf1e8465e54197bfde8062a12b2895 --
Apr 25 21:01:16 euki-aspirea51556 kernel: microcode: microcode updated early to revision 0xa6, date = 2022-06-28
Apr 25 21:01:16 euki-aspirea51556 kernel: Linux version 6.1.25-1-MANJARO (builduser@fv-az1238-680) (gcc (GCC) 12.2.1 20230201, GNU ld (GNU Binutils) 2.40) #1 SMP PREEMPT_DYNAMIC Thu Apr 20 13:48:36 UTC 2023
Apr 25 21:01:16 euki-aspirea51556 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.1-x86_64 root=UUID=a9e9ed78-6807-4caa-9dc4-c9c4a75cb204 rw quiet splash apparmor=1 security=apparmor resume=UUID=18619d01-619e-4ef4-b175-214d1f7c5f4f udev.log_priority=3
And everything booted just fine beside some minor problems.
My thought is that the keyboard/touchpad driver is not 100% compatible with your keyboard and need “quirks” to be set, or you need to set it in a specific mode on the UEFI Settings. Touchpad and keyboard on laptops are mostly very firmware depended.
For reference:
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
input: ELAN0515:01 04F3:3142 Mouse as /devices/pci0000:00/0000:00:15.3/i2c_designware.1/i2c-2/i2c-ELAN0515:01/0018:04F3:3142.0001/input/input8
input: ELAN0515:01 04F3:3142 Touchpad as /devices/pci0000:00/0000:00:15.3/i2c_designware.1/i2c-2/i2c-ELAN0515:01/0018:04F3:3142.0001/input/input10
But no idea what could be done here, actually. Myself, I never had a ghosting input device. Probably there is a delay of input reactions due ASPM? Just a guess.
You could add touchpad and keyboard to the TLP deny list, so that it never goes into powersave mode.
That could be more a result of a feature, which is called “disable touchpad when writing” and that is enabled by default.
When you run sudo libinput list-devices you should see Disable-w-typing: enabled at the touchpad device.
I don’t know if this is anything, but i have not seen BPF load/unload repetitions like you have going on regularly. Maybe see if the interval it happens with corresponds to your windows appearing/disappearing or other issue.
disabling tochpad when writing solved it… I also changed the touchpad driver on BIOS and it seems to work now.
How can I add touchpad to the TLP deny list? I don’t know how to do that
Thank you very much, by the way
Great. 
Run:
sudo tlp-stat --pcie
Take a look at the device address. For example 0000:01:00.0. What we need is: 01:00.0 of it.
Then open the config:
sudo nano /etc/tlp.conf
Scoll down until you see RUNTIME_PM_DISABLE. Remove # at the beginning and insert the addresses:
RUNTIME_PM_DISABLE="01:00.0 00:1f.5"
Save it and close.
The addresses are examples.
Reboot the system and check again the stats:
sudo tlp-stats --pcie
I ran sudo tlp-sat --pcie but can´t identify the device:
sudo tlp-stat --pcie
--- TLP 1.5.0 --------------------------------------------
+++ PCIe Active State Power Management
/sys/module/pcie_aspm/parameters/policy = [default] performance powersave powersupersave
+++ PCIe Runtime Power Management
Enable devices = (disabled)
Disable devices = (disabled)
Device denylist = (disabled)
Driver denylist = mei_me nouveau radeon
/sys/bus/pci/devices/0000:00:00.0/power/control = auto (0x060000, Host bridge, no driver)
/sys/bus/pci/devices/0000:00:02.0/power/control = auto (0x030000, VGA compatible controller, i915)
/sys/bus/pci/devices/0000:00:08.0/power/control = auto (0x088000, System peripheral, no driver)
/sys/bus/pci/devices/0000:00:0e.0/power/control = auto (0x010400, RAID bus controller, vmd)
/sys/bus/pci/devices/0000:00:14.0/power/control = auto (0x0c0330, USB controller, xhci_hcd)
/sys/bus/pci/devices/0000:00:14.2/power/control = auto (0x050000, RAM memory, no driver)
/sys/bus/pci/devices/0000:00:15.0/power/control = auto (0x0c8000, Serial bus controller, intel-lpss)
/sys/bus/pci/devices/0000:00:15.3/power/control = auto (0x0c8000, Serial bus controller, intel-lpss)
/sys/bus/pci/devices/0000:00:16.0/power/control = auto (0x078000, Communication controller, mei_me)
/sys/bus/pci/devices/0000:00:17.0/power/control = auto (0x088000, System peripheral, no driver)
/sys/bus/pci/devices/0000:00:19.0/power/control = auto (0x0c8000, Serial bus controller, intel-lpss)
/sys/bus/pci/devices/0000:00:19.1/power/control = auto (0x0c8000, Serial bus controller, intel-lpss)
/sys/bus/pci/devices/0000:00:1d.0/power/control = auto (0x060400, PCI bridge, pcieport)
/sys/bus/pci/devices/0000:00:1d.1/power/control = auto (0x060400, PCI bridge, pcieport)
/sys/bus/pci/devices/0000:00:1f.0/power/control = auto (0x060100, ISA bridge, no driver)
/sys/bus/pci/devices/0000:00:1f.3/power/control = auto (0x040100, Multimedia audio controller, sof-audio-pci-intel-tgl)
/sys/bus/pci/devices/0000:00:1f.4/power/control = auto (0x0c0500, SMBus, i801_smbus)
/sys/bus/pci/devices/0000:00:1f.5/power/control = auto (0x0c8000, Serial bus controller, intel-spi)
/sys/bus/pci/devices/0000:01:00.0/power/control = auto (0x020000, Ethernet controller, r8169)
/sys/bus/pci/devices/0000:02:00.0/power/control = auto (0x028000, Network controller, mt7921e)
/sys/bus/pci/devices/0000:10000:e0:17.0/power/control = (not available) (, SATA controller, no driver)
/sys/bus/pci/devices/0000:10000:e0:1c.0/power/control = (not available) (, System peripheral, no driver)
/sys/bus/pci/devices/0000:10000:e0:1c.4/power/control = (not available) (, PCI bridge, no driver)
/sys/bus/pci/devices/0000:10000:e1:00.0/power/control = (not available) (, Non-Volatile memory controller, no driver)
Can you tell?