|
Title: Anyone else having issues with their Antminer A3? Post by: Zand_ on January 24, 2018, 06:35:51 PM I received my A3 this afternoon and having been having some problems. When I first set it up, everything was working flawlessly. Hashing at 833GHs on Siamining, no HW errors, everything smooth. About 2 hours later I checked again and saw my hashrate dropped in half with a bunch of X's on one of the hashboards. Since then I've only been able to reach 500-600 GHs, and am getting HW errors on different boards whenever I refresh. Anyone else having issues? I would normally try reflashing the firmware but it's not available on Bitmain's support page.
Title: Re: Anyone else having issues with their Antminer A3? Post by: Marvell2 on January 24, 2018, 06:37:52 PM I would stop mining on sia pool, seems they are doing something to mess up A3's
Title: Re: Anyone else having issues with their Antminer A3? Post by: Zand_ on January 24, 2018, 06:40:36 PM Where do you recommend mining then?
Title: Re: Anyone else having issues with their Antminer A3? Post by: Marvell2 on January 24, 2018, 06:47:29 PM Where do you recommend mining then? suprnova is a fair poolTitle: Re: Anyone else having issues with their Antminer A3? Post by: Marvell2 on January 24, 2018, 06:50:51 PM nm looks like a false alarm maybe ddos on the pool
Title: Re: Anyone else having issues with their Antminer A3? Post by: kl4real on January 25, 2018, 05:19:43 AM can someone help me find my ip address for the A3?
using apw3++ on 110v connected on ethernet cable with orange light on and green light quickly blinking. red "fault" light is off and green "normal" light is steady slow blinking the only other light is a red light on top at the control board i am in california and have comcast cable i accessed my router admin page and searched the connected devices and it does not appear i have pushed the "ip report" button numerous times i have powered the unit on and off several times including my router i have pushed the "reset" several times for over 10 seconds and yes i felt the button inside click any advice? Title: Re: Anyone else having issues with their Antminer A3? Post by: hawkfish007 on January 25, 2018, 05:36:22 AM can someone help me find my ip address for the A3? using apw3++ on 110v connected on ethernet cable with orange light on and green light quickly blinking. red "fault" light is off and green "normal" light is steady slow blinking the only other light is a red light on top at the control board i am in california and have comcast cable i accessed my router admin page and searched the connected devices and it does not appear i have pushed the "ip report" button numerous times i have powered the unit on and off several times including my router i have pushed the "reset" several times for over 10 seconds and yes i felt the button inside click any advice? Access your router's settings page amd find attached devices. If the A3 is connected, it should show up as ANTMINER. Title: Re: Anyone else having issues with their Antminer A3? Post by: kl4real on January 25, 2018, 06:20:31 AM i did access the router settings page and looked at all of the devices that are connected and its not listed.
when i unplug the ethernet cable from the A3 it makes so fan adjustments and when i reconnect it - seems to "power" up again so it seems like there is a signal/connection with the ethernet cable Title: Re: Anyone else having issues with their Antminer A3? Post by: senseless on January 25, 2018, 06:23:36 AM I received my A3 this afternoon and having been having some problems. When I first set it up, everything was working flawlessly. Hashing at 833GHs on Siamining, no HW errors, everything smooth. About 2 hours later I checked again and saw my hashrate dropped in half with a bunch of X's on one of the hashboards. Since then I've only been able to reach 500-600 GHs, and am getting HW errors on different boards whenever I refresh. Anyone else having issues? I would normally try reflashing the firmware but it's not available on Bitmain's support page. Ya, sia coin developers were testing a soft fork to render the A3 useless. The total hashrate for the whole network dropped by almost half around 1:30PM EST. Hashrate dropped for all A3 on every pool simultaneously. Title: Re: Anyone else having issues with their Antminer A3? Post by: dlezama on January 25, 2018, 08:44:37 AM I would stop mining on sia pool, seems they are doing something to mess up A3's It wasn't siamining, it was the whole network (only A3s though). Nobody knows why yet.Title: Re: Anyone else having issues with their Antminer A3? Post by: dlezama on January 25, 2018, 08:49:10 AM I received my A3 this afternoon and having been having some problems. When I first set it up, everything was working flawlessly. Hashing at 833GHs on Siamining, no HW errors, everything smooth. About 2 hours later I checked again and saw my hashrate dropped in half with a bunch of X's on one of the hashboards. Since then I've only been able to reach 500-600 GHs, and am getting HW errors on different boards whenever I refresh. Anyone else having issues? I would normally try reflashing the firmware but it's not available on Bitmain's support page. Ya, sia coin developers were testing a soft fork to render the A3 useless. The total hashrate for the whole network dropped by almost half around 1:30PM EST. Hashrate dropped for all A3 on every pool simultaneously. It is true that every A3 on every pool dropped the hashrate. But, I don't see how the sia team could do that. That would require coordinating with all the pools, including p2pool that is not very friendly. I talked with a couple of pool owners today and they were investigating this, but they still have no clue. My theory is that this is a bug in the A3s, that was triggered by the block they were mining on top of at that point. But who knows. Some are thinking of antbleed stuff, after all bitmain hasn't published the A3 firmware yet. I see it very unlikely, especially since A3s didn't stop mining, just started to get an awful lot of calculation errors. Title: Re: Anyone else having issues with their Antminer A3? Post by: gabakusa on January 25, 2018, 03:51:21 PM I have a problem it will mine with the default config but as soon I add my info it wont do anything
https://www.photobox.co.uk/my/photo/full?photo_id=500529233636 https://www.photobox.co.uk/my/photo/full?photo_id=500529232198 I received my A3 this afternoon and having been having some problems. When I first set it up, everything was working flawlessly. Hashing at 833GHs on Siamining, no HW errors, everything smooth. About 2 hours later I checked again and saw my hashrate dropped in half with a bunch of X's on one of the hashboards. Since then I've only been able to reach 500-600 GHs, and am getting HW errors on different boards whenever I refresh. Anyone else having issues? I would normally try reflashing the firmware but it's not available on Bitmain's support page. Title: Re: Anyone else having issues with their Antminer A3? Post by: Ulewap on January 25, 2018, 08:33:57 PM Received mine today: first connection erros. then 1 board dead and the 2 that survived showed 0 hashing speed :'(
Title: Re: Anyone else having issues with their Antminer A3? Post by: kl4real on January 25, 2018, 09:53:33 PM @ulewap
how did you fix your connection error? do you have it plugged into a 110v or 220v? Title: Re: Anyone else having issues with their Antminer A3? Post by: DragosD1 on January 25, 2018, 10:12:05 PM Same here.
Connecting only on Antpool with factory settings, but as soon as I input my credentials, socket connection error, conection refused. As Antpool has removed SIA pool few hours ago, I tried Nicehash, same issue, then Nanopool, same issue, finally, it does connect to SiaMining. That's very strange! I'm having 220V, also few D3's running on same network with no issues. So it's not my network issue. Title: Re: Anyone else having issues with their Antminer A3? Post by: dlezama on January 26, 2018, 05:48:18 AM Same here. Not strange at all, from the ones you mention only siamining support it at the moment.Connecting only on Antpool with factory settings, but as soon as I input my credentials, socket connection error, conection refused. As Antpool has removed SIA pool few hours ago, I tried Nicehash, same issue, then Nanopool, same issue, finally, it does connect to SiaMining. That's very strange! I'm having 220V, also few D3's running on same network with no issues. So it's not my network issue. Title: Re: Anyone else having issues with their Antminer A3? Post by: kl4real on January 26, 2018, 06:51:30 AM does luxor support it?
Title: Re: Anyone else having issues with their Antminer A3? Post by: DragosD1 on January 26, 2018, 07:22:14 AM Yes, I can confirm, Luxor is on!
Also someone mentioned Suprnova, but pool is no longer available on Suprnova. So, only SiaMining and Luxor for now. Title: Re: Anyone else having issues with their Antminer A3? Post by: dlezama on January 26, 2018, 09:40:31 AM Yes, I can confirm, Luxor is on! Well, you do have p2pool too. They were mining empty blocks only, so nobody in the community would recommend them. Apparently they are including transactions now as of a few blocks back. If they're behaving, I don't see why not use them :)Also someone mentioned Suprnova, but pool is no longer available on Suprnova. So, only SiaMining and Luxor for now. Title: Re: Anyone else having issues with their Antminer A3? Post by: senseless on January 26, 2018, 02:31:06 PM Managed to get one unit stable at 61/62c on hashboards at 500mhz with 90% fan speed. The other unit is stable at 61/62C on hashboards at 550mhz with 90% fan speed. Others are saying you can push them up to 80C, but that will obviously reduce the lifespan of the device. (700Gh/s on one, 760Gh/s on the other)
Title: Re: Anyone else having issues with their Antminer A3? Post by: kl4real on January 26, 2018, 06:32:31 PM everything works fine on my A3 unit now since i switched from 110v to 220v
Title: Re: Anyone else having issues with their Antminer A3? Post by: greyday on January 27, 2018, 03:10:31 AM everything works fine on my A3 unit now since i switched from 110v to 220v Mine works fine on 110v. You just can't use the AW3 only, I have it powering the main boards and two of the hashing cards, a second PSU powering the last card. Not sure of my consumption yet, but it's running smoothly. I don't know what's up with pools, so far I've had no luck connecting to nanopool, and limited luck with Luxor (was working fine for a bit, now it claims my wallet/miner doesn't exist; they have a maintenance message up for the search function, but the instructions they give get the same "does not exist" result). Switched back over to--ung--antpool for now, as at least it is working well enough, though I can't seem to add my wallet to that one (it says it is emailing me and then doesn't). It'll probably be a little it before everything calms down and works right. EDIT: Nevermind, Luxor is working again. Seemed like the problem was just reporting, as my coin count is higher than when I stopped being able to check, so I'm pretty confident Luxor is a good place to point my rig for a while (plus they donate part of the pool profits to the sia devs, which I am all for)... Title: Re: Anyone else having issues with their Antminer A3? Post by: crypto.lawyer.187 on January 27, 2018, 04:30:46 AM I would stop mining on sia pool, seems they are doing something to mess up A3's It wasn't siamining, it was the whole network (only A3s though). Nobody knows why yet.i also have a dead hash board what does yours do Title: Re: Anyone else having issues with their Antminer A3? Post by: jessamp on January 27, 2018, 05:56:34 AM I just about fried mine LOL.. Out of the box in a 22C room temperature was running 85c. Did some reading, sounded normal, and read that other models have overheat protection.. So I mean this one should have it too right??
Then while I was having a drink it overheated, I seen 96C on screen before I could get to it and shut it down, went into fault mode, solid red light. Would not hash, HW errors in the 15k+ within a minute. was only reading 54 ASICS on one of the hash boards. WOW thought I really fried it... $3000 mistake FFS.. Reboot.. Nothing solid red light, power down and on, solid red light then one hash board 0 ASICS registered. I did a factory reset using a pin in the reset hole, then after doing up the settings, and another reboot it all came back working again thank heavens.. I'm not a farmer.. just getting into ASIC (last time I used an ASIC was in 2013ish), and $3000 is a chunk of change. So since I live in Canada and it's winter here, an open window with a box fan blowing in cold air to cool the entire room is working good. Temps are stable at 79, 69, and 83, factory clock. Why didn't they put an overheat protection on the A3 like other models?? I have owned an A3 for 7 hours and I'm scared to leave my house now... Title: Re: Anyone else having issues with their Antminer A3? Post by: Marvell2 on January 27, 2018, 06:01:40 AM I just about fried mine LOL.. Out of the box in a 22C room temperature was running 85c. Did some reading, sounded normal, and read that other models have overheat protection.. So I mean this one should have it too right?? Then while I was having a drink it overheated, I seen 96C on screen before I could get to it and shut it down, went into fault mode, solid red light. Would not hash, HW errors in the 15k+ within a minute. was only reading 54 ASICS on one of the hash boards. WOW thought I really fried it... $3000 mistake FFS.. Reboot.. Nothing solid red light, power down and on, solid red light then one hash board 0 ASICS registered. I did a factory reset using a pin in the reset hole, then after doing up the settings, and another reboot it all came back working again thank heavens.. I'm not a farmer.. just getting into ASIC (last time I used an ASIC was in 2013ish), and $3000 is a chunk of change. So since I live in Canada and it's winter here, an open window with a box fan blowing in cold air to cool the entire room is working good. Temps are stable at 79, 69, and 83, factory clock. Why didn't they put an overheat protection on the A3 like other models?? I have owned an A3 for 7 hours and I'm scared to leave my house now... those are stull high temps for the top and bottom chains, id down clock to 575 Title: Re: Anyone else having issues with their Antminer A3? Post by: jessamp on January 27, 2018, 06:19:09 AM those are stull high temps for the top and bottom chains, id down clock to 575 Noted.. I'm dropping ASICS on chain 3 again. FML.. Room temp is about 16C now. Is it safe to run with a couple dropped chips? or should I reboot a few times and get em to kick in again? Title: Re: Anyone else having issues with their Antminer A3? Post by: Marvell2 on January 27, 2018, 06:47:24 AM those are stull high temps for the top and bottom chains, id down clock to 575 Noted.. I'm dropping ASICS on chain 3 again. FML.. Room temp is about 16C now. Is it safe to run with a couple dropped chips? or should I reboot a few times and get em to kick in again? you dont want to be running with any dropped chips , no , just keep downclocking till you have less hardware errors over three hours , less than 100 or so then slowly raise clocks till you find a stable setting and temps around 75-ish to 77 max on chips pcb temps are fine around 50-65 is your fan set to 100% ? I run in a climate controled serve room with lots of heat exhaust and I still have to set my fans to 100% Im running stock settings Title: Re: Anyone else having issues with their Antminer A3? Post by: jessamp on January 27, 2018, 06:51:03 AM yeah my HW errors are off the charts now.. was running fine before, definitely damage caused
Title: Re: Anyone else having issues with their Antminer A3? Post by: jessamp on January 28, 2018, 08:00:00 AM I have been playing with all different clock levels and Hash Board #3 is consistently between 5 to 10 degrees hotter than the rest.. I assume it's because the chips and heat sinks are on the outside and lacking air flow. Suppose I open the thing, and reverse the hash board.. I can dremel some new holes if necessary... I have 700mhz running stable now cause I am in winter in Canada and my mining room is only 10C right now LOL.... temps are 74,64,82 So obviously airflow to outside boards are the problem, and I would assume board 3 was designed the wrong way fir air LOL just thoughts.. Also only running 57 ASICS on board 3 cause earlier problems... I like to live dangerously
Title: Re: Anyone else having issues with their Antminer A3? Post by: furqan7 on January 28, 2018, 11:59:25 AM Hi guys,
I had the same issues that you guys mentioned. I assumed maybe like the rest i also had hardware issues but apparently the issue was resolved by doing a reset or a power cycle. Sometimes the temps get high after power cycle which didnt make any sense as the room temp and when previously it was running smoothly were low. It didnt look like a hardware problem but a software problem. Sometimes i had just 1 X and sometimes one of the entire boards showed xxxx. Checked the wires .. Did a power cycle which helped once. Then at the next power cycle it just was full of errors. Now after a factory reset its working fine and temps are 80 or below. Hopefully it will stay the same. I was mining before on siamining but have changed to luxor. Works good so far. Hopefully u get to fix urs. P.S. I had factory reset it a couple of times. Title: Re: Anyone else having issues with their Antminer A3? Post by: MagicSmoker on January 28, 2018, 12:05:10 PM Managed to get one unit stable at 61/62c on hashboards at 500mhz with 90% fan speed. The other unit is stable at 61/62C on hashboards at 550mhz with 90% fan speed. Others are saying you can push them up to 80C, but that will obviously reduce the lifespan of the device. (700Gh/s on one, 760Gh/s on the other) Aye, high temperature is the enemy of electronics - about a 50% reduction in lifespan for every 10-11C increase in temp - but an ASIC miner is only cashflow positive for a few months anyway, isn't it? Title: Re: Anyone else having issues with their Antminer A3? Post by: senseless on January 28, 2018, 12:44:36 PM I have been playing with all different clock levels and Hash Board #3 is consistently between 5 to 10 degrees hotter than the rest.. I assume it's because the chips and heat sinks are on the outside and lacking air flow. Suppose I open the thing, and reverse the hash board.. I can dremel some new holes if necessary... I have 700mhz running stable now cause I am in winter in Canada and my mining room is only 10C right now LOL.... temps are 74,64,82 So obviously airflow to outside boards are the problem, and I would assume board 3 was designed the wrong way fir air LOL just thoughts.. Also only running 57 ASICS on board 3 cause earlier problems... I like to live dangerously Started playing around a little this AM myself. At default freq and 95% fan the 2 outside boards are the same temp for me. 76/69/77 & 75/68/76. They're just not getting the same amount of airflow as that center board. It might be more effective to take these things out of the case and get better airflow over all boards. Should be possible to get the temps down to reasonable levels at 600mhz. I'm thinking, custom case to house the hashing boards. Title: Re: Anyone else having issues with their Antminer A3? Post by: jessamp on January 28, 2018, 07:41:22 PM Hi guys, I had the same issues that you guys mentioned. I assumed maybe like the rest i also had hardware issues but apparently the issue was resolved by doing a reset or a power cycle. Sometimes the temps get high after power cycle which didnt make any sense as the room temp and when previously it was running smoothly were low. It didnt look like a hardware problem but a software problem. Sometimes i had just 1 X and sometimes one of the entire boards showed xxxx. Checked the wires .. Did a power cycle which helped once. Then at the next power cycle it just was full of errors. Now after a factory reset its working fine and temps are 80 or below. Hopefully it will stay the same. I was mining before on siamining but have changed to luxor. Works good so far. Hopefully u get to fix urs. P.S. I had factory reset it a couple of times. Yeah I not had any X's or -'s or anything other than 0's in the status area, but I am only counting 57 ASICs on chain 3, and there are 3 missing 0's. Sometimes I get CRC errors in the log on bootup, and have to reboot a few times to get it running. Hopefully it lasts long enough to pay for itself. Title: Re: Anyone else having issues with their Antminer A3? Post by: senseless on January 28, 2018, 09:05:07 PM One of my hashboards crashed at 600mhz running at 77C after about 8 hours. Hashboard came back after a restart. Moved both machines back down to 550mhz.
77C is NOT stable. Now running 65/64/71, 62/64/65 at 550mhz with 95% fan. Stable so far. Title: Re: Anyone else having issues with their Antminer A3? Post by: jessamp on January 28, 2018, 10:46:45 PM One of my hashboards crashed at 600mhz running at 77C after about 8 hours. Hashboard came back after a restart. Moved both machines back down to 550mhz. 77C is NOT stable. Now running 65/64/71, 62/64/65 at 550mhz with 95% fan. Stable so far. Yeah I pulled back down to 650 after my crash at 700. But I am running 650 and now only 69C on hottest board. Title: Re: Anyone else having issues with their Antminer A3? Post by: kl4real on January 29, 2018, 03:56:04 AM Hi guys, I had the same issues that you guys mentioned. I assumed maybe like the rest i also had hardware issues but apparently the issue was resolved by doing a reset or a power cycle. Sometimes the temps get high after power cycle which didnt make any sense as the room temp and when previously it was running smoothly were low. It didnt look like a hardware problem but a software problem. Sometimes i had just 1 X and sometimes one of the entire boards showed xxxx. Checked the wires .. Did a power cycle which helped once. Then at the next power cycle it just was full of errors. Now after a factory reset its working fine and temps are 80 or below. Hopefully it will stay the same. I was mining before on siamining but have changed to luxor. Works good so far. Hopefully u get to fix urs. P.S. I had factory reset it a couple of times. i had it on luxor several days ago but then they were having some display error so i switched to siamining - but it seemed luxor was producing more. i'm averaging 825gh/s on siamining and getting 51 sc per hour/ 1,457 sc for last 24 hr. what are you getting on luxor? Title: Re: Anyone else having issues with their Antminer A3? Post by: greyday on February 01, 2018, 01:40:16 AM One of my hashboards crashed at 600mhz running at 77C after about 8 hours. Hashboard came back after a restart. Moved both machines back down to 550mhz. 77C is NOT stable. Now running 65/64/71, 62/64/65 at 550mhz with 95% fan. Stable so far. Yeah I pulled back down to 650 after my crash at 700. But I am running 650 and now only 69C on hottest board. 619 @78% fan for me. Runs smoothly, not TOO loud (over 85% and the vibrations come through the floor), and temps all in the low 70s. Title: Re: Anyone else having issues with their Antminer A3? Post by: greyday on February 01, 2018, 01:51:00 AM i had it on luxor several days ago but then they were having some display error so i switched to siamining - but it seemed luxor was producing more. i'm averaging 825gh/s on siamining and getting 51 sc per hour/ 1,457 sc for last 24 hr. what are you getting on luxor? The display error was just with using the search function to view your account. I've been mining there for almost a week with no issues on that end (you can just paste your wallet onto the end of the url for the same result). My only problem was a payment that didn't go through but that turned out to be solved by doing a recovery of the wallet (rescanning the blockchain). Luxor wasn't super helpful on the support end for that, but the coins weren't lost so I'm not complaining... Title: Re: Anyone else having issues with their Antminer A3? Post by: senseless on February 01, 2018, 07:03:13 PM Underclocked today to 350mhz.
Power consumption 3A @ 240V (720W) (-50%) Hashrate 520Gh/s (-35%) Ghs / Watt 0.72 (+21%) Default settings: 600mhz Power consumption 6A @ 240v (1440W) Hashrate 810Gh/s Gh/s / Watt 0.5625 Title: Re: Anyone else having issues with their Antminer A3? Post by: greyday on February 01, 2018, 08:37:02 PM Underclocked today to 350mhz. Power consumption 3A @ 240V (720W) (-50%) Hashrate 520Gh/s (-35%) Ghs / Watt 0.72 (+21%) Default settings: 600mhz Power consumption 6A @ 240v (1440W) Hashrate 810Gh/s Gh/s / Watt 0.5625 Those are great "space heater" settings, actually. Keeping them for when the A3 becomes barely profitable, thanks! Title: Re: Anyone else having issues with their Antminer A3? Post by: Staber on February 02, 2018, 05:39:46 AM Guy, can anyone tell please whats happened?
my a3 works all nights, everything is ok but still 0 in a balance. what's the problem? Title: Re: Anyone else having issues with their Antminer A3? Post by: dlezama on February 02, 2018, 06:11:17 AM Guy, can anyone tell please whats happened? You're not using antpool are you? Use siaminingmy a3 works all nights, everything is ok but still 0 in a balance. what's the problem? Title: Re: Anyone else having issues with their Antminer A3? Post by: Staber on February 02, 2018, 06:40:21 AM yes, I'm using antpool.
but why I can not use it? Title: Re: Anyone else having issues with their Antminer A3? Post by: dlezama on February 02, 2018, 06:44:31 AM yes, I'm using antpool. They never found a block, and they pay PPLNS, that means they never paid anything. I think their pool is broken. There are currently 3 pools that work with the A3:but why I can not use it? https://www.f2pool.com/ (https://www.f2pool.com/) https://siamining.com/ (https://siamining.com/) http://mining.luxor.tech/ (http://mining.luxor.tech/) The three of them pay PPS with 3% fee. I recommend siamining, but you can choose the one you like. Title: Re: Anyone else having issues with their Antminer A3? Post by: Staber on February 02, 2018, 06:49:36 AM thank you so much for your reply! I'll go to siaming
Title: Re: Anyone else having issues with their Antminer A3? Post by: jsen14 on February 02, 2018, 01:46:39 PM Hi guys, can use some opinions on why my A3 is not working. Situation:
I purchased a few A3 and set them up at home. Had a hell of a time figuring out the "No Socket Connection" errors until I determined that SiaMining was the only thing that got it to run. At home, I run 240v and they were powered on one Bitmain APW3 PSU. Ran beautifully. I sold one to a friend. He set it up with the following: 120V 2 850W power supplies (1 powering 2 boards, the other powering the main control board and the 3rd board) No matter what we did, we could not get his to mine. We tried all of the following: 1. Reflashing the firmware. 2. Giving the miner a static IP address on the network 3. Multiple reboots 4. Multiple Resets to default settings. 5. Unplugging and re-powering After the static IP failed to work, I tried to revert it to a DHCP Ip address, and here's where we are now stuck. Now, the miner shows me nothing on the General Overview Page. Everything on that page is completely blank for the System fields, and all of the Memory status bars are at 0. I tried re-flashing the firmware again, and still everything is blank, and I cannot even click on any other tabs within the antminer menu. I cannot click on Configuration, or Status, or Network. He lives in a colder climate and just got the machine yesterday, so I told him to unplug it for the night and let it get to room temp indoors before we try again. As we were troubleshooting, the A3 was on high speed with the fan, so I am wondering if it was overheated after being delivered in the cold. Any advice on what else to try is extremely appreciated. Title: Re: Anyone else having issues with their Antminer A3? Post by: jessamp on February 02, 2018, 07:47:03 PM Hi guys, can use some opinions on why my A3 is not working. Situation: I purchased a few A3 and set them up at home. Had a hell of a time figuring out the "No Socket Connection" errors until I determined that SiaMining was the only thing that got it to run. At home, I run 240v and they were powered on one Bitmain APW3 PSU. Ran beautifully. I sold one to a friend. He set it up with the following: 120V 2 850W power supplies (1 powering 2 boards, the other powering the main control board and the 3rd board) No matter what we did, we could not get his to mine. We tried all of the following: 1. Reflashing the firmware. 2. Giving the miner a static IP address on the network 3. Multiple reboots 4. Multiple Resets to default settings. 5. Unplugging and re-powering After the static IP failed to work, I tried to revert it to a DHCP Ip address, and here's where we are now stuck. Now, the miner shows me nothing on the General Overview Page. Everything on that page is completely blank for the System fields, and all of the Memory status bars are at 0. I tried re-flashing the firmware again, and still everything is blank, and I cannot even click on any other tabs within the antminer menu. I cannot click on Configuration, or Status, or Network. He lives in a colder climate and just got the machine yesterday, so I told him to unplug it for the night and let it get to room temp indoors before we try again. As we were troubleshooting, the A3 was on high speed with the fan, so I am wondering if it was overheated after being delivered in the cold. Any advice on what else to try is extremely appreciated. I don't think 850w is enough to power 2 boards. I am using 2x 750w supplies, but also using breakout boards to manage power distribution and fault protection. Hash board #2 is being powered by both supplies. But a single board can draw up to 520w according to specs. So try underclocking to like 350mhz, get it to boot up, then move up until you find your highest stable level. Title: Re: Anyone else having issues with their Antminer A3? Post by: jsen14 on February 02, 2018, 08:22:54 PM We're using 2x 850W power supplies.
I can't even get to the screen to adjust frequency, with everything blank on the main screen. Title: Re: Anyone else having issues with their Antminer A3? Post by: jsen14 on February 02, 2018, 08:36:05 PM Nevermind I just re-read that. I see what you mean about the PSU not being enough.
We do have a Bitmain Apw PSU, but we're running 120V. How would you recommend utilizing 1 Bitmain PSU and 2 850W PSUs to power this thing at 120v? Title: Re: Anyone else having issues with their Antminer A3? Post by: jessamp on February 02, 2018, 08:42:29 PM We're using 2x 850W power supplies. I can't even get to the screen to adjust frequency, with everything blank on the main screen. Yes but you are using 2x PSUs without power distribution. So you have 1 PSU connected to 2 boards, which could take up to 1050w. 425w is not necessarily enough to boot up 1 board if they are specified 525w each. I have power distribution circuit boards, so I can use 2 PSUs on the same board.. Try disconnecting all hash boards, and only boot up the control unit only. Then configure to low clock, then re-connect everything and power on again. But if you mean blank, as in White page, no menu, can't click Configuration at all, then it sounds like you lost your firmware. If so.. Then no clue what to tell you... Can you get SSH access?? If so then possible for someone here to send you a copy of the firmware if you trust it for no viruses .. LOL ;) Bitmain has not posted a copy of firmware yet... Just thoughts Title: Re: Anyone else having issues with their Antminer A3? Post by: jsen14 on February 02, 2018, 08:46:03 PM Thanks for the help. Will try this.
I have a copy of the firmware, Bitmain emailed it to me in a support ticket. And I've tried reflashing it to no avail. But I will try to do this when powering up only the main board and let you know. Thanks again. Title: Re: Anyone else having issues with their Antminer A3? Post by: jsen14 on February 02, 2018, 08:52:14 PM This is likely a noob question, but how does one SSH into a miner?
Title: Re: Anyone else having issues with their Antminer A3? Post by: shellyfinest on February 02, 2018, 09:00:15 PM If your home breaker panel can handle it, request a contractor or electrician to install a 240V outlet with
*sorry 30amp is too much, I stand corrected in the comment after mine Title: Re: Anyone else having issues with their Antminer A3? Post by: jessamp on February 02, 2018, 09:19:30 PM SSH on Windblows, use a program like putty (never used it, Windblows sucks)
On Linux use SSH command (duh) ssh -p 22 root@192.168.?.? <-whatever your miner's IP is.. user is root pass is admin (default bitmain user settings) Not liable for what you do with this info.. And I am not sure exactly how to do up the firmware, have to check Bitmain instructions for that. Haven't done it. Highly suggest getting a Google PHD before you try anything stupid.. And a 30 amp 220v outlet is overkill, I'd just use 10 amp 220, unless you are going to connect power distribution unit to it. 30amp 220v will run 3 APW3's. But without a PDU, if you have a faulty power supply, (over heating, short circuit etc..), it will not kick off the breaker if you are running a 10amp PSU on a 30 amp circuit, will just run til it lights on fire.. Safety concern there. Title: Re: Anyone else having issues with their Antminer A3? Post by: greyday on February 02, 2018, 11:50:12 PM Nevermind I just re-read that. I see what you mean about the PSU not being enough. We do have a Bitmain Apw PSU, but we're running 120V. How would you recommend utilizing 1 Bitmain PSU and 2 850W PSUs to power this thing at 120v? I'm also running 120; my set up is, currently, one APW-3 on two boards and the mains, one 650W PSU on the remaining board. Once the profit decreases significantly, I will undervolt and leave it on just the APW3, but the current hashrate is worth the electrical cost. Title: Re: Anyone else having issues with their Antminer A3? Post by: STATIK on February 03, 2018, 05:34:07 PM Nevermind I just re-read that. I see what you mean about the PSU not being enough. We do have a Bitmain Apw PSU, but we're running 120V. How would you recommend utilizing 1 Bitmain PSU and 2 850W PSUs to power this thing at 120v? I'm also running 120; my set up is, currently, one APW-3 on two boards and the mains, one 650W PSU on the remaining board. Once the profit decreases significantly, I will undervolt and leave it on just the APW3, but the current hashrate is worth the electrical cost. If you want it to run APW efficently get a 220v basically 2 live wires and a neutral with a 20amp breaker ideally you want to run the sucker on a single PSU and 220v is the way to go Title: Re: Anyone else having issues with their Antminer A3? Post by: STATIK on February 03, 2018, 05:39:30 PM STATIC network settings do not work unless you have a static IP, if you run a modem and a router and obtain dynamic IP you should use DHCP network settings instead. Cold air intake is a must if in a heated environment.
Support Sia by mining their pool Title: Re: Anyone else having issues with their Antminer A3? Post by: nuanicaj on February 03, 2018, 06:15:56 PM i did access the router settings page and looked at all of the devices that are connected and its not listed. when i unplug the ethernet cable from the A3 it makes so fan adjustments and when i reconnect it - seems to "power" up again so it seems like there is a signal/connection with the ethernet cable When I setup my device.. Window Edge didn't let me in.. I download Opera Browser and was able. Check you router for any lan connected mine didn't show Antmine it was lan connected port 192.168.1.168 Hope that help. just check any lan connect port. if you can't login in root root get a different browser .. Edge sucks. Title: Re: Anyone else having issues with their Antminer A3? Post by: greyday on February 03, 2018, 08:05:49 PM Nevermind I just re-read that. I see what you mean about the PSU not being enough. We do have a Bitmain Apw PSU, but we're running 120V. How would you recommend utilizing 1 Bitmain PSU and 2 850W PSUs to power this thing at 120v? I'm also running 120; my set up is, currently, one APW-3 on two boards and the mains, one 650W PSU on the remaining board. Once the profit decreases significantly, I will undervolt and leave it on just the APW3, but the current hashrate is worth the electrical cost. If you want it to run APW efficently get a 220v basically 2 live wires and a neutral with a 20amp breaker ideally you want to run the sucker on a single PSU and 220v is the way to go I already had the 650 lying around. I don't have room in my panel for another 220 right now (only space left is for a breaker box for an add on project), hence 110. :) Title: Re: Anyone else having issues with their Antminer A3? Post by: sk8rax350 on February 03, 2018, 10:50:54 PM I have my A3 running at stock frequency with one APW3++ @ 115v (per my Kil-a-watt) with no problems since I got it. Why are you guys hooking up more PSUs to yours, if you are already using an APW3++? I don't even have the benefit of cold weather, with the high being in the 80s Fahrenheit lately.
Title: Re: Anyone else having issues with their Antminer A3? Post by: dlezama on February 03, 2018, 11:09:30 PM I have my A3 running at stock frequency with one APW3++ @ 115v (per my Kil-a-watt) with no problems since I got it. Why are you guys hooking up more PSUs to yours, if you are already using an APW3++? I don't even have the benefit of cold weather, with the high being in the 80s lately. APW3++ are 1200W at 110V. Miner is about 1350W What you're doing may be working, but you're pushing the PSU outside the specs, and that is a risk.Title: Re: Anyone else having issues with their Antminer A3? Post by: greyday on February 04, 2018, 12:20:21 AM I have my A3 running at stock frequency with one APW3++ @ 115v (per my Kil-a-watt) with no problems since I got it. Why are you guys hooking up more PSUs to yours, if you are already using an APW3++? I don't even have the benefit of cold weather, with the high being in the 80s lately. APW3++ are 1200W at 110V. Miner is about 1350W What you're doing may be working, but you're pushing the PSU outside the specs, and that is a risk.Seconded. I suggest switching to 220 or adding a second PSU for one of the cards. Also keep in mind that if you're on a 15a circuit, you're pushing its limits and likely those of the wiring. Title: Re: Anyone else having issues with their Antminer A3? Post by: STATIK on February 04, 2018, 04:58:47 AM I have my A3 running at stock frequency with one APW3++ @ 115v (per my Kil-a-watt) with no problems since I got it. Why are you guys hooking up more PSUs to yours, if you are already using an APW3++? I don't even have the benefit of cold weather, with the high being in the 80s lately. APW3++ are 1200W at 110V. Miner is about 1350W What you're doing may be working, but you're pushing the PSU outside the specs, and that is a risk.Title: Re: Anyone else having issues with their Antminer A3? Post by: sk8rax350 on February 04, 2018, 07:04:39 AM I have my A3 running at stock frequency with one APW3++ @ 115v (per my Kil-a-watt) with no problems since I got it. Why are you guys hooking up more PSUs to yours, if you are already using an APW3++? I don't even have the benefit of cold weather, with the high being in the 80s lately. APW3++ are 1200W at 110V. Miner is about 1350W What you're doing may be working, but you're pushing the PSU outside the specs, and that is a risk.Per Bitmain, the A3 is 1,186 watts DC. The power coming out of your wall is AC. The PSU converts AC to usable DC power, with some loss in the conversion process, leading to a higher draw in AC power at the wall than provided to the miner in DC. The only things one APW3++ can't solely power on 110v within specs at stock frequency, with its 1,200 watts DC max, are most S9s (11.5 TH/s batch excluded) and the T9. The APW3++ is operating within its specs, even if it is close to the top with the A3. Title: Re: Anyone else having issues with their Antminer A3? Post by: sk8rax350 on February 04, 2018, 07:15:07 AM I have my A3 running at stock frequency with one APW3++ @ 115v (per my Kil-a-watt) with no problems since I got it. Why are you guys hooking up more PSUs to yours, if you are already using an APW3++? I don't even have the benefit of cold weather, with the high being in the 80s lately. APW3++ are 1200W at 110V. Miner is about 1350W What you're doing may be working, but you're pushing the PSU outside the specs, and that is a risk.Seconded. I suggest switching to 220 or adding a second PSU for one of the cards. Also keep in mind that if you're on a 15a circuit, you're pushing its limits and likely those of the wiring. 220V would be optimal, with better efficiency from the PSU, but a 15A 110V circuit is plenty capable of handling the load. I wouldn't recommend much more of anything on the circuit though. Don't forget to gauge your PSU power cord properly, especially if you go the single PSU route like I am! Title: Re: Anyone else having issues with their Antminer A3? Post by: sk8rax350 on February 04, 2018, 07:23:12 AM I have my A3 running at stock frequency with one APW3++ @ 115v (per my Kil-a-watt) with no problems since I got it. Why are you guys hooking up more PSUs to yours, if you are already using an APW3++? I don't even have the benefit of cold weather, with the high being in the 80s lately. APW3++ are 1200W at 110V. Miner is about 1350W What you're doing may be working, but you're pushing the PSU outside the specs, and that is a risk.My 830GH/s average at the stock frequency of 600 says differently! 8) Title: Re: Anyone else having issues with their Antminer A3? Post by: dlezama on February 04, 2018, 10:17:33 AM I have my A3 running at stock frequency with one APW3++ @ 115v (per my Kil-a-watt) with no problems since I got it. Why are you guys hooking up more PSUs to yours, if you are already using an APW3++? I don't even have the benefit of cold weather, with the high being in the 80s lately. APW3++ are 1200W at 110V. Miner is about 1350W What you're doing may be working, but you're pushing the PSU outside the specs, and that is a risk.Per Bitmain, the A3 is 1,186 watts DC. The power coming out of your wall is AC. The PSU converts AC to usable DC power, with some loss in the conversion process, leading to a higher draw in AC power at the wall than provided to the miner in DC. The only things one APW3++ can't solely power on 110v within specs at stock frequency, with its 1,200 watts DC max, are most S9s (11.5 TH/s batch excluded) and the T9. The APW3++ is operating within its specs, even if it is close to the top with the A3. I have 220V installation and most miners do because server PSUs usually give you more watts at 220V and you can take advantage of that. PSUs are usually more efficient at 220V too. Also, dealing with half the amps help with breakers, cables, etc... Title: Re: Anyone else having issues with their Antminer A3? Post by: greyday on February 04, 2018, 12:50:58 PM I have my A3 running at stock frequency with one APW3++ @ 115v (per my Kil-a-watt) with no problems since I got it. Why are you guys hooking up more PSUs to yours, if you are already using an APW3++? I don't even have the benefit of cold weather, with the high being in the 80s lately. APW3++ are 1200W at 110V. Miner is about 1350W What you're doing may be working, but you're pushing the PSU outside the specs, and that is a risk.Per Bitmain, the A3 is 1,186 watts DC. The power coming out of your wall is AC. The PSU converts AC to usable DC power, with some loss in the conversion process, leading to a higher draw in AC power at the wall than provided to the miner in DC. The only things one APW3++ can't solely power on 110v within specs at stock frequency, with its 1,200 watts DC max, are most S9s (11.5 TH/s batch excluded) and the T9. The APW3++ is operating within its specs, even if it is close to the top with the A3. I have 220V installation and most miners do because server PSUs usually give you more watts at 220V and you can take advantage of that. PSUs are usually more efficient at 220V too. Also, dealing with half the amps help with breakers, cables, etc... The page does say that now, but as you rightly point out, draw at the wall is being reported much higher. Then again, maybe the March batch runs more efficiently? Makes me think of the D3, which is currently listed as being stock @ 15gh/s at the same 1200 wattage as the batch I got (which was listed and defaults @ 19gh/s). Not sure if the hardware is different, but considering that with BlissZ's firmware I can get 15gh/s out of mine @750...I trust my kill-o-watt way more than I trust Bitmain's numbers, especially when the listing isn't the same batch as the miner I'm using. Half the amps is somewhat of a misnomer, you can run twice the amperage of a 220v intake breaker at 110v. The amperage on a breaker is a safety cut off, you still calculate the total wattage. Not really relevant either way, though, since 220s take up twice the space as 110s in the breaker box anyway... And second vote in most cases for 220 (even though all my rigs are 110), PSUs and especially server PSUs run around 5% more efficiently (iirc) at 220. But at gold rating and above that discrepancy diminishes (or so I'm told, I can't currently do a comparison). Title: Re: Anyone else having issues with their Antminer A3? Post by: Ulewap on February 06, 2018, 09:04:27 PM @ulewap how did you fix your connection error? do you have it plugged into a 110v or 220v? 220v. but had to send it back to china... will receive it hopefully in a few days. see if I can mine some sia if there is some left to mine Title: Re: Anyone else having issues with their Antminer A3? Post by: STATIK on February 07, 2018, 01:02:21 AM I have my A3 running at stock frequency with one APW3++ @ 115v (per my Kil-a-watt) with no problems since I got it. Why are you guys hooking up more PSUs to yours, if you are already using an APW3++? I don't even have the benefit of cold weather, with the high being in the 80s lately. APW3++ are 1200W at 110V. Miner is about 1350W What you're doing may be working, but you're pushing the PSU outside the specs, and that is a risk.My 830GH/s average at the stock frequency of 600 says differently! 8) Title: Re: Anyone else having issues with their Antminer A3? Post by: Blkmktinsurance on February 08, 2018, 09:34:12 PM i had a problem with a string of asics giving X's.
I changed the frequency from 600 to 550 it worked, once stable, slowly increased back to 600. stable 2 days now Title: Re: Anyone else having issues with their Antminer A3? Post by: STATIK on February 11, 2018, 07:07:39 AM https://file.bitmain.com/shop-file-server/firmwares/Antiminer%20A3/Manual/007201802091050251715B3L9tLw0659/A3%20installation%20guide.pdf
Title: Re: Anyone else having issues with their Antminer A3? Post by: btcneodev on February 12, 2018, 01:35:57 AM i had a problem with a string of asics giving X's. I changed the frequency from 600 to 550 it worked, once stable, slowly increased back to 600. stable 2 days now Yes, it is always suggested to lower the frequency at the beginning, then slowly increase it. Same job on every miner including GPU. Title: Re: Anyone else having issues with their Antminer A3? Post by: STATIK on February 12, 2018, 01:37:36 AM Thanks for the help. Will try this. I have the same problem with you about the A3....I can't connect to A3 miner status, miner configuration , etc. Just blank overview page.I have a copy of the firmware, Bitmain emailed it to me in a support ticket. And I've tried reflashing it to no avail. But I will try to do this when powering up only the main board and let you know. Thanks again. Did you solve your problem already? Title: Re: Anyone else having issues with their Antminer A3? Post by: STATIK on February 12, 2018, 05:44:08 AM My A3 problem is when it started as soon as the fan blowing fast, the red led was blinking and then the fan slow again. And then the fan started blowing fast and the red led was blinking and the fan slowing again. And it repeating itself on this condition. So you are saying you cannot change between pages over to NETWORK settings?I can't get into A3 monitoring page. I get blank info and can't go to miner status, configuration, network etc. I resetted several time but the problem still the same. Any help?? here the video of this problem https://www.youtube.com/watch?v=TnlaL6h9kHc Title: Re: Anyone else having issues with their Antminer A3? Post by: greyday on February 12, 2018, 07:25:07 AM My A3 problem is when it started as soon as the fan blowing fast, the red led was blinking and then the fan slow again. And then the fan started blowing fast and the red led was blinking and the fan slowing again. And it repeating itself on this condition. I can't get into A3 monitoring page. I get blank info and can't go to miner status, configuration, network etc. I resetted several time but the problem still the same. Any help?? here the video of this problem https://www.youtube.com/watch?v=TnlaL6h9kHc You may need to try booting from a microSD card. There are instrux on Bitmain's support page... Title: Re: Anyone else having issues with their Antminer A3? Post by: jessamp on February 12, 2018, 03:33:46 PM My A3 problem is when it started as soon as the fan blowing fast, the red led was blinking and then the fan slow again. And then the fan started blowing fast and the red led was blinking and the fan slowing again. And it repeating itself on this condition. I can't get into A3 monitoring page. I get blank info and can't go to miner status, configuration, network etc. I resetted several time but the problem still the same. Any help?? here the video of this problem https://www.youtube.com/watch?v=TnlaL6h9kHc Hashboard fault. Either due to corrupt firmware, or faulty/damaged hash board. Check the Kernel Log while it is booting up. You should be able to see errors in there. Title: Re: Anyone else having issues with their Antminer A3? Post by: STATIK on February 13, 2018, 05:07:46 AM My A3 problem is when it started as soon as the fan blowing fast, the red led was blinking and then the fan slow again. And then the fan started blowing fast and the red led was blinking and the fan slowing again. And it repeating itself on this condition. So you are saying you cannot change between pages over to NETWORK settings?I can't get into A3 monitoring page. I get blank info and can't go to miner status, configuration, network etc. I resetted several time but the problem still the same. Any help?? here the video of this problem https://www.youtube.com/watch?v=TnlaL6h9kHc https://file.bitmain.com/shop-file-server/firmwares/Antiminer%20A3/Manual/007201802091050251715B3L9tLw0659/A3%20installation%20guide.pdf ASIC status O means OK X means error --means dead If nothing is displayed it does not have to mean they're dead Title: Re: Anyone else having issues with their Antminer A3? Post by: FNT on February 17, 2018, 09:08:57 AM Hi guys,
Could anybody please post a picture - in good quality- of an hasboard? I'd like to see which PIC,etc they are using. Thanks a lot and bye, FNT Title: Re: Anyone else having issues with their Antminer A3? Post by: DMAN_LTC on February 19, 2018, 03:29:07 PM I'm new to Mining so I'm trying to decided if I should stick my Antminer A3 in the Cooler for noise reduction
or if buying a "Silent Jet Fan" like the ones that the Antminer s5 are modified with by their owners will work? Modified Cooler or Silent Jet Fan? Or better options (liquid Mineral Oil might be too much). Title: Re: Anyone else having issues with their Antminer A3? Post by: greyday on February 21, 2018, 05:15:33 AM I'm new to Mining so I'm trying to decided if I should stick my Antminer A3 in the Cooler for noise reduction or if buying a "Silent Jet Fan" like the ones that the Antminer s5 are modified with by their owners will work? Modified Cooler or Silent Jet Fan? Or better options (liquid Mineral Oil might be too much). Why are you using bold? Silent fans don't seem to work on later antminers due to the number of boards and type of heat sink (the S5s had 2 hashing boards with a pair of thick foil style heatsinks running through the center, where the fans blow; the A3, for example, has three boards with one in the center and shallower heat sinks). I've tried the same fans I have on my S5 with my D3, even underclocked significantly (drawing around 700W) and it overheated in about four minutes, while my S5 has literally been running silently non-stop for weeks. AFAIK most of the noise in the newer antminers comes from the airflow over the heatsinks, not the fans themselves, so even if you COULD find quieter fans that would work, I doubt they would make a huge difference. But if you find some, let us know! (And I built a sound dampening box out of spare wood, some insulated ducting, and an old floor mat I had laying around, it's worth the time, my A3 is overclocked but running stably and quiet enough) Title: Re: Anyone else having issues with their Antminer A3? Post by: David71j on February 24, 2018, 02:39:43 AM Title: sec . teil .. Post by: David71j on February 24, 2018, 02:48:06 AM Feb 24 01:48:28 (none) local0.notice cgminer[21429]: Start A New Asic Response.Chain Id:[0]
Feb 24 01:48:28 (none) local0.err cgminer[21429]: create tx read thread for chain 0 ok Feb 24 01:48:28 (none) local0.notice cgminer[21429]: open device over Feb 24 01:48:28 (none) local0.warn cgminer[21429]: check_asic_reg: Chain0 has 0 ASICs Feb 24 01:48:28 (none) local0.notice cgminer[21429]: recheck_asic_num DONE! Feb 24 01:48:29 (none) local0.notice cgminer[21429]: reset_hash_board_low 0 Feb 24 01:48:29 (none) local0.notice cgminer[21429]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:48:30 (none) local0.notice cgminer[21429]: reset_hash_board_high 0 Feb 24 01:48:30 (none) local0.notice cgminer[21429]: tty_init_chain Feb 24 01:48:30 (none) local0.notice cgminer[21429]: tty_init_chain chainid = 0 Feb 24 01:48:30 (none) local0.err cgminer[21429]: create rx read thread for chain 0 ok Feb 24 01:48:30 (none) local0.notice cgminer[21429]: Start A New Asic Response.Chain Id:[0] Feb 24 01:48:30 (none) local0.err cgminer[21429]: create tx read thread for chain 0 ok Feb 24 01:48:30 (none) local0.notice cgminer[21429]: open device over Feb 24 01:48:30 (none) local0.warn cgminer[21429]: check_asic_reg: Chain0 has 0 ASICs Feb 24 01:48:31 (none) local0.notice cgminer[21429]: recheck_asic_num DONE! Feb 24 01:48:31 (none) local0.notice cgminer[21429]: calculate_address_interval: temp_asic_number = 64, addrInterval = 4 Feb 24 01:48:31 (none) local0.notice cgminer[21429]: set_ticket_mask ticket_mask = 0x00000020 Feb 24 01:48:31 (none) local0.notice cgminer[21429]: every_chain_get_PIC16F1704_freq_new Feb 24 01:48:33 (none) local0.notice cgminer[21429]: set_frequency: frequency = 600 Feb 24 01:48:33 (none) local0.notice cgminer[21429]: software_set_address_chain: chain 0 has 0 ASIC, and addrInterval is 4 Feb 24 01:48:33 (none) local0.notice cgminer[21429]: Now Set
Feb 24 01:48:34 (none) local0.notice cgminer[21429]: Now Set [1] Chain Address Feb 24 01:48:35 (none) local0.notice cgminer[21429]: software_set_address_chain: chain 2 has 60 ASIC, and addrInterval is 4 Feb 24 01:48:35 (none) local0.notice cgminer[21429]: Now Set [2] Chain Address Feb 24 01:48:35 (none) local0.notice cgminer[21429]: software_set_address_chain: chain 3 has 0 ASIC, and addrInterval is 4 Feb 24 01:48:35 (none) local0.notice cgminer[21429]: check_every_chain_asic_number Feb 24 01:48:36 (none) local0.warn cgminer[21429]: check_asic_reg: Chain0 has 0 ASICs Feb 24 01:48:36 (none) local0.warn cgminer[21429]: check_asic_reg: Chain1 has 60 ASICs Feb 24 01:48:36 (none) local0.warn cgminer[21429]: check_asic_reg: Chain2 has 60 ASICs Feb 24 01:48:36 (none) local0.notice cgminer[21429]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 01:48:36 (none) local0.notice cgminer[21429]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 01:48:36 (none) local0.notice cgminer[21429]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 01:48:36 (none) local0.notice cgminer[21429]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 01:48:36 (none) local0.notice cgminer[21429]: select_core_to_check_temperature: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:48:36 (none) local0.notice cgminer[21429]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:48:36 (none) local0.notice cgminer[21429]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:48:36 (none) local0.notice cgminer[21429]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:48:36 (none) local0.notice cgminer[21429]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:48:36 (none) local0.notice cgminer[21429]: 0 calibration_sensor_offset_chain Feb 24 01:48:37 (none) local0.notice cgminer[21429]: chain:0 local:0 remote:0 Feb 24 01:48:37 (none) local0.warn cgminer[21429]: Chain 0 set_temperature_offset_value_chain_sensor Feb 24 01:48:38 (none) local0.notice cgminer[21429]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : 00, Feb 24 01:48:38 (none) local0.notice cgminer[21429]: 1 calibration_sensor_offset_chain Feb 24 01:48:38 (none) local0.notice cgminer[21429]: chain:1 local:28 remote:27 Feb 24 01:48:38 (none) local0.warn cgminer[21429]: Chain 1 set_temperature_offset_value_chain_sensor Feb 24 01:48:38 (none) local0.notice cgminer[21429]: set_temperature_offset_value_chain_sensor: Chain1 Sensor0 temp offset : 01, Feb 24 01:48:38 (none) local0.notice cgminer[21429]: 2 calibration_sensor_offset_chain Feb 24 01:48:39 (none) local0.notice cgminer[21429]: chain:2 local:20 remote:19 Feb 24 01:48:39 (none) local0.warn cgminer[21429]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 01:48:39 (none) local0.notice cgminer[21429]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : 01, Feb 24 01:48:39 (none) local0.warn cgminer[21429]: Chain 0 set_temperature_offset_value_chain Feb 24 01:48:39 (none) local0.warn cgminer[21429]: Chain 0 set_temperature_offset_value_chain_sensor Feb 24 01:48:40 (none) local0.notice cgminer[21429]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : 00, Feb 24 01:48:40 (none) local0.warn cgminer[21429]: Chain 1 set_temperature_offset_value_chain Feb 24 01:48:40 (none) local0.warn cgminer[21429]: Chain 1 set_temperature_offset_value_chain_sensor Feb 24 01:48:40 (none) local0.notice cgminer[21429]: set_temperature_offset_value_chain_sensor: Chain1 Sensor0 temp offset : 01, Feb 24 01:48:40 (none) local0.warn cgminer[21429]: Chain 2 set_temperature_offset_value_chain Feb 24 01:48:40 (none) local0.warn cgminer[21429]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 01:48:40 (none) local0.notice cgminer[21429]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : 01, Feb 24 01:48:40 (none) local0.notice cgminer[21429]: frequency = '600' Feb 24 01:48:40 (none) local0.notice cgminer[21429]: dev.timeout = 8511 us Feb 24 01:48:45 (none) local0.err cgminer[21429]: cgminer time error total_secs = 1519436925.734046 last_total_secs = 1.000000 Feb 24 01:48:45 (none) local0.notice cgminer[21429]: fan_error_num:1 fan_num 2 fan_pwm 24 fan_speed_value[0] 2880 fan_speed_value[1] 2880 Feb 24 01:48:57 (none) local0.err cgminer: Miner compile time: Fri Dec 29 17:12:57 CST 2017 type: Antminer A3 Feb 24 01:48:57 (none) local0.warn cgminer: Started cgminer 4.9.0 Feb 24 01:48:57 (none) local0.warn cgminer[21914]: bitmain_sia_init Feb 24 01:48:57 (none) local0.err cgminer[21914]: FAN1 too slow ... Feb 24 01:48:57 (none) local0.err cgminer[21914]: FAN2 too slow ... Feb 24 01:48:58 (none) local0.err cgminer[21914]: FAN1 too slow ... Feb 24 01:48:58 (none) local0.err cgminer[21914]: FAN2 too slow ... Feb 24 01:48:58 (none) local0.warn cgminer[21914]: check_fan_speed OK Feb 24 01:48:58 (none) local0.notice cgminer[21914]: detected at /sys/class/gpio/gpio51/value chain 0 Feb 24 01:48:58 (none) local0.notice cgminer[21914]: detected at /sys/class/gpio/gpio48/value chain 1 Feb 24 01:48:58 (none) local0.notice cgminer[21914]: detected at /sys/class/gpio/gpio47/value chain 2 Feb 24 01:48:58 (none) local0.notice cgminer[21914]: detect total chain num 3 Feb 24 01:48:58 (none) local0.notice cgminer[21914]: i2c init ok Feb 24 01:48:58 (none) local0.notice cgminer[21914]: check_whether_need_update_pic_program Feb 24 01:48:59 (none) local0.notice cgminer[21914]: reset_PIC16F1704_pic_new ok Feb 24 01:49:00 (none) local0.notice cgminer[21914]: jump_from_loader_to_app_PIC16F1704_new ok Feb 24 01:49:00 (none) local0.notice cgminer[21914]: get_PIC16F1704_software_version_new ok, version = 0x81 Feb 24 01:49:01 (none) local0.notice cgminer[21914]: reset_PIC16F1704_pic_new ok Feb 24 01:49:02 (none) local0.notice cgminer[21914]: jump_from_loader_to_app_PIC16F1704_new ok Feb 24 01:49:02 (none) local0.notice cgminer[21914]: get_PIC16F1704_software_version_new ok, version = 0x81 Feb 24 01:49:04 (none) local0.notice cgminer[21914]: reset_PIC16F1704_pic_new ok Feb 24 01:49:04 (none) local0.notice cgminer[21914]: jump_from_loader_to_app_PIC16F1704_new ok Feb 24 01:49:05 (none) local0.notice cgminer[21914]: get_PIC16F1704_software_version_new ok, version = 0x81 Feb 24 01:49:05 (none) local0.notice cgminer[21914]: every_chain_reset_PIC16F1704_pic_new Feb 24 01:49:06 (none) local0.notice cgminer[21914]: reset_PIC16F1704_pic_new ok Feb 24 01:49:07 (none) local0.notice cgminer[21914]: reset_PIC16F1704_pic_new ok Feb 24 01:49:08 (none) local0.notice cgminer[21914]: reset_PIC16F1704_pic_new ok Feb 24 01:49:09 (none) local0.notice cgminer[21914]: every_chain_jump_from_loader_to_app_PIC16F1704_new Feb 24 01:49:09 (none) local0.notice cgminer[21914]: jump_from_loader_to_app_PIC16F1704_new ok Feb 24 01:49:10 (none) local0.notice cgminer[21914]: jump_from_loader_to_app_PIC16F1704_new ok Feb 24 01:49:10 (none) local0.notice cgminer[21914]: jump_from_loader_to_app_PIC16F1704_new ok Feb 24 01:49:11 (none) local0.notice cgminer[21914]: reset_hash_board_low 0 Feb 24 01:49:11 (none) local0.notice cgminer[21914]: pic_heart_beat_func_new Feb 24 01:49:11 (none) local0.notice cgminer[21914]: reset_hash_board_low 1 Feb 24 01:49:11 (none) local0.notice cgminer[21914]: reset_hash_board_low 2 Feb 24 01:49:11 (none) local0.notice cgminer[21914]: reset_hash_board_low 3 Feb 24 01:49:11 (none) local0.notice cgminer[21914]: every_chain_enable_PIC16F1704_dc_dc_new Feb 24 01:49:11 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:49:11 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:49:11 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:49:12 (none) local0.notice cgminer[21914]: reset_hash_board_high 0 Feb 24 01:49:12 (none) local0.notice cgminer[21914]: reset_hash_board_high 1 Feb 24 01:49:12 (none) local0.notice cgminer[21914]: reset_hash_board_high 2 Feb 24 01:49:12 (none) local0.notice cgminer[21914]: reset_hash_board_high 3 Feb 24 01:49:12 (none) local0.notice cgminer[21914]: tty_init Feb 24 01:49:12 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 01:49:12 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 0 Feb 24 01:49:12 (none) local0.err cgminer[21914]: create rx read thread for chain 0 ok Feb 24 01:49:12 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[0] Feb 24 01:49:13 (none) local0.err cgminer[21914]: create tx read thread for chain 0 ok Feb 24 01:49:13 (none) local0.notice cgminer[21914]: open device over Feb 24 01:49:13 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 01:49:13 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 1 Feb 24 01:49:13 (none) local0.err cgminer[21914]: create rx read thread for chain 1 ok Feb 24 01:49:13 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[1] Feb 24 01:49:13 (none) local0.err cgminer[21914]: create tx read thread for chain 1 ok Feb 24 01:49:13 (none) local0.notice cgminer[21914]: open device over Feb 24 01:49:13 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 01:49:13 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 2 Feb 24 01:49:13 (none) local0.err cgminer[21914]: create rx read thread for chain 2 ok Feb 24 01:49:13 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[2] Feb 24 01:49:13 (none) local0.err cgminer[21914]: create tx read thread for chain 2 ok Feb 24 01:49:13 (none) local0.notice cgminer[21914]: open device over Feb 24 01:49:13 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 01:49:13 (none) local0.notice cgminer[21914]: open device over Feb 24 01:49:13 (none) local0.notice cgminer[21914]: check_every_chain_asic_number Feb 24 01:49:14 (none) local0.warn cgminer[21914]: check_asic_reg: Chain0 has 0 ASICs Feb 24 01:49:14 (none) local0.warn cgminer[21914]: check_asic_reg: Chain1 has 60 ASICs Feb 24 01:49:14 (none) local0.warn cgminer[21914]: check_asic_reg: Chain2 has 60 ASICs Feb 24 01:49:15 (none) local0.notice cgminer[21914]: reset_hash_board_low 0 Feb 24 01:49:15 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:49:16 (none) local0.notice cgminer[21914]: reset_hash_board_high 0 Feb 24 01:49:16 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 01:49:16 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 0 Feb 24 01:49:16 (none) local0.err cgminer[21914]: create rx read thread for chain 0 ok Feb 24 01:49:16 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[0] Feb 24 01:49:16 (none) local0.err cgminer[21914]: create tx read thread for chain 0 ok Feb 24 01:49:16 (none) local0.notice cgminer[21914]: open device over Feb 24 01:49:17 (none) local0.warn cgminer[21914]: check_asic_reg: Chain0 has 0 ASICs Feb 24 01:49:17 (none) local0.notice cgminer[21914]: recheck_asic_num DONE! Feb 24 01:49:17 (none) local0.notice cgminer[21914]: reset_hash_board_low 0 Feb 24 01:49:17 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:49:18 (none) local0.notice cgminer[21914]: reset_hash_board_high 0 Feb 24 01:49:18 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 01:49:18 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 0 Feb 24 01:49:18 (none) local0.err cgminer[21914]: create rx read thread for chain 0 ok Feb 24 01:49:18 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[0] Feb 24 01:49:18 (none) local0.err cgminer[21914]: create tx read thread for chain 0 ok Feb 24 01:49:18 (none) local0.notice cgminer[21914]: open device over Feb 24 01:49:19 (none) local0.warn cgminer[21914]: check_asic_reg: Chain0 has 0 ASICs Feb 24 01:49:19 (none) local0.notice cgminer[21914]: recheck_asic_num DONE! Feb 24 01:49:19 (none) local0.notice cgminer[21914]: reset_hash_board_low 0 Feb 24 01:49:19 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:49:20 (none) local0.notice cgminer[21914]: reset_hash_board_high 0 Feb 24 01:49:20 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 01:49:20 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 0 Feb 24 01:49:20 (none) local0.err cgminer[21914]: create rx read thread for chain 0 ok Feb 24 01:49:20 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[0] Feb 24 01:49:20 (none) local0.err cgminer[21914]: create tx read thread for chain 0 ok Feb 24 01:49:20 (none) local0.notice cgminer[21914]: open device over Feb 24 01:49:21 (none) local0.warn cgminer[21914]: check_asic_reg: Chain0 has 0 ASICs Feb 24 01:49:21 (none) local0.notice cgminer[21914]: recheck_asic_num DONE! Feb 24 01:49:21 (none) local0.notice cgminer[21914]: calculate_address_interval: temp_asic_number = 64, addrInterval = 4 Feb 24 01:49:21 (none) local0.notice cgminer[21914]: set_ticket_mask ticket_mask = 0x00000020 Feb 24 01:49:21 (none) local0.notice cgminer[21914]: every_chain_get_PIC16F1704_freq_new Feb 24 01:49:23 (none) local0.notice cgminer[21914]: set_frequency: frequency = 600 Feb 24 01:49:23 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 0 has 0 ASIC, and addrInterval is 4 Feb 24 01:49:23 (none) local0.notice cgminer[21914]: Now Set
Feb 24 01:49:24 (none) local0.notice cgminer[21914]: Now Set [1] Chain Address Feb 24 01:49:25 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 2 has 60 ASIC, and addrInterval is 4 Feb 24 01:49:25 (none) local0.notice cgminer[21914]: Now Set [2] Chain Address Feb 24 01:49:26 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 3 has 0 ASIC, and addrInterval is 4 Feb 24 01:49:26 (none) local0.notice cgminer[21914]: check_every_chain_asic_number Feb 24 01:49:26 (none) local0.warn cgminer[21914]: check_asic_reg: Chain0 has 0 ASICs Feb 24 01:49:26 (none) local0.warn cgminer[21914]: check_asic_reg: Chain1 has 60 ASICs Feb 24 01:49:27 (none) local0.warn cgminer[21914]: check_asic_reg: Chain2 has 60 ASICs Feb 24 01:49:27 (none) local0.notice cgminer[21914]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 01:49:27 (none) local0.notice cgminer[21914]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 01:49:27 (none) local0.notice cgminer[21914]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 01:49:27 (none) local0.notice cgminer[21914]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 01:49:27 (none) local0.notice cgminer[21914]: select_core_to_check_temperature: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:49:27 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:49:27 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:49:27 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:49:27 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:49:27 (none) local0.notice cgminer[21914]: 0 calibration_sensor_offset_chain Feb 24 01:49:27 (none) local0.notice cgminer[21914]: chain:0 local:0 remote:0 Feb 24 01:49:27 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain_sensor Feb 24 01:49:28 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : 00, Feb 24 01:49:28 (none) local0.notice cgminer[21914]: 1 calibration_sensor_offset_chain Feb 24 01:49:28 (none) local0.notice cgminer[21914]: chain:1 local:25 remote:33 Feb 24 01:49:28 (none) local0.warn cgminer[21914]: Chain 1 set_temperature_offset_value_chain_sensor Feb 24 01:49:29 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain1 Sensor0 temp offset : -8, Feb 24 01:49:29 (none) local0.notice cgminer[21914]: chain:1 local:25 remote:24 Feb 24 01:49:29 (none) local0.warn cgminer[21914]: Chain 1 set_temperature_offset_value_chain_sensor Feb 24 01:49:29 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain1 Sensor0 temp offset : -7, Feb 24 01:49:29 (none) local0.notice cgminer[21914]: 2 calibration_sensor_offset_chain Feb 24 01:49:30 (none) local0.notice cgminer[21914]: chain:2 local:26 remote:36 Feb 24 01:49:30 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 01:49:30 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -10, Feb 24 01:49:30 (none) local0.notice cgminer[21914]: chain:2 local:26 remote:25 Feb 24 01:49:30 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 01:49:31 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -9, Feb 24 01:49:31 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain Feb 24 01:49:31 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain_sensor Feb 24 01:49:31 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : 00, Feb 24 01:49:31 (none) local0.warn cgminer[21914]: Chain 1 set_temperature_offset_value_chain Feb 24 01:49:31 (none) local0.warn cgminer[21914]: Chain 1 set_temperature_offset_value_chain_sensor Feb 24 01:49:32 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain1 Sensor0 temp offset : -7, Feb 24 01:49:32 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain Feb 24 01:49:32 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 01:49:32 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -9, Feb 24 01:49:32 (none) local0.notice cgminer[21914]: frequency = '600' Feb 24 01:49:32 (none) local0.notice cgminer[21914]: dev.timeout = 8511 us Feb 24 01:49:37 (none) local0.err cgminer[21914]: cgminer time error total_secs = 1519436977.339521 last_total_secs = 1.000000 Feb 24 01:49:37 (none) local0.notice cgminer[21914]: fan_error_num:1 fan_num 2 fan_pwm 24 fan_speed_value[0] 2970 fan_speed_value[1] 2940 Feb 24 01:49:38 (none) local0.notice cgminer[21914]: fan_error_num:1 fan_num 2 fan_pwm 24 fan_speed_value[0] 4290 fan_speed_value[1] 4260 Feb 24 01:49:38 (none) local0.warn cgminer[21914]: Pool 0 stratum+tcp://eu.luxor.tech:3333 alive, testing stability Feb 24 01:49:38 (none) local0.warn cgminer[21914]: Switching to pool 0 stratum+tcp://eu.luxor.tech:3333 Feb 24 01:49:43 (none) local0.warn cgminer[21914]: API running in IP access mode on port 4028 (15) Feb 24 01:50:37 (none) local0.notice cgminer[21914]: fan_error_num:1 fan_num 2 fan_pwm 24 fan_speed_value[0] 2610 fan_speed_value[1] 2610 Feb 24 01:50:39 (none) local0.notice cgminer[21914]: fan_error_num:1 fan_num 2 fan_pwm 24 fan_speed_value[0] 3750 fan_speed_value[1] 3690 Feb 24 01:50:40 (none) local0.notice cgminer[21914]: fan_error_num:1 fan_num 2 fan_pwm 24 fan_speed_value[0] 5040 fan_speed_value[1] 5010 Feb 24 01:51:38 (none) local0.notice cgminer[21914]: chain 0 reinit 0.00 Feb 24 01:51:38 (none) local0.notice cgminer[21914]: chain 1 reinit 0.00 Feb 24 01:51:38 (none) local0.notice cgminer[21914]: chain 2 reinit 0.00 Feb 24 01:51:38 (none) local0.notice cgminer[21914]: reset_hash_board_low 2 Feb 24 01:51:38 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:51:39 (none) local0.notice cgminer[21914]: reset_hash_board_high 2 Feb 24 01:51:39 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 01:51:39 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 2 Feb 24 01:51:39 (none) local0.err cgminer[21914]: create rx read thread for chain 2 ok Feb 24 01:51:39 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[2] Feb 24 01:51:39 (none) local0.err cgminer[21914]: create tx read thread for chain 2 ok Feb 24 01:51:39 (none) local0.notice cgminer[21914]: open device over Feb 24 01:51:39 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 2 has 60 ASIC, and addrInterval is 4 Feb 24 01:51:40 (none) local0.notice cgminer[21914]: Now Set [2] Chain Address Feb 24 01:51:40 (none) local0.notice cgminer[21914]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 01:51:40 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:51:40 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain Feb 24 01:51:40 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 01:51:41 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -9, Feb 24 01:51:41 (none) local0.notice cgminer[21914]: reset_hash_board_low 0 Feb 24 01:51:42 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:51:43 (none) local0.notice cgminer[21914]: reset_hash_board_high 0 Feb 24 01:51:43 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 01:51:43 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 0 Feb 24 01:51:43 (none) local0.err cgminer[21914]: create rx read thread for chain 0 ok Feb 24 01:51:43 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[0] Feb 24 01:51:43 (none) local0.err cgminer[21914]: create tx read thread for chain 0 ok Feb 24 01:51:43 (none) local0.notice cgminer[21914]: open device over Feb 24 01:51:43 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 0 has 0 ASIC, and addrInterval is 4 Feb 24 01:51:43 (none) local0.notice cgminer[21914]: Now Set
Feb 24 01:51:44 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:51:44 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain Feb 24 01:51:44 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain_sensor Feb 24 01:51:44 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : 00, Feb 24 01:51:45 (none) local0.notice cgminer[21914]: reset_hash_board_low 1 Feb 24 01:51:45 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:51:46 (none) local0.notice cgminer[21914]: reset_hash_board_high 1 Feb 24 01:51:47 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 01:51:47 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 1 Feb 24 01:51:47 (none) local0.err cgminer[21914]: create rx read thread for chain 1 ok Feb 24 01:51:47 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[1] Feb 24 01:51:47 (none) local0.err cgminer[21914]: create tx read thread for chain 1 ok Feb 24 01:51:47 (none) local0.notice cgminer[21914]: open device over Feb 24 01:51:47 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 1 has 60 ASIC, and addrInterval is 4 Feb 24 01:51:47 (none) local0.notice cgminer[21914]: Now Set [1] Chain Address Feb 24 01:51:48 (none) local0.notice cgminer[21914]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 01:51:48 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:51:48 (none) local0.warn cgminer[21914]: Chain 1 set_temperature_offset_value_chain Feb 24 01:51:48 (none) local0.warn cgminer[21914]: Chain 1 set_temperature_offset_value_chain_sensor Feb 24 01:51:48 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain1 Sensor0 temp offset : -7, Feb 24 01:53:39 (none) local0.notice cgminer[21914]: chain 0 reinit 0.00 Feb 24 01:53:39 (none) local0.notice cgminer[21914]: chain 2 reinit 0.00 Feb 24 01:53:39 (none) local0.notice cgminer[21914]: reset_hash_board_low 2 Feb 24 01:53:40 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:53:41 (none) local0.notice cgminer[21914]: reset_hash_board_high 2 Feb 24 01:53:41 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 01:53:41 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 2 Feb 24 01:53:41 (none) local0.err cgminer[21914]: create rx read thread for chain 2 ok Feb 24 01:53:41 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[2] Feb 24 01:53:41 (none) local0.err cgminer[21914]: create tx read thread for chain 2 ok Feb 24 01:53:41 (none) local0.notice cgminer[21914]: open device over Feb 24 01:53:41 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 2 has 60 ASIC, and addrInterval is 4 Feb 24 01:53:41 (none) local0.notice cgminer[21914]: Now Set [2] Chain Address Feb 24 01:53:42 (none) local0.notice cgminer[21914]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 01:53:42 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:53:42 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain Feb 24 01:53:42 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 01:53:42 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -9, Feb 24 01:53:43 (none) local0.notice cgminer[21914]: reset_hash_board_low 0 Feb 24 01:53:43 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:53:44 (none) local0.notice cgminer[21914]: reset_hash_board_high 0 Feb 24 01:53:44 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 01:53:44 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 0 Feb 24 01:53:44 (none) local0.err cgminer[21914]: create rx read thread for chain 0 ok Feb 24 01:53:44 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[0] Feb 24 01:53:44 (none) local0.err cgminer[21914]: create tx read thread for chain 0 ok Feb 24 01:53:44 (none) local0.notice cgminer[21914]: open device over Feb 24 01:53:44 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 0 has 0 ASIC, and addrInterval is 4 Feb 24 01:53:44 (none) local0.notice cgminer[21914]: Now Set
Feb 24 01:53:45 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:53:45 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain Feb 24 01:53:45 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain_sensor Feb 24 01:53:46 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : 00, Feb 24 01:55:40 (none) local0.notice cgminer[21914]: chain 0 reinit 0.00 Feb 24 01:55:40 (none) local0.notice cgminer[21914]: chain 2 reinit 0.00 Feb 24 01:55:41 (none) local0.notice cgminer[21914]: reset_hash_board_low 2 Feb 24 01:55:41 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:55:42 (none) local0.notice cgminer[21914]: reset_hash_board_high 2 Feb 24 01:55:42 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 01:55:42 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 2 Feb 24 01:55:42 (none) local0.err cgminer[21914]: create rx read thread for chain 2 ok Feb 24 01:55:42 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[2] Feb 24 01:55:42 (none) local0.err cgminer[21914]: create tx read thread for chain 2 ok Feb 24 01:55:42 (none) local0.notice cgminer[21914]: open device over Feb 24 01:55:42 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 2 has 60 ASIC, and addrInterval is 4 Feb 24 01:55:42 (none) local0.notice cgminer[21914]: Now Set [2] Chain Address Feb 24 01:55:43 (none) local0.notice cgminer[21914]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 01:55:43 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:55:43 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain Feb 24 01:55:43 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 01:55:43 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -9, Feb 24 01:55:44 (none) local0.notice cgminer[21914]: reset_hash_board_low 0 Feb 24 01:55:44 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:55:45 (none) local0.notice cgminer[21914]: reset_hash_board_high 0 Feb 24 01:55:45 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 01:55:45 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 0 Feb 24 01:55:45 (none) local0.err cgminer[21914]: create rx read thread for chain 0 ok Feb 24 01:55:45 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[0] Feb 24 01:55:46 (none) local0.err cgminer[21914]: create tx read thread for chain 0 ok Feb 24 01:55:46 (none) local0.notice cgminer[21914]: open device over Feb 24 01:55:46 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 0 has 0 ASIC, and addrInterval is 4 Feb 24 01:55:46 (none) local0.notice cgminer[21914]: Now Set
Feb 24 01:55:46 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:55:46 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain Feb 24 01:55:46 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain_sensor Feb 24 01:55:47 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : 00, Feb 24 01:57:42 (none) local0.notice cgminer[21914]: chain 0 reinit 0.00 Feb 24 01:57:42 (none) local0.notice cgminer[21914]: chain 2 reinit 0.00 Feb 24 01:57:42 (none) local0.notice cgminer[21914]: reset_hash_board_low 2 Feb 24 01:57:43 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:57:44 (none) local0.notice cgminer[21914]: reset_hash_board_high 2 Feb 24 01:57:44 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 01:57:44 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 2 Feb 24 01:57:44 (none) local0.err cgminer[21914]: create rx read thread for chain 2 ok Feb 24 01:57:44 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[2] Feb 24 01:57:44 (none) local0.err cgminer[21914]: create tx read thread for chain 2 ok Feb 24 01:57:44 (none) local0.notice cgminer[21914]: open device over Feb 24 01:57:44 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 2 has 60 ASIC, and addrInterval is 4 Feb 24 01:57:44 (none) local0.notice cgminer[21914]: Now Set [2] Chain Address Feb 24 01:57:45 (none) local0.notice cgminer[21914]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 01:57:45 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:57:45 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain Feb 24 01:57:45 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 01:57:45 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -9, Feb 24 01:57:46 (none) local0.notice cgminer[21914]: reset_hash_board_low 0 Feb 24 01:57:46 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:57:47 (none) local0.notice cgminer[21914]: reset_hash_board_high 0 Feb 24 01:57:47 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 01:57:47 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 0 Feb 24 01:57:47 (none) local0.err cgminer[21914]: create rx read thread for chain 0 ok Feb 24 01:57:47 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[0] Feb 24 01:57:48 (none) local0.err cgminer[21914]: create tx read thread for chain 0 ok Feb 24 01:57:48 (none) local0.notice cgminer[21914]: open device over Feb 24 01:57:48 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 0 has 0 ASIC, and addrInterval is 4 Feb 24 01:57:48 (none) local0.notice cgminer[21914]: Now Set
Feb 24 01:57:48 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:57:48 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain Feb 24 01:57:48 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain_sensor Feb 24 01:57:49 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : 00, Feb 24 01:59:44 (none) local0.notice cgminer[21914]: chain 0 reinit 0.00 Feb 24 01:59:44 (none) local0.notice cgminer[21914]: chain 2 reinit 0.00 Feb 24 01:59:44 (none) local0.notice cgminer[21914]: reset_hash_board_low 2 Feb 24 01:59:44 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:59:45 (none) local0.notice cgminer[21914]: reset_hash_board_high 2 Feb 24 01:59:45 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 01:59:45 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 2 Feb 24 01:59:45 (none) local0.err cgminer[21914]: create rx read thread for chain 2 ok Feb 24 01:59:45 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[2] Feb 24 01:59:45 (none) local0.err cgminer[21914]: create tx read thread for chain 2 ok Feb 24 01:59:45 (none) local0.notice cgminer[21914]: open device over Feb 24 01:59:45 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 2 has 60 ASIC, and addrInterval is 4 Feb 24 01:59:46 (none) local0.notice cgminer[21914]: Now Set [2] Chain Address Feb 24 01:59:46 (none) local0.notice cgminer[21914]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 01:59:46 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:59:46 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain Feb 24 01:59:46 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 01:59:47 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -9, Feb 24 01:59:47 (none) local0.notice cgminer[21914]: reset_hash_board_low 0 Feb 24 01:59:48 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:59:49 (none) local0.notice cgminer[21914]: reset_hash_board_high 0 Feb 24 01:59:49 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 01:59:49 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 0 Feb 24 01:59:49 (none) local0.err cgminer[21914]: create rx read thread for chain 0 ok Feb 24 01:59:49 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[0] Feb 24 01:59:49 (none) local0.err cgminer[21914]: create tx read thread for chain 0 ok Feb 24 01:59:49 (none) local0.notice cgminer[21914]: open device over Feb 24 01:59:49 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 0 has 0 ASIC, and addrInterval is 4 Feb 24 01:59:49 (none) local0.notice cgminer[21914]: Now Set
Feb 24 01:59:50 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:59:50 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain Feb 24 01:59:50 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain_sensor Feb 24 01:59:51 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : 00, Feb 24 02:01:45 (none) local0.notice cgminer[21914]: chain 0 reinit 0.00 Feb 24 02:01:45 (none) local0.notice cgminer[21914]: chain 2 reinit 0.00 Feb 24 02:01:45 (none) local0.notice cgminer[21914]: reset_hash_board_low 2 Feb 24 02:01:45 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 02:01:46 (none) local0.notice cgminer[21914]: reset_hash_board_high 2 Feb 24 02:01:46 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 02:01:46 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 2 Feb 24 02:01:46 (none) local0.err cgminer[21914]: create rx read thread for chain 2 ok Feb 24 02:01:46 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[2] Feb 24 02:01:47 (none) local0.err cgminer[21914]: create tx read thread for chain 2 ok Feb 24 02:01:47 (none) local0.notice cgminer[21914]: open device over Feb 24 02:01:47 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 2 has 60 ASIC, and addrInterval is 4 Feb 24 02:01:47 (none) local0.notice cgminer[21914]: Now Set [2] Chain Address Feb 24 02:01:47 (none) local0.notice cgminer[21914]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 02:01:47 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 02:01:47 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain Feb 24 02:01:47 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 02:01:48 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -9, Feb 24 02:01:48 (none) local0.notice cgminer[21914]: reset_hash_board_low 0 Feb 24 02:01:49 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 02:01:50 (none) local0.notice cgminer[21914]: reset_hash_board_high 0 Feb 24 02:01:50 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 02:01:50 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 0 Feb 24 02:01:50 (none) local0.err cgminer[21914]: create rx read thread for chain 0 ok Feb 24 02:01:50 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[0] Feb 24 02:01:50 (none) local0.err cgminer[21914]: create tx read thread for chain 0 ok Feb 24 02:01:50 (none) local0.notice cgminer[21914]: open device over Feb 24 02:01:50 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 0 has 0 ASIC, and addrInterval is 4 Feb 24 02:01:50 (none) local0.notice cgminer[21914]: Now Set
Feb 24 02:01:51 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 02:01:51 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain Feb 24 02:01:51 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain_sensor Feb 24 02:01:52 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : 00, Feb 24 02:03:46 (none) local0.notice cgminer[21914]: chain 0 reinit 0.00 Feb 24 02:03:46 (none) local0.notice cgminer[21914]: chain 2 reinit 0.00 Feb 24 02:03:46 (none) local0.notice cgminer[21914]: reset_hash_board_low 2 Feb 24 02:03:46 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 02:03:47 (none) local0.notice cgminer[21914]: reset_hash_board_high 2 Feb 24 02:03:47 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 02:03:47 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 2 Feb 24 02:03:47 (none) local0.err cgminer[21914]: create rx read thread for chain 2 ok Feb 24 02:03:47 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[2] Feb 24 02:03:48 (none) local0.err cgminer[21914]: create tx read thread for chain 2 ok Feb 24 02:03:48 (none) local0.notice cgminer[21914]: open device over Feb 24 02:03:48 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 2 has 60 ASIC, and addrInterval is 4 Feb 24 02:03:48 (none) local0.notice cgminer[21914]: Now Set [2] Chain Address Feb 24 02:03:48 (none) local0.notice cgminer[21914]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 02:03:48 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 02:03:48 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain Feb 24 02:03:48 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 02:03:49 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -9, Feb 24 02:03:50 (none) local0.notice cgminer[21914]: reset_hash_board_low 0 Feb 24 02:03:50 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 02:03:51 (none) local0.notice cgminer[21914]: reset_hash_board_high 0 Feb 24 02:03:51 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 02:03:51 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 0 Feb 24 02:03:51 (none) local0.err cgminer[21914]: create rx read thread for chain 0 ok Feb 24 02:03:51 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[0] Feb 24 02:03:51 (none) local0.err cgminer[21914]: create tx read thread for chain 0 ok Feb 24 02:03:51 (none) local0.notice cgminer[21914]: open device over Feb 24 02:03:51 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 0 has 0 ASIC, and addrInterval is 4 Feb 24 02:03:51 (none) local0.notice cgminer[21914]: Now Set
Feb 24 02:03:52 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 02:03:52 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain Feb 24 02:03:52 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain_sensor Feb 24 02:03:53 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : 00, Feb 24 02:05:47 (none) local0.notice cgminer[21914]: chain 0 reinit 0.00 Feb 24 02:05:47 (none) local0.notice cgminer[21914]: chain 2 reinit 0.00 Feb 24 02:05:47 (none) local0.notice cgminer[21914]: reset_hash_board_low 2 Feb 24 02:05:47 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 02:05:48 (none) local0.notice cgminer[21914]: reset_hash_board_high 2 Feb 24 02:05:48 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 02:05:48 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 2 Feb 24 02:05:48 (none) local0.err cgminer[21914]: create rx read thread for chain 2 ok Feb 24 02:05:48 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[2] Feb 24 02:05:49 (none) local0.err cgminer[21914]: create tx read thread for chain 2 ok Feb 24 02:05:49 (none) local0.notice cgminer[21914]: open device over Feb 24 02:05:49 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 2 has 60 ASIC, and addrInterval is 4 Feb 24 02:05:49 (none) local0.notice cgminer[21914]: Now Set [2] Chain Address Feb 24 02:05:50 (none) local0.notice cgminer[21914]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 02:05:50 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 02:05:50 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain Feb 24 02:05:50 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 02:05:50 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -9, Feb 24 02:05:51 (none) local0.notice cgminer[21914]: reset_hash_board_low 0 Feb 24 02:05:51 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 02:05:52 (none) local0.notice cgminer[21914]: reset_hash_board_high 0 Feb 24 02:05:52 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 02:05:52 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 0 Feb 24 02:05:52 (none) local0.err cgminer[21914]: create rx read thread for chain 0 ok Feb 24 02:05:52 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[0] Feb 24 02:05:52 (none) local0.err cgminer[21914]: create tx read thread for chain 0 ok Feb 24 02:05:52 (none) local0.notice cgminer[21914]: open device over Feb 24 02:05:52 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 0 has 0 ASIC, and addrInterval is 4 Feb 24 02:05:52 (none) local0.notice cgminer[21914]: Now Set
Feb 24 02:05:53 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 02:05:53 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain Feb 24 02:05:53 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain_sensor Feb 24 02:05:54 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : 00, Feb 24 02:07:48 (none) local0.notice cgminer[21914]: chain 0 reinit 0.00 Feb 24 02:07:48 (none) local0.notice cgminer[21914]: chain 2 reinit 0.00 Feb 24 02:07:48 (none) local0.notice cgminer[21914]: reset_hash_board_low 0 Feb 24 02:07:49 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 02:07:50 (none) local0.notice cgminer[21914]: reset_hash_board_high 0 Feb 24 02:07:50 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 02:07:50 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 0 Feb 24 02:07:50 (none) local0.err cgminer[21914]: create rx read thread for chain 0 ok Feb 24 02:07:50 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[0] Feb 24 02:07:50 (none) local0.err cgminer[21914]: create tx read thread for chain 0 ok Feb 24 02:07:50 (none) local0.notice cgminer[21914]: open device over Feb 24 02:07:50 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 0 has 0 ASIC, and addrInterval is 4 Feb 24 02:07:50 (none) local0.notice cgminer[21914]: Now Set
Feb 24 02:07:51 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 02:07:51 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain Feb 24 02:07:51 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain_sensor Feb 24 02:07:51 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : 00, Feb 24 02:07:52 (none) local0.notice cgminer[21914]: reset_hash_board_low 2 Feb 24 02:07:53 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 02:07:54 (none) local0.notice cgminer[21914]: reset_hash_board_high 2 Feb 24 02:07:54 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 02:07:54 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 2 Feb 24 02:07:54 (none) local0.err cgminer[21914]: create rx read thread for chain 2 ok Feb 24 02:07:54 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[2] Feb 24 02:07:54 (none) local0.err cgminer[21914]: create tx read thread for chain 2 ok Feb 24 02:07:54 (none) local0.notice cgminer[21914]: open device over Feb 24 02:07:54 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 2 has 60 ASIC, and addrInterval is 4 Feb 24 02:07:54 (none) local0.notice cgminer[21914]: Now Set [2] Chain Address Feb 24 02:07:55 (none) local0.notice cgminer[21914]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 02:07:55 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 02:07:55 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain Feb 24 02:07:55 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 02:07:55 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -9, Feb 24 02:09:50 (none) local0.notice cgminer[21914]: chain 0 reinit 0.00 Feb 24 02:09:50 (none) local0.notice cgminer[21914]: chain 2 reinit 0.00 Feb 24 02:09:51 (none) local0.notice cgminer[21914]: reset_hash_board_low 2 Feb 24 02:09:51 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 02:09:52 (none) local0.notice cgminer[21914]: reset_hash_board_high 2 Feb 24 02:09:52 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 02:09:52 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 2 Feb 24 02:09:52 (none) local0.err cgminer[21914]: create rx read thread for chain 2 ok Feb 24 02:09:52 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[2] Feb 24 02:09:52 (none) local0.err cgminer[21914]: create tx read thread for chain 2 ok Feb 24 02:09:52 (none) local0.notice cgminer[21914]: open device over Feb 24 02:09:52 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 2 has 60 ASIC, and addrInterval is 4 Feb 24 02:09:52 (none) local0.notice cgminer[21914]: Now Set [2] Chain Address Feb 24 02:09:53 (none) local0.notice cgminer[21914]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 02:09:53 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 02:09:53 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain Feb 24 02:09:53 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 02:09:53 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -9, Feb 24 02:09:54 (none) local0.notice cgminer[21914]: reset_hash_board_low 0 Feb 24 02:09:54 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 02:09:55 (none) local0.notice cgminer[21914]: reset_hash_board_high 0 Feb 24 02:09:56 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 02:09:56 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 0 Feb 24 02:09:56 (none) local0.err cgminer[21914]: create rx read thread for chain 0 ok Feb 24 02:09:56 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[0] Feb 24 02:09:56 (none) local0.err cgminer[21914]: create tx read thread for chain 0 ok Feb 24 02:09:56 (none) local0.notice cgminer[21914]: open device over Feb 24 02:09:56 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 0 has 0 ASIC, and addrInterval is 4 Feb 24 02:09:56 (none) local0.notice cgminer[21914]: Now Set
Feb 24 02:09:57 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 02:09:57 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain Feb 24 02:09:57 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain_sensor Feb 24 02:09:57 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : 00, Feb 24 02:11:52 (none) local0.notice cgminer[21914]: chain 0 reinit 0.00 Feb 24 02:11:52 (none) local0.notice cgminer[21914]: chain 2 reinit 0.00 Feb 24 02:11:52 (none) local0.notice cgminer[21914]: reset_hash_board_low 2 Feb 24 02:11:52 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 02:11:53 (none) local0.notice cgminer[21914]: reset_hash_board_high 2 Feb 24 02:11:53 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 02:11:53 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 2 Feb 24 02:11:53 (none) local0.err cgminer[21914]: create rx read thread for chain 2 ok Feb 24 02:11:53 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[2] Feb 24 02:11:54 (none) local0.err cgminer[21914]: create tx read thread for chain 2 ok Feb 24 02:11:54 (none) local0.notice cgminer[21914]: open device over Feb 24 02:11:54 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 2 has 60 ASIC, and addrInterval is 4 Feb 24 02:11:54 (none) local0.notice cgminer[21914]: Now Set [2] Chain Address Feb 24 02:11:54 (none) local0.notice cgminer[21914]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 02:11:54 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 02:11:54 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain Feb 24 02:11:54 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 02:11:55 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -9, Feb 24 02:11:56 (none) local0.notice cgminer[21914]: reset_hash_board_low 0 Feb 24 02:11:56 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 02:11:57 (none) local0.notice cgminer[21914]: reset_hash_board_high 0 Feb 24 02:11:57 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 02:11:57 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 0 Feb 24 02:11:57 (none) local0.err cgminer[21914]: create rx read thread for chain 0 ok Feb 24 02:11:57 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[0] Feb 24 02:11:57 (none) local0.err cgminer[21914]: create tx read thread for chain 0 ok Feb 24 02:11:57 (none) local0.notice cgminer[21914]: open device over Feb 24 02:11:57 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 0 has 0 ASIC, and addrInterval is 4 Feb 24 02:11:57 (none) local0.notice cgminer[21914]: Now Set
Feb 24 02:11:58 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 02:11:58 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain Feb 24 02:11:58 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain_sensor Feb 24 02:11:59 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : 00, Feb 24 02:13:54 (none) local0.notice cgminer[21914]: chain 0 reinit 0.00 Feb 24 02:13:54 (none) local0.notice cgminer[21914]: chain 2 reinit 0.00 Feb 24 02:13:54 (none) local0.notice cgminer[21914]: reset_hash_board_low 2 Feb 24 02:13:55 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 02:13:56 (none) local0.notice cgminer[21914]: reset_hash_board_high 2 Feb 24 02:13:56 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 02:13:56 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 2 Feb 24 02:13:56 (none) local0.err cgminer[21914]: create rx read thread for chain 2 ok Feb 24 02:13:56 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[2] Feb 24 02:13:56 (none) local0.err cgminer[21914]: create tx read thread for chain 2 ok Feb 24 02:13:56 (none) local0.notice cgminer[21914]: open device over Feb 24 02:13:56 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 2 has 60 ASIC, and addrInterval is 4 Feb 24 02:13:56 (none) local0.notice cgminer[21914]: Now Set [2] Chain Address Feb 24 02:13:57 (none) local0.notice cgminer[21914]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 02:13:57 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 02:13:57 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain Feb 24 02:13:57 (none) local0.warn cgminer[21914]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 02:13:57 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -9, Feb 24 02:13:58 (none) local0.notice cgminer[21914]: reset_hash_board_low 0 Feb 24 02:13:58 (none) local0.notice cgminer[21914]: enable_PIC16F1704_dc_dc_new ok Feb 24 02:13:59 (none) local0.notice cgminer[21914]: reset_hash_board_high 0 Feb 24 02:13:59 (none) local0.notice cgminer[21914]: tty_init_chain Feb 24 02:13:59 (none) local0.notice cgminer[21914]: tty_init_chain chainid = 0 Feb 24 02:13:59 (none) local0.err cgminer[21914]: create rx read thread for chain 0 ok Feb 24 02:13:59 (none) local0.notice cgminer[21914]: Start A New Asic Response.Chain Id:[0] Feb 24 02:13:59 (none) local0.err cgminer[21914]: create tx read thread for chain 0 ok Feb 24 02:13:59 (none) local0.notice cgminer[21914]: open device over Feb 24 02:13:59 (none) local0.notice cgminer[21914]: software_set_address_chain: chain 0 has 0 ASIC, and addrInterval is 4 Feb 24 02:13:59 (none) local0.notice cgminer[21914]: Now Set
Feb 24 02:14:00 (none) local0.notice cgminer[21914]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 02:14:00 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain Feb 24 02:14:00 (none) local0.warn cgminer[21914]: Chain 0 set_temperature_offset_value_chain_sensor Feb 24 02:14:01 (none) local0.notice cgminer[21914]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : 00, Title: Re: Anyone else having issues with their Antminer A3? Post by: FNT on February 24, 2018, 09:03:56 AM Hi!
What does bitmain say? Looks like "hashboard1" (=0) is not found or better the Asics. check_asic_reg: Chain0 has 0 ASICs check_asic_reg: Chain1 has 60 ASICs check_asic_reg: Chain2 has 60 ASICs Psu: Everything pluged in and power supply is ok? Which one you use? What if you change psu plugs for hashboard? Bye, FNT Title: Re: Anyone else having issues with their Antminer A3? Post by: David71j on February 24, 2018, 11:42:46 AM I have rebooted und pressed the reset-botton
I have controlled the cable. I don't know how to go on, what I should do next. Title: Re: Anyone else having issues with their Antminer A3? Post by: David71j on February 24, 2018, 06:10:53 PM Title: Re: Anyone else having issues with their Antminer A3? Post by: Marvell2 on February 24, 2018, 07:27:54 PM [ 0.000000] Booting Linux on physical CPU 0x0 this fool poster his whole fucking log 😂😂😂 , I just had to qoute it lol[ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Linux version 3.8.13 (xxl@armdev01) (gcc version 4.7.4 20130626 (prerelease) (Linaro GCC 4.7-2013.07) ) #22 SMP Tue Dec 2 15:26:11 CST 2014 [ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=50c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] Machine: Generic AM33XX (Flattened Device Tree), model: TI AM335x BeagleBone [ 0.000000] Memory policy: ECC disabled, Data cache writeback [ 0.000000] On node 0 totalpages: 65280 [ 0.000000] free_area_init_node: node 0, pgdat c06cb100, node_mem_map c0726000 [ 0.000000] Normal zone: 512 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 64768 pages, LIFO batch:15 [ 0.000000] AM335X ES1.0 (neon ) [ 0.000000] PERCPU: Embedded 8 pages/cpu @c0933000 s9408 r8192 d15168 u32768 [ 0.000000] pcpu-alloc: s9408 r8192 d15168 u32768 alloc=8*4096 [ 0.000000] pcpu-alloc:
[ 0.000000] Kernel command line: console=ttyO0,115200n8 init=/sbin/init [ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes) [ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) [ 0.000000] __ex_table already sorted, skipping sort [ 0.000000] allocated 524288 bytes of page_cgroup [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups [ 0.000000] Memory: 255MB = 255MB total [ 0.000000] Memory: 238884k/238884k available, 23260k reserved, 0K highmem [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) [ 0.000000] vmalloc : 0xd0800000 - 0xff000000 ( 744 MB) [ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB) [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) [ 0.000000] modules : 0xbf800000 - 0xbfe00000 ( 6 MB) [ 0.000000] .text : 0xc0008000 - 0xc0612cf0 (6188 kB) [ 0.000000] .init : 0xc0613000 - 0xc06554c0 ( 266 kB) [ 0.000000] .data : 0xc0656000 - 0xc06cc020 ( 473 kB) [ 0.000000] .bss : 0xc06cc020 - 0xc0725e3c ( 360 kB) [ 0.000000] Hierarchical RCU implementation. [ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1. [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts [ 0.000000] Total of 128 interrupts on 1 active controller [ 0.000000] OMAP clockevent source: GPTIMER1 at 24000000 Hz [ 0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms [ 0.000000] OMAP clocksource: GPTIMER2 at 24000000 Hz [ 0.000000] Console: colour dummy device 80x30 [ 0.000356] Calibrating delay loop... 545.07 BogoMIPS (lpj=531968) [ 0.015439] pid_max: default: 32768 minimum: 301 [ 0.015670] Security Framework initialized [ 0.015763] Mount-cache hash table entries: 512 [ 0.024580] Initializing cgroup subsys cpuacct [ 0.024611] Initializing cgroup subsys memory [ 0.024675] Initializing cgroup subsys blkio [ 0.024812] CPU: Testing write buffer coherency: ok [ 0.025384] CPU0: thread -1, cpu 0, socket -1, mpidr 0 [ 0.025461] Setting up static identity map for 0x8038c820 - 0x8038c86c [ 0.026783] Brought up 1 CPUs [ 0.026806] SMP: Total of 1 processors activated (545.07 BogoMIPS). [ 0.028115] devtmpfs: initialized [ 0.092456] pinctrl core: initialized pinctrl subsystem [ 0.092671] rstctl core: initialized rstctl subsystem [ 0.093163] regulator-dummy: no parameters [ 0.093736] NET: Registered protocol family 16 [ 0.094441] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.104116] pinctrl-single 44e10800.pinmux: prop pinctrl-0 index 0 invalid phandle [ 0.104299] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568 [ 0.105387] platform 49000000.edma: alias fck already exists [ 0.105422] platform 49000000.edma: alias fck already exists [ 0.105450] platform 49000000.edma: alias fck already exists [ 0.106601] gpiochip_add: registered GPIOs 0 to 31 on device: gpio [ 0.106785] OMAP GPIO hardware version 0.1 [ 0.108195] gpiochip_add: registered GPIOs 32 to 63 on device: gpio [ 0.109510] gpiochip_add: registered GPIOs 64 to 95 on device: gpio [ 0.110824] gpiochip_add: registered GPIOs 96 to 127 on device: gpio [ 0.111447] of_get_named_gpio_flags exited with status 52 [ 0.111476] gpio-rctrl rstctl.3: loaded OK [ 0.116583] omap-gpmc 50000000.gpmc: GPMC revision 6.0 [ 0.119799] hw-breakpoint: debug architecture 0x4 unsupported. [ 0.121979] cpsw.0: No hwaddr in dt. Using 94:e3:6d:f8:48:19 from efuse [ 0.122011] cpsw.1: No hwaddr in dt. Using 94:e3:6d:f8:48:1b from efuse [ 0.137566] bio: create slab <bio-0> at 0 [ 0.149686] edma-dma-engine edma-dma-engine.0: TI EDMA DMA engine driver [ 0.149925] of_get_named_gpio_flags: can't parse gpios property [ 0.150167] vmmcsd_fixed: 3300 mV [ 0.153325] SCSI subsystem initialized [ 0.153777] usbcore: registered new interface driver usbfs [ 0.153892] usbcore: registered new interface driver hub [ 0.154225] usbcore: registered new device driver usb [ 0.156325] omap_i2c 4819c000.i2c: bus 0 rev0.11 at 100 kHz [ 0.156358] omap_i2c 4819c000.i2c: unable to select pin group [ 0.156554] media: Linux media interface: v0.10 [ 0.156648] Linux video capture interface: v2.00 [ 0.156764] pps_core: LinuxPPS API ver. 1 registered [ 0.156781] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 0.157500] Advanced Linux Sound Architecture Driver Initialized. [ 0.158692] Switching to clocksource gp_timer [ 0.176738] NET: Registered protocol family 2 [ 0.177733] TCP established hash table entries: 2048 (order: 2, 16384 bytes) [ 0.177822] TCP bind hash table entries: 2048 (order: 3, 40960 bytes) [ 0.177912] TCP: Hash tables configured (established 2048 bind 2048) [ 0.178004] TCP: reno registered [ 0.178030] UDP hash table entries: 256 (order: 1, 12288 bytes) [ 0.178076] UDP-Lite hash table entries: 256 (order: 1, 12288 bytes) [ 0.178564] NET: Registered protocol family 1 [ 0.179150] RPC: Registered named UNIX socket transport module. [ 0.179171] RPC: Registered udp transport module. [ 0.179184] RPC: Registered tcp transport module. [ 0.179198] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.179585] Trying to unpack rootfs image as initramfs... [ 1.921539] Freeing initrd memory: 12032K [ 1.922226] CPU PMU: probing PMU on CPU 0 [ 1.922259] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available [ 1.922864] omap2_mbox_probe: platform not supported [ 1.926752] VFS: Disk quotas dquot_6.5.2 [ 1.926987] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 1.928363] NFS: Registering the id_resolver key type [ 1.928460] Key type id_resolver registered [ 1.928478] Key type id_legacy registered [ 1.928548] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. [ 1.928991] msgmni has been set to 490 [ 1.931791] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249) [ 1.931818] io scheduler noop registered [ 1.931834] io scheduler deadline registered [ 1.931892] io scheduler cfq registered (default) [ 1.935839] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 1.938422] omap_uart 44e09000.serial: did not get pins for uart0 error: -19 [ 1.938702] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88) is a OMAP UART0 [ 2.599517] console [ttyO0] enabled [ 2.604043] 48022000.serial: ttyO1 at MMIO 0x48022000 (irq = 89) is a OMAP UART1 [ 2.612735] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 90) is a OMAP UART2 [ 2.621372] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 61) is a OMAP UART4 [ 2.630023] 481aa000.serial: ttyO5 at MMIO 0x481aa000 (irq = 62) is a OMAP UART5 [ 2.639008] [drm] Initialized drm 1.1.0 20060810 [ 2.657698] brd: module loaded [ 2.667973] loop: module loaded [ 2.672164] bone-capemgr bone_capemgr.8: Failed to find baseboard eeprom node [ 2.682102] nand_get_flash_type: 2c,f1 against 2c,f1 [ 2.687633] ONFI param page 0 valid [ 2.691306] ONFI flash detected [ 2.694627] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xf1 (Micron MT29F1G08ABAEAWP), 128MiB, page size: 2048, OOB size: 64 [ 2.706539] omap2-nand: detected x8 NAND flash [ 2.711204] nand: using OMAP_ECC_BCH8_CODE_HW ECC scheme [ 2.716788] omap2-nand: using custom ecc layout [ 2.721635] 10 ofpart partitions found on MTD device omap2-nand.0 [ 2.728031] Creating 10 MTD partitions on "omap2-nand.0": [ 2.733708] 0x000000000000-0x000000020000 : "spl" [ 2.740501] 0x000000020000-0x000000040000 : "spl_backup1" [ 2.747973] 0x000000040000-0x000000060000 : "spl_backup2" [ 2.755388] 0x000000060000-0x000000080000 : "spl_backup3" [ 2.762794] 0x000000080000-0x000000240000 : "u-boot" [ 2.771051] 0x000000240000-0x000000260000 : "bootenv" [ 2.778012] 0x000000260000-0x000000280000 : "fdt" [ 2.784641] 0x000000280000-0x000000780000 : "kernel" [ 2.795650] 0x000000800000-0x000001c00000 : "root" [ 2.819144] 0x000001c00000-0x000003000000 : "config" [ 2.842917] OneNAND driver initializing [ 2.848655] usbcore: registered new interface driver asix [ 2.854468] usbcore: registered new interface driver cdc_ether [ 2.860711] usbcore: registered new interface driver smsc95xx [ 2.866829] usbcore: registered new interface driver net1080 [ 2.872855] usbcore: registered new interface driver cdc_subset [ 2.879148] usbcore: registered new interface driver zaurus [ 2.885156] usbcore: registered new interface driver cdc_ncm [ 2.891936] usbcore: registered new interface driver cdc_acm [ 2.897897] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 2.906276] Initializing USB Mass Storage driver... [ 2.911518] usbcore: registered new interface driver usb-storage [ 2.917818] USB Mass Storage support registered. [ 2.922860] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host) [ 2.929576] musb-hdrc musb-hdrc.0.auto: pdev->id = 0 [ 2.934820] musb-hdrc musb-hdrc.0.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK [ 2.943591] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn) [ 2.943613] musb-hdrc: MHDRC RTL version 2.0 [ 2.943628] musb-hdrc: setup fifo_mode 4 [ 2.943656] musb-hdrc: 28/31 max ep, 16384/16384 memory [ 2.943804] musb-hdrc musb-hdrc.0.auto: *** mode=3 [ 2.948849] musb-hdrc musb-hdrc.0.auto: *** power=250 [ 2.954874] musb-hdrc musb-hdrc.1.auto: pdev->id = 1 [ 2.960125] musb-hdrc musb-hdrc.1.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK [ 2.968895] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn) [ 2.968915] musb-hdrc: MHDRC RTL version 2.0 [ 2.968929] musb-hdrc: setup fifo_mode 4 [ 2.968951] musb-hdrc: 28/31 max ep, 16384/16384 memory [ 2.969092] musb-hdrc musb-hdrc.1.auto: *** mode=1 [ 2.974135] musb-hdrc musb-hdrc.1.auto: *** power=250 [ 2.979445] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver [ 2.985819] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 1 [ 2.994061] musb-hdrc musb-hdrc.1.auto: supports USB remote wakeup [ 2.994165] usb usb1: default language 0x0409 [ 2.994224] usb usb1: udev 1, busnum 1, minor = 0 [ 2.994247] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 3.001402] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.008974] usb usb1: Product: MUSB HDRC host driver [ 3.014187] usb usb1: Manufacturer: Linux 3.8.13 musb-hcd [ 3.019853] usb usb1: SerialNumber: musb-hdrc.1.auto [ 3.026109] usb usb1: usb_probe_device [ 3.026139] usb usb1: configuration #1 chosen from 1 choice [ 3.026210] usb usb1: adding 1-0:1.0 (config #1, interface 0) [ 3.026415] hub 1-0:1.0: usb_probe_interface [ 3.026438] hub 1-0:1.0: usb_probe_interface - got id [ 3.026466] hub 1-0:1.0: USB hub found [ 3.030462] hub 1-0:1.0: 1 port detected [ 3.034601] hub 1-0:1.0: standalone hub [ 3.034621] hub 1-0:1.0: individual port power switching [ 3.034639] hub 1-0:1.0: no over-current protection [ 3.034657] hub 1-0:1.0: Single TT [ 3.034678] hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns) [ 3.034697] hub 1-0:1.0: power on to power good time: 10ms [ 3.034752] hub 1-0:1.0: local power source is good [ 3.034867] hub 1-0:1.0: enabling power on all ports [ 3.035989] mousedev: PS/2 mouse device common for all mice [ 3.043873] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0 [ 3.051694] i2c /dev entries driver [ 3.056696] pps_ldisc: PPS line discipline registered [ 3.062188] Driver for 1-wire Dallas network protocol. [ 3.069475] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec [ 3.077068] cpuidle: using governor ladder [ 3.081395] cpuidle: using governor menu [ 3.085962] of_get_named_gpio_flags exited with status 6 [ 3.085982] of_get_named_gpio_flags: can't parse gpios property [ 3.085998] of_get_named_gpio_flags: can't parse gpios property [ 3.086034] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' failed [ 3.093274] omap_hsmmc mmc.4: Failed to get rstctl; not using any [ 3.100086] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25 [ 3.107310] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24 [ 3.114632] mmc.4 supply vmmc_aux not found, using dummy regulator [ 3.121587] omap_hsmmc mmc.4: pins are not configured from the driver [ 3.135460] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000 [ 3.155486] of_get_named_gpio_flags exited with status -517 [ 3.155551] platform gpio-leds.7: Driver leds-gpio requests probe deferral [ 3.163325] ledtrig-cpu: registered to indicate activity on CPUs [ 3.170101] edma-dma-engine edma-dma-engine.0: allocated channel for 0:36 [ 3.177294] omap-sham 53100000.sham: hw accel on OMAP rev 4.3 [ 3.185389] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2 [ 3.191739] edma-dma-engine edma-dma-engine.0: allocated channel for 0:5 [ 3.198924] edma-dma-engine edma-dma-engine.0: allocated channel for 0:6 [ 3.211163] usbcore: registered new interface driver usbhid [ 3.217080] usbhid: USB HID core driver [ 3.223981] TCP: cubic registered [ 3.227506] Initializing XFRM netlink socket [ 3.232075] NET: Registered protocol family 17 [ 3.236935] NET: Registered protocol family 15 [ 3.241809] Key type dns_resolver registered [ 3.246454] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3 [ 3.254563] ThumbEE CPU extension supported. [ 3.259080] Registering SWP/SWPB emulation handler [ 3.265097] registered taskstats version 1 [ 3.271720] of_get_named_gpio_flags exited with status -517 [ 3.271793] platform gpio-leds.7: Driver leds-gpio requests probe deferral [ 3.328767] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6 [ 3.335178] davinci_mdio 4a101000.mdio: detected phy mask fffffffe [ 3.349735] libphy: 4a101000.mdio: probed [ 3.354051] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720 [ 3.364291] Detected MACID = 94:e3:6d:f8:48:19 [ 3.368973] cpsw 4a100000.ethernet: NAPI disabled [ 3.374364] of_get_named_gpio_flags exited with status -517 [ 3.374430] platform gpio-leds.7: Driver leds-gpio requests probe deferral [ 3.383155] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800) [ 3.392442] cpu0 supply cpu0 not found, using dummy regulator [ 3.398933] cpufreq_cpu0: failed to scale voltage up: -22 [ 3.404749] cpufreq_cpu0: failed to scale voltage up: -22 [ 3.417534] ALSA device list: [ 3.420761] No soundcards found. [ 3.425315] Freeing init memory: 264K [ 3.429368] Failed to execute /init [ 4.407969] jffs2: notice: (122) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found. [ 5.765247] net eth0: initializing cpsw version 1.12 (0) [ 5.774225] net eth0: phy found : id is : 0x7c0f1 [ 5.779617] libphy: PHY 4a101000.mdio:01 not found [ 5.784810] net eth0: phy 4a101000.mdio:01 not found on slave 1 [ 9.922981] libphy: 4a101000.mdio:00 - Link is Up - 100/Full Feb 24 01:43:14 (none) local0.err cgminer: Miner compile time: Fri Dec 29 17:12:57 CST 2017 type: Antminer A3 Feb 24 01:43:14 (none) local0.warn cgminer: Started cgminer 4.9.0 Feb 24 01:43:14 (none) local0.warn cgminer[376]: bitmain_sia_init Feb 24 01:43:15 (none) local0.err cgminer[376]: FAN1 too slow ... Feb 24 01:43:15 (none) local0.err cgminer[376]: FAN2 too slow ... Feb 24 01:43:15 (none) local0.err cgminer[376]: FAN1 too slow ... Feb 24 01:43:15 (none) local0.err cgminer[376]: FAN2 too slow ... Feb 24 01:43:16 (none) local0.err cgminer[376]: FAN1 too slow ... Feb 24 01:43:16 (none) local0.err cgminer[376]: FAN2 too slow ... Feb 24 01:43:16 (none) local0.err cgminer[376]: FAN1 too slow ... Feb 24 01:43:16 (none) local0.err cgminer[376]: FAN2 too slow ... Feb 24 01:43:17 (none) local0.err cgminer[376]: FAN1 too slow ... Feb 24 01:43:17 (none) local0.err cgminer[376]: FAN2 too slow ... Feb 24 01:43:17 (none) local0.err cgminer[376]: FAN1 too slow ... Feb 24 01:43:18 (none) local0.err cgminer[376]: FAN1 too slow ... Feb 24 01:43:18 (none) local0.warn cgminer[376]: check_fan_speed OK Feb 24 01:43:18 (none) local0.notice cgminer[376]: detected at /sys/class/gpio/gpio51/value chain 0 Feb 24 01:43:18 (none) local0.notice cgminer[376]: detected at /sys/class/gpio/gpio48/value chain 1 Feb 24 01:43:18 (none) local0.notice cgminer[376]: detected at /sys/class/gpio/gpio47/value chain 2 Feb 24 01:43:18 (none) local0.notice cgminer[376]: detect total chain num 3 Feb 24 01:43:18 (none) local0.notice cgminer[376]: i2c init ok Feb 24 01:43:18 (none) local0.notice cgminer[376]: check_whether_need_update_pic_program Feb 24 01:43:19 (none) local0.notice cgminer[376]: reset_PIC16F1704_pic_new ok Feb 24 01:43:20 (none) local0.notice cgminer[376]: jump_from_loader_to_app_PIC16F1704_new ok Feb 24 01:43:20 (none) local0.notice cgminer[376]: get_PIC16F1704_software_version_new ok, version = 0x81 Feb 24 01:43:22 (none) local0.notice cgminer[376]: reset_PIC16F1704_pic_new ok Feb 24 01:43:22 (none) local0.notice cgminer[376]: jump_from_loader_to_app_PIC16F1704_new ok Feb 24 01:43:23 (none) local0.notice cgminer[376]: get_PIC16F1704_software_version_new ok, version = 0x81 Feb 24 01:43:24 (none) local0.notice cgminer[376]: reset_PIC16F1704_pic_new ok Feb 24 01:43:24 (none) local0.notice cgminer[376]: jump_from_loader_to_app_PIC16F1704_new ok Feb 24 01:43:25 (none) local0.notice cgminer[376]: get_PIC16F1704_software_version_new ok, version = 0x81 Feb 24 01:43:25 (none) local0.notice cgminer[376]: every_chain_reset_PIC16F1704_pic_new Feb 24 01:43:26 (none) local0.notice cgminer[376]: reset_PIC16F1704_pic_new ok Feb 24 01:43:27 (none) local0.notice cgminer[376]: reset_PIC16F1704_pic_new ok Feb 24 01:43:28 (none) local0.notice cgminer[376]: reset_PIC16F1704_pic_new ok Feb 24 01:43:29 (none) local0.notice cgminer[376]: every_chain_jump_from_loader_to_app_PIC16F1704_new Feb 24 01:43:29 (none) local0.notice cgminer[376]: jump_from_loader_to_app_PIC16F1704_new ok Feb 24 01:43:30 (none) local0.notice cgminer[376]: jump_from_loader_to_app_PIC16F1704_new ok Feb 24 01:43:30 (none) local0.notice cgminer[376]: jump_from_loader_to_app_PIC16F1704_new ok Feb 24 01:43:31 (none) local0.notice cgminer[376]: reset_hash_board_low 0 Feb 24 01:43:31 (none) local0.notice cgminer[376]: pic_heart_beat_func_new Feb 24 01:43:31 (none) local0.notice cgminer[376]: reset_hash_board_low 1 Feb 24 01:43:31 (none) local0.notice cgminer[376]: reset_hash_board_low 2 Feb 24 01:43:31 (none) local0.notice cgminer[376]: reset_hash_board_low 3 Feb 24 01:43:31 (none) local0.notice cgminer[376]: every_chain_enable_PIC16F1704_dc_dc_new Feb 24 01:43:31 (none) local0.notice cgminer[376]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:43:31 (none) local0.notice cgminer[376]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:43:32 (none) local0.notice cgminer[376]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:43:32 (none) local0.notice cgminer[376]: reset_hash_board_high 0 Feb 24 01:43:32 (none) local0.notice cgminer[376]: reset_hash_board_high 1 Feb 24 01:43:32 (none) local0.notice cgminer[376]: reset_hash_board_high 2 Feb 24 01:43:32 (none) local0.notice cgminer[376]: reset_hash_board_high 3 Feb 24 01:43:32 (none) local0.notice cgminer[376]: tty_init Feb 24 01:43:32 (none) local0.notice cgminer[376]: tty_init_chain Feb 24 01:43:32 (none) local0.notice cgminer[376]: tty_init_chain chainid = 0 Feb 24 01:43:32 (none) local0.err cgminer[376]: create rx read thread for chain 0 ok Feb 24 01:43:32 (none) local0.notice cgminer[376]: Start A New Asic Response.Chain Id:[0] Feb 24 01:43:33 (none) local0.err cgminer[376]: create tx read thread for chain 0 ok Feb 24 01:43:33 (none) local0.notice cgminer[376]: open device over Feb 24 01:43:33 (none) local0.notice cgminer[376]: tty_init_chain Feb 24 01:43:33 (none) local0.notice cgminer[376]: tty_init_chain chainid = 1 Feb 24 01:43:33 (none) local0.err cgminer[376]: create rx read thread for chain 1 ok Feb 24 01:43:33 (none) local0.notice cgminer[376]: Start A New Asic Response.Chain Id:[1] Feb 24 01:43:33 (none) local0.err cgminer[376]: create tx read thread for chain 1 ok Feb 24 01:43:33 (none) local0.notice cgminer[376]: open device over Feb 24 01:43:33 (none) local0.notice cgminer[376]: tty_init_chain Feb 24 01:43:33 (none) local0.notice cgminer[376]: tty_init_chain chainid = 2 Feb 24 01:43:33 (none) local0.err cgminer[376]: create rx read thread for chain 2 ok Feb 24 01:43:33 (none) local0.notice cgminer[376]: Start A New Asic Response.Chain Id:[2] Feb 24 01:43:33 (none) local0.err cgminer[376]: create tx read thread for chain 2 ok Feb 24 01:43:33 (none) local0.notice cgminer[376]: open device over Feb 24 01:43:33 (none) local0.notice cgminer[376]: tty_init_chain Feb 24 01:43:33 (none) local0.notice cgminer[376]: open device over Feb 24 01:43:34 (none) local0.notice cgminer[376]: check_every_chain_asic_number Feb 24 01:43:34 (none) local0.warn cgminer[376]: check_asic_reg: Chain0 has 0 ASICs Feb 24 01:43:34 (none) local0.warn cgminer[376]: check_asic_reg: Chain1 has 60 ASICs Feb 24 01:43:34 (none) local0.warn cgminer[376]: check_asic_reg: Chain2 has 60 ASICs Feb 24 01:43:35 (none) local0.notice cgminer[376]: reset_hash_board_low 0 Feb 24 01:43:35 (none) local0.notice cgminer[376]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:43:36 (none) local0.notice cgminer[376]: reset_hash_board_high 0 Feb 24 01:43:36 (none) local0.notice cgminer[376]: tty_init_chain Feb 24 01:43:36 (none) local0.notice cgminer[376]: tty_init_chain chainid = 0 Feb 24 01:43:36 (none) local0.err cgminer[376]: create rx read thread for chain 0 ok Feb 24 01:43:36 (none) local0.notice cgminer[376]: Start A New Asic Response.Chain Id:[0] Feb 24 01:43:37 (none) local0.err cgminer[376]: create tx read thread for chain 0 ok Feb 24 01:43:37 (none) local0.notice cgminer[376]: open device over Feb 24 01:43:37 (none) local0.warn cgminer[376]: check_asic_reg: Chain0 has 0 ASICs Feb 24 01:43:37 (none) local0.notice cgminer[376]: recheck_asic_num DONE! Feb 24 01:43:37 (none) local0.notice cgminer[376]: reset_hash_board_low 0 Feb 24 01:43:37 (none) local0.notice cgminer[376]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:43:38 (none) local0.notice cgminer[376]: reset_hash_board_high 0 Feb 24 01:43:38 (none) local0.notice cgminer[376]: tty_init_chain Feb 24 01:43:38 (none) local0.notice cgminer[376]: tty_init_chain chainid = 0 Feb 24 01:43:38 (none) local0.err cgminer[376]: create rx read thread for chain 0 ok Feb 24 01:43:38 (none) local0.notice cgminer[376]: Start A New Asic Response.Chain Id:[0] Feb 24 01:43:39 (none) local0.err cgminer[376]: create tx read thread for chain 0 ok Feb 24 01:43:39 (none) local0.notice cgminer[376]: open device over Feb 24 01:43:39 (none) local0.warn cgminer[376]: check_asic_reg: Chain0 has 0 ASICs Feb 24 01:43:39 (none) local0.notice cgminer[376]: recheck_asic_num DONE! Feb 24 01:43:39 (none) local0.notice cgminer[376]: reset_hash_board_low 0 Feb 24 01:43:39 (none) local0.notice cgminer[376]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:43:40 (none) local0.notice cgminer[376]: reset_hash_board_high 0 Feb 24 01:43:40 (none) local0.notice cgminer[376]: tty_init_chain Feb 24 01:43:40 (none) local0.notice cgminer[376]: tty_init_chain chainid = 0 Feb 24 01:43:40 (none) local0.err cgminer[376]: create rx read thread for chain 0 ok Feb 24 01:43:40 (none) local0.notice cgminer[376]: Start A New Asic Response.Chain Id:[0] Feb 24 01:43:41 (none) local0.err cgminer[376]: create tx read thread for chain 0 ok Feb 24 01:43:41 (none) local0.notice cgminer[376]: open device over Feb 24 01:43:41 (none) local0.warn cgminer[376]: check_asic_reg: Chain0 has 0 ASICs Feb 24 01:43:41 (none) local0.notice cgminer[376]: recheck_asic_num DONE! Feb 24 01:43:41 (none) local0.notice cgminer[376]: calculate_address_interval: temp_asic_number = 64, addrInterval = 4 Feb 24 01:43:41 (none) local0.notice cgminer[376]: set_ticket_mask ticket_mask = 0x00000020 Feb 24 01:43:41 (none) local0.notice cgminer[376]: every_chain_get_PIC16F1704_freq_new Feb 24 01:43:44 (none) local0.notice cgminer[376]: set_frequency: frequency = 600 Feb 24 01:43:44 (none) local0.notice cgminer[376]: software_set_address_chain: chain 0 has 0 ASIC, and addrInterval is 4 Feb 24 01:43:44 (none) local0.notice cgminer[376]: Now Set
Feb 24 01:43:44 (none) local0.notice cgminer[376]: Now Set [1] Chain Address Feb 24 01:43:45 (none) local0.notice cgminer[376]: software_set_address_chain: chain 2 has 60 ASIC, and addrInterval is 4 Feb 24 01:43:45 (none) local0.notice cgminer[376]: Now Set [2] Chain Address Feb 24 01:43:46 (none) local0.notice cgminer[376]: software_set_address_chain: chain 3 has 0 ASIC, and addrInterval is 4 Feb 24 01:43:46 (none) local0.notice cgminer[376]: check_every_chain_asic_number Feb 24 01:43:46 (none) local0.warn cgminer[376]: check_asic_reg: Chain0 has 0 ASICs Feb 24 01:43:46 (none) local0.warn cgminer[376]: check_asic_reg: Chain1 has 60 ASICs Feb 24 01:43:47 (none) local0.warn cgminer[376]: check_asic_reg: Chain2 has 60 ASICs Feb 24 01:43:47 (none) local0.notice cgminer[376]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 01:43:47 (none) local0.notice cgminer[376]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 01:43:47 (none) local0.notice cgminer[376]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 01:43:47 (none) local0.notice cgminer[376]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 01:43:47 (none) local0.notice cgminer[376]: select_core_to_check_temperature: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:43:47 (none) local0.notice cgminer[376]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:43:47 (none) local0.notice cgminer[376]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:43:47 (none) local0.notice cgminer[376]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:43:47 (none) local0.notice cgminer[376]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:43:47 (none) local0.notice cgminer[376]: 0 calibration_sensor_offset_chain Feb 24 01:43:48 (none) local0.notice cgminer[376]: chain:0 local:0 remote:0 Feb 24 01:43:48 (none) local0.warn cgminer[376]: Chain 0 set_temperature_offset_value_chain_sensor Feb 24 01:43:48 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : 00, Feb 24 01:43:48 (none) local0.notice cgminer[376]: 1 calibration_sensor_offset_chain Feb 24 01:43:49 (none) local0.notice cgminer[376]: chain:1 local:19 remote:27 Feb 24 01:43:49 (none) local0.warn cgminer[376]: Chain 1 set_temperature_offset_value_chain_sensor Feb 24 01:43:49 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain1 Sensor0 temp offset : -8, Feb 24 01:43:49 (none) local0.notice cgminer[376]: chain:1 local:19 remote:19 Feb 24 01:43:49 (none) local0.warn cgminer[376]: Chain 1 set_temperature_offset_value_chain_sensor Feb 24 01:43:50 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain1 Sensor0 temp offset : -8, Feb 24 01:43:50 (none) local0.notice cgminer[376]: 2 calibration_sensor_offset_chain Feb 24 01:43:50 (none) local0.notice cgminer[376]: chain:2 local:18 remote:28 Feb 24 01:43:50 (none) local0.warn cgminer[376]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 01:43:50 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -10, Feb 24 01:43:51 (none) local0.notice cgminer[376]: chain:2 local:18 remote:18 Feb 24 01:43:51 (none) local0.warn cgminer[376]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 01:43:51 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -10, Feb 24 01:43:51 (none) local0.warn cgminer[376]: Chain 0 set_temperature_offset_value_chain Feb 24 01:43:51 (none) local0.warn cgminer[376]: Chain 0 set_temperature_offset_value_chain_sensor Feb 24 01:43:52 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : 00, Feb 24 01:43:52 (none) local0.warn cgminer[376]: Chain 1 set_temperature_offset_value_chain Feb 24 01:43:52 (none) local0.warn cgminer[376]: Chain 1 set_temperature_offset_value_chain_sensor Feb 24 01:43:52 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain1 Sensor0 temp offset : -8, Feb 24 01:43:52 (none) local0.warn cgminer[376]: Chain 2 set_temperature_offset_value_chain Feb 24 01:43:52 (none) local0.warn cgminer[376]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 01:43:52 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -10, Feb 24 01:43:52 (none) local0.notice cgminer[376]: frequency = '600' Feb 24 01:43:52 (none) local0.notice cgminer[376]: dev.timeout = 8511 us Feb 24 01:43:57 (none) local0.err cgminer[376]: cgminer time error total_secs = 1519436637.502966 last_total_secs = 1.000000 Feb 24 01:43:58 (none) local0.warn cgminer[376]: Pool 0 stratum+tcp://eu.luxor.tech:3333 alive, testing stability Feb 24 01:43:58 (none) local0.warn cgminer[376]: Switching to pool 0 stratum+tcp://eu.luxor.tech:3333 Feb 24 01:44:03 (none) local0.warn cgminer[376]: API running in IP access mode on port 4028 (17) Feb 24 01:45:58 (none) local0.notice cgminer[376]: chain 0 reinit 0.00 Feb 24 01:45:58 (none) local0.notice cgminer[376]: chain 2 reinit 0.00 Feb 24 01:45:58 (none) local0.notice cgminer[376]: reset_hash_board_low 2 Feb 24 01:45:58 (none) local0.notice cgminer[376]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:45:59 (none) local0.notice cgminer[376]: fan_error_num:1 fan_num 2 fan_pwm 48 fan_speed_value[0] 4560 fan_speed_value[1] 4560 Feb 24 01:45:59 (none) local0.notice cgminer[376]: reset_hash_board_high 2 Feb 24 01:46:00 (none) local0.notice cgminer[376]: tty_init_chain Feb 24 01:46:00 (none) local0.notice cgminer[376]: tty_init_chain chainid = 2 Feb 24 01:46:00 (none) local0.err cgminer[376]: create rx read thread for chain 2 ok Feb 24 01:46:00 (none) local0.notice cgminer[376]: Start A New Asic Response.Chain Id:[2] Feb 24 01:46:00 (none) local0.err cgminer[376]: create tx read thread for chain 2 ok Feb 24 01:46:00 (none) local0.notice cgminer[376]: open device over Feb 24 01:46:00 (none) local0.notice cgminer[376]: software_set_address_chain: chain 2 has 60 ASIC, and addrInterval is 4 Feb 24 01:46:00 (none) local0.notice cgminer[376]: Now Set [2] Chain Address Feb 24 01:46:01 (none) local0.notice cgminer[376]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 01:46:01 (none) local0.notice cgminer[376]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:46:01 (none) local0.warn cgminer[376]: Chain 2 set_temperature_offset_value_chain Feb 24 01:46:01 (none) local0.warn cgminer[376]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 01:46:01 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -10, Feb 24 01:46:02 (none) local0.notice cgminer[376]: reset_hash_board_low 0 Feb 24 01:46:02 (none) local0.notice cgminer[376]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:46:03 (none) local0.notice cgminer[376]: reset_hash_board_high 0 Feb 24 01:46:03 (none) local0.notice cgminer[376]: tty_init_chain Feb 24 01:46:03 (none) local0.notice cgminer[376]: tty_init_chain chainid = 0 Feb 24 01:46:03 (none) local0.err cgminer[376]: create rx read thread for chain 0 ok Feb 24 01:46:03 (none) local0.notice cgminer[376]: Start A New Asic Response.Chain Id:[0] Feb 24 01:46:03 (none) local0.err cgminer[376]: create tx read thread for chain 0 ok Feb 24 01:46:03 (none) local0.notice cgminer[376]: open device over Feb 24 01:46:03 (none) local0.notice cgminer[376]: software_set_address_chain: chain 0 has 0 ASIC, and addrInterval is 4 Feb 24 01:46:03 (none) local0.notice cgminer[376]: Now Set
Feb 24 01:46:04 (none) local0.notice cgminer[376]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:46:04 (none) local0.warn cgminer[376]: Chain 0 set_temperature_offset_value_chain Feb 24 01:46:04 (none) local0.warn cgminer[376]: Chain 0 set_temperature_offset_value_chain_sensor Feb 24 01:46:05 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain0 Sensor0 temp offset : 00, Feb 24 01:48:00 (none) local0.notice cgminer[376]: chain 0 reinit 0.00 Feb 24 01:48:00 (none) local0.notice cgminer[376]: chain 2 reinit 0.00 Feb 24 01:48:00 (none) local0.notice cgminer[376]: reset_hash_board_low 2 Feb 24 01:48:00 (none) local0.notice cgminer[376]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:48:01 (none) local0.notice cgminer[376]: reset_hash_board_high 2 Feb 24 01:48:01 (none) local0.notice cgminer[376]: tty_init_chain Feb 24 01:48:01 (none) local0.notice cgminer[376]: tty_init_chain chainid = 2 Feb 24 01:48:01 (none) local0.err cgminer[376]: create rx read thread for chain 2 ok Feb 24 01:48:01 (none) local0.notice cgminer[376]: Start A New Asic Response.Chain Id:[2] Feb 24 01:48:01 (none) local0.err cgminer[376]: create tx read thread for chain 2 ok Feb 24 01:48:01 (none) local0.notice cgminer[376]: open device over Feb 24 01:48:01 (none) local0.notice cgminer[376]: software_set_address_chain: chain 2 has 60 ASIC, and addrInterval is 4 Feb 24 01:48:01 (none) local0.notice cgminer[376]: Now Set [2] Chain Address Feb 24 01:48:02 (none) local0.notice cgminer[376]: enable_read_temperature_from_asic_chain: reg_value = 0x07007a61 Feb 24 01:48:02 (none) local0.notice cgminer[376]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:48:02 (none) local0.warn cgminer[376]: Chain 2 set_temperature_offset_value_chain Feb 24 01:48:02 (none) local0.warn cgminer[376]: Chain 2 set_temperature_offset_value_chain_sensor Feb 24 01:48:03 (none) local0.notice cgminer[376]: set_temperature_offset_value_chain_sensor: Chain2 Sensor0 temp offset : -10, Feb 24 01:48:03 (none) local0.notice cgminer[376]: reset_hash_board_low 0 Feb 24 01:48:04 (none) local0.notice cgminer[376]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:48:05 (none) local0.notice cgminer[376]: reset_hash_board_high 0 Feb 24 01:48:05 (none) local0.notice cgminer[376]: tty_init_chain Feb 24 01:48:05 (none) local0.notice cgminer[376]: tty_init_chain chainid = 0 Feb 24 01:48:05 (none) local0.err cgminer[376]: create rx read thread for chain 0 ok Feb 24 01:48:05 (none) local0.notice cgminer[376]: Start A New Asic Response.Chain Id:[0] Feb 24 01:48:05 (none) local0.err cgminer[376]: create tx read thread for chain 0 ok Feb 24 01:48:05 (none) local0.notice cgminer[376]: open device over Feb 24 01:48:05 (none) local0.notice cgminer[376]: software_set_address_chain: chain 0 has 0 ASIC, and addrInterval is 4 Feb 24 01:48:05 (none) local0.notice cgminer[376]: Now Set
Feb 24 01:48:06 (none) local0.notice cgminer[376]: select_core_to_check_temperature_chain: diode_mux_sel = 4, vdd_mux_sel = 0 Feb 24 01:48:06 (none) local0.warn cgminer[376]: Chain 0 set_temperature_offset_value_chain Feb 24 01:48:06 (none) local0.warn cgminer[376]: Chain 0 set_temperature_offset_value_chain_sensor Feb 24 01:48:06 (none) local0.err cgminer: Miner compile time: Fri Dec 29 17:12:57 CST 2017 type: Antminer A3 Feb 24 01:48:06 (none) local0.warn cgminer: Started cgminer 4.9.0 Feb 24 01:48:06 (none) local0.warn cgminer[21429]: bitmain_sia_init Feb 24 01:48:07 (none) local0.err cgminer[21429]: FAN1 too slow ... Feb 24 01:48:07 (none) local0.err cgminer[21429]: FAN2 too slow ... Feb 24 01:48:07 (none) local0.err cgminer[21429]: FAN1 too slow ... Feb 24 01:48:07 (none) local0.err cgminer[21429]: FAN2 too slow ... Feb 24 01:48:08 (none) local0.warn cgminer[21429]: check_fan_speed OK Feb 24 01:48:08 (none) local0.notice cgminer[21429]: detected at /sys/class/gpio/gpio51/value chain 0 Feb 24 01:48:08 (none) local0.notice cgminer[21429]: detected at /sys/class/gpio/gpio48/value chain 1 Feb 24 01:48:08 (none) local0.notice cgminer[21429]: detected at /sys/class/gpio/gpio47/value chain 2 Feb 24 01:48:08 (none) local0.notice cgminer[21429]: detect total chain num 3 Feb 24 01:48:08 (none) local0.notice cgminer[21429]: i2c init ok Feb 24 01:48:08 (none) local0.notice cgminer[21429]: check_whether_need_update_pic_program Feb 24 01:48:09 (none) local0.notice cgminer[21429]: reset_PIC16F1704_pic_new ok Feb 24 01:48:09 (none) local0.notice cgminer[21429]: jump_from_loader_to_app_PIC16F1704_new ok Feb 24 01:48:10 (none) local0.notice cgminer[21429]: get_PIC16F1704_software_version_new ok, version = 0x81 Feb 24 01:48:11 (none) local0.notice cgminer[21429]: reset_PIC16F1704_pic_new ok Feb 24 01:48:12 (none) local0.notice cgminer[21429]: jump_from_loader_to_app_PIC16F1704_new ok Feb 24 01:48:12 (none) local0.notice cgminer[21429]: get_PIC16F1704_software_version_new ok, version = 0x81 Feb 24 01:48:13 (none) local0.notice cgminer[21429]: reset_PIC16F1704_pic_new ok Feb 24 01:48:14 (none) local0.notice cgminer[21429]: jump_from_loader_to_app_PIC16F1704_new ok Feb 24 01:48:14 (none) local0.notice cgminer[21429]: get_PIC16F1704_software_version_new ok, version = 0x81 Feb 24 01:48:14 (none) local0.notice cgminer[21429]: every_chain_reset_PIC16F1704_pic_new Feb 24 01:48:15 (none) local0.notice cgminer[21429]: reset_PIC16F1704_pic_new ok Feb 24 01:48:16 (none) local0.notice cgminer[21429]: reset_PIC16F1704_pic_new ok Feb 24 01:48:18 (none) local0.notice cgminer[21429]: reset_PIC16F1704_pic_new ok Feb 24 01:48:18 (none) local0.notice cgminer[21429]: every_chain_jump_from_loader_to_app_PIC16F1704_new Feb 24 01:48:19 (none) local0.notice cgminer[21429]: jump_from_loader_to_app_PIC16F1704_new ok Feb 24 01:48:19 (none) local0.notice cgminer[21429]: jump_from_loader_to_app_PIC16F1704_new ok Feb 24 01:48:20 (none) local0.notice cgminer[21429]: jump_from_loader_to_app_PIC16F1704_new ok Feb 24 01:48:20 (none) local0.notice cgminer[21429]: reset_hash_board_low 0 Feb 24 01:48:20 (none) local0.notice cgminer[21429]: pic_heart_beat_func_new Feb 24 01:48:20 (none) local0.notice cgminer[21429]: reset_hash_board_low 1 Feb 24 01:48:20 (none) local0.notice cgminer[21429]: reset_hash_board_low 2 Feb 24 01:48:20 (none) local0.notice cgminer[21429]: reset_hash_board_low 3 Feb 24 01:48:20 (none) local0.notice cgminer[21429]: every_chain_enable_PIC16F1704_dc_dc_new Feb 24 01:48:21 (none) local0.notice cgminer[21429]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:48:21 (none) local0.notice cgminer[21429]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:48:21 (none) local0.notice cgminer[21429]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:48:22 (none) local0.notice cgminer[21429]: reset_hash_board_high 0 Feb 24 01:48:22 (none) local0.notice cgminer[21429]: reset_hash_board_high 1 Feb 24 01:48:22 (none) local0.notice cgminer[21429]: reset_hash_board_high 2 Feb 24 01:48:22 (none) local0.notice cgminer[21429]: reset_hash_board_high 3 Feb 24 01:48:22 (none) local0.notice cgminer[21429]: tty_init Feb 24 01:48:22 (none) local0.notice cgminer[21429]: tty_init_chain Feb 24 01:48:22 (none) local0.notice cgminer[21429]: tty_init_chain chainid = 0 Feb 24 01:48:22 (none) local0.err cgminer[21429]: create rx read thread for chain 0 ok Feb 24 01:48:22 (none) local0.notice cgminer[21429]: Start A New Asic Response.Chain Id:[0] Feb 24 01:48:22 (none) local0.err cgminer[21429]: create tx read thread for chain 0 ok Feb 24 01:48:22 (none) local0.notice cgminer[21429]: open device over Feb 24 01:48:22 (none) local0.notice cgminer[21429]: tty_init_chain Feb 24 01:48:22 (none) local0.notice cgminer[21429]: tty_init_chain chainid = 1 Feb 24 01:48:22 (none) local0.err cgminer[21429]: create rx read thread for chain 1 ok Feb 24 01:48:22 (none) local0.notice cgminer[21429]: Start A New Asic Response.Chain Id:[1] Feb 24 01:48:22 (none) local0.err cgminer[21429]: create tx read thread for chain 1 ok Feb 24 01:48:22 (none) local0.notice cgminer[21429]: open device over Feb 24 01:48:22 (none) local0.notice cgminer[21429]: tty_init_chain Feb 24 01:48:22 (none) local0.notice cgminer[21429]: tty_init_chain chainid = 2 Feb 24 01:48:22 (none) local0.err cgminer[21429]: create rx read thread for chain 2 ok Feb 24 01:48:22 (none) local0.notice cgminer[21429]: Start A New Asic Response.Chain Id:[2] Feb 24 01:48:23 (none) local0.err cgminer[21429]: create tx read thread for chain 2 ok Feb 24 01:48:23 (none) local0.notice cgminer[21429]: open device over Feb 24 01:48:23 (none) local0.notice cgminer[21429]: tty_init_chain Feb 24 01:48:23 (none) local0.notice cgminer[21429]: open device over Feb 24 01:48:23 (none) local0.notice cgminer[21429]: check_every_chain_asic_number Feb 24 01:48:23 (none) local0.warn cgminer[21429]: check_asic_reg: Chain0 has 0 ASICs Feb 24 01:48:24 (none) local0.warn cgminer[21429]: check_asic_reg: Chain1 has 60 ASICs Feb 24 01:48:24 (none) local0.warn cgminer[21429]: check_asic_reg: Chain2 has 60 ASICs Feb 24 01:48:24 (none) local0.notice cgminer[21429]: reset_hash_board_low 0 Feb 24 01:48:25 (none) local0.notice cgminer[21429]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:48:26 (none) local0.notice cgminer[21429]: reset_hash_board_high 0 Feb 24 01:48:26 (none) local0.notice cgminer[21429]: tty_init_chain Feb 24 01:48:26 (none) local0.notice cgminer[21429]: tty_init_chain chainid = 0 Feb 24 01:48:26 (none) local0.err cgminer[21429]: create rx read thread for chain 0 ok Feb 24 01:48:26 (none) local0.notice cgminer[21429]: Start A New Asic Response.Chain Id:[0] Feb 24 01:48:26 (none) local0.err cgminer[21429]: create tx read thread for chain 0 ok Feb 24 01:48:26 (none) local0.notice cgminer[21429]: open device over Feb 24 01:48:26 (none) local0.warn cgminer[21429]: check_asic_reg: Chain0 has 0 ASICs Feb 24 01:48:26 (none) local0.notice cgminer[21429]: recheck_asic_num DONE! Feb 24 01:48:27 (none) local0.notice cgminer[21429]: reset_hash_board_low 0 Feb 24 01:48:27 (none) local0.notice cgminer[21429]: enable_PIC16F1704_dc_dc_new ok Feb 24 01:48:28 (none) local0.notice cgminer[21429]: reset_hash_board_high 0 Feb 24 01:48:28 (none) local0.notice cgminer[21429]: tty_init_chain Feb 24 01:48:28 (none) local0.notice cgminer[21429]: tty_init_chain chainid = 0 Feb 24 01:48:28 (none) local0.err cgminer[21429]: create rx read thread for chain 0 ok ??? https://img3.picload.org/image/dadicdlw/fehler.jpg way .. Help even bitmain support doesnt ask for this. Just send it back to them Title: Re: Anyone else having issues with their Antminer A3? Post by: 18TommyBoy18 on February 24, 2018, 09:30:28 PM H/W and counting, this is number of errors, I have too 1 panel wrong of 3 (Antminer S9). Only change, or try what making guys with heat gun at youtube...
Title: Re: Anyone else having issues with their Antminer A3? Post by: David71j on February 24, 2018, 11:01:55 PM Only change, or try what making guys with heat gun at youtube... do you have a link for me thank you Title: Re: Anyone else having issues with their Antminer A3? Post by: costapete on March 05, 2018, 09:35:10 PM please help and thank you very much i do appreciate any help
many miners running good A-3 Was fine now after reloaction it powers but wont hash no red or green lights. resets doesnt do anything no IP what can i do? Title: Re: Anyone else having issues with their Antminer A3? Post by: costapete on March 05, 2018, 10:37:13 PM i will send 75$ coin bounty
\ Title: Re: Anyone else having issues with their Antminer A3? Post by: Germanminer on March 06, 2018, 10:26:05 AM Hello guys.i have situation about quantity of errors of A3.All chips are 000 but the quantity of errors is about 110K after 1d5h restart with 850-880Gh and frq 631m,it's after when i made it down for one step frq,before it was even more errors about 450k for 9hours work.
and hashes so jumping up and down from 850-890gh is it normal situation for this machine?temp on chip 61-68 who can recommend smth? Title: Re: Anyone else having issues with their Antminer A3? Post by: costapete on March 06, 2018, 04:16:56 PM how can i reset the control board its locked up
Title: Re: Anyone else having issues with their Antminer A3? Post by: David71j on March 08, 2018, 01:18:04 PM User 'costapete' has not chosen to allow messages from newbies. You should post in their relevant thread to remind them to enable this setting.
tssssss Title: Re: Anyone else having issues with their Antminer A3? Post by: Bling2017 on March 15, 2018, 08:00:17 AM I received my A3 this afternoon and having been having some problems. When I first set it up, everything was working flawlessly. Hashing at 833GHs on Siamining, no HW errors, everything smooth. About 2 hours later I checked again and saw my hashrate dropped in half with a bunch of X's on one of the hashboards. Since then I've only been able to reach 500-600 GHs, and am getting HW errors on different boards whenever I refresh. Anyone else having issues? I would normally try reflashing the firmware but it's not available on Bitmain's support page. Ok the A3 does not like high temps above 90 Celcius at all. this will probably cause issues with HW faults and then become dead XXXXXX. For some reason its fans appear not to push enough air flow when I have it set up with my other set of four antminers 4 inch vent tubes going into the homes ventilation system per a 48 inch vent box that is sealed and connected using a 2 inch by 12 inch vent riser. I can feel a back force of air when tube vent not hooked up to back of A3, so I instead ran a separate straight outside through my window by 4 inch tubing and a 4 inch vent that is screwed to a board sitting in the window. now my temps are at about 80 on all board chips of A3. I figured it out by testing on desk for 1 hour with temps only reaching 75 celcius and never had an issue but a few HW. I originally had a failure after I left It running for the first time went to sleep and it was all XXXXX on boards, after looking at the statistics page per my miner address I found out it quit at about 2 hrs and I'm sure the temps raised up to 90 and above, I highly doubt that it ever got to 100 celcius because when I tested this morning and when I got off work it would fail at about 95 across all 3 boards of the miner, so don't believe when elsewhere I seen someone post Bitmain told them acceptable temps up to 115 celcius. good luck. By the way I did play with the frequency by lowering it but it never helped me I still got many faults every time at the 3 minutes running mark of the A3 when rebooted.Title: Re: Anyone else having issues with their Antminer A3? Post by: STATIK on March 15, 2018, 09:14:27 AM Hello guys.i have situation about quantity of errors of A3.All chips are 000 but the quantity of errors is about 110K after 1d5h restart with 850-880Gh and frq 631m,it's after when i made it down for one step frq,before it was even more errors about 450k for 9hours work. and hashes so jumping up and down from 850-890gh is it normal situation for this machine?temp on chip 61-68 who can recommend smth? HW errors are not a big deal there is a formula I posted in earlier pages of this topic variation in hash is not unusual Title: Re: Anyone else having issues with their Antminer A3? Post by: STATIK on March 15, 2018, 09:18:09 AM please help and thank you very much i do appreciate any help Network issue likely, check static/dhcp settingsmany miners running good A-3 Was fine now after reloaction it powers but wont hash no red or green lights. resets doesnt do anything no IP what can i do? Title: Re: Anyone else having issues with their Antminer A3? Post by: STATIK on March 15, 2018, 09:19:41 AM I'm new to Mining so I'm trying to decided if I should stick my Antminer A3 in the Cooler for noise reduction Yea I doubt this thing will survive any form of air constriction or deprivation too tight with heat sinks... OP sorry bud seems everyone has hijacked your post with not much helpor if buying a "Silent Jet Fan" like the ones that the Antminer s5 are modified with by their owners will work? Modified Cooler or Silent Jet Fan? Or better options (liquid Mineral Oil might be too much). Title: Re: Anyone else having issues with their Antminer A3? Post by: STATIK on March 15, 2018, 09:25:36 AM David71j could you confirm you have a failed board by switching it to another set of connectors and seeing if it in fact is a failed board and reads CHAIN 0 has 0 ASIC again in kernel log, this should confirm if you need to send it back to BITMAIN
Title: Re: Anyone else having issues with their Antminer A3? Post by: Voltar on March 18, 2018, 05:35:03 AM I'm new to Mining so I'm trying to decided if I should stick my Antminer A3 in the Cooler for noise reduction Yea I doubt this thing will survive any form of air constriction or deprivation too tight with heat sinks... OP sorry bud seems everyone has hijacked your post with not much helpor if buying a "Silent Jet Fan" like the ones that the Antminer s5 are modified with by their owners will work? Modified Cooler or Silent Jet Fan? Or better options (liquid Mineral Oil might be too much). Just buy another power supply. The power supply is the noisiest part. Title: Re: Anyone else having issues with their Antminer A3? Post by: EricJH801 on March 18, 2018, 05:40:11 AM Power supply makes barely any noise if it's a APW3++. The fans on the antminer A3 itself are very loud (6000 RPM) at about 85DB.
Plenty of methods to make them quieter and cooler, just look it up on youtube. Better yet, put them somewhere they won't bug you and let them go. I'm new to Mining so I'm trying to decided if I should stick my Antminer A3 in the Cooler for noise reduction Yea I doubt this thing will survive any form of air constriction or deprivation too tight with heat sinks... OP sorry bud seems everyone has hijacked your post with not much helpor if buying a "Silent Jet Fan" like the ones that the Antminer s5 are modified with by their owners will work? Modified Cooler or Silent Jet Fan? Or better options (liquid Mineral Oil might be too much). Just buy another power supply. The power supply is the noisiest part. Title: Re: Anyone else having issues with their Antminer A3? Post by: JacobHarding1978 on March 18, 2018, 11:03:02 AM Ok kids,
You all look like awesome boffs. But looking at the kernel log of john smith back there he look like he is having the same issue i was. Pop out your control board. Yep disconnect all your cables. Flip the cboard over and look at all the solder connections. I found horrible white powder. Yep the low silver content causes the connections to 'decay'. I fixed it by getting a new toothnrush and give the ol girl a good scrub to clean any of the offensive unwanted powder out. Whack her back in and see how she winds up. Ask me my sia coin addy for a generous doni if it works. Title: Re: Anyone else having issues with their Antminer A3? Post by: David71j on March 20, 2018, 12:25:42 PM David71j .........send it back to BITMAIN My device is being repaired Title: Re: Anyone else having issues with their Antminer A3? Post by: Mrkizg on March 22, 2018, 03:06:22 PM I have a problem with the brand new A3 miner. The fans power on, but there is no green nor red light, there is no IP, reset button doesn't work...I cannot do anything with it...is it a control panel malfunction or what? I tried everything including flashing via SD card and nothing helped. Help anyone who can ???
Title: Re: Anyone else having issues with their Antminer A3? Post by: satiriasis on March 22, 2018, 03:52:22 PM Hi,
I just received my first Anminer - A3 version and having similar problems, only 1 hash board is functional. Using Bitmain PSU@220V. I will try advice that JacobHarding suggested, do you have any other advices that has worked for you? I will also check to reconnect the PCIe and localize the not working hashing boards. My hash board #2 is visible, but having xxxxx instead of 0000... and the third hash board is not detected at all... Thanks for any advice Title: Re: Anyone else having issues with their Antminer A3? Post by: srkota on March 25, 2018, 08:54:17 PM I have the same problem with the brand new A3 miner. The fans power on, but there is no green nor red light, there is no IP, reset button doesn't work...I cannot do anything with it...is it a control panel malfunction or what? fan is going on and off every minute. logs show that FAN1 too slow, FAN2 too slow. Hardware version shows as "Socket connect failed: Connection refused". Tried reboot and reset. Nothing worked. can anyone help with this?
Title: Re: Anyone else having issues with their Antminer A3? Post by: satiriasis on March 26, 2018, 07:13:12 PM While debugging the device according Bitmain instructions I came to know, that two hash boards are faulty. I sent them back to Hongkong for repair... It is unfortunate situation, the post is really costly and this device seems to be really time dependent, the profitability falls rapidly down...
Title: Re: Anyone else having issues with their Antminer A3? Post by: JacobHarding1978 on March 27, 2018, 09:36:44 PM just another suggestion guys...under your advanced settings in miner config....set your freq to 600...the system seems to default to that....I had the issue also and I manually set the freq and fan speed to 75%.
Save and reboot. Title: Re: Anyone else having issues with their Antminer A3? Post by: David71j on July 30, 2018, 08:43:11 PM who has the device still in use? Title: Re: Anyone else having issues with their Antminer A3? Post by: omaxomax on September 01, 2018, 07:03:29 PM hello
i have bought a A3 recently. the hash rate in siamining is around 40GH/s is it normal?what should i do? (antminer a3 815GH/s?) please help im new |
