CharlieCox
Member

Offline
Activity: 212
Merit: 12
|
 |
October 19, 2018, 12:37:10 PM |
|
1. v8 is not v7. It's a new algo version, it hashes a bit slower and draws more power. It's the same for everyone. Deal with it.
Exactly. This hash rate drop doesn't affect anybody's earnings in a negative way. You get your rewards proportionally, which means you will still earn as many XMR as before the fork. Keep it real guys. The only issue could be increased power consumption and heat. I always preferred to mine XMR over ETH, since ETH uses more power and generates more heat. Thankfully, winter is coming in Europe so extra heat won't be an issue for a while.
|
|
|
|
abg00
Jr. Member
Offline
Activity: 288
Merit: 1
|
 |
October 19, 2018, 12:48:40 PM |
|
So, is anybody else having problems with nicehash compatibility on this new version with v8 algo? I am getting all "shares above target" if I run v8 with it. Otherwise the hashrate is pretty much unchanged.
Could someone with nicehash config paste their pool lines since it seems I am too dumb to have it set correctly or the miner is broken...? Mine is:
{ "pools" : [ {"pool" : "cryptonightv8.eu.nicehash.com:3367", "wallet" : "N/A", "password" : "x", "nicehash" : true}, {"pool" : "cryptonightv8.usa.nicehash.com:3367", "wallet" : "N/A", "password" : "x", "nicehash" : true} ] }
{"pool" : "cryptonightv8.usa.nicehash.com:3367", "wallet" : "N/A", "password" : "x", "nicehash" : true},
|
|
|
|
Pabu7
Newbie
Offline
Activity: 1
Merit: 0
|
 |
October 19, 2018, 12:56:40 PM |
|
Is the hashrate showed on the miner real? I'm mining on supportxmr for 12hours now and my avg is in 4.72kh/s, the miner shows 5.42kh/s. Before the fork I was using version 1.4.3, and my avg on the pool was 5.56kh/s, more or less the same that the miner showed. I was using it with greedisgood, but even accounting for the miner fee 4.72 is too low compared to 5.42, it's almost 13% and not 0.85% of the total. On xmr-stak I get about 4.9kh/s, minus the fee I will still get 4.85kh/s. That's why I ask if the hashrate shown is real.
|
|
|
|
ntshb
Newbie
Offline
Activity: 95
Merit: 0
|
 |
October 19, 2018, 01:44:04 PM |
|
this is all i need to set in the config v8 file right?
{ "cryptonight_type" : "normalv8", "intensity" : 0, "double_threads" : true "min_rig_speed" : 7000 }
do i need to include "reboot_script_min_rig_speed" : (??)
|
|
|
|
kristikun
Newbie
Offline
Activity: 62
Merit: 0
|
 |
October 19, 2018, 01:44:49 PM |
|
im getting really sweet hashrates thx for hard work , wanted to ask about todays monero V9 Fork is miner suporting it ?
|
|
|
|
seefatlow
Jr. Member
Offline
Activity: 80
Merit: 1
|
 |
October 19, 2018, 02:15:38 PM |
|
Just to share my v8 Vega hashrates
Rx Vega 64(Samsung) 1941 H/s T: 61C CC 1448 MhZ MC 1050MHz Rx Vega 56(Samsung) 1892 H/s T: 59C CC 1448 MHz MC 910 MHz RX Vega 56 (Hynix) 1811 H/s T:62C CC 1448 MHz MC 910 MHz
Intensity 120/12/2
9 Vega Rig - 1950 W out of the wall power draw
|
|
|
|
CharlieCox
Member

Offline
Activity: 212
Merit: 12
|
 |
October 19, 2018, 02:19:03 PM |
|
9 Vega Rig - 1950 W out of the wall power draw
Did you undervolt?
|
|
|
|
seefatlow
Jr. Member
Offline
Activity: 80
Merit: 1
|
 |
October 19, 2018, 02:29:06 PM |
|
9 Vega Rig - 1950 W out of the wall power draw
Did you undervolt? Most definitely
|
|
|
|
ntshb
Newbie
Offline
Activity: 95
Merit: 0
|
 |
October 19, 2018, 02:51:42 PM |
|
1107w for 4 vega 64 is quite high isn't it?
|
|
|
|
nightfury626
Newbie
Offline
Activity: 75
Merit: 0
|
 |
October 19, 2018, 03:15:12 PM |
|
can anyone help me, after switching from monero7 to monero8, my hashrates went from 2156 to 1275. what extra stuff is needed with this fork to get my hashrates back please?
|
|
|
|
Bojcha
|
 |
October 19, 2018, 03:21:26 PM |
|
Vega owners, check your hotspot temps. My Vega didnt survive the night mining v8 even when I dropped the core to 1250@865mV And a big fat F U to Monero devs
Completely your fault. Many times was repeated - do not look GPU temp. Every Vega need to be set at 50c gpu temp (which is minimum by driver) and then HotSpot and HBM2 temps will be ok.
|
|
|
|
goran89
Newbie
Offline
Activity: 13
Merit: 0
|
 |
October 19, 2018, 03:24:37 PM |
|
Strange thing with v8 is that my 570's hashrate is same (950 H/s) but my 580's droped from 1025 to 975 H/s. I use same settings just changed worksize from 8 to 16 and my power consumption went up for about 80-85 W for 5 cards. On friends rig I also have problem with "Initialising open CL driver/cards...." It just stuck on that after I start miner. We have same windows version (1709), same driver (18.6.1) and same miner but on his rig it won't start. Any solution (don't want to reinstall whole windows again  ) ?
|
|
|
|
Bojcha
|
 |
October 19, 2018, 03:25:27 PM |
|
Just to share my v8 Vega hashrates 9 Vega Rig - 1950 W out of the wall power draw
Too much power draw. That is about 210W per card (?) it should be around 180w for 1950-1980H/s
|
|
|
|
dragonmike
|
 |
October 19, 2018, 03:34:02 PM |
|
Just to share my v8 Vega hashrates 9 Vega Rig - 1950 W out of the wall power draw
Too much power draw. That is about 210W per card (?) it should be around 180w for 1950-1980H/s I doubt you can actually reach that at the wall with v8. Unless you have ice cold airflow and your GPU fans are hardly spinning... or you have won the silicon lottery.
|
|
|
|
nordmann666
Member

Offline
Activity: 364
Merit: 16
|
 |
October 19, 2018, 03:54:24 PM |
|
Strange thing with v8 is that my 570's hashrate is same (950 H/s) but my 580's droped from 1025 to 975 H/s. I use same settings just changed worksize from 8 to 16 and my power consumption went up for about 80-85 W for 5 cards. On friends rig I also have problem with "Initialising open CL driver/cards...." It just stuck on that after I start miner. We have same windows version (1709), same driver (18.6.1) and same miner but on his rig it won't start. Any solution (don't want to reinstall whole windows again  ) ? which cards exactly with RAM and whats your sxettings to get 950 with 570´s
|
|
|
|
O-Coin
Jr. Member
Offline
Activity: 61
Merit: 2
|
 |
October 19, 2018, 04:10:04 PM |
|
Vega owners, check your hotspot temps. My Vega didnt survive the night mining v8 even when I dropped the core to 1250@865mV And a big fat F U to Monero devs
Over the night SRBMiner reset every cca 2 hours, ONE Vega 56 (gpu 0) drop hash to 0 and reset. And that is after I changed power and intensity. Try more mV on core and memory to see the result. Now testing OverdriveNtool: Problematic card Vega 56 reference: [Profile_0] Name=Sapphire GPU_P0=852;900 GPU_P1=991;900;0 GPU_P2=1084;900;0 GPU_P3=1138;900;0 GPU_P4=1150;900;0 GPU_P5=1202;900;0 GPU_P6=1212;905;0 GPU_P7=1407;950 Mem_P0=167;900;0 Mem_P1=500;900;0 Mem_P2=800;900;0 Mem_P3=1050;950 Fan_Min=3350 Fan_Max=4900 Fan_Target=75 Fan_Acoustic=2400 Power_Temp=85 Power_Target=0 Other Vega 56 reference: [Profile_3] Name=Gigabyte GPU_P0=852;900 GPU_P1=991;900;0 GPU_P2=1084;900;0 GPU_P3=1138;900;0 GPU_P4=1150;900;0 GPU_P5=1202;900;0 GPU_P6=1212;905;0 GPU_P7=1407;950 Mem_P0=167;900;0 Mem_P1=500;900;0 Mem_P2=800;900;0 Mem_P3=1095;950 Fan_Min=3350 Fan_Max=4900 Fan_Target=75 Fan_Acoustic=2400 Power_Temp=85 Power_Target=0 I cant get my P3 near that high any higher and I get compute errors. I have Hynix Mem in all my Vega56s and average about 1840-1860. No shut down or restarts. [Profile_5] Name=FAST GPU_P0=852;900;0 GPU_P1=991;900;0 GPU_P2=1084;900;0 GPU_P3=1138;900;0 GPU_P4=1150;900;0 GPU_P5=1202;900;0 GPU_P6=1212;905;0 GPU_P7=1407;925 Mem_P0=167;800;0 Mem_P1=500;800;0 Mem_P2=700;900;0 Mem_P3=955;930 Fan_Min=2800 Fan_Max=4900 Fan_Target=50 Fan_Acoustic=2400 Power_Temp=80 Power_Target=0 Did you flash to 64 bios?
|
|
|
|
goran89
Newbie
Offline
Activity: 13
Merit: 0
|
 |
October 19, 2018, 04:24:52 PM |
|
Strange thing with v8 is that my 570's hashrate is same (950 H/s) but my 580's droped from 1025 to 975 H/s. I use same settings just changed worksize from 8 to 16 and my power consumption went up for about 80-85 W for 5 cards. On friends rig I also have problem with "Initialising open CL driver/cards...." It just stuck on that after I start miner. We have same windows version (1709), same driver (18.6.1) and same miner but on his rig it won't start. Any solution (don't want to reinstall whole windows again  ) ? which cards exactly with RAM and whats your sxettings to get 950 with 570´s XFX RX 570 RS 4GB XXX Edition with elpida memory 1220/900 core and 2035/910 memory miner settings I:58,W:16,T:2
|
|
|
|
tvukoman
Jr. Member
Offline
Activity: 69
Merit: 5
|
 |
October 19, 2018, 04:45:59 PM |
|
Did you flash to 64 bios?
yes, of course.
|
|
|
|
ntshb
Newbie
Offline
Activity: 95
Merit: 0
|
 |
October 19, 2018, 04:57:42 PM |
|
ok this is what I got and it's strange. for 1 of them I had very little hash drop the rest had significant drops
miner 1 5x vega56 flashed to 64(reference) before v8 it was 9855+h/s v8 8955h/s 1260w at the wall
miner 2 4x vega 64 (reference) before v8 it was 7900h/s v8 7755h/s 1250mhz/1100mhz 935w
miner 3 6x vega 56 (non ref, 1 PC vega 56 and 5 gigabyte vega 56) before v8 10300-11000h/s v8 10300+h/s 1400w
So for every vega, I need 2 IDs?
{ "id" : 0, "intensity" : 124, "worksize" : 16, "threads" : 2} { "id" : 1, "intensity" : 124, "worksize" : 16, "threads" : 2} { "id" : 2, "intensity" : 124, "worksize" : 16, "threads" : 2} { "id" : 3, "intensity" : 124, "worksize" : 16, "threads" : 2} { "id" : 4, "intensity" : 124, "worksize" : 16, "threads" : 2} { "id" : 5, "intensity" : 124, "worksize" : 16, "threads" : 2} { "id" : 6, "intensity" : 124, "worksize" : 16, "threads" : 2} { "id" : 7, "intensity" : 124, "worksize" : 16, "threads" : 2}
|
|
|
|
Bare
Member

Offline
Activity: 130
Merit: 11
|
 |
October 19, 2018, 05:01:05 PM |
|
Hi everybody, can anyone please help me with an issue I'm dealing with? In forward, I apologise if this problem has been asked and resolved before already. I'm having a problem running SRBminer across my win 10 rigs, I'm getting this error in windows application has been blocked from accessing graphics hardware Bear in mind my win 10 rigs are perfectly operational on other miners such as claymore's but windows is blocking SRBminer's access to graphics hardware for some reason and I don't know how to bypass this shit. the result of error I get in the miner is in this image How did you guys bypass this windows issue? It seems like it's a fairly simple registry fix or something Thank you!
|
|
|
|
|