Avalon ASIC users thread

[flyonwall]

Sorry if this has been asked already:

Is it possible to run just wired (ethernet, no WAN)? I tried disabling the WAN hoping the packets would route through ethernet, no dice.

--S

It is possible. You need to reserve a fixed IP address on your home router, then connect the WR703N through an Ethernet port (most WiFi routers come with extra Ethernet ports). The WR703N has a fixed IP address (I believe it's 192.168.0.100). Once you do this, I believe you can also connect to the WR703N though your home WiFi router.

Here's a sample setup: http://www.kraterminer.com

[1714997766]

1714997766

[1714997766]

1714997766

[koxman]

Same problem here.

You have to disable wifi interface. This will unload kernel module I think. Deleting wifi interface will not help. Since than several days uptime @ 340Mhz.

So you can keep wifi network device but in menu Network->Wifi disable the device.

I think this has something to do with unattached wifi antena. I havent tried it but its possible that this problem will disappear with attached wifi antena even when not using wifi.

[Syke]

My cgminer is restarting too frequently. Is there a log showing why it was restarted?

[cypherdoc]

My cgminer is restarting too frequently. Is there a log showing why it was restarted?

System Log.

try a hard reboot.

[kano]

i'm puzzled why my NMW and MWC are both so low even after being up for over 30 hours.  and NMW 0?

https://i.imgur.com/CnyGxSV.png

... check Elapsed ... if it reboots or cgminer restarts, of course it wont add up to 30 hours of mining

[Syke]

My cgminer is restarting too frequently. Is there a log showing why it was restarted?

System Log.

try a hard reboot.

syslog is simply showing that cgminer-monitor is running regularly. It doesn't show why cgminer died/restarted.

[cypherdoc]

i'm puzzled why my NMW and MWC are both so low even after being up for over 30 hours.  and NMW 0?

https://i.imgur.com/CnyGxSV.png

... check Elapsed ... if it reboots or cgminer restarts, of course it wont add up to 30 hours of mining

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?

[cypherdoc]

My cgminer is restarting too frequently. Is there a log showing why it was restarted?

System Log.

try a hard reboot.

syslog is simply showing that cgminer-monitor is running regularly. It doesn't show why cgminer died/restarted.

how about the cgminer API log?

[Syke]

how about the cgminer API log?

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

[kano]

i'm puzzled why my NMW and MWC are both so low even after being up for over 30 hours.  and NMW 0?

https://i.imgur.com/CnyGxSV.png

... check Elapsed ... if it reboots or cgminer restarts, of course it wont add up to 30 hours of mining

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?

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"

[kano]

how about the cgminer API log?

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

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

[Syke]

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

[cypherdoc]

i'm puzzled why my NMW and MWC are both so low even after being up for over 30 hours.  and NMW 0?

https://i.imgur.com/CnyGxSV.png

... check Elapsed ... if it reboots or cgminer restarts, of course it wont add up to 30 hours of mining

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?

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"

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....

[-ck]

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.

[Syke]

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.

* 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.

[cypherdoc]

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.

* 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.

also try deleting the WWAN.

[Syke]

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

[kano]

i'm puzzled why my NMW and MWC are both so low even after being up for over 30 hours.  and NMW 0?

https://i.imgur.com/CnyGxSV.png

... check Elapsed ... if it reboots or cgminer restarts, of course it wont add up to 30 hours of mining

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?

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"

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....

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

[snaxion]

Same problem here.

You have to disable wifi interface. This will unload kernel module I think. Deleting wifi interface will not help. Since than several days uptime @ 340Mhz.

So you can keep wifi network device but in menu Network->Wifi disable the device.

I think this has something to do with unattached wifi antena. I havent tried it but its possible that this problem will disappear with attached wifi antena even when not using wifi.

Thanks! Seems to work so far.

[-ck]

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.