Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 844. (Read 1260245 times)

ati/amd drivers always sucked big time and they still do
and their gpus are not known to be quiet or anything anyway

if someone doesn't need to work in the same room and/or has a different rig only for that purpose I understand, but I can't risk my main rig

it reaches the hashrate stated here though https://docs.google.com/spreadsheets/d/1hTOUdJZrKqrNDXTIbXgNvJtj_fnpECREcs-eHxaGrZc/edit?usp=sharing

Sounds more like a driver issue.

AMD 7970
sgminer from groestlcoin site just like the cpuminer
different custom options and the one from the groestlcoin page for the 7970

yes, it is quieter than scrypt, but it still corrupts the image (random up and down flickering that really messes with your mind) so that I can't use it for work while mining plus it's still too loud to work or do anything useful besides.
And I don't want to threaten the lifetime of my production rig GPU with being at 170F/77C constantly

I've been there when bitcoin started and couldn't mine because I needed the pc for other stuff. Now I can't mine because I ain't got GPUs to waste lol. It is kind of frustrating that cryptocurrencies are instantly exploited so that the average guy who doesn't spend money on building a mining rig doesn't really stand a chance.

That is really not much. I´ll do the same with my old AMD Phenom II X4. It is hard to mine something with that low hashrate.

I use my normal gpu on my home pc, but with the new algo it is much quieter than mining scrypt coins and it produce less heat.

it also doesn't work with the wildcard.
I tried it with diamond.conf and diamondcoin.conf in the -datadir folder. (both filenames appear in this thread)

currently trying to mine with a pool, but diff seems to be too high for a single i7 to warrant all this

The daemon finally get compiled. It begins to sync. I will report some problems later. Thanks

Hmmm the only different between our settings is i use for it.

@cryptonit + daishi:
exactly the same download from groestlcoin
batch is the same: minerd -a groestl -t 8 -o 127.0.0.1:17772 -u somesecretuser -p themegaultranooneknowpassword

the diamond.conf is in the %appdata%/Diamond folder respective my -datadir folder

I always get the connection refused message..

is there a way to check if it loads the diamond.conf correctly?

EDIT: I'm not so sure if I should even try getting it to work, difficulty just exploded.. I had a really hard time getting 10 DMD a week before with diff 1-3, now it's over 40!
I guess it's good for the price, but mining seems impossible if you don't have a dedicated GPU mining rig or tons of CPUs

what mining software u use?

use only mining software thats combatible with groestlcoin too
until we updated our website find them here http://www.groestlcoin.org/pools/

Which  OS and mining software do you use for cpu-mining?

Which settings u use for it?

I use minerd on windows and it works fine.

Here are my settings for my bat file

source updated https://github.com/pitdmd/DMD_Pit

precompiled linux diamondd headless wallet https://mega.co.nz/#!XI5QlAzJ!xKD4JtMLpJPAGdf0rAmiwARkZfdYRAO9fE3BcL71NAU


please keep in mind pool need custom stratum u need to be groestl combatible stratum
and u need to be foundation share compatible

here some point to start researching regarding needed foundation stratum changes
only interesting for people who setup a pool https://bitcointalk.org/index.php?topic=581065.920

regarding groestl stratum changes please pool owner with already running groestlpool share their knowledge

WITHOUT FIXED STRATUM POOLS WONT GET ACCEPTED BLOCKS!

I have contributed the following changes to makefile.bsd, in order to make diamond compile on FreeBSD. The first defines might be install specific, as they refer to the port versions I have installed.

diff -r Diamond-Coin-2.0.orig/src/makefile.bsd DMD_Final/src/makefile.bsd
5,6c5,11
< USE_UPNP:=0
< USE_IPV6:=1
---
> USE_UPNP:=-
> USE_IPV6:=-
> BOOST_INCLUDE_PATH=/usr/local/include
> BDB_INCLUDE_PATH=/usr/local/include/db48
> BOOST_LIB_PATH=/usr/local/lib
> BDB_LIB_PATH=/usr/local/lib/db48
> STATIC=1
55c60
<    -l dl \
---
> #   -l dl \
133a139,140
>     hash/groestl.o \
>     obj/scrypt.o \


So far so good, let's see how it runs.

Has anyone succeeded in making DMD work with a pool? I was away the whole day..

we know its open issue
on ui designer pc they where working after compile it was white in white in mouseover
we will fix this glitch in another wallet update
stability fix was to urgend to wait for ui mouseover fix

Found block with updated wallet looking good. 

Awesome work it is not crashing for me solo mining! Well at least not yet the other wallet worked for a few hours.
I am sure this was a very quick patch just reporting that any of the hover bubbles that pop up appear blank.

Edit: They are not blank. Text is just very close to the same color as the bubble.

I'm surprised by that response.

First, because my suggestion was so far fetched to begin with such that a smiley face would have been enough to put it down (and any implementation would have been truly revolutionary from the community ethic standpoint).

Second, because no-one would have even thought to include anything outside of this specific launch period in their counter-argument (what does anything about whether someone mined or not prior to block 386228 have to do with it? what does anything about the future have to do with it? we're talking about a specific period of time where only the selfish have benefited).

Third, because, at the end of the day, it is a response that ultimately defends (albeit poorly argued with irrelevant arguments) the position of the selfish miner who did not think of the community, and it ignores those who put the community first (think about it, who would benefit from your logic if such a revolutionary idea were indeed to be seriously contemplated? the selfish miner or the community contributor? - again, during this period of time from block 386228 to now, or whenever we do get the DMD network up and running)

None of that is to say that those are/were your intentions, but a very serious inference can be taken from your words.

As I said, I'm very surprised by that reply. It's very out of character for you.

And it's just not true that everyone had his chance to mine and that none got any advantage. To say that suggests a complete disconnect with the reality behind the current issue and situation.

Here is a post a few pages back:

isnt 5970 a card with 2x5870 chip? if so then even 5870 get the same hash rate as 7950

its not strange
its know that 59xx cards have very high performance on groestl algo