Author

Topic: Number 9! Ninth altcoin thread. Back to the moon Baby! - page 147. (Read 66169 times)

legendary
Activity: 3724
Merit: 3836
I am getting old simply can't remember shit.

So I had an old bminer 14.0  and fork killed it off.

I loaded bminer 15.7.2  and I get rejected shares.

I am remote to these rigs.  So 15.7.2 does not work.

[WARN] [2019-07-22T03:57:03+02:00] Rejected share #0 (Unknown)
[INFO] [2019-07-22T03:57:04+02:00] [GPU 0] Speed: 5.93 G/s Fidelity 1.395 Temp: 64C Fan: 61% Power: 106W 0.06 G/J
[INFO] [2019-07-22T03:57:04+02:00] [GPU 1] Speed: 5.49 G/s Fidelity 0.971 Temp: 52C Fan: 61% Power: 117W 0.05 G/J
[INFO] [2019-07-22T03:57:04+02:00] Total 11.42 G/s Accepted shares 0 Rejected shares 21
[WARN] [2019-07-22T03:57:07+02:00] Rejected share #0 (Unknown)
[INFO] [2019-07-22T03:57:08+02:00] Received new job 112296032
[INFO] [2019-07-22T03:57:12+02:00] Received new job 113360992
[WARN] [2019-07-22T03:57:26+02:00] Rejected share #0 (Unknown)
[INFO] [2019-07-22T03:57:29+02:00] Received new job 113361504
[WARN] [2019-07-22T03:57:29+02:00] Rejected share #0 (Unknown)
[WARN] [2019-07-22T03:57:29+02:00] Get error: Too many rejected shares, resetting in 5 seconds
[INFO] [2019-07-22T03:57:34+02:00] [GPU 0] Speed: 5.90 G/s Fidelity 1.293 Temp: 65C Fan: 61% Power: 147W 0.04 G/J
[INFO] [2019-07-22T03:57:34+02:00] [GPU 1] Speed: 5.47 G/s Fidelity 0.861 Temp: 53C Fan: 61% Power: 110W 0.05 G/J
[INFO] [2019-07-22T03:57:34+02:00] Total 11.37 G/s Accepted shares 0 Rejected shares 24
[INFO] [2019-07-22T03:57:34+02:00] Connected to grin29.f2pool.com:13654
[INFO] [2019-07-22T03:57:35+02:00] Authorized with the server
[INFO] [2019-07-22T03:57:35+02:00] Received new job 113360992



If you ever want to go back to bminer 15.7.2, I got the same (rejected shares), but the solution is simple:
make sure that you specified cuckaroo29d instead of cuckaroo29 (note extra "d") in your bminer string.
After that it worked fine (no rejected shares).
legendary
Activity: 4088
Merit: 7701
'The right to privacy matters'
Thanks citronick  got it back and running.


--algo cuckarood29 --pers auto --server grin29-us.f2pool.com --port 13654 --user philipma1957.one —pass x --api 3333

--algo cuckarood29 --pers auto --server grin29-us.f2pool.com --port 13654 --user philipma1957.two —pass x --api 3333

--algo cuckarood29 --pers auto --server grin29-us.f2pool.com --port 13654 --user philipma1957.three —pass x --api 3333



There is a miner called nbminer-nebutech that seems to be quite popular too. Maybe this miner can do NH.

Its cool I am happy with f2pool
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
Thanks citronick  got it back and running.


--algo cuckarood29 --pers auto --server grin29-us.f2pool.com --port 13654 --user philipma1957.one —pass x --api 3333

--algo cuckarood29 --pers auto --server grin29-us.f2pool.com --port 13654 --user philipma1957.two —pass x --api 3333

--algo cuckarood29 --pers auto --server grin29-us.f2pool.com --port 13654 --user philipma1957.three —pass x --api 3333



There is a miner called nbminer-nebutech that seems to be quite popular too. Maybe this miner can do NH.
legendary
Activity: 4088
Merit: 7701
'The right to privacy matters'
Thanks citronick  got it back and running.


--algo cuckarood29 --pers auto --server grin29-us.f2pool.com --port 13654 --user philipma1957.one —pass x --api 3333

--algo cuckarood29 --pers auto --server grin29-us.f2pool.com --port 13654 --user philipma1957.two —pass x --api 3333

--algo cuckarood29 --pers auto --server grin29-us.f2pool.com --port 13654 --user philipma1957.three —pass x --api 3333

legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
I am getting old simply can't remember shit.

So I had an old bminer 14.0  and fork killed it off.

I loaded bminer 15.7.2  and I get rejected shares.

I am remote to these rigs.  So 15.7.2 does not work.

,
,
,

back to gminer 1.52

I am using this

--algo grin29://philipma1957.005:[email protected]:13654 -api 3333

which is not right

can someone show me a bat to mine with nice hash or f2pool

the forked algo is cuckarood29 ..... see that extra "d"

gminer-v1.52   

--algo cuckarood29 --pers auto --server grin29.f2pool.com --port 13654 --user citronick --pass x --api 3333


4 x 1080ti
=====
04:25:52 GPU3 Share Accepted 136 ms
04:25:52 GPU2 Share Accepted 135 ms
04:25:55 GPU1 Share Accepted 134 ms
04:25:58 GPU3 Share Accepted 135 ms
04:26:00 New Job: 94603344 Difficulty: 16
04:26:00 New Job: 94619728 Difficulty: 16
04:26:10 GPU2 Share Accepted 136 ms
04:26:15 Temperature: GPU0 63C GPU1 59C GPU2 57C GPU3 49C
04:26:15 Speed: GPU0 7.18 G/s GPU1 7.51 G/s GPU2 7.30 G/s GPU3 7.25 G/s
04:26:15 Accepted Shares: GPU0 17 GPU1 15 GPU2 16 GPU3 12
04:26:15 Rejected Shares: GPU0 0 GPU1 0 GPU2 0 GPU3 0
04:26:15 Fidelity: GPU0 2.301 GPU1 1.979 GPU2 1.995 GPU3 1.872
04:26:15 Power: GPU0 156W 0.05 G/W GPU1 155W 0.05 G/W GPU2 158W 0.05 G/W GPU3 154W 0.05 G/W
04:26:15 Total Speed: 29.24 G/s Fidelity: 2.037 Shares Accepted: 60 Rejected: 0 Power: 623W 0.05 G/W
04:26:15 Uptime: 0d 00:03:00 Electricity: 0.030kWh
04:26:15 New Job: 94620240 Difficulty: 32
04:26:15 GPU0 Share Accepted 135 ms
======
legendary
Activity: 4088
Merit: 7701
'The right to privacy matters'
Use gminer 1.51 or higher, bminer have problems when fork happened

yeah I got that but I never had a working  miner for nicehash or for f2pool

does some one have a bat to run it at either pool

how about this ?

--algo grin29 --server stratum+tcp://grincuckaroo29.usa.nicehash.com --port 3371 --user 146UJM5kgzLVUV23CXCf33KQKHckoX1gx3 --pass x --api 3333
member
Activity: 224
Merit: 18
Use gminer 1.51 or higher, bminer have problems when fork happened
legendary
Activity: 4088
Merit: 7701
'The right to privacy matters'
I am getting old simply can't remember shit.

So I had an old bminer 14.0  and fork killed it off.

I loaded bminer 15.7.2  and I get rejected shares.

I am remote to these rigs.  So 15.7.2 does not work.

[WARN] [2019-07-22T03:57:03+02:00] Rejected share #0 (Unknown)
[INFO] [2019-07-22T03:57:04+02:00] [GPU 0] Speed: 5.93 G/s Fidelity 1.395 Temp: 64C Fan: 61% Power: 106W 0.06 G/J
[INFO] [2019-07-22T03:57:04+02:00] [GPU 1] Speed: 5.49 G/s Fidelity 0.971 Temp: 52C Fan: 61% Power: 117W 0.05 G/J
[INFO] [2019-07-22T03:57:04+02:00] Total 11.42 G/s Accepted shares 0 Rejected shares 21
[WARN] [2019-07-22T03:57:07+02:00] Rejected share #0 (Unknown)
[INFO] [2019-07-22T03:57:08+02:00] Received new job 112296032
[INFO] [2019-07-22T03:57:12+02:00] Received new job 113360992
[WARN] [2019-07-22T03:57:26+02:00] Rejected share #0 (Unknown)
[INFO] [2019-07-22T03:57:29+02:00] Received new job 113361504
[WARN] [2019-07-22T03:57:29+02:00] Rejected share #0 (Unknown)
[WARN] [2019-07-22T03:57:29+02:00] Get error: Too many rejected shares, resetting in 5 seconds
[INFO] [2019-07-22T03:57:34+02:00] [GPU 0] Speed: 5.90 G/s Fidelity 1.293 Temp: 65C Fan: 61% Power: 147W 0.04 G/J
[INFO] [2019-07-22T03:57:34+02:00] [GPU 1] Speed: 5.47 G/s Fidelity 0.861 Temp: 53C Fan: 61% Power: 110W 0.05 G/J
[INFO] [2019-07-22T03:57:34+02:00] Total 11.37 G/s Accepted shares 0 Rejected shares 24
[INFO] [2019-07-22T03:57:34+02:00] Connected to grin29.f2pool.com:13654
[INFO] [2019-07-22T03:57:35+02:00] Authorized with the server
[INFO] [2019-07-22T03:57:35+02:00] Received new job 113360992



back to gminer 1.52

I am using this

--algo grin29://philipma1957.005:[email protected]:13654 -api 3333

which is not right

can someone show me a bat to mine with nice hash or f2pool
legendary
Activity: 3724
Merit: 3836
on Ubuntu linux 16.04, Nvidia 1080ti cards
grin fork works fine with bminer 15.7.2
legendary
Activity: 4088
Merit: 7701
'The right to privacy matters'
With grin 29 fork. What do I need to do to get my simple Mining back on track.?

I pointed my 1080ti to bci for last few days.

Would prefer to mine grin

Phil,

Gminer since v1.51 supports the fork - see GITHUB
SMOS has v1.52 updated.

1.51
@develsoftware develsoftware released this 6 days ago
added Cuckarood29 algorithm for Nvidia cards (use --algo grin29 for autoswitch after hardfork)


okay let me check
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
With grin 29 fork. What do I need to do to get my simple Mining back on track.?

I pointed my 1080ti to bci for last few days.

Would prefer to mine grin

Phil,

Gminer since v1.51 supports the fork - see GITHUB
SMOS has v1.52 updated.

1.51
@develsoftware develsoftware released this 6 days ago
added Cuckarood29 algorithm for Nvidia cards (use --algo grin29 for autoswitch after hardfork)
legendary
Activity: 4088
Merit: 7701
'The right to privacy matters'
With grin 29 fork. What do I need to do to get my simple Mining back on track.?

I pointed my 1080ti to bci for last few days.

Would prefer to mine grin
hero member
Activity: 729
Merit: 513



I was able to get the rig to push 338mhs at Nicehash@DaggerHashimoto, using PhoenixMiner and recommended amdmemorytweak utility inserted in the advanced tool settings on the SMOS dashboard. Great help from the SMOS Discord channel.

BogdanCo settings is even better but my rig couldn't handle it, so I had to settle for 42-43mhs per Vega




You can try 1000 core, 1075 mem @ 850mV with amdmemorytweak --rp 12 --rc 44 --rfc 250 --rrds 3 --rrdl 3 --rcdrd 12 --rcdwr 5 --CL 19 --RAS 28 --REF 15600
Should get ~48.2 Mh/s ETH / Vega64 and stable with no rejected shares...

With these settings on PhoenixMiner ..... rig is alive bt #GPU4 stay 0mhs.... the 7 x Vegas are working fine - could this be a bad GPU?

All of them are Sapphire reference? I have a 6x MSI Reference cards for which I had to set 875mV to be stable. For the rest of Sapphire (Reference) and ASUS (not Reference) 850mV works quite well.
legendary
Activity: 1848
Merit: 1165
My AR-15 ID's itself as a toaster. Want breakfast?
yeah, i was drawn away from those style of boards because you are adding more points of failure to power distribution; more contact points, cables, etc....

This is why I loved the D8P soo much;  aside from the 8+4.
legendary
Activity: 4088
Merit: 7701
'The right to privacy matters'
I'm kind of worried that 1200W+ is running through the traces in the board. At the same time I wonder if it's possible to push 8x Vega VII at 250W each  Grin

Bought one of these similar boards as sample today, but has a cpu socket to use a G4560 instead of the soldered 3865U. It's slightly cheaper than the onda boards and most importantly $86 USD Bitmain APW7 can be used instead of 1500w titaniums.

If on Windows..... I may share the same concerns with you... that's why putting this on Linux SMOS with tighter power controls is preferred without messing with Windows, registry, power-tables etc.

The 2400w Deltas are rated 94% platinums - I have got a bunch of these (during Parallel Miner firesales). They are really a live saver and I dont have to worry about number of cables needed even for heavy duty GPUs like 1080tis or 32 cables....

you do not need to setup with all that power into the mobo

psu send 6 pcie to mobo

psu send 8 pcie to cards

do not feed a lot of cables out of the mobo into the cards.

less energy goes into the mobo.

somewhere some place I did photos on this board  and

 sending cables right to the cards = better

then cables to mobos to cards

the mobo still needs 6 cables into it for the slots to be powered.

it does not need any out of it into the cards.

although it is neater wiring .
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----



I was able to get the rig to push 338mhs at Nicehash@DaggerHashimoto, using PhoenixMiner and recommended amdmemorytweak utility inserted in the advanced tool settings on the SMOS dashboard. Great help from the SMOS Discord channel.

BogdanCo settings is even better but my rig couldn't handle it, so I had to settle for 42-43mhs per Vega




You can try 1000 core, 1075 mem @ 850mV with amdmemorytweak --rp 12 --rc 44 --rfc 250 --rrds 3 --rrdl 3 --rcdrd 12 --rcdwr 5 --CL 19 --RAS 28 --REF 15600
Should get ~48.2 Mh/s ETH / Vega64 and stable with no rejected shares...

With these settings on PhoenixMiner ..... rig is alive bt #GPU4 stay 0mhs.... the 7 x Vegas are working fine - could this be a bad GPU?
hero member
Activity: 729
Merit: 513



I was able to get the rig to push 338mhs at Nicehash@DaggerHashimoto, using PhoenixMiner and recommended amdmemorytweak utility inserted in the advanced tool settings on the SMOS dashboard. Great help from the SMOS Discord channel.

BogdanCo settings is even better but my rig couldn't handle it, so I had to settle for 42-43mhs per Vega




You can try 1000 core, 1075 mem @ 850mV with amdmemorytweak --rp 12 --rc 44 --rfc 250 --rrds 3 --rrdl 3 --rcdrd 12 --rcdwr 5 --CL 19 --RAS 28 --REF 15600
Should get ~48.2 Mh/s ETH / Vega64 and stable with no rejected shares...
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
I'm kind of worried that 1200W+ is running through the traces in the board. At the same time I wonder if it's possible to push 8x Vega VII at 250W each  Grin

Bought one of these similar boards as sample today, but has a cpu socket to use a G4560 instead of the soldered 3865U. It's slightly cheaper than the onda boards and most importantly $86 USD Bitmain APW7 can be used instead of 1500w titaniums.

If on Windows..... I may share the same concerns with you... that's why putting this on Linux SMOS with tighter power controls is preferred without messing with Windows, registry, power-tables etc.

The 2400w Deltas are rated 94% platinums - I have got a bunch of these (during Parallel Miner firesales). They are really a live saver and I dont have to worry about number of cables needed even for heavy duty GPUs like 1080tis or 32 cables....
sr. member
Activity: 610
Merit: 265
I'm kind of worried that 1200W+ is running through the traces in the board. At the same time I wonder if it's possible to push 8x Vega VII at 250W each  Grin

Bought one of these similar boards as sample today, but has a cpu socket to use a G4560 instead of the soldered 3865U. It's slightly cheaper than the onda boards and most importantly $86 USD Bitmain APW7 can be used instead of 1500w titaniums.
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
Finally the Vegas are on SMOS (Vega version)...

Any suggestions on how to further optimize watts and hash?

8 x Vega64 / 300MHs / 37.xxMHs per card

I can push memory higher to 1100 to achieve 44Mhs per card
but I am worried about overall watts consumed by this rig
currently just under 1300watts.

The Vegas have Samsung memory.
PSU is 2400w Delta.

I haven't experiment with eliovp's auto-mem utility and rxboost.

*** eliovp, tytanick - if you guys are reading this post, please advise.

.
.
.

Curious how the power delivery works for this mobo.

Is it just 8x 6pin input from PSU, then 8x 6pin output from mobo, which goes into a splitter and then into the Vegas?

This board is quite simple, just like what you described above.

The splitter is quite safe since total watts less per splitter is way less than 300w - as per SMOS and the clock settings, max watts per card around 130watts per Vega64.

Surprisingly quite cooling this setup, since this Gen1 Vegas are reference blower type.

I got these boards from Letine.





I was able to get the rig to push 338mhs at Nicehash@DaggerHashimoto, using PhoenixMiner and recommended amdmemorytweak utility inserted in the advanced tool settings on the SMOS dashboard. Great help from the SMOS Discord channel.

BogdanCo settings is even better but my rig couldn't handle it, so I had to settle for 42-43mhs per Vega



Jump to: