Pages:
Author

Topic: Official FutureBit Moonlander 2 Driver and Support Thread - page 32. (Read 71717 times)

newbie
Activity: 8
Merit: 0
Hi. I have downloaded the software specific to the miner and it run fine on a Debian machine. Then i moved the miner to another machine that has Gentoo and bfgminer ran fine for like a day or two and then does segmentation fault. It has happened very consistently so i ran it through dbg to get log. I don't know if there is another place where i can put this or if there is other way to get more debugging info.
Code:
Starting program: /home/user/bfgminer_5.4.2-futurebit2_linux_x86_64/bfgminer --scrypt -o stratum+tcp://hub.miningpoolhub.com:20523/\#skipcbcheck -u userName.minerName -p p -d 128 -S ALL --set MLD:clock=796
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7ffff4ae2700 (LWP 2349)]
[New Thread 0x7ffff42e1700 (LWP 2350)]
[New Thread 0x7ffff3ae0700 (LWP 2351)]
[Thread 0x7ffff42e1700 (LWP 2350) exited]
[New Thread 0x7ffff32df700 (LWP 2352)]
[Thread 0x7ffff3ae0700 (LWP 2351) exited]
[New Thread 0x7ffff2ade700 (LWP 2353)]
[Thread 0x7ffff32df700 (LWP 2352) exited]
[New Thread 0x7ffff22dd700 (LWP 2354)]
[Thread 0x7ffff2ade700 (LWP 2353) exited]
[New Thread 0x7ffff1adc700 (LWP 2355)]
[Thread 0x7ffff22dd700 (LWP 2354) exited]
[New Thread 0x7ffff12db700 (LWP 2356)]
[Thread 0x7ffff1adc700 (LWP 2355) exited]
[New Thread 0x7ffff0ada700 (LWP 2357)]
[Thread 0x7ffff12db700 (LWP 2356) exited]
[Thread 0x7ffff0ada700 (LWP 2357) exited]
[New Thread 0x7ffff0ada700 (LWP 2360)]
[New Thread 0x7ffff12db700 (LWP 2361)]
[Thread 0x7ffff12db700 (LWP 2361) exited]
[New Thread 0x7ffff12db700 (LWP 2362)]
[Thread 0x7ffff0ada700 (LWP 2360) exited]
[New Thread 0x7ffff1adc700 (LWP 2364)]
[New Thread 0x7ffff22dd700 (LWP 2365)]
[New Thread 0x7ffff3cb8700 (LWP 2366)]
[New Thread 0x7ffff34b7700 (LWP 2367)]
[New Thread 0x7ffff2cb6700 (LWP 2368)]
[New Thread 0x7fffe3fff700 (LWP 2369)]
[Thread 0x7ffff2cb6700 (LWP 2368) exited]
[New Thread 0x7ffff2cb6700 (LWP 2370)]
[New Thread 0x7fffe37fe700 (LWP 9331)]
[Thread 0x7fffe37fe700 (LWP 9331) exited]

Thread 13 "stratum0" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff12db700 (LWP 2362)]
0x00007ffff757ddc0 in ?? () from /usr/lib64/libcurl-gnutls.so.4
#0  0x00007ffff757ddc0 in ?? () from /usr/lib64/libcurl-gnutls.so.4
#1  0x00007ffff757319c in curl_easy_recv () from /usr/lib64/libcurl-gnutls.so.4
#2  0x0000000000437acb in clear_sock (pool=pool@entry=0x6971e0) at util.c:1837
#3  0x000000000043c7c0 in recv_line (pool=pool@entry=0x6971e0) at util.c:1937
#4  0x000000000042ce13 in stratum_thread (userdata=0x6971e0) at miner.c:9657
#5  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#6  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 20 (Thread 0x7ffff2cb6700 (LWP 2370)):
#0  0x00007ffff711facd in read () from /lib64/libpthread.so.0
#1  0x00007ffff6eecaaf in _nc_wgetch () from /usr/lib64/libncurses.so.5
#2  0x00007ffff6eed426 in wgetch () from /usr/lib64/libncurses.so.5
#3  0x00000000004117f3 in __real_getch () at ./miner.h:206
#4  my_cancellable_getch () at miner.c:3787
#5  0x00000000004328f5 in input_thread (userdata=) at miner.c:8895
#6  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#7  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 19 (Thread 0x7fffe3fff700 (LWP 2369)):
#0  0x00007ffff64cd2a3 in epoll_wait () from /lib64/libc.so.6
#1  0x00000000004172f9 in hotplug_thread (p=) at miner.c:13087
#2  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#3  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 17 (Thread 0x7ffff34b7700 (LWP 2367)):
#0  0x00007ffff6497c6d in nanosleep () from /lib64/libc.so.6
#1  0x00007ffff6497baa in sleep () from /lib64/libc.so.6
#2  0x0000000000422bb2 in watchdog_thread (userdata=) at miner.c:11609
#3  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#4  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 16 (Thread 0x7ffff3cb8700 (LWP 2366)):
#0  0x00007ffff712019d in nanosleep () from /lib64/libpthread.so.0
#1  0x0000000000435f75 in _cgsleep_us_r_nanosleep (tv_start=, us=) at util.c:1474
#2  0x0000000000439cf3 in cgsleep_ms_r (ms=30000, tv_start=0x7ffff3cb6ea0) at util.c:1457
#3  cgsleep_ms (ms=ms@entry=30000) at util.c:1483
#4  0x000000000042b8c5 in watchpool_thread (userdata=) at miner.c:11461
#5  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#6  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 15 (Thread 0x7ffff22dd700 (LWP 2365)):
#0  0x00007ffff64c3f63 in select () from /lib64/libc.so.6
#1  0x000000000042780a in submit_work_thread (userdata=) at miner.c:6976
#2  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#3  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 14 (Thread 0x7ffff1adc700 (LWP 2364)):
#0  0x00007ffff711facd in read () from /lib64/libpthread.so.0
#1  0x0000000000451d8c in read (__nbytes=8, __buf=0x7ffff1ad9dd0, __fd=13) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  _serial_read (fd=fd@entry=13, buf=buf@entry=0x7ffff1ad9dd0 "<\020\377\032\t'V\024`\f", bufsiz=bufsiz@entry=8,
    eol=eol@entry=0x0) at lowl-vcom.c:1239
#3  0x0000000000455042 in futurebit_scanhash (thr=0x6bbc10, work=0x6bb330, max_nonce=) at driver-futurebit.c:650
#4  0x0000000000433d3f in minerloop_scanhash (mythr=0x6bbc10) at deviceapi.c:274
#5  0x0000000000434eb2 in miner_thread (userdata=0x6bbc10) at deviceapi.c:772
#6  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#7  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 13 (Thread 0x7ffff12db700 (LWP 2362)):
#0  0x00007ffff757ddc0 in ?? () from /usr/lib64/libcurl-gnutls.so.4
#1  0x00007ffff757319c in curl_easy_recv () from /usr/lib64/libcurl-gnutls.so.4
#2  0x0000000000437acb in clear_sock (pool=pool@entry=0x6971e0) at util.c:1837
#3  0x000000000043c7c0 in recv_line (pool=pool@entry=0x6971e0) at util.c:1937
#4  0x000000000042ce13 in stratum_thread (userdata=0x6971e0) at miner.c:9657
#5  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#6  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7ffff4ae2700 (LWP 2349)):
#0  0x00007ffff64c18fd in poll () from /lib64/libc.so.6
#1  0x00007ffff7fb5fc1 in ?? () from /lib64/libusb-1.0.so.0
#2  0x00007ffff71148f7 in start_thread () from /lib64/libpthread.so.0
#3  0x00007ffff64ccc7f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7ffff7f9ab40 (LWP 2345)):
#0  0x00007ffff711b7f6 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x0000000000408a4e in main (argc=1, argv=) at miner.c:13859

newbie
Activity: 38
Merit: 0
I have 4 of them, which no longer work thanks to the windows upgrade. I can get 1 with the 6.75 driver to work, but the rest have conflicts with COM ports on that version. Did anyone figure out a work-around yet for multiple Moonlanders?
legendary
Activity: 2174
Merit: 1401
I just installed the Windows 10 update 1803 and after install the Moonlander2 drivers did not work.
In device manager it listed the Moonlanders but had a triangle.
BFGMiner when run says "No devices found".
I tried reinstalling them, removing them and reinstalling but to no avail. The driver Preinstaller program fails with an error.
When I try to manually install the drivers, the error says INF file invalid.

I downloaded the v6.7.5 version from the driver page and they worked!
In device manager under COM ports it no longer lists them as Moonlander2 and instead lists them as Silicon Labs CP210x USB to UART Bridge (COMx).
BFGimner now sees them Smiley

Just a tip should you run into this.

Bob


Sounds like some driver signing issue with the new windows release. Im sure silicon labs will sort it out.
newbie
Activity: 44
Merit: 0
I just installed the Windows 10 update 1803 and after install the Moonlander2 drivers did not work.
In device manager it listed the Moonlanders but had a triangle.
BFGMiner when run says "No devices found".
I tried reinstalling them, removing them and reinstalling but to no avail. The driver Preinstaller program fails with an error.
When I try to manually install the drivers, the error says INF file invalid.

I downloaded the v6.7.5 version from the driver page and they worked!
In device manager under COM ports it no longer lists them as Moonlander2 and instead lists them as Silicon Labs CP210x USB to UART Bridge (COMx).
BFGimner now sees them Smiley

Just a tip should you run into this.

Bob
newbie
Activity: 88
Merit: 0
I'm looking to update my raspberry pi from 5.4.2-34 to 5.4.2-38 for the auto restart. Has the GitHub armv6 download link been updated to the newest version? It still installs ver. 5.4.2-34.

thanks!


Maybe that's why bfgminer on my pi will not auto restart. My bfgminer comes up with 5.4.2-34, not 5.4.2-38 when following the instructions from page 1

hmmm, the beta 2 link for armv6 shows build 34? Ill check it and update it. Ill be building new version with latest updates soon anyway.

Any idea when the armv6 build might be updated? I have to restart my pi and moonlander about once a day do to internet dropouts.
legendary
Activity: 2174
Merit: 1401
I have a fried Moonlander 2. This one was working perfectly on one of my computers for weeks,  and I moved it to another computer that was in a more favorable location. Set up the computer the same way, Windows 7, standard software (bfgminer, etc). However, when I plugged it in, and the fan worked fine, and then I smelled the familiar smell of smoked electronic components. Looks like U2 on the board is fried with a black smoldered hole  in the middle of it.

What is the component? What could have caused this? Is this ML2 repairable, or is it a lost cause? My other 2 ML2's are working great, but am scared to move them in the event this same thing happens.

Any guidance would be great.

Thanks!


Hmm thats not good. U2 is the memory voltage controller. Sounds like something shorted or overheated. Were you running higher clocks? If only the controller blew the repair would be relatively easy and its a 50 cent component if your good with removing/soldering SMDs. If your in the US and don't mind sending it in shoot me a PM...catastrophic failures like this are super rare so they are good dissecting cases.

No, I was running straight defaults at 600 clock speed on litecoinpool.org with 128 difficulty. I am in the US, and will send you a PM. Thanks!



Is there something wroung with the USB port on your computer?

No, I have been running two other miners and no problem with that port. Only thing I can think of is that a surge took it out.  Are there any other components before the voltage controller from the initial usb connection on that circuit? Jstefanop, I sent you a PM a couple of days ago, but I am not sure if you got it. Thanks!

