I get a REALLY large number of invalid shares with my Avalon.
I'm not sure whats going on. It's not consistent.
One day I'll be mining and I'll get 99+% valid shares and the next day or two it will only be 88% valid shares.
I've tried mining on Ozcoin and 50btc and it seems to be bad on both.
I don't think it is my network because my jalapenos only get <1% invalid shares.
I'm using the dynamically adjusting frequency and it usually settle at about 352 MHz or so and 82 GH/s on average. Of course, according to the pool, I'm only getting 70 GH/s or so due to all the invalid shares.
I have an AC feeding directly into the intake on the Avalon and no temperature gets above 48 or 49 or so (very rarely 50).
What could be wrong?
This is normal on stratum. Every time the block changes, you get invalids. Some days burn more blocks than others. It seems like I have way more than other Avalon users, at least from what I've seen on Ozcoin. Most of them have only a couple percent invalid shares at most, while I will have 12 or 13% invalid shares. Right now I'm standing at about 94% efficiency on average, that's with 400,000 invalid shares in the less than a week I've been mining there. That is definitely far more than you should be getting. There is a good chance you're submitting heaps of duplicates which may also be a different form of instability that the auto mode can't check for. Try setting a lower maximum speed if you're using auto mode because clearly you're not doing 82GH of useful work. |
|
|
|
It's highly likely that your hub can not provide enough power for 33 USB block eruptors simultaneously. In fact, from your experiments, it seems to not be able to provide enough power for more than 7 at a time. What power levels is it rated at? Each block eruptor will need 0.5 - 0.6 Amps.
Power Supply is fine, coming from Win7 where they work. Sparkle 400 is 30A@5v. Thanks! They're all hashing.
10890Mhs/333Mhs=32.7
Exactly. It's driving me nuts that there's no work! If your usb hub is a usb2 hub and not a usb3 hub you will be far better off moving to the latest version of cgminer instead. The only reason to stick with the old version of cgminer is if you have multiple usb1.1 devices on a usb3 hub for there remains an instability there that we've been unable to debug so far. |
|
|
|
Why would I be needing to run as root even after changing /dev/ttyUSB0 to 777? pi@raspberrypi ~/bin $ sudo chmod 777 /dev/ttyUSB0
pi@raspberrypi ~/bin $ ./cgminer-3.3.0a -n
[2013-07-15 19:59:34] USB all: found 4 devices - listing known devices
.USB dev 0: Bus 1 Device 4 ID: 10c4:ea60
** dev 0: Failed to open, err -3
[2013-07-15 19:59:34] 1 known USB devices
pi@raspberrypi ~/bin $ sudo ./cgminer-3.3.0a -n
[2013-07-15 19:59:38] USB all: found 4 devices - listing known devices
.USB dev 0: Bus 1 Device 4 ID: 10c4:ea60
Manufacturer: 'Silicon Labs'
Product: 'CP2102 USB to UART Bridge Controller'
[2013-07-15 19:59:38] 1 known USB devices
pi@raspberrypi ~/bin $
cgminer no longer uses ttyUSB0 so you're changing permissions on an interface cgminer doesn't use. See the relevant readme instead (FPGA-README or ASIC-README). |
|
|
|
Sorry, couldn't resist. You didn't deserve that comeback  |
|
|
|
|
I used to get 1200W of heat from my GPU rig which mined 2.7GH of bitcoin. Now I get 1200W of heat from my ASICs mining 200GH of bitcoin.
|
|
|
|
|
This is all opinion based...
I estimate based on finding 5 blocks on average per difficulty change to avoid the variance of missing blocks before a diff rise in a way that can never be recovered. That's 5 out of 2016 blocks so you need to be >= .25% of the total network hashrate. At (current) difficulty 26 million, you need to generate 5 * 26 million shares in less than 2 weeks, or 26 million shares every 403 blocks which is ~4030 mins (in reality less time because diff is rising). That's ~6500 shares per minute. You get 1 share per 71.6MH per minute, so you'll need ~6500 * 72 = 470GH. One BFL SC minirig therefore is about the minimum requirement (this week).
Not only do you need a ludicrous amount of hashrate to reach that milestone, it gets increasingly difficult to set up an efficient solo operation as the network hashrate increases. Even the most hardcore miners gave up solo mining for any extended period for the risks are too great with such a large investment.
Summary: Pool mine.
|
|
|
|
Con, what is the appropriate NMW/MWC ratio?
No such thing as "appropriate" as it's just another hardware error. If your hashrate is okay, it's okay. You can read a few pages ago about how I chose the "appropriate" hardware error target rate of <2%. |
|
|
|
I'm assuming your talking about dynamic mode? If so it's not an error. Dynamic mode adjusts your GPU in an attempt to keep your desktop GUI responsive so you can use your computer while mining. Dynamic mode only uses one thread instead of the default 2 so it's disabling the unused one. --intensity|-I <arg> Intensity of GPU scanning (d or -10 -> 10, default: d to maintain desktop interactivity) Thank you. But I can not receive any "accept" when this message appear. You're going to have to give a lot more information then before we can help you. |
|
|
|
|
Have other pools lost interest in implementing reconnect support?
|
|
|
|
what's the difference btwn different "[Stats0,1]"?
You found it then. At some stage the avalon disconnects due to some USB issue and cgminer automatically hotplugs it. Since it's newly hotplugged it comes up as a new device (ava1 instead of ava0). |
|
|
|
Precisely 14 microseconds after the first one of these is actually delivered, the price of the Asicminer product will magically drop to match it in price/performance. |
|
|
|
Hi, I've finally given up on trying to find out what I'm doing wrong with connecting to 50btc. Here's my cgminer.conf file. It's an exact copy of another one that works fine, just with btcoxygen in stead of 50btc. Running on Raspbian with USB Erupters I just get the same error: [2013-07-14 15:33:16] ./cgminer: --config: JSON decode of file '/home/pi/cgminer-3.1.1/cgminer.conf' failed '}' expected near '*' I hope someone can help. Thanks Your password is confusing the conf file reader with the asterisk (*) there. Change your password to something without an asterisk or learn how to escape the asterisk in a json compatible way. |
|
|
|
ckolivasCgminer (07/03 firmware) submit "stale" shares to a pool or discard it by default? I found that mmpool have incredible low reject rate 0.0022% (64/2862167 diff1 and fixed difficulty = 32) but have "stale" ~0.17% (5216/2862167 diff1) so my "stale" shares accepted by pool or not?  At any other pool I have 0.2-0.3% normal reject rate. Cgminer submits stale shares unless you use --no-submit-stale. Some pools accept stale shares for some period after the block has changed to fake it looking like their stale rate is lower than other pools. Overall since they accept the same proportion of stales from everyone, no one actually gets paid more, it's just marketing. |
|
|
|
It's not the pool connection. Something happens and all work ends up "discarded" until cgminer is restarted. What would cause that?
It's got nowhere to go. It prepares work and then no device is working to take it so it just discards it. |
|
|
|
I can watch MHS5s slowly drop to 0, and eventually cgminer-monitor will restart cgminer. Why is cgminer stopping hashing?
Common reasons: Wifi kernel problem Overdoing the overclocking Pool failure and the cgminer-monitor watchdog is trigger happy and kills cgminer when all it's doing is waiting for a pool to come back online. FPGA failure in the avalon. For maximum stability while I'm away, I limited my batch 2 overclock to 333 and it's been up for a week. At 350 it would restart cgminer every 12 hours and eventually after a few days would restart the entire router. |
|
|
|
is 1 instance of cgminer USB Erupters only mining for BTC and an additional instance of cgminer GPU only mining scrypt possible on the same PC? Yes |
|
|
|
|
Only 15 of the 16 engines in each chip can be used with the current design so you can't enable engine 0. If you try to enable it, you will be unable to run more than one chip so you'll be limited to ~4.5GH.
|
|
|
|
|
Older SDKs no longer produce valid shares with newer drivers.
|
|
|
|
I have the issue of not having opencl drivers and not being able to get those drivers to work. That won't matter right?
Correct. There is a cgminer binary built that doesn't need the opencl drivers. (cgminer-nogpu). |
|
|
|
|
Besides mining cryptocoins, they make great bookends, paperweights, doorstops and coffee table ornaments.
They only do a specific subset of sha256 twice on specific data types and return specific results only, so they're not useful for absolutely anything else for their computational ability.
|
|
|
|
|
Show Posts
