I still love the particular way that Garuda configures some things from the get go. I always knew it was Arch based and might break eventually. What I didn’t expect was the stupid power button deciding that it doesn’t want to work anymore.
I did, by pushing really hard in random directions =/ I’m going to have to take it apart and clean things with a hope that it gets fixed. Until then, I’m going to have to only use sleep and not turn it off for real.
That’s how I used to turn my tower on when I was a teenager. The motherboard was also outside of the tower, lying on a piece of bubble wrap on the floor. When playing an exciting game, we’d sometimes kick the graphics card out of place.
I can’t do the lid shutdown thing because the built-in screen also has serious issues. It is very finicky. I just use either the terminal or KDE’s built-in feature to do it. I’ve really put this poor machine through hell.
I just have a script that repeats the “install-kernel” command and the “bootctl install” one that I run after every big update. It should be fine without them, right? Too many times the kernel one fails in the pacman update chain and I’ve had to chroot from a live USB too many times to do the bootctl install to put the correct bootloaders in the efi partition to skip the manual bootclt install from my actual PC after updates.
Just in case. It takes 2 seconds vs searching the pendrive, loading, typing in an European keyboard when the live USB asumes it’s american, searching the chroot command on my phone… All of this when I just want to relax. Weird stuff I know.
Me updating my Arch install in the morning at school (there’s faster connection):
But, with current install I finally started writing logs of all manual changes I make (config updates, created symlinks outside home dir, package installations, etc…). I’ll finally know what I did instead of trying to guess what weird thing I did 2 years ago.
This is a fantastic idea. Keep a config diary. I can imagine a teenager doing this and eventually getting in trouble with the law. Parents open the diary only to discover scribbled bash scripts in confusion.
For real, though, I’m going to journal it all and upload to NextCloud.
Let us pray that he will be succeeded by a worthy descendant. At least we can always find refuge in BSD - it has not yet started to ensh*tify as I’ve heard
Everyone is an atheist until they do kernel/full system update on their daily driver machine
I still love the particular way that Garuda configures some things from the get go. I always knew it was Arch based and might break eventually. What I didn’t expect was the stupid power button deciding that it doesn’t want to work anymore.
Yeah that kind of device failure is really frustrating, did you manage to make it work?
I did, by pushing really hard in random directions =/ I’m going to have to take it apart and clean things with a hope that it gets fixed. Until then, I’m going to have to only use sleep and not turn it off for real.
You can just yank it off and short the wires manually to boot ☝🏻🤓
instructions unclear: hooked the power button circuits up to a car battery and caused 2 battery fires
Nice, now it is warm
That’s how I used to turn my tower on when I was a teenager. The motherboard was also outside of the tower, lying on a piece of bubble wrap on the floor. When playing an exciting game, we’d sometimes kick the graphics card out of place.
I rarely shutdown my laptop. Most days I just close lid when I am done and back to what I was doing next day instantly.
I can’t do the lid shutdown thing because the built-in screen also has serious issues. It is very finicky. I just use either the terminal or KDE’s built-in feature to do it. I’ve really put this poor machine through hell.
pacman -Syu hangs after updating kernel but before mkinitcpio.
Jesus, take the wheel.
I just have a script that repeats the “install-kernel” command and the “bootctl install” one that I run after every big update. It should be fine without them, right? Too many times the kernel one fails in the pacman update chain and I’ve had to chroot from a live USB too many times to do the bootctl install to put the correct bootloaders in the efi partition to skip the manual bootclt install from my actual PC after updates.
Just in case. It takes 2 seconds vs searching the pendrive, loading, typing in an European keyboard when the live USB asumes it’s american, searching the chroot command on my phone… All of this when I just want to relax. Weird stuff I know.
Me updating my Arch install in the morning at school (there’s faster connection):
But, with current install I finally started writing logs of all manual changes I make (config updates, created symlinks outside home dir, package installations, etc…). I’ll finally know what I did instead of trying to guess what weird thing I did 2 years ago.
This is a fantastic idea. Keep a config diary. I can imagine a teenager doing this and eventually getting in trouble with the law. Parents open the diary only to discover scribbled bash scripts in confusion.
For real, though, I’m going to journal it all and upload to NextCloud.
True. I started to pray to GabeN recently too.
Let us pray that he will be succeeded by a worthy descendant. At least we can always find refuge in BSD - it has not yet started to ensh*tify as I’ve heard
Me, installing Linux mints major update like a month ago after finally getting things just right:
If it breaks, new distro I guess 🤷
chuckles in immutable distribution