[ANN][DCR] Decred - Community Governance | Bitcoin Devs | Lightning Network - page 488.

Shrikez

sr. member

Activity: 400

Merit: 263

Quote from: jwinterm on February 05, 2016, 09:37:08 AM

Quote from: Shrikez on February 05, 2016, 05:31:17 AM

Quote from: wildduck on February 05, 2016, 05:16:08 AM

Quote from: Shrikez on February 05, 2016, 03:52:38 AM

Quote from: ocminer on February 05, 2016, 03:40:29 AM

Hmm sorry no idea.. maybe its missing an export or so ?

I compile with ./configure --enable-opencl and it works just fine

I'll dive into it when I have more time. For the sake of completeness here's the config.log: http://fpaste.org/318868/54662242/

Thank you for your time

One question mate in ADL_SDK directory did you put file for support for amd GPU?

Pardon me, I don't understand. Could you elaborate?

You need to download the ADL_SDK library, and put the contents of the /include folder in the /ADL_SDK folder in your miner directory, before you do config/make. I'm sure if you google "adl sdk cgminer" you'll get lots more info.

Thanks, I just did that but the result is the same, the output remains

Code:

OpenCL...............: NOT FOUND. GPU mining support DISABLED
configure: error: No mining configured in

will duckduckgo around a bit later tonight. thanks again.

jwinterm

legendary

Activity: 3136

Merit: 1116

Quote from: Shrikez on February 05, 2016, 05:31:17 AM

Quote from: wildduck on February 05, 2016, 05:16:08 AM

Quote from: Shrikez on February 05, 2016, 03:52:38 AM

Quote from: ocminer on February 05, 2016, 03:40:29 AM

Hmm sorry no idea.. maybe its missing an export or so ?

I compile with ./configure --enable-opencl and it works just fine

I'll dive into it when I have more time. For the sake of completeness here's the config.log: http://fpaste.org/318868/54662242/

Thank you for your time

One question mate in ADL_SDK directory did you put file for support for amd GPU?

Pardon me, I don't understand. Could you elaborate?

You need to download the ADL_SDK library, and put the contents of the /include folder in the /ADL_SDK folder in your miner directory, before you do config/make. I'm sure if you google "adl sdk cgminer" you'll get lots more info.

tbearhere

legendary

Activity: 3164

Merit: 1003

Quote from: ocminer on February 05, 2016, 09:03:01 AM

Quote from: tbearhere on February 05, 2016, 08:42:08 AM

Quote from: ocminer on December 15, 2015, 11:20:31 AM

Will be ready for this one

Are you ready for us to sign up oc ? thx

sure, reg is open, just create your account, test your miners and everything will be good at launch

Great thx
ps sp I believe is now working on ccminer for Decred for nvidia cards.

ocminer

legendary

Activity: 2688

Merit: 1240

Quote from: tbearhere on February 05, 2016, 08:42:08 AM

Quote from: ocminer on December 15, 2015, 11:20:31 AM

Will be ready for this one

Are you ready for us to sign up oc ? thx

sure, reg is open, just create your account, test your miners and everything will be good at launch

Wolf0

member

Activity: 81

Merit: 1002

It was only the wind.

Everyone using my builds should update to the latest one here for Win64:
https://ottrbutt.com/miner/downloads/decred-cgminer/wolf-decred-cgminer-02042016-win64.zip
https://ottrbutt.com/miner/downloads/decred-cgminer/wolf-decred-cgminer-02042016-win64.zip.sig
These are based off of the official Decred CGMiner GitHub sources found at https://github.com/decred/cgminer - branch 3.7, commit c172a7a62455fae62afdc7995021f5c046aab9d7 with small modifications to get it to build with my set of Win64 tools. As before, it should require no DLLs other than what ships with Windows to function. Failure to upgrade may result in rejected/duplicate shares when pool mining, and/or other bugs.

tbearhere

legendary

Activity: 3164

Merit: 1003

Quote from: ocminer on December 15, 2015, 11:20:31 AM

Will be ready for this one

Are you ready for us to sign up oc ? thx

Bitcoin_Delivery

hero member

Activity: 952

Merit: 500

Quote from: ocminer on February 05, 2016, 01:41:44 AM

Be sure to use the latest version of cgminer - it's tagged 0.0.2 from decred official or compile directly from github:

https://github.com/decred/cgminer

I'm unsure on which version Wolf's compile is based on.

According to the post of Wolf on the official forum thread

[....]These are based off of the official Decred CGMiner GitHub sources found at https://github.com/decred/cgminer - branch 3.7, commit c172a7a62455fae62afdc7995021f5c046aab9d7 with small modifications[....]
Can read all here https://forum.decred.org/threads/cgminer-hardware-performance.330/page-9#post-6368

ocminer

legendary

Activity: 2688

Merit: 1240

Quote from: kahir on February 05, 2016, 05:03:50 AM

OCminer is there a NVidia windows miner ?

Afaik no ccminer yet, I am not sure tpruvot is working on it, just heard some rumors.

Shrikez

sr. member

Activity: 400

Merit: 263

Quote from: wildduck on February 05, 2016, 05:16:08 AM

Quote from: Shrikez on February 05, 2016, 03:52:38 AM

Quote from: ocminer on February 05, 2016, 03:40:29 AM

Hmm sorry no idea.. maybe its missing an export or so ?

I compile with ./configure --enable-opencl and it works just fine

I'll dive into it when I have more time. For the sake of completeness here's the config.log: http://fpaste.org/318868/54662242/

Thank you for your time

One question mate in ADL_SDK directory did you put file for support for amd GPU?

Pardon me, I don't understand. Could you elaborate?

wildduck

legendary

Activity: 966

Merit: 1001

Quote from: Shrikez on February 05, 2016, 03:52:38 AM

Quote from: ocminer on February 05, 2016, 03:40:29 AM

Hmm sorry no idea.. maybe its missing an export or so ?

I compile with ./configure --enable-opencl and it works just fine

I'll dive into it when I have more time. For the sake of completeness here's the config.log: http://fpaste.org/318868/54662242/

Thank you for your time

One question mate in ADL_SDK directory did you put file for support for amd GPU?

Wolf0

member

Activity: 81

Merit: 1002

It was only the wind.

Quote from: theLosers106 on February 04, 2016, 11:50:50 AM

Quote from: Wolf0 on February 04, 2016, 11:45:45 AM

Quote from: sambiohazard on February 04, 2016, 10:59:48 AM

Quote from: Wolf0 on February 04, 2016, 10:38:45 AM

Quote from: sambiohazard on February 04, 2016, 09:23:55 AM

Quote from: Wolf0 on February 04, 2016, 09:05:11 AM

Quote from: sambiohazard on February 04, 2016, 08:21:04 AM

Quote from: Wolf0 on February 04, 2016, 06:10:08 AM

Quote from: sambiohazard on February 04, 2016, 05:25:47 AM

Quote from: Wolf0 on February 03, 2016, 10:15:16 PM

Quote from: thefix on February 03, 2016, 08:39:00 PM

Very interesting project, unfortunate that Nvidia miners are not getting the same love as AMD

Do we need to crowd fund to get something valid released?

Maybe we just do not have enough Nvidia miners to Justify our existence.

Really, you're not being as picked on as it seems - CUDA is great when it comes to more complex algos, or algos that can benefit from Nvidia-specific optimizations that the compiler is unable to find by itself, but this is not the case for Decred. Really, you're talking about a minor bump I would guess, at most. The algo is dead simple - I've made the miner a few percent faster on AMD - but we're talking single digit percentages... and low digits. The Nvidia OpenCL compiler would really have a hard time fucking it up.

@wolf I tried the cgminer & ccminer both & they give me

970 1.52 GH/s on ccminer & 1.11GH/s on cgminer
750ti 530MH/s in ccminer & 431 MH/s on cgminer

so there is 75-80% loss in hashrate. Also as i remember, ccminer was running at much lower TDP% as shown in Afterburner, ~80% while cgminer was using 98-100% power. Considering all this i think there is a big disadvantage & some potential for optimizing ccminer for decred, unless the modification required for decred somehow lower the hashrate. But i guess ccminer devs are too busy taking potshots at each other, so we will have to make do with what we have or wait for decred team to release something.

Dude, of COURSE there is. That's 8 round Blake, this is 14 round Blake. Try to understand what the PoW is before benchmarking.

Since 14 is 75% more than 8... you're DEAD ON.

Nope that is for 14 round blake. On 8 round blake i get 2.5GH/s & 920 MH/s. I am mining VNL right now. I am a noob but not that much.

*facepaw* VNL is 8 round.

@wolf exactly 8 round blake on VNL is giving me 2.5 GH/s & 920 MH/s and 14 round gives me 1.5GH/s & 520MH/s on ccminer. What is facepalm about it? still cgminer is 80% less than what i get on ccminer for 14 round blake. Also 14 round blake is 60% of 8 round blake on ccminer so there is some room for improvement if as you say it should be 80% of 8 round blake. Dude you totally taking me for a moron or am i really missing something here?

I don't get it - how are you testing an 8 round Blake-256 on ccminer when it's not implemented?

Its implemented for VNL for sure & i guess for blakecoin as well, although i am not sure, in tpruvot's ccminer fork. I am using that.

See, when you say things like that, it makes me think you misunderstand. You see, VNL uses eight round Blake-256. Blakecoin uses 8 round Blake-256. Decred is the only one I know of using 14-round Blake-256, and it doesn't have a CCMiner implementation yet as far as I know, so I'm unsure as to how you've benchmarked it.

Not to pissed anyone.. but Wolf0, I'm assuming he is using this: https://github.com/tpruvot/ccminer/blob/windows/ccminer.cpp#L1833 to benchmark..

NOW I get it - I didn't know CCMiner had ANY 14 round code done.

kahir

legendary

Activity: 1050

Merit: 1000

OCminer is there a NVidia windows miner ?

Shrikez

sr. member

Activity: 400

Merit: 263

Quote from: ocminer on February 05, 2016, 03:40:29 AM

Hmm sorry no idea.. maybe its missing an export or so ?

I compile with ./configure --enable-opencl and it works just fine

I'll dive into it when I have more time. For the sake of completeness here's the config.log: http://fpaste.org/318868/54662242/

Thank you for your time

ocminer

legendary

Activity: 2688

Merit: 1240

Quote from: Shrikez on February 05, 2016, 03:39:20 AM

Quote from: ocminer on February 05, 2016, 03:23:23 AM

Quote from: Shrikez on February 05, 2016, 03:22:36 AM

ocminer:

I am having issues building your miner on Linux (Mint 17.3). I am still kind of a newbie on Linux so it's very likely some oversight happend.

this is my result after running ./config:

http://fpaste.org/318850/46604871/

and subsequently after running make:

http://fpaste.org/318848/14546604/

any hint on what might be wrong?

Thank you in advance

I saw that too, its a broken autoconfigure.ac

I've deleted my repo now, as all my fixes are merged into the official branch, just grab this one:

https://github.com/decred/cgminer

It'll work fine !

I cloned from above link and tried again but I still get http://fpaste.org/318859/66136914/ (OpenCL...............: NOT FOUND. GPU mining support DISABLED)
after running ./config

make now produces the following result:

http://fpaste.org/318860/14546615/

Sorry for bothering you Sad

Hmm sorry no idea.. maybe its missing an export or so ?

I compile with ./configure --enable-opencl and it works just fine

Shrikez

sr. member

Activity: 400

Merit: 263

Quote from: ocminer on February 05, 2016, 03:23:23 AM

Quote from: Shrikez on February 05, 2016, 03:22:36 AM

ocminer:

I am having issues building your miner on Linux (Mint 17.3). I am still kind of a newbie on Linux so it's very likely some oversight happend.

this is my result after running ./config:

http://fpaste.org/318850/46604871/

and subsequently after running make:

http://fpaste.org/318848/14546604/

any hint on what might be wrong?

Thank you in advance

I saw that too, its a broken autoconfigure.ac

I've deleted my repo now, as all my fixes are merged into the official branch, just grab this one:

https://github.com/decred/cgminer

It'll work fine !

I cloned from above link and tried again but I still get http://fpaste.org/318859/66136914/ (OpenCL...............: NOT FOUND. GPU mining support DISABLED)
after running ./config

make now produces the following result:

http://fpaste.org/318860/14546615/

Sorry for bothering you Sad

Wolf0

member

Activity: 81

Merit: 1002

It was only the wind.

Quote from: sambiohazard on February 04, 2016, 10:59:48 AM

Quote from: Wolf0 on February 04, 2016, 10:38:45 AM

Quote from: sambiohazard on February 04, 2016, 09:23:55 AM

Quote from: Wolf0 on February 04, 2016, 09:05:11 AM

Quote from: sambiohazard on February 04, 2016, 08:21:04 AM

Quote from: Wolf0 on February 04, 2016, 06:10:08 AM

Quote from: sambiohazard on February 04, 2016, 05:25:47 AM

Quote from: Wolf0 on February 03, 2016, 10:15:16 PM

Quote from: thefix on February 03, 2016, 08:39:00 PM

Very interesting project, unfortunate that Nvidia miners are not getting the same love as AMD

Do we need to crowd fund to get something valid released?

Maybe we just do not have enough Nvidia miners to Justify our existence.

Really, you're not being as picked on as it seems - CUDA is great when it comes to more complex algos, or algos that can benefit from Nvidia-specific optimizations that the compiler is unable to find by itself, but this is not the case for Decred. Really, you're talking about a minor bump I would guess, at most. The algo is dead simple - I've made the miner a few percent faster on AMD - but we're talking single digit percentages... and low digits. The Nvidia OpenCL compiler would really have a hard time fucking it up.

@wolf I tried the cgminer & ccminer both & they give me

970 1.52 GH/s on ccminer & 1.11GH/s on cgminer
750ti 530MH/s in ccminer & 431 MH/s on cgminer

so there is 75-80% loss in hashrate. Also as i remember, ccminer was running at much lower TDP% as shown in Afterburner, ~80% while cgminer was using 98-100% power. Considering all this i think there is a big disadvantage & some potential for optimizing ccminer for decred, unless the modification required for decred somehow lower the hashrate. But i guess ccminer devs are too busy taking potshots at each other, so we will have to make do with what we have or wait for decred team to release something.

Dude, of COURSE there is. That's 8 round Blake, this is 14 round Blake. Try to understand what the PoW is before benchmarking.

Since 14 is 75% more than 8... you're DEAD ON.

Nope that is for 14 round blake. On 8 round blake i get 2.5GH/s & 920 MH/s. I am mining VNL right now. I am a noob but not that much.

*facepaw* VNL is 8 round.

@wolf exactly 8 round blake on VNL is giving me 2.5 GH/s & 920 MH/s and 14 round gives me 1.5GH/s & 520MH/s on ccminer. What is facepalm about it? still cgminer is 80% less than what i get on ccminer for 14 round blake. Also 14 round blake is 60% of 8 round blake on ccminer so there is some room for improvement if as you say it should be 80% of 8 round blake. Dude you totally taking me for a moron or am i really missing something here?

I don't get it - how are you testing an 8 round Blake-256 on ccminer when it's not implemented?

Its implemented for VNL for sure & i guess for blakecoin as well, although i am not sure, in tpruvot's ccminer fork. I am using that.

See, when you say things like that, it makes me think you misunderstand. You see, VNL uses eight round Blake-256. Blakecoin uses 8 round Blake-256. Decred is the only one I know of using 14-round Blake-256, and it doesn't have a CCMiner implementation yet as far as I know, so I'm unsure as to how you've benchmarked it.

ocminer

legendary

Activity: 2688

Merit: 1240

Quote from: Shrikez on February 05, 2016, 03:22:36 AM

ocminer:

I am having issues building your miner on Linux (Mint 17.3). I am still kind of a newbie on Linux so it's very likely some oversight happend.

this is my result after running ./config:

http://fpaste.org/318850/46604871/

and subsequently after running make:

http://fpaste.org/318848/14546604/

any hint on what might be wrong?

Thank you in advance

I saw that too, its a broken autoconfigure.ac

I've deleted my repo now, as all my fixes are merged into the official branch, just grab this one:

https://github.com/decred/cgminer

It'll work fine !

Shrikez

sr. member

Activity: 400

Merit: 263

ocminer:

I am having issues building your miner on Linux (Mint 17.3). I am still kind of a newbie on Linux so it's very likely some oversight happend.

this is my result after running ./config:

http://fpaste.org/318850/46604871/

and subsequently after running make:

http://fpaste.org/318848/14546604/

any hint on what might be wrong?

Thank you in advance

Wolf0

member

Activity: 81

Merit: 1002

It was only the wind.

Quote from: sambiohazard on February 04, 2016, 09:23:55 AM

Quote from: Wolf0 on February 04, 2016, 09:05:11 AM

Quote from: sambiohazard on February 04, 2016, 08:21:04 AM

Quote from: Wolf0 on February 04, 2016, 06:10:08 AM

Quote from: sambiohazard on February 04, 2016, 05:25:47 AM

Quote from: Wolf0 on February 03, 2016, 10:15:16 PM

Quote from: thefix on February 03, 2016, 08:39:00 PM

Very interesting project, unfortunate that Nvidia miners are not getting the same love as AMD

Do we need to crowd fund to get something valid released?

Maybe we just do not have enough Nvidia miners to Justify our existence.

Really, you're not being as picked on as it seems - CUDA is great when it comes to more complex algos, or algos that can benefit from Nvidia-specific optimizations that the compiler is unable to find by itself, but this is not the case for Decred. Really, you're talking about a minor bump I would guess, at most. The algo is dead simple - I've made the miner a few percent faster on AMD - but we're talking single digit percentages... and low digits. The Nvidia OpenCL compiler would really have a hard time fucking it up.

@wolf I tried the cgminer & ccminer both & they give me

970 1.52 GH/s on ccminer & 1.11GH/s on cgminer
750ti 530MH/s in ccminer & 431 MH/s on cgminer

so there is 75-80% loss in hashrate. Also as i remember, ccminer was running at much lower TDP% as shown in Afterburner, ~80% while cgminer was using 98-100% power. Considering all this i think there is a big disadvantage & some potential for optimizing ccminer for decred, unless the modification required for decred somehow lower the hashrate. But i guess ccminer devs are too busy taking potshots at each other, so we will have to make do with what we have or wait for decred team to release something.

Dude, of COURSE there is. That's 8 round Blake, this is 14 round Blake. Try to understand what the PoW is before benchmarking.

Since 14 is 75% more than 8... you're DEAD ON.

Nope that is for 14 round blake. On 8 round blake i get 2.5GH/s & 920 MH/s. I am mining VNL right now. I am a noob but not that much.

*facepaw* VNL is 8 round.

@wolf exactly 8 round blake on VNL is giving me 2.5 GH/s & 920 MH/s and 14 round gives me 1.5GH/s & 520MH/s on ccminer. What is facepalm about it? still cgminer is 80% less than what i get on ccminer for 14 round blake. Also 14 round blake is 60% of 8 round blake on ccminer so there is some room for improvement if as you say it should be 80% of 8 round blake. Dude you totally taking me for a moron or am i really missing something here?

I don't get it - how are you testing an 8 round Blake-256 on ccminer when it's not implemented?

ocminer

legendary

Activity: 2688

Merit: 1240

Be sure to use the latest version of cgminer - it's tagged 0.0.2 from decred official or compile directly from github:

https://github.com/decred/cgminer

I'm unsure on which version Wolf's compile is based on.

Earlier versions had two (severe) errors:

roll-work was broken - this means the ntime of the work done was incremented at the wrong end of the hex string, the years where incremented, not the seconds. The work was done for shares in the year 2525 or somewhere then - which of course then are rejected by the daemon. So the pool rejects those shares (time-too-new). This is or at least should be fixed in the latest version.

duplicate shares - those are also fixed in the latest version.

If you still get those errors with the latest versions of the miners, let me know with the workername and i'll check in the logs what you've submitted.

Topic: [ANN][DCR] Decred - Community Governance | Bitcoin Devs | Lightning Network - page 488. (Read 1201380 times)