• 8 Posts
  • 779 Comments
Joined 2 年前
cake
Cake day: 2023年12月20日

help-circle
  • Pop!_OS is quite an unorthodox choice for a server OS, ain’t it? I’m genuinely interested in why you chose it specifically over, say, Debian or Ubuntu.

    I ran Debian and derivatives (Ubuntu, Mint), Arch and derivatives (EndeavourOS, Manjaro), Fedora and OpenSUSE, although each one on a very “user” level; I’m no IT guy, I just value what Linux gives me and am forced to learn to use it well.

    Each has their merits. Currently, I go with OpenSUSE because it gives reasonable stability while not going ancient. When set up right, you can rely on it to keep doing things the same way, without needing to intervene manually. It also features correctly set snapper by default, which ensures I, as a generally non-technical user, won’t shoot myself in the foot.

    Ideally, I would go with OpenSUSE Slowroll, as I love the concept, but it is still experimental and I don’t want both my machines to rely on beta builds. Still, my laptop has it installed and it works like a charm. The idea of “nearly bleeding-edge, but behind the most adventurous users” is why I chose Manjaro as my first distribution back in the day. Sadly, it is poorly managed, and issues arising with AUR only make things worse. OpenSUSE Slowroll feels to me like Manjaro done right.

    As per other distributions I tried:

    • Debian gets very ancient very quickly (and even if you rely on flatpaks, system packages are, like, OLD)
    • Ubuntu is poorly managed and filled with controversies, I don’t feel like I own my computer
    • Mint is nearly a single distribution that doesn’t officially ship with KDE (likely because most of its userbase would ditch Cinnamon immediately, huh) and has caused issues on my machines specifically
    • Arch/EndeavourOS is “move fast and break things”, and things DO break unless you manually intervene on numerous occasions based on whatever forums tell you. Also, on all Arch-based systems, I face insane lags and RAM hogging when moving large files. I don’t know why.
    • Manjaro, as I said, is well-intentioned, but poorly executed. It breaks from so many things, which makes it lose its novice appeal. Still, it’s cozy and not scary to enter, so this is where I started, and then learning to fight the bugs taught me a lot about Linux
    • Fedora needs some work out of the box, but is generally stable and nice. However, the community is too fast to make breaking decisions (like when they ditched X11, which broke my gf’s work because her tools don’t work with Wayland, and she went with Fedora). Also, I’m not thrilled by its association with Red Hat, which turns increasingly…Canonical.

    So, OpenSUSE it is. I never knew I would end up here, but here I am. Slowroll on my laptop for the last half a year or so convinced me to ditch EndeavourOS on my desktop and go OpenSUSE as well. Up to a rough start, but hoping it will go well after that.


  • Nah, YaST is still a piece of crap imo, both antique and impractical for most purposes. They should either make it modern and user-friendly, or phase it out.

    That said, it kinda helped me to locate the correct system package this time.

    In any case, OpenSUSE Slowroll is already my daily driver on laptop, which doesn’t have an NVidia GPU, and it’s part of the reason why I decided to give it a spin on desktop. At the end of the day, the issue got resolved, and now I can keep it, hopefully, in here too.





  • sudo modprobe nvidia gives the following output: modprobe: ERROR: could not insert 'nvidia': No such device

    dmesg gives the following:

    [ 56.697148] [   T2989] NVRM: The NVIDIA GPU 0000:27:00.0 (PCI ID: 10de:1c03)
                              NVRM: installed in this system is not supported by open
                              NVRM: nvidia.ko because it does not include the required GPU
                              NVRM: System Processor (GSP).
                              NVRM: Please see the 'Open Linux Kernel Modules' and 'GSP
                              NVRM: Firmware' sections in the driver README, available on
                              NVRM: the Linux graphics driver download page at
                              NVRM: www.nvidia.com.
    [   56.702043] [   T2989] nvidia 0000:27:00.0: probe with driver nvidia failed with error -1
    [   56.702102] [   T2989] NVRM: The NVIDIA probe routine failed for 1 device(s).
    [   56.702104] [   T2989] NVRM: None of the NVIDIA devices were initialized.
    [   56.702837] [   T2989] nvidia-nvlink: Unregistered Nvlink Core, major device number 238
    

    Guess it won’t work with my card? Gonna read through that (quite massive) readme, it seems…

    P.S. Looks like everything pre-Turing does not support open drivers, and OpenSUSE did not communicate it well. Looking into ways to install proprietary driver.

    P.P.S. Wait, it gets worse! The main way to install the proprietary driver is through install-new-recommends, BUT this installs open drivers on unsupported cards! This may be a good reason for a bug report once I figure the rest out.






  • Allero@lemmy.todaytoLinux@lemmy.mlOne GNOME session, multiple styles
    link
    fedilink
    arrow-up
    18
    arrow-down
    1
    ·
    edit-2
    15 天前

    Honestly I just want KDE to do the backbone and GNOME to do the designs.

    Adwaita apps look just right, minimalistic yet powerful, pinnacle of modern simplified designs. Everything you actually need is close, and the rest doesn’t clog the view.

    The rest of GNOME is heavily meh. Customization is next to nothing, and generally any workflow falling outside the one window = one task paradigm is gonna be a pain. Settings are convoluted and sometimes straight up unreachable without additional tools or config edits (and sometimes they don’t even apply).

    I guess what unites Adwaita and GNOME project overall is the stubborn adversity to users making it comfy for themselves - it’s the GNOME way, or no way. And while Adwaita is at least actually good in its defaults, GNOME is not.

    KDE, on the other hand, is brilliant as a desktop environment, but menus could be so, so much better. So, when I have a choice, I use Adwaita-themed apps on KDE. With proper theming on KDE side of things, they come together just right.






  • Good. Seriously, I hope such actions will be met with complaints and lawsuits everywhere.

    Sexual life is a very sensitive and intimate subject, and it’s bad enough that she even had policemen invade it by opening the box (though this in particular is obviously a necessary part of police operations), let alone make a laughing matter out of it.

    In general, though, I hope we will be able to eventually get more open about such things, so that it would be seen as a regular set of household items, even if it’s hidden from plain sight.




  • Allero@lemmy.todaytoTechnology@lemmy.worldThis website is for humans
    link
    fedilink
    English
    arrow-up
    20
    ·
    edit-2
    1 个月前

    Locking information into corporate-controlled loops is antithetical to freedom and accessibility.

    Having singular proprietary point of entry, or even few of them, into the entire knowledge of mankind is not sharing.

    This is the part people are willing to protect. Actual peer-to-peer sharing of information, with as little private choke points as possible.

    And having the web ruined by SEO is not an argument to keep going. It’s already worse than it should be, and search engines already provide worse quality results than before. This needs to be reversed, not reinforced.


  • Allero@lemmy.todaytoTechnology@lemmy.worldThis website is for humans
    link
    fedilink
    English
    arrow-up
    26
    ·
    edit-2
    1 个月前

    When the Web was first designed, some of the concerns we have today were nonexistent.

    I believe in freedom of information, and would love for the information I share to be accessed in any way a given user wants.

    But I have to stand defensive and support the author here, too. The modern LLM boom aims to essentially replace original resources with AI-generated summaries step by step. This is detrimental to the Internet, and to knowledge as we know and preserve it.

    First, there is an event commonly called Google Zero, which is briefly mentioned in the article. If you don’t know what it is, it is the not-so-hypothetical-anymore moment when Google (or, really, any other large player) essentially accumulates all information on the Web, feeds it to AI, and since then doesn’t serve links anymore, going straight to answers based on training data. Users will jump to this - they already do - because it offers convenience. But for any independent creators it means having no audience, no money, and no means to produce new quality content, trapping users in a self-containing loop that loses nuance, actuality, and truthfulness, and stays under corporate control. This goes beyond cooking recipes and personal notes - it permeates science, political discussion, and much more.

    Second, LLMs multiply traffic coming to sites, which becomes an infrastructural problem. Bots access sites at much higher rates than humans do, and when their intent is to scrape your entire website every now and again and there are dozens of them, this becomes huge.

    Third, having proprietary models train on the data I provide without any attribution, copyright etc. makes giant corporation profit off my back, while at the same thing making it so that less genuine users will see what I produce. This means careers of authors, journalists etc. are dying, and this also means they are left free to abuse each and every one of us without any consent.

    Fourth, and I wonder if you see it by now, LLMs and the way they represent data, along with SEO tools meant to drive information through the search bots, begin to shape how we talk. All I say doesn’t have to be a list of points, yet it is. It could be less verbose, more readable, yet it is the way it is. Because when we interact with the products of such developments too much, we begin shaping our own language in a way that is less human-readable and more meant for machines, without us often being aware of it. This is a real issue of communication.

    So, as much as I hate it, I’m gonna protect a lot of the data I share.