RPI 3b not working

Hello there after config my rpi 3b for fold for covid., shows:

Rosetta needs 3gb but only 900mb

How can I solve it?

Greetings and stay in home

2 Likes

only PI 4 s are supported at the moment and PI 4 s with 4G+ RAM are preferred (mine only has 2G)

Hi,
I have the same problem.
According to: https://foldforcovid.io/#faqs Also RPI3 should work now. There was even a blog post that now more devices are supported.
https://www.balena.io/blog/balena-enables-more-devices-to-join-rosetta-home-to-research-covid-19/

Any information on this?

my bad :sorry: i was told earlier on this forum that only 64 bit ARMs were supported !

but i forget that balena have a PI 3 64 bit OS ! has anyone got a PI 3 64 working yet ?

Hey folks - the Pi 3 will work, and indeed I have a few here that are crunching, but they will only do work when the Rosetta project assigns tasks that are able to run with the lower amount of memory. So definitely set Pi 3s up and keep them online, as it means as soon as those tasks are set up the device will start crunching :+1:

We’ll get this information added to the FAQ on the site.

P.S. welcome to the community @londere!

2 Likes

Hi @chrisys ,
ok, thanks. Maybe the application output is also misleading:

17.04.20 10:00:11 (+0200)  boinc-client  17-Apr-2020 08:00:11 [---] 
17.04.20 10:00:11 (+0200)  boinc-client  17-Apr-2020 08:00:11 [---] 
17.04.20 10:00:11 (+0200)  boinc-client  17-Apr-2020 08:00:11 [---] 
17.04.20 10:00:11 (+0200)  boinc-client  17-Apr-2020 08:00:11 [---] 
17.04.20 10:00:13 (+0200)  boinc-client  17-Apr-2020 08:00:13 [http://boinc.bakerlab.org/rosetta/] Sending scheduler request: Project initialization.
17.04.20 10:00:13 (+0200)  boinc-client  17-Apr-2020 08:00:13 [http://boinc.bakerlab.org/rosetta/] Requesting new tasks for CPU
17.04.20 10:00:15 (+0200)  boinc-client  17-Apr-2020 08:00:15 [Rosetta@home] Scheduler request completed: got 0 new tasks
17.04.20 10:00:15 (+0200)  boinc-client  17-Apr-2020 08:00:15 [Rosetta@home] No tasks sent
17.04.20 10:00:15 (+0200)  boinc-client  17-Apr-2020 08:00:15 [Rosetta@home] Rosetta needs 1907.35 MB RAM but only 966.82 MB is available for use.

… looks a bit like the “boot process” was stopped, as the system requirements are not met.

Can you confirm that this is “as intended”?
Thanks

1 Like

yes and no

needs 1907.35 MB RAM but only 966.82 MB is available for use

looks like you need a PI 3 with > 4G

i will try and reproduce but my PI says it only has 1G ! so maybe theres no hope for me

however i am using a 32 bit OS so will reimage with a 64 bit to see if memory increases

# free
              total        used        free      shared  buff/cache   available
Mem:         998996      525692       78492       38100      394812      716188
Swap:             0           0           0

@chrisys how much ram do you have on your PI3’s ? is it even worth me trying a PI3 with 1G ?

RPI3 always has 1GB.
Only RPI4 has options from 1-4GB.

1 Like

so how can rosetta ever work on a PI 3 then ?

needs 1907.35 MB RAM but only 966.82 MB is available for use

oh dear i have even less RAM when i switch to PI OS 64bit

root@0fb8ff8:~# uname -a
Linux 0fb8ff8 4.19.71 #1 SMP PREEMPT Fri Jan 31 09:22:56 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux
root@0fb8ff8:~# free
              total        used        free      shared  buff/cache   available
Mem:         990024      244692      596992       13120      148340      749104
Swap:             0           0           0

just noticed the github page now says PI 3s ARE supported so i will persevere in seeing if i can get it running on my PI 3

This project should run on 64-bit OS devices with 1 or more GB of RAM, but we’ve tested on the below:

Raspberry Pi 3 (1GB RAM)
Raspberry Pi 4 (1GB RAM)
Raspberry Pi 4 (2GB RAM)
Raspberry Pi 4 (4GB RAM)

and make sure you pull latest rosetta from github since start.sh has changed

totalmem=$(awk '/^MemTotal:/{print $2}' /proc/meminfo)

if [ "$totalmem" -lt "2500000" ]; then
  echo "Less than 2.5GB RAM - running single concurrent task"
  exec boinc --allow_remote_gui_rpc --fetch_minimal_work
else
  exec boinc --allow_remote_gui_rpc
fi

result !

you MUST get latest code from github that supports < 2G ram and use PUBLIC URL via CLOUD gui instead of rosetta.local URLs which do not work

The Raspberry Pi 3 (running 64-bit OS) is available, but, there are not many work units available that fit within the 1gb RAM threshold. As the Baker Lab researchers load up work units into the Rosetta queue, most of them require 2gb of memory. There are a few however, that are smaller, and if any are available the Pi 3 will grab them.

So for now, if you have a 1gb RAM device and are not receiving any tasks you will simply need to wait for some smaller units to become available.

Hello dtischler,

I’m in the same situation and I was a little upset when I saw this memory lack on my RaspPI3, Therefore I decided to join forum to check if it was common issue. I admit i didn’t know there was a task queue. It would be helpful to learn a little bit about this queue and how tasks are assigned, how often and how it decides the device.

How ever I will let my RaspPi3 powered to check if it’s worth it the energy consuming and if at least once in a while Rosetta assigns a task to it.

1 Like

mi PI 3 has been running 110% CPU for over 36 hours at 5V and ~0.6A so only used 200 Wh

1000 Wh in the UK cost 15p

Mine is running two tasks now, I rebooted the Pi twice as it seemed stuck (first time gave up due to the 1Gb memory issue), then there was some server issue but now it seems OK.

1 Like

nice one ! whats your ranking in the TEAM list ? i got as high as 16th

How to find the TEAM ranking? My Pi3B+ seems to spend a lot of time waiting for tasks…

BOINC TEAM RANKINGS
https://boinc.bakerlab.org/rosetta/team_members.php?teamid=18832

if you are not ranked then get a KEY from
https://boinc.bakerlab.org/rosetta/weak_auth.php

then add it to YOU APP
wait 24 hrs then you should appear in the ranking

dont worry about waiting for jobs there are only a few jobs for CPUs with <2G RAM
it is a problem for all PI users (we will always be outranked by INUC users)

maybe @balenamktg could setup a separate team for PI users to give us a fair chance ?