tictoc

I've been running AMD GPUs on Linux since back in the bad old fglrx days, and outside of compute the current state of the drivers is better than it has ever been. @Bones your issue with the Radeon VII was probably due to the rather outdated kernel that ships with Mint. I don't know how much Mint backports to their kernel, but FYI for anyone that is running an AMD GPU, the AMD kernel driver receives constant updates and improvements and you will almost always be better served running a more up-to-date kernel than what many distros ship. For compute on AMD, AMD is re-working a bunch of their docs around ROCm (as evidenced by the link being "ROCm_5.1.1" even though it points to ROCM 5.1.3 ). Here is a link to the current docs: https://docs.amd.com/category/ROCm_v5.1.1 @bonami2 Technically the 6800XT is not listed in AMD's docs as "officially" supported on the ROCm stack, but most everything I've tested with my 6900XT works including F@H. Once you get ROCm installed you should be good to go on your 6800XT. I can't confirm if the posted install method from Diff works. I run an "unsupported" distro, but what Diff posted, and the link to the GitHub issue, looks good to me so it's worth a shot.

It's an EJ257, and the turbo cars (with the MLS gaskets) do not have the same head gasket issues that the NA cars have EJ251/53. Generally speaking head gasket failure is not that common on the turbo motors. Ironically, I did blow a head gasket at about 130k miles, but that has been the only issue I've had with the car. It is probably a bit of a unicorn, since it's been pushing well over stock power for 230k miles.

1/4 of a million miles and still rippin'. Last big snow of the year was last weekend, and night time temps have been pretty consistently above 34°F, so off with the snow shoes.

Looks like I'm not in this yet. Latest addition: Unicomp Mini M Daily driver | Filco Majestouch 2 TKL Camo | MX Brown | Keycaps: Blank Black PBT and Double Shot PBT Dark Gray w/ Black Legends Work board | Cooler Master Quick Fire TK | MX Brown w/ dampers On the KVM | Max Blackbird TKL | MX Brown Spare board | Corsair K65 RGB Mini Black | MX Speed

Not my last purchase, but one I purchased quite a while ago, that showed up on my front porch today. First order of business will be taking care of those nasty Windows keys Unicomp Mini M

I've been out since the beginning of the month (BOINC Pentathlon), but I'll have some gear back up an folding later this week.

Everything is up and running, and it will be getting a two week long stress test with the CPU and GPUs running 24/7, all out, for the BOINC Pentathlon. Setting up the whole software stack for the server will have to wait, so for now it's just running a minimal headless Arch setup for crunching.

I think one of the bigger problems is that a large percentage of "media" companies are owned or run by the companies that are actually delivering the media. This is especially a problem when there are large swathes of the US outside of major cities that only have one or maybe two options for internet/TV service. Companies like Comcast, AT&T, Verizon, and Charter are able to leverage their infrastructure to prop up their own media companies. This requires an obscene amount of oversight, since it would be easy for the companies that deliver the media to push the scales to favor their own in house media companies.

double post

If you're curious, you can grab a copy and give it a go. https://archive.org/search.php?query=creator%3A"PeoplePC"

Nice work last month @axipher I will not have my GPUs running 24/7 between now and the 19th. The BOINC Pentathlon has begun, and even though my team has gotten much smaller, I will be giving it all I've got. There will still be some folding time when my GPUs are not active. I'll be back to full time shortly after the 19th.

PowerShell is crazy in that it will display the path "properly" on Linux, but you can do whatever you want from the command line. The aggressive path normalization can break all sorts of things in a mixed Unix/Windows environment. From the command line these are all the same and the shell doesn't care: PS /> gci -Path home/tictoc/temp/testing/powershell -i *`(1`)* -r | ri PS /> gci -Path home\tictoc\temp\testing\powershell -i *`(1`)* -r | ri PS /> gci -Path home\tictoc/temp\testing/powershell -i *`(1`)* -r | ri

I imagine most of that performance lead evaporates against a 5995WX. IPC improvement of Zen 2 to Zen 3 is somewhere around 19% plus the higher stock clocks on a 5995WX. The real question is how Sapphire Rapids Xeons will compare to current Milan-X CPUs and the Zen 4 Genoa chips. Depending on the workload, a 7773X is a pretty nice improvement over a 7763 (especially for a mid-process refresh), to say nothing of the upcoming Genoa chips and it's rumored monster L2 cache and 20% performance improvement.

Late to the show, but this is the kind of task that can be quickly accomplished from the CLI. More than likely this is what those GUI apps are using under the hood. Since you're on windows we can use PowerShell with a few cmdlets. *Note* I am running this from PowerShell on Linux, but everything should be the same on Windows. Here is a test scenario I created to accomplish this from the CLI. List directories, sub-directories, and files in the current path: List all the files with "(1)" somewhere in the middle of the file name. PS /home/tictoc/temp/testing/powershell> Get-ChildItem -Include *`(1`)* -Recurse Directory: /home/tictoc/temp/testing/powershell/music UnixMode User Group LastWriteTime Size Name -------- ---- ----- ------------- ---- ---- -rw-r--r-- tictoc tictoc 4/28/2022 17:37 0 test (1).mp3 -rw-r--r-- tictoc tictoc 4/28/2022 17:37 0 test1 (1).mp3 -rw-r--r-- tictoc tictoc 4/28/2022 17:39 0 test2 (1).mp3 -rw-r--r-- tictoc tictoc 4/28/2022 17:39 0 test3 (1).mp3 -rw-r--r-- tictoc tictoc 4/28/2022 17:39 0 test4 (1).mp3 -rw-r--r-- tictoc tictoc 4/28/2022 17:39 0 test5 (1).mp3 Directory: /home/tictoc/temp/testing/powershell/music2 UnixMode User Group LastWriteTime Size Name -------- ---- ----- ------------- ---- ---- -rw-r--r-- tictoc tictoc 4/28/2022 19:02 0 test (1).mp3 -rw-r--r-- tictoc tictoc 4/28/2022 19:02 0 test1 (1).mp3 -rw-r--r-- tictoc tictoc 4/28/2022 19:02 0 test2 (1).mp3 -rw-r--r-- tictoc tictoc 4/28/2022 19:02 0 test3 (1).mp3 -rw-r--r-- tictoc tictoc 4/28/2022 19:02 0 test4 (1).mp3 -rw-r--r-- tictoc tictoc 4/28/2022 19:02 0 test5 (1).mp3 Find the files and delete them: PS /home/tictoc/temp/testing/powershell> Get-ChildItem -Include *`(1`)* -Recurse | RemoveItem or the short and sweet one-liner with aliases: PS /home/tictoc/temp/testing/powershell> gci -i *`(1`)* -r | ri Final result: PS /home/tictoc/temp/testing/powershell> Get-ChildItem -Recurse Directory: /home/tictoc/temp/testing/powershell UnixMode User Group LastWriteTime Size Name -------- ---- ----- ------------- ---- ---- drwxr-xr-x tictoc tictoc 4/28/2022 19:14 4096 music drwxr-xr-x tictoc tictoc 4/28/2022 19:14 4096 music2 Directory: /home/tictoc/temp/testing/powershell/music UnixMode User Group LastWriteTime Size Name -------- ---- ----- ------------- ---- ---- -rw-r--r-- tictoc tictoc 4/28/2022 17:33 0 test.mp3 -rw-r--r-- tictoc tictoc 4/28/2022 17:36 0 test1.mp3 -rw-r--r-- tictoc tictoc 4/28/2022 17:38 0 test2.mp3 -rw-r--r-- tictoc tictoc 4/28/2022 17:38 0 test3.mp3 -rw-r--r-- tictoc tictoc 4/28/2022 17:38 0 test4.mp3 -rw-r--r-- tictoc tictoc 4/28/2022 17:38 0 test5.mp3 Directory: /home/tictoc/temp/testing/powershell/music2 UnixMode User Group LastWriteTime Size Name -------- ---- ----- ------------- ---- ---- -rw-r--r-- tictoc tictoc 4/28/2022 19:02 0 test.mp3 -rw-r--r-- tictoc tictoc 4/28/2022 19:02 0 test1.mp3 -rw-r--r-- tictoc tictoc 4/28/2022 19:02 0 test2.mp3 -rw-r--r-- tictoc tictoc 4/28/2022 19:02 0 test3.mp3 -rw-r--r-- tictoc tictoc 4/28/2022 19:02 0 test4.mp3 -rw-r--r-- tictoc tictoc 4/28/2022 19:02 0 test5.mp3 Random aside, running PowerShell on Linux always feels like some whacky voodoo.

The maximum number of threads is 32 threads per slot. To get around this maximum, you just need to use miultiple CPU slots. I'll quote myself from the other thread:

I don't belive any dual socket boards ever hit the consumer market. Most of the high density Phi clusters were/are running on blades, so 4 boards/processors per 2U rack space.

F@H will maximize CPU usage, but many of the simulations are highly parallelizable, so those calculations are more suited to GPUs. Once upon a time there were some very large tasks that were tailored to many core CPUs, but most of that work has been ported over to OpenMM to run on GPUs. That being said, there are a number of projects that are CPU work only, and they are doing very interesting work. Here is a list of the currently active projects: https://apps.foldingathome.org/psummary The links in the project column will take you to a description of the project. The OPENMM_22 core is GPU work, and GRO_A8 and GRO_A7 are CPU only. The CPU core has been optimized over the last 4-5 years, and now takes advantage of AVX instructions so it will put the CPU to work.