Raspberry Pi 2B Work

aurorans_solis
aurorans_solis
Joined: 4 Apr 20
Posts: 11
Credit: 44,000
RAC: 0
Topic 221800

Hello, I'm trying to start some Raspberry Pis I have working on Einstein@home, but I keep getting the message that there's no work for armv7a-unknown-linux-gnueabihf. I'm curious what armv7* arches there are work for. It'll be some work to get things set up again since I'm running Gentoo (lots of stuff to recompile), but I wouldn't mind doing it too much.

Gary Roberts
Gary Roberts
Moderator
Joined: 9 Feb 05
Posts: 5,870
Credit: 116,035,479,448
RAC: 35,672,541

Hi, Welcome to Einstein! I

Hi, Welcome to Einstein!

I don't know anything about Pis but there are a number of people contributing here who do.

I just used the SEARCH button (top RH corner) and inserted the string "Pi AND 2B" and came up with a bunch of suggestions.  This one seems particularly promising (back in 2017) since it has information that changing preferences to allow 'test tasks' was successful at allowing a 2B to start working.  You might like to read through that thread to see if it's relevant.  If not, one of the Pi experts will probably come along shortly.

Good luck!!

 

Cheers,
Gary.

aurorans_solis
aurorans_solis
Joined: 4 Apr 20
Posts: 11
Credit: 44,000
RAC: 0

Thanks so much for your

Thanks so much for your reply! I had not come across that thread in my searching, but unfortunately it didn't turn out to be a solution to the problem I'm having. I checked through the XML files mentioned there (and some other ones I found in a similar directory), but none of them had anything that seemed to enable something like testing or beta versions of work. I also searched through the account settings available here in the web browser, but nothing seemed to indicate any sort of function like that.

Much thanks for your effort, though!

Gary Roberts
Gary Roberts
Moderator
Joined: 9 Feb 05
Posts: 5,870
Credit: 116,035,479,448
RAC: 35,672,541

Go to your account ->

Go to your account -> Preferences -> Project (ie. go here) and look for the sub-heading "Beta Settings".  Set "Run test apps" to "YES" and make sure you find the "Save Changes" button at the bottom of the page.  If you have different computers in different "Locations" make sure you are changing the preferences for the correct location you are using.  Not relevant if you don't use "Locations".

Cheers,
Gary.

aurorans_solis
aurorans_solis
Joined: 4 Apr 20
Posts: 11
Credit: 44,000
RAC: 0

Oh whoops, looks like I

Oh whoops, looks like I entirely missed that section of the preferences page. Nice work, me. Thanks for fixing my blindness.

aurorans_solis
aurorans_solis
Joined: 4 Apr 20
Posts: 11
Credit: 44,000
RAC: 0

Alright, got that set. I

Alright, got that set. I tried doing a project reset from boincmgr, but that kept telling me that server communication was deferred for 24 hours and my compute preferences that I changed never seemed to update. So I tried removing the project and adding it again. That got something:Event log shows "platform armv7a-unknown-linux-gnueabihf not found"

It then proceeded not to get any work.

Anonymous

have a look at this

have a look at this thread:  https://einsteinathome.org/content/parallella-raspberry-pi-fpga-all-stuff?page=20#comment-174570

Pay attention to the link within that thead and follow its instructions and I think you will be up and running.  

aurorans_solis
aurorans_solis
Joined: 4 Apr 20
Posts: 11
Credit: 44,000
RAC: 0

From what I'm seeing,

From what I'm seeing, Debian/Raspbian appears to be using the armv7l-unknown-linux-gnueabihf target, so if I swap over to that I should (hopefully) be able to get tasks. I'll give that a go on one of my Pis.

aurorans_solis
aurorans_solis
Joined: 4 Apr 20
Posts: 11
Credit: 44,000
RAC: 0

Too bad crossdev is having a

Too bad crossdev is having a bad time with merging that target - cross-armv7l-unknown-linux-gnueabihf/glibc just refuses to build, and no errors are left in the log. Hopefully I'll get this figured out, since I'd actually like to put some of my spare computing power to something useful.

 

Edit: turns out that despite the overall toolchain failing, the parts that succeeded were still left in. Just got the kernel compiled for the new target. Will do the rest when I wake up later this morning.

aurorans_solis
aurorans_solis
Joined: 4 Apr 20
Posts: 11
Credit: 44,000
RAC: 0

Ah, got it! I modified my

Ah, got it! I modified my ebuild for the arm arch so that its source configuration is


src_configure() {
    econf --disable-server \
        --enable-client \
        --disable-manager \
        --enable-dynamic-client-linkage \
        --disable-static \
        --enable-unicode \
        --with-ssl \
        --with-boinc-platform=arm-unknown-linux-gnueabihf \
        --with-boinc-alt-platform=arm-unknown-linux-gnueabihf
}

The '--with-boinc-platform=arm-unknown-linux-gnueabihf' was probably enough, but I included '--with-boinc-alt-platform=arm-unknown-linux-gnueabihf' to be safe. My clients just fetched their first work units. Yay! Now I just have to clone the ebuild to my other RPis, remake the manifests, build the new clients, and start them up again. Then I'll have 16 cores working on E@h. Feels good to resolve this finally!

Gary Roberts
Gary Roberts
Moderator
Joined: 9 Feb 05
Posts: 5,870
Credit: 116,035,479,448
RAC: 35,672,541

Congratulations on

Congratulations on persevering and succeeding!

Cheers,
Gary.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.