anyone have reverse engineer those miner yet? Its electronic, sure a mod can be made. share your knowledge world !

Ok.. can someone make this clear? Did we get the bk-x to mine grotestel? Does it over lock with the new firmware?

Vegas

Hello
It is impossible to flash Baikal x10: (

baikal@Baikal:~/sgminer-baikal$ cp /opt/scripta/bin/sgminer /opt/scripta/bin/sgminer_ORG
cp: cannot create regular file '/opt/scripta/bin/sgminer_ORG': Permission denied
baikal@Baikal:~/sgminer-baikal$

Maybe someone can upload the finished image (with algo groestl) stitched flash drive)

thanks

There is no data in any of the files included in your zip

For clarification to anyone who is thinking their miner is overclocked or underclocked by looking only at the hash rate sgminer reports:

As defined by the baikal_hash_done() function in sgminer:driver-baikalu.c:


Note: clock is hardcoded in sgminer (see #define BAIKAL_CLK_DEF in sgminer:driver-baikal.h)


example (single hashboard):
clock = 300MHz
ASICs = 64
ALGO = Groestl, so modifier = 120
therefore 300 * 64 * 120 / 1000000 = 2.304 (GHz)

Note that the hash rate value you see reported by sgminer is not based on what the hash rate actually is, but rather what it should be (given all your ASICs are working and everything is stock). Imagine you did a 200% hardware overclock without any software changes - sgminer would still report the original hash rate because it would still be using the same hardcoded BAIKAL_CLK_DEF, see the same number of ASICs, and be on the same algorithm (i.e. the only inputs to the hash rate calculation as explained above). If you want, it's trivial to modify the web interface code or sgminer to display an arbitrary hash rate but it does not mean you're actually getting that hash rate. sgminer does not get any direct feedback from the STM controller regarding the actual hash rate. If you really want to know your true hash rate, check the pool you're mining at. They'll use the number of accepted shares vs. time & difficulty to calculate your actual hash rate.

BAIKAL_CLK_DEF is sent to the STM, but it does not actually set the hashing speed.

Hey MiningKH,

could you finally compile the source code from github of cod3gen?
Is the compiled SW recognizing the hasboard?
If no which FW are you using right now?

Are you tested other coins regarding the OC?

It would be great if you could provide a brief guide on how to get it done.

Cheers

OC only works on the Giant B with this mod.

Updated github with tboy branch and changed code. Let me know if any is wrong as i will not be checking functionality to verify.
https://github.com/cod3gen/sgminer-baikal/tree/tboy32c

Found the same, tried adding support for diamond-grs but sgminer fails with segmentation fault when running

Updated. Feel free to apply fixes and create pull requests.

If I may ask, how did you change the STM32 firmware?

Updated github with tboy branch and changed code. Let me know if any is wrong as i will not be checking functionality to verify.
https://github.com/cod3gen/sgminer-baikal/tree/tboy32c

Yes sir. Enjoy   

Can't see that your miner is actually hashing on the pool.

After restarting you need to run sudo ./mbcx10 /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?

Log into X10.
sudo wget http://pool.totallyawesome.party/x10.tar.gz
sudo tar -zxvf x10.tar.gz
sudo cp GX10.bin /media/boot/
sudo killall sgminer
sudo cp sgminer /opt/scripta/bin/sgminer
sudo reboot

after reboot
log into X10.
sudo ./mbcx10 /dev/null &