Message boards : News : Geforce 10 / Pascal app coming soon
Author | Message |
---|---|
hi Crunchers | |
ID: 44031 | Rating: 0 | rate: / Reply Quote | |
Will it help out the Maxwell cards? | |
ID: 44032 | Rating: 0 | rate: / Reply Quote | |
hi Crunchers Thank you. Eagerly awaiting !!! | |
ID: 44034 | Rating: 0 | rate: / Reply Quote | |
+1 My Geforce 1070 can't await it... :-) | |
ID: 44040 | Rating: 0 | rate: / Reply Quote | |
Anythoughts if this will incress GPU load percentage? I find that the GPU load is quite low compared to Folding@home. | |
ID: 44042 | Rating: 0 | rate: / Reply Quote | |
Anythoughts if this will incress GPU load percentage? I find that the GPU load is quite low compared to Folding@home. If you go back to the 359.6 driver your gpu load will rise by between 4% to 5% | |
ID: 44043 | Rating: 0 | rate: / Reply Quote | |
hi Crunchers 27 May 2016 https://www.phoronix.com/scan.php?page=news_item&px=CUDA-8-Release-Candidate https://developer.nvidia.com/cuda-toolkit ____________ 1 Corinthians 9:16 "For though I preach the gospel, I have nothing to glory of: for necessity is laid upon me; yea, woe is unto me, if I preach not the gospel!" Ephesians 6:18-20, please ;-) http://tbc-pa.org | |
ID: 44135 | Rating: 0 | rate: / Reply Quote | |
Yeah, the Release Candidate has been around for some time, but you can't legally use it in publicly available apps... | |
ID: 44138 | Rating: 0 | rate: / Reply Quote | |
Yeah, the Release Candidate has been around for some time, but you can't legally use it in publicly available apps... Judging by the time went by since then it's probably had a couple bugs to fix. I recall that there were issues even with the CUDA subsystem of released drivers in the past. | |
ID: 44141 | Rating: 0 | rate: / Reply Quote | |
It could still be used for building the code and working out some bugs in house then release the full product with very minimal testing once a bug free final CUDA 8 is released. I just don't want to see us waiting til a public official release comes out before touching it at all, which I assume is not happening anyway. | |
ID: 44155 | Rating: 0 | rate: / Reply Quote | |
That has been happening. If there were no bugs then the Cuda 8 dev kit would have already been released for public use. | |
ID: 44169 | Rating: 0 | rate: / Reply Quote | |
Bulletin for crunchers with Pascal GPU's and XP: Microsoft Windows XP/Windows XP 64-bit driver support for GeForce GPUs has been deprecated with driver branch R370_00 and onward. Driver 368.81 is the last driver to support Windows XP/Windows XP 64-bit. http://us.download.nvidia.com/Windows/372.54/372.54-win10-win8-win7-desktop-release-notes.pdf https://forums.geforce.com/default/topic/957568/geforce-drivers/official-372-54-game-ready-whql-display-driver-feedback-thread-released-8-15-16-/1/ | |
ID: 44190 | Rating: 0 | rate: / Reply Quote | |
Can we crunch with today nvidia drivers on win10 on pascal gpu ? are short run available to test ? Or only long run ? | |
ID: 44198 | Rating: 0 | rate: / Reply Quote | |
Not yet, but I'd like to ask pretty much the same thing: today driver 372.54 was released, including official CUDA 8 support. Is that enough yet? | |
ID: 44200 | Rating: 0 | rate: / Reply Quote | |
Bulletin for crunchers with Pascal GPU's and XP: I thought that this will happen. It's time for me to install Linux on one of my hosts. | |
ID: 44201 | Rating: 0 | rate: / Reply Quote | |
Still failing with 372.54 Nvidia drivers and gtx 1070/1060 | |
ID: 44207 | Rating: 0 | rate: / Reply Quote | |
Still failing with 372.54 Nvidia drivers and gtx 1070/1060 Yes, it is not the drivers on your computer that counts at this point. It is the programing of the tasks to be done on that new driver (CUDA version) needed for the new cards. NVIDIA has to complete, test, and release a bug free version (a gold version) of the CUDA SDK for GPUGRID to make the code in the project work with your card and driver. The ball on this is in the NVIDIA court currently to release that after making a version that they feel confident in releasing. Really, most companies that make an actual product makes the drivers and the SDK available to manufacturers of the products that work with their product and software companies that make software to work with that product before releasing the product and its user end drivers. In the case of this whole line of products NVIDIA seems to have done this backwards and released the product, the user drivers and not the toolkit to make products and software to use the GTX10 line of cards and the CUDA 8 platform. So until NVIDIA releases that, the tasks coming out of GPUGRID will continue to fail on these new cards. That is unless GPUGRID uses the buggy/non-gold SDK available to compile new tasks risking more failed tasks for the sake of the processing power going untapped. I would think that unless they actually release the amount of work that surpasses the need for that extra unused power in the installed cards that want to crunch GPUGRID, they should not take that risk and should just let the NVIDIA timeline dictate the use of the cards. If they can release enough work to surpass the user's current non-GTX10 cards and actually need the GTX10 cards in production, then I would say there is even a discussion to be had on the matter of taking that risk. | |
ID: 44208 | Rating: 0 | rate: / Reply Quote | |
We have received information that one important bug for us has been fixed. | |
ID: 44209 | Rating: 0 | rate: / Reply Quote | |
We have received information that one important bug for us has been fixed. great ! hoppefully long runs are not flagged as error as it was sometime the case on titan x maxwell. short runs were always ok. | |
ID: 44213 | Rating: 0 | rate: / Reply Quote | |
We have received information that one important bug for us has been fixed. Hi Gianni, How went the linux port ? | |
ID: 44278 | Rating: 0 | rate: / Reply Quote | |
Just checking in. I have a 1080 and 1070 waiting for a Windows app. They've been busy on Einstein in the meantime. | |
ID: 44322 | Rating: 0 | rate: / Reply Quote | |
Just checking in. I have a 1080 and 1070 waiting for a Windows app. They've been busy on Einstein in the meantime. Still waiting on the release of CUDA 8.5 | |
ID: 44342 | Rating: 0 | rate: / Reply Quote | |
Just checking in. I have a 1080 and 1070 waiting for a Windows app. They've been busy on Einstein in the meantime. This is worse than I've feared. A quick google search of "CUDA 8.5" gave the following two results as best match: http://www.cudabrand.com/cuda-8-5-titanium-bonded-bent-needle-nose-pliers.html http://www.cudabrand.com/cuda-8-5-titanium-bonded-dehooker.html which left me unimpressed. | |
ID: 44438 | Rating: 0 | rate: / Reply Quote | |
Still waiting on the release of CUDA 8.5 Zoltan, there has to be a "catch and release" joke in there somewhere... | |
ID: 44439 | Rating: 0 | rate: / Reply Quote | |
HAH! | |
ID: 44441 | Rating: 0 | rate: / Reply Quote | |
Just checking in. I have a 1080 and 1070 waiting for a Windows app. They've been busy on Einstein in the meantime. Speculation: CUDA 8.5 publicly available near (GP107) GTX 1050 release (October) or further down the road when (GP102) GTX 1080ti appears in early 2017 or late 2016. http://ambermd.org/gpus/benchmarks.htm CUDA 8.0 AMBER benchmarks show what we're missing in potential throughput with Pascal. For example: GTX 1070 Single job throughput equal to Maxwell Titan X or GTX 980ti. | |
ID: 44452 | Rating: 0 | rate: / Reply Quote | |
My strategy seems to work: I restricted my purchase of a latest generation Nvidia GPU to the availability of a working app for this generation on my priority project GPUGRID. The price of these cards goes in the right direction… down:-) | |
ID: 44458 | Rating: 0 | rate: / Reply Quote | |
I must be missing an important detail, but is there a reason why the GPUGRID code for NVIDIA GPUs will not run on the new Pascal cards? Is the hardware not backwards compatible that it can run older code like other projects such as Einstein or POEM which have been working without the release of CUDA 8.0/8.5 support on the 1080/1070? | |
ID: 44472 | Rating: 0 | rate: / Reply Quote | |
...is there a reason why the GPUGRID code for NVIDIA GPUs will not run on the new Pascal cards? Judging only by the error messages the app throws, it uses different libraries for different Compute Capabilities (to maximize efficiency I guess), and the one which is necessary for CC6.1 is simply not present in the CUDA6.5 code (obviously because there was no CC6.1 back then when the CUDA6.5 came out). Is the hardware not backwards compatible that it can run older code They are backwards compatible, and they could run older code. ... it can run older code like other projects such as Einstein or POEM which have been working without the release of CUDA 8.0/8.5 support on the 1080/1070? Probably the CUDA 6.5 code could be made to work on the Pascals, but when you do that, your app could be missing a significant part of the hardware improvements, thus it could be slower and/or less energy efficient than a new code. | |
ID: 44473 | Rating: 0 | rate: / Reply Quote | |
I would say better less than 100% efficient but to have at least something. | |
ID: 44474 | Rating: 0 | rate: / Reply Quote | |
I would say better less than 100% efficient but to have at least something. A fellow cruncher called the CUDA6.5 client "ancient" in another thread. Other projects go the way according to the "to have at least something" mentality, resulting in CUDA3.2, CUDA5.0, and CUDA5.5 apps. What would that fellow call those clients? This project has chosen the other way: to have state of the art app (because it's using a proprietary code provided by Acellera, so it has to be competitive). To have clients serving both mentalities requires doubled development teams, but it's gratifying to have at least one such team. Thus there always could be a group of people who can pick on the way a project goes, but I'm quite satisfied with the way this project goes, however the pace could be faster, but it's limited by 3rd party (NVidia). | |
ID: 44475 | Rating: 0 | rate: / Reply Quote | |
Hi everybody ! | |
ID: 44476 | Rating: 0 | rate: / Reply Quote | |
Excuse my "newbie" question but would it be possible that all apps be written with OpenCL in mind instead of proprietary CUDA ? That would be ideal to have all applications in OpenCL. But the acemd application is written with CUDA and there is no intention to rewrite it to OpenCL, which is not trivial task and part of it code is not open so not even possible. On the other hand some benchmarks show that OpenCL is bit slower on nvidia cards (citation-needed). ____________ | |
ID: 44489 | Rating: 0 | rate: / Reply Quote | |
Thanks, I understand your answer but "the bit slower" could be forgotten if AMD GPUs could also crunch these WUs because more GPUs crunching at the same time means that the batch is sooner finished ! | |
ID: 44501 | Rating: 0 | rate: / Reply Quote | |
Two things. | |
ID: 44513 | Rating: 0 | rate: / Reply Quote | |
Maybe this could be of interest: | |
ID: 44517 | Rating: 0 | rate: / Reply Quote | |
Yup. That would prolly be it. :-) | |
ID: 44518 | Rating: 0 | rate: / Reply Quote | |
Maybe this could be of interest: Hope that Anaconda GPUGRID distrib is not only for INTEL !!... ____________ Lubuntu 16.04.1 LTS x64 | |
ID: 44520 | Rating: 0 | rate: / Reply Quote | |
@Jihal: the last time they tried to port their code to OpenCL was probably 2-3 years ago. At that point the app was really slow. If I remember correctly the AMD GPUs were about a factor of 10 behind the "gaming equivalent" nVidias running CUDA code. Some libraries were clearly not optimized well. But worst was that they couldn't make it stable, i.e. the app would crash randomly. At that point they stopped these efforts, after having spent a few months on it I guess. Things will have improved by now, but I can understand if they're not keep on trying OpenCL again. | |
ID: 44527 | Rating: 0 | rate: / Reply Quote | |
So with the release of the CUDA 8 toolkit, we can assume support for the new cards is forthcoming very shortly? | |
ID: 44592 | Rating: 0 | rate: / Reply Quote | |
So with the release of the CUDA 8 toolkit, we can assume support for the new cards is forthcoming very shortly? http://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html Deprecated Features: •Fermi Architecture Support. Fermi architecture support is being deprecated in the CUDA 8.0 Toolkit, which will be the last toolkit release to support it. Future versions of the CUDA Toolkit will not support the architecture and are not guaranteed to work on that platform. Note that support for Fermi is being deprecated in the CUDA Toolkit but not in the driver. Applications compiled with CUDA 8.0 or older will continue to work on Fermi with newer NVIDIA drivers. •Windows Server 2008 R2 Support. Support for Windows Server 2008 R2 is now deprecated and will be removed in a future version of the CUDA Toolkit. •32-bit Linux CUDA Applications. CUDA Toolkit support for 32-bit Linux CUDA applications has been dropped. Existing 32-bit applications will continue to work with the 64-bit driver, but support is deprecated. A note about 8.0.44 toolkit: driver 369.30 (non r370 branch) is included in package which most likely allow's for Windows XP support (368.81 for XP is a CUDA 8.0 driver) if the project chooses to develop with now publicly available 8.0 toolkit. Waiting until 8.5CUDA could cease XP support completely unless a workaround is available. | |
ID: 44599 | Rating: 0 | rate: / Reply Quote | |
Seems that CUDA 8 has been released recently. Our Pascal GPUs are waiting eagerly to get off the starting blocks ;-) | |
ID: 44627 | Rating: 0 | rate: / Reply Quote | |
Seems that CUDA 8 has been released these days. Our Pascal GPUs are waiting eagerly to get off the starting blocks ;-) The Linux X64 NVidia driver 370.28 is CUDA 8.0 capable and I'm using it on my GTX TITAN Black GPU. Non Pascal GPUs could be able to crunch too with CUDA 8.0 driver ? ____________ Lubuntu 16.04.1 LTS x64 | |
ID: 44628 | Rating: 0 | rate: / Reply Quote | |
In addition yo my preceeding post about 370.28 driver : sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt-get update Yoy may then use the Synaptic packets manager to install the latest available proprietary driver from NVidia . You don't need any more a manual installation ! BOINC journal : ... CUDA: NVIDIA GPU 0: GeForce GTX TITAN Black (driver version 370.28, CUDA version 8.0, compute capability 3.5, 4096MB, 4010MB available, 6396 GFLOPS peak) ... OpenCL: NVIDIA GPU 0: GeForce GTX TITAN Black (driver version 370.28, device version OpenCL 1.2 CUDA, 6074MB, 4010MB available, 6396 GFLOPS peak) Hope this helps... ____________ Lubuntu 16.04.1 LTS x64 | |
ID: 44629 | Rating: 0 | rate: / Reply Quote | |
Seems that CUDA 8 has been released recently. Our Pascal GPUs are waiting eagerly to get off the starting blocks ;-) According to this post, we're waiting for the release of CUDA8.5, so we still have to be patient. | |
ID: 44630 | Rating: 0 | rate: / Reply Quote | |
Non Pascal GPUs could be able to crunch too with CUDA 8.0 driver ? They are working with CUDA8.0 driver, however on Windows systems it seems to be slower than the latest CUDA7.5 driver (359.06). | |
ID: 44631 | Rating: 0 | rate: / Reply Quote | |
hi Crunchers Still waiting on the release of CUDA 8.5 So we need clarification then. Which were we waiting on? ____________ 1 Corinthians 9:16 "For though I preach the gospel, I have nothing to glory of: for necessity is laid upon me; yea, woe is unto me, if I preach not the gospel!" Ephesians 6:18-20, please ;-) http://tbc-pa.org | |
ID: 44633 | Rating: 0 | rate: / Reply Quote | |
Cripes! My new 1070 and 1080 are bored beyond belief. So I have to redeploy them at Folding@Home for a while. Too bad that I pensioned my 980 off recently :-( | |
ID: 44636 | Rating: 0 | rate: / Reply Quote | |
They definitely said CUDA 8.5 - it's right in this thread. My GTX 1060 is off to Folding@Home, too, since POEM quit a few days ago. | |
ID: 44644 | Rating: 0 | rate: / Reply Quote | |
They definitely said CUDA 8.5 - it's right in this thread. My GTX 1060 is off to Folding@Home, too, since POEM quit a few days ago. Makes you wonder as to the value of some projects when they QUIT! Doesn't it? | |
ID: 44646 | Rating: 0 | rate: / Reply Quote | |
.....since POEM quit a few days ago.... Ah, but in reality you should be quite curious as to WHY they quit. Pretty exciting, although sad to lose a favorite project without much notice. | |
ID: 44647 | Rating: 0 | rate: / Reply Quote | |
.....since POEM quit a few days ago.... No, I don't because as they say on their site they now have enough computational resources to do what the need without out you. So thank you for eight years and P***s O** Or to translate: We now have no need for "something for nothing" If GPUGrid goes the same way I'm out for good after 16 years+ BOINC has ultimately proven good only for unfunded projects to exist to some extent until proven to be worthy of funding so BOINC will go on to be a massive waste of our resources in order to preserve theirs. I am still around for GPUGrid so hope to be proved wrong! | |
ID: 44648 | Rating: 0 | rate: / Reply Quote | |
Makes you wonder as to the value of some projects when they QUIT! Doesn't it? So, POEM was of questionable value or not? LOL. Sorry to be a thorn in your side, well, not really, I like poking people a bit. :D I do fully understand your frustration, though. We donate freely, in hopes of real breakthroughs, and longer/better lives for all mankind, and then those real breakthroughs seem to get patented and cost $100 to $50,000 per dose. Ain't right. | |
ID: 44649 | Rating: 0 | rate: / Reply Quote | |
BOINC has ultimately proven good only for unfunded projects to exist to some extent until proven to be worthy of funding so BOINC will go on to be a massive waste of our resources in order to preserve theirs. They have funding for researchers (student or otherwise) and servers. If they had funding for big computers, they wouldn't need BOINC, or us. But most of them will publish papers and never get funded beyond that. Whether that is worthwhile depends on the project. I consider some of them a waste of electricity. Others are studies that are very basic, long before the commercial stage, but could be very important eventually. | |
ID: 44650 | Rating: 0 | rate: / Reply Quote | |
Hi all ! | |
ID: 44651 | Rating: 0 | rate: / Reply Quote | |
[OT] When science is performed by corporations the objective is profit, not cure. | |
ID: 44652 | Rating: 0 | rate: / Reply Quote | |
Sorry for OT but I really dont understand some aspects...
Yes, and the problem is? They have money now, they will publish their work done with BOINC, now you can support scientists who does not have enough funding. Isn't that a sincere and good approach?!
I'm so confused... For some projects it is true, and again - what is your problem with that? That is a proof that work done with BOINC was interesting, useful and worth of support. Support of not only a bunch of nerds like you and me, with computers who usually don't even know exactly what they are actually crunching, but also support of people and institutions with (really) big money and influence. Thats great, not bad. I am still around for GPUGrid so hope to be proved wrong! If GPUGRID would for some reason get IDK, NASA support with enough power to thank us I will be very happy. Of course, it's sad to "lose" a project but dont get irrational. | |
ID: 44653 | Rating: 0 | rate: / Reply Quote | |
The POEM forum is open if you want to continue the discussion there. | |
ID: 44654 | Rating: 0 | rate: / Reply Quote | |
To other Admins & Mods: I unlocked the thread because I see no reason to lock it. If this is wrong from your point of view, feel free to lock it again but please provide some message here. | |
ID: 44731 | Rating: 0 | rate: / Reply Quote | |
Hey, | |
ID: 44748 | Rating: 0 | rate: / Reply Quote | |
I noticed today that I've had two separate replication _3 long tasks issued. Fields for NVIDIA GPU apps which would do the trick. | |
ID: 44749 | Rating: 0 | rate: / Reply Quote | |
... perhaps you could consider excluding Pascal GPUs from work allocation for the time being? +1000 | |
ID: 44753 | Rating: 0 | rate: / Reply Quote | |
I am getting some work units but they error out immediately: <core_client_version>7.6.22</core_client_version> <![CDATA[ <message> (unknown error) - exit code -59 (0xffffffc5) </message> <stderr_txt> # GPU [GeForce GTX 1070] Platform [Windows] Rev [3212] VERSION [65] # SWAN Device 0 : # Name : GeForce GTX 1070 # ECC : Disabled # Global mem : 4095MB # Capability : 6.1 # PCI ID : 0000:01:00.0 # Device clock : 1683MHz # Memory clock : 4004MHz # Memory width : 256bit # Driver version : r370_00 : 37306 #SWAN: FATAL: cannot find image for module [.nonbonded.cu.] for device version 610 </stderr_txt> ]]> | |
ID: 44778 | Rating: 0 | rate: / Reply Quote | |
I am getting some work units but they error out immediately: It's because the GPUGrid app does not support Pascal GPUs yet. | |
ID: 44784 | Rating: 0 | rate: / Reply Quote | |
I'm curious why F@H supports Pascal GPUs just fine but GPUGRID doesn't? | |
ID: 44785 | Rating: 0 | rate: / Reply Quote | |
Pascal also works just fine at every other DC project that I know, with CUDA 8.0 driver. However, GPU-Grid targets CUDA 8.5 for the next app and is waiting for its release. We don't know what CUDA 8.5 offers them beyond what CUDA 8.0 already provides. | |
ID: 44786 | Rating: 0 | rate: / Reply Quote | |
FAH uses OpenCL, not CUDA, so the same WUs can run on any card. | |
ID: 44791 | Rating: 0 | rate: / Reply Quote | |
But there's no answer here why 8.5 is needed vs another version from what I've seen. I think MJH said (or implied) earlier that the bug they needed fixed was not fixed in CUDA 8.0, as they had originally hoped, but won't be implemented until CUDA 8.5. There seems to be no speculation on when that will be released, so Nvidia must keep a tight leash on their developers. | |
ID: 44794 | Rating: 0 | rate: / Reply Quote | |
Poem@home being stopped, I think GPUGRID will get much more GPU power if available for Pascal. | |
ID: 44807 | Rating: 0 | rate: / Reply Quote | |
I've recognized too, they stopped some weeks ago. I had been running Poem on my 1070 for the last month, waiting for GPU grid to support Pascal. Now, it's doing Seti. | |
ID: 44815 | Rating: 0 | rate: / Reply Quote | |
There are speculations (on other projects [not BOINC, but development on projects like Debian/Ubuntu releases and such]) that the new branch of GCC was supposed to be supported in CUDA 8 and then it was put on speculation as Q1 2017. Could that be the answer we are looking for and can't get? Are we waiting on the GCC6 support with CUDA 8+? If so, the Q1 2017 speculation and a release of CUDA is speculated to follow that in short order just like the original GCC6 had the CUDA 8 release within about 20 days after realizing it was not going to have that support. Does BOINC, or some other component of what we are doing, like the MD/ACEMD rely on GCC support and to upgrade to the new architecture of NVIDIA GPUs in a "perfect world moving forward release" capacity, we need a CUDA 8 (or better) with GCC6 (or better) support? | |
ID: 44820 | Rating: 0 | rate: / Reply Quote | |
Hello, Mike: There are speculations (on other projects [not BOINC, but development on projects like Debian/Ubuntu releases and such]) that the new branch of GCC was supposed to be supported in CUDA 8 and then it was put on speculation as Q1 2017. Could that be the answer we are looking for and can't get? Are we waiting on the GCC6 support with CUDA 8+? If so, the Q1 2017 speculation and a release of CUDA is speculated to follow that in short order just like the original GCC6 had the CUDA 8 release within about 20 days after realizing it was not going to have that support. Does BOINC, or some other component of what we are doing, like the MD/ACEMD rely on GCC support and to upgrade to the new architecture of NVIDIA GPUs in a "perfect world moving forward release" capacity, we need a CUDA 8 (or better) with GCC6 (or better) support? | |
ID: 44821 | Rating: 0 | rate: / Reply Quote | |
John, this is surely not the place for the question, but since you asked, I'll answer. | |
ID: 44827 | Rating: 0 | rate: / Reply Quote | |
we will have support for Pascal very soon, in a matter of days. | |
ID: 44851 | Rating: 0 | rate: / Reply Quote | |
we will have support for Pascal very soon, in a matter of days. This is good news. Could you share more details about the new app? What CUDA / driver version will be needed for it? The old apps (CUDA60 & CUDA65) will still be available after the new app is released? Will it work on older cards? Will it work on older OS? (especially Windows XP - but I guess it depends on the driver) For what OSes will it be available? (I guess it will come out for Linux first) | |
ID: 44853 | Rating: 0 | rate: / Reply Quote | |
we will have support for Pascal very soon, in a matter of days. Very good news! Time to start reducing my cache of Einstein tasks. | |
ID: 44854 | Rating: 0 | rate: / Reply Quote | |
we will have support for Pascal very soon, in a matter of days. Sweet! Now is finally the time to start looking into the cards available to upgrade.... but need to get my pcs stable!!! (my seeming constant struggle I keep losing) | |
ID: 44858 | Rating: 0 | rate: / Reply Quote | |
we will have support for Pascal very soon, in a matter of days. What's wrong with the PC? ____________ Cruncher/Learner in progress. | |
ID: 44859 | Rating: 0 | rate: / Reply Quote | |
we will have support for Pascal very soon, in a matter of days. Any recent change in the server scheduling for Pascal (also with Maxwell) blacklisting? Unable to download tasks during last couple days on my (2) GTX 1070 / (1) GTX 1060 / (2) GTX 970 / (1) 384core GT 630 system. Windows 8.1 refuses to see more than 4 GPU's since r370 branch (including r375). As of late a couple of 7/8 GPUs Window 10 (enterprise) were on the performance page. | |
ID: 44860 | Rating: 0 | rate: / Reply Quote | |
What are we waiting for at this point? The developer of your software to update to the new Cuda? | |
ID: 44862 | Rating: 0 | rate: / Reply Quote | |
What are we waiting for at this point? The developer of your software to update to the new Cuda? | |
ID: 44863 | Rating: 0 | rate: / Reply Quote | |
What are we waiting for at this point? The developer of your software to update to the new Cuda? Our Windows app has until now been built as a 32bit Windows XP application. CUDA 8 has dropped support for this platform, so we are having to move to a 64bit Windows 7 development platform. This is causing some problems, but it should be done in a while. | |
ID: 44865 | Rating: 0 | rate: / Reply Quote | |
Hi Matt, | |
ID: 44867 | Rating: 0 | rate: / Reply Quote | |
Hi Matt, To spoil my next post -- If you have a Pascal GPU you will need driver 360+, Windows 7 and 64bit. Older GPUs will keep the current 65 app. | |
ID: 44868 | Rating: 0 | rate: / Reply Quote | |
Okay thank you | |
ID: 44917 | Rating: 0 | rate: / Reply Quote | |
FAH uses OpenCL, not CUDA, so the same WUs can run on any card. What are the pluses and minuses in using OpenCL over CUDA? Or was that already posted somewhere in this form? | |
ID: 44942 | Rating: 0 | rate: / Reply Quote | |
When you will support Pascal GPU on Linux hosts? | |
ID: 44989 | Rating: 0 | rate: / Reply Quote | |
Testing should start next week, or the following week (depending on Matt's availability and results testing on Windows). | |
ID: 44992 | Rating: 0 | rate: / Reply Quote | |
Hello, | |
ID: 45018 | Rating: 0 | rate: / Reply Quote | |
Until the app arrive, I chrunch for PimeGrid. You can have another try now, as the version 9.14 app is working fine. Your host was running the previous versions, which weren't working. | |
ID: 45030 | Rating: 0 | rate: / Reply Quote | |
Just checking in. I have a 1080 and 1070 waiting for a Windows app. They've been busy on Einstein in the meantime. Well, in the light of yesterday's events, could you please explain this post? | |
ID: 45031 | Rating: 0 | rate: / Reply Quote | |
Good morning, | |
ID: 45034 | Rating: 0 | rate: / Reply Quote | |
I understand that Fermi GPU are out of support with GPUGRID, is it true ? Basically yes. There are some batches which will work on Fermi cards, but question which batches are these can be answered only by experience (=there will be a lot of failed workunits on Fermi GPUs). Fermi cards have so poor energy efficiency compared to recent generations that they are rather not recommended. EDIT: I've found a host with a working GTX 480, here's its tasklist EDIT2: Host 176489 with a working GTX 480, its tasklist EDIT3: Host 205349 with a working GTX 480, its tasklist | |
ID: 45047 | Rating: 0 | rate: / Reply Quote | |
Host 158961 with a working GTX 580, its tasklist | |
ID: 45048 | Rating: 0 | rate: / Reply Quote | |
Just throwing it out there but you can look on my 2nd PC as well that has a GTX 460. | |
ID: 45049 | Rating: 0 | rate: / Reply Quote | |
Hello, | |
ID: 45058 | Rating: 0 | rate: / Reply Quote | |
I have a GTX 1060 card and noticed that the server sends both cuda65 and cuda80 tasks to my machine. The cuda65 tasks obviously won't run due to the well known incompatibility issue. This is a waste of perfectly good WUs (which are hard to come by anyway). Is there something I can do to prevent getting cuda65 tasks? | |
ID: 45844 | Rating: 0 | rate: / Reply Quote | |
I have a GTX 1060 card and noticed that the server sends both cuda65 and cuda80 tasks to my machine. The cuda65 tasks obviously won't run due to the well known incompatibility issue. This is a waste of perfectly good WUs (which are hard to come by anyway). Is there something I can do to prevent getting cuda65 tasks? Hmm, I do not know why it would be sending you those but for now I would check the WUs and abort the cuda65 WU as this allows someone else with the appropriate hardware to grab it. | |
ID: 45857 | Rating: 0 | rate: / Reply Quote | |
I have a GTX 1060 card and noticed that the server sends both cuda65 and cuda80 tasks to my machine. The cuda65 tasks obviously won't run due to the well known incompatibility issue. This is a waste of perfectly good WUs (which are hard to come by anyway). Is there something I can do to prevent getting cuda65 tasks? What version of Linux and what driver are you using? Have you upgraded your GPU or driver? ____________ FAQ's HOW TO: - Opt out of Beta Tests - Ask for Help | |
ID: 45878 | Rating: 0 | rate: / Reply Quote | |
I am running openSUSE 42.1 with the 375.20 driver. The card is new. | |
ID: 45879 | Rating: 0 | rate: / Reply Quote | |
I am running openSUSE 42.1 with the 375.20 driver. The card is new. It's also worth noting that you're using BOINC v7.2.42, which is getting quite elderly (released ~ 28-Feb-2014). It's possible that version may not report all the card and driver information required for the server to make a proper allocation, especially with such a new card. But I haven't checked that yet. | |
ID: 45883 | Rating: 0 | rate: / Reply Quote | |
Boinc v7.2.42 is still the recommended version. It detects the card correctly, so there is no reason it should not be able to report this to the server: 15-Dec-2016 21:47:50 [---] CUDA: NVIDIA GPU 0: GeForce GTX 1060 3GB (driver version unknown, CUDA version 8.0, compute capability 6.1, 3036MB, 2931MB available, 6167 GFLOPS peak) 15-Dec-2016 21:47:50 [---] OpenCL: NVIDIA GPU 0: GeForce GTX 1060 3GB (driver version 375.20, device version OpenCL 1.2 CUDA, 3036MB, 2931MB available, 6167 GFLOPS peak) The string "driver version unknown" is surprising, especially since it does detect it correctly on the openCL line, but the card version and compute capability information is there... | |
ID: 45887 | Rating: 0 | rate: / Reply Quote | |
7.6.31 is the recommended version for Linux, if that's the issue (the app reads the driver directly at GPUGrid). It's likely in the repository, if you installed Boinc that way. | |
ID: 45888 | Rating: 0 | rate: / Reply Quote | |
Merry Christmas everybody ! sudo add-apt-repository ppa:graphics-drivers/ppa See this link for details : http://www.omgubuntu.co.uk/2015/08/ubuntu-nvidia-graphics-drivers-ppa-is-ready-for-action Currently running with 370.28 Hope this helps... ____________ Lubuntu 16.04.1 LTS x64 | |
ID: 45890 | Rating: 0 | rate: / Reply Quote | |
7.6.33 is the recommended version for Linux, if that's the issue (the app reads the driver directly at GPUGrid). I think you are confused with Windows there. The recommended version for Linux is 7.2.42. I am sure the app communicates directly with the driver, but by then it is too late. The server decides the app version, and the cuda65 app cannot handle my hardware. Alternatively, there might be an issue with that 375 driver. I don't see any issues with the driver so far. It seems to be fine. The server decides to send tasks for the wrong version of the app to me. That is where the problem is. | |
ID: 45897 | Rating: 0 | rate: / Reply Quote | |
7.6.33 is the recommended version for Linux, if that's the issue (the app reads the driver directly at GPUGrid). If you are looking at the Berkeley page (which doesn't get much attention these days), the recommended version is 7.2.42. Using the software installer in Ubuntu Linux, I get 7.6.33. | |
ID: 45906 | Rating: 0 | rate: / Reply Quote | |
Merry Christmas everybody ! I'll 2nd that! | |
ID: 45908 | Rating: 0 | rate: / Reply Quote | |
Happy Christmas. | |
ID: 45912 | Rating: 0 | rate: / Reply Quote | |
The issue with detecting NVIDIA/CUDA driver versions on linux was fixed in BOINC 7.3.16, circa late April 2014. You must run a newer version than that (and I don't believe this fix was ever checked into the 7.2.x branch). | |
ID: 45916 | Rating: 0 | rate: / Reply Quote | |
OpenSUSE 42.1 was released in Nov 2015. Any Boinc version placed into repositories around that time would have been adapted for 42.1 from the latest Berkely versions prior to Nov 2015. However, if someone upgraded to 42.1 then I guess they might be using an even older version. openSUSE Leap 42.1 and 42.2 both ship v7.2.42, while openSUSE Tumbleweed ships v7.6.32 (but Tumbleweed is useless for running GPGPU work as the proprietary drivers would be forever breaking due to the very aggressive kernel updates). So openSUSE Leap seems to be following the Boinc recommendation. PS - it makes no difference if you installed openSUSE from scratch or upgraded from an older version, you will always get the latest version of a package in the repository (it would be too difficult to manage the security fixes otherwise). But if you installed boinc from a third-party site, then the openSUSE installer will leave that alone of course. http://www.rechenaugust.de/boinc/boinc_7.6.31_x86_64-suse-linux-gnu.sh I installed this, and so far it seems to do the trick and solve my problem. It is worrying though that I have to rely on a third-party site to get a working version of Boinc. This is not exactly what I would think linux support should look like... Thanks for the link! | |
ID: 45943 | Rating: 0 | rate: / Reply Quote | |
The Nvidia driver will register itself with DKMS (if that's installed) so that it gets rebuilt every time the machine is rebootedf with a new kernel installed. Matt | |
ID: 45968 | Rating: 0 | rate: / Reply Quote | |
The Nvidia driver will register itself with DKMS (if that's installed) so that it gets rebuilt every time the machine is rebooted with a new kernel installed. Indeed, but that will only work if the kernel is supported. If the kernel is too new, it can break the build. I fear that will happen quite a lot with Tumbleweed due to its very aggressive bleeding edge kernel support (haven't tried this, but I am pretty sure that will happen). The people at Suse themselves warn that they make no effort to keep the proprietary drivers alive in Tumbleweed. But the automatic rebuilds work quite well in openSUSE Leap. | |
ID: 45974 | Rating: 0 | rate: / Reply Quote | |
Message boards : News : Geforce 10 / Pascal app coming soon