Bitcoin Forum
November 28, 2022, 02:01:01 AM *
News: Bitcointalk Community Awards
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1] 2 3 »
1  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N / B - Open Source - Confirmed OC Giant B! on: January 07, 2019, 12:59:39 AM
And unfortunately it is not possible to clock the miner over 390Mhz. no idea why.

Take a look:
https://bitcointalk.org/index.php?topic=2790982.msg33090927#msg33090927

It's a bug in sgminer. It should be something like
Code:
((clk - 200) / 10) + 2
instead. However it doesn't really matter (for the reasons mentioned in my last post) so I didn't bother correcting it in the version I posted.
2  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N / B - Open Source - Confirmed OC Giant B! on: January 07, 2019, 12:34:33 AM
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:

Code:
[Displayed Hash Rate (in GHz)] = [clock (in MHz)] * [ASIC count] * [ALGO modifier] / 1000000

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

Code:
[ALGO modifier] (defined by Baikal in sgminer) =
X11/QUARK/QUBIT/NIST/MYRIAD_GROESTL/GROESTL: 120
SKEIN2: 62
X11GOST: 16

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.
3  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N / B - Open Source - Confirmed OC Giant B! on: January 02, 2019, 12:52:34 PM
Bus 007 Device 002: ID 0483:5740 STMicroelectronics STM32F407 is the current result, blue LEDs are up, sgminer is running (with your firmware).

root@Baikal:~# md5sum /media/boot/G*.bin
d806968a965a7499b026ee558073af54  /media/boot/GX10.bin

root@Baikal:~# python /usr/bin/update_fw.py

Downloading...
Done

That all looks good except for the checksum of the bin file you're using. I'm getting b7ee4ca88a190fb086655761e1f55c6c for the stock v1.2 file. I'd try pulling the file from the v1.2 OrangePi image and try again. Remember to revert back to the stock v1.2 sgminer too.
4  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N / B - Open Source - Confirmed OC Giant B! on: December 31, 2018, 03:48:48 PM
lsusb | grep 0483 (with v1.2)
Code:
Bus 007 Device 013: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
lsusb | grep 0483 (with your firmware)
Code:
Bus 007 Device 014: ID 0483:5740 STMicroelectronics STM32F407

At least the STM shows up for you! That's better than the problem chup has.

Is 0483:5740 STMicroelectronics STM32F407 the result you have currently? If so, are you also saying you do not see the blue LED at all? IF the STM has my firmware, AND it is in RUN mode (as your last result would indicate), AND sgminer is not running (as indicated by your previous post where you ran the miner-stop script), then the blue LED should be flashing (especially if you also ran the reset_stm script as previously indicated).

Try this next if you would:
  • Put the desired .bin firmware file in /media/boot
  • Make sure the filename starts with a capital G
  • Run md5sum /media/boot/G*.bin    -what is the result?
  • Run python /usr/bin/update_fw.py   & please post the entire output of that command
5  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N / B - Open Source - Confirmed OC Giant B! on: December 30, 2018, 10:10:28 PM
I can not confirm rolling back to 1.2. If i try to, controler board stays in DFU mode (red LEDs).

I did those steps:
Code:
./opt/scripta/startup/miner-stop.sh
python /usr/bin/update_fw.py
python reset_stm.py
lsusb | grep 0483

What does this command show when you run it?
Code:
lsusb | grep 0483
Either there's nothing, or something with "STMicroelectronics" in it.

Same question as to chup: What was the last firmware you successfully flashed (the one I posted? flexmeister's? One of the stock images?)
6  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N / B - Open Source - Confirmed OC Giant B! on: December 30, 2018, 10:05:31 PM
Here is what I get after commenting exit from DFU Mode in update_fw.py and running it with v1.2 GX10.bin:

Not getting any STM devices in that list is pretty odd. Obviously if you haven't tried you should completely power cycle the miner and try again. In order to determine if the problem lies with the OrangePi or STM you could do this:
  • Remove the OrangePi from the controller board (important). Leave the Ethernet connected.
  • Use a USB cable to connect the USB device connector on the controller board with the USB A host port on the Orange Pi
  • Use another USB cable to connect the Orange Pi's micro USB port to any other powered device's USB host port (to power the Orange Pi)
  • Run the lsusb | grep 0483 command again.

A working setup will show the STM device on Bus 006 (not 007 like when the OrangePi is seated on the controller board directly). If this time you DO get something, then the USB port on the Pi pin headers isn't working, but the STM probably is. If you still get nothing, you could swap controller boards with another Baikal Giant miner (if you have another) and try again.

What was the last firmware you successfully flashed (the one I posted? flexmeister's? One of the stock images?)

7  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N / B - Open Source - Confirmed OC Giant B! on: December 30, 2018, 07:38:29 PM
If I may ask, how did you change the STM32 firmware?
That would also interest me very much.
Spending a lot of time poking at the miner. You'll need to have a decent background in software & hardware.


Nice work! How long have you guys had these running?  Grin
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.
Too bad you did not share....  Cheesy Grin
I had just spent several months of my free time reverse engineering with the collaborator so a few months of slightly higher profit mining helped make me feel a little better about trading a small part of my life away for it.


No luck on Keecak? I guess you would answer no anyhow..  Grin
Looks like I have a comment in the firmware for keccak saying "experimental" so I don't think I got it working, although I don't remember putting much time into figuring out why not.


Do I understand it correctly that DiamondGroestl is added, not Groestl and not SKEIN2.
I can only vouch for Groestl with the software I posted.


Rollback is working.
Store the backup file into media/boot and reboot your device. Ensure the filename begins with "G"...bin
Cheers
unfortunately didn't work. so i decided to reflash sd card with org. image v1.1 and/or v1.2 - still not working. hashboards are showing only red leds :-(
i've already trieded to change sd cards and orange pi - doesn't matter, hashboards don't work- leds red.
Wellcome to the club of bricked X10s.
witch GX10.bin? original one? and witch update_fw.py ? meanwhile i've changed psu, sd card, hashboard.... looks like control board is defective
From these quotes I'm not sure if there are actual "bricking" problems or if people are just having trouble with the steps to change firmware. I will confirm that I am able to rollback firmware from the firmware image I posted. If ONLY the red LEDs are showing, then that should mean the control board is in firmware update mode. If the red LEDs are on and you see a blue flashing LED, then the control board is in RUN mode but sgminer has not given it work to do (either sgminer died or the pools are all down, etc). If you see blue solid LEDs then it's hashing. If you don't see any LEDs then your device is not powered Tongue.

If you run update_fw.py and get:
Code:
dfu-util: No DFU capable USB device available
you can try editing the update_fw.py script by commenting out (adding a "#" at the start of the line) the last couple lines:
Code:
#update_firmware()
#exit_dfumode()
Run the modified script and it should have reset the STM and left it in firmware update mode. Then run:
Code:
lsusb | grep 0483
And the result sholuld be this:
Code:
Bus 007 Device 002: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
(the "device" number will vary)
If instead you get:
Code:
ID 0483:5740 STMicroelectronics STM32F407
we'll have to go from there.
8  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N / B - Open Source - Confirmed OC Giant B! on: December 28, 2018, 10:23:58 PM
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?  Grin
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 Wink? 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.
9  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N / B - Open Source - Confirmed OC Giant B! on: December 21, 2018, 06:22:52 PM
  • https://drive.google.com/open?id=1jqSKB3G-nKtHLF3dfPGalSgNLOiHAMBf
  • Custom X10 firmware w/groestl & skein2
  • Free (as in lunch) - no dev fee or anything like that
  • Personal hobby project for me to do reverse engineering
  • Only tested on one hash board but should theoretically work with all three
  • No asic mods req'd to add those algos i.e. X10 has always had the ability
  • Don't really have time to support this, so installing it/troubleshooting is on you. Review this thread for help on how to change out firmware
  • Would be appreciated if any trusted members of the forum could test this out and let us know if it works for you (how many scams tell you this?)
  • Release source? Maybe someday. This is free after all
  • Uses slightly modified sgminer as pulled by Cod3gen
  • Included sgminer incompatible with stock firmware
  • Uses completely custom firmware built from scratch by myself based on original behavior analysis
  • Copies original firmware behavior as closely as possible i.e. there may be possible optimizations
  • Need to run reset script before running sgminer each time (couldn't be bothered to fix in sgminer/firmware)
  • Suggest adding reset script plus a 5 sec delay to miner-start.sh file
  • Hash rates: you tell me. The pool I test with has poor rate reporting
  • Sgminer (even original) reports the hash rate based on what it is supposed to be, not what it actually is i.e. the actual hash rate is not measured, so best to use pool-reported hash rate
  • One other direct collaborator who may reveal forum identity if they wish (I'll confirm if they do)
  • I accept forum merit/trust if you'd like


My ("tboy32c") PGP fingerprint: 02F2 B257 1793 8F10 3089 F951 2EE7 F90A 2A75 9BC6
Message signature:
iQEzBAABCAAdFiEEAvKyVxeTjxAwiflRLuf5Cip1m8YFAlwdLDEACgkQLuf5Cip1m8ZOawf+
KREdgviOwT+zkNg7IyvQ8++DpnXzIsl0n+FWpGyAosGhUQC3QBqWulwbBYt9PQ2TmNh5ITPI
nSr3I1onazWjBYso19huRAsP7SYei5ewSYkVms5+N5ui7Hfh5qPFGvhQdSX43j5NheDM9dIn
lj54pwR5ONR3xHphmLmm6PmiYcboPeWGiOCjjoxWBsOtuhJArXnmCq6ZpdysgBjoPRVlQzjH
JFkpSNMEKnpjvoo7i/DT9IsYcJd7Yy9kl+zlBKOM3LL1BR4fKC1cMezKx8udMgXBt1p0KZwn
m2yJfArWZTaIHWq41MldDll7APnjU53Ogdi7pvjorV3rtXW2fss+xQ==
10  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N / B - Open Source - Confirmed OC Giant B! on: July 25, 2018, 10:32:39 AM
Does anyone have any experience with Baikal repair service ?   Four of my Baikal's went down from an electrical storm .  Three are Giant B and 1 Giant X .  Is it worth the effort to repair them ?    I know the shipping will be steep .

     Thanks ,  James

If you have any others you could try swapping a known good Orange Pi/controller board with one of the ones that don't work. If only the Orange Pi or controller board died you're in luck since those are easy to replace (Baikal sells them separately if you contact them). If the hash boards died you may not be able to repair them depending on if the ASICs themselves fried of if it was any of the other components.
11  Alternate cryptocurrencies / Mining (Altcoins) / Re: Baikal Giant X10 on: July 11, 2018, 07:12:46 PM
Well, I think I screwed up. One of the hashboards won't come on any more. The other two work, so I can still run it at 2/3 capability. I will be looking to move it indoors, instead of outside in my mining shed. I guess the humidity and/or heat was too much for it, being in south Texas. Some of the components have green around the contacts. I went to blow off the dirt and debris with an air compressor, and part of the red paint over the copper came off. Looks corroded bad.

If that hash board looks corroded have you checked all your other equipment in your mining shed? It might be worth converting your shed to use closed-loop cooling so you could remove the heat without transferring air directly from/to outside.

Do you think you'll be able to clean/repair the corroded board and get it working again?
12  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N / B - Open Source - Confirmed OC Giant B! on: April 25, 2018, 06:22:57 PM
Guys, I'm seriously a noob at all this.

I have a question .. hoping you can help.

Is there a way to update the new Nist5 firmware update from Baikal for the X10 without physical access to the machine? You will be saving me a lot of unnecessary time and expense wasted if this is possible.

Thanks a million in advance.



If you can mount the updated image on your machine, you can copy contents from /opt/scripta folder to your miner via SCP. You will also need firmware update file which is located on the FAT partition of the image, i cannot remember which script to use on the miner to update the firmware at the moment - maybe someone else remembers it?

If you don't mind directly editing the miner.conf file for pool settings then only two files are required to be copied:

Updating sgminer and the STM firmware seems to be all that is needed. Both are obviously found in the new image file using something like 7zip to open the archive, then browse to 1.img/opt/bin/scripta/sgminer and 0.fat/GX10.bin. Copy both to your X10, the GX10 file should go in /media/boot. Rebooting should auto-update the STM firmware.

Remember to do
Code:
chmod +x /opt/scripta/bin/sgminer
after you've replaced the old version.

If you want to be able to use the web interface for modifying your pools then a bit more work is required, but I haven't looked into it. After you've copied the new firmware file you can run:

Code:
sudo python /usr/bin/update_fw.py
13  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N / B - Open Source - Confirmed OC Giant B! on: April 11, 2018, 02:43:39 PM
Updating sgminer and the STM firmware seems to be all that is needed. Both are obviously found in the new image file using something like 7zip to open the archive, then browse to 1.img/opt/bin/scripta/sgminer and 0.fat/GX10.bin. Copy both to your X10, the GX10 file should go in /media/boot. Rebooting should auto-update the STM firmware.

Remember to do
Code:
chmod +x /opt/scripta/bin/sgminer
after you've replaced the old version.

14  Alternate cryptocurrencies / Mining (Altcoins) / Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡ on: April 11, 2018, 12:16:42 PM
From the new image:

Code:
Start-Date: 2018-04-08  20:31:58
Commandline: apt-get install secure-delete

Start-Date: 2018-04-08  20:45:48
Commandline: apt-get install testdisk

Covering their tracks this time, then making sure the secure delete worked using the same program used on this thread to extract deleted files. Hi Baikal! Grin
15  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N / B - Open Source - Confirmed OC Giant B! on: April 02, 2018, 09:09:12 AM
Its been brought to my attention from multiple points that this version will OC Baikal Giant B!
Compiling and using my version it will deliver ~10-15% more hashes on LBRY than stock version based on pool side results. Great news for Giant B owners, which im not..!! :-S

Some changes in code and it will deliver even more. Will add a new post when i`ve had access to a Giant B.

Interesting!

  • How many people have confirmed with you that a modified sgminer can overclock a Giant B?
  • Did they share their code changes/improvements with you or give you any idea of what they did?
  • What method did they use to measure the 10-15% increase in hash rate?
  • What do you have in mind for further software changes in order to boost the OC higher?

16  Alternate cryptocurrencies / Mining (Altcoins) / Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡ on: April 02, 2018, 08:55:10 AM
baikal giant B on mineral water my friend, 800hmz is overload but i have laboratory condition for -30 degree, please use 16v dc + 100a

How much current does your overclocked miner draw compared to the stock unmodified miner? Did you find that using 16VDC was necessary or is that only what you had available?


...
msg.data[0] = (clk == 0) ? clk : ((clk / 10) % 20) + 2.2;

this is not ASIC chip .... so the chip frequency is 2 + modulo of + 2.0 + add 0.2 = 10% more power  freq

32 chip X 3 = 96 X 2.2 = 211mhz...

Did you actually try doing that modification?
17  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N - Open Source on: March 30, 2018, 11:36:30 PM
So, I'm confused by the mystic line of code in driver-baikalu.c:

Code:
msg.data[0] = (clk == 0) ? clk : ((clk / 10) % 20) + 2;

I decided to run some common settings.  These resulting values in no way correlate, even if the controller board was accepting input:

mhz  | ((clk / 10) % 20) + 2      
-------------------------------
150   |    17
200   |    2
250   |    7
300   |    12
350   |    17
400   |    2

Perhaps someone smarter can enlighten me?

Also, I found that the following line seems to be leftover from an earlier generation of miner (PiZero_170605_V1.4.img):

Code:
miner->clock        = msg.data[3] << 1;

But I'm not sure why they are bitwise left shifting it.

It seems to me like they're using a lookup table of clock settings to get actual speeds (https://bitcointalk.org/index.php?topic=2790982.msg33090927#msg33090927). If true the max speed might be 490, for a 490/440= 11% overclock (vs 440 stock x10).
18  Alternate cryptocurrencies / Mining (Altcoins) / Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡ on: March 25, 2018, 11:35:47 PM
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.

Nicely done! How many different source files did you need to find and/or modify? When you call baikal_setoption() what arguments do you use? Do you plan on open-sourcing the work you've done or listing the modifications you had to make?
19  Alternate cryptocurrencies / Mining (Altcoins) / Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡ on: March 24, 2018, 10:48:39 PM
Of particular interest is this line:
Code:
msg.data[0] = (clk == 0) ? clk : ((clk / 10) % 20) + 2;
It looks like calling baikal_setoption() allows the clock to be set to an arbitrary value.

To be honest I don't get the point of this part ((clk / 10) % 20) + 2
It just doesn't make any sense to me. If the clock is set to 400 MHz, then the msg.data[0] value will be 2. While if the clock is 300 MHz, then msg.data[0] is 12.
What is the logic here?

[divide by 10] indicates 10MHz increments, [mod 20] indicates a lookup table with 20 items, [+ 2] indicates the list begins at index #2:

Code:
2    400 (Giant B stock)
3    410/210
4    420/220
5    430/230
6    440/240
7    450/250
8    460/260
9    470/270
10   480/280
11   490/290
12   300 (Giant x10 stock)
13   310
14   320
15   330
16   340
17   350
18   360
19   370
20   380
21   390

Not sure whether, for example, #7 would give 450 or 250MHz - an experiment is needed.
20  Alternate cryptocurrencies / Mining (Altcoins) / Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡ on: March 23, 2018, 11:36:48 PM
Here it is.  A slightly modified algorithm.h file:

Thanks. Now I'm interested in:
Code:
int to_baikal_algorithm(algorithm_type_t type);

In a different file:
Code:
#ifdef USE_BAIKAL
int to_baikal_algorithm(algorithm_type_t type)
{
    switch (type) {
    case ALGO_X11:
        return 1;
    case ALGO_X13:
        return 2;
    case ALGO_X14:
        return 3;
    case ALGO_X15:           
        return 4;
    case ALGO_QUARK:       
        return 5;
    case ALGO_QUBIT:
        return 6;   
    default:
        return 0;
        break;
    }
}
#endif

Looks like this is a pretty old version of the source as that list doesn't contain Skein or MGroestl, as the x10 is known to have. This looks like the same list of algorithms that Baikal's older Mini Miner and Giant A900 Dash Miner had so it may not have any new code at all for the x10/B/N (in this deleted version). Maybe it's just as easy as adding a few cases in there for the missing ones and using guess-and-check to get the right values.
Pages: [1] 2 3 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!