Some projects have the same CPID but refuse to show up in the combined totals.Īlso, stats aren't being shown on CPID:- 81362746 at all. The thing is now I have multiple CPID's and multiple entries in the "BoincSats/FreeDC stats" database(s). Still processing BOINC projects per your excellent tasballs as usual. Here's a head scratcher - I thought I'd pass it by you before raising it with othes.Īs probably everyone on the planet has done, I've had to rebuild my SD card (more than once). The best way is the one wot suits u) Reply Delete When the BOINC Manager has opened, to see the benchmark figures click "Advanced" & "Event Log" When the list of menu items appear click on BOINC Manager. Start the boinc manager using the "Other" menu item by.
BOINC PROJEKT PASSWORD
Logon as usual with your username and password (if you haven't changed them)
Type in the necessary configuration parametersĪfter exiting the editor, restart the RPi using the command To edit the configuration file, enter the command:. Reboot the Raspberry Pi and enter your username and password. which is a bit more human-friendly than vi. I have tried and tried but keep failing with the obtuse message about ! when editing a read-only file. with BOINC 10%, if I start Midori the RPi struggles again:- 100% on the CPU graph aargh! Reply Delete Anything I did seemed to send the Raspian CPU graph to 100% even a click on the Logout icon with nothing running? Again, truly slow at anything non-BOINC & struggles via BOINC (manager) to perform a simple task like "communicate with client".Įventually I managed to shutdown despite BOINC refusing to shut up shop showing the fail to "communicate with client" popup.Īfter a warm restart. Yes it will eventually work (some minutes). However, open up a browser (like Midori) and everything just grinds to a halt and the RPi struggles via BOINC (manager) to perform a simple task like "communicate with client". Thinking a bit of slack time would be useful I tried reducing the CPU setting in BOINC - same (bad) experience at 90% CPU.Īt 50% then 66.66% & 75% CPU everything was pretty much OK without another program running - a little jerky but at least the RPi talked to me. I once waited 20 minutes for a single mouse click to register. Here is a bit more, hopefully helpful, info:-Īt 100% CPU the RPi does well crunching but is almost unusable otherwise.
OK BOINC crunching (via Raspbian in my case) using Xwindows & the BOINC GUI on the RPi is early days. No - it wasn't a faulty keyboard/mouse adapter plug.
0 kommentar(er)