Sent you a PM.
newbie
Activity: 19
Merit: 0
I have a fried Moonlander 2. This one was working perfectly on one of my computers for weeks,  and I moved it to another computer that was in a more favorable location. Set up the computer the same way, Windows 7, standard software (bfgminer, etc). However, when I plugged it in, and the fan worked fine, and then I smelled the familiar smell of smoked electronic components. Looks like U2 on the board is fried with a black smoldered hole  in the middle of it.

What is the component? What could have caused this? Is this ML2 repairable, or is it a lost cause? My other 2 ML2's are working great, but am scared to move them in the event this same thing happens.

Any guidance would be great.

Thanks!


Hmm thats not good. U2 is the memory voltage controller. Sounds like something shorted or overheated. Were you running higher clocks? If only the controller blew the repair would be relatively easy and its a 50 cent component if your good with removing/soldering SMDs. If your in the US and don't mind sending it in shoot me a PM...catastrophic failures like this are super rare so they are good dissecting cases.

No, I was running straight defaults at 600 clock speed on litecoinpool.org with 128 difficulty. I am in the US, and will send you a PM. Thanks!



Is there something wroung with the USB port on your computer?

No, I have been running two other miners and no problem with that port. Only thing I can think of is that a surge took it out.  Are there any other components before the voltage controller from the initial usb connection on that circuit? Jstefanop, I sent you a PM a couple of days ago, but I am not sure if you got it. Thanks!
newbie
Activity: 88
Merit: 0
I'm looking to update my raspberry pi from 5.4.2-34 to 5.4.2-38 for the auto restart. Has the GitHub armv6 download link been updated to the newest version? It still installs ver. 5.4.2-34.

thanks!


Maybe that's why bfgminer on my pi will not auto restart. My bfgminer comes up with 5.4.2-34, not 5.4.2-38 when following the instructions from page 1

hmmm, the beta 2 link for armv6 shows build 34? Ill check it and update it. Ill be building new version with latest updates soon anyway.

Thanks for looking into this. And just an FYI the instructions for the Pi install on page one still links to the old build.
legendary
Activity: 2174
Merit: 1401
I'm looking to update my raspberry pi from 5.4.2-34 to 5.4.2-38 for the auto restart. Has the GitHub armv6 download link been updated to the newest version? It still installs ver. 5.4.2-34.

thanks!


Maybe that's why bfgminer on my pi will not auto restart. My bfgminer comes up with 5.4.2-34, not 5.4.2-38 when following the instructions from page 1

hmmm, the beta 2 link for armv6 shows build 34? Ill check it and update it. Ill be building new version with latest updates soon anyway.
newbie
Activity: 88
Merit: 0
I'm looking to update my raspberry pi from 5.4.2-34 to 5.4.2-38 for the auto restart. Has the GitHub armv6 download link been updated to the newest version? It still installs ver. 5.4.2-34.

thanks!


Maybe that's why bfgminer on my pi will not auto restart. My bfgminer comes up with 5.4.2-34, not 5.4.2-38 when following the instructions from page 1
newbie
Activity: 88
Merit: 0
...

Nice looking setup. Personally, I would only run 5 off that hub so you can run them full speed. If you only have on one hub then you could plug you Pi and extra fans into the hub too because they don't need that much power.  Have you tried to get bfgminer to run at startup? I am new to pi and Linux in general and have not been able to get it to work.

Nah I dont really need to been using pi's for years and they seldom crash, I use ssh and tmux to control it. that theres my trusty old pi2 with a broken hdmi out  Grin

I'm sure you know what ssh is tmux may be a mystery to you it allows you to run a program through ssh and it'll keep running even after you disconnect. its similair to screen but a bit more advanced/configurable

Yes, I tried screen but it was not getting me anywhere. Besides I just want it to autostart every time the pi boots up.

make sure screen is installed (sudo apt install screen)

create a file in your home directory with nano like this:

Code:
nano startup.sh

inside this file put something like this

Code:
cd /home/YOUR_PI_ACCOUNT_NAME/YOUR_BFGMINER_FOLDER_NAME
screen -dmS miner bash -c './start_moonlander.sh; exec bash'

