Mining with more than 4 Vegas and HBCC -> SOLUTION - page 3.

l1xx

member

Activity: 115

Merit: 10

Quote from: Mattthev on October 25, 2017, 07:17:16 AM

Quote from: HBCCACTIVATE on October 25, 2017, 06:42:07 AM

Hey,

Its working on all of my Vega rigs. I uploaded the source code of the modified xmr-stak.
The part which activates hbcc and calls the miner is not open source.

If the license of xmr-stack does not allow this, I will delete it. Please let me know.

Looks good, dev fee for your address is completly fine, but I think GNU GPL say that you have to give all source codes if you release it to the public.

Did you try the app? Is it really working? After watching the video, it looks like he's not even setting HBCC sliders with Wattmann.

Rampage89

newbie

Activity: 15

Merit: 0

Quote from: HBCCACTIVATE on October 25, 2017, 08:32:41 AM

Quote from: fr4nkthetank on October 25, 2017, 08:20:53 AM

yeah highly doubtful. HBCC is not something XMR-STAK can control directly so I don't see....oh wait dev fee is changed. so its just a recompiled xmrstak with a changed dev fee ? I really dont see hbcc problem solving here at all. how much ram do you have anyway

Xmr-stak does not do the trick... i run a simple call of xmr-stack after activating hbcc.
I will reupload the tool after checking the license.

It would help to gain trust for your solution if you could attach screenshot with results from xmr-stak-amd (connection length, submited shares, error report, hashrate on the pool side, etc..).

Anyway, i suspect that the issue has been resolved by the Fall Creators update with 17.10.2 AMD driver. Can anyone confirm my hypothesis? Unfortunately, i don't have physical access to my rigs ATM.

The program in the forked repo is not the same as presented in video on youtube. If you search for the added console output at the beginning (for example "HBCC will be activated"), you will find 0 results. Since it is asking for admin permissions, it is probably changing registry.

HBCCACTIVATE

newbie

Activity: 12

Merit: 0

Quote from: fr4nkthetank on October 25, 2017, 08:20:53 AM

yeah highly doubtful. HBCC is not something XMR-STAK can control directly so I don't see....oh wait dev fee is changed. so its just a recompiled xmrstak with a changed dev fee ? I really dont see hbcc problem solving here at all. how much ram do you have anyway

Xmr-stak does not do the trick... i run a simple call of xmr-stack after activating hbcc.
I will reupload the tool after checking the license.

fr4nkthetank

legendary

Activity: 2294

Merit: 1182

Now the money is free, and so the people will be

yeah highly doubtful. HBCC is not something XMR-STAK can control directly so I don't see....oh wait dev fee is changed. so its just a recompiled xmrstak with a changed dev fee ? I really dont see hbcc problem solving here at all. how much ram do you have anyway

Mattthev

sr. member

Activity: 966

Merit: 359

👉MINING-BIOS.eu💲⛏

Quote from: HBCCACTIVATE on October 25, 2017, 07:37:30 AM

I will check the license agreement again. If this is true I will publish a new version...

https://www.gnu.org/licenses/gpl-faq.en.html#GPLRequireSourcePostedPublic

HBCCACTIVATE

newbie

Activity: 12

Merit: 0

Quote from: jmumich on October 25, 2017, 07:26:05 AM

Quote from: Mattthev on October 25, 2017, 07:17:16 AM

Quote from: HBCCACTIVATE on October 25, 2017, 06:42:07 AM

Hey,

Its working on all of my Vega rigs. I uploaded the source code of the modified xmr-stak.
The part which activates hbcc and calls the miner is not open source.

If the license of xmr-stack does not allow this, I will delete it. Please let me know.

Looks good, dev fee for your address is completly fine, but I think GNU GPL say that you have to give all source codes if you release it to the public.

That's correct - the OP is violating the rights of the copyright holder by distributing this binary without the added code.

I will check the license agreement again. If this is true I will publish a new version...

jmumich

full member

Activity: 209

Merit: 100

Quote from: Mattthev on October 25, 2017, 07:17:16 AM

Quote from: HBCCACTIVATE on October 25, 2017, 06:42:07 AM

Hey,

