Avalon ASIC users thread - page 118.

cypherdoc

legendary

Activity: 1764

Merit: 1002

Quote from: bitdude on July 14, 2013, 04:56:05 AM

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?

Check to see if the f1 fuse is still onboard.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: demkd on July 14, 2013, 04:50:20 AM

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? Huh

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.

bitdude

sr. member

Activity: 277

Merit: 254

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?

demkd

full member

Activity: 242

Merit: 100

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? Huh

At any other pool I have 0.2-0.3% normal reject rate.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: Syke on July 14, 2013, 12:56:44 AM

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.

snaxion

newbie

Activity: 41

Merit: 0

Quote from: koxman on July 13, 2013, 04:46:38 PM

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

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: cypherdoc on July 13, 2013, 11:04:42 PM

Quote from: kano on July 13, 2013, 10:50:34 PM

Quote from: cypherdoc on July 13, 2013, 10:45:08 PM

Quote from: kano on July 13, 2013, 10:41:11 PM

Quote from: cypherdoc on July 13, 2013, 04:08:30 PM

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

http://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 Tongue

Syke

legendary

Activity: 3878

Merit: 1193

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

cypherdoc

legendary

Activity: 1764

Merit: 1002

Quote from: Syke on July 13, 2013, 11:19:19 PM

Quote from: -ck on July 13, 2013, 11:09:47 PM

Quote from: Syke on July 13, 2013, 11:01:32 PM

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

legendary

Activity: 3878

Merit: 1193

Quote from: -ck on July 13, 2013, 11:09:47 PM

Quote from: Syke on July 13, 2013, 11:01:32 PM

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.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: Syke on July 13, 2013, 11:01:32 PM

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.

cypherdoc

legendary

Activity: 1764

Merit: 1002

Quote from: kano on July 13, 2013, 10:50:34 PM

Quote from: cypherdoc on July 13, 2013, 10:45:08 PM

Quote from: kano on July 13, 2013, 10:41:11 PM

Quote from: cypherdoc on July 13, 2013, 04:08:30 PM

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

http://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....

Syke

legendary

Activity: 3878

Merit: 1193

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

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: Syke on July 13, 2013, 10:49:09 PM

Quote from: cypherdoc on July 13, 2013, 10:47:26 PM

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 Tongue

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: cypherdoc on July 13, 2013, 10:45:08 PM

Quote from: kano on July 13, 2013, 10:41:11 PM

Quote from: cypherdoc on July 13, 2013, 04:08:30 PM

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

http://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"

Syke

legendary

Activity: 3878

Merit: 1193

Quote from: cypherdoc on July 13, 2013, 10:47:26 PM

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?

cypherdoc

legendary

Activity: 1764

Merit: 1002

Quote from: Syke on July 13, 2013, 10:44:41 PM

Quote from: cypherdoc on July 13, 2013, 09:56:29 PM

Quote from: Syke on July 13, 2013, 09:52:39 PM

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?

cypherdoc

legendary

Activity: 1764

Merit: 1002

Quote from: kano on July 13, 2013, 10:41:11 PM

Quote from: cypherdoc on July 13, 2013, 04:08:30 PM

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

http://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?

Syke

legendary

Activity: 3878

Merit: 1193

Quote from: cypherdoc on July 13, 2013, 09:56:29 PM

Quote from: Syke on July 13, 2013, 09:52:39 PM

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.

kano

legendary

Activity: 4634

Merit: 1851

Linux since 1997 RedHat 4

Quote from: cypherdoc on July 13, 2013, 04:08:30 PM

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

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

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

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