then turn startup script to executible

Code:
sudo chmod +x startup.sh

and add this to crontab

Code:
sudo crontab -e

go down after all the ## and add this line

Code:
@reboot /home/YOUR_PI_ACCOUNT_NAME/startup.sh

then

Code:
sudo reboot

once rebooted just do

Code:
sudo screen -dr

and you should see bfgminer running. Press control then A then D at the same time to exit screen without terminating process.

That should do it  Wink

Thanks for your time putting these instructions together. I finally had a chance to try it last night and the miner starts every time I power up the pi. One last question, is there a way to automate the last step (sudo screen -dr) so the terminal with bfgminer comes up on the connected HDMI screen every time?
newbie
Activity: 88
Merit: 0
I have a fried Moonlander 2. This one was working perfectly on one of my computers for weeks,  and I moved it to another computer that was in a more favorable location. Set up the computer the same way, Windows 7, standard software (bfgminer, etc). However, when I plugged it in, and the fan worked fine, and then I smelled the familiar smell of smoked electronic components. Looks like U2 on the board is fried with a black smoldered hole  in the middle of it.

What is the component? What could have caused this? Is this ML2 repairable, or is it a lost cause? My other 2 ML2's are working great, but am scared to move them in the event this same thing happens.

Any guidance would be great.

Thanks!


Hmm thats not good. U2 is the memory voltage controller. Sounds like something shorted or overheated. Were you running higher clocks? If only the controller blew the repair would be relatively easy and its a 50 cent component if your good with removing/soldering SMDs. If your in the US and don't mind sending it in shoot me a PM...catastrophic failures like this are super rare so they are good dissecting cases.

No, I was running straight defaults at 600 clock speed on litecoinpool.org with 128 difficulty. I am in the US, and will send you a PM. Thanks!



Is there something wroung with the USB port on your computer?
newbie
Activity: 19
Merit: 0
I have a fried Moonlander 2. This one was working perfectly on one of my computers for weeks,  and I moved it to another computer that was in a more favorable location. Set up the computer the same way, Windows 7, standard software (bfgminer, etc). However, when I plugged it in, and the fan worked fine, and then I smelled the familiar smell of smoked electronic components. Looks like U2 on the board is fried with a black smoldered hole  in the middle of it.

What is the component? What could have caused this? Is this ML2 repairable, or is it a lost cause? My other 2 ML2's are working great, but am scared to move them in the event this same thing happens.

Any guidance would be great.

Thanks!


Hmm thats not good. U2 is the memory voltage controller. Sounds like something shorted or overheated. Were you running higher clocks? If only the controller blew the repair would be relatively easy and its a 50 cent component if your good with removing/soldering SMDs. If your in the US and don't mind sending it in shoot me a PM...catastrophic failures like this are super rare so they are good dissecting cases.

No, I was running straight defaults at 600 clock speed on litecoinpool.org with 128 difficulty. I am in the US, and will send you a PM. Thanks!

legendary
Activity: 2174
Merit: 1401
I have a fried Moonlander 2. This one was working perfectly on one of my computers for weeks,  and I moved it to another computer that was in a more favorable location. Set up the computer the same way, Windows 7, standard software (bfgminer, etc). However, when I plugged it in, and the fan worked fine, and then I smelled the familiar smell of smoked electronic components. Looks like U2 on the board is fried with a black smoldered hole  in the middle of it.

What is the component? What could have caused this? Is this ML2 repairable, or is it a lost cause? My other 2 ML2's are working great, but am scared to move them in the event this same thing happens.

Any guidance would be great.

Thanks!


Hmm thats not good. U2 is the memory voltage controller. Sounds like something shorted or overheated. Were you running higher clocks? If only the controller blew the repair would be relatively easy and its a 50 cent component if your good with removing/soldering SMDs. If your in the US and don't mind sending it in shoot me a PM...catastrophic failures like this are super rare so they are good dissecting cases.
legendary
Activity: 2174
Merit: 1401
Code:
bfgminer.exe --scrypt -o stratum+tcp://eu.multipool.us:3351 -u Moonlander2.1 -p x,d=256  -S MLD:all --set MLD:clock=796
pause

Ok so i have it running on litecoinpool and on multipool. Works but i run into the same error. After a while it just stops hashing. If i restart bfg then it works like a champ again.
So can someone help me. Is there a way to set bfgminer up to auto restart after an hour. yea I know its not perfect but at this point i just want the dang thing to run nearly 24 hours. I hate waking up to find it pooped out after 30 minutes and sat idle 6 hours. Is there a way to add a piece to this scrypt that will make it auto restart after an hour? Since I have no clue why it keeps stopping. And before we trouble shoot again just assume its all running on the right stuff. yes powered hub. yes 100mbps connection which is stable. Yes way more than adequate cooling. This thing will run 30 minutes and stop or 32 hours and stop. No rhyme or reason i see. If there is a code to auto restart after an hour that would be gold.  Any help?

Any ideas?

This depends on whats going on with your setup. First are you running the latest bfgminer binaries I release that have auto-restart built into the miner? Sounds like your not since restarting bfgminer pretty much does what I already do in the new driver release automatically.

i have 5.4.2. isnt that the newest one? i see no restart timer


You should see 5.4.2-38 at the top if your running the latest version.
newbie
Activity: 19
Merit: 0
I have a fried Moonlander 2. This one was working perfectly on one of my computers for weeks,  and I moved it to another computer that was in a more favorable location. Set up the computer the same way, Windows 7, standard software (bfgminer, etc). However, when I plugged it in, and the fan worked fine, and then I smelled the familiar smell of smoked electronic components. Looks like U2 on the board is fried with a black smoldered hole  in the middle of it.

What is the component? What could have caused this? Is this ML2 repairable, or is it a lost cause? My other 2 ML2's are working great, but am scared to move them in the event this same thing happens.

Any guidance would be great.

Thanks!
newbie
Activity: 42
Merit: 0
Code:
bfgminer.exe --scrypt -o stratum+tcp://eu.multipool.us:3351 -u Moonlander2.1 -p x,d=256  -S MLD:all --set MLD:clock=796
pause

Ok so i have it running on litecoinpool and on multipool. Works but i run into the same error. After a while it just stops hashing. If i restart bfg then it works like a champ again.
So can someone help me. Is there a way to set bfgminer up to auto restart after an hour. yea I know its not perfect but at this point i just want the dang thing to run nearly 24 hours. I hate waking up to find it pooped out after 30 minutes and sat idle 6 hours. Is there a way to add a piece to this scrypt that will make it auto restart after an hour? Since I have no clue why it keeps stopping. And before we trouble shoot again just assume its all running on the right stuff. yes powered hub. yes 100mbps connection which is stable. Yes way more than adequate cooling. This thing will run 30 minutes and stop or 32 hours and stop. No rhyme or reason i see. If there is a code to auto restart after an hour that would be gold.  Any help?

Any ideas?

Have you tried lowering the frequency to 6xx to see if it runs better? Do you have tools to check how many volts, amps, and watts are being used? Do you have a heat gun to measure temp on the ASIC?

In Windows, you could forcefully kill the bfgminer using a free tool called pskill:
https://docs.microsoft.com/en-us/sysinternals/downloads/pskill

https://ss64.com/nt/timeout.html

You can use a batch file where you loop bfgminer on, wait 1 hr, bfgminer kill

So, something like this:

bfgminer_restart.bat -- the first line should launch bfgminer.exe in its own window, second line waits one hour, third line kills bfgminer, fourth line restarts the loop

Code:
:top
START /b CMD /c "bfgminer.exe --scrypt -o stratum+tcp://eu.multipool.us:3351 -u Moonlander2.1 -p x,d=256  -S MLD:all --set MLD:clock=796"
timeout 3600
pskill bfgminer.exe
goto top


Wow got that pskill thing on and used your scrypt. Working like a champ. If it restarts you rock so much. Thanks. Ill post back if this solved my issue. I have the current miner running as well.
newbie
Activity: 42
Merit: 0
Code:
bfgminer.exe --scrypt -o stratum+tcp://eu.multipool.us:3351 -u Moonlander2.1 -p x,d=256  -S MLD:all --set MLD:clock=796
pause

Ok so i have it running on litecoinpool and on multipool. Works but i run into the same error. After a while it just stops hashing. If i restart bfg then it works like a champ again.
So can someone help me. Is there a way to set bfgminer up to auto restart after an hour. yea I know its not perfect but at this point i just want the dang thing to run nearly 24 hours. I hate waking up to find it pooped out after 30 minutes and sat idle 6 hours. Is there a way to add a piece to this scrypt that will make it auto restart after an hour? Since I have no clue why it keeps stopping. And before we trouble shoot again just assume its all running on the right stuff. yes powered hub. yes 100mbps connection which is stable. Yes way more than adequate cooling. This thing will run 30 minutes and stop or 32 hours and stop. No rhyme or reason i see. If there is a code to auto restart after an hour that would be gold.  Any help?

Any ideas?

This depends on whats going on with your setup. First are you running the latest bfgminer binaries I release that have auto-restart built into the miner? Sounds like your not since restarting bfgminer pretty much does what I already do in the new driver release automatically.

i have 5.4.2. isnt that the newest one? i see no restart timer
newbie
Activity: 6
Merit: 0
Hello,

I don't know if I'm being stupid here but I've had this moonlander2 working on my old PC, I've now changed PC and come to set it up the exact same again and i get the following as a message?

Anyone have any ideas?

I've read through all the errors other have had, I've reinstalled the driver and also downloaded the latest version of BFG and still the same issues. I'm baffled.

https://preview.ibb.co/dWRzbx/error.png
newbie
Activity: 42
Merit: 0
Code:
bfgminer.exe --scrypt -o stratum+tcp://eu.multipool.us:3351 -u Moonlander2.1 -p x,d=256  -S MLD:all --set MLD:clock=796
pause

Ok so i have it running on litecoinpool and on multipool. Works but i run into the same error. After a while it just stops hashing. If i restart bfg then it works like a champ again.
So can someone help me. Is there a way to set bfgminer up to auto restart after an hour. yea I know its not perfect but at this point i just want the dang thing to run nearly 24 hours. I hate waking up to find it pooped out after 30 minutes and sat idle 6 hours. Is there a way to add a piece to this scrypt that will make it auto restart after an hour? Since I have no clue why it keeps stopping. And before we trouble shoot again just assume its all running on the right stuff. yes powered hub. yes 100mbps connection which is stable. Yes way more than adequate cooling. This thing will run 30 minutes and stop or 32 hours and stop. No rhyme or reason i see. If there is a code to auto restart after an hour that would be gold.  Any help?

Any ideas?

Have you tried lowering the frequency to 6xx to see if it runs better? Do you have tools to check how many volts, amps, and watts are being used? Do you have a heat gun to measure temp on the ASIC?

In Windows, you could forcefully kill the bfgminer using a free tool called pskill:
https://docs.microsoft.com/en-us/sysinternals/downloads/pskill

https://ss64.com/nt/timeout.html

You can use a batch file where you loop bfgminer on, wait 1 hr, bfgminer kill

So, something like this:

bfgminer_restart.bat -- the first line should launch bfgminer.exe in its own window, second line waits one hour, third line kills bfgminer, fourth line restarts the loop

Code:
:top
START /b CMD /c "bfgminer.exe --scrypt -o stratum+tcp://eu.multipool.us:3351 -u Moonlander2.1 -p x,d=256  -S MLD:all --set MLD:clock=796"
timeout 3600
pskill bfgminer.exe
goto top



I'll try updating as jstefanop says. If that doesn't work I'll try your method. The USB miner is still stock. Never messed with anything. Only removed the bad fan.
Pages:
Jump to: