I loaded zadig 8 or 9 times and it finally works .
this stick is mining on www.mmpool.org
see screen shot
it is pulling 11gh
Topic: The combined sidehack-novak usb stick review thread. AKA GekkoScience BM1384 - page 17. (Read 26365 times)
June 11, 2015, 06:12:34 PM
Okay many tries on 2 different windows 7 machines and success!
I loaded zadig 8 or 9 times and it finally works .
this stick is mining on www.mmpool.org
see screen shot
it is pulling 11gh
I loaded zadig 8 or 9 times and it finally works .
this stick is mining on www.mmpool.org
see screen shot
it is pulling 11gh
June 11, 2015, 03:40:39 PM
Sidehack, may I ask which USB hub you're using for your Raspberry Pi ?
thanks
thanks
I got one of those $8 11-port junkers from Ebay about two years ago, stripped it down and beefed the power lines with extra wire and capacitors for running overclocked block erupters. There's pictures in the dev thread. We're thinking about building our own hub that'll take in higher than 12V and internally regulate high-current 5V to the ports, which would be good for Compac and Amita stuff but also for anyone working on a solar setup or charging a lot of devices in a car or something. So I'll probably be testing that in a month or so, but for now I have a junker hub that's been rebuilt for higher current.
Allright thanks, I was asking as I had no luck with the few usb hubs i tried. My Pi couldn't see more then 1 CP2102
(I had 8 connected) 
June 11, 2015, 02:26:28 PM
Its usually Windows Defender that is the stick in the mud between Win7 and Zadig. You need to check and see which program Defender is blocking or adjust the security level long enough to let Zadig install then place it in the allowed list within Defender. Don't forget, to get Zadig to work, you need to let the siliconlabs driver install first then run Zadig as Administrator.
Zadig has never worked on both Win7 systems I've tried to put it on in the last couple years. I have the silabs driver working fine, used it on an older cgminer for TheRealSteve's block erupter competition. But Zadig installer has never worked, and it's not because of any Windows security garbage.
What is the hashrate per chip supposed to be? I haven't been following this as closely as I have want'ed to do.
Go back up about 8-9 posts, and you'll find a table of frequency/hashrate. That's for one chip, which is what this stick has.
The U3 uses four BM1382 (same as S3/S4); the miner he's testing has a single BM1384 (same as S5) on it. The table was frequencies cgminer understands for the U3, but the listed hashrates are what the BM1384 will do with those frequencies. It's a 55-core chip, so MHz to GH/s is times 0.055
Also, if you have a Raspberry Pi, I ran five sticks off the stock cgminer in the latest Minera build without any problems. If you don't want to screw with the overly scripted and weighty web UI, just ssh into the pi and do stuff from there.
The bulk of this information is already presented in the GekkoScience BM1384 Dev thread, so don't be too surprised if it gets pared out of this review thread. But for now, there it is.
June 11, 2015, 02:42:50 PM
I've been using the BEUSB creds on that pool as a low-diff test for when I wanted to see what shares were actually coming out (and yes, the one on the hub on the Pi is pointed there now). One annoying thing with the U3 driver is the timeout; it's expecting about four times the hashrate it's actually getting so it resets the device occasionally if it hasn't seen a share for 2-4 seconds (depending on frequency). With a high-diff pool, you don't often see cgminer-reported shares, so sometimes your whole window is just "timeout reset" notices when you know the thing is submitting, typically, a couple shares a second (well below vardiff). The LED flashes with each returned share, so you know it's doing something.
June 11, 2015, 02:38:27 PM
I have the silabs driver working fine, used it on an older cgminer for TheRealSteve's block erupter competition.
I've not used suggest-diff but that's probably a good idea. Eligius starts out at 128, which this stick should see about 7 instead.
Speaking of which - I couldn't get Eligius to go below 127 when I tested it, suggest-diff be damned. Might have been user error, though. But if not, the pool that was used for that comp goes all the way down to Diff=2, and I'm gonna guess is currently seeing one of these miners hashing away quite nicely. Philip / other reviewers, if you'd like a user/pass, I'd be happy to set those up. Or see that thread for some other lower diff pools.( and yes, feel free to delete this post when the time for clean-up comes
) June 11, 2015, 02:35:21 PM
Sidehack, may I ask which USB hub you're using for your Raspberry Pi ?
thanks
thanks
I got one of those $8 11-port junkers from Ebay about two years ago, stripped it down and beefed the power lines with extra wire and capacitors for running overclocked block erupters. There's pictures in the dev thread. We're thinking about building our own hub that'll take in higher than 12V and internally regulate high-current 5V to the ports, which would be good for Compac and Amita stuff but also for anyone working on a solar setup or charging a lot of devices in a car or something. So I'll probably be testing that in a month or so, but for now I have a junker hub that's been rebuilt for higher current.
June 11, 2015, 02:25:29 PM
Sidehack, may I ask which USB hub you're using for your Raspberry Pi ?
thanks
thanks
June 11, 2015, 02:10:45 PM
What is the hashrate per chip supposed to be? I haven't been following this as closely as I have want'ed to do.
Go back up about 8-9 posts, and you'll find a table of frequency/hashrate. That's for one chip, which is what this stick has.
June 11, 2015, 02:22:44 PM
Its usually Windows Defender that is the stick in the mud between Win7 and Zadig. You need to check and see which program Defender is blocking or adjust the security level long enough to let Zadig install then place it in the allowed list within Defender. Don't forget, to get Zadig to work, you need to let the siliconlabs driver install first then run Zadig as Administrator.
Zadig has never worked on both Win7 systems I've tried to put it on in the last couple years. I have the silabs driver working fine, used it on an older cgminer for TheRealSteve's block erupter competition. But Zadig installer has never worked, and it's not because of any Windows security garbage.
What is the hashrate per chip supposed to be? I haven't been following this as closely as I have want'ed to do.
Go back up about 8-9 posts, and you'll find a table of frequency/hashrate. That's for one chip, which is what this stick has.
The U3 uses four BM1382 (same as S3/S4); the miner he's testing has a single BM1384 (same as S5) on it. The table was frequencies cgminer understands for the U3, but the listed hashrates are what the BM1384 will do with those frequencies. It's a 55-core chip, so MHz to GH/s is times 0.055
Also, if you have a Raspberry Pi, I ran five sticks off the stock cgminer in the latest Minera build without any problems. If you don't want to screw with the overly scripted and weighty web UI, just ssh into the pi and do stuff from there.
The bulk of this information is already presented in the GekkoScience BM1384 Dev thread, so don't be too surprised if it gets pared out of this review thread. But for now, there it is.
June 11, 2015, 02:17:36 PM
What is the hashrate per chip supposed to be? I haven't been following this as closely as I have want'ed to do.
Go back up about 8-9 posts, and you'll find a table of frequency/hashrate. That's for one chip, which is what this stick has.
Sidehack or Novak might have to weigh in here, but I think the table was derived by measurements from sidehack. The U3 connection is that it identifies to the driver/miner software as a U3, even though it obviously isn't a U3.
That's how I understand it, but I've been wrong before as my wife likes to say....
June 11, 2015, 02:08:54 PM
What is the hashrate per chip supposed to be? I haven't been following this as closely as I have want'ed to do.
Go back up about 8-9 posts, and you'll find a table of frequency/hashrate. That's for one chip, which is what this stick has.
June 11, 2015, 02:02:06 PM
What is the hashrate per chip supposed to be? I haven't been following this as closely as I have want'ed to do.
June 11, 2015, 02:08:13 PM
Its usually Windows Defender that is the stick in the mud between Win7 and Zadig. You need to check and see which program Defender is blocking or adjust the security level long enough to let Zadig install then place it in the allowed list within Defender. Don't forget, to get Zadig to work, you need to let the siliconlabs driver install first then run Zadig as Administrator.
June 11, 2015, 02:00:47 PM
Does anybody know if bfgminer supports the U3? It's been over 9 months since I worried about USB stick mining, and haven't kept up with support in bfgminer.
The latest version, 5.2.0, has U3 support, although there are mixed results between users.
June 11, 2015, 01:53:07 PM
Since this is using the U3 stuff in cgminer, you may want to use cgminer 4.9.0. 4.9.1 does not recognize the U3, it's a known bug, so don't know if that will affect this stick.
You probably also want to add --suggest-diff 1 to your .bat file so that your stick starts at a reasonable pool diff.
You probably also want to add --suggest-diff 1 to your .bat file so that your stick starts at a reasonable pool diff.
If it enumerated as a COM port, you need to install the WinUSB driver for hotplug support and such (Zadig) which will allow cgminer to detect it natively.
Is there a way to do this without using Zadig? I have a computer that refuses to complete the Zadig installation, so I need to find another way to do what Zadig does.yeah this win 7 is not liking zadig. I am going to strip this back.
I had a fear of this issue I have another pc to try on. and I am building a pc next week.
Phil, I run the zadig driver without issue on my Win7. I have 7 S1 blades running with that driver and some CP2102.
I think the CGminer I run was modify to be able to do that. I run CGMiner 4.7.0.
I can send you my executable if you wanna try.
Here's from the thread => https://bitcointalk.org/index.php?topic=671128.680
Quote
short summary:
we connected the antminer blades to cp2102 usb sticks, and got cgminer to mine at full speed, repo:
https://github.com/FireWalkerX/cgminer-bmsc.git
edit: compile : ./autogen.sh --enable-bmsc;make
windows:
https://www.dropbox.com/s/iuj9fz6zt8qm3q9/cgminer-bmsc.zip?dl=0
underclocked the antminers, per instructions from here:
https://bitcointalksearch.org/topic/guide-undervolt-antminer-s1-119wgh-at-the-wall-526060
i never recieved the prototype from j4bberwock, so, im guessing we will have to settle for the cp2102 usb sticks,
next, well, since it can still pay to use my s1 boards underclocked ill keep them running for now, and looking for the next project :-p
that about covers it
Hope it helps !
EDIT: Also, make sure within zadig, to install the correct winusb driver for the USB your device is connected (Go in Option => Show all Devices)
EDIT2: I guess the bmsc option won't work with the unit tho ...
June 11, 2015, 01:52:33 PM
Does anybody know if bfgminer supports the U3? It's been over 9 months since I worried about USB stick mining, and haven't kept up with support in bfgminer.
I too found the Zadig/Windows interaction to be quite frustrating. I ultimately went to the Raspberry Pi realm, which I found a bit more stable.
I too found the Zadig/Windows interaction to be quite frustrating. I ultimately went to the Raspberry Pi realm, which I found a bit more stable.
June 11, 2015, 12:47:07 PM
Since this is using the U3 stuff in cgminer, you may want to use cgminer 4.9.0. 4.9.1 does not recognize the U3, it's a known bug, so don't know if that will affect this stick.
You probably also want to add --suggest-diff 1 to your .bat file so that your stick starts at a reasonable pool diff.
You probably also want to add --suggest-diff 1 to your .bat file so that your stick starts at a reasonable pool diff.
If it enumerated as a COM port, you need to install the WinUSB driver for hotplug support and such (Zadig) which will allow cgminer to detect it natively.
Is there a way to do this without using Zadig? I have a computer that refuses to complete the Zadig installation, so I need to find another way to do what Zadig does.yeah this win 7 is not liking zadig. I am going to strip this back.
I had a fear of this issue I have another pc to try on. and I am building a pc next week.
June 11, 2015, 11:25:31 AM
Since this is using the U3 stuff in cgminer, you may want to use cgminer 4.9.0. 4.9.1 does not recognize the U3, it's a known bug, so don't know if that will affect this stick.
You probably also want to add --suggest-diff 1 to your .bat file so that your stick starts at a reasonable pool diff.
You probably also want to add --suggest-diff 1 to your .bat file so that your stick starts at a reasonable pool diff.
If it enumerated as a COM port, you need to install the WinUSB driver for hotplug support and such (Zadig) which will allow cgminer to detect it natively.
Is there a way to do this without using Zadig? I have a computer that refuses to complete the Zadig installation, so I need to find another way to do what Zadig does.could do a 'buntu run, need to give permissions to the com port though, 0224 hours here, so not up to pulling info right now, if you need it, pm me, i'll look for it about 0900
June 11, 2015, 11:17:46 AM
I've not used suggest-diff but that's probably a good idea. Eligius starts out at 128, which this stick should see about 7 instead.
The 4.9.1 compiled into the latest Minera build works fine, but I've been testing with 4.9.0 on Windows so I can verify it's good.
I think the drivers can be found external to Zadig and possibly installed manually. I've not tried. My Win7 desk machine has never taken kindly to Zadig installer.
The 4.9.1 compiled into the latest Minera build works fine, but I've been testing with 4.9.0 on Windows so I can verify it's good.
I think the drivers can be found external to Zadig and possibly installed manually. I've not tried. My Win7 desk machine has never taken kindly to Zadig installer.
June 11, 2015, 11:12:07 AM
Since this is using the U3 stuff in cgminer, you may want to use cgminer 4.9.0. 4.9.1 does not recognize the U3, it's a known bug, so don't know if that will affect this stick.
You probably also want to add --suggest-diff 1 to your .bat file so that your stick starts at a reasonable pool diff.
You probably also want to add --suggest-diff 1 to your .bat file so that your stick starts at a reasonable pool diff.
If it enumerated as a COM port, you need to install the WinUSB driver for hotplug support and such (Zadig) which will allow cgminer to detect it natively.
Is there a way to do this without using Zadig? I have a computer that refuses to complete the Zadig installation, so I need to find another way to do what Zadig does. Jump to: