Topic: Newbie miner:Please help with avalon 200ghs miner. £25 or $40 donation on offer (Read 7361 times)

If your fans dont start thats not good something fusing or blown

Do they turn a little then stop when you power it up?

Ive changed the power supply and still doenst work

Sorry I found the answer about DHPC, hope to get throug... it worked 2 days than stopped... could be because of fans? Seems to be too hot, when I touch it can't keep the finger on main board...

Hi, I have the same problem... trying to solve but being newbie isn't easy... what is DHPC ? 
Thanks

My fans dont start , they dont make noise or anithyng theres just this red led light. Please help , i will pay 0.5 BTC if i get help and it starts, thank you.
On the api log says :

[Firmware Version] => 20131118
cgminer: 176747f
cgminer-openwrt-packages: 0e12b1b
luci: 346e3e7+
Socket connect failed: Connection refused

 I cant enter now to the miner , i entered i changed the ipv4 to 192.168.1.102 and i can enter , when i enter i get a black page that says luci interface and inmediatly goes to internet explorer cannot display the webpage.
I put this exact same numbers, instead of ipv4 192.168.1.100 i put 192.168.1.102
https://ip.bitcointalk.org/?u=http%3A%2F%2Foi43.tinypic.com%2F30955zq.jpg%5B%2Fimg%5Bimg%5Dhttp%3A%2F%2Foi40.tinypic.com%2Fqs09lk.jpg&t=537&c=EzDOY4phGofTxA





Internet Explorer cannot display the webpage
 


 



 


What you can try:
 


 







Diagnose Connection Problems

 


 







More information



This problem can be caused by a variety of issues, including:
•Internet connectivity has been lost.
•The website is temporarily unavailable.
•The Domain Name Server (DNS) is not reachable.
•The Domain Name Server (DNS) does not have a listing for the website's domain.
•There might be a typing error in the address.
•If this is an HTTPS (secure) address, click Tools, click Internet Options, click Advanced, and check to be sure the SSL and TLS protocols are enabled under the security section.


For offline users

 You can still view subscribed feeds and some recently viewed webpages.
 To view subscribed feeds:
1.Click the Favorites button , click Feeds, and then click the feed you want to view.


To view recently visited webpages (might not work on all pages):
1.Press Alt, click File, and then click Work Offline.
2.Click the Favorites button , click History, and then click the page you want to view.
 

Check and replace that power supply as I've heard of this before.If the fans spin up then stop it's a sign of insufficient power.Try this to rule out a faulty miner.If it still does it with a new PSU,the miner needs to be replaced.If it works after changing the PSU,then it's the PSU that's at fault not the miner.

If this helps/fixes the issue,send me that tip of £25 via my paypal.Thanks

I have the same problem but i cant get them to mine , can you send the skype of your china supplier , im about to go to china and kill mine. Thank you

You look good to go.  Congrats.

Hi ok guys thanks for the support i think its sorted, the supplier in china helped me by logging in on teamviewer im not exactly sure what he did but he did mention something to do with my bt home hub and its ip not being changeable like most routers.  I asked him what was wrong and he said didnt know but the units up and hashing now.  And has been for 5 or so hours.

Its still not setup on dhcp its on stati ip the fatory assigned one actually
 
He also played about with the chip frequency and i noticed its not got a target temperature in there now either.

Ive attached some screen shots of how its setup up now hopefully that may shed some light on it and what was wrong with my network setup in the miners back end as it would be nice to know where i was going wrong.

How do you think its performing?  

So when you change your settings on the Avalon to DHCP....  you are unable to access your miner?

Your router should just assign it a new address automatically and you should be able to log in, provided that you are on the same subnet.

Look for your list of devices and get the ip address after switching to DHCP on the Avalon.

Since you have reset back to stock, now just set it up for DHCP/your pool settings and go for a Save and Apply.

Once the machine applies those settings you should be good with a "new" ip address on your Avalon.

You must go get that address from your router to view in your browser.

So remember that 192.168.0.100 is going to disappear once you hit save and apply.....then get the new address from your router after the settings have been changed.

You can do it.

and remember to change all the network settings to fit your network as you did before... gateway subnet mask DNS etc.

Badabing, listen to Studio....


OK so you want to go to DHCP

in the network page where you changed to DHCP there is a tickbox at the bottom which is ticked by default

it is called

Disable DHCP

go back to DHCP settings instead of fixed IP

and UNTICK THE BOX


also remember

you MUST go to system startup and stop CGMiner before editing the configuration or it will not take the configuration you put in.

OK

plug into your PC, no router

change your PC IPv4 back to

192.168.0.123

scan

192.168.0.1 to 192.268.0.255



ok back into it by ethenet direct into computer its on 192.168.0.100  so it seems the reset i did by hitting the button on the w305 has took it back to stock settings throughout.

OK

plug into your PC, no router

change your PC IPv4 back to

192.168.0.123

scan

192.168.0.1 to 192.268.0.255

and if no luck

change your IPv4 to

192.168.1.123

scan

192.168.1.1 to 192.168.255


post results up here.

Ive just also scanned with ip scan from 192.168.0.0 to 192.168.1.254  and it doesnt show up anywhere.

Ok ive brought up a command prompt pinged the miner at the ip it was assigned 192.168.1.139 and it responded back yet when i type 192.168.1.139 into my browser i can get into it.  (DHCP is now off on the miner btw)  And its since i switched the dhcp off  and assigned it a static ip that i cant get back into the backend

Ive also tried holding down the reset button on the wr305n router the light then flashes really fast and if it a open up a command prompt and ping it at 192.168.1.0 it does again respond yet once i put that it my browser nothing comes up either.

Its really got me now as i just cannot get the login screen up to get into the open wrt backend at all.  

try connecting direct from your PC again with an ethernet cable

Did you remember to go into starup and stop CGminer before changing the config?

did you untick disable DHCP as well as changing it from static IP to DHCP?

Does anyone know which range i should searching for in ip scanner to try to find it?

