Posts by TRuEQ & TuVaLu

1) Message boards : News : BOINC for Android launched (Message 50276)
Posted 21 Aug 2013 by TRuEQ & TuVaLu
Post:
That's already done... each computer that joins a project recieves an unique id on that particular project (different on each project)


My 2 androids gets the same id.
2) Message boards : News : BOINC for Android launched (Message 50258)
Posted 20 Aug 2013 by TRuEQ & TuVaLu
Post:
Any chance boinc can sence there already is 1 device connected and then ask a simple question if this is device x+1 and then give it a unique device number during the install.

//TRuEQ
3) Message boards : News : BOINC for Android launched (Message 50226)
Posted 18 Aug 2013 by TRuEQ & TuVaLu
Post:
I have 2 Sony Ericsson android phones.

I've tested them on several projects.
Works pretty ok.

But there is a problem.

They are the same phone when I look at www for the projects computor status.
When I update the first it shows as the second phone and vice versa.

The 2 phones at Einstein and SETI Beta

http://einstein.phys.uwm.edu/hosts_user.php
http://setiweb.ssl.berkeley.edu/beta/hosts_user.php?userid=14842

Eric at Seti Beta suggested I inform BoincManager Dev people about this.
So here it is.

I hope someone here can make sence to this.

And computor id is the same on both phones.
4) Message boards : News : BOINC for Android launched (Message 50156)
Posted 9 Aug 2013 by TRuEQ & TuVaLu
Post:
Is there any chance that the BM for android can show version number where the little boinc icon are besides BOINC?


¤BOINC 7.2.9 or something...

5) Message boards : News : BOINC for Android launched (Message 50020)
Posted 28 Jul 2013 by TRuEQ & TuVaLu
Post:
Will Boinc update itself to newer versions when they are available?

I don't think so. Version 7.2.8 is available in the Google Play Store, if your BOINC is still 7.2.7, it doesn't update itself.
And will the project list update itself as more projects becomes availabe?

Yes, that one will update itself.

I saw you mentioned The skynet pogs as an arm project but it wasn't in the projects list.

That's because 7.2.7 was built before SkynetPOGs was added.

By the way, there's also an Android FAQ that is updated quite regularly.


Thank you.
6) Message boards : News : BOINC for Android launched (Message 50017)
Posted 28 Jul 2013 by TRuEQ & TuVaLu
Post:
I added 2 Sony Ericsson 1ghz phones today.
Running WCG on 1 and asteroids on the other.

Will Boinc update itself to newer versions when they are available?
And will the project list update itself as more projects becomes availabe?

I saw you mentioned The skynet pogs as an arm project but it wasn't in the projects list.

7) Message boards : BOINC client : BM .64 cc_config.xml changed... (Message 49329)
Posted 26 May 2013 by TRuEQ & TuVaLu
Post:
The added lines won't change, and it doesn't make the use of BOINC any slower. So there's really no need to rewrite the file. It's easy as well for if you ever just want to enable any debug lines, then you only have to change a zero for a one, not have to figure out how to spell words and make sure the lines have the correct end tags or not.

Plus as soon as you add a file again through the exclusive apps option, they'll all be back.


I used the exclusive app on request to see if that would help.
A half a second after I started the exclusive app(Firefox) computor frooze.

The exclude lines are not present after added exclusion app.

Yes I can understand the benefits for addind >1> to some of the lines.

8) Message boards : BOINC client : GPU Numbering on ATI 5970 (Message 49327)
Posted 25 May 2013 by TRuEQ & TuVaLu
Post:
SIV says there way of giving numbers to the GPU's are correct.

Well, when the developer for that application says his way is the only correct way, then that must be it. Case solved. Why bother to ask?

But here's the thing, SIV can use an OS specific API to do all the hard work of polling the videocard for it, whereas BOINC needs to be showing the same numbers when compiled on Windows, Linux, FreeBSD or OSX, and where applicable and supported. It cannot rely on an OS specific API. It will also have the detect Nvidia GPUs, AMD GPUs and Intel GPUs and put them in a certain order, these being 1 - compute capability, 2 - software version, 3 - available memory and 4 - speed.

