l1xx
Member

Offline
Activity: 115
Merit: 10
|
 |
October 30, 2017, 05:08:20 PM |
|
I have one of the Vega cards showing a green led when initialized. It cannot be used for mining. Anyone knows what this green led is ? (it's on the right of the blue/red stripe of leds).
The card works normally when used alone. It's making this thing when used with others.
I've seen this only when its powered, but not connected to the board.
|
|
|
|
bytiges
|
 |
October 30, 2017, 05:10:36 PM |
|
I have one of the Vega cards showing a green led when initialized. It cannot be used for mining. Anyone knows what this green led is ? (it's on the right of the blue/red stripe of leds).
The card works normally when used alone. It's making this thing when used with others.
What do you mean cannot be used for mining? What's happening when you try multi card mining? I mean the card cannot be used/initialized: it's there but blocks when accessed. I fixed the problem. It was the card in the x16 slot of the mobo. The fix was to use Gen2 protocol and not Gen3. I think the problem is the driver. It would do this "green" led when the card was activated and there were other cards activated too. it started doing it after a hard reset (lockup). Nevermind, we're all waiting for better drivers, until then life is what it is  I would not mind knowing what that green led means. It's normally off but seems to light up on issues.
|
|
|
|
MoneroCrusher
Jr. Member
Offline
Activity: 88
Merit: 1
|
 |
October 30, 2017, 05:11:16 PM |
|
@MoneroCrusher: It seems that both you and me have downloaded the 32bit exe into a 64bit system. Downloaded the correct one and it's working great (removed the necessity to run as admin as well).
thanks for the tip! Finally working I downloaded x86 instead of amd64 (I thought that was for amd cpus, pretty confusing)
|
|
|
|
bytiges
|
 |
October 30, 2017, 05:11:43 PM |
|
I have one of the Vega cards showing a green led when initialized. It cannot be used for mining. Anyone knows what this green led is ? (it's on the right of the blue/red stripe of leds).
The card works normally when used alone. It's making this thing when used with others.
I've seen this only when its powered, but not connected to the board. Thanks. Might be when it cannot communicate. Makes sense also in my case.
|
|
|
|
bytiges
|
 |
October 30, 2017, 05:13:04 PM |
|
Hi guys, Someone try new drivers 17.10.3? I am also curious if someone prepare new power tables.
Don't touch them. They work at 1100h per card. Also cannot be undervolted. And I had to reinstall windows after because neither DDU nor AMD uninstaller could get rid of them and the blockchain drivers could not be installed after (lost a few hours sleep because of them).
|
|
|
|
MoneroCrusher
Jr. Member
Offline
Activity: 88
Merit: 1
|
 |
October 30, 2017, 05:15:14 PM |
|
I have one of the Vega cards showing a green led when initialized. It cannot be used for mining. Anyone knows what this green led is ? (it's on the right of the blue/red stripe of leds).
The card works normally when used alone. It's making this thing when used with others.
I've seen this only when its powered, but not connected to the board. Thanks. Might be when it cannot communicate. Makes sense also in my case. I thought one card is green if you have crossfire enabled
|
|
|
|
Permonik
Member

Offline
Activity: 275
Merit: 11
|
 |
October 30, 2017, 05:37:21 PM |
|
Hi guys, Someone try new drivers 17.10.3? I am also curious if someone prepare new power tables.
Don't touch them. They work at 1100h per card. Also cannot be undervolted. And I had to reinstall windows after because neither DDU nor AMD uninstaller could get rid of them and the blockchain drivers could not be installed after (lost a few hours sleep because of them). Hi, thx for advice, what you mean that they works at 1100h per card? And the drivers 17.10.2? I need them for 10x vegas on single board. Thx
|
|
|
|
twan69666
Newbie
Offline
Activity: 59
Merit: 0
|
 |
October 30, 2017, 05:40:57 PM |
|
Hi guys, Someone try new drivers 17.10.3? I am also curious if someone prepare new power tables.
Don't touch them. They work at 1100h per card. Also cannot be undervolted. And I had to reinstall windows after because neither DDU nor AMD uninstaller could get rid of them and the blockchain drivers could not be installed after (lost a few hours sleep because of them). I used them, switched to the blockchain driver, and then switched back to 17.10.3. Undervolting also works fine. I just use Wattman myself and dont get into the PP tables. I think you had an issue somewhere. I did not nor have I seen a lot of issues popping up about these drivers. Although the hash rates are still nowhere near the blockchain driver, I can pull 1200-1300h/s. However, I use my Vega mostly for gaming
|
|
|
|
bytiges
|
 |
October 30, 2017, 09:08:43 PM Last edit: October 30, 2017, 09:34:55 PM by bytiges |
|
Hi guys, Someone try new drivers 17.10.3? I am also curious if someone prepare new power tables.
Don't touch them. They work at 1100h per card. Also cannot be undervolted. And I had to reinstall windows after because neither DDU nor AMD uninstaller could get rid of them and the blockchain drivers could not be installed after (lost a few hours sleep because of them). I used them, switched to the blockchain driver, and then switched back to 17.10.3. Undervolting also works fine. I just use Wattman myself and dont get into the PP tables. I think you had an issue somewhere. I did not nor have I seen a lot of issues popping up about these drivers. Although the hash rates are still nowhere near the blockchain driver, I can pull 1200-1300h/s. However, I use my Vega mostly for gaming Well, I might have had issues. Wattman does not cut it for me. I use power tables and extreme undervolting, but doing 1940h/s average on 130 W per vega56 card (flashed to 64) with stak-amd. Loosing 600h/s per card is too much for me. I have a 4 vega 56 rig used for "development". On this rig I've been switching between 17.10.2, 17.10.3 and blockchain aug23 quite a bit in the last few days (17.10.3 is only 3 days old!). Last thing I know is after I installed 17.10.3 for the first time I could not get back to blockchain. It would not uninstall neither with ddu nor with amd uninstaller. Windows would pick the damn drivers every time. Block chain driver would take ages to install and fail at the end. So, combined I wouldn't use them yet for the above reasons. If somebody can come and help making them work I'd be willing to follow.
|
|
|
|
bostonvex
Member

Offline
Activity: 71
Merit: 10
|
 |
October 30, 2017, 10:48:06 PM |
|
I have one of the Vega cards showing a green led when initialized. It cannot be used for mining. Anyone knows what this green led is ? (it's on the right of the blue/red stripe of leds).
The card works normally when used alone. It's making this thing when used with others.
What do you mean cannot be used for mining? What's happening when you try multi card mining? I mean the card cannot be used/initialized: it's there but blocks when accessed. I fixed the problem. It was the card in the x16 slot of the mobo. The fix was to use Gen2 protocol and not Gen3. I think the problem is the driver. It would do this "green" led when the card was activated and there were other cards activated too. it started doing it after a hard reset (lockup). Nevermind, we're all waiting for better drivers, until then life is what it is  I would not mind knowing what that green led means. It's normally off but seems to light up on issues. Yes, turn off Crossfire.
|
|
|
|
bytiges
|
 |
October 31, 2017, 09:24:37 AM |
|
Yes, turn off Crossfire.
Can crossfile be on with no monitor attached ?
|
|
|
|
bytiges
|
 |
October 31, 2017, 10:10:28 AM |
|
So, I'm trying to pinpoint an issue with STAK-AMD.
On my test rig with 4 vega 56, it will lock up hard after 10 to 60 minutes in the mining.
One of the cards will do 0 hash. The miner is locked up. Stopping it hangs windows with a driver error.
Rising the HBM and GPU voltage from 905 to 930 will stabilize the card, but then something else happens: All cards stop mining after some time (again, 10 to 60 minutes).
At that point it's possible to stop the miner, restart the cards and go for a little while until the same happens.
If I take out the "problematic card", laving only 3 of the others, the same happens: all cards stop mining.
Now the catch: I get cast-xmr and it's been mining for hours with no issues. I can also mine at about 7850 h/s on 4 vega, at 700 W from the wall.
Using the blockchain drivers from Aug.23. Registry undervolting. 905-905 gpu/hbm and 1408/1100 freq on gpu/hbm.
Reducing the memory speeds does nothing. Stak will hang again.
Now, anyone has stak-amd running well on similar hashrates or are you all using some other miner ?
|
|
|
|
rednoW
Legendary
Offline
Activity: 1510
Merit: 1003
|
 |
October 31, 2017, 10:13:50 AM |
|
So, I'm trying to pinpoint an issue with STAK-AMD.
On my test rig with 4 vega 56, it will lock up hard after 10 to 60 minutes in the mining.
One of the cards will do 0 hash. The miner is locked up. Stopping it hangs windows with a driver error.
Rising the HBM and GPU voltage from 905 to 930 will stabilize the card, but then something else happens: All cards stop mining after some time (again, 10 to 60 minutes).
At that point it's possible to stop the miner, restart the cards and go for a little while until the same happens.
If I take out the "problematic card", laving only 3 of the others, the same happens: all cards stop mining.
Now the catch: I get cast-xmr and it's been mining for hours with no issues. I can also mine at about 7850 h/s on 4 vega, at 700 W from the wall.
Using the blockchain drivers from Aug.23. Registry undervolting. 905-905 gpu/hbm and 1408/1100 freq on gpu/hbm.
Reducing the memory speeds does nothing. Stak will hang again.
Now, anyone has stak-amd running well on similar hashrates or are you all using some other miner ?
What config did you use with xmr-stak-amd? Vega56 doesn't like high intensities with xmr-stak. cast-xmr is way better for vega56 if you are not concerned with closed-source risk ))
|
|
|
|
bytiges
|
 |
October 31, 2017, 10:45:59 AM |
|
What config did you use with xmr-stak-amd? Vega56 doesn't like high intensities with xmr-stak. cast-xmr is way better for vega56 if you are not concerned with closed-source risk ))
I'm running 2016/1600 and 2016/1736. Both have the same issue. I've been following the reddit definitive guide and it mentions no problems with those intensities. At some point I remember lowering them to 1920 / 1524 but was not stable either. Can you suggest some intensities to try ? PS: yes, I don't like running closed source. I even compiled stak-amd myself, but it makes no difference vs. the stability issue above.
|
|
|
|
Permonik
Member

Offline
Activity: 275
Merit: 11
|
 |
October 31, 2017, 11:18:08 AM |
|
Hi, Someone told me that hanging of stak-xmr can be caused by gpu inside the 16x pci-e slot on asrock 110 btc, so I will try to connect the card to another slot. I am experiencing the system freezing too, the longest run was 20h. And today, I will try new driver with 10x vegas64.
|
|
|
|
|
Yerba
Member

Offline
Activity: 146
Merit: 10
|
 |
October 31, 2017, 11:37:17 AM |
|
What config did you use with xmr-stak-amd? Vega56 doesn't like high intensities with xmr-stak. cast-xmr is way better for vega56 if you are not concerned with closed-source risk ))
I'm running 2016/1600 and 2016/1736. Both have the same issue. I've been following the reddit definitive guide and it mentions no problems with those intensities. At some point I remember lowering them to 1920 / 1524 but was not stable either. Can you suggest some intensities to try ? PS: yes, I don't like running closed source. I even compiled stak-amd myself, but it makes no difference vs. the stability issue above. I am running 5rigs with 4xgigabyte vega56 cards. GPU 920mv, memory 910mv @ 1100 Mhz. 7700 hash ( 2016/1736 ). All rigs are 20+ days stable aka nonstop.
|
|
|
|
Permonik
Member

Offline
Activity: 275
Merit: 11
|
 |
October 31, 2017, 11:40:27 AM |
|
I think that this driver is primary focused to workstations with fire pro and so on... This is not what we are looking for.
|
|
|
|
tarui
|
 |
October 31, 2017, 12:20:36 PM |
|
Ledipaa, Your calculator is wrong. Two rx on eth in dual with dcr currently gives ~$90/month. While unstable working Vega 56 on monero ~85.
power used for 2 rx on eth with dcr vs power used for 1x 56 mining monero I see claims with 140 watts for 2000 hash on vega's doing monero I know 2x rx 470's 480's 570's or 580's will use more then 140 watts so form factor a good board could do very well with vega 56's I have this board on order. comes on monday seems really good to run 4 vega 56's with endless spacing for cooling but right now I am almost all nvidia mostly because of a few more coin choices  do you have the link for this? the ones I can find on taobao.com are those with embedded cpu
|
|
|
|
jmumich
|
 |
October 31, 2017, 12:31:02 PM |
|
Using the blockchain drivers from Aug.23. Registry undervolting. 905-905 gpu/hbm and 1408/1100 freq on gpu/hbm.
Reducing the memory speeds does nothing. Stak will hang again.
Now, anyone has stak-amd running well on similar hashrates or are you all using some other miner ?
How low are you bringing the memory speeds? 1100 seems high for a 56, and high to run XMR in general. I don't see much improvement over 950, and run mine at 920 getting about 1900h/s (edit - unflashed - I didnt see any benefit flashing to 64, either)
|
|
|
|
|