Bitcoin Forum
May 03, 2024, 07:44:47 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 [65] 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 ... 233 »
  Print  
Author Topic: [ANN] sgminer v5 - optimized X11/X13/NeoScrypt/Lyra2RE/etc. kernel-switch miner  (Read 877795 times)
badman74
Hero Member
*****
Offline Offline

Activity: 658
Merit: 500



View Profile
July 25, 2014, 08:32:06 PM
 #1281


That's funny cause 1 renter told I was selling a 4.2mh/s rig but I have 9.8mh/s.(4x7950)
At the graph at betarigs u see fluctuating hashrates but can't see that at sgminer like i saw it with xI=65.(290x)
Average is still 9.6mh/s, a bit lower than normal, but no way 4.2mh/s. Is there a tweak for flat hashrates? Decreasing intensity?

gpu-vddc is set at 0 ,because I set it with msi afterburner for testing. At github guide u should set it like "1.000"
i tried those myself...
while my hash rate went up on 1 gpu it dropped lower on the other
overall the hash rate was actually lower than i had with just I 16
also anything above 1040/1375 I 16 tends to cause my 290x's to crash
1714722287
Hero Member
*
Offline Offline

Posts: 1714722287

View Profile Personal Message (Offline)

Ignore
1714722287
Reply with quote  #2

1714722287
Report to moderator
1714722287
Hero Member
*
Offline Offline

Posts: 1714722287

View Profile Personal Message (Offline)

Ignore
1714722287
Reply with quote  #2

1714722287
Report to moderator
I HATE TABLES I HATE TABLES I HA(╯°□°)╯︵ ┻━┻ TABLES I HATE TABLES I HATE TABLES
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714722287
Hero Member
*
Offline Offline

Posts: 1714722287

View Profile Personal Message (Offline)

Ignore
1714722287
Reply with quote  #2

1714722287
Report to moderator
1714722287
Hero Member
*
Offline Offline

Posts: 1714722287

View Profile Personal Message (Offline)

Ignore
1714722287
Reply with quote  #2

1714722287
Report to moderator
1714722287
Hero Member
*
Offline Offline

Posts: 1714722287

View Profile Personal Message (Offline)

Ignore
1714722287
Reply with quote  #2

1714722287
Report to moderator
BrewCrewFan
Hero Member
*****
Offline Offline

Activity: 672
Merit: 501



View Profile
July 25, 2014, 08:34:04 PM
 #1282

Guys I have a quick question here... sure its been answered but excuse the fact this thread is many pages long....


Anyways, I have a rig with 5x 7850s in them, but sgminer 5.0 refuses to run on them. Gives me an error that is similar to the ones when you used to set the TC way to high back in the days of scrypt mining... I have even gone as far as re installing windows, reinstalling the AMD drivers to the 14.6RC still no dice.

Of course the have both setx commands and set commands in the .bat file.

The rig with the 7770 and the 260x does the same thing..... yet I think the 6950s are older but will run on SGminer 5.0.... I am lost.

Free SIGNs giving everyday. Be part, do not miss!.
SqMe5ceYfdcGsRyVpgvpYb6bRLS9j8omvB

XChat : Addy : XYuZESQpeMtZ2wit8nVVnXKGytfiaTBCo6 PubKey : eteshLzeq8Bh54BRjGSunMTc6Ytxtk7HYaSmDYMQn61z
badman74
Hero Member
*****
Offline Offline

Activity: 658
Merit: 500



View Profile
July 25, 2014, 08:41:22 PM
 #1283

Guys I have a quick question here... sure its been answered but excuse the fact this thread is many pages long....


Anyways, I have a rig with 5x 7850s in them, but sgminer 5.0 refuses to run on them. Gives me an error that is similar to the ones when you used to set the TC way to high back in the days of scrypt mining... I have even gone as far as re installing windows, reinstalling the AMD drivers to the 14.6RC still no dice.

Of course the have both setx commands and set commands in the .bat file.

The rig with the 7770 and the 260x does the same thing..... yet I think the 6950s are older but will run on SGminer 5.0.... I am lost.
need more info....
need to know what error you are getting, also need to know how your config is setup
also need to know if your MB has an onboard graphics card

edit: the 7770 and the 260x may have to be run in separate instances of sgminer
sgminer5 has a known issue with multiple card types causing problems when in the same rig

try --gpu-platform 1 on the 7850 rig if it has an onboard gpu

on the other try --remove-disabled --device 0 for the 7770 instance
and --remove-disabled --device 1 for the 260x
phishfi
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
July 25, 2014, 09:17:35 PM
 #1284

edit
I notice a hashrate drop to below 6mh/s and rise back again with xI=65.
Drop to xI=64 (6274kh/s) and is not dropping anymore.(10kh/s or so)

Edit2
As u can see the Accepted shares are calculate fine in sgminer, but the above value isn't.
Is it hard to change the above value to the value sgminer is showing with "G".?

edit3
Still stable after 3 hours.

Restarted and see if the other algos also be stable...6.346kh/s Shocked

Sigh... every time I get close someone has to leap farther ahead.   Wink

Looks like you encountered the same thing I did with the x-65/x-64 threshold. I'm running x-68 since last night, averaging 5.96 Mhash/GPU across 4 290X's over 12 hours. Stable apart from a renter trying to load dead pools for a while, LOL. I get up to around 6.17 Mhash on one of the GPU's but they keep dropping off and don't hold consistently at the highest speeds. But I'm still at 1020/1350 on the clocks so that explains much of my shortfall, I'm sure.

On scrypt I had all 4 of my GPU's individually tuned to four different engine and memory speeds for the fastest possible stable speed. I'm going to try the latest builds and settings you and badman74 helpfully shared, and then see if I can push individual GPU's higher. Thanks again!

EDIT: Dumb question - I've never messed with voltage settings before as I didn't want to fry anything. But I see in bullus' profile that he has vddc set to 0. Does that mean "go with the default setting"? As I understand it the reference voltage on a 290X is 1.0 volt. So if I wanted to try cutting that by 10%, should I put "0.9" in the vddc line, or "-0.1"?  Reading the docs would have me trying the former, but bullus' example makes me think the latter is right.

That's funny cause 1 renter told I was selling a 4.2mh/s rig but I have 9.8mh/s.(4x7950)
At the graph at betarigs u see fluctuating hashrates but can't see that at sgminer like i saw it with xI=65.(290x)
Average is still 9.6mh/s, a bit lower than normal, but no way 4.2mh/s. Is there a tweak for flat hashrates? Decreasing intensity?

http://tweakers.net/ext/f/a5NGbC2mRhfIRA2wrElkXbq5/full.png

gpu-vddc is set at 0 ,because I set it with msi afterburner for testing. At github guide u should set it like "1.000"


I don't know where he saw 4.2, especially with your average per 2 hours right where it should be. The thing about Betarigs is that the hashrate they show is just based on their readings of your rig's submitted shares. There's two things you can do, you could explain to the renter that the accepted shares will be higher if they direct the rig to a pool that's closer to your rig, or you could change no-submit-stale to false (or just delete that line). Doing that would mean that your rig would still submit stales but at least his pool will see a higher amount of total shares submitted (and that would mean a more accurate gauge of your hashrate). Another issue with betarigs is that I don't think most people are setting the difficulty properly, so there's going to be pretty wild variance on your hashrate.

I might just create a pre-build paragraph to message the renter as soon as they rent the rig to make sure that they understand all of this and to try to help them out as best I can with finding the right pool (I can test the latency to their pool and let them know if it'll be a factor for stales/rejects) and kinda guide them through setting the difficulty properly for the hashrate of the worker.
platinum4
Sr. Member
****
Offline Offline

Activity: 547
Merit: 250



View Profile
July 25, 2014, 09:32:16 PM
 #1285

Not really, renters are generally fucking stupid and some start bitching if you haven't started hashing on their pool within 2 minutes.

Last night I had a renter email me their full login info, worker name and password as well and asked me to log in and hash for them.

Fuck that.
BrewCrewFan
Hero Member
*****
Offline Offline

Activity: 672
Merit: 501



View Profile
July 25, 2014, 09:41:51 PM
 #1286

Guys I have a quick question here... sure its been answered but excuse the fact this thread is many pages long....


Anyways, I have a rig with 5x 7850s in them, but sgminer 5.0 refuses to run on them. Gives me an error that is similar to the ones when you used to set the TC way to high back in the days of scrypt mining... I have even gone as far as re installing windows, reinstalling the AMD drivers to the 14.6RC still no dice.

Of course the have both setx commands and set commands in the .bat file.

The rig with the 7770 and the 260x does the same thing..... yet I think the 6950s are older but will run on SGminer 5.0.... I am lost.
need more info....
need to know what error you are getting, also need to know how your config is setup
also need to know if your MB has an onboard graphics card

edit: the 7770 and the 260x may have to be run in separate instances of sgminer
sgminer5 has a known issue with multiple card types causing problems when in the same rig

try --gpu-platform 1 on the 7850 rig if it has an onboard gpu

on the other try --remove-disabled --device 0 for the 7770 instance
and --remove-disabled --device 1 for the 260x

Alright this is my logfile.txt when running sorry for the spam for I dont know how to do those cute little boxes you all do where you can scroll lol.....


Code:
[16:22:33] Set default algorithm to whirlcoin
[16:22:33] Global quota greatest common denominator set to 1
[16:22:33] Default Devices = 0,1,2,3
[16:22:33] set_devices(0,1,2,3)
[16:22:33] set_devices(0,1,2,3) done.
[16:22:33] Loading settings from default_profile for pool 0
[16:22:33] Pool 0 Algorithm set to "whirlcoin"
[16:22:33] Pool 0 devices set to "0,1,2,3"
[16:22:33] Pool 0 lookup gap set to "2"
[16:22:33] Pool 0 Intensity set to "18,18,18,18"
[16:22:33] Pool 0 XIntensity set to "(null)"
[16:22:33] Pool 0 Raw Intensity set to "(null)"
[16:22:33] Pool 0 Thread Concurrency set to "8192,8192,8192,8192"
[16:22:33] Pool 0 GPU Clock set to "1100,1100,1100,1100"
[16:22:33] Pool 0 GPU Memory clock set to "(null)"
[16:22:33] Pool 0 GPU Threads set to "1"
[16:22:33] Pool 0 GPU Fan set to "30-100,30-100,30-100,30-100"
[16:22:33] Pool 0 GPU Powertune set to "20"
[16:22:33] Pool 0 GPU Vddc set to "0.000"
[16:22:33] Pool 0 Shaders set to "(null)"
[16:22:33] Pool 0 Worksize set to "64"
[16:22:33] Started sgminer 4.2.2
[16:22:33] * using Jansson 2.5
[16:22:33] Loaded configuration file sgminer5.0.conf
[16:22:35] CL Platform vendor: Advanced Micro Devices, Inc.
[16:22:35] CL Platform name: AMD Accelerated Parallel Processing
[16:22:35] CL Platform version: OpenCL 1.2 AMD-APP (1526.3)
[16:22:35] Platform devices: 4
[16:22:35] 0 Pitcairn
[16:22:35] 1 Pitcairn
[16:22:35] 2 Pitcairn
[16:22:35] 3 Pitcairn
[16:22:35] Number of ADL devices: 4
[16:22:36] ATI ADL Overdrive5 API found.
[16:22:36] ATI ADL Overdrive6 API found.
[16:22:36] Found 24 logical ADL adapters
[16:22:36] ADL index 0, id -1765859840 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] GPU 0 assigned: iAdapterIndex:0 iPresent:1 strUDID:PCI_VEN_1002&DEV_6819&SUBSYS_32641682&REV_00_4&2AA7974B&0&0030A iBusNumber:4 iDeviceNumber:0 iFunctionNumber:0 iVendorID:1002 name:AMD Radeon HD 7800 Series
[16:22:36] ADL index 1, id -1765859840 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] ADL index 2, id -1765859840 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] ADL index 3, id -1765859840 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] ADL index 4, id -1765859840 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] ADL index 5, id -1765859840 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] ADL index 6, id -1924070016 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] GPU 1 assigned: iAdapterIndex:6 iPresent:1 strUDID:PCI_VEN_1002&DEV_6819&SUBSYS_32641682&REV_00_4&36AAE60&0&0010A iBusNumber:1 iDeviceNumber:0 iFunctionNumber:0 iVendorID:1002 name:AMD Radeon HD 7800 Series
[16:22:36] ADL index 7, id -1924070016 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] ADL index 8, id -1924070016 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] ADL index 9, id -1924070016 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] ADL index 10, id -1924070016 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] ADL index 11, id -1924070016 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] ADL index 12, id -1860256512 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] GPU 2 assigned: iAdapterIndex:12 iPresent:1 strUDID:PCI_VEN_1002&DEV_6819&SUBSYS_32641682&REV_00_4&3A36456B&0&0020A iBusNumber:2 iDeviceNumber:0 iFunctionNumber:0 iVendorID:1002 name:AMD Radeon HD 7800 Series
[16:22:36] ADL index 13, id -1860256512 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] ADL index 14, id -1860256512 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] ADL index 15, id -1860256512 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] ADL index 16, id -1860256512 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] ADL index 17, id -1860256512 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] ADL index 18, id -1795492608 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] GPU 3 assigned: iAdapterIndex:18 iPresent:1 strUDID:PCI_VEN_1002&DEV_6819&SUBSYS_32641682&REV_00_4&B9E949A&0&0028A iBusNumber:3 iDeviceNumber:0 iFunctionNumber:0 iVendorID:1002 name:AMD Radeon HD 7800 Series
[16:22:36] ADL index 19, id -1795492608 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] ADL index 20, id -1795492608 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] ADL index 21, id -1795492608 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] ADL index 22, id -1795492608 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] ADL index 23, id -1795492608 - BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] GPU 0 AMD Radeon HD 7800 Series hardware monitoring enabled
[16:22:36] ADL GPU 0 is Adapter index 0 and maps to adapter id -1765859840
[16:22:36] GPU 0 BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] Setting GPU 0 engine clock to 1100
[16:22:36] GPU 1 AMD Radeon HD 7800 Series hardware monitoring enabled
[16:22:36] ADL GPU 1 is Adapter index 6 and maps to adapter id -1924070016
[16:22:36] GPU 1 BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] Setting GPU 1 engine clock to 1100
[16:22:36] GPU 2 AMD Radeon HD 7800 Series hardware monitoring enabled
[16:22:36] ADL GPU 2 is Adapter index 12 and maps to adapter id -1860256512
[16:22:36] GPU 2 BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] Setting GPU 2 engine clock to 1100
[16:22:36] GPU 3 AMD Radeon HD 7800 Series hardware monitoring enabled
[16:22:36] ADL GPU 3 is Adapter index 18 and maps to adapter id -1795492608
[16:22:36] GPU 3 BIOS partno.: 113-785ZNB70.SB   , version: 015.018.000.001, date: 2013/01/02 21:30
[16:22:36] Setting GPU 3 engine clock to 1100
[16:22:36] Probing for an alive pool
[16:22:36] Testing erebor.dwarfpool.com
[16:22:36] Succeeded delayed connect
[16:22:36] Failed to get sessionid in initiate_stratum
[16:22:37] erebor.dwarfpool.com difficulty changed to 0.001
[16:22:37] Cannot subscribe to mining.extranonce on erebor.dwarfpool.com
[16:22:37] Stratum authorisation success for erebor.dwarfpool.com
[16:22:37] erebor.dwarfpool.com alive
[16:22:37] Startup GPU initialization... Using settings from pool erebor.dwarfpool.com.
[16:22:37] Startup Pool No = 0
[16:22:37] set_devices(0,1,2,3)
[16:22:37] set_devices(0,1,2,3) done.
[16:22:37] Set GPU 0 to whirlcoin
[16:22:37] Set GPU 1 to whirlcoin
[16:22:37] Set GPU 2 to whirlcoin
[16:22:37] Set GPU 3 to whirlcoin
[16:22:37] Allocate new threads...
[16:22:37] Assign threads for device 0
[16:22:37] Thread 0 set pool = 0 (erebor.dwarfpool.com)
[16:22:37] Init GPU thread 0 GPU 0 virtual GPU 0
[16:22:37] CL Platform vendor: Advanced Micro Devices, Inc.
[16:22:37] CL Platform name: AMD Accelerated Parallel Processing
[16:22:37] CL Platform version: OpenCL 1.2 AMD-APP (1526.3)
[16:22:37] Platform devices: 4
[16:22:37] 0 Pitcairn
[16:22:37] 1 Pitcairn
[16:22:37] 2 Pitcairn
[16:22:37] 3 Pitcairn
[16:22:37] List of devices:
[16:22:37] 0 Pitcairn
[16:22:37] Selected 0: Pitcairn
[16:22:37] 1 Pitcairn
[16:22:37] 2 Pitcairn
[16:22:37] 3 Pitcairn
[16:22:37] Preferred vector width reported 1
[16:22:37] Max work group size reported 256
[16:22:37] Max shaders calculated 1024
[16:22:37] Max mem alloc size is 804257792
[16:22:37] Setting worksize to 64
[16:22:37] cl_amd_media_ops found, setting BITALIGN
[16:22:37] BFI_INT patch requiring device not found, will not BFI_INT patch
[16:22:37] No binary found, generating from source
[16:22:37] Building binary whirlcoinPitcairngw64l4.bin
[16:22:37] Trying to open /usr/local/bin/whirlcoin.cl...
[16:22:37] Trying to open ./whirlcoin.cl...
[16:22:37] Trying to open ./kernel/whirlcoin.cl...
[16:22:37] Using ./kernel/whirlcoin.cl
[16:22:37] CompilerOptions: -I "." -I "./kernel" -I "." -D WORKSIZE=64 -D BITALIGN -I "/usr/local/bin"
[16:22:44] Binary size found in binary slot 0: 275752
[16:22:44] Initialising kernel whirlcoin.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[16:22:44] Creating buffer sized 536870912
[16:22:44] initCl() finished. Found Pitcairn
[16:22:44] Assign threads for device 1
[16:22:44] Thread 1 set pool = 0 (erebor.dwarfpool.com)
[16:22:44] Init GPU thread 1 GPU 1 virtual GPU 1
[16:22:44] CL Platform vendor: Advanced Micro Devices, Inc.
[16:22:44] CL Platform name: AMD Accelerated Parallel Processing
[16:22:44] CL Platform version: OpenCL 1.2 AMD-APP (1526.3)
[16:22:44] Platform devices: 4
[16:22:44] 0 Pitcairn
[16:22:44] 1 Pitcairn
[16:22:44] 2 Pitcairn
[16:22:44] 3 Pitcairn
[16:22:44] List of devices:
[16:22:44] 0 Pitcairn
[16:22:44] 1 Pitcairn
[16:22:44] Selected 1: Pitcairn
[16:22:44] 2 Pitcairn
[16:22:44] 3 Pitcairn
[16:22:44] Preferred vector width reported 1
[16:22:44] Max work group size reported 256
[16:22:44] Max shaders calculated 1024
[16:22:44] Max mem alloc size is 804257792
[16:22:44] Setting worksize to 64
[16:22:44] cl_amd_media_ops found, setting BITALIGN
[16:22:44] BFI_INT patch requiring device not found, will not BFI_INT patch
[16:22:44] Loaded binary image whirlcoinPitcairngw64l4.bin
[16:22:44] Initialising kernel whirlcoin.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[16:22:44] Creating buffer sized 536870912
[16:22:44] initCl() finished. Found Pitcairn
[16:22:44] Assign threads for device 2
[16:22:44] Thread 2 set pool = 0 (erebor.dwarfpool.com)
[16:22:44] Init GPU thread 2 GPU 2 virtual GPU 2
[16:22:44] CL Platform vendor: Advanced Micro Devices, Inc.
[16:22:44] CL Platform name: AMD Accelerated Parallel Processing
[16:22:44] CL Platform version: OpenCL 1.2 AMD-APP (1526.3)
[16:22:44] Platform devices: 4
[16:22:44] 0 Pitcairn
[16:22:44] 1 Pitcairn
[16:22:44] 2 Pitcairn
[16:22:44] 3 Pitcairn
[16:22:44] List of devices:
[16:22:44] 0 Pitcairn
[16:22:44] 1 Pitcairn
[16:22:44] 2 Pitcairn
[16:22:44] Selected 2: Pitcairn
[16:22:44] 3 Pitcairn
[16:22:44] Preferred vector width reported 1
[16:22:44] Max work group size reported 256
[16:22:44] Max shaders calculated 1024
[16:22:44] Max mem alloc size is 804257792
[16:22:44] Setting worksize to 64
[16:22:44] cl_amd_media_ops found, setting BITALIGN
[16:22:44] BFI_INT patch requiring device not found, will not BFI_INT patch
[16:22:44] Loaded binary image whirlcoinPitcairngw64l4.bin
[16:22:44] Initialising kernel whirlcoin.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[16:22:44] Creating buffer sized 536870912
[16:22:44] initCl() finished. Found Pitcairn
[16:22:44] Assign threads for device 3
[16:22:44] Thread 3 set pool = 0 (erebor.dwarfpool.com)
[16:22:44] Init GPU thread 3 GPU 3 virtual GPU 3
[16:22:44] CL Platform vendor: Advanced Micro Devices, Inc.
[16:22:44] CL Platform name: AMD Accelerated Parallel Processing
[16:22:44] CL Platform version: OpenCL 1.2 AMD-APP (1526.3)
[16:22:44] Platform devices: 4
[16:22:44] 0 Pitcairn
[16:22:44] 1 Pitcairn
[16:22:44] 2 Pitcairn
[16:22:44] 3 Pitcairn
[16:22:44] List of devices:
[16:22:44] 0 Pitcairn
[16:22:44] 1 Pitcairn
[16:22:44] 2 Pitcairn
[16:22:44] 3 Pitcairn
[16:22:44] Selected 3: Pitcairn
[16:22:44] Preferred vector width reported 1
[16:22:44] Max work group size reported 256
[16:22:44] Max shaders calculated 1024
[16:22:44] Max mem alloc size is 804257792
[16:22:44] Setting worksize to 64
[16:22:44] cl_amd_media_ops found, setting BITALIGN
[16:22:44] BFI_INT patch requiring device not found, will not BFI_INT patch
[16:22:44] Loaded binary image whirlcoinPitcairngw64l4.bin
[16:22:44] Initialising kernel whirlcoin.cl with bitalign, unpatched BFI, nfactor 10, n 1024
[16:22:44] Creating buffer sized 536870912
[16:22:44] initCl() finished. Found Pitcairn
[16:22:44] Starting device 0 mining thread 0...
[16:22:44] Pushing sem post to thread 0
[16:22:44] Starting device 1 mining thread 0...
[16:22:44] Pushing sem post to thread 1
[16:22:44] Starting device 2 mining thread 0...
[16:22:44] Waiting on sem in miner thread
[16:22:44] Pushing sem post to thread 2
[16:22:44] Popping work from get queue to get work
[16:22:44] Starting device 3 mining thread 0...
[16:22:44] Waiting on sem in miner thread
[16:22:44] Pushing sem post to thread 3
[16:22:44] Popping work from get queue to get work
[16:22:44] Waiting on sem in miner thread
[16:22:44] Popping work from get queue to get work
[16:22:44] Waiting on sem in miner thread
[16:22:44] Popping work from get queue to get work
[16:22:44] Work update message received
[16:22:44] Selecting erebor.dwarfpool.com for work
[16:22:44] Generated stratum merkle d7f14de2cca044ab523036f16a712b3df549c430dea9ec615016455bf985e36c
[16:22:44] Generated stratum header 0000007090f3efb66bfa0d95f470043363c3ee5c26f572a81c4a7f4002cf807400000000d7f14de2cca044ab523036f16a712b3df549c430dea9ec615016455bf985e36c53d2ca8d1c0bd27e00000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000
[16:22:44] Work job_id fb0 nonce2 0 ntime 53d2ca8d
[16:22:44] Generated target 000000000000000000000000000000000000000000000000000000fcff030000
[16:22:44] Generated stratum work
[16:22:44] Pushing work from erebor.dwarfpool.com to hash queue
[16:22:44] New block: 0000000002cf80741c4a7f4026f572a863c3ee5cf47004336bfa0d9590f3efb6... diff 21
[16:22:44] Got work from get queue to get work for thread 3
[16:22:44] Generated target 000000000000000000000000000000000000000000000000000000fcff030000
[16:22:44] Error -4: Enqueueing kernel onto command queue. (clEnqueueNDRangeKernel)
[16:22:44] Selecting erebor.dwarfpool.com for work
[16:22:44] GPU 3 failure, disabling!
[16:22:44] Generated stratum merkle 36988efa91e8610bb9d08e1e982f998057bd34505f87a40b704a15c1de582ca4
[16:22:44] Generated stratum header 0000007090f3efb66bfa0d95f470043363c3ee5c26f572a81c4a7f4002cf80740000000036988efa91e8610bb9d08e1e982f998057bd34505f87a40b704a15c1de582ca453d2ca8d1c0bd27e00000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000
[16:22:44] Work job_id fb0 nonce2 1 ntime 53d2ca8d
[16:22:44] Generated target 000000000000000000000000000000000000000000000000000000fcff030000
[16:22:44] Generated stratum work
[16:22:44] Pushing work from erebor.dwarfpool.com to hash queue
[16:22:44] Got work from get queue to get work for thread 0
[16:22:44] Generated target 000000000000000000000000000000000000000000000000000000fcff030000
[16:22:44] Error -4: Enqueueing kernel onto command queue. (clEnqueueNDRangeKernel)
[16:22:44] GPU 0 failure, disabling!
[16:22:44] Selecting erebor.dwarfpool.com for work
[16:22:44] Generated stratum merkle 4346c799b4bea277a58810e502b6726028c4dbbba9643da85c8cb3d1a0ab4fe9
[16:22:44] Generated stratum header 0000007090f3efb66bfa0d95f470043363c3ee5c26f572a81c4a7f4002cf8074000000004346c799b4bea277a58810e502b6726028c4dbbba9643da85c8cb3d1a0ab4fe953d2ca8d1c0bd27e00000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000
[16:22:44] Work job_id fb0 nonce2 2 ntime 53d2ca8d
[16:22:44] Generated target 000000000000000000000000000000000000000000000000000000fcff030000
[16:22:44] Generated stratum work
[16:22:44] Pushing work from erebor.dwarfpool.com to hash queue

[16:22:51] 35.0 C  F: 30%(1082RPM)  E: 300MHz  M: 150Mhz  V: 0.800V  A: 0%  P: 20%
[16:22:51] 37.0 C  F: 30%(1077RPM)  E: 300MHz  M: 150Mhz  V: 0.800V  A: 0%  P: 20%
[16:22:51] 38.0 C  F: 30%(1133RPM)  E: 300MHz  M: 150Mhz  V: 0.800V  A: 0%  P: 20%
[16:22:51] 35.0 C  F: 30%(1080RPM)  E: 300MHz  M: 150Mhz  V: 0.800V  A: 0%  P: 20%
[16:22:53] Staged work: total (1) > max (0), discarding
[16:22:53] Discarded work
[16:22:53] Selecting erebor.dwarfpool.com for work
[16:22:53] Generated stratum merkle fe7c44c4b775f7e9a78cdb013606e80cf9d02078402803fde374d136fc59d6cd
[16:22:53] Generated stratum header 000000709868486b7c7742365eb3789b943823faf80311ca7855a3cc04ab5a7e00000000fe7c44c4b775f7e9a78cdb013606e80cf9d02078402803fde374d136fc59d6cd53d2caa11c0b7b9200000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000

[16:23:33] Selecting erebor.dwarfpool.com for work
[16:23:33] Generated stratum merkle 9f94963ad17f028be023da88f81304c2606cd4f796cf9b78b1fa5c45e2241de1
[16:23:33] Generated stratum header 000000709868486b7c7742365eb3789b943823faf80311ca7855a3cc04ab5a7e000000009f94963ad17f028be023da88f81304c2606cd4f796cf9b78b1fa5c45e2241de153d2caa11c0b7b9200000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000
[16:23:33] Work job_id fb1 nonce2 40 ntime 53d2caa1
[16:23:33] Generated target 000000000000000000000000000000000000000000000000000000fcff030000
[16:23:33] Generated stratum work
[16:23:33] Pushing work from erebor.dwarfpool.com to hash queue
[16:23:33] Staged work: total (1) > max (0), discarding
[16:23:33] Discarded work
[16:23:33] Selecting erebor.dwarfpool.com for work
[16:23:33] Generated stratum merkle 78df730ec3835e426d07f66e76e7c14f6dd418f2f74abab5db2f4918b3de8b6d
[16:23:33] Generated stratum header 000000709868486b7c7742365eb3789b943823faf80311ca7855a3cc04ab5a7e0000000078df730ec3835e426d07f66e76e7c14f6dd418f2f74abab5db2f4918b3de8b6d53d2caa11c0b7b9200000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000
[16:23:33] Work job_id fb1 nonce2 41 ntime 53d2caa1
[16:23:33] Generated target 000000000000000000000000000000000000000000000000000000fcff030000
[16:23:33] Generated stratum work
[16:23:33] Pushing work from erebor.dwarfpool.com to hash queue
[16:23:33] 35.0 C  F: 30%(1084RPM)  E: 300MHz  M: 150Mhz  V: 0.800V  A: 0%  P: 20%
[16:23:33] 36.0 C  F: 30%(1074RPM)  E: 300MHz  M: 150Mhz  V: 0.800V  A: 0%  P: 20%
[16:23:33] 37.0 C  F: 30%(1126RPM)  E: 300MHz  M: 150Mhz  V: 0.800V  A: 0%  P: 20%
[16:23:33] Generated stratum merkle ff55130ac518ba17e754af5ec1517d522cf3a4216b557897a49a714b965d4da9
[16:23:33] Generated stratum header 00000070a9e07708bd284badc83ff2ce360376262410387235b0d67503d2e30f00000000ff55130ac518ba17e754af5ec1517d522cf3a4216b557897a49a714b965d4da953d2cace1c0aaa6600000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000
[16:23:33] Work job_id fb3 nonce2 0 ntime 53d2cace
[16:23:33] Generated target 000000000000000000000000000000000000000000000000000000fcff030000
[16:23:33] New block: 0000000003d2e30f35b0d6752410387236037626c83ff2cebd284bada9e07708... diff 24
[16:23:33] Work stale due to block mismatch
[16:23:33] Discarded work
[16:25:57] Selecting erebor.dwarfpool.com for work
[16:25:57] Generated stratum merkle 375a3664509f354eaef7d022e872ebdbfe705ec939dc65d1d30a7c72985120e8
[16:25:57] Generated stratum header 00000070a3f596be4674caaafa7a648840d74824d11c0a7e568bbebc024e8b1c00000000375a3664509f354eaef7d022e872ebdbfe705ec939dc65d1d30a7c72985120e853d2cb4d1c0b9f7c00000000000000800000000000000000000000000000000000000000000000000000000000000000000000000000000080020000
[16:25:57] Work job_id fb7 nonce2 16 ntime 53d2cb4d
[16:25:57] Generated target 000000000000000000000000000000000000000000000000000000fcff030000
[16:25:57] Generated stratum work
[16:25:57] Pushing work from erebor.dwarfpool.com to hash queue
[16:25:57] 34.0 C  F: 30%(1080RPM)  E: 300MHz  M: 150Mhz  V: 0.800V  A: 0%  P: 20%
[16:25:57] 36.0 C  F: 30%(1067RPM)  E: 300MHz  M: 150Mhz  V: 0.800V  A: 0%  P: 20%
[16:25:57] 37.0 C  F: 30%(1142RPM)  E: 300MHz  M: 150Mhz  V: 0.800V  A: 0%  P: 20%
[16:25:57] 33.0 C  F: 30%(1061RPM)  E: 300MHz  M: 150Mhz  V: 0.800V  A: 0%  P: 20%



Here is the config


Code:
{
"pools" : [
{
"url" : "stratum+tcp://erebor.dwarfpool.com:3358",
"user" : "FX6dhq7GDmQzgGvNkxVSThmybstpQEA4rE.5",
"pass" : "x"
    }

],
"thread-concurrency" : "8192,8192,8192,8192",
"api-allow" : "W:127.0.0.1",
"api-listen" : true,
"gpu-vddc" : "0.000,0.000,0.000,0.000",
"intensity" : "18,18,18,18",
"worksize" : "64,64,64,64",
"gpu-engine" : "1100,1100,1100,1100",
"lookup-gap" : "2",
"api-mcast-port" : "4028",
"api-port" : "4028",
"expiry" : "30",
"failover-switch-delay" : "60",
"gpu-dyninterval" : "7",
"gpu-platform" : "0",
"log" : "5",
"no-pool-disable" : true,
"queue" : "0",
"scan-time" : "15",
"tcp-keepalive" : "30",
"temp-hysteresis" : "2",
"shares" : "0",
"vectors" : "1",
"device" : "0,1,2,3",
"temp-cutoff" : "95,95,95,95",
"temp-overheat" : "85,85,85,85",
"temp-target" : "75,75,75,75",
"auto-fan" : true,
"gpu-fan" : "30-100,30-100,30-100,30-100",
"gpu-powertune" : "20,20,20,20"
}

The .bat

Code:
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
set GPU_MAX_ALLOC_PERCENT 100
set GPU_USE_SYNC_OBJECTS 1
del *.bin
sgminer.exe 2>logfile.txt --kernel whirlcoin -g 1 --gpu-platform 1 --config sgminer5.0.conf


It spits out the error line of:

GPU xxxx failure, disabling!
Error -4 Enqueueing kernel onto command queue. <clEnqueueNDRangeKerne,>


Mind you this is just one algo, even with the X11 or NST5 algos in the miner this does not work ( well the x11 being the darkcoin-mod )


Ninja edit:

Ooooo thats what
Code:
 does lol.



Free SIGNs giving everyday. Be part, do not miss!.
SqMe5ceYfdcGsRyVpgvpYb6bRLS9j8omvB

XChat : Addy : XYuZESQpeMtZ2wit8nVVnXKGytfiaTBCo6 PubKey : eteshLzeq8Bh54BRjGSunMTc6Ytxtk7HYaSmDYMQn61z
BrewCrewFan
Hero Member
*****
Offline Offline

Activity: 672
Merit: 501



View Profile
July 25, 2014, 09:48:10 PM
 #1287

To add no the mobo is a older NI8 sli ( abit skt 775 ).

No onboard grafix

Maybe its the 1 gig ram? I could try installing more ram and see if that works, but, I have to find a few extra sticks.... DDR 2 is so 2000's lol...

The normal sgminer works just fine, but improvements seem to be totally on this version of SGminer that is why I want to use it. Plus , with the multi algo support and all that fun stuff.

Free SIGNs giving everyday. Be part, do not miss!.
SqMe5ceYfdcGsRyVpgvpYb6bRLS9j8omvB

XChat : Addy : XYuZESQpeMtZ2wit8nVVnXKGytfiaTBCo6 PubKey : eteshLzeq8Bh54BRjGSunMTc6Ytxtk7HYaSmDYMQn61z
badman74
Hero Member
*****
Offline Offline

Activity: 658
Merit: 500



View Profile
July 25, 2014, 09:50:24 PM
Last edit: July 25, 2014, 10:09:49 PM by badman74
 #1288


It spits out the error line of:

GPU xxxx failure, disabling!
Error -4 Enqueueing kernel onto command queue. <clEnqueueNDRangeKerne,>


Mind you this is just one algo, even with the X11 or NST5 algos in the miner this does not work ( well the x11 being the darkcoin-mod )


Ninja edit:

Ooooo thats what
Code:
 does lol.
dont use --kernel
use --algorithm
also TC is only used for scrypt/nscrypt
bullus
Sr. Member
****
Offline Offline

Activity: 294
Merit: 250


View Profile
July 25, 2014, 09:50:28 PM
 #1289

edit
I notice a hashrate drop to below 6mh/s and rise back again with xI=65.
Drop to xI=64 (6274kh/s) and is not dropping anymore.(10kh/s or so)

Edit2
As u can see the Accepted shares are calculate fine in sgminer, but the above value isn't.
Is it hard to change the above value to the value sgminer is showing with "G".?

edit3
Still stable after 3 hours.

Restarted and see if the other algos also be stable...6.346kh/s Shocked

Sigh... every time I get close someone has to leap farther ahead.   Wink

Looks like you encountered the same thing I did with the x-65/x-64 threshold. I'm running x-68 since last night, averaging 5.96 Mhash/GPU across 4 290X's over 12 hours. Stable apart from a renter trying to load dead pools for a while, LOL. I get up to around 6.17 Mhash on one of the GPU's but they keep dropping off and don't hold consistently at the highest speeds. But I'm still at 1020/1350 on the clocks so that explains much of my shortfall, I'm sure.

On scrypt I had all 4 of my GPU's individually tuned to four different engine and memory speeds for the fastest possible stable speed. I'm going to try the latest builds and settings you and badman74 helpfully shared, and then see if I can push individual GPU's higher. Thanks again!

EDIT: Dumb question - I've never messed with voltage settings before as I didn't want to fry anything. But I see in bullus' profile that he has vddc set to 0. Does that mean "go with the default setting"? As I understand it the reference voltage on a 290X is 1.0 volt. So if I wanted to try cutting that by 10%, should I put "0.9" in the vddc line, or "-0.1"?  Reading the docs would have me trying the former, but bullus' example makes me think the latter is right.

That's funny cause 1 renter told I was selling a 4.2mh/s rig but I have 9.8mh/s.(4x7950)
At the graph at betarigs u see fluctuating hashrates but can't see that at sgminer like i saw it with xI=65.(290x)
Average is still 9.6mh/s, a bit lower than normal, but no way 4.2mh/s. Is there a tweak for flat hashrates? Decreasing intensity?



gpu-vddc is set at 0 ,because I set it with msi afterburner for testing. At github guide u should set it like "1.000"


I don't know where he saw 4.2, especially with your average per 2 hours right where it should be. The thing about Betarigs is that the hashrate they show is just based on their readings of your rig's submitted shares. There's two things you can do, you could explain to the renter that the accepted shares will be higher if they direct the rig to a pool that's closer to your rig, or you could change no-submit-stale to false (or just delete that line). Doing that would mean that your rig would still submit stales but at least his pool will see a higher amount of total shares submitted (and that would mean a more accurate gauge of your hashrate). Another issue with betarigs is that I don't think most people are setting the difficulty properly, so there's going to be pretty wild variance on your hashrate.

