Posts by Mumps [MM]
log in
1) Message boards : Number crunching : Crunching with an Intel GPU? (Message 16078)
Posted 1773 days ago by Profile Mumps [MM]
So, any progress yet? My Intel GPU is still wasting away bored and BOINCless. :)
2) Message boards : Number crunching : Crunching with an Intel GPU? (Message 15958)
Posted 1813 days ago by Profile Mumps [MM]
Ahh, yes, that's what is meant by the statement that the newest BOINC clients seem to support it. But I think it's declared a different Plan Class. So the Project needs to create apps or at least associate apps with the new Plan Class. Otherwise you'll never get any work from a project for it.

For some reason, I doubt it's as easy as telling the BOINC client (using an app_info.xml as an example) to treat it the same as a traditional OpenCL GPU. But I'm hoping the gurus here at Collatz can get us all hooked up for it. :)
3) Message boards : Number crunching : Crunching with an Intel GPU? (Message 15954)
Posted 1813 days ago by Profile Mumps [MM]
Are we any closer to being able to crunch with the latest Intel Integrated GPU's? They do support OpenCL after all, and the latest BOINC Client claims to support them now. Seems we just need to get a project that'll put out an App that'll run on 'em. ;-)
4) Message boards : Number crunching : 1.10 Error Thread (Message 546)
Posted 3078 days ago by Profile Mumps [MM]
That trailing "_" is a common convention that indicates the component is compressed. Which means you need to install it using the installer to get it uncompressed. Not just renamed.
5) Message boards : Number crunching : ATI Application (Message 512)
Posted 3079 days ago by Profile Mumps [MM]
OK. So has anybody managed to get the project to work on an ATI Mobility Radeon HD 3430? Running BOINC 6.6.20 without the Protected mode install under Win 7 64 bit locks the system up totally after a period of crunching. I'm not sure what's at fault though. Wouldn't be surprised at the drivers though, considering I've got the first "official" install. (Previous installs were called "Beta.")
6) Message boards : Number crunching : 1.10 Error Thread (Message 426)
Posted 3084 days ago by Profile Mumps [MM]
I run my XP boxes as a service with ATI's no problem, but on my win7 desk and vista laptop it wouldn't work had to reinstall as non-service.

Thanks Liuqyn. That's enough info to try something new. :-)
7) Message boards : Number crunching : 1.10 Error Thread (Message 424)
Posted 3084 days ago by Profile Mumps [MM]
Do you really need this file?


Short answer, No.

I tend to agree. After reading up a bit on XP/Vista/Win7 compatibility, it shouldn't be required. It may belong with IE8, rather than IE7, or FireFox.

Actually, I did grab a WU and tried to run it in standalone mode. It worked, for a while, but then the system totally locked up. My guess is it just wasn't meant to be. No running on the Integrated Radeon HD Mobility 3430 on this HP Laptop. My guess is it's an issue with the shared memory architecture. (That, or running it in standalone mode with the system also running an Aqua WU on the CPU cores. :-))

But, I've got a real 3430 to try on a Core2 Duo box next. :-)

Quick thought though, is there possibly an issue with BOINC 6.6.20 trying to access the card when running as a service under Win7? That's one more thing I haven't tried. Just reinstalling BOINC so as to not run as a service. Anybody else running on the ATI with BOINC as a service? (Protected mode install.) Or maybe something to do with UAC?
8) Message boards : Number crunching : 1.10 Error Thread (Message 402)
Posted 3086 days ago by Profile Mumps [MM]
Okay, so now I have all six dll inside system32 folder, I installed the recommended MSVC 2005 SP1 runtime package 32bit just in case I needed it. Still no dice. I still have the same error that I had before.

Is there any other driver version for the Radeon HD 3200 that I can role back to bypass these errors. I don't really care what driver I have on there as long as it works.

Another driver version won't help as the error you are seeing means the application couldn't initialize properly (normally some dynamically linked component, i.e. a dll, is missing).

Could you run the dependency walker (direct download links: 32bit, 64bit) and load the ATI app into it? That tool will tell you what dlls it's trying to load and which of them are missing.

