|
Another smooth transaction/trade today. Thanks!
|
|
|
|
I finally got it working!  My PC has 2 USB controllers and it seems I've randomly picked the Intel one which doesn't work (USB 3.0). After moving the hub on the VIA controller (USB 2.0) it changed each 2Pac's location in Device Manager to something like Location 0 (Port_#0003.Hub_#0002). After that, it started to work flawlessly with all 2Pacs and all cgminer builds which were failing earlier. Yay! Awesome find. I'll link the Q&A to this post when I get back this evening. |
|
|
|
|
Sold 0.1 BTC for PayPal. Smooth TX.
|
|
|
|
PS1: tried with only 1 device instead of 3, same story.
..
Any ideas?
Thanks!
Also try one device, no hub. |
|
|
|
UPDATE:
I've tried also with build 4fc8783 of cgminer and it starts, however it gives me "failed usb_init" for all 3 sticks.
If I go to USB Management and then to List all known devices it detects them but gives the "err -3" privilege message.
Running Windows 7 x64 under admin privileges.
Something's got a lock on device before cgminer can. I've only personally seen the error in windows when two cgminer.exe are running. Here the excerpt from the README regarding windows usb install that might help: "When you first switch a device over to WinUSB with zadig and it shows that correctly on the left of the zadig window, but it still gives permission errors, you may need to unplug the USB miner and then plug it back in. Some users may need to reboot at this point." |
|
|
|
I am running 4, 2pacs on NiceHash with your Windows build. My NiceHash reports say I am running at low efficiency as I am not using the #xnsub (extranonce.subscription ). I have tried adding #xnsub in the command, but it flags a URL error. My question is, have you incorporated the NiceHash include file for extranonce in your cgminer for windows builds? Thanks for all your support! It's not and won't be. See the cgminer thread for details. Post there if you wish to discuss it. https://bitcointalk.org/index.php?topic=28402.msg10919157;topicseen#msg10919157 |
|
|
|
|
Just cutting off the red/black line back towards the hub will be sufficient.
|
|
|
|
|
I've seen the same issue splicing power into extension cables.
It went away once I minimize the distance power has to travel physically on the cable to under an inch.
On a different note for others experimenting this way:
Make sure power isn't back-feeding through the other end of the cable, you want it going only one direction.
|
|
|
|
Are there any updates in this new version that affect stability or hashrate performance?
affecting hashrate, no. stability, maybe. there's some items upstream (merged) that targets specific problems. also any new code change has a tiny chance of introducing stability negatively. there's nothing urgent in this build that you need to rush to update. so wait a few days or weeks or when you have some spare time, if everything is working for you now. |
|
|
|
i compiled the cgminer geekko for openwrt but when i do cgminer-api -o devs nothing comes up..
can someone try that and see if its me or the driver or cgminer?
edit, i should note that im using the new cgminer gekko for the old compacs..
i'll look into it. check back in 24hrs. |
|
|
|
For minimal headless Pi setup: The raspbian image creators left a FAT32 partition there for you to further configure. After you use Win32DiskImager to load the raspbian image onto the usb/micro sd. Open up the usb drive in windows (labeled boot) and drop in two file into parent folder: " ssh" - empty file, enables ssh " wpa_supplicant.conf" - enables wifi ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=US
network={
ssid="mywifi-ssid"
psk="password"
key_mgmt=WPA-PSK
}
Insert the card to your Pi, power it up. Check your router for the Pi's IP and putty into it. Cut-n-paste away. Save off the two files once you got the right combination of ssid and password in the wpa, for future image loads. |
|
|
|
Im sorry if this has already been answered before but its driving me crazy and ive trawled through 14 pages and seen nothing but a sudo command to help fix the problem which dosent help in win10.
I'm getting this error:
USB init, open device failed, err -3, you don't have privilege to access - BSC device 3:5
I've followed the setup, Im using the most recent linked bcminer, running as admin. Ive tried without extensions, with extensions. I've installed the driver using Zadig.
What have i done wrong?
Reread the "SETTING UP USB DEVICES" in the README.txt file for "WINDOWS:" to see if anything is missed. |
|
|
|
"You can order any amount you want."  Sly as a fox(miner). |
|
|
|
Ok so I was still having issues with my 2Pac failing in cgminer and cgminer disabling it. I started trouble shooting... Turns out I was using the libusb-win32 (v1.2.6.0) driver. It was working but I uninstalled it and put on the WinUSB (v6.1.7600.16385) driver and it starts and hashes but is getting libusb pipe error Trying to clear. It gets this over and over every second but it is hashing...after a few min it will die I suspect from the error. Is it possible there is still some reference to the libusb win32 driver in cgminer? I am going to reinstall it clean and try that but any info would be great. I tried searching for the error and got results but it was in the linux sections. This was interesting since I had installed the libusbk driver at one point . Here is a screen shot...  The pipe error is pointing at power, hub, or hardware. |
|
|
|
Hey vh...My cgminer wont start all of a sudden so i went to re-download and it still does the same. I also noticed that the latest one does not seem to download all the time correctly...just an fyi. Most likely an issue on my end but it is a strange coincidence.
Does it not show any devices or does it not start at all? Begin with "cgminer.exe -n" to make sure that 1) the executable runs 2) the OS is presenting the device. Then move slowly forward by removing extra parameters on run, followed by removing any intermediate hardware (ie, direct pc, no hubs, no extension cables) and test one unit only directly connected to the PC at the default frequency. |
|
|
|
Here's a cgminer preview of the three models running happily together.  And a view of them sprinting along the upper end of their voltage and frequency, with a firm amount of power and air to keep them going.  |
|
|
|
I'm running windows 7. And yes, it increased over time. That happens even when I run the two compac-1s by alone without the compac-2s. Since the increasing numbers really didn't get in the way of hashing I kind of ignored them. Are the increasing numbers due to insufficient power reaching the chips?
Thanks.
Yes. It looses communication and cgminers retries. Currently if it happens in a continuous loop (waking up and then disconnecting again), cgminer will eventually come to a halt. |
|
|
|
Just a few follow up questions: Which windows version are you using? 7/8/10? Did you happen to notice if the number/id to the left of the GSD string increase slowly over time? |
|
|
|
|
Show Posts
