[Ultracoin] [Est. Feb 2014] ~ ASIC Resistant & Ultrafast 6 Second Transactions! - page 166.

Thirtybird

hero member

Activity: 693

Merit: 500

Quote from: king_pin on January 23, 2015, 01:41:57 PM

I see that ATI cards get around 4 times less than on NF14, but NVIDIA cards go down only 3 times in hashrate, damn wish I had more Nvidias Sad

280X - 1,2 kH/s is OK
290 - 1,4 kH/s is OK

Because you have the wrong AMD cards for high N factors

wtfc360

full member

Activity: 137

Merit: 100

Yes, @ 1200/1500 seem to be working, getting the same 1174h/s for 4 out of 5 GPUs the sick one gets around 445h/s then goes sick again.
config from configgen

Quote from: tex81 on January 24, 2015, 10:48:06 AM

Gettin` 1188 h/s on 280X @ 1200/1500
Now 4 (cards) x 20-25 accepts without HW.
Config from configgen.

tex81

full member

Activity: 145

Merit: 100

Gettin` 1188 h/s on 280X @ 1200/1500
Now 4 (cards) x 20-25 accepts without HW.
Config from configgen.

wtfc360

full member

Activity: 137

Merit: 100

FAAK, the rig died when rebooting through TW, HAHAHA, have to go and restart it manually tomorrow, that's what you get for being to greedy Cheesy

@ Wirly Thanks for trying to help! Might be back again when its up again tomorrow...

Quote from: Wirly on January 24, 2015, 09:55:22 AM

Reboot the rigs. Do not just restart the miners when you make these changes.

Quote from: wtfc360 on January 24, 2015, 09:50:19 AM

So this is the batfile:
C:\Users\Mining1\Desktop\Yacminer-3.5.0-yac2-x86\yacminer.exe --scrypt-chacha -o stratum+tcp://stratum2.tumblingblock.com:5555 -u worker.1 -p password -R 2560 -g 1 -w 128 --buffer-size 2590 --lookup-gap 8 --gpu-engine 1000 --gpu-memclock 1250 --temp-cutoff 85 --nfmin 4 --nfmax 30 --starttime 1388361600

gives me: 0 (Sick), 978,978, 450, 130

Wirly

full member

Activity: 136

Merit: 100

Reboot the rigs. Do not just restart the miners when you make these changes.

Quote from: wtfc360 on January 24, 2015, 09:50:19 AM

So this is the batfile:
C:\Users\Mining1\Desktop\Yacminer-3.5.0-yac2-x86\yacminer.exe --scrypt-chacha -o stratum+tcp://stratum2.tumblingblock.com:5555 -u worker.1 -p password -R 2560 -g 1 -w 128 --buffer-size 2590 --lookup-gap 8 --gpu-engine 1000 --gpu-memclock 1250 --temp-cutoff 85 --nfmin 4 --nfmax 30 --starttime 1388361600

gives me: 0 (Sick), 978,978, 450, 130

volyova

legendary

Activity: 910

Merit: 1000

Quote from: volyova on January 24, 2015, 09:49:02 AM

Quote from: wtfc360 on January 24, 2015, 08:33:21 AM

I use the data from configgen and have this setup for all my rigs:
C:\Users\Mining1\Desktop\Yacminer-3.5.0-yac2-x86\yacminer.exe --scrypt-chacha -o stratum+tcp://stratum2.tumblingblock.com:5555 -u worker.1 -p password -R 2560 -g 1 -w 128 --buffer-size 2590 --lookup-gap 8 --temp-cutoff 85 --nfmin 4 --nfmax 30 --starttime 1388361600

From that I get different results for every rig:

5 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 490h/s ,139h/s & one SICK
5 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 998h/s, 362h/s & one DEAD
5 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 490h/s ,139h/s & one SICK
4 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 998h/s, & one DEAD

5 x ASUS Radeon R9 280x 3GB: 1,047Kh/s, 1,047Kh/s, 1,047Kh/s, 1,047Kh/s & one DEAD
5 x ASUS Radeon R9 280x 3GB: 1,047Kh/s, 1,047Kh/s, 1,047Kh/s, 1,047Kh/s & one DEAD
4 x ASUS Radeon R9 280x 3GB: 1,047Kh/s, 1,047Kh/s, 1,047Kh/s & one DEAD

