It slowed down my usual recent time algo (Skein) in interface as well as at pool.
Groestl is working with the speed of almost 7 GH/s shown at web interface, and pool is fluctuating around this number.
As a matter of fact, my BK10 is downclocked for 1/3 with this firmware.
This firmware, and or software makes the miner a lot slower, roughly it mines at 7-8 Gh/s on pool side.
Thank you for the speed confirmations. I attempted to replicate the behavior of the original firmware as much as possible, but obviously came up short somewhere. Besides fixing the firmware to bring the speed up to stock rates, there are likely a few more optimizations that might bring it up to, say, 110% stock speed. I don't have the time required to work on this at the moment, and I'm not sure when I'll get that time.
Skein2 was not working for me at the only one pool that accepts skein2 hash. Maybe pool problem, couldn't check with another one because there is none. I think that even if I collected Skein2 coins (Woodcoin), I couldn't exchange them, lack of exchanges too.
Didn't get Skein2 to work.
Now that I think of it I may not have tested Skein2 on a pool. I may have just compared the hash output to what the expected hash should have been and saw it matched Skein2. I concur with chup that it probably isn't worth investigating since there doesn't seem to be much coin support for it anyway. I apologize for advertising Skein2 support originally when it wasn't fully tested.
Nice work! How long have you guys had these running?
Personally since about May, on a single hash board. At that time I needed to transition to another unrelated project and promptly forgot all about crypto for a few months. flexmeister wasn't the collaborator I was originally referring to and I'm guessing only for a few days for them since their solution seems to use the same firmware & sgminer that I posted, if I'm not mistaken. Here's a screenshot of the Groestlcoin network hash rate around that time:
Please post the source changes that you've made.
Not to be an asshole, but i have done a lot of work on making Baikals sgminer open source. Make sure to post link to your github or any other that includes any of the source code with changes that where orginally provided by me. This is licenced under GPL3.
Sure thing:
https://drive.google.com/open?id=1c6klf2gfuawZqOiOC7cHuWijc_iUxqXc . I apologize for not having the time to do this earlier.
...are the algorithms on-chip implemented in a way where they can be decoupled or reordered? This would be similar to how Baikal implemented their X11 chips and is what allows them to also support algorithms such as Quark, Qubit, Myr-Groestl, plain Groestl etc.
...The BK-X can do Groestl as well as Keccak, and can be overclocked (although not very much / it is unstable and I don't recommend it)
astraleureka would you care to share more of your knowledge on the X10? Were you contributing to the large jumps in Groestlcoin hash rate earlier in the year
? Any other algos you've found? How much of an overclock were you able to achieve?
After about a month of trial and error every day have finally managed to get the X10/BK28 to mine MBC.
...
The only catch is you have to use the included mining pool which has a 20% fee for all the hard work that went into this.
Verify stats at pool.totallyawesome.party
Hi, my x10 runs at 7GH. Not 10GH like you.
Can't see that your miner is actually hashing on the pool.
After restarting you need to run sudo ./mbcx10 </dev/null &>/dev/null &
This will apply all the required changes to mine MBC and change the clock speed. Once done can you confirm the clock speed and hashrate?
flexmeister does this mean you were able to fix the hash rate and boost it up to stock speeds? My custom firmware runs slower than stock so if you found a solution I'd be happy to hear how you fixed it.
codeg3n and tboy32c welcome to contact me for sharing of rewards as they have been invaluable to developing the soltuion
Thanks for the acknowledgement. I appreciate the offer but I'll politely decline. I think I'd feel kinda dirty accepting a share, but thank you regardless.
