Awesome! Good to see exchange listing.
|
|
|
It has been a while since I checked this thread... LOL What is going on here!!! Even the so called legit guys these days cannot deliver.
|
|
|
THanks GKumaran!!! SRB 1.7.2 = 8650 h/s per Vega 56
|
|
|
Anyone mining UPX with Vega 56's?
I am using SRB V1.7.3 and Radeon 18.8.2.
I get 8700H/s per card but after a few minutes I start getting compute errors
Config: { "id" : 0, "intensity" : 230, "double_threads" : true, "old_mode" : true },
CC 1475 MC 1100
When I change the config to "old_mode : false" then I get no more compute errors but hashrate is only 6600H/s. Even dropping CC, MC and intensity much lower I still get compute errors when using "old_mode" : true
Any advice?
Old mode + new drivers are a no go. Old mode creates kernels well, the old way, which worked OK with drivers up to 18.6.1 + Added a gpu_conf only parameter 'old_mode'. With the changes i made in 1.7.2, that allow the creation of kernels on drivers newer than 18.6.1, algos that use a scratchpad <=1MB (litev7, mox, dark, upx) suffer from a hashrate drop on Vegas (maybe others too, i didn't test). So if you set this parameter to true, it will create kernel the old way, and the speed on these algos should be back. Don't forget, if you use old_mode : true, and compile the kernel on a driver newer than 18.6.1, you probably won't be finding any shares!
Thank Dok but even with the 18.6.1 I still get compute errors. I dropped the clocks and intensity lower and even upped the voltage without any luck. With "old_mode" : false" I get no compute errors but only have hashrate of 6600H/s Anything else I could try? Have you: 1. cleaned the cache folder in miner folder 2. remove old driver with ddu before installing new driver Dok is legend! No more compute errors after clearing the cache folder
|
|
|
Anyone mining UPX with Vega 56's?
I am using SRB V1.7.3 and Radeon 18.8.2.
I get 8700H/s per card but after a few minutes I start getting compute errors
Config: { "id" : 0, "intensity" : 230, "double_threads" : true, "old_mode" : true },
CC 1475 MC 1100
When I change the config to "old_mode : false" then I get no more compute errors but hashrate is only 6600H/s. Even dropping CC, MC and intensity much lower I still get compute errors when using "old_mode" : true
Any advice?
Old mode + new drivers are a no go. Old mode creates kernels well, the old way, which worked OK with drivers up to 18.6.1 + Added a gpu_conf only parameter 'old_mode'. With the changes i made in 1.7.2, that allow the creation of kernels on drivers newer than 18.6.1, algos that use a scratchpad <=1MB (litev7, mox, dark, upx) suffer from a hashrate drop on Vegas (maybe others too, i didn't test). So if you set this parameter to true, it will create kernel the old way, and the speed on these algos should be back. Don't forget, if you use old_mode : true, and compile the kernel on a driver newer than 18.6.1, you probably won't be finding any shares!
Thank Dok but even with the 18.6.1 I still get compute errors. I dropped the clocks and intensity lower and even upped the voltage without any luck. With "old_mode" : false" I get no compute errors but only have hashrate of 6600H/s Anything else I could try?
|
|
|
Anyone mining UPX with Vega 56's?
I am using SRB V1.7.3 and Radeon 18.8.2.
I get 8700H/s per card but after a few minutes I start getting compute errors
Config: { "id" : 0, "intensity" : 230, "double_threads" : true, "old_mode" : true },
CC 1475 MC 1100
When I change the config to "old_mode : false" then I get no more compute errors but hashrate is only 6600H/s. Even dropping CC, MC and intensity much lower I still get compute errors when using "old_mode" : true
Any advice?
|
|
|
Good to see active devs and a strong project being developed!
|
|
|
BCash is slowly dying.... LOL i mean BTrash!
|
|
|
Thanks Doc! I get 120h/s extra with V1.7.0 on my Vega 56's! They doing around 1690h/s per card on heavy/bittubev2
|
|
|
Thanks for all the info everything has been giving! Latest version of JCE.
4 x Vega 56 Reference with V64 BIOS 1475 / 915 and 1100 /900
Getting 1650h/s per card
Current Config:
{ "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":896 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 128, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":896 },
Driver :24.20.13011.1009
Tried various configs, cannot get more than 1650h/s. Any advice?
And is it normal for JCE not to show temp and fan speed?
Thanks
|
|
|
The release we've been waiting for is here Version 0.4.0f addresses all known issues with easy shielding of coinbases to any z-address, including Sapling, adds logic to handle staking during forks or reorgs more effectively, has a much nicer transaction display that shows stake transactions in a much more aesthetically pleasing way (thanks @michaeltoutjr !), enables setting your own maximum transparent and private transaction limits in Agama App config (careful, it can slow down to the point of being unusable with over a couple thousand). With this version, we hope and believe that we will all enjoy mining, staking, and catching cheaters on the Verus Coin Network more than with any previous release. As mentioned before, this newer Verus Enhanced Agama wallet now also supports lite mode Bitcoin, Zcash (with Sapling), Litecoin, and Dash, as well as Komodo and most Komodo family coins by default as well. We have not yet integrated support for Pirate, which we intend to do in an upcoming version. Thanks to everyone who helped make this release and the Sapling transition smooth for the network and community! Whether you were testing, sometimes through the night, helping people in the community, which let the devs focus more on development when necessary, making connections to exchanges or the media, voting for Verus online, working on writing, design, spreading the word, developing, or testing by using Verus Coin, we appreciate everyone who helped make this release what it is. Other developers and I could not have done it without you! As usual, the latest builds of CLI and GUI are available from the website or our github repositories: https://veruscoin.io/https://github.com/veruscoinGreat update guys!
|
|
|
I am trying out JCE for the first time. Getting 1660h/s per card. What would be the best config for Vega 56's on BittubeV2?
This is my config.
"gpu_threads_conf" : [ { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":464 }, { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":464 }, ],
Thanks
|
|
|
Dok... JCE and Teamredminer are really upping their game with Heavy and CNv8. Vega 56 1750h/s on heavy Vega 64 2200h/s on CNv8
Are you planning any performance increases with SRB soon?
Hmm, come on mk111, you expect to Doktor do miracle (once again), and expect it today? Think what U can do to improve miner, lets start with reading Doktor post on this same page: are you going to reduce power usee like team red miner did, it uses 10 to 15 percent power same hash too unstable for me tho compared to srb
Well that miner gave me homework to do, so i am working on something since then. It will definitely increase the hashrate, but don't know about the power consumption. we will see. Looks like i finally found the 'secret' of hash increase on heavy algos , it can be applied to v8 also. Just wondering how the hell i did not think of this earlier, it was so obvious lol if everything goes well i hope i can push the new version in max a week. Don't know about the speed compared to other miners, we will see. But probably won't reach the JCE advertised 1750hs, but my preliminary tests on Vega56 show an increase of ~ 6-7% Good news!
|
|
|
Dok... JCE and Teamredminer are really upping their game with Heavy and CNv8. Vega 56 1750h/s on heavy Vega 64 2200h/s on CNv8
Are you planning any performance increases with SRB soon?
|
|
|
Pretty cool
|
|
|
my t-rex miner freeze when dev fee pops up and its only happening to one of my rigs. Any ideas?
I had the same issue today
|
|
|
I have noticed the same. Pallas which project are you going to be focusing on?
|
|
|
How much Mh/s does a Vega 56 or 64 do on X22i?
Hi, XFX VEGA 64 LC 8 GB -> 6300 kH/s (default parameter -> 380W) ....reduced to -25% power 1400MHz Core@950mV 1060MHz RAM@950mV = 5950 kH/s (230W) all with zjazz-1.1-amd-win64 Thanks for the reply. So not really a good idea to mine this algo with AMD cards as similar NVIDIA cards perform much better.
|
|
|
Does SRB work with Windows 10 1803?
|
|
|
How much Mh/s does a Vega 56 or 64 do on X22i?
|
|
|
|