tictoc

In Q_Cruncher

Just in case there's any confusion on the ECC that is standard with DDR5. The ECC included in those modules is on-die ECC, which can automatically correct in chip bit flips. It is mostly there to increase stability as process nodes get smaller and bandwidth increases with DDR5. The on-die ECC won't correct in transit errors nor will it report the in chip errors to the platform or the OS. For that there will still be traditional RDIMMs/LRDIMMs. The on-die ECC is more similar in concept to the error correction in NAND SSDs. *Edit* On the topic of the Adata XPG, I had a few DDR3 XPG kits and had no issues with them.

If you are seeing any throttling, then adjusting the offset, in tandem with adjusting the max turbo, might keep it at a higher consistent clock. Can be a bit tedious to dial it in, but might be worth it if you can squeeze out a bit more performance.

No direct experience with it, but the Arctic Liquid Freezer II is supposed to be a very performant clc and is less expensive. I don't think you'll see a huge performance increase over the D15. Maybe a few degrees cooler, but not a night and day difference. Have you tried adjusting your OC and AVX offsets? CPU tasks for F@H are now AVX accelerated, and are quite a bit more stressful than the older CPU WUs.

Progress has been slow to zero over the last few months. I did get the pumps installed, and plumbed up the res, pumps, and radiators last night. Hopefully I'll drop the board in tonight and get the CPU and GPU in the loop for leak testing. The down-sizing from my 42U rack to the 12U rack is mostly complete. Once I have the server done I'll finish up the rack which will be housing the following gear: two 2U UPS, one 1U UPS, one 24 port patch panel, one 12 port patch panel, 24 port 1G switch, 8 port 10G switch, 1.5U router/firewall, and 1U PDU. I'll probably throw up a thread on the router/firewall and the build-out for the rack once this machine is up and running.

The latest BIOS looks to be an identical copy to the beta BIOS that ASRock sent me back in May. I was actually able to save my settings before flashing to the new BIOS, and all of the settings were intact after the BIOS update.

@AllenG ASRock Rack has released an official BIOS with the additional PCIe bifurcation options. I haven't tested it yet, to see how it compares to the beta BIOS I got from ASRock, but I assume it is basically the same. I will actually be moving forward with this build over the next few days, so if anyone is still interested, there will actually be some progress incoming.

Thanks E. I was offline for the last week, and wasn't able to follow up. What we have certainly works, and thanks again for trying a few different options.

I think you already noticed this, but I don't see the button in the editor. --Edit-- I was on my phone for that test. The code snippet button is visible when I'm not on mobile.

It had been in the editor since the restart of the site, and I used it when I made the OP

We did have a button for code blocks with syntax highlighting, and it worked in both light and dark modes. I think the button was next to the justify buttons or maybe next to the emoji button it looked like this: <>

The input for this looks more or less like the current code block, but it doesn't appear to have a background behind the code sections. I took a look at the plugin, and I don't think it's quite what I was asking about. The code blocks that we had before worked well, it was really more of a formatting issue. With inline code only the portion of a sentance or paragraph is highlighted, rather than an entire block. In markdown, words surrounded by a single backtick will be highlighted like the screenshot I posted a above, and triple backticks (or four preceeding spaces depending on the the flavor of markdown) will render a code block like what we had with the code <> flag. Example: https://www.freecodecamp.org/news/how-to-format-code-in-markdown/ It really isn't a big deal, and what we had before definitely worked fine in standard and dark modes. No need to waste your time or dev time on something that really isn't used that often here.

These tasks are now in full F@H. p18112-p18114. Not sure how they run on the RX-580s that everyone is running, but they are pretty brutal on my Radeon VII. -40-50% PPD compared to a p18201.

Is it possible to enable inline code in the editor on this platform? Inline code really cleans up posts that have multiple commands. Here's an example from another site compared to the code blocks in our current editor. Inline Code Example: Using Code Blocks: Here's a quick example. Adjust the paths as necessary for how you have your other instances set up. $ taskset -c 3-7 /usr/bin/boinc --daemon --allow_multiple_clients --gui_rpc_port 31422 --dir ~/boinc2/ That will launch your second instance pinning it to cores 3-7. To check that it worked you can look at htop and also pick one of the pid's from the second instance and check it with taskset. $ taskset -cp yourPID That should return: pid yourPID current affinity list: 3-7

I haven't used it, but since you are on Linux, you could check out this fork of ZenStates which has added support for ppt, edc, and tdc. https://github.com/irusanov/ZenStates-Linux All three of my Ryzen machines are just running static OC's. All of those machines are generally at 90-100% load, so the dynamic boosting and clocks speeds are somewhat pointless. I was able to hit higher clocks at lower temps/volts with static OC's, compared to what the CPU would do on it's own. ¢¢

I'm on 470.74. 470.82 was just released today and hasn't hit the Arch repos yet. Nothing much in the release notes for the driver released today, but NVIDIA is not always great about being thorough on release notes. I'll try the newest driver as soon as it's available, which will probably be later today or tomorrow.

I did remove the beta flag for now on the 980, but since I am fairly active testing beta projects on the beta team, I try to keep at least one GPU running beta tasks. The error is a CUDA kernel error, but it is fairly random and after a restart I can complete the task that had errored out.

980 crashed again. I'm not sure if it's a hardware issue or an issue with the WUs. The crash has only happened on a specific set of beta WUs. Back up and running now. I have reported the error, so we'll see if anyone else has hit the same problem.

I am running F@H on Arch. Right now I have a 980 and a 2080S folding on a headless machine, running a minimal Arch install. The current AUR package has a few quirks to tighten up security, but it does work without issue. SNAPs will never see the light of day on any of my machines, so I've always ran the package from the AUR. I've had at least one machine folding on Arch for at least the last five years. I actually put together a little guide for one of my teammates on how to setup a minimal headless Arch install for folding. You can find that guide in a bit of an odd location: https://forums.extremehw.net/topic/1574-unable-to-add-attachment-to-pm-or-post-and-kicked-out-of-editor/?do=findComment&comment=18925

My 980 crashed at some point in time over the weekend. I didn't even realize it was down, since it's in the same machine as the 2080S, which just kept on folding. I backed the clocks down a bit, and it's back up and running now.

Evil Linux h4x0|2 Thanks for looking into it E, and archiving similar files is an easy workaround.

Here is a screenshot of the error when attaching the file.

I have been tempted to upgrade. I have a machine running one of the first batch Ryzen 7 1700s with the segfault bug. I never RMA'd, so from time to time I hit the bug. That machine mostly sits on my test bench. The bug doesn't come up too often, but every time it crashes, I have to determine if it's a real crash or the faulty CPU. Too bad I also need a new motherboard to run a 5800x, which is $370 at Microcenter right now.

Sorry I forgot to report back. I did try it again, but the result was more or less the same. I will give it another test in this post. *Test 1 with Firefox* With the text pasted into a code block in a spoiler, I was sent to a captcha page, completed the captcha, and then it just kicked me back without submitting the reply. All of the content was still in the editor. *Test 2 with Firefox* Attaching the .txt file to this post resulted in the same -200 error *Test 3 with Chromium* Attaching the file failed with the -200 error. Pasting the text into a code block did work after completing a captcha.

In Q_Cruncher