Topic: Bitmain Announces the Antminer R4 and APW5 Power Supply, Designed for Silence - page 13. (Read 84827 times)
January 24, 2017, 06:30:34 PM
There is no need to fear firmware upgrades as long as you confirm the firmware is for your device/batch/whatever before attempting to flash. I have flashed literally thousands of bitmain units without bricking a single controller.
January 24, 2017, 06:07:06 PM
Great - Thanks!
BTW - How do I see what the current release and/or firmware I have? The system/overview info for both R4s appear to be identical....
Thanks again (sorry for the newbie questions)
System > Overview, look at the date after File System Version. That is actually the firmware version. For Bitmains downloads the date is given in YR-MO-DAY-24hr time format eg. 201612020035 is 2016 Dec 2 00:35 Eastern TimeBTW - How do I see what the current release and/or firmware I have? The system/overview info for both R4s appear to be identical....
Thanks again (sorry for the newbie questions)
So my 1st R4 is:Fri Dec 2 00:35:59 EST 2016
2nd R4 is:Sat Nov 19 03:13:24 EST 2016
Is the 1st considered an "upgrade" to the firmware?
I read somewhere here NOT to fool with firmware upgrades..but the unit is running hot..hotter than a few hours ago..in the mid 116F ish right now
EDIT: Query -- which one runs hot? The Nov 19 or Dec 2 release? I ask because the R4 b6 that lost a hashboard (reports only 8 ASIC's) has the Dec 2 firmware and the remaining board runs around 100C.
The R4 b6 I got Monday has firmware dated Dec 9 and runs 3-5 C cooler.
January 24, 2017, 06:01:08 PM
Great - Thanks!
BTW - How do I see what the current release and/or firmware I have? The system/overview info for both R4s appear to be identical....
Thanks again (sorry for the newbie questions)
System > Overview, look at the date after File System Version. That is actually the firmware version. For Bitmains downloads the date is given in YR-MO-DAY-24hr time format eg. 201612020035 is 2016 Dec 2 00:35 Eastern TimeBTW - How do I see what the current release and/or firmware I have? The system/overview info for both R4s appear to be identical....
Thanks again (sorry for the newbie questions)
So my 1st R4 is:Fri Dec 2 00:35:59 EST 2016
2nd R4 is:Sat Nov 19 03:13:24 EST 2016
Is the 1st considered an "upgrade" to the firmware?
I read somewhere here NOT to fool with firmware upgrades..but the unit is running hot..hotter than a few hours ago..in the mid 116F ish right now
January 24, 2017, 04:09:57 PM
Decided not to go the slow boat to China route, even though unit just a few days old, and just shipped my R4 with bad board to BitmainWarranty in Colorado for repair. I'm hoping for the best. We'll see what happens.
January 24, 2017, 04:03:49 PM
I just received my 2nd R4 today and it is up and running - albeit a little hot!
My 1st R4 has temperature monitoring on two (2) chips, generally between the 70-mid 90 degree ranges.
This new R4 (my 2nd) only has one of its chips monitored, and is (so far) running around 110-115 degree range.
I guess my 1st concern is why is only one chip being monitored (both boards are at 100+% Th/s) and the 2nd concern, is 100 degree plus OK?
My 1st R4 has temperature monitoring on two (2) chips, generally between the 70-mid 90 degree ranges.
This new R4 (my 2nd) only has one of its chips monitored, and is (so far) running around 110-115 degree range.
I guess my 1st concern is why is only one chip being monitored (both boards are at 100+% Th/s) and the 2nd concern, is 100 degree plus OK?
Update to the latest firmware release and you will get the monitoring for both chips and it will help bring your temps down a little.
I had a similar unit with one board reporting temps above 100 C. After 2 days the board stopped working. I hope you have better luck. Keep us updated.
January 24, 2017, 03:48:35 PM
Great - Thanks!
BTW - How do I see what the current release and/or firmware I have? The system/overview info for both R4s appear to be identical....
Thanks again (sorry for the newbie questions)
System > Overview, look at the date after File System Version. That is actually the firmware version. For Bitmains downloads the date is given in YR-MO-DAY-24hr time format eg. 201612020035 is 2016 Dec 2 00:35 Eastern Time BTW - How do I see what the current release and/or firmware I have? The system/overview info for both R4s appear to be identical....
Thanks again (sorry for the newbie questions)
January 24, 2017, 03:35:34 PM
Great - Thanks!
BTW - How do I see what the current release and/or firmware I have? The system/overview info for both R4s appear to be identical....
Thanks again (sorry for the newbie questions)
BTW - How do I see what the current release and/or firmware I have? The system/overview info for both R4s appear to be identical....
Thanks again (sorry for the newbie questions)
January 24, 2017, 03:14:51 PM
I just received my 2nd R4 today and it is up and running - albeit a little hot!
My 1st R4 has temperature monitoring on two (2) chips, generally between the 70-mid 90 degree ranges.
This new R4 (my 2nd) only has one of its chips monitored, and is (so far) running around 110-115 degree range.
I guess my 1st concern is why is only one chip being monitored (both boards are at 100+% Th/s) and the 2nd concern, is 100 degree plus OK?
My 1st R4 has temperature monitoring on two (2) chips, generally between the 70-mid 90 degree ranges.
This new R4 (my 2nd) only has one of its chips monitored, and is (so far) running around 110-115 degree range.
I guess my 1st concern is why is only one chip being monitored (both boards are at 100+% Th/s) and the 2nd concern, is 100 degree plus OK?
Update to the latest firmware release and you will get the monitoring for both chips and it will help bring your temps down a little.
January 24, 2017, 02:46:12 PM
I just received my 2nd R4 today and it is up and running - albeit a little hot!
My 1st R4 has temperature monitoring on two (2) chips, generally between the 70-mid 90 degree ranges.
This new R4 (my 2nd) only has one of its chips monitored, and is (so far) running around 110-115 degree range.
I guess my 1st concern is why is only one chip being monitored (both boards are at 100+% Th/s) and the 2nd concern, is 100 degree plus OK?
My 1st R4 has temperature monitoring on two (2) chips, generally between the 70-mid 90 degree ranges.
This new R4 (my 2nd) only has one of its chips monitored, and is (so far) running around 110-115 degree range.
I guess my 1st concern is why is only one chip being monitored (both boards are at 100+% Th/s) and the 2nd concern, is 100 degree plus OK?
January 24, 2017, 03:21:27 AM
Yep, right spot. Yours is dated Nov 25, 2016
Just as with my 1st batch-6 (with bad board after 22hrs so is 1/2 speed, Dec 2 firmware), this latest batch-6 has eerily smooth hashrate compared to the s9's.
ref:
http://i.imgur.com/3KOtxkDl.png
I wonder if it has to do with this bit of code the log spits out and the miner is per-chip tweaking to give advertised spec?
Just as with my 1st batch-6 (with bad board after 22hrs so is 1/2 speed, Dec 2 firmware), this latest batch-6 has eerily smooth hashrate compared to the s9's.
ref:
http://i.imgur.com/3KOtxkDl.png
I wonder if it has to do with this bit of code the log spits out and the miner is per-chip tweaking to give advertised spec?
Code:
miner total rate=8898GH/s fixed rate=8700GH/s
My R4 Batch-4 in my main farm at work is just as rugged looking as those s9's are. Hmm...That graph looks more like the R4's are being logged on low difficulty shares and the S9's logging higher diff shares showing more variance. My R4's show similar spikes as my S7's & S9's.
January 23, 2017, 11:26:25 PM
@elokk,
Please check the reported tracking number. Techs will manually handle your repair request but tracking number you reported may be wrong and there may have been internal mix up due to the information not matching up.
Internal data, it shows, it was received on the 9th but the tracking you provided shows, it was delivered in another state on the 11th.
chances are your R4 is ready to go out to you since the the 10th or the 11th this month but may have mismatch identifier (tracking) and sitting in the owner response required que.
P.S: (GENERAL ANNOUNCEMENT) please help us by using 1 same Ticket Number for support request on the same item. Also, communication from 1 email address or one account is also very appreciated for expediting the process. Burnt PCB is highly unlikely attain successful repair.
Please check the reported tracking number. Techs will manually handle your repair request but tracking number you reported may be wrong and there may have been internal mix up due to the information not matching up.
Internal data, it shows, it was received on the 9th but the tracking you provided shows, it was delivered in another state on the 11th.
chances are your R4 is ready to go out to you since the the 10th or the 11th this month but may have mismatch identifier (tracking) and sitting in the owner response required que.
P.S: (GENERAL ANNOUNCEMENT) please help us by using 1 same Ticket Number for support request on the same item. Also, communication from 1 email address or one account is also very appreciated for expediting the process. Burnt PCB is highly unlikely attain successful repair.
I sent an R4 into Bitmain Warranty repair a few weeks ago. Still have not heard back since they received it
Definitely worth spending a little extra money to buy a used R4 that has been verified to hash on both boards and not risk the DOA units from China
Definitely worth spending a little extra money to buy a used R4 that has been verified to hash on both boards and not risk the DOA units from China
January 23, 2017, 09:22:06 PM
Yep, right spot. Yours is dated Nov 25, 2016
Just as with my 1st batch-6 (with bad board after 22hrs so is 1/2 speed, Dec 2 firmware), this latest batch-6 has eerily smooth hashrate compared to the s9's.
ref:
I wonder if it has to do with this bit of code the log spits out and the miner is per-chip tweaking to give advertised spec?
Just as with my 1st batch-6 (with bad board after 22hrs so is 1/2 speed, Dec 2 firmware), this latest batch-6 has eerily smooth hashrate compared to the s9's.
ref:
I wonder if it has to do with this bit of code the log spits out and the miner is per-chip tweaking to give advertised spec?
Code:
miner total rate=8898GH/s fixed rate=8700GH/s
The R4 Batch-4 in my main farm at work is just as rugged looking as those s9's are. Hmm... 
January 23, 2017, 09:12:33 PM
Got my other R4 batch-6 today: so far so good, holding a very even 8.7-8.9THs and all temps under 100C
Interesting thing: My 1st batch-6 (which had a board crap out 22hrs after running it) which I got last Tuesday has firmware dated Dec. 2 2016 - same as what Bitmain has up on their site.
This new one firmware date is Dec 9 2016...
Hmm, beta testing on us customers again?
Interesting thing: My 1st batch-6 (which had a board crap out 22hrs after running it) which I got last Tuesday has firmware dated Dec. 2 2016 - same as what Bitmain has up on their site.
This new one firmware date is Dec 9 2016...
Hmm, beta testing on us customers again?
let me check my 7.5th version
is this the right spot?
Miner Type Antminer R4
Hostname antMiner
Model GNU/Linux
Hardware Version 4.8.1.3
Kernel Version Linux 3.14.0-xilinx-gf387dab-dirty #38 SMP PREEMPT Fri Jun 17 20:02:51 CST 2016
File System Version Fri Nov 25 21:20:07 EST 2016
BMminer Version 2.0.0
Uptime 4:19
Load Average 0.14, 0.21, 0.21
January 23, 2017, 08:24:51 PM
Got my other R4 batch-6 today: so far so good, holding a very even 8.7-8.9THs and all temps under 100C
Interesting thing: My 1st batch-6 (which had a board crap out 22hrs after running it) which I got last Tuesday has firmware dated Dec. 2 2016 - same as what Bitmain has up on their site.
This new one firmware date is Dec 9 2016...
Hmm, beta testing on us customers again?
Interesting thing: My 1st batch-6 (which had a board crap out 22hrs after running it) which I got last Tuesday has firmware dated Dec. 2 2016 - same as what Bitmain has up on their site.
This new one firmware date is Dec 9 2016...
Hmm, beta testing on us customers again?
January 23, 2017, 08:23:51 PM
My older r4. Has dropped a board.
I will need to send it back to china I guess.
My new r4 came today and is working okay.
So I have 3/4 of the boards working.
I will need to send it back to china I guess.
My new r4 came today and is working okay.
So I have 3/4 of the boards working.
January 22, 2017, 08:30:42 PM
I sent an R4 into Bitmain Warranty repair a few weeks ago. Still have not heard back since they received it
Definitely worth spending a little extra money to buy a used R4 that has been verified to hash on both boards and not risk the DOA units from China
Definitely worth spending a little extra money to buy a used R4 that has been verified to hash on both boards and not risk the DOA units from China
January 22, 2017, 08:28:33 PM
Thanks all for the help. I finally did get it to hash with the single board by swapping the cables on the controller board and unplugging cable and power from bad board.
January 22, 2017, 05:57:06 PM
Since it seems I have a bad board, I tried powering one board at a time (with controller powered) to reduce power load but I get no hashing. This was easy to do issue on S7s, but it seems like both boards need to be powered on the R4 to get anything. Is there a way to just power one board and controller to get the same hash as above at a lower power? Is anyone powering just one board?
I ran into the same issue. This was my first thought as well. I hooked up a 2nd PSU to the bad board and powered it that way, then once it was on, I just turned the power off on the 2nd PSU. I found UPS wanted $400 to return the entire unit to China, which made bitmainwarranty.com cheaper, even though you have to pay for the repair. It was also a very fast turnaround time.
January 22, 2017, 05:49:44 PM
Bad board, see below
Since it seems I have a bad board, I tried powering one board at a time (with controller powered) to reduce power load but I get no hashing. This was easy to do issue on S7s, but it seems like both boards need to be powered on the R4 to get anything. Is there a way to just power one board and controller to get the same hash as above at a lower power? Is anyone powering just one board?
Since it seems I have a bad board, I tried powering one board at a time (with controller powered) to reduce power load but I get no hashing. This was easy to do issue on S7s, but it seems like both boards need to be powered on the R4 to get anything. Is there a way to just power one board and controller to get the same hash as above at a lower power? Is anyone powering just one board?
January 22, 2017, 03:21:12 PM
QUESTION ON RETURN TO BITMAIN
Do I ship to China address and does Bitmain pay for shipping or do I?
Help please Bitmain
Do I ship to China address and does Bitmain pay for shipping or do I?
Help please Bitmain
Everything I have had to ship back to China for warranty repair I had to pay the shipping. It was an S9 board and a controller. Shipping was expensive as a MF'r. And that was only a single board and a controller! BM paid the return shipping.
For the R4, I think you are supposed to return the whole unit. I can't imagine what that will cost.
Good luck.
Jump to: