I post content. You view content. I moderate content. You no like, you no pay

  • 3 Posts
  • 22 Comments
Joined 1 year ago
cake
Cake day: June 6th, 2023

help-circle



  • Red@reddthat.comtoLinux@lemmy.mlKDE often not sleeping when idle
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    5 months ago

    Close, that is because of the wakeup. (I think)

    See all of your devices that make your computer: cat /proc/acpi/wakeup

    Toggle all of them one by one:

    echo GPP0 | sudo tee /proc/acpi/wakeup (where GPP0 is the item in the left hand column)

    Cat again if you want to see if it’s disabled

    Keep going until you find the one that is ‘waking’ your computer back up after a sleep.

    When you find the right one, add it to your crontab so it turns it off on every boot:

    sudo crontab -e
    @reboot echo "GPP0" > /proc/acpi/wakeup
    








  • When I interview people, I don’t care how they get an answer, I want to see that they can get to the answer, ideally the correct one, but it doesn’t matter if it’s wrong. I want them to show me their problem solving skills and that they understand their own solution.

    If you can read existing code and understand complexities you are already better than 80% of these hires.








  • Those wakelock devices map to specific devices. If you run lsusb you will see the pci:0000:00:1c.4 and others.

    • Find the one that your mouse is.
    • Do the echo command into that device RP05.
    • Confirm it’s disabled.
    • suspend & then try moving the mouse
    • if it works edit the systemd script with the correct echo command
    • make sure you make the service Enabled (otherwise it won’t start on boot)
    • reboot and confirm it’s still disabled.

    That should be what is needed to disable waking up from the mouse.



  • Yep. Keep the WAN port dhcp Client enabled if you can, just one less thing to worry about.

    Also take note that when you change the static IP of the new router it would conflict with the old one (and dhcp might fail). So you might need to set your local clients IP. Take note of the configuration it has and the steps to set it manually.

    The rest all sounds right.


  • Your router’s IP can be anything. Choose any internal IP address on your subnet.

    You can have 2 routers on the same subnet just make sure you disable DHCP on the new one while you perform the setup of everything else.
    Then when you want to switch over, toggle on dhcp on the new router and replace the cables and you should be fine. You’ll know it’s working when you plug into it and get a default route of the new router.