Only after those 4 have been ascertained, will BOINC give out numbers for GPUs and show that in the start-up messages. And they'll be the same numbers whether you run Windows, Linux, OSX or FreeBSD. Easy, huh? :-)


From what I understood, he used ATI way of detecting.
9) Message boards : BOINC client : GPU Numbering on ATI 5970 (Message 49319)
Posted 25 May 2013 by TRuEQ & TuVaLu
Post:
Why does SIV and BoincManager give different number to the GPU's on 5970 card.
SIV says there way of giving numbers to the GPU's are correct.

see here.



Any ideas...???
10) Message boards : BOINC client : BM .64 cc_config.xml changed... (Message 49277)
Posted 23 May 2013 by TRuEQ & TuVaLu
Post:
That's not new in v7.0.64 - for some time now, the Manager (and I think it is a Manager thing, not the core client) has created a fully-populated template for cc_config.xml in alphabetical order, every time you use the GUI tool for adding an exclusive application.

It's a very useful feature, IMHO.



Thank you for that answer.
It explains everything since I added an exclusive app.
But now exclusive app is removed and they are still there....

I'll write a new one with less lines.
11) Message boards : BOINC client : BM .64 cc_config.xml changed... (Message 49263)
Posted 23 May 2013 by TRuEQ & TuVaLu
Post:
What can make my cc_config.xml to look like this???
A couple of days ago it had only 10-15 lines....




<cc_config>
<log_flags>
<file_xfer>1</file_xfer>
<sched_ops>1</sched_ops>
<task>1</task>
<app_msg_receive>0</app_msg_receive>
<app_msg_send>0</app_msg_send>
<async_file_debug>0</async_file_debug>
<benchmark_debug>0</benchmark_debug>
<checkpoint_debug>0</checkpoint_debug>
<coproc_debug>0</coproc_debug>
<cpu_sched>0</cpu_sched>
<cpu_sched_debug>0</cpu_sched_debug>
<cpu_sched_status>0</cpu_sched_status>
<dcf_debug>0</dcf_debug>
<disk_usage_debug>0</disk_usage_debug>
<file_xfer_debug>0</file_xfer_debug>
<gui_rpc_debug>0</gui_rpc_debug>
<heartbeat_debug>0</heartbeat_debug>
<http_debug>0</http_debug>
<http_xfer_debug>0</http_xfer_debug>
<mem_usage_debug>0</mem_usage_debug>
<network_status_debug>0</network_status_debug>
<notice_debug>0</notice_debug>
<poll_debug>0</poll_debug>
<priority_debug>0</priority_debug>
<proxy_debug>0</proxy_debug>
<rr_simulation>0</rr_simulation>
<rrsim_detail>0</rrsim_detail>
<sched_op_debug>0</sched_op_debug>
<scrsave_debug>0</scrsave_debug>
<slot_debug>0</slot_debug>
<state_debug>0</state_debug>
<statefile_debug>0</statefile_debug>
<suspend_debug>0</suspend_debug>
<task_debug>0</task_debug>
<time_debug>0</time_debug>
<trickle_debug>0</trickle_debug>
<unparsed_xml>0</unparsed_xml>
<work_fetch_debug>0</work_fetch_debug>
</log_flags>
<options>
<abort_jobs_on_exit>0</abort_jobs_on_exit>
<allow_multiple_clients>0</allow_multiple_clients>
<allow_remote_gui_rpc>0</allow_remote_gui_rpc>
<client_version_check_url>http://boinc.berkeley.edu/download.php?xml=1</client_version_check_url>
<client_download_url>http://boinc.berkeley.edu/download.php</client_download_url>
<disallow_attach>0</disallow_attach>
<dont_check_file_sizes>0</dont_check_file_sizes>
<dont_contact_ref_site>0</dont_contact_ref_site>
<exit_after_finish>0</exit_after_finish>
<exit_before_start>0</exit_before_start>
<exit_when_idle>0</exit_when_idle>
<fetch_minimal_work>0</fetch_minimal_work>
<fetch_on_update>0</fetch_on_update>
<force_auth>default</force_auth>
<http_1_0>0</http_1_0>
<http_transfer_timeout>600</http_transfer_timeout>
<http_transfer_timeout_bps>10</http_transfer_timeout_bps>
<max_file_xfers>8</max_file_xfers>
<max_file_xfers_per_project>4</max_file_xfers_per_project>
<max_stderr_file_size>0</max_stderr_file_size>
<max_stdout_file_size>0</max_stdout_file_size>
<max_tasks_reported>0</max_tasks_reported>
<ncpus>-1</ncpus>
<network_test_url>http://www.google.com/</network_test_url>
<no_alt_platform>0</no_alt_platform>
<no_gpus>0</no_gpus>
<no_info_fetch>0</no_info_fetch>
<no_priority_change>0</no_priority_change>
<os_random_only>0</os_random_only>
<proxy_info>
<socks_server_name></socks_server_name>
<socks_server_port>80</socks_server_port>
<http_server_name></http_server_name>
<http_server_port>80</http_server_port>
<socks5_user_name></socks5_user_name>
<socks5_user_passwd></socks5_user_passwd>
<http_user_name></http_user_name>
<http_user_passwd></http_user_passwd>
<no_proxy></no_proxy>
</proxy_info>
<rec_half_life_days>0.250000</rec_half_life_days>
<report_results_immediately>1</report_results_immediately>
<run_apps_manually>0</run_apps_manually>
<save_stats_days>30</save_stats_days>
<skip_cpu_benchmarks>0</skip_cpu_benchmarks>
<simple_gui_only>0</simple_gui_only>
<start_delay>0</start_delay>
<stderr_head>0</stderr_head>
<suppress_net_info>0</suppress_net_info>
<unsigned_apps_ok>0</unsigned_apps_ok>
<use_all_gpus>0</use_all_gpus>
<use_certs>0</use_certs>
<use_certs_only>0</use_certs_only>
<vbox_window>0</vbox_window>
</options>
</cc_config>
12) Message boards : BOINC client : My Wish List (Message 49062)
Posted 9 May 2013 by TRuEQ & TuVaLu
Post:
It would be nice to have an option for "snooze Gpu(X) where there today is snooze GPU down at the windows clock icon when right-clicking the BM icon.

Since I might want to use the GPU, maybe to see a movie and that is connected to my primary display, then it would be nice to snooze that particular GPU and still use all other Gpu's for Boinc.

Today the only way to temporarily do this is to snooze all Gpu's or write a config file.

A snooze Gpu(X) would make it alot smoother.
13) Message boards : BOINC client : .64 seems to work. (Message 48767)
Posted 22 Apr 2013 by TRuEQ & TuVaLu
Post:
I'd say "go" after running it 24hours.
14) Message boards : BOINC client : BM .62 strange (Message 48624)
Posted 13 Apr 2013 by TRuEQ & TuVaLu
Post:
You can post in your thread ad nauseum, but without specific data there is nothing that we can see or do about any of it. Your problem, you have to explain in detail what you see, what you think you should see, where it differs from the last test you did. There's nothing in it that I can send to the developers either, as they'll just request debug logs and such, things that you neglect to give.

So you really have to do better than this. If not in text, then use pictures. Use Photobucket, Imageshack or TinyPic to store the image and give an URL or IMG to the image.

Since you're choosing to run development versions of BOINC, I also want to remind you of the disclaimer and reminder to alpha testers:
Disclaimer
On development versions of BOINC:
- Expect parts of it to be broken, or in the least to work in a different way than you are used to.
- Expect work failures, deadline misses and losing all your accumulated work in progress, or not getting credit for your work due to unknown and unforeseen circumstances.
- Only use it when you are willing to participate in the Alpha test program and do not mind sending (bug) reports in to the developers on the email list specially assigned for this purpose.
- Due to the OpenCL detection, your screen may flicker or turn off temporarily. This is normal.


REMINDER TO ALL ALPHA TESTERS:
It's far easier for the developers to fix problems when you send message logs with the appropriate flags set. The main flags are:

<cpu_sched_debug>: problems involving the choice of applications to run.
<work_fetch_debug>: problems involving work fetch (which projects are asked for work, and how much).
<rr_simulation>: problems involving jobs being run in high-priority mode.
<sched_op_debug>: problems involving scheduler operations and other low level information.

