• 0 Posts
  • 22 Comments
Joined 1 year ago
cake
Cake day: July 17th, 2023

help-circle


  • The only thing I can think of is to try the drives in a different system and see how they behave (same OS and configuration).

    If they behave the same then that rules out everything except the drives themselves and the OS.

    Considering how you mentioned the behavior is better in Windows, it sounds like a software issue, but you never know until you try.


  • FWIW I’ve also had memory issues with XMP.

    Turns out that ASUS firmware is omega pepega and decided to go against AMD’s specifications even for XMP profiles.

    CLDO VDDP was stuck at the same voltage as SOC. Per AMD it has to be up to VSOC - 0.1V

    So, after manually setting that, and other VDDP and VDDG voltages, it magically started working perfectly.

    So do check voltages anyway even if you found a bad stick. Mine endured through the crappy firmware thanks to it being Samsung B-die.

    Also check this for more info in general (I recommend this even if you won’t OC, just the memtest alone is a huge section)

    https://github.com/integralfx/MemTestHelper/blob/oc-guide/DDR4 OC Guide.md

    I tested with OCCT to find even more errors, so either do that in a mini windows environment or do one of the Linux tests to check memory some more. Memtest86+ isn’t enough.









  • It needs to be accurate and fast, indeed. The code being old isn’t a problem unto itself, but rather the side effects of it.

    It is fine for all intents and purposes today. But, there is some inherent difficulty associated with decisions brought years ago when some of the code was originally written, making portability quite a challenge.

    I wasn’t making a comment on its age, mind you. I don’t necessarily think it’s that big of a problem and probably can be fixed easily. If anything, it has gotten way better thanks to the departure from the plugin system and various other optimizations over the years.


  • Well, stenzek is the developer of DuckStation and the person behind the new Qt UI and many new fixes on the backend of PCSX2.

    But, I will agree that we do need a new emulator. The emulator called “Play!” is a really good candidate and looks promising. Seeing how it runs on ARM beautifully, I can’t wait to see how far it goes.

    PCSX2 runs fine for most people today, but the foundation is a bit too old for its own good. This is why you don’t see too many ports of PCSX2 to other plaforms. They have improved massively by ditching the entire plugin system a few years ago, but that alone isn’t enough to make it more portable and easy to run.







  • That’s ok if you look at it that way. But at the end of the day, it’s just a tool like any other. Personally I find it really silly to put any moral questions into it because I don’t believe it’s worth my time to think about it, lose time on silly things and/or sacrifice the quality of my work. I’m not trying to imply anything about Linux, btw, it’s the same for the other ways around. It just feels stupid because it ends up like a political discussion, when it really shouldn’t be. You have the option to use basically anything and choosing to limit yourself over that is just plain stupid imo. You could make the arguments for how they process data, which is a whole other discussion, but then again, there are plenty of workarounds to all of those problems (which is exactly what some people are doing with virtualization, different machines entirely, OS tweaks, etc., which is fine, because they’re benefiting from it). Nothing against FOSS or otherwise, btw, I do agree about the need to support, but there are so many other ways to do it. Just using it isn’t enough, sadly. As the point of this OP is - it’s also market adoption, marketing itself, etc. None of this changes the fact that using certain tool(s) (e.g. gdb) is best done on a certain OS (e.g. a Linux distro) at a given time.