Message boards :
Number crunching :
Packets get ready up to 90 %, then start again?
Message board moderation
Author | Message |
---|---|
Iikka Send message Joined: 12 Jul 17 Posts: 14 Credit: 2,246,416 RAC: 5 |
This happens with my new Raspberry PI 4B with Rasbpian installed. Never had aby trouble with Windows, Android or an older Raspberry Pi 3 B+ Calculations never get ready to be sent. This computer is on 24/7. What could be wrong here? I've made no big modifications to the system. -iikka |
rob smith Send message Joined: 7 Mar 03 Posts: 22605 Credit: 416,307,556 RAC: 380 |
I've made no big modifications to the system So what have you changed? I found my Pi4 ran very hot, and when "too hot" it would drop its wireless connection frequently. But having put a small fan blowing across both surfaces of the board it has kept its wireless connection it performed solidly (until I repurposed it for another job which means I'm not using it to process SETI data just now) Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? |
Iikka Send message Joined: 12 Jul 17 Posts: 14 Credit: 2,246,416 RAC: 5 |
I've made no big modifications to the system My Pi 4 has a fan, the 'Fan SHIM' from Pimoroni, and it works fine. It is adjustable, I have set it to kick in when CPU temperature reaches 75 Celsius, and go off again when cooled down to 63 C. So temperature is not a problem here. Also, the Pi is connected via ethernet cable. Can't find the problem. This morning, Pi is running fine after the night, but BOINC is still showing those same four packets, now 53 % ready... Maybe I just abandon these and wait for new ones. -iikka |
rob smith Send message Joined: 7 Mar 03 Posts: 22605 Credit: 416,307,556 RAC: 380 |
75C for the CPU (which is where the temperature is measured) appears to mean the RF chip is running too hot and it goes into its own thermal protection. I first tried a fan on the top surface but that didn't really work, so I swapped it to blow across the board so both surfaces are cooled. Hardwired connection - check for lease timeouts - I think the Pi has a short lease time by default which over rides any long lease time set by rest network hardware. Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? |
Iikka Send message Joined: 12 Jul 17 Posts: 14 Credit: 2,246,416 RAC: 5 |
Thank you.. I will try another (cooler) setting. BTW, my fan is this thing: https://learn.pimoroni.com/tutorial/sandyj/getting-started-with-fan-shim -iikka |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
BOINC only shows the running tasks on your computer, not the ones in queue? That's a setting in BOINC Manager, advanced view, tasks tab, Show all tasks. This button shows the option you have, not the state it's in (show running tasks). |
Iikka Send message Joined: 12 Jul 17 Posts: 14 Credit: 2,246,416 RAC: 5 |
Yes, I know that of course. From my homepage / computers stats view I can see that the RaspBerry 4 that we are talking about has no score, has contacted Seti's server a week ago (!)... And BOINC Manager shows me that it has started from scratch again, while the machine has been running just fine. -iikka |
Iikka Send message Joined: 12 Jul 17 Posts: 14 Credit: 2,246,416 RAC: 5 |
Yes, I know that of course. In the mean time btw, I've installed a new cooling case to the Pi 4. Temparatures are ~65 C when running Seti / doing other stuff. I also lowered the CPU load to 75 %, makes no difference to the problem. -iikka |
©2025 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.