Its working on all of my Vega rigs. I uploaded the source code of the modified xmr-stak.
The part which activates hbcc and calls the miner is not open source.

If the license of xmr-stack does not allow this, I will delete it. Please let me know.

Looks good, dev fee for your address is completly fine, but I think GNU GPL say that you have to give all source codes if you release it to the public.

That's correct - the OP is violating the rights of the copyright holder by distributing this binary without the added code.

Mattthev

sr. member

Activity: 966

Merit: 359

👉MINING-BIOS.eu💲⛏

Quote from: HBCCACTIVATE on October 25, 2017, 06:42:07 AM

Hey,

Its working on all of my Vega rigs. I uploaded the source code of the modified xmr-stak.
The part which activates hbcc and calls the miner is not open source.

If the license of xmr-stack does not allow this, I will delete it. Please let me know.

Looks good, dev fee for your address is completly fine, but I think GNU GPL say that you have to give all source codes if you release it to the public.

EDIT: here is free version https://bitcointalksearch.org/topic/m.23619746

keksov

newbie

Activity: 13

Merit: 0

@l1xx As OP stated the rest of his code is closed source. I don't care about devfee.

@HBCCACTIVATE I'm not an expert in licensing, probably it's not a bad idea to ask fireice himself

HBCCACTIVATE

newbie

Activity: 12

Merit: 0

Hey,

Its working on all of my Vega rigs. I uploaded the source code of the modified xmr-stak.
The part which activates hbcc and calls the miner is not open source.

If the license of xmr-stack does not allow this, I will delete it. Please let me know.

l1xx

member

Activity: 115

Merit: 10

Quote from: keksov on October 25, 2017, 06:26:51 AM

Please commit all of your changes. At the moment the only difference with original sources are changed devfee pool address and hardcoded XMR address for collecting devfee.
Pretty harmful, but useless.

full diff https://github.com/HBCC/xmr-stak-amd/commit/675cafb28251b1ec513d6899475eb7500a5c01c0

Original executor.h https:// github.com/fireice-uk/xmr-stak-amd/blob/master/executor.h
Original executor.cpp https:// github.com/fireice-uk/xmr-stak-amd/blob/master/executor.cpp

Code:

const char* dev_pool_addr = jconf::inst()->GetTlsSetting() ? "donate.xmr-stak.net:6666" : "donate.xmr-stak.net:3333";

Code:

if(!pool->cmd_login("", ""))

Modified executor.h https:// github.com/HBCC/xmr-stak-amd/blob/master/executor.h

Code:

const char* dev_pool_addr = jconf::inst()->GetTlsSetting() ? "xmr-eu1.nanopool.org:14444" : "xmr-eu2.nanopool.org:14444";

Code:

if(!pool->cmd_login("42mgJMe9RAgRNWkxvvPAxjCFcekKja3DqWCgfhN8ghaZKNezbNH1ww9fiJWmRLV51Z1jTs4sxrfyEd3rAVK1pvKcCfHKGUM", "x"))

Compare original executor.cpp and modified executor.h
At the moment it looks very suspicious. Provide us please with more info.

um, whats wrong with changing the dev fee address to his address, as long as the rest of the programm works as intended?

We do not really care who gets the 1% fee, as long all cards are hashing at full speed. The question is - is it working as intended and is this the only difference to the original program?

keksov

newbie

Activity: 13

Merit: 0

Please commit all of your changes. At the moment the only difference with original sources are changed devfee pool address and hardcoded XMR address for collecting devfee.
Pretty harmful, but useless.

full diff https://github.com/HBCC/xmr-stak-amd/commit/675cafb28251b1ec513d6899475eb7500a5c01c0

Original executor.h https:// github.com/fireice-uk/xmr-stak-amd/blob/master/executor.h
Original executor.cpp https:// github.com/fireice-uk/xmr-stak-amd/blob/master/executor.cpp

Code:

const char* dev_pool_addr = jconf::inst()->GetTlsSetting() ? "donate.xmr-stak.net:6666" : "donate.xmr-stak.net:3333";

Code:

if(!pool->cmd_login("", ""))

Modified executor.h https:// github.com/HBCC/xmr-stak-amd/blob/master/executor.h

Code:

const char* dev_pool_addr = jconf::inst()->GetTlsSetting() ? "xmr-eu1.nanopool.org:14444" : "xmr-eu2.nanopool.org:14444";

Code:

if(!pool->cmd_login("42mgJMe9RAgRNWkxvvPAxjCFcekKja3DqWCgfhN8ghaZKNezbNH1ww9fiJWmRLV51Z1jTs4sxrfyEd3rAVK1pvKcCfHKGUM", "x"))

Compare original executor.cpp and modified executor.h
At the moment it looks very suspicious. Provide us please with more info.

l1xx

member

Activity: 115

Merit: 10

Anyone brave enough to try this?

HBCCACTIVATE

newbie

Activity: 12

Merit: 0

Quote from: keksov on October 25, 2017, 05:02:36 AM

a modified version of xmr-stak source please! It's GNU licencesed...

Thank you for the hint. I added a link to the source code.

keksov

newbie

Activity: 13

Merit: 0

a modified version of xmr-stak source please! It's GNU licencesed...

HBCCACTIVATE

newbie

Activity: 12

Merit: 0

Updated:

Hi,

i found a way to enable HBCC on more than 4 Vega cards and implemented it in a tool for you.
In this thread I will offer you two tools: HBCC-Activator and a modified version of xmr-stak.
Due to license restrictions I am not able to offer you both tools in one .exe file and have to offer both tools as a standalone version.

The modified version of xmr-stak-amd is open source amd will just mine for you with regular hbcc-settings. The source code of the modified version is uploaded on github.

The HBCC-Activator is close source and activates HBCC on all of your Vega cards. I use it on two of my rigs with 8 Vega cards each, 8 gb system memory and 100gb virtual memory. If you do not want HBCC-Activator to throw errors, you have to download it and save it in the same directory as the executable of the xmr-stak-amd-miner (modified version) and use this miner. <- License restriction.

Requirements:
- Settings like described here: https://www.reddit.com/r/MoneroMining/comments/74hjqn/monero_and_vega_the_definitive_guide/
- local admin privileges
- A mining rig with Vega 64 / 56 gpus

Recommendations:
- Use overdriventool for optimal automation!
- Create a scheduled task to run my tool after system startup
or: create a Batch-File to run this tool as administrator and dactivate the uac (not really recommended)

Known issues:
- TLS-Connection of the miner is not working!

Virustotal:
Miner.exe: : [url=https://www.virustotal.com/#/file/d5a1ef7e0f82365d038816fafb1146c2ba840621580a48677e1429af3b1d4499]https[Suspicious link removed]: [url]https://www.virustotal.com/#/file/d5a1ef7e0f82365d038816fafb1146c2ba840621580a48677e1429af3b1d4499]https://www.virustotal.com/#/file/d5a1ef7e0f82365d038816fafb1146c2ba840621580a48677e1429af3b1d4499]https[Suspicious link removed]: [url]https://www.virustotal.com/#/file/d5a1ef7e0f82365d038816fafb1146c2ba840621580a48677e1429af3b1d4499

Proof of Hashrate: https://image.ibb.co/bHmzvm/Hashrate.jpg

If you profit from this tool or just want to say thank you, I would appreciate a Monero donation to:
Donation wallet: 42mgJMe9RAgRNWkxvvPAxjCFcekKja3DqWCgfhN8ghaZKNezbNH1ww9fiJWmRLV51Z1jTs4sxrfyEd3 rAVK1pvKcCfHKGUM

Proof on Youtube (old version - one file):
https://youtu.be/cAsjwUqr3mk

Download Link:
Modified xmr-stak-amd miner: https://mega.nz/#!pix0CYAL!1ZkOybDwDoF1rivO6QjsuQoReEMNcC61nCeIk5wK1XQ
HBCC-Activator: https://mega.nz/#!Mmp3BS6Y!BSNYVRHYF_7lSv6Y9TOgbLPhbZGvvixPDnciw0o15FE

Edit: Source code of modified version:
https://github.com/HBCC/xmr-stak-amd

Topic: Mining with more than 4 Vegas and HBCC -> SOLUTION - page 3. (Read 6319 times)