![]() |
|
|
#639 | |
|
Nov 2010
Germany
3×199 Posts |
Quote:
Unfortunately, my first attempt to "simply port it" did not work. My GPU sieve does not work, it seems to randomly kill FCs ... I have not yet been able to debug it to see why. I had put this back a little and instead played around with 2 montgomery kernels (which are ~10% slower than the barretts as of now). And I made the kernels that are based on 15-bit math work with George's improvements to the barrett reduction. A better plan to make the best out of all the different AMD GPU generations is also on the way. So yes, I plan for GPU sieving also on OpenCL, but I can't tell when this will come. Bdot |
|
|
|
|
|
|
#640 | |
|
"Mr. Meeseeks"
Jan 2012
California, USA
23·271 Posts |
Quote:
|
|
|
|
|
|
|
#641 |
|
Oct 2011
10101001112 Posts |
With the breakthroughs on GPU sieving on the Nvidia models, is there similar work being done for the AMD GPUs?
|
|
|
|
|
|
#642 |
|
"Mr. Meeseeks"
Jan 2012
California, USA
23·271 Posts |
|
|
|
|
|
|
#643 |
|
Oct 2011
7×97 Posts |
|
|
|
|
|
|
#644 | |
|
Jun 2010
Pennsylvania
11101001102 Posts |
A few weeks ago, I posted the following:
Quote:
Now, while GPU-Z did like that and is providing additional info on the Intel HD 4000, and Device Manager says that that's working properly, still I can't get anybody to make use of it. mfakto is still giving error messages if I test using the switch -d 2, -d 02, -d 21, etc. It only ever finds two platforms and one device. So I have not yet been able to make use of the onboard graphics. Next, I'll try connecting it to a different monitor and see what happens. Rodrigo Last fiddled with by Rodrigo on 2013-01-27 at 05:57 |
|
|
|
|
|
|
#645 | |
|
Jan 2013
22·17 Posts |
Quote:
|
|
|
|
|
|
|
#646 | |
|
Nov 2010
Germany
3·199 Posts |
Quote:
does clinfo now include the HD 4000? Do you have a picture on the HD4000 (when switching the monitor to the VGA input)? Do things change, if you disconnect the cable from the real GPU before booting up? BTW, the AMD drivers should still allow you to use the HD7770, even if it is not connected. If nothing helps, you need to extract the real GPU from the system to test it ... Bdot |
|
|
|
|
|
|
#647 | |
|
Jun 2010
Pennsylvania
3A616 Posts |
The research I did last night doesn't offer a lot of hope that we can get the HD4000 to work. People are having trouble getting OpenCL to work with that iGPU:
http://communities.intel.com/message/173795#173795 http://communities.intel.com/thread/29246?tstart=0 http://communities.intel.com/message/179163#179163 http://communities.intel.com/message/176221#176221 (I don't even have a VGA port, only DVI's through either the GPU or the iGPU) http://software.intel.com/en-us/forums/topic/342698 http://software.intel.com/en-us/forums/topic/292292 That last one is from August, but according to an Intel employee -- Quote:
As a further test, I just downloaded and tried to run mfakto on the HD4000 in a new i5-3210M laptop. It doesn't find the HD4000 (the ONLY graphics installed in that computer). In fact, it didn't even find the CPU, so all -d combinations failed. We may have to give up on this idea of using both the GPU and the iGPU until the thing becomes more mature. Rodrigo |
|
|
|
|
|
|
#648 | |
|
Jun 2010
Pennsylvania
2×467 Posts |
Quote:
Nope, clinfo still isn't listing the iGPU, and switching the source to the VGA input merely gives a blank screen. Here are the next two steps I tried, and a third one: 1. Power off the computer, connect the iGPU output to an input on a separate monitor, and reboot. Result: There was no display to the separate monitor (blank screen). Not really sure if it booted into Windows.2. Power off the computer, reconnect the iGPU to the original monitor, then disconnect the output from the add-on GPU and reboot. Result: There was no display on the monitor (blank screen). I think that it did boot into Windows, though, because after reconnecting the addo-n GPU and rebooting, my Gadgets were in the middle of the screen instead of off to the right, which suggests that there was an invisible display at some lower resolution. But maybe that was simply some kind of generic low-res output, rather than actual output from the HD4000.3. Remove the add-on GPU from inside the PC case and reboot. Steps 2 and 3 are the ones you suggested. I'm hoping to avoid Step 3. (It may be rendered moot by the information in the previous post.) ![]() Rodrigo |
|
|
|
|
|
|
#649 | ||||
|
Nov 2010
Germany
3×199 Posts |
Quote:
I just hope Catalyst would at least install the OpenCL runtime, even if it does not find any AMD hardware ... Would you give it a try? Quote:
Quote:
When you have connected both GPUs to some monitor (can be the same), could you try pressing the Windows-P combination and select "Duplicate"? I think by default, windows does not automatically enable additional screens. Also, if you go the the "Screen resolution" control panel applet, does it show both GPUs? Quote:
Bdot |
||||
|
|
|
![]() |
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| gpuOwL: an OpenCL program for Mersenne primality testing | preda | GpuOwl | 2718 | 2021-07-06 18:30 |
| mfaktc: a CUDA program for Mersenne prefactoring | TheJudger | GPU Computing | 3497 | 2021-06-05 12:27 |
| LL with OpenCL | msft | GPU Computing | 433 | 2019-06-23 21:11 |
| OpenCL for FPGAs | TObject | GPU Computing | 2 | 2013-10-12 21:09 |
| Program to TF Mersenne numbers with more than 1 sextillion digits? | Stargate38 | Factoring | 24 | 2011-11-03 00:34 |