here is a JSON example config file for bfgminer V5.4.2 for the futurebit moonlander 2
i hope it useful for someone
{
"pools" : [
{
"url" : "your-first-miningpool",
"user" : "your_username" ,
"pass" : "your_password"
},
{
"url" : "your-second-miningpool",
"user" : "your_username",
"pass" : "your_password"
},
{
"url" : "your-third-miningpool",
"user" : "your_username",
"pass" : "your_password"
}
]
,
"api-listen" : true,
"api-mcast-port" : "4028",
"api-network" : true,
"api-port" : "4028",
"expiry" : "120",
"failover-only" : true,
"hotplug" : "17",
"log" : "5",
"no-pool-disable" : true,
"queue" : "4",
"scan-time" : "60",
"scrypt" : true,
"shares" : "0",
"api-allow" : "W:127.0.0.1, R:192.168.1,0/24",
"scan" : "MLD:all",
"set" : "MLD:clock=600,baud=23040,chips=1,usefifo=0,thread-concurrency=50000,lookup-gap=0,gpu-threads=1"
}
starting the BFGminer with
./bfgminer --config ./bfgminer.conf
@jstefanop
Φίλε Γιάννη, πoλύ καλή δoυλειά έκανες!
Topic: Official FutureBit Moonlander 2 Driver and Support Thread - page 12. (Read 71430 times)
First Time poster.
Just got my first moonlander 2 to mess around with and have run into a problem I can't seem to get around
Failed to sanity check in lowl-vcom.c windows_usb_get_string():508 is the error that keeps popping up.
any thoughts?
Just got my first moonlander 2 to mess around with and have run into a problem I can't seem to get around
Failed to sanity check in lowl-vcom.c windows_usb_get_string():508 is the error that keeps popping up.
any thoughts?
Sounds like some windows/usb driver incompatibility...what version of windows are you running, and are you using the latest silicon labs USB driver?
I am running windows ten and have reloaded the drivers. I actually had it working for about a day or so but then it started happening again. Any thoughts?
sorry to say but ive had so many issues with mine..
windows 10 is not happy with the way they communicate through usb.
just get a cheap raspberry pi and use that with minera.. then have it reboot every few hours and they restart automatically..
Gotcha, no real experience with raspberry pi. Can you point me in a direction for research/purchase advice, thanks for the help.
mine is a really old one, but you can get the whole kit on amazon for pretty cheap.
i know they sell them at frys, and maybe microcenter.
First Time poster.
Just got my first moonlander 2 to mess around with and have run into a problem I can't seem to get around
Failed to sanity check in lowl-vcom.c windows_usb_get_string():508 is the error that keeps popping up.
any thoughts?
Just got my first moonlander 2 to mess around with and have run into a problem I can't seem to get around
Failed to sanity check in lowl-vcom.c windows_usb_get_string():508 is the error that keeps popping up.
any thoughts?
Sounds like some windows/usb driver incompatibility...what version of windows are you running, and are you using the latest silicon labs USB driver?
I am running windows ten and have reloaded the drivers. I actually had it working for about a day or so but then it started happening again. Any thoughts?
sorry to say but ive had so many issues with mine..
windows 10 is not happy with the way they communicate through usb.
just get a cheap raspberry pi and use that with minera.. then have it reboot every few hours and they restart automatically..
Gotcha, no real experience with raspberry pi. Can you point me in a direction for research/purchase advice, thanks for the help.
First Time poster.
Just got my first moonlander 2 to mess around with and have run into a problem I can't seem to get around
Failed to sanity check in lowl-vcom.c windows_usb_get_string():508 is the error that keeps popping up.
any thoughts?
Just got my first moonlander 2 to mess around with and have run into a problem I can't seem to get around
Failed to sanity check in lowl-vcom.c windows_usb_get_string():508 is the error that keeps popping up.
any thoughts?
Sounds like some windows/usb driver incompatibility...what version of windows are you running, and are you using the latest silicon labs USB driver?
I am running windows ten and have reloaded the drivers. I actually had it working for about a day or so but then it started happening again. Any thoughts?
sorry to say but ive had so many issues with mine..
windows 10 is not happy with the way they communicate through usb.
just get a cheap raspberry pi and use that with minera.. then have it reboot every few hours and they restart automatically..
First Time poster.
Just got my first moonlander 2 to mess around with and have run into a problem I can't seem to get around
Failed to sanity check in lowl-vcom.c windows_usb_get_string():508 is the error that keeps popping up.
any thoughts?
Just got my first moonlander 2 to mess around with and have run into a problem I can't seem to get around
Failed to sanity check in lowl-vcom.c windows_usb_get_string():508 is the error that keeps popping up.
any thoughts?
Sounds like some windows/usb driver incompatibility...what version of windows are you running, and are you using the latest silicon labs USB driver?
I am running windows ten and have reloaded the drivers. I actually had it working for about a day or so but then it started happening again. Any thoughts?
Any fixes for the:
Haven't seen any responses. Just curious as now I have both miners just collecting dust, removed them completely out of my rig. As it's getting segmentation faults on every pool. Ran both on a Ubuntu and raspberry pi systems. It's been running flawlessly for months 24/7 on my raspberry Pi until just recently. Not sure why they are failing now unless this is a problem with the moon lander itself?
Have you run any updates on the Pi?Code:
[2019-10-31 11:11:59] Started bfgminer 5.4.2-38-g106390aSegmentation fault
Haven't seen any responses. Just curious as now I have both miners just collecting dust, removed them completely out of my rig. As it's getting segmentation faults on every pool. Ran both on a Ubuntu and raspberry pi systems. It's been running flawlessly for months 24/7 on my raspberry Pi until just recently. Not sure why they are failing now unless this is a problem with the moon lander itself?
You might want to delete bfgminer and rebuild. From some minor research it looks like segmentation faults are often from build issues, though sometimes it is from missing dependencies on the OS. So I would try an update and reboot first and if that fails start from scratch. If you used the download from Futurebit I might redownload and unzip it to a different location.
Otherwise I have no clue...
Thanks I'll try rebuilding it. Haven't done any updates to that unit since everything has been working. I also run several Newpacs and R606's also on the same pi 4. I'll rebuild it into a new directory and see if that resolves the issue. I have another Pi 4 that's currently not being used, may give it a try on it as well. Just to rule out if something is a bit off on the rig it's currently running or not.
Thanks for the assist
I use MiningRigRentals (MRR) to sell my hashing power when I'm not actively experimenting/using it, but I keep getting segmentation faults when MRR points to a new pool while the MLD is mining.
As a temporary fix to this, I made a bash script so that it'll restart the program if it doesn't exit with code 0 which worked BARELY 50% of the time. I've been trying to figure out why this is happening by checking the CP210x drivers, reinstalling BFGMiner and rebooting my RPI, trying different configurations, clocking down, but what I noticed is that if I don't use MRR and instead mine directly to a pool myself, there's no problem when I tell BFGMiner to mine in a different pool.
I tried using NiceHash even to see if it was just MRR, but the instant BFGMiner tries to initialize MLD, it seg faults.
May someone please point me to the right direction as to where things could be going wrong?
Thanks in advance.
As a temporary fix to this, I made a bash script so that it'll restart the program if it doesn't exit with code 0 which worked BARELY 50% of the time. I've been trying to figure out why this is happening by checking the CP210x drivers, reinstalling BFGMiner and rebooting my RPI, trying different configurations, clocking down, but what I noticed is that if I don't use MRR and instead mine directly to a pool myself, there's no problem when I tell BFGMiner to mine in a different pool.
I tried using NiceHash even to see if it was just MRR, but the instant BFGMiner tries to initialize MLD, it seg faults.
May someone please point me to the right direction as to where things could be going wrong?
Thanks in advance.
Any fixes for the:
Haven't seen any responses. Just curious as now I have both miners just collecting dust, removed them completely out of my rig. As it's getting segmentation faults on every pool. Ran both on a Ubuntu and raspberry pi systems. It's been running flawlessly for months 24/7 on my raspberry Pi until just recently. Not sure why they are failing now unless this is a problem with the moon lander itself?
Have you run any updates on the Pi?Code:
[2019-10-31 11:11:59] Started bfgminer 5.4.2-38-g106390aSegmentation fault
Haven't seen any responses. Just curious as now I have both miners just collecting dust, removed them completely out of my rig. As it's getting segmentation faults on every pool. Ran both on a Ubuntu and raspberry pi systems. It's been running flawlessly for months 24/7 on my raspberry Pi until just recently. Not sure why they are failing now unless this is a problem with the moon lander itself?
You might want to delete bfgminer and rebuild. From some minor research it looks like segmentation faults are often from build issues, though sometimes it is from missing dependencies on the OS. So I would try an update and reboot first and if that fails start from scratch. If you used the download from Futurebit I might redownload and unzip it to a different location.
Otherwise I have no clue...
Any fixes for the:
Haven't seen any responses. Just curious as now I have both miners just collecting dust, removed them completely out of my rig. As it's getting segmentation faults on every pool. Ran both on a Ubuntu and raspberry pi systems. It's been running flawlessly for months 24/7 on my raspberry Pi until just recently. Not sure why they are failing now unless this is a problem with the moon lander itself?
Code:
[2019-10-31 11:11:59] Started bfgminer 5.4.2-38-g106390aSegmentation fault
Haven't seen any responses. Just curious as now I have both miners just collecting dust, removed them completely out of my rig. As it's getting segmentation faults on every pool. Ran both on a Ubuntu and raspberry pi systems. It's been running flawlessly for months 24/7 on my raspberry Pi until just recently. Not sure why they are failing now unless this is a problem with the moon lander itself?
First Time poster.
Just got my first moonlander 2 to mess around with and have run into a problem I can't seem to get around
Failed to sanity check in lowl-vcom.c windows_usb_get_string():508 is the error that keeps popping up.
any thoughts?
Just got my first moonlander 2 to mess around with and have run into a problem I can't seem to get around
Failed to sanity check in lowl-vcom.c windows_usb_get_string():508 is the error that keeps popping up.
any thoughts?
Sounds like some windows/usb driver incompatibility...what version of windows are you running, and are you using the latest silicon labs USB driver?
First Time poster.
Just got my first moonlander 2 to mess around with and have run into a problem I can't seem to get around
Failed to sanity check in lowl-vcom.c windows_usb_get_string():508 is the error that keeps popping up.
any thoughts?
Just got my first moonlander 2 to mess around with and have run into a problem I can't seem to get around
Failed to sanity check in lowl-vcom.c windows_usb_get_string():508 is the error that keeps popping up.
any thoughts?
This is my first post here.
I have two Moonlander 2s, both with noisy and vibrating fans. This seems to be an issue with many people.
Found these at Amazon. Ball bearings, rated for 60,000 hrs service life, They are also the same brand fan as are in my moonlanders. They come in a five pack.
I installed two today. Amazing difference. Silent, almost zero vibrations.
https://www.amazon.com/gp/product/B07KS5DGG5
I have two Moonlander 2s, both with noisy and vibrating fans. This seems to be an issue with many people.
Found these at Amazon. Ball bearings, rated for 60,000 hrs service life, They are also the same brand fan as are in my moonlanders. They come in a five pack.
I installed two today. Amazing difference. Silent, almost zero vibrations.
https://www.amazon.com/gp/product/B07KS5DGG5
Afternoon all. I have been mining with 2 Moonlander 2's for about a year now and here lately I have been getting Segmentation fault crashes on the miners quite often. The exact error:
These are running off a Raspberry Pi 4 with 4gb ram. Originally when I first bought these they were running on a Raspberry Pi 3 b+. They have been on the 4 version ever since the Pi 4 came out this year without any issues until recently. Any suggestions? I run them at 700 Mhz, have 2 artic usb fans over them as I have them also running with a set of Newpac's. And I also have a 12" 1930's ArticAire antique desk fan blowing over the area as well. So plenty of airflow. Room temp is currently 72 Degree's F.
Not sure what to check. Otherwise I just reboot and it'll run again stable for a few days to a week and then it'll happen again.
** Edit **
Well, now after reboot, removing the devices from their hub and back, full power down and restart nope. Nothing works. Getting Segmentation Fault every time now
Code:
[2019-10-31 11:11:59] Started bfgminer 5.4.2-38-g106390aSegmentation fault
These are running off a Raspberry Pi 4 with 4gb ram. Originally when I first bought these they were running on a Raspberry Pi 3 b+. They have been on the 4 version ever since the Pi 4 came out this year without any issues until recently. Any suggestions? I run them at 700 Mhz, have 2 artic usb fans over them as I have them also running with a set of Newpac's. And I also have a 12" 1930's ArticAire antique desk fan blowing over the area as well. So plenty of airflow. Room temp is currently 72 Degree's F.
Not sure what to check. Otherwise I just reboot and it'll run again stable for a few days to a week and then it'll happen again.
** Edit **
Well, now after reboot, removing the devices from their hub and back, full power down and restart nope. Nothing works. Getting Segmentation Fault every time now
is there a recommended clock speed to run these fanless?
all of my fans have failed on mine and at this point its too expensive to go out and buy new ones.
all of my fans have failed on mine and at this point its too expensive to go out and buy new ones.
Anything under 600 MHZ you should be good, but you'll need to bring down core voltage as well to be safe.
is there a recommended clock speed to run these fanless?
all of my fans have failed on mine and at this point its too expensive to go out and buy new ones.
all of my fans have failed on mine and at this point its too expensive to go out and buy new ones.
Has anyone been able to connect to coinfoundry or another pool that requires wallet address and username?
Ok for the last few months this has been bugging me! Im trying to get my Moonlander 2 set up with prohash dodge coin pool and im getting this issue? What am and have been doing wrong?
Any help much appreciated!
Code:
C:\Users\root\Downloads\bfgminer-5.4.2-futurebit2-win64\bfgminer-5.4.2-futurebit2-win64>bfgminer.exe --scrypt -o stratum+tcp://prohashing.com:3333 -u noobminer19 -p,d=128 -S MLD:all --set MLD:clock=600
'bfgminer.exe' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\root\Downloads\bfgminer-5.4.2-futurebit2-win64\bfgminer-5.4.2-futurebit2-win64>pause
Press any key to continue . . .
Any help much appreciated!
Sigh....read the first page of this thread and the FAQ section...your anti-virus is deleting bfgminer when you unzip it.
I guess I read straight over it. Thank you
Ok for the last few months this has been bugging me! Im trying to get my Moonlander 2 set up with prohash dodge coin pool and im getting this issue? What am and have been doing wrong?
Any help much appreciated!
Code:
C:\Users\root\Downloads\bfgminer-5.4.2-futurebit2-win64\bfgminer-5.4.2-futurebit2-win64>bfgminer.exe --scrypt -o stratum+tcp://prohashing.com:3333 -u noobminer19 -p,d=128 -S MLD:all --set MLD:clock=600
'bfgminer.exe' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\root\Downloads\bfgminer-5.4.2-futurebit2-win64\bfgminer-5.4.2-futurebit2-win64>pause
Press any key to continue . . .
Any help much appreciated!
Sigh....read the first page of this thread and the FAQ section...your anti-virus is deleting bfgminer when you unzip it.
Ok for the last few months this has been bugging me! Im trying to get my Moonlander 2 set up with prohash dodge coin pool and im getting this issue? What am and have been doing wrong?
Any help much appreciated!
Code:
C:\Users\root\Downloads\bfgminer-5.4.2-futurebit2-win64\bfgminer-5.4.2-futurebit2-win64>bfgminer.exe --scrypt -o stratum+tcp://prohashing.com:3333 -u noobminer19 -p,d=128 -S MLD:all --set MLD:clock=600
'bfgminer.exe' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\root\Downloads\bfgminer-5.4.2-futurebit2-win64\bfgminer-5.4.2-futurebit2-win64>pause
Press any key to continue . . .
Any help much appreciated!
I just started mining with my new moonlander 2 yesterday. I currently have it directly plugged into a USB SS port. I have had to dial the frequency back to 384, since anything above that causes large amounts of HW errors. I also checked the temp and it is running around 100f. I am assuming that this is a power issue and not a defective unit but figured I would run it by the community to see if you all have experienced this before. Thanks in advance.
Yes your USB port is not providing enough power, you can also try moving the bottom pot slightly (~10 degrees) clockwise to increase the voltage and see if that has a change.
Whats the error %? Did you try another computer/USB port?
Jump to: