New AMD drivers... 14.6... possible speed increase?

[MTJ151]

Are due to be released today.

But it seems they have already been leaked here: http://www.overclock.net/t/1492046/amd-catalyst-14-6-leak-download-link

I've tried them out and initially thought I had a good increase while mining x11 coins. (>4mh per 280x using the new miner & new drivers).

However, I then noticed I was not getting any accepted shares and lots of HW errors. Messed around with my settings but always got HW errors.

Anyone else want to give it a go and report back?

Interestingly enough I tried mining some script and that worked... although my hashrate was lower then the 13.2 drivers... I didn't mess around with it too much to see if I could get equal/better performance with different settings.

[tuanvie]

means the new driver if there is a new setting to be done?
to get better results?

I tried mining x11 and have not been successful to date

[MTJ151]

AMD have now released the official version.

Still can't get it to mine X11 though. It gives readings of 4mh + for my 280x's but only HW errors

Anyone know why?

[Remember remember the 5th of November]

AMD have now released the official version.

Still can't get it to mine X11 though. It gives readings of 4mh + for my 280x's but only HW errors

Anyone know why?

We would have to wait for more users to test, but if it happens to everybody then AMD have screwed up their OpenCL implementation.

[MTJ151]

Thanks Remember!

If anyone wants to give it a go you can get the new official driver from:

http://support.amd.com/en-us/download

Perhaps I uninstalled the old driver incorrectly or something and the new one does actually improve hash. Please let us know how it goes if you do try it out!

Note that the new driver im referring to is 14.6. I think most people mine using 13.12. Also note that my hash went from 3.3mh using the new miner on 13.12 drivers to 3.5mh on the 14.4 drivers for x11 (with a decrease in engine speed too)... although scrypt mining lost a little hash. The 14.6 drivers were quoted to make a 25% improvement to games so I'm hoping hash will be even better then 14.4. If it actually works......

[MajidBC]

Note that the new driver im referring to is 14.6. I think most people mine using 13.12. Also note that my hash went from 3.3mh using the new miner on 13.12 drivers to 3.5mh on the 14.4 drivers for x11 (with a decrease in engine speed too)...

I'm using 280x with 14.4 drivers in Ubuntu 14.04, but just getting around 2.3 MH/s at 1100/1500. can you please tell me where I am wrong?

[MTJ151]

Im running 280x toxic's. I also have a 280x msi thats getting 3.3mh. All running on Windows 7 64x.

Using the following config for the toxics:

set PATH=%PATH%;./dlls
set TERMINFO=.\dlls\terminfo
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
del *.bin
sgminer.exe -k darkcoin -g 2 -w 256 -I 19 --thread-concurrency=8192 --gpu-engine=1150 --gpu-memclock=1600 --auto-fan --auto-gpu --gpu-powertune=-20 --gpu-vddc=1.2 --shaders 2048 -o stratum+tcp://drk.minep.it:3365 -u username.workername -p pass --temp-cutoff 80 --temp-overheat 79 --temp-target 72 --expiry 1 --scan-time 1 --queue 0
pause

For the MSi I use:

set PATH=%PATH%;./dlls
set TERMINFO=.\dlls\terminfo
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
del *.bin
sgminer.exe -k darkcoin --gpu-vddc=1.2 -g 2 -w 256 -I 19 --thread-concurrency=8193 --gpu-engine=1080 --gpu-memclock=1500 --auto-fan --auto-gpu --gpu-powertune=-20 -o stratum+tcp://drk.minep.it:3365 -u username.workername -p pass --temp-cutoff 80 --temp-overheat 79 --temp-target 72 --expiry 1 --scan-time 1 --queue 0
pause

Im also using the 2% version of SG miner from here (hence the 1st two lines of my bat file):

https://bitcointalk.org/index.php?topic=616786.0


The 2% version made my hash go from 2.3mh to 3.3mh. Then the 14.14 driver made it go up to 3.5. The new 14.6 drivers give me more then 4mh's but they are not accepted... only get HW errors.

[MajidBC]

Im running 280x toxic's. I also have a 280x msi thats getting 3.3mh. All running on Windows 7 64x.

Using the following config for the toxics:

set PATH=%PATH%;./dlls
set TERMINFO=.\dlls\terminfo
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
del *.bin
sgminer.exe -k darkcoin -g 2 -w 256 -I 19 --thread-concurrency=8192 --gpu-engine=1150 --gpu-memclock=1600 --auto-fan --auto-gpu --gpu-powertune=-20 --gpu-vddc=1.2 --shaders 2048 -o stratum+tcp://drk.minep.it:3365 -u username.workername -p pass --temp-cutoff 80 --temp-overheat 79 --temp-target 72 --expiry 1 --scan-time 1 --queue 0
pause

For the MSi I use:

set PATH=%PATH%;./dlls
set TERMINFO=.\dlls\terminfo
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
del *.bin
sgminer.exe -k darkcoin --gpu-vddc=1.2 -g 2 -w 256 -I 19 --thread-concurrency=8193 --gpu-engine=1080 --gpu-memclock=1500 --auto-fan --auto-gpu --gpu-powertune=-20 -o stratum+tcp://drk.minep.it:3365 -u username.workername -p pass --temp-cutoff 80 --temp-overheat 79 --temp-target 72 --expiry 1 --scan-time 1 --queue 0
pause

Im also using the 2% version of SG miner from here (hence the 1st two lines of my bat file):

https://bitcointalk.org/index.php?topic=616786.0


The 2% version made my hash go from 2.3mh to 3.3mh. Then the 14.14 driver made it go up to 3.5. The new 14.6 drivers give me more then 4mh's but they are not accepted... only get HW errors.

Thanks a lot. I will try them. By the way, is the 2% version safe? Have you tried the other versions like lasybear's?

[SavageWS6]

If people are getting more MH/s and more HW errors... I'm assuming there was changes or vastly updated OpenCL library. I'm not physically near my rig so I don't wanna take the chance of updating drivers 2500 miles away atm. I may try them once I go back

EDIT: Checked, guess its the same OpenCL library. Still not sure why it would introduce more HW errors

[MTJ151]

I've had no problems with the 2% version and I'm fairly sure it works as described. You can cancel the 2% fee pool by pressing 'P,C,Zero'... although I think I read that he cancelled it anyway?

I have not tried the other versions that have been made since. I read some of the threads and decided to wait a while before spending more time with it for now... since the other one works good and no1 reports improved results as far as I can see.

Re the last post:
I'm not sure if they changed anything to do with OpenCL.. They apparently made it so you could do 'eyefinity' at different resolutions (run multiple monitors for gaming at different resolutions and made it so you could change the colour between the monitors or something).

If they have changed openCL does that mean that the drivers are messged up (being beta) or does it mean the miner needs to change to allow it??

[MTJ151]

EDIT: Checked, guess its the same OpenCL library. Still not sure why it would introduce more HW errors

We need someone else to give it a whirl for us!!

[SavageWS6]

EDIT: Checked, guess its the same OpenCL library. Still not sure why it would introduce more HW errors

We need someone else to give it a whirl for us!!

I've had no problems with the 2% version and I'm fairly sure it works as described. You can cancel the 2% fee pool by pressing 'P,C,Zero'... although I think I read that he cancelled it anyway?

I have not tried the other versions that have been made since. I read some of the threads and decided to wait a while before spending more time with it for now... since the other one works good and no1 reports improved results as far as I can see.

Re the last post:
I'm not sure if they changed anything to do with OpenCL.. They apparently made it so you could do 'eyefinity' at different resolutions (run multiple monitors for gaming at different resolutions and made it so you could change the colour between the monitors or something).

If they have changed openCL does that mean that the drivers are messged up (being beta) or does it mean the miner needs to change to allow it??

haha ya I just edited my post about OpenCL not being changed. well I usually don't touch beta drivers. I can't say exactly what its doing differently (wish I could look at it and read it but I can't reverse engineer anything myself)

I'm 2500 miles away though lmao. Ya technically I could do it through teamviewer but.. If this goes south, I can't get to the rig till June 7th

[MTJ151]

I don't blame you dude... im sitting next to my rig and having problems!!

[SavageWS6]

I don't blame you dude... im sitting next to my rig and having problems!!

Damn, You using the optimized sgminrer for X11 coins? Maybe it has something to do with it coming from different driver versions.. but I really have no idea

[MTJ151]

Tried the 2% version and the latest release of sgminer I think.

[MTJ151]

Well, I'm about to give up and go back to 14.4 drivers I think! After fiddling around for a while it seems like the miner program (sgminer) does not actually change the clock speeds etc. I am watching the clock speeds using gpuz and whenever I run the miner the clocks restore to default. Perhaps this problem extends to more then just the clock speeds and in turn causing HW errors.

[hero18688]

Thanks Remember!

If anyone wants to give it a go you can get the new official driver from:

http://support.amd.com/en-us/download

Perhaps I uninstalled the old driver incorrectly or something and the new one does actually improve hash. Please let us know how it goes if you do try it out!

Note that the new 'beta' driver is 14.6. I think most people mine using 13.12. Also note that my hash went from 3.3mh using the new miner on 13.12 drivers to 3.5mh on the 14.4 drivers. The 14.6 drivers were quoted to make a 25% improvement to games so I'm hoping hash will be even better then 14.4. If it actually works......

I got 3.35mh with 14.4.How can you make it to 3.5mh?
Posted from Bitcointa.lk - #ai8hjlNeyX14nTHB

[Glizlack]

hoping for some good news here. Another speed boost would be fantastic.

Steve

[tsumeone]

After moving to 14.6 got an error starting sgminer saying my TC was too high.  Worked fine on 14.4.  Deleted bin, same error.  Decreased TC a bit, it started but all HW errors.  Going back to 14.4.  This is on reference R9 290 cards.

[MTJ151]

So the drivers are broken when it comes to mining it seems?