Hey Thanks CK... I'll see about updating my Ubuntu tomorrow and see if I have any joy there.
Do you think the firmware will resolve the machine with the LIBSUB error?
Doubt it. From what I've seen of the devices out there, some have unfixable problems and need to be RMAd. |
|
|
|
Losing the will to live here. Having gone through the ballache of installing Ubuntu in order to update the firmware, in trying to update all I get back is this Reading serial number from module.
x86_64/readserial: symbol lookup error: x86_64/readserial: undefined symbol: libusb_strerror
Same response for a machine that works and the machine that has the LIBUSB error. So now what? Looks like you're on an older ubuntu. For whatever reason, hashfast's loader is not that portable and looks like it needs a recent ubuntu, probably 13.10 |
|
|
|
Still got one sick board that won't work. Anyone have any ideas on this... RMA its arse. |
|
|
|
|
Please update cgminer, those versions are all absolutely ancient. The current version is 4.1.0
|
|
|
|
|
That's what might happen if you used an ancient version of cgminer that did not actually support these devices. Upgrade to the latest (which is 4.1.0)
|
|
|
|
4.1.0 + FW 0.3 is the most stable for me -- since running both my miners with these there have been zero shutdowns. 4.1.0 also seems to produce less HW errors.
If I upgrade to FW 0.4, cgminer 4.1.0 shuts down cores for being bad ("squelching"), which seems to result in me losing hashrate.
I guess you can try the --hfa-noshed option with 0.4. It doesn't entirely disable the squelching but may leave more intact. I think they're false positives in that firmware to be honest. |
|
|
|
EDIT: Fixed in git, along with an opportunity for a further optimisation.
Any optimizations to help Block Erupters? Still not quite stable for me, 4.x that is. Oh dear, if they're not good by now, they never will be  4.0.x had regressions but there should be no reason 4.1 is any less stable with erupters than any of the best 3.x versions. |
|
|
|
|
Any difference you see in HW% with the latest firmware is almost certainly sheer coincidence.
|
|
|
|
Hello Con, I might be wrong but i found a possible memleak in void roll_work(struct work *work)... More info if (work->ntime) work->ntime = offset_ntime(work->ntime, 1); should be something like if (work->ntime) { char *memleak = work->ntime; work->ntime = offset_ntime(work->ntime, 1); free(memleak); } as long as offset_ntime returns new pointer and old work->ntime pointer is lost and never freed on free_work call PS: consider it as confirmed and fixed  My tplinks are a lot mare happy with the above fix. Everything is working fine and most important memory is not leaking Good catch, looks valid, thanks! EDIT: Fixed in git, along with an opportunity for a further optimisation. |
|
|
|
The new CGMiner also support the new Antminer U2?
I mean yes, only the Heatsink is new?
Try it and let us know  We don't have any U2's but I think they are the same with just a better heat sink? Ive got a few boxes of these on hand.... pretty nice.
Of the U2s? hows the software support? do they use the same software as the prior versions? Theoretically they're supposed to run identical software to the U1s which cgminer has full support for. Does anyone know how to overclock them? It seems it works different than the U1, at least I am not able to OC them yet.
If they run the same as the U1 then it would take the same cgminer parameter to overclock it, i.e. adding '--anu-freq 250' would make them run at 2GH |
|
|
|
They are not malicious files. I put them there and your virus checker or web browser is giving you a false positive. It is the ONLY official place to download cgminer so any other ones you have downloaded are more likely to be malicious. |
|
|
|
Hi all, I have a Bitmain Antminer U1 USB miner (1.6 GH/s) which seems to be dead. When I start cgminer, it doesn't seem to find any USB device attached. Here's the output: cgminer version 3.8.5 - Started: [2014-03-08 15:57:01]
[2014-03-08 15:57:38] Bmsc send golden nonce
Does Bitmain have any kind of warranty, repair, or replacement? I have another (separate) Antminer U1 and it seems to be working great. Try the official version of cgminer instead of this unofficial fork just to be sure. |
|
|
|
|
That is one ancient version of cgminer. Upgrade and check the ASIC-README file included in the zip.
|
|
|
|
Are you going to review their miner at the end? Or you will wait until legal issues are resolved. I saw your pictures but that was all, I am interested to see your review though
I'm waiting for someone here to sort out the power supply issues for me and I'll probably get it mining tomorrow, followed by a brief review. There are no legal issues affecting me, nor have I signed any agreement (In fact I refuse to be involved in any projects that require me to sign an NDA). |
|
|
|
Put the discussion on hold for the time being. I'm asking bitmine directly for I certainly do not want to be put in the middle of such controversy. I can easily see a number of possibilities for how it has ended in this stalemate, and it is not clear to me that there is incontrovertible evidence saying that JT produced these illegally, nor that any stealing was involved. A statement from bitmine is the only thing that can clear this up one way or another. If bitmine do not respond then I have to assume Innosilicon do indeed have the right to produce exact copies and sell these chips.
I've had official confirmation from bitmine directly that, while they do have ongoing dispute with a Chinese company, that I am free to develop for this device without fear of legal recourse provided the driver does not use the bitmine or coincraft name to reference any aspect of these devices or drivers. They have also said they will only release an official statement once the issue has been resolved. While this more or less confirms my own suspicions with respect to what's going on, I don't feel the need to speculate further on the matter and will return to concentrate purely on the software matters irrespective of what other people have to say on the issue. |
|
|
|
Hello, someone can build the latest openwrt trunk with the lastest cgminer? (4.1.0)
Here you go, and given the bugfixes that went into 4.1.0, this might be one of the best firmwares ever, though it's completely untested. http://ck.kolivas.org/apps/cgminer/avalon/20140309/ |
|
|
|
VS3 i like your design and cant wait for NF2
I`m ordered 32 chips so have some to playing with it:D
How cgminer or bgminer detect NF1/NF2 ?
are you planning build more powerfull miner with more chips?
Hello bfgminer will detect both. cgminer as far as I know doesn't detect the NF2 (it detects only first chip so it will essentially behave as a NF1). I am also working on a USB miner with more chips but that's a bit questionable design as you'll somehow need to provide 5V at 2-3A to the device (which a standard USB port can't do). So, we'll see where that ends. There is a different bitfury USB stick that cgminer supports with 2 chips. It would be trivial to add support for the 2nd chip to the existing NF1 driver as well, but as always would need testing on real hardware. |
|
|
|
Quick question about compiling cgminer, please. I tweak a few of the constants in the Klondike driver for use with my devices, and I recompile every couple of days, trying different things. Since I'm using an RPi, compiling takes about 30-45 minutes total. Right now, I use a small shell script with the following lines, based on a combination of advice from Kano's blog post and a troubleshooting guide I use for Klondikes: cd ~/cgminer
git pull
CFLAGS="-g -W -Wall" ./autogen.sh
./configure --enable-icarus --enable-klondike
make clean
make Obviously, this takes a while to run. How much of this has to be rerun every time I tweak the code, and how much of it only needs to be run once? Thanks. autogen is only rarely required with a significant git update so you can skip that and do CFLAGS="-g -W -Wall -O2" ./configure --enable-icarus --enable-klondike I note you're not adding any optimisation flags like O2 but you probably should unless you're debugging a real issue. |
|
|
|
More importantly...
when did the word "sell" get replaced by the word "sale"? I see it all of the time on bitcointalk and other places. Sale is a noun and sell is a verb. "I'm going sale my old ASICs" should read "I'm going to sell my old ASICs". Right? Or did this suddenly change?
You're... noticing the bad English on this forum now? I don't think I've ever been on a forum with worse spelling and grammar, so I just ignore it since I have no choice (even though that's usually the sort of thing that makes me cringe). There their they're your you're yaw yore "alot"... all the abuse you can imagine and more.. But at least it gives me an excuse to post this again: http://hyperboleandahalf.blogspot.com/2010/04/alot-is-better-than-you-at-everything.html |
|
|
|
|
Show Posts
