- #Raspberry pi boinc 7.6.33 64 Bit#
- #Raspberry pi boinc 7.6.33 software#
- #Raspberry pi boinc 7.6.33 free#
Can I do anything to increase my benchmark performance? If your devices are running hot, and you can't add cooling, you can reduce heat by limiting the amount of CPU BOINC is permitted to use.ĭoes this sidebar need an addition or correction? Tell me here You run the risk of seriously damaging the components, or even starting a fire. ✻ Smokey says: A NEW LIFE AWAITS US in our post-transition future Be smart with your electronics, never operate them with inadequate ventilation.
#Raspberry pi boinc 7.6.33 free#
Users can decide which projects they participate in, using the free and open-source BOINC client software. My question is: Does it sound like a defective hardware on the Raspberry PI ?Īny other ideas, what to check/do ? I'm going crazy with this issue, trying to solve it for the past few weeks.A subreddit dedicated to all things BOINC, a platform enabling the public to volunteer their computer's processing capability towards research projects distributed across the globe. Its just very odd to me that two identical PIs behave differently.
Even at 100% cpu, Pi #1 is still pretty responsive to commands at terminal through SSH. Second, Pi #1 has proved to me that its possible. Well, I want to maximize performance per Watts for BOINC. You may ask why I want to run at 100% cpu.
#Raspberry pi boinc 7.6.33 software#
I do not have any other peripherals connected to the PIs, and no other software running (except the default stuff thats installed on DietPi, such as Dropbear for SSH).
#Raspberry pi boinc 7.6.33 64 Bit#
Other random stuff: I tried running other OS on #2, mainly 64 bit such as Ubuntu server for arm64.No special problems, didn't solve the issue. Ran fsck on the SD Card of Pi #2 (on my Ubuntu laptop).I think the system crashes/freezes even before an error is written to the logs. Looking for errors in syslog: Nothing special found, as far as I understand.Monitoring voltage, temp, and CPU clock - everything looks OK.Running memtester, stress on #2, all results fine (throttling worked as expected when temp went high).Exchange ethernet cables, power suppies and cables.(in this scenario, setting Usage to 75% in BOINC means that all 4 cores will be used at 100%, but only for 75% of the time, for example 3 seconds work, 1 second suspend).ĭiagnostics wise I have tried the following: It seems like when running all 4 cores is problematic. In contrast, when number of CPUs is set to 100% (all 4 cores) but Usage set to 75%, it still crashes after a while. I am able to run BOINC on #2 with a lower number of CPUs (say 75 percent, meaning 3 cores will be used) and it runs fairly ok, even if Usage is set to 100 % (load average around 3.0). Same with BOINC's configuration (global_prefs override, same account manager, same project). I checked to make sure that cmdline.txt, and config.txt are identical on both. Memory usage is usage is usually less than 200MB on both of them. Wifi, BT and sound card set to off in config.txt Both are set to DHCP, and given a static IP by my router. Network: both connected to a 8 port gigabit switch using CAT6 cables. Set back everything to defaults now, on both Pis.
I tried to play with it to see if it has any effects, but it didn't. I've tried running in case, out of case, same results Swap file: Both have a 1GB swap file, but its not really being used (0 bytes/1GB).ģ heat sinks on each: CPU, LAN and on memory chipĬooling: Fan in case. Power supply: Both were originally on a 6 port USB charger, but in order to rule out power issues, #2 is now on its own 2.5A USB power supply with a high quality USB cable. Kernel: Linux 4.14.98-v7+ #1200 SMP Tue Feb 12 20:27: armv7l GNU/Linuxĭocker engine: Docker version 18.06.3-ce, build d7080c1īoinc docker container (boinc/client:arm32v7): 7.12.0 arm-unknown-linux-gnueabihf OS: DietPi (slimmed down version of Raspbian Stretch) v6.21.1 The thing that drives me crazy is that they are both identical, but #2 consistently freezes/crashes.īoth of them are running with the exact same configurations: On the other one (#1), I run BOINC at 100% CPU ( both #of CPUs and Usage in BOINC set to 100%), with load average a bit above 4.0 and its running great for days now! (Red PWR led on, Green ACT led offb bothe network leds on constantly, not blinking) Whenever the cpu load average gets close to 4 (usually between 3.5 and 4.0), it freezes, requiring me to pull the plug on it.
I'm running BOINC on two headless identical Pi 3 (B, not plus) but one of them (lets call it #2) is misbhaving: I would really appreciate the help of the experts here I have been playing around with Raspberry Pis ever since the Pi 2 came out, but I have a strange problem thats driving me crazy!
0 kommentar(er)
