tictoc

It might be the client. I had issues with the latest one, and didn't take the time to sort it out. Maybe try rolling back to an older version of the F@H client.

Sorry for the somewhat OT double post. @Diffident I'm not a fan of the way that the latest F@H client is packaged in the AUR, and I think it might actually cause some issues when running F@H on ROCm. I didn't have time to fully test it, so I've just continued to use the older client. The new client in the AUR broke some scripts that I have for F@H along with some other things that I don't really like about how it's installed. I'm currently running the 7.5.1 client. If you want to give that a go, here's my PKGBUILD along with the post-install and SystemD service. foldingathome.zip

Not sure what the special sauce is for F@H on ROCm. Previously I had no issues running the closed source bits of the pro driver, but now the performance for F@H has really tanked. Just took a quick look at the rocm-opencl-runtime Gentoo package, and as far as I can tell, all of the necessary libs, compilers, and applications should be getting built. I build a bit more of the ROCm stack, but that is all for HIP, profiling, and debugging. FWIW I've only tested and ran F@H+ROCm_4.0 on kernels 5.10.7 and 5.10.8.

ROCm is AMD's open source compute stack of software. https://www.amd.com/en/graphics/servers-solutions-rocm OpenCL is still very hit and miss on the open source stack. I am actually testing some HIP code that was ported from CUDA and it is working surprisingly well. For F@H the ROCm opencl-runtime is definitely the way to go, at least on anything Vega. Here's a quick little comparison of some WUs running on the AMD closed source OpenCL driver and on the ROCm 4.0 OpenCL driver. Radeon VII amdgpu-pro-20.30_1109583 Slot 01 p14914 - tpf=3:17 Slot 00 p14911 - tpf=3:10 Slot 02 p14912 - tpf=5:31 Slot 03 p13442 - tpf=11:46 ROCm 4.0 Slot 01 p14914 - tpf=1:14 Slot 00 p14911 - tpf=1:17 Slot 02 p14912 - tpf=1:16 Slot 03 p13442 - tpf=1:42 The p1491x WUs are pretty brutal on AMD GPUs, only about 800-900k ppd on a Radeon VII. That is at least tolerable compared to the 250k ppd on the amdgpu-pro driver. Some other WUs are actually pretty decent, like the p17321, which is around 2.9M ppd.

I'll probably have to upgrade my bulk media storage sooner rather than later. I grabbed a few remastered Blu-ray box sets, and that is going to eat up a few TBs of storage. On a side note the X-Files Blu-rays look really good. Especially since Season 1 and 2 I had originally ripped from VHS.

Have a few GPUs folding for EHW while testing the latest ROCm. I'll keeping them going through the comp.

This build is still alive, but it's stuck on my test bench for now while I work out the software stack and make some final decisions on hardware. New RAM has been dead stable for 3 weeks running at 2933 CL19. Still not sure which way to go on the GPUs in the server. I had plans to swap some hardware around, but the lack of GPU availability has kind of slowed progress.

Would be nuts if you could unlock the disabled CCD. I'll jump on the train if it can actually happen. My 960T clocked better than my 1055T or my 1090T.

More speed is always a good thing, but for everyday user systems the benefits are pretty much nonexistent. PCIe 4.0 SSDs have been pretty underwhelming for really any workload. Hopefully the updated controllers will change that for the next round of SSD launches.

Had a bit an accident late last winter with my single burner lantern, so I gave my self an early Xmas present. NEMO Sonic 0

I could have saved my self hours of testing, if I would have just replaced the garbage stick sooner. Swapped out the bad stick for one of the new sticks, loaded a 2866 CL16 profile that I had saved, and I am 30 minutes into a stressapptest run with zero errors. With the old stick in I would start to see errors within 20 seconds of starting a stress test.

Have you tried playing on your 5650X with the 1.05 patch?

Two new sticks are set to be delivered on Wednesday, so hopefully I can get it sorted out with the new sticks. One of the other sticks also showed a single error, but I'm pretty sure that only showed up when trying to get 128GB to run at 3200. I already have mis-matched sticks, so more than likely even if the replacement is good, I will be maxed out at 2866-2933. Four of the sticks (including the bad one) have some funky Micron Rev H? chips, that I'm pretty sure are some sort of ES ICs. This late in the life cycle of DDR4 you start to see some funny stuff getting put on modules. Especially, with something like ECC UDIMMs which are not really made in real quantity.

I've ran it all the way up and down from 1.25v to 1.6v while testing. That stick just doesn't want to run stable at anything over 2666, even at CL22.

One less than stellar stick of RAM. That stick won't really run at anything over 2666. Rolled the dice on a new pair of sticks, and we'll see what ICs I get.

1.2 sounds about right to me. It's been a bit since I folded on a 5700XT, but that should be close to the average when you account for the low ppd WUs.

Since the chipset on X570 is PCIe-4.0 it does get pretty warm. The chipset is always the hottest thing on my TRX40 board. I let it sit at around 65°C, because that little fan starts to get a bit whiny over 4500 RPM.

Pretty nuts that I am playing the most anticipated game of the year on Linux on launch day. There are a number of gotchas to play it on Linux, but in the short time that I've been playing, I've had zero issues. Playing on a Radeon VII running at 2075/1150, 3440x1440, high preset with motion blur off. I didn't really mess with the settings too much, since I really just wanted to see if the game was actually playable. At high settings FPS was hovering in the 35-45 range, so the setting could use some tuning. Even at the lower frame rate the game was still smooth, and I didn't encounter any bugs. Since this is a screenshot thread, here's the first one for your thread.

Just a little update. It looks like this is going to turn into a very overkill server. Thinking about swapping out a few things on my workstation, so I might be adding a pair of Radeon VIIs to this machine. For now just testing with a pair of Vega 64s.

I imagine you already got a new phone, but if not, here's another vote for a Pixel. I just picked up a Pixel 4a for $350 US. I have zero interest in the Google ecosystem, but it's the closest to pure android and super easy to run an alternate OS on. The camera is excellent, and overall I would say this is my favorite phone since I retired my Lumia 1020. Even though I have fairly large hands, giant phones drive me nuts. It's nice to have a compact device again, even if we'll never see a proper aspect ratio on a phone again. 15:9 ftw

Yep, 5x 360mm rads.

Forgot about this thread. Here's an update on my main machine. Maxed out the case back in June. I had to clearance the floor a bit to get the last GPU in.

10Gb networking makes pretty quick work of transferring data around. I'll probably spin up a temporary 6-8TB SSD RAID-0 to pull the data off the server, add the old drives to the new storage pool, and then it's just a local rsync to put the data in the new storage pool. Since I purged a bunch of stuff off my current file server to cold archives, I should be able to get everything moved in 2 batches.

Looks like it is actually an issue with some things I have disabled in Firefox. Last test was using Safe Mode, but that only disables add-ons, and doesn't reset any about:config changes. I just wiped my profile, and image upload works fine. Thanks for testing. ?

Looks like maybe just a Linux issue. I'll reload a fresh empty profile and test. *Edit* No change with a bone stock empty Firefox profile.