Use these flags from the cc_config.xml file.

Report any problems you get with it to the Alpha email list. This list needs registration. When sending logs or other attachments, make sure to CC David, Rom, or Charlie separately, since the email list will drop attachments!

Reporting bugs on this forum or any project's forum isn't very productive as the developers simply do not have time to scour through all forums looking for posts with your bug reports in them. While it may happen that we - other volunteers - forward your problem to them, history has shown it is quite difficult being the middle man in this when more information is needed from you. Hence why it's better for all concerned that you report the problem directly to the developers, who will come back directly to you when they need more information or better logs or to tell you that they've checked in a fix for the specific problem.



Thanks for your advice.

My feedback was mostly to describe a multiple problem including multiple test programs runned at the same time.

My intention was to give information about what I experience so if anyone else sees something similiar or partly similiar it might be worth further investigation.

The pauses of BM was most likely from a setting used when running SETI Beta task. -sbs 256(default=64) when using 64 problem dissapeared. I can use -256 with seti ati ap tasks without problem. I've spent some hours trying to find the cause of this. Now we know what and why.

GPU(0,1,2) order with catalyst, BM and SIV I informed SIV people it was probebly wrong order in their program.
SIV dev requested more info and I've proveded them with it.(hopefully fixed in next SIV version). using the same rules(standards) is of help i think.

exclude(GPU) in cc_config.xml that made me run 1 Moowrap task + 2 POEM tasks does not work in BM .62 but still works in .60


I will get rid of as many "fuzzy things" i can before upgrading BM from .60

And you guys wanted positive feedback as well as malfunction reports.

So I'd like to say. On my rig BM 7.0.60 works. No problems detected.
15) Message boards : BOINC client : Bm counters stops for about 1min and then resumes. Any ideas? (Message 48623)
Posted 13 Apr 2013 by TRuEQ & TuVaLu
Post:
I have an explanation for the BM pauses.

When setting -sbs to 128 or 256 i get BM counters pauses and after about a min they do resume.

running Seti Beta mb ATI tasks
using an empty cmdline.txt which equals -sbs 64 gives no pauses.

problem about the pauses equals stressed PCIE bus in my case.
16) Message boards : BOINC client : BM .62 strange (Message 48621)
Posted 13 Apr 2013 by TRuEQ & TuVaLu
Post:
.60 works fine.
17) Message boards : BOINC client : GPU number when having multiple GPU's (Message 48618)
Posted 13 Apr 2013 by TRuEQ & TuVaLu
Post:
Catalyst is numbering PCIE X4 5850 card as 0
And Catalsyst also numbers GPU 2 as the number the task is running on.
So I guess BM assigns the correct number.

I'll try get a note to SIV people about this.


I've connected my monitor to both cards but I am using the slower PCIE X4 slot as primary screen adapter.

Maybe that's why it says GPU(0)

18) Message boards : BOINC client : GPU number when having multiple GPU's (Message 48617)
Posted 13 Apr 2013 by TRuEQ & TuVaLu
Post:
(note)
It may be the driver that assigns the number and then it is a AMD/ATI issue....
19) Message boards : BOINC client : GPU number when having multiple GPU's (Message 48616)
Posted 13 Apr 2013 by TRuEQ & TuVaLu
Post:
My logic says.

PCIE X16 are primary and GPU should start with 0 or 0 and 1(if having a dual gpu attached to it).

The slower(secondary) card should be numbered with 1 or 2 when having single gpu card attached to it.

I dunno if this has any impact on the different program languages used to create apps though....
20) Message boards : BOINC client : GPU number when having multiple GPU's (Message 48615)
Posted 13 Apr 2013 by TRuEQ & TuVaLu
Post:
I've noticed BM and SIV says GPU 0 for my 5850 and that is located in my slower PCIE slot, X4 slot.

My 5970(2GPU's) are located in fast PCIE slot X16

SIV counts the first GPU as (1)
BM counts the first as (2)

I can tell when only running 1 task the 5970(2GPU's).

Then I wonder which program gives the correct device number.
SIV or BM??


Next 20

Copyright © 2019 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.