5 x MSI Radeon R9 3 GB: 998h/s, 998h/s, 998h/s, 998h/s, 998h/s

Anyone got any idea why one card is always dead in each rig from Sapphire/ASUS but not from the MSI-cards?
Before mininig at N14 they didn't go DEAD/Sick...?

Quote from: barbados-fs on January 24, 2015, 06:22:25 AM

Friends share settings for R9 28x 0and R9 270x. Just not here - http://cfg.ultracoin.net/ the result is less than it should be.
Thank U.

Coz MSI iz teh best!

Srsly noobz, dnt buy Sapphire.

wtfc360

full member

Activity: 137

Merit: 100

volyova

legendary

Activity: 910

Merit: 1000

Quote from: wtfc360 on January 24, 2015, 08:33:21 AM

I use the data from configgen and have this setup for all my rigs:
C:\Users\Mining1\Desktop\Yacminer-3.5.0-yac2-x86\yacminer.exe --scrypt-chacha -o stratum+tcp://stratum2.tumblingblock.com:5555 -u worker.1 -p password -R 2560 -g 1 -w 128 --buffer-size 2590 --lookup-gap 8 --temp-cutoff 85 --nfmin 4 --nfmax 30 --starttime 1388361600

From that I get different results for every rig:

5 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 490h/s ,139h/s & one SICK
5 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 998h/s, 362h/s & one DEAD
5 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 490h/s ,139h/s & one SICK
4 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 998h/s, & one DEAD

5 x ASUS Radeon R9 280x 3GB: 1,047Kh/s, 1,047Kh/s, 1,047Kh/s, 1,047Kh/s & one DEAD
5 x ASUS Radeon R9 280x 3GB: 1,047Kh/s, 1,047Kh/s, 1,047Kh/s, 1,047Kh/s & one DEAD
4 x ASUS Radeon R9 280x 3GB: 1,047Kh/s, 1,047Kh/s, 1,047Kh/s & one DEAD

5 x MSI Radeon R9 3 GB: 998h/s, 998h/s, 998h/s, 998h/s, 998h/s

Anyone got any idea why one card is always dead in each rig from Sapphire/ASUS but not from the MSI-cards?
Before mininig at N14 they didn't go DEAD/Sick...?

Quote from: barbados-fs on January 24, 2015, 06:22:25 AM

Friends share settings for R9 28x 0and R9 270x. Just not here - http://cfg.ultracoin.net/ the result is less than it should be.
Thank U.

Coz MSI iz teh best!

Wirly

full member

Activity: 136

Merit: 100

You are having memory issues, to much engine speed not enough memory. You can see that your gpu 0, 1 and 2 are affecting each other and 3 and 4 are proly sharing. Depending on the design of your MOB your GPU may be sharing a data bus. Example, my 6 gpu rigs are the same and gpu1 and 4 share a bus and changing anything on 1 affects 4, but only when there are 6 gpu's running. try gpu-engine 1000 and gpu-memclock of 1250 for start.

Quote from: wtfc360 on January 24, 2015, 09:23:25 AM

So tried --gpu-engine 1031, 1031, 1031, 1031, 1031 and get : 0 (Sick/dead), 1,009 Kh/s, 1,009Kh/s, 490h/s, 134h/s.
Then I try --gpu-engine 900, 1031, 1031, 900, 900 and get: 0 (Sick/dead), 881h/s, 881h/s, 489h/s, 130h/s
Why is GPU 1 and 2 affected by the GPU 0 engine set?

Quote from: Wirly on January 24, 2015, 09:13:01 AM

rapture333

sr. member

Activity: 476

Merit: 250

Quote from: volyova on January 24, 2015, 02:01:50 AM

Quote from: rapture333 on January 23, 2015, 11:30:26 PM

@SecretsOfCrypto

Rapture has always been my online alias; in the beginning anonymity was important to me, just like many in the crypto word, but it is much less so now that I am doing professional work for Ultracoin and using my full name all the time. I am not a hard target to dox either.

Is it a religious rapture, or just a normal rapture? Tongue

Non-religious definition, Rapture 1. "a feeling of intense pleasure or joy." Also the name of my motorcycle Cool

wtfc360

full member

Activity: 137

Merit: 100

So tried --gpu-engine 1031, 1031, 1031, 1031, 1031 and get : 0 (Sick/dead), 1,009 Kh/s, 1,009Kh/s, 490h/s, 134h/s.
Then I try --gpu-engine 900, 1031, 1031, 900, 900 and get: 0 (Sick/dead), 881h/s, 881h/s, 489h/s, 130h/s
Why is GPU 1 and 2 affected by the GPU 0 engine set?

Quote from: Wirly on January 24, 2015, 09:13:01 AM

Yes

Quote from: wtfc360 on January 24, 2015, 09:08:14 AM

Ok, I'll try that. If it says GPU 0 is sick would that be automatically the first engine to slow down, in your example: --gpu-engine 1040,1040,1040,1000,1000 and slow that from 1040 to lets say 1000?

Quote from: Wirly on January 24, 2015, 08:54:40 AM

Quote from: wtfc360 on January 24, 2015, 08:33:21 AM

I use the data from configgen and have this setup for all my rigs:
C:\Users\Mining1\Desktop\Yacminer-3.5.0-yac2-x86\yacminer.exe --scrypt-chacha -o stratum+tcp://stratum2.tumblingblock.com:5555 -u worker.1 -p password -R 2560 -g 1 -w 128 --buffer-size 2590 --lookup-gap 8 --temp-cutoff 85 --nfmin 4 --nfmax 30 --starttime 1388361600

From that I get different results for every rig:

5 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 490h/s ,139h/s & one SICK
5 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 998h/s, 362h/s & one DEAD
5 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 490h/s ,139h/s & one SICK
4 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 998h/s, & one DEAD

5 x ASUS Radeon R9 280x 3GB: 1,047Kh/s, 1,047Kh/s, 1,047Kh/s, 1,047Kh/s & one DEAD
5 x ASUS Radeon R9 280x 3GB: 1,047Kh/s, 1,047Kh/s, 1,047Kh/s, 1,047Kh/s & one DEAD
4 x ASUS Radeon R9 280x 3GB: 1,047Kh/s, 1,047Kh/s, 1,047Kh/s & one DEAD

5 x MSI Radeon R9 3 GB: 998h/s, 998h/s, 998h/s, 998h/s, 998h/s

Anyone got any idea why one card is always dead in each rig from Sapphire/ASUS but not from the MSI-cards?
Before mininig at N14 they didn't go DEAD/Sick...?

Quote from: barbados-fs on January 24, 2015, 06:22:25 AM

Friends share settings for R9 28x 0and R9 270x. Just not here - http://cfg.ultracoin.net/ the result is less than it should be.
Thank U.

Try slowing down the engine speed of the gpu going sick, example --gpu-engine 1040,1040,1040,1000,1000
or turn down the raw intensity by using individual -R values for each, example -R 2560,2560,2560,2432,2432 (decreased in increments of the work size setting of 128)
or if using windows try increasing the amount of virtual memory your hard drive is using

Wirly

full member

Activity: 136

Merit: 100

Yes

Quote from: wtfc360 on January 24, 2015, 09:08:14 AM

Ok, I'll try that. If it says GPU 0 is sick would that be automatically the first engine to slow down, in your example: --gpu-engine 1040,1040,1040,1000,1000 and slow that from 1040 to lets say 1000?

Quote from: Wirly on January 24, 2015, 08:54:40 AM

Quote from: wtfc360 on January 24, 2015, 08:33:21 AM

I use the data from configgen and have this setup for all my rigs:
C:\Users\Mining1\Desktop\Yacminer-3.5.0-yac2-x86\yacminer.exe --scrypt-chacha -o stratum+tcp://stratum2.tumblingblock.com:5555 -u worker.1 -p password -R 2560 -g 1 -w 128 --buffer-size 2590 --lookup-gap 8 --temp-cutoff 85 --nfmin 4 --nfmax 30 --starttime 1388361600

From that I get different results for every rig:

5 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 490h/s ,139h/s & one SICK
5 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 998h/s, 362h/s & one DEAD
5 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 490h/s ,139h/s & one SICK
4 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 998h/s, & one DEAD

5 x ASUS Radeon R9 280x 3GB: 1,047Kh/s, 1,047Kh/s, 1,047Kh/s, 1,047Kh/s & one DEAD
5 x ASUS Radeon R9 280x 3GB: 1,047Kh/s, 1,047Kh/s, 1,047Kh/s, 1,047Kh/s & one DEAD
4 x ASUS Radeon R9 280x 3GB: 1,047Kh/s, 1,047Kh/s, 1,047Kh/s & one DEAD

5 x MSI Radeon R9 3 GB: 998h/s, 998h/s, 998h/s, 998h/s, 998h/s

Anyone got any idea why one card is always dead in each rig from Sapphire/ASUS but not from the MSI-cards?
Before mininig at N14 they didn't go DEAD/Sick...?

Quote from: barbados-fs on January 24, 2015, 06:22:25 AM

Friends share settings for R9 28x 0and R9 270x. Just not here - http://cfg.ultracoin.net/ the result is less than it should be.
Thank U.

Try slowing down the engine speed of the gpu going sick, example --gpu-engine 1040,1040,1040,1000,1000
or turn down the raw intensity by using individual -R values for each, example -R 2560,2560,2560,2432,2432 (decreased in increments of the work size setting of 128)
or if using windows try increasing the amount of virtual memory your hard drive is using

wtfc360

full member

Activity: 137

Merit: 100

Ok, I'll try that. If it says GPU 0 is sick would that be automatically the first engine to slow down, in your example: --gpu-engine 1040,1040,1040,1000,1000 and slow that from 1040 to lets say 1000?

Quote from: Wirly on January 24, 2015, 08:54:40 AM

Quote from: wtfc360 on January 24, 2015, 08:33:21 AM

I use the data from configgen and have this setup for all my rigs:
C:\Users\Mining1\Desktop\Yacminer-3.5.0-yac2-x86\yacminer.exe --scrypt-chacha -o stratum+tcp://stratum2.tumblingblock.com:5555 -u worker.1 -p password -R 2560 -g 1 -w 128 --buffer-size 2590 --lookup-gap 8 --temp-cutoff 85 --nfmin 4 --nfmax 30 --starttime 1388361600

From that I get different results for every rig:

5 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 490h/s ,139h/s & one SICK
5 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 998h/s, 362h/s & one DEAD
5 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 490h/s ,139h/s & one SICK
4 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 998h/s, & one DEAD

5 x ASUS Radeon R9 280x 3GB: 1,047Kh/s, 1,047Kh/s, 1,047Kh/s, 1,047Kh/s & one DEAD
5 x ASUS Radeon R9 280x 3GB: 1,047Kh/s, 1,047Kh/s, 1,047Kh/s, 1,047Kh/s & one DEAD
4 x ASUS Radeon R9 280x 3GB: 1,047Kh/s, 1,047Kh/s, 1,047Kh/s & one DEAD

5 x MSI Radeon R9 3 GB: 998h/s, 998h/s, 998h/s, 998h/s, 998h/s

Anyone got any idea why one card is always dead in each rig from Sapphire/ASUS but not from the MSI-cards?
Before mininig at N14 they didn't go DEAD/Sick...?

Quote from: barbados-fs on January 24, 2015, 06:22:25 AM

Friends share settings for R9 28x 0and R9 270x. Just not here - http://cfg.ultracoin.net/ the result is less than it should be.
Thank U.

Try slowing down the engine speed of the gpu going sick, example --gpu-engine 1040,1040,1040,1000,1000
or turn down the raw intensity by using individual -R values for each, example -R 2560,2560,2560,2432,2432 (decreased in increments of the work size setting of 128)
or if using windows try increasing the amount of virtual memory your hard drive is using

Wirly

full member

Activity: 136

Merit: 100

Quote from: wtfc360 on January 24, 2015, 08:33:21 AM

I use the data from configgen and have this setup for all my rigs:
C:\Users\Mining1\Desktop\Yacminer-3.5.0-yac2-x86\yacminer.exe --scrypt-chacha -o stratum+tcp://stratum2.tumblingblock.com:5555 -u worker.1 -p password -R 2560 -g 1 -w 128 --buffer-size 2590 --lookup-gap 8 --temp-cutoff 85 --nfmin 4 --nfmax 30 --starttime 1388361600

From that I get different results for every rig:

5 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 490h/s ,139h/s & one SICK
5 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 998h/s, 362h/s & one DEAD
5 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 490h/s ,139h/s & one SICK
4 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 998h/s, & one DEAD

5 x ASUS Radeon R9 280x 3GB: 1,047Kh/s, 1,047Kh/s, 1,047Kh/s, 1,047Kh/s & one DEAD
5 x ASUS Radeon R9 280x 3GB: 1,047Kh/s, 1,047Kh/s, 1,047Kh/s, 1,047Kh/s & one DEAD
4 x ASUS Radeon R9 280x 3GB: 1,047Kh/s, 1,047Kh/s, 1,047Kh/s & one DEAD

5 x MSI Radeon R9 3 GB: 998h/s, 998h/s, 998h/s, 998h/s, 998h/s

Anyone got any idea why one card is always dead in each rig from Sapphire/ASUS but not from the MSI-cards?
Before mininig at N14 they didn't go DEAD/Sick...?

Quote from: barbados-fs on January 24, 2015, 06:22:25 AM

Friends share settings for R9 28x 0and R9 270x. Just not here - http://cfg.ultracoin.net/ the result is less than it should be.
Thank U.

Try slowing down the engine speed of the gpu going sick, example --gpu-engine 1040,1040,1040,1000,1000
or turn down the raw intensity by using individual -R values for each, example -R 2560,2560,2560,2432,2432 (decreased in increments of the work size setting of 128)
or if using windows try increasing the amount of virtual memory your hard drive is using

Any combination of this worked for my rigs when that happens

wtfc360

full member

Activity: 137

Merit: 100

I use the data from configgen and have this setup for all my rigs:
C:\Users\Mining1\Desktop\Yacminer-3.5.0-yac2-x86\yacminer.exe --scrypt-chacha -o stratum+tcp://stratum2.tumblingblock.com:5555 -u worker.1 -p password -R 2560 -g 1 -w 128 --buffer-size 2590 --lookup-gap 8 --temp-cutoff 85 --nfmin 4 --nfmax 30 --starttime 1388361600

From that I get different results for every rig:

5 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 490h/s ,139h/s & one SICK
5 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 998h/s, 362h/s & one DEAD
5 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 490h/s ,139h/s & one SICK
4 x Sapphire Dual-x R9 280x 3GB: 998h/s, 998h/s, 998h/s, & one DEAD

5 x ASUS Radeon R9 280x 3GB: 1,047Kh/s, 1,047Kh/s, 1,047Kh/s, 1,047Kh/s & one DEAD
5 x ASUS Radeon R9 280x 3GB: 1,047Kh/s, 1,047Kh/s, 1,047Kh/s, 1,047Kh/s & one DEAD
4 x ASUS Radeon R9 280x 3GB: 1,047Kh/s, 1,047Kh/s, 1,047Kh/s & one DEAD

5 x MSI Radeon R9 3 GB: 998h/s, 998h/s, 998h/s, 998h/s, 998h/s

Anyone got any idea why one card is always dead in each rig from Sapphire/ASUS but not from the MSI-cards?
Before mininig at N14 they didn't go DEAD/Sick...?

Quote from: barbados-fs on January 24, 2015, 06:22:25 AM

Friends share settings for R9 28x 0and R9 270x. Just not here - http://cfg.ultracoin.net/ the result is less than it should be.
Thank U.

barbados-fs

hero member

Activity: 837

Merit: 505

Friends share settings for R9 28x 0and R9 270x. Just not here - http://cfg.ultracoin.net/ the result is less than it should be.
Thank U.

king_pin

sr. member

Activity: 416

Merit: 250

Someone found good settings for NVIDIA 970 cards?
Autotune makes my rig crash Sad

wtfc360

full member

Activity: 137

Merit: 100

I'm not sure I'm answering your question, but you can clear the orphans in the transaction tab by rightclick on any transaction and a new window will appear, choose "clear orphans" and the orphans will disappear...

Quote from: dan_and_shan on January 24, 2015, 03:09:00 AM

Gday
just a question is there anyway to limit "generated but not accepted".

Regards Dan

dan_and_shan

sr. member

Activity: 433

Merit: 250

Gday
just a question is there anyway to limit "generated but not accepted".

Regards Dan

volyova

legendary

Activity: 910

Merit: 1000

Quote from: rapture333 on January 23, 2015, 11:30:26 PM

@SecretsOfCrypto

Rapture has always been my online alias; in the beginning anonymity was important to me, just like many in the crypto word, but it is much less so now that I am doing professional work for Ultracoin and using my full name all the time. I am not a hard target to dox either.

Is it a religious rapture, or just a normal rapture? Tongue

Topic: [Ultracoin] [Est. Feb 2014] ~ ASIC Resistant & Ultrafast 6 Second Transactions! - page 166. (Read 381060 times)