Posts by Jeff Buck

1) Message boards : Number crunching : Completed WUs going nowhere? (Message 1884832)
Posted 3 days ago by Profile Jeff Buck
Post:
There is a big list of "In Progress" tasks listed here on the website ( https://setiathome.berkeley.edu/results.php?hostid=8299899 ). Some of them are timing out now. But on the computer, there are currently only 7 tasks listed on BOINC Manager. 2 are in progress, 5 are waiting to run.

I think the "In Progress" WUs that don't show up on the BOINC Manager interface are in the projects/setiathome.berkeley.edu directory on the computer. Is there a way to get BOINC to see them again? Maybe some .xml file can be edited by hand to add them into the list again? Is there a way to cancel those WUs so that someone else can pick them up, instead of waiting for them to time out?
You can't cancel them, but there is a way to recover "lost" tasks (or "ghosts") so they can still be run on your host . See Message 1865033 for step-by-step instructions.
2) Message boards : Number crunching : NVIDIA GPU Fan Control using GUI in Linux (Message 1884603)
Posted 4 days ago by Profile Jeff Buck
Post:
Jeff, followed the readme to delete the previous gui file and removed the cfg file from the archive and copied everything over to desktop folder. Stopped the app and restarted and up comes v0.4.1 and everything running as it should. So Python recompiled the gui file as you said it would. Good Job! Thanks
You're welcome! And thank you for reporting your observations.
3) Message boards : Number crunching : NVIDIA GPU Fan Control using GUI in Linux (Message 1884536)
Posted 4 days ago by Profile Jeff Buck
Post:
I take that there is a further revision to the 0.4.1 release from your last post.
Nope, v0.4.1 is the latest (for now). The two minor changes I mentioned are included in that release.
4) Message boards : Number crunching : NVIDIA GPU Fan Control using GUI in Linux (Message 1884521)
Posted 4 days ago by Profile Jeff Buck
Post:
. . The long and the short of it is that I have not gotten around to trying it out, I am still running with the original terminal script-based version which is doing the trick. I did download the files but I have not d/l'd the other app you say is necessary to run it (which I cannot now remember now, was it Python?). When I resolve my other issues I will jump back in on that one. I am sorry if I let you down ... :(

Stephen

:(
No worries, and certainly no letdown, Stephen. I wrote the thing purely for my own benefit, so if anyone else finds it useful, that's just a bonus!

As Keith noted, Python generally gets installed automatically as part of most flavors of Linux. However, you probably will need to add the "python-numpy" package. Keith also found that his setup was missing "python-qt4", although that seemed to come standard with mine. Check with Package Manager for both of those.

@Keith
The v0.4.1 distribution just has minor changes. If you didn't see the caption alignment problem before, you shouldn't see anything different in that area. (The "Fan Control:" text was overlaying the "Off" button on Mageia 6.) The "Revert" button is primarily useful if you're playing around with fine-tuning your settings but want a quick way to jump back to the last settings that you saved.
5) Message boards : Number crunching : NVIDIA GPU Fan Control using GUI in Linux (Message 1884361)
Posted 5 days ago by Profile Jeff Buck
Post:
I've uploaded a new version (v0.4.1) with just a couple minor changes, for anyone still interested in trying this out.

W3Perl identified a text alignment issue for one of the captions when the app was run on Mageia 6 systems. That has been resolved. He also requested a "Revert" button, to revert to the last saved settings after trying out one or more new settings. That button has been added. (It will only appear after at least one setting has been changed subsequent to the last save.)

NOTE: The distribution zip file no longer includes the compiled GUI file, gpufancnvgui.pyc, just on the off-chance that there might be any conflict when a file compiled on my Ubuntu 14.04 system runs under another Linux OS. A new gpufancnvgui.pyc should be created the first time the app is run. For current users of an earlier version, it may be advisable to delete any existing gpufancnvgui.pyc that you have, although Python should recognize the older datestamp and recompile automatically. A compiled file isn't necessary for the app to run, though it theoretically improves load time after the first execution, for whatever that's worth. :^)

EDIT: The download link remains the same as in my first post in the thread.
6) Message boards : Number crunching : Panic Mode On (107) Server Problems? (Message 1883899)
Posted 7 days ago by Profile Jeff Buck
Post:
Just took a quick look at my 3 big boxes again and the work buffers are now at 100%, 91%, and 100% of capacity (for the moment, anyway).
7) Message boards : Number crunching : Panic Mode On (107) Server Problems? (Message 1883876)
Posted 7 days ago by Profile Jeff Buck
Post:
On another idea, can someone post their minimal cc_config.xml for a machine running the special app please.
Here's what I've got on my #1 cruncher:

<cc_config>
   <log_flags>
      <cpu_sched>1</cpu_sched>
  </log_flags>
   <options>
      <use_all_gpus>1</use_all_gpus>
      <no_priority_change>1</no_priority_change>
   </options>
</cc_config>

EDIT: ...and #2 has:
<cc_config>
   <log_flags>
       <cpu_sched>1</cpu_sched>
   </log_flags>
   <options>
       <max_event_log_lines>10000</max_event_log_lines>
       <use_all_gpus>1</use_all_gpus>
   </options>
</cc_config>

EDIT2: ...and to round it off, #3 has:
<cc_config>
   <log_flags>
       <cpu_sched>1</cpu_sched>
   </log_flags>
   <options>
       <use_all_gpus>1</use_all_gpus>
   </options>
</cc_config>

All in all, pretty basic stuff only.
8) Message boards : Number crunching : Panic Mode On (107) Server Problems? (Message 1883868)
Posted 7 days ago by Profile Jeff Buck
Post:
Thanks for the comments, Z. Not good to hear when the WOW contest starts in 10 hours. I have had this issue on the Windows machines last week for a while but they have calmed down over the weekend and are full up. Just having the problem currently on the Linux box.
The work buffers on my 3 Linux boxes have been fluctuating this morning, but none have gotten below about 60% full. A couple that had dropped a good bit just recently got transfusions of about 80-100 tasks and the 3 boxes currently stand at 92%, 91%, and 94% full. (They normally stay right at 100% when there aren't a lot of Arecibo VLARs in the feeder.) No special intervention has been required here.
9) Message boards : Number crunching : Setting up a Linux machine to crunch CUDA80 for Windows users (Message 1883468)
Posted 9 days ago by Profile Jeff Buck
Post:
Ah....a dual GPU card. That didn't even occur to me. Perhaps because I've never breathed the rarified atmosphere up there in Titan land. ;^)

Glad to hear you got it working!
10) Message boards : Number crunching : Panic Mode On (107) Server Problems? (Message 1883463)
Posted 9 days ago by Profile Jeff Buck
Post:
The 100 WUs per CPU/GPU limit is a Seti one.
And Petri simply appears to have added a multiplier to the BOINC client's GPU count to make it think he has 4 times as many GPUs when it sends a scheduler request. But each (real or imagined) still only gets 100 tasks max per the project's limit.
11) Message boards : Number crunching : Panic Mode On (107) Server Problems? (Message 1883384)
Posted 9 days ago by Profile Jeff Buck
Post:
I, too, have tried to avoid "jinxing" myself by commenting on this issue, as I've never had a problem keeping the work buffers full (or close to it) except when the feeder was clogged with Arecibo VLARs. However, yesterday my #1 cruncher actually ran out of GPU work late in the afternoon. Fortunately, it reached that point about 5 minutes before its scheduled weekday afternoon shutdown (avoiding peak period electric rates). When it came back up 5 hours later, it filled the buffer in 2 requests, 176 tasks in the first and 127 in the second. I tend to believe that Arecibo VLARs were the primary culprit again yesterday, but then that probably wouldn't explain the responses that said the limit of tasks in progress had been reached when, in fact, the work buffer was steadily shrinking to zero.

Since refraining from comment ultimately didn't avoid the jinx, I'll go ahead and mention the following, for what it's worth. I haven't touched my settings in a long, long time, probably a couple years. My application preferences are "Yes, Yes, No" and my work buffer is 1.8 days plus 0.2 days. Also, assuming that the project shares might somehow play into the scheduler's decision-making, I have no active backup projects that might possibly muddy the waters.

That's about it, for whatever bit of insight it might provide.
12) Message boards : Number crunching : Setting up a Linux machine to crunch CUDA80 for Windows users (Message 1883382)
Posted 9 days ago by Profile Jeff Buck
Post:
You may need to include 3 more Monitor sections, since the Screen sections reference 4 monitors. That's the way mine was generated, even though I only have the one monitor. I'm also wondering about the "0 0" at the end of your Screen 0 "Screen0" 0 0 line. Were those added intentionally, or just some sort of artifact?

(Please note that I don't actually have much expertise in this area. I'm just making observations from what catches my eye.)
13) Message boards : Number crunching : Setting up a Linux machine to crunch CUDA80 for Windows users (Message 1883274)
Posted 10 days ago by Profile Jeff Buck
Post:
I don't know that I have any specific suggestions, but just for comparison, here's what the complete xorg.conf file looks like on one of my Linux boxes that has never had any problems with Coolbits. Perhaps you can spot something significant.

# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 375.39  (buildmeister@swio-display-x86-rhel47-09)  Tue Jan 31 20:47:44 PST 2017


Section "ServerLayout"
    Identifier     "Layout0"
    Screen      0  "Screen0"
    Screen      1  "Screen1" RightOf "Screen0"
    Screen      2  "Screen2" RightOf "Screen1"
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor2"
    VendorName     "Unknown"
    ModelName      "Unknown"
    HorizSync       28.0 - 33.0
    VertRefresh     43.0 - 72.0
    Option         "DPMS"
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 780"
    BusID          "PCI:1:0:0"
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 670"
    BusID          "PCI:2:0:0"
EndSection

Section "Device"
    Identifier     "Device2"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce GTX 960"
    BusID          "PCI:6:0:0"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "ThermalConfigurationCheck" "True"
    Option         "Coolbits" "28"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "ThermalConfigurationCheck" "True"
    Option         "Coolbits" "28"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen2"
    Device         "Device2"
    Monitor        "Monitor2"
    DefaultDepth    24
    Option         "ThermalConfigurationCheck" "True"
    Option         "Coolbits" "28"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

I did notice one thing, probably a typo, in your Screen0 section, where you have Monitor1 specified instead of Monitor0. Maybe that's significant, or maybe not.

EDIT: Apparently, the system isn't picky about the BoardNames. I just noticed that the file still shows a GTX 780 and GTX 670, both of which were replaced by GTX 980s several weeks ago, without any effect on the saved configuration.
14) Message boards : Number crunching : Setting up a Linux machine to crunch CUDA80 for Windows users (Message 1883035)
Posted 11 days ago by Profile Jeff Buck
Post:
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce GTX TITAN Z"
BusID "PCI:3:0:0"
Option "Cool-bits" "4"
EndSection
I believe the "Coolbits" (no hyphen) entries should be in the "Screen" sections, not the "Device" sections. At least that's the way it's set up on my Ubuntu 14.04 machines.

EDIT: Which I now see is pretty much what TBar said in his reply.
15) Message boards : Number crunching : NVIDIA GPU Fan Control using GUI in Linux (Message 1882538)
Posted 15 days ago by Profile Jeff Buck
Post:
Oh, that's interesting. Yeah, must be something external because the program itself has no "start minimized" option. I thought about building in such an option, but I'm concerned that it might be too easy to mistake a startup failure for a successful, but minimized, launch. That happens to me periodically with Precision X in Windows, when Windows apparently gets too busy at startup and simply bypasses some of the things it's supposed to start. Since I don't often keep a close eye on my crunch-only machines when they restart each weekday evening, it's usually a disturbing surprise the next day to find that the GPUs have been running at 80C or so all night! :^(
16) Message boards : Number crunching : Panic Mode On (107) Server Problems? (Message 1882534)
Posted 15 days ago by Profile Jeff Buck
Post:

After an outage I will often have me cached filled in one request. Along the lines of:
01-Aug-2017 20:09:22 [SETI@home] Requesting new tasks for CPU
01-Aug-2017 20:09:24 [SETI@home] Scheduler request completed: got 100 new tasks

Just rub it in Hal ...... just rub it in. ;-{
Ooh, this looks like fun! Can I get in on it?

01-Aug-2017 21:11:53 [SETI@home] Reporting 311 completed tasks
01-Aug-2017 21:11:53 [SETI@home] Requesting new tasks for CPU and NVIDIA
01-Aug-2017 21:12:19 [SETI@home] Scheduler request completed: got 187 new tasks
17) Message boards : Number crunching : NVIDIA GPU Fan Control using GUI in Linux (Message 1882530)
Posted 15 days ago by Profile Jeff Buck
Post:
OK, just entering gpufancnv.pyw in terminal just got me "Command not found"

Entering ./gpufancnv.pyw executed the expected script output in the terminal window AND opened up the GUI control window.
Fantastic! That's as it should be, then.

When entering the command for the app in Startup Applications, just use the full path name, without "python". For instance, on this machine mine is entered just as /home/jeff/Programs/gpufancnv/gpufancnv.pyw. (I created the "Programs" directory just to keep some things separate.) It looks like yours would probably be /home/keith//Desktop/gpufancnv/gpufancnv.pyw
18) Message boards : Number crunching : NVIDIA GPU Fan Control using GUI in Linux (Message 1882522)
Posted 15 days ago by Profile Jeff Buck
Post:
I just re-verified that it works okay from the Terminal on all 3 of my Linux boxes, so perhaps there's an OS-specific issue here. Bur first, try launching it without "python" at the beginning, just entering gpufancnv.pyw (or, perhaps, ./gpufancnv.pyw).
19) Message boards : Number crunching : NVIDIA GPU Fan Control using GUI in Linux (Message 1882516)
Posted 15 days ago by Profile Jeff Buck
Post:
When it launches successfully, you should always see the app's window appear, although it could be hidden behind other windows if you have multiple applications launching at startup.
20) Message boards : Number crunching : NVIDIA GPU Fan Control using GUI in Linux (Message 1882505)
Posted 15 days ago by Profile Jeff Buck
Post:
Just on the off chance that there's a silent user out there who's trying out the app, but has discovered (or soon will) that it wouldn't launch automatically from "Startup Applications" on a reboot, version 0.3 is now available, which should fix that shortcoming. The D/L link remains the same.


Next 20


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