Password to be set for the blade but it is password of the PC running the software this?
The password doesn't matter, there just needs to be one. The username is also unimportant, as long as it is unique.
Topic: bfgminer+ asic blade (Read 978 times)
Password to be set for the blade but it is password of the PC running the software this?
The password doesn't matter, there just needs to be one. The username is also unimportant, as long as it is unique.
I havetroublenow very
I'm're struggling to bitcoin to the proxy bfgminer, but it does not work anyway
Communication also seems to be recognized by so doing. But it does not work
PXY 0: | SICK / 0.0 / 0.0 h / s | A: 0 R: 0 +0 (none) HW: 0/none
The stalls in the 60 seconds is displayed.
PXY 0: Idle for more than 60 seconds, declaring SICK!
Password to be set for the blade but it is password of the PC running the software this?
localhost: point to be worried about and look at the 8330 One
While it is displayed on the local host
"error": null, "result": {"target": "ffffffffffffffffffffffffffffffffffffffffffffffffffffffff00000000", "data": "000000025fd91bc1c0cbae1d34b1c3b0192ecc491248e6ed810b0d8100000003000000005f90367 dd8162099385ad8e74c77140abeea504cfb188ac3a6759cea0fd15d0752addee91904ba6e000000 0000000080000000000000000000000000000000000000000000000000000000000000000000000 0000000000080020000", "midstate": "6da4541b30e0f1bccba35e7cdd683555235fb8caa03515eda46f8d79e76723ec", "hash1": "0000000000000000000000000000000000000000000000000000000000000000000000800000000 0000000000000000000000000000000000000000000010000"}, "id": 0}
"error": null, "result": Is this the cause?
I'm're struggling to bitcoin to the proxy bfgminer, but it does not work anyway
Communication also seems to be recognized by so doing. But it does not work
PXY 0: | SICK / 0.0 / 0.0 h / s | A: 0 R: 0 +0 (none) HW: 0/none
The stalls in the 60 seconds is displayed.
PXY 0: Idle for more than 60 seconds, declaring SICK!
Password to be set for the blade but it is password of the PC running the software this?
localhost: point to be worried about and look at the 8330 One
While it is displayed on the local host
"error": null, "result": {"target": "ffffffffffffffffffffffffffffffffffffffffffffffffffffffff00000000", "data": "000000025fd91bc1c0cbae1d34b1c3b0192ecc491248e6ed810b0d8100000003000000005f90367 dd8162099385ad8e74c77140abeea504cfb188ac3a6759cea0fd15d0752addee91904ba6e000000 0000000080000000000000000000000000000000000000000000000000000000000000000000000 0000000000080020000", "midstate": "6da4541b30e0f1bccba35e7cdd683555235fb8caa03515eda46f8d79e76723ec", "hash1": "0000000000000000000000000000000000000000000000000000000000000000000000800000000 0000000000000000000000000000000000000000000010000"}, "id": 0}
"error": null, "result": Is this the cause?
Jump to: