well, I just did a little google fu on it and if I do try it I would probably go with a razorknife to score both sides and then crack it apart. Seems like the lowest impact option to me. I might want to mine until it breaks even before I try though  Better yet, just buy K16s, if that's what you want  Leave your K64s intact. Yea, that would be smart ... I didn't see past the part where I saved a few bucks on a k64 over 4x k16s, then later realized I can fit more hashing power in a regular case with k16s  I'm sure I will figure out something though Oh, I see... So you are really looking at maybe needing to cut some apart... Lol, up 'til now I thought we were just speaking theoretically  Your method of scoring both sides and breaking the board does work, but be very careful about flexing the boards. Even if they are cut pretty deeply, it can still take a good deal of force to break the board, and SMT capacitors and resistors can crack if they get flexed much. It should be fine, just don't force it. |
|
|
|
well, I just did a little google fu on it and if I do try it I would probably go with a razorknife to score both sides and then crack it apart. Seems like the lowest impact option to me. I might want to mine until it breaks even before I try though Better yet, just buy K16s, if that's what you want Leave your K64s intact. |
|
|
|
I saw that but wondered can they really be cut without damaging the chip connections, etc? I assume one would need a dremel and some care to get it done, not sure if I would want to risk it Companies that manufacture the PCBs do this all the time. You can do it by hand, but it is a lot of work. I wouldn't recommend buying K64s and then cutting them into K16s. I suppose TH (and other board builders) could order them with break-away cuts if they wanted to, so they can easily be separated. What I meant with the dremel comment was that I am pretty sure I can't just lay the thing down on my table saw and cut away... Work I am fine with, finding out the vibrations from my work shook loose a chip or three I am not so fine with I guess I will have to look into this a bit more. I only have 1x k64 and the rest is all k16s, so if I know I can do it without breaking anything, it might be worth the effort for me. jdape - brilliant! FWIW, I've cut boards like that many a time with a band saw - but FR4 is pretty rough on the blades. I don't recommend it. |
|
|
|
Hi, why diff show 0 when scrypt mining? In cgminer show 32 or 64, depending of pool cgminer is showing Ldiff (Litecoin difficulty). BFGMiner is showing pdiff (pool difficulty). Exactly pool difficulty in BFGMiner is 0, and Ldiff is 894. in cgminer pool difficulty is 32, and Ldiff is 58.6M. Here my settings: @echo off setx GPU_MAX_ALLOC_PERCENT 100 bfgminer.exe --scrypt -o stratum+tcp://mining.eu.hypernova.pw:3333 -u user -p password -d 0,1 -I 20,19 -w 256 -v 1 -g 1 --lookup-gap 2 --thread-concurrency 21772,16192 --queue 0 -s 1, whats wrong? From the cgminer README/FAQ: Q: Why do the scrypt diffs not match with the current difficulty target?
A: The current scrypt block difficulty is expressed in terms of how many
multiples of the BTC difficulty it currently is (eg 28) whereas the shares of
"difficulty 1" are actually 65536 times smaller than the BTC ones. The diff
expressed by cgminer is as multiples of difficulty 1 shares.
It looks like BFGMiner does not do the same re-calculation that CGMiner does. |
|
|
|
I saw that but wondered can they really be cut without damaging the chip connections, etc? I assume one would need a dremel and some care to get it done, not sure if I would want to risk it Companies that manufacture the PCBs do this all the time. You can do it by hand, but it is a lot of work. I wouldn't recommend buying K64s and then cutting them into K16s. I suppose TH (and other board builders) could order them with break-away cuts if they wanted to, so they can easily be separated. |
|
|
|
anything over 2000000 and mine crashes. x64 bit launches and stops closes window.
You sure you're on the newest version (hp7)? I just tested 10mil on x64 and it worked fine. What kind of CPU are you using? I have an i7 3820, and I have been reporting this problem since at least hp4. I used to be able to go up to 4M just fine, and anything over that crashed - but with hp7, anything much over 2M crashes. |
|
|
|
Is it possible to remove threads you posted in from the watch-list/notification?
It looks like if you post in a thread, it is automatically watched.
The only thread I saw related to it was to delete all your own posts in that thread.
If you go to your watchlist, there is a link to 'Edit Watchlist'. You can unwatch threads from there. |
|
|
|
I just went from v5 to v7 and now my prime rate is halved. Anyone else having this? Is it because of the optomizations made (ie. more efficient/accurate)?
Also, I have set: -sievesize=4000000
but when I view stats with getmininginfo it always says its on 1M not 4M?
I believe that when you set sievesize from the command line, you need to leave a space between the switch and the value for it to parse correctly, i.e., "-sievesize 4000000". If you are setting it in your .conf file, then you need the '=' sign. Nope, you need to use the '=' sign without any spaces in between. That's how Primecoin (Bitcoin) command line parameters work. Some examples: primecoin-qt.exe -sievesize=2000000 primecoind.exe -sievesize=2000000 Sorry, I stand corrected. |
|
|
|
I just went from v5 to v7 and now my prime rate is halved. Anyone else having this? Is it because of the optomizations made (ie. more efficient/accurate)?
Also, I have set: -sievesize=4000000
but when I view stats with getmininginfo it always says its on 1M not 4M?
I believe that when you set sievesize from the command line, you need to leave a space between the switch and the value for it to parse correctly, i.e., "-sievesize 4000000". If you are setting it in your .conf file, then you need the '=' sign. |
|
|
|
Why is the block 202kb?
We're kind of stuck on it, transactions are adding up quickly  I could swear when I was looking at this in the debug window, it said there were 13 transactions, and the block was over 200k, but I just looked in the block explorer, and it only shows one transaction - the coinbase tx. |
|
|
|
Guys you do realise he is trying to improve FPGA efficiency, and patent the results? This is a hell of a long way from open source.
OMG he's been outed as a Capitalist! Someone kill him before he gets away! Improving on stuff and making a profit from his efforts! This cannot be endured... |
|
|
|
Read your PMs |
|
|
|
I used your version hp5. I'm running Windows 8 R2 Standard 64 bit. The processor is: Intel Xeon CPU E5-2420 @1.90 ghz My settings are: maxconnections=256 genproclimit=-1 sievesize=4000000 gen=1 My server processor shows 12 cores running and my desktop shows only 8 cores. but it's still slower than the desktop by almost half. Also my server processor cost 4x more than the the desktop processor...
Well, your server shouldn't be lagging behind by that much. Which operating system is the server running? Which version of the client are you using? Did you compile it yourself? 'genproclimit=1' will cause it to only create one thread for mining. Is that really what you want? |
|
|
|
OK, Thanks. What does "Currentblocktx" : 0 mean?
I'm gonna guess that it's the number of transactions currently associated with the block... |
|
|
|
try this
sudo pkill primecoind
I tried that too.. primecoind stop error: no response from server Then when I go back to launch or watch it... i get this error: no response from server error: no response from server EDIT: now black screen... Using HP5 Are you sure it's running in server mode? Put 'server=1' in your conf file, or start it with the '-server' switch. |
|
|
|
I feel like I am not doing the mining correctly. Am I correct to be mining from within primecoin-qt through the debug window by simply setting "setgenerate true -1"?
That's correct. You can type 'getprimespersecond' or 'getmininginfo' to make sure you are actually mining. It varies a lot, and is not a good indicator of how fast you are mining, but as long as it's higher than zero, you should be ok. |
|
|
|
How can the sieve size be altered? I can't find any list of commands fro Primcoin-qt
Also, my currentblocktx seems to always be zero and rarely 1 - same with pooledtx. What does that mean?
primecoind --daemon -seivesize=2000000 Or whatever you need for seivesize. Does not have to be 2000000 I can't get the command to work in Primecoin-qt. I've tried the above and seivesize=2000000 You are spelling 'sievesize' wrong. |
|
|
|
No offence, but this is a stupid poll.
Why do people so readily associate libertarians with Ayn Rand? I haven't read any of her works or writings and barely know anything about her. I also have no idea what objectivism is, beyond knowing that Rand coined it, nor do I care.
I simply use logic and evidence to divine the truth of things which leads me to the freedom viewpoint.
ism's of any kind don't matter at the end of the day. Critical thinking is what you need.
I basically agree with you. "ism's" always focus so sharply on single aspects of reality that they miss the true complexity of how every thing works together, and fail to provide a real view of the whole. I would, however, recommend reading the work of others, even if they are "ism's". and even if you know going in that you disagree with the author. There is a lot of value in seeing things from a different perspective, even if it is just to help you frame your own beliefs more solidly. |
|
|
|
Didn't the consensus show that 1M sievesize was some kind of sweet spot ?
Can I pass in the sieve size, or do I need to recompile? You can pass it on the command line with the '-sievesize' parameter, or you can put sievesize=<size> in your primecoin.conf. Is that the only tuning parameter I can pass in at the moment? I don't know. Maybe mikaelh will chime in and answer your question. |
|
|
|
|
Show Posts
