• 8 Posts
  • 67 Comments
Joined 2 years ago
cake
Cake day: December 27th, 2023

help-circle



    1. Boot live USB
    2. Find the correct partitions using lsblk (you may only need the root partition)
    3. Mount them (root goes on /mnt, others go within the root)
    4. chroot /mnt (if permission denied, run it with sudo)
    5. Search the logs or journals for the error (journald was the first to fail, maybe check its logs first)

    If you get errors like “no proc filesystem mounted”, then you also need to mount special filesystems before entering the chroot. Run these commands as root:

    mount /proc -t proc /mnt/proc
    mount /sys -t sysfs /mnt/sys
    mount /dev -t devtmpfs /mnt/dev
    




  • Here’s how to disable the GPU drivers:

    Remove “nomodeset” from the GRUB_CMDLINE_LINUX variable in /etc/default/grub

    Add “rd.driver.blacklist=nouveau modprobe.blacklist=nouveau” to GRUB_CMDLINE_LINUX instead

    Run sudo update-grub then reboot

    Note: This only works if you’re using the open-source drivers, known as Nouveau. If you’re using the proprietary drivers, this will not work.

    To check if you’re using Nouveau or the proprietary drivers, run lspci and check for “NVIDIA”, then run lsmod and check for Nouveau.

    Remember to change it back when you want to re-enable the NVIDIA drivers.

    (PS: I used this website as a source, their procedure is more complicated.)





  • I think it’s something with the monitor’s firmware.

    • Does the monitor have its own power button? Does it disconnect the power flow completely?
    • If it doesn’t, it could be the monitor’s firmware misbehaving, thinking the button was pressed when it wasn’t.
    • When you shut down your computer, see if the monitor turns off as well, or if it stays on and says “No Signal”.
    • Also, test it with another computer.

    Another possibility is with the GPU. Try disabling it temporarily, and booting with only software rendering.