Jure Repinc

Digital and software freedom/rights advocate from Slovenia, Europe. Also a member of the Pirate party. You can find me on Mastodon: @JRepin@mstdn.io

  • 217 Posts
  • 44 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2023

help-circle






















  • Jure Repinc@lemmy.mltoGaming@lemmy.mlHDMI 2.1
    link
    fedilink
    English
    arrow-up
    32
    ·
    7 days ago

    Oh how I wish those TV manufacturers would get rid of HDMI and replace it with DisplyPort. HDMI mafia does not allow opensource implementations of HDMI specification and so not all latest features of it can be supported by graphics card drivers on GNU/Linux. Death to HDMI!






  • Jure Repinc@lemmy.mltoAsklemmy@lemmy.mllinux or windows?
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    16 days ago

    GNU/Linux only, with KDE Plasma for desktop as possible. Using it on work laptop (Kubuntu), home laptop (openSUSE Tumbleweed), PC (openSUSE Tumbleweed, also used for gaming), Steam Deck (Arch-based SteamOS). I don’t use spyware/adware so Windows is out of question for me. Also it is not free as in freedom and opensource.


  • Jure Repinc@lemmy.mlOPtoLinux@lemmy.mlLinux 6.11 released
    link
    fedilink
    English
    arrow-up
    4
    ·
    24 days ago

    Anyone else having the problem with the new kernel that graphics in games/benchmarks is quite a lot slower (about 15-20%) then with older kernel (I used 6.10.7 before I upgraded). This is with Powercolor Hellhound AMD Radeon RX 7900 GRE? Even Einstein@Home GPU tasks take about 20% longer now (28 min with previous kernel to about 34 min now).




  • From my experince AMD drivers are pretty close, I’d even say slightly better on GNU/Linux, definitely more stable and consistent. For Nvidia, yeah they are bad at supporting GNU/Linux. Improved a lot through the years but still not there. For Intel, well not exactly an option for gaming, at least not the integrated GPUs I have used so far, but still better than in Windows in a similar way as in AMD case.

    P.S. Another great thing with libre/opensource GNU/Linux drivers: When you report a bug with Mesa3D drivers the bug is quite quickly fixed, especially when you can provide them with backtrace and/or Vulkan/OpenGL API trace. Doing a bisect of source code commits amd identifying the commit that introduced a regression also help a great deal. Good luck doing the same with closed/Windows drivers: you can wait for years and no fix.