Unsupported computer

Message boards : Number crunching : Unsupported computer
Message board moderation

To post messages, you must log in.

AuthorMessage
Kevin Arnold

Send message
Joined: 4 Jan 02
Posts: 2
Credit: 481,059
RAC: 0
United States
Message 1760000 - Posted: 28 Jan 2016, 14:49:35 UTC

I have a functioning Boinc client and manager, but when I try to attach to SETI it gives me the following: 28-Jan-2016 08:07:39 [SETI@home] This project doesn't support computers of type x86_64-pc-freebsd

Any ideas to make this work, or just wait for v8?

OS: FreeBSD 10.2-Stable
Boinc Manager Version 7.2.33 (x64)
wxWidgets Version 2.8.12
BOINC client version 7.2.33 for x86_64-pc-freebsd
ID: 1760000 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6534
Credit: 196,805,888
RAC: 57
United States
Message 1760006 - Posted: 28 Jan 2016, 14:58:50 UTC
Last modified: 28 Jan 2016, 15:01:04 UTC

Looking at the BOINC projects list it looks like only a few have native support for FreeBSD.

I don't know how large the bsd user base for SETI@home is, but there might be someone that complies the apps for that platform. If not could can compile the apps for your system.

EDIT: The information on https://setiathome.berkeley.edu/sah_porting.php looks out of date. So you might need to get the source from lunatics if you are going to roll your own.
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[
ID: 1760006 · Report as offensive
Profile William
Volunteer tester
Avatar

Send message
Joined: 14 Feb 13
Posts: 2037
Credit: 17,689,662
RAC: 0
Message 1760009 - Posted: 28 Jan 2016, 15:13:26 UTC - in response to Message 1760006.  

The information on https://setiathome.berkeley.edu/sah_porting.php looks out of date. So you might need to get the source from lunatics if you are going to roll your own.

Since quite a while back, Lunatics sources are hosted at Berkeley too:
https://setisvn.ssl.berkeley.edu/trac/browser/branches/sah_v7_opt
or do an SVN checkout as described on the porting page.
A person who won't read has no advantage over one who can't read. (Mark Twain)
ID: 1760009 · Report as offensive
Profile HAL9000
Volunteer tester
Avatar

Send message
Joined: 11 Sep 99
Posts: 6534
Credit: 196,805,888
RAC: 57
United States
Message 1760025 - Posted: 28 Jan 2016, 15:57:13 UTC - in response to Message 1760009.  

The information on https://setiathome.berkeley.edu/sah_porting.php looks out of date. So you might need to get the source from lunatics if you are going to roll your own.

Since quite a while back, Lunatics sources are hosted at Berkeley too:
https://setisvn.ssl.berkeley.edu/trac/browser/branches/sah_v7_opt
or do an SVN checkout as described on the porting page.

I didn't see anything for v8. That's why it looked out of date to me.
SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[
ID: 1760025 · Report as offensive
Profile William
Volunteer tester
Avatar

Send message
Joined: 14 Feb 13
Posts: 2037
Credit: 17,689,662
RAC: 0
Message 1760072 - Posted: 28 Jan 2016, 18:37:30 UTC - in response to Message 1760025.  

The information on https://setiathome.berkeley.edu/sah_porting.php looks out of date. So you might need to get the source from lunatics if you are going to roll your own.

Since quite a while back, Lunatics sources are hosted at Berkeley too:
https://setisvn.ssl.berkeley.edu/trac/browser/branches/sah_v7_opt
or do an SVN checkout as described on the porting page.

I didn't see anything for v8. That's why it looked out of date to me.

Well apparentely neither Jason nor Raistmer felt it necessary to start a whole new branch for v8, but one of them put v7 into the initial commit...
Trust me all the optimisations are going into that sah_v7_opt branch (cuda is under XBranch in there) and Eric is committing in seti_boinc/client (so that's the branch you want to build for stock).
A person who won't read has no advantage over one who can't read. (Mark Twain)
ID: 1760072 · Report as offensive
Cygnus X-1
Volunteer tester

Send message
Joined: 15 Feb 04
Posts: 75
Credit: 3,732,505
RAC: 175
Canada
Message 1760472 - Posted: 29 Jan 2016, 21:59:03 UTC

I had a FreeBSD system running Seti until recently that I got going using these instructions: http://people.freebsd.org/~pav/boinc.html. I don't know if the ports have been updated to include the new V8 client yet.

You could also try running the linux version:

https://en.wikipedia.org/wiki/FreeBSD#OS_compatibility_layers
http://boinc.berkeley.edu/wiki/Installing_on_FreeBSD
ID: 1760472 · Report as offensive
Kevin Arnold

Send message
Joined: 4 Jan 02
Posts: 2
Credit: 481,059
RAC: 0
United States
Message 1760542 - Posted: 30 Jan 2016, 2:42:05 UTC - in response to Message 1760472.  

The current port works for Boinc, but is broken for Seti.

I did get Seti to work under wine. It seems to be running slower than it should.

I tried to compile from the source, but will need to edit the makefile to get the compiler to finish. This is not my strong suit.

The linux version is a good idea and I will try it to see how fast it operates.

Thanks everyone for all the input.
ID: 1760542 · Report as offensive
rob smith Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer moderator
Volunteer tester

Send message
Joined: 7 Mar 03
Posts: 22204
Credit: 416,307,556
RAC: 380
United Kingdom
Message 1760635 - Posted: 30 Jan 2016, 8:11:48 UTC

BOINC is not the same as SETI - BOINC is the environment in which SETI (and a whole load of other projects' applications run.
Thus it is perfectly possible for the environment to be running but a particular application not to run.

In this case it is probably because nobody has successfully ported and complied a FreeBSD version of the v8 application.
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?
ID: 1760635 · Report as offensive

Message boards : Number crunching : Unsupported computer


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.