Based on the posting in the "News" area from Eric, it appears there is a problem with the Linux64/Nvidia app. The short answers for when it might be available are "wait" and "it will be ready when it is ready" but does anyone know if it is the result of a major or minor setback and if there is an estimate on when it will be available? Inquiring minds would like to know if we need to brave the cold and fetch more wood for the stove :).

No just logistics of me getting a suitable build to Eric, and then him being happy with it, enough to push out. For Cuda MB, Stock support of Both Linux and Mac is a new thing with v8, so just procedural and practical slowness, rather than technical difficulty. (probably finishing some documentation and getting prelim builds to Eric before Tuesday's outage). Once ín the system'I'd expect both Linux and Mac future release for Cuda apps to be more or less in lockstep, though number of builds would initially be minimal, so as to find any lurking issues. Not sure whetehr he'd want to beta first, but probably IMO, since there is increased precision in v8 processing.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Thanks for taking time out of your busy day to bring me up to speed.

Thanks for taking time out of your busy day to bring me up to speed.

Lol, no worries. Actually just after 6am Saturday morning here, and finally got some good sleep yesterday, so hoping the smooth sailing continues.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

No just logistics of me getting a suitable build to Eric, and then him being happy with it, enough to push out. For Cuda MB, Stock support of Both Linux and Mac is a new thing with v8, so just procedural and practical slowness, rather than technical difficulty. (probably finishing some documentation and getting prelim builds to Eric before Tuesday's outage). Once ín the system'I'd expect both Linux and Mac future release for Cuda apps to be more or less in lockstep, though number of builds would initially be minimal, so as to find any lurking issues. Not sure whetehr he'd want to beta first, but probably IMO, since there is increased precision in v8 processing.

Any chance of an update?

Just for grins I ran through 181 WUs on the beta site a couple of days ago using r3316 on a GTX 750Ti with 2 failures. They happened within a few minutes of each other and they appear to have been caused by a “segmentation violation". Not sure if that is of any help or not.

Yeah, have been dealing with stuff here (including a random acqaintance funeral). Will probably be sorting out things this week, as long as no more randomness , lol.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Sorry to hear about your problems, despite what some may say family and friends come first Jason - take your time.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

It's often painful when life gets in the way :-(
Hope you managed to get back into the groove...
Do you have any more news on progress of Linux v8 cuda?
We've got machines twiddling their virtual thumbs!

Yeah, watching the test machine (my Linux Host) for a bit before forwarding at least one Linux x64 build to Eric. Seems OK, with the majority of inconclusives seeming explainable, leaving inconclusive to pending ratio better than the 5% target.

Had been further tied up unexpectedly, which delayed this and the Mac builds being packaged up for Eric with suitable documentation. Since there are still some unknowns for the readmes for both platforms, I'll probably field what I can in the morning via my website downloads. That way I can cheat by letting the community tell me what needs to go in all the question marks in the readmes, lol.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Tut, Tut - cheating again ;-)

I'm sure the relevant communities will be delighted with your efforts Jason

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Thanks Jason, nice to know that you're still working on it - looking forward to getting crunching again!

bump... :-)

Been running well, all packaged up (with template readme) and looking for a chance to upload. Not sure when Eric will get a chance to look at it, but I'll post a direct link here, before I have to archive all the irrelevant apps on my website.

Since this is the worst/slowest/most-frustrating/least-fun part of development, this'll be automated later in the year, down to build, test, document update, packaging, deployment, advisory tweets/posts, email to the project, and website download update.

Still grinding it old-school at the moment :D

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

As per the other thread. I can't manage your (owned) files at Lunatics, but I can upload new ones - if I know where to find them.

As per the other thread. I can't manage your (owned) files at Lunatics, but I can upload new ones - if I know where to find them.

Sorting that out at the moment (with beer). One day I'll make use of the database facilities I installed on my site and never used, lol.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

And it's up for Linux, Note that the readme has a lot of unknowns, with ??? placeholders. Any community assistance in working out how to fill in those blanks would be greatly appreciated ( e.g. system requirements for the build )

http://jgopt.org/download.html

would probably include other versions as development/optimisations progress. I may or may not extend to 32 bit and deprecated hardware on this platform. Depends largely on community demand, and practicalities with systems here, as building from source on Linux is relatively straightforward (compared to Windows and Mac)

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Thanks Jason,

Have tried to install it, but need a working xml spec to add to app_info.xml

I made some guesses, but boinc just deletes the app after restarting, even if owned by root.

I have no idea what version_num or plan_class should or, or even if coproc/type is correct.

    <app>
      <name>setiathome_v8</name>
    </app>
    <file_info>
      <name>setiathome_x41zi_x86_64-pc-linux-gnu_cuda60</name>
      <executable/>
    </file_info>
    <app_version>
        <app_name>setiathome_v8</app_name>
        <version_num>800</version_num>
        <platform>x86_64-pc-linux-gnu</platform>
        <plan_class>cuda_fermi</plan_class>
        <avg_ncpus>0.05</avg_ncpus>
        <max_ncpus>1.0</max_ncpus>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>setiathome_x41zi_x86_64-pc-linux-gnu_cuda60</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>libcudart.so.6.0</file_name>
        </file_ref>
        <file_ref>
            <file_name>libcufft.so.6.0</file_name>
        </file_ref>
    </app_version>

(I also have another problem in that a month ago this machine started resetting without warning after a few minutes to a few hours of running boinc, and even resets during the boot up. Happens with cpu apps or large videos - have swapped mainboards with another machine, peripherals and ram, and still happens. Only constants were the video card GTX760 and PSU which I thoroughly cleaned. Hope it's not the GPU - next thing to swap and test.)

Hi!

Works for me.
Not with old slackware (glibc is too old, works with others),
nor with old GTX 275 card (driver 340 is latest there).



under

   <app>
      <name>setiathome_v8</name>
    </app>

After CPU MB I put:

  <file_info>
    <name>setiathome_x41zi_x86_64-pc-linux-gnu_cuda60</name>
    <executable/>
  </file_info>
  <file_info>
    <name>libcudart.so.6.0</name>
    <executable/>
  </file_info>
  <file_info>
    <name>libcufft.so.6.0</name>
    <executable/>
  </file_info>
  <app_version>
    <app_name>setiathome_v8</app_name>
    <version_num>803</version_num>
    <platform>x86_64-pc-linux-gnu</platform>
    <plan_class>cuda60</plan_class>
    <avg_ncpus>0.1</avg_ncpus>
    <max_ncpus>1.0</max_ncpus>
    <coproc>
      <type>CUDA</type>
      <count>0.33</count>
    </coproc>
    <file_ref>
      <file_name>setiathome_x41zi_x86_64-pc-linux-gnu_cuda60</file_name>
      <main_program/>
    </file_ref>
    <file_ref>
      <file_name>libcudart.so.6.0</file_name>
    </file_ref>
    <file_ref>
      <file_name>libcufft.so.6.0</file_name>
    </file_ref>
  </app_version>

file_info is differet, Version 8.03 help to distinguish, hopefully.
It is just v7 that works a bit eddited,

Thanks Jason,

Have tried to install it, but need a working xml spec to add to app_info.xml

I made some guesses, but boinc just deletes the app after restarting, even if owned by root.

I have no idea what version_num or plan_class should or, or even if coproc/type is correct.

    <app>
      <name>setiathome_v8</name>
    </app>
    <file_info>
      <name>setiathome_x41zi_x86_64-pc-linux-gnu_cuda60</name>
      <executable/>
    </file_info>
    <app_version>
        <app_name>setiathome_v8</app_name>
        <version_num>800</version_num>
        <platform>x86_64-pc-linux-gnu</platform>
        <plan_class>cuda_fermi</plan_class>
        <avg_ncpus>0.05</avg_ncpus>
        <max_ncpus>1.0</max_ncpus>
        <coproc>
            <type>CUDA</type>
            <count>1</count>
        </coproc>
        <file_ref>
            <file_name>setiathome_x41zi_x86_64-pc-linux-gnu_cuda60</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>libcudart.so.6.0</file_name>
        </file_ref>
        <file_ref>
            <file_name>libcufft.so.6.0</file_name>
        </file_ref>
    </app_version>

(I also have another problem in that a month ago this machine started resetting without warning after a few minutes to a few hours of running boinc, and even resets during the boot up. Happens with cpu apps or large videos - have swapped mainboards with another machine, peripherals and ram, and still happens. Only constants were the video card GTX760 and PSU which I thoroughly cleaned. Hope it's not the GPU - next thing to swap and test.)

BR
s52d

Thanks for the feedback,
Yeah basic app_info.xml like the one shown below should work fine, changing the <count> value as appropriate. Sample might go best in the readme (?), given it'll need to be the portion only related the Cuda MB, whereas CPU and AP app sectionss will be different. Perhaps I'll script something and make aistubs similar to the way the Windows installer works (?) Still undecided on that.

I'll consider doing an earlier Cuda version to support the older GPUs, and kernels as well, once I have Windows, Mac and Linux in lockstep. What I end up making will depend on demand, priorities and available time, so in lot's of really strange cases compiling from source would be a better option.

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Hvala!

Got it working eventually - doing my nut because I had this:

<file_info>
  <file_name>libcudart.so.6.0</file_name>
  <executable/>
</file_info>

<file_info> expects "name", but <file_ref> expects "file_name":

<file_ref>
  <file_name>libcudart.so.6.0</file_name>
</file_ref>

Don't ya just love consistency?

Yep, the video card was also a problem :( Replaced it with a smaller one and the reboots have stopped. Really annoying.