HellDiverUK
|
|
November 25, 2013, 08:33:47 AM |
|
I don't see any problem, apart from some missing lacquer, which probably came off when you were removing the resistors.
|
|
|
|
tk1337
|
|
November 25, 2013, 08:56:48 AM |
|
I don't see any problem, apart from some missing lacquer, which probably came off when you were removing the resistors.
I really doubt that, as cautious as I was being, with low air-speed and semi-low heat (enough to get the solder going) on with rework station. No soldering irons were used to get these off, everything was done pretty precision, also, not to mention the one from earlier today, you could see the under the resistor enough to already see where the pad was extended to almost the other pad before anything was done to it.
|
|
|
|
kabopar
|
|
November 25, 2013, 10:28:31 AM |
|
tk1337, Thanks for this update. I share the appreciation of the Big Picture team and others behind the BitFury based USB miners, hoping that they will improve in future production runs. It is understandable that with the time pressures and small production run such quality 'bugs' can occur. If the copper tracks had incorrect dimensions on some boards causing partial shorts, that could also be production quality issue that needs to be addressed for the future runs. It is great that you managed to revive the non-performing sticks and uncovered these additional issues in the process.
Cheers
|
|
|
|
wunch
Newbie
Offline
Activity: 49
Merit: 0
|
|
November 25, 2013, 10:33:40 AM |
|
I've put up a new version of cgminer, 3.8.1 with improvements to the blue/red fury devices.
Any idea why i get this errors on BF1s ? [2013-11-12 23:08:58] Hotplug: bitfury added BF1 5 [2013-11-12 23:08:58] BF1 5 BF1RequestWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT [2013-11-12 23:08:58] BF1 5: Device disappeared, disabling thread [2013-11-12 23:08:58] BF1 5 failure, disabling!
And it is random on time and also on device. I run cgminer 3.8.1 on Debian 7.1. It is not runing on RPi. There is no pencil mod. There are 5 BEs and 5 BF1s, each od them on its own USB hub ( 3,5A powered). It was try with connection of hubs into cascade ( BF1s hub connected to BEs hub and this to computer) and also try to connect hubs directly to computer and always the same result. If i reset BF1s with reset switch on board it comes back. Today i "upgraded" to version 3.8.3 and i still get this LIBUSB error: [2013-11-23 12:12:24] Hotplug: bitfury added BF1 8 [2013-11-23 12:12:38] BF1 8 BF1RequestWork usb write err:(-7) LIBUSB_ERROR_TIMEOUT [2013-11-23 12:12:38] BF1 8: Device disappeared, disabling thread [2013-11-23 12:12:38] BF1 8 failure, disabling!
Does anyone else have this issue ? If the device disappears and shows up as ZOMBIE and never re-hotplugs, there's nothing there on the USB any more for cgminer to talk to, so something is causing USB flakiness there. Check what 'dmesg' shows you after this has happened. There's not much the software can do if the device is effectively disappearing from the USB hub. If on the other hand the device is still there and it's just cgminer dropping out, it's possible that cgminer is too trigger happy - but if that were the case it would re-hotplug soon after. Hi ckolivas I get this problem on a windows x64 machine. Devices are a mixture blue/red fury and will randomly Zombie. I have tried everyhting to rule out flaky USB (Zadig, diffrent hub, unplugging anything usb except keyboard/mouse etc) and i am currently running 4 on there own Orico hub. They will zombie out and not come back but still show as being present in device manager/ devices. If i power cycle the hub (it has a nice switch at the front) they come back as normal. Hope this info helps and thanks for your hard work!
|
|
|
|
mchu168
|
|
November 25, 2013, 05:53:14 PM |
|
Has anybody run into a limitation on the number of Blue/Red Fury's that can be run on one PC Client?
I've run into a 32 device limit on Ubuntu 13.10 and BFGMiner 3.5.3. I get a error message on boot up that says something like "no more free ACM devices).
On Windows 8, I can't get BFGMiner 3.6 to recognize more than 48 sticks. Windows shows more than 48 COM devices, but BFGMiner will not find them with auto probe.
I have a bunch of 49 port hubs but I'm running out of PCs!
|
|
|
|
-ck
Legendary
Offline
Activity: 4242
Merit: 1644
Ruu \o/
|
|
November 25, 2013, 07:45:52 PM |
|
Hi ckolivas
I get this problem on a windows x64 machine. Devices are a mixture blue/red fury and will randomly Zombie. I have tried everyhting to rule out flaky USB (Zadig, diffrent hub, unplugging anything usb except keyboard/mouse etc) and i am currently running 4 on there own Orico hub. They will zombie out and not come back but still show as being present in device manager/ devices. If i power cycle the hub (it has a nice switch at the front) they come back as normal.
Hope this info helps and thanks for your hard work!
Try this binary for windows instead then please: http://ck.kolivas.org/apps/cgminer/temp/cgminer-fff.exe
|
Developer/maintainer for cgminer, ckpool/ckproxy, and the -ck kernel 2% Fee Solo mining at solo.ckpool.org -ck
|
|
|
AndrewHenson
Newbie
Offline
Activity: 22
Merit: 0
|
|
November 25, 2013, 09:05:23 PM |
|
Hello,
I just received my RedFury in the post today, I watched the youtube video and this worked first time. Does anyone have any instructions on how to reprogram the rom and compile the rom source so I can have a play with it. I am using windows, which might be a problem. However if I need to switch to linux I have a spare laptop I can use.
thanks
Andrew
|
|
|
|
kabopar
|
|
November 26, 2013, 04:32:43 AM |
|
Hello,
I just received my RedFury in the post today, I watched the youtube video and this worked first time. Does anyone have any instructions on how to reprogram the rom and compile the rom source so I can have a play with it. I am using windows, which might be a problem. However if I need to switch to linux I have a spare laptop I can use.
thanks
Andrew
The OP of this thread has instructions how to reflash the device https://bitcointalk.org/index.php?topic=319419.0. This maybe what you are looking for. (It's the target binary file for the micro-controller running the Red Fury (which is supposed to be identical to the Blue Fury, except for pcb/heat sink color scheme)). Cheers
|
|
|
|
eRRoRist
Newbie
Offline
Activity: 19
Merit: 0
|
|
November 26, 2013, 05:11:05 AM |
|
What do you guys think would be a safe amount of overclocking for the BFs? Is over 3GH safe if I have enough cooling?
|
|
|
|
sebdude420
|
|
November 26, 2013, 07:01:05 AM |
|
Anyone got extra replacement resistors on hand?
|
OG Bitcoin Miner turned Proof of Stake Validator. Maxed out Raspberry Pi 4 8GB at 120$ a Day Revenue with ~15K XTZ Bonds in Summer of 2021. Looking at Proof of Stake systems all across the crypto ecosystem to expand operations.
|
|
|
MaxGen
Member
Offline
Activity: 79
Merit: 10
|
|
November 26, 2013, 02:20:56 PM |
|
Failed to initialize (incorrect device?)
Plugged in my 2 new Blue Fury's last night and they were hashing normally. Went to bed and woke up to 2 ZOMBIE's. Restarted cgminer 3.8.2 and I get the failed to initialize error.
Tried pressing the reset button and re socketing them in the hub. Can't get past this error.
I haven't read every page of this thread, but I will if necessary, will I find the answer here? Is this a common problem?
Thanks,
|
|
|
|
Mudbankkeith
|
|
November 26, 2013, 02:27:15 PM |
|
Failed to initialize (incorrect device?)
Plugged in my 2 new Blue Fury's last night and they were hashing normally. Went to bed and woke up to 2 ZOMBIE's. Restarted cgminer 3.8.2 and I get the failed to initialize error.
Tried pressing the reset button and re socketing them in the hub. Can't get past this error.
I haven't read every page of this thread, but I will if necessary, will I find the answer here? Is this a common problem?
Thanks,
Try BFG
|
BTc donations welcome:- 13c2KuzWCaWFTXF171Zn1HrKhMYARPKv97
|
|
|
Atomar
|
|
November 26, 2013, 02:38:13 PM |
|
I had with bfg for Windows and bfg in Minepeon no Problem!
|
|
|
|
NorbyTheGeek
|
|
November 26, 2013, 03:34:16 PM |
|
Failed to initialize (incorrect device?)
Plugged in my 2 new Blue Fury's last night and they were hashing normally. Went to bed and woke up to 2 ZOMBIE's. Restarted cgminer 3.8.2 and I get the failed to initialize error.
Tried pressing the reset button and re socketing them in the hub. Can't get past this error.
I haven't read every page of this thread, but I will if necessary, will I find the answer here? Is this a common problem?
Thanks,
Try BFG Absolutely. I never could get cgminer to work quite right, so I went back to bfgminer.
|
|
|
|
mogrith
Legendary
Offline
Activity: 1470
Merit: 1001
Use Coinbase Account almosanywhere with Shift card
|
|
November 26, 2013, 06:31:51 PM |
|
note that if you go to BFG you will need to change drivers
|
|
|
|
teletobi
|
|
November 26, 2013, 11:00:47 PM |
|
After running my remaining 12 BFs for some weeks fine with 1.900 to 2.800 GH, I have trouble since about a week. They are hashing for about 5 to 10 Minutes and then they are Zombies. I already bought other PSUs and Hubs and am running a fresh and clean git pulled Minepeon 0.2.4. It doesn't matter if there is 1 or 5 in a Hub (each Hub with at least 3A PSU, No Hub with more than 5 Units). I even changed the Multi socket (is it called so?) where the PSUs are plugged in. Does any only have an idea? I can't believe they are all faulty...
|
|
|
|
Mudbankkeith
|
|
November 26, 2013, 11:03:18 PM |
|
After running my remaining 12 BFs for some weeks fine with 1.900 to 2.800 GH, I have trouble since about a week. They are hashing for about 5 to 10 Minutes and then they are Zombies. I already bought other PSUs and Hubs and am running a fresh and clean git pulled Minepeon 0.2.4. It doesn't matter if there is 1 or 5 in a Hub (each Hub with at least 3A PSU, No Hub with more than 5 Units). I even changed the Multi socket (is it called so?) where the PSUs are plugged in. Does any only have an idea? I can't believe they are all faulty...
Minepeon CG or BFG
|
BTc donations welcome:- 13c2KuzWCaWFTXF171Zn1HrKhMYARPKv97
|
|
|
philipma1957
Legendary
Offline
Activity: 4270
Merit: 8627
'The right to privacy matters'
|
|
November 26, 2013, 11:10:14 PM |
|
After running my remaining 12 BFs for some weeks fine with 1.900 to 2.800 GH, I have trouble since about a week. They are hashing for about 5 to 10 Minutes and then they are Zombies. I already bought other PSUs and Hubs and am running a fresh and clean git pulled Minepeon 0.2.4. It doesn't matter if there is 1 or 5 in a Hub (each Hub with at least 3A PSU, No Hub with more than 5 Units). I even changed the Multi socket (is it called so?) where the PSUs are plugged in. Does any only have an idea? I can't believe they are all faulty...
I am getting some more red furies on fri. mine work great on windows 7 and with bfg. if you want to lend me a bad stick I could run it on my system see if I get better results. I am in New Jersey. I would try putting 1 of them on real pc use bfg use cg even use bit minters java code. compare results. remember a pi is basically a toss away piece of gear. at least try 2 or more mining clients. on your gear.
|
|
|
|
tk1337
|
|
November 26, 2013, 11:37:39 PM |
|
After running my remaining 12 BFs for some weeks fine with 1.900 to 2.800 GH, I have trouble since about a week. They are hashing for about 5 to 10 Minutes and then they are Zombies. I already bought other PSUs and Hubs and am running a fresh and clean git pulled Minepeon 0.2.4. It doesn't matter if there is 1 or 5 in a Hub (each Hub with at least 3A PSU, No Hub with more than 5 Units). I even changed the Multi socket (is it called so?) where the PSUs are plugged in. Does any only have an idea? I can't believe they are all faulty...
Under CGMiner 3.8.3 they seem to Zombie a lot (not just on the rPi either)... ck made a change to make CGMiner 3.8.3 "less trigger happy" in regards to the issue with lsusb and the units going Zombie, however since he made that change (a few days ago?) I haven't recompiled CGMiner 3.8.3 from github to try it out. (Other people have reported this issue in 3.8.1, but I have not personally seen it.) I've got 15 running all at 2.5GH/s - 3.10GH/s all below 4% error rate with BFGMiner 3.6.0 (along with a BFL Jally & 20 erupters). Uptime on the miner is more than a couple of days now, which is only because I took off the Fury units to replace the resistors. So to the person stating that the rPi could be/is at fault, would be an incorrect statement, as there are many factors involved.
|
|
|
|
OleOle
|
|
November 27, 2013, 12:06:19 AM |
|
remember a pi is basically a toss away piece of gear.
Haha! That made me laugh, thanks for that
|
|
|
|
|