|
huntingthesnark
|
 |
October 23, 2018, 06:53:20 PM |
|
Mining Monero seems to be a PITA at the moment.
I cannot make myself bothering to troubleshoot and make this software works properly with the new fork and cannot bother to move to SBR miner or wtf is called.
I was doing a lot of tweaking and testing in my early days of mining, about 10/12 months ago, when the gig was much more profitable than these days.
Also considering the 7% performance hit you take moving to the new fork, IMO mining Monero does not make a lot of sense.
So, hopefully our Dev is gong to make, via an update, the transition to v.8 a little more straight forward than it actually is.
In the mean time, I moved to other coins that are slightly more profitable and liquid enough in exchanges. A couple of them may also have more upside potential than XMR.
I am just curious if other Cast users are doing the same.
Cheers.
There was a difficulty drop initially, but that's almost vanished now, and the new drivers have wrought havoc with my rigs. Deffo one for a rollback and some kind of CN-Heavy action, methinks. |
|
|
|
AlexanderDumas
Newbie
 Offline
Activity: 206
Merit: 0
|
|
October 23, 2018, 07:56:23 PM |
|
Mining Monero seems to be a PITA at the moment.
I cannot make myself bothering to troubleshoot and make this software works properly with the new fork and cannot bother to move to SBR miner or wtf is called.
I was doing a lot of tweaking and testing in my early days of mining, about 10/12 months ago, when the gig was much more profitable than these days.
Also considering the 7% performance hit you take moving to the new fork, IMO mining Monero does not make a lot of sense.
So, hopefully our Dev is gong to make, via an update, the transition to v.8 a little more straight forward than it actually is.
In the mean time, I moved to other coins that are slightly more profitable and liquid enough in exchanges. A couple of them may also have more upside potential than XMR.
I am just curious if other Cast users are doing the same.
Cheers.
There was a difficulty drop initially, but that's almost vanished now, and the new drivers have wrought havoc with my rigs. Deffo one for a rollback and some kind of CN-Heavy action, methinks. I assume, the difficulty drop was also because a lot of miners/workers did not update the software or incurred in technical problems, therefore there was hashrate drop, which also led to the difficulty drop. Now is back to the new normal, which means waste electricity for pennies.  |
|
|
|
|
shap00
Newbie
Offline
Activity: 54
Merit: 0
|
|
October 24, 2018, 01:10:41 PM |
|
hey guys, i forgot about the 18 octomber update and i've mined thin air the past days.
now i've downloaded the new version, i copy paste the bat file in the new one and i get half the speed i had in the past?
how can i fix this? is there a new command with the new update that i should insert in the bat?
this is my bat: cast_xmr-vega --algo=-1 -S pool -u address.user --opencl 1 -G 0,1,2,3,4,5
thanks
|
|
|
|
|
|
Bakhtra
|
|
October 24, 2018, 01:49:56 PM |
|
hey guys, i forgot about the 18 octomber update and i've mined thin air the past days.
now i've downloaded the new version, i copy paste the bat file in the new one and i get half the speed i had in the past?
how can i fix this? is there a new command with the new update that i should insert in the bat?
this is my bat: cast_xmr-vega --algo=-1 -S pool -u address.user --opencl 1 -G 0,1,2,3,4,5
thanks
Update your driver at least to Adrenalin 18.6.1. |
|
|
|
|
ingyenfrag
Newbie
Offline
Activity: 84
Merit: 0
|
|
October 24, 2018, 03:18:58 PM |
|
hey guys, i forgot about the 18 octomber update and i've mined thin air the past days.
now i've downloaded the new version, i copy paste the bat file in the new one and i get half the speed i had in the past?
how can i fix this? is there a new command with the new update that i should insert in the bat?
this is my bat: cast_xmr-vega --algo=-1 -S pool -u address.user --opencl 1 -G 0,1,2,3,4,5
thanks
And set intensity to 7 (--intensity=7) if you have vaga card(s). |
|
|
|
|
|
huntingthesnark
|
|
October 24, 2018, 03:56:28 PM |
|
Hullo folks, is there a powershell script or similar to automate the switch-radeon-gpu commands/overdriveN and run Cast? Many thanks in advance!
|
|
|
|
MOAMiner
Jr. Member
Offline
Activity: 61
Merit: 2
|
|
October 24, 2018, 05:19:57 PM
Last edit: October 26, 2018, 12:30:27 PM by MOAMiner |
|
why is the API not reporting the hashrate in H/s .. looks like it reports in milliHash/second.
Any reason for this or is it a bug?
edit: well, as noone is answering, we enhanced our genericJSON interface with the ability to define a multiplier (testing-branch)
|
MOAMiner - Automatic Algorithm Switching Software with Online Monitoring - watch our testrigs (http://moaminer.com/public/xMozfE0T)
|
|
|
GordoLui
Jr. Member
Offline
Activity: 73
Merit: 2
|
|
October 24, 2018, 05:35:14 PM |
|
Looks like fastjobswitch did the trick now im mining at 100%-99% accepted rate on all my mining rigs. Still I do have a weird issue on two of my machines where one gpu would stop mining after several hours. Settings seem to be the same all across the board. Nothing seems to be wrong with either of the machines either, aside from that one gpu not mining.
|
|
|
|
|
ut3wt
Newbie
Offline
Activity: 14
Merit: 0
|
|
October 24, 2018, 06:55:15 PM
Last edit: October 24, 2018, 07:25:11 PM by ut3wt |
|
Hi, after update driver on my RIG i have problems! i dont no how to solve it... i try install different driver (latest include) but 4 GPU work ok, 2-GPU not hashing??? this moment 18.5.2 https://picua.org/images/2018/10/24/293516a30ef174dc7ad9bc53884039ed.jpgDetected OpenCL Platform: OpenCL 2.1 AMD-APP (2580.6)
GPU0: Radeon RX Vega (gfx900) ... no changes.
GPU1: Radeon RX Vega (gfx900) ... no changes.
GPU2: Radeon RX Vega (gfx900) ... no changes.
GPU3: Radeon RX Vega (gfx900) ... no changes.
GPU0: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF
GPU1: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF
GPU2: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF
GPU3: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF
[Pool: 'pool.supportxmr.com:7777' | Connected: 2018-10-24 21:43:39]
0:17:24 (100%) Online
0:00:00 ( 0%) Offline
[Job: #21 | Difficulty: 276363 | Running: 3.0 sec | Avg Job Time: 52.0 sec]
[Hash Rate Avg: 7426.2 H/s]
1825.7 H/s GPU0
1726.0 H/s GPU1
1729.8 H/s GPU2
1740.7 H/s GPU3
210.3 H/s GPU4
193.7 H/s GPU5
[Shares Found: 48 | Avg Search Time: 20.5 sec]
48 (100%) Accepted
0 ( 0%) Rejected by pool
0 ( 0%) Invalid result computation failed
0 ( 0%) Could not be submitted because of network error
0 ( 0%) Outdated because of job change
after switch-radeon-gpu --hbcc=on autorestart GPU0-GPU3= it is gfx901 and two gfx900  (fantastic) but also two GPU not hashing((( Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2580.6)
GPU0: Radeon RX Vega (gfx901) ... no changes.
GPU1: Radeon RX Vega (gfx901) ... no changes.
GPU2: Radeon RX Vega (gfx901) ... no changes.
GPU3: Radeon RX Vega (gfx901) ... no changes.
GPU4: Radeon RX Vega (gfx900) ... no changes.
GPU5: Radeon RX Vega (gfx900) ... no changes.
GPU0: Radeon RX Vega (gfx901) | HBCC: ON | Large Pages: OFF
GPU1: Radeon RX Vega (gfx901) | HBCC: ON | Large Pages: OFF
GPU2: Radeon RX Vega (gfx901) | HBCC: ON | Large Pages: OFF
GPU3: Radeon RX Vega (gfx901) | HBCC: ON | Large Pages: OFF
GPU4: Radeon RX Vega (gfx900) | HBCC: ON | Large Pages: ON
GPU5: Radeon RX Vega (gfx900) | HBCC: ON | Large Pages: ON
[Pool: 'pool.supportxmr.com:7777' | Connected: 2018-10-24 22:09:44]
0:06:53 (100%) Online
0:00:00 ( 0%) Offline
[Job: #10 | Difficulty: 74880 | Running: 34.0 sec | Avg Job Time: 42.0 sec]
[Hash Rate Avg: 3590.7 H/s]
785.5 H/s GPU0
767.1 H/s GPU1
780.2 H/s GPU2
786.5 H/s GPU3
197.2 H/s GPU4
274.2 H/s GPU5
[Shares Found: 24 | Avg Search Time: 17.2 sec]
22 ( 92%) Accepted
0 ( 0%) Rejected by pool
0 ( 0%) Invalid result computation failed
0 ( 0%) Could not be submitted because of network error
2 ( 8%) Outdated because of job change
|
|
|
|
|
majhaar
Newbie
Offline
Activity: 6
Merit: 0
|
|
October 24, 2018, 09:12:27 PM |
|
Ive switched to SRBMiner too, even after using DDU removing the BC drivers and installing 18.6.1 i'm still struggling to get above 1500 per card that were running at 1900+ on my Vegas.
Getting 1850 now on SRBMiner with all the same settings.
|
|
|
|
|
ut3wt
Newbie
Offline
Activity: 14
Merit: 0
|
|
October 25, 2018, 07:26:02 AM
Last edit: October 25, 2018, 08:00:20 AM by ut3wt |
|
Well my Vegas are running @ ~900Khs lool
And when I run cast xmr (last version) it says Gfx900(?) , can anyone confirm this ? it was supposed to say Gfx901(?)
A Vega lists as gfx901 when HBCC is on gfx900 when HBCC is off Hi dear glph3k! I find part answer in your previous post, but i have problem 6-gpu Vega64 in OLD mode (CN V7) work very good 12kHs stability, after update to cast xmr 1.5.0 and driver (this moment i use 18.5.2) two GPUs in my log example №4,5 not hashing... and i observe after command switch-radeon-gpu -G 0,1,2,3,4,5 --hbcc=on autorestart i have it: GPU0-3 it is ok gfx901 but GPU4,5 gfx900 --??? i confused [09:54:39] Initializing GPU, loading kernel ...
Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2580.6)
Fast job switching mode enabled.
Driver Version OK.
GPU0: Radeon RX Vega (gfx901) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
HBCC Memory Segment is enabled.
It is recommended to turn HBCC off to run with higher stable intensity settings.
GPU1: Radeon RX Vega (gfx901) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
HBCC Memory Segment is enabled.
It is recommended to turn HBCC off to run with higher stable intensity settings.
GPU2: Radeon RX Vega (gfx901) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
HBCC Memory Segment is enabled.
It is recommended to turn HBCC off to run with higher stable intensity settings.
GPU3: Radeon RX Vega (gfx901) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
HBCC Memory Segment is enabled.
It is recommended to turn HBCC off to run with higher stable intensity settings.
GPU4: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
GPU5: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10 i think that GPU 4,5 HBCC Memory Segment not switch, it is bug (soft, driver..e.t.c) or my two GPU (HBCC Memory) defective? half all hashrate [Hash Rate Avg: 4766.1 H/s]
922.9 H/s GPU0
913.3 H/s GPU1
893.3 H/s GPU2
879.3 H/s GPU3
730.9 H/s GPU4
426.4 H/s GPU5
[Shares Found: 233 | Avg Search Time: 14.2 sec]
68 ( 29%) Accepted
19 ( 8%) Rejected by pool
0 ( 0%) Invalid result computation failed
0 ( 0%) Could not be submitted because of network error
146 ( 63%) Outdated because of job change after command switch-radeon-gpu -G 0,1,2,3,4,5 --hbcc=off autorestart i have all gfx900, but GPU4,5 not hashing((( [10:15:10] Initializing GPU, loading kernel ...
Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2580.6)
Fast job switching mode enabled.
Driver Version OK.
GPU0: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
GPU1: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
GPU2: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
GPU3: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
GPU4: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
GPU5: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
[10:15:14] Connecting to pool.supportxmr.com:7777 ... [Pool: 'pool.supportxmr.com:7777' | Connected: 2018-10-25 10:15:14]
0:02:38 (100%) Online
0:00:00 ( 0%) Offline
[Job: #3 | Difficulty: 185704 | Running: 87.0 sec | Avg Job Time: 35.0 sec]
[Hash Rate Avg: 7912.9 H/s]
1853.2 H/s GPU0
1871.1 H/s GPU1
1868.7 H/s GPU2
1873.9 H/s GPU3
227.9 H/s GPU4
218.2 H/s GPU5
[Shares Found: 16 | Avg Search Time: 11.3 sec]
8 ( 50%) Accepted
0 ( 0%) Rejected by pool
0 ( 0%) Invalid result computation failed
0 ( 0%) Could not be submitted because of network error
8 ( 50%) Outdated because of job change GPU0: Radeon RX Vega (gfx900) ... no changes.
GPU1: Radeon RX Vega (gfx900) ... no changes.
GPU2: Radeon RX Vega (gfx900) ... no changes.
GPU3: Radeon RX Vega (gfx900) ... no changes.
GPU4: Radeon RX Vega (gfx900) ... no changes.
GPU5: Radeon RX Vega (gfx900) ... no changes.
GPU0: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF
GPU1: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF
GPU2: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF
GPU3: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF
GPU4: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF
GPU5: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF... Plz help me to solve this issue, thank very much! |
|
|
|
|
|
BogdanCo
|
|
October 25, 2018, 08:00:05 AM |
|
@ut3wt: make sure crossfire and ULPS are disabled.
|
|
|
|
|
|
|
|
huntingthesnark
|
|
October 25, 2018, 09:11:48 AM |
|
Well my Vegas are running @ ~900Khs lool
And when I run cast xmr (last version) it says Gfx900(?) , can anyone confirm this ? it was supposed to say Gfx901(?)
A Vega lists as gfx901 when HBCC is on gfx900 when HBCC is off Hi dear glph3k! I find part answer in your previous post, but i have problem 6-gpu Vega64 in OLD mode (CN V7) work very good 12kHs stability, after update to cast xmr 1.5.0 and driver (this moment i use 18.5.2) two GPUs in my log example №4,5 not hashing... and i observe after command switch-radeon-gpu -G 0,1,2,3,4,5 --hbcc=on autorestart i have it: GPU0-3 it is ok gfx901 but GPU4,5 gfx900 --??? i confused [09:54:39] Initializing GPU, loading kernel ...
Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2580.6)
Fast job switching mode enabled.
Driver Version OK.
GPU0: Radeon RX Vega (gfx901) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
HBCC Memory Segment is enabled.
It is recommended to turn HBCC off to run with higher stable intensity settings.
GPU1: Radeon RX Vega (gfx901) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
HBCC Memory Segment is enabled.
It is recommended to turn HBCC off to run with higher stable intensity settings.
GPU2: Radeon RX Vega (gfx901) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
HBCC Memory Segment is enabled.
It is recommended to turn HBCC off to run with higher stable intensity settings.
GPU3: Radeon RX Vega (gfx901) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
HBCC Memory Segment is enabled.
It is recommended to turn HBCC off to run with higher stable intensity settings.
GPU4: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
GPU5: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10 i think that GPU 4,5 HBCC Memory Segment not switch, it is bug (soft, driver..e.t.c) or my two GPU (HBCC Memory) defective? half all hashrate [Hash Rate Avg: 4766.1 H/s]
922.9 H/s GPU0
913.3 H/s GPU1
893.3 H/s GPU2
879.3 H/s GPU3
730.9 H/s GPU4
426.4 H/s GPU5
[Shares Found: 233 | Avg Search Time: 14.2 sec]
68 ( 29%) Accepted
19 ( 8%) Rejected by pool
0 ( 0%) Invalid result computation failed
0 ( 0%) Could not be submitted because of network error
146 ( 63%) Outdated because of job change after command switch-radeon-gpu -G 0,1,2,3,4,5 --hbcc=off autorestart i have all gfx900, but GPU4,5 not hashing((( [10:15:10] Initializing GPU, loading kernel ...
Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2580.6)
Fast job switching mode enabled.
Driver Version OK.
GPU0: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
GPU1: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
GPU2: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
GPU3: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
GPU4: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
GPU5: Radeon RX Vega (gfx900) | 64 Compute Units | Memory (MB): 8176 | Intensity: 9 / 10
[10:15:14] Connecting to pool.supportxmr.com:7777 ... [Pool: 'pool.supportxmr.com:7777' | Connected: 2018-10-25 10:15:14]
0:02:38 (100%) Online
0:00:00 ( 0%) Offline
[Job: #3 | Difficulty: 185704 | Running: 87.0 sec | Avg Job Time: 35.0 sec]
[Hash Rate Avg: 7912.9 H/s]
1853.2 H/s GPU0
1871.1 H/s GPU1
1868.7 H/s GPU2
1873.9 H/s GPU3
227.9 H/s GPU4
218.2 H/s GPU5
[Shares Found: 16 | Avg Search Time: 11.3 sec]
8 ( 50%) Accepted
0 ( 0%) Rejected by pool
0 ( 0%) Invalid result computation failed
0 ( 0%) Could not be submitted because of network error
8 ( 50%) Outdated because of job change GPU0: Radeon RX Vega (gfx900) ... no changes.
GPU1: Radeon RX Vega (gfx900) ... no changes.
GPU2: Radeon RX Vega (gfx900) ... no changes.
GPU3: Radeon RX Vega (gfx900) ... no changes.
GPU4: Radeon RX Vega (gfx900) ... no changes.
GPU5: Radeon RX Vega (gfx900) ... no changes.
GPU0: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF
GPU1: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF
GPU2: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF
GPU3: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF
GPU4: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF
GPU5: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF... Plz help me to solve this issue, thank very much! Me too. I gave up in the end, rolled back to blockchain drivers, mining other CN variants. Worth pointing out that on blockchain drivers the problem vanishes. Tried SRB miner too, same issue. I assume it's a driver bug (thanks AMD). |
|
|
|
Bazzaar
Jr. Member
Offline
Activity: 75
Merit: 1
|
|
October 25, 2018, 12:14:50 PM |
|
Just lower the intensity
|
|
|
|
|
|
BogdanCo
|
|
October 25, 2018, 07:54:30 PM |
|
@ut3wt: make sure crossfire and ULPS are disabled.
yes all GPUs are disabled ULPS and crossfire  Maybe DDU and install 18.7.1 drivers? I see you have 000 and 001 there but no GPU are installed on these reg values. You can try to delete them before doing DDU and see if it's working. I had 20x Vega64 on Blockchain drivers, for Monero V8 I did DDU Blockchan drivers, installed 18.7.1 drivers, applied Soft Power tables, Disabled Crossfire and ULPS and all 20 of them are hashing at ~1900 h/s now on MoneroV8. |
|
|
|
|
ut3wt
Newbie
Offline
Activity: 14
Merit: 0
|
|
October 25, 2018, 09:34:50 PM
Last edit: October 25, 2018, 09:59:50 PM by ut3wt |
|
Maybe DDU and install 18.7.1 drivers? I see you have 000 and 001 there but no GPU are installed on these reg values. You can try to delete them before doing DDU and see if it's working. I had 20x Vega64 on Blockchain drivers, for Monero V8 I did DDU Blockchan drivers, installed 18.7.1 drivers, applied Soft Power tables, Disabled Crossfire and ULPS and all 20 of them are hashing at ~1900 h/s now on MoneroV8.
Thanks for the answer, after install 18.7.1 driver hashrate better but two gpu not hashing(( P.S. 001 it is Intel integrate GPU 000 I d'no, I delete it from registry, but not result... I think problem maybe in driver AMD two GPUs not switch memory HBCC after command on\off...? how to solve it? [Pool: 'pool.supportxmr.com:7777' | Connected: 2018-10-26 00:27:31]
0:01:37 (100%) Online
0:00:00 ( 0%) Offline
[Job: #4 | Difficulty: 266107 | Running: 35.0 sec | Avg Job Time: 20.7 sec]
[Hash Rate Avg: 8437.8 H/s]
1906.9 H/s GPU0
1903.9 H/s GPU1
1904.4 H/s GPU2
1905.9 H/s GPU3
454.3 H/s GPU4
362.4 H/s GPU5
[Shares Found: 12 | Avg Search Time: 6.8 sec]
12 (100%) Accepted
0 ( 0%) Rejected by pool
0 ( 0%) Invalid result computation failed
0 ( 0%) Could not be submitted because of network error
0 ( 0%) Outdated because of job change c:\xxx\cast_xmr150v8>switch-radeon-gpu -G 0,1,2,3,4,5 --hbcc=on autorestart
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Switch Radeon GPU 0.9.5
Restart GPUs and switch 'Compute Mode', 'Large Pages' and 'HBCC memory'
on or off for example:
'switch-radeon-gpu -G 0 --compute=on restart'
Run with --help to list available optionss
Coded by [glph3k] for more info visit http://www.gandalph3000.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2639.5)
GPU0: Radeon RX Vega (gfx900) ... switch HBCC Memory ON ... restart GPU
GPU1: Radeon RX Vega (gfx900) ... switch HBCC Memory ON ... restart GPU
GPU2: Radeon RX Vega (gfx900) ... switch HBCC Memory ON ... restart GPU
GPU3: Radeon RX Vega (gfx900) ... switch HBCC Memory ON ... restart GPU
GPU4: Radeon RX Vega (gfx900) ... switch HBCC Memory ON ... restart GPU
GPU5: Radeon RX Vega (gfx900) ... switch HBCC Memory ON ... restart GPU
Device Change privileges are required to apply the settings!
The Windows User Account Control dialog will appear.
When clicking 'YES' in the upcoming dialog the app will be granted the
Windows privileges to execute the above listed actions.
Proceed? (Y/N)
Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2639.5)
GPU0: Radeon RX Vega (gfx901) ... no changes.
GPU1: Radeon RX Vega (gfx901) ... no changes.
GPU2: Radeon RX Vega (gfx901) ... no changes.
GPU3: Radeon RX Vega (gfx901) ... no changes.
GPU4: Radeon RX Vega (gfx900) ... no changes.
GPU5: Radeon RX Vega (gfx900) ... no changes.
GPU0: Radeon RX Vega (gfx901) | HBCC: ON | Large Pages: OFF
GPU1: Radeon RX Vega (gfx901) | HBCC: ON | Large Pages: OFF
GPU2: Radeon RX Vega (gfx901) | HBCC: ON | Large Pages: OFF
GPU3: Radeon RX Vega (gfx901) | HBCC: ON | Large Pages: OFF
GPU4: Radeon RX Vega (gfx900) | HBCC: ON | Large Pages: OFF
GPU5: Radeon RX Vega (gfx900) | HBCC: ON | Large Pages: OFF switch off c:\xxx\cast_xmr150v8>switch-radeon-gpu -G 0,1,2,3,4,5 --hbcc=off autorestart
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Switch Radeon GPU 0.9.5
Restart GPUs and switch 'Compute Mode', 'Large Pages' and 'HBCC memory'
on or off for example:
'switch-radeon-gpu -G 0 --compute=on restart'
Run with --help to list available optionss
Coded by [glph3k] for more info visit http://www.gandalph3000.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2639.5)
GPU0: Radeon RX Vega (gfx901) ... switch HBCC Memory OFF ... restart GPU
GPU1: Radeon RX Vega (gfx901) ... switch HBCC Memory OFF ... restart GPU
GPU2: Radeon RX Vega (gfx901) ... switch HBCC Memory OFF ... restart GPU
GPU3: Radeon RX Vega (gfx901) ... switch HBCC Memory OFF ... restart GPU
GPU4: Radeon RX Vega (gfx900) ... switch HBCC Memory OFF ... restart GPU
GPU5: Radeon RX Vega (gfx900) ... switch HBCC Memory OFF ... restart GPU
Device Change privileges are required to apply the settings!
The Windows User Account Control dialog will appear.
When clicking 'YES' in the upcoming dialog the app will be granted the
Windows privileges to execute the above listed actions.
Proceed? (Y/N)
Detected OpenCL Platform: OpenCL 2.1 AMD-APP (2639.5)
GPU0: Radeon RX Vega (gfx900) ... no changes.
GPU1: Radeon RX Vega (gfx900) ... no changes.
GPU2: Radeon RX Vega (gfx900) ... no changes.
GPU3: Radeon RX Vega (gfx900) ... no changes.
GPU4: Radeon RX Vega (gfx900) ... no changes.
GPU5: Radeon RX Vega (gfx900) ... no changes.
GPU0: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF
GPU1: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF
GPU2: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF
GPU3: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF
GPU4: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF
GPU5: Radeon RX Vega (gfx900) | HBCC: OFF | Large Pages: OFF |
|
|
|
|
ingyenfrag
Newbie
Offline
Activity: 84
Merit: 0
|
|
October 25, 2018, 10:39:06 PM
Last edit: October 25, 2018, 11:21:09 PM by ingyenfrag |
|
I've managed to lower the consumption with a new PPT mod what I made. GPU-s clocks set to 1408MHz running on ~1350-1360 @0.8375V. 2 of my 11 GPU-s are not stable on 0.8375V. Those need 0.85V to run. In a 6 card rig (ref vega56@64) before this mod all of my GPU were at 0.875V (0.8688V sometimes). The consumption was about 1250W with 2*750W EVGA GQ 80+ Gold (6 additional 12cm fan). Same rig with 4 GPUs running on 0.8375V and 2 at 0.85V the consumption is about 1160W. Regfiles --> https://drive.google.com/open?id=1OvKJbv7psAO59I8EavFH5704wf7sr_9zSet HBM P3 voltage to 860mV to 0.8375V GPU. Set HBM P3 voltage to 880mV to 0.85V GPU. You can go even lower. I'm still testing 0.825V (GPU P7 to 830mv, HBM P3 to 850mV) For a short run it seems that 7 out of 11 GPU run even on 0.825mV. Crazy.  |
|
|
|
|
|
BogdanCo
|
|
October 26, 2018, 06:51:22 AM |
|
Maybe DDU and install 18.7.1 drivers? I see you have 000 and 001 there but no GPU are installed on these reg values. You can try to delete them before doing DDU and see if it's working. I had 20x Vega64 on Blockchain drivers, for Monero V8 I did DDU Blockchan drivers, installed 18.7.1 drivers, applied Soft Power tables, Disabled Crossfire and ULPS and all 20 of them are hashing at ~1900 h/s now on MoneroV8.
Thanks for the answer, after install 18.7.1 driver hashrate better but two gpu not hashing(( P.S. 001 it is Intel integrate GPU 000 I d'no, I delete it from registry, but not result... I think problem maybe in driver AMD two GPUs not switch memory HBCC after command on\off...? how to solve it? I forgot to tell you, install proper driver for the IGPU and boot the system on it. And make sure the last 2 Vega's are not in Crossfire. |
|
|
|
|
Zorg33
Jr. Member
Offline
Activity: 144
Merit: 2
|
|
October 26, 2018, 01:03:53 PM |
|
@ut3wt: make sure crossfire and ULPS are disabled.
yes all GPUs are disabled ULPS and crossfire Maybe DDU and install 18.7.1 drivers? I see you have 000 and 001 there but no GPU are installed on these reg values. You can try to delete them before doing DDU and see if it's working. I had 20x Vega64 on Blockchain drivers, for Monero V8 I did DDU Blockchan drivers, installed 18.7.1 drivers, applied Soft Power tables, Disabled Crossfire and ULPS and all 20 of them are hashing at ~1900 h/s now on MoneroV8. @ut3wt I got the solution. I went through the exact same suckage yesterday till I found the trick. The driver does not give a single f*ck what's in the registry! I reinstalled the 18.6.1 driver multiple times and manually set those values in the registry and after reboot I checked in AMD Settings and CF was still ON! I had to manually turn CF off in AMD Setting and the 2 out of 6 cards that were previously hashing at only ~100h/s got back to normal with ~1850h/s. Now all 6 cards are hashing fine with 18.6.1. I had to remove prev driver with amdcleanutility and install 18.6.1 from scratch. I also switched to Compute mode, but that my not matter for Vegas. FYI: BC drivers are shit at V8 indeed. Only ~700h/s |
|
|
|
|
|
