Posts by David Anderson (not *that* DA)

1) Message boards : Number crunching : Ubuntu 18.04 (Message 1938099)
Posted 18 days ago by Profile David Anderson (not *that* DA) Project Donor
Post:
I had a similar problem when Ubuntu 16.04 installed 384.130
a couple days ago.

I fixed it with the series of actions I document in
https://setiathome.berkeley.edu/forum_thread.php?id=82997

which was advice I think I got from Tbar in march 2017.
Worked then and worked today.
2) Message boards : Number crunching : Opencl Ubuntu 16.04 nvidia 384.130 fails (Message 1938097)
Posted 18 days ago by Profile David Anderson (not *that* DA) Project Donor
Post:
Looks as if GPU tasks completing ok now.
I'll keep watching.
3) Message boards : Number crunching : Opencl Ubuntu 16.04 nvidia 384.130 fails (Message 1938088)
Posted 18 days ago by Profile David Anderson (not *that* DA) Project Donor
Post:
I switched to Noveau, the non-nvidia driver.
Rebooted.
dpkg -l |grep -i nvidia
sudo apt purge (the stuff listed by the above)
sudo bash
cd /var/lib/boinc*/projects/seti*
and rm *wisdom* *bin*
exit (back to being me)


Used 'additional drivers' panel to request 384.130

Rebooted
Restarted seti.
One gpu task seems to be running toward completion.
There are a few more. Turned off getting new tasks
while I wait to see how the opencl_nvidia_SoG
tasks go.
4) Message boards : Number crunching : Opencl Ubuntu 16.04 nvidia 384.130 fails (Message 1937961)
Posted 20 days ago by Profile David Anderson (not *that* DA) Project Donor
Post:
WARNING: boinc_get_opencl_ids failed with code -1
Error: Getting Platforms. (clGetPlatformsIDs)
BOINC assigns slot on device #0.
WARNING: BOINC failed to provide OpenCL device, using own enumeration abilities
ERROR: OpenCL kernel/call 'clGetDeviceIDs (second call)' call failed (-32) in file ../../src/GPU_lock.cpp near line 1311.

computer: 7748035
This Ubuntu 16.04 machine got a new nvidia
driver (not that I requested such) replacing one that worked with...
the above. The good one, 340.104, worked fine a long time.

In about a day the bad one accumulated 248 error tasks.
Erroring very quickly indeed. There are reports of opencl issues
with the latest driver on backports (which means on 16.04 ).

Well, ugh. Took me a whole day to notice.
I hope the older driver still works, I switched to the older one.
I won't restart seti on this machine till I will be where
I can watch progress and
can stop it if nvidia/opencl still broken.
5) Message boards : Number crunching : No protocol specified - in boincerr.log (Message 1934006)
Posted 6 May 2018 by Profile David Anderson (not *that* DA) Project Donor
Post:
A linux machine running boinc-client has no monitor
plugged in and after a couple minutes up time
boinc-client starts writing "No protocol specified"
to /var/log/boincerr.log once every second. Forever.

boinc-client runs fine. seti tasks run fine.
boincmgr (ver 7.6.31) , run via ssh from
another machine, runs fine.
The message on boincerr.log seems completely pointless
and is a waste of flash-disc update cycles.

Why doesn't the message repeat-time back-off so the rate goes asymptotically to zero?
Or something.

Is there a way to suppress this message?
Thanks for any suggestions.
6) Message boards : Number crunching : SETI/BOINC Milestones [ v2.0 ] - XXIX (Message 1929790)
Posted 13 Apr 2018 by Profile David Anderson (not *that* DA) Project Donor
Post:
I finally arrived at 50,000,000 cobblestones!
Took quite a while and I managed to 'enlist'
a couple more computers and keep them
focused on Seti...

The most interesting of the lot is a tiny
single-board machine with 8 arm cores each
at nearly 2GHz. It's still hard to believe
that such a thing exists. Under US$100.

What to set as the next goal?
7) Message boards : Number crunching : boinc-client and X and monitor (Message 1927535)
Posted 31 Mar 2018 by Profile David Anderson (not *that* DA) Project Donor
Post:
I tried that and it did not make a difference.
It does not surprise that Linux and X don't use the
same monitor-sense approach as past Windows.

For now on the system I'm just letting boinc-client log
in boincerr.log every second :-(

Thanks for the tip, though. Worth a try.
DavidA.
8) Message boards : Number crunching : GPU Not Detected - Linux (Message 1926777)
Posted 26 Mar 2018 by Profile David Anderson (not *that* DA) Project Donor
Post:
In the menu system (Assuming Ubuntu or equiv)
Go to Settings->Additional Drivers and in the Additional Drivers
area of that page click on the driver you want (radio buttons
there...).

Simply installing a driver does not (necessarily?)
make it the current GPU driver.

That page will install the driver named if it's not installed
already.
========
9) Message boards : Number crunching : boinc-client and X and monitor (Message 1923138)
Posted 7 Mar 2018 by Profile David Anderson (not *that* DA) Project Donor
Post:
Was unable to find anything (meaningful to me)
about running boinc-client with no monitor.
What little I found was old(er) boinc-client and
the logging has, according to some messages
I found, changed over time.

Reducing the clock rate slightly on the
single board computer has let it run
boinc for two days (with monitor attached).
It seems possible the boinc-client log
messages (when headless) were not a problem at all,
just an annoyance.

If anyone has knowledge of current boinc-client run headless
and controlling boinc-client logging in that environment
I'd appreciate hearing about such.
But otherwise I'll just take this as a learning experience :-)
10) Message boards : Number crunching : boinc-client and X and monitor (Message 1922239)
Posted 3 Mar 2018 by Profile David Anderson (not *that* DA) Project Donor
Post:
Focusing on confusing issues with odroid-xu4 itself right now.
It's run 24 hours with 4 seti tasks at once, no errors.

For now just letting it run with os configure changes
on that machine. In a couple days will review
again unless something changes sooner.
11) Message boards : Number crunching : boinc-client and X and monitor (Message 1921752)
Posted 28 Feb 2018 by Profile David Anderson (not *that* DA) Project Donor
Post:
Thanks Keith. I will look for such threads.
I was out of town a couple days (now back) and
notice that plugging in a monitor (
while system down, then rebooting)
does not remove the messages from boinc.
Even logged in via ssh.
But logging in at the local keyboard/monitor stops
the
No protocol specified
boinc-client messages.

Have yet to have the system in question
run two days
without stopping...sigh.
12) Message boards : Number crunching : boinc-client and X and monitor (Message 1921106)
Posted 25 Feb 2018 by Profile David Anderson (not *that* DA) Project Donor
Post:
My concern is that a side effect of the 'error' is to pile up
some set of resources leading to eventual kernel
hangup. Not that I have any evidence of that
other than the system just seeming to stop.

So far, with monitor in use, I see no boincerr.log
records being added and no hangs.
But odroid-xu4 needs to keep going for much longer
to mean much.
13) Message boards : Number crunching : boinc-client and X and monitor (Message 1921083)
Posted 25 Feb 2018 by Profile David Anderson (not *that* DA) Project Donor
Post:
boinc-client is started by systemd, so it's running
as a daemon already, I would think.

/etc/systemd/system/multi-user.target.wants
links boink service to
/lib/systemd/system/boinc-client.service

which comtains:
[Unit]
Description=Berkeley Open Infrastructure Network Computing Client
After=network.target

[Service]
Nice=10
User=boinc
PermissionsStartOnly=yes
ExecStartPre=/usr/bin/touch /var/log/boinc.log /var/log/boincerr.log
ExecStartPre=/bin/chown boinc:boinc /var/log/boinc.log /var/log/boincerr.log
#ExecStart=/usr/bin/boinc --dir /var/lib/boinc-client
ExecStart=/bin/sh -c '/usr/bin/boinc --dir /var/lib/boinc-client >/var/log/boinc.log 2>/var/log/boincerr.log'
ExecReload=/usr/bin/boinccmd --read_cc_config
ExecStopPost=/bin/rm -f /var/lib/boinc-client/lockfile
IOSchedulingClass=idle

[Install]
WantedBy=multi-user.target

Which does not use -daemon . Hmm. I don't know much about systemd
though.
14) Message boards : Number crunching : CPU GPU pause when in use (Message 1920936)
Posted 24 Feb 2018 by Profile David Anderson (not *that* DA) Project Donor
Post:
Oh. Somehow Keith's reply did not show up at the right
time, so mine was redundant.
15) Message boards : Number crunching : CPU GPU pause when in use (Message 1920934)
Posted 24 Feb 2018 by Profile David Anderson (not *that* DA) Project Donor
Post:
Could something running in background (after the
3 minute dormancy check, like an intrusive screen-saver)
be making boinc think the computer is in use when
you don't think it is? Just a guess.
16) Message boards : Number crunching : boinc-client and X and monitor (Message 1920929)
Posted 24 Feb 2018 by Profile David Anderson (not *that* DA) Project Donor
Post:
Running boinc on a small computer. If I leave the monitor detached boinc-client starts to complain that "No protocol specified" in /var/log/boincerr.log .

This is with
boinc-client 7.6.31+dfsg- armhf
Ubuntu 16.04 LTS

Seems quite odd to me. I don't have much need for a monitor
on that machine (I ssh in and run boincmgr remotely), so ... why?
Quite odd.
17) Message boards : Number crunching : Cost of acquisition + performance per W for newer single board computers vs. desktop and dedicated GPUs. (Message 1917892)
Posted 9 Feb 2018 by Profile David Anderson (not *that* DA) Project Donor
Post:
I'm measuring the (12 W) power use at the wall plug
with a Brand Electronics Digital Power Meter.
18) Message boards : Number crunching : Cost of acquisition + performance per W for newer single board computers vs. desktop and dedicated GPUs. (Message 1917891)
Posted 9 Feb 2018 by Profile David Anderson (not *that* DA) Project Donor
Post:
I decided that I should measure power instead
of just quoting the max power the ac-dc
converter can deliver.

Running seti (four tasks) its power
use bounces around between 11W
and 12.x watts.

I'll call it 12W.
19) Message boards : Number crunching : Cost of acquisition + performance per W for newer single board computers vs. desktop and dedicated GPUs. (Message 1917889)
Posted 9 Feb 2018 by Profile David Anderson (not *that* DA) Project Donor
Post:
Just a single datapoint here. I thought the sbc concept was
interesting. (Not using rasbperry pi for seti: have a couple
doing record-keeping/control though).

I acquired an odroid-xu4 (16GiB eMMC disk, 4 core,2GiB ram, 2GhZ clock) and
finished the setup a day or so ago.
Preliminary results suggest that it will accumulate about
700-900 cobblestones per day total
across the 4 cores. One built-in 40mm fan
cooling the cpu.

Preliminary results indicate that Ubuntu-Mate 16.04
sees the 4 cores as 8 (some threading bios
setting) but (again, preliminary) it appears that
running more than 4 seti threads is not helpful.

A single core takes about 8 hours for each current
task it gets.

Power use is under 40 watts at 5V.

I had been running an old HP laptop (68 watts, 1 AMD core)
as an experiment (it took 4-5 hours per task)
but it was big/heavy at 17-inches and its screen and keyboard
were failing so I've junked it.
20) Message boards : Number crunching : SETI/BOINC Milestones [ v2.0 ] - XXIX (Message 1863777)
Posted 26 Apr 2017 by Profile David Anderson (not *that* DA) Project Donor
Post:
By the time you see this I'll have 40,000,000 for Seti.
Happy Computing, all.

At this time of year computing all powered by sunshine!


Next 20


 
©2018 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.