Topic: Avalon ASIC users thread - page 118. (Read 438596 times)

My Avalon is in a remote room with good air temperature, but without wired network access.

I configured my Avalon so that a laptop connects to the wired interface, and the WiFi connects to my router and then the world.  The laptop can pull web pages while I am in the room with the Avalon.

These are the changes I made

1. I found a small subnet for the wired interface.

2.  I set the laptop to a static network configuration:
    Address: 192.168.0.101
    Mask      255.255.255.248
    Gateway 192.168.0.97

3.  I logged into http://192.168.0.100
    network --> WiFi
      physical settings
        lan
          unclicked "wireless network" from the bridge
      scan
        join my main router's WiFi network
        uncheck new network
        radio wan
    network --> interfaces --> lan
      Address  192.168.0.97
      Mask  255.255.255.248
      Gateway  192.168.0.2   <-- my WiFi router's address.

4.  Somewhere I set the WiFi interface to "client"  I forgot what tab that is under.
    The DHCP details give some address
      Mask 255.255.255.0
      Address Range 192.168.0.xxx
      

This lets me pull web pages for reference on my laptop while connected to the Avalon wired network, and it lets me pull the web pages on the Avalon from my other local computers.

Notice that I changed the Avalon to be 192.168.0.97, and I used the Avalon address for the Gateway on my laptop.  That is using the convention that the low address on the subnet are the router or gateway.

This isn't completely finished, as I can't see the laptop from the other computers.

ok, same problem.  let run for an additional day and still get same NMW and MWC here:



despite these mining stats:



any ideas?

edit:  oops, i may have missed something further down:



what's the difference btwn different "[Stats0,1]"?

Check to see if the f1 fuse is still onboard.

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.

hmm, so not even deleting WWAN solved error -71 for me
despite a possible correlation between temperature and occurrence of these errors, it happened now while being on 44 C, so for sure it occurs here even when "cold"

but should I worry if that happens like 10-15x per week? can it cause any real damage in the long term?

ckolivas
Cgminer (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.

It's got nowhere to go. It prepares work and then no device is working to take it so it just discards it.

Thanks! Seems to work so far.

Approx 840 shares per device in 30 hours.
840 * 24 * 2^32 / 30 / 60 / 60 ... 800MH/s

It's not the pool connection. Something happens and all work ends up "discarded" until cgminer is restarted. What would cause that?

also try deleting the WWAN.

* wifi is already disabled.
* running at a moderate 300 mhz
* other miners are connected to the pool just fine

I don't see how restarting cgminer would fix a FPGA failure. So from that list of possibilities, pool issue seems most likely. I'll set a backup pool and see if it switches to that.

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.

wait, where do you get 800MH/s?

i know the MWC's are in the 800's but those aren't hashing rates are they?  they accumulate over time....

I can watch MHS5s slowly drop to 0, and eventually cgminer-monitor will restart cgminer. Why is cgminer stopping hashing?

Well, not to be too pedantic, but my API also shows historical information ...
Just only about the current running cgminer

Those stats say 800MH/s ... so clearly that isn't expected for hashing for 30 hours ...

NMW=0 is good - may or may not be what you want - but it is of course good.

If it has been hashing for 30 hours then of course you need to post the mining stats, not what you posted, to determine what it is doing.

Matching work is simply the amount of recognised work sent back to cgminer ... not sure what you mean by "sensor"

The API log in the web interface just shows the current state of the system. Is there an actual log file somewhere else?

how about the cgminer API log?

i've taken that into account.  for some reason, on this machine, i get NMW=0 no matter how high the MWC goes.  and then the MWC never gets that high despite the Elapsed.

i know the machine is hashing and reaching the network as i'm monitoring the hashrate at the exit port, so it doesn't make sense to me.  perhaps the sensor responsible for these stats is malfunctioning?