Posts by wobo

1) Message boards : Number crunching : Multicore CPU crunching only 1 WU at a time (Message 980441)
Posted 18 Mar 2010 by Profile wobo
Post:
No, sorry, forgot to add: settings on my computer care for 5 days worth of WUs, so I have pretty much enough to work on.

EDIT: I just looked and now I have 4 active WUs again! Hmm, problem vanished how it has come, all of a sudden with no explanation.

Problem seems to be solved, although I'd like to know what it was caused by.
2) Message boards : Number crunching : Multicore CPU crunching only 1 WU at a time (Message 980410)
Posted 18 Mar 2010 by Profile wobo
Post:
Subject tells the problem, here are the details:
Windows 7, SETI@HOME, CPU is i7, GPU is Nvidia GT230

Settings are to use 75% of the CPUs, and graphics chip when not in use. Until recently the machine crunched 4 WUs at a time (3 with CPU, 1 with GPU). Without changing anything, no reboot, no Windows crash, suddenly the CPU dropped crunching. Now I see only one WU active, the one being crunched by the GPU. Whatever I do in settings, nothing brings back the CPU to work.

There's no hardware problem involved, temperature and other parameters are all as they should be.

I checked the latest 2 pages of this forum without finding a related thread, of course I only scanned the thread titles. Tell me if you need more information.
3) Message boards : Number crunching : No WUs for GPU? (Message 957131)
Posted 18 Dec 2009 by Profile wobo
Post:
The stock Seti CUDA application is for Windows only.

Ah, I did not know that, /cuda.php told me: "CUDA apps are supported only on Windows and Linux"
But reading a bit further on in this forum I see that I can't run CPU and GPU on the SETI@Home at the same time anyway, so the question is obsolete.

Thx Jord & Claggy for your hints!
4) Message boards : Number crunching : No WUs for GPU? (Message 957089)
Posted 18 Dec 2009 by Profile wobo
Post:
I restarted with SETI late last month with a brandnew 64-Bit machine running Linux.
1. I read the FAQ, pointing me to the page about running SETI@Home on my Nvidia GPU.
2. I checked the Nvidia page about my graphics chip - is supported.
I have the latest driver installed. Wenn I start the BOINC client it lists the GPU as:
NVIDIA GPU 0: GeForce GT 230 (driver version unknown, CUDA version 2020, compute capability 1.1, 1536MB, 240 GFLOPS peak)

But from the start 3 weeks ago I never received any WUs for the GPU:
SETI@home	Requesting new tasks for GPU
SETI@home	Scheduler request completed: got 0 new tasks
SETI@home	Message from server: No work sent

What am I missing?
5) Message boards : Number crunching : Boinc stopped in the middle of a WU (Message 263079)
Posted 16 Mar 2006 by Profile wobo
Post:
I just experienced that an old myth is really true! If you have problems with Windows or any app under Windows - restart the computer!

I should have done that earlier but I'm no experienced Windows user so I thought this was only a myth. But it works!

wobo
6) Message boards : Number crunching : Boinc stopped in the middle of a WU (Message 262947)
Posted 16 Mar 2006 by Profile wobo
Post:
Running 5.2.13 under Windows XP

All of a sudden in the middle of work the cruncher stopped working. Last entrances in the log were:

2006-03-16 17:58:37 [SETI@home] Starting result 03my03aa.28528.32448.997154.1.243_2 using setiathome version 418
2006-03-16 17:58:37 [SETI@home] Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2006-03-16 17:58:37 [SETI@home] Reason: To fetch work
2006-03-16 17:58:37 [SETI@home] Requesting 900 seconds of new work
2006-03-16 17:58:39 [SETI@home] Started upload of 03my03aa.28528.32097.298580.1.137_2_0
2006-03-16 17:58:42 [SETI@home] Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
2006-03-16 17:58:43 [SETI@home] Finished upload of 03my03aa.28528.32097.298580.1.137_2_0
2006-03-16 17:58:43 [SETI@home] Throughput 9692 bytes/sec
2006-03-16 17:58:44 [SETI@home] Started download of 19ja03ab.4934.13520.903410.1.89
2006-03-16 17:58:48 [SETI@home] Finished download of 19ja03ab.4934.13520.903410.1.89
2006-03-16 17:58:48 [SETI@home] Throughput 137198 bytes/sec
2006-03-16 17:58:49 [---] request_reschedule_cpus: files downloaded
2006-03-16 18:20:25 [---] request_reschedule_cpus: project op
2006-03-16 18:25:02 [---] request_reschedule_cpus: process exited

Last WU was started at 17:58:37 and now it is listed in the work tab with 38% and 'Active'. (local time at the time of writing: 20:32)

where do I go from there?

wobo
7) Message boards : Number crunching : Client stops and never starts again (Message 259207)
Posted 8 Mar 2006 by Profile wobo
Post:
Solution:

1. I detached the project with
./boinc -detach_project http://setiathome.berkeley.edu/


This caused a seg violation:
SIGSEGV: segmentation violation*** glibc detected *** malloc(): memory corruption: 0x082a5e28 ***
SIGABRT: abort called

so I had to kill the process with 'kill -9 11606'

2. I re-attached with
./boinc -attach_project http://setiathome.berkeley.edu/ <my_key>

and it started with a benchmark and then started downloading WUs and is happily crunching away now. :)

wobo
8) Message boards : Number crunching : Client stops and never starts again (Message 259179)
Posted 8 Mar 2006 by Profile wobo
Post:
Thanks.

Yes, it could have been caused by the trux cruncher. But this is easily put away with. I just remove the cruncher and the app.xml of the cruncher and copy the original cruncher file back to the project directory. No need to re-attach.

Alas, that was not the solution to the problem at hand.

BTW: I'm using Linux, no exe involved :)

wobo
9) Message boards : Number crunching : Client stops and never starts again (Message 259078)
Posted 8 Mar 2006 by Profile wobo
Post:
Yesterday my client (on linux) stopped in the middle of work. Actually he stopped crunching, did a new benchmark and then stopped with the message:
cpu: process exited

or similar - can't remember the exact message.

I restarted the client and got this:

[wobo@localhost BOINC]$ ./boinc
11:41:17 [---] Starting BOINC client version 5.3.12.tx36 for i686-pc-linux-gnu
11:41:17 [---] libcurl/7.15.1 OpenSSL/0.9.7a zlib/1.2.1.2 libidn/0.5.6
11:41:17 [---] Data directory: /home/wobo/BOINC
11:41:17 [SETI@home] Found app_info.xml; using anonymous platform
11:41:17 [---] Processor: 1 GenuineIntel Intel(R) Pentium(R) 4 CPU 2.40GHz
11:41:17 [---] Memory: 503.36 MB physical, 1.56 GB virtual
11:41:17 [---] Disk: 6.12 GB total, 1.89 GB free
11:41:17 [SETI@home] Computer ID: 2110720; location: home; project prefs: default
11:41:17 [---] General prefs: from SETI@home (last modified 2005-06-08 12:52:03)
11:41:17 [---] General prefs: using separate prefs for home
11:41:17 [---] Remote control not allowed
11:41:17 [---] Listening on port 31416


That's all. It's sitting right there and does nothing. A search for the process with 'ps aux' revealed that it is sleeping and waiting for an event to wake it up (S+).

What did I try?

Looked for WUs: I did not run out of WUs - otherwise the client would try to download.

Looked for the internet connection: My internet connection goes through a router and is permanent. I have another machine with boinc running, no problems there.

Looked for changes in the machine's configurations: None. The client stopped to work while I was not at home and not doing anything with that machine.

Any idea?
10) Questions and Answers : Windows : SETI/BOINC on Windows = SLOW! (Message 242168)
Posted 4 Feb 2006 by Profile wobo
Post:
I'll give the optimized section a try, although it's just for a couple of weeks.


Just as a proof of a good advice i received:
I went to the address given, downloaded and installed the oprimized exe.
Before: >7 hours for one WU
After: 1:20 for a WU of similar size.

This is really amazing! Under Linux the optimized naparst client gave an advantage of 20-30% compared to the generic client. But from 7:00 down to 1:20 is an amazing leap.

Thx again, this way my fellow comrades of the mandrivauser.de team will not be too angry at me! :)

wobo
11) Questions and Answers : Windows : SETI/BOINC on Windows = SLOW! (Message 242116)
Posted 4 Feb 2006 by Profile wobo
Post:
I'll give the optimized section a try, although it's just for a couple of weeks.

Aye... hopefully earlier. As Seti Enhanced will soon be taking over. :)


Hehehe, actually I meant that I have to run this machine on Windows just for a couple of weeks and then return back to Linux (hopefully not spoiled) :)

wobo
12) Questions and Answers : Windows : SETI/BOINC on Windows = SLOW! (Message 241892)
Posted 4 Feb 2006 by Profile wobo
Post:
Look in the Number Crunching forums for any thread with "optimized client" or "optimized application" in the name. You'll quickly find out why it is that the Windows Seti_4.18.exe app is so slow: It's not compiled with optimization to your specific processor.

The standard application is slow.
Catch a quicker app at Crunch3r's site. Full install steps are available.


WIll do, thx. I'm using an optimized client on Linux as well because that's my turf and I know my where-abouts. In Windows I feel a bit lost and I have to struggle to find my way... a lot of things I have to read up in the help section. :(

I'll give the optimized section a try, although it's just for a couple of weeks.

wobo
13) Questions and Answers : Windows : SETI/BOINC on Windows = SLOW! (Message 241854)
Posted 4 Feb 2006 by Profile wobo
Post:
... and with SLOW! I mean, REALLY slow. Normally I work with Linux and the machine in question does a WU in 1:20:00 (average). Now I have to use Windows for a special project and I thought, well, let BOINC run on Windows for a change.

Installed, attached, go.
The first WU was done after 7:24:03, the second WU is in progress, showing 4:54:00 CPU useage and 79% of the work done. On the same machine where it crunches a WU in 80 minutes under Linux.

I know that Linux is far better than Windows (sorry!) but I did not know that the difference is so great! No, only kidding! There must be something I haven't found yet which slows the work down.

wobo
14) Message boards : Number crunching : Crunching stopped due to lack of WUs (Message 159080)
Posted 29 Aug 2005 by Profile wobo
Post:
Thanks, folk. All machines have a permanent uplink (dsl) so I'll just let it be.
The suggestion to attach to other projects is a sensible suggestion, no doubt. But my only real interest lies in seti, so it would make no sense to attach to a different project just because the seti serrver is gone fishin'

wobo
15) Message boards : Number crunching : Crunching stopped due to lack of WUs (Message 159060)
Posted 29 Aug 2005 by Profile wobo
Post:
Running 3 machines with seti@home. Permanent net connection. Set to 5 days contact cycle.

Now due to unreachable server (since Aug 23) all 3 machines have stopped crunching because there are no new WUs.

Q: Shall I just keep the client running and as soon as the server is reachable again the client will pick up new WUs and go on crunching? Or do I have to do something like detaching from the project and re-attaching?

wobo
16) Questions and Answers : Unix/Linux : Slow processing of WUs on FreeBSD (Message 123856)
Posted 15 Jun 2005 by Profile wobo
Post:
Found the problem. My user name was not associated with the wheel group.

That's what I wrote twice. You can always trust me up to a financial worth of 5.00 USD. :)

wobo
17) Questions and Answers : Unix/Linux : Slow processing of WUs on FreeBSD (Message 121538)
Posted 10 Jun 2005 by Profile wobo
Post:
I'm not sure about the 'wheel' group.

But I am. To use 'su' the user must be a member of the group 'wheel'

Is there a way to boot FreeBSD and prevent KDE from starting?

Hmm, the normal way to start IS without KDE (or any gui, that is). I guess you installed it with booting right into the gui. Try to kill the X server (Ctrl+Backspace).

Where did you get the FreeBSD port of BOINC?

Through the ports collection.

Advices:
1. Grab the online documentation of FreeBSD
2. Read about the basics (like being able to 'su')
3. Read about the ports collection
4. Read about using sysinstall to install pre-packaged software
5. Read
6. Read
7. Read
etcetera ad infinitum

wobo
18) Questions and Answers : Unix/Linux : Slow processing of WUs on FreeBSD (Message 121165)
Posted 9 Jun 2005 by Profile wobo
Post:
I would assume that since BOINC is written for Linux/x86 that on your machine it's running through the emulator.


No, I have the ported BOINC client and cruncher installed, it's both ported to FreeBSD.

I'm running KDE, which I really like. KDE refuses to give me administrative rights and hence I cannot install anything, yet. I can't even get Firefox installed.

It's not KDE which gives you admin (aka root) privileges, it's the system. Logged in as user you have to type in 'su' and give the root password. If you are not allowed to do that, remember that your user must be in the group 'wheel' to do so.

wobo
19) Questions and Answers : Unix/Linux : Slow processing of WUs on FreeBSD (Message 120553)
Posted 8 Jun 2005 by Profile wobo
Post:
Lately I changed from Linux to FreeBSD and installed the proper BOINC client and number cruncher. It works and runs without problems on my 24/7 desktop machine.

BUT:

It's slow, compared to the speed of the same machine under Linux. With Linux I nedded around 4 hours for 1 WU. Despite the fact that the benchmark under FreeBSD returned higher results than under Linux now the machine needs nearly 8 hours for 1 WU!

I'm using the same preferences I used under Linux, it's the same computer, nothing has changed except the OS. Is there any option I have to set in FreeBSD which is not needed in Linux?

wobo
20) Questions and Answers : Unix/Linux : Message from server: platform 'i386-portbld-freebsd5.4' not found (Message 116172)
Posted 29 May 2005 by Profile wobo
Post:
you do not seem to have the appropriate app_info.xml


That was one part of the answer, let's say: it was a symtom but not the cause.

Iwrote that I use FreeBSD. What I did not know: in FreeBSD the client and the actual number-crunching program are 2 separate software packages. You have to install the client first and then the work-tool.

I did that (after a cvsup of my ports collection) and now it's running and crunching numbers.

wobo


Next 20


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