PrimeGrid
Please visit donation page to help the project cover running costs for this month

Toggle Menu

Join PrimeGrid

Returning Participants

Community

Leader Boards

Results

Other

drummers-lowrise
11) Message boards : Problems and Help : New BOINC Wrapper needed for Windows LLR (Message 32230)
Posted 4201 days ago by Profile Crunch3r
It's done. The app is listed in the PG download-directory...


Yes, looks like it's listed under "Sophie Germain Prime Search (LLR)" as 6.09...
(The wrapper prints 6.03 to stderr.txt... but that's of no interest anyway)

12) Message boards : Problems and Help : New BOINC Wrapper needed for Windows LLR (Message 32134)
Posted 4203 days ago by Profile Crunch3r
OK... i've experimented with the wrapper code a bit today and FINALLY made some progress.

The whole problem why it doesn't work is that when redirecting the input/output of a console process,
the parent process is being blocked by "ReadFile" which also causes the "loss" of control over the child process and
therefore one is unable to successfully "resume from suspention" and unable to terminate the child pid as well.

(don't know how that's called on windows, but in linux terms that would be a "zombie" (child process)...)

Anyway, here's the current situation:

What works:
- suspend the app
- resume the app
- terminate the app (boinc shutdown)
- progress bar(*) (when resumed from suspention and boinc wasn't shut down)
- result files get written/reported properly when the app is done (100%)

What doesn't work:
- *progress bar, when resuming from a (fake?)checkpoit and boinc was shut down ... it starts counting from zero again
(Does that work properly on linux ????????)


So.... since none dared to reply here... i'm replying to myself :D !!!

Judging from what i've heard.. it all looks excelent as of now!

My wrapper does the same as the one over a linux!

Need to read more ? -> http://board.mpits.net/viewtopic.php?f=32&t=39

Having some time (~2hrs) and a bit of focus did the trick.... shame on all socalled "devs" that tried before...n00bs you failed and suck big time !!!!

I KNOW...lIT'S MEAN... BUT TEAM BOINC UNITED MADE IT WORK....once again.. :D
13) Message boards : Problems and Help : New BOINC Wrapper needed for Windows LLR (Message 32130)
Posted 4203 days ago by Profile Crunch3r
OK... i've experimented with the wrapper code a bit today and FINALLY made some progress.

The whole problem why it doesn't work is that when redirecting the input/output of a console process,
the parent process is being blocked by "ReadFile" which also causes the "loss" of control over the child process and
therefore one is unable to successfully "resume from suspention" and unable to terminate the child pid as well.

(don't know how that's called on windows, but in linux terms that would be a "zombie" (child process)...)

Anyway, here's the current situation:

What works:
- suspend the app
- resume the app
- terminate the app (boinc shutdown)
- progress bar(*) (when resumed from suspention and boinc wasn't shut down)
- result files get written/reported properly when the app is done (100%)

What doesn't work:
- *progress bar, when resuming from a (fake?)checkpoit and boinc was shut down ... it starts counting from zero again
(Does that work properly on linux ????????)
14) Message boards : Problems and Help : New BOINC Wrapper needed for Windows LLR (Message 31737)
Posted 4210 days ago by Profile Crunch3r
What exactly do you need ?

We need a custom wrapper which
1) copies input file where LLR application can find it;
2) runs LLR and monitors its stdout for status messages and reports progress to BOINC accordingly. It also should monitor filesystem for file writes (checkpoints) and notify BOINC about them.
3) Copies outout file to the place where BOINC can find it.

It's fairly straightforward, it's just that I couldn't figure out how to correctly read progress (I had made it work standalone, but it fails when running under BOINC).

If you think you can help, PM or email me admin@primegrid.com and I will give you exact details. Thanks!


Ok, i got the link to the wrapper source from John.

I've used the linux source code, since there are already new versions for the wrapper and i "assume" that the progress bar is working there(there should be no difference between win<->linux since this is boinc specific).

Had to modifiy the source a bit (needed to include a header) and got both x86 and x86_64 wrappers compiled.

The only thing i need to know is if i need to modify the :
# define LLR_EXE_FILENAME "primegrid_cllr_3.7.1c.exe.orig" # define LLR_LOCAL_EXE_FILENAME "primegrid_cllr_3.7.1c.exe"


and

boinc_resolve_filename_s("llr.ini.6.00", sInputFile);


or not...

Besides that, an app_info.xml for testing the wrapper would be great as well ;)


EDIT:

Got your pm Rytis and replied with a download url ;)
Let's hope that it works.



OK... so from what i could gather and the experience with the behavior of wrapper code after compilation, it's safe to assume that it's not usable in it's current form.

There seems to be a serious issue regarding the security descriptors(tread handles) that causes havok when running on a 64 bit OS (xp 64+ upwards to win7). Therfore the spawed thread cannot be suspended/resumed...

A forced stop (terminate) is possible, with killing the llr thread entirely... (contrary to what the boinc wrapper sample code suggest... terminateprocess(pid,-1) <--- where pid is ok but -1 seems screwed .... how could it work.. since it needs to be a signed int...)

Anyway, the whole suspend_resume() is not working at all, basically i guess due to the screwed up security descritors... it's a big mess and completely unusable as of now...

Anyway, there's still a possibility to circumvent compiling a new wrapper... well see about that... and hopefully my suggestion works, at least for now, till this mess can be cleaned up properly...

If anyone of the previous devs have the code rewritten to adjust these issues and the only thing stopping you is getting it complied, feel free to contact me via pm and i can compile your code to see if that works any better compared to the "junk" that the wrapper is atm...



15) Message boards : Problems and Help : New BOINC Wrapper needed for Windows LLR (Message 31625)
Posted 4212 days ago by Profile Crunch3r
What exactly do you need ?

We need a custom wrapper which
1) copies input file where LLR application can find it;
2) runs LLR and monitors its stdout for status messages and reports progress to BOINC accordingly. It also should monitor filesystem for file writes (checkpoints) and notify BOINC about them.
3) Copies outout file to the place where BOINC can find it.

It's fairly straightforward, it's just that I couldn't figure out how to correctly read progress (I had made it work standalone, but it fails when running under BOINC).

If you think you can help, PM or email me admin@primegrid.com and I will give you exact details. Thanks!


Ok, i got the link to the wrapper source from John.

I've used the linux source code, since there are already new versions for the wrapper and i "assume" that the progress bar is working there(there should be no difference between win<->linux since this is boinc specific).

Had to modifiy the source a bit (needed to include a header) and got both x86 and x86_64 wrappers compiled.

The only thing i need to know is if i need to modify the :
# define LLR_EXE_FILENAME "primegrid_cllr_3.7.1c.exe.orig" # define LLR_LOCAL_EXE_FILENAME "primegrid_cllr_3.7.1c.exe"


and

boinc_resolve_filename_s("llr.ini.6.00", sInputFile);


or not...

Besides that, an app_info.xml for testing the wrapper would be great as well ;)


EDIT:

Got your pm Rytis and replied with a download url ;)
Let's hope that it works.
16) Message boards : Problems and Help : New BOINC Wrapper needed for Windows LLR (Message 31593)
Posted 4213 days ago by Profile Crunch3r
At least two people have tried to help with this, including myself. The problem isn't in the programing so much as it's difficult to get a correct development environment running that will compile the BOINC libraries and sample code.


That's not a problem at all. I use vs 2005 and have a working setup that compiles&links the stock wrapper included in the boinc sources.


They seem to correctly compile only on versions of the compiler that are no longer available. So if you don't already have an working dev setup for creating BOINC code, you'll need to somehow 'acquire' old versions of Visual Studio. Either that or there's some details of the necessary setup steps that are both undocumented and difficult to figure out.


So if i read all the info here correctly, then a working wrapper already exists for linux.
All i'd need is the source code for that so i could compile it for windows.
17) Message boards : Problems and Help : New BOINC Wrapper needed for Windows LLR (Message 31573)
Posted 4213 days ago by Profile Crunch3r
No progress?

None


What exactly do you need ?
18) Message boards : Proth Prime Search : windows x64 app for ATI? (Message 30881)
Posted 4226 days ago by Profile Crunch3r
After a 6 hour struggle, I once more was trying to get this to work on Win7-64 and in my case finally figured out the issue... Unlike before where you could mix ATI and CUDA cards, the last two driver versions will not load if there is a NVIDIA card installed. Well, not totally true, the driver installs and works (ATI was primary display and it worked), but no GPU computing ... BOINC will not see the card though it is working fine... pull the nvidia card and the ATI card is fine... put in a second ATI card and that is fine as well...