Great. So I grabbed dependencywalker and it reports I'm missing IESHIMS.DLL. Now to figure out where that comes from! :-D
Program Files\Internet Explorer
Added to path, depends is happier, but still runs on the CPU, not the GPU. Strange things to ponder...
9) Message boards : Number crunching : ATI Application (Message 322)
Posted 3091 days ago by Profile Mumps [MM]
OK. So I've downloaded and installed the 1.10 Win 64 CAL Op app and grabbed a single WU. Any thoughts on why it still doesn't see a CAL device for me? Because it's a laptop integrated Radeon Mobility HD 3430, it can't run MW, but originally it was suggested it should be able to run Collatz. Is that actually not the case? How should I go about figuring out why it thinks there are 0 available GPU's if it should work?

EDIT: Well, let's see if this works any better. I just went and grabbed the current Win7 64 bit drivers and installed them. The installer indicated that the previous version driver wasn't installed. (?) After installing and re-copying the atical -> amdcal, the next WU is now reporting it's found a CAL device. Here's hoping it takes less than 41 hours this time around! :-)


I hope that this isn't the new WU. Someone else running Server 2008 had a result with similar output. I haven't seen that on any of the XP boxes. Has anyone had that problem with Vista?

Nope. That one, and the identical one that errored out with a 135 error, were from right after installing the updated drivers. That's the result you get when you run without doing the

cd /d %systemroot%\system32
copy amdcal* atical*

first after updating the drivers. The driver install removed the older copies as part of uninstalling the older drivers, but then didn't recreate them automatically afterwards.

Sadly enough, that followup WU finished in almost the same time as my last one that ran exclusively on the CPU, and the logged output still shows 0 GPU's found:

Beginning processing...
2 concurrent WUs allowed
Collatz ATI v1.10 (GPU Optimized Application)
CAL Runtime: 1.4.344
Found 0 CAL device

worker: trying boinc_get_init_data()...
Looking for checkpoint file...
No checkpoint file found. Starting at beginning.
No free GPU! Waiting ... 0 seconds.
Starting WU on GPU 13893976

But when I manually tried to run it (in standalone mode per-se) it showed it found the CAL device. I'll have to spend some time to try to puzzle that one out...

In the meantime, is that an error in the output from Collatz? It almost looks like it should be reporting

Starting WU on CPU

not GPU.
10) Message boards : Number crunching : ATI Application (Message 275)
Posted 3092 days ago by Profile Mumps [MM]
OK. So I've downloaded and installed the 1.10 Win 64 CAL Op app and grabbed a single WU. Any thoughts on why it still doesn't see a CAL device for me? Because it's a laptop integrated Radeon Mobility HD 3430, it can't run MW, but originally it was suggested it should be able to run Collatz. Is that actually not the case? How should I go about figuring out why it thinks there are 0 available GPU's if it should work?

EDIT: Well, let's see if this works any better. I just went and grabbed the current Win7 64 bit drivers and installed them. The installer indicated that the previous version driver wasn't installed. (?) After installing and re-copying the atical -> amdcal, the next WU is now reporting it's found a CAL device. Here's hoping it takes less than 41 hours this time around! :-)
11) Message boards : Number crunching : ATI Application (Message 146)
Posted 3102 days ago by Profile Mumps [MM]
Note the comments in the log:

Collatz ATI v1.09 (GPU Optimized)
CAL Runtime: 1.4.283
Found 0 CAL device

worker: trying boinc_get_init_data()...
No free GPU! Waiting ... 0 seconds.
Starting WU on GPU 15466840
Beginning processing...

It completed and reported 50,454 seconds of runtime, but the work log reports it only took 7,090 seconds of GPU time. Any thoughts on it?

It detected no GPU and used the CPU fallback, which can be quite slow.


I think the key information is: "Starting WU on GPU 15466840"

The array that holds the list of valid devices was not being initialized properly. That should be fixed in v1.10. The fact that it finished in just under 118 minutes of gpu time leads me to believe that it may have actually run on the GPU since I don't think the CPU version can finish that quickly (yet).

