Post
Topic
Board Mining (Altcoins)
Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
by
cod3gen
on 25/03/2018, 18:47:48 UTC
Tired as hell, but woohaa!

Code:
sgminer 5.6.2-cod3gen - Started: [2018-03-25 20:31:35] - [0 days 00:01:14]
--------------------------------------------------------------------------------
(5s):10.13G (avg):10.27Gh/s | A:829  R:0  HW:37  WU:31147.411/m
ST: 1  SS: 12  NB: 4  LW: 4168  GF: 0  RF: 0
Connected to quark.eu.nicehash.com (stratum) diff 40 as user XXX
Block: 8826b8d8...  Diff:87M  Started: [20:32:35]  Best share: 39.3K
--------------------------------------------------------------------------------
 [U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
BKLU 0: 39C 300MHz [ASICS #64] | 3.379G/3.616Gh/s | A:288 R: 0 HW:25 WU:10739.883/m
BKLU 1: 39C 300MHz [ASICS #64] | 3.379G/3.610Gh/s | A:287 R: 0 HW: 5 WU:11230.049/m
BKLU 2: 38C 300MHz [ASICS #64] | 3.379G/3.613Gh/s | A:302 R: 0 HW:10 WU:11173.155/m

Have not tried any other algo`s just yet, so i only know that quark works at the moment. However, i see a high rise in hardware errors, on stock sgminer this have always been "0"(Ive had the X10 in only 2 day though). Chip temps are the same as before. Ill see over the night if hashrates are showing up correctly at nicehash. Will continue tomorrow.

Great work!
Did you add these changes to usbutils.h?
Code:
...
USB_ADD_COMMAND(C_BAIKAL_SEND, "BaikalSend") \
USB_ADD_COMMAND(C_BAIKAL_READ, "BaikalRead")
...


Yepp, came down to being fault definition of chip manufacturer in usbutils.c in its search function for finding devices
Code:
.iManufacturer = "Baikal", // 25.03.18 changed from "MS Technology" to "Baikal"

It seems that baikal continuously does live changes on their partition and just mirrors it to a image, that why we are able to recover these files and the reason why there are so many of the same ones. Files goes years back to A900 and Dash Mini Miner.