_mat_
-
Posts
1003 -
Joined
-
Last visited
-
Days Won
41
Content Type
Profiles
Forums
Events
Blogs
Posts posted by _mat_
-
-
I have debugged this issue and Intel OpenCL drivers are not compatible with Core2Duos and Core2Quads anymore - at least with the drivers version 15.1 and 14.2. It might work with older versions of the SDK, but they are simply not available on the internet.skulstation -I wonder, what to do, when GPUPI just output the message "Could not start worker thread" ...
Btw, if you want to downgrade the Intel OpenCL drivers you have to manually delete the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Intel\OpenCL
Otherwise the installer will tell you that there is already a higher version installed, even if you have uninstalled it.
But there is a solution: The AMD OpenCL drivers that are automatically installed with the Catalyst drivers DO WORK with these old Intel CPUs. Just go with them, it will work. You might have to plug in an AMD card to be able to install the Catalyst drivers though.
-
lanbonden, the problem is with your OS timer. Have a look at your HPET frequency, it's way out of bounds. Seems like QueryPerformanceFrequency() returns a very wrong value on XP, that GPUPI can't handle at all. Which SP of XP is this? I will have to look into that.
A quick solution for you: Disable your HPET timer in the BIOS and it should automatically fall back to RTC.
-
Then it's a driver issue, because the latest GPUPI has no changes in this regard.HD 4800 should work just fine. Well, at least it did when using older GPUPI 2.0. http://hwbot.org/submission/2830026_havli_gpupi___1b_radeon_hd_4870_16min_54sec_963msMaybe I'll try it again tomorow with latest GPUPI version.
skulstation, I will have a look at OpenCL initialization on these old CPUs. Maybe there is a compatibility issue with certain parameters when creating the context.
-
Nice one! Congrats!
-
Desktop with Haswell-E and Windows 8 install with upgrade to 8.1.
Well, it doesn't matter anyway, because we can not rely on any Windows version that QPC is handled by the HPET. The same goes for Windows 7, but we can rely on RTC there, which can not be skewed. That problem only exists in W8.
Has anybody tried RTC on Windows 10? I assume it has the same problems as 8, but we should test it. If Microsoft solved the problem, depending on the timer used, a few benchmarks could be allowed. And GPUPI can fallback on RTC as well.
Edit: My copy is currently on its way, I will test it as soon as I've installed it.
-
It could depend on the hardware/drivers that are installed, like it is the case for Windows 7.ofc it is enabled by default but it is not by default the default/main timerOn my system it was enabled by default and used as the primary timer by QueryPerformanceCounter().
-
Although double precision was introduced with the HD 4800 series, it seems like it still does not support it via OpenCL. Maybe it's only a driver bug, but I don't think that the double precision extension was ever implemented for it. I remember these times, OpenCL was not around when the RV770 was launched in 2008 and also after it's first draft in August 2009 it took a while to catch on. Back then ATI/AMD had its own GPGPU languages like Brook and CTM (Close-To-Metal) ... both are no longer supported by the AMD Stream SDK.
So I guess you are out of luck with those graphics cards.
Btw, I have not given up on the idea to replace double precision with an float emulation mode yet. Let's see what the future brings.
-
A classic rookie mistake.
damn that was a typo. Was LN2 ofc
:celebration:
-
It's normally enabled by default in Windows 8 as well.
-
Clarkdale on LHe? WTF, Roman ... so awesome! Any pictures of the session? Would love to share them!
-
We will have a look at it, thanks.
-
Have a good one, guys!
:celebration:
-
- Legacy version will be compiled with CUDA 6.5 (so GTX 200 series should work again)
- Improvements to HWBOT submission: Progress bar for online submission, possibility to cancel the process any time, timeout of 30 seconds for reaching the HWBOT servers (in case they are down)
- Way better name for the data file (ie: GPUPI_1B_20.134s.result)
- Some minor bugfixes as well
- Legacy version will be compiled with CUDA 6.5 (so GTX 200 series should work again)
-
It's a debug result, just ignore it. Couldn't delete the submission myself, I don't know why.
Btw, I am currently working on GPUPI 2.1.3.
-
GPUPI on a tablet? Who would have thought ... awesome!
-
Sorry for the delay, just came back from my vacation.
Errors like these indicate a malformed file or an errornous upload. The submission files are very sensitive because of their encryption. As the browser switch solved your problem I would guess a browser extension got in the way.
-
Awesome score! Congrats, Roman.
-
Not true. GPUPI is just not memory bandwidth limited especially on GPUs where memory is already very fast. It's like SuperPi 1M if you would like to compare them. But you shouldn't because these two benches are very different in its core. GPUPI has its own tweaks in hardware and software but like for every benchmark out there it depends on the bottlenecks to get the most efficieny.
But I get what you mean. GPUPI relies on another API+driver layer, like 3D benchmarks with DX and GPU driver. That adds another level of tweaking as well that should be used of course.
-
Parallel computations like in GPUPI can not be validated during a run. The result is an accumulation of billions of smaller partial results, that have been crunched by each core.
-
havli, as far as I can see it threads and blocks are not the problem here. In the legacy version for CUDA 6.0 my own code decides the occupancy of the GPU, because there is no kernel analyzer function in this version of the CUDA toolkit. Starting with 6.5 such a function was introuduced in CUDA and therefor it is used in GPUPI.
The problem here is more likely some bug in the CUDA implementation. Like some really small issue with a double precision function.
ls, as said in my pn this is related to stability of your system and not a bug.
-
Thanks for your report! Try 1M and let me know if it's working. The result is invalid because the kernels can not be executed anymore after a certain point. I might have to look at this problem closer.
Btw, GPUPI 1.4 uses CUDA 6.5, GPUPI 2.1 uses 6.0. I thought I could improve backwards compatibiltiy with 6.0 by supporting Compute Capabilty 1.2. But these old versions won't allow double precison anyway. Well, I might switch back to CUDA 6.5 for the legacy version, which should fix this problem too.
-
Hello fellow overclockers!
I took us some time but last Monday we finally delivered the donations to St. Anna Kinderspital! Turrican's family was with us to hand over no less than 1200 Euro! I wanted to let you know, that they are very grateful for all you guys showing your love and respect for him. Thanks for each and every donation, it wouldn't have been possible without you!
You can see Turrican's family on the right side, his parents and his two lovely sisters. Btw, his father looks almost exactly like Karl.
We published a little news (in German), you can find it here: https://www.overclockers.at/news/spendenuebergabe-im-andenken-an-unseren-turrican
-
I've just updated GPUPI to version 2.1.2. It's a minor release that fixes the detection of AMDs Furys and R9 300 graphics cards.
If you have any problems with the release, just let me know. Btw, this is not a mandatory release, all versions >= 2.1 will work for submission.
Downloads: GPUPI 2.1.2 (1.06 MB, CRC-32: CB9069F2) | GPUPI 2.1.2 - Legacy Version (Windows XP, GeForce 200 series, 590 KB, CRC-32: 1497D087)
-
So close to beating the 3 minutes with 6 cores! Keep pushing!
GPUPI - SuperPI on the GPU
in Benchmark software
Posted
You can install the AMD APP SDK as well, it should work without an AMD graphics card.
Btw, the graphics card is only needed to be able to install the Catalyst drivers. Otherwise the installation quits because there is "no supported hardware" found on the system.