tictoc

I don't think so, it looks like 1.7.3 released 5/14/20 is the latest.

Not sure if anyone is still using this or following this thread, but the "New Version?" button is a broken link. @ENTERPRISE maybe we could redirect the broken link to here. Broken link address: https://extremehw.net/forum/amd/general/6090-dram-calculator-for-ryzen™-news-and-discussions?p=6232#post6232

Right on. I'm still not positive what I'll be folding on. My schedule is pretty busy at the moment, but I'll have some time in the next few weeks to finalize what I'll be folding on.

I took a day off from folding on the Radeon VII, while I sorted a few things out on my workstation. It's back up and running now. I rolled back to the old closed-source amdgpu-pro driver to do some testing on some non-F@H work, and much to my surprise, the current WU that I'm running (beta WU 18201) is seeing a massive performance improvement running on the old driver. amd-staging-drm-next kernel + ROCm 4.2 = 2M ppd 5.12.9 kernel + OpenCl from amdgpu-pro 20.30_1109583-1 = 3.1M ppd

You could put a USB 3.0 card in the PCIe 2.0 x4 slot, and use that to drive your front monitors. https://vantecusa.com/products_detail.php?p_id=125&p_name=

I would be fine with using the All OS average, and then doing a week long test, just to make sure that everything is in line. The only real issue is that if there aren't any recent results then the average on LARS is probably going to include a bunch of pre-CUDA tasks. On average the old OpenCL NVIDIA tasks were at least 25-30% less PPD, compared to the current CUDA tasks. I'm not 100% sure on the above, since I have no idea how long the LARS database has been up and running.

I have not had time to do much testing. Although it looks like I should run some low spec hardware for max points. I have a high clocking AMD 5770, that would probably give me twice the adjusted points compared to any of my other GPUs. In the little testing that I've done it looks like my 980 classy, that won a few times in the old TC, would also put out fairly decent points. In order to really figure it out I need to free up my test bench. Hopefully that will happen in the next couple of days. I have the chassis for my server stripped down, and I should be able to get that board off the test bench this week.

The ASRock Rack board has a BMC with onboard VGA, so no issues there unless the primary video is set from auto or onboard to PCIe in the BIOS. My Taichi board, on the release BIOS, would hang on post with no GPU installed. I'm not sure if I ever tried it on a more recent BIOS. There is really no technical reason for failing to post without a GPU, except for shoddy UEFI programming.

No issues on the ASRock boards that I have. The three boards will happily run headless, as long as there is a GPU in the primary slot.

No 960. The only Maxwell I have is a 980.

Not sure if it's just my browsers, but the "Unmultiplied points" tooltip is showing up far from the cursor. Runnning latest Firefox and Chromium in Linux. Firefox: Chromium:

Back up and running with a Radeon VII. I'll be testing out some other GPUs this week, so I might be changing my TC card for June.

@Avacado You could mine other coins on the M40, but not ETH at the current DAG (4GB). Maxwell only has 1GB of addressable TLB, and that is why you see low hash rates.

No idea if this will work, but you could just try the Quadro drivers without a BIOS flash, and then turn off TCC with nvidia-smi. Open a shell (CMD or Powershell) as an administrator List GPU devices to get the GPU_ID of the device with the Quadro drivers: nvidia-smi -L Turn off TCC: nvidia-smi -g GPU_ID -dm 0 **GPU_ID will be the number of the device from the previous command** Reboot

Interesting. I don't know what would be in the Tesla driver that would restrict mining. One thing that might be holding it up is the ECC on the memory. The M40 isn't really a proper Tesla, and it only has ECC on the memory not the cache or registers, so that extra trip to the memory shouldn't nerf mining that hard. The memory clocks are quite a bit lower, but you could edit those in the BIOS. To run the Titan X BIOS you would need to Hex edit the device ID, and I'm not sure how the Titan firmware would handle the ECC. ? *Edit* You could try a Quadro M6000 BIOS. That card is effectively the same as the M40, but with display outputs. No verified M6000 12GB BIOS on TPU, but there is a PNY from the community: https://www.techpowerup.com/vgabios/173217/173217

I don't see the point in flashing the Titan X BIOS. You have full control over power and clocks, so a Titan X BIOS isn't really going to give you anything, unless I'm missing something...

Excellent. Nice to see that card stretching its legs. Looks like you have a bit of headroom on both temps and power.

Small update on the bifurcation options. The implementation in the BETA BIOS that I am running seems to be 100% complete. The slots that are electrically x16 all work in x4x4x4x4 mode, and the x4x4x8 splits also work correctly. This is a huge improvement especially on this platform. The 2970WX and the 2990WX CPUs have four NUMA nodes, with two NUMA nodes having direct access to memory and certain PCIe slots. With proper bifurcation on all the slots, there is much more flexibility when running VMs. It is now much easier to pin high performance VMs to the proper NUMA node, without having to swap devices from slot to slot. The only real limitation now is due to the fact that slots 3 and 5 are only x8 electrically. At the end of the day it probably doesn't really matter. With all the bifurcation options working, the use case where this might matter is going to be a niche, of a niche, of a niche, use case, and there are reasonably priced EPYC options available.

You need to use an older version of nvflash (v5.287) with the cert check bypassed: https://www.techpowerup.com/download/bios-modding/

The wee little units are actually pretty great on less powerful GPUs. I've had a 980 up doing some testing and those 15 second TPF units (don't remember the project # p13447) are like 1.2M ppd on the 980.

Yes, you should be able to tweak the BIOS with Maxwell BIOS Tweaker. No need to do the modern day silliness of cross-flashing BIOS, since these cards are from a time when NVIDIA actually let their customers do whatever they wanted to do with their property. First I would try raising the power limit with nvidia-smi, and also see what application clocks are available. I only played around with Keplar era Teslas, but the Maxwell cards can have their BIOS tweaked.

I'm guessing you didn't mess with the terminals on the heatkiller blocks, but if you did, that's another possible leak location. It's easy to pinch the o-rings on those terminals if the o-rings aren't fully seated in the slot. Hope you get it sorted out, and I'm excited to see that machine up and running.

Right now it is nowhere. Although, there is one user on one project that made an EHW team.

Did you hit all the fittings with a spray bottle and soapy water while you had it under air pressure? That's the quickest way (but can be a bit messy) to find the leak outside of filling up the loop. I don't ever leak test any of my systems on air. I usually just run the pump on a separate power supply, or jump the 24 pin with only the pump plugged in, spread some paper towels around possible drip locations, and run the loop with distilled.

In Q_Cruncher You can exclude me from the prize drawing.