Wonder how many you qualify as "many" I have about 5 perm leases in my router right now. Depends on router maybe some may not function well with this. But either way you should get it to stick if sync coldreboot is used on system or do the router thing....assume you got it now?
i've tried sync, and coldreboot. but it still failed. Well I dont know, maybe with the special litecoin build there were some things taken out and thats why its not working. It has worked for me, but I use regular BAMT, even for litecoin mining. |
|
|
|
Also use your router just set a permanent lease (That's what I did) thus no change needed on OS but IP never changes :-)
if your have many rigs, it will get you mad.. .haha. it is good idea for little rigs. Not necessarily. Its one of those do it once and never have to worry about it things. You set the router to assign an IP address to a certain MAC address and every time you plug that machine in, the DHCP would assign it that address, even if you re-install the OS. |
|
|
|
I have both of my BAMT rigs set to static IP's, but I didnt use SSH to do it (although those instructions should work, I instead hooked it up to a monitor and set it that way. Its the one thing I do through the GUI, everything else I command line. I would recommend doing it that way.
thanks very much. plug a monitor that way, it is working. but if you manager over 50 or 100 or 200 rigs. it is more complicated. any easier way to set the bamt to static ip? Best. SSH into your unit, then set the static IP like this. iface eth0 inet static
address xxx.xxx.xxx.xxx
netmask xxx.xxx.xxx.xxx
gateway xxx.xxx.xxx.xxx After that, do as suggested and do a sync so it saves the settings. |
|
|
|
|
It appears to have taken it in some capacity. Usually if it doesnt like it, it will tell you that it doesnt recognize the command.
|
|
|
|
|
Probably not since Easyminer really is just a pretty GUI interface that runs BFG in the background. As for the pool side, thats just an estimate on your hashrate depending on the amount of shares you submit during a snapshot time period (usually like 15 minutes). So if you turn out some lucky shares/solve some higher difficulty shares/the pool isnt reporting shares and needs to catch up then that can be affected (I have had my Jalapeno clock in at nearly 20GH before because the pool took a while to record all of my shares that when it did it seemed as though I was hashing at a much higher rate).
|
|
|
|
|
I would guess that you truly arent getting 2.0A out of your hub power and thus your Pi is pulling too much power. Get a separate AC adapter for your Pi and try the BE in the hub by themselves.
|
|
|
|
|
Have you tried to also systemctl enable cgminer.service, then rebooting?
|
|
|
|
First I would run bfgminer as you stated above, then once its started type S to display the settings, then type W to write a config file. This should save it for you so next time all you have to do is just start bfgminer without the -S all afterwards (I could be wrong, never done it that way, but seems like what you would do).
Now, auto starting is the next step. I know this works for Minepeon, but I dont know about Raspbian, but they are similar so why not give it a try.
Try:
sudo systemctl enable bfgminer.service
sudo systemctl start bfgminer.service
Reboot and see if that works. I
I did the first step, but "systemctl" command is not found Try this first sudo apt-get update sudo apt-get install systemd Once you do that, try running those commands again. Now on sudo systemctl enable bfgminer.service Operation failed: No such file or directory Odd....try: sudo unmask bfgminer.service Then try and enable and start it agian. If not, then its over my head. |
|
|
|
First I would run bfgminer as you stated above, then once its started type S to display the settings, then type W to write a config file. This should save it for you so next time all you have to do is just start bfgminer without the -S all afterwards (I could be wrong, never done it that way, but seems like what you would do).
Now, auto starting is the next step. I know this works for Minepeon, but I dont know about Raspbian, but they are similar so why not give it a try.
Try:
sudo systemctl enable bfgminer.service
sudo systemctl start bfgminer.service
Reboot and see if that works. I
I did the first step, but "systemctl" command is not found Try this first sudo apt-get update sudo apt-get install systemd Once you do that, try running those commands again. |
|
|
|
|
First I would run bfgminer as you stated above, then once its started type S to display the settings, then type W to write a config file. This should save it for you so next time all you have to do is just start bfgminer without the -S all afterwards (I could be wrong, never done it that way, but seems like what you would do).
Now, auto starting is the next step. I know this works for Minepeon, but I dont know about Raspbian, but they are similar so why not give it a try.
Try:
sudo systemctl enable bfgminer.service
sudo systemctl start bfgminer.service
Reboot and see if that works. I
|
|
|
|
With Luke's help, I've got my Pi mining with my ASIC.  Currently, I start it by 1) opening a terminal 2) changing to the bfgminer-3.2.1 directory 3) entering sudo ./bfgminer I'd like it to start mining automatically when powered up. I found this post https://bitcointalk.org/index.php?topic=168174.msg2689279#msg2689279but I don't think everything I need is there. Could someone please tell me what to do, and keep in mind that Linux is a foreign language to me. Thanks What OS on your Pi are you running? If you look a few posts up, there was mention of how to automatically start bfgminer when your pi turns on. |
|
|
|
Try README: Q: I ran cgminer, and now BFGMiner doesn't work!
A: cgminer has its own non-standard implementations of the drivers for most USB devices, and disables the official drivers (on Windows, you did this manually using Zadig). Before you can use BFGMiner, you will need to restore the original driver. With Linux, usually rebooting or re-plugging the device is sufficient. Well i had been doing a daemon-reload after stopping and disabling cg.... So i decided to go ahead and just try a reboot. and THANK YOU THANK YOU!! that worked. I ssh'd in, stopped and disabled cg, then enabled bfg and rebooted the device. once it came back up they all came online and started mining! I knew i was doing something newbish and stupid. Problem solved You can have bfgminer be your default miner when your Pi starts up. If nothing has changed it should be sudo systemctl stop cgminer.service
sudo systemctl disable cgminer.service
sudo systemctl enable bfgminer.service
sudo systemctl start bfgminer.service |
|
|
|
Try stratum+tcp://pool:port for 3333? It is stratum, right? http is used for longpoll and you would need to use the appropriate longpoll port that would then advertise stratum and switch you to it.
Still identifies it as bad Tried it from the command line and in pool management Try it without any leading protocol definition. I use "-o us.ozco.in:3333" for instance. Sam You mean like cgminer -o http://pool:port -u username -p password as I posted above, or am I completely misunderstanding you? Edit: Oh, you mean without the http. I use us3.eclipsemc.com:3333 but that isn't working What about using one of the other US servers? I personally use us1 with us2 as my failover. |
|
|
|
What hub are you using?
Pi does not work with usb3 hubs,
usb 2 hubs are low on power for erupters. Even the best with 2500mA psu only stay stable with 5 erupters.(D-Link 7 port is one of the better units, and falls over with 6 erupters in my rig)
Pi usb support is not the best. I have better results by only using one port on the Pi. So move the BFL to the hub.
Try another hub. or add another hub in daisy chain.
EDIT see my post from yesterday
Hub brand escapes me at the moment, like i said, not at home right now. But i do have the D-link 7 port hub being delivered today. I had also tried a 2nd powered hub daisy chained and it still crashed. But this is with cgminer. I understand the importance of the hub and such, but even if we assume the hub itself is having issues, then why doesnt bfgminer see my BFL which is plugged directly in? I think if i could find the answer to that then i could fumble through the rest. What OS are you running on it (Minepeon or Raspian)? If you are using an older distro, it probably has an out dated version of bfgminer on it, you may need to update it. |
|
|
|
Currently, i am running 1 BFL Jalapeno and 4 block erupters with cgminer on my MinePeon rpi box. I have 2 more BE's that i want to add to the mix but this causes cgminer to flip out and continuously reboot my rpi. Minepeon also supports BFGminer and i am wanting to switch to this, however i can not for the life of me get it to recognize the BE's or the BFL. i have tried -S all, -S auto, -S erupter:all, -S bitforce:all (as i had seen suggested somewhere on a search). But none of these work, when i do screen -r to check the readout its telling me no devices found. the BE's are all connected with a usb hub and the BFL is plugged directly in to the rpi. and like i said, this current set up is works with cgminer, i just cant add anymore of the BE's without it crashing.
I have searched this thread and come up empty (although there have been plenty of suggestions), can someone please tell me what i am doing wrong?
Pi's are notoriously bad for having weak USB ports. Are you using a powered hub? If so, what kind/what is the power supply/ac adapter specs (volts, amps)? |
|
|
|
Seems about right. I ran solo with 20 usb sticks for a few days before and noticed that BFGminer seemed as though no work was happening. Thanks for the help. Highly anticipating these new blades. About to place an order with SSB this afternoon. Wish I had enough coin to do 10 on a backplane. 100GH for 40btc could pay off after two blocks solved!
So, how you nade it? Iīd like to mine in solo with some ASICīs devices but how? If somebody knows, please PM!!!!! Thanks Should have worked fine. Since this post I did some solo mining with my ASICs and yes, thats exactly how it worked. There were no accepted shares until I found a block, and then depending on the program I was using, it either showed 1 accepted, or it showed the amount of coins that were in that block. |
|
|
|
I thought about the port release issue but verified that nothing was using the ports using netstat. The other proxy was on another machine entirely.
No firewall on the computer (makes testing easier)
However, I got it up and running by using another port entirely. Instead of 8332, I chose 8339. Now it's up and running. Going to let it stabalize and report its stats back.
I do find it curious that nothing is trying to use 8332 (or anything close) but that port just won't work. I'll try some other software on the port later and see if it's an issue regardless of software.
What about a firewall on your router (if you are using one)? Would also be an issue with that blocking it, instead of a Windows firewall. |
|
|
|
What do you mean the time on my computer is going out of whack?
He means, what is the time set in your operating system? When you send shares back to your pool, it goes back with a time stamp on them. If the time stamp doesnt match up, it gets rejected. Many times with people saying that all their shares are being rejected, its because the time on their OS is not set correctly (few hours off, few years, wrong month, etc). |
|
|
|
Using Easy Miner for BFL Jalapeno and using the Manual Mining option with BFGMiner.
I read in the README to add: -S opencl:noauto to disable GPU but when I add it in the Manual Mining line the miner won't run anything.
My line reads: bfgminer -o stratum.btcguild.com:3333 -u asdfasdf_xxx -p
Is there a specific order I have to add the -S opencl:noauto?
For what it is worth, I do NOT have the "Enable GPU Mining" box checked.
bfgminer -o stratum.btcguild.com:3333 -u asdfasdf_xxx -p -G -S All or bfgminer -o stratum.btcguild.com:3333 -u asdfasdf_xxx -p -S opencl:noauto depending on how much you want to type. |
|
|
|
|
Show Posts
