Oh no, you!

  • 0 Posts
  • 19 Comments
Joined 2 months ago
cake
Cake day: November 3rd, 2024

help-circle
  • Which distro(s) did you try?

    I’ve been a linux user for 20-25 years (exclusively for 10), and I find that Linux Mint works pretty well out of the box. I’ve heard others recommend other distros for the same reason, but I’ll let someone with first hand experience recommend them, as Mint is my go-to distro for desktops and laptops.

    And just a tip: Take people who go “Don’t use X distro because of Y” with a grain of salt. All distros have their own quirks (Mint’s being relatively old packages), but whatever works for you is the best distro for you, and that’s the most important part.

    I recently got myself a brand spanking new and relatively high end laptop, and everything worked out of the box. The only “problem” was that I wasn’t satisfied with the wifi performance (it worked, just not as fast as it should), so I installed a different kernel module. ome to think of it, I had to select NVIDIA proprietary driver as well, due to it defaulting to an open source driver. But it’s just a few mouseclicks (yes, all GUI) to get that sorted.

    Allegedly AMD has better support for linux than NVIDIA does, so I guess that’s a good omen for you.

    The rest worked flawlessly, including the proprietary lenovo hotkeys that requires it’s own Lenovo program on windows - I was prepared to live without those, but I’m glad I don’t have to. Fn+Q to change power/performance/cooling balance on the fly is pretty neat.

    I have no idea how to edit videos, and I’ve never touched any software for doing so, so I can’t help you there. Same goes for CAD stuff. I think it’s safe to assume that doing arduino stuff on linux is well supported, though.



  • neidu3@sh.itjust.workstoLinux@lemmy.mlGRUB is confusing
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    4 days ago

    You have one per installed kernel. Not sure what (if any) automagic is common for removing old kernels, I guess this varies between distros, but at least on my computers, old kernel remain. At least the previous one, maybe more. It comes in handy in case a kernel upgrade breaks something, which it actually did recently on one of my laptops - makes it easier to boot from old kernel and revert.

    EDIT: I just checked. I have just one on my daily driver. It’s quite new, and I don’t think I’ve had a kernel upgrade on that one, so it makes sense.

    On my work laptop (the one with borked kernel upgrade) I have two.

    So what you most likely have is one or more vmlinuz-version-numbers, and then simply a symlink named just vmlinuz to the version you boot from.


  • neidu3@sh.itjust.workstoLinux@lemmy.mlGRUB is confusing
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    5 days ago

    Short answer to your last paragraph:
    vmlinuz is the kernel. It ends with z instead of x, because it’s z-compressed to save space. (I’ve heard that it’s possible to use an uncompressed kernel for that 1ms faster boot time)
    Initramfs (not intramuscular, which my autocorrect thinks is appropriate) is a small filesystem blob, “initial ram filesystem”, meant to be loaded directly into ram to allow the kernel to talk to your hardware via drivers. It also has a lot of binaries needed to perform other tasks that need to run before the root filesystem is mounted.












  • I love how features like these are quickly adopted by some dev in some basement, resulting in support built in the OS and automatically supported.

    For example, I recently got myself a brand new Lenovo Legion 7, and the intention was always to nuke the windows install and get Linux up and running. I was curious about the hotkey too adjust the fan/cooling schema, as it seemed to rely on some proprietary Lenovo windows program.

    Less than an hour after picking it up at the post office I had a basic Linux Mint ip and running with the GPU drivers working well, and the hotkeys worked out of the box.




  • Yes-ish. Updated graphics/reskin was the original idea, but this changed to add some long-wanted features. This is where the problem began: The reskin was built on the old KSP source base, which the original developers have admitted was very difficult to work with.

    When the development changed focus, the feature scope was simply not realistic with so much legacy code getting in the way.

    Worst of all, the devs working on KSP2 were barred from talking to Squad (the original developers) about ANYTHING. No communication about specific parts of the code. No communication about why various approaches to different problems were chosen. Basically due to corporate stupidity that focused on a quick buck through a resin, the developers had to pretty much reinvent the wheel a bunch of times.

    I think the initial corporate plan was a reskin-scam. The development plan involved a lot more than that. These goals were simply incompatible, which is why everything was so delayed and buggy.

    There were some really passionate and talented devs on the team, but they didn’t get what was needed to build what KSP2 could’ve (and should’ve) been.

    ShadowZone made a couple of really good in-depth videos on what went wrong, and this sums it up well: https://youtu.be/NtMA594am4M