• beefbot@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    14
    arrow-down
    3
    ·
    5 months ago

    Good god, it takes 25 years to set up Linux? What happened to 8 hours for every minor problem?! I’m never gonna be free of WinBLOWS :(

  • Chemical Wonka@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    12
    ·
    edit-2
    5 months ago

    You gonna be very upset when you realize that Fedora ditched support for some essential codecs for hardware acceleration on Intel Integrated Graphics and any forum won’t be able to help you properly. Bullshit experience. Arch is much better (btw)

    • thayer@lemmy.ca
      link
      fedilink
      English
      arrow-up
      14
      ·
      5 months ago

      This is old news and long-since resolved by RPM Fusion and/or flatpaks.

      • Chemical Wonka@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        edit-2
        5 months ago

        In fact you can but this didn’t solve the problem. I installed all drivers possible but nothing fixed the high CPU usage when I opened some apps like calculator and Super Tux Kart for example. I have a Intel Nuc 12 gen and with arch is all working flawlessly

        • thayer@lemmy.ca
          link
          fedilink
          English
          arrow-up
          2
          ·
          5 months ago

          I’m sorry to hear of your bad experience. Four of my Intel/AMD workstations are running Fedora Silverblue and Kiniote and I’ve thankfully never experienced the same. Either way, I’m glad you’ve found some success with Arch. It’s still my go-to for the command line and all container work.

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

      Why do we gotta be like this?

      Fedora is fine, it’s the work of seconds to add non-free codecs.

      • thayer@lemmy.ca
        link
        fedilink
        English
        arrow-up
        13
        ·
        5 months ago

        They’re probably talking about Fedora dropping the h.264, h.265 and VC1 VA-API support back in 2022 for legal reasons due to patents:

        https://www.phoronix.com/news/Fedora-Disable-Bad-VA-API

        It’s largely a non-issue as you can easily install the patched Mesa from RPM Fusion, and I believe all Flatpaks incorporate the codecs already.

        Don’t get me wrong, Arch is great and it will always have a place in my heart, but I also think Fedora is a top-tier project and I completely understand why they weren’t comfortable risking patent law unnecessarily.

        • Spectacle8011@lemmy.comfysnug.space
          link
          fedilink
          arrow-up
          2
          ·
          5 months ago

          I believe all Flatpaks incorporate the codecs already.

          Flathub even has hardware decoding with the drivers they distribute. However, Flatpak applications need to specifically opt in to ffmpeg-full rather than the normal ffmpeg package, which has support for patent-encumbered codecs.

          Fedora Flatpaks, on the other hand, have no such codec support.

          Fedora is a top-tier project and I completely understand why they weren’t comfortable risking patent law unnecessarily.

          💯

          • thayer@lemmy.ca
            link
            fedilink
            English
            arrow-up
            1
            ·
            5 months ago

            I have to admit one of the first things I do when setting up a Fedora atomic distro is disable the Fedora flatpak repo and replace all existing apps with Flathub equivalents. Still, good info to keep in mind!