Luke-Jr told me on IRC last night that since BFL offered to ship him his unit, but kindly agreed to keep it in their warehouse and send him pictures instead, that the unit still qualifies as being "shipped" to him. He wished people would stop "slandering" him by saying the unit hadn't shipped.  Disclaimer: That's not what I actually said. |
|
|
|
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). 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): |
|
|
|
Why the witch-hunt? He's decided to shut down the pool. He's planning on paying users. Side note: A mtred user on IRC was complaining that apparently they aren't paying shares found after the last block, and that he was unable to withdraw his full balance... |
|
|
|
same - crashes on bfgminer 3.0 and 2.10.6 with ztex and 6950 im on bitminter too
2.10.5 was stable
cgminer 2.11.4 is stable too
im using backup pools and i think problem is in this;)
It sounds like you might be able to reproduce the crash easily? If so, are you willing to go through a series of test builds (preferrably on IRC) to track down the cause? Thanks, Luke |
|
|
|
Turns out bitbet.us may actually be in the wrong here! My Little Single is getting 29.4 Gh/s with a firmware update. In their defense, the bet could be argued to require +/- 10% as delivered (eg, disqualifying firmware updates), but if this performance issue had merely been my software, they'd have defrauded people... you sure say some stupid things. You may have a unit, but the bet was for BFL to ship out units to customers. Which they failed to do.. This. The bet says "will deliver ASIC Bitcoin mining devices to their customers", NOT " a customer" thus implying plurality. Having one unit shipped to one customer does not logically satisfy the conditions of the bet. You're right. While it's just one character, it does make an important difference. Delivery to one customer certainly isn't "customers" no matter how accurate the rest. I take back what I said. |
|
|
|
Turns out bitbet.us may actually be in the wrong here! My Little Single is getting 29.4 Gh/s with a firmware update. In their defense, the bet could be argued to require +/- 10% as delivered (eg, disqualifying firmware updates), but if this performance issue had merely been my software, they'd have defrauded people... |
|
|
|
Turns out bitbet.us may actually be in the wrong here! My Little Single is getting 29.4 Gh/s with a firmware update. In their defense, the bet could be argued to require +/- 10% as delivered (eg, disqualifying firmware updates), but if this performance issue had merely been my software, they'd have defrauded people... |
|
|
|
Almost vanilla, I only had to do a slightly patch to permit both cgminer and bfgminer installed, using /usr/share/bfgminer for kernels instead of /usr/bin. Maybe you should do that upstream too (having .cl files in /usr/bin is against FHS hier)  Actually, this is what I'd consider completely vanilla - "make install" isn't really supported right now. I'd welcome a patch to fix this, but it's not really a high priority. For some reason, I can't seem to access the archlinux.org URI. |
|
|
|
Last 3 trolls seem to be missing the fact that the bet deadline was at the end of April 1, not the start of it.
1) do you really think these angry users are all trolls? I think they're sore losers who shouldn't be betting if they can't take responsibility for making sure the bet terms satisfy them. They should be glad it was declared a draw rather than a win for the pre-April side. 2) IMO you helped BFL manipulate a bet, which is shameful & dishonest. All I did was accept a device I paid for. |
|
|
|
ASICs CAN NOT mine namecoins because it is almost required that ASIC must mine with stratum, because they solve shares too fast. Namecoin can not be mined with stratum. Don't know where you got that idea. ASICs work great with GBT, and Namecoin can very well be mined with stratum (Eligius did so for a while before removing Namecoin simply because it's a dead system). |
|
|
|
April 9th and no one else has "received" a BFL ASIC???
Luke, what are we to think? As far as I'm aware, BFL is waiting until a hardware revision is done to improve power usage before delivering any more. I want the rest of my order just as much as anyone else  |
|
|
|
Running on Windows on a Toshiba laptop with an ATI Radeon HD 6520G.
Can't get either version (stable or 3.0) to work, period. Starts and hangs immediately after I put in the URL/username/password for the pool. Tried 4-5 times with 3 different pools. No dice.
Normal hash rates for this laptop using cgminer are in the 30 MHash/s range (yes, slow, I know, but it's what I've got). Am looking at getting an ASIC, but haven't committed yet. Would love some software which works for the ASIC that I can just switch settings for.
Is there a super-verbose logging mode that might help, that I could PM you the results, to kinda see if the problem surfaces?
-D -T Next time check README... |
|
|
|
cgminer supports Cairnsmore1 HashVoodoo dynamic frequency changing?
No, if you want good FPGA support you need BFGMiner. Good - as in - delay the BFL release by almost a week. Good - as in - brick Avalon ASICs Good - as in - his new "Luke-Jr is God" thread shows a REALLY large number of commits to attempt and fail to get Avalon working on his BrickMiner Sounds good to me  Meanwhile - checkout cgminer - support for Avalon (working fine but not in release yet) completed by the originator of more code in cgminer than anyone else - ckolivas  Though there is one thing good about the BrickMiner - all the code he copies from cgminer every release ... just a pity what he does with it ... ... ... the youtube video is gross, don't watch it But no, we rarely copy any of the abortion he creates, back We know to avoid his ineptitude. You wish, liar. |
|
|
|
|
I don't think anyone is the least bit inclined to reward squatters.
You should be ashamed of yourself.
|
|
|
|
|
I'd suggest perhaps making it GBT/Stratum only on the main node, and offering a private getwork port to miners on request.
Only potential problem is, most likely miners using getwork are also the ones who don't pay any attention :|
|
|
|
|
Too bad you have no clue what you're talking about, eh? |
|
|
|
USB does, yes. But not the devices in question.
If that's the case, then I suppose I see no real benefit to using libusb either. cgminer already implements functionality that uses the advantages of libusb ... ... Another is the usb API stats
All devices have statistics recorded about all I/O to them, including the initial control transfers that the serial-USB code doesn't even know about Yes, this is made possible using libusb. Too bad it's completely useless.Just thought I'd point out this little gem of utter stupidity by the retard Luke-Jr So he's been hashing away on a BFL SC for how many days now? Edit: 6 or 7 days! And ... the latest problem has been a supposed 500ms latency issue with I/O Pity they chose the crappy miner code to test all this on - coz cgminer (my USB statistics) already reports all this through the API on a per command level. Min, Max, Total, Count ... (average = Total/Count of course) So I guess they would have known about this how many days ago if they were testing with cgminer instead of the 30 year old crap code used in the crap clone? Too bad you have no clue what you're talking about, eh? |
|
|
|
|
Show Posts
