 |
May 31, 2014, 06:45:21 PM Last edit: June 01, 2014, 05:56:30 AM by Sonicprince |
|
Hi All,
Some notes that might help others with NanoFury/Yellowjacket oddities when run with other devices.
I reinstalled WinXP today on my old laptop with a new harddisk to a) give me more room for BitcoinQT, and b) seemed like a good time anyway, it also rules out any other problems behind my problem with starting order of USB devices.
I've been having a problem with BFGMiner v3.10.x and now v4.0.0, If I simply plug all my USB devices in, and ensure that WinXP picks them all up in Device Manager, I end up with a mess, the BEE's (and sometimes the BIF) are never found by BFGMiner when its started with the NFY's already plugged in, and the NFY's are found very errratically. I had BEE's, BPM's, NFY all plugged into one USB2 hub (no plugs, direct soldered leads to an excellent switchmode supply), and a BIF which I have plugged into a USB3 hub.
Turns out the NFY's don't like starting up at the same time as Block Eruptors (BEE's) and BPM's (that's right, not the BIF), so I've put BEE's, BPM's, and BIF on the USB3 hub, and put all my NFY's on the USB2 hub. For NFY's think NanoFury's/Yellowjackets.
Solution that works all the time.
Start BFGMiner with only the USB3 hub and all BEE's, BPM's and BIF are found and started, then I plug in the USB2 hub, 1 or 2 NFY's are automatically found, within a few minutes the rest of the NFY's are then found. (I normally do a "M + auto" in BFGMiner as I'm impatient)
I have tried different hubs, with the same results, I haven't looked further as I don't have any debug/trace tools for Windows, this is the only thing with windows on it in this house as we aren't windows people but at least it give the old laptop a reason for being.
Cheers
(edited, I deleted the wrong bit when originally writing this)
|