The problem with this image would be the voltage and frequency values since the 1.5 T architecture is quite different - 6 blades / 10 chips per blade.
But nevertheless it worth trying to see if the RPi boots up. Actually he can use the standard 1T image (4 blades / 8 chips per blade) to check if it works - it may not recognize the extra hardware that the rig has but still may work @1TH or maybe even @2TH - will have to try that as well.
Topic: Help w/ Firmware for 2 TH/s A1 miner (Read 7328 times)
Of course, try other images, I think notlist3d suggested some other image. You should know that standard SD card for these rigs as they come from China is Sandisc Extreme 8GB Class 10. I've tried the image in question with the regular one (Class 6 8GB) and it worked as well.
I don't know what is wrong in your case but definatelly tested this image and it works.
Keep us posted if you find the issue.
I don't know what is wrong in your case but definatelly tested this image and it works.
Keep us posted if you find the issue.
My image was a different one. Not a ton of unit's use it compared to the 1T images. But it's worth a shot of trying since nothing else worked. It's from a 1.5 T unit.
It also came off a 8 gb sd card, and will fit on a 8 gb sd card.
Of course, try other images, I think notlist3d suggested some other image. You should know that standard SD card for these rigs as they come from China is Sandisc Extreme 8GB Class 10. I've tried the image in question with the regular one (Class 6 8GB) and it worked as well.
I don't know what is wrong in your case but definatelly tested this image and it works - actually I am using it right now for all of the 1T Dragons because of the low BTC prices - to underclock them.
Keep us posted if you find the issue.
I don't know what is wrong in your case but definatelly tested this image and it works - actually I am using it right now for all of the 1T Dragons because of the low BTC prices - to underclock them.
Keep us posted if you find the issue.
[/quote]
What's that supose to mean ?
On 32G SD card the image is booting up and it's fine ?
or
You can copy the image only on 32 GB card ?
[/quote]
both
boots on the 32g micro sd
dosen't work with the 8g micro sd hc - tried several cards
burned using rufus
still cant access via network -
192.168.1.113
nothing -
using putty
can access same pi with other raspbians on so not the pi
going to try with other image
and
will keep tweaking -
i've got a new router coming will see if that helps
...
image works on a sd that is a 32g
but dosen't work on an 8g card
...
image works on a sd that is a 32g
but dosen't work on an 8g card
...
What's that supose to mean ?
On 32G SD card the image is booting up and it's fine ?
or
You can copy the image only on 32 GB card ?
Either way - you're doing something wrong or inappropriate SD cards are used.
Most (not 100% sure but I think all) images for these type of rigs are intended for 8 GB SD cards preferably class 10.
Try writing the image to SD card and do the testing on another Dragon if you have one or your friend's one.
Or even easier, try the newly made SD card on someone else's RPi to check if it's booting.
P.S. By the way what is the network addressing you're using ? Is your network 192.168.1.X ?
cant connect with ssh- well i tried putty and its a no go , http @ ip , no joy either
image works on a sd that is a 32g
but dosen't work on an 8g card
will try some more later
thing is - the pi network lights are not lit though it works with other sd images - will have to try a different pi model
image works on a sd that is a 32g
but dosen't work on an 8g card
will try some more later
thing is - the pi network lights are not lit though it works with other sd images - will have to try a different pi model
Just for the heck of it try this one - https://www.dropbox.com/s/so2wrtqbqd6jzzs/Dragon1.5boot.rar?dl=0
It's been a long while since I have used it so not sure of it. If all the standard ones are not working it's worth trying.
cant connect with ssh- well i tried putty and its a no go , http @ ip , no joy either
image works on a sd that is a 32g
but dosen't work on an 8g card
will try some more later
thing is - the pi network lights are not lit though it works with other sd images - will have to try a different pi model
image works on a sd that is a 32g
but dosen't work on an 8g card
will try some more later
thing is - the pi network lights are not lit though it works with other sd images - will have to try a different pi model
I don't get that hdmi part.There shouldn't be anything from pi-hdmi out.You simply connect via HTTP or SSH.So can you connect to pi either way?
I have had a few dragon's in my day. Helped a lot with them. I personally never used hdmi as a tool.
I would agree ssh is better way to go. Assuming you can get access from ssh, you can tell a lot from it.
I don't get that hdmi part.There shouldn't be anything from pi-hdmi out.You simply connect via HTTP or SSH.So can you connect to pi either way?
I can't say for sure that it's the reason. I've never had HDMI connected during the boot of any of these images. Did you try to access the rig via [email protected], ping ?
How are you making the image copy ? I am using rufus.
Does your SD card have 8GB capacity ? What speed Class is the SD card ?
Can you use a RPi model B instead if you think that this could be the culprit ?
There's a lot of things that may go wrong.
You have to keep trying with the trobleshooting since this image works for sure.
How are you making the image copy ? I am using rufus.
Does your SD card have 8GB capacity ? What speed Class is the SD card ?
Can you use a RPi model B instead if you think that this could be the culprit ?
There's a lot of things that may go wrong.
You have to keep trying with the trobleshooting since this image works for sure.
Look at this article here.
It's in Russian but you can view the translation in Chrome and see the detailed screenshots and settings of the image I posted - it's the same as in this article. Moreover I think the hardware is pretty much the same as yours.
And I'm pretty sure that this image works - tested on more than 10 of Dragons. No sure where you see these messages but its IP address is 192.168.1.113 (HTTP access).
You said that this rig was for spare parts - it might have a some kind of hardware problem (control board, RPi or something else broken).
It's in Russian but you can view the translation in Chrome and see the detailed screenshots and settings of the image I posted - it's the same as in this article. Moreover I think the hardware is pretty much the same as yours.
And I'm pretty sure that this image works - tested on more than 10 of Dragons. No sure where you see these messages but its IP address is 192.168.1.113 (HTTP access).
You said that this rig was for spare parts - it might have a some kind of hardware problem (control board, RPi or something else broken).
yes i am sure its the same model - probably some partial hardware issue
the rpi it came with was broken - i replaced it for a rpi b+ - slightly different rpi model but maybe that's what the problem is
- driver support for networking ? on the image - would it be an issue - i wouldn't have thought so . the new rpi networks fine with other raspbian sd installed no problem remote accessing with ip address- but no network lights on the miner image install.
tried without control board attached in hope it would simply network but still not
getting the messages from the rpi - hdmi out to monitor
so its got to be the software images network driver ? right ?
It was tested on Dragon 1TH (4 blades / 8 chips per blade) and obvioulsy it works on Dragon 2 TH like the one in the article mentioned.
Look at this article here.
It's in Russian but you can view the translation in Chrome and see the detailed screenshots and settings of the image I posted - it's the same as in this article. Moreover I think the hardware is pretty much the same as yours.
And I'm pretty sure that this image works - tested on more than 10 of Dragons. No sure where you see these messages but its IP address is 192.168.1.113 (HTTP access).
You said that this rig was for spare parts - it might have a some kind of hardware problem (control board, RPi or something else broken).
It's in Russian but you can view the translation in Chrome and see the detailed screenshots and settings of the image I posted - it's the same as in this article. Moreover I think the hardware is pretty much the same as yours.
And I'm pretty sure that this image works - tested on more than 10 of Dragons. No sure where you see these messages but its IP address is 192.168.1.113 (HTTP access).
You said that this rig was for spare parts - it might have a some kind of hardware problem (control board, RPi or something else broken).
What type of dragon's where they tested on? I believe there is two main variant's based on how many chips on each blade. It is not one size fit all like it once was.
Look at this article here.
It's in Russian but you can view the translation in Chrome and see the detailed screenshots and settings of the image I posted - it's the same as in this article. Moreover I think the hardware is pretty much the same as yours.
And I'm pretty sure that this image works - tested on more than 10 of Dragons. No sure where you see these messages but its IP address is 192.168.1.113 (HTTP access).
You said that this rig was for spare parts - it might have a some kind of hardware problem (control board, RPi or something else broken).
It's in Russian but you can view the translation in Chrome and see the detailed screenshots and settings of the image I posted - it's the same as in this article. Moreover I think the hardware is pretty much the same as yours.
And I'm pretty sure that this image works - tested on more than 10 of Dragons. No sure where you see these messages but its IP address is 192.168.1.113 (HTTP access).
You said that this rig was for spare parts - it might have a some kind of hardware problem (control board, RPi or something else broken).
well nearly right-
can't access through network yet--
can you help here?
image boots fine all looking well until...
remote desktop protocol server :xrdp sesman
then it just repeats
ip 5
ip 5
2 ip 5
over and over again
any ideas?
can't access through network yet--
can you help here?
image boots fine all looking well until...
remote desktop protocol server :xrdp sesman
then it just repeats
ip 5
ip 5
2 ip 5
over and over again
any ideas?
I would ask pinhead666 for his image knowing the IP make sure to use a different sd card so you don't lose that.
But if he has a working image on his it should be pretty easy to clone it.
well nearly right-
can't access through network yet--
can you help here?
image boots fine all looking well until...
remote desktop protocol server :xrdp sesman
then it just repeats
ip 5
ip 5
2 ip 5
over and over again
any ideas?
can't access through network yet--
can you help here?
image boots fine all looking well until...
remote desktop protocol server :xrdp sesman
then it just repeats
ip 5
ip 5
2 ip 5
over and over again
any ideas?
I had "free" electricity so I didn't bother underclocking it.It can be overclocked to 2,3TH but psus are rated only 1150W so I didn't.That config in picture takes 1000W per psu and gives 2,1TH.Now I have no free electric anymore so I have that thing hosted elsewhere.I once played with it and powered 3 blades (or six modules) with one psu underclocked and -volted heavily.I got 1,4 or 1,6 TH out with 1000W but error rate was huge.On the pool side maybe 1.2TH.
I have one of these A1 terminator 2TH miners. It has only 4 pcb-boards but 8 connection cables.So 8-board fw should be fine.Here is screenshot of the original fw.
Thanks for posting. Very interesting as far as an A1 firmware. Seems they gave you a lot of control. Which is very nice. Might even be able to find a decent under clock.
I have one of these A1 terminator 2TH miners. It has only 4 pcb-boards but 8 connection cables.So 8-board fw should be fine.Here is screenshot of the original fw.
Sure, if everything else is OK it should work.
Jump to: