I'm getting this too often: " Pool vtc.suprnova.cc rpc timed out after 69 seconds. Reconnecting."
Me too - different pool tho.
Lyra2rev3, Win 10, Vega 64.
Topic: [ANN] TeamRedMiner - Optimized Win/Linux AMD GPU Miner for lyra2z and phi2 - page 24. (Read 85791 times)
February 04, 2019, 05:49:52 PM
Me too - different pool tho.
Lyra2rev3, Win 10, Vega 64.
February 04, 2019, 01:51:37 AM
That's what i was thinking too but never have messed much with it.
Ok so on GPU P0-P7 and Memory P0-P3 i have them all set to 900mv. Which value would be the core?
Ok so on GPU P0-P7 and Memory P0-P3 i have them all set to 900mv. Which value would be the core?
I'd start bumping it +5mV at the time, and only for the problematic GPUs. Are you using OverdriveNTool? If so, it's good to run the miner with --bus_reorder so you get a GPU order that matches the PCIe bus id order, which is what ONT is using iirc.
You can also run the miner with --debug and you'll see the current values for clocks and voltages read from ADL. This would be to verify that you have increased the voltage for the correct GPU. Note: I assumed you're running on Windows here, but I believe it would work under linux as well, although you'd have to use other tools to set clocks/voltages of course.
That seemed to do the trick! everything is now running perfectly! Saw another guy get around close to what i got on hash rate so i think i'm good.
February 03, 2019, 10:47:48 PM
I'm getting 58.8Mhs@135Wt with Fury cards in lyra2rev3. Though they are 60CU, not 56.
How can you do this? 135W? this is info from wattmeter? What settings? I get more 200W with -125mV !
February 03, 2019, 10:21:15 PM
Does this miner supports old Tahiti GPUs (Radeon 7950/R9 280)?
Unfortunately not, we support GCN 3 and up, Fiji and Tonga being the oldest archs supported.
We wait kernel for hawaii!! This is strong and good GPUs!
February 03, 2019, 09:59:35 PM
Lyra2REv3 TEST
VEGA 56 84mh/s 1408/900 950/910 200w
VEGA 64 air coole 96mhs/s 1408/900 1000/900 200w
rx570 45mh/s 1290/900 2000/880 110w
VEGA 56 84mh/s 1408/900 950/910 200w
VEGA 64 air coole 96mhs/s 1408/900 1000/900 200w
rx570 45mh/s 1290/900 2000/880 110w
February 03, 2019, 04:50:04 PM
That's what i was thinking too but never have messed much with it.
Ok so on GPU P0-P7 and Memory P0-P3 i have them all set to 900mv. Which value would be the core?
Ok so on GPU P0-P7 and Memory P0-P3 i have them all set to 900mv. Which value would be the core?
I'd start bumping it +5mV at the time, and only for the problematic GPUs. Are you using OverdriveNTool? If so, it's good to run the miner with --bus_reorder so you get a GPU order that matches the PCIe bus id order, which is what ONT is using iirc.
You can also run the miner with --debug and you'll see the current values for clocks and voltages read from ADL. This would be to verify that you have increased the voltage for the correct GPU. Note: I assumed you're running on Windows here, but I believe it would work under linux as well, although you'd have to use other tools to set clocks/voltages of course.
February 03, 2019, 04:33:04 PM
That's what i was thinking too but never have messed much with it.
Ok so on GPU P0-P7 and Memory P0-P3 i have them all set to 900mv. Which value would be the core?
Ok so on GPU P0-P7 and Memory P0-P3 i have them all set to 900mv. Which value would be the core?
February 03, 2019, 04:26:03 PM
Trying out the latest version and the duplicate error have disappeared for me and rejected rate down to almost 0%. Very nice! Hash rate seems to gone up a bit for most my cards.
The only thing i'm trying to fix is that on two of my miners, i have one dead gpu. Not sure if that means i have to mess around with my overclock settings. They all start off ok but anywhere between 1-10 minutes a card just dies and i don't know why.
And I agree with the sentiment that adding some other algorithms like mimble wimble would be pretty nice. The options for amd for new algorithms is sadly lacking.
The only thing i'm trying to fix is that on two of my miners, i have one dead gpu. Not sure if that means i have to mess around with my overclock settings. They all start off ok but anywhere between 1-10 minutes a card just dies and i don't know why.
And I agree with the sentiment that adding some other algorithms like mimble wimble would be pretty nice. The options for amd for new algorithms is sadly lacking.
It sounds like a classic clock tweak situation, they just need some TLC. Lower core clk and/or higher core voltage, try it in small increments.
February 03, 2019, 04:23:19 PM
Trying out the latest version and the duplicate error have disappeared for me and rejected rate down to almost 0%. Very nice! Hash rate seems to gone up a bit for most my cards.
The only thing i'm trying to fix is that on two of my miners, i have one dead gpu. Not sure if that means i have to mess around with my overclock settings. They all start off ok but anywhere between 1-10 minutes a card just dies and i don't know why.
And I agree with the sentiment that adding some other algorithms like mimble wimble would be pretty nice. The options for amd for new algorithms is sadly lacking.
The only thing i'm trying to fix is that on two of my miners, i have one dead gpu. Not sure if that means i have to mess around with my overclock settings. They all start off ok but anywhere between 1-10 minutes a card just dies and i don't know why.
And I agree with the sentiment that adding some other algorithms like mimble wimble would be pretty nice. The options for amd for new algorithms is sadly lacking.
February 03, 2019, 03:45:34 PM
Also, the kernels are designed to handle a downclock of mem all the way down to 300 MHz on Polaris cards and 500 MHz on Vegas, this without hashrate being affected. It probably won't save more than 1-2W per gpu, but always something.
Speed with memory on 300MHz is slower than on full speed... About 1 MH on my RX 580 8GbYMMV, the 580 in my test rig handles it fine. It's such a tiny power save anyway, just find the spot where you don't lose perf, I've seen people putting it around 1000-1100 MHz, for example. Out of curiosity though, is this your 580 driving monitor(s)?
February 03, 2019, 02:17:35 PM
Also, the kernels are designed to handle a downclock of mem all the way down to 300 MHz on Polaris cards and 500 MHz on Vegas, this without hashrate being affected. It probably won't save more than 1-2W per gpu, but always something.
Speed with memory on 300MHz is slower than on full speed... About 1 MH on my RX 580 8GbYMMV, the 580 in my test rig handles it fine. It's such a tiny power save anyway, just find the spot where you don't lose perf, I've seen people putting it around 1000-1100 MHz, for example. Out of curiosity though, is this your 580 driving monitor(s)?
February 03, 2019, 01:42:24 PM
Would you guys be able to dev mimblewimble miner? Seriously lacking a good AMD one to compete 
February 03, 2019, 01:24:34 PM
Also, the kernels are designed to handle a downclock of mem all the way down to 300 MHz on Polaris cards and 500 MHz on Vegas, this without hashrate being affected. It probably won't save more than 1-2W per gpu, but always something.
Speed with memory on 300MHz is slower than on full speed... About 1 MH on my RX 580 8Gb February 03, 2019, 12:42:02 PM
But on my 580 cards memory not 300MHz but on full speed. How I can make downclock of memory?
Use OverdriveNTool February 03, 2019, 12:25:09 PM
AMD RX580 Pulse 4GB - 54,7MHs on lyra2v3
Nvidia GTX 1070 8GB - 45,8MHs https://nlpool.nl/bench?algo=lyra2v3&chip=6
Nvidia GTX 1070 8GB - 45,8MHs https://nlpool.nl/bench?algo=lyra2v3&chip=6
February 03, 2019, 11:43:27 AM
After 2h5m no rejected impressive!
impressive!Thank you! After filtering for a few random rejected shares due to new jobs there shouldn't really be any rejects though, so we're just where things should be
. Also, the kernels are designed to handle a downclock of mem all the way down to 300 MHz on Polaris cards and 500 MHz on Vegas, this without hashrate being affected. It probably won't save more than 1-2W per gpu, but always something.
February 03, 2019, 10:15:46 AM
I use Sapphire TRIXX
but in HWiNFO64 i see GPU Core Voltage 1.000V
but in HWiNFO64 i see GPU Core Voltage 1.000V
February 03, 2019, 10:14:47 AM
After 2h5m no rejected impressive!
impressive!Thank you! After filtering for a few random rejected shares due to new jobs there shouldn't really be any rejects though, so we're just where things should be
. Also, the kernels are designed to handle a downclock of mem all the way down to 300 MHz on Polaris cards and 500 MHz on Vegas, this without hashrate being affected. It probably won't save more than 1-2W per gpu, but always something.
February 03, 2019, 10:03:57 AM
undervolt -120
how is this done.
This is how the undervolt is made.
February 03, 2019, 09:46:31 AM
138w HWiNFO64
Jump to: