I too would like to have some input from XMRPool.net

the website is flaky and rarely has any information displayed, as if the API is not working.

I have no real problem with having zero information, and the servers seem be working most of the time.

but it would be nice to have SOME sort of communication from the people I'm paying "dev" fees

Did you ever get this figured out?
The 2019 firmware disables SSH, which means you are locked to using only BITMAIN firmware.

BUT

I just finished downgrading from the 2019 firmware.

I had to do a "Control Board Program Recovery"

The way listed on the BITMAIN site gave me problems though; I was not able to login using the default username/password

If you run into the same problem with logging in you have to modify the Control board recovery.

 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

1. Download the old firmware from here ( https://github.com/jeffpcyo/asic-firmware/tree/master/Bitmain/Antminer/L3%2B) (This is just the first place i found the 2017 firmware)


2. Download the "L3+、D3、A3-SD Tools.zip" from here ( https://service.bitmain.com/support/download?product=Flashing%20SD%20card%20with%20image ) (BITMAIN's support site)


3. Extract "Antminer-L3+-201708251737-384M.tar.gz" to somewhere (so you can get at the Antminer-L3+-201708251737-384M.tar inside)


4. Extract "Antminer-L3+-201708251737-384M.tar" to somewhere


5. Extract "L3+、D3、A3-SD Tools.zip" to somewhere ( I use 7zip, just right-clicked and extracted each of these to a folder with their name)


now that you have all the files ready you can proceed:

(From BITMAIN's Control Board Recovery page)
3. Insert the Micro SD card into the card reader and connect to the computer.

4. Format the Micro SD card to FAT32

5. Copy the extracted file to the Micro SD card (Extracted from "L3+、D3、A3-SD Tools.zip")


RIGKING's FIXY-fixxer-son

6. Copy the files extracted from "Antminer-L3+-201708251737-384M.tar" to the SD card - Overwriting when prompted



Now continue following the directions from BITMAIN's support

6. Insert the Micro SD card into the control board

7. Power on the miner

8. Remove the Micro SD card after the miner gets its IP address


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -


From this point, I was able to use the default credentials to log in, and flash the correct firmware

forager is currently mining

Group  Algorithm   Coin        Miner                   LocalSpeed Acc/Rej PLim Watt USD/W mBTC/Day USD/Day Profit/Day PoolSpeed Workers Pool
-----  ---------   ----        -----                   ---------- ------- ---- ---- ----- -------- ------- ---------- --------- ------- ----
AMD    Equihash144 Equihash144 A-lolMiner-0.9.3                       1/0                  0.00000    0.00       0.00   219.9 h      55 Zpool-US
NVIDIA NeoScrypt   NeoScrypt   N-CryptoDredge-0.22       2.006 mh    29/0                  0.06292    0.63       0.62  458.1 kh     251 Zpool-US
CPU    Power2b|t4  Power2b     C-CpuMinerRplant-4.0.29    666.5 h    57/0                  0.01231    0.12       0.12  1.129 kh      51 Zpool-US

but when LOLminer starts, it is running on device 0, e.g. GPU0 is submitting all the shares, which is my 1080ti

if I change the LOLminer .json from  "--devices #Devices#", to  "--devices 1",

how is that going to screw me over later??


Setup Miner...
 Device 0:
    Name:    GeForce GTX 1080 Ti
    Address: 7:0
    Vendor:  NVIDIA Corporation
    Memory:  11264 MByte
    Active:  true (Selected Algorithm: Equihash 144/5 Nvidia)
 Device 1:
    Name:    Radeon RX 570 Series
    Address: 10:0
    Vendor:  Advanced Micro Devices (AMD)
    Memory:  8192 MByte (8142 MByte free)
    Active:  false (not selected)

Connecting to pool...
Connected to equihash144.na.mine.zpool.ca:2144 (TLS disabled)
Subscribed to stratum server
Authorized worker: ( - BTC WAOLLET - )
New target received: 00ffff0000000000
New job received: 15ea (sngemPoW)
Start Mining...
GPU 0: Share accepted (33 ms)

=====================================================================================

I think I found the solution

removed @devices tag from N- and A- .json, and put in the correct device number for this rig                             !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

===================================================================================