You are not logged in.
This is what I see when a lagspike happens:
ac_adapter ACPI0003:00 00000002 00000000
ac_adapter ACPI0003:00 00000080 00000000
ac_adapter ACPI0003:00 00000002 00000001
ac_adapter ACPI0003:00 00000080 00000001
ac_adapter ACPI0003:00 00000002 00000000
ac_adapter ACPI0003:00 00000080 00000000
ac_adapter ACPI0003:00 00000002 00000001
ac_adapter ACPI0003:00 00000080 00000001
ac_adapter ACPI0003:00 00000002 00000000
ac_adapter ACPI0003:00 00000080 00000000This is me unplugging the charger:
ac_adapter ACPI0003:00 00000002 00000000
wmi PNP0C14:01 000000ff 00000000
wmi PNP0C14:01 000000ff 00000000
battery PNP0C0A:00 00000080 00000001
ac_adapter ACPI0003:00 00000080 00000000
ac_adapter ACPI0003:00 00000080 00000000
battery PNP0C0A:00 00000081 00000001
battery PNP0C0A:00 00000080 00000001This is me plugging it back in:
ac_adapter ACPI0003:00 00000002 00000001
wmi PNP0C14:01 000000ff 00000000
wmi PNP0C14:01 000000ff 00000000
battery PNP0C0A:00 00000081 00000001
battery PNP0C0A:00 00000080 00000001
ac_adapter ACPI0003:00 00000080 00000001
ac_adapter ACPI0003:00 00000080 00000001Last edited by TheAirBlow (2025-06-22 05:01:05)
Offline
My solution for now is:
sudo acpidump -o acpi-full.dat
sudo acpixtract acpi-full.dat
nano dsdt.dsl
# find ACPI0003
# find Method (_STA, 0, NotSerialized)
# replace return value with 0
iasl -f -tc dsdt.dsl
sudo mkdir /etc/initcpio/acpi_override
sudo cp dsdt.aml /etc/initcpio/acpi_override/
sudo nano /etc/mkinitcpio.conf
# add acpi_override to HOOKS
sudo mkinitcpio -PThis stops the kernel from detecting the Power Source Device, and therefore prevents any events from being dispatched.
Last edited by TheAirBlow (2025-06-22 05:28:34)
Offline
Battery events are still dispatched though, which also cause lag, but now the lagspikes aren't as loboriously long. At least I think they aren't ![]()
Disabling them would be a far fetch and probably cause issues, and that way I at least know when the charger fully disconnects so I can accordingly.
Last edited by TheAirBlow (2025-06-22 05:37:44)
Offline
The GPU still is aware of charger events, so this didn't help. Guh.
I assumed it was because of the driver because it's just fine on Windows, but it appears to be handled by the hardware/firmware/BIOS (I assume)
Last edited by TheAirBlow (2025-06-22 06:58:29)
Offline
seth wrote:You could use the handler.sh script to maybe figure what these events are.
Is the charger plug possibly loose?I assume it is. Sometimes I plug it in and I hear a concoction of plug in/plug out sounds from Plasma.
If there's no obvious physical defect you can just "unbend" (be careful to not snap stuff) - how much will a replacement set you back?
Also, if this is caused by tension of the cord angling the charger, maybe there's a physical fix where you kind wedge the cable/plug into a stable position from the outside?
I assumed it was because of the driver because it's just fine on Windows, but it appears to be handled by the hardware/firmware/BIOS (I assume)
If it's handled by the firmware, windows would be affected, too - no?
Is asusd still running?
Offline
TheAirBlow wrote:seth wrote:You could use the handler.sh script to maybe figure what these events are.
Is the charger plug possibly loose?I assume it is. Sometimes I plug it in and I hear a concoction of plug in/plug out sounds from Plasma.
If there's no obvious physical defect you can just "unbend" (be careful to not snap stuff) - how much will a replacement set you back?
Also, if this is caused by tension of the cord angling the charger, maybe there's a physical fix where you kind wedge the cable/plug into a stable position from the outside?I assumed it was because of the driver because it's just fine on Windows, but it appears to be handled by the hardware/firmware/BIOS (I assume)
If it's handled by the firmware, windows would be affected, too - no?
Is asusd still running?
Same still happens without asusd running.
And yeah, I didn't notice any lag while on Windows for whatever reason.
Last edited by TheAirBlow (2025-06-22 07:32:33)
Offline