OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 186.

hhs99

member

Activity: 103

Merit: 10

I tried Cudaminer but it kept crashing but thats a topic for another day. Its just strange that benchmark gets great rates but it wont run like normal. Is it normal for benchmark to run perfectly but when you step out of benchmark it goes crazy? Heck I just want to GPU mine and step away from cpuminer. I would even let someone into the box to check it out.

Quote from: zyk0 on November 03, 2013, 03:22:49 AM

Quote from: hhs99 on November 03, 2013, 03:17:15 AM

I have a computer with 2 Nvidia cards and the benchmark works perfectly but when I run normal it segfaults. This is an xubuntu machine. below is the debug from cgminer. I don't expect a lot of hashes just have to last until my 7900's get here. How would I fix this? I'm still a newbe so please forgive me if its something stupid simple. ALso if anyone has working worksize for these cards please let me know, I would love to get a few extra hashes.

for scrypt+nvidia, you're probably better off trying cudaminer.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: -ck on November 02, 2013, 05:39:58 PM

Despite what it may look like, we are making progress.

Next:
~~http://ck.kolivas.org/apps/cgminer/temp/cgminer-wtf.exe~~

Ignore that binary, it's known broken. Here's the real next test one:

http://ck.kolivas.org/apps/cgminer/debug/cgminer-gtfo.exe

EDIT: Followed by:

http://ck.kolivas.org/apps/cgminer/temp/cgminer-lol.exe

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: zyk0 on November 03, 2013, 03:49:02 AM

Thanks for banging out some work on it in the middle of your AMU stuff/other things in life. I'm sure there will be a lot of people happy to see this working.

for those not able to use that debug/win32 binary, they can just do a quick hack change of s/BPMC/BFMG/ in usbutils.c and be good to go?

The debug binary should be fine, it will only use slightly more cpu and memory. A new full version will likely be out in the next day or so, but the change is trivial and committed to git already that will fix them.

Code:

diff --git a/usbutils.c b/usbutils.c
index c4402f0..580d4b1 100644
--- a/usbutils.c
+++ b/usbutils.c
@@ -305,7 +305,7 @@ static struct usb_find_devices find_dev[] = {
   .config = 1,
   .timeout = BITFURY_TIMEOUT_MS,
   .latency = LATENCY_UNUSED,
- .iManufacturer = "BPMC",
+ //.iManufacturer = "BPMC",
   .iProduct = "Bitfury BF1",
   INTINFO(bfu_ints)
   },

zyk0

newbie

Activity: 33

Merit: 0

Quote from: -ck on November 03, 2013, 03:40:06 AM

Quote from: zyk0 on November 03, 2013, 03:36:35 AM

fork of mainline rather than AMU work is quite a bit better, they're showing up and usable now.

but hashing is a bit off the mark.

Code:

Be patient. It takes ages to get a meaningful hashrate from them since it's based purely on share return rate.

Thank goodness it's trivial to fix them.

Thanks for banging out some work on it in the middle of your AMU stuff/other things in life. I'm sure there will be a lot of people happy to see this working.

for those not able to use that debug/win32 binary, they can just do a quick hack change of s/BPMC/BFMG/ in usbutils.c and be good to go?

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: zyk0 on November 03, 2013, 03:36:35 AM

fork of mainline rather than AMU work is quite a bit better, they're showing up and usable now.

but hashing is a bit off the mark.

Code:

Be patient. It takes ages to get a meaningful hashrate from them since it's based purely on share return rate.

Thank goodness it's trivial to fix them.

zyk0

newbie

Activity: 33

Merit: 0

Quote from: -ck on November 03, 2013, 03:25:12 AM

It is possible these are not trivially different from the red fury and a simple change will not fix it. That executable I uploaded was based on the AMU testing we've been doing, so I've reuploaded one based on the regular cgminer code, though I doubt it will fix it. Try redownloading and trying again. Your logs are only for 3 seconds but I assume you let it run longer. If this is no better, I'm afraid you may be on your own, and will have to contact your vendor for more support since I don't have one. I hate sounding like a broken record.

3 second log was as long as -T -D ran.

fork of mainline rather than AMU work is quite a bit better, they're showing up and usable now.

Code:

[2013-11-03 01:28:04] BF1 looking for and found BF1 03eb:204b
[2013-11-03 01:28:04] USB lock bitfury 8-8
[2013-11-03 01:28:04] RES: bitfury (8:8) lock=1
[2013-11-03 01:28:04] USB res lock bitfury 8-8
[2013-11-03 01:28:04] RES: bitfury (8:8) lock ok=1
[2013-11-03 01:28:04] USB init - BF1 device 8:8-i1 usbver=0110 prod='Bitfury BF1' manuf='BFMG' serial='64937323235351409051'
[2013-11-03 01:28:04] BF1 0: Found at 8:8-i1
[2013-11-03 01:28:05] BF10: BF1Flush (amt=0 err=-7 ern=16)
[2013-11-03 01:28:05] BF1 0: Getinfo returned version 1, product BF1 serial 15040915
[2013-11-03 01:28:07] BF1 0: Getreset returned RR
[2013-11-03 01:28:08] BF10: BF1Flush (amt=0 err=-7 ern=10060)
[2013-11-03 01:28:09] BF10: BF1Flush (amt=0 err=-7 ern=10060)
[2013-11-03 01:28:09] BF1 0: Successfully initialised 8:8-i1
[2013-11-03 01:28:09] BF1 looking for and found BF1 03eb:204b
[2013-11-03 01:28:09] USB lock bitfury 8-3
[2013-11-03 01:28:09] RES: bitfury (8:3) lock=1
[2013-11-03 01:28:09] USB res lock bitfury 8-3
[2013-11-03 01:28:09] RES: bitfury (8:3) lock ok=1
[2013-11-03 01:28:09] USB init - BF1 device 8:3-i1 usbver=0110 prod='Bitfury BF1' manuf='BFMG' serial='64937323235351603221'
[2013-11-03 01:28:09] BF1 0: Found at 8:3-i1
[2013-11-03 01:28:10] BF10: BF1Flush (amt=0 err=-7 ern=16)
[2013-11-03 01:28:10] BF1 0: Getinfo returned version 1, product BF1 serial 15062312
[2013-11-03 01:28:11] BF1 0: Getreset returned RR
[2013-11-03 01:28:12] BF10: BF1Flush (amt=0 err=-7 ern=10060)
[2013-11-03 01:28:13] BF10: BF1Flush (amt=0 err=-7 ern=10060)
[2013-11-03 01:28:13] BF1 1: Successfully initialised 8:3-i1
[2013-11-03 01:28:13] BF1 looking for and found BF1 03eb:204b
[2013-11-03 01:28:13] USB lock bitfury 8-2
[2013-11-03 01:28:13] RES: bitfury (8:2) lock=1
[2013-11-03 01:28:13] USB res lock bitfury 8-2
[2013-11-03 01:28:13] RES: bitfury (8:2) lock ok=1
[2013-11-03 01:28:13] USB init - BF1 device 8:2-i1 usbver=0110 prod='Bitfury BF1' manuf='BFMG' serial='64937323235351609251'
[2013-11-03 01:28:13] BF1 0: Found at 8:2-i1
[2013-11-03 01:28:14] BF10: BF1Flush (amt=0 err=-7 ern=16)
[2013-11-03 01:28:14] BF1 0: Getinfo returned version 1, product BF1 serial 15062915
[2013-11-03 01:28:14] BF1 0: Getreset returned RR
[2013-11-03 01:28:15] BF10: BF1Flush (amt=0 err=-7 ern=10060)
[2013-11-03 01:28:16] BF10: BF1Flush (amt=0 err=-7 ern=10060)
[2013-11-03 01:28:16] BF1 2: Successfully initialised 8:2-i1
[2013-11-03 01:28:16] BF1 looking for and found BF1 03eb:204b
[2013-11-03 01:28:16] USB lock bitfury 8-5
[2013-11-03 01:28:16] RES: bitfury (8:5) lock=1
[2013-11-03 01:28:16] USB res lock bitfury 8-5
[2013-11-03 01:28:16] RES: bitfury (8:5) lock ok=1
[2013-11-03 01:28:16] USB init - BF1 device 8:5-i1 usbver=0110 prod='Bitfury BF1' manuf='BFMG' serial='6493732323535160B251'
[2013-11-03 01:28:16] BF1 0: Found at 8:5-i1
[2013-11-03 01:28:17] BF10: BF1Flush (amt=0 err=-7 ern=16)
[2013-11-03 01:28:17] BF1 0: Getinfo returned version 1, product BF1 serial 15062b15
[2013-11-03 01:28:18] BF1 0: Getreset returned RR
[2013-11-03 01:28:19] BF10: BF1Flush (amt=0 err=-7 ern=10060)
[2013-11-03 01:28:20] BF10: BF1Flush (amt=0 err=-7 ern=10060)
[2013-11-03 01:28:20] BF1 3: Successfully initialised 8:5-i1

but hashing is a bit off the mark, but I haven't investigated what they're capable of w/ bfgminer.

Code:

