[–] 6 points 1 year ago (3 children)

What was your mount command? You might have to do something like mount -t ntfs3 /dev/sda1 /whereveryouwannamountthething or edit your fstab entry, something like /dev/sda1 /whereveryouwannamountthething ntfs3 defaults 0 0

Here's the Arch wiki page for NTFS, the Arch wiki is usually where I'd start for fixing stuff, their documentation is fantastic.

  • source
  • [–] 2 points 1 year ago*

    I have a 60hz and 144hz monitors on my desk, and I've found that sometimes the frame rate only changes for the monitor where the settings window was opened from.

    If you right click on the desired monitor's desktop and change screen settings/refresh rate from there, it'll actually work, usually.

  • source
  • [–] 2 points 1 year ago (1 child)

    i just prefer nightly as it has a faster release schedule but it also can more more unstable (nothing breaking though at least not in a while). you'll typically update every night. plus i love the icon more :)

    nightly is about 2 versions ahead - 143 vs 141

  • source
  • parent
  • context
  • [–] 4 points 1 year ago (1 child)

    I don’t use Mint so I can’t talk too much about the software choices. Transmission is a simpler more user friendly torrent client. It used to be the go-to client on Mac, maybe it still is. I find it a bit too simple so I use qBitTorrent as well.

    You’ve moved to a completely new ecosystem. There’s lots of software out there and most of it’s free so give it all a go. I know in Windows when you install something and then remove it they always seem to leave traces around. Linux is much better at cleaning up so there’s no real reason not to install something you want to try.

  • source
  • [–] 4 points 1 year ago (3 children)

    i typically uninstall firefox for firefox nightly, thunderbird for thunderbird beta, and then use qbittorrent instead of transmission personally but it's all just preference. there's nothing wrong with celluloid either; it's a nice little player. i just like vlc more because i'm used to it.

  • source
  • [–] 4 points 1 year ago (1 child)

    You are on Mint, so it is more of a Long Term Support LTS distro. The thing to understand is why LTS actually exists in the first place. The underlying reason for LTS kernels is so that anyone can create a server that is connected to the internet and uses simple high level scripts to connect software and do useful stuff. Many types of software are constantly in a state of flux that break backwards compatibility. Actively developed software in the open source world often stays up to date with the latest packages. Other distros like Fedora or Arch stay up to date in the latest software. If you write a script on a server that runs one of these distros it will likely require regular maintenance. If you write the same script on a LTS kernel distro, your script is likely to work the same for years without any need for intervention. In this LTS arrangement, kernel maintainers are committed to back porting any security patches required for the packages they include in the distro. Some of these packages may already have their own independent commitment to never breaking backwards compatibility. These will still get updated regularly in a LTS distro.

    So the choices the Mint packagers are making are centered around LTS like stability. Many of the packages may be outdated especially in the glue and obscure edge case software in the native software repository. You may need to manually add sources to get newer versions in the package manager.

    This fundamental understanding of what a LTS kernel means is key to understanding Mint overall, and by extension the reason most distros exist; they all have a niche purpose.

  • source
  • [–] 7 points 1 year ago (1 child)

    The good thing about Linux is: preinstalled literally just means preinstalled. Not preferred, not prerequisite, and perfectly uninstallable.

    But that's all I have to say. You can test each and see if you like them, or look up what people think of each individualy. If you don't like one, just uninstall it, and install your preferred alternative.

  • source
  • [–] 11 points 1 year ago (1 child)

    Generally good. If you wanna hit the ground running, they're good choices.

    If you decide you don't like them, they can be uninstalled too.

    Personally I prefer qbittorrent and VLC, and have installed them, but I've used all 4 and the mint defaults seem perfectly functional.

  • source
  • [–] 1 point 1 year ago*

    I don't think it would either to be honest, but it's a good way to determine if a form of visual corruption is caused by the display abstraction layer, or the gfx umd (or something else entirely, like the OS). I use the same technique at work 😅

  • source
  • parent
  • context
  • [–] [S] 1 point 1 year ago (3 children)

    It's very quick and unpredictable. I have not noticed it across both screens at the same time, but can't rule that out. They're pretty thin lines and usually only one at a time, like a scan line on a TV. It just started becoming more noticeable recently so I'll try to keep track of when it happens.

  • source
  • parent
  • context
  • [–] 1 point 1 year ago (4 children)

    to be honest, I feel as if I may have jumped the gun somewhat by suggesting this could be display underflow. I gather how tricky this could be but if you could somehow capture some footage of this in progress, I'd be curious to see it.

    Does this white line show up across both displays in tandem?

  • source
  • parent
  • context
  • [–] [S] 1 point 1 year ago (5 children)

    Thank you for the detailed answer, this is very informative. I should read up some more on the underflow issue. This is the first time I've heard that term. I'm familiar with buffer underflows, but this sounds a little more complex.

    You are right, it did start happening just recently (within the last couple of weeks maybe). I forgot to mention that I am running this through a 4-port KVM. I didn't think it relevant before because I'm not seeing any issues when using another port (my work PC), but I can't rule it out.

    It has been some time since I played with it, but I think the reason I went out-of-repo at the time was to get recent enough versions of amdgpu and rocm to run ollama. I was following some online guide and had no idea what I was doing so I probably messed something up.

    It sounds like it should be safe to uninstall the out-of-repo amdgpu and rocm packages. I am not doing any local AI right now so I can probably leave it out. I do use the PC for gaming, but from what I've been reading it sounds like the standard drivers are good enough for that now.

    Thank you everyone for your help. I didn't expect anyone to actually reply and you guys have been awesome! I am going to swap the cables first of all since that's an easy thing to try and see if anything changes.

  • source
  • parent
  • context
  • [–] 2 points 1 year ago* (6 children)

    Perhaps i fudged the dnf command example, it doesn't appear to be possible to list the gfx kernel driver version via dnf. The entity we see is the external package installed for ROCm support. On that note, it's worth mentioning that Fedora directly packages ROCm, and I'd recommend uninstalling the downloaded driver and switching over unless you have a specific reason to use the out-of-repo package.

    As for underflow, a colleague of mine had provided a nice little run-down: The display buffer holds image you want to send to the display, is like part of GPU memory. When you send via DisplayPort, HDMI etc., you add some sync signals to indicate properties like the start of a frame, start of line, and extra data. If at any point this exchange gets messed up (like memory is unreadable, or you send data when it's not ready), you get garbage on-screen.

    One way underflow can happen from the context of DAL (display abstraction layer) is during a DPM (dynamic power management) change. This change takes a relatively long time, and on rare occasions, lead to underflow.

    Alternatively, sometimes display hardware can't change refresh rate (for example) as fast as we ask it to, and you may end up with underflow from that. I suppose we could try other cables but the impression I get is that this just started happening at some point?

    if this behaviour is very recent, it could be from the distro provided amdgpu kernel driver, though I'm not sure if there could be any conflict by having the external package installed. Like I've mentioned above, it could be worth removing that set of packages installing the Fedora ROCm metapackage instead (sudo dnf install rocm).

  • source
  • parent
  • context
  • [–] [S] 2 points 1 year ago (7 children)

    Thank you for responding! I'm not sure how to find the versions, but here goes:

    glxinfo reports:

    Extended renderer info (GLX_MESA_query_renderer):
        Vendor: AMD (0x1002)
        Device: Radeon RX 7900 XTX (radeonsi, navi31, LLVM 20.1.6, DRM 3.63, 6.15.9-201.fc42.x86_64) (0x744c)
        Version: 25.1.4
        Accelerated: yes
        Video memory: 24576MB
    
    OpenGL renderer string: Radeon RX 7900 XTX (radeonsi, navi31, LLVM 20.1.6, DRM 3.63, 6.15.9-201.fc42.x86_64)
    
    

    AMDgpu package:

    $ dnf info amdgpu
    Updating and loading repositories:
    Repositories loaded.
    Available packages
    Name           : amdgpu
    Epoch          : 1
    Version        : 6.2.60203
    Release        : 2044426.el9
    

    The exact kernel version is 6.15.9-201

    I am slo seeing some amdgpu related stuff in dmesg:

    amdgpu 0000:03:00.0: [drm] Registered 4 planes with drm panic
    amdgpu 0000:03:00.0: [drm] REG_WAIT timeout 1us * 100 tries - dcn32_program_compbuf_size line:138
    

    What could cause an underflow? I have two displays running: Primary is 3840x2160@60 (150% scale, HDR mode), Secondary is 2560x1440@60. Could cables be an issue?

  • source
  • parent
  • context
  • view more: ‹ prev next ›