tictoc

I have been back-and-forth with ASRock, testing a number of beta BIOS. The same issue still exists with x8x8 working, but x4x4x4x4 just acts like x16. It is going up the chain to a BIOS engineer, so it seems as if there might be some progress in the near future on the bifurcation issues.

You could go browns with dampers. That is pretty quiet and what I use at work. If you're not bottoming out the keys, it is not too loud.

The handicapping is what makes it interesting. I have been crushed at work, so no time to start fiddling around with different GPUs. Hopefully things slow down and I can start testing some other GPUs next week.

RDNA2 GPUs have Vulkan Ray Tracing via the latest AMDGPU-Pro driver. 6900XT Metro Exodus - https://www.youtube.com/watch?v=B4r183JwhL0 NVIDIA has been releasing Vulkan Ray tracing enabled drivers since December.

NVIDIA has gotten much better over the last few years of disclosing vulnerabilities. Prior to that, I'm sure there were just as many issues, but they were probably just quietly fixed with new drivers. Link to NVIDIA's Security Bulletin Page: https://www.nvidia.com/en-us/security/ Link to the old archives: https://www.nvidia.com/en-us/security/archive/

If I had an ASRock x370 instead of an ASUS x370, I's go this route for sure. I have one of the bugged 1700s, that I never RMA'd. It works fine for most tasks, but it will crash with heavy compiling.

Even in a test/demo I do not like losing. ? I might have to actually OC the Radeon VII that I'm running for TC.

The board does have some limits on the number of addressable peripherals. On the previous BIOS I tested with all the PCIe slots populated and PCIE 2 split into two slots with a passive splitter. In order for all the devices to be recognized I had to disable onboard audio and the USB 3 header. I've ran into this issue on other platforms, and depending on what all you need there can be some work-arounds with some things disabled. Your testing seems pretty thorough, but I'll give it a go with an ASRock Ultra Quad M.2 card. Choice of colors is pretty standard for a server motherboard. I don't think I've ever seen an ASRock Rack board that is anything other than green with white, blue, or black RAM and PCIe slots.

The -2M should probably be given, but for now I'm prepared to let him be happy at the top of the leaderboard as a reward for getting things fired up. All jokes aside, I don't see any issues, and thanks for taking the time to help.

Flashed to a beta bios with additional PCIe bifurcation options. I've yet to test the additional options other than double checking the link speed. No odd splits like x4x4x8 or lower like I have on some intel platforms, but 4x or 8x NVMe for a smoking fast db server is now possible.

Other than the very obvious 1.2M mixup in FPN and TFA's point totals everything looks good to me.

Speaking of other accounts. Did anyone ever cash in their FLDC?

Currently the GPU portion of this is just 3D acceleration of OpenGl. Someone did file a request on the WSLg repo for OpenCl support. https://github.com/microsoft/wslg/issues/39 It was possible to do this before, but it was not a seamless experience like what Microsoft is doing here. It is still a bit hacky with what amounts to a nested VM inside of WSL accessed over RDP. Other than that, I'll just keep my thoughts to myself on the whole MicrosoftLinux narrative.

You're killing me. Might have to see if I can catch up when I get home tonight.

Liking all of the above. There will always be some outliers with any handicapping system, but I dig the overall plan. For what it's worth the db baseline numbers are almost certainly mostly cards running at stock with whatever version of GPU boost the card has. Everything that I've ran recently and in the past always exceeded whatever averages were out there, whether it was LARS or the old wu database on OCN. @Avacado I've got some tricks for your Teslas that we can test out over the next month, and it should be smoking by the time the comp starts on June 1st.

I think the multiplier should be based on the highest ppd GPU. Also, you can get some pretty whacky results when you handicap by OS. For example, the R9 200/300(aka 290, 390, etc) would get nearly a 2x multiplier if you ran it in Linux. I can say with 100% confidence that Windows is not twice as fast as Linux. In reality it is pretty much a wash between the two OS's. There are similar results with newer GPUs as well. A 2080S is for sure not 27% better when run in Linux. With the CUDA tasks it is maybe a few percent better. You can see this on the newer GPUs like the 3090 which is actually better on Windows according to the LARS db. I'm not sure how we account for those types of inconsistencies without just totally eliminating the OS as a variable in the handicapping.

Nothing to set. The EHW FAT is just the monthly folding competition. To enter for prizes and/or individual stats tracking during the competition, you just have to post in the thread with "IN" followed by your folding username.

https://forums.extremehw.net/topic/1095-extremehw-foldinghome-competition-april-21st-23rd/

I guess that's a wrap for April. Good luck next month.

p17800 was released to full F@H beck in February or March I think. All of the reports on that WU in the beta forum mirror what you're seeing. p17600 has a small number of atoms (36k), so it will be good on lower end GPUs, but high end GPUs will see reduced usage/ppd. Someone just reported the reduced ppd in the beta forum.

Tough to say for sure, since there really haven't been announcements since last summer of which projects are going from beta->advanced, except for a few times in the beta testing thread for the project. There have been announcements when projects go to full FAH, but some of those projects pretty much went from closed beta to full FAH without really ever hitting advanced (aka open beta). p17600 was just released to beta. I'll swap back over to beta on a few GPUs, and see if I see the same thing, I'll be sure and report it.

I'll clean it up a bit, and verify which flags are still relevant/working before posting.

I've been lucky with lockdowns and quarantines. I live out in the sticks, and if I'm not at work, working on one of my vehicles, or messing around with all my machines, I spend my free time out in the back-country. My life didn't really change once we went on lock down. I only have one semi-regret, and that is that I backed out of buying a 1999 2.5 RS coupe for my rally build. The guy was laid off from the lockdown, and just needed cash quick for rent and bills. I didn't feel right buying the car for 2k, when it was worth at least 3x that. I was the first one to call and go look at the car; I ended up hooking him up with a job, and he was able to keep the car. Happy ending for him, but now I'm on the hunt once again to get something to run next season.

That will work for setting a different team in the slot options. You can set team, user, and passkey to different values for each slot. Right now one of my machines looks something like this: <config> <!-- Folding Core --> <checkpoint v='10'/> <!-- Folding Slot Configuration --> <gpu v='false'/> <smp v='false'/> <!-- HTTP Server --> <allow v='0.0.0.0/0,127.0.0.1'/> <!-- Logging --> <verbosity v='5'/> <!-- Network --> <proxy v=':8080'/> <!-- Remote Command Server --> <command-allow-no-pass v='0.0.0.0/0,127.0.0.1'/> <!-- Slot Control --> <pause-on-battery v='false'/> <power v='full'/> <!-- User Information --> <passkey v='xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'/> <team v='239902'/> <user v='Q_Cruncher'/> <!-- Work Unit Control --> <next-unit-percentage v='98'/> <!-- Folding Slots --> <slot id='1' type='GPU'> <passkey v='xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'/> <team v='37726'/> <user v='TickTock99'/> </slot> <slot id='0' type='GPU'> <passkey v='xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'/> <team v='37726'/> <user v='TickTock99'/> </slot> <slot id='2' type='GPU'> <passkey v='xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'/> <team v='37726'/> <user v='TickTock99'/> <client-type v='beta'/> </slot> <slot id='3' type='GPU'> <passkey v='xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'/> </slot> </config>

Nothing specific, just a day of driving around, and then four days backpacking.