10 minute resets confirmed by other testers too.
Feedback (does not mean 100% right):
1) "S9 works, but every 10 minutes it climbs to check the devfee pools. Pools are disabled, so every 10 minutes the ASIC is rebooted with this firmware."
2) "Loaded into S9, worked 10 minutes and fell off the pool, connected again to the pool worked again 10 minutes and again fell off.
Happens and works on the pool for 30 minutes, then did not check."
3) "One of the S9 with firmware 6b goes into reboot every 10 minutes."
Topic: Two stage performance tuning for S9 / S9i (include version for immersion cooling - page 3. (Read 2730 times)
August 16, 2018, 04:56:24 AM
August 15, 2018, 03:10:49 AM
Hello!
Please send the results of the Kernel Log page. it seems like a reduction in the frequency for individual chips, tomorrow I will make a new version
Please send the results of the Kernel Log page. it seems like a reduction in the frequency for individual chips, tomorrow I will make a new version
Hi developer
Tested on 3 different versions of S9
Results:
1)S9 13.5T resets (every 10 minutes)
2)S9i resets (every 10 minutes)
3)But one old S9 is OK
Kernel logs are here: https://1drv.ms/f/s!ArNwsEYWIidwgeJDG3-vG0ZqYYbX5A
Thank you for your work
August 13, 2018, 06:40:35 PM
I tested and result is good, except without "Auto Fan" - "Auto Reload Page" - "Auto Reboot when Hashrate if Low" features.. Can you add this features? it would be the best S9 firmware ever I quess 
I can return the auto fan, but the temperature will be higher. This is how the standard firmware behaves by default, constantly changing the speed of the fans, after the asic warms up.
August 13, 2018, 06:38:17 PM
Could you please explain is it Ok when S9 miner is reset about every 10mins when auto-tune is disabled?
How to avoid it? Any suggestions?
How to avoid it? Any suggestions?
Hello!
Please send the results of the Kernel Log page. it seems like a reduction in the frequency for individual chips, tomorrow I will make a new version
August 12, 2018, 11:55:07 AM
Hi developer,
Could you please explain is it Ok when S9 miner is reset about every 10mins when auto-tune is disabled?
How to avoid it? Any suggestions?
Thank you.
Could you please explain is it Ok when S9 miner is reset about every 10mins when auto-tune is disabled?
How to avoid it? Any suggestions?
Thank you.
August 09, 2018, 05:23:23 AM
I have problem with your firmware.
My antminer constantly restarting, even on default settings. (650 mhz frequency, 880 voltage).
I have turned off auto tuning.
With original firmware - no restarts. Could you explain what is wrong?
My antminer constantly restarting, even on default settings. (650 mhz frequency, 880 voltage).
I have turned off auto tuning.
With original firmware - no restarts. Could you explain what is wrong?
August 07, 2018, 02:46:01 PM
I tested and result is good, except without "Auto Fan" - "Auto Reload Page" - "Auto Reboot when Hashrate if Low" features.. Can you add this features? it would be the best S9 firmware ever I quess
August 06, 2018, 03:04:59 AM
Confirm.
It will be good to have the option to choose fan % or Auto.
It will be good to have the option to choose fan % or Auto.
August 05, 2018, 05:03:01 PM
I have tried the v6b..........the fans remain on 100% and dont auto increase or decrease.
Is there any way to enable autofan or fixed to a specific speed.
FAN PWM: 0
read_temp_func Done!
Thanks..
Is there any way to enable autofan or fixed to a specific speed.
FAN PWM: 0
read_temp_func Done!
Thanks..
since the main purpose of the firmware is overclocking, to reduce the risk of overheating, the fans are forcibly set to 100%
August 05, 2018, 06:33:13 AM
I have tried the v6b..........the fans remain on 100% and dont auto increase or decrease.
Is there any way to enable autofan or fixed to a specific speed.
FAN PWM: 0
read_temp_func Done!
Thanks..
Is there any way to enable autofan or fixed to a specific speed.
FAN PWM: 0
read_temp_func Done!
Thanks..
August 03, 2018, 10:08:42 PM
Actually you are the incorrect one here. There are many temperature sensors not used on the board because they are part of each hashing chip. Speaking on technical things you dont understand just makes you look a bit silly.
They are used.... cpu temp in miner stats is the average of all individual chips on each hasboard.
August 03, 2018, 01:13:07 PM
You know how dumb that is. There are not unused sensors. You think you can just program a sensor and it magically appears on the hashboards this is just funny...
Actually you are the incorrect one here. There are many temperature sensors not used on the board because they are part of each hashing chip. Speaking on technical things you dont understand just makes you look a bit silly.
August 03, 2018, 07:29:26 AM
Could you also add v6b with no check fan?
ready:
https://drive.google.com/open?id=1lLeA3DCAOpyJUBi1zIBe2fslFto7_ckt
But remember that this version is only for immersion cooling!
August 03, 2018, 07:16:24 AM
Could you also add v6b with no check fan?
August 03, 2018, 07:07:02 AM
I left the autotune alone for over 8 hours.
Then I disabled autotune and rebooted the miners. It took less than a minute to get back on.
However, the two pools still appear to be dead. Only ViaBTC pool is alive.
Then I disabled autotune and rebooted the miners. It took less than a minute to get back on.
However, the two pools still appear to be dead. Only ViaBTC pool is alive.
Thanks for testing, a rare error was fixed - the pool was not activated
new version (6b) here:
https://drive.google.com/open?id=1YQavbX5RV7zqco4KKJAqPLmv1-N-CQgr
August 02, 2018, 08:43:51 PM
I left the autotune alone for over 8 hours.
Then I disabled autotune and rebooted the miners. It took less than a minute to get back on.
However, the two pools still appear to be dead. Only ViaBTC pool is alive.
Then I disabled autotune and rebooted the miners. It took less than a minute to get back on.
However, the two pools still appear to be dead. Only ViaBTC pool is alive.
August 02, 2018, 04:36:19 PM
Currently testing the firmware and it seems to do what it's supposed to do after a few PSU trips during autotuning.
However, 2 pools does not seem to get registered and always show as "dead". On default bitmain firmware, they all work fine.
Are you able to figure out what could be the issue?
stratum+tcp://prohashing.com:3333- Dead
stratum+tcp://sha256.hk.nicehash.com:3334- Dead
However, 2 pools does not seem to get registered and always show as "dead". On default bitmain firmware, they all work fine.
Are you able to figure out what could be the issue?
stratum+tcp://prohashing.com:3333- Dead
stratum+tcp://sha256.hk.nicehash.com:3334- Dead
Thank you for testing! To understand what is the matter, specify: 1) did you try to restart, after the completion of auto-tuning 2) how long did it take after rebooting?
I did not check this combination of pools, until it is clear what the problem may be
August 02, 2018, 01:05:30 PM
Currently testing the firmware and it seems to do what it's supposed to do after a few PSU trips during autotuning.
However, 2 pools does not seem to get registered and always show as "dead". On default bitmain firmware, they all work fine.
Are you able to figure out what could be the issue?
stratum+tcp://prohashing.com:3333- Dead
stratum+tcp://sha256.hk.nicehash.com:3334- Dead
However, 2 pools does not seem to get registered and always show as "dead". On default bitmain firmware, they all work fine.
Are you able to figure out what could be the issue?
stratum+tcp://prohashing.com:3333- Dead
stratum+tcp://sha256.hk.nicehash.com:3334- Dead
August 01, 2018, 10:39:56 PM
You realize the GPL license is what requires the blissz firmware for the L3 and D3 to have their thread closed.
This is thread is funny, why are you trolling this guy in his own thread? have you even tried his firmware? I wanna try this firmware just hoping someone else would first... lol
July 31, 2018, 08:41:27 AM
I understand you're just jealous liar, I will not answer you
Goodbye
Goodbye
You realize the GPL license is what requires the blissz firmware for the L3 and D3 to have their thread closed.
Jump to: