• EccTM@lemmy.ml
    link
    fedilink
    English
    arrow-up
    39
    ·
    7 months ago

    Nvidia Arch user here, are you just forgetting to rebuild your kernel modules after a kernel or nvidia driver update?

    You can just add a pacman hook that triggers mkinitcpio -P after the linux or nvidia packages are updated. I’ve never had a no-GUI situation from a stray update… maybe one or two that were my own doing when trying to set up UKI’s though.

      • yeehaw@lemmy.ca
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        7 months ago

        I think dkms is for inserting kernel modules, but I’m dumb and what’s the difference between both these approaches?

    • Dnn@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      7 months ago

      I just followed the note that’s mentioned on the top of your link and installed the Nvidia driver as dkms package. I originally did that because of trouble with a new driver version and temporary downgrading is much smoother with dkms.

      Also never had issues with the DE starting properly after upgrade since then.

      • EccTM@lemmy.ml
        link
        fedilink
        English
        arrow-up
        2
        ·
        7 months ago

        I’m usually using nvidia-beta drivers from AUR because they’re newer, so I just added the hook as an insurance policy.

        The DKMS drivers are probably the safer option because they’ll handle rebuilding the kernel modules. Even though (like EddyBot said) the kernel and nvidia packages are supposed to get updated together, sometimes you can spam pacman -Syu at the wrong time and only one package is updated and things go wonky…

    • herrvogel@lemmy.world
      link
      fedilink
      arrow-up
      7
      ·
      7 months ago

      Don’t bother with the tty. If experienced chess players can play entire games in their heads, why can’t you just do the same to use a computer? Just type away and use your superior power usering skills to visualize the output in your head.

    • Evrala@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      6 months ago

      Just got a new laptop and put an arch flavor on it, keep thinking of going back to Tumbleweed. I’ve kept on Arch derivatives cause of the AUR, but I haven’t actually touched the AUR in a while, and a couple of the things I used the AUR for are now being published as flatpaks by the creators because of the Steam Deck.

    • Séra Balázs@lemmy.worldOP
      link
      fedilink
      arrow-up
      3
      arrow-down
      2
      ·
      7 months ago

      Last time I tried it, the more custom stuff I put on it(custom color scheme, window decorations etc.) the more it fell apart

    • Yer Ma@lemm.ee
      link
      fedilink
      arrow-up
      5
      arrow-down
      4
      ·
      7 months ago

      Funny because just like those door to door bible sales, Tumbleweed promises magic and salvation, but completely crumbles under any stress or expansion

      • Kusimulkku@lemm.ee
        link
        fedilink
        arrow-up
        5
        ·
        7 months ago

        Not my experience at all. It’s the one distro that stopped my distro hopping.

        Besides, something goes fucky or (more likely in my case) I fuck something up, I can just roll back the changes with a single command and reboot. It’s awesome. I’ve also used to just test things out, removed all KDE stuff, installed GNOME, tested it out for a while and then did a snapper rollback. The system was just like I hadn’t changed anything. It’s really cool, more distros need this feature.

        • Yer Ma@lemm.ee
          link
          fedilink
          arrow-up
          1
          arrow-down
          1
          ·
          7 months ago

          Wild, every time I’ve tried using it on both metal and as a VM it has self destructed rather quickly. The last few times, just doing an update after the initial install broke the system for various reasons… but everyone has different hardware and software mixes I suppose

    • excitingburp@lemmy.world
      link
      fedilink
      arrow-up
      7
      ·
      7 months ago

      There’s a difference between “can” and “want.” For example, OP might have been planning to watch his home vids with your mom, but couldn’t due to a rolling update.

  • Vilian@lemmy.ca
    link
    fedilink
    arrow-up
    8
    ·
    7 months ago

    well arch moment, you could use snapshots or ostree to rollback if something like that happen

    • Séra Balázs@lemmy.worldOP
      link
      fedilink
      arrow-up
      5
      arrow-down
      1
      ·
      7 months ago

      I usually just do a full reinstall, it’s faster, requires less storage, and it’s more futureproof. I have my home folder at a different partition, so the files aren’t a problem. Archinstall made this a lot easier, and i love it.

      • Kusimulkku@lemm.ee
        link
        fedilink
        arrow-up
        3
        ·
        7 months ago

        After being with my current distro and install for several years I’ve accumulated so many small changes and tweaks into the system that it’d take ages for me to get back to where I am with a fresh install. Snapper snapshots for life

      • Vilian@lemmy.ca
        link
        fedilink
        arrow-up
        1
        ·
        7 months ago

        yeah, separated home folder is also a solution, now, faster than “rpm-ostree reset” or pulling the old snapshot? idk

  • AeonFelis@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    7 months ago

    As long as I can get into the terminal I can fix the GUI. What really sucks is when it something that runs in the DM init sequence was using Python but a Python upgrade changed the import path and no it keeps restarting and I need to boot from a USB to disable that service so I can log into something and properly fix it.

    • adavis@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      7 months ago

      Pass something stupid via your bootloader so it aborts boot and dumps you in an initrd busybox shell. No usb required.

      This was my poor man’s boot environments when I was using zfs on root. I had a pacman hook to snapshot before package transactions, then if it became unbootable I’d interrupt the following boot attempt, edit my grub command line with something wrong so I’d get dumped in the busybox shell, import my zfs pool and roll back before finally rebooting again.

      • AeonFelis@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        7 months ago

        That’s nice. I’ve later googled it and found out that I could have added 3 to the end of the grub command to make it boot in runlevel 3 which does not trigger the GUI, but I guess your way could also bypass boot issues that prevent even non-gui boot.

        I also see that there is runlevel 1, which is kind of an emergency mode, so maybe that would be the best thing to use?