[ANN] MMC.1GH.COM - GPU mining, CPU mining ★

Started by 1gh, December 30, 2013, 09:49:57 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Banch

I got about 22hpm with 7970 with Windows Miner but then it crashed after about 5mins. Clocks went  from 1100/1150 -> 300/150... Need to reboot to see can I get it back online lol
Part of the Memorycoin 2.0 support team. Contacts in Finnish/English
MMC:MLAdfMX6LestwzuaQMyMFiGNrqM9qCS2Qf
LTC: LYdwtVfmaeCX8TyZ8etUBJfhithSxBATtc

lest

Quote from: reorder on December 30, 2013, 02:17:36 PM
Guys, windows miner is ready for testing: http://mmcdl.1gh.com/mc2-1gh-win.zip

Please report your success or any problems with running it.

I'm getting 8-10 hpm on two 7950 3Gb each. Profitability is the same as mining scrypt crypto at the moment.

andhar

aaah well that explains it then hehe.
[url="https://steemit.com/@harand"]https://steemit.com/@harand[/url]

Djemi

Quote from: andhar on December 30, 2013, 02:28:30 PM
Tested, opens and closes in a flash on win 8 64 bit. Using a Geforce 670 Card

It is for AMD Radeon only.

andhar

Tested, opens and closes in a flash on win 8 64 bit. Using a Geforce 670 Card
[url="https://steemit.com/@harand"]https://steemit.com/@harand[/url]

h0g0f0g0

Quote from: reorder on December 30, 2013, 02:14:35 PM
Quote from: h0g0f0g0 on December 30, 2013, 02:04:06 PM
Quote from: reorder on December 30, 2013, 01:59:10 PM
Quote from: h0g0f0g0 on December 30, 2013, 01:48:36 PM
Quote from: reorder on December 30, 2013, 12:56:47 PM
Quote from: h0g0f0g0 on December 30, 2013, 11:41:23 AM
This binary miner doesn't work on CentOS 6.5
Would you please quote the error message?

Initially:
./mmc-miner: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory

I have 1.0.1e self compiled on the system so I copied libcrypto and libssl into mc2 directory. Now
./mmc-miner: /root/mc2-1gh-lin-x64/libcrypto.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /root/mc2-1gh-lin-x64/libpython2.7.so.1.0)
./mmc-miner: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/mc2-1gh-lin-x64/libpython2.7.so.1.0)
./mmc-miner: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by /root/mc2-1gh-lin-x64/libpython2.7.so.1.0)
./mmc-miner: /root/mc2-1gh-lin-x64/libssl.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /root/mc2-1gh-lin-x64/libpython2.7.so.1.0)
Thank you so much for sharing. While I could get rid of openssl dependencies, libc is next to impossible to replace. Rewriting in C with static linking seems to be the only viable option, but that will take quite a lot of time.

Of course, the fastest option would be to provide the source code. I can compile binaries for multiple distributions then.
That for sure, but I have a stake in the pool and need to, you know, secure it. Though if you are interested, I could provide you with a compiled python-module-dll that you could run with any 64-bit python 2.7 interpreter.

Sure, I fully understand that. Python module would be great. thanks!

reorder

Guys, windows miner is ready for testing: http://mmcdl.1gh.com/mc2-1gh-win.zip

Please report your success or any problems with running it.

reorder

Quote from: h0g0f0g0 on December 30, 2013, 02:04:06 PM
Quote from: reorder on December 30, 2013, 01:59:10 PM
Quote from: h0g0f0g0 on December 30, 2013, 01:48:36 PM
Quote from: reorder on December 30, 2013, 12:56:47 PM
Quote from: h0g0f0g0 on December 30, 2013, 11:41:23 AM
This binary miner doesn't work on CentOS 6.5
Would you please quote the error message?

Initially:
./mmc-miner: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory

I have 1.0.1e self compiled on the system so I copied libcrypto and libssl into mc2 directory. Now
./mmc-miner: /root/mc2-1gh-lin-x64/libcrypto.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /root/mc2-1gh-lin-x64/libpython2.7.so.1.0)
./mmc-miner: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/mc2-1gh-lin-x64/libpython2.7.so.1.0)
./mmc-miner: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by /root/mc2-1gh-lin-x64/libpython2.7.so.1.0)
./mmc-miner: /root/mc2-1gh-lin-x64/libssl.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /root/mc2-1gh-lin-x64/libpython2.7.so.1.0)
Thank you so much for sharing. While I could get rid of openssl dependencies, libc is next to impossible to replace. Rewriting in C with static linking seems to be the only viable option, but that will take quite a lot of time.

Of course, the fastest option would be to provide the source code. I can compile binaries for multiple distributions then.
That for sure, but I have a stake in the pool and need to, you know, secure it. Though if you are interested, I could provide you with a compiled python-module-dll that you could run with any 64-bit python 2.7 interpreter.

h0g0f0g0

Quote from: reorder on December 30, 2013, 01:59:10 PM
Quote from: h0g0f0g0 on December 30, 2013, 01:48:36 PM
Quote from: reorder on December 30, 2013, 12:56:47 PM
Quote from: h0g0f0g0 on December 30, 2013, 11:41:23 AM
This binary miner doesn't work on CentOS 6.5
Would you please quote the error message?

Initially:
./mmc-miner: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory

I have 1.0.1e self compiled on the system so I copied libcrypto and libssl into mc2 directory. Now
./mmc-miner: /root/mc2-1gh-lin-x64/libcrypto.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /root/mc2-1gh-lin-x64/libpython2.7.so.1.0)
./mmc-miner: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/mc2-1gh-lin-x64/libpython2.7.so.1.0)
./mmc-miner: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by /root/mc2-1gh-lin-x64/libpython2.7.so.1.0)
./mmc-miner: /root/mc2-1gh-lin-x64/libssl.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /root/mc2-1gh-lin-x64/libpython2.7.so.1.0)
Thank you so much for sharing. While I could get rid of openssl dependencies, libc is next to impossible to replace. Rewriting in C with static linking seems to be the only viable option, but that will take quite a lot of time.

Of course, the fastest option would be to provide the source code. I can compile binaries for multiple distributions then.

reorder

Quote from: h0g0f0g0 on December 30, 2013, 01:48:36 PM
Quote from: reorder on December 30, 2013, 12:56:47 PM
Quote from: h0g0f0g0 on December 30, 2013, 11:41:23 AM
This binary miner doesn't work on CentOS 6.5
Would you please quote the error message?

Initially:
./mmc-miner: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory

I have 1.0.1e self compiled on the system so I copied libcrypto and libssl into mc2 directory. Now
./mmc-miner: /root/mc2-1gh-lin-x64/libcrypto.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /root/mc2-1gh-lin-x64/libpython2.7.so.1.0)
./mmc-miner: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/mc2-1gh-lin-x64/libpython2.7.so.1.0)
./mmc-miner: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by /root/mc2-1gh-lin-x64/libpython2.7.so.1.0)
./mmc-miner: /root/mc2-1gh-lin-x64/libssl.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /root/mc2-1gh-lin-x64/libpython2.7.so.1.0)
Thank you so much for sharing. While I could get rid of openssl dependencies, libc is next to impossible to replace. Rewriting in C with static linking seems to be the only viable option, but that will take quite a lot of time.

h0g0f0g0

Quote from: reorder on December 30, 2013, 12:56:47 PM
Quote from: h0g0f0g0 on December 30, 2013, 11:41:23 AM
This binary miner doesn't work on CentOS 6.5
Would you please quote the error message?

Initially:
./mmc-miner: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory

I have 1.0.1e self compiled on the system so I copied libcrypto and libssl into mc2 directory. Now
./mmc-miner: /root/mc2-1gh-lin-x64/libcrypto.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /root/mc2-1gh-lin-x64/libpython2.7.so.1.0)
./mmc-miner: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /root/mc2-1gh-lin-x64/libpython2.7.so.1.0)
./mmc-miner: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by /root/mc2-1gh-lin-x64/libpython2.7.so.1.0)
./mmc-miner: /root/mc2-1gh-lin-x64/libssl.so.1.0.0: version `OPENSSL_1.0.0' not found (required by /root/mc2-1gh-lin-x64/libpython2.7.so.1.0)

earntodie

1GH CLUB!! PTS mining club - [url=http://PTS.1GH.COM]PTS.1GH.COM[/url], MEMORY coin mining club - [url=http://mmc.1gh.com]MMC.1GH.COM[/url], MAX coin mining club - [url=http://max.1GH.COM]MAX.1GH.COM[/url]

itsik78

Haven't noticed, but I will restart it later and let you know.
The cards have 4gb mem each

reorder

Quote from: smokim11 on December 30, 2013, 12:34:37 PM
Well when rig miners hear about this were going to see a huge inflow of MMC into the market. Supply is going to be overflowing the market and MMC if were lucky will still be worth more than a cent.
New mint inflow is constant no matter what the total hpm. I do not think rig owners are more likely to mine and dump than botnet owners are.

reorder

Quote from: itsik78 on December 30, 2013, 01:04:15 PM
UPDATE:
2 cards seem to work better in total:
(2xR290)
·
Accepted                                                                                │············································
Mon Dec 30 15:01:31 2013 Worker 1 hpm 24.456386 wpm 18.919091 A/R/T 10/0/0 -> RPC result:│············································
Accepted                                                                                │············································
Mon Dec 30 15:02:08 2013 Worker 0 hpm 17.449997 wpm 18.874486 A/R/T 11/0/0 -> RPC result:│············································
Accepted                                                                                │············································
Mon Dec 30 15:02:12 2013 Worker 1 hpm 22.090128 wpm 18.934395 A/R/T 11/0/0 -> RPC result:│············································
Accepted                                                                                │············································
Mon Dec 30 15:02:18 2013 Worker 1 hpm 22.316627 wpm 18.935319 A/R/T 12/0/0 -> RPC result:│············································
Accepted                                                                                │············································
Mon Dec 30 15:02:21 2013 Worker 0 hpm 18.876240 wpm 18.876240 A/R/T 12/0/0 -> RPC result:│············································
Accepted                                                                                │············································
Mon Dec 30 15:02:30 2013 Worker 0 hpm 19.505215 wpm 18.876014 A/R/T 13/0/0 -> RPC result:│············································
Accepted                                                                                │············································
Mon Dec 30 15:02:37 2013 Worker 1 hpm 21.380258 wpm 18.936799 A/R/T 13/0/0 -> RPC result:│············································
Accepted                                                                                │············································
Mon Dec 30 15:02:56 2013 Worker 1 hpm 20.891281 wpm 18.941428 A/R/T 14/0/0 -> RPC result:│············································
Accepted                                                                                │············································
Mon Dec 30 15:03:05 2013 Worker 0 hpm 19.150587 wpm 18.884606 A/R/T 14/0/0 -> RPC result:│············································
Accepted                                                                                │············································
Mon Dec 30 15:03:18 2013 Worker 0 hpm 19.643999 wpm 18.888460 A/R/T 15/0/0 -> RPC result:│············································
Accepted                                                                                │············································
Mon Dec 30 15:03:30 2013 Worker 0 hpm 19.843978 wpm 18.887642 A/R/T 16/0/0 -> RPC result:│············································
Accepted                                                                                │············································
Mon Dec 30 15:03:34 2013 Worker 1 hpm 20.134477 wpm 18.950096 A/R/T 15/0/0 -> RPC result:│············································
Accepted         
During initialization, did it tell it is using 1-pass or 2-pass algo? Because 2-pass is for cards with 2G RAM and is slower than 1-pass that is for everything higher.