Most USB miners appear to be more of a collectors item, I wouldn't believe it to be a great addition to your mining set-up. Maybe a starter piece as a bit of fun or as a learning tool.
Yeah. Well, no actually. My USB miners have replaced my GPUs. They use 2.5W rather than 200W. |
|
|
|
|
If you're planning on investing in a GPU farm, you're doing it wrong. I don't see how what you're saying is anything else. ASICs just need plugged in, if and when you get them, so no "building" required there?
Your post it too vague to be interesting to anyone, really.
|
|
|
|
|
No, you don't. Just use a dynamic DNS service like no-ip or dyndns.
I use no-ip.biz - it's free, and my router has a no-ip.biz client built in, so always updates the IP without my intervention.
|
|
|
|
|
Don't run cgminer out of a folder on the desktop. You run in to Windows permissions issues, which can bugger up cgminer.
Move the cgminer folder to the root of a drive, and run it from there, it'll work.
|
|
|
|
When your btc mining with 11.x drivers you should not anything plugged in, at least with windows. I only had to start plugging 1 into the main card when I started using 7900 series cards with newer drivers.
You're finding the total opposite to everyone else. Older 11.x need dummies, 12.x and 13.x don't. |
|
|
|
We all know the rule:
You need to plug something into each GPU in your rig so that each cards thinks that it is plugged into a monitor and does not get shut down by the system.
Is this needed for all OS/GPU/mobo combinations or are there some that do not need this?
The folding at home guys seem to have solved this in their software and can force all GPUs to be on whether or not they are connected to a monitor.
Do we really need to keep on with the VGA dongles or can we just fix this with some mods to our mining software?
It's not a rule. You don't. No. No, only if you're using ancient, outdated drivers. Nothing to do with hardware. What? No. Just install drivers released in the last two years and you don't need dummy plugs. I've never run a dummy plug on any of my cards (5870, 6970, 7770, 7850, 7950), and NONE of those have ever had a monitor plugged in to them. Or a dummy plug. The machines have always been using Intel iGPU for display, the ATI GPUs have been doing nothing but mining. |
|
|
|
Yep, forgot that - both miners are coming on leaps and bounds in support for ASICs.  |
|
|
|
and i was thinking u just signed up on the forum .... how can u ask that with activity 185 ? LOL
All TX and no RX, probably.  |
|
|
|
Well it is slightly more work initially, despite what kano says, but you run zadig as administrator, plug in ONE device, wait till windows finishes fscking around with it, then tell zadig to change that device to winusb (that's all the extra work there is). Then you don't need to specify any command line options for cgminer to recognise and use the device, and any time you plug in any other device of the same kind from then on forever more, it will run, including without restarting cgminer since it will hotplug them.
Finally, someone with some sense.  I still prefer the new bfgminer interface (Blue bits!), and pool prioritization facility (rather than the plain old Failover etc of cgminer).  |
|
|
|
(Zadig) that all but the inept can follow.
That's not really true, is it? WinUSB and zadiag is an unnecessary complication. And an unreliable one at that. VCP drivers, as I said above, are so simple anyone can get those working. It's a 2 second install, wait for the sticks to be installed, run miner. No Well, yes actually.  I don't understand? It really is as simple as running the VCP driver installer (double click, press next, press finish). Plug in hub. Plug in Erupters. Wait a few minutes until Erupters are assigned COM port. Run bfgminer with -S erupter:all flag, job done. That's literally from a fresh install of Windows. No other driver. How can running zadiag and changing drivers per stick and all that jazz possibly be easier that doing nothing? My mind is literally boggling as to how you think all those extra steps are easier than one step. |
|
|
|
|
Or you could:
1. Download bfgminer
2. Download VCP drivers
3. Install VCP drivers by double clicking the setup program
4. Plug in your hub and miners
5. Run bfgminer
Awful, awful lot easier.
|
|
|
|
|
Wow, you're only the tenth person to ask, and the answer is still no.
They're a chip designed to do one thing, and one thing only. That's mine Bitcoins (or other pointless SHA256 altcoins).
|
|
|
|
|
Not required on bfgminer 3.1.4 now - just use -S erupter:all instead.
|
|
|
|
(Zadig) that all but the inept can follow.
That's not really true, is it? WinUSB and zadiag is an unnecessary complication. And an unreliable one at that. VCP drivers, as I said above, are so simple anyone can get those working. It's a 2 second install, wait for the sticks to be installed, run miner. |
|
|
|
Tried bfgminer? Works better for me with my little Erupters.
What driver do you use for the erupters with BFGMiner? I have tried WinUSB (zadig) and the Silicon Labs CP210x drivers, and BFGMiner refuses to see either. Get rid of WinUSB. Just use the VCP drivers for bfgminer - it'll work if you see your BEs being assigned a COM port in Windows. The WinUSB drivers are, in my opinion, a HUGE mistake that the cgminer folks have made. It's unnecessarily difficult to get working, and gives no real benefit. The VCP drivers are a 2 second install, and they just work (or at least have for me on a few different machines on Server 2012, Win7 and Win8. |
|
|
|
|
Tried bfgminer? Works better for me with my little Erupters.
|
|
|
|
|
Are you using the latest 13.2 version of p2pool? Didn't 13.1 have issues with Avalons? Or was that something different?
|
|
|
|
|
Looks like slush is too busy with his Trebor or whatever it's called. Pool seems to be limping along on it's own, and doing a bad job of it.
|
|
|
|
Is there anyone running an OC'd four module Avalon on p2pool?
I seem to get the same hashrate (90GH) at 325 as I do at 300, except with more heat and noise.
And I don't think it's a problem with power or cooling because if I switch to a different pool it hashes at around 105GH.
What's your GetBlockLatency like? How fast is the machine running p2pool? To me (not having anywhere near that hashing power) it seems like p2pool isn't able to provide work fast enough? If you want, you could point your miner at my node for a few minutes (0.25% fee) and see what it reports? http://847pool.no-ip.biz:9332 |
|
|
|
|
Show Posts
