Skip Navigation

Posts
1
Comments
75
Joined
3 yr. ago

  • Cute :3

  • You might not want to trust chatgpt with anything where accuracy and specificity are both essential to not brick a machine or lose data though. Especially since you can't check the sources it used. It did a decent job at getting the general workflow right, but even that's not a given. :/

  • Foxit still provides a free version that's linux compatible. Its been a lifesaver at work to do document signing without messing everything up. It may take a little tweaking to run, but it's worth a try for forms.

  • Gotta love terminator. I also always greatly appreciated how uncluttered and to the point its ui was, while being modern and configurable.

  • You could switch all your repos to the core Arch ones. I did that by accident once, and it was fine (although, I did switch them back eventually). Maybe it’d add release stability? I’m not really clear how the EOS repos vary off the baseline, except by adding some custom packages.

    They don't afaik. EOS uses Arch's repos directly, unlike Manjaro. Just adds its own on top for all the fancy EOS stuff. Which is why EOS was immediately affected by the grub meltdown and not Manjaro. (which kinda digs a few holes in the stability hypothesis, though Manjaro is another kettle of fish tbf)

    Snapper sounds really interesting, and I didn't expect "super easy" to be the feedback there. Sounds a bit overkill for my use case at home but I might look into it for work. Thanks for the info!

    Oh god a borked BIOS is my nightmare... I don't even know how you'd go about fixing that on a modern PC mobo... Let's not jinx it shall we?

  • Ah no no, maybe I was unclear, but the issue occurs during the initramfs stage, long before any of my KDE/Plasma nonsense had any chance to run! KMS has nothing to do with KDE. ^^

    Edit: You still likely are an outlier though :)

  • Mostly using eos-update by clicking on the notification, unless I'm on a terminal where I still have the yay reflex from arch. I should remember to use eos-update though, I do appreciate the extra housekeeping.

    Nop, I avoid nvidia as much as I can as well, I already can't avoid it at work, too much driver drama. Ryzen and radeon it is, with (almost) no fuss.

    Also mostly using wayland, it works well even on KDE, but got Xorg around just in case, and I've had the occasional issue on both. That being said, it's plymouth that blows up, long before the graphical session is opened, so that shouldn't have an influence either.

    Maybe I'm just a black cat, and/or maybe it just comes with the territory when you stay long enough on a bleeding-edge-use-at-your-own-risk kinda distro and update almost every day. Something's bound to go wrong eventually. Which, has also "been Arch with an easier install" for me, tbf.

    Gonna investigate a bit more today, couldn't be asked yesterday. But if you're curious I can keep you updated when I find a fix. :)

    Edit: Found the solution by essentially doing the same thing the folks on reddit did with nvidia by enabling early KMS start, and learning quite a bit along the way. Apparently it's now required by Plymouth and my system didn't get the memo? Or something? Eh it works.

  • Yeop, you can say that again. Can't read the Arch wiki on a Nokia 3310 for sure lol

    Tbh I'm not too careful about updates, I have regular backups and grub exploding wasn't enough to stop me, so eeeeh, if something really goes awfully wrong I have enough free time to deal with it and use it as a learning experience. I know I should be smarter about them like you are, but on my personal computer I just cannot be asked. ^^

  • It's exactly the opposite for me. Why? Because I'm just not used to Windows and nothing is where I expect it, or works as I would expect, and a lot of it makes no sense to me. On the other hand, I've been daily driving Linux since 2010 and I know what to do for most of the things I want to change in my system.

    It's literally just a matter of what you're used to. ¯(ツ)

  • https://endeavouros.com/news/full-transparency-on-the-grub-issue/

    A LOT of people's PCs were bricked, including mine. No boot, just blank screen with blinking cursor. Thankfully Endeavour's team was quick to react (quicker than Arch, as it happens) and published a full tutorial on how to chroot into your system and downgrade grub, but that already required a good level of knowledge and confidence in the Linux system as none of this was trivial, or intuitive for any stretch of the imagination. I woudl imagine most affected EndeavourOS users who were new-ish to Linux threw the towel that day. Wouldn't blame them, it was jarring even for me, and it wasn't my first chroot.

  • I daily drive endeavour and love it to bits but let's not recommend it to someone who wants an OS with no fuss. It WILL break and require experience to fix. Remember the grub update fiasco?

  • No offense but this is highly anecdotal. When my Linux systems broke, I've always found good leads to solutions on the internet with a good search. On the other hand, every time Windows broke on me, it's been near impossible to find relevant information as everything is drowned in a sea of basic nonsense, and the built-in tools that were supposed to help me, e.g., revert the system to a previous state, either errored out or did nothing, leaving me only with reinstalling the whole system as an option. Absolute nightmare.

  • Wow when you out it that way it sounds even dumber

  • Thank you so much! <3

    I'll be honest, it was a struggle, especially with yarn this thin, and I almost gave up, but I'm glad I didn't! ^^

    Also don't feel bad for failing to pick up crocheting, that happened to me too the first time. It was such a disaster that I didn't touch a crochet for about 25 years lol