Ok trying to solomine this bad boy on my W8.1 rig... I did the following: Downloaded installed "shift-windows-386" Downloaded installed "ShiftWallet_0_9_1" Wallet up and running and connected to 8 peers Then followed the instructions here http://cryptomining-blog.com/5344-quick-guide-on-solo-gpu-mining-ethereum-on-windows/Starting geth for solo mining: – To listen for connections only on the local system type: geth --rpc --rpcaddr "localhost" --rpcport 8545and Starting ethminer for solo mining: – For local system mining with ethminer on the same PC that geth is running on use: ethminer -GHowever it doesn't appear to be mining. Did i miss a step?  1. start shift-windows-386 2. create an account3. wait until your client is full syncronized (until it starts importing just one block a time above block #21955) 4. start ethminer |
|
|
|
still segfaulting... i also notice it segfaults with just the -h or -V flags too after printing out the infos and curiously it doesn't when started inside gdb (it starts hashing normally) What's your command line? I don't have a pool for that so only tested with -a whirlpoolx --benchmark. I came across that other mess of crashes you mentioned. Uninitialized globals galore! See https://github.com/t-nelson/ccminer/tree/sigh. I'll PR it once I test build on Windows. the same command line as you and replacing --benchmark with pool's url/user/pass flags doesn't make any difference... sp_ merged the first fix. I've rebased the branch mentioned in my last post on top of it. Give that a try, maybe I fixed it by accident.  Mind linking me to the pool you're using? Or if it's public/anon pool you can just PM me your credentials and I'll throw some hashes at you to test. why not yours?  ./ccminer -a whirpoolx -o stratum+tcp://whirlpoolx.eu.nicehash.com:3343 -u 1K4yxRwZB8DpFfCgeJnFinSqeU23dQFEMu -p x with this command line i've got a segfault while running inside the debugger if it helps: $ gdb ./ccminer
GNU gdb (Gentoo 7.9.1 vanilla) 7.9.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://bugs.gentoo.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./ccminer...done.
(gdb) run -a whirlpoolx -o stratum+tcp://whirlpoolx.eu.nicehash.com:3343 -u 1K4yxRwZB8DpFfCgeJnFinSqeU23dQFEMu -p x
Starting program: /home/skunk/bitcoin/ccminer-nelson/ccminer -a whirlpoolx -o stratum+tcp://whirlpoolx.eu.nicehash.com:3343 -u 1K4yxRwZB8DpFfCgeJnFinSqeU23dQFEMu -p x
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
*** ccminer 1.5.65-git(SP-MOD) for nVidia GPUs by sp-hash@github ***
Built with the nVidia CUDA SDK 6.5
Based on pooler cpuminer 2.3.2 and the tpruvot@github fork
CUDA support by Christian Buchner, Christian H. and DJM34
Includes optimizations implemented by sp , klaust, tpruvot and tsiv.
[2015-09-06 20:20:22] Starting Stratum on stratum+tcp://whirlpoolx.eu.nicehash.com:3343
[New Thread 0x7fffeffff700 (LWP 6145)]
[2015-09-06 20:20:22] NVML GPU monitoring enabled.
[2015-09-06 20:20:22] 1 miner thread started, using 'whirlpoolx' algorithm.
[2015-09-06 20:20:22] Binding thread 0 to cpu 0 (mask 1)
0
[2015-09-06 20:20:22] Stratum difficulty set to 0.08
[2015-09-06 20:20:23] whirlpoolx.eu.nicehash.com:3343 whirlpoolx block 200187
[New Thread 0x7fffeefd1700 (LWP 6148)]
[New Thread 0x7fffee7d0700 (LWP 6152)]
[New Thread 0x7ffff4b0b700 (LWP 6144)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffeefd1700 (LWP 6148)]
0x00000000004ea081 in whirlpoolx_setBlock_80(void*, void const*) ()
(gdb) bt
#0 0x00000000004ea081 in whirlpoolx_setBlock_80(void*, void const*) ()
#1 0x00000000004ea8a3 in scanhash_whirlpoolx ()
#2 0x00000000004128af in miner_thread(void*) ()
#3 0x00007ffff6cfb5c4 in start_thread () from /lib64/libpthread.so.0
#4 0x00007ffff5dafedd in clone () from /lib64/libc.so.6
(gdb)
|
|
|
|
still segfaulting... i also notice it segfaults with just the -h or -V flags too after printing out the infos and curiously it doesn't when started inside gdb (it starts hashing normally) What's your command line? I don't have a pool for that so only tested with -a whirlpoolx --benchmark. I came across that other mess of crashes you mentioned. Uninitialized globals galore! See https://github.com/t-nelson/ccminer/tree/sigh. I'll PR it once I test build on Windows. the same command line as you and replacing --benchmark with pool's url/user/pass flags doesn't make any difference... |
|
|
|
still segfaulting... i also notice it segfaults even with the -h or -V flags too after printing out the infos and curiously it doesn't when started inside gdb (it starts hashing normally) |
|
|
|
|
master's whirlpoolx seems broken, it segfaults under linux...
|
|
|
|
intersting... do you know bitnation? maybe the two project can join each other... |
|
|
|
What does this -p d=0.002 do?  it's the desired share difficulty you can set as password parameter on some multipools or on nicehash So a difficulty of 0.002 is better on some algo/hardware than 0.001 it uses at default when nothing is set? no. read https://www.nicehash.com/index.jsp?p=faq#faqs10 |
|
|
|
What does this -p d=0.002 do? it's the desired share difficulty you can set as password parameter on some multipools or on nicehash |
|
|
|
Submitted an optimalization in bmw-256.
Do bmw with less assembly instructions
lyra2v2 +10KHASH on the 750ti.
lyra2/lyra2REv2.o: In function `scanhash_lyra2v2':
tmpxft_00002d40_00000000-3_lyra2REv2.cudafe1.cpp:(.text+0x6f8): undefined reference to `bmw256_cpu_hash_32(int, unsigned int, unsigned int, unsigned long*, unsigned int*, unsigned long)'
collect2: error: ld returned 1 exit status
|
|
|
|
I do not know what I need to do to let it sync. In the previous, older version synchronization started automatically! The clock on my computer is OK and your work!?!?!
What impressed me is that the new version geth.exe /1.1.0/ does no creat blockchain folder in user\appdata\roaming\ethereum.....!
yes, mine works and it's still v1.0.2-a0303ff4... do you let it run at least 5 minutes before checking? what's the output of net.peerCount? admin.chainSyncStatus? (you don't need to post unecessary screenshots btw) did you try resetting your system time? are you sure windows or router firewall it's not in your way? maybe you should ask for support on ethereum forum |
|
|
|
I downloaded the new version and copy new file geth.exe instead of the old! Again not working. Balance again '0', but this time in red. Furthermore, the new wallet is not synchronized with the network and does not move!
I do not understand what the problem was and why I can not see the real balance of 11.00 ETH.
Other ideas!
what's the output of eth.blockNumber? it should be greater then 147333, else your client isn't syncing... if not, check your system time as geth stops to sync if it's off. |
|
|
|
|
how do i calculate daily mined coins from my hashrate on the gpu channel?
|
|
|
|
hi,
since yesterday's issue, my balance was reset to 0 and didn't receive any payment, i'm mining here since two days with 10 mhs and got just .4 eth when it should have been at least 2...
my account is 0x873517202d47c9dd023ee89fa2e072dcc76ea2c4
thank you
Yesterday Eth network had an issue, and pool was on wrong chain. More informations > https://blog.ethereum.org/2015/08/20/security-alert-consensus-issue/Now everything is fine. We have updated client. this doesn't explain where my previous balance (before the reset) went! |
|
|
|
|
hi,
since yesterday's issue, my balance was reset to 0 and didn't receive any payment, i'm mining here since two days with 10 mhs and got just .4 eth when it should have been at least 2...
my account is 0x873517202d47c9dd023ee89fa2e072dcc76ea2c4
thank you
|
|
|
|
50mhs throwing to pool ,how much i get in one day?
actually 4.7 eth |
|
|
|
There is no projectfile for visual studio 2013. and the cuda 7.0 compiler is slow. Perhaps 30% faster with cuda 6.5.
You can tip the crypto mining blog, they have compiled a windows version before..
Ask them to build for cuda 6.5
doesn't make much of a difference actually, everything is slowed down my mem load/store. (moving to 32bit would probably help a little as well but get some problem with some dll) actually can't get my 780ti/750ti to work properly because of the high mem allocation (which actually isn't so high... but it doesn't like that) under linux ethminer allocates 1087mb on each gpu and almost 800mb on the system, i wonder if it's moving hashes between cpu and gpu's memory... 800meg is alot. Whatbis your hashrate? ~52 mhs, so ~8.7 mhs per card |
|
|
|
And the speed? Any faster?
I compiled for windows with cuda 6.5. There is a windows bug in it, my 750Ti is only at 2.2+MHs instead of the possible 9+MHs. Did you build with debug? then build release. I think the kernal need some tuning. Might work on it later. I see work has been done by tvprovut in his fork. I always build release. From what I've read on the other forum, the same code works correctly in linux. Others that run in windows get bad hashrates. Whatever the problem is, is beyond my understanding. My system: Win10, Nvidia driver 355.60, CUDA 6.5 windows 10 is the problem, it sends the missing hashes to microsoft's pool  |
|
|
|
There is no projectfile for visual studio 2013. and the cuda 7.0 compiler is slow. Perhaps 30% faster with cuda 6.5.
You can tip the crypto mining blog, they have compiled a windows version before..
Ask them to build for cuda 6.5
doesn't make much of a difference actually, everything is slowed down my mem load/store. (moving to 32bit would probably help a little as well but get some problem with some dll) actually can't get my 780ti/750ti to work properly because of the high mem allocation (which actually isn't so high... but it doesn't like that) under linux ethminer allocates 1087mb on each gpu and almost 800mb on the system, i wonder if it's moving hashes between cpu and gpu's memory... |
|
|
|
|
Show Posts
