search

dtbartle / cgminer-gc3355

CGMiner 3.72 with GridSeed GC3355 support
GNU General Public License v3.0
29 stars 56 forks source link

gridseed detect (4:4) failed to initialise (incorrect device?) #4

Open l0c0luke opened 10 years ago

l0c0luke commented 10 years ago

(Thanks for the OSX fix!)

When I startup cgminer, I get the message above. I am trying to start it with

./cgminer -o stratum+tcp://doge.us.1coinpool.com:3334 -u xxxxx -p xxxxx --scrypt

dtbartle commented 10 years ago

Does it work if you run it as root? You might need to adjust USB permissions, but I have no idea how to do that on OS X.

l0c0luke commented 10 years ago

I had tried running as root. I didn't attempt to alter the mode of the devices though. Ultimately I got this damn gridseed working with the cpuminer included with the macminer app so I guess I am content. You can close this issue if you want. I presume it was a setup problem on my end. THanks for looking at it though.

jeteokeeffe commented 10 years ago

I've running into the same issue (running as root) when running more then 9 gridseeds

cgminer --retries=3 --api-listen --api-allow=192.168.1.66 --gridseed-options=baud=115200,freq=850,chips=5,modules=1,usefifo=0,btc=0 --hotplug=30 -u xxxx -p xxxx

I'm seeing the following error messages

[2014-03-25 19:45:11] gridseed detect (1:78) failed to initialise (incorrect device?)
[2014-03-25 19:49:27] GSD 1 GetResults usb read err:(-99) LIBUSB_ERROR_OTHER
 [2014-03-25 19:49:27] No response from 1
 [2014-03-25 19:49:27] GSD 1 failure, disabling!
[2014-03-25 19:55:17] GSD3: TIMEOUT GetResults took 1400ms but was 100ms
 [2014-03-25 19:55:17] GSD5: TIMEOUT GetResults took 1400ms but was 100ms
 [2014-03-25 19:55:17] GSD2: TIMEOUT GetResults took 1399ms but was 100ms
 [2014-03-25 19:55:17] GSD10: TIMEOUT GetResults took 1398ms but was 100ms
 [2014-03-25 19:55:17] GSD9: TIMEOUT GetResults took 1398ms but was 100ms
 [2014-03-25 19:55:17] GSD0: TIMEOUT GetResults took 1400ms but was 100ms
 [2014-03-25 19:55:17] GSD7: TIMEOUT GetResults took 1399ms but was 100ms
 [2014-03-25 19:55:17] GSD8: TIMEOUT GetResults took 1398ms but was 100ms
jeteokeeffe commented 10 years ago

Just to give more details

root@miner1:~# uname -a
Linux miner1 3.11.0-15-generic #25-Ubuntu SMP Thu Jan 30 17:22:01 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
root@miner1:~# gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.8.1-10ubuntu9' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.8 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix

I've disabled hotplugging and I'm no longer seeing the gridseed detect (1:78) failed to initialise (incorrect device?) issue. I haven't seen any timeouts since then either. I'm still getting this error GetResults usb read err:(-99) LIBUSB_ERROR_OTHER which causes cgminer to restart.

Bitcoin3ra commented 6 years ago

Hi. I know it has been a while, but I was experiencing the exact same issue as @jeteokeeffe and for me the solution was simply buying a new PSU for the miner. The original PSU that came with it was making a cricket-like noise and the same day this started these error messages appeared. Probably it was due some kind of sudden power shortage or the voltage not being stable. I don't know because I am no electrician. In any case, hopefully this can help somebody.