I might just create a pre-build paragraph to message the renter as soon as they rent the rig to make sure that they understand all of this and to try to help them out as best I can with finding the right pool (I can test the latency to their pool and let them know if it'll be a factor for stales/rejects) and kinda guide them through setting the difficulty properly for the hashrate of the worker.

I don't know either, only once my hash from the graph show 4.2mh/s and he complains my rig is down and rented as 4.2mh/s..fuck it. I told him to make a ticket that I was selling my rig for 4.2mh/s instead of 9.8mh/s..heard nothing of him anymore. I'm gonna change no-submit-stale to false and see if that work better. Thanks

btc 16LWhms487bzCxQWq5oeW8SMDPmU2rvQjf
BrewCrewFan
Hero Member
*****
Offline Offline

Activity: 672
Merit: 501



View Profile
July 25, 2014, 11:52:54 PM
 #1290


It spits out the error line of:

GPU xxxx failure, disabling!
Error -4 Enqueueing kernel onto command queue. <clEnqueueNDRangeKerne,>


Mind you this is just one algo, even with the X11 or NST5 algos in the miner this does not work ( well the x11 being the darkcoin-mod )


Ninja edit:

Ooooo thats what
Code:
 does lol.
dont use --kernel
use --algorithm
also TC is only used for scrypt/nscrypt

Okay so I installed 2 more gig of ram... and windows...

I run the sgminer 5.0 before I install VNC and it works just great.

Now, I wonder if VNC is the issue .... I almost think so.

Free SIGNs giving everyday. Be part, do not miss!.
SqMe5ceYfdcGsRyVpgvpYb6bRLS9j8omvB

XChat : Addy : XYuZESQpeMtZ2wit8nVVnXKGytfiaTBCo6 PubKey : eteshLzeq8Bh54BRjGSunMTc6Ytxtk7HYaSmDYMQn61z
badman74
Hero Member
*****
Offline Offline

Activity: 658
Merit: 500



View Profile
July 26, 2014, 12:13:17 AM
 #1291


It spits out the error line of:

GPU xxxx failure, disabling!
Error -4 Enqueueing kernel onto command queue. <clEnqueueNDRangeKerne,>


Mind you this is just one algo, even with the X11 or NST5 algos in the miner this does not work ( well the x11 being the darkcoin-mod )


Ninja edit:

Ooooo thats what
Code:
 does lol.
dont use --kernel
use --algorithm
also TC is only used for scrypt/nscrypt

Okay so I installed 2 more gig of ram... and windows...

I run the sgminer 5.0 before I install VNC and it works just great.

Now, I wonder if VNC is the issue .... I almost think so.
i found teamviewer works better for me and much easier, though my extra miners are running pimp at the moment
KiloWatts
Member
**
Offline Offline

Activity: 119
Merit: 10


View Profile
July 26, 2014, 01:20:02 AM
 #1292


It spits out the error line of:

GPU xxxx failure, disabling!
Error -4 Enqueueing kernel onto command queue. <clEnqueueNDRangeKerne,>


Mind you this is just one algo, even with the X11 or NST5 algos in the miner this does not work ( well the x11 being the darkcoin-mod )


Ninja edit:

Ooooo thats what
Code:
 does lol.
dont use --kernel
use --algorithm
also TC is only used for scrypt/nscrypt

Okay so I installed 2 more gig of ram... and windows...

I run the sgminer 5.0 before I install VNC and it works just great.

Now, I wonder if VNC is the issue .... I almost think so.
i found teamviewer works better for me and much easier, though my extra miners are running pimp at the moment

I use TightVNC with no issues.  You need a VNC program that doesn't mess with your display when connecting.
bullus
Sr. Member
****
Offline Offline

Activity: 294
Merit: 250


View Profile
July 26, 2014, 08:39:44 AM
Last edit: July 26, 2014, 12:31:09 PM by bullus
 #1293

@badman

I tried your mod v5 and get about -250kh/s for x11 and better hashrates with x13/x15.
But when I copied the old x11bin to your miner and mine again I don't have a higher hashrate.
Also copied the x13-x15 bin to the other miner gives me no higher hashrates..can u test and do u have the same issue?
sgminer-5.0-daily-20140712-15-win32 and your modded miner.

btc 16LWhms487bzCxQWq5oeW8SMDPmU2rvQjf
platinum4
Sr. Member
****
Offline Offline

Activity: 547
Merit: 250



View Profile
July 26, 2014, 09:14:56 AM
 #1294

@badman

I tried your mod v5 and get about -50kh/s for x11 and better hashrates with x13/x15.
But when I copied the old x11bin to your miner and mine again I don't have a higher hashrate.
Also copied the x13-x15 bin to the other miner gives me no higher hashrates..can u test and do u have the same issue?
sgminer-5.0-daily-20140712-15-win32 and your modded miner.


I've gotten incredibly stable uptime with the https://www.nicehash.com/software/nightly/sgminer-5.0-daily-20140725-21-win32.zip

I don't know why, but there is another build under it labeled '1' instead of '21' that I have not tried yet.
bullus
Sr. Member
****
Offline Offline

Activity: 294
Merit: 250


View Profile
July 26, 2014, 09:30:21 AM
 #1295

@badman

I tried your mod v5 and get about -50kh/s for x11 and better hashrates with x13/x15.
But when I copied the old x11bin to your miner and mine again I don't have a higher hashrate.
Also copied the x13-x15 bin to the other miner gives me no higher hashrates..can u test and do u have the same issue?
sgminer-5.0-daily-20140712-15-win32 and your modded miner.


I've gotten incredibly stable uptime with the https://www.nicehash.com/software/nightly/sgminer-5.0-daily-20140725-21-win32.zip

I don't know why, but there is another build under it labeled '1' instead of '21' that I have not tried yet.

Gonna test those.
About betarig. I change the no-submit-stale to false and even lowerd the intensity and use my 290x for the total of 10mh/s ,but stil fluctuate ..I did what I can so it's got to be annother issue not at my side.

btc 16LWhms487bzCxQWq5oeW8SMDPmU2rvQjf
kenshirothefist (OP)
Sr. Member
****
Offline Offline

Activity: 457
Merit: 273



View Profile
July 26, 2014, 10:31:18 AM
 #1296

I don't know why, but there is another build under it labeled '1' instead of '21' that I have not tried yet.

Note the name sgminer-dev-daily-20140725-1-win32.zip - we've added also nightly builds for develop branch of sgminer: https://github.com/sgminer-dev/sgminer/tree/develop ... it has support for Fresh algo, etc. ... it is expected for the v5.0 branch to stabilise and new features will be added to develop branch only.
bullus
Sr. Member
****
Offline Offline

Activity: 294
Merit: 250


View Profile
July 26, 2014, 10:49:41 AM
 #1297

@badman

I tried your mod v5 and get about -50kh/s for x11 and better hashrates with x13/x15.
But when I copied the old x11bin to your miner and mine again I don't have a higher hashrate.
Also copied the x13-x15 bin to the other miner gives me no higher hashrates..can u test and do u have the same issue?
sgminer-5.0-daily-20140712-15-win32 and your modded miner.


I've gotten incredibly stable uptime with the https://www.nicehash.com/software/nightly/sgminer-5.0-daily-20140725-21-win32.zip

I don't know why, but there is another build under it labeled '1' instead of '21' that I have not tried yet.

Tested the hashrates but x11 is still very low 5500kh/s where I can get 6200kh/s with the optimized bin.
x13/x15 is ok.

btc 16LWhms487bzCxQWq5oeW8SMDPmU2rvQjf
badman74
Hero Member
*****
Offline Offline

Activity: 658
Merit: 500



View Profile
July 26, 2014, 12:02:44 PM
Last edit: July 26, 2014, 12:15:12 PM by badman74
 #1298

@badman

I tried your mod v5 and get about -50kh/s for x11 and better hashrates with x13/x15.
But when I copied the old x11bin to your miner and mine again I don't have a higher hashrate.
Also copied the x13-x15 bin to the other miner gives me no higher hashrates..can u test and do u have the same issue?
sgminer-5.0-daily-20140712-15-win32 and your modded miner.

the nightly builds from nicehash are unmodified sgminer5 builds straight from the git
the one i linked you was one where i modded a few things

changed
#define SPH_LUFFA_PARALLEL 0 to #define SPH_LUFFA_PARALLEL 1
#define SPH_KECCAK_UNROLL 0 to #define SPH_KECCAK_UNROLL 1

in groestl.cl
changed
Code:
#define PERM_BIG_P(a)   do { \
    int r; \
    for (r = 0; r < 14; r += 2) { \
      ROUND_BIG_P(a, r + 0); \
      ROUND_BIG_P(a, r + 1); \
    } \
  } while (0)

#define PERM_BIG_Q(a)   do { \
    int r; \
    for (r = 0; r < 14; r += 2) { \
      ROUND_BIG_Q(a, r + 0); \
      ROUND_BIG_Q(a, r + 1); \
    } \
  } while (0)
to
Code:
#define PERM_BIG_P(a)   do { \
    int r; \
    for (r = 0; r < 14; r ++) { \
      ROUND_BIG_P(a, r); \
    } \
  } while (0)

#define PERM_BIG_Q(a)   do { \
    int r; \
    for (r = 0; r < 14; r ++) { \
      ROUND_BIG_Q(a, r); \
    } \
  } while (0)
and that gets me 5.95mh/s with 1040/1375 at I 16

if you want to get the hash rate the easy way, pull the darkcoin-mod.cl and any others you want out of aznboy84's build and it should give at least as good hash rate as mine probably better
bullus
Sr. Member
****
Offline Offline

Activity: 294
Merit: 250


View Profile
July 26, 2014, 12:20:00 PM
 #1299

I'm getting 6230kh/s with the aznboy bin (1050/1350, xI=64) u should try xI=64.

btc 16LWhms487bzCxQWq5oeW8SMDPmU2rvQjf
badman74
Hero Member
*****
Offline Offline

Activity: 658
Merit: 500



View Profile
July 26, 2014, 12:33:33 PM
 #1300

I'm getting 6230kh/s with the aznboy bin (1050/1350, xI=64) u should try xI=64.
i have... while it does give me as much as 6.45 on one of my gpu the other drops to as low as 5.0 and the average drops to around 5.8 per gpu. then they also start crashing on me so i just went back to my stable settings
i can get 6.0 with I 17 but it crashes after a while and locks the whole computer
Pages: « 1 ... 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 [65] 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 ... 233 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!