Hello,
I've been happily crunching units on my laptop (Dell Precision M6500 with ATI Firepro M7820) until I updated my Catalyst drivers to the latest certified ones. Since then every unit has failed to start and I've now got a huge list.

I don't want to roll back because the current drivers are more stable for my own work - do I have any options? I have already tried the latest stable BOINC.
Thanks!
Miles

---

BOINC doesn't add things as OpenCL, only the GPU manufacturer's drivers do that. The only thing that BOINC does is take those drivers and detect the capabilities of the GPU.

So your only options are:
- return to drivers with the correct OpenCL component included;
- set Seti@home not to use the ATI GPU (in project preferences);
- continue like this and hope that Seti sends its hybrid (CAL) application.

---

 
http://www.hal6000.com/seti/boinc_ati_gpu_cheat_sheet.htm

You seem to use driver equal to Catalyst 11.11 now (driver: 1.4.1607):
http://setiathome.berkeley.edu/show_host_detail.php?hostid=6628579

... and back on 14 Oct 2014 - your last Valid task for AstroPulse v6:
http://setiathome.berkeley.edu/result.php?resultid=3783631857

Driver version: CAL 1.4.1607 (VM)
Version: OpenCL 1.1 AMD-APP-SDK-v2.5 (793.1)


For AstroPulse v7 and SETI@home v7 you need at least SDK-v2.6 (Catalyst 11.12)
(You may try to install only OpenCL.msi from a newer package)


It's terrible that Dell's "latest" have 'Release date 18 Aug 2010' (what means 'Last Updated 05 Mar 2014'? - is this for the file or just the web page?)
http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=R278596&fileId=2731114132&osCode=WW1&productCode=precision-m6500&languageCode=EN&categoryId=VI


ON YOUR RISK: You may try to find this file:
https://www.google.com/#q=%22AMD-APP-SDK-v2.6-Windows-64.exe%22

Check the 'Digital Signature' to make sure the file is not changed (have to be signed by ATI Technologies)

 

---

 


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

Hey guys...I have read what I could on this topic but still need some clarification if I can get it.

Running a HP Pavilion DV7 (only run Seti in BOINC) with a Radeon 7470M HD card. There have no graphic updates to this machine. The on board drivers are AMD 8.882.2.3000 dated 9/30/2011. Seti has run everything flawlessly since the machine was new two years ago. However I did the BOINC 7.4.27 (64) update yesterday and now all the AstroPulse V7 work units are giving me the "Postponded Unsupported OpenCl runtime" warning. All the non-AstroPulse work units are running fine. Also not sure how to dump Postponed units. Today I just just deleted SETI from BOINC and rejoined and it downloaded non AP units but now I see I have two more none working AP units back.

Do I need to update the drivers? (which I hate to do as this is a work machine and its its perfect as is) All the threads talk about going BACK to a working driver but there have been no updates to go back too. Also this just started once I did the BOINC update.

Help?

Tom

---

Hey guys...I have read what I could on this topic but still need some clarification if I can get it.

Running a HP Pavilion DV7 (only run Seti in BOINC) with a Radeon 7470M HD card. There have no graphic updates to this machine. The on board drivers are AMD 8.882.2.3000 dated 9/30/2011. Seti has run everything flawlessly since the machine was new two years ago. However I did the BOINC 7.4.27 (64) update yesterday and now all the AstroPulse V7 work units are giving me the "Postponded Unsupported OpenCl runtime" warning. All the non-AstroPulse work units are running fine. Also not sure how to dump Postponed units. Today I just just deleted SETI from BOINC and rejoined and it downloaded non AP units but now I see I have two more none working AP units back.

Do I need to update the drivers? (which I hate to do as this is a work machine and its its perfect as is) All the threads talk about going BACK to a working driver but there have been no updates to go back too. Also this just started once I did the BOINC update.

Help?

Tom

That was an attempt to limit errored work coming back in. It was revoked in later builds.

Try this one instead.

http://boinc.berkeley.edu/dl/boinc_7.4.35_windows_x86_64.exe

---

Welp.....

I did backup to BOINC 7.4.35 and after restarting I now get different message (on the one APV7 WU) that says "GPU Missing Waiting to Run (0.0437 CPU's + 1 AMD/ATI GPU)"

I know I have a working GPU so its not "missing" just seems the APV7 WU's cant see it (something to do with the OpenCL runtime stuff I guess)

I did try to update to the latest Radeon Catalyst(14.1) but my computer only would boot up with the Intel Display Driver so I had to backup to the current 11.1 drivers.

Anyway I guess its ok to not run the APV7 stuff and just dump Seti once in a while to get rid of them as the other WU are running fine.

Any other thoughts?

Thanks again..

Tom

---

I did backup to BOINC 7.4.35 and after restarting I now get different message (on the one APV7 WU) that says "GPU Missing Waiting to Run (0.0437 CPU's + 1 AMD/ATI GPU)"

When BOINC cannot find the GPU, you either have BOINC installed as a service, or you're missing the correct graphics card drivers. When updating drivers, never use those pushed by Windows, as these miss necessary details such as the OpenCL component. Always update from -- in this case -- AMD.

I did try to update to the latest Radeon Catalyst(14.1) but my computer only would boot up with the Intel Display Driver so I had to backup to the current 11.1 drivers.

The latest are the Omega 14.12 drivers. I found this afternoon that they may give errors with "these drivers are not digitally signed" and thus fall back to another GPU or to Windows built-in VGASave because Windows will not use drivers that are not digitally signed. Check Device Manager with the drivers installed, if there's any sign next to your AMD GPU's icon, there's a problem.

I solved the problem by reverting back to a restore point I made last night due to installing Windows updates. After reverting back, I installed Omega 14.12 directly over the older drivers in that system. That worked for me. (Although that system doesn't run BOINC, but it would be nice if it could at least use the TV at 1920x19080p instead of 1600x1200 :))

If you do not want to run AstroPulse tasks, then set that in your Seti Project preferences (edit, uncheck Astropulse v6 and v7, Update preferences). That way you don't have to download them and then abort them.

Although that wasn't the problem. APs run fine on AMD GPUs. You just need the correct BOINC installation and drivers.

---

He (Thomas Tilson) have some laptop:
"Running a HP Pavilion DV7 ... with a Radeon 7470M HD card"
http://en.wikipedia.org/wiki/HP_Pavilion_dv7

(too many models, all under name "HP Pavilion dv7")

Which means the drivers probably have to be from HP and not the 'generic' ATI AMD
(the laptop maybe have something called "switchable graphics" which complicates things)


HP Pavilion dv7 Entertainment Notebook PC series (~380 models listed)
Software & driver downloads
http://h20180.www2.hp.com/apps/Nav?h_pagetype=s-002&h_lang=en&h_cc=us&h_product=3744230&h_client=S-A-R163-1&h_page=hpcom&lang=en&cc=us

---

 


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

Which means the drivers probably have to be from HP and not the 'generic' ATI AMD

Even HP Support people in their own forums acknowledge you can install AMD's drivers without problems (example). The trick apparently is to install the AMD drivers directly over the drivers already installed, without uninstalling the previous drivers first.

When I check around on the HP website for unspecific AMD Radeon xxx GPUs, I always get on the actual physical card descriptions "Downloads for this product are not available through this website."

---

I guess the only solution to this problem is to "set Seti@home not to use the ATI GPU (in project preferences)". This problem started out of the blue for me. I'm not aware of any driver updates but I did do a BIONIC update awhile back.

That would be a reasonable conclusion if you are getting the same error message and have the same hardware and have exhausted all other troubleshooting options.