SETI@home 8 released for Raspberry Pi.
Message boards :
News :
SETI@home 8 released for Raspberry Pi.
Message board moderation
Previous · 1 · 2 · 3 · 4 · 5
| Author | Message |
|---|---|
 BQL_FFM  Send message Joined: 25 Jan 04 Posts: 11 Credit: 1,197,409 RAC: 0 
|
Works fine with the newest Raspbian Jessie version and the Raspberry Pi 3B/2B. Good job! 
ID: 1794450 ·  |
|
The Jedi Alliance - ^WarHawk^ Send message Joined: 25 Jun 99 Posts: 29 Credit: 33,205,318 RAC: 77 
|
Sweet! Got it running on my RPi B at home, any way you gurus at seti@home can chop wu smaller for the ARM architecture 50-80 hour wu times are a bit lengthy, maybe cut em into 1/5 to 1/10 size chunks dedicated to arm crunchers..not a powerhouse processor, but you still have to eat an elephant one bite at a time Coincidentally, got the command line how to here https://pimylifeup.com/raspberry-pi-boinc/ ID: 1796026 · |
|
The Jedi Alliance - ^WarHawk^ Send message Joined: 25 Jun 99 Posts: 29 Credit: 33,205,318 RAC: 77
|
Does this work with the Pi 1 Model B? Does it take advantage of the GPU? I know the CPU is pretty weak on this unit... Yup, single core happily crunching at an estimated 80 hour wu time...yoikes! ID: 1796033 · |
|
The Jedi Alliance - ^WarHawk^ Send message Joined: 25 Jun 99 Posts: 29 Credit: 33,205,318 RAC: 77
|
I did have to update the /etc/boinc-client files [redirected from /var/lib/boinc-client/ directory] to match those of most of my windows machines namely the cc_config.xml global_prefs_override.xml files Just righ clicked and edit C:\ProgramData\BOINC <the files above> Copied the text over and in nano pasted it in, saved it Then ran boinccmd --read_cc_config The global_prefs_override.xml overrides the config files that all the clients download from the servers mine looks like this there really isn't much to it <global_preferences> <run_on_batteries>1</run_on_batteries> <run_if_user_active>1</run_if_user_active> <run_gpu_if_user_active>1</run_gpu_if_user_active> <suspend_cpu_usage>0.000000</suspend_cpu_usage> <start_hour>0.000000</start_hour> <end_hour>0.000000</end_hour> <net_start_hour>0.000000</net_start_hour> <net_end_hour>0.000000</net_end_hour> <leave_apps_in_memory>1</leave_apps_in_memory> <confirm_before_connecting>0</confirm_before_connecting> <hangup_if_dialed>0</hangup_if_dialed> <dont_verify_images>0</dont_verify_images> <work_buf_min_days>3.000000</work_buf_min_days> <work_buf_additional_days>3.000000</work_buf_additional_days> <max_ncpus_pct>100.000000</max_ncpus_pct> <cpu_scheduling_period_minutes>60.000000</cpu_scheduling_period_minutes> <disk_interval>300.000000</disk_interval> <disk_max_used_gb>0.000000</disk_max_used_gb> <disk_max_used_pct>50.000000</disk_max_used_pct> <disk_min_free_gb>0.100000</disk_min_free_gb> <vm_max_used_pct>75.000000</vm_max_used_pct> <ram_max_used_busy_pct>25.000000</ram_max_used_busy_pct> <ram_max_used_idle_pct>100.000000</ram_max_used_idle_pct> <max_bytes_sec_up>0.000000</max_bytes_sec_up> <max_bytes_sec_down>0.000000</max_bytes_sec_down> <cpu_usage_limit>100.000000</cpu_usage_limit> <daily_xfer_limit_mb>0.000000</daily_xfer_limit_mb> <daily_xfer_period_days>0</daily_xfer_period_days> </global_preferences> Here is the url for all the client config options in case you were wondering http://boinc.berkeley.edu/wiki/Client_configuration Command to restart boinc is: service boinc-client [stop|start|restart] I do have a question though...is boinc supposed to run under user boinc or root, and if so, what are the /var/lib/boinc-client ownership of the files supposed to be...I might have borked it when I did a -R chown root:root on that above directory... ID: 1796085 · |
|
The Jedi Alliance - ^WarHawk^ Send message Joined: 25 Jun 99 Posts: 29 Credit: 33,205,318 RAC: 77
|
upon reboot, boinc --daemon and now the setiathome_8.02 is running under user boinc so all is well. Very cool! ID: 1796327 · |
|
The Jedi Alliance - ^WarHawk^ Send message Joined: 25 Jun 99 Posts: 29 Credit: 33,205,318 RAC: 77
|
My seti@home seems to keep conking out, get a kernel error then when I view the task in top I se 0 0 0 on the seti@home program I created config files global_prefs.xml and global_prefs_override.xml and copied the information from there from my windows config files I get the below Initialization completed I keep getting this error Jun 17 18:11:02 raspberrypi kernel: [221780.132410] BUG: unsupported FP instruction in kernel mode Jun 17 18:11:02 raspberrypi kernel: [221780.141533] Internal error: Oops - undefined instruction: 0 [#6] ARM Jun 17 18:11:02 raspberrypi kernel: [221780.151504] Modules linked in: zram lz4_compress zsmalloc tun cpufreq_stats mkiss ax25 arc4 ecb md4 md5 hmac nls_utf8 cifs xt_nat iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack ip_tables x_tables snd_bcm2835 snd_usb_audio snd_usbmidi_lib snd_hwdep snd_seq_midi snd_seq_midi_event snd_rawmidi snd_pcm snd_seq snd_seq_device snd_timer snd evdev bcm2835_gpiomem bcm2835_rng uio_pdrv_genirq uio Jun 17 18:11:02 raspberrypi kernel: [221780.209429] CPU: 0 PID: 14186 Comm: setiathome_8.02 Tainted: G D 4.1.19+ #858 Jun 17 18:11:02 raspberrypi kernel: [221780.224269] Hardware name: BCM2708 Jun 17 18:11:02 raspberrypi kernel: [221780.230931] task: d4668da0 ti: dd19e000 task.ti: dd19e000 Jun 17 18:11:02 raspberrypi kernel: [221780.239566] PC is at vfp_save_state+0x0/0x28 Jun 17 18:11:02 raspberrypi kernel: [221780.246985] LR is at vfp_sync_hwstate+0x3c/0x48 Jun 17 18:11:02 raspberrypi kernel: [221780.254583] pc : [<c000a948>] lr : [<c000a58c>] psr: 60000113 Jun 17 18:11:02 raspberrypi kernel: [221780.254583] sp : dd19fe78 ip : dd19fe90 fp : dd19fe8c Jun 17 18:11:02 raspberrypi kernel: [221780.272037] r10: 002efe08 r9 : dd19e000 r8 : bebfd3d8 Jun 17 18:11:02 raspberrypi kernel: [221780.280205] r7 : bebfd4c8 r6 : dd19e0f8 r5 : bebfd5d0 r4 : c0000788 Jun 17 18:11:02 raspberrypi kernel: [221780.289637] r3 : dd19e0f8 r2 : c0842364 r1 : c0000788 r0 : dd19e0f8 Jun 17 18:11:02 raspberrypi kernel: [221780.299008] Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user Jun 17 18:11:02 raspberrypi kernel: [221780.309012] Control: 00c5387d Table: 1d1b0008 DAC: 00000015 Jun 17 18:11:02 raspberrypi kernel: [221780.317604] Process setiathome_8.02 (pid: 14186, stack limit = 0xdd19e188) Jun 17 18:11:02 raspberrypi kernel: [221780.327281] Stack: (0xdd19fe78 to 0xdd1a0000) Jun 17 18:11:02 raspberrypi kernel: [221780.334368] fe60: dd19fe90 dd19e000 Jun 17 18:11:02 raspberrypi kernel: [221780.347754] fe80: dd19feac dd19fe90 c000a6f0 c000a55c 00000000 bebfd3d8 00000000 d4669208 Jun 17 18:11:02 raspberrypi kernel: [221780.361234] fea0: dd19fec4 dd19feb0 c0012d20 c000a6c8 dd19ffb0 dd19fec8 dd19ff8c dd19fec8 Jun 17 18:11:02 raspberrypi kernel: [221780.374871] fec0: c0013150 c0012bac 000d5378 14000000 0021b940 00000000 00000000 0000000e Jun 17 18:11:02 raspberrypi kernel: [221780.388693] fee0: 00000000 00000080 00000000 00000000 00000000 00000001 00000000 dd19ff08 Jun 17 18:11:02 raspberrypi kernel: [221780.402610] ff00: c005b474 c005d5e0 c0044b1c 0000000e 00000011 c07d6e1c 00000001 c07d6e1c Jun 17 18:11:02 raspberrypi kernel: [221780.416644] ff20: c081b9b8 00000000 00000000 c005dc4c dd19ff4c dd19ff40 c005dc4c c005a9b8 Jun 17 18:11:02 raspberrypi kernel: [221780.430914] ff40: dd19ff5c dd19ff50 c001ff64 c002741c dd19ff74 dd19ff60 c002741c 0000000e Jun 17 18:11:02 raspberrypi kernel: [221780.445471] ff60: c005df80 00000001 dd19e000 00000000 dd19ffb0 00000000 dd19e000 002efe08 Jun 17 18:11:02 raspberrypi kernel: [221780.460324] ff80: dd19ffac dd19ff90 c0013458 c0012e8c 0002b410 80000010 f200b200 00c5387d Jun 17 18:11:02 raspberrypi kernel: [221780.475479] ffa0: 00000000 dd19ffb0 c000f7e4 c001339c 007cfd5c bebfd73c 00000026 007cfd80 Jun 17 18:11:02 raspberrypi kernel: [221780.490845] ffc0: 007cfc80 00000011 007cfa98 00000040 002f1f60 002eff31 002efe08 002e8958 Jun 17 18:11:02 raspberrypi kernel: [221780.506321] ffe0: 007cfb2c bebfd6c8 0002b3b8 0002b410 80000010 ffffffff 00000000 00000000 Jun 17 18:11:02 raspberrypi kernel: [221780.522041] [<c000a948>] (vfp_save_state) from [<c000a6f0>] (vfp_preserve_user_clear_hwstate+0x34/0xc0) Jun 17 18:11:02 raspberrypi kernel: [221780.539196] [<c000a6f0>] (vfp_preserve_user_clear_hwstate) from [<c0012d20>] (setup_sigframe+0x180/0x190) Jun 17 18:11:02 raspberrypi kernel: [221780.556397] [<c0012d20>] (setup_sigframe) from [<c0013150>] (do_signal+0x2d0/0x3e0) Jun 17 18:11:02 raspberrypi kernel: [221780.571559] [<c0013150>] (do_signal) from [<c0013458>] (do_work_pending+0xc8/0xd8) Jun 17 18:11:02 raspberrypi kernel: [221780.586592] [<c0013458>] (do_work_pending) from [<c000f7e4>] (work_pending+0xc/0x20) Jun 17 18:11:02 raspberrypi kernel: [221780.601767] Code: e12fff1e e1a0200d e1a0e009 eafffebe (eca00b20) Jun 17 18:11:02 raspberrypi kernel: [221780.651861] ---[ end trace 1c84d8a60ef928d4 ]--- Found this Please advise over root@raspberrypi /var/log # ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 3793 max locked memory (kbytes, -l) unlimited max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 95 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 3793 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited I did this...let's see if it helps ulimit -s 65536 root@raspberrypi /var/log # ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 3793 max locked memory (kbytes, -l) unlimited max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 95 stack size (kbytes, -s) 65536 cpu time (seconds, -t) unlimited max user processes (-u) 3793 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited ID: 1796978 · |
|
Tom Rinehart Send message Joined: 12 Dec 01 Posts: 113 Credit: 13,255,975 RAC: 6
|
I did this...let's see if it helps This is a known issue that no one has been able to resolve so far. Please let us all know if this works. ID: 1797566 · |
|
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 
|
I did this...let's see if it helps I checked this out on my SDCard image with kernel 3.10.25+ where this problem doesn't exist and i get: pi@raspberrypi /var/log $ ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 3372 max locked memory (kbytes, -l) unlimited max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 95 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 3372 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited Stack size wasn't any bigger then, but maybe later kernels need bigger stack sizes Claggy ID: 1797598 · |
|
The Jedi Alliance - ^WarHawk^ Send message Joined: 25 Jun 99 Posts: 29 Credit: 33,205,318 RAC: 77
|
Still locking up... I'm at a loss Jun 21 13:29:20 raspberrypi kernel: [62653.599313] BUG: unsupported FP instruction in kernel mode root@raspberrypi /var/log # uname -mrs Linux 4.1.19+ armv6l I just did a sudo rpi-update root@raspberrypi /home/pi # uname -mrs Linux 4.4.13+ armv6l I wonder if the person that compiled 8.02 set a stack limit or it was set default...perhaps an upgraded compile for arm with unlimited or larger stack size...heck I don't even know if I am even looking in the right spot for the lockup of the program so I'm just spitballing here I found a few other discussions about this...it seems like it's a kernel issue, not a program issue https://github.com/raspberrypi/linux/issues/859 https://github.com/raspberrypi/linux/issues/600 ID: 1798595 · |
|
Tom Rinehart Send message Joined: 12 Dec 01 Posts: 113 Credit: 13,255,975 RAC: 6
|
I compiled the 8.02 version and didn't change the stack limit. I'm not sure where that would be even. The issue seems like a memory problem to me, but everything I've read looks like it is related to the kernel. It doesn't happen to my Pi 1 B with Einstein@home or when I was running beta S@H and it was serving small WUs. It doesn't work well with big WUs for some reason and has this crash. ID: 1799690 · |
|
Tom Rinehart Send message Joined: 12 Dec 01 Posts: 113 Credit: 13,255,975 RAC: 6
|
According to the Applications page (http://setiathome.berkeley.edu/apps.php) the Linux ARM application is now producing greater than 500 GigaFLOPS from all the various Linux ARM devices out there! Now we just need someone that understands ARM assembly language or how to inline assembly language into C properly to help get the chirp data routines working on VFP and NEON for an even faster app. ID: 1799693 · |
|
The Jedi Alliance - ^WarHawk^ Send message Joined: 25 Jun 99 Posts: 29 Credit: 33,205,318 RAC: 77
|
I saw where someone changed their global preferences to like below I've been successful at getting my Orange Pi One (https://setiathome.berkeley.edu/results.php?hostid=8027213) to run the SETI app with all four cores. I had to adjust how Boinc uses memory for it to be stable by editing: still checking if stable...just restarted my crashed BOINC...lets see if it remains stable ID: 1805888 · |
|
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4
|
Still locking up... The kernel issue has now been fixed, anyone running kernels 4.4.48+ #964 or 4.9.9+ #965 or later won't see this issue again, Do the following to show what kernel version you run: uname -a Do the following in a cmd window to update, then reboot: sudo apt-get update && sudo apt-get upgrade I posted about the issue on GitHub, I get a response that a patch might fix it, Forked the RaspberryPi Kernel source tree on GitHub, carefully applied the patch to the later kernel, did a push request, got it applied, tested it via the rpi-update app, proved that it fixed it, then waited for it to be applied to the production kernel, then made sure that the 4.4.48+ kernel worked too. Faster Arm apps are in testing at Seti Beta too :-) Claggy ID: 1852378 · |
Eric Gigante   Send message Joined: 26 Jun 99 Posts: 5 Credit: 10,144,922 RAC: 14
|
I have been running Seti on my Raspberry Pi 2 model b and the average work unit is around 50 hours. I understand that is average and I am not trying to overclock the Pi's. What I am wondering is if the Raspberry Pi 3 complete's the work units any faster? 
ID: 1852451 · |
Gary Charpentier     Send message Joined: 25 Dec 00 Posts: 30923 Credit: 53,134,872 RAC: 32
|
I have been running Seti on my Raspberry Pi 2 model b and the average work unit is around 50 hours. I understand that is average and I am not trying to overclock the Pi's. What I am wondering is if the Raspberry Pi 3 complete's the work units any faster? A Pi 3 https://setiathome.berkeley.edu/results.php?hostid=8173315 calculate to your hearts content. 
ID: 1852465 · |
Wiggo  Send message Joined: 24 Jan 00 Posts: 36336 Credit: 261,360,520 RAC: 489 
|
I have been running Seti on my Raspberry Pi 2 model b and the average work unit is around 50 hours. I understand that is average and I am not trying to overclock the Pi's. What I am wondering is if the Raspberry Pi 3 complete's the work units any faster? About 20hrs faster by the looks of similar AR tasks in the 0.4-0.44 range by a quick look. Cheers. ID: 1852469 · |
|
BetelgeuseFive Send message Joined: 6 Jul 99 Posts: 158 Credit: 17,117,787 RAC: 19 
|
Work on a better application for Raspberry Pi is in progress over on Beta. Check this thread: https://setiweb.ssl.berkeley.edu/beta/forum_thread.php?id=2275 Tom ID: 1852504 · |
©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.