Pages:
Author

Topic: DragonMint T1 16TH/S halongmining.com - page 16. (Read 87857 times)

legendary
Activity: 3822
Merit: 2703
Evil beware: We have waffles!
I wonder why they do this?

Given how Halong has behaved from day-1, to me it's on-par with how they run things. Totally expected.

Kudos for them actually getting product out the door that mostly/does work. Jeers for their support and openness.
legendary
Activity: 4326
Merit: 8899
'The right to privacy matters'
Yet another shitty feature of the T1, locking you out of the OS on something you own. Even bitmain allows this.

I wonder why they do this?
hero member
Activity: 756
Merit: 560
Managing via SSH is not supported, you need to use the API.


Yet another shitty feature of the T1, locking you out of the OS on something you own. Even bitmain allows this.
sr. member
Activity: 261
Merit: 257
Does anyone have information as to when the DragonMint T1 will permit access via SSH?

I use Awesome Miner to manage the miners in my farm. Because no known way exists to access the DragonMint T1 via SSH, I can't apply any triggers/rules to them, which is complicating my maintenance and monitoring.

Patrik Engström of Awesome Miner is willing to add API support for the DragonMint if the vendor will provide the SSH access details. Thank you.

Managing via SSH is not supported, you need to use the API.
jr. member
Activity: 42
Merit: 120
Does anyone have information as to when the DragonMint T1 will permit access via SSH?

I use Awesome Miner to manage the miners in my farm. Because no known way exists to access the DragonMint T1 via SSH, I can't apply any triggers/rules to them, which is complicating my maintenance and monitoring.

Patrik Engström of Awesome Miner is willing to add API support for the DragonMint if the vendor will provide the SSH access details. Thank you.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
re ^^, again, contact MyRig. This is not a Halong Dragonmint issue.
Betcha that the mods move the posts to the MyRig support thread...
I'm sure they would if this fucked up ancient forum provided such a capability to the mods. The new forum which we'll allegedly be getting in 2.5 years ago should fix that.

Pls pm me when u figured out how to get the time machine to go back to 2.5 years ago lol
Indeed if you think the users are frustrated by the delays on the new forum software, it's nothing compared to the pain the mods feel... But we better get back on topic.
full member
Activity: 462
Merit: 118
I'm sure they would if this fucked up ancient forum provided such a capability to the mods. The new forum which we'll allegedly be getting in 2.5 years ago should fix that.

Pls pm me when u figured out how to get the time machine to go back to 2.5 years ago lol
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
re ^^, again, contact MyRig. This is not a Halong Dragonmint issue.
Betcha that the mods move the posts to the MyRig support thread...
I'm sure they would if this fucked up ancient forum provided such a capability to the mods. The new forum which we'll allegedly be getting in 2.5 years ago should fix that.
donator
Activity: 792
Merit: 510
IF PSU was a part of DragonMint purchase and came with Halong's stamp on the commercial invoice, please email [email protected]   
legendary
Activity: 3822
Merit: 2703
Evil beware: We have waffles!
Hi
I have a dead Myrig PSU with 1 week from de purchase, it doesn't power anymore
Replaced with a bitmain psu and my T1 is working OK
Myrig PSUs have warranty?
Of course it has a warranty. Um, perhaps check the MyRig site or email them [email protected] to file a support ticket? Wink
Also, MyRig has an official support thread here you might want to use.
member
Activity: 71
Merit: 17
Hi

I have a dead Myrig PSU with 1 week from de purchase, it doesn't power anymore

Replaced with a bitmain psu and my T1 is working OK

Myrig PSUs have warranty?
jr. member
Activity: 284
Merit: 3
Well common sense would say that one is not quite right then...

I didnt think it was hence the question. Also, this miner is not able to take the latest update. I had to roll back to
t1_20180428_053938
28th of April 2018 05:39 AM in order to get it to run. Suggestions?

Edit. Actually was able to update from firmware above to latest firmware. Just not from original factory firmware. Fan now at 55 after update.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Fan is at 100% on efficiency mode, Boards are running at 70, 72, 76 according to awesome miner. 14TH/s. Is this normal?
It's normal for a very hot environment... I really wouldn't run them at anything but efficient mode mode given that. You won't even be able to tune them at anything higher.
6 other t1's on the same rack, right next to each other fans running at 36-64 same temps.
Well common sense would say that one is not quite right then... Make sure they're on the same firmwares. One had dodgy values.
jr. member
Activity: 284
Merit: 3
It's normal for a very hot environment... I really wouldn't run them at anything but efficient mode mode given that. You won't even be able to tune them at anything higher.

6 other t1's on the same rack, right next to each other fans running at 36-64 same temps.
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
Fan is at 100% on efficiency mode, Boards are running at 70, 72, 76 according to awesome miner. 14TH/s. Is this normal?
It's normal for a very hot environment... I really wouldn't run them at anything but efficient mode mode given that. You won't even be able to tune them at anything higher.
jr. member
Activity: 284
Merit: 3
Fan is at 100% on efficiency mode, Boards are running at 70, 72, 76 according to awesome miner. 14TH/s. Is this normal?
-ck
legendary
Activity: 4088
Merit: 1631
Ruu \o/
(2) more PSUs just failed.
And I have one T1 that just stays in Autotune
Hashing at 12.6TH/s for over 12 hours.
Tried rebooting but just keeps Autotuning.

 Huh Huh Huh
If they are running too hot during autotune it will refuse to complete and the display will wrongly show that autotune is still in process long after startup. What fanspeeds are you hitting in the first half hour of runtime?

Will you please provide a specific range of what qualifies as "running too hot" that will trigger this problem -- or at least what temp range we should aim to be in when we autotune? Thank you....

The driver automatically throttles the device to prevent it overheating so in principle you should NEVER see them overheat now. But once it has throttled it will not complete tuning. If your fan hits 100% for any period, that's when you know it would have otherwise overheated.
newbie
Activity: 5
Merit: 0
192.168.8.129 is a miner and computer is 192.168.8.175 .

My miner works in solo.ckpool.org

A few logs worries me and looking for an explanation:

Code:
May 30 07:09:53 dragonMint cgminer[1329]: hub_cmd_read_result crc error !

Error, cgminer have problem oder my miner? What can I do?

Code:
May 30 07:11:14 dragonMint cgminer[1329]: [48.0K blob data]

is the cgminer file from the difficulty level?

Code:
May 30 10:29:59 dragonMint systemd-journal-gatewayd[1366]: microhttpd: Failed to send data in request for `/entries'.
May 30 10:29:59 dragonMint systemd-journal-gatewayd[1366]: microhttpd: Failed to send data in request for `/entries'.
May 30 10:49:39 dragonMint cgminer[1329]: [47.9K blob data]

Here I understand that I have broken two chips. Can I take them out?

Code:
May 30 06:40:34 dragonMint dm-monitor[1268]: [INFO:2018-05-30 06:40:34.110] b9 pin:957,a10 pin:943
May 30 06:40:34 dragonMint dm-monitor[1268]: [INFO:2018-05-30 06:40:34.110] b9:1,a10:1,val:0x00000003
May 30 06:40:34 dragonMint dm-monitor[1268]: [INFO:2018-05-30 06:40:34.110] b9 pin:957,a10 pin:943
May 30 06:40:34 dragonMint dm-monitor[1268]: [INFO:2018-05-30 06:40:34.110] b9:1,a10:1,val:0x00000003
May 30 06:40:34 dragonMint dm-monitor[1268]: [INFO:2018-05-30 06:40:34.110] cow vid vid
May 30 06:40:34 dragonMint dm-monitor[1268]: [INFO:2018-05-30 06:40:34.110] cow vid vid

Code:
May 30 08:01:10 dragonMint systemd-journal-gatewayd[1366]: microhttpd: Failed to send data in request for `/entries'.

here, please explain why this is happening?

Code:
May 30 10:29:59 dragonMint systemd-journal-gatewayd[1366]: microhttpd: Failed to send data in request for `/entries'.
May 30 10:29:59 dragonMint systemd-journal-gatewayd[1366]: microhttpd: Failed to send data in request for `/entries'.
May 30 10:49:39 dragonMint cgminer[1329]: [47.9K blob data]

Thanks in advance for your help.
jr. member
Activity: 42
Merit: 120
If they are running too hot during autotune it will refuse to complete and the display will wrongly show that autotune is still in process long after startup. What fanspeeds are you hitting in the first half hour of runtime?

Will you please provide a specific range of what qualifies as "running too hot" that will trigger this problem -- or at least what temp range we should aim to be in when we autotune? Thank you....
legendary
Activity: 3234
Merit: 1220
Can anyone thats explain to me?? Miner logs in my T1.:

[...]

Looks like logs of your computer browser looking at the log file on the miner. Not sure what /entries folder does on the interface as I don't have direct access to mine.

Is the IP address of your computer 192.168.8.129? I know you are on a Mac, but you should be able to find it.
Pages:
Jump to: