well the pump was backed by 100k coins at each satoshi increment, obvious it cant sustain for long  |
|
|
|
Hi, when i try to 'make' bfgminer i get this: bfgminer-deviceapi.o: In function `add_cgpu':
/home/user1/bfgminer/deviceapi.c:621: undefined reference to `detectone_meta_info'
/home/user1/bfgminer/deviceapi.c:622: undefined reference to `detectone_meta_info'
/home/user1/bfgminer/deviceapi.c:623: undefined reference to `detectone_meta_info'
/home/user1/bfgminer/deviceapi.c:622: undefined reference to `detectone_meta_info'
bfgminer-driver-cpu.o: In function `cpu_detect':
/home/user1/bfgminer/driver-cpu.c:789: undefined reference to `_serial_detect'
/home/user1/bfgminer/driver-cpu.c:787: undefined reference to `_serial_detect'
collect2: ld returned 1 exit status
make[2]: *** [bfgminer] Error 1
make[2]: Leaving directory `/home/user1/bfgminer'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/user1/bfgminer'
make: *** [all] Error 2
any help on that? dont deactivate GPU/others, its a bug |
|
|
|
Please check that you're using the latest SDK. I also encountered memory problems with cuda 5.0 and I'm using 5.5 now which works for me.
ACK, will do later and report back  |
|
|
|
self signed as the CAs cant be trusted, their keys can be stolen, inside jobs, etc. but the self signed cert should be signed with the guys known GPG key to validate it  therefore not even the CAs can break it  EDIT: this might also be of interest for u: http://convergence.io/ |
|
|
|
My 2 cents: mining entirely on GPU wont be easy and is impractical, but tandem mining with interleaved CPU+GPU computations may very well give good speed ups.
Some feedback from knowledgeable people indicates that mod_exp probably would not speed up as well on gpu. However I think if gpu can do the sieve much more efficiently it could generate a lot less candidates for the Fermat test, which could speed things up quite a bit. There is indeed a problem with the speeds of Fermat tests on the GPU. GNU GMP uses the most sophisticated algorithms available, the student library I found and which I started to extend uses the most basic algorithms. Mpz_powmod needs fast multiplications of big ints, GMP's algorithm is most likely in O(log(n)*n), school book multiplication which the GPU now uses is O(n^2). I hoped that for the ~400 bit numbers involved it wouldn't make such a difference. Currently, the new version in my repo does Fermat tests on the GPU (rate is 10 per second), but my CPU is still faster due to better algorithms and a better big num implementation. But don't worry, I won't give up so fast! The current situation is that I either need to look into porting better algorithms to the GPU or to do something else than Fermat tests on the GPU to sieve candidates (e.g. trial division with most common primes). Anybody with a better GPU than the Geforce 570 TI I own, please test this! My stats (base version is still hp4): 2013-07-24 21:53:38 primemeter 24303 prime/h 490729 test/h 47 5-chains/h prime/h and test/h seem to fluctuate enormously and seem to be rather meaningless. As most tests are on the GPU, I have no idea if this is even measuring the tests right. 5-chains is accurate though. You have to use setgenerate true 1, i.e. one CPU thread for mining. running current git (b0c7062f3925482935f5eb352b17737d21b95c5b) and i cant see any usage of my GPU, no heat nor used mem increases when using the QT. anything special to activate so it mines with the GPU? i got a powerfull GPU to test with EDIT: 2013-07-25 13:35:43 primemeter 0 prime/h 34261932 test/h 0 5-chains/h seems the miner thread which should launch the CUDA is borked? EDIT2: Have 2400 candidates after main loop
Cuda start!
Cuda error: cudaMemcpy: cudaMemcpyDeviceToHost, the launch timed out and was terminated from debug log You can also run it with -printmining -printtoconsole to see that output directly. Could you compile the cuda portion with -G -g (change the qt project file where it invokes nvcc) and give me the output of cuda-memcheck? You can also #define CUDA_DEBUG in the cu file, to see the GPU printfs from the console was already running with -g just waiting for the "cuda start message", stoped it now and recompile with -D CUDA_DEBUG EDIT: its up and running, waiting for the cuda init + crash EDIT2: why does it take so long until the miner starts the cuda thread? that seems stupid :S EDIT3: here we go, it crashed debug.log Have 2400 candidates after main loop
Cuda start!
Cuda error: cudaMemcpy: cudaMemcpyDeviceToHost, unspecified launch failure stdout [0] start!
sizeof(struct) = 400
mpz_print:mpz_capacity: 0
[0] string candidate is
[0] N is: mpz_capacity: 30 ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
[0] E is: mpz_capacity: 30 fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffe
gdb: dont want to spam, sending per PM and message too big -.- |
|
|
|
My 2 cents: mining entirely on GPU wont be easy and is impractical, but tandem mining with interleaved CPU+GPU computations may very well give good speed ups.
Some feedback from knowledgeable people indicates that mod_exp probably would not speed up as well on gpu. However I think if gpu can do the sieve much more efficiently it could generate a lot less candidates for the Fermat test, which could speed things up quite a bit. There is indeed a problem with the speeds of Fermat tests on the GPU. GNU GMP uses the most sophisticated algorithms available, the student library I found and which I started to extend uses the most basic algorithms. Mpz_powmod needs fast multiplications of big ints, GMP's algorithm is most likely in O(log(n)*n), school book multiplication which the GPU now uses is O(n^2). I hoped that for the ~400 bit numbers involved it wouldn't make such a difference. Currently, the new version in my repo does Fermat tests on the GPU (rate is 10 per second), but my CPU is still faster due to better algorithms and a better big num implementation. But don't worry, I won't give up so fast! The current situation is that I either need to look into porting better algorithms to the GPU or to do something else than Fermat tests on the GPU to sieve candidates (e.g. trial division with most common primes). Anybody with a better GPU than the Geforce 570 TI I own, please test this! My stats (base version is still hp4): 2013-07-24 21:53:38 primemeter 24303 prime/h 490729 test/h 47 5-chains/h prime/h and test/h seem to fluctuate enormously and seem to be rather meaningless. As most tests are on the GPU, I have no idea if this is even measuring the tests right. 5-chains is accurate though. You have to use setgenerate true 1, i.e. one CPU thread for mining. running current git (b0c7062f3925482935f5eb352b17737d21b95c5b) and i cant see any usage of my GPU, no heat nor used mem increases when using the QT. anything special to activate so it mines with the GPU? i got a powerfull GPU to test with EDIT: 2013-07-25 13:35:43 primemeter 0 prime/h 34261932 test/h 0 5-chains/h seems the miner thread which should launch the CUDA is borked? EDIT2: Have 2400 candidates after main loop
Cuda start!
Cuda error: cudaMemcpy: cudaMemcpyDeviceToHost, the launch timed out and was terminated from debug.log after the message it segfaults, going to debug with gdb |
|
|
|
Got this alert when visiting vircurex today.
Warning: Something's Not Right Here!
vircurex.com contains content from coinurl.com, a site known to distribute malware. Your computer might catch a virus if you visit this site.
Google has found malicious software may be installed onto your computer if you proceed. If you've visited this site in the past or you trust this site, it's possible that it has just recently been compromised by a hacker. You should not proceed, and perhaps try again tomorrow or go somewhere else.
We have already notified coinurl.com that we found malware on the site. For more about the problems found on coinurl.com, visit the Google Safe Browsing diagnostic page.
Go back
If you understand that visiting this site may harm your computer, proceed anyway.
thats bullshit, turn of those google notifications, almost all are false positives... |
|
|
|
Does this mean that people with hp7 that find blocks are effectively at difficulty 10?
That would certainly explain my long dryspell...
yes |
|
|
|
|
did this offer "die"?
have you actually send anything?
|
|
|
|
Sorry guys!
got some trojan/virus thing that has pretty much destroyed my computer (using a friends) - I'll keep you updated on the recovery and plan to continue with iTrader once I've fixed my computer!
this just shows nobody can trust your code as you dont know anything about security... well was obvious since its winblows only |
|
|
|
thanks genjix, this will save alot time in the future |
|
|
|
this auction is pretty much done, those NMC are only worth 0.603394649 as per exchanges  |
|
|
|
current git is hp6? oh well, in this case im already on hp6 since some time, ty |
|
|
|
In case you're wondering... here's the code to update to HP6 UPDATE TO HP6primecoind stop wget -O primecoin-0.1.1-hp6.tar.bz2 " http://sourceforge.net/projects/primecoin-hp/files/0.1.1-hp6/primecoin-0.1.1-hp6.tar.bz2" tar -xvjf primecoin-0.1.1-hp6.tar.bz2 rm -rf ~/primecoin mv primecoin-0.1.1-hp6 primecoin cd ~/primecoin/src make -f makefile.unix USE_UPNP=- sudo rm -rf /usr/local/bin/primecoind sudo mv primecoind /usr/local/bin/. primecoind --daemon watch -n 5 'primecoind getmininginfo & primecoind listaccounts' not yet on git |
|
|
|
ive done the same with my RPi and odroid-x2 jff RPi: scrypt - 0.44 khash/s sha256d - 258.40 khash/s odroid-x2: scrypt - 6.71 khash/s sha256d - 4219 khash/s |
|
|
|
I see you had used old version 0.29.
The latest is 0.66 with many bugs fixed
Wow that's true, anyway i downloaded from here: http://darkgamex.ch/ufasoft/teorically the last one i downloaded is marked as 0.32. Any more compiled Linux version? Oh yeah by the way, I CAN use it ^^ just i've to execute the binary file, not the SH... but I only can mine with SHA256, not with Scrypt algorithm... so Litecoins and another cryptocurencys i'm not able to mine it i stoped creating new builds as compiling failed and ufasoft didnt answer, il look at it now again EDIT: nope, still cant compile ~/ufasoft_coin-0.66$ make
g++ -DHAVE_CONFIG_H -I. -I coin/inc -I coin/miner -pthread -Wno-invalid-offsetof -g -O2 -std=c++0x -c el/ext.h
el/ext.h:12:9: warning: #pragma once in main file [enabled by default]
In file included from ./el/libext/ext-cpp.h:1102:0,
from ./el/libext.h:1433,
from el/ext.h:18:
./el/libext/ext-fw.h: In member function 'int Ext::MemoryMappedFile::GetHandle()':
./el/libext/ext-fw.h:526:60: error: cast from 'Ext::HANDLE {aka void*}' to 'int' loses precision [-fpermissive]
make: *** [el/ext.h.gch] Error 1
~/ufasoft_coin-0.66$ make
make all-am
make[1]: Entering directory `/home/k1773r/ufasoft_coin-0.66'
CXX coin/miner/bitcoin-miner.o
CXX coin/miner/bitcoin-sha256.o
CXX coin/util/util.o
CXX coin/miner/miner.o
CXX coin/miner/stratum-client.o
CXX coin/miner/serial-device.o
CXX coin/miner/miner-bitforce.o
CXX coin/miner/miner-fpga-modminer.o
g++ -DHAVE_CONFIG_H -I. -I coin/inc -I coin/miner -pthread -Wno-invalid-offsetof -g -O2 -std=c++0x -c -msse2 -o coin/miner/bitcoin-sha256-x86x64.o coin/miner/bitcoin-sha256-x86x64.cpp
CXX coin/miner/miner-opencl.o
In file included from coin/miner/miner-opencl.cpp:11:0:
./el/comp/ext-opencl.h:19:3: error: #error OpenCL 1.2 or later version is required
coin/miner/miner-opencl.cpp: In constructor 'Coin::OpenclMiner::OpenclMiner(Coin::BitcoinMiner&, const Ext::Cl::Device&, const Ext::ConstBuf&)':
coin/miner/miner-opencl.cpp:176:8: error: 'CL_CONTEXT_OFFLINE_DEVICES_AMD' was not declared in this scope
make[1]: *** [coin/miner/miner-opencl.o] Error 1
make[1]: Leaving directory `/home/k1773r/ufasoft_coin-0.66'
make: *** [all] Error 2 |
|
|
|
Oh, this is such a shame. KLLRwhatever, you said you'd fix it 2 months ago, and then "forgot" about it? And now you want to damage the project further by keeping the false advertising? Sad, so sad. FinShaggys false advertising will live on, with support from the devcoiners themselves.
i edited, cant you read? |
|
|
|
@hotcoldcoin: as i promised, i changed it Only partially correct. You promised to change it, then did nothing. Then 2 months later I had to come back and start screaming at people to notice this again, and THEN you changed it. Devcoin supporters, you are a big disappointment. im no devcoin wiki admin/similiar, as i didnt see this thread popping up again @ watchlist again, i forgot about it if i wouldnt have done it, probably nobody would have done it. i wonder if i should reverse the edit just because of you being mad at me for not doing something which isnt my job at all! EDIT: wiki is slow, its still "saving it", just wait EDIT2: this is what i changed it to: Devcoin has been around for over a year, and at one point was even worth $10 per coin. (The $10 Was a trading mistake and shouldnt be taken seriously, ie too few/many zeros while buying/selling) |
|
|
|
@hotcoldcoin: as i promised, i changed it @markm: lol @ thousands of words |
|
|
|
nvcc fatal : Value 'compute_35' is not defined for option 'gpu-architecture' you need CUDA 5 for that |
|
|
|
|
Show Posts