Not sure if this is a detection problem... or a driver problem ...

Oh, and for the prime program to work you just need to install the "AMD Catalystâ„¢ Accelerated Parallel Processing (APP) Technology Edition" ...


you can still mix ati & nvidia cards and runn the latest drivers. I do that myself with a 5870 & 8800GS.

Here's what i did to get both working.

1. uninstall both ATI & NVIDA drivers
2. reboot and run "Driver Cleaner" -> remove all references to ATI & NVIDIA
3. shutdown and remove the NVIDIA card
4. download and install the ATI drivers & restart
5. shutdown and insert the NVIDIA card again
6. download and install the latest NV drivers & reboot

That's with the ATI card being the primary card.

If it's different on your systzem you need to change the steps

After thatbeing done, both cards were recognized by boinc again.
19) Message boards : Proth Prime Search : What happened here? (Message 30307)
Posted 4235 days ago by Profile Crunch3r
My GTX 460 machine has been tearing through the sieve WUs at an alarming rate; I've seen 9:50 to 10:20 for completion times, and tasks never error out.

I'm a bit confused, though, as to why one particular task took so very long. (the one in the middle below)

214779753 150755940 165444 4 Jan 2011 4:01:19 UTC 4 Jan 2011 4:32:45 UTC Completed and validated 617.70 76.56 2,311.00 Proth Prime Search (Sieve) v1.37 (cuda23) 214779630 150755672 165444 4 Jan 2011 4:01:19 UTC 4 Jan 2011 5:39:35 UTC Completed and validated 2,488.47 74.14 2,311.00 Proth Prime Search (Sieve) v1.37 (cuda23) 214779504 150755673 165444 4 Jan 2011 4:01:19 UTC 4 Jan 2011 5:30:38 UTC Completed and validated 612.72 74.48 2,311.00 Proth Prime Search (Sieve) v1.37 (cuda23)


The task in question is this one - completed and validated just fine, but why'd it take over 4 times as long as every other?

All the sieve tasks use 0.36 CPUs, which on my P4 translates to 0.18 of 1 virtual core, and the whole system actually reads as having a bit less memory than the GPU it's running - if anything, I want to be sure I'm not heading down the wrong path by using a brand-new, overclocked Fermi card on a mostly-six-year-old computer.

Note that I have had tasks "hang" in the past, where they'll run for ~20 minutes and hit maybe 5% before I realize there's something wrong and abort them.

It would also appear, from reading some stderrs, that none of the sieve tasks I do ever checkpoint to disk, meaning that I cannot suspend them without having to restart them (and that's not always successful either).

So, is this normal, or should I change something?

As much as I know about GPUs and crunching on 'em, I'm not exactly familiar with how things work "under the hood," so to speak, with regards to apps like PPS.

Any pointers?


A possible cause for that is when boinc does "benchmarks" of the cpu. It should be possible to see that in the messages tab or in the log files.
20) Message boards : Proth Prime Search : Computation Error on Proth Prime Search ( Sieve ) V1.35 (Message 30300)
Posted 4235 days ago by Profile Crunch3r
I get a computation error on startup for Proth Prime Search ( Sieve ) V1.35 the WU's seem to stop after a few seconds.

Not too much of a problem I just abort the WU in question.

The WU's for Proth Prime Search ( Sieve ) V1.36 appear to run OK.

Is there anything I can do to prevent downloads of Proth Prime Search ( Sieve ) V1.35 WU's.

I am running a Windows 7, 64 Bit Intel Dual Core machine with a Radeon HD4570 GPU.

Any suggestions and help would be most welcome.

Thanks


Your ATI drivers are to old. You need to update them -> http://sites.amd.com/us/game/downloads/Pages/radeon_win7-64.aspx
Download and install the "AMD Catalystâ„¢ Accelerated Parallel Processing (APP) Technology Edition" drivers.


Next 10 posts
[Return to PrimeGrid main page]
DNS Powered by DNSEXIT.COM
Copyright © 2005 - 2022 Rytis Slatkevičius (contact) and PrimeGrid community. Server load 1.59, 1.32, 1.19
Generated 9 Aug 2022 | 18:00:41 UTC