Back on Bitcoin.cz for now. As one would expect, contacting BFL is futile. I apologize if this caused any disruption to this pool. I really do like this pool, but ALL
I have are monarchs. Maybe sometime down the road, I will be able to use CGminer with my cards.
|
|
|
Hi. Just switched one of my miners over to this pool. I am having an issue where I get a bunch of diff 1 shares rejected that say (Above target). I am using BFGminer 5.4.1. I have to use this because of the Monarchs I have. I think this also results in a ton of invalids. This doesn't happen on Bitcoin.cz. Thanks! Its normal for monarchs on BFGMiner. Mine does that too, could not figure out how to stop it. Kano said not to worry about it since it will adjust and start submitting shares at the correct difficulty. It should only do that for about 20-30 seconds. They do it when switching to new blocks as well. Now the shares say (invalid jobID)
|
|
|
Hi. Just switched one of my miners over to this pool. I am having an issue where I get a bunch of diff 1 shares rejected that say (Above target). I am using BFGminer 5.4.1. I have to use this mining software because of the Monarchs I have. I think this also results in a ton of invalids (95%+). This doesn't happen on Bitcoin.cz. Thanks!
|
|
|
Might not be very safe wiring the outputs of two power suppiles together. Diodes might be in order.
|
|
|
Anyone know how long a deposit takes to show up on Cyptopia? My wallet indicates "confirmed" but still nothing. I am using the latest wallet.
Edit: Nevermind, took about 15 minutes.
|
|
|
Are the 1100w units + breakout and cables still for sale?
|
|
|
Thanks for the offer guys, but being in Australia means it would cost more to ship than the hardware itself is worth. Perhaps if you could find a document somewhere with firmware change details I could guess what modifications might be needed in the driver from it and work on one remotely.
According to BFL "Monarchs shipped April 2015 and after can use the official BFGMiner 5.1.0 or later." and it would appear there were changes there that broke all older versions since BFL says to use a custom version built on Jun 23rd 2014 for "Monarchs shipped before April 2015". I would guess that the change can be found somewhere here on a date after Jun 23rd 2014. I wonder how you would determine which units shipped prior to April 2014? I got all of mine second hand. Maybe that is the month F/W 1.4.5 started going on production units. As a sidenote, I have been using BFGminer 5.4.0 but the cpu usage is very high when I have many units controlled by one instance (15+).
|
|
|
try 5.4.0 ? taskmanager reports cgminer as hogging the cpu ? Tried 5.4.0, no difference. Yes cpu usage of bfgminer is around 60% on a modern intel cpu. I am hoping maybe Luke-Jr has some input. The stratum protocol isn't "free" - it does use some CPU, which grows as hashrate does - and as block size grows as well. If you want to see if there's a cheap way to reduce the usage, you'll need to provide me more useful information than just "60%"... Hmm. The instance of BFGminer I have is pushing around 8.35TH, pool is Bitcoincz. This behavior is also present on the beaglebone running Minera. That has BFGminer 4.9.0 I believe. I only have monarchs connected to this host and they are using 1.4.5 firmware. What other info would you need? Really the extra cpu usage isn't a big deal, just curious at to why it is there. Some kind of profiling report would be relevant. Is this a log? Does BFGminer have a command to produce this?
|
|
|
Older versions Identify it as a "BAS' aka single. I think back around March, or page 798 of this thread: https://bitcointalk.org/index.php?topic=28402.msg10844936#msg10844936-ck updated the driver to properly tell the difference between a monarch and the older 65nm stuff. CGminer works great with my older monarchs but these units all have later firmware (the latest i think) and they behave poorly when using cgminer. They mine at full speed with that "other" mining software but it has very high CPU usage with many monarchs connected to one host. This was reported before (I believe by Os2sam) where they updated the firmware and never told us anything, breaking cgminer. We've lost all contact with BFL (which was very tenuous at the best of times anyway) and neither Kano nor I have any working BFL hardware any more to update the software, so there really isn't much choice I'm afraid. Yep, I forgot about it over my summer as I shutdown the Monarchs because it was just too warm to run them. But if hardware is what you need I would be happy to send you my unit for development purposes. I would need it back when the software was working with it though. I do have a unit I could part with in the name of development. Shipping would be pricey though.
|
|
|
I have (for sale):
2X asicminer tube+controller 35X Blackarrow Bitfury 40GH boards+cables 10x Antminer S1
Most of this stuff has been modified (reversible) to run at lower power/hashrates.
|
|
|
My BBB has Minera 6.0, and is using BFGminer 4.9.0. I did not see the need to update it. At one point I was going to try compiling BFGminer just for the BFL gear
and using the "custom miner feature" in Minera. This would be an attempt to host 20+ monarchs on a beaglebone black.
|
|
|
try 5.4.0 ? taskmanager reports cgminer as hogging the cpu ? Tried 5.4.0, no difference. Yes cpu usage of bfgminer is around 60% on a modern intel cpu. I am hoping maybe Luke-Jr has some input. The stratum protocol isn't "free" - it does use some CPU, which grows as hashrate does - and as block size grows as well. If you want to see if there's a cheap way to reduce the usage, you'll need to provide me more useful information than just "60%"... Hmm. The instance of BFGminer I have is pushing around 8.35TH, pool is Bitcoincz. This behavior is also present on the beaglebone running Minera. That has BFGminer 4.9.0 I believe. I only have monarchs connected to this host and they are using 1.4.5 firmware. What other info would you need? Really the extra cpu usage isn't a big deal, just curious at to why it is there.
|
|
|
try 5.4.0 ? taskmanager reports cgminer as hogging the cpu ? Tried 5.4.0, no difference. Yes cpu usage of bfgminer is around 60% on a modern intel cpu. I am hoping maybe Luke-Jr has some input.
|
|
|
Hi all. I am having very high cpu usage with BFGminer 5.3.0 under windows 7 X64. The gear I am hosting on this system consists of 16 monarch's.
Mining speeds for the frequency and voltage I have specified are good, but cpu usage is around 50-60%. Host system is a modern Intel based platform setup
for coin mining and nothing else.
Thanks!
Any ideas?
|
|
|
What's your definition of any? I have all sorts of outdated stuff.
|
|
|
Older versions Identify it as a "BAS' aka single. I think back around March, or page 798 of this thread: https://bitcointalk.org/index.php?topic=28402.msg10844936#msg10844936-ck updated the driver to properly tell the difference between a monarch and the older 65nm stuff. CGminer works great with my older monarchs but these units all have later firmware (the latest i think) and they behave poorly when using cgminer. They mine at full speed with that "other" mining software but it has very high CPU usage with many monarchs connected to one host.
|
|
|
My monarch died long ago ... that someone else (not BFL) supplied me with.
BFL never contacted us about firmware changes or anything like that (or even about the Monarch until LONG after they should have) so your on your own with support of newer firmware in them since I've no idea at all what might have changed and no way to test it.
I am just guessing here but it seem like CGminer is treating this unit (Monarch W/1.4.5 FW) as a "single". My units all hash at about 60-70Gh. Maybe incorrect identification in some way.
|
|
|
Nice 4 blocks in a row after a pretty blah weekend. Keep up the slushin'!
Ya, nice change!
|
|
|
Anyone had any problems with poor performance of Monarchs using firmware 1.4.5? Mine all hash at about 25% of their expected rate. This problem
does not happen with the units I have using firmware 1.4.2 or 1.4.3. I have tried CGminer 4.9.2 in Windows 7 X64 and with Minera on a beaglebone.
Same issue on both platforms.
|
|
|
|