That's what I thought was so strange. 118 minutes of GPU time, but 14 hours of CPU time and over 30 hours of walltime... And it did report "Starting WU on GPU"


While testing the new apps, I also discovered that the gpu time gets reset if the app is suspended since that wasn't getting written to the checkpoint file, so whenever it started back up, it reset to zero. So it probably did run on the CPU.

Well, eagerly awaiting 1.10! :-)
12) Message boards : Number crunching : ATI Application (Message 130)
Posted 3106 days ago by Profile Mumps [MM]
Note the comments in the log:

Collatz ATI v1.09 (GPU Optimized)
CAL Runtime: 1.4.283
Found 0 CAL device

worker: trying boinc_get_init_data()...
No free GPU! Waiting ... 0 seconds.
Starting WU on GPU 15466840
Beginning processing...

It completed and reported 50,454 seconds of runtime, but the work log reports it only took 7,090 seconds of GPU time. Any thoughts on it?

It detected no GPU and used the CPU fallback, which can be quite slow.


I think the key information is: "Starting WU on GPU 15466840"

The array that holds the list of valid devices was not being initialized properly. That should be fixed in v1.10. The fact that it finished in just under 118 minutes of gpu time leads me to believe that it may have actually run on the GPU since I don't think the CPU version can finish that quickly (yet).

That's what I thought was so strange. 118 minutes of GPU time, but 14 hours of CPU time and over 30 hours of walltime... And it did report "Starting WU on GPU"
13) Message boards : Number crunching : ATI Application (Message 124)
Posted 3107 days ago by Profile Mumps [MM]
OK. I have yet to get anything to process and validate correctly on my system. The last two WU's that I grabbed took forever to run. Almost like it ran on CPU rather than GPU.

Core2-Duo laptop
ATI Mobility Radeon 3430 integrated Video
Windwos 7 Beta 64bit
Catalyst 9.6 (Only release I could find for Windows 7)
Driver package version 8.612
Collatz 1.09c package

One of the WU's that seems to have completed and validated is:
This one

Note the comments in the log:

Collatz ATI v1.09 (GPU Optimized)
CAL Runtime: 1.4.283
Found 0 CAL device

worker: trying boinc_get_init_data()...
No free GPU! Waiting ... 0 seconds.
Starting WU on GPU 15466840
Beginning processing...

It completed and reported 50,454 seconds of runtime, but the work log reports it only took 7,090 seconds of GPU time. Any thoughts on it?
14) Message boards : Number crunching : ATI Application (Message 41)
Posted 3111 days ago by Profile Mumps [MM]
Oh well. I have to agree here. My Windows 7 x64 host doesn't like 1.08 either. But then, it didn't have any luck with any of the earlier releases either...
15) Message boards : Number crunching : Credit (Message 26)
Posted 3117 days ago by Profile Mumps [MM]
So, any thoughts on what's happening with my ATI Cruncher? Everything it returns seems to me to finish way to quickly, but there's nothing in the output to help me figure out if it's just a broken Brook install or something else.

The ATI results have yet to validate at all... Only those you manually granted credit for it seems...

Host


I see it is running Windows 7 x64. Anyone else gotten any WUs to validate using Windows 7?

What kind of ATI card is it?

It's an integrated Mobility Radeon HD 3430 on my laptop

What version of the ATI driver are you using?

The Beta drivers for Win 7. Catalyst 9.6 (The only ones available for D/L)

Have you copy and renamed the 3 ATI DLLs to AMD?

Yup. Couldn't get even this far without that. :-)

Has it run MW ATI workunits OK?

Being a 3430, it won't run MilkyWay...

What version of the ATI app are you using?

The latest, 1.07.
16) Message boards : Number crunching : Credit (Message 24)
Posted 3117 days ago by Profile Mumps [MM]
So, any thoughts on what's happening with my ATI Cruncher? Everything it returns seems to me to finish way to quickly, but there's nothing in the output to help me figure out if it's just a broken Brook install or something else.

The ATI results have yet to validate at all... Only those you manually granted credit for it seems...

Host




Main page · Your account · Message boards


Copyright © 2018 Jon Sonntag; All rights reserved.