DRILLBIT SYSTEM Miners - Avalon range available - Now $104.99!

[jedimstr]

I have seen at least half a dozen reports of people with these USB disconnects on the 8 boards.  Anyone closer to a solution? (no it's not the cable or hub)

Seriously... it's been discussed to death in the Drillbit forums.  They know about it... it looks like some USB transfer issues that were supposedly fixed in CGMiner 3.8.1, but seem to have cropped back up in 3.8.4.  There's even C code snippets on some of the threads pointing out where the problem should be.  You'll get a better idea about it talking directly to the engineers and developers for Drillbit over there than you will in the generic Group Buy thread here.

[bobsag3]

US people: Labels have been sent off to TK, so the first set of boards should be on their way back today/tomorrow.

[erk]

I have seen at least half a dozen reports of people with these USB disconnects on the 8 boards.  Anyone closer to a solution? (no it's not the cable or hub)

Seriously... it's been discussed to death in the Drillbit forums.  They know about it... it looks like some USB transfer issues that were supposedly fixed in CGMiner 3.8.1, but seem to have cropped back up in 3.8.4.  There's even C code snippets on some of the threads pointing out where the problem should be.  You'll get a better idea about it talking directly to the engineers and developers for Drillbit over there than you will in the generic Group Buy thread here.

The people who bought from this thread have a right to know there are issues and the answers. I am not talking about some configuration issue, but a bug in the product which many users have reported. It's not my fault that the thread was in group buys and not custom hardware. I fail to see why something important has to be buried in the corner of a tiny product specific forum. I can't see any thread about the USB timeout problem over there, so I guess the issue is buried in some other thread.

How about a simple link to the discussion/solution to the problem?

[lajz99]

I have seen at least half a dozen reports of people with these USB disconnects on the 8 boards.  Anyone closer to a solution? (no it's not the cable or hub)

Seriously... it's been discussed to death in the Drillbit forums.  They know about it... it looks like some USB transfer issues that were supposedly fixed in CGMiner 3.8.1, but seem to have cropped back up in 3.8.4.  There's even C code snippets on some of the threads pointing out where the problem should be.  You'll get a better idea about it talking directly to the engineers and developers for Drillbit over there than you will in the generic Group Buy thread here.

The people who bought from this thread have a right to know there are issues and the answers. I am not talking about some configuration issue, but a bug in the product which many users have reported. It's not my fault that the thread was in group buys and not custom hardware. I fail to see why something important has to be buried in the corner of a tiny product specific forum. I can't see any thread about the USB timeout problem over there, so I guess the issue is buried in some other thread.

It has been stated many, many times that specifics will be discussed on the drillbit forum.  Yes, it is in a thread over there.  Of course you're free to post here, but don't expect an answer.

[erk]

It has been stated many, many times that specifics will be discussed on the drillbit forum.  Yes, it is in a thread over there.  Of course you're free to post here, but don't expect an answer.

Stuff that, I WANT people who bought the 8 board from this thread to know there is a USB problem, and to have access to the solution. It's common courtesy.

[tk1337]

It has been stated many, many times that specifics will be discussed on the drillbit forum.  Yes, it is in a thread over there.  Of course you're free to post here, but don't expect an answer.

Stuff you, I WANT people who bought the 8 board from this thread to know there is a USB problem, and to have access to the solution. It's common courtesy.

If you're referring to the libusb error; That's more of an issue with CGMiner, not the actual product, though there might be some firmware updates that could change the timing.

However, I can honestly say I've been running 6 boards for far over 72hrs added 2 boards to that setup 24hrs ago and not a single error, also, on a raspberryPi running MinePeon. However I did do somethings to achieve this, probably the major thing I did was change my difficulty at my pool as well as my queue on the miner software.

I figured the queue to be 4 per 20GH/s (so, 32 @ 8 boards) and I upped the difficulty to 64 at the pool. Since the difficulty is higher, the boards aren't vomiting information as fast (almost just as fast, but not as fast), therefore it allows for some small amount of breathing room between USB communications, where as it would normally just be flooding the miner software with messages.

Why did I do these things? Well, being completely honest, I hoped on my rPi for my Blue Fury miners and forgot the one thing I loved about BFGMiner versus CGMiner, it dynamically set the queue size and a few other variables, where as CGMiner, doesn't. So, I saw the setting for my 30GH/s on my Blue Fury devices and then calculated what I needed to set it to in CGMiner and did so accordingly; Likewise I accidentally forgot to turn off the MinePeon donations, so I saw my hash rate drop at the pool (ghash.io notifies me every 15min if there's a drop) and forgot that some pools dynamically set the difficulty, which BTCGuild does and it set it to 64, so I copied that setting.

Since doing all of the above, I haven't ran into a single LIBUSB error for over 3 days now...
(Yes, I did get them before doing that, about once every 7 hours on the rPi's and about every 15hrs on Windows7.)

Now, with that being said, stating that the product is faulty here, I'd declare that to be false; Maybe more so of people not knowing how to configure settings correctly, that may very well, be true. I'll let you all be the judge of that, but I've been mining on my rPi solid now. I think it's wise to factor in all the variables before making out right accusations that a product is faulty, especially when in mining, there are *a lot* of settings and configurations that most people aren't even aware of how to use. Are there improvements that can be made in the firmware to help this issue (maybe avoid it completely)? Probably, yes, of which Angus and the Drillbit team have stated they are looking into.

So, yea... 

[tk1337]

And by the way... Blue/Red Fury devices, flooded CGMiner 3.8.0 and 3.8.1 with "LIBUSB" errors until the day after 3.8.1 was released, ckolivas updated the repository with code that pulled back on the timing to make it "not as trigger happy". However since I got all those errors on CGMiner, I just said fuck it and stuck with BFGMiner for those devices, as it worked perfectly fine.


**cough, cough, I wish Luke-Jr or someone would add-in support for Drillbit devices on BFGMiner.. **

[erk]

And by the way... Blue/Red Fury devices, flooded CGMiner 3.8.0 and 3.8.1 with "LIBUSB" errors until the day after 3.8.1 was released, ckolivas updated the repository with code that pulled back on the timing to make it "not as trigger happy". However since I got all those errors on CGMiner, I just said fuck it and stuck with BFGMiner for those devices, as it worked perfectly fine.


**cough, cough, I wish Luke-Jr or someone would add-in support for Drillbit devices on BFGMiner.. **

Interesting, I have several Block Erupters and BFL devices with no LIBUSB errors, I was not aware that Drillbit was part of cgminer distribution, I thought it was it's own fork so I didn't try the drillbit version to see if the other gear gave problems.


 

[tk1337]

And by the way... Blue/Red Fury devices, flooded CGMiner 3.8.0 and 3.8.1 with "LIBUSB" errors until the day after 3.8.1 was released, ckolivas updated the repository with code that pulled back on the timing to make it "not as trigger happy". However since I got all those errors on CGMiner, I just said fuck it and stuck with BFGMiner for those devices, as it worked perfectly fine.
**cough, cough, I wish Luke-Jr or someone would add-in support for Drillbit devices on BFGMiner.. **

Interesting, I have several Block Erupters and BFL devices with no LIBUSB errors, I was not aware that Drillbit was part of cgminer distribution, I thought it was it's own fork so I didn't try the drillbit version to see if the other gear gave problems.

I have never seen the issue on BFL, I have seen the issue on Erupters when I got up to 122 erupters on one rPi, which caused me to switch to BFGMiner (CGMiner wasn't very stable after 30 erupters anyhow). I didn't see the issues on Blue/Red Fury devices until CGMiner 3.8.0/3.8.1; If you want to browse through the hell that is the CGMiner thread here on the forums, you will find other people with LIBUSB errors on other random hardware.

[erk]

I have never seen the issue on BFL, I have seen the issue on Erupters when I got up to 122 erupters on one rPi, which caused me to switch to BFGMiner (CGMiner wasn't very stable after 30 erupters anyhow). I didn't see the issues on Blue/Red Fury devices until CGMiner 3.8.0/3.8.1; If you want to browse through the hell that is the CGMiner thread here on the forums, you will find other people with LIBUSB errors on other random hardware.

I did have a look at the thread before, didn't see all that much. I see in last weeks release 3.8.5 they have added - Attempt a libusb reset device on usb devices that have stopped responding.  Which of course is attempting to correct a symptom rather than the problem which caused the device to stop responding.

[tk1337]

I have never seen the issue on BFL, I have seen the issue on Erupters when I got up to 122 erupters on one rPi, which caused me to switch to BFGMiner (CGMiner wasn't very stable after 30 erupters anyhow). I didn't see the issues on Blue/Red Fury devices until CGMiner 3.8.0/3.8.1; If you want to browse through the hell that is the CGMiner thread here on the forums, you will find other people with LIBUSB errors on other random hardware.

I did have a look at the thread before, didn't see all that much. I see in last weeks release 3.8.5 they have added - Attempt a libusb reset device on usb devices that have stopped responding.  Which of course is attempting to correct a symptom rather than the problem which caused the device to stop responding.

When I say go back through the thread, I mean like back to 3.1.1, lol, the biggest issue with CGMiner (from what I can tell and in my own personal experiences) is how it interacts with USB devices. Hot-plugging is great to have however, not always the best, I think the want to always have hot-plugging while using libsub is CGMiner's biggest down fall... which you don't really have with BFGMiner, as it doesn't support hot-plugging...

[jedimstr]

That said... any word yet from Luke-Jr on BFGMiner support?  Did he get his test board/thumb yet?

[tk1337]

That said... any word yet from Luke-Jr on BFGMiner support?  Did he get his test board/thumb yet?

No idea, I haven't tried PM'ing him or asking on the BFG thread again. I may try to implement it myself after I take a breather from all the repairs & everyone has their boards back and hashing.

[JBT]

barntech/bobsag is sent you guys a pm and email. i know you guys are busy but can you answer me please?

[Unacceptable]

"Please lukejr,your our only hope" LMAO 

I only got the error once in 4 days of mining,so I'll let you guys know if it happens again.I just rebooted my host PC & all is well.............for now 

[erk]

I have never seen the issue on BFL, I have seen the issue on Erupters when I got up to 122 erupters on one rPi, which caused me to switch to BFGMiner (CGMiner wasn't very stable after 30 erupters anyhow). I didn't see the issues on Blue/Red Fury devices until CGMiner 3.8.0/3.8.1; If you want to browse through the hell that is the CGMiner thread here on the forums, you will find other people with LIBUSB errors on other random hardware.

I did have a look at the thread before, didn't see all that much. I see in last weeks release 3.8.5 they have added - Attempt a libusb reset device on usb devices that have stopped responding.  Which of course is attempting to correct a symptom rather than the problem which caused the device to stop responding.

When I say go back through the thread, I mean like back to 3.1.1, lol, the biggest issue with CGMiner (from what I can tell and in my own personal experiences) is how it interacts with USB devices. Hot-plugging is great to have however, not always the best, I think the want to always have hot-plugging while using libsub is CGMiner's biggest down fall... which you don't really have with BFGMiner, as it doesn't support hot-plugging...

You seem to be missing an important point. Drillbit support is not part of the standard cgminer release, I am quite sure it could have been if you sent Kano a board to develop on. Nevertheless, the Drillbit devs took it upon themselves to fork cgminer and patch it for Drillbit boards, but they didn't do it properly, there are issues with libusb disconnects, if Drillbit requires a certain version or configuration of libusb then that should have been done, it is not up to the cgminer devs, trying to deflect the blame back to them for managing problems in the Drillbit fork of the code is rather childish.

[lajz99]

You seem to be missing an important point. Drillbit support is not part of the standard cgminer release, I am quite sure it could have been if you sent Kano a board to develop on. Nevertheless, the Drillbit devs took it upon themselves to fork cgminer and patch it for Drillbit boards, but they didn't do it properly, there are issues with libusb disconnects, if Drillbit requires a certain version or configuration of libusb then that should have been done, it is not up to the cgminer devs, trying to deflect the blame back to them for managing problems in the Drillbit fork of the code is rather childish.

I think "irk" would be a more appropriate alias.   

If you were paying attention to the appropriate forum you would have seen this thread: http://drillbitsystem.com/forum/index.php?topic=235.0

[erk]

You seem to be missing an important point. Drillbit support is not part of the standard cgminer release, I am quite sure it could have been if you sent Kano a board to develop on. Nevertheless, the Drillbit devs took it upon themselves to fork cgminer and patch it for Drillbit boards, but they didn't do it properly, there are issues with libusb disconnects, if Drillbit requires a certain version or configuration of libusb then that should have been done, it is not up to the cgminer devs, trying to deflect the blame back to them for managing problems in the Drillbit fork of the code is rather childish.

I think "irk" would be a more appropriate alias.  

If you were paying attention to the appropriate forum you would have seen this thread: http://drillbitsystem.com/forum/index.php?topic=235.0

I have read the thread many times, stop trying to deflect the blame back onto the cgminer devs for code problems with a non-supported product.

If you are going to fork someone elses code for your product, then you suddenly take on responsibility for every line of that code to be right for your product. If it were me I would have made a Drillbit board available to ckolivas, Kano, Luke-jr and let them take care of making their mining software work with the hardware, a small price to pay for the work involved.

[lajz99]

You seem to be missing an important point. Drillbit support is not part of the standard cgminer release, I am quite sure it could have been if you sent Kano a board to develop on. Nevertheless, the Drillbit devs took it upon themselves to fork cgminer and patch it for Drillbit boards, but they didn't do it properly, there are issues with libusb disconnects, if Drillbit requires a certain version or configuration of libusb then that should have been done, it is not up to the cgminer devs, trying to deflect the blame back to them for managing problems in the Drillbit fork of the code is rather childish.

I think "irk" would be a more appropriate alias.   

If you were paying attention to the appropriate forum you would have seen this thread: http://drillbitsystem.com/forum/index.php?topic=235.0

I have read the thread many times, stop trying to deflect the blame back onto the cgminer devs for code problems with a non-supported product.

I'm not deflecting blame, I'm nicely trying to tell you to go use the other damn forum where you may actually get a response!!  It's really not that difficult of a concept. 

[tk1337]

I have never seen the issue on BFL, I have seen the issue on Erupters when I got up to 122 erupters on one rPi, which caused me to switch to BFGMiner (CGMiner wasn't very stable after 30 erupters anyhow). I didn't see the issues on Blue/Red Fury devices until CGMiner 3.8.0/3.8.1; If you want to browse through the hell that is the CGMiner thread here on the forums, you will find other people with LIBUSB errors on other random hardware.

I did have a look at the thread before, didn't see all that much. I see in last weeks release 3.8.5 they have added - Attempt a libusb reset device on usb devices that have stopped responding.  Which of course is attempting to correct a symptom rather than the problem which caused the device to stop responding.

When I say go back through the thread, I mean like back to 3.1.1, lol, the biggest issue with CGMiner (from what I can tell and in my own personal experiences) is how it interacts with USB devices. Hot-plugging is great to have however, not always the best, I think the want to always have hot-plugging while using libsub is CGMiner's biggest down fall... which you don't really have with BFGMiner, as it doesn't support hot-plugging...

You seem to be missing an important point. Drillbit support is not part of the standard cgminer release, I am quite sure it could have been if you sent Kano a board to develop on. Nevertheless, the Drillbit devs took it upon themselves to fork cgminer and patch it for Drillbit boards, but they didn't do it properly, there are issues with libusb disconnects, if Drillbit requires a certain version or configuration of libusb then that should have been done, it is not up to the cgminer devs, trying to deflect the blame back to them for managing problems in the Drillbit fork of the code is rather childish.

I think you seem to be missing the point, or rather avoiding it...

The issue with LIBUSB is not drillbit related in any way shape or form (hence why OTHER products which are officially supported by CGMiner have the issue as well). It's blatantly obvious that you want to keep ignoring this fact just so you have something to bitch and run your mouth about, so nothing anyone says here will help you. The issue has been around since before the Drillbit 8 Boards were manufactured, since before Drillbit developers ever wrote code, etc...

So how about you do some actual reading for once and learn what LIBUSB is... it's a library written in C for USB communications, which omfg, has bugs, not to mention the implementation CGMiner uses it in, had & has bugs with it. http://www.libusb.org/

Not_a_damn_thing_to_do_directly_with_drillbit.

Granted I understand if you're mentally incapable of understanding logic, I won't make fun of you for being mentally handicap, so if that is the case please speak up. However I'll gladly point out how much of an idiot someone is when all the facts are right in front of their face yet they choose to still ignore them. So which is it with you?