The Nov 5 app_info.xml Nautilus posted had (at line 51 of app_info.xml)
a </app_version> which appears to not belong to any previous
<app_version>.

I saved the posted app_info text to Test.txt and used Find.

The results:

find "app_version" Test.txt

---------- TEST.TXT
    <app_version>
    </app_version>
    <app_version>
    </app_version>
    <app_version>
    </app_version>
    <app_version>
    </app_version>
    <app_version>
    </app_version>
    <app_version>
    </app_version>
    <app_version>
    </app_version>    
    <app_version>
    </app_version>
    <app_version>
    </app_version>
    <app_version>
    </app_version>

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

... every time I attempt to install the optimized apps I get a BOINC meltdown.

;) Yes, it looks like this

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

probably the same thing I posted on the linux forums. I've installed Ubuntu and BOINC on my 64 bit PC and every time I attempt to install the optimized apps I get a BOINC meltdown. The Boinc manager can't connect to the host process, then I lose all my WU's and eventually I just have to uninstall BOINC and reinstall.

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

The Nov 5 app_info.xml Nautilus posted had (at line 51 of app_info.xml)
a </app_version> which appears to not belong to any previous
<app_version>.

Maybe I'm bad at counting, but I don't see any stray </app_version> especially not at line 51.
App_info.xml done by the lunatics installer is automated using templates. Unless some manual editing was done, that would mean that the master template is borked, which I rather doubt.

I'm just beginning to try to understand
how to use app_info.xml to run an optimized astropulse and
also I guess the stock multibeam(?) (already made one mistake in trying to get that set up). Linux Ubuntu 11.10 32bit Intel. Suggestions
of places to look for info and other suggestions are welcome.
Yes I've looked at lunatics.kwsn.net and am continuing to search
these forums.

What exactly do you want to know? Just ask?
Starting your own thread if you are after Linux specific advice might help, and there are several pairs of eyes that can look over any app_info.xml.

The Nov 5 app_info.xml Nautilus posted had (at line 51 of app_info.xml)
a </app_version> which appears to not belong to any previous
<app_version>.

I'm just beginning to try to understand
how to use app_info.xml to run an optimized astropulse and
also I guess the stock multibeam(?) (already made one mistake in trying to get that set up). Linux Ubuntu 11.10 32bit Intel. Suggestions
of places to look for info and other suggestions are welcome.
Yes I've looked at lunatics.kwsn.net and am continuing to search
these forums.

It works fine after restarting Windooze.

0.05 CPU, 0.5 GPU

---

Contrary to what Ozz says (sorry Ozz, I'm going to disagree with you on this one), the task running on the ATI GPU would show as "0.04 CPUs + 0.50 ATI GPUs" if the <count>0.5</count> lines had been recognised.

That's fine, I'm still learning some of this ATi stuff myself! ;-)

That app_info.xml file can't have been active at the time the screenshot was taken.

Contrary to what Ozz says (sorry Ozz, I'm going to disagree with you on this one), the task running on the ATI GPU would show as "0.04 CPUs + 0.50 ATI GPUs" if the <count>0.5</count> lines had been recognised.

As Grant said, "You have to exit & restart BOINC for any changes in app_info to take effect". That means shutting down the Core Client too, not just the Manager - my guess is that's what it's waiting for (unless you edited a different copy of app_info.xml, and didn't put the new version into the data/project folder).

I believe it's easier to just close the client and reconnect using the Advanced view > Advanced tab > "Shut down connected client" option. Pressing OK on the Shutdown dialogue box and then OK again (or press enter) on the next box (Select computer)restarts/reloads the BOINC client and any app_info.xml (or other changes) will be recognised.

No worries about closing the Manager and then checking to see if the client is or isn't still running, or did BOINCTray close, too (and may need restarting seperately).

Lt

That app_info.xml file can't have been active at the time the screenshot was taken.

Contrary to what Ozz says (sorry Ozz, I'm going to disagree with you on this one), the task running on the ATI GPU would show as "0.04 CPUs + 0.50 ATI GPUs" if the <count>0.5</count> lines had been recognised.

As Grant said, "You have to exit & restart BOINC for any changes in app_info to take effect". That means shutting down the Core Client too, not just the Manager - my guess is that's what it's waiting for (unless you edited a different copy of app_info.xml, and didn't put the new version into the data/project folder).

From what i can remember, existing WUs will still run on the CPU, only new WUs will run on the GPU. If the next AP download goes to the CPU, there's a problem.
I only had a quick look at your app_info (maybe someone with a bit more experiece might like to have a closer look?) but it looks OK.

---

Grant
Darwin NT

It will still say using 1.00 GPU because there is only 1 GPU. You should see the second workunit via the extra load on the GPU through GPU-Z.

You'll also see 2 WUs running on the GPU in the BOINC manmager.

So far i see only one.


And here's the content of my app_info.xml

<app_info> 
    <app>
        <name>setiathome_enhanced</name>
    </app>
    <file_info>
        <name>AK_v8b_win_x64_SSE41.exe</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>603</version_num>
	<platform>windows_intelx86</platform>
        <file_ref>
           <file_name>AK_v8b_win_x64_SSE41.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>603</version_num>
	<platform>windows_x86_64</platform>
        <file_ref>
           <file_name>AK_v8b_win_x64_SSE41.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>
    <app>
        <name>astropulse_v505</name>
    </app>
    <file_info>
        <name>ap_5.06_win_x86_SSE2_OpenCL_ATI_r521.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>AstroPulse_Kernels_r521.cl</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>astropulse_v505</app_name>
        <version_num>506</version_num>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <platform>windows_intelx86</platform>
        <plan_class>ati13ati</plan_class>
        <cmdline>-instances_per_device 2 -unroll 6 -ffa_block 4096 -ffa_block_fetch 2048</cmdline>
        <coproc>
            <type>ATI</type>
            <count>0.5</count>
        </coproc>
        <file_ref>
            <file_name>ap_5.06_win_x86_SSE2_OpenCL_ATI_r521.exe</file_name>
            <main_program/>                           
        </file_ref>
        <file_ref>
            <file_name>AstroPulse_Kernels_r521.cl</file_name>
            <copy_file/>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v505</app_name>
        <version_num>505</version_num>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <platform>windows_intelx86</platform>
        <plan_class>ati13ati</plan_class>
        <cmdline>-instances_per_device 2 -unroll 6 -ffa_block 4096 -ffa_block_fetch 2048</cmdline>
        <coproc>
            <type>ATI</type>
            <count>0.5</count>
        </coproc>
        <file_ref>
            <file_name>ap_5.06_win_x86_SSE2_OpenCL_ATI_r521.exe</file_name>
            <main_program/>                           
        </file_ref>
        <file_ref>
            <file_name>AstroPulse_Kernels_r521.cl</file_name>
            <copy_file/>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v505</app_name>
        <version_num>506</version_num>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <platform>windows_x86_64</platform>
        <plan_class>ati13ati</plan_class>
        <cmdline>-instances_per_device 2 -unroll 6 -ffa_block 4096 -ffa_block_fetch 2048</cmdline>
        <coproc>
            <type>ATI</type>
            <count>0.5</count>
        </coproc>
        <file_ref>
            <file_name>ap_5.06_win_x86_SSE2_OpenCL_ATI_r521.exe</file_name>
            <main_program/>                           
        </file_ref>
        <file_ref>
            <file_name>AstroPulse_Kernels_r521.cl</file_name>
            <copy_file/>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>astropulse_v505</app_name>
        <version_num>505</version_num>
        <avg_ncpus>0.04</avg_ncpus>
        <max_ncpus>0.2</max_ncpus>
        <platform>windows_x86_64</platform>
        <plan_class>ati13ati</plan_class>
        <cmdline>-instances_per_device 2 -unroll 6 -ffa_block 4096 -ffa_block_fetch 2048</cmdline>
        <coproc>
            <type>ATI</type>
            <count>0.5</count>
        </coproc>
        <file_ref>
            <file_name>ap_5.06_win_x86_SSE2_OpenCL_ATI_r521.exe</file_name>
            <main_program/>                           
        </file_ref>
        <file_ref>
            <file_name>AstroPulse_Kernels_r521.cl</file_name>
            <copy_file/>
        </file_ref>
    </app_version>
    <app>
        <name>astropulse_v505</name>
    </app>
    <file_info>
        <name>ap_5.05r409_SSE.exe</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>astropulse_v505</app_name>
        <version_num>505</version_num>
	<platform>windows_intelx86</platform>
        <file_ref>
            <file_name>ap_5.05r409_SSE.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>    
    <app_version>
        <app_name>astropulse_v505</app_name>
        <version_num>505</version_num>
	<platform>windows_x86_64</platform>
        <file_ref>
            <file_name>ap_5.05r409_SSE.exe</file_name>
            <main_program/>
        </file_ref>
    </app_version>
    <app>
        <name>setiathome_enhanced</name>
    </app>
    <file_info>
        <name>MB_6.10_win_SSE3_ATI_r177.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>MultiBeam_Kernels_r177.cl</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>610</version_num>
        <platform>windows_intelx86</platform>
        <avg_ncpus>0.05</avg_ncpus>
        <max_ncpus>0.05</max_ncpus>
        <plan_class>ati13ati</plan_class>
        <cmdline>-period_iterations_num 5 -instances_per_device 2</cmdline>
        <coproc>
            <type>ATI</type>
            <count>0.5</count>
        </coproc>
        <file_ref>
            <file_name>MB_6.10_win_SSE3_ATI_r177.exe</file_name>
            <main_program/>                           
        </file_ref>
        <file_ref>
            <file_name>MultiBeam_Kernels_r177.cl</file_name>
            <open_name>MultiBeam_Kernels.cl</open_name>
            <copy_file/>
        </file_ref>
    </app_version>
    <app_version>
        <app_name>setiathome_enhanced</app_name>
        <version_num>610</version_num>
        <platform>windows_x86_64</platform>
        <avg_ncpus>0.05</avg_ncpus>
        <max_ncpus>0.05</max_ncpus>
        <plan_class>ati13ati</plan_class>
        <cmdline>-period_iterations_num 5 -instances_per_device 2</cmdline>
        <coproc>
            <type>ATI</type>
            <count>0.5</count>
        </coproc>
        <file_ref>
            <file_name>MB_6.10_win_SSE3_ATI_r177.exe</file_name>
            <main_program/>                           
        </file_ref>
        <file_ref>
            <file_name>MultiBeam_Kernels_r177.cl</file_name>
            <open_name>MultiBeam_Kernels.cl</open_name>
            <copy_file/>
        </file_ref>
    </app_version>
</app_info> 

---

It will still say using 1.00 GPU because there is only 1 GPU. You should see the second workunit via the extra load on the GPU through GPU-Z.

You'll also see 2 WUs running on the GPU in the BOINC manmager.

---

Grant
Darwin NT

I observed no difference after editing app_info.xml as you stated. GPU tasks still use 1.00 GPU. Maybe i did something wrong.

You have to exit & restart BOINC for any changes in app_info to take effect. If you did that, and it's still running only one task, exit, checkout app_info closely & make sure you make changes in all the entries for your video cards (from memory there are more than one).

---

Grant
Darwin NT

It will still say using 1.00 GPU because there is only 1 GPU. You should see the second workunit via the extra load on the GPU through GPU-Z.

There is some kind efficiency issues too. Like only 25%, 50% utilization of GPU on some tasks.

To have more load of the GPU you can try 2 or 3 simultaneous ATI tasks

Since you know the computers well I'll give only this short info:
(Make backup copy of app_info.xml before editing for easy restore.
It's in ...\BOINC\projects\setiathome.berkeley.edu\ which in your case is exactly:
C:\ProgramData\BOINC\projects\setiathome.berkeley.edu\
)

Exit BOINC
Edit the app_info.xml file with Notepad

For 2 tasks at a time:
Change (in ATI sections) all occurrences of:
<count>1</count>
<cmdline>-instances_per_device 1</cmdline>

... to

<coproc>
   <type>ATI</type>
   <count>0.5</count>
</coproc>

and:
<cmdline>-instances_per_device 2</cmdline>

I observed no difference after editing app_info.xml as you stated. GPU tasks still use 1.00 GPU. Maybe i did something wrong.

---

There is some kind efficiency issues too. Like only 25%, 50% utilization of GPU on some tasks.

To have more load of the GPU you can try 2 or 3 simultaneous ATI tasks

Since you know the computers well I'll give only this short info:
(Make backup copy of app_info.xml before editing for easy restore.
It's in ...\BOINC\projects\setiathome.berkeley.edu\ which in your case is exactly:
C:\ProgramData\BOINC\projects\setiathome.berkeley.edu\
)

Exit BOINC
Edit the app_info.xml file with Notepad

For 2 tasks at a time:
Change (in ATI sections) all occurrences of:
<count>1</count>
<cmdline>-instances_per_device 1</cmdline>

... to

<coproc>
   <type>ATI</type>
   <count>0.5</count>
</coproc>

and:
<cmdline>-instances_per_device 2</cmdline>

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Now my GPU is in works :) Thank y'all.

I RMA'ed my second 6870. It'll arrive in a week or so. I guess won't have problems related to Crossfire right?

edit: There is some kind efficiency issues too. Like only 25%, 50% utilization of GPU on some tasks.

---

Just hit the update button in the projects tab and look at the messages you´ve got.

I did as you said but;

05/11/2011 12:29:52 | SETI@home | Requesting new tasks for ATI GPU
05/11/2011 12:30:03 | SETI@home | Scheduler request completed: got 0 new tasks

:(

You are requesting work but the feeder had none.

You can go to your preferences here at your account page and set a cache of 2 - 3 days.
You only have 50 atm.

---

With each crime and every kindness we birth our future.

Just hit the update button in the projects tab and look at the messages you´ve got.

I did as you said but;

05/11/2011 12:29:52 | SETI@home | Requesting new tasks for ATI GPU
05/11/2011 12:30:03 | SETI@home | Scheduler request completed: got 0 new tasks

:(

Wait for the 5 minute and 3 seconds timeout to time out, then try again,

Claggy

Just hit the update button in the projects tab and look at the messages you´ve got.

I did as you said but;

05/11/2011 12:29:52 | SETI@home | Requesting new tasks for ATI GPU
05/11/2011 12:30:03 | SETI@home | Scheduler request completed: got 0 new tasks

:(

---