• simple@lemm.eeEnglish
    0·
    7 months ago

    Dropping the old NTFS driver.

    Good stuff. Hasn’t there always been confusion on mounting your NTFS drive using the old driver vs the new?

    • d3Xt3r@lemmy.nzM
      0·
      7 months ago

      Indeed. But I think some confusion will still remain as long as the ntfs-3g FUSE driver is still included by distros. Because right now, you have to explicitly specify the filesystem type as ntfs3 if you want to use the new in-kernel driver, otherwise it would use ntfs-3g. And most guides on the web still haven’t been updated to use ntfs3 in the fstab, so I’m afraid this confusion will continue to persist for some time.

      • SteveTech@programming.devEnglish
        0·
        7 months ago

        I’ve had bad experiences with ntfs3 anyway, so it’s probably for the best that ntfs-3g is the default. Also last I checked ntfs3 had effectively been orphaned by paragon (the developers), is that still the case?

        • d3Xt3r@lemmy.nzM
          0·
          7 months ago

          ntfs3 has had several improvements in 6.2 and 6.8, and it’s been pretty stable for me of late. I use it to share/backup my Steam game library mainly + for my portable drives for general data storage/local backups, and haven’t had any issues.

          It’s not orphaned. There was a bit of lull after it was introduced in kernel 5.15, and yes it was a bit unstable in the 5.x series, but it’s been pretty good since 6.2 where they finally introduced the nocase and windows_names mount options. The performance improvements are worth it if you use NTFS heavily, so I would personally recommend switching.

          • Sina@beehaw.org
            0·
            7 months ago

            I would have loved to take that performance before I converted my data drives to ext4, however it’s just inherently not stable.

            Sometimes If you have a power loss you have to run checkdisk on Windows to get out of ro mode, no?

            • d3Xt3r@lemmy.nzM
              0·
              7 months ago

              There’s no need to run chkdsk from Windows, you can run ntfsfix directly from Linux:

              sudo ntfsfix /dev/path --clear-dirty
          • taaz@biglemmowski.winEnglish
            0·
            7 months ago

            For me, Steam (on Linux) has been periodically corrupting the ntfs disk, I do use it on windows too and not even win hybrid/fastboot/hibernation disabled helps.

            May I see what mount options you use for the ntfs3 driver in fstab? I do not currently have the nocase and windows_names …

            • d3Xt3r@lemmy.nzM
              0·
              7 months ago

              Mine looks like this:

              UUID=blah /media/games ntfs3 uid=1000,gid=1000,umask=000,rw,user,exec,nofail,nocase,windows_names 0 0

              If you’re copy-pasting this, make sure your uid and gid matches of course.

              But the key thing for Steam is you need to have your compatdata folder on a Linux partition, because Proton creates folders with invalid characters (like :). windows_names would prevent that of course, and thus prevents corruption, but it would cause Proton to fail since if can’t create those folders/files. So you’ll need to symlink that folder on your NTFS disk to point to a folder on a Linux partition.

              Eg:

              $ mkdir -p ~/.steam/steam/steamapps/compatdata
$ ln -s ~/.steam/steam/steamapps/compatdata /media/games/Steam/steamapps/

              Of course, before you run the above, you’ll need to delete the existing compatdata folder from the NTFS disk.

      • GloriousGouda@lemmy.myserv.one
        0·
        7 months ago

        You know I didn’t realize until now there was actually “confusion”. I just thought I was a dolt for forgetting the package name or confusing the command name. Heh!

  • Karna@lemmy.ml
    0·
    7 months ago

    Used Mainline to install it on Ubuntu 23.10. Together with Nvidia driver v550, it is working without an issue for me.

  • d3Xt3r@lemmy.nzM
    0·
    7 months ago

    Here’s the TL;DR from Phoronix:

    #AMD

    • AMD P-State Preferred Core handling for modern Ryzen systems. This is for leveraging ACPI CPPC data between CPU cores for improving task placement on AMD Ryzen systems for cores that can achieve higher frequencies and also helping in hybrid selection between say Zen 4 and Zen 4C cores. This AMD Preferred Core support has been in development since last year.

    • Performance gains on AMD 4th Gen EPYC

    • AMD FRU Memory Poison Manager merged along with other work as part of better supporting the AMD MI300 series.

    • AMD has continued upstreaming more RDNA3+ refresh and RDNA4 graphics hardware support into the AMDGPU driver.

    #Intel

    • Intel Xeon Max gains in some AI workloads

    • Intel FRED was merged for Flexible Return and Event Delivery with future Intel CPUs to overhaul CPU ring transitions.

    • Reworked x86 topology code for better handling Intel Core hybrid CPUs.

    • Intel Fastboot support is now enabled across all supported graphics generations.

    • Intel Core Ultra “Meteor Lake” tuning that can yield nice performance improvements for those using new Intel laptops.

    • Continued work on the experimental Intel Xe DRM kernel graphics driver that Intel is aiming to get ready in time for Xe2 / Lunar Lake.

    Video, Filesystem & Network

    • Support for larger frame-buffer console fonts with modern 4K+ displays.

    • Dropping the old NTFS driver.

    • Improved case-insensitive file/folder handling.

    • Performance optimizations for Btrfs.

    • More efficient discard and improved journal pipelining for Bcachefs.

    • FUSE passthrough mode finally made it to the mainline kernel.

    • More online repair improvements for XFS.

    • Much faster exFAT performance when engaging the “dirsync” mount option.

    • Many networking improvements.

    Full summary here: https://www.phoronix.com/review/linux-69-features/

          • fuckwit_mcbumcrumble@lemmy.dbzer0.comEnglish
            0·
            7 months ago

            Same boat. Good news is 11th gen generally gets better battery life than 12th+ because all those extra cores still eat power.

            Bad news is I already get as bad as 30 minutes of battery life so IDK how 12th gen can be even worse.

              • fuckwit_mcbumcrumble@lemmy.dbzer0.comEnglish
                0·
                7 months ago

                Yeah but this is Intel, they’re not capable of doing something the most efficient way possible. E cores use less power than P cores, but that doesn’t mean they’re very good at getting the job done using the least amount of power. Currently (using Intel’s management) 12th and 13th gen start a task on the P cores, and if it runs for longer than X time it gets shifted over to the E cores where it can churn away. Meteor lake has 3 stages of things since there’s P cores, E cores, and LP E cores. If I remember right Meteor lake starts a task on the LP E cores, then shifts it to P cores, then shifts it to the E cores if it’s taking too long. But Intel likes to blast the power away with turbo boost and runs the E cores way past their actual efficient zone unless you wrangle them back down. Sometimes it’s faster to blast the task away on the P cores then return to idle, other times letting it churn away on the E cores forever is the best way.

                Also all those extra cores being active still uses power. So if you went from a 4 core CPU to a 4 + 4 cpu now you have all the same power draw as the old one, plus the extra 4 efficient cores sipping at even more power. I think that’s where 12th gen really suffers the most.

              • iopq@lemmy.world
                0·
                7 months ago

                Spoilers: they are efficient in space, not really power

                So for multicore workloads they are actually power efficient because you get more throughput (more performance iso power)

                But for idle that has no benefit

              • TheGrandNagus@lemmy.worldEnglish
                0·
                7 months ago

                They’re not really made for power efficiency, but rather space efficiency. ~4 E-cores fit into the size of a P-core.

                They’re there to boost multi-core performance without having a huge die-size or increasing latency in the P-cores when doing lightly threaded tasks, essentially.