Could i find it by plugging it straight into my laptop by ethenet?  if so what should i change my laptops lan ethnet ip4`s ip address to?  (is it something similar in range) like 192.168.1.123 ?



Failing that im thinking of hitting the rest button on the wrt305 but how do i go about finding it then does it resort to a default ip?

Okl managed to get straight in this morning on the ip i assinged it 192.168.1.139 even though dhcp was on?

but really struggling with this now tried all of the below:-

tried changing pool to bt guild made no difference still got the error in cgi status which wont seem to clear regardless of reboot, restarting cgi miner etc
tried removing the wifi and just using the lan ethenet interface - no difference
tried changing chip frequency to 256 p- no difference
tried changing miner count to ten - no difference

The unit is totally sinlent todasy where as yestreday after the reset it was making some noise ,  then it hashed for 8 minutes and now im back to square 1.



And ive just tried changing it from dhcp back to static by entering the details as below and now it wont let me in at all again on the 192.168.1.139.  My next plan was to factory reset by the back end again to see if i could get rid of the error as it seemed to have disappeared after resetting it last time but now i can get into it at all again now?

The settings i entered when taking the dhcp off are as follows:-



 

Try miner count set to 10 too.

Ok thanks i decided to leave it at work because after toying with it all last night and today at work it was getting to the point where i felt like throwing it through the nearest window.

So tomorrow going to have a fresh go at it:-

Plan is to

1.  Scan using angry IP to try to find its ip now its set to dhcp .  Or log into my homehub router and see if it shows there.
2.  Once in im going to check that LAN is pinned in the network menu and not wifi as thats stil not funtioning.
then try it now.

3. If no sucess im going to try changing pools something like btguild as ive a sneaky feeling that could be the issue as it only threw a fit after i changed from the avalons factory sets pool (there own) to slushes pool. So im wondering if it just doesnt like slushes pool.

4. If above fails im going to try to set the chip frequency to 256 as ive read elsewhere that that helped someone with the error code. They also apparently cleared the "quiet" from the more options menu....  What does the chip frequency do to it exactly?  ive currently set it as suggested by a member on here its set at following:-

frequency 1300
miner count 16
target temp 60
over heat cutoff 70
more options quiet

5. Lastly if all above fails im going to factory reset it again back to oem then do it all  again one step at a time. As after the reset before the error wasnt there and it did look set to hash until it popped up. (this is making me wonder about slushes pool doing it when i inserted my details)(ive only just signed up to slushes pool today btw)
 

Thats really all i can try any more suggestions are welcomed.

Yeah, use a scanner to find the miner.

Thats because you set it to DHCP, so it has been dynamically applied a new IP address by your router

You should be able to see its IP by logging onto your router and checking IP addresses of devices connected by ethernet.

Definitely still  some network issue ive just reset it power off and reboot and not it wont even let me log back into it at the ip i gave it 192.168.1.139

I don't think so, did you stop CGMiner before entering your pool details?

It looks like an initial network error,

Wed Jan 15 18:47:46 2014 daemon.info sysinit: ntpd: bad address '1.openwrt.pool.ntp.org'
Wed Jan 15 18:47:46 2014 daemon.info sysinit: ntpd: could not resolve peer 1.openwrt.pool.ntp.org, skipping
Wed Jan 15 18:47:46 2014 daemon.info sysinit: ntpd: bad address '0.openwrt.pool.ntp.org'
Wed Jan 15 18:47:46 2014 daemon.info sysinit: ntpd: could not resolve peer 0.openwrt.pool.ntp.org, skipping


which is then resolved

Wed Jan 15 18:48:07 2014 daemon.info sysinit: ntpd: resolved peer 3.openwrt.pool.ntp.org to 213.136.0.252


 but then doesn't authenticate with the pool.

Wed Jan 15 18:48:09 2014 daemon.info sysinit: ntpd: reply from 217.114.59.66: reach 0x01 offset 25.980903 delay 1.785423 status 0x24 strat 2 refid 0x9e2bc042 rootdelay 0.010025

 Do you use any other pools?

I suggest

go to system

startup

stop CGMiner

setup on another pool (try BTCGuild I use them with these machines no problem)

enter the pool details

also just enter 123 in the password section as some pools are a bit weird about that for some reason

Make sure the rest of the CGMiner settings are correct

Also I think the Miner count needs to be set to 10 for the 200G machines, wouldn't swear to it and can't check until the morning now

save and apply

see what happens.

I had the same problem as yours, and it is network problem. You need to set up DHCP, and save. Then once finished saving, do a hard reboot. Turn the power off at the power switch. Wait 10 seconds, and then it back on. You should have a new DHCP address. Now the problem should be fixed.

no nothing it only ran for like 8 minutes.  I cant understand it just getting this same error all the time now and no information what so ever on the cgi status page.

Im wondering whether to factory reset it again as when i first got back into it today on after the reset earlier today that error was no where to be seen,  but it was on it yesterday when i first unboxed the unit and plugged it in.

Im wondering if it has a hardware fault?

have you had any shares accepted at your pool?

Oh dear didnt last long getting same fault that i had in the very beginning,  its stopped hashing and nothing showing in the status area.

[Firmware Version] => 20131110
cgminer: 176747f
cgminer-openwrt-packages: 0e12b1b
luci: 346e3e7
Socket connect failed: Connection refused


Wed Jan 15 18:47:46 2014 daemon.info sysinit: ntpd: bad address '1.openwrt.pool.ntp.org'
Wed Jan 15 18:47:46 2014 daemon.info sysinit: ntpd: could not resolve peer 1.openwrt.pool.ntp.org, skipping
Wed Jan 15 18:47:46 2014 daemon.info sysinit: ntpd: bad address '0.openwrt.pool.ntp.org'
Wed Jan 15 18:47:46 2014 daemon.info sysinit: ntpd: could not resolve peer 0.openwrt.pool.ntp.org, skipping
Wed Jan 15 18:47:46 2014 kern.info kernel: [   56.310000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 3/3)
Wed Jan 15 18:47:47 2014 kern.info kernel: [   56.520000] wlan0: authentication with 00:81:d8:6e:3f:9a timed out
Wed Jan 15 18:47:48 2014 kern.info kernel: [   58.210000] wlan0: authenticate with 00:81:d8:6e:3f:9a
Wed Jan 15 18:47:49 2014 kern.info kernel: [   58.640000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 1/3)
Wed Jan 15 18:47:49 2014 kern.info kernel: [   58.850000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 2/3)
Wed Jan 15 18:47:49 2014 kern.info kernel: [   59.060000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 3/3)
Wed Jan 15 18:47:49 2014 kern.info kernel: [   59.270000] wlan0: authentication with 00:81:d8:6e:3f:9a timed out
Wed Jan 15 18:47:50 2014 daemon.info sysinit: Alarm clock
Wed Jan 15 18:47:50 2014 daemon.info sysinit: ntpd: bad address '3.openwrt.pool.ntp.org'
Wed Jan 15 18:47:50 2014 daemon.info sysinit: ntpd: could not resolve peer 3.openwrt.pool.ntp.org, skipping
Wed Jan 15 18:47:50 2014 daemon.info sysinit: ntpd: bad address '2.openwrt.pool.ntp.org'
Wed Jan 15 18:47:50 2014 daemon.info sysinit: ntpd: could not resolve peer 2.openwrt.pool.ntp.org, skipping
Wed Jan 15 18:47:50 2014 daemon.info sysinit: ntpd: bad address '1.openwrt.pool.ntp.org'
Wed Jan 15 18:47:50 2014 daemon.info sysinit: ntpd: could not resolve peer 1.openwrt.pool.ntp.org, skipping
Wed Jan 15 18:47:50 2014 daemon.info sysinit: ntpd: bad address '0.openwrt.pool.ntp.org'
Wed Jan 15 18:47:50 2014 daemon.info sysinit: ntpd: could not resolve peer 0.openwrt.pool.ntp.org, skipping
Wed Jan 15 18:47:56 2014 daemon.info sysinit: ntpd: bad address '3.openwrt.pool.ntp.org'
Wed Jan 15 18:47:56 2014 daemon.info sysinit: ntpd: could not resolve peer 3.openwrt.pool.ntp.org, skipping
Wed Jan 15 18:47:56 2014 daemon.info sysinit: ntpd: bad address '2.openwrt.pool.ntp.org'
Wed Jan 15 18:47:56 2014 daemon.info sysinit: ntpd: could not resolve peer 2.openwrt.pool.ntp.org, skipping
Wed Jan 15 18:47:56 2014 daemon.info sysinit: ntpd: bad address '1.openwrt.pool.ntp.org'
Wed Jan 15 18:47:56 2014 daemon.info sysinit: ntpd: could not resolve peer 1.openwrt.pool.ntp.org, skipping
Wed Jan 15 18:47:56 2014 daemon.info sysinit: ntpd: bad address '0.openwrt.pool.ntp.org'
Wed Jan 15 18:47:56 2014 daemon.info sysinit: ntpd: could not resolve peer 0.openwrt.pool.ntp.org, skipping
Wed Jan 15 18:48:00 2014 kern.info kernel: [   70.000000] wlan0: authenticate with 00:81:d8:6e:3f:9a
Wed Jan 15 18:48:00 2014 daemon.info sysinit: Alarm clock
Wed Jan 15 18:48:00 2014 daemon.info sysinit: ntpd: bad address '3.openwrt.pool.ntp.org'
Wed Jan 15 18:48:00 2014 daemon.info sysinit: ntpd: could not resolve peer 3.openwrt.pool.ntp.org, skipping
Wed Jan 15 18:48:00 2014 daemon.info sysinit: ntpd: bad address '2.openwrt.pool.ntp.org'
Wed Jan 15 18:48:00 2014 daemon.info sysinit: ntpd: could not resolve peer 2.openwrt.pool.ntp.org, skipping
Wed Jan 15 18:48:00 2014 daemon.info sysinit: ntpd: bad address '1.openwrt.pool.ntp.org'
Wed Jan 15 18:48:00 2014 daemon.info sysinit: ntpd: could not resolve peer 1.openwrt.pool.ntp.org, skipping
Wed Jan 15 18:48:00 2014 daemon.info sysinit: ntpd: bad address '0.openwrt.pool.ntp.org'
Wed Jan 15 18:48:00 2014 daemon.info sysinit: ntpd: could not resolve peer 0.openwrt.pool.ntp.org, skipping
Wed Jan 15 18:48:00 2014 kern.info kernel: [   70.430000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 1/3)
Wed Jan 15 18:48:01 2014 kern.info kernel: [   70.640000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 2/3)
Wed Jan 15 18:48:01 2014 kern.info kernel: [   70.850000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 3/3)
Wed Jan 15 18:48:01 2014 kern.info kernel: [   71.060000] wlan0: authentication with 00:81:d8:6e:3f:9a timed out
Wed Jan 15 18:48:01 2014 cron.info crond[559]: crond: USER root pid 946 cmd /usr/bin/cgminer-monitor
Wed Jan 15 18:48:03 2014 daemon.notice netifd: lan (571): Sending select for 192.168.1.139...
Wed Jan 15 18:48:03 2014 daemon.notice netifd: lan (571): Lease of 192.168.1.139 obtained, lease time 86400
Wed Jan 15 18:48:04 2014 daemon.notice netifd: Interface 'lan' is now up
Wed Jan 15 18:48:04 2014 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Wed Jan 15 18:48:06 2014 daemon.info dnsmasq[647]: reading /tmp/resolv.conf.auto
Wed Jan 15 18:48:06 2014 daemon.info dnsmasq[647]: using nameserver 192.168.1.254#53
Wed Jan 15 18:48:06 2014 daemon.info dnsmasq[647]: using local addresses only for domain lan
Wed Jan 15 18:48:07 2014 daemon.info sysinit: ntpd: resolved peer 3.openwrt.pool.ntp.org to 213.136.0.252
Wed Jan 15 18:48:07 2014 daemon.info sysinit: ntpd: sent query to 213.136.0.252
Wed Jan 15 18:48:08 2014 daemon.info sysinit: ntpd: resolved peer 2.openwrt.pool.ntp.org to 217.114.59.66
Wed Jan 15 18:48:08 2014 daemon.info sysinit: ntpd: sent query to 217.114.59.66
Wed Jan 15 18:48:08 2014 daemon.info sysinit: ntpd: resolved peer 1.openwrt.pool.ntp.org to 91.236.251.24
Wed Jan 15 18:48:08 2014 daemon.info sysinit: ntpd: sent query to 91.236.251.24
Wed Jan 15 18:48:09 2014 daemon.info sysinit: ntpd: resolved peer 0.openwrt.pool.ntp.org to 88.190.16.117
Wed Jan 15 18:48:09 2014 daemon.info sysinit: ntpd: sent query to 88.190.16.117
Wed Jan 15 18:48:09 2014 daemon.info sysinit: ntpd: reply from 213.136.0.252: reach 0x01 offset 25.654418 delay 2.443525 status 0x24 strat 1 refid 0x50505300 rootdelay 0.000000
Wed Jan 15 18:48:09 2014 daemon.info sysinit: ntpd: reply from 217.114.59.66: reach 0x01 offset 25.980903 delay 1.785423 status 0x24 strat 2 refid 0x9e2bc042 rootdelay 0.010025
Wed Jan 15 18:48:09 2014 daemon.info sysinit: ntpd: reply from 91.236.251.24: reach 0x01 offset 26.150966 delay 1.586017 status 0x24 strat 3 refid 0x5becfb0c rootdelay 0.044068
Wed Jan 15 18:48:09 2014 daemon.info sysinit: ntpd: reply from 88.190.16.117: reach 0x01 offset 26.850994 delay 0.044443 status 0x24 strat 2 refid 0xc05d0214 rootdelay 0.002411
Wed Jan 15 18:48:10 2014 daemon.info sysinit: ntpd: sent query to 213.136.0.252
Wed Jan 15 18:48:10 2014 daemon.info sysinit: ntpd: sent query to 217.114.59.66
Wed Jan 15 18:48:10 2014 daemon.info sysinit: ntpd: sent query to 91.236.251.24
Wed Jan 15 18:48:10 2014 daemon.info sysinit: ntpd: reply from 213.136.0.252: reach 0x03 offset 26.855108 delay 0.038972 status 0x24 strat 1 refid 0x50505300 rootdelay 0.000000
Wed Jan 15 18:48:10 2014 daemon.info sysinit: ntpd: reply from 217.114.59.66: reach 0x03 offset 26.855036 delay 0.039230 status 0x24 strat 2 refid 0x9e2bc042 rootdelay 0.010025
Wed Jan 15 18:48:11 2014 daemon.info sysinit: ntpd: reply from 91.236.251.24: reach 0x03 offset 26.863637 delay 0.147802 status 0x24 strat 3 refid 0x5becfb0c rootdelay 0.044068
Wed Jan 15 18:48:12 2014 daemon.info sysinit: ntpd: sent query to 213.136.0.252
Wed Jan 15 18:48:12 2014 daemon.info sysinit: ntpd: sent query to 88.190.16.117
Wed Jan 15 18:48:12 2014 daemon.info sysinit: ntpd: reply from 213.136.0.252: reach 0x07 offset 26.855919 delay 0.040337 status 0x24 strat 1 refid 0x50505300 rootdelay 0.000000
Wed Jan 15 18:48:12 2014 daemon.info sysinit: ntpd: reply from 88.190.16.117: reach 0x03 offset 26.850617 delay 0.046815 status 0x24 strat 2 refid 0xc05d0214 rootdelay 0.002411
Wed Jan 15 18:48:13 2014 daemon.info sysinit: ntpd: sent query to 213.136.0.252
Wed Jan 15 18:48:13 2014 daemon.info sysinit: ntpd: sent query to 217.114.59.66
Wed Jan 15 18:48:13 2014 daemon.info sysinit: ntpd: sent query to 91.236.251.24
Wed Jan 15 18:48:13 2014 daemon.info sysinit: ntpd: reply from 213.136.0.252: reach 0x0f offset 26.855503 delay 0.037401 status 0x24 strat 1 refid 0x50505300 rootdelay 0.000000
Wed Jan 15 18:48:13 2014 daemon.info sysinit: ntpd: reply from 217.114.59.66: reach 0x07 offset 26.855912 delay 0.039548 status 0x24 strat 2 refid 0x9e2bc042 rootdelay 0.010025
Wed Jan 15 18:48:13 2014 daemon.info sysinit: ntpd: reply from 91.236.251.24: reach 0x07 offset 26.871253 delay 0.139987 status 0x24 strat 3 refid 0x5becfb0c rootdelay 0.044068
Wed Jan 15 18:48:14 2014 daemon.info sysinit: ntpd: sent query to 91.236.251.24
Wed Jan 15 18:48:14 2014 daemon.info sysinit: ntpd: sent query to 88.190.16.117
Wed Jan 15 18:48:14 2014 daemon.info sysinit: ntpd: reply from 88.190.16.117: reach 0x07 offset 26.850117 delay 0.046277 status 0x24 strat 2 refid 0xc05d0214 rootdelay 0.002411
Wed Jan 15 18:48:14 2014 daemon.info sysinit: ntpd: reply from 91.236.251.24: reach 0x0f offset 26.871537 delay 0.133922 status 0x24 strat 3 refid 0x5becfb0c rootdelay 0.044068
Wed Jan 15 18:48:42 2014 daemon.info sysinit: ntpd: sent query to 213.136.0.252
Wed Jan 15 18:48:42 2014 daemon.info sysinit: ntpd: sent query to 217.114.59.66
Wed Jan 15 18:48:42 2014 daemon.info sysinit: ntpd: sent query to 91.236.251.24
Wed Jan 15 18:48:42 2014 daemon.info sysinit: ntpd: sent query to 88.190.16.117
Wed Jan 15 18:48:42 2014 daemon.info sysinit: ntpd: reply from 217.114.59.66: reach 0x0f offset 0.047524 delay 0.037515 status 0x24 strat 2 refid 0x9e2bc042 rootdelay 0.010025
Wed Jan 15 18:48:42 2014 daemon.info sysinit: ntpd: reply from 213.136.0.252: reach 0x1f offset 0.047354 delay 0.038719 status 0x24 strat 1 refid 0x50505300 rootdelay 0.000000
Wed Jan 15 18:48:42 2014 daemon.info sysinit: ntpd: reply from 88.190.16.117: reach 0x0f offset 0.044106 delay 0.049387 status 0x24 strat 2 refid 0xc05d0214 rootdelay 0.002411
Wed Jan 15 18:48:42 2014 daemon.info sysinit: ntpd: reply from 91.236.251.24: reach 0x1f offset 0.060276 delay 0.141879 status 0x24 strat 3 refid 0x5becfb0c rootdelay 0.044068
Wed Jan 15 18:48:43 2014 daemon.info sysinit: ntpd: sent query to 213.136.0.252
Wed Jan 15 18:48:43 2014 daemon.info sysinit: ntpd: sent query to 217.114.59.66
Wed Jan 15 18:48:43 2014 daemon.info sysinit: ntpd: reply from 213.136.0.252: reach 0x3f offset 0.047654 delay 0.038115 status 0x24 strat 1 refid 0x50505300 rootdelay 0.000000
Wed Jan 15 18:48:43 2014 daemon.info sysinit: ntpd: reply from 217.114.59.66: reach 0x1f offset 0.047526 delay 0.038415 status 0x24 strat 2 refid 0x9e2bc042 rootdelay 0.010025
Wed Jan 15 18:48:44 2014 daemon.info sysinit: ntpd: sent query to 217.114.59.66
Wed Jan 15 18:48:44 2014 daemon.info sysinit: ntpd: sent query to 91.236.251.24
Wed Jan 15 18:48:44 2014 daemon.info sysinit: ntpd: sent query to 88.190.16.117
Wed Jan 15 18:48:44 2014 daemon.info sysinit: ntpd: reply from 217.114.59.66: reach 0x3f offset 0.047427 delay 0.037950 status 0x24 strat 2 refid 0x9e2bc042 rootdelay 0.010025
Wed Jan 15 18:48:44 2014 daemon.info sysinit: ntpd: reply from 88.190.16.117: reach 0x1f offset 0.042830 delay 0.046915 status 0x24 strat 2 refid 0xc05d0214 rootdelay 0.002411
Wed Jan 15 18:48:44 2014 daemon.info sysinit: ntpd: reply from 91.236.251.24: reach 0x3f offset 0.064736 delay 0.127624 status 0x24 strat 3 refid 0x5becfb0c rootdelay 0.044068
Wed Jan 15 18:48:45 2014 daemon.info sysinit: ntpd: sent query to 213.136.0.252
Wed Jan 15 18:48:45 2014 daemon.info sysinit: ntpd: reply from 213.136.0.252: reach 0x7f offset 0.047567 delay 0.038255 status 0x24 strat 1 refid 0x50505300 rootdelay 0.000000
Wed Jan 15 18:48:46 2014 daemon.info sysinit: ntpd: sent query to 217.114.59.66
Wed Jan 15 18:48:46 2014 daemon.info sysinit: ntpd: sent query to 91.236.251.24
Wed Jan 15 18:48:46 2014 daemon.info sysinit: ntpd: sent query to 88.190.16.117
Wed Jan 15 18:48:46 2014 daemon.info sysinit: ntpd: reply from 217.114.59.66: reach 0x7f offset 0.048231 delay 0.039553 status 0x24 strat 2 refid 0x9e2bc042 rootdelay 0.010025
Wed Jan 15 18:48:46 2014 daemon.info sysinit: ntpd: reply from 88.190.16.117: reach 0x3f offset 0.043797 delay 0.044621 status 0x24 strat 2 refid 0xc05d0214 rootdelay 0.002411
Wed Jan 15 18:48:46 2014 daemon.info sysinit: ntpd: reply from 91.236.251.24: reach 0x7f offset 0.062215 delay 0.131965 status 0x24 strat 3 refid 0x5becfb0c rootdelay 0.044068
Wed Jan 15 18:48:47 2014 daemon.info sysinit: ntpd: sent query to 213.136.0.252
Wed Jan 15 18:48:47 2014 daemon.info sysinit: ntpd: sent query to 217.114.59.66
Wed Jan 15 18:48:47 2014 daemon.info sysinit: ntpd: sent query to 91.236.251.24
Wed Jan 15 18:48:47 2014 daemon.info sysinit: ntpd: sent query to 88.190.16.117
Wed Jan 15 18:48:47 2014 daemon.info sysinit: ntpd: reply from 213.136.0.252: reach 0xff offset 0.047575 delay 0.038712 status 0x24 strat 1 refid 0x50505300 rootdelay 0.000000
Wed Jan 15 18:48:47 2014 daemon.info sysinit: ntpd: reply from 217.114.59.66: reach 0xff offset 0.048629 delay 0.039929 status 0x24 strat 2 refid 0x9e2bc042 rootdelay 0.010025
Wed Jan 15 18:48:47 2014 daemon.info sysinit: ntpd: reply from 88.190.16.117: reach 0x7f offset 0.043827 delay 0.045375 status 0x24 strat 2 refid 0xc05d0214 rootdelay 0.002411
Wed Jan 15 18:48:47 2014 daemon.info sysinit: ntpd: reply from 91.236.251.24: reach 0xff offset 0.062700 delay 0.127256 status 0x24 strat 3 refid 0x5becfb0c rootdelay 0.044068
Wed Jan 15 18:48:48 2014 daemon.info sysinit: ntpd: sent query to 217.114.59.66
Wed Jan 15 18:48:48 2014 daemon.info sysinit: ntpd: reply from 217.114.59.66: reach 0xff offset 0.047076 delay 0.037653 status 0x24 strat 2 refid 0x9e2bc042 rootdelay 0.010025
Wed Jan 15 18:48:49 2014 kern.info kernel: [   92.120000] wlan0: authenticate with 00:81:d8:6e:3f:9a
Wed Jan 15 18:48:49 2014 daemon.info sysinit: ntpd: sent query to 213.136.0.252
Wed Jan 15 18:48:49 2014 daemon.info sysinit: ntpd: sent query to 217.114.59.66
Wed Jan 15 18:48:49 2014 daemon.info sysinit: ntpd: sent query to 91.236.251.24
Wed Jan 15 18:48:49 2014 daemon.info sysinit: ntpd: sent query to 88.190.16.117
Wed Jan 15 18:48:49 2014 kern.info kernel: [   92.550000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 1/3)
Wed Jan 15 18:48:49 2014 daemon.info sysinit: ntpd: reply from 213.136.0.252: reach 0xff offset 0.048047 delay 0.040505 status 0x24 strat 1 refid 0x50505300 rootdelay 0.000000
Wed Jan 15 18:48:49 2014 daemon.info sysinit: ntpd: reply from 217.114.59.66: reach 0xff offset 0.048150 delay 0.040665 status 0x24 strat 2 refid 0x9e2bc042 rootdelay 0.010025
Wed Jan 15 18:48:49 2014 daemon.info sysinit: ntpd: reply from 88.190.16.117: reach 0xff offset 0.045274 delay 0.047336 status 0x24 strat 2 refid 0xc05d0214 rootdelay 0.002411
Wed Jan 15 18:48:49 2014 daemon.info sysinit: ntpd: reply from 91.236.251.24: reach 0xff offset 0.061091 delay 0.127781 status 0x24 strat 3 refid 0x5becfb0c rootdelay 0.044068
Wed Jan 15 18:48:50 2014 kern.info kernel: [   92.760000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 2/3)
Wed Jan 15 18:48:50 2014 kern.info kernel: [   92.970000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 3/3)
Wed Jan 15 18:48:50 2014 kern.info kernel: [   93.180000] wlan0: authentication with 00:81:d8:6e:3f:9a timed out
Wed Jan 15 18:48:51 2014 daemon.info sysinit: ntpd: sent query to 213.136.0.252
Wed Jan 15 18:48:51 2014 daemon.info sysinit: ntpd: sent query to 88.190.16.117
Wed Jan 15 18:48:51 2014 daemon.info sysinit: ntpd: reply from 213.136.0.252: reach 0xff offset 0.047879 delay 0.038195 status 0x24 strat 1 refid 0x50505300 rootdelay 0.000000
Wed Jan 15 18:48:51 2014 daemon.info sysinit: ntpd: reply from 88.190.16.117: reach 0xff offset 0.042256 delay 0.048059 status 0x24 strat 2 refid 0xc05d0214 rootdelay 0.002411
Wed Jan 15 18:48:52 2014 daemon.info sysinit: ntpd: sent query to 213.136.0.252
Wed Jan 15 18:48:52 2014 daemon.info sysinit: ntpd: sent query to 217.114.59.66
Wed Jan 15 18:48:52 2014 daemon.info sysinit: ntpd: sent query to 91.236.251.24
Wed Jan 15 18:48:52 2014 daemon.info sysinit: ntpd: reply from 217.114.59.66: reach 0xff offset 0.047512 delay 0.037791 status 0x24 strat 2 refid 0x9e2bc042 rootdelay 0.010025
Wed Jan 15 18:48:52 2014 daemon.info sysinit: - init complete -
Wed Jan 15 18:49:18 2014 kern.info kernel: [  120.680000] wlan0: authenticate with 00:81:d8:6e:3f:9a
Wed Jan 15 18:49:18 2014 kern.info kernel: [  121.110000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 1/3)
Wed Jan 15 18:49:18 2014 kern.info kernel: [  121.320000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 2/3)
Wed Jan 15 18:49:18 2014 kern.info kernel: [  121.530000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 3/3)
Wed Jan 15 18:49:19 2014 kern.info kernel: [  121.740000] wlan0: authentication with 00:81:d8:6e:3f:9a timed out
Wed Jan 15 18:50:01 2014 cron.info crond[559]: crond: USER root pid 1197 cmd /usr/bin/cgminer-monitor
Wed Jan 15 18:50:16 2014 kern.info kernel: [  179.480000] wlan0: authenticate with 00:81:d8:6e:3f:9a
Wed Jan 15 18:50:17 2014 kern.info kernel: [  179.910000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 1/3)
Wed Jan 15 18:50:17 2014 kern.info kernel: [  180.120000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 2/3)
Wed Jan 15 18:50:17 2014 kern.info kernel: [  180.330000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 3/3)
Wed Jan 15 18:50:17 2014 kern.info kernel: [  180.540000] wlan0: authentication with 00:81:d8:6e:3f:9a timed out
Wed Jan 15 18:50:40 2014 kern.info kernel: [  203.000000] wlan0: authenticate with 00:81:d8:6e:3f:9a
Wed Jan 15 18:50:40 2014 kern.info kernel: [  203.430000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 1/3)
Wed Jan 15 18:50:40 2014 kern.info kernel: [  203.640000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 2/3)
Wed Jan 15 18:50:41 2014 kern.info kernel: [  203.850000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 3/3)
Wed Jan 15 18:50:41 2014 kern.info kernel: [  204.060000] wlan0: authentication with 00:81:d8:6e:3f:9a timed out
Wed Jan 15 18:51:12 2014 kern.info kernel: [  234.920000] wlan0: authenticate with 00:81:d8:6e:3f:9a
Wed Jan 15 18:51:12 2014 kern.info kernel: [  235.350000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 1/3)
Wed Jan 15 18:51:12 2014 kern.info kernel: [  235.560000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 2/3)
Wed Jan 15 18:51:13 2014 kern.info kernel: [  235.770000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 3/3)
Wed Jan 15 18:51:13 2014 kern.info kernel: [  235.980000] wlan0: authentication with 00:81:d8:6e:3f:9a timed out




kernel log

[    0.000000] Linux version 3.10.12 (xiangfu@0xf8) (gcc version 4.6.4 (OpenWrt/Linaro GCC 4.6-2013.05 r38031) ) #6 Sun Nov 10 19:19:31 CST 2013
[    0.000000] MyLoader: sysp=388dd517, boardp=04505212, parts=7709ac36
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU revision is: 00019374 (MIPS 24Kc)
[    0.000000] SoC: Atheros AR9330 rev 1
[    0.000000] Clocks: CPU:400.000MHz, DDR:400.000MHz, AHB:200.000MHz, Ref:25.000MHz
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 02000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x00000000-0x01ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x00000000-0x01ffffff]
[    0.000000] On node 0 totalpages: 8192
[    0.000000] free_area_init_node: node 0, pgdat 803005b0, node_mem_map 81000000
[    0.000000]   Normal zone: 64 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 8192 pages, LIFO batch:0
[    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc:

• 0

[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 8128
[    0.000000] Kernel command line:  board=TL-WR703N console=ttyATH0,115200 rootfstype=squashfs,jffs2 noinitrd
[    0.000000] PID hash table entries: 128 (order: -3, 512 bytes)
[    0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Writing ErrCtl register=00000000
[    0.000000] Readback ErrCtl register=00000000
[    0.000000] Memory: 28848k/32768k available (2187k kernel code, 3920k reserved, 588k data, 232k init, 0k highmem)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:51
[    0.080000] Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104)
[    0.080000] pid_max: default: 32768 minimum: 301
[    0.080000] Mount-cache hash table entries: 512
[    0.090000] NET: Registered protocol family 16
[    0.100000] MIPS: machine is TP-LINK TL-WR703N v1
[    0.350000] bio: create slab at 0
[    0.360000] Switching to clocksource MIPS
[    0.360000] NET: Registered protocol family 2
[    0.370000] TCP established hash table entries: 512 (order: 0, 4096 bytes)
[    0.370000] TCP bind hash table entries: 512 (order: -1, 2048 bytes)
[    0.370000] TCP: Hash tables configured (established 512 bind 512)
[    0.380000] TCP: reno registered
[    0.380000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.390000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.400000] NET: Registered protocol family 1
[    0.400000] PCI: CLS 0 bytes, default 32
[    0.420000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.420000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.430000] msgmni has been set to 56
[    0.440000] io scheduler noop registered
[    0.440000] io scheduler deadline registered (default)
[    0.440000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
[    0.450000] ar933x-uart: ttyATH0 at MMIO 0x18020000 (irq = 11) is a AR933X UART
[    0.460000] console [ttyATH0] enabled, bootconsole disabled
[    0.470000] ath79-spi ath79-spi: master is unqueued, this is deprecated
[    0.480000] m25p80 spi0.0: found s25sl032p, expected m25p80
[    0.480000] m25p80 spi0.0: s25sl032p (4096 Kbytes)
[    0.490000] 5 tp-link partitions found on MTD device spi0.0
[    0.490000] Creating 5 MTD partitions on "spi0.0":
[    0.500000] 0x000000000000-0x000000020000 : "u-boot"
[    0.500000] 0x000000020000-0x000000117d1c : "kernel"
[    0.510000] mtd: partition "kernel" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
[    0.520000] 0x000000117d1c-0x0000003f0000 : "rootfs"
[    0.530000] mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
[    0.540000] mtd: partition "rootfs" set to be root filesystem
[    0.540000] mtd: partition "rootfs_data" created automatically, ofs=0x340000, len=0xb0000
[    0.550000] 0x000000340000-0x0000003f0000 : "rootfs_data"
[    0.560000] 0x0000003f0000-0x000000400000 : "art"
[    0.560000] 0x000000020000-0x0000003f0000 : "firmware"
[    0.590000] libphy: ag71xx_mdio: probed
[    0.590000] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:MII
[    1.140000] ag71xx ag71xx.0 eth0: connected to PHY at ag71xx-mdio.1:04 [uid=004dd041, driver=Generic PHY]
[    1.150000] TCP: cubic registered
[    1.160000] NET: Registered protocol family 17
[    1.160000] 8021q: 802.1Q VLAN Support v1.8
[    1.170000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
[    1.180000] Freeing unused kernel memory: 232K (80316000 - 80350000)
[    3.750000] usbcore: registered new interface driver usbfs
[    3.750000] usbcore: registered new interface driver hub
[    3.760000] usbcore: registered new device driver usb
[    3.770000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    3.780000] ehci-platform: EHCI generic platform driver
[    3.780000] ehci-platform ehci-platform: EHCI Host Controller
[    3.790000] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1
[    3.790000] ehci-platform ehci-platform: irq 3, io mem 0x1b000000
[    3.820000] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00
[    3.820000] hub 1-0:1.0: USB hub found
[    3.820000] hub 1-0:1.0: 1 port detected
[    4.170000] usb 1-1: new high-speed USB device number 2 using ehci-platform
[    4.320000] hub 1-1:1.0: USB hub found
[    4.320000] hub 1-1:1.0: 2 ports detected
[    4.600000] usb 1-1.1: new full-speed USB device number 3 using ehci-platform
[    7.150000] eth0: link up (100Mbps/Full duplex)
[    7.460000] jffs2: notice: (308) jffs2_build_xattr_subsystem: complete building xattr subsystem, 4 of xdatum (1 unchecked, 3 orphan) and 34 of xref (0 dead, 21 orphan) found.
[    7.490000] eth0: link down
[    9.720000] Loading modules backported from Linux version master-2013-06-27-0-gdcfa6d5
[    9.730000] Backport generated by backports.git backports-20130617-4-ge3220f5
[    9.740000] nf_conntrack version 0.5.0 (454 buckets, 1816 max)
[    9.790000] xt_time: kernel timezone is -0000
[    9.810000] cfg80211: Calling CRDA to update world regulatory domain
[    9.810000] cfg80211: World regulatory domain updated:
[    9.820000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[    9.830000] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[    9.840000] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[    9.840000] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[    9.850000] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[    9.860000] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[    9.870000] ip_tables: (C) 2000-2006 Netfilter Core Team
[   10.010000] ath: EEPROM regdomain: 0x0
[   10.010000] ath: EEPROM indicates default country code should be used
[   10.010000] ath: doing EEPROM country->regdmn map search
[   10.010000] ath: country maps to regdmn code: 0x3a
[   10.010000] ath: Country alpha2 being used: US
[   10.010000] ath: Regpair used: 0x3a
[   10.020000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   10.030000] cfg80211: Calling CRDA for country: US
[   10.040000] cfg80211: Regulatory domain changed to country: US
[   10.040000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[   10.050000] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
[   10.060000] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
[   10.060000] cfg80211:   (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   10.070000] cfg80211:   (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   10.080000] cfg80211:   (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   10.090000] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
[   10.100000] ieee80211 phy0: Atheros AR9330 Rev:1 mem=0xb8100000, irq=2
[   13.660000] device eth0 entered promiscuous mode
[   14.230000] eth0: link up (100Mbps/Full duplex)
[   14.230000] br-lan: port 1(eth0) entered forwarding state
[   14.240000] br-lan: port 1(eth0) entered forwarding state
[   16.240000] br-lan: port 1(eth0) entered forwarding state
[   39.990000] wlan0: authenticate with 00:81:d8:6e:3f:9a
[   40.030000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 1/3)
[   40.240000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 2/3)
[   40.450000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 3/3)
[   40.660000] wlan0: authentication with 00:81:d8:6e:3f:9a timed out
[   48.170000] wlan0: authenticate with 00:81:d8:6e:3f:9a
[   48.600000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 1/3)
[   48.810000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 2/3)
[   49.020000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 3/3)
[   49.230000] wlan0: authentication with 00:81:d8:6e:3f:9a timed out
[   55.460000] wlan0: authenticate with 00:81:d8:6e:3f:9a
[   55.880000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 1/3)
[   56.100000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 2/3)
[   56.310000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 3/3)
[   56.520000] wlan0: authentication with 00:81:d8:6e:3f:9a timed out
[   58.210000] wlan0: authenticate with 00:81:d8:6e:3f:9a
[   58.640000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 1/3)
[   58.850000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 2/3)
[   59.060000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 3/3)
[   59.270000] wlan0: authentication with 00:81:d8:6e:3f:9a timed out
[   70.000000] wlan0: authenticate with 00:81:d8:6e:3f:9a
[   70.430000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 1/3)
[   70.640000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 2/3)
[   70.850000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 3/3)
[   71.060000] wlan0: authentication with 00:81:d8:6e:3f:9a timed out
[   92.120000] wlan0: authenticate with 00:81:d8:6e:3f:9a
[   92.550000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 1/3)
[   92.760000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 2/3)
[   92.970000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 3/3)
[   93.180000] wlan0: authentication with 00:81:d8:6e:3f:9a timed out
[  120.680000] wlan0: authenticate with 00:81:d8:6e:3f:9a
[  121.110000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 1/3)
[  121.320000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 2/3)
[  121.530000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 3/3)
[  121.740000] wlan0: authentication with 00:81:d8:6e:3f:9a timed out
[  179.480000] wlan0: authenticate with 00:81:d8:6e:3f:9a
[  179.910000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 1/3)
[  180.120000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 2/3)
[  180.330000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 3/3)
[  180.540000] wlan0: authentication with 00:81:d8:6e:3f:9a timed out
[  203.000000] wlan0: authenticate with 00:81:d8:6e:3f:9a
[  203.430000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 1/3)
[  203.640000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 2/3)
[  203.850000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 3/3)
[  204.060000] wlan0: authentication with 00:81:d8:6e:3f:9a timed out
[  234.920000] wlan0: authenticate with 00:81:d8:6e:3f:9a
[  235.350000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 1/3)
[  235.560000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 2/3)
[  235.770000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 3/3)
[  235.980000] wlan0: authentication with 00:81:d8:6e:3f:9a timed out
[  266.960000] wlan0: authenticate with 00:81:d8:6e:3f:9a
[  267.390000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 1/3)
[  267.600000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 2/3)
[  267.810000] wlan0: direct probe to 00:81:d8:6e:3f:9a (try 3/3)
[  268.020000] wlan0: authentication with 00:81:d8:6e:3f:9a timed out

BTW, get yourself 2 of this:

http://www.amazon.co.uk/gp/product/B002QVLBM2/ref=oh_details_o01_s00_i00?ie=UTF8&psc=1

and 2 of this:

http://www.amazon.co.uk/gp/product/B003VYB76I/ref=oh_details_o01_s00_i01?ie=UTF8&psc=1

Then the noisy engine noise will disappear, by opening your case and change the case fans.

Don't do Paypal...... but if you wanna donate me some coin feel free:

1BvGbrgRhNfJLbBG93L6F7tCSifcMSMnQf


Happy hashing!

Pleased its working for you

Don't want a fiat payment from you, more than happy to help. When you mine some BTC if you want you can send some to



But really don't feel any obligation, happy to just see someone join the network  

Just to be sure go to the CGMiner status page and you should be able to see a speed under the Mhash section. Also check your pool for accepted shares.

ok noise is building now (exciting)  


thanks i really do owe those who helped il send each you guys a share of the money if you drop me your paypal details ,  thanks

Go ahead and change your settings to one pool only.  Erase the other two.

Make sure you change the chipset an other settings to these settings:



Make sure you save and apply...... then it should start.

ok not sure how to ping my pools address from the avalon

but ive just checked cgi settings and there different so il  make them same as yours and see if it takes off?

ive got same pool and worker for all three but assume thats ok?

Once you have verified all your settings are correct....

Go to your cgminer status page....if your bottom line of stats have numbers (not zeros "0") and your machine is running loud as hell.......then you are hashing just fine.

It will take time to max out....just give it like 10 mins once it starts hashing.

Check your pool's website to ensure your worker's generated shares are being received.

And current cgi status not sure if this is hashing or not?

Ok i changed to dhcp nothing seems to have changed much i can still log also via the same 192.168.1.139 also

How do i know if its hashing then,  ive entered my pool details etc ,.

Im still not syure if its connected to the wider area network though with the wifi still not working.

The device is plugged into my homehub now.
 

Theres no errors in the cgi miner log at least.

[Firmware Version] => 20131110
cgminer: 176747f
cgminer-openwrt-packages: 0e12b1b
luci: 346e3e7
Reply was 'STATUS=S,When=1389807817,Code=70,Msg=CGMiner stats,Description=cgminer 3.4.3|STATS=0,ID=AVA0,Elapsed=206,Calls=0,Wait=0.000000,Max=0.000000,Min=99999999.000000,baud=115200,miner_count=32,asic_count=10,timeout=45,frequency=282,fan1=0,fan2=0,fan3=0,temp1=0,temp2=0,temp3=0,temp_max=0,Device Hardware%=100.0000,no_matching_work=10,match_work_count1=111,match_work_count2=85,match_work_count3=104,match_work_count4=87,match_work_count5=81,match_work_count6=82,match_work_count7=101,match_work_count8=95,match_work_count9=85,match_work_count10=90,match_work_count11=84,match_work_count12=106,match_work_count13=100,match_work_count14=88,match_work_count15=95,match_work_count16=85,match_work_count17=0,match_work_count18=0,match_work_count19=0,match_work_count20=0,match_work_count21=0,match_work_count22=0,match_work_count23=0,match_work_count24=0,match_work_count25=0,match_work_count26=0,match_work_count27=0,match_work_count28=0,match_work_count29=0,match_work_count30=0,match_work_count31=0,match_work_count32=0,Controller Version=0,Avalon Chip=110,USB Pipe=0,USB Delay=r0 0.000000 w0 0.000000,USB tmo=22532 0|STATS=1,ID=POOL0,Elapsed=206,Calls=0,Wait=0.000000,Max=0.000000,Min=99999999.000000,Pool Calls=0,Pool Attempts=0,Pool Wait=0.000000,Pool Max=0.000000,Pool Min=99999999.000000,Pool Av=0.000000,Work Had Roll Time=false,Work Can Roll=false,Work Had Expire=false,Work Roll Time=0,Work Diff=1.00000000,Min Diff=1.00000000,Max Diff=3.00000000,Min Diff Count=1265,Max Diff Count=161,Times Sent=4,Bytes Sent=312,Times Recv=15,Bytes Recv=10181,Net Bytes Sent=1049,Net Bytes Recv=10181|STATS=2,ID=POOL1,Elapsed=206,Calls=0,Wait=0.000000,Max=0.000000,Min=99999999.000000,Pool Calls=0,Pool Attempts=0,Pool Wait=0.000000,Pool Max=0.000000,Pool Min=99999999.000000,Pool Av=0.000000,Work Had Roll Time=false,Work Can Roll=false,Work Had Expire=false,Work Roll Time=0,Work Diff=1.00000000,Min Diff=1.00000000,Max Diff=3.00000000,Min Diff Count=1050,Max Diff Count=375,Times Sent=4,Bytes Sent=312,Times Recv=15,Bytes Recv=10152,Net Bytes Sent=1049,Net Bytes Recv=10152|STATS=3,ID=POOL2,Elapsed=206,Calls=0,Wait=0.000000,Max=0.000000,Min=99999999.000000,Pool Calls=0,Pool Attempts=0,Pool Wait=0.000000,Pool Max=0.000000,Pool Min=99999999.000000,Pool Av=0.000000,Work Had Roll Time=false,Work Can Roll=false,Work Had Expire=false,Work Roll Time=0,Work Diff=1.00000000,Min Diff=1.00000000,Max Diff=3.00000000,Min Diff Count=1050,Max Diff Count=375,Times Sent=4,Bytes Sent=314,Times Recv=15,Bytes Recv=10158,Net Bytes Sent=1051,Net Bytes Recv=10158|'
[STATUS] =>
(
   [STATUS] => S
   [When] => 1389807817
   

Your first circe is where u changing dhcp details.
Once protocol is changed your miner will change Ip once again. But this time will work with router.

Ok do i do that here at top red circle or bottom red circle?  yes i think home hub is dhcp from factory

I am sorry.......

I missed the fact that your router is on the "1" subnet.

Ok..... if you just change the Avalon's protocol to DHCP, then it will work.

Do not got to the "0" subnet.  Ensure your computer and the Avalon are on the "1" subnet.

That is that they both have ip address on the "1"..... ex:  192.168.1.139

If you have DHCP configured on both your Avalon and router, then you will begin hashing automatically.

Check for DHCP on your Avalon.  I am sure your router is on DHCP.

I think your problem can be the broadcast ip address , I think it must to be 192.168.1.255. 

Now that you can log in on subnet "1"

Change your network protocol to DHCP:  path Network/Interfaces/Lan..... then change the protocol to DHCP.

You are going to loose connection....don't worry.  Change your computer's address back to the "0" subnet.  (ex: 192.168.0.121)  

Now log into your router.  Look for all your network devices ip addresses.  Get the new address for the Avalon.

Place that address in your browser and log into the Avalon.

DHCP is your problem.

Ok just plugged miner into back of my router hit  went to 192.168.1.139 and went straight in

i think it may be mining now all be it not to myself but does this indicate its working at least and i can continue to enter my pool details now?




thanks

honestly, your WiFi should work.

Just go through the setup to the end and then wait 30 seconds and it should pop up.

Router configuration

yes that is definitely correct. Just looked it up

if you want to do it via Ethernet you are going to need to configure your lan port on the Avalon box.


Network -> Interfaces -> LAN -> Edit -> Common Configuration -> General Setup

Hi thanks for staying with me  

they go like this top to bottom

IPv4 address                   original 192.168.0.100    changed to  192.168.1.139
IPv4 netmask                  original 255.255.255.0  (no change)
IPv4 gateway                 original 192.168.0.1     changed to 192.168.1.254  (which is address of my homehub)
IPv4 broadcast               original192.68.0.255     changed to 192.168.1.200
Use custom dns servers   original 192.168.0.1     changed to  4.2.2.2


just changed ipv4 lan adaptor to 192.168.1.123  and im back in the back end of the avalon now (one step forwards again)

studio:-
Yes to get into my homehub i type 192.168.1.254  does this sound right?>

Looks like you need to set up your network to DHCP, first.

Ensure your router is set for DHCP.

Change your computer's IP to the subnet of the Avalon clone. 

If 192.168.0.100 is the address of your Avalon, then make sure your computer's ip is on the same subnet.

"If Avalon is:  192.168.0.100 .... make your computer's address something like:  192.168.0.141"

(Ensuring your device count is set to reach that far on your router)

Once on the same subnet, you need to change the Avalon to accept "DHCP".

It look like you have it set to "Static address".  This will prevent connection and is your root problem....... so change it to DHCP.

Once you change it, you will loose communication with the Avalon, as your router will assign your Avalon a new "dynamic" ip address (automatically assigned by DHCP services).

Log into your router and view all of your devices on your network.  You should see a new ip address.

This address is assigned automatically when the network is set to DHCP.

Take the new ip and enter that address in your browser.  Login in and configure your Avalon for the pool of choice.

It should start hashing automatically.....sometimes it takes a few.  Especially on a new machine.

ok so 3rd box is gateway

is your router IP really 192.168.1.254?

sounds wrong to me it will be 192.168.1.1  I would have thought.

I can't remember the order the boxes are in on your photo, I will check but your settings look to be mixed up to me there. I can't see any that would correspond to your routers IP, which is what the gateway should be set to.

but back to the problem of why you can't connect now from your PC.

You can't connect via ethernet because your pc is now running on the incorrect subnet mask.

imagine it is like this

192 -- motorway

168 -- main road

1 -- street

139 - house number


You changed the street on your PC from 1 to 0

because you changed the ipv4 to 192.168.0.xxx

but your Avalon box is now on

192.168.1.139

so you need to go back into network settings and put your IPv4 back to 192.168.1.xxx

because at the moment it is knocking on the right house number but it is knocking on the wrong street.

tell me your router IP address and I will give you the correct settings.

Talk about one step forwards two steps back i couldn't get wifi to work but i pressed ahead and entered the network details as in the video because i thought it my work by Ethernet cable any way and that was how i was planning to mine in anycase.


i carefully followed the video did everything he said changed its details to same as my home hubs gateway created the miner a new i etc etc saved changes and now i cannot access it again .  My lan Ethernet ipv4 address in my computer has been changed to exactly the same address as the device 192.168.1.139 and now im back to square one with it and cannot long into the miner again  arrrgh!

Ive still got it plugged in by Ethernet direct to my laptop

i changed them from the following:-



to



And now i cant get to it on 192.168.0.100  or 192.168.1.139 or anything?  Scan in angry ip brings up nothing either ? 

im at a loss!

OK, it will do this.

When you go to enter the wireless key and select lan, it will go to the next page, where you choose WWFI

on this page it will show no connection and that it is not there.

click save and apply

it will go to the next page

wait around 30 seconds, it should show connected.

Ok thanks studio one halfway there now I managed to change my settings connect by Ethernet and get into it the unit at ip address  192.168.0.100.  

Been watching the video its should help me a lot thanks however hot a stumbling block at the wifi bit,

Although the unit finds my wifi when scanning it wont connect to it and show a signal even when ive entered the wireless key correctly??

Im using a homehub 3 do you think il need to change the encryption type channel or something apparently the homehub uses WPA by default ive tried that  but still no signal so it wont hook up to my wifi.  

Here, I found this for you, this is setting up a Avalon miner from factory settings

http://www.youtube.com/watch?v=If-padHumv4

Ok.

You are only changing your ipv4. The xxx means 3 random digits so say 192.268.0.123


Save and apply this

Then you need to go to your browser and type in the box ip which is now at factory default 192.168.0.100

You are not using a gateway as there is nothing between you and the avalon box. They are talking directly. What is important is that the box is on the same subnet mask as your pc so they can talk. I pad you my mobile if you need to alk.

Ok you will have to bear with me as my network experience is very limited so let me get this right so i know have it connected direct to my laptop by ethnet and this is what i do?

Go to control panel (network and internet)
then network and sharing center
then change adaptor settings
then right click on my LAN Ethernet adaptor
go to properties
go down to internet protocol ver 4 tcp/ipv4
go to its properties
change the  ip address to 192.168.0.xxx   (im assuming xxx means i leave the last three blank?)
then i change the subnet mask also to 192.168.0.xxx

what about the default gateway do i leave that empty?


Now do i run an ip scan?>  if so from which range to what?


thanks and sorry if ive asked some dummy questions there. 

Read my second post. You cannot connect via your router because the subnet mask has changed no scanner will see it. You can only connect via ether net direct from your pc.

You only need to change your ipv4 be case you are not connecting via a gateway.  As long as your ip is set to the same subnet mask you will be able to connect.

The machines ip is now 192.168.0.100


I have been through the exact same issue mate and fixed it. Follow these instructions exactly

Ok ive just had it plugged into back of my wireless home router scanned with angry ip from from my computer which is also connected to router by ethenet and its not found the machine it.  It just found printer and my other computers and my home adsl router itself.



Next im going to try SILVERBOX says attempt to plugged it direct into my laptop wifi disabled
go to PC under network find Ethernet connection and setup ipv 4 address to
192.168.0.127(PC or laptop).
subnet mask is 255.255.255.0,

and default gateway is going to be my miners ip?  which i dont know do i? So do i set it to?:  192.168.0.123

What do i do then scan again with angry ip see if anything shows?

Thanks  

I wouldn't trust sticker. scan IP range and see where u r. thus machine must show somewhere in the range given. try smart IP scanner.

I think the initial problem may have been something to do with the internet but at the moment i cant even find the miner and log into it at all since i did the configuration reset in the open wrt back end.  So my first hurdle is trying to get it showing again somehow so i can log in.,  I was able to log into it when i first received it on 192.168.1.139 (same as sticker on side of machine)

Can you ssh to the machine? Try ssh to it. And try to ping something like www.google.com

Just check the internet connection for the machine.

I think the problem may be the connection to Internet.

check range from 192.168.0.1 up to 192.168.2.254
this is Chinese clone if Avalon so who knows what's really IP address have.

Ive downloaded angry ip but which range should i be scanning to and from? 

Ive just logged into my bt homehub and its not showing as connected all i have is my two computers and printer.

OK, seems that machine has different ip than on sticker. try that:

download IP scanner and see what devices can u see connected in the network. same outcome u will have if u log in to your router and under devices there will be Ethernet device IP.

once u will find IP of the miner, u need to setup like new.

Ethernet cable to your laptop or PC.

dissabble WiFi on laptop or PC
under network find Ethernet connection and setup ipv 4 address which will look like miner address but will not be the same: 192.168.0.123(miner), 192.168.0.127(PC or laptop).
subnet mask is 255.255.255.0, and default gateway will be your miner IP.

once this is done just type in browser miner IP and you are in.

setup once again pool and of you go. under network option find wan - and setup dhcp as standard. miner will choose address and from there connect miner to rougher and check again under devices what ip miner have. once u got IP just login and miner should work. if not post log info here and we will see.

yes, you will need to connect direct via ethernet because 192.168.0.xxx is a different subnet mask to your router. You will also need to change your ethernet subnet mask IPv4 in network settings to the same subnet so assign your computer an IP address 192.168.0.xxx then connect directly via Ethernet

from there you can change the Avalon machine IP to the correct subnet mask in your routers range, don't worry you haven't bricked it, it has just gone back to factory default IP

@smoothrunnings

These machines are not made by Avalon but they are made using the Avalon 55nm 2nd generation chips. You can buy the chips direct from Avalon by the roll. There are loads of factories in China buying the chips, making PCBA and a control board then putting them inside a case.

Haha thats probably true like most things from china

Avalon doesn't make a 200GH/s mining rig. What you have is an Avalon clone/knock off.

Tried 192.168.0.100 but nothing

tried the original 192.168.1.139 which is what it came on and i could log in before but nothing now either.

Its plugged into the back of my home broadband router at the minute and ive just scanned with angry ip from 192.168.1.0 to 192.168.1.199 and it does findthe miner at all.

Im wondering if its bricked the wrt305?

What about if i connect it direct to my laptop by Ethernet would that work?

factory default setting for Avalon machines in 192.168.0.100

you will need to change your IPV4 subnet mask on your PC / laptop to 192.168.0.xxx

before adjusting CGMiner settings you need to go into startup, scrill down to CGMiner and click stop

then adjust the CGMiner settings and save and apply.

As CGMiner starts running autonatically on boot up you need to stop it before it can save any config changes


It is totally normal to receive them premined. Every supplier does it.

Hope this helps

Hi guys would have put this in the hardware section but im a newbie so cant post .


Because with bitcoin "money talks" im offering £25 or $40 donation on offer to anyone who can fix it and set it up,  if you can do this remotely on join me that would be useful.  Sorry i cant pay you by bit coin as i haven't mined any coins as yet lol  but i will paypal you the funds if you can fix it.   


Just took delivery today of an 200gh/s avalon clone? mining machine from china it looks like they've sent me a used machine (not impressed) but thought id boot it up sand give it a run.

Connected it to my pc, entered ip address (label on side of machine with ip address)

I filled out the pool details slushes and my wallet in slushes pool etc.

Unit powers up fan starts fast then settles down etc.

Everything seemed up just it wouldn't mine i noticed it had someone elses pool and network settings in there so it had obviously been used before and i was getting the following error :-

it was something like the below

luci-56acbaa
cgminer_openwrt-packages-d9bac89
socket connect failed: connection refused

tried rebooting it and and it was same i thought it may be because the other original user (in china assume) had his network settings so i thought if it could get the machine back to factory default somehow that would help me.

So i found a part on the system interface where you can back up your settings and configuration (i BACKED UP and saved it first ) then i pressed reset, it then displayed a screen saying (system erasing) the system is erasing the configuration partition now and will reboot itself when finished)

Well it was  like that for 2hr now  time just going round on timer,  ive opened and another browser and tried the ip address again and nothing comes up so i think this is some kind of master reset ive done??  ive tried the ip address 192.168.1.139 which was the one that it was on and nothing and ive tried the standard ip 192.168.1.1 nothing.

Tried switching power off and on on device it starts up as normal led goes to green the little internal router tp305n light flashes blue then goes to a constant blue led.

I have obviously saved the back up before i reset it but i dont know what to do now.   have i goosed the machine?

Im pretty mad that the supplier sent me a used machine in the first place with all his old network settings on etc ,  but now im really in it deep as i dont know what to do next with it.


Heres the last screen i saw and the back up file i took





Help ?


To make matters worse after a search ive found others reporting that the initial error i was getting and it could have been a simple router / network issue. Sad