• Jhex@lemmy.world
    link
    fedilink
    arrow-up
    5
    arrow-down
    2
    ·
    1 day ago

    I always loved the “it’s not polished” excuse withoutb a single example

    • massive_bereavement@fedia.io
      link
      fedilink
      arrow-up
      13
      arrow-down
      1
      ·
      1 day ago

      Let me check dmesg:

      amdgpu 0000:03:00.0: amdgpu: failed to write reg 291c wait reg 292e

      or

      [46531.357889] amdgpu 0000:c5:00.0: [drm] ERROR lttpr_caps phy_repeater_cnt is 0xff, forcing it to 0x80.

      Let me know if more examples are needed ;)

      • N0x0n@lemmy.ml
        link
        fedilink
        arrow-up
        7
        arrow-down
        1
        ·
        1 day ago

        It’s not because you can’t check on Windows, that it doesn’t exist ! I’m sure there are a lot of different boot issue logs in Windows, they are just hidden behind a “beautiful” Welcome page.

        • wizardbeard@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          6
          arrow-down
          2
          ·
          edit-2
          1 day ago

          You’re making a huge assumption based only on the fact that Windows hides these logs from the end user.

          I’ve had line of sight to those logs through a system that automatically highlights those errors and warnings for something like eight years now, for a fleet of over 1000 Windows machines at the start which is now roughly 5000 total.

          In that time I’ve seen less than 200 graphics driver issues logged, and they all were on machines with failing hardware.

          Yes, they are not anywhere as visible to the end user as they are on Linux, but they are also significantly less common (graphics issues in particular).


          Also, if the warnings are meaningless, why display them to the end user? It’s just more noise that actual problems can sneak by in.

          • Russ@bitforged.space
            link
            fedilink
            English
            arrow-up
            2
            ·
            20 hours ago

            Also, if the warnings are meaningless, why display them to the end user?

            I mean to be fair, the Windows Event Viewer has zero shortage of warnings that are meaningless to the everyday user as well.

            I’ve always seen the event viewer and dmesg to be two sides of the same coin - both of them serve the same (or close enough of an equivalent) purpose to my knowledge, and both are very verbose.

        • Samskara@sh.itjust.works
          link
          fedilink
          arrow-up
          6
          ·
          1 day ago

          Looks like it’s still rough around the edges.

          https://wiki.archlinux.org/title/HDR_monitor_support

          KDE Plasma 6.0 introduced experimental HDR support for Wayland session.

          DRM clients can directly pass HDR metadata, but this is not available from regular userspace clients, only specialized software can use it.

          Web browsers: No web browsers support HDR on Linux at this time.

          Valve’s Steam compositor gamescope offers experimental HDR support.