Out of ARM64 assignments?

[stinerman]

Hi friends,

I set up a headless Pi 4B and installed the client. So far I haven't received a WU. I'm new to Raspberry Pi and configured it manually, so I'm checking to see if this is a "just me" thing or if anyone else is experiencing a WU shortage as well.

Happy folding!

[bruce]

It does look like we are short of WUs. ARM is still in active development so most anything might have happened.

The more mature clients (GPUs/X86) have been short of new work but the scientists tend to replenish them more frequently/quickly than the developmental segments of the workload.

[stinerman]

Yep, my x64/GPU folding is running fine. Thanks bruce!

[bruce]

Is your set up able to differentiate between big and LITTLE hardware components?

[DocWherm]

Same thing is happening to me. It has been ~18 hours and my ARM64 client has been unable to get work units. I have tried all kinds of configurations on my CPU slot(s) and have tried using the advanced client option and still can't get anything. Are we just out of WUs for the ARM client or???

[Neil-B]

Are we just out of WUs for the ARM client or???

Welcome to the forums DocWherm ... See bruce's first response in thread above

[stinerman]

Is your set up able to differentiate between big and LITTLE hardware components?

I'm not certain what this means but my config is as follows:

<config>
<!-- Folding Core -->
<checkpoint v='30'/>

<!-- Folding Slot Configuration -->
<cause v='HIGH_PRIORITY'/>
<gpu v='false'/>

<!-- HTTP Server -->
<allow v='127.0.0.1 192.168.0.0/24'/>

<!-- Network -->
<proxy v=':8080'/>

<!-- Remote Command Server -->
<command-allow-no-pass v='127.0.0.1 192.168.0.0/24'/>

<!-- Slot Control -->
<pause-on-battery v='false'/>
<power v='full'/>

<!-- User Information -->
<passkey v='********'/>
<team v='224497'/>
<user v='stinerman'/>

<!-- Folding Slots -->
<slot id='0' type='CPU'/>
</config>

One thing that may be useful is that I'm running the beta 64-bit Raspberry Pi OS on my machine.

[SilvioMartin]

I think you just had bad luck. I have been running FH on a Raspberry Pi 4B since November and on a rack of 4 Raspberry Pi 4B since mid December. I use the default setting, running on all 4 cores. They just stopped getting new WUs on February 22nd late evening (UTC). There were times without work units earlier. The longest I've seen was a phase of several days (4? 5? 7?) without new work units in early January. Here you can check, how my guys are doing: http://anne-emscher.net/fah/ If you see anyone there working and yours isn't, then you might have an issue with your specific configuration.

[bruce]

One thing that may be useful is that I'm running the beta 64-bit Raspberry Pi OS on my machine.

Perhaps that's the difference.

@ SilvioMartin Please describe your software.

@ stinerman Please include the information mentioned in the Sig block of my first post in this topic.

[SilvioMartin]

@bruce: Sure.

1. Raspberry Pi OS 64 bit beta, downloaded from here: https://downloads.raspberrypi.org/raspios_arm64/images/ There are two versions as of now. I ran the FAH client with both successfully. Now I am using the one in raspios_arm64-2020-08-24 only.
2. FAH client, control and viewer 7.6.21, for ARM Linux / Raspberry Pi, downloaded here: https://foldingathome.org/alternative-downloads/

I run this on Raspberry Pi 4B with 2 GB RAM and a 16 GB SanDisk Ultra SD card. The setup of the OS and the FAH client is described here on page 7 and 8: http://www.anne-emscher.net/fah/FAtRasPi.pdf

[SilvioMartin]

There is something in the ARM pipeline again:

Code: Select all

06:36:57:WU00:FS00:0xa8:Project: 16517 (Run 0, Clone 763, Gen 1)

I haven't seen that project before.

[stinerman]

Yes, I just received a work unit about 8 hours ago. Looks like all is well.

[bruce]

Project: 16517 is out of HKUST (Hong Kong University of Science and Technology) has been a mostly inactive supplier of FAH projects (though I know Dr. Xuhui from his days at Stanford.)

it never hurts to have an active FAH server in another part of the world.