Well, I couldn't get it to work right and I just don't have the patience to deal with it anymore since I'm not mining it currently as detailed in a previous post. Though, I will point out a curiousity that happened last time I solo mined and it happened again.
I get a share well above the necessary amount to find a block. I didn't see it happen. All I know is it shows up in my best share area as 115k. It doesn't show up in my wallet as a transaction at all. Not an orphan, not anything. No rejects or accepted in the miner. It's like that share never happened. The last 4 times I've had a share above the target while solo mining, I've seen no evidence that anything happened. I can't figure it out.
I'm soloing another coin right now, all things are as expected. Accepted shares show up as the current difficulty under A:. Rejects do the same under R: Accepted shares that are orphaned show up as transactions that never make it to my balance, or as orphans when in the debug screen.
Something funny is going on with this coin or my wallet when solo mining.
Topic: [ANN] [ASIC-RESISTANT] UltraCoin (UTC) - Ultrafast 6 second transactions!! - page 281. (Read 946650 times)
April 05, 2014, 11:09:08 PM
April 05, 2014, 11:00:47 PM
Though I'm close, I'm using 4 different TC's for each card, my setup will be of no use to anyone for 290x, or perhaps one of the 4 might help 1 of 4 people... who knows.
Ye many miners may have to increase system RAM, hoping I can squeeze by with 8GB and 3 GPU; gonna be close if so.
edit: think I'm at 0 HW's!! woot
care to share a pointer or two? i have 16GB RAM on my system with 3 7950s and keep figuring out new ways to BSOD
Sure, still playing but here's where I'm at with 0 HW's and getting 48.8 Kh/s per card. WU showing 125 (3 cards in rig) but not long enough to settle. Vitural RAM set @ default (same as system) 8192mb
For sapphire: 1060-1080 Clock and 1600Mhz RAM
For Powercolor: 1050 Clock and 1500 Mhz RAM
Code:
ultracoinminer (pool info) --scrypt-jane --sj-nfmin 4 --sj-nfmax 30 --sj-time 1388361600 --failover-only --thread-concurrency 62720 --intensity 18 --lookup-gap 3 --gpu-powertune 20 --worksize 256 --gpu-dyninterval 5 --no-submit-stale -g 1 --scan-time 1 --expiry 10 --queue 0
Proud to be running -g 1 still
edit: not sure of catalyst / adl / sdk versions; but they're probably 10 months old.
my cards seem happy after a few minutes of running. thanks again.
April 05, 2014, 10:58:04 PM
As a temporary fix to get your rig running,
lower the intensity by 1 and reduce your total thread concurrency by a number
equal to the shaders count on your card.
Example: a 7950 card has 1792 shaders so the current TC should be 16384-1792= 14592
If your rig is still showing everything running normal, this is a false positive,
restart your rig and apply the new settings.
This is also a good time to check your virtual ram setting on windows systems
and set that at a size 3 or 4 times of what windows have set it at.
lower the intensity by 1 and reduce your total thread concurrency by a number
equal to the shaders count on your card.
Example: a 7950 card has 1792 shaders so the current TC should be 16384-1792= 14592
If your rig is still showing everything running normal, this is a false positive,
restart your rig and apply the new settings.
This is also a good time to check your virtual ram setting on windows systems
and set that at a size 3 or 4 times of what windows have set it at.
On a 4 gpu rig, lowering my TC actually increases my HW errors. This has been true since the last N-factor.
+1 decreasing has always given me HW increasing always made them go away
I found upping GPU cores helped last time
so far only dropped I 1 level
I also use small work sizes
using TC 65536 will tweak them later on
2560 shaders is what I think R9 290's had ..
got an excel sheet I worked on that’s got the new N factor setting on it somewhere ...
I think 3472MB was the MAX amount of RAM avail for GPU
April 05, 2014, 10:55:48 PM
Though I'm close, I'm using 4 different TC's for each card, my setup will be of no use to anyone for 290x, or perhaps one of the 4 might help 1 of 4 people... who knows.
Ye many miners may have to increase system RAM, hoping I can squeeze by with 8GB and 3 GPU; gonna be close if so.
edit: think I'm at 0 HW's!! woot
Okay. I'm now at 56KH/s for each 280x accepting shares. Averaging 50 WU each,
But I got 1-2 HW errors on some and 0 on some others. Not perfect but close!
My 4 x 280x rigs only have 4GB RAM. I just had to raise the swap file to 32768.
Still tweaking....
How did you manage this? Before the change i was getting 152 while everyone else seemed to be getting 135ish. Now i cant get over 41. I've got 16gb ram using I11 and all TCs from 8k to 24k in 2048 increments.
April 05, 2014, 10:45:03 PM
Though I'm close, I'm using 4 different TC's for each card, my setup will be of no use to anyone for 290x, or perhaps one of the 4 might help 1 of 4 people... who knows.
Ye many miners may have to increase system RAM, hoping I can squeeze by with 8GB and 3 GPU; gonna be close if so.
edit: think I'm at 0 HW's!! woot
care to share a pointer or two? i have 16GB RAM on my system with 3 7950s and keep figuring out new ways to BSOD
Sure, still playing but here's where I'm at with 0 HW's and getting 48.8 Kh/s per card. WU showing 125 (3 cards in rig) but not long enough to settle. Vitural RAM set @ default (same as system) 8192mb
For sapphire: 1060-1080 Clock and 1600Mhz RAM
For Powercolor: 1050 Clock and 1500 Mhz RAM
Code:
ultracoinminer (pool info) --scrypt-jane --sj-nfmin 4 --sj-nfmax 30 --sj-time 1388361600 --failover-only --thread-concurrency 62720 --intensity 18 --lookup-gap 3 --gpu-powertune 20 --worksize 256 --gpu-dyninterval 5 --no-submit-stale -g 1 --scan-time 1 --expiry 10 --queue 0
Proud to be running -g 1 still
edit: not sure of catalyst / adl / sdk versions; but they're probably 10 months old.
April 05, 2014, 10:44:41 PM
As a temporary fix to get your rig running,
lower the intensity by 1 and reduce your total thread concurrency by a number
equal to the shaders count on your card.
Example: a 7950 card has 1792 shaders so the current TC should be 16384-1792= 14592
If your rig is still showing everything running normal, this is a false positive,
restart your rig and apply the new settings.
This is also a good time to check your virtual ram setting on windows systems
and set that at a size 3 or 4 times of what windows have set it at.
lower the intensity by 1 and reduce your total thread concurrency by a number
equal to the shaders count on your card.
Example: a 7950 card has 1792 shaders so the current TC should be 16384-1792= 14592
If your rig is still showing everything running normal, this is a false positive,
restart your rig and apply the new settings.
This is also a good time to check your virtual ram setting on windows systems
and set that at a size 3 or 4 times of what windows have set it at.
On a 4 gpu rig, lowering my TC actually increases my HW errors. This has been true since the last N-factor.
April 05, 2014, 10:42:36 PM
As a temporary fix to get your rig running,
lower the intensity by 1 and reduce your total thread concurrency by a number
equal to the shaders count on your card.
Example: a 7950 card has 1792 shaders so the current TC should be 16384-1792= 14592
If your rig is still showing everything running normal, this is a false positive,
restart your rig and apply the new settings.
This is also a good time to check your virtual ram setting on windows systems
and set that at a size 3 or 4 times of what windows have set it at.
lower the intensity by 1 and reduce your total thread concurrency by a number
equal to the shaders count on your card.
Example: a 7950 card has 1792 shaders so the current TC should be 16384-1792= 14592
If your rig is still showing everything running normal, this is a false positive,
restart your rig and apply the new settings.
This is also a good time to check your virtual ram setting on windows systems
and set that at a size 3 or 4 times of what windows have set it at.
April 05, 2014, 10:35:31 PM
Though I'm close, I'm using 4 different TC's for each card, my setup will be of no use to anyone for 290x, or perhaps one of the 4 might help 1 of 4 people... who knows.
Ye many miners may have to increase system RAM, hoping I can squeeze by with 8GB and 3 GPU; gonna be close if so.
edit: think I'm at 0 HW's!! woot
yes, the 8GB with 4 GPU is my problem, I'm well aware, just trying to work around the limitation right now. I have 3 running without HW errors right now, can't pull in the 4th.
April 05, 2014, 10:35:08 PM
Though I'm close, I'm using 4 different TC's for each card, my setup will be of no use to anyone for 290x, or perhaps one of the 4 might help 1 of 4 people... who knows.
Ye many miners may have to increase system RAM, hoping I can squeeze by with 8GB and 3 GPU; gonna be close if so.
edit: think I'm at 0 HW's!! woot
care to share a pointer or two? i have 16GB RAM on my system with 3 7950s and keep figuring out new ways to BSOD
April 05, 2014, 10:34:54 PM
Though I'm close, I'm using 4 different TC's for each card, my setup will be of no use to anyone for 290x, or perhaps one of the 4 might help 1 of 4 people... who knows.
Ye many miners may have to increase system RAM, hoping I can squeeze by with 8GB and 3 GPU; gonna be close if so.
edit: think I'm at 0 HW's!! woot
Okay. I'm now at 56KH/s for each 280x accepting shares. Averaging 50 WU each,
But I got 1-2 HW errors on some and 0 on some others. Not perfect but close!
My 4 x 280x rigs only have 4GB RAM. I just had to raise the swap file to 32768.
Still tweaking....
April 05, 2014, 10:25:14 PM
Looks like I cannot mine without more RAM too, this change is quite dramatic.
Ye many miners may have to increase system RAM, hoping I can squeeze by with 8GB and 3 GPU; gonna be close if so.
Though I'm close, I'm using 4 different TC's for each card, my setup will be of no use to anyone for 290x, or perhaps one of the 4 might help 1 of 4 people... who knows.
Ye many miners may have to increase system RAM, hoping I can squeeze by with 8GB and 3 GPU; gonna be close if so.
April 05, 2014, 10:22:13 PM
Though I'm close, I'm using 4 different TC's for each card, my setup will be of no use to anyone for 290x, or perhaps one of the 4 might help 1 of 4 people... who knows.
Ye many miners may have to increase system RAM, hoping I can squeeze by with 8GB and 3 GPU; gonna be close if so.
edit: think I'm at 0 HW's!! woot
April 05, 2014, 10:19:49 PM
Though I'm close, I'm using 4 different TC's for each card, my setup will be of no use to anyone for 290x, or perhaps one of the 4 might help 1 of 4 people... who knows.
April 05, 2014, 10:13:51 PM
still bugging out the HW's on the 7950's though I'm getting them rarely, so hopefully close. seems they are in the 45-48 Kh/s range. I'll keep pluggin away
April 05, 2014, 10:09:09 PM
MSI 7950 = 36kh no HW (1030/1250) I=11 .Anyone have better setting?
April 05, 2014, 10:06:40 PM
so was their an N factor change or not ? mine are still running the same as before ??
Mine were too during the last N-factor change until I restarted my miner, at least it said they were. Turned out everything was HW errors, it just didn't show it until restart.
Has anyone got over 37kh/s with 280x yet? (I can get 45kh/s with no errors but it also gets no shares. =p)
April 05, 2014, 10:06:19 PM
Diff is 0.78....get em runnin! Nitro down to 1000 miners April 05, 2014, 10:03:33 PM
so was their an N factor change or not ? mine are still running the same as before ??
Mine were too during the last N-factor change until I restarted my miner, at least it said they were. Turned out everything was HW errors, it just didn't show it until restart.
April 05, 2014, 10:00:19 PM
so was their an N factor change or not ? mine are still running the same as before ??
yes it changed April 05, 2014, 09:56:29 PM
so was their an N factor change or not ? mine are still running the same as before ??
was already running TC 65536 with 4 x GPU threads ... looks like it was compatible with N factor change
was already running TC 65536 with 4 x GPU threads ... looks like it was compatible with N factor change
Jump to: