ANTMINER S3+ Discussion and Support Thread - page 104.

bitsolutions

sr. member

Activity: 261

Merit: 257

Quote from: DevonMiner on December 16, 2014, 02:05:46 PM

Any ideas on this problem please? ...

One of my S3s won't load the 'miner status' tab on the web GUI, all other tabs can be accessed.

This is what it displays:

Code:

/usr/lib/lua/luci/dispatcher.lua:448: Failed to execute cbi dispatcher target for entry '/admin/status/minerstatus'.
The called action terminated with an exception:
/usr/lib/lua/luci/controller/cgminer.lua:32: bad argument #1 to 'floor' (number expected, got string)
stack traceback:
	[C]: in function 'assert'
	/usr/lib/lua/luci/dispatcher.lua:448: in function 'dispatch'
	/usr/lib/lua/luci/dispatcher.lua:195: in function

I have flashed to the latest firmware, and back again ... even restored an old backup. Whichever version is loaded into the miner gives the same error message on the miner status tab.

Can't do a hard reset, as it doesn't seem to work ... hold down for 10 seconds or more ... the miner doesn't reset.

If you are on the latest November firmware try running this command over ssh.

Code:

cp /overlay/etc/config/cgminer /tmp/cgminer.tmp && cp /overlay/etc/config/network /tmp/network.tmp && rm -r /overlay/* && mkdir /overlay/etc && mkdir /overlay/etc/config && cp /tmp/cgminer.tmp /overlay/etc/config/cgminer && cp /tmp/network.tmp /overlay/etc/config/network && reboot

mazedk

sr. member

Activity: 457

Merit: 250

Has anyone seen anything like this in their processes?

working:

cgminer --bitmain-options 115200:32:8:18:218.75:1106 -o uk1.ghash.io:3333 -O xx.btc1:123 -o us1.ghash.io:3333 -O xx.btc1:123 --bitmain-notempoverctrl --bitmain-nobeeper --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --version-file /usr/bin/compile_time --queue 4096

isnt working:

cgminer --bitmain-options 115200:32:8:18:218.75:1106 -o uk1.ghash.io:3333 -O xx.btc1:123 -o us1.ghash.io:3333 -O xx.btc1:123 --bitmain-nobeeper --api-listen --api-network --bitmain-checkn2diff --bitmain-hwerror --queue 4096

theres some difference.. but also it doesnt say "model S3" in the front page of the failing miner.. it says:

ModelITP-Link TL-WR743N/ND v2
Firmware VersionIOpenWrt Barrier Breaker r38031 / LuCI Trunk (svn-r9909)

pekatete

hero member

Activity: 518

Merit: 500

Quote from: dog1965 on December 16, 2014, 03:07:18 PM

can you actually use the CP2102 USB to serial controller to mine with it hooked up to the built in controller and cgminer running on your pc instead of sh*tmains version.

If you have 2 CP2102, you can connect one to each board and mine away! cgminer will recognise the boards (so long as you have the right drivers compiled in), but you will probably have to run them with the blue wire hack for temp control.

dog1965

sr. member

Activity: 392

Merit: 250

can you actually use the CP2102 USB to serial controller to mine with it hooked up to the built in controller and cgminer running on your pc instead of sh*tmains version.

DevonMiner

sr. member

Activity: 471

Merit: 250

Any ideas on this problem please? ...

One of my S3s won't load the 'miner status' tab on the web GUI, all other tabs can be accessed.

This is what it displays:

Code:

/usr/lib/lua/luci/dispatcher.lua:448: Failed to execute cbi dispatcher target for entry '/admin/status/minerstatus'.
The called action terminated with an exception:
/usr/lib/lua/luci/controller/cgminer.lua:32: bad argument #1 to 'floor' (number expected, got string)
stack traceback:
	[C]: in function 'assert'
	/usr/lib/lua/luci/dispatcher.lua:448: in function 'dispatch'
	/usr/lib/lua/luci/dispatcher.lua:195: in function

I have flashed to the latest firmware, and back again ... even restored an old backup. Whichever version is loaded into the miner gives the same error message on the miner status tab.

Can't do a hard reset, as it doesn't seem to work ... hold down for 10 seconds or more ... the miner doesn't reset.

nitrox1

newbie

Activity: 28

Merit: 0

Quote from: ATCkit on December 16, 2014, 10:03:46 AM

Quote from: macgyver007 on December 16, 2014, 09:35:03 AM

Quote from: nitrox1 on December 16, 2014, 09:31:14 AM

So if I get a USB to serial, then connect to debug.
Quote: "the ground pin, connect tx and rx....if you get a load of junk on your screen reverse the rx/tx and you will see magic...well not really but you will see the data on the screen...for putty set 115200, no flow control, and make sure you have the correct COM port defined"

Then what,? Hit it with a herring? Or other smoked fish? Get the fans going and cook bacon? So lost

So when you putty in to old IP address its not asking you for username/password?

Smoked salmon works best mmmmm bacon Grin

Sorry I amended the instructions...once you have access to the miner, type
mtd -r erase rootfs_data and hit enter
then type REBOOT and hit enter

If anyone has a bricked controller and not comfortable de-bricking it I can help...Im based in Canada

If you're in Ottawa, i would pay you to come over with your device and get my miner up and running. If you're not in Ottawa (most likely you're in Toronto or Vancouver), PM me your phone number.

Will talk later as i gotta run to the Dr now.

Nope, Just is the only putty window that doesn't shut down.
So I do have the red blinking light of death then.
No recovery available through flashing, then?
Where can I get a control board? Anywhere speedier than Bitmain?

pekatete

hero member

Activity: 518

Merit: 500

Quote from: bitsolutions on December 16, 2014, 11:32:16 AM

Quote from: pekatete on December 16, 2014, 08:49:06 AM

Now the easy bit, @bitsolutions or any of you clever clogs out there, can you make any sense of that?

Lol, this is not the "easy bit", its a compiled file, you aren't going to get much further than this unless you know how to read assembly.

That was tongue-in-cheek stuff, but yeah, I thought if anyone was going to have a clue about what the hell was going on, it was going to be you. In the meantime, dog1965 seems to have a historic attachement to machine language, so he's going to run a rule over the file .... fingers crossed. Any other clever clogs about and conversant with machine language, do not feel shy!

bitsolutions

sr. member

Activity: 261

Merit: 257

Quote from: nitrox1 on December 16, 2014, 09:08:01 AM

Very new here.But seem like I'm another the latest firmware as bricked my control board.
It was flashed over WIFI network, and had the message that the firmware was ready to flash.
Now I have the red flashing LED of death.
Latest firmware took on my two other units.
I'm able to open a telnet connection on the old IP address, but that is it. I'm lost from here.
I see some HEX stuff going on, but it is way beyond me. Is the hex file able to be flashed through ethernet?
Any solutions to get firmware flashed over again maybe over LAN1, Debug???

If you can't get to the webui or ssh in try the reset button, latest firmware shouldn't brick control board, its just somewhat unstable. The hex file has nothing to do with this issue.

Quote from: pekatete on December 16, 2014, 08:49:06 AM

Not being one to take good advice when given some, after realising the miner_pic.hex file was an ASCII file, I decided to deploy my secret reference material (read google) and seem to have found something, though I can not make any sense of it. I am sure bitsolutions, the clever clogs on our side, can so here goes.

1. My reference material suggested a site to view a hex file: http://en.webhex.net/
On visiting the site, I browsed to the file and uploaded the miner_pic.hex file

2. On the next screen, I scrolled to the bottom of the box and clicked on the Export link

3. When the Export screen was loaded, I un-checked the Headline, Offsets and Readable Characters check-boxes then clicked on the Export button on that screen.

4. I was then presented with the hex data in a web page. I had not mentioned this, but earlier, my reference material had also suggested to me an online dis-assembler here : http://www2.onlinedisassembler.com/odaweb/

5. I copied all the exported hex data (Ctrl + A then Ctrl + C) then flicked over to the dis-assembler, clicked on the Platform button and changed it to avr (this may b wrong), and in the box below that I pasted the hex data into it.

The page then did a little spinning wheel and after a short while, spewed out something like this:

Now the easy bit, @bitsolutions or any of you clever clogs out there, can you make any sense of that?

Lol, this is not the "easy bit", its a compiled file, you aren't going to get much further than this unless you know how to read assembly.

Quote from: ATCkit on December 16, 2014, 07:57:34 AM

@bitsolutions

".... I recommend everyone stay far far away from antMiner_S320141024 as it greatly increases the chance of you bricking your control card(only way to recover is with ttl) since the reset doesn't work(filesystem issue)...."

I have the bricking problem you mention. Bitmain just told me my warranty has expired. (They must start counting the 90 days from the time they ship instead of teh day I received it Sad

)

Questions:

1. Instead of buying another control board, how do i use ttl to recover it? Sorry, I 'm gonna need step by step instructions.

2. My other S3s are running okay on the Oct 24th release. Should i re-flash them to the Oct 13th firmware?

TTL recovery is tricky if you haven't done that type of thing before and requires special adapters. Just send the control card to the US warranty address with your return address phone and email and they will let you know if it can be recovered.
Bitmain Warranty
3700 Quebec Street #100239
Denver, Colorado 80207
USA
Yes, you probably want to flash the older firmware or latest firmware with the pic fix.

neo9436

full member

Activity: 211

Merit: 100

So I updated 3 of my S3's to antMiner_S320141024.bin.

Had to restart 1 of the units and it seems to be bricked. Emailed bitmain, no response yet.

While the other 2 are still working, should I flash them to antMiner_S320140826.bin? I have no idea how to do an ssh stuff, so don't really want to mess around with antMiner_S320141013.bin.

Thanks.

ATCkit

hero member

Activity: 786

Merit: 1000

Quote from: macgyver007 on December 16, 2014, 09:35:03 AM

Quote from: nitrox1 on December 16, 2014, 09:31:14 AM

So if I get a USB to serial, then connect to debug.
Quote: "the ground pin, connect tx and rx....if you get a load of junk on your screen reverse the rx/tx and you will see magic...well not really but you will see the data on the screen...for putty set 115200, no flow control, and make sure you have the correct COM port defined"

Then what,? Hit it with a herring? Or other smoked fish? Get the fans going and cook bacon? So lost

So when you putty in to old IP address its not asking you for username/password?

Smoked salmon works best mmmmm bacon Grin

Sorry I amended the instructions...once you have access to the miner, type
mtd -r erase rootfs_data and hit enter
then type REBOOT and hit enter

If anyone has a bricked controller and not comfortable de-bricking it I can help...Im based in Canada

If you're in Ottawa, i would pay you to come over with your device and get my miner up and running. If you're not in Ottawa (most likely you're in Toronto or Vancouver), PM me your phone number.

Will talk later as i gotta run to the Dr now.

macgyver007

member

Activity: 105

Merit: 10

Quote from: nitrox1 on December 16, 2014, 09:31:14 AM

So if I get a USB to serial, then connect to debug.
Quote: "the ground pin, connect tx and rx....if you get a load of junk on your screen reverse the rx/tx and you will see magic...well not really but you will see the data on the screen...for putty set 115200, no flow control, and make sure you have the correct COM port defined"

Then what,? Hit it with a herring? Or other smoked fish? Get the fans going and cook bacon? So lost

So when you putty in to old IP address its not asking you for username/password?

Smoked salmon works best mmmmm bacon Grin

Sorry I amended the instructions...once you have access to the miner, type
mtd -r erase rootfs_data and hit enter
then type REBOOT and hit enter

If anyone has a bricked controller and not comfortable de-bricking it I can help...Im based in Canada

pekatete

hero member

Activity: 518

Merit: 500

Quote from: dog1965 on December 16, 2014, 09:20:51 AM

push = push onto stack. pop=pull off of stack note: first byte in is last byte out so if I push four values "10 20 30 40 whatever" I have to pop the stack four times to get the first value I pushed in.

jne = jump if not equal compare values if they are not equal the jump back in the loop to LOC_00000010 this is the beginning of the sub loop routine.

ret = return from sub loop once values are equal. Continue processing "keep going down screen"

you get the idea its like C the same structure. when you compile C this is what it turns it into provided you did not make any error lol. Cheesy

I catch the drift .... I think ..... yes, I think so.
Anyhow, is it possible to dis-assemble this machine language further into C++? The image above only shows a small fraction of the data, possibly less than 1% ....

nitrox1

newbie

Activity: 28

Merit: 0

So if I get a USB to serial, then connect to debug.
Quote: "the ground pin, connect tx and rx....if you get a load of junk on your screen reverse the rx/tx and you will see magic...well not really but you will see the data on the screen...for putty set 115200, no flow control, and make sure you have the correct COM port defined"

Then what,? Hit it with a herring? Or other smoked fish? Get the fans going and cook bacon? So lost

pekatete

hero member

Activity: 518

Merit: 500

Quote from: dog1965 on December 16, 2014, 09:00:49 AM

ah that is assembly language otherwise known as "MACHINE LAUNGUAGE" I used to write programs with it back in the 1980's so I know how to do it I recognize the commands just some new ones in there I see. like I said I am rusty but I think I can do I just have to brush up on the new commands.

Another clever clogs about .... very well. If you need anything from me, post here or drop me a PM.

dog1965

sr. member

Activity: 392

Merit: 250

push = push onto stack. pop=pull off of stack note: first byte in is last byte out so if I push four values "10 20 30 40 whatever" I have to pop the stack four times to get the first value I pushed in.

jne = jump if not equal compare values if they are not equal the jump back in the loop to LOC_00000010 this is the beginning of the sub loop routine.

ret = return from sub loop once values are equal. Continue processing "keep going down screen"

you get the idea its like C the same structure. when you compile C this is what it turns it into provided you did not make any error lol. Cheesy

nitrox1

newbie

Activity: 28

Merit: 0

Quote from: macgyver007 on December 16, 2014, 09:13:25 AM

Quote from: nitrox1 on December 16, 2014, 09:08:01 AM

Very new here.But seem like I'm another the latest firmware as bricked my control board.
It was flashed over WIFI network, and had the message that the firmware was ready to flash.
Now I have the red flashing LED of death.
Latest firmware took on my two other units.
I'm able to open a telnet connection on the old IP address, but that is it. I'm lost from here.
I see some HEX stuff going on, but it is way beyond me. Is the hex file able to be flashed through ethernet?
Any solutions to get firmware flashed over again maybe over LAN1, Debug???

If you can telnet to the miner all hope is not lost...does it allow you to log in to the miner using telnet?
You can use serial connect instructions are here....
https://bitcointalksearch.org/topic/bitmain-s3-serial-connect-889206

Ok, let me clarify. Telnet connection over putty, to the old IP address over Ethernet, is the only one that doesn't say connection failed. I don't know if I actually have a connection. I still get a blank screen

macgyver007

member

Activity: 105

Merit: 10

Quote from: nitrox1 on December 16, 2014, 09:08:01 AM

Very new here.But seem like I'm another the latest firmware as bricked my control board.
It was flashed over WIFI network, and had the message that the firmware was ready to flash.
Now I have the red flashing LED of death.
Latest firmware took on my two other units.
I'm able to open a telnet connection on the old IP address, but that is it. I'm lost from here.
I see some HEX stuff going on, but it is way beyond me. Is the hex file able to be flashed through ethernet?
Any solutions to get firmware flashed over again maybe over LAN1, Debug???

If you can telnet to the miner all hope is not lost...does it allow you to log in to the miner using telnet?
You can use serial connect instructions are here....
https://bitcointalksearch.org/topic/bitmain-s3-serial-connect-889206

nitrox1

newbie

Activity: 28

Merit: 0

Very new here.But seem like I'm another the latest firmware as bricked my control board.
It was flashed over WIFI network, and had the message that the firmware was ready to flash.
Now I have the red flashing LED of death.
Latest firmware took on my two other units.
I'm able to open a telnet connection on the old IP address, but that is it. I'm lost from here.
I see some HEX stuff going on, but it is way beyond me. Is the hex file able to be flashed through ethernet?
Any solutions to get firmware flashed over again maybe over LAN1, Debug???

macgyver007

member

Activity: 105

Merit: 10

I am looking at one of the most "incredible" displays of sheer incompetence and negligence by a company, namely BITMAIN releasing not 1, not 2 but 3 sabotaged firmwares in the last 2 months to the day...what really bothers me is not only the fact that all of the last 3 firmwares are BROKEN and not only has BITMAIN basically ignored these problems by doing nothing, they are allowing the community to in essence POISON the bitcoin network with faulty hardware by allowing others to still download and brick their miners....unbelievable really Roll Eyes

I don't see how this is not negligent behavior and not downright reckless by BITMAIN to still even have those 3 firmware on their page...1 is worse than the other and all 3 can brick units....

BITMAIN PULL THE DEFECTIVE FIRMWARE FROM YOUR SITE AND FIX IT..this is IRRESPONSIBLE AND RECKLESS ENDANGERMENT

dog1965

sr. member

Activity: 392

Merit: 250

ah that is assembly language otherwise known as "MACHINE LAUNGUAGE" I used to write programs with it back in the 1980's so I know how to do it I recognize the commands just some new ones in there I see. like I said I am rusty but I think I can do I just have to brush up on the new commands.

Topic: ANTMINER S3+ Discussion and Support Thread - page 104. (Read 710164 times)