The Bitcoin network protocol was designed to be extremely flexible. It can be used to create timed transactions, escrow transactions, multi-signature transactions, etc. The current features of the client only hint at what will be possible in the future.

Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.

Ooppsss... I have already cleaned up everything related to the previous HEAD version, including the compiled package. I need to figure out how to tell OpenWRT build package to roll back to previous commit.

Is this quite important Luke? For instance, do you suspect something might broke other parts? I prefer to move on with your latest commits, but if that would be important I will try to roll back and re-compile.

Ooppsss... I have already cleaned up everything related to the previous HEAD version, including the compiled package. I need to figure out how to tell OpenWRT build package to roll back to previous commit.

Is this quite important Luke? For instance, do you suspect something might broke other parts? I prefer to move on with your latest commits, but if that would be important I will try to roll back and re-compile.

Maybe not so important since it's just a matter of displayed device name.

Maybe not so important since it's just a matter of displayed device name.

I believe you are looking for confirmation from debug output. I took a debug log after I upgraded my BFGMiner from 5.2.0 to the broken version of 5.3.0 on the 5th of September. I think it confirms that the device name of my Antminer U3's were recognised as CBM device. Below are some of the lines on that debug log. I can send you the whole log (only about 1 minute worth of messages though) if you are interested on that.

Maybe not so important since it's just a matter of displayed device name.

I believe you are looking for confirmation from debug output. I took a debug log after I upgraded my BFGMiner from 5.2.0 to the broken version of 5.3.0 on the 5th of September. I think it confirms that the device name of my Antminer U3's were recognised as CBM device. Below are some of the lines on that debug log. I can send you the whole log (only about 1 minute worth of messages though) if you are interested on that.

OK, I think that's related to the bug I found then.Not a very simple fix, but it could cause other problems in the future, so I'll try to get it fixed.

Could you please briefly explain the bug?

Is that related to the issue that I raised on your github 2 months ago?

If you would like to make sure that what your suspected to be the bug is related to the way I executed bfgminer, could you please just tell me the command line that I should execute to confirm whether it is really a bug or not?

OK, I think that's related to the bug I found then.Not a very simple fix, but it could cause other problems in the future, so I'll try to get it fixed.

Could you please briefly explain the bug?

Drivers are registered in a hash table by their name, and when you specify -S dname:anything, when <anything> is seen, it always probes <dname> first. But the hash table does not support multiple entries with the same string, so since compac was called "antminer", it was getting probed for anything specifying "antminer".

If you would like to make sure that what your suspected to be the bug is related to the way I executed bfgminer, could you please just tell me the command line that I should execute to confirm whether it is really a bug or not?

The only way I can think to confirm it further, would be to produce a 5.3.0 with only that bug fixed.Probably won't have this until tomorrow or Monday.

If you would like to make sure that what your suspected to be the bug is related to the way I executed bfgminer, could you please just tell me the command line that I should execute to confirm whether it is really a bug or not?

The only way I can think to confirm it further, would be to produce a 5.3.0 with only that bug fixed.Probably won't have this until tomorrow or Monday.

I have been trying different branches of your github. At some points (and actually just now), I am confused with the versions as all of them only show "bfgminer 5.3.0-unknown". I can differentiate them from the package versions as I can set them. But there is no way to know the version on the screenshot of the UI or debug log (unless I make sure to identify them from the log file name).

Would it be possible to include an indication of branch/tag/commit/whatever in the UI and debug log to differentiate between each version?

Edit - for some reason the forum keeps inserting the extra /code breaks at the end. I didn't put them there, and when I edit to delete them they just show up again when I save...[/code][/code][/code]

I have two gekko compacs running on this particular machine and the rpc command only appears to have increased the frequency on one stick. I replaced "cbm0" with "cbm1" to see if I could effect the other stick. The command was accepted successfully, however, the second stick did not increase in hash rate. Do I need to do something different to get the second stick to see the new frequency?

I have two gekko compacs running on this particular machine and the rpc command only appears to have increased the frequency on one stick. I replaced "cbm0" with "cbm1" to see if I could effect the other stick. The command was accepted successfully, however, the second stick did not increase in hash rate. Do I need to do something different to get the second stick to see the new frequency?

I forgot pgaset doesn't take a device specification like that. Really you need to identify them by number, so 0 and 1 instead of cbm0 and cbm1.

I have been trying different branches of your github. At some points (and actually just now), I am confused with the versions as all of them only show "bfgminer 5.3.0-unknown". I can differentiate them from the package versions as I can set them. But there is no way to know the version on the screenshot of the UI or debug log (unless I make sure to identify them from the log file name).

Would it be possible to include an indication of branch/tag/commit/whatever in the UI and debug log to differentiate between each version?

You must be doing something unusual to build BFGMiner.That "5.3.0-unknown" usually has the git commit id for custom builds.Are you perhaps downloading zips/tars from GitHub rather than using git itself to fetch?