380 / 390 / Fury on New Drivers - Still Getting Invalid Results for > 1 BRP6 Task?
6 Jul 2016 3:03:37 UTC
Topic 198676
(moderation:
I know I saw a post somewhere, but I can't find it so will post in a new thread -- has anyone tested the new AMD drivers released with the RX 480 to see if the "can only only do one task at a time" issue has changed on the 380, 390 and Fury series?
380 / 390 / Fury on New Drivers - Still Getting Invalid Results
)
Ask Gavin here: https://einsteinathome.org/goto/comment/140142
As I quietly announced in
)
As I quietly announced in another thread I can confirm that my 390 card is now successfully crunching and producing valid results running two tasks concurrently using Beta driver 16.6.2. The situation is still far from perfect after accruing several inconclusive results and a number of invalids but this is perhaps real progress for Hawaii owners! Previous attempts to run more than one task at once would produce immediate validate error for all work with this card.
My hope is that future drivers will improve the situation further and also fix the issues with my RX 480 card... These problems though are for a different thread.
Gav.
Thank you, Gavin. I've
)
Thank you, Gavin. I've bookmarked the system and will keep watching. Depending on how things go as more cards get released this year, I may pick up some used GPUs.
RE: Depending on how things
)
Your approach may yet pay dividends. It seems AMD's recent drivers have been evolving into something that should have been mainstream years ago and I have no plans as yet to change the operating parameters for my Hawaii machine.
For clarification purposes the card is in a PCI-e2 slot running x16 mode and GPU tasks x2 with no other project work interfering. (some of my recent results may be interspersed with tasks run at x1 concurrency and it would be fair to say I'm at fault after inadvertently reinstating my app_config file)!
I'm looking forward to others experiences testing with this driver.
Gav.
Hi, I´m still using the R9
)
Hi,
I´m still using the R9 290. With the new drivers (16.6.2) the results are still inconclusive or error out when running more than one wu at the time.
I updated the driver for my
)
I updated the driver for my 390 today to beta 16.7.2.
Initial indications are promising compared to results with the earlier driver but it is too early to make firm judgement. I will let it run 'as is' for the next day or so and if all goes well I may try for x3.
hotze33, that is disappointing and sadly I have no answer. I may be wrong (again!) but I believe there are differences between 290 and 390 series GPU's even though they are still classed as 'Hawaii', some slight tweak to the architecture may make all the difference? We will need a proper GPU guru to answer that one...
Gav.
RE: I updated the driver
)
Since updating to driver 16.7.2 it has appeared to be business as usual. As yet I have had no task produce straight error but that said, over the last couple of days my inconclusive and invalid task count has risen.
The newer drivers (I think) are still a step in the right direction but remain very far from perfect.
I have re-applied my app_config limiting tasks to x1 purely to help stop the slide in this machines RAC over the last 2 weeks or so since I started to run x2. The drop in credit appears to be quicker than the production rate of invalid daily tasks implies.
My next move is to shift the card to another machine running Linux and test using the amd_gpu-pro drivers...
I'll be back!
RE: I may be wrong (again!)
)
The chips are exactly the same. Their configuration is different (clock speeds, power limits etc.) and there's a slight difference in memory timings in favor of the newer cards. AMD has made driver based differences between such cards in the past, though, so this may not be the last word in this matter.
MrS
Scanning for our furry friends since Jan 2002
RE: My next move is to
)
Bugger. That was an hour or two wasted, should have read the amd gpu-pro release notes first! R9 390's are not supported by this driver.
Of course its now clear why but every boot attempt with the 390 installed failed at the point of reaching the desktop, the screen would go black and the keyboard became unusable.
I then spent some time messing around in the Ubuntu safe mode options. I can't describe exactly what I did because I didn't really know what I was doing (other than clutching at straws). However I did manage to glean a snippet of information which my be useful to those that know Linux. I ran some sort of debug feature (sorry, I know that's vague) and was presented with a dialogue box warning that Plasma (presumably the desktop environment?) failed to start or would be closed due to an unsupported OpenGL device - obviously that's my 390 - I only mention all this as somebody may know of a workaround in the absence of official AMD support for older GPU's in the new Linux drivers.
RE: RE: My next move is
)
See this thread Ubuntu 16.04 LTS Is Deprecating AMD's fglrx (Catalyst) (released this month)
Mesa will be your only option, or 14.04 and fgrlx.
Edit: I knew I had seen a discussion about older cards see Phoronix article about older AMD GPUs and Vulkan