IMO, if Nefario also said not to buy them, he's under no obligation to honour ones bought afterward...
|
|
|
Definitely plan to implement in BFGMiner if possible.
TheSeven suggested the current code could be opened as-is including the signcryption private keys, to get things going immediately (miners could self-signcrypt), and leave removing the signcryption to later assuming it's non-trivial.
|
|
|
(...) Nefario has said the fake GLBSE shares will be removed from everyone's accounts and they will be given the IPO price (0.1 BTC). (...)
Personally, paying 0.1 is too much for them, it's like rewarding exploiters. Even after Nefario told those were fake shares, there are still individuals wanting to exploit his good-will for maximum profit. Incredible! Welcome to the wonderful world of bitcoin forums lolIts Goat we are talking about here. And Goat is a known troll.
|
|
|
Q: On linux I can see the /dev/ttyUSB* devices for my ICA/BFL/MMQ FPGA, but cgminer can't mine on them ... Then logout and back in again FYI, this is bad advice and is likely to screw up your system. Well, no. Adding your current user to the "dialout" group is not going to screw up anything. Indeed that wouldn't, but the commands Kano suggests also removes you from every other group. Including sudo. (BFGMiner has suggested almost idential but with the -a option for a few releases now) Unfortunately, when you pulled that change from my git into your git - you didn't fix it then either. Your README still says that also. You'll need the commit in my git that's been pulled into cgminer to fix it .. No, I just forgot to push when I fixed it in BFGMiner - though I'll probably overwrite it with yours before the next release.
|
|
|
Important factor: What happened to the IPO funds for the phony stock?
|
|
|
If I understand correctly GBT also supports LP, doesn't it? Did you make use of LP with getwork and GBT in your test? Yes, of course. It would really be interesting to see the stale ratio of GBT+LP vs Stratum over one week on the same pool/same connection. Unfortunately, I haven't optimized GBT in BFGMiner at all yet, so I doubt it would compare well vs Stratum proxy. It would be interesting for someone to make a quick port of the Stratum proxy to GBT (python-bitcoinrpc + python-blkmaker should do it very easily) to compare with. Of course, you'd also need a biprotocol pool, which AFAIK doesn't exist yet.
|
|
|
Q: On linux I can see the /dev/ttyUSB* devices for my ICA/BFL/MMQ FPGA, but cgminer can't mine on them A: Make sure you have the required priviledges to access the /dev/ttyUSB* devices: sudo ls -las /dev/ttyUSB* will give output like: 0 crw-rw---- 1 root dialout 188, 0 2012-09-11 13:49 /dev/ttyUSB0 This means your account must have the group 'dialout' or root priviledges To permanently give your account the 'dialout' group: sudo usermod -G dialout `whoami` Then logout and back in again FYI, this is bad advice and is likely to screw up your system. Well, no. Adding your current user to the "dialout" group is not going to screw up anything. Indeed that wouldn't, but the commands Kano suggests also removes you from every other group. Including sudo. (BFGMiner has suggested almost idential but with the -a option for a few releases now)
|
|
|
Q: On linux I can see the /dev/ttyUSB* devices for my ICA/BFL/MMQ FPGA, but cgminer can't mine on them A: Make sure you have the required priviledges to access the /dev/ttyUSB* devices: sudo ls -las /dev/ttyUSB* will give output like: 0 crw-rw---- 1 root dialout 188, 0 2012-09-11 13:49 /dev/ttyUSB0 This means your account must have the group 'dialout' or root priviledges To permanently give your account the 'dialout' group: sudo usermod -G dialout `whoami` Then logout and back in again FYI, this is bad advice and is likely to screw up your system.
|
|
|
Luke-Jr: I'm seeing high CPU usage with BFGMiner. I use it on my system with my 6870 and 7770. I thought it was high before when I was using the IGP, but since I've turned that off, the CPU usage is still at 50%. I use Win7 64bit. Any ideas?
Can you open an issue with the full details of your setup (hardware, config, BFG version, etc)?
|
|
|
Numbers? Now that I've had BFGMiner 2.8 running for a number of days, I have some reasonably useful numbers... getwork session A: 0.83% stale getwork session B: 1.09% stale GBT session A: 0.71% stale GBT session B: 0.66% stale There's probably a good chance the GBT stales are lower only by coincidence (a lot depends on when blocks are found, after all), but I think it's pretty safe to conclude there's not any notable practical difference just from the protocol.
|
|
|
What would I need to do that on Windows? Time with me on IRC
|
|
|
It's happened as far back as 2.7.5 or 2.7.4 I believe Yeah, I was thinking more in terms of "compile 50% of the code, see if it complains"
|
|
|
Your current cgsnoop does not work with bfgminer 2.8.0. It doesn't output "Temperature" anymore via the API if none of your devices can show the temperature... thanks. in general, bamt makes no attempt to have compatibility with software/versions other than those it comes with or delivers via fixer/apt. in this case it is likely that we'll be packaging bfg 2.8.0 in the near future though, so this is good to know. Pretty sure this has been the case since 2.5.0, FWIW.
|
|
|
I don't have any development tools on Windows, so I don't know.. it's the EXE that's getting flagged for me anyway. It was linked earlier: http://luke.dashjr.org/tmp/code/pdcurses.dllBut if the EXE is getting flagged, that probably won't help Maybe some time we should "bisect" out what it's flagging and workaround it...
|
|
|
I get similar problems from Bitdefender. The CS has been less than helpful. Bitdefender is a piece of shit, BTW... don't buy it. Does the self-compiled DLL work for you?
|
|
|
Is there really STILL no coin control options in this release? This is the major feature I have been waiting for for many many months and I am so disappointed that it seems to be not here ? Please find or hire someone to update and fix the problems in it, so that it might be merged in the future. Maybe start a bounty? Today's next-test still has Coin Control barely merged in, but this will probably be the last time due to rapid bitrot.
|
|
|
next-test is a branch of the master bitcoind & Bitcoin-Qt code with as many pull requests merged as possible, to aid in testing them. This branch can be used to test many pull requests in your daily Bitcoin use. The goal is to help pull requests get the testing they need to be merged into the main tree, so once you test a change, please comment in the relevant pull request (ideally with details). Due to Coin Control's poor design and abandonment, it has begun to bitrot rapidly. This will probably be the last next-test supporting it, unless someone steps up to maintain it. Please note these might possibly corrupt your wallet. No warranty of any kind of provided. BACKUP YOUR WALLETToday's next-test includes the following pull requests (green are merged now; red are disputed):
|
|
|
waaaait a minute. are you saying 0.7.x is an unstable / testing branch? 0.6.x is basically stable branch? 0.7.0 is a "master" branch release, but should be stable in theory. perhaps 0.7.x has "crazy, new, untested features" and isn't broken in yet? Of course it has new features. The only one I am particularly concerned about, though, is the time refactoring I did. It did get plenty of testing, but gmaxwell found some bugs in it last-minute that were not fixed in the final. immediately, what comes to mind is odd-numbered branches of linux are "development / test" versions and not considered stable. (I'm remembering when I was on linux 2.4.x upgrading to 2.6.x years back) Bitcoin does not use such a system. more simply, my only ACTUAL question:
So uhm, is 0.6.x effectively "long term support" version? Likely whatever version Debian ends up shipping will be "LTS". Other than that, it all depends on which backports people still need - hence the polls Note that unless 0.6.0.x is still needed, I plan to discontinue it as soon as Eligius has upgraded to 0.7.0 - so if anyone needs that, speak up ASAP.
|
|
|
Does bfgminer require root account to run Ztex boards?
No, but you might need to check your user's permissions. The devices are under /dev/bus/usb/*/*
|
|
|
|