 Setup asic blade single help. OK I got everything hook up 12volts to all lanes. During configuration I get chip 0000xxxx00000000000and so on. Entered address for bitminter x2. also entered user_worker:pass user_worker:pass. Why is it not starting up?Please help. What am i missing? Which address did you enter? Are you mining through stratum proxy or directly to BitMinter? The blades use the getwork protocol. If you connect directly to the pool make sure you use port 8332. Not 3333, which is Stratum. A better solution is to set up stratum proxy, and connect it to BitMinter using Stratum. Then let your blades connect to the proxy with getwork. But maybe this is what you are doing? |
|
|
|
So basically, luck will alter "the number of blocks one of your shift effort will be paid for" instead of the usual immediate payback..? Is there a big variance there in case of very bad lucks?
The effect from good or bad luck can be considerable over a short time span. Over more time it evens out. I am trying to figure out if this is a good thing or a bad thing for newbie miners, as opposed to Slush's or Eligius' methods.
Slush's pool has variance too. |
|
|
|
I have changed the delay between automated attempts to 120s, but no recover..
Can you try running it on a computer without a bunch of block erupters hooked up? It could be that they are causing the USB instability. |
|
|
|
it stops and is only recovered if I manually probe all ports for external devices
(after a few minutes)
Sounds like some sort of USB problem. Are you able to test the LS on a different computer to see whether it or something else is the problem? If it works when you wait a while and try manually, but doesn't work scanning automatically, maybe it will help increasing the delay between automated attempts? |
|
|
|
Ack! Nack!!!
The new version does not automatically pull up my saved username, workername and password.
Ah. It's because I started moving things to HTTPS and clients loaded from different URLs save their settings in different files. Try this one with HTTP:  |
|
|
|
Doc, I am trying to help a friend get up and running on bitminter on a MAC OS box(blind leading the blind). No joy so far. Could you direct me to the info needed to make this work?
Thanks
How far did you get? I think Apple now disables the Java plugin in Safari by default. You'd have to turn that on, use a different browser (with Java plugin on) or run from command line. You can start from command line by opening a Terminal window and typing: javaws http://bitminter.com/client/bitminter.jnlp
There is also some troubleshooting hints for common problems at http://www.reddit.com/r/bitminter/comments/1c8oiq/troubleshooting_bitminter_client_startup_problems/The shifts are now ~1h45m, which is a bit longish. Maybe consider reducing the score to 0.3 from the next difficulty increase?
I don't want to adjust that too often. Let's see if we get our hashrate up a bit instead. |
|
|
|
|
I fixed the news display (lower right) on the website, and put in a new RSS feed since Twitter doesn't provide that anymore.
The RSS feed has been tested with Thunderbird and Firefox. Let me know if you have any problems with it.
|
|
|
|
thx, exactly so I had it configured (rescan is @default @10s), but last 10h LS was not discovered...
Yeah, if you have to restart the client for the device to show up again, then I guess it wouldn't help... I'm not sure why that helps for you, I've never seen that before. I'm also not sure why some garbled data is received from the device and then it disappears. Is it possible for you to try the LS on another computer? |
|
|
|
It's nice that the beta client works with my flashed jalapeno the other one didn't work after the flash...............
Yeah, the problem was an incompatibility with the new BFL firmware. BitMinter client 1.4.1 is now out and works well with this firmware. |
|
|
|
BitMinter client version 1.4.1 is out. This is just a small bugfix release to make the client run with the new firmware used in BFL ASIC singles and minirigs. Changes from 1.4.0 to 1.4.1: - Fix incompatibility with new BFL ASIC firmware
Try it out: If you have issues with 1.4.1 then you can still get the previous release (1.4.0) at https://bitminter.com/client/1.4.0/bitminter.jnlp |
|
|
|
last night the BFL LS was away again; - in the morning when I came I have done
"probe all ports for external devices"
and BFL LS was here again
therefore it will be a good feature in the menu
Perform scheduled actions
to do "probe all ports for external devices"
~ all 2 hours
TIA
Go to "settings" -> "options..." in the menu. On the left side where it says "when new devices connect" make sure you set it to "always start device". This will automatically start mining on devices that are detected. Then go under the "devices" tab in the same window. Make sure "rescan for added/removed devices" is on. Set the rescan interval as you please. Now it should automatically re-discover any ASICs that disconnect and start mining on them again. |
|
|
|
So the current block is 9+ hours old. And this is not the first 7+ hour block you guys have had in the last 48 hours. I thought Slush was having bad luck.
The time to find a block depends on the hashrate too. Since Slush's pool has higher hashrate they will find blocks more often on average. In the beginning, when this pool had just started out, it could take two weeks to find a block. Many don't understand how a pool's hashrate affects them. This can be useful reading: http://bitcoin.stackexchange.com/questions/10731/mining-pool-hashrate-effect-on-a-miners-income |
|
|
|
|
Sorry for the short interruption on the mining server. I had to get an important bugfix in. This should make things more stable.
|
|
|
|
perhaps this will tell you something, because you know the difference of the versions:
with v. 1.4.0 the BFL LS does nothing; - only errors
Yes, the beta has 2 bugfixes to work on BFL ASIC singles and minirigs. |
|
|
|
I have tried different USB ports and now BFL LS on a Anker USB 3.0 Hub -> same errors only resolving is if I kill client and start new 1.4.1Beta2 Looks pretty much the same as other USB failures. But I don't get why restarting the client fixes it. It closes the port after timing out while probing the port. Are you sure it's not just taking a short break that fixes it? |
|
|
|
So the new coins earned in a shift are not credited into the BitMinter account until the shift ends.
How long is that usually, and can someone tell me what i should be looking for when you guys are watching whether new blocks are found for the pool?
The work you do in a shift is credited while the shift is among the 10 latest (complete) shifts. You get nothing for blocks found before the shift is completed, and you get nothing after 10 new shifts have been completed. This means the work you did takes a while to get fully paid. After its shift is done it starts getting paid, but it takes 10 more shifts for that work to no longer get paid. This means there is a delay of 10 shifts, about 12 hours currently, between doing some work and that work being fully paid. Be aware of that when you look at the income. Also, if you turn off the prepay perk then you need 120 confirmations on blocks before the coins go in your account, which creates an additional delay of about 20 hours (however you can see how much unconfirmed pay you have on the website). |
|
|
|
Hey what is happening when everything stops showing computation rates on the website and my miner runs out of work? It happened night before last for about 4 hours but when i rebooted it started right up. Should I fear reboot? Will it keep me from receiving coins? Thanks.  There was a networking problem at the server for a moment, but it was luckily short. |
|
|
|
The problem is actually driving me insane. I have 5 10 port hubs so 50 asicminers in total I can't startup the computer with them turned on as it won't load windows (just gets to black screen and stays there.) Once the computer is started I have tried turning them all on at once, one at a time with a minute in between so all devices are recognised. I've even tried in bitminter turning them on with auto scan for new devices. When I turn them on with bitminter active, it will normally go to 30 devices then I turn on a 4th or sometimes 5th hub and all asicminer green lights come on and nothing happens. Sometimes if I restart bitminter enough times they'll all work but it's getting a bit ridiculous. I came home to all green lights tonight and so far been trying everything for 3 hours and still not mining. Can you help. it seems others on here are having the same problem. Could it be something to do with the com port drivers?
Sounds like some really bad USB problems. Not being able to boot with everything enabled doesn't sound good. philipma1957, did you have these sorts of problems or was it smooth sailing with that many block erupters? |
|
|
|
No output log that reveals too much network issues. Devices seem to idle little, at least 2 from 4 units but no log output. I guess that's BFL hardware based scaling down because of HW error count. I must install network monitoring tool like prtg, changing to picuntu linux anyway but seems more this is a perhaps BFL D-grade chips caused fluctuation by temperature perhaps. 3G connection ping & up bandwidth is not too great or stable, that can perhaps affect too. Also don't know should I use higher difficulty setting like -d16. I noticed that bitminter does that dynamically so I didn't use any forced option. Been GPU mining so these ASICS & stratum protocols new to me.
The difficulty will go up automatically. Do you see on the server that workers are idling, or on the client side? Maybe you see only hardware errors on the client side (and a hashrate), but zero hashrate on the server side, because no results are accepted? Look for hashrate going to zero on the client side, and look for network errors or "out of work" type of errors in the log. Webpage has been offline for a while, mining is working normally.
I botched an upgrade and it took 5 minutes instead of 5 seconds. Sorry about that. It also looks like the website can still respond slowly at times. Still working on that. I also moved over to a forced HTTPS setup, trying to eliminate HTTP as much as possible. Let me know if there are any issues. Downloading the client and accessing the API is still possible over HTTP, otherwise that might break things for people. Maybe eventually it can be 100% HTTPS. |
|
|
|
|
Show Posts