cgminer version 3.6.6 - Started: [2013-11-03 01:28:54]
--------------------------------------------------------------------------------
(5s):4.708G (avg):4.574Gh/s | A:392 R:6 HW:0 WU:68.5/m
ST: 2 SS: 0 NB: 2 LW: 1090 GF: 0 RF: 0
Connected to xxxxxxxxxxxxxxxxxxxxxxxx diff 2 with stratum as user xxxxxx
Block: 64c8ebfe... Diff:391M Started: [01:31:32] Best share: 135
--------------------------------------------------------------------------------
[P]ool management [S]ettings [D]isplay options [Q]uit
BF1 0: | 502.2M/487.1Mh/s | A: 34 R:0 HW:0 WU: 7.0/m
BF1 1: | 1.948G/1.861Gh/s | A:172 R:4 HW:0 WU:27.8/m
BF1 2: | 242.4M/215.9Mh/s | A: 18 R:0 HW:0 WU: 3.2/m
BF1 3: | 2.170G/2.056Gh/s | A:170 R:2 HW:0 WU:31.2/m
--------------------------------------------------------------------------------

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: zyk0 on November 03, 2013, 02:46:46 AM

Quote from: -ck on November 03, 2013, 02:28:13 AM

Quote from: zyk0 on November 03, 2013, 02:13:07 AM

Quote from: -ck on November 03, 2013, 02:00:00 AM

I don't know that, for the error message implies that it's not installed. I have one red fury, it works on windows 7 as I said. You can give me the output of what happens when you start cgminer with -T -D and I can see what I make of it.

Thanks, this appears to be the relevant part of the output, and probably readily solves the mystery

Code:

[2013-11-03 00:10:23] USB init, iManufacturer mismatch - BF1 device 8:8-i1

Indeed, for the iManufacturer code matches only the red fury.

It's a debug build for now, but see if this suffices:
http://ck.kolivas.org/apps/cgminer/debug/cgminer-nogpu.exe

If the iProduct entry does not match we'll need to account for that too. Start it with -D -T again if it fails.

Errors out on flush and getinfo (several times)

output log @ http://www.frohike.net/bluefury/bluefury_TD.txt

It is possible these are not trivially different from the red fury and a simple change will not fix it. That executable I uploaded was based on the AMU testing we've been doing, so I've reuploaded one based on the regular cgminer code, though I doubt it will fix it. Try redownloading and trying again. Your logs are only for 3 seconds but I assume you let it run longer. If this is no better, I'm afraid you may be on your own, and will have to contact your vendor for more support since I don't have one. I hate sounding like a broken record.

EDIT: That previous binary was broken even for me so it's no surprise it didn't work for you Tongue

Try the redownload.

zyk0

newbie

Activity: 33

Merit: 0

Quote from: hhs99 on November 03, 2013, 03:17:15 AM

I have a computer with 2 Nvidia cards and the benchmark works perfectly but when I run normal it segfaults. This is an xubuntu machine. below is the debug from cgminer. I don't expect a lot of hashes just have to last until my 7900's get here. How would I fix this? I'm still a newbe so please forgive me if its something stupid simple. ALso if anyone has working worksize for these cards please let me know, I would love to get a few extra hashes.

for scrypt+nvidia, you're probably better off trying cudaminer.

hhs99

member

Activity: 103

Merit: 10

I have a computer with 2 Nvidia cards and the benchmark works perfectly but when I run normal it segfaults. This is an xubuntu machine. below is the debug from cgminer. I don't expect a lot of hashes just have to last until my 7900's get here. How would I fix this? I'm still a newbe so please forgive me if its something stupid simple. ALso if anyone has working worksize for these cards please let me know, I would love to get a few extra hashes.

Code:

/usr/local/cgminer/cgminer -o stratum+tcp://coinotron.com:3337 -u user -p pw --scrypt -D -T
[2013-11-02 13:03:04] Started cgminer 3.6.6
[2013-11-02 13:03:05] CL Platform 0 vendor: NVIDIA Corporation
[2013-11-02 13:03:05] CL Platform 0 name: NVIDIA CUDA
[2013-11-02 13:03:05] CL Platform 0 version: OpenCL 1.1 CUDA 4.2.1
[2013-11-02 13:03:05] Platform 0 devices: 2
[2013-11-02 13:03:05] 0 GeForce 8600 GT
[2013-11-02 13:03:05] 1 GeForce 9100
[2013-11-02 13:03:05] Probing for an alive pool
[2013-11-02 13:03:05] Popping work to stage thread
[2013-11-02 13:03:05] Testing pool stratum+tcp://coinotron.com:3337
[2013-11-02 13:03:15] Succeeded delayed connect
[2013-11-02 13:03:15] Failed to get sessionid in initiate_stratum
[2013-11-02 13:03:15] Pool 0 difficulty changed to 256
[2013-11-02 13:03:15] Stratum authorisation success for pool 0
[2013-11-02 13:03:15] Pool 0 stratum+tcp://coinotron.com:3337 alive
[2013-11-02 13:03:15] Generated stratum merkle 70a3ffb971bec052afedf948e84cbfa10ce7bf18f2f3e8e08eebffcb24a2d63a
[2013-11-02 13:03:15] Generated stratum header 0000000174e85646ab02ce7cea6aeb283a5538163d1c2745edadda08251252cac3a15f1d70a3ffb971bec052afedf948e84cbfa10ce7bf18f2f3e8e08eebffcb24a2d63a527530201c020239000000000000008000000000000000000000000000000000000000000000000000000000000000
[2013-11-02 13:03:15] Work job_id 335 nonce2 0 ntime 52753020
[2013-11-02 13:03:15] Generated target 000000000000000000000000000000000000000000000000000000ffff000000
[2013-11-02 13:03:15] Network diff set to 127
[2013-11-02 13:03:15] New block: 52caedadda083d1c... diff 127
[2013-11-02 13:03:15] Stratum from pool 0 detected new block
[2013-11-02 13:03:16] Init GPU thread 0 GPU 0 virtual GPU 0
[2013-11-02 13:03:16] CL Platform vendor: NVIDIA Corporation
[2013-11-02 13:03:16] CL Platform name: NVIDIA CUDA
[2013-11-02 13:03:16] CL Platform version: OpenCL 1.1 CUDA 4.2.1
[2013-11-02 13:03:16] List of devices:
[2013-11-02 13:03:16] 0[7CGeForce 8600 GT
[2013-11-02 13:03:16] 1[7CGeForce 9100
[2013-11-02 13:03:16] Selected 0: GeForce 8600 GT
[2013-11-02 13:03:16] Preferred vector width reported 1
[2013-11-02 13:03:16] Max work group size reported 512
[2013-11-02 13:03:16] Max mem alloc size is 134217728
[2013-11-02 13:03:16] Selecting scrypt kernel
[2013-11-02 13:03:16] GPU 0: selecting lookup gap of 2
[2013-11-02 13:03:16] GPU 0: selecting thread concurrency of 960
[2013-11-02 13:03:16] No binary found, generating from source
[2013-11-02 13:03:16] Setting worksize to 256
[2013-11-02 13:03:16] cl_amd_media_ops not found, will not set BITALIGN
[2013-11-02 13:03:16] BFI_INT patch requiring device not found, will not BFI_INT patch
[2013-11-02 13:03:16] CompilerOptions: -D LOOKUP_GAP=2 -D CONCURRENT_THREADS=960 -D WORKSIZE=256 -D GOFFSET -D OCL1
[2013-11-02 13:04:12] Generated stratum merkle e4cfe749470fd742dc9850e568562ed9cfdceab9df4e9fac61e670003710e821
[2013-11-02 13:04:12] Generated stratum header 00000001636524ab9c16017125e28d13676bb795ab756945ad20648dada8d12d607b01bbe4cfe749470fd742dc9850e568562ed9cfdceab9df4e9fac61e670003710e8215275307e1c020239000000000000008000000000000000000000000000000000000000000000000000000000000000
[2013-11-02 13:04:12] Work job_id 337 nonce2 0 ntime 5275307e
[2013-11-02 13:04:12] Generated target 000000000000000000000000000000000000000000000000000000ffff000000
[2013-11-02 13:04:12] Network diff set to 127
[2013-11-02 13:04:12] New block: d12dad20648dab75... diff 127
Segmentation fault (core dumped)

zyk0

newbie

Activity: 33

Merit: 0

Quote from: -ck on November 03, 2013, 02:28:13 AM

Quote from: zyk0 on November 03, 2013, 02:13:07 AM

Quote from: -ck on November 03, 2013, 02:00:00 AM

I don't know that, for the error message implies that it's not installed. I have one red fury, it works on windows 7 as I said. You can give me the output of what happens when you start cgminer with -T -D and I can see what I make of it.

Thanks, this appears to be the relevant part of the output, and probably readily solves the mystery

Code:

[2013-11-03 00:10:23] USB init, iManufacturer mismatch - BF1 device 8:8-i1

Indeed, for the iManufacturer code matches only the red fury.

It's a debug build for now, but see if this suffices:
http://ck.kolivas.org/apps/cgminer/debug/cgminer-nogpu.exe

If the iProduct entry does not match we'll need to account for that too. Start it with -D -T again if it fails.

Errors out on flush and getinfo (several times)

output log @ http://www.frohike.net/bluefury/bluefury_TD.txt
or you can decode it from

Code:

begin 644 bluefury_TD.txt.xz
M_3=Z6%H```3FUK1&`@`A`1P````0SUC,YWX-!9==`!`6PD,`YQG!&Q\)Z6L&
M9%$^VFJ--61_W7!EO<7]Y1/,YOT6`RC9^70C"6J;8E
MVBYI`>Y**3\K1U;`0&6TU20JH%$MP_G>!I^R0P@@R:ROHDN.JL#N3T^S-I3M
MHF=.K.\MP)<"Z>KLH%529#
M'?'7!IK,OF]"T)P+)2VZ^J)_!#!W`6A=XH$]P38ZH.!0NE-C0M=-^IA&35T>9ZZGAQ/+-_HN[;!$G`(U;-,9@1:@3@@T&Q%=7E7!C.JE">DD]
M]:GSU7..F-`(&A.-BM"L>&N.%(;V>H6\&_7":./GFH._;B!B[S6CXS`D")$`
MGZ'@5$:L'Z7+$W"?,<[FU6T>8CBF@73I+YPHP20F[^9N"%W*EHS3HNU)LG1T
M_/`,E&"/=3805R/Z],H!KT[Y&I<#P3LW9N)_=CN$`;J5GW?!2W!`.?.Z/[-4
MF-]]-YLCE@ID/]8/D5GW^1F<4NS97\V;T?4-Q=CGJH$,1W#VL8?7-4B3>;P4
MTT?1(F,8U""MN\?:<1A4XOE"*`.]<.11ILD&&27ZSG-4,:>N8'V:?[',E]*X,2E*@9EO20P4
MR:LKR2"7_H18K-*':AH>"MT"4C01#HG]X\@"M/^U\3P]9Z7DS+"@R_Y"N2FD
M4M:W*_'@H*?X0_N`P.DD\!>BF<1':E4=^W,SKF<)9:A%?%@K:(J?3#N8#4':
M`09.?Q,C6^+9*<5/J\*'$&THI`R>D(RWXPH"[email protected]*%B#F\Q0J^3K*V
MJ:Q%'"(7KE0C7X+H%5T1PM[$4\^!VT3@3&QZPCN.Y$@5;6@"&MKL'_K;.A+3
MWD&,A:[WB@YFJ^$Y\.GIEX7LO5RCH'2:*E]*H9.7YV(M=P=($'K9^#2;Z.![
M78P:;$#P>6PI53ZC&FJ!MA]%UWA9W?J-ID*4:YS81)3ZFZXT<<-)O9E^QN'E
M,\JI(B&('777PXYHH:\F*)>WM\=\M./=\;G.A'D[.RB"O[`-Y-MZ1Q)!EY'V;U41<>K50(JF%EY?T1VLPA5!,T-!9V_*>;7R[U'=V]TQ]!C'#:B
M28LG>+'5!2QCC"=8@RUE4,$0(_C1P3[RZ$O/UK2=#35*^4TU\$J$*)TEHT08
M/*,>"HJE5>4TNOOQ?A8D#N')"Q[="54N#9Y,-R$9SR"+/^>0!DFR6ZOM[R'>-F`0(H;L+1>?9+;=]FY"$/#AO:(^5F5^2/30=%:#G`1NS+W9Z(JMERW_
M%L:Y8NK&?`7IXRA]D--S<#J:Z%>`!6NV7$F$BBB&"WIF;#Z;DT(35(II^GN-
M:I/'%'9Q3XB\%3EB$2$9>"\P4"M>=\J$V`ACV_JV^$JHR6T#H`]U$!PG3+=\
M>>;>?B!62*).KNRHQ5_8F$$ZH;3&/E[/?QV-P^5K"6&TTW39(QU29;O[GP8=
M/\HZG*S\H8\36(R]C5<*PUF4OP0=[3S)'!DH6TAK.+!S$'I0D3ZE>HO*;A;_
MK*ONZ3;.[X&07.^U-@9P\3/.T;.TKT=/#AVZ?)\G'C]T4M39"@"Q<`!*'<1O
MY8.\92[C7D5%O`E\O`8J2S;W])E3R+TQ#3GWY;*\![9:_@FC(9)$<7[:;,2T
MEAI5O+^B[,GHXZ>YWS@\6M&!1\L@5IQC$NV^;-PB9-P+0^[M9H#PBTOA0P-X
M&D'*.TATS`FX"G@*C.=@P)UU=BQH%6\)Z%4&`1_;D2U:5.S%M:1?TN=%5[JR
M317T9LRZZ:0K#+L'FI:M/VUZ-%P*G0?\/^\1USAE<$N-%&1=,L*`R_%/&G?'
MG'IXBP"@UY'#/"R2.>N@[VW^9H70?```M,SQSH*O`(P``;,+COP=`+>C[V:Q
+Q&?[`@`````$65H`
`
end

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: zyk0 on November 03, 2013, 02:13:07 AM

Quote from: -ck on November 03, 2013, 02:00:00 AM

I don't know that, for the error message implies that it's not installed. I have one red fury, it works on windows 7 as I said. You can give me the output of what happens when you start cgminer with -T -D and I can see what I make of it.

Thanks, this appears to be the relevant part of the output, and probably readily solves the mystery

Code:

[2013-11-03 00:10:23] USB init, iManufacturer mismatch - BF1 device 8:8-i1

Indeed, for the iManufacturer code matches only the red fury.

It's a debug build for now, but see if this suffices:
http://ck.kolivas.org/apps/cgminer/debug/cgminer-nogpu.exe

If the iProduct entry does not match we'll need to account for that too. Start it with -D -T again if it fails.

zyk0

newbie

Activity: 33

Merit: 0

Quote from: -ck on November 03, 2013, 02:00:00 AM

I don't know that, for the error message implies that it's not installed. I have one red fury, it works on windows 7 as I said. You can give me the output of what happens when you start cgminer with -T -D and I can see what I make of it.

Thanks, this appears to be the relevant part of the output, and probably readily solves the mystery

Code:

[2013-11-03 00:10:23] BF1 looking for and found BF1 03eb:204b
[2013-11-03 00:10:23] USB lock bitfury 8-8
[2013-11-03 00:10:23] RES: bitfury (8:8) lock=1
[2013-11-03 00:10:23] USB res lock bitfury 8-8
[2013-11-03 00:10:23] RES: bitfury (8:8) lock ok=1
[2013-11-03 00:10:23] USB init, iManufacturer mismatch - BF1 device 8:8-i1
[2013-11-03 00:10:23] USB free BF1
[2013-11-03 00:10:23] USB unlock bitfury 8-8
[2013-11-03 00:10:23] BF1 looking for and found BF1 03eb:204b
[2013-11-03 00:10:23] USB lock bitfury 8-3
[2013-11-03 00:10:23] RES: bitfury (8:3) lock=1
[2013-11-03 00:10:23] USB res lock bitfury 8-3
[2013-11-03 00:10:23] RES: bitfury (8:3) lock ok=1
[2013-11-03 00:10:23] RES: bitfury (8:8) lock=0
[2013-11-03 00:10:23] USB res unlock bitfury 8-8
[2013-11-03 00:10:23] USB init, iManufacturer mismatch - BF1 device 8:3-i1
[2013-11-03 00:10:23] USB free BF1
[2013-11-03 00:10:23] USB unlock bitfury 8-3
[2013-11-03 00:10:23] BF1 looking for and found BF1 03eb:204b
[2013-11-03 00:10:23] RES: bitfury (8:3) lock=0
[2013-11-03 00:10:23] USB res unlock bitfury 8-3
[2013-11-03 00:10:23] USB lock bitfury 8-2
[2013-11-03 00:10:23] RES: bitfury (8:2) lock=1
[2013-11-03 00:10:23] USB res lock bitfury 8-2
[2013-11-03 00:10:23] RES: bitfury (8:2) lock ok=1
[2013-11-03 00:10:24] USB init, iManufacturer mismatch - BF1 device 8:2-i1
[2013-11-03 00:10:24] USB free BF1
[2013-11-03 00:10:24] USB unlock bitfury 8-2
[2013-11-03 00:10:24] BF1 looking for and found BF1 03eb:204b
[2013-11-03 00:10:24] RES: bitfury (8:2) lock=0
[2013-11-03 00:10:24] USB lock bitfury 8-9
[2013-11-03 00:10:24] USB res unlock bitfury 8-2
[2013-11-03 00:10:24] RES: bitfury (8:9) lock=1
[2013-11-03 00:10:24] USB res lock bitfury 8-9
[2013-11-03 00:10:24] RES: bitfury (8:9) lock ok=1
[2013-11-03 00:10:24] USB init, iManufacturer mismatch - BF1 device 8:9-i1
[2013-11-03 00:10:24] USB free BF1
[2013-11-03 00:10:24] USB unlock bitfury 8-9

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: zyk0 on November 03, 2013, 01:56:13 AM

Quote from: -ck on November 03, 2013, 01:29:29 AM

Quote from: zyk0 on November 02, 2013, 10:13:22 PM

Quote from: -ck on November 02, 2013, 07:16:09 PM

Quote from: OgNasty on November 02, 2013, 02:09:07 PM

Any idea why my Blue Fury's aren't being detected? Zadig driver installation went smoothly... Do I need a special command to recognize them or something?

No. Sometimes mine take up to a minute to recognise and initialise properly. Also if you have AMUs, I have heard that they conflict and you may have to unplug and plug the furies back in for the to work concurrently.

Now that they're out in the wild, lots of other people are also not getting their Blue Fury's to work in cgminer (see Blue Fury Support Thread). I haven't seen any reported successes w/ cgminer, only bfgminer.

I'm in that same boat, with cgminer seeing them but not doing anything with them.

If I disable one in device manage I can get a

[2013-11-02 20:35:50] USB init, open device failed, err -12, you need to install a WinUSB driver for - BF1 device 8:5-i1
[2013-11-02 20:35:50] bitfury detect (8:5) failed to initialise (incorrect device?)

every hotplug poll, but once I enable it those messages go away as if everything is copacetic. But the devices are basically ignored.

So... the obvious question: Did you install a winusb driver for them? Note I only have a redfury but as far as I'm aware they should be identical and it works perfectly fine on windows 7.

Yes, that cgminer -n output would have been nothing like that w/o WinUSB. I figured that was easily inferred.

I don't know that, for the error message implies that it's not installed. I have one red fury, it works on windows 7 as I said. You can give me the output of what happens when you start cgminer with -T -D and I can see what I make of it.

zyk0

newbie

Activity: 33

Merit: 0

Quote from: -ck on November 03, 2013, 01:29:29 AM

Quote from: zyk0 on November 02, 2013, 10:13:22 PM

Quote from: -ck on November 02, 2013, 07:16:09 PM

Quote from: OgNasty on November 02, 2013, 02:09:07 PM

Any idea why my Blue Fury's aren't being detected? Zadig driver installation went smoothly... Do I need a special command to recognize them or something?

No. Sometimes mine take up to a minute to recognise and initialise properly. Also if you have AMUs, I have heard that they conflict and you may have to unplug and plug the furies back in for the to work concurrently.

Now that they're out in the wild, lots of other people are also not getting their Blue Fury's to work in cgminer (see Blue Fury Support Thread). I haven't seen any reported successes w/ cgminer, only bfgminer.

I'm in that same boat, with cgminer seeing them but not doing anything with them.

If I disable one in device manage I can get a

[2013-11-02 20:35:50] USB init, open device failed, err -12, you need to install a WinUSB driver for - BF1 device 8:5-i1
[2013-11-02 20:35:50] bitfury detect (8:5) failed to initialise (incorrect device?)

every hotplug poll, but once I enable it those messages go away as if everything is copacetic. But the devices are basically ignored.

So... the obvious question: Did you install a winusb driver for them? Note I only have a redfury but as far as I'm aware they should be identical and it works perfectly fine on windows 7.

Yes, that cgminer -n output would have been nothing like that w/o WinUSB. I figured that was easily inferred.
Besides, if you follow that support thread, other people are getting the same results in Linux.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: zyk0 on November 02, 2013, 10:13:22 PM

Quote from: -ck on November 02, 2013, 07:16:09 PM

Quote from: OgNasty on November 02, 2013, 02:09:07 PM

Any idea why my Blue Fury's aren't being detected? Zadig driver installation went smoothly... Do I need a special command to recognize them or something?

No. Sometimes mine take up to a minute to recognise and initialise properly. Also if you have AMUs, I have heard that they conflict and you may have to unplug and plug the furies back in for the to work concurrently.

Now that they're out in the wild, lots of other people are also not getting their Blue Fury's to work in cgminer (see Blue Fury Support Thread). I haven't seen any reported successes w/ cgminer, only bfgminer.

I'm in that same boat, with cgminer seeing them but not doing anything with them.

If I disable one in device manage I can get a

[2013-11-02 20:35:50] USB init, open device failed, err -12, you need to install a WinUSB driver for - BF1 device 8:5-i1
[2013-11-02 20:35:50] bitfury detect (8:5) failed to initialise (incorrect device?)

every hotplug poll, but once I enable it those messages go away as if everything is copacetic. But the devices are basically ignored.

So... the obvious question: Did you install a winusb driver for them? Note I only have a redfury but as far as I'm aware they should be identical and it works perfectly fine on windows 7.

Xian01

legendary

Activity: 1652

Merit: 1067

Christian Antkow

Con, humble request for the next version of CGMiner, specifically dealing with K16's - It would be super spiffy if we could get a --klondike-temp-cutoff parm or something to override the hard-coded 54.5C.

A couple of mine are running hotter than others, despite a ton of airflow, and often hit 55C and then cutoff until they drop back to 45C; would be nice to set higher thresholds for testing/troubleshooting without the need to recompile for Windows.

Also, that "KLNx:0 went idle before work was sent" spam is troubling.

Cheers.

zyk0

newbie

Activity: 33

Merit: 0

Quote from: -ck on November 02, 2013, 07:16:09 PM

Quote from: OgNasty on November 02, 2013, 02:09:07 PM

Any idea why my Blue Fury's aren't being detected? Zadig driver installation went smoothly... Do I need a special command to recognize them or something?

No. Sometimes mine take up to a minute to recognise and initialise properly. Also if you have AMUs, I have heard that they conflict and you may have to unplug and plug the furies back in for the to work concurrently.

Now that they're out in the wild, lots of other people are also not getting their Blue Fury's to work in cgminer (see Blue Fury Support Thread). I haven't seen any reported successes w/ cgminer, only bfgminer.

I'm in that same boat, with cgminer seeing them but not doing anything with them.

"cgminer --disable-gpu -n" output:

Code:

[2013-11-02 20:09:57] 0 GPU devices max detected
[2013-11-02 20:09:57] USB all: found 17 devices - listing known devices
.USB dev 0: Bus 8 Device 8 ID: 03eb:204b
  Manufacturer: 'BFMG'
  Product: 'Bitfury BF1'
.USB dev 1: Bus 8 Device 3 ID: 03eb:204b
  Manufacturer: 'BFMG'
  Product: 'Bitfury BF1'
.USB dev 2: Bus 8 Device 2 ID: 03eb:204b
  Manufacturer: 'BFMG'
  Product: 'Bitfury BF1'
.USB dev 3: Bus 8 Device 5 ID: 03eb:204b
  Manufacturer: 'BFMG'
  Product: 'Bitfury BF1'
.USB dev 4: Bus 8 Device 7 ID: 0403:6014
  Manufacturer: 'FTDI'
  Product: 'BitFORCE SHA256 SC'
[2013-11-02 20:09:57] 5 known USB devices

but "cgminer --disable-gpu --usb 8:8,8:3,8:2,8:5 --benchmark" gives:

Code:

cgminer version 3.6.6 - Started: [2013-11-02 20:11:47]
--------------------------------------------------------------------------------
(5s):0.000 (avg):0.000h/s | A:0 R:0 HW:0 WU:0.0/m
ST: 2 SS: 0 NB: 0 LW: 0 GF: 1 RF: 0
Connected to (null) diff 0 without LP as user Benchmark
Block: (null)... Diff: Started: Best share: 0
--------------------------------------------------------------------------------
[P]ool management [S]ettings [D]isplay options [Q]uit
--------------------------------------------------------------------------------

[2013-11-02 20:11:45] Started cgminer 3.6.6
[2013-11-02 20:11:47] No devices detected!
[2013-11-02 20:11:47] Waiting for USB hotplug devices or press q to quit
[2013-11-02 20:11:47] Pool 0 not providing work fast enough

If I disable one in device manage I can get a

Code:

[2013-11-02 20:35:50] USB init, open device failed, err -12, you need to install a WinUSB driver for - BF1 device 8:5-i1
[2013-11-02 20:35:50] bitfury detect (8:5) failed to initialise (incorrect device?)

every hotplug poll, but once I enable it those messages go away as if everything is copacetic. But the devices are basically ignored.

aigeezer

legendary

Activity: 1450

Merit: 1013

Cryptanalyst castrated by his government, 1952

Quote from: -ck on November 02, 2013, 07:22:11 PM

Quote from: aigeezer on November 01, 2013, 08:50:38 PM

Edit: I added logging/debug to chopwsync and it found a zombie! I have to leave for 10 hours or so but I'll look at the log then. Meanwhile I'll run some other version.

Do you have this log available?

This should be it. Sorry for the delay: https://www.dropbox.com/s/b438ywichzjuxuf/chopwsync-log.txt

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: aigeezer on November 01, 2013, 08:50:38 PM

Edit: I added logging/debug to chopwsync and it found a zombie! I have to leave for 10 hours or so but I'll look at the log then. Meanwhile I'll run some other version.

Do you have this log available?

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: dlasher on November 02, 2013, 10:37:11 AM

upgraded from 3.6.2 to 3.6.6 two days ago, and have twice run into a new issue.

(5) different machines running 3.6.6 at (3) different physical locations, different carriers.

each miner set up for (6) pool entries, (3) btcguild, (2) eligius, (1) deepbit, set to "failover" mode.

I've now had (2) of them completely stall, no new work.

At that point ALL work in/out of cgminer stops..I get idle miner notifications from btcguild, but it doesn't fail down to eligius or deepbit.

For now I'm going back to 3.6.2, but wanted you to know I'd seen something new. I'm sorry I don't have better logs.

No I have not had this reported. There are some issues with pools that use round robin DNS and stratum and possibly you have run into that. There is nothing really different in 3.6.6 versus 3.6.2 if I recall correctly that might have made this come up so if you may well have the same issue with 3.6.2. I've made some changes to the upcoming code that hopefully will help this but a new release is not due out just yet while I keep bashing my head against the AMU wall.

Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 186. (Read 5806015 times)