Show Posts
|
Pages: « 1 2 [3] 4 5 »
|
has anyone tried vega frontier on this? do i have to install 18.1.1 then update to blockchain drivers?
|
|
|
if i am using vegas, do I still use 2 lines of intensity for xmr stak like the older versions ?
{ "index" : 0, "intensity" : 1932, "worksize" : 8, "affine_to_cpu" : false }, { "index" : 0, "intensity" : 1932, "worksize" : 8, "affine_to_cpu" : false },
or it's just 1 line now?
cast xmr's newest version says that the 18.3.4 drivers will achieve 99% performance that of the aug 23 drivers, is this the same for xmr stak?
|
|
|
how do i get vega frontier edition to work properly?
I've tried 1703, 1709, using blockchain drivers, 17.2, 17.1 various registry files but for some strange reason,
I keep getting code 43 when i manually disable enable vega FE in dev mgr or it enables and hashes at 1500h/s
clean install of blockchain drivers on windows fall edition, set 2 threads at 2016 disable and re-enable Vega FE in windows device drivers, set overdriven tool settings to normal params (mem to 1100 to 1107) including fans and mine away works for me? Are you using risers?
|
|
|
how do i get vega frontier edition to work properly?
I've tried 1703, 1709, using blockchain drivers, 17.2, 17.1 various registry files but for some strange reason,
I keep getting code 43 when i manually disable enable vega FE in dev mgr or it enables and hashes at 1500h/s
Which miner do you use? My vegas hashing 2khs on xmr-stak 2.2.0 but only 1.5khs on 2.3.0 version. Any advices are appreciated. P.s. did you saw that video? https://youtu.be/wUrt7DgSiDM2.2 , cast xmr and also nicehash It doesn't work for me. I don't get the same results as he did
|
|
|
how do i get vega frontier edition to work properly?
I've tried 1703, 1709, using blockchain drivers, 17.2, 17.1 various registry files but for some strange reason,
I keep getting code 43 when i manually disable enable vega FE in dev mgr or it enables and hashes at 1500h/s
|
|
|
i've been trying to crack this problem with the different hashrate performance on 5 of my reference vega 64s. they are all reference cards except that 1 is a limited edition and 1 of them has a MSI sticker, 1 has a xfx sticker while the rest are sapphire. (as far as I can tell, they are not from the same brand) I even went as far as to save the bios from the card that hashes at 2000h/s and force flashing into the cards that hash at 1600h/s all 5 cards went through the same disable/enable scripts and the only difference i can find is in their P states. out of the 5 cards, only 2 hashes at 2000h/s, the rest hash at 1500 to 1900h/s anyway to force the cards that have 1200mhz at p5 to run at 1400mhz?
|
|
|
i've posted about my problems no less than a dozen times and no one has ever helped.
thanks everyone.
|
|
|
anyone knows why I can't seem to get shares recorded in nanopool (xmr) when I am using xmr stak? Previously I was using xmr stak with supportxmr pool then some issues happened so i switched to cast xmr with nanopool. then I decided to give xmr stak with nanopool another go and it was hashing fine for a few mins until i added failover server addresses (bad idea, it doesn't seem to switch to other servers like claymore) so i undid those changes but nanopool records it as offline but it regularly submits shares as you can see, the wallet address is correct and it is hashing fine.
|
|
|
anyone knows why I can't seem to get shares recorded in nanopool (xmr) when I am using xmr stak? Previously I was using xmr stak with supportxmr pool then some issues happened so i switched to cast xmr with nanopool. then I decided to give xmr stak with nanopool another go and it was hashing fine for a few mins until i added failover server addresses (bad idea, it doesn't seem to switch to other servers like claymore) so i undid those changes but nanopool records it as offline but it regularly submits shares as you can see, the wallet address is correct and it is hashing fine.
|
|
|
Anyone with experience with gigabyte Rx Vega 56 cards?
gaming or reference?
|
|
|
\i seem to be drawing more power with cast xmr than xmr stak
853w for 4 vega 64 (1325/1025mhz 925/900mv) on cast xmr compared to 1000w for 6 cards for xmr stak
|
|
|
I have some issues with the vegas not hashing as expected across 2 -3 miners. Hope someone can help I use this script ( http://vega.miningguides.com/p/auto-run-miner-without-hashmonitor.html) for 2 miner PCs but 1 of them (4x vega64s), only 2 vegas hash at around 1970~, the remaining 2 hash at 1600+h/s . the other PC (5x vega 56 at stock bios) hashes at only 1400-1500h/s. I've reset the vegas in both PCs but it doesnt improve.
|
|
|
I have some issues with the vegas not hashing as expected across 2 -3 miners. Hope someone can help I use this script ( http://vega.miningguides.com/p/auto-run-miner-without-hashmonitor.html) for 2 miner PCs but 1 of them (4x vega64s), only 2 vegas hash at around 1970~, the remaining 2 hash at 1600+h/s . the other PC (5x vega 56 at stock bios) hashes at only 1400-1500h/s. I've reset the vegas in both PCs but it doesnt improve. has anyone tried the JJ's script and hash monitor to automatically reset if the hashrate drops? Not sure if you ever read the entire thread, I have shared my modified version here albeit at an older JJ version & Cast version. Feel free to update it to latest one accordingly. https://bitcointalk.org/index.php?topic=2256917.msg25631033#msg25631033thanks So all I have to do is edit $vidTool += 'OverdriveNTool.exe -r1 -p1Vega64' # Expects to be in same folder as this script and $global:CAST_XMRcmdline = "-S cryptonight.hk.nicehash.com:3355 -u 1C58yRKSf1ctSKBpP9FrSrDTjzYaRPPumD.VegaLuno -G 1 --remoteaccess" # CAST_XMR arguments. Not required, REMARK out if not needed Can i remove the remoteaccess part? You will need the remote access part for the hash monitor to work. I think the following link should be more updated to v2.9. https://drive.google.com/open?id=1TnicWxpB1TtGQCe_cuXND8ha-XsgQsU1I have detailed my change log inside, you will also most likely need to define the minimum vega hashrate for a restart for your case (I use 1 card so it's a simple 1750000, for your simple use case you can multiply it with the number of cards you have, or if you prefer a restart by checking each card individually). If you need it to be tweaked somewhat specifically on a per card basis, I can see about modifying the script to fit your use case. Hit me up on Skype (mo.jin.ee) if you would like to do so. I've edited the settings to $vidTool += 'OverdriveNTool.exe -r1 -r2 -r3 -r4 -p1Vega64 -p2Vega64 -p3Vega64 -p4Vega64' $global:CAST_XMRcmdline = "-S pool.supportxmr.com:7777 -u walletaddress.Vega64-3 -G 0,1,2,3 --remoteaccess" as long as I change these 2 lines that;s fine right? why is the hashdiff so high? i mean vegas are hashing at 2000 per card? You will know why if you ever bother reading through the changelog that I have detailed together with the modified JJ Hash Monitor script, or if you happen to read up more on Cast-XMR monitoring result port comparison on the very guide that Circus Dad has put together comparing xmr-stak vs cast-xmr : http://vega.miningguides.com/p/castxmr-vs-xmrstak.htmlI really don't want to be cynical when it comes to the community helping each other, but when almost every single help that comes the way could actually be solved by oneself bothering to read up more on so many documentation online I really can't help bringing myself to be rather disappointed altogether. thanks for your help
|
|
|
I have some issues with the vegas not hashing as expected across 2 -3 miners. Hope someone can help I use this script ( http://vega.miningguides.com/p/auto-run-miner-without-hashmonitor.html) for 2 miner PCs but 1 of them (4x vega64s), only 2 vegas hash at around 1970~, the remaining 2 hash at 1600+h/s . the other PC (5x vega 56 at stock bios) hashes at only 1400-1500h/s. I've reset the vegas in both PCs but it doesnt improve. has anyone tried the JJ's script and hash monitor to automatically reset if the hashrate drops? Not sure if you ever read the entire thread, I have shared my modified version here albeit at an older JJ version & Cast version. Feel free to update it to latest one accordingly. https://bitcointalk.org/index.php?topic=2256917.msg25631033#msg25631033thanks So all I have to do is edit $vidTool += 'OverdriveNTool.exe -r1 -p1Vega64' # Expects to be in same folder as this script and $global:CAST_XMRcmdline = "-S cryptonight.hk.nicehash.com:3355 -u 1C58yRKSf1ctSKBpP9FrSrDTjzYaRPPumD.VegaLuno -G 1 --remoteaccess" # CAST_XMR arguments. Not required, REMARK out if not needed Can i remove the remoteaccess part? You will need the remote access part for the hash monitor to work. I think the following link should be more updated to v2.9. https://drive.google.com/open?id=1TnicWxpB1TtGQCe_cuXND8ha-XsgQsU1I have detailed my change log inside, you will also most likely need to define the minimum vega hashrate for a restart for your case (I use 1 card so it's a simple 1750000, for your simple use case you can multiply it with the number of cards you have, or if you prefer a restart by checking each card individually). If you need it to be tweaked somewhat specifically on a per card basis, I can see about modifying the script to fit your use case. Hit me up on Skype (mo.jin.ee) if you would like to do so. I've edited the settings to $vidTool += 'OverdriveNTool.exe -r1 -r2 -r3 -r4 -p1Vega64 -p2Vega64 -p3Vega64 -p4Vega64' $global:CAST_XMRcmdline = "-S pool.supportxmr.com:7777 -u walletaddress.Vega64-3 -G 0,1,2,3 --remoteaccess" as long as I change these 2 lines that;s fine right? why is the hashdiff so high? i mean vegas are hashing at 2000 per card?
|
|
|
I have some issues with the vegas not hashing as expected across 2 -3 miners. Hope someone can help I use this script ( http://vega.miningguides.com/p/auto-run-miner-without-hashmonitor.html) for 2 miner PCs but 1 of them (4x vega64s), only 2 vegas hash at around 1970~, the remaining 2 hash at 1600+h/s . the other PC (5x vega 56 at stock bios) hashes at only 1400-1500h/s. I've reset the vegas in both PCs but it doesnt improve. has anyone tried the JJ's script and hash monitor to automatically reset if the hashrate drops? Not sure if you ever read the entire thread, I have shared my modified version here albeit at an older JJ version & Cast version. Feel free to update it to latest one accordingly. https://bitcointalk.org/index.php?topic=2256917.msg25631033#msg25631033thanks So all I have to do is edit $vidTool += 'OverdriveNTool.exe -r1 -p1Vega64' # Expects to be in same folder as this script and $global:CAST_XMRcmdline = "-S cryptonight.hk.nicehash.com:3355 -u 1C58yRKSf1ctSKBpP9FrSrDTjzYaRPPumD.VegaLuno -G 1 --remoteaccess" # CAST_XMR arguments. Not required, REMARK out if not needed Can i remove the remoteaccess part?
|
|
|
when the main page says
Vega 56 Hash Rates
1900 Hash/s with 150 watts power consumption
Core Frequency: -10% Memory Clock: 945 MHz Power Limit: -22%
how much is -10%?
1407-10%? what's the actual clock speed ?
|
|
|
Hi All, I've been working on a simple GUI wrapper around the miner to monitor it in a more user-friendly way and to restart the miner automatically if the hashrate drops below a specified amount. I'm sure there's lots of bugs (very little validation in the GUI), but it might be useful for some of you. https://github.com/anadventureisu/cast-xmr-uiso how do i install it?
|
|
|
I have some issues with the vegas not hashing as expected across 2 -3 miners. Hope someone can help I use this script ( http://vega.miningguides.com/p/auto-run-miner-without-hashmonitor.html) for 2 miner PCs but 1 of them (4x vega64s), only 2 vegas hash at around 1970~, the remaining 2 hash at 1600+h/s . the other PC (5x vega 56 at stock bios) hashes at only 1400-1500h/s. I've reset the vegas in both PCs but it doesnt improve. has anyone tried the JJ's script and hash monitor to automatically reset if the hashrate drops?
|
|
|
Just got my aftermarket vega 56 and it's using hynix memory. can i still flash it to the manufacturer's vega 64 bios from reference cards? (samsung)
or which vega 64 bios can i flash to?
I'm having the same issue. I purchased a vega 56 red devil which has Hynix memory. I can't find any vega 64 bios with Hynix memory at all, they all have Samsung. Might have to stick with samsung only unless they start making Vega 64s with Hynix later on. Any one else figured out a way to flash a Hynix vega 56 to 64? Why you need to flash 56 to 64? I just use stock bios and modregistry for 56 and I can get 1925 h/s with core 1375 905w mem 975 900w. For the sake of simplicity. I have 3 Vega rigs each with four 56s and four 64s. I don't want to do multiple different overdrive settings for the cards. I want them all to run as 64s and have the exact same settings for ease of troubleshooting and what not. Yea I know you can apply the powerplay tables without the V64 bios, but this hynix memory seems to be giving me issues compared to the samsung from the founders cards. it's the same thing for me too. my non-ref vega 56 are giving me troubles.
|
|
|
Just got my aftermarket vega 56 and it's using hynix memory. can i still flash it to the manufacturer's vega 64 bios from reference cards? (samsung)
or which vega 64 bios can i flash to?
I'm having the same issue. I purchased a vega 56 red devil which has Hynix memory. I can't find any vega 64 bios with Hynix memory at all, they all have Samsung. Might have to stick with samsung only unless they start making Vega 64s with Hynix later on. Any one else figured out a way to flash a Hynix vega 56 to 64? Why you need to flash 56 to 64? I just use stock bios and modregistry for 56 and I can get 1925 h/s with core 1375 905w mem 975 900w. core clock 1375 mem clock 975? core 905mv and mem 900mv?
|
|
|
|