configure CFLAGS='-O3' -enable-scrypt -enable-gridseed Sudo apt-get build-essential autoconf automake libtool pkg-config libcurl4-gnutls-dev libjansson-dev uthash-dev libncursesw5-dev libudev-dev libusb-1.0-0-dev libevent-dev libmicrohttpd-dev libcurl4-openssl-dev libncurses5-dev

I was eventual able to get the GC3355 up and running on raspberrypi by doing this: Reply to this email directly or view it on GitHub. It is quite frustrating- but seems to be pretty stable once up and running. I, like you, see that lsusb and cgminer -n always list the device- but only very rarely does dualminer respond and activate while running. Then, after power on of PI, power on USB hub, connect USB and cross fingers. I don't remember what it took to get it to work- but I believe your best shot is to turn everything off (hubs, pi) and disconnect USB. I've only had to deal with this situation twice- once when I first set things up and another when I accidently cut power. Getting USB DM working on a raspberry PI (or AFAICT any linux system in general) is somewhat frustrating. On Mar 25, 2014, at 4:51 AM, John Dean wrote: Personally, I wouldn't go near the Pi - I've always felt they were garbage. That's a bit simplistic, but I suppose might be the quickest way to resolve The general consensus seems to be that if you're having USB issues, then you have a

Maybe 'SCRIPTA' will get you rolling quicker. Unfortunately, I just haven't had time to help with the code. I've actually found these versions more reliable than this branch.

If you built bfgminer with default options, then you are using udev - which might be the problem.ĭoes the device show-up in /dev? You can also try disabling udev with your build.īy default, cgminer/cpuminer custom versions use libusb/compat for connectivity. My old Shuttle 945 board, my Gigabye UEFI Hackintosh, my gBox SLAV, and my ALIX OpenWRT uberrouter. I've used the the GC3355 device on (4) different systems now with any issues with USB.

Cgminer 3.5.0 windows