monolith: fix suspend wakeup from kb, disable from mouse
This commit is contained in:
parent
d823926714
commit
1ebe2d8a34
1 changed files with 6 additions and 1 deletions
|
|
@ -120,9 +120,14 @@ in
|
|||
virtualisation.virtualbox.host.enable = true;
|
||||
|
||||
services.udev.extraRules = ''
|
||||
# Arm all USB root hubs (vendor 1d6b) so any USB device can wake the system.
|
||||
# Wakeup only fires if the device on the end also has wakeup enabled, so we still
|
||||
# disable it individually for devices that must NOT wake the system (see below).
|
||||
ACTION=="add" SUBSYSTEM=="usb" ATTR{idVendor}=="1d6b" ATTR{power/wakeup}="enabled"
|
||||
# Fix broken suspend with Logitech USB dongle
|
||||
# The mouse/mousepad receiver wakes the system right after suspend, so disable its wakeup.
|
||||
# `lsusb | grep Logitech` will return "vendor:product"
|
||||
ACTION=="add" SUBSYSTEM=="usb" ATTR{idVendor}=="046d" ATTR{idProduct}=="c547" ATTR{power/wakeup}="disabled"
|
||||
ACTION=="add" SUBSYSTEM=="usb" ATTR{idVendor}=="046d" ATTR{idProduct}=="c53a" ATTR{power/wakeup}="disabled"
|
||||
# Force all disks to use kyber scheduler
|
||||
# For some reason "noop" is used by default which is kinda bad when io is saturated
|
||||
ACTION=="add|change", KERNEL=="sd[a-z]*[0-9]*|mmcblk[0-9]*p[0-9]*|nvme[0-9]*n[0-9]*p[0-9]*", ATTR{../queue/scheduler}="kyber"
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue