Bitcoin Forum

Alternate cryptocurrencies => Mining (Altcoins) => Topic started by: OSMIUMCOIN on January 20, 2018, 11:25:05 AM



Title: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: OSMIUMCOIN on January 20, 2018, 11:25:05 AM
Hi guys ,

https://1.bp.blogspot.com/-WyA1wx6r0b4/WhPZUHn5C4I/AAAAAAAABU8/LZGvk5nj14ICYhfTfW0A-sBcWFwbHyLdACLcBGAs/s320/Bitcoin%2Banimation.gif


Pay 0.2 BTC for working tutorial how to OVERCLOCK Baikal x10
from 300MHz to 400 Mhz


https://i.imgur.com/k9pvI7u.jpg


How to claim 0.2 ? Must show me video on PM

ESCROW


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.1 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: maleemk on January 20, 2018, 01:47:14 PM
Hi guys ,

https://1.bp.blogspot.com/-WyA1wx6r0b4/WhPZUHn5C4I/AAAAAAAABU8/LZGvk5nj14ICYhfTfW0A-sBcWFwbHyLdACLcBGAs/s320/Bitcoin%2Banimation.gif


Pay 0.1 BTC for working tutorial how to OVERCLOCK Baikal x10
from 300MHz to 400 Mhz


https://i.imgur.com/k9pvI7u.jpg


How to claim 0.1 ? Must show me video on PM

ESCROW
Add 0.1 BTC from me also. But needs to by stable and proven.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.1 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Dlikrot on January 20, 2018, 03:27:50 PM
Baikals pictures show them running at 400 somthing, so I think it’s no harm..unless you mine with x11 maybe.

Would like to try it, but 0.1 btc is too steep when I haven’t got many miners..


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.1 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: OSMIUMCOIN on January 22, 2018, 10:29:20 PM
Guys please help :) how to ⚡OVERCLOCK⚡

https://i.imgur.com/k9pvI7u.jpg


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: OSMIUMCOIN on January 22, 2018, 10:44:25 PM
NOW !!! Pay 0.2 BTC for working tutorial how to OVERCLOCK Baikal x10
from 300MHz to 400 Mhz [/size]

https://i.imgur.com/k9pvI7u.jpg


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: bittawm on January 22, 2018, 11:07:00 PM
watching


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: denax on January 23, 2018, 12:32:28 AM
0.2 BTC from me as well, but for someone who could modify the A3 firmware to mine Blake2s instead of Blake2b,  To mine Verge.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: senseless on January 23, 2018, 01:37:56 AM
I just downloaded the X10 firmware for another project. I'll take a look and see what I can find out. If someone would like to give me access to one so I can snoop around a live system I'd appreciate it. I can teamviewer into a PC and then ssh to the miner from there.

0.2 BTC from me as well, but for someone who could modify the A3 firmware to mine Blake2s instead of Blake2b,  To mine Verge.

Probably not possible..


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: senseless on January 23, 2018, 06:03:37 AM
I figured out how to change the clock rate... Anyone care to give me access to their miner to test?

And, looking at the code, I think it'll be possible to get these things to multi-mine too.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: bittawm on January 23, 2018, 06:45:05 AM
I figured out how to change the clock rate... Anyone care to give me access to their miner to test?

And, looking at the code, I think it'll be possible to get these things to multi-mine too.

watching you senseless


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: burnsauce on January 23, 2018, 11:41:25 AM
I figured out how to change the clock rate... Anyone care to give me access to their miner to test?

And, looking at the code, I think it'll be possible to get these things to multi-mine too.
Can you share what you found (or give a hint)? I can poke around myself on a live system and report back.

It would not be possible to give you access to my system, sorry. However, I do think we can work together to solve this.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: fabfab82 on January 23, 2018, 12:15:39 PM
After you guys have found it, could you also have a look at the giant B?  ;D ;D ;D ;D :D ;D


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: senseless on January 23, 2018, 01:24:48 PM

percy_tc has an x10 and is going to allow me to test on his. Once I get confirmation of success I'll let you guys know.



Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: asgardcfr on January 23, 2018, 02:07:56 PM
I have a X10, i look with console and script are located to :/opt/scripta/etc/ for conf and /opt/scripta/bin/sgminer for exe

sgminer version is :5-6-2-1(or l)

So if someone know variable of this version to overclock, you can post here  :)

Up: probably special version because we use "baikal-fan" :"100" ;

Up2:

Code:
sgminer 5.6.2-l
Usage: /opt/scripta/bin/sgminer [-kDdElLLmpPQqUsTouvOchnV]
Options for both config file and command line:
--algorithm|--kernel|-k <arg> Set mining algorithm and most common defaults, default: scrypt
--api-allow <arg>   Allow API access only to the given list of [G:]IP[/Prefix] addresses[/subnets]
--api-description <arg> Description placed in the API status header, default: sgminer version
--api-groups <arg>  API one letter groups G:cmd:cmd[,P:cmd:*...] defining the cmds a groups can use
--api-listen        Enable API, default: disabled
--api-mcast         Enable API Multicast listener, default: disabled
--api-mcast-addr <arg> API Multicast listen address
--api-mcast-code <arg> Code expected in the API Multicast message, don't use '-'
--api-mcast-des <arg> Description appended to the API Multicast reply, default: ''
--api-mcast-port <arg> API Multicast listen port (default: 4028)
--api-network       Allow API (if enabled) to listen on/for any address, default: only 127.0.0.1
--api-port <arg>    Port number of miner API (default: 4028)
--balance           Change multipool strategy from failover to even share balance
--blake-compact     Set SPH_COMPACT_BLAKE64 for Xn derived algorithms (Can give better hashrate for some GPUs)
--compact           Use compact display without per device statistics
--debug|-D          Enable debug output
--debug-log         Enable debug logging when stderr is redirected to file
--default-profile <arg> Set Default Profile
--description <arg> Pool description
--device|-d <arg>   Select device to use, one value, range and/or comma separated (e.g. 0-2,4) default: all
--disable-rejecting Automatically disable pools that continually reject shares
--expiry|-E <arg>   Upper bound on how many seconds after getting work we consider a share from it stale (default: 28)
--event-on <arg>    Select event type to perform task on
--event-runcmd <arg> Command to perform on event
--event-reboot <arg> Reboot the system on event
--event-reboot-delay <arg> Delay in seconds to wait before rebooting
--event-quit <arg>  Quit sgminer on event
--event-quit-message <arg> Quit message when quitting sgminer on event
--failover-only     Don't leak work to backup pools when primary pool is lagging
--failover-switch-delay <arg> Delay in seconds before switching back to a failed pool (default: 60)
--fix-protocol      Do not redirect to a different getwork protocol (eg. stratum)
--incognito         Do not display user name in status window
--hotplug <arg>     Seconds between hotplug checks (0 means never check)
--more-notices      Shows work restart and new block notices, hidden by default
--load-balance      Change multipool strategy from failover to quota based balance
--log|-l <arg>      Interval in seconds between log output (default: 5)
--log-file|-L <arg> Log stderr to file
--log-show-date|-L  Show date on every log line
--lowmem            Minimise caching of shares for low memory applications
--monitor|-m <arg>  Use custom pipe cmd for output messages
--name|--pool-name <arg> Name of pool
--net-delay         Impose small delays in networking to not overload slow routers
--nfactor <arg>     Override default scrypt N-factor parameter.
--no-client-reconnect Disable 'client.reconnect' stratum functionality
--no-restart        Do not attempt to restart GPUs that hang
--no-submit-stale   Don't submit shares if they are detected as stale
--no-extranonce|--pool-no-extranonce Disable 'extranonce' stratum subscribe for pool
--pass|--pool-pass|-p <arg> Password for bitcoin JSON-RPC server
--per-device-stats  Force verbose mode and output per-device statistics
--pool-algorithm|--pool-kernel|--pool-algo <arg> Set algorithm for pool
--pool-backup       Mark this pool as a backup for simple connect strategy
--extranonce|--pool-extranonce <arg> Enable 'extranonce' stratum subscribe for pool
--priority|--pool-priority <arg> Pool priority
--profile-algorithm|--profile-kernel <arg> Set algorithm for profile
--protocol-dump|-P  Verbose dump of protocol-level activities
--queue|-Q <arg>    Minimum number of work items to have queued (0+) (default: 1)
--quiet|-q          Disable logging output, display status and errors
--quota|--pool-quota|-U <arg> quota;URL combination for server with load-balance strategy quotas
--real-quiet        Disable all output
--remove-disabled   Remove disabled devices entirely, as if they didn't exist
--rotate <arg>      Change multipool strategy from failover to regularly rotate at N minutes (default: 0)
--round-robin       Change multipool strategy from failover to round robin on failure
--scan-time|-s <arg> Upper bound on time spent scanning current work, in seconds (default: 60)
--sched-start <arg> Set a time of day in HH:MM to start mining (a once off without a stop time)
--sched-stop <arg>  Set a time of day in HH:MM to stop mining (will quit without a start time)
--sharelog <arg>    Append share log to file
--shares <arg>      Quit after mining N shares (default: unlimited)
--socks-proxy <arg> Set socks4 proxy (host:port)
--show-coindiff     Show coin difficulty rather than hash value of a share
--state|--pool-state <arg> Specify pool state at startup (default: enabled)
--keepalive|--pool-keepalive <arg> Specify pool if keepalived method is used (default: false)
--switcher-mode <arg> Algorithm/gpu settings switcher mode.
--syslog            Use system log for output messages (default: standard error)
--tcp-keepalive <arg> TCP keepalive packet idle time (default: 30)
--text-only|-T      Disable ncurses formatted screen output
--url|--pool-url|-o <arg> URL for bitcoin JSON-RPC server
--usb <arg>         USB device selection
--user|--pool-user|-u <arg> Username for bitcoin JSON-RPC server
--verbose|-v        Log verbose output to stderr as well as status output
--vote <arg>        Optional vote value for decred blocks (default: 0)
--watchpool-refresh <arg> Interval in seconds to refresh pool status (default: 30)
--userpass|--pool-userpass|-O <arg> Username:Password pair for bitcoin JSON-RPC server
--worktime          Display extra work time debug information
--difficulty-multiplier <arg> (deprecated) Difficulty multiplier for jobs received from stratum pools
--baikal-options <arg> Set baikal options clock:recover temp:cutoff temp
--baikal-fan <arg>  Set baikal fan speed(percent)
--enable-nicehashsma Use extra wide display without toggling
Options for command line only:
--config|-c <arg>   Load a JSON-format configuration file
See example.conf for an example configuration.
--default-config <arg> Specify the filename of the default config file
Loaded at start and used when saving without a name.
--remote-config-retry <arg> Number of times to retry downloading remote config file. Default: 3 (default: 3)
--remote-config-wait <arg> Time in seconds to wait between download retries of remote config files. Default: 10secs (default: 10)
--remote-config-usecache Use cached copy of the remote config file when download fails. Default: No
--help|-h           Print this message
--ndevs|-n          Display all USB devices and exit
--version|-V        Display version and exit


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: senseless on January 23, 2018, 08:08:49 PM
After getting access to a X10 I was able to verify that it will NOT work. The baikal-options setting is being completely ignored in this software. I also tried to discover which algos are the ones that are working but hidden. It's not included in this compile of sgminer either. I tried every one it could possibly be to no avail.

I'm still working on it. It'll just take a little longer than expected.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: coingotrade on January 23, 2018, 09:12:02 PM
I have successfuly overclocked the miner to 400mhz, however the controller's firmware has a fixed hashrate so overclocking makes 0 difference.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Nokio2010 on January 24, 2018, 07:26:59 AM
NOW !!! Pay 0.2 BTC for working tutorial how to OVERCLOCK Baikal x10
from 300MHz to 400 Mhz [/size]

https://i.imgur.com/k9pvI7u.jpg

Can you show the screen with overclocked system?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: asgardcfr on January 24, 2018, 09:58:39 AM
I can overclock to 1Ghz with no evidence, please give me all your money :)  ;D


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: DVD_GR on January 24, 2018, 10:32:47 AM
pi zero can also be overclocked :D


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Baikalek on January 27, 2018, 08:08:05 AM
Here (https://youtu.be/aON6WXmdLm8) on the video you can see that the chips are running at 420 Mhz. But even so, the hashrate is as good as the chips at 300 Mhz. Because Baikal Giant X10 has two hashrate of 5 and 10 GH, I think the frequencies will be set for each algorithm separately.

https://i.imgur.com/2E0VP0r.jpg


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: OSMIUMCOIN on January 27, 2018, 08:28:53 AM
Here (https://youtu.be/aON6WXmdLm8) on the video you can see that the chips are running at 420 Mhz. But even so, the hashrate is as good as the chips at 300 Mhz. Because Baikal Giant X10 has two hashrate of 5 and 10 GH, I think the frequencies will be set for each algorithm separately.

https://i.imgur.com/2E0VP0r.jpg

OC Working or not ? hash rate up , more than 10GHS ?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: percy_tc on January 27, 2018, 09:40:32 AM
Looks like it stays on 10GH/s.

Show us a print screen of improved hashrate please.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tothanhtuan on January 27, 2018, 11:27:22 AM
You have any evidence to show your proof? anyone sends him money ?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Baikalek on January 27, 2018, 12:16:35 PM
Please look at my post attentively. There is a link to the video. That's not my job. I just noticed that no matter the chip frequency 300 or 420, hashrate is the same!


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Baikalek on January 27, 2018, 05:37:10 PM
This could also help with how Baikal Goant X10 updates with three algorithms for five algorithms. Does anyone have experience with this? Someone was upgraded. How?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: senseless on January 28, 2018, 11:24:18 AM

I sent in an email asking them to release their firmware and software.



Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Baikalek on January 28, 2018, 03:12:51 PM

I sent in an email asking them to release their firmware and software.


And you upgraded from three algorithms to five algorithms? How? Only Orage Pi or FW on hashboards?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Ironeinstein on January 29, 2018, 06:45:13 PM
If anyone has access to a Giant B and would be willing to upload the firmware, please let me know. I've been working on an overclock for a while, and from what I can tell the frequency multiplier is either hard-coded into the firmware of the STM32 chip, or hard-coded into the ASICs. I'm ordering parts now to try a hardware mod to see if an overclock is even possible.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: OSMIUMCOIN on January 30, 2018, 10:01:36 PM
If anyone has access to a Giant B and would be willing to upload the firmware, please let me know. I've been working on an overclock for a while, and from what I can tell the frequency multiplier is either hard-coded into the firmware of the STM32 chip, or hard-coded into the ASICs. I'm ordering parts now to try a hardware mod to see if an overclock is even possible.

https://github.com/baikalminer/GB/tree/master/orangepi


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: darkly spectre on February 01, 2018, 02:13:21 AM
yeah judging by the difficulty this is going a hard mod might be necessary to get rid of hardware related limitations

if somebody can do it.

il throw another 0.1 BTC at you


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tboy32c on February 02, 2018, 01:36:26 PM
If anyone has access to a Giant B and would be willing to upload the firmware, please let me know. I've been working on an overclock for a while, and from what I can tell the frequency multiplier is either hard-coded into the firmware of the STM32 chip, or hard-coded into the ASICs. I'm ordering parts now to try a hardware mod to see if an overclock is even possible.

https://github.com/baikalminer/GB/tree/master/orangepi

I think Ironeinstein was referring to the STM (chip on blue controller board) firmware, not the OrangePi firmware. The STM firmware does not come in baikalminer's github image. Someone with actual access (can be remote SSH) to a Giant-B would need to be willing to run a few commands on their miner to pull the firmware off of it. This file would be helpful in determining if a software overclock on the x10 is possible.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Baikalek on February 03, 2018, 10:47:20 AM
Code:
root@Baikal:~# lshw
baikal
    description: Computer
    width: 32 bits
  *-core
       description: Motherboard
       physical id: 0
     *-memory
          description: System memory
          physical id: 0
          size: 193MiB
     *-cpu:0
          physical id: 1
          bus info: cpu@0
          size: 816MHz
          capacity: 1008MHz
          capabilities: cpufreq
     *-cpu:1
          physical id: 2
          bus info: cpu@1
          size: 816MHz
          capacity: 1008MHz
          capabilities: cpufreq
     *-cpu:2
          physical id: 3
          bus info: cpu@2
          size: 816MHz
          capacity: 1008MHz
          capabilities: cpufreq
     *-cpu:3
          physical id: 4
          bus info: cpu@3
          size: 816MHz
          capacity: 1008MHz
          capabilities: swp half thumb fastmult vfp edsp thumbee neon vfpv3 tls vfpv4 idiva idivt cpufreq
  *-usbhost:0
       product: SW USB2.0 'Open' Host Controller (OHCI) Driver
       vendor: Linux 3.4.39 ohci_hcd
       physical id: 1
       bus info: usb@8
       logical name: usb8
       version: 3.04
       capabilities: usb-1.10
       configuration: driver=hub slots=1 speed=12Mbit/s
  *-usbhost:1
       product: SW USB2.0 'Open' Host Controller (OHCI) Driver
       vendor: Linux 3.4.39 ohci_hcd
       physical id: 2
       bus info: usb@7
       logical name: usb7
       version: 3.04
       capabilities: usb-1.10
       configuration: driver=hub slots=1 speed=12Mbit/s
     *-usb
          description: Communication device
          product: Baikal Miner
          vendor: Baikal
          physical id: 1
          bus info: usb@7:1
          version: 2.00
          serial: BKLU
          capabilities: usb-2.00
          configuration: driver=usbfs maxpower=100mA speed=12Mbit/s
  *-usbhost:2
       product: SW USB2.0 'Open' Host Controller (OHCI) Driver
       vendor: Linux 3.4.39 ohci_hcd
       physical id: 3
       bus info: usb@6
       logical name: usb6
       version: 3.04
       capabilities: usb-1.10
       configuration: driver=hub slots=1 speed=12Mbit/s
  *-usbhost:3
       product: SW USB2.0 'Open' Host Controller (OHCI) Driver
       vendor: Linux 3.4.39 ohci_hcd
       physical id: 4
       bus info: usb@5
       logical name: usb5
       version: 3.04
       capabilities: usb-1.10
       configuration: driver=hub slots=1 speed=12Mbit/s
  *-usbhost:4
       product: SW USB2.0 'Enhanced' Host Controller (EHCI) Driver
       vendor: Linux 3.4.39 ehci_hcd
       physical id: 5
       bus info: usb@4
       logical name: usb4
       version: 3.04
       capabilities: usb-2.00
       configuration: driver=hub slots=1 speed=480Mbit/s
  *-usbhost:5
       product: SW USB2.0 'Enhanced' Host Controller (EHCI) Driver
       vendor: Linux 3.4.39 ehci_hcd
       physical id: 6
       bus info: usb@3
       logical name: usb3
       version: 3.04
       capabilities: usb-2.00
       configuration: driver=hub slots=1 speed=480Mbit/s
  *-usbhost:6
       product: SW USB2.0 'Enhanced' Host Controller (EHCI) Driver
       vendor: Linux 3.4.39 ehci_hcd
       physical id: 7
       bus info: usb@2
       logical name: usb2
       version: 3.04
       capabilities: usb-2.00
       configuration: driver=hub slots=1 speed=480Mbit/s
  *-usbhost:7
       product: SW USB2.0 'Enhanced' Host Controller (EHCI) Driver
       vendor: Linux 3.4.39 ehci_hcd
       physical id: 8
       bus info: usb@1
       logical name: usb1
       version: 3.04
       capabilities: usb-2.00
       configuration: driver=hub slots=1 speed=480Mbit/s
  *-network
       description: Ethernet interface
       physical id: 9
       logical name: eth0
       serial: c2:47:93:ac:13:83
       size: 100Mbit/s
       capacity: 100Mbit/s
       capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=sunxi_geth driverversion=SUNXI Gbgit driver V1.1 duplex=full ip=10.12.14.111 link=yes multicast=yes port=MII speed=100Mbit/s
Here's HWINFO from UBUNTU.

Code:
root@Baikal:/opt/scripta/bin# ./sgminer -n
[11:39:32] USB all: found 9 devices - listing known devices
.USB dev 0: Bus 7 Device 2 ID: 0483:5740
  Manufacturer: 'Baikal'
  Product: 'Baikal Miner'
Here's USBINFO from SGMINER.

In the \ usr \ bin folder then the update_fw.py file is with this content (maybe it will help):
Code:
#!/usr/bin/env python
import subprocess
import os
import sys
from subprocess import Popen, PIPE
import fcntl
import time
import glob
tmpfile = '/home/baikal/tmp.bin'
path = '/media/boot/G*.bin'
fwfile = glob.glob(path)
if not fwfile:
print 'No firmware'
sys.exit()

USBDEVFS_RESET= 21780

# enter dfu mode
def enter_dfumode():
  subprocess.call('echo 0 > /sys/class/gpio_sw/PA18/data', shell=True)
  subprocess.call('echo 0 > /sys/class/gpio_sw/PA10/data', shell=True)
  subprocess.call('echo 1 > /sys/class/gpio_sw/PA10/data', shell=True)

def exit_dfumode():
  subprocess.call('echo 1 > /sys/class/gpio_sw/PA18/data', shell=True)
  subprocess.call('echo 0 > /sys/class/gpio_sw/PA10/data', shell=True)
  subprocess.call('echo 1 > /sys/class/gpio_sw/PA10/data', shell=True)

def reset_usb(driver):
  try:
    lsusb_out = Popen("lsusb | grep -i %s"%driver, shell=True, bufsize=64, stdin=PIPE, stdout=PIPE, close_fds=True).stdout.read().strip().split()
    bus = lsusb_out[1]
    device = lsusb_out[3][:-1]
    f = open("/dev/bus/usb/%s/%s"%(bus, device), 'w', os.O_WRONLY)
    fcntl.ioctl(f, USBDEVFS_RESET, 0)
  except Exception, msg:
    print ""

def update_firmware():
  enter_dfumode()
  reset_usb("DFU")
  print 'Downloading... ' + fwfile[0]
  cmd = 'sudo dfu-util -a 0 -d 0483:df11 -s 0x08000000:leave -D ' + fwfile[0]
  subprocess.call(cmd, shell=True)
  cmd = 'sudo rm -rf ' + path
  subprocess.call(cmd, shell=True)

enter_dfumode()
reset_usb("STM32F407")
reset_usb("DFU")
update_firmware()
exit_dfumode()

print "Done"

Please type the commands I can download FW from the X10 miner. Not from OpenPI.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Baikalek on February 03, 2018, 11:45:12 AM
With the command: 
Code:
sudo dfu-util -a 0 -d 0483:df11 -s 0x08000000:leave -U /home/baikal/tmp.bin
I probably got FW boards.
I do not know what to do next.
Here's the file. (http://leteckaposta.cz/473537086)


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tboy32c on February 03, 2018, 12:08:21 PM
With the command: 
Code:
sudo dfu-util -a 0 -d 0483:df11 -s 0x08000000:leave -U /home/baikal/tmp.bin
I probably got FW boards.
I do not know what to do next.
Here's the file. (http://leteckaposta.cz/473537086)

That's good but someone with a Giant-B needs to do it.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Ironeinstein on February 03, 2018, 06:17:24 PM
Bumping this thread up. If anyone has access to a Giant B, please run this command and upload the file somewhere. This will help significantly with overclocking both the X10 and Giant B.

Code:
sudo dfu-util -a 0 -d 0483:df11 -s 0x08000000:leave -U /home/baikal/tmp.bin

If you have access to a Giant B and need more explicit instructions, just let me know.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Baikalek on February 03, 2018, 06:29:41 PM
Bumping this thread up. If anyone has access to a Giant B, please run this command and upload the file somewhere. This will help significantly with overclocking both the X10 and Giant B.

Code:
sudo dfu-util -a 0 -d 0483:df11 -s 0x08000000:leave -U /home/baikal/tmp.bin

If you have access to a Giant B and need more explicit instructions, just let me know.

Possible USB adress could be different (0483:df11), first look at the file \usr\bin\update_fw.py
and the command dfu-util needs to be run in the usr\bin\


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 03, 2018, 06:33:40 PM
Hello Gang!

I'd like to say thank you to all of you first, as reading this has inspired me to reveal some interesting news.

If any of you have the Giant B or X10 Images downloaded, you will see if you diggggggggggggg  deeply. They left some crumbs.

Hint, GZIP.

You will see that the Baikal Team has already implemented use of Cryptonight and Cryptonight-lite in the Giant B image prior to release with the Monero and Aeon coins.

See below..........

  <h4>Monero Pools</h4>
    <p class="help-block" ng-show="settings.userHelp">
      Click to add pool to pool's list
    </p>
   
     <div class="list-group">       
     <a href="" ng-click="poolAdd({url:'stratum+tcp://pool.supportxmr.com:7777',pass:'x',priority:'0',algo:'cryptonight'})" class="list-group-item">SupportXMR</a>       
   <a href="" ng-click="poolAdd({url:'stratum+tcp://mine.xmrpool.net:7778',pass:'x',priority:'0',algo:'cryptonight'})" class="list-group-item">XMRPool</a>           
        <a href="" ng-click="poolAdd({url:'stratum+tcp://xmr-eu.dwarfpool.com:8050',pass:'x',priority:'0',algo:'cryptonight'})" class="list-group-item">DwarfPool</a>
        <a href="" ng-click="poolAdd({url:'stratum+tcp://xmr-asia1.nanopool.org:14444',pass:'x',priority:'0',algo:'cryptonight'})" class="list-group-item">NanoPool</a>               
        <a href="" ng-click="poolAdd({url:'stratum+tcp://cryptonight.hk.nicehash.com:3355',pass:'x',priority:'0',algo:'cryptonight'})" class="list-group-item">Nicehash</a>                       
    </div>
    <h4>Aeon Pools</h4>
    <p class="help-block" ng-show="settings.userHelp">
      Click to add pool to pool's list
    </p>

    <div class="list-group">
       <a href="" ng-click="poolAdd({url:'stratum+tcp://pool.aeonminingpool.com:3333',pass:'x',priority:'0',algo:'cryptonight-lite'})" class="list-group-item">AeonMiningPool</a>
        <a href="" ng-click="poolAdd({url:'stratum+tcp://aeon.sumominer.com:3333',pass:'x',priority:'0',algo:'cryptonight-lite'})" class="list-group-item">Sumominer</a>       
        <a href="" ng-click="poolAdd({url:'stratum+tcp://aeon.[Suspicious link removed]:7777',pass:'x',priority:'0',algo:'cryptonight-lite'})" class="list-group-item">RuPool</a>
    </div>   

 
  </div>
   
  <div class="col-sm-12 col-md-9 pull-right">
      <div class="clearfix">
         <div class="pull-right">
            <br />
            <p>
               <button type="button" ng-click="minerRestart=1" class="btn btn-warning">Miner commands</button>
            </p>
            <p class="help-block" ng-show="minerRestart&&settings.userHelp">
               Ordered from gentle to rough.
            </p>
            <div class="list-group" ng-show="minerRestart">
               <a title="Reset miner" href="" ng-click="cgminer('restart')" class="list-group-item">Cgminer soft reset (RPC)</a>
               <!--<a title="Start miner" href="" ng-click="cgminerHardCtl('1')" class="list-group-item">Start</a> -->
               <a title="Restart miner" href="" ng-click="cgminerHardCtl('0')" class="list-group-item">Restart cgminer linux process(30s)</a>
               <!--<a title="Shutdown your PI (be careful!)" href="" id="link_shutdown" onclick="ctrl_host(1)" class="list-group-item">Shutdown</a> -->
               <!--<a title="Reboot your PI" href="" id="link_reboot"  onclick="ctrl_host(0)" class="list-group-item">Reboot</a> -->
            </div>
         </div>
      </div>

    <h3>Pools</h3>

    <p class="help-block" ng-show="settings.userHelp">
      The settings below serve as direct input to the miner. <strong>One little error can and will let the miner crash.</strong>
    </p>
    <form name="poolForm" class="form-horizontal">
      <div class="row">
        <label class="col-sm-4">URL</label>
        <label class="col-sm-3">Algo</label>
        <label class="col-sm-3">User</label>
        <label class="col-sm-1">Pass</label>
        <label class="col-sm-1">Priority</label>
      </div>
      <div class="form-group" ng-repeat="pool in pools">
        <div class="col-sm-4">
          <input type="text" ng-model="pool.url" class="form-control" required>
        </div>
       
        <div class="col-sm-3">           
                 <select class="form-control" ng-model="pool.algo" required>
                   <option>cryptonight</option>                   
                   <option>cryptonight-lite</option>
                 </select>               
         </div>
       
        <div class="col-sm-3">
          <input type="text" ng-model="pool.user" class="form-control" required>
        </div>
      <div class="col-sm-1">
          <input type="text" ng-model="pool.pass" class="form-control" required>
      </div>


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Baikalek on February 03, 2018, 06:36:42 PM
Still, capable people. If you come to the way to change the clock or activate the hidden algo on the X10. Please do not The secrets it. I've been doing it for days and trying to share all my knowledge.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Baikalek on February 03, 2018, 06:43:05 PM
Hello Gang!

I'd like to say thank you to all of you first, as reading this has inspired me to reveal some interesting news.

If any of you have the Giant B or X10 Images downloaded, you will see if you diggggggggggggg  deeply. They left some crumbs.

Hint, GZIP.

You will see that the Baikal Team has already implemented use of Cryptonight and Cryptonight-lite in the Giant B image prior to release with the Monero and Aeon coins.

See below..........
Code:
  <h4>Monero Pools</h4>
    <p class="help-block" ng-show="settings.userHelp">
      Click to add pool to pool's list
    </p>
   
  <div class="list-group">       
  <a href="" ng-click="poolAdd({url:'stratum+tcp://pool.supportxmr.com:7777',pass:'x',priority:'0',algo:'cryptonight'})" class="list-group-item">SupportXMR</a>       
<a href="" ng-click="poolAdd({url:'stratum+tcp://mine.xmrpool.net:7778',pass:'x',priority:'0',algo:'cryptonight'})" class="list-group-item">XMRPool</a> 
        <a href="" ng-click="poolAdd({url:'stratum+tcp://xmr-eu.dwarfpool.com:8050',pass:'x',priority:'0',algo:'cryptonight'})" class="list-group-item">DwarfPool</a>
        <a href="" ng-click="poolAdd({url:'stratum+tcp://xmr-asia1.nanopool.org:14444',pass:'x',priority:'0',algo:'cryptonight'})" class="list-group-item">NanoPool</a>               
        <a href="" ng-click="poolAdd({url:'stratum+tcp://cryptonight.hk.nicehash.com:3355',pass:'x',priority:'0',algo:'cryptonight'})" class="list-group-item">Nicehash</a>                       
    </div>
    <h4>Aeon Pools</h4>
    <p class="help-block" ng-show="settings.userHelp">
      Click to add pool to pool's list
    </p>

    <div class="list-group">
    <a href="" ng-click="poolAdd({url:'stratum+tcp://pool.aeonminingpool.com:3333',pass:'x',priority:'0',algo:'cryptonight-lite'})" class="list-group-item">AeonMiningPool</a>
        <a href="" ng-click="poolAdd({url:'stratum+tcp://aeon.sumominer.com:3333',pass:'x',priority:'0',algo:'cryptonight-lite'})" class="list-group-item">Sumominer</a>       
        <a href="" ng-click="poolAdd({url:'stratum+tcp://aeon.[Suspicious link removed]:7777',pass:'x',priority:'0',algo:'cryptonight-lite'})" class="list-group-item">RuPool</a>
    </div>   

 
  </div>
   
  <div class="col-sm-12 col-md-9 pull-right">
<div class="clearfix">
<div class="pull-right">
<br />
<p>
<button type="button" ng-click="minerRestart=1" class="btn btn-warning">Miner commands</button>
</p>
<p class="help-block" ng-show="minerRestart&&settings.userHelp">
Ordered from gentle to rough.
</p>
<div class="list-group" ng-show="minerRestart">
<a title="Reset miner" href="" ng-click="cgminer('restart')" class="list-group-item">Cgminer soft reset (RPC)</a>
<!--<a title="Start miner" href="" ng-click="cgminerHardCtl('1')" class="list-group-item">Start</a> -->
<a title="Restart miner" href="" ng-click="cgminerHardCtl('0')" class="list-group-item">Restart cgminer linux process(30s)</a>
<!--<a title="Shutdown your PI (be careful!)" href="" id="link_shutdown" onclick="ctrl_host(1)" class="list-group-item">Shutdown</a> -->
<!--<a title="Reboot your PI" href="" id="link_reboot"  onclick="ctrl_host(0)" class="list-group-item">Reboot</a> -->
</div>
</div>
</div>

    <h3>Pools</h3>

    <p class="help-block" ng-show="settings.userHelp">
      The settings below serve as direct input to the miner. <strong>One little error can and will let the miner crash.</strong>
    </p>
    <form name="poolForm" class="form-horizontal">
      <div class="row">
        <label class="col-sm-4">URL</label>
        <label class="col-sm-3">Algo</label>
        <label class="col-sm-3">User</label>
        <label class="col-sm-1">Pass</label>
        <label class="col-sm-1">Priority</label>
      </div>
      <div class="form-group" ng-repeat="pool in pools">
        <div class="col-sm-4">
          <input type="text" ng-model="pool.url" class="form-control" required>
        </div>
       
        <div class="col-sm-3">       
  <select class="form-control" ng-model="pool.algo" required>
    <option>cryptonight</option>   
    <option>cryptonight-lite</option>
  </select>
      </div>
       
        <div class="col-sm-3">
          <input type="text" ng-model="pool.user" class="form-control" required>
        </div>
      <div class="col-sm-1">
          <input type="text" ng-model="pool.pass" class="form-control" required>
      </div>


It is a question of whether they are developing new models.

It's a real thing. In the Baikal X10 several files with NIST5 and GROESTL algo were found. For example in command history Baikal user:
Code:
# Registers:
"0 CHAR 0
5
"1 LINE 0
                             poolAdd({url:'stratum+tcp://77.249.213.25:7903',pass:'x',priority:'3',algo:'x11'});
"2 LINE 0
                             7903',pass:'111',priority:'1',algo:'x11'});
"3 LINE 0
    <option>groestl</option>
"4 LINE 0
    <option>nist5</option>
"5 LINE 0
                             poolAdd({url:'stratum+tcp://nist5.mine.zpool.ca:3833',pass:'x11=1,quark=1,qubit=1,groestl=1,nist5=1',priority:'6',algo:'nist5',extranonce:true});
"6 LINE 0
                             poolAdd({url:'stratum+tcp://groestl.mine.zpool.ca:5333',pass:'x11=1,quark=1,qubit=1,groestl=1,nist5=1',priority:'5',algo:'groestl',extranonce:true});
"7 LINE 0
     poolAdd({url:'stratum+tcp://nist5.eu.nicehash.com:3340',pass:'x',priority:'3',algo:'nist5',extranonce:true});
"8 LINE 0
                             poolAdd({url:'stratum+tcp://qubit.mine.zpool.ca:4733',pass:'x11=0.5,x13=0.5,x14=0.5,x15=0.5,quark=0.5,qubit=0.5',priority:'5',algo:'qubit',extranonce:true});
"9 LINE 0
                             poolAdd({url:'stratum+tcp://quark.mine.zpool.ca:4033',pass:'x11=0.5,x13=0.5,x14=0.5,x15=0.5,quark=0.5,qubit=0.5',priority:'4',algo:'quark',extranonce:true});
""- CHAR 0
2


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 03, 2018, 06:47:51 PM
There's no need to develop new models.

Just make one hardware and sell multiple versions of it.

They will probably have 3-4 versions of the GB and X10.

Make more money and mass produce the same box. Easier support and part replacements.

And in the mean time they use the miners to make thousands per machine daily until they decide to release it, where then they make money on the machine.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: bitcoinexplorer on February 03, 2018, 06:49:51 PM
There's no need to develop new models.

Just make one hardware and sell multiple versions of it.

They will probably have 3-4 versions of the GB and X10.

Make more money and mass produce the same box. Easier support and part replacements.

And in the mean time they use the miners to make thousands per machine daily until they decide to release it, where then they make money on the machine.


Are you from Cuba? If yes Cuba allows mining?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Baikalek on February 03, 2018, 06:52:05 PM
There's no need to develop new models.

Just make one hardware and sell multiple versions of it.

They will probably have 3-4 versions of the GB and X10.

Make more money and mass produce the same box. Easier support and part replacements.

And in the mean time they use the miners to make thousands per machine daily until they decide to release it, where then they make money on the machine.

Even this version could be true :-)


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 03, 2018, 06:55:17 PM
Just thought I'd drop off one more piece of good news.

This was inside the X10 image.
File name: miner.html-gzip-1547-8889-1508339623       
Dated 10/18/2017

Notice, Nist5 and Groestl were options in the drop down.

Gotta love Scripta, lol.


        <div class="col-sm-2">           
                 <select class="form-control" ng-model="pool.algo" required>
                   <option>x11</option>                   
                   <option>quark</option>
                   <option>qubit</option>                   
                   <option>nist5</option>
                   <option>skein</option>
                   <option>groestl</option>
                   <option>myr-gr</option>                   
                 </select>               
         </div>


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Baikalek on February 03, 2018, 07:08:15 PM
Just thought I'd drop off one more piece of good news.

This was inside the X10 image.
File name: miner.html-gzip-1547-8889-1508339623       
Dated 10/18/2017

Notice, Nist5 and Groestl were options in the drop down.

Gotta love Scripta, lol.

Code:

        <div class="col-sm-2">       
  <select class="form-control" ng-model="pool.algo" required>
    <option>x11</option>   
    <option>quark</option>
    <option>qubit</option>   
    <option>nist5</option>
    <option>skein</option>
    <option>groestl</option>
    <option>myr-gr</option>   
  </select>
      </div>
Code:
xxx

Please enter long source code into xxx.
Between labels [ code] and [ /code] without space [_c.....


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 03, 2018, 07:17:20 PM
Anyone noticed Baikal updated they're firmware on the Giant B????

I had previously downloaded PiZero_GB_171221_V1.0.

Now I revisited the site and its changed to PiZero_GB_180105_V1.0.

What the heck are they up to.... ???


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 03, 2018, 09:47:52 PM
So far what I can understand.

Giant X10 is running Custom Version of SGMiner 5.6.2-L
Giant B is running Custom Version of SGMiner 5.6.2-B

Hardware seems to not be a differentiator here, only the code.

Unless someone can decompile these files and enable the other algo's, we aren't getting anywhere.
 


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Saingo on February 05, 2018, 04:32:44 AM
Hello Gang!

I'd like to say thank you to all of you first, as reading this has inspired me to reveal some interesting news.

If any of you have the Giant B or X10 Images downloaded, you will see if you diggggggggggggg  deeply. They left some crumbs.

Hint, GZIP.

You will see that the Baikal Team has already implemented use of Cryptonight and Cryptonight-lite in the Giant B image prior to release with the Monero and Aeon coins.

See below..........

  <h4>Monero Pools</h4>
    <p class="help-block" ng-show="settings.userHelp">
      Click to add pool to pool's list
    </p>
   
     <div class="list-group">       
     <a href="" ng-click="poolAdd({url:'stratum+tcp://pool.supportxmr.com:7777',pass:'x',priority:'0',algo:'cryptonight'})" class="list-group-item">SupportXMR</a>       
   <a href="" ng-click="poolAdd({url:'stratum+tcp://mine.xmrpool.net:7778',pass:'x',priority:'0',algo:'cryptonight'})" class="list-group-item">XMRPool</a>           
        <a href="" ng-click="poolAdd({url:'stratum+tcp://xmr-eu.dwarfpool.com:8050',pass:'x',priority:'0',algo:'cryptonight'})" class="list-group-item">DwarfPool</a>
        <a href="" ng-click="poolAdd({url:'stratum+tcp://xmr-asia1.nanopool.org:14444',pass:'x',priority:'0',algo:'cryptonight'})" class="list-group-item">NanoPool</a>               
        <a href="" ng-click="poolAdd({url:'stratum+tcp://cryptonight.hk.nicehash.com:3355',pass:'x',priority:'0',algo:'cryptonight'})" class="list-group-item">Nicehash</a>                       
    </div>
    <h4>Aeon Pools</h4>
    <p class="help-block" ng-show="settings.userHelp">
      Click to add pool to pool's list
    </p>

    <div class="list-group">
       <a href="" ng-click="poolAdd({url:'stratum+tcp://pool.aeonminingpool.com:3333',pass:'x',priority:'0',algo:'cryptonight-lite'})" class="list-group-item">AeonMiningPool</a>
        <a href="" ng-click="poolAdd({url:'stratum+tcp://aeon.sumominer.com:3333',pass:'x',priority:'0',algo:'cryptonight-lite'})" class="list-group-item">Sumominer</a>       
        <a href="" ng-click="poolAdd({url:'stratum+tcp://aeon.[Suspicious link removed]:7777',pass:'x',priority:'0',algo:'cryptonight-lite'})" class="list-group-item">RuPool</a>
    </div>   

 
  </div>
   
  <div class="col-sm-12 col-md-9 pull-right">
      <div class="clearfix">
         <div class="pull-right">
            <br />
            <p>
               <button type="button" ng-click="minerRestart=1" class="btn btn-warning">Miner commands</button>
            </p>
            <p class="help-block" ng-show="minerRestart&&settings.userHelp">
               Ordered from gentle to rough.
            </p>
            <div class="list-group" ng-show="minerRestart">
               <a title="Reset miner" href="" ng-click="cgminer('restart')" class="list-group-item">Cgminer soft reset (RPC)</a>
               <!--<a title="Start miner" href="" ng-click="cgminerHardCtl('1')" class="list-group-item">Start</a> -->
               <a title="Restart miner" href="" ng-click="cgminerHardCtl('0')" class="list-group-item">Restart cgminer linux process(30s)</a>
               <!--<a title="Shutdown your PI (be careful!)" href="" id="link_shutdown" onclick="ctrl_host(1)" class="list-group-item">Shutdown</a> -->
               <!--<a title="Reboot your PI" href="" id="link_reboot"  onclick="ctrl_host(0)" class="list-group-item">Reboot</a> -->
            </div>
         </div>
      </div>

    <h3>Pools</h3>

    <p class="help-block" ng-show="settings.userHelp">
      The settings below serve as direct input to the miner. <strong>One little error can and will let the miner crash.</strong>
    </p>
    <form name="poolForm" class="form-horizontal">
      <div class="row">
        <label class="col-sm-4">URL</label>
        <label class="col-sm-3">Algo</label>
        <label class="col-sm-3">User</label>
        <label class="col-sm-1">Pass</label>
        <label class="col-sm-1">Priority</label>
      </div>
      <div class="form-group" ng-repeat="pool in pools">
        <div class="col-sm-4">
          <input type="text" ng-model="pool.url" class="form-control" required>
        </div>
       
        <div class="col-sm-3">           
                 <select class="form-control" ng-model="pool.algo" required>
                   <option>cryptonight</option>                   
                   <option>cryptonight-lite</option>
                 </select>               
         </div>
       
        <div class="col-sm-3">
          <input type="text" ng-model="pool.user" class="form-control" required>
        </div>
      <div class="col-sm-1">
          <input type="text" ng-model="pool.pass" class="form-control" required>
      </div>


Im willing to use my baikal giant B as a test subject. Let me know what you need.
If we can figure an overclock or a new algo that would be great!


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 05, 2018, 04:39:17 AM
Upon further digging and using recovery tools. I’m not 100% sure but I believe I might have been able to extract the usb Baikal driver files.

Does anyone know how to add drivers to the build and compile the latest version of sgminer, which contains the missing algos?

I will post the complete recovered files of what I found for both the X10 and GB later.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Saingo on February 05, 2018, 04:50:23 AM
Upon further digging and using recovery tools. I’m not 100% sure but I believe I might have been able to extract the usb Baikal driver files.

Does anyone know how to add drivers to the build and compile the latest version of sgminer, which contains the missing algos?

I will post the complete recovered files of what I found for both the X10 and GB later.


I think they released a update for x10 before from 3 to 5 algos. So i am sure there is a manual online somewhere. Ps you can use my baikal giant b as ecperiment? If need be you can use teamviewer to connect


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 05, 2018, 05:00:59 AM
If the new image that upgrades the x10 from 3 to 5 algorithms contains a bin file in the boot folder means that the hardware itself needs additional coding to allow the new algorithms. If the image doesn’t contain a bin file in the boot folder then the algorithms can be added by modifying the sgminer file.

If someone can share with me the original OrangePi image for 3 algorithms and also the image that updates the x10 to 5 algorithms I will be able to confirm this theory.

My point is that we all have the same machines. X10 is the Giant B, just restricted on algos and frequency.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Baikalek on February 05, 2018, 06:03:37 AM
Quote
Im willing to use my baikal giant B as a test subject. Let me know what you need.
If we can figure an overclock or a new algo that would be great!

Please try this on Giant B: https://bitcointalk.org/index.php?topic=2790982.msg29541197#msg29541197


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Thopf on February 05, 2018, 06:27:12 AM
Quote
Im willing to use my baikal giant B as a test subject. Let me know what you need.
If we can figure an overclock or a new algo that would be great!

Please try this on Giant B: https://bitcointalk.org/index.php?topic=2790982.msg29541197#msg29541197

Hello ,
this comes up..

dfu-util: No DFU capable USB device available
baikal@Baikal:~$ dfu-util
dfu-util 0.8


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Baikalek on February 05, 2018, 06:35:41 AM
Quote
Im willing to use my baikal giant B as a test subject. Let me know what you need.
If we can figure an overclock or a new algo that would be great!

Please try this on Giant B: https://bitcointalk.org/index.php?topic=2790982.msg29541197#msg29541197

Hello ,
this comes up..

dfu-util: No DFU capable USB device available
baikal@Baikal:~$ dfu-util
dfu-util 0.8

OK, then:
- backup your \usr\bin\update_fw.py
- edit this file via SFTP red must be change
Code:
#!/usr/bin/env python
import subprocess
import os
import sys
from subprocess import Popen, PIPE
import fcntl
import time
import glob
tmpfile = '/home/baikal/tmp.bin'
path = '/media/boot/G*.bin'
fwfile = glob.glob(path)
if not fwfile:
   print 'No firmware'
   sys.exit()
Code:
	
USBDEVFS_RESET= 21780

# enter dfu mode
def enter_dfumode():
  subprocess.call('echo 0 > /sys/class/gpio_sw/PA18/data', shell=True)
  subprocess.call('echo 0 > /sys/class/gpio_sw/PA10/data', shell=True)
  subprocess.call('echo 1 > /sys/class/gpio_sw/PA10/data', shell=True)

def exit_dfumode():
  subprocess.call('echo 1 > /sys/class/gpio_sw/PA18/data', shell=True)
  subprocess.call('echo 0 > /sys/class/gpio_sw/PA10/data', shell=True)
  subprocess.call('echo 1 > /sys/class/gpio_sw/PA10/data', shell=True)

def reset_usb(driver):
  try:
    lsusb_out = Popen("lsusb | grep -i %s"%driver, shell=True, bufsize=64, stdin=PIPE, stdout=PIPE, close_fds=True).stdout.read().strip().split()
    bus = lsusb_out[1]
    device = lsusb_out[3][:-1]
    f = open("/dev/bus/usb/%s/%s"%(bus, device), 'w', os.O_WRONLY)
    fcntl.ioctl(f, USBDEVFS_RESET, 0)
  except Exception, msg:
    print ""

def update_firmware():
  enter_dfumode()
  reset_usb("DFU")
  print 'Downloading... ' + fwfile[0]
 cmd = 'sudo dfu-util -a 0 -d 0483:df11 -s 0x08000000:leave -U /home/baikal/tmp.bin'
Code:
  subprocess.call(cmd, shell=True)
  cmd = 'sudo rm -rf ' + path
  subprocess.call(cmd, shell=True)

enter_dfumode()
reset_usb("STM32F407")
reset_usb("DFU")
update_firmware()
exit_dfumode()

print "Done"
- run ./update_fw.py in folder \usr\bin\ via PuTTY
- in folder /home/baikal/ is now this file tmp.bin
- upload back your original update_fw.py and reebot your Baikal


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Thopf on February 05, 2018, 07:08:45 AM
I changed and i startet the command.


Traceback (most recent call last):
  File "./update_fw.py", line 51, in <module>
    update_firmware()
  File "./update_fw.py", line 42, in update_firmware
    print 'Downloading... ' + fwfile[0]
IndexError: list index out of range


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Baikalek on February 05, 2018, 07:28:22 AM
I changed and i startet the command.


Traceback (most recent call last):
  File "./update_fw.py", line 51, in <module>
    update_firmware()
  File "./update_fw.py", line 42, in update_firmware
    print 'Downloading... ' + fwfile[0]
IndexError: list index out of range

Delete please print 'Downloading... ' + fwfile[0]
Sorry


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tboy32c on February 05, 2018, 10:53:12 AM
Another way:

Modify /usr/bin/check_update.py:

Lines 51 and 52 currently look like this:
Code:
  subprocess.call('sudo rm -rf /home/baikal/tmp.bin', shell=True)
  return ret

Modify them to look like this:
Code:
  #subprocess.call('sudo rm -rf /home/baikal/tmp.bin', shell=True)
  return 0
Note the # and 0. Do NOT forget the 0. Comment out line 65 just in case:
Code:
 #subprocess.call(cmd, shell=True)

Now run these commands:
Code:
sudo touch /media/boot/G.bin
sudo python /usr/bin/check_update.py
sudo rm /media/boot/G.bin

You should see the line "Upload done." if it worked.

There should now be a new file: /home/baikal/tmp.bin. Upload this file to a file hosting site and share the link here.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Saingo on February 05, 2018, 11:51:41 AM
Just woke up. Ok i got my baikal b ready. What do you want me to do? Please give me simple steps as im a total noob


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Thopf on February 05, 2018, 11:54:32 AM
First :)

Here´s the tmp-file from a Baikal Giant B.

 KLICK  (https://uploadfiles.io/4y950)

Is it possible , to add the hidden Algo to the Baikal B?
 


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Palichka on February 05, 2018, 11:59:23 AM
you can use http://dropmefiles.com/
I think this the best share service


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: XrayHunter7 on February 05, 2018, 03:29:09 PM
Can someone extract this .bin file ?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 05, 2018, 05:30:21 PM
I ran the file through an ARM decompiler and each version of the bin seems to be coded directly for the different algos


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: XrayHunter7 on February 05, 2018, 06:16:13 PM
Can you upload it ?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Baikalek on February 05, 2018, 06:40:20 PM
Please try someone IDA program (https://www.google.com/search?client=firefox-b&ei=XKR4WsbOBYKvU9PxmogL&q=Hex-Rays+Decompiler&oq=Hex-Rays+Decompiler&gs_l=psy-ab.3..0j0i22i30k1l9.15293.15293.0.15475.1.1.0.0.0.0.159.159.0j1.1.0....0...1c.2.64.psy-ab..0.1.158....0.Lkb5XdFakmo), decompilation seems to work well, but I do not know anymore. Here is full version (https://ufile.io/9y3g8).


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Ironeinstein on February 06, 2018, 03:37:30 PM
First :)

Here´s the tmp-file from a Baikal Giant B.

 KLICK  (https://uploadfiles.io/4y950)

Is it possible , to add the hidden Algo to the Baikal B?
 


Awesome! Thank you for the upload.

I've been able to confirm that you can't re-image an X10 to a Giant B by simply pushing the STM firmware down and using the Giant B image for the Pi Zero. The structure of the firmware is very similar to the X10, but it looks like the algorithms are hard-coded into the firmware. I was hoping the firmware was just acting as a USB to SPI translator, but it looks like it's doing more low-level work for the algorithms and to drive the chips.

I've also been able to get a successful decompile using Binary Ninja and the Thumb2-linux architecture, but this will only get you machine code afaik.

Edit: Here's an upload of the GB and GX10 firmwares and binary ninja decompile databases: https://ufile.io/ues7g
If someone knows how to diff two SQLlite databases, that would be helpful.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Baikalek on February 06, 2018, 06:47:59 PM
First :)

Here´s the tmp-file from a Baikal Giant B.

 KLICK  (https://uploadfiles.io/4y950)

Is it possible , to add the hidden Algo to the Baikal B?
 


Awesome! Thank you for the upload.

I've been able to confirm that you can't re-image an X10 to a Giant B by simply pushing the STM firmware down and using the Giant B image for the Pi Zero. The structure of the firmware is very similar to the X10, but it looks like the algorithms are hard-coded into the firmware. I was hoping the firmware was just acting as a USB to SPI translator, but it looks like it's doing more low-level work for the algorithms and to drive the chips.

I've also been able to get a successful decompile using Binary Ninja and the Thumb2-linux architecture, but this will only get you machine code afaik.

Edit: Here's an upload of the GB and GX10 firmwares and binary ninja decompile databases: https://ufile.io/ues7g
If someone knows how to diff two SQLlite databases, that would be helpful.
hi your file contains
miner_fw_Gx10.bin
not SQL dbs


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Saingo on February 06, 2018, 10:28:30 PM
hi guys i managed to log on and find these commands. please let me know if any has relevance to help overclock.

man: can't set the locale; make sure $LC_* and $LANG are correct                                                                                           
bootchart.conf (5)   - Boot performance analysis graphing tool configuration files                                                                         
bootchart.conf.d (5) - Boot performance analysis graphing tool configuration files                                                                         
perf_event_open (2)  - set up performance monitoring                                                                                                       
perfmonctl (2)       - interface to IA-64 performance monitoring unit                                                                                     
s_time (1ssl)        - SSL/TLS performance timing program                                                                                                 
speed (1ssl)         - test library performance                                                                                                           
systemd-analyze (1)  - Analyze system boot-up performance                                                                                                 
systemd-bootchart (1) - Boot performance graphing tool   

thanks


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 06, 2018, 11:14:36 PM
Basically we need a hardware engineer/programmer to get this going in the direction we all want.

We don’t care to overclock, we care to mine coins on asic not yet available to the public. Which yield enormously higher daily revenues.

We want to beat Baikal and Bitmain to the punch.

If you all are in agreement let’s figure this out and make it happen.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: shaninium on February 07, 2018, 12:28:31 AM
If yas figure out how to do this dont be surprised  to get a cease and desist from baikal.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 07, 2018, 12:35:38 AM
Once you pay for hardware, it’s yours. You can do as you wish with it. If You create an image file that allow us to run new algo’s who’s going to stop that if it’s given free... no one. Also, they have no patents or anything of that nature in the US. And since they don’t respect the US’s patents.

Here’s my response to them getting rich off of us, Oh well...


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Thopf on February 07, 2018, 06:14:06 AM
That’s true.
If I buy a GPU-Card , I can do what I want.
Play games or mine a coin....
There is no rule...

Before Overclocking , it makes more Sense to use the hidden Algorithm than to Overclock and maybe to brick the machine...


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: mikej007 on February 07, 2018, 06:50:36 AM
Basically we need a hardware engineer/programmer to get this going in the direction we all want.

We don’t care to overclock, we care to mine coins on asic not yet available to the public. Which yield enormously higher daily revenues.

We want to beat Baikal and Bitmain to the punch.

If you all are in agreement let’s figure this out and make it happen.

I have been trying to work backwards from the miner gui which might lead to some ideas. The main question I have is where are the algo's coming from in the miners drop down selector, remote file? or the ASIC's themselves. Angularjs is being used with ngmodel=pool.algo

Just ideas


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 07, 2018, 04:28:07 PM
The list is coming from a static html file, called miner.html. You can add a complete list of algorithms that sgminer supports. However because the firmware on the chip doesn't have the library the miners will default to the base algorithm. On the Giant B it defaults to Blake. Not sure about the X10.

What I have done on my GB, I have added the list and noticed that many will connect to the pools correctly and will send data back and forth, and show as live on the status page of the miner. Those that do connect come back with 99.9% reject errors, not because sgminer didn't have the code, but because of the hardware is incorrectly hashing with the Blake algorithm instead of using the one selected by sgminer.

By telling sgminer to use cryptonight or nist5 for example, it works, as it passes along the commands to the hardware. However, the hardware level (STM Chip Firmware) is stopping us from reaching our goal of adding them and running those additional coins.

I'm very certain this can be accomplished, but its a bit beyond me at this point. We need a C Programmer with STM Chip programming experience.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: mikej007 on February 07, 2018, 05:43:57 PM
The list is coming from a static html file, called miner.html. You can add a complete list of algorithms that sgminer supports. However because the firmware on the chip doesn't have the library the miners will default to the base algorithm. On the Giant B it defaults to Blake. Not sure about the X10.

What I have done on my GB, I have added the list and noticed that many will connect to the pools correctly and will send data back and forth, and show as live on the status page of the miner. Those that do connect come back with 99.9% reject errors, not because sgminer didn't have the code, but because of the hardware is incorrectly hashing with the Blake algorithm instead of using the one selected by sgminer.

By telling sgminer to use cryptonight or nist5 for example, it works, as it passes along the commands to the hardware. However, the hardware level (STM Chip Firmware) is stopping us from reaching our goal of adding them and running those additional coins.

I'm very certain this can be accomplished, but its a bit beyond me at this point. We need a C Programmer with STM Chip programming experience.

From the digging I have done, the miner.html is generated from miner.php file in var/www . I have looked through all files there and still do not see the algos mentioned within any of those files so this is still a mystery to me, maybe someone can find the source. It is looking like you say that the chips are the key.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Thopf on February 07, 2018, 06:18:39 PM
For better understanding... (Baikal Giant B)

On Top , is the Orange Pi.
Under the Orange-Pi is the "STM interface" connected to the 3 Mining Boards?
Correct?





Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 07, 2018, 06:47:47 PM
Yes, correct.

Top Layer is Orange Pi

Middle Layer is STM Chip on board

Bottom Layer is 3 hash boards


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 07, 2018, 06:58:17 PM
Look in this folder \var\www\partials. There you will find the miner.html file.

This is where sgminer gets its names from on which algorithms to mine.

Obviously sgminer needs to have the matching name already programmed in it for it to connect to the pools.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Baikalek on February 07, 2018, 07:03:00 PM
Look in this folder \var\www\partials. There you will find the miner.html file.

This is where sgminer gets its names from on which algorithms to mine.

Obviously sgminer needs to have the matching name already programmed in it for it to connect to the pools.

I've tried it several times. But I did not do it anywhere. It must either be in sgminer or rather in FW STM.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 07, 2018, 07:38:14 PM
Look in this folder \var\www\partials. There you will find the miner.html file.

This is where sgminer gets its names from on which algorithms to mine.

Obviously sgminer needs to have the matching name already programmed in it for it to connect to the pools.

I've tried it several times. But I did not do it anywhere. It must either be in sgminer or rather in FW STM.

What was it that you tried? To add the algorithms to the drop down list?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Baikalek on February 07, 2018, 07:43:44 PM
Look in this folder \var\www\partials. There you will find the miner.html file.

This is where sgminer gets its names from on which algorithms to mine.

Obviously sgminer needs to have the matching name already programmed in it for it to connect to the pools.

I've tried it several times. But I did not do it anywhere. It must either be in sgminer or rather in FW STM.

What was it that you tried? To add the algorithms to the drop down list?
Yes exactly. Also change the algorithm and pool data in \opt\scripta\etc
files miner.conf and miner.pools.json
And Miner ran to default algo: Quarkcoin


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: XrayHunter7 on February 07, 2018, 08:57:17 PM
Maybe driver for STM chip ? in this folder: home/baikal/modules/3.4.113+/kernel/crypto$    files: af_alg.ko   algif_hash.ko     algif_rng.ko    algif_skcipher.ko    crypto_user.ko


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 08, 2018, 12:45:09 AM
Look in this folder \var\www\partials. There you will find the miner.html file.

This is where sgminer gets its names from on which algorithms to mine.

Obviously sgminer needs to have the matching name already programmed in it for it to connect to the pools.

I've tried it several times. But I did not do it anywhere. It must either be in sgminer or rather in FW STM.

What was it that you tried? To add the algorithms to the drop down list?
Yes exactly. Also change the algorithm and pool data in \opt\scripta\etc
files miner.conf and miner.pools.json
And Miner ran to default algo: Quarkcoin

The only place I was able to find the list of Algorithms was in the miner.html page. I added all other possible algorithms supported on sgminer as of version 5.6.1. When I did that I was able to connect to some pools of those algorithms. Some others I could not. The ones that did connect to the pools, the devices kept defaulting to the Blakecoin algorithm, which I believe is the default for GB.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Saingo on February 08, 2018, 02:46:10 AM
Look in this folder \var\www\partials. There you will find the miner.html file.

This is where sgminer gets its names from on which algorithms to mine.

Obviously sgminer needs to have the matching name already programmed in it for it to connect to the pools.

I've tried it several times. But I did not do it anywhere. It must either be in sgminer or rather in FW STM.

What was it that you tried? To add the algorithms to the drop down list?
Yes exactly. Also change the algorithm and pool data in \opt\scripta\etc
files miner.conf and miner.pools.json
And Miner ran to default algo: Quarkcoin

The only place I was able to find the list of Algorithms was in the miner.html page. I added all other possible algorithms supported on sgminer as of version 5.6.1. When I did that I was able to connect to some pools of those algorithms. Some others I could not. The ones that did connect to the pools, the devices kept defaulting to the Blakecoin algorithm, which I believe is the default for GB.

Any luck overclocking?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Thopf on February 08, 2018, 09:24:15 AM

Ok , if the Algos are located in the Chip , is it possible to "log" or "monitor" the actual processes?

On the STM Board , i see a OTG connection and on ST.com are so many tools. (http://www.st.com/en/microcontrollers/stm32f407vg.html#sw-tools-scroll (http://www.st.com/en/microcontrollers/stm32f407vg.html#sw-tools-scroll) )


Pictures from a Giant B

https://preview.ibb.co/jf5KwH/IMG_5091.jpg (https://ibb.co/cbhMAc)
https://preview.ibb.co/kB8Hix/IMG_5095.jpg (https://ibb.co/djbRbH)
https://preview.ibb.co/kF0mbH/IMG_5096.jpg (https://ibb.co/hnfmbH)



Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: XrayHunter7 on February 09, 2018, 10:34:26 AM

Ok , if the Algos are located in the Chip , is it possible to "log" or "monitor" the actual processes?

On the STM Board , i see a OTG connection and on ST.com are so many tools. (http://www.st.com/en/microcontrollers/stm32f407vg.html#sw-tools-scroll (http://www.st.com/en/microcontrollers/stm32f407vg.html#sw-tools-scroll) )


Pictures from a Giant B

https://preview.ibb.co/jf5KwH/IMG_5091.jpg (https://ibb.co/cbhMAc)
https://preview.ibb.co/kB8Hix/IMG_5095.jpg (https://ibb.co/djbRbH)
https://preview.ibb.co/kF0mbH/IMG_5096.jpg (https://ibb.co/hnfmbH)



On giant x10 is same STM Board.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: flip909 on February 09, 2018, 01:49:19 PM
Hi all,

Hows this all coming along?

I have X10s and Giant Bs. have been thinking about this for a while.

Whats ppls best guesses for X10 Algos?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: XrayHunter7 on February 09, 2018, 04:49:45 PM
First :)

Here´s the tmp-file from a Baikal Giant B.

 KLICK  (https://uploadfiles.io/4y950)

Is it possible , to add the hidden Algo to the Baikal B?
 


Maybe We can try to use extracted Giant Bfw on X10 OR X10fw on B.

and

X10 Custom Version of SGMiner 5.6.2-L
Giant B Custom Version of SGMiner 5.6.2-B


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: namsss on February 09, 2018, 06:14:59 PM
Hi all,

Hows this all coming along?

I have X10s and Giant Bs. have been thinking about this for a while.

Whats ppls best guesses for X10 Algos?
Hi ,
Can you swap Arm board from x10 to B ? Is it still work ?
Thankyou


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 09, 2018, 07:46:36 PM
I'm 99% sure, if we place the extracted firmware (*.bin) of an X10 in the SD card in the boot folder, it will reimage the firmware with the same image in the STM chip.

Same thing should apply to the GB.

Therefore if I get a X10 image with bin file in the boot folder and start up a GB with that SD card, it should reflash the STM chip with the coding of an X10 and in theory work.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 09, 2018, 08:44:38 PM
The filename must start with G.

The reason behind that is that the file, update_fw.py. Located in the \usr\bin folder.

Code:
#!/usr/bin/env python
import subprocess
import os
import sys
from subprocess import Popen, PIPE
import fcntl
import time
import glob
tmpfile = '/home/baikal/tmp.bin'
path = '/media/boot/G*.bin'
fwfile = glob.glob(path)
if not fwfile:
print 'No firmware'
sys.exit()

USBDEVFS_RESET= 21780

# enter dfu mode
def enter_dfumode():
  subprocess.call('echo 0 > /sys/class/gpio_sw/PA18/data', shell=True)
  subprocess.call('echo 0 > /sys/class/gpio_sw/PA10/data', shell=True)
  subprocess.call('echo 1 > /sys/class/gpio_sw/PA10/data', shell=True)

def exit_dfumode():
  subprocess.call('echo 1 > /sys/class/gpio_sw/PA18/data', shell=True)
  subprocess.call('echo 0 > /sys/class/gpio_sw/PA10/data', shell=True)
  subprocess.call('echo 1 > /sys/class/gpio_sw/PA10/data', shell=True)

def reset_usb(driver):
  try:
    lsusb_out = Popen("lsusb | grep -i %s"%driver, shell=True, bufsize=64, stdin=PIPE, stdout=PIPE, close_fds=True).stdout.read().strip().split()
    bus = lsusb_out[1]
    device = lsusb_out[3][:-1]
    f = open("/dev/bus/usb/%s/%s"%(bus, device), 'w', os.O_WRONLY)
    fcntl.ioctl(f, USBDEVFS_RESET, 0)
  except Exception, msg:
    print ""

def update_firmware():
  enter_dfumode()
  reset_usb("DFU")
  print 'Downloading... ' + fwfile[0]
  cmd = 'sudo dfu-util -a 0 -d 0483:df11 -s 0x08000000:leave -D ' + fwfile[0]
  subprocess.call(cmd, shell=True)
  cmd = 'sudo rm -rf ' + path
  subprocess.call(cmd, shell=True)

enter_dfumode()
reset_usb("STM32F407")
reset_usb("DFU")
update_firmware()
exit_dfumode()

print "Done"



Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: XrayHunter7 on February 09, 2018, 10:45:16 PM
The filename must start with G.

The reason behind that is that the file, update_fw.py. Located in the \usr\bin folder.

Code:
#!/usr/bin/env python
import subprocess
import os
import sys
from subprocess import Popen, PIPE
import fcntl
import time
import glob
tmpfile = '/home/baikal/tmp.bin'
path = '/media/boot/G*.bin'
fwfile = glob.glob(path)
if not fwfile:
print 'No firmware'
sys.exit()

USBDEVFS_RESET= 21780

# enter dfu mode
def enter_dfumode():
  subprocess.call('echo 0 > /sys/class/gpio_sw/PA18/data', shell=True)
  subprocess.call('echo 0 > /sys/class/gpio_sw/PA10/data', shell=True)
  subprocess.call('echo 1 > /sys/class/gpio_sw/PA10/data', shell=True)

def exit_dfumode():
  subprocess.call('echo 1 > /sys/class/gpio_sw/PA18/data', shell=True)
  subprocess.call('echo 0 > /sys/class/gpio_sw/PA10/data', shell=True)
  subprocess.call('echo 1 > /sys/class/gpio_sw/PA10/data', shell=True)

def reset_usb(driver):
  try:
    lsusb_out = Popen("lsusb | grep -i %s"%driver, shell=True, bufsize=64, stdin=PIPE, stdout=PIPE, close_fds=True).stdout.read().strip().split()
    bus = lsusb_out[1]
    device = lsusb_out[3][:-1]
    f = open("/dev/bus/usb/%s/%s"%(bus, device), 'w', os.O_WRONLY)
    fcntl.ioctl(f, USBDEVFS_RESET, 0)
  except Exception, msg:
    print ""

def update_firmware():
  enter_dfumode()
  reset_usb("DFU")
  print 'Downloading... ' + fwfile[0]
  cmd = 'sudo dfu-util -a 0 -d 0483:df11 -s 0x08000000:leave -D ' + fwfile[0]
  subprocess.call(cmd, shell=True)
  cmd = 'sudo rm -rf ' + path
  subprocess.call(cmd, shell=True)

enter_dfumode()
reset_usb("STM32F407")
reset_usb("DFU")
update_firmware()
exit_dfumode()

print "Done"



Do you think that STM chip is hardcoded ? I got new STM board and orange pi from baikal for X10. What If I buy STM for giant B ?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 09, 2018, 10:46:53 PM
I'm under the impression from reading the STM chip manufacturer documents that it is flashed via USB or through the OrangePI Zero in this case.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: namsss on February 10, 2018, 01:50:05 AM
I'm 99% sure, if we place the extracted firmware (*.bin) of an X10 in the SD card in the boot folder, it will reimage the firmware with the same image in the STM chip.

Same thing should apply to the GB.

Therefore if I get a X10 image with bin file in the boot folder and start up a GB with that SD card, it should reflash the STM chip with the coding of an X10 and in theory work.
Dear !
I think hashboard are different bt x10 and B.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: darkly spectre on February 10, 2018, 01:57:59 AM
honestly the only way to truly know if they are different is if somebody has the balls to take the heat sinks off both the X10 and GB and see if the ASICs have model numbers on them


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 10, 2018, 01:59:45 AM
honestly the only way to truly know if they are different is if somebody has the balls to take the heat sinks off both the X10 and GB and see if the ASICs have model numbers on them

 ;D
hahaha, love it!

I'm sure someone has done this before.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: namsss on February 10, 2018, 06:46:01 AM
I'm under the impression from reading the STM chip manufacturer documents that it is flashed via USB or through the OrangePI Zero in this case.
Hi
Can you extract STM bin from baikal Giant A2000
Thank


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: XrayHunter7 on February 10, 2018, 09:02:11 PM
I must correct myself. Giant x10 STM control board is same as Giant B.
But STM chips are different.

Giant x10:
STM32F407
VET6Y
7B368 VG
PHL 78 72B

Giant B:
STM32F407
VET6Y
7B827 VG
PHL 78 72B


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: manfire911 on February 11, 2018, 03:57:03 PM
honestly the only way to truly know if they are different is if somebody has the balls to take the heat sinks off both the X10 and GB and see if the ASICs have model numbers on them

 ;D
hahaha, love it!

I'm sure someone has done this before.


TEST WAS ALLREADY DONE SIR

#1 - INSTALLED SGMINER-A   SGMINER-B  SGMINER-2000 start in ssh all exec bin on each baikal reserve test all ... nothing add algo or give bonus
#2 - put firmware 300mhz cube on x10 a  - NOT WORKING  COMPLETE BROKE THE ARM PLATE BLUE
#3 - echange GIANT B on GIANT A AND REVERSE  - NOT WORKING
#4  - put firmware GIANT B on GIANT A                - NOT WORKING


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 11, 2018, 04:01:35 PM
honestly the only way to truly know if they are different is if somebody has the balls to take the heat sinks off both the X10 and GB and see if the ASICs have model numbers on them

 ;D
hahaha, love it!

I'm sure someone has done this before.


TEST WAS ALLREADY DONE SIR

#1 - INSTALLED SGMINER-A   SGMINER-B  SGMINER-2000 start in ssh all exec bin on each baikal reserve test all ... nothing add algo or give bonus
#2 - put firmware 300mhz cube on x10 a  - NOT WORKING  COMPLETE BROKE THE ARM PLATE BLUE
#3 - echange GIANT B on GIANT A AND REVERSE  - NOT WORKING
#4  - put firmware GIANT B on GIANT A                - NOT WORKING


Did you chang the STM firmware? Not just the SD card on the orange pi? On the Giants


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: manfire911 on February 11, 2018, 04:13:07 PM
someone have the usd idvendor and idprouct of baikal giant 2000 us 006 Device 003: ID ****:**** STMicroelectronics ????


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: manfire911 on February 11, 2018, 04:14:31 PM
honestly the only way to truly know if they are different is if somebody has the balls to take the heat sinks off both the X10 and GB and see if the ASICs have model numbers on them

 ;D
hahaha, love it!

I'm sure someone has done this before.


TEST WAS ALLREADY DONE SIR

#1 - INSTALLED SGMINER-A   SGMINER-B  SGMINER-2000 start in ssh all exec bin on each baikal reserve test all ... nothing add algo or give bonus
#2 - put firmware 300mhz cube on x10 a  - NOT WORKING  COMPLETE BROKE THE ARM PLATE BLUE
#3 - echange GIANT B on GIANT A AND REVERSE  - NOT WORKING
#4  - put firmware GIANT B on GIANT A                - NOT WORKING


Did you chang the STM firmware? Not just the SD card on the orange pi? On the Giants
I EXTRACT THE FIRMWARE OF THE ARM WITH THE SCRIPT ON USR BIN AND I PUSH UP THE FIRMWARE ON THE GIANT B PLATE WITH THE SAME SCRIPT

fw-upgrade....


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 11, 2018, 04:19:35 PM
honestly the only way to truly know if they are different is if somebody has the balls to take the heat sinks off both the X10 and GB and see if the ASICs have model numbers on them

 ;D
hahaha, love it!

I'm sure someone has done this before.


TEST WAS ALLREADY DONE SIR

#1 - INSTALLED SGMINER-A   SGMINER-B  SGMINER-2000 start in ssh all exec bin on each baikal reserve test all ... nothing add algo or give bonus
#2 - put firmware 300mhz cube on x10 a  - NOT WORKING  COMPLETE BROKE THE ARM PLATE BLUE
#3 - echange GIANT B on GIANT A AND REVERSE  - NOT WORKING
#4  - put firmware GIANT B on GIANT A                - NOT WORKING


Did you chang the STM firmware? Not just the SD card on the orange pi? On the Giants
I EXTRACT THE FIRMWARE OF THE ARM WITH THE SCRIPT ON USR BIN AND I PUSH UP THE FIRMWARE ON THE GIANT B PLATE WITH THE SAME SCRIPT

fw-upgrade....


He only other thing I would try is to swap the STM board + OrangePi of Giant A and Swap with Giant B. Leave original code as is.

That would mean that we could order spare parts for each type and use hashboards


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Ironeinstein on February 11, 2018, 04:27:03 PM
I've tried flashing the Giant B firmware to an X10 and running the Giant B image on the Pi but no luck converting an X10 to GB or using that firmware image to overclock (so far).

Interesting that the controller boards are the same, but not surprising. I can't find the difference between those two STM model numbers anywhere online. Could the last couple lines just be batch numbers?

I DID take the heatsink off an X10 and the model number on the asic is this:

[Baikal Logo]
BK177280
ND33U

I'd upload a picture, but the chips are too small for my potato camera.

<Your move Giant-B owners!>


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: XrayHunter7 on February 11, 2018, 04:35:24 PM
I've tried flashing the Giant B firmware to an X10 and running the Giant B image on the Pi but no luck converting an X10 to GB or using that firmware image to overclock (so far).

Interesting that the controller boards are the same, but not surprising. I can't find the difference between those two STM model numbers anywhere online. Could the last couple lines just be batch numbers?

I DID take the heatsink off an X10 and the model number on the asic is this:

[Baikal Logo]
BK177280
ND33U

I'd upload a picture, but the chips are too small for my potato camera.

<Your move Giant-B owners!>

Yes. If chips on Giant B are different only way is to modify firmware to comunicate with x10 chips. Or B to X10


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 11, 2018, 04:40:04 PM
I've tried flashing the Giant B firmware to an X10 and running the Giant B image on the Pi but no luck converting an X10 to GB or using that firmware image to overclock (so far).

Interesting that the controller boards are the same, but not surprising. I can't find the difference between those two STM model numbers anywhere online. Could the last couple lines just be batch numbers?

I DID take the heatsink off an X10 and the model number on the asic is this:

[Baikal Logo]
BK177280
ND33U

I'd upload a picture, but the chips are too small for my potato camera.

<Your move Giant-B owners!>

Yes. If chips on Giant B are different only way is to modify firmware to comunicate with x10 chips. Or B to X10

When you took off the heat sink, was there any thermal paste? And did you replace it?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Ironeinstein on February 12, 2018, 06:14:42 AM
There are thermal pads under the heatsink. I have replacements ordered, but I'm only running myr-gr, so not too worried about heat. You could probably replace the thermal pads with Arctic silver, but I'd be worried about it getting on the board.

There's a small heatsink on one side, and a large one on the other. The chips are all under the small one, so dont worry about taking them both off.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: manfire911 on February 12, 2018, 08:38:55 PM
Hi guys ,

https://1.bp.blogspot.com/-WyA1wx6r0b4/WhPZUHn5C4I/AAAAAAAABU8/LZGvk5nj14ICYhfTfW0A-sBcWFwbHyLdACLcBGAs/s320/Bitcoin%2Banimation.gif


Pay 0.2 BTC for working tutorial how to OVERCLOCK Baikal x10
from 300MHz to 400 Mhz


https://i.imgur.com/k9pvI7u.jpg


How to claim 0.2 ? Must show me video on PM

ESCROW

I dont know if I win the 0.2 but the reason is simple, all giant a algo have a string lenght take and calculed by the baikal at the 300mhz clock so if you change the frequency the only think happen is a lot of invalid share that it !


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 12, 2018, 08:44:13 PM
Hi guys ,

https://1.bp.blogspot.com/-WyA1wx6r0b4/WhPZUHn5C4I/AAAAAAAABU8/LZGvk5nj14ICYhfTfW0A-sBcWFwbHyLdACLcBGAs/s320/Bitcoin%2Banimation.gif


Pay 0.2 BTC for working tutorial how to OVERCLOCK Baikal x10
from 300MHz to 400 Mhz


https://i.imgur.com/k9pvI7u.jpg


How to claim 0.2 ? Must show me video on PM

ESCROW

I dont know if I win the 0.2 but the reason is simple, all giant a algo have a string lenght take and calculed by the baikal at the 300mhz clock so if you change the frequency the only think happen is a lot of invalid share that it !

I think you need to provide more details on how you accomplished overclocking it, not keeping the 300MHz the same


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: manfire911 on February 12, 2018, 08:48:46 PM
exemple

the string lenght of quark if

[04:47:14] [THR1] Generated target 00000000000000000000000000000000000000000000000000a0a90a01000000
[04:47:14] [THR0] gen_stratum_work() - algorithm = quark
[04:47:14] [THR0] Generated stratum merkle a4cabd4cb6a2275c654cf7228c1f8fd427d0c520121a6921367d00ebeb5c5636
[04:47:14] [THR0] Generated stratum header 000000031237f750298c12396693229f8d92cc0e841efaac5f96e18d00000d1400000000a4cabd4 cb6a2275c654cf7228c1f8fd427d0c520121a6921367d00ebeb5c56365a81fd301a4a5bf3000000 000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000
[04:47:14] [THR0] Work job_id ec nonce2 3 ntime 5a81fd30
[04:47:14] [THR0] Generated target 00000000000000000000000000000000000000000000000000a0a90a01000000
[04:47:14] Generated stratum work
[04:47:14] [THR0] Pushing work from to hash queue
[04:47:14] Pool 13 stratum share result lag time 0 seconds
[04:47:14] [THR0] PROOF OF WORK RESULT: true (yay!!!)

and the result with 400 mhz

[04:48:07] [THR2] Generated target 0000000000000000000000000000000000000000000000000000f6ff09000000
[04:48:07] [THR0] gen_stratum_work() - algorithm = quark
[04:48:07] [THR0] Generated stratum merkle f8e7f4689d8432d965b165b64a5be7b79b8d667e488ebc317f95f905173b7647
[04:48:07] [THR0] Generated stratum header 000000031fdbe60845f086328218ace1092ccd2821e136e6bbc73e87000023b900000000f8e7f46 89d8432d965b165b64a5be7b79b8d667e488ebc317f95f905173b76475a81fd711a489116000000 000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000
[04:48:07] [THR0] Work job_id ee nonce2 551 ntime 5a81fd71
[04:48:07] [THR0] Generated target 00000000000000000000000000000000000000000000000000009cff63000000
[04:48:07] Generated stratum work


the baikal try to full up the 100mhz more with 000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000


I know is not frequency put the data inside the baikal but the rehash logical power use the clock to calculed the end of the string return that it !




Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: namsss on February 13, 2018, 04:24:04 AM
The X10 use 10Mhz crystal oscillator , B use 12MHz . Giant A2000 8MHz


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: takeapart on February 13, 2018, 07:25:46 AM
sgminer was hardcoded to report 300Mhz.
Its not picking up the value from STM board, what you see on sgminer interface is hardcoded string, nothing more.
I can make it report anything i want.

Moreover, Mhz setting to baikal_setoption is hardcoded as well, see below.

Code:
BL              to_baikal_algorithm
LDRB.W          R2, [SP,#0x70+fanspeed]
LDRB.W          R3, [SP,#0x70+cutofftemp] ; temp
MOV.W           R1, #0x12C ; ; set clock 300Mhz
STR             R2, [SP,#0x70+var_70] ; fanspeed
UXTB            R2, R0
MOV             R0, baikal ; baikal
BL              baikal_setoption

Changing supplied option to anything (over/undeclock) makes no difference in both calls to baikal_setoption.
I believe this setting is simply ignored by the STM firmware.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Saingo on February 13, 2018, 10:05:00 PM
sgminer was hardcoded to report 300Mhz.
Its not picking up the value from STM board, what you see on sgminer interface is hardcoded string, nothing more.
I can make it report anything i want.

Moreover, Mhz setting to baikal_setoption is hardcoded as well, see below.

Code:
BL              to_baikal_algorithm
LDRB.W          R2, [SP,#0x70+fanspeed]
LDRB.W          R3, [SP,#0x70+cutofftemp] ; temp
MOV.W           R1, #0x12C ; ; set clock 300Mhz
STR             R2, [SP,#0x70+var_70] ; fanspeed
UXTB            R2, R0
MOV             R0, baikal ; baikal
BL              baikal_setoption

Changing supplied option to anything (over/undeclock) makes no difference in both calls to baikal_setoption.
I believe this setting is simply ignored by the STM firmware.
How did you get this page up?

we are able to change fan speed, which here says 70 so why cannot it work for clock speed?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: bittawm on February 13, 2018, 10:23:16 PM
keep up the good work gents, still watching


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheCubanMiner on February 13, 2018, 10:51:30 PM
keep up the good work gents, still watching
why dont you join in and leave the sidelines?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: takeapart on February 14, 2018, 10:33:23 AM

How did you get this page up?

we are able to change fan speed, which here says 70 so why cannot it work for clock speed?


Its not a page, its a disassembly of the sgminer.
70 is not a value but offset to a variable..

I'm almost 99.9% sure that you cannot do anything to baikal without changing its crystal or charing STM firmware.
FInding the right crystal that will only give 10-20% boost would be hard..
Disassembling firmware even harder.. :)


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: dmanukr on February 16, 2018, 02:04:17 AM

How did you get this page up?

we are able to change fan speed, which here says 70 so why cannot it work for clock speed?




Its not a page, its a disassembly of the sgminer.
70 is not a value but offset to a variable..

I'm almost 99.9% sure that you cannot do anything to baikal without changing its crystal or charing STM firmware.
FInding the right crystal that will only give 10-20% boost would be hard..
Disassembling firmware even harder.. :)

Then the question becomes, how do we make the miner, better?  What change would give it a boost?  It may be someone is trying to clone and improve it and may tap into the talent in this forum for future development .. never know


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: asgardcfr on February 16, 2018, 12:40:11 PM
can we compare to a CPU?
can we overclock it?
on the electronic boards, are there the components allowing to vary the voltages and finally the frequency

or as mentioned above, quartz can't be modified ?

we somes god in electronics on this topic  :)


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: namsss on February 16, 2018, 05:27:26 PM
I've tried flashing the Giant B firmware to an X10 and running the Giant B image on the Pi but no luck converting an X10 to GB or using that firmware image to overclock (so far).

Interesting that the controller boards are the same, but not surprising. I can't find the difference between those two STM model numbers anywhere online. Could the last couple lines just be batch numbers?

I DID take the heatsink off an X10 and the model number on the asic is this:

[Baikal Logo]
BK177280
ND33U

I'd upload a picture, but the chips are too small for my potato camera.

<Your move Giant-B owners!>

Here is Giant B
[Baikal Logo]
BK1791R0
ND262

Cystal 12.5 Mhz


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: XrayHunter7 on February 22, 2018, 08:20:53 AM
Without stupid hashrate limitter its running pretty fast. But only for 10sec. I asked Baikal If there is some hashrate limit - and they say yes.
https://i.imgur.com/DQazDza.jpg


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: adra12 on February 24, 2018, 09:43:23 PM
sgminer was hardcoded to report 300Mhz.
Its not picking up the value from STM board, what you see on sgminer interface is hardcoded string, nothing more.
I can make it report anything i want.

Moreover, Mhz setting to baikal_setoption is hardcoded as well, see below.

Code:
BL              to_baikal_algorithm
LDRB.W          R2, [SP,#0x70+fanspeed]
LDRB.W          R3, [SP,#0x70+cutofftemp] ; temp
MOV.W           R1, #0x12C ; ; set clock 300Mhz
STR             R2, [SP,#0x70+var_70] ; fanspeed
UXTB            R2, R0
MOV             R0, baikal ; baikal
BL              baikal_setoption

Changing supplied option to anything (over/undeclock) makes no difference in both calls to baikal_setoption.
I believe this setting is simply ignored by the STM firmware.

I changed that value to 0x190 in sgminer, but it didn't have any impact on the hash rate. So probably you are right.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tx3000s on February 25, 2018, 06:39:56 PM
Without stupid hashrate limitter its running pretty fast. But only for 10sec. I asked Baikal If there is some hashrate limit - and they say yes.
https://i.imgur.com/DQazDza.jpg

this is X10 or GB?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Baikalek on February 25, 2018, 06:48:09 PM
Without stupid hashrate limitter its running pretty fast. But only for 10sec. I asked Baikal If there is some hashrate limit - and they say yes.
https://i.imgur.com/DQazDza.jpg

this is X10 or GB?
Myriad-Groestl
This is X10 miner


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tboy32c on February 26, 2018, 01:57:58 AM
Without stupid hashrate limitter its running pretty fast. But only for 10sec. I asked Baikal If there is some hashrate limit - and they say yes.
https://i.imgur.com/DQazDza.jpg

What happens after 10 seconds? Could you achieve the same result for any arbitrary 10-second period during mining or does it have to be the very first 10 seconds after the miner starts hashing?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tx3000s on February 26, 2018, 08:21:05 AM
Anyone noticed Baikal updated they're firmware on the Giant B????

I had previously downloaded PiZero_GB_171221_V1.0.

Now I revisited the site and its changed to PiZero_GB_180105_V1.0.

What the heck are they up to.... ???

hello ..can you share  PiZero_GB_171221_V1.0 ?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: XrayHunter7 on February 26, 2018, 09:09:07 AM
Without stupid hashrate limitter its running pretty fast. But only for 10sec. I asked Baikal If there is some hashrate limit - and they say yes.
https://i.imgur.com/DQazDza.jpg

What happens after 10 seconds? Could you achieve the same result for any arbitrary 10-second period during mining or does it have to be the very first 10 seconds after the miner starts hashing?


I underclock orange pi. So its running super slow. And booting sequence looks like this: Miner UP, DEV1,2,3 load, 5sec, DEV 1 set hashrate limit, DEV 2 set hashrate limit, DEV 3 set hashrate limit. So I have first 5 seconds to see x10 running on "full speed" after that it starts limiting each hashing board.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: adra12 on February 26, 2018, 09:46:23 AM
I underclock orange pi. So its running super slow. And booting sequence looks like this: Miner UP, DEV1,2,3 load, 5sec, DEV 1 set hashrate limit, DEV 2 set hashrate limit, DEV 3 set hashrate limit. So I have first 5 seconds to see x10 running on "full speed" after that it starts limiting each hashing board.

I can confirm that sgminer is limiting the hashing power.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tboy32c on February 26, 2018, 10:13:54 AM
Without stupid hashrate limitter its running pretty fast. But only for 10sec. I asked Baikal If there is some hashrate limit - and they say yes.
https://i.imgur.com/DQazDza.jpg

What happens after 10 seconds? Could you achieve the same result for any arbitrary 10-second period during mining or does it have to be the very first 10 seconds after the miner starts hashing?


I underclock orange pi. So its running super slow. And booting sequence looks like this: Miner UP, DEV1,2,3 load, 5sec, DEV 1 set hashrate limit, DEV 2 set hashrate limit, DEV 3 set hashrate limit. So I have first 5 seconds to see x10 running on "full speed" after that it starts limiting each hashing board.

Are you sure that slowing the OrangePi doesn't interfere with how it calculates the hashrates? Race cars travel twice as fast as they actually do according to a 50% underclocked stopwatch.



Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tboy32c on February 26, 2018, 10:26:52 AM
I underclock orange pi. So its running super slow. And booting sequence looks like this: Miner UP, DEV1,2,3 load, 5sec, DEV 1 set hashrate limit, DEV 2 set hashrate limit, DEV 3 set hashrate limit. So I have first 5 seconds to see x10 running on "full speed" after that it starts limiting each hashing board.

I can confirm that sgminer is limiting the hashing power.

Does that mean you've overcome said limit or just that you've made an observation that leads you to that conclusion?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: arma33 on February 26, 2018, 11:02:39 AM
Without stupid hashrate limitter its running pretty fast. But only for 10sec. I asked Baikal If there is some hashrate limit - and they say yes.
https://i.imgur.com/DQazDza.jpg


So how much time such indicators. Then still the power drops to the factory?It turns out in pizero written?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: adra12 on February 26, 2018, 11:23:19 AM
Does that mean you've overcome said limit or just that you've made an observation that leads you to that conclusion?

I just tried different versions of sgminer on an X10, which resulted in different hash rates. And the hashboards were calculating for sure, even the Orange pi was lagging at a higher hashing rate. I also assume that the baikal driver is compiled into sgminer, hence it doesn't work with other hashing boards. So this means that the only solution is to decompile and edit sgminer, or get the original source code for that system.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: ismurdegus on February 26, 2018, 11:30:23 AM
Will be a dream if we can unlock the hash rate!


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tboy32c on February 26, 2018, 11:52:19 AM
Does that mean you've overcome said limit or just that you've made an observation that leads you to that conclusion?

I just tried different versions of sgminer on an X10, which resulted in different hash rates. And the hashboards were calculating for sure, even the Orange pi was lagging at a higher hashing rate. I also assume that the baikal driver is compiled into sgminer, hence it doesn't work with other hashing boards. So this means that the only solution is to decompile and edit sgminer, or get the original source code for that system.

Ahh I see. Which versions did you try and what were the corresponding hash rates? Did you try running each version of sgminer for a set duration (say over an hour) and comparing the total number of accepted shares?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: adra12 on February 26, 2018, 12:22:48 PM
Ahh I see. Which versions did you try and what were the corresponding hash rates? Did you try running each version of sgminer for a set duration (say over an hour) and comparing the total number of accepted shares?

I used the original X10 sgminer, which was working as it should. The other one that was working was the GB sgminer, which detected the hashing boards and started hashing with the default algorithm, but without any accepted shares. Probably this is due to driver incompatibility. The other sgminer was built by myself from the online available source code, and I also tried another one compiled by someone else with all the GPU drivers compiled into it. The last two did not detect the hashing boards, which means that baikal is using proprietary drivers for each device.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: aerodynomic on February 26, 2018, 02:58:36 PM
I know im just jumping in here but i thought id add some interesting things Ive noticed with my x10. There are times when I initally turn it on and it just loads the miner that the hash rate will for each board spikes up to 20GH/s for 60 GH/s total. This has happened a few times. Ill try to get a screeen shot the next time I can but if thats true these machines are very powerful and they do really underclock them.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: dmanukr on February 26, 2018, 11:15:31 PM
Once you pay for hardware, it’s yours. You can do as you wish with it. If You create an image file that allow us to run new algo’s who’s going to stop that if it’s given free... no one. Also, they have no patents or anything of that nature in the US. And since they don’t respect the US’s patents.

Here’s my response to them getting rich off of us, Oh well...

Im with you on this


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Microcosm on February 27, 2018, 03:51:41 AM
Registered to the forum so I could get in on this one!

If we had to prioritize, which would be a better outcome? Removing the hash limit or unlocking algos? Probably the limit... yeah?

Does anyone know specifically the skill set we need to move this forward? I know some high-class engineers that may be interested but better f I approach with specific & detailed questions...

Hope we can pull this one off!

T


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: dmanukr on February 27, 2018, 01:14:44 PM
If the boards can be successfully cloned with all same components, etc. can you guys think of a reason why you wouldn't be able to just flash the firmware and have fully functioning unit? 

I reached out to a couple of you privately to no avail so I'll just put this in the open, for those of you who have taken out a hashboard and examined it,
seen the components or can make photo or list of components, can you share that?  Some of you speak as though you're seriously interested in doing this but it's hard to see if it's just a hobby or challenge game, or if you're really interested in doing this in a bigger way. I'm interested in the latter. 
If you prefer to keep a hobby and no interest beyond, and you have a hashboard you'd sell me so i can have it examined, great, let me know.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tboy32c on February 27, 2018, 02:58:54 PM
If the boards can be successfully cloned with all same components, etc. can you guys think of a reason why you wouldn't be able to just flash the firmware and have fully functioning unit? 

I reached out to a couple of you privately to no avail so I'll just put this in the open, for those of you who have taken out a hashboard and examined it,
seen the components or can make photo or list of components, can you share that?  Some of you speak as though you're seriously interested in doing this but it's hard to see if it's just a hobby or challenge game, or if you're really interested in doing this in a bigger way. I'm interested in the latter. 
If you prefer to keep a hobby and no interest beyond, and you have a hashboard you'd sell me so i can have it examined, great, let me know.


The ASICs cannot be cloned. Take a look at this comment:

...
I DID take the heatsink off an X10 and the model number on the asic is this:

[Baikal Logo]
BK177280
ND33U

...

The ASIC chips themselves are manufactured specifically for Baikal only since it's their own custom design. Even if everything else on the miner could be sourced, the key missing component would be the ASICs themselves which are closed-source and proprietary.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Ironeinstein on February 27, 2018, 05:34:56 PM

I sent in an email asking them to release their firmware and software.



Senseless, did you ever get a reply on the software or firmware?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: dmanukr on February 27, 2018, 05:41:33 PM
No. I'll get it done one way or another, just thought there would be others interested.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tboy32c on February 28, 2018, 12:39:02 AM
No. I'll get it done one way or another, just thought there would be others interested.

Are you interested in making your own X10 miner or in modifying ones that already exist? From my understanding those posting in this thread have been interested in overclocking and/or unlocking the additional two promised algorithms that the X10 is supposedly capable of. I don't think anyone has been trying to recreate their own miner.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: dmanukr on February 28, 2018, 01:49:36 AM
If the boards can be successfully cloned with all same components, etc. can you guys think of a reason why you wouldn't be able to just flash the firmware and have fully functioning unit?  

I reached out to a couple of you privately to no avail so I'll just put this in the open, for those of you who have taken out a hashboard and examined it,
seen the components or can make photo or list of components, can you share that?  Some of you speak as though you're seriously interested in doing this but it's hard to see if it's just a hobby or challenge game, or if you're really interested in doing this in a bigger way. I'm interested in the latter.  
If you prefer to keep a hobby and no interest beyond, and you have a hashboard you'd sell me so i can have it examined, great, let me know.


The ASICs cannot be cloned. Take a look at this comment:

...
I DID take the heatsink off an X10 and the model number on the asic is this:

[Baikal Logo]
BK177280
ND33U

...

The ASIC chips themselves are manufactured specifically for Baikal only since it's their own custom design. Even if everything else on the miner could be sourced, the key missing component would be the ASICs themselves which are closed-source and proprietary.

Yes I saw this.. Baikal is a Russian electronics company .. they produce the asic chips and I may be able to acquire them. The hashboard is what would be otherwise proprietary but according to prelminary discussions with my engineers, can likely be cloned or functionally matched.  So my question is if someone has already photos or can make a bill of materials or components they see on the board.. or if they would sell me a working or non-working board and I'll get it done myself .. besides the asic chip listed (all the other transistors, etc.)  I can put it through to see if they can source everything.

I suppose I was hinting for partners in what may be a much bigger project, as I've already decided I'm going to make the investment for the chance to get it done provided the required chips are available.. some of the skills and perhaps material that this group may have, could make it a reality in which case there would be a very small group of people with access to the resulting product.  Yeah it's maybe a big dream, but it's worth it. Multi algo miners are the way to go and to understand and be able to create more efficient ones or more capable, isn't so far fetched.

In the meantime, my other question was a programming one.  Isnt the firmware what is provided to flash the system or is there a rom that is pre-programmed with base functions that would have to be decompiled?  


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Ironeinstein on February 28, 2018, 04:53:03 AM

Yes I saw this.. Baikal is a Russian electronics company .. they produce the asic chips and I may be able to acquire them. The hashboard is what would be otherwise proprietary but according to prelminary discussions with my engineers, can likely be cloned or functionally matched.  So my question is if someone has already photos or can make a bill of materials or components they see on the board.. or if they would sell me a working or non-working board and I'll get it done myself .. besides the asic chip listed (all the other transistors, etc.)  I can put it through to see if they can source everything.

I suppose I was hinting for partners in what may be a much bigger project, as I've already decided I'm going to make the investment for the chance to get it done provided the required chips are available.. some of the skills and perhaps material that this group may have, could make it a reality in which case there would be a very small group of people with access to the resulting product.  Yeah it's maybe a big dream, but it's worth it. Multi algo miners are the way to go and to understand and be able to create more efficient ones or more capable, isn't so far fetched.

In the meantime, my other question was a programming one.  Isnt the firmware what is provided to flash the system or is there a rom that is pre-programmed with base functions that would have to be decompiled?  

If you can source the chips, that would be a huge step toward cloning the whole miner, but I'm having a hard time picturing how you would do that ethically. I don't imagine Baikal is selling these chips on the open market.

If you decide to develop your own systems however, keep me in mind. I have some unique ideas about how to design a multi-algo asic to target a group of algorithms, but don't have the experience or resources to implement it in silicon. I also have a good idea of which algos and networks to target without causing a D3-level fiasco. Keep me in mind if you actually kick off this project.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tomwrx on February 28, 2018, 11:14:15 AM
If the boards can be successfully cloned with all same components, etc. can you guys think of a reason why you wouldn't be able to just flash the firmware and have fully functioning unit?  

I reached out to a couple of you privately to no avail so I'll just put this in the open, for those of you who have taken out a hashboard and examined it,
seen the components or can make photo or list of components, can you share that?  Some of you speak as though you're seriously interested in doing this but it's hard to see if it's just a hobby or challenge game, or if you're really interested in doing this in a bigger way. I'm interested in the latter.  
If you prefer to keep a hobby and no interest beyond, and you have a hashboard you'd sell me so i can have it examined, great, let me know.


The ASICs cannot be cloned. Take a look at this comment:

...
I DID take the heatsink off an X10 and the model number on the asic is this:

[Baikal Logo]
BK177280
ND33U

...

The ASIC chips themselves are manufactured specifically for Baikal only since it's their own custom design. Even if everything else on the miner could be sourced, the key missing component would be the ASICs themselves which are closed-source and proprietary.

Yes I saw this.. Baikal is a Russian electronics company ..   

Where did you find that info? Baikal is chinese company. There is no link between Baikal lake in Russia Siberia and Baikal company.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: dmanukr on February 28, 2018, 01:22:31 PM

Yes I saw this.. Baikal is a Russian electronics company .. they produce the asic chips and I may be able to acquire them. The hashboard is what would be otherwise proprietary but according to prelminary discussions with my engineers, can likely be cloned or functionally matched.  So my question is if someone has already photos or can make a bill of materials or components they see on the board.. or if they would sell me a working or non-working board and I'll get it done myself .. besides the asic chip listed (all the other transistors, etc.)  I can put it through to see if they can source everything.

I suppose I was hinting for partners in what may be a much bigger project, as I've already decided I'm going to make the investment for the chance to get it done provided the required chips are available.. some of the skills and perhaps material that this group may have, could make it a reality in which case there would be a very small group of people with access to the resulting product.  Yeah it's maybe a big dream, but it's worth it. Multi algo miners are the way to go and to understand and be able to create more efficient ones or more capable, isn't so far fetched.

In the meantime, my other question was a programming one.  Isnt the firmware what is provided to flash the system or is there a rom that is pre-programmed with base functions that would have to be decompiled?  

If you can source the chips, that would be a huge step toward cloning the whole miner, but I'm having a hard time picturing how you would do that ethically. I don't imagine Baikal is selling these chips on the open market.

If you decide to develop your own systems however, keep me in mind. I have some unique ideas about how to design a multi-algo asic to target a group of algorithms, but don't have the experience or resources to implement it in silicon. I also have a good idea of which algos and networks to target without causing a D3-level fiasco. Keep me in mind if you actually kick off this project.

The idea would definitely to be develop my own system ultimately, just using the x10 as a basemodel to build from.  With that said I have to either have a bill of materials or a board to provide so the determination can be made whether it can be done.  The ppl i'm working with say yes from photos Ive provided.. Companies do this all the time, use an existing design and improve. And yes they may not sell the chips on the open market but most likely it's their programming that's proprietary, Everything else is just components that may well be available, which is why I'm hoping someone would sell me a board or has more info on the components they find when they took apart a machine.. so I can find out.

With that said I'll probably move this discussion to a private one to find ppl seriously interested. 


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tboy32c on February 28, 2018, 03:22:52 PM
The idea would definitely to be develop my own system ultimately, just using the x10 as a basemodel to build from.  With that said I have to either have a bill of materials or a board to provide so the determination can be made whether it can be done.  The ppl i'm working with say yes from photos Ive provided.. Companies do this all the time, use an existing design and improve. And yes they may not sell the chips on the open market but most likely it's their programming that's proprietary, Everything else is just components that may well be available, which is why I'm hoping someone would sell me a board or has more info on the components they find when they took apart a machine.. so I can find out.

With that said I'll probably move this discussion to a private one to find ppl seriously interested. 

If you can procure the actual ASIC chips that changes everything. I'd definitely be interested if that were the case.

That being said, as you probably know, ASICs are Application Specific and aren't programmable or else they wouldn't be "application specific" by definition. The original prototype design is done on an FPGA which is Field Programmable and can, therefore, be reprogrammed. When ASICs are manufactured there's no need for them to be programmable anymore.

I found this to be a good read: http://www.7400.digital/ (http://www.7400.digital/).

I imagine all other components could be pretty easily sourced. The entire premise hinges on sourcing available ASICs, so I'd focus on that goal first before looking at the rest of the miner.

As mentioned, if you do find yourself with Baikal's ASICs in-hand, be sure to let me know.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: dmanukr on February 28, 2018, 04:30:40 PM
The idea would definitely to be develop my own system ultimately, just using the x10 as a basemodel to build from.  With that said I have to either have a bill of materials or a board to provide so the determination can be made whether it can be done.  The ppl i'm working with say yes from photos Ive provided.. Companies do this all the time, use an existing design and improve. And yes they may not sell the chips on the open market but most likely it's their programming that's proprietary, Everything else is just components that may well be available, which is why I'm hoping someone would sell me a board or has more info on the components they find when they took apart a machine.. so I can find out.

With that said I'll probably move this discussion to a private one to find ppl seriously interested. 

If you can procure the actual ASIC chips that changes everything. I'd definitely be interested if that were the case.

That being said, as you probably know, ASICs are Application Specific and aren't programmable or else they wouldn't be "application specific" by definition. The original prototype design is done on an FPGA which is Field Programmable and can, therefore, be reprogrammed. When ASICs are manufactured there's no need for them to be programmable anymore.

I found this to be a good read: http://www.7400.digital/ (http://www.7400.digital/).

I imagine all other components could be pretty easily sourced. The entire premise hinges on sourcing available ASICs, so I'd focus on that goal first before looking at the rest of the miner.

As mentioned, if you do find yourself with Baikal's ASICs in-hand, be sure to let me know.


Yes thanks am familiar but thanks for read... The X10 obviously is uniquein that something IS programmable otherwise it couldn't offer multiple and diverse algos. It's likely that the chosen algos share common set of routines that allowed the asic design while algo differentials are controlled by other components...guess of course.  My first thought was the STM chip on the controller and that may be but likely another chip on the hashboard. The STM chip is readily available but the controller board is complex..  more complex than the hashboard according to my contacts. 

Let's continue off public board.. anyone else interested are welcome to dm me.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Finsterkamm on February 28, 2018, 07:48:43 PM
Do you think those Baikal miners not based on this silicon chip? 
https://en.wikipedia.org/wiki/Baikal_CPU


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: adra12 on February 28, 2018, 10:29:13 PM
Do you think those Baikal miners not based on this silicon chip? 
https://en.wikipedia.org/wiki/Baikal_CPU

I think this is a different company, as Baikal miner is a Chinese company for sure. Of course it can easily happen that they are using just re-branded chips on their hashing boards.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: dmanukr on March 01, 2018, 01:21:09 AM
Do you think those Baikal miners not based on this silicon chip? 
https://en.wikipedia.org/wiki/Baikal_CPU

I think this is a different company, as Baikal miner is a Chinese company for sure. Of course it can easily happen that they are using just re-branded chips on their hashing boards.

The company you buy the miners from is a Chinese company, of which the miners is a small part of their business.. the ASIC chips in the miners are Russian.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Finsterkamm on March 01, 2018, 12:05:33 PM
Have any proof of that? :) Of course we can slip into speculation that since Baikal-T1 fabricated on TMSC, than there is a big chance that they ordered "something else" just some sort of collateral product. And this is exactly the ASICs we are talking of.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: darkly spectre on March 01, 2018, 11:55:36 PM
The idea would definitely to be develop my own system ultimately, just using the x10 as a basemodel to build from.  With that said I have to either have a bill of materials or a board to provide so the determination can be made whether it can be done.  The ppl i'm working with say yes from photos Ive provided.. Companies do this all the time, use an existing design and improve. And yes they may not sell the chips on the open market but most likely it's their programming that's proprietary, Everything else is just components that may well be available, which is why I'm hoping someone would sell me a board or has more info on the components they find when they took apart a machine.. so I can find out.

With that said I'll probably move this discussion to a private one to find ppl seriously interested. 

If you can procure the actual ASIC chips that changes everything. I'd definitely be interested if that were the case.

That being said, as you probably know, ASICs are Application Specific and aren't programmable or else they wouldn't be "application specific" by definition. The original prototype design is done on an FPGA which is Field Programmable and can, therefore, be reprogrammed. When ASICs are manufactured there's no need for them to be programmable anymore.

I found this to be a good read: http://www.7400.digital/ (http://www.7400.digital/).

I imagine all other components could be pretty easily sourced. The entire premise hinges on sourcing available ASICs, so I'd focus on that goal first before looking at the rest of the miner.

As mentioned, if you do find yourself with Baikal's ASICs in-hand, be sure to let me know.

I know ASICS are pre-burned for the function they are set to do. it IS possible to program them to do more than just one thing IF said functions are on the ASIC.

but what stumps me is the promised 2 extra algorithms. if these are trully ASICS then it shouldn't be possible to add two more algorithms since the algos should of been on the ASIC already.

so either these aren't ASICS or the future algorithms are already on the ASICs but they just haven't enabled them for whatever reason.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tboy32c on March 02, 2018, 12:41:05 AM
I know ASICS are pre-burned for the function they are set to do. it IS possible to program them to do more than just one thing IF said functions are on the ASIC.

but what stumps me is the promised 2 extra algorithms. if these are trully ASICS then it shouldn't be possible to add two more algorithms since the algos should of been on the ASIC already.

so either these aren't ASICS or the future algorithms are already on the ASICs but they just haven't enabled them for whatever reason.

I agree with you 100% on that and it is a great point. If there actually are additional algorithms then they should already be on the current ASICs and simply need to be enabled (which will be something to do with sgminer and/or the STM controller).


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: darkly spectre on March 02, 2018, 09:14:17 PM
man imagine if we finally figure out how to actually change shit on the X10 and enable those algos before anybody else. :P


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: dmanukr on March 03, 2018, 06:23:30 AM
I will PAY someone have for detailed X10 hash board photos on both sides without the heat sinks.  I will also pay for a full list of components that are recognizable on a hash board such as "3 - chips with code xyz, 10 chips with code "blah blah" .. etc. "   If you're willing to help on this contact me please.  



Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: zapatista34 on March 03, 2018, 07:06:15 AM
thanks for information bro  ::)


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tboy32c on March 03, 2018, 11:17:47 AM
I will PAY someone have for detailed X10 hash board photos on both sides without the heat sinks. I will also pay for a list of components that are recognizable on a hash board such as "3 - chips with code xyz, 10 chips with code "blah blah" .. etc. "   If you're willing to help on this contact me please. 

Here's one of the components on the hash boards (64 per board):

...the model number on the asic is this:

[Baikal Logo]
BK177280
ND33U

...



Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: darkly spectre on March 03, 2018, 08:25:48 PM
I will PAY someone have for detailed X10 hash board photos on both sides without the heat sinks. I will also pay for a list of components that are recognizable on a hash board such as "3 - chips with code xyz, 10 chips with code "blah blah" .. etc. "   If you're willing to help on this contact me please. 

Here's one of the components on the hash boards (64 per board):

...the model number on the asic is this:

[Baikal Logo]
BK177280
ND33U

...



we all knew that. he wants to know EVERYTHING on the hashboards in an attempt to know what components are used to invest into cloning it


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tboy32c on March 03, 2018, 08:48:55 PM
I will PAY someone have for detailed X10 hash board photos on both sides without the heat sinks. I will also pay for a list of components that are recognizable on a hash board such as "3 - chips with code xyz, 10 chips with code "blah blah" .. etc. "   If you're willing to help on this contact me please. 

Here's one of the components on the hash boards (64 per board):

...the model number on the asic is this:

[Baikal Logo]
BK177280
ND33U

...



we all knew that. he wants to know EVERYTHING on the hashboards in an attempt to know what components are used to invest into cloning it

Can we agree that without ASICs any attempt to clone the rest of the miner (in an effort to build a functioning miner) is pointless? Similar to cloning a pen but never having a source of ink or having access to 1000 crypto miners but without access to electricity. If they have a source of the X10 ASICs then the story changes. I'm just trying to save them time & effort from what would be a fruitless pursuit (as far as I can tell, anyway).


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: adra12 on March 03, 2018, 10:03:02 PM
Did anybody manage to restore the driver-baikalu.c source file? It would help a lot to understand how it is working with sgminer.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: dmanukr on March 03, 2018, 10:38:54 PM
I will PAY someone have for detailed X10 hash board photos on both sides without the heat sinks. I will also pay for a list of components that are recognizable on a hash board such as "3 - chips with code xyz, 10 chips with code "blah blah" .. etc. "   If you're willing to help on this contact me please. 

Here's one of the components on the hash boards (64 per board):

...the model number on the asic is this:

[Baikal Logo]
BK177280
ND33U

...



we all knew that. he wants to know EVERYTHING on the hashboards in an attempt to know what components are used to invest into cloning it

Can we agree that without ASICs any attempt to clone the rest of the miner (in an effort to build a functioning miner) is pointless? Similar to cloning a pen but never having a source of ink or having access to 1000 crypto miners but without access to electricity. If they have a source of the X10 ASICs then the story changes. I'm just trying to save them time & effort from what would be a fruitless pursuit (as far as I can tell, anyway).

Yes of course that's correct.  Without the asics it's pointless which is one reason I'm willing to pay someone for the info I've asked for.  It could save me time and alot of money to do what I hope to accomplish.  I won't comment publicly anymore on this topic anyone is free to contact me privately if interested


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: ismurdegus on March 04, 2018, 08:26:20 AM
I have some high resolution picture

https://imgur.com/a/MeXWH


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: CNoteFan on March 06, 2018, 03:38:29 AM
Did anybody manage to restore the driver-baikalu.c source file? It would help a lot to understand how it is working with sgminer.

I wish Baikal would release the sgminer source code. 

Anyone know if it falls under the same licensing as cgminer?
https://bitcointalk.org/index.php?topic=2694602.msg28367617#msg28367617


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: dmanukr on March 06, 2018, 04:16:06 AM
Did anybody manage to restore the driver-baikalu.c source file? It would help a lot to understand how it is working with sgminer.

I wish Baikal would release the sgminer source code. 

Anyone know if it falls under the same licensing as cgminer?
https://bitcointalk.org/index.php?topic=2694602.msg28367617#msg28367617

Don't count on them doing that.. they're using a version sgminer/5.6.3-l which must be a proprietary fork

Is it not possible to get it from the sd card?  That should be where it resides? 


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: adra12 on March 07, 2018, 06:00:17 PM
I wish Baikal would release the sgminer source code. 

Anyone know if it falls under the same licensing as cgminer?
https://bitcointalk.org/index.php?topic=2694602.msg28367617#msg28367617

In that case the initiation was started at bitcointalk, so they could end it very quickly if the source was not released.

You can check the original sgminer homepage:
https://github.com/sgminer-dev/sgminer (https://github.com/sgminer-dev/sgminer)
License: GPLv3. See COPYING for details.

Baikal just doesn't give a shit about it. Unfortunately no one can force them to release the source code, but they would need to do so.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: adra12 on March 12, 2018, 04:04:14 PM
I would like to share the bash history of an X10 machine. I have commented the commands, so you should be able to understand it even if you are not familiar with Linux commands.

If you notice a mistake or you have a suggestion, then please let me know. I can still edit the file.

https://pastebin.com/qit9sA9M (https://pastebin.com/qit9sA9M)



Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: dibidi on March 19, 2018, 11:35:01 PM
I would like to share the bash history of an X10 machine. I have commented the commands, so you should be able to understand it even if you are not familiar with Linux commands.

If you notice a mistake or you have a suggestion, then please let me know. I can still edit the file.

https://pastebin.com/qit9sA9M (https://pastebin.com/qit9sA9M)



Good morning.
Can I apply it in the same way as in url?
Does it work properly on x10?
Is there a command to add SGMINER Options in x10 miner setting?
I would appreciate your reply.
Thank you.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: adra12 on March 20, 2018, 09:24:48 AM

Good morning.
Can I apply it in the same way as in url?
Does it work properly on x10?
Is there a command to add SGMINER Options in x10 miner setting?
I would appreciate your reply.
Thank you.

These commands are just for reference if you intend to reverse-engineer their work step by step.

Unless you have the source code of sgminer and the firmware, it is pointless to issue the same commands as you don't have the same files.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: dmanukr on March 21, 2018, 01:37:32 AM
...
These commands are just for reference if you intend to reverse-engineer their work step by step.

Unless you have the source code of sgminer and the firmware, it is pointless to issue the same commands as you don't have the same files.

Isn't the firmware in the flashcard that is used?  The sgminer code may also be in that since it would be impractical to embed permanently into a rom, don't you think?  Anyone have any experience with this?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: CNoteFan on March 21, 2018, 02:30:45 AM
Has anyone tried to "undelete" from the SD after writing the image to it?  Perhaps the source is still there, just "deleted?"


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: adra12 on March 21, 2018, 10:21:51 AM
Isn't the firmware in the flashcard that is used?  The sgminer code may also be in that since it would be impractical to embed permanently into a rom, don't you think?  Anyone have any experience with this?

By the time you get your miner the firmware is flashed to the microcontroller. You can still obtain it, but it is as useful as the compiled sgminer. You can only edit it with a Hex editor, but development is not possible without the source code.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Finsterkamm on March 21, 2018, 11:43:54 AM
@CNoteFan:
It's hardly ever possible. Most likely developers are sitting on PC doing cross-development for OrangePi.
After that they release image for flashing there only binaries residues. No even traces of source code.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: CNoteFan on March 21, 2018, 03:05:40 PM
@CNoteFan:
It's hardly ever possible. Most likely developers are sitting on PC doing cross-development for OrangePi.
After that they release image for flashing there only binaries residues. No even traces of source code.



From the link above, some of the bash history from @adra12:

Code:
// Open the following file with VIM text editor for editing
vi driver-baikalu.c
 
// View sgminer CLI
sudo screen -r
 
// List content
ls
 
// List content
ls
 
// Delete this folder
rm -rf sgminer/


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: adra12 on March 21, 2018, 04:13:44 PM

From the link above, some of the bash history from @adra12:

Code:
// Open the following file with VIM text editor for editing
vi driver-baikalu.c
 
// View sgminer CLI
sudo screen -r
 
// List content
ls
 
// List content
ls
 
// Delete this folder
rm -rf sgminer/

That means that sgminer was compiled on the machine, and they deleted the folder with the source code. Still there are no traces of the source code of the firmware. And both of them are needed.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: CNoteFan on March 21, 2018, 07:35:45 PM

From the link above, some of the bash history from @adra12:

Code:
// Open the following file with VIM text editor for editing
vi driver-baikalu.c
 
// View sgminer CLI
sudo screen -r
 
// List content
ls
 
// List content
ls
 
// Delete this folder
rm -rf sgminer/

That means that sgminer was compiled on the machine, and they deleted the folder with the source code. Still there are no traces of the source code of the firmware. And both of them are needed.

For the meantime, I'd be happy with just some of the source!


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: dibidi on March 22, 2018, 09:03:50 AM

From the link above, some of the bash history from @adra12:

Code:
// Open the following file with VIM text editor for editing
vi driver-baikalu.c
 
// View sgminer CLI
sudo screen -r
 
// List content
ls
 
// List content
ls
 
// Delete this folder
rm -rf sgminer/

That means that sgminer was compiled on the machine, and they deleted the folder with the source code. Still there are no traces of the source code of the firmware. And both of them are needed.

I have a question. adra12
If you checked the firmware source code, did you check all three X10 firmware?
I know that there are three firmware versions in October, November, and December.
I have only the firmware in November, December. There is no firmware in October.
All three firmware did not have sgminer source code?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: adra12 on March 22, 2018, 10:03:27 AM
I have a question. adra12
If you checked the firmware source code, did you check all three X10 firmware?
I know that there are three firmware versions in October, November, and December.
I have only the firmware in November, December. There is no firmware in October.
All three firmware did not have sgminer source code?

I only have the following image file:
PiZero_GX10_171229_V1.1.img

And the microcontroller firmware I have is exactly the same like this one:
http://leteckaposta.cz/473537086 (http://leteckaposta.cz/473537086)

It would be nice to have the previous image, sgminer, firmware files for comparison.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: CNoteFan on March 23, 2018, 12:13:45 AM
I found quit a bit of the source for sgminer after writing the bin image(PiZero_GX10_171229_V1.1.img) to an SD card and looking at deleted files. 
Not sure if this has already been discovered.  Not sure if there's enough to actually compile a working version.

Here's some of what I found:

Code:
#ifndef __DEVICE_BAIKAL_H__
#define __DEVICE_BAIKAL_H__

#include "miner.h"

#define BAIKAL_MAXMINERS     (16)
#define BAIKAL_MAXASICS         (200)
#define BAIKAL_WORK_FIFO        (255)

#define BAIKAL_CLK_MIN  (150)
#define BAIKAL_CLK_DEF  (300)
#define BAIKAL_CLK_MAX     (300)
#define BAIKAL_CUTOFF_TEMP      (85)
#define BAIKAL_FANSPEED_DEF     (100)
#define BAIKAL_FANSPEED_MAX     (100)
#define BAIKAL_RECOVER_TEMP     (60)

#define BAIKAL_RESET     (0x01)
#define BAIKAL_GET_INFO         (0x02)
#define BAIKAL_SET_OPTION     (0x03)
#define BAIKAL_SEND_WORK     (0x04)
#define BAIKAL_GET_RESULT     (0x05)
#define BAIKAL_SET_ID     (0x06)
#define BAIKAL_SET_IDLE     (0x07)

#define BAIKAL_MINER_TYPE_NONE  (0x00)
#define BAIKAL_MINER_TYPE_MINI  (0x01)
#define BAIKAL_MINER_TYPE_CUBE  (0x02)

#define BAIKAL_ENABLE_SETCLK    (0)

struct asic_info {
    uint32_t nonce;
    uint32_t error;
};

struct miner_info {
    int     thr_id;
    int     asic_count; 
    int     unit_count;
int temp; 
    int     clock;
    bool    working;
    bool    overheated;
    uint8_t fw_ver;
    uint8_t hw_ver;
    uint8_t asic_ver;   
    uint32_t nonce;
    uint32_t error;   
    double working_diff;   
    struct asic_info asics[BAIKAL_MAXASICS];
    cgtimer_t start_time;
};


struct baikal_info {
    struct pool pool;
    int miner_count;
    int clock;
    uint8_t cutofftemp;
    uint8_t fanspeed; // percent
    uint8_t recovertemp;
pthread_t *process_thr;
    uint8_t work_idx;
    struct work *works[BAIKAL_WORK_FIFO];
    struct miner_info miners[BAIKAL_MAXMINERS];

    uint8_t miner_type;
};

typedef struct {
    uint8_t     miner_id;
    uint8_t     cmd;
    uint8_t     param;
    uint8_t     dest;
    uint8_t     data[512];
    uint32_t    len;
} baikal_msg;


#endif /* __DEVICE_BAIKAL_H__ */


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: CNoteFan on March 23, 2018, 01:00:58 AM
Looks like they decided to leave out the part that allows us to adjust the clock frequency...
Code:
...
#define BAIKAL_ENABLE_SETCLK    (0)
...
Code:
...
#if BAIKAL_ENABLE_SETCLK
    if (opt_baikal_options != NULL) {
        sscanf(opt_baikal_options, "%d:%d:%d", &clock, &recovertemp, &cutofftemp);
        if (clock < BAIKAL_CLK_MIN) {
            clock = BAIKAL_CLK_MIN;
        }
        if (clock > BAIKAL_CLK_MAX) {
            clock = BAIKAL_CLK_MAX;
        }
    }
#else
    if (opt_baikal_options != NULL) {
        sscanf(opt_baikal_options, "%d:%d", &recovertemp, &cutofftemp);
    }
#endif

    if (opt_baikal_fan != NULL) {
        sscanf(opt_baikal_fan, "%d", &fanspeed);
        if (fanspeed > BAIKAL_FANSPEED_MAX) {
            fanspeed = BAIKAL_FANSPEED_DEF;
        }
    }

    baikal = usb_alloc_cgpu(&baikalu_drv, 1);
    baikal->mutex = calloc(1, sizeof(*(baikal->mutex)));
    mutex_init(baikal->mutex);

    info = (struct baikal_info *)calloc(1, sizeof(struct baikal_info));
    info->clock         = clock;
    info->cutofftemp    = (uint8_t)cutofftemp;
    info->fanspeed      = (uint8_t)fanspeed;
    info->recovertemp   = (uint8_t)recovertemp;

    baikal->device_data = info;
    baikal->name        = strdup("BKLU");
    baikal->miner_id    = 0;
    baikal->algorithm   = default_profile.algorithm;

    miner = &info->miners[baikal->miner_id];
    cgtimer_time(&miner->start_time);
...


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tboy32c on March 23, 2018, 12:31:07 PM
I found quit a bit of the source for sgminer after writing the bin image(PiZero_GX10_171229_V1.1.img) to an SD card and looking at deleted files.  ...

Thanks for the info. Care to share what method you used to find the deleted files once the image was written to the SD card? Do the filenames seem to correlate with their contents?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: CNoteFan on March 23, 2018, 01:30:22 PM
I found quit a bit of the source for sgminer after writing the bin image(PiZero_GX10_171229_V1.1.img) to an SD card and looking at deleted files.  ...

Thanks for the info. Care to share what method you used to find the deleted files once the image was written to the SD card? Do the filenames seem to correlate with their contents?

I just used photorec to recovery any/all deleted files, then used astrogrep to do some searching.  The file names do not correlate.  Photorec just gives them a generic name.  We'll need more people searching for the other source files, my brain hurts.  ;o) 

Can someone post the very first image file for the X10? I have v1.0 and v1.1, but was thinking I heard someone mention an earlier one.

Code:
/*
 * Copyright 2012-2013 Andrew Smith
 * Copyright 2012 Luke Dashjr
 *
 * This program is free software; you can redistribute it and/or modify it
 * under the terms of the GNU General Public License as published by the Free
 * Software Foundation; either version 3 of the License, or (at your option)
 * any later version.  See COPYING for more details.
 */

#include "config.h"

#include <stdarg.h>
#include <stdio.h>
#include <unistd.h>
#include <math.h>
#include <pthread.h>

#include "logging.h"
#include "miner.h"
#include "usbutils.h"
#include "util.h"
#include "config_parser.h"
#include "driver-baikal.h"
#include "compat.h"
#include "algorithm.h"

static int baikal_sendmsg(struct cgpu_info *baikal, baikal_msg *msg)
{
    int err;
    int i, pos = 0;
    int amount;
    uint8_t buf[512] = {0, };

    buf[pos++] = ':';
    buf[pos++] = msg->miner_id;
    buf[pos++] = msg->cmd;
    buf[pos++] = msg->param;
    buf[pos++] = msg->dest;

    for (i = 0; i < msg->len; i++, pos += 2) {
        buf[pos + 1] = msg->data[i];
    }

    buf[pos++] = '\r';
    buf[pos++] = '\n';

    err = usb_write(baikal, (char *)buf, pos, &amount, C_BAIKAL_SEND);
    if (err < 0) {
        applog(LOG_ERR, "baikal_sendmsg error(%d)\n", err);
        return (err);
    }

    return (amount);
}


static int baikal_readmsg(struct cgpu_info *baikal, baikal_msg *msg, int size)
{
    int err;
    int amount;
    int len, pos = 1;
    uint8_t buf[128] = {0, };

    err = usb_read_once(baikal, (char *)buf, size, &amount, C_BAIKAL_READ);
    if (err < 0 || amount < 7) {
        return (err);
    }

    if ((buf[0] != ':') || (buf[amount - 2] != '\r') || (buf[amount - 1] != '\n')) {
        return (-1);
    }

    msg->miner_id   = buf[pos++];
    msg->cmd        = buf[pos++];
    msg->param      = buf[pos++];
    msg->dest       = buf[pos++];

    for (len = 0; pos < amount - 2; len++, pos += 2) {
        msg->data[len] = buf[pos + 1];
    }

    msg->len = len;

    return (amount);
}

static void baikal_cleanup(struct cgpu_info *baikal)
{
    int i;
    struct baikal_info *info  = baikal->device_data;
    struct miner_info *miner;
    struct cgpu_info *tmp;
    struct thr_info *thr;

    for (i = 0; i < info->miner_count; i++) {
        miner  = &info->miners[i];
        thr = mining_thr[miner->thr_id];

        if (thr) {
            tmp = thr->cgpu;
            tmp->shutdown = true;
            tmp->deven = DEV_DISABLED;
            usb_nodev(tmp);
        }
    }
}


static void baikal_clearbuffer(struct cgpu_info *baikal)
{
    int err, retries = 0;
    baikal_msg msg;

    do {
        err = baikal_readmsg(baikal, &msg, 128);
        usb_buffer_clear(baikal);
        if (err < 0)
            break;
    }
    while (retries++ < 10);
}


static bool baikal_finalize(struct cgpu_info *baikal)
{
    usb_uninit(baikal);

    if (baikal->device_data) {
        free(baikal->device_data);
        baikal->device_data = NULL;
    }

    if (baikal->mutex) {
        free(baikal->mutex);
    }

    if (baikal->name) {
        free(baikal->name);
    }

    baikal = usb_free_cgpu(baikal);

    return (true);
}


static bool baikal_reset(struct cgpu_info *baikal)
{
    int amount;
    struct baikal_info *info    = baikal->device_data;
    baikal_msg msg = {0, };

    msg.miner_id    = 0x0;
    msg.cmd         = BAIKAL_RESET;
    msg.len         = 0;
    msg.dest        = 0;

    mutex_lock(baikal->mutex);

    amount = baikal_sendmsg(baikal, &msg);
    if (amount < 0) {
        mutex_unlock(baikal->mutex);
        return (false);
    }

    cgsleep_ms(400);

    amount = baikal_readmsg(baikal, &msg, 7);
    if (amount < 0) {
        mutex_unlock(baikal->mutex);
        return (false);
    }

    info->miner_count = msg.param;

    mutex_unlock(baikal->mutex);

    return (true);
}


static bool baikal_getinfo(struct cgpu_info *baikal)
{
    int amount;
    uint16_t sign;
    baikal_msg msg = {0, };
    struct baikal_info *info    = baikal->device_data;
    struct miner_info *miner  = &info->miners[baikal->miner_id];

    msg.miner_id    = baikal->miner_id;
    msg.cmd         = BAIKAL_GET_INFO;
    msg.dest        = 0;
    msg.len         = 0;

    mutex_lock(baikal->mutex);

    amount = baikal_sendmsg(baikal, &msg);
    if (amount < 0) {
        mutex_unlock(baikal->mutex);
        return (false);
    }

    // TODO :
    cgsleep_ms(200);

    amount = baikal_readmsg(baikal, &msg, 21);
    if (amount < 0) {
        mutex_unlock(baikal->mutex);
        return (false);
    }

    mutex_unlock(baikal->mutex);

    miner->fw_ver       = msg.data[0];
    miner->hw_ver       = msg.data[1];
    miner->unit_count   = msg.data[2];
    miner->clock        = msg.data[3] << 1;
    miner->asic_count   = msg.data[4];
    miner->asic_ver     = msg.data[5] << 8 | msg.data[6];
    miner->working_diff = 0.01;
    miner->working      = true;
    miner->overheated   = false;

    return (true);
}


static bool baikal_setoption(struct cgpu_info *baikal, uint16_t clk, uint8_t mode, uint8_t temp, uint8_t fanspeed)
{
    int amount;
    baikal_msg msg = {0, };

    msg.miner_id    = baikal->miner_id;
    msg.cmd         = BAIKAL_SET_OPTION;
    msg.data[0] = (clk == 0) ? clk : ((clk / 10) % 20) + 2;
    msg.data[1] = mode;
    msg.data[2] = temp;
    msg.data[3] = fanspeed;
    msg.dest        = 0;
    msg.len         = 4;

    mutex_lock(baikal->mutex);

    amount = baikal_sendmsg(baikal, &msg);
    if (amount < 0) {
        mutex_unlock(baikal->mutex);
        return (false);
    }

    amount = baikal_readmsg(baikal, &msg, 7);
    if (amount < 0) {
        mutex_unlock(baikal->mutex);
        return (false);
    }

    mutex_unlock(baikal->mutex);

    return (true);
}


static bool baikal_setidle(struct cgpu_info *baikal)
{
    int amount;
    struct baikal_info *info    = baikal->device_data;
    baikal_msg msg = {0, };

    msg.miner_id    = 0x0;
    msg.cmd         = BAIKAL_SET_IDLE;
    msg.len         = 0;
    msg.dest        = 0;

    mutex_lock(baikal->mutex);

    amount = baikal_sendmsg(baikal, &msg);
    mutex_unlock(baikal->mutex);

    return (true);
}


static bool baikal_detect_remains(struct cgpu_info *baikal)
{
    int index;
    char devpath[32];
    struct baikal_info *info = baikal->device_data;
    struct miner_info *miner;

    for (index = 1; index < info->miner_count; index++) {

        struct cgpu_info *tmp = usb_copy_cgpu(baikal);

        sprintf(devpath, "%d:%d:%d",
                (int)(baikal->usbinfo.bus_number),
                (int)(baikal->usbinfo.device_address),
                index);

        tmp->device_path        = strdup(devpath);
        tmp->usbinfo.usbstat    = USB_NOSTAT;
        tmp->miner_id           = index;
        tmp->device_data        = baikal->device_data;
        tmp->mutex              = baikal->mutex;
        tmp->algorithm          = baikal->algorithm;
        tmp->threads            = 1;

        miner = &info->miners[tmp->miner_id];
        cgtimer_time(&miner->start_time);
        if (baikal_getinfo(tmp) == false) {
            tmp = usb_free_cgpu(tmp);
            continue;
        }

        if (baikal_setoption(tmp, info->clock, to_baikal_algorithm(baikal->algorithm.type), info->cutofftemp, info->fanspeed) != true) {
            tmp = usb_free_cgpu(tmp);
            continue;
        }

        if (!add_cgpu(tmp)) {
            tmp = usb_free_cgpu(tmp);
            continue;
        }

        update_usb_stats(tmp);
    }

    return (true);
}


static struct cgpu_info* baikal_detect_one(struct libusb_device *dev, struct usb_find_devices *found)
{
    struct cgpu_info *baikal;
    struct baikal_info *info;
    struct miner_info *miner;
    int clock           = BAIKAL_CLK_DEF;
    int cutofftemp      = BAIKAL_CUTOFF_TEMP;
    int fanspeed        = BAIKAL_FANSPEED_DEF;
    int recovertemp     = BAIKAL_RECOVER_TEMP;

#if BAIKAL_ENABLE_SETCLK
    if (opt_baikal_options != NULL) {
        sscanf(opt_baikal_options, "%d:%d:%d", &clock, &recovertemp, &cutofftemp);
        if (clock < BAIKAL_CLK_MIN) {
            clock = BAIKAL_CLK_MIN;
        }
        if (clock > BAIKAL_CLK_MAX) {
            clock = BAIKAL_CLK_MAX;
        }
    }
#else
    if (opt_baikal_options != NULL) {
        sscanf(opt_baikal_options, "%d:%d", &recovertemp, &cutofftemp);
    }
#endif

    if (opt_baikal_fan != NULL) {
        sscanf(opt_baikal_fan, "%d", &fanspeed);
        if (fanspeed > BAIKAL_FANSPEED_MAX) {
            fanspeed = BAIKAL_FANSPEED_DEF;
        }
    }

    baikal = usb_alloc_cgpu(&baikalu_drv, 1);
    baikal->mutex = calloc(1, sizeof(*(baikal->mutex)));
    mutex_init(baikal->mutex);

    info = (struct baikal_info *)calloc(1, sizeof(struct baikal_info));
    info->clock         = clock;
    info->cutofftemp    = (uint8_t)cutofftemp;
    info->fanspeed      = (uint8_t)fanspeed;
    info->recovertemp   = (uint8_t)recovertemp;

    baikal->device_data = info;
    baikal->name        = strdup("BKLU");
    baikal->miner_id    = 0;
    baikal->algorithm   = default_profile.algorithm;

    miner = &info->miners[baikal->miner_id];
    cgtimer_time(&miner->start_time);


    if (!usb_init(baikal, dev, found)) {
        goto out;
    }

    baikal_clearbuffer(baikal);

    if (baikal_reset(baikal) != true) {
        goto out;
    }

    /* TODO : Remove it */
    cgsleep_ms(200);

    if (baikal_getinfo(baikal) != true) {
        goto out;
    }

    if (baikal_setoption(baikal, clock, to_baikal_algorithm(default_profile.algorithm.type), cutofftemp, fanspeed) != true) {
        goto out;
    }

    if (!add_cgpu(baikal)) {
        goto out;
    }

    update_usb_stats(baikal);

    baikal_detect_remains(baikal);

    return (baikal);

out:
    baikal_finalize(baikal);
    return (NULL);
}


static void baikal_detect(void)
{
    usb_detect(&baikalu_drv, baikal_detect_one);
}


static void baikal_get_statline_before(char *buf, size_t bufsiz, struct cgpu_info *baikal)
{
    struct baikal_info *info    = baikal->device_data;
    struct miner_info *miner  = &info->miners[baikal->miner_id];

    tailsprintf(buf, bufsiz, "%s%dC %3uMHz [ASICS #%d] | ", (baikal->temp < 10) ? " " : "", (int)miner->temp, miner->clock, miner->asic_count);
}


static struct api_data* baikal_api_stats(struct cgpu_info *cgpu)
{
    struct baikal_info *info    = cgpu->device_data;
    struct miner_info *miner    = &info->miners[cgpu->miner_id];
    struct thr_info *thr = mining_thr[miner->thr_id];
    struct api_data *root = NULL;

    root = api_add_int(root, "Chip Count", (int *)&miner->asic_count, false);
    root = api_add_int(root, "Clock", (int *)&miner->clock, false);
    root = api_add_int(root, "HWV", (int *)&miner->hw_ver, false);
    root = api_add_int(root, "FWV", (int *)&miner->fw_ver, false);
    root = api_add_string(root, "Algo", (char *)algorithm_type_str[thr->cgpu->algorithm.type], false);

    return (root);
}


static void baikal_identify(struct cgpu_info *baikal)
{
    int amount;
    baikal_msg msg = {0, };

    msg.miner_id    = baikal->miner_id;
    msg.cmd         = BAIKAL_SET_ID;
    msg.dest        = 0;
    msg.len         = 0;

    mutex_lock(baikal->mutex);

    amount = baikal_sendmsg(baikal, &msg);
    if (amount < 0) {
        mutex_unlock(baikal->mutex);
        return;
    }

    amount = baikal_readmsg(baikal, &msg, 7);
    if (amount < 0) {
        mutex_unlock(baikal->mutex);
        return;
    }

    mutex_unlock(baikal->mutex);
}


static bool baikal_prepare(struct thr_info *thr)
{
    struct cgpu_info *baikal    = thr->cgpu;
    struct baikal_info *info    = baikal->device_data;

    cglock_init(&(info->pool.data_lock));

    return (true);
}


static void baikal_checknonce(struct cgpu_info *baikal, baikal_msg *msg)
{
    struct baikal_info *info = baikal->device_data;
    struct miner_info *miner = &info->miners[msg->miner_id];
    uint8_t work_idx, chip_id;
    uint32_t nonce;

    chip_id     = msg->data[4];
    work_idx    = msg->data[5];
    nonce       = *((uint32_t *)msg->data);

    if (info->works[work_idx] == NULL) {
          return;
    }

    /* check algorithm */
    if (info->works[work_idx]->pool->algorithm.type != baikal->algorithm.type) {
        return;
    }

    if (submit_nonce(mining_thr[miner->thr_id], info->works[work_idx], nonce) == true) {
        miner->nonce++;
    }
    else {
        miner->error++;
    }
}


static bool baikal_send_work(struct cgpu_info *baikal, int miner_id)
{
    struct baikal_info *info = baikal->device_data;
    struct miner_info *miner = &info->miners[miner_id];
    struct thr_info *thr = mining_thr[miner->thr_id];
    struct work *work;
    uint32_t target;
    baikal_msg msg;
    uint8_t algo;
    uint32_t * mdata,*wdata;

    /* Do not send */
    if (miner->overheated == true) {
        return (true);
    }
   
mutex_lock(baikal->mutex);
    if (info->works[info->work_idx] == NULL) {
        work = get_work(thr, miner->thr_id);                             
        info->works[info->work_idx] = work;

#if 0   /* TODO : Performance Check */
        if (thr->work_restart) {                   
            free_work(info->works[info->work_idx]);
            info->works[info->work_idx] = NULL;   
            applog(LOG_ERR, "work restart\n");     
        mutex_unlock(baikal->mutex);           
            return true;                           
        }                                         
#endif
    }
   
    if (work->pool->algorithm.type != thr->cgpu->algorithm.type) {
        thr->cgpu->algorithm.type = work->pool->algorithm.type;
    }

    work->device_diff = MAX(miner->working_diff, work->work_difficulty);
    //work->device_diff = MIN(miner->working_diff, work->work_difficulty);
    set_target(work->device_target, work->device_diff, work->pool->algorithm.diff_multiplier2, work->thr_id);

    memset(msg.data, 0x0, 512);
    msg.data[0] = to_baikal_algorithm(thr->cgpu->algorithm.type);
    msg.data[1] = miner_id;
    memcpy(&msg.data[2], &work->device_target[24], 8);
    if (*((uint32_t *)&msg.data[6]) != 0x0) { // TripleS
        memset(&msg.data[2], 0xFF, 4);
    }

    switch (baikal->algorithm.type) {
    case ALGO_BLAKECOIN:        // blake256r8
    case ALGO_VANILLA:
        if (work->pool->algorithm.calc_midstate) {   // use midstate
            msg.data[0] += 1;

            memcpy(&msg.data[10], work->midstate, 32);
            memcpy(&msg.data[42], &work->data[64], 16);
            be32enc_vect((uint32_t *)&msg.data[42], (const uint32_t *)&msg.data[42], 4);
            *((uint32_t *)&msg.data[58]) = 0x00000080;
            *((uint32_t *)&msg.data[94]) = 0x01000000;
            *((uint32_t *)&msg.data[102]) = 0x80020000;
            msg.len = 106;
        }
        else {
            memcpy(&msg.data[10], work->data, 80);
            be32enc_vect((uint32_t *)&msg.data[10], (const uint32_t *)&msg.data[10], 20);
            msg.len = 90;
        }
        break;

    case ALGO_DECRED:           // blake256r14
        if (work->pool->algorithm.calc_midstate) {   // use midstate
            msg.data[0] += 1;

            memcpy(&msg.data[10], work->midstate, 32);
            memcpy(&msg.data[42], &work->data[128], 52);
            *((uint32_t *)&msg.data[94]) = 0x01000080UL;
            *((uint32_t *)&msg.data[98]) = 0x00000000UL;
            *((uint32_t *)&msg.data[102]) = 0xa0050000UL;
            msg.len = 106;
        }
        else {
            memcpy(&msg.data[10], work->data, 180);
            msg.len = 190;
        }
        break;
    case ALGO_SIA:              // blake2b
        memcpy(&msg.data[10], work->data, 80);
        be32enc_vect((uint32_t *)&msg.data[10], (const uint32_t *)&msg.data[10], 20);
        msg.len = 90;
        break;

    case ALGO_LBRY:             // lbry-all
        memcpy(&msg.data[10], work->data, 112);
        be32enc_vect((uint32_t *)&msg.data[10], (const uint32_t *)&msg.data[10], 27);
        msg.len = 122;
        break;

    case ALGO_PASCAL:           // lbry-sha
        memcpy(&msg.data[10], work->data, 200);
        msg.len = 210;
        break;

    case ALGO_X11:
    case ALGO_X11GOST:
    case ALGO_SKEINCOIN:
    case ALGO_MYRIAD_GROESTL:
    case ALGO_QUARK:
    case ALGO_QUBIT:
    case ALGO_GROESTL:
    case ALGO_SKEIN2:
    case ALGO_NIST:
    case ALGO_CRYPTONIGHT:
    case ALGO_CRYPTONIGHT_LITE:
    case ALGO_BLAKE:
    case ALGO_VELTOR:
    default:
        memcpy(&msg.data[10], work->data, 80);
        msg.len = 90;
        break;
    }
    msg.miner_id    = miner_id;
    msg.cmd         = BAIKAL_SEND_WORK;
    msg.param       = info->work_idx;
    msg.dest        = 0;

    //mutex_lock(baikal->mutex);

    if (baikal_sendmsg(baikal, &msg) < 0) {
        applog(LOG_ERR, "baikal_send_work : sendmsg error[%d]", miner_id);
        mutex_unlock(baikal->mutex);
        return (false);
    }

    if (baikal_readmsg(baikal, &msg, 7) < 0) {
        applog(LOG_ERR, "baikal_send_work : readmsg error[%d]", miner_id);
        mutex_unlock(baikal->mutex);
        return (false);
    }

    /* update clock */
    miner->clock = msg.param << 1;

    info->work_idx++;
    if (info->work_idx >= BAIKAL_WORK_FIFO) {
        info->work_idx = 0;
    }

    if (info->works[info->work_idx] != NULL) {
        free_work(info->works[info->work_idx]);
        info->works[info->work_idx] = NULL;
    }
       
    cgtimer_time(&miner->start_time);
    mutex_unlock(baikal->mutex);

    return (true);
}


static bool baikal_process_result(struct cgpu_info *baikal)
{
    struct baikal_info *info = baikal->device_data;
    struct miner_info *miner;
    baikal_msg msg = {0, };
    int i;

    for (i = 0; i < info->miner_count; i++) {
        miner = &info->miners[i];
        if (miner->working == true) {           
            msg.miner_id    = i;
            msg.cmd         = BAIKAL_GET_RESULT;
            msg.dest        = 0;
            msg.len         = 0;

            mutex_lock(baikal->mutex);
            if (baikal_sendmsg(baikal, &msg) < 0) {
                applog(LOG_ERR, "baikal_process_result : sendmsg error");
                mutex_unlock(baikal->mutex);
                return (false);
            }

            if (baikal_readmsg(baikal, &msg, 23) < 0) {
                applog(LOG_ERR, "baikal_process_result : readmsg error miner_id = %d", i);
                mutex_unlock(baikal->mutex);
                return (false);
            }
            mutex_unlock(baikal->mutex);
           
            miner->temp = msg.data[6];

            if (msg.param & 0x01) {
                baikal_checknonce(baikal, &msg);
            }

            if (msg.param & 0x02) {
                baikal_send_work(baikal, i);   
            }

            if (msg.param & 0x04) {
                baikal_cleanup(baikal);  /* new miner detect*/             
            }             

            if (miner->temp > info->cutofftemp) {
                miner->overheated = true;
            }
            else if (miner->temp < info->recovertemp) {
                miner->overheated = false;
            }
            cgsleep_ms(1);
        }       
    }

    return (true);
}

static int64_t baikal_hash_done(struct cgpu_info *baikal, struct miner_info *miner, int elpased)
{
    int64_t hash_done = 0;

    switch(baikal->algorithm.type) {       
    case ALGO_CRYPTONIGHT:
        hash_done = miner->clock * miner->asic_count * elpased / 1776;
        break;
    case ALGO_CRYPTONIGHT_LITE:
        hash_done = miner->clock * miner->asic_count * elpased / 888;
        break;
    case ALGO_X11:
    case ALGO_QUARK:
    case ALGO_QUBIT:
    case ALGO_NIST: 
    case ALGO_SKEINCOIN:
    case ALGO_SKEIN2:
    case ALGO_MYRIAD_GROESTL:
    case ALGO_GROESTL:
        hash_done = miner->clock * miner->asic_count * elpased * 128;
        break;
    case ALGO_X11GOST:
    case ALGO_VELTOR:
        hash_done = miner->clock * miner->asic_count * elpased * 18;
        break;
   
    case ALGO_BLAKECOIN:
    case ALGO_DECRED:
    case ALGO_VANILLA:
    case ALGO_BLAKE:
        hash_done = miner->clock * miner->asic_count * elpased * 2048;
        break;

    case ALGO_SIA:   
        hash_done = miner->clock * miner->asic_count * elpased * 1024;
        break;   
    case ALGO_LBRY:
    case ALGO_PASCAL:
        hash_done = miner->clock * miner->asic_count * elpased * 512;
        break;
    }

    return hash_done;
}


static int64_t baikal_scanhash(struct thr_info *thr)
{
    struct cgpu_info *baikal = thr->cgpu;
    struct baikal_info *info = baikal->device_data;
    struct miner_info *miner = &info->miners[baikal->miner_id];
    cgtimer_t now;
    int elapsed, i;

    if (baikal->usbinfo.nodev) {
        return (-1);
    }

    if (baikal->miner_id == 0) {
        if (baikal_process_result(baikal) != true) {
            baikal_cleanup(baikal);
            return (-1);
        }
    }
    else {
        cgsleep_ms(100);
    }

    baikal->temp = miner->temp;

    cgtimer_time(&now);
    elapsed = cgtimer_to_ms(&now) - cgtimer_to_ms(&miner->start_time);
    miner->start_time = now;

    return (baikal_hash_done(baikal, miner, elapsed));   
}


static void baikal_update_work(struct cgpu_info *baikal)
{
    int i, j;
    struct timeval now;
    struct baikal_info *info = baikal->device_data;   
    //struct thr_info *thr = mining_thr[miner->thr_id];

    /* TODO : check when bk1791 160 chips used */
    if (baikal->miner_id == 0) {
        for (i = 0; i < info->miner_count; i++) {
            struct miner_info *miner = &info->miners[i];
            if (miner->working == true) {
                for (j = 0; j < miner->unit_count; j++) {
                    if (baikal_send_work(baikal, i) != true) {
                        baikal_cleanup(baikal);
                    }
                }
            }
        }
    }
}


static bool baikal_init(struct thr_info *thr)
{
    struct cgpu_info *baikal    = thr->cgpu;
    struct baikal_info *info    = baikal->device_data;
    struct miner_info *miner    = &info->miners[baikal->miner_id];

    //memset(miner, 0, sizeof(struct miner_info));
    miner->thr_id               = thr->id;
    cgtimer_time(&miner->start_time);
    return (true);
}


static void baikal_shutdown(struct thr_info *thr)
{
    struct cgpu_info *baikal = thr->cgpu;
    struct baikal_info *info = baikal->device_data;

    if (baikal->miner_id == 0) {
        baikal_setidle(baikal);
    }

    baikal->shutdown = true;
}


struct device_drv baikalu_drv = {
    .drv_id = DRIVER_baikalu,
    .dname = "Baikal",
    .name = "BKLU",
    .drv_detect = baikal_detect,
    .get_statline_before = baikal_get_statline_before,
    .get_api_stats = baikal_api_stats,
    .identify_device = baikal_identify,
    .thread_prepare = baikal_prepare,
    .thread_init = baikal_init,
    .hash_work              = hash_driver_work,
    .update_work            = baikal_update_work,
    //.flush_work             = baikal_update_work,
    .scanwork = baikal_scanhash,
    .thread_shutdown        = baikal_shutdown,
};


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tboy32c on March 23, 2018, 02:21:21 PM
I found quit a bit of the source for sgminer after writing the bin image(PiZero_GX10_171229_V1.1.img) to an SD card and looking at deleted files.  ...

Thanks for the info. Care to share what method you used to find the deleted files once the image was written to the SD card? Do the filenames seem to correlate with their contents?

I just used photorec to recovery any/all deleted files, then used astrogrep to do some searching.  The file names do not correlate.  Photorec just gives them a generic name.  We'll need more people searching for the other source files, my brain hurts.  ;o) 

Excellent discovery. Looks like this is pretty much all that is needed to build a custom sgminer for the Giants. Notice all the algorithms listed:

Code:
CRYPTONIGHT
CRYPTONIGHT_LITE
X11
QUARK
QUBIT
NIST
SKEINCOIN
SKEIN2
MYRIAD_GROESTL
GROESTL
X11GOST
VELTOR
BLAKECOIN
DECRED
VANILLA
BLAKE
SIA   
LBRY
PASCAL

Did you happen to find the file defining
Code:
ALGO_X11
ALGO_QUARK
ALGO_QUBIT
etc...
?

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.

Does anyone have an opinion on which fork of sgminer is the best to start from? Stripping all the GPU/OpenCL related code should probably be done first, then this source can be added.




Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: CNoteFan on March 23, 2018, 05:09:21 PM
Here it is.  A slightly modified algorithm.h file:

Code:
#ifndef ALGORITHM_H
#define ALGORITHM_H

#include "config.h"

#ifdef __APPLE_CC__
#include <OpenCL/opencl.h>
#else
#ifdef USE_GPU
#include <CL/cl.h>
#endif
#endif

#include <inttypes.h>
#include <stdbool.h>
#include <stddef.h>

#ifdef USE_GPU
#include "ocl/build_kernel.h"   // For the build_kernel_data type
#endif

#define SUPPORT_SIAPOOL        (0)

typedef enum {
  ALGO_UNK,
  ALGO_CRE,
  ALGO_SCRYPT,
  ALGO_NSCRYPT,
  ALGO_PASCAL,
  ALGO_X11,
  ALGO_X11GOST,
  ALGO_X13,
  ALGO_X14,
  ALGO_X15,
  ALGO_KECCAK,
  ALGO_QUARK,
  ALGO_TWE,
  ALGO_FUGUE,
  ALGO_NIST,
  ALGO_FRESH,
  ALGO_WHIRL,
  ALGO_NEOSCRYPT,
  ALGO_WHIRLPOOLX,
  ALGO_LYRA2RE,
  ALGO_LYRA2REV2,
  ALGO_PLUCK,
  ALGO_YESCRYPT,
  ALGO_YESCRYPT_MULTI,
  ALGO_BLAKECOIN,
  ALGO_BLAKE,
  ALGO_SIA,
  ALGO_DECRED,
  ALGO_VANILLA,
  ALGO_LBRY,
  ALGO_CRYPTONIGHT,
  ALGO_CRYPTONIGHT_LITE,
  ALGO_SKEINCOIN,
  ALGO_SKEIN2,
  ALGO_QUBIT,
  ALGO_MYRIAD_GROESTL,
  ALGO_GROESTL,
  ALGO_DIDAMOND,
  ALGO_NEVACOIN,
  ALGO_VELTOR,
  ALGO_MAX
} algorithm_type_t;


extern const char *algorithm_type_str[];

extern void gen_hash(const unsigned char *data, unsigned int len, unsigned char *hash);

#ifdef USE_GPU
struct __clState;
#endif

struct _dev_blk_ctx;

#ifdef USE_GPU
struct _build_kernel_data;
#endif

struct cgpu_info;
struct work;

/* Describes the Scrypt parameters and hashing functions used to mine
 * a specific coin.
 */
typedef struct _algorithm_t {
  char     name[20]; /* Human-readable identifier */
  algorithm_type_t type; //algorithm type
  const char *kernelfile; /* alternate kernel file */
  uint32_t n;        /* N (CPU/Memory tradeoff parameter) */
  uint8_t  nfactor;  /* Factor of N above (n = 2^nfactor) */
  double   diff_multiplier1;
  double   diff_multiplier2;
  double   share_diff_multiplier;
  uint32_t xintensity_shift;
  uint32_t intensity_shift;
  uint32_t found_idx;
  unsigned long long   diff_numerator;
  uint32_t diff1targ;
  size_t n_extra_kernels;
  long rw_buffer_size;
#ifdef USE_GPU
  cl_command_queue_properties cq_properties;
#endif
  void(*regenhash)(struct work *);
  void(*calc_midstate)(struct work *);
  void(*prepare_work)(struct _dev_blk_ctx *, uint32_t *, uint32_t *);
#ifdef USE_GPU
  cl_int(*queue_kernel)(struct __clState *, struct _dev_blk_ctx *, cl_uint);
#endif
  void(*gen_hash)(const unsigned char *, unsigned int, unsigned char *);

#ifdef USE_GPU
  void(*set_compile_options)(struct _build_kernel_data *, struct cgpu_info *, struct _algorithm_t *);
#endif
} algorithm_t;

typedef struct _algorithm_settings_t
{
const char *name;
algorithm_type_t type;
const char *kernelfile;
double   diff_multiplier1;
double   diff_multiplier2;
double   share_diff_multiplier;
uint32_t xintensity_shift;
uint32_t intensity_shift;
uint32_t found_idx;
unsigned long long   diff_numerator;
uint32_t diff1targ;
size_t n_extra_kernels;
long rw_buffer_size;
#ifdef USE_GPU
cl_command_queue_properties cq_properties;
#endif
void     (*regenhash)(struct work *);
void     (*calc_midstate)(struct work *);
void     (*prepare_work)(struct _dev_blk_ctx *, uint32_t *, uint32_t *);
#ifdef USE_GPU
cl_int   (*queue_kernel)(struct __clState *, struct _dev_blk_ctx *, cl_uint);
#endif
void     (*gen_hash)(const unsigned char *, unsigned int, unsigned char *);
#ifdef USE_GPU
void     (*set_compile_options)(build_kernel_data *, struct cgpu_info *, algorithm_t *);
#endif
} algorithm_settings_t;

/* Set default parameters based on name. */
void set_algorithm(algorithm_t* algo, const char* name);

/* Set to specific N factor. */
void set_algorithm_nfactor(algorithm_t* algo, const uint8_t nfactor);

/* Compare two algorithm parameters */
bool cmp_algorithm(const algorithm_t* algo1, const algorithm_t* algo2);

int to_baikal_algorithm(algorithm_type_t type);

#endif /* ALGORITHM_H */


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tboy32c 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.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: CNoteFan on March 24, 2018, 12:43:17 AM
Could be.  There are many copies of most of the files, I think they'll need to be compared to figure out the latest version.  I am hoping someone smarter than me can piece it together and at least get the clock rate adjustable.  Give me some more keywords to search for and I'll try to post more information.  The searches take a while to complete.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: fawasme on March 24, 2018, 04:04:44 AM
Will try to reocover more files. In the other hand, I was messing around the terminal of the X10, went in root mode to some folders inside where they code a lot about the clockrate of each of the three cards, will post about it later on guys.

I do believe Baikal will not help us to make more money, but if we get together we can make this machine a BEAST mining any algo at diffrerent clockrates!

Keep it up guys...very nice work! will help for sure...lets try to get this more private.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: fawasme on March 24, 2018, 04:13:45 AM
By the way, while looking at some TAR Files recovered, I do see a lot "fakeroot" mentions, and a "ustar" mention, maybe the wanna play us with some fakeroot login through terminal....

I am not a programmer but just saying...


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: cod3gen on March 24, 2018, 10:41:40 AM
Im more interested in what other coins can be mined. Currently what i have figured out is that;
Currently included:
X11
QUARK
QUBIT
SKEIN
MyrGroestl

Possible and highly likely alternatives listed below, however they are defined with a different type of X10 it seems, so im not sure it even will be possible for those that are for sale now:
- Groestl
- Nist5
- X11 Gost
- Veltor

These alternatives are based on recovered files. The code also seems to reveal that they have had the "new" CN miner a long time, actually it would seem as they maybe even started production of that one before X10.

Currently done recovering about 80% of the code, will probably start trying to recompile to see if it works tomorrow.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: ruplikminer on March 24, 2018, 02:59:10 PM
Im more interested in what other coins can be mined. Currently what i have figured out is that;
Currently included:
X11
QUARK
QUBIT
SKEIN
MyrGroestl

Possible and highly likely alternatives listed below, however they are defined with a different type of X10 it seems, so im not sure it even will be possible for those that are for sale now:
- Groestl
- Nist5
- X11 Gost
- Veltor

These alternatives are based on recovered files. The code also seems to reveal that they have had the "new" CN miner a long time, actually it would seem as they maybe even started production of that one before X10.

Currently done recovering about 80% of the code, will probably start trying to recompile to see if it works tomorrow.

Amazing I am very excited about it. I will have xome X10 soon. Keep us updated! :)


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: CNoteFan on March 24, 2018, 03:46:16 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.

Did those earlier generations use pi's also?  I've never messed with them.

Here's a couple snippets from another version that do contain Skein and Myriad Groestl:

Code:
...
static bool baikal_send_work(struct cgpu_info *baikal, int miner_id)
{
    struct baikal_info *info = baikal->device_data;
    struct miner_info *miner = &info->miners[miner_id];
    struct thr_info *thr = mining_thr[miner->thr_id];
    struct work *work;
    uint32_t target;
    baikal_msg msg;
    uint8_t algo;
    uint32_t * mdata,*wdata;

    /* Do not send */
    if (miner->overheated == true) {
        return (true);
    }

    mutex_lock(baikal->mutex);
    if (info->works[info->work_idx] == NULL) {
        work = get_work(thr, miner->thr_id);                             
        info->works[info->work_idx] = work;

#if 0   /* TODO : Performance Check */
        if (thr->work_restart) {                   
            free_work(info->works[info->work_idx]);
            info->works[info->work_idx] = NULL;   
            applog(LOG_ERR, "work restart\n");     
            mutex_unlock(baikal->mutex);           
            return true;                           
        }                                         
#endif
    }
   
    if (work->pool->algorithm.type != thr->cgpu->algorithm.type) {
        thr->cgpu->algorithm.type = work->pool->algorithm.type;
    }

    work->device_diff = MAX(miner->working_diff, work->work_difficulty);
    //work->device_diff = MIN(miner->working_diff, work->work_difficulty);
    set_target(work->device_target, work->device_diff, work->pool->algorithm.diff_multiplier2, work->thr_id);

    memset(msg.data, 0x0, 512);
    msg.data[0] = to_baikal_algorithm(thr->cgpu->algorithm.type);
    msg.data[1] = miner_id;
    memcpy(&msg.data[2], &work->device_target[24], 8);
    if (*((uint32_t *)&msg.data[6]) != 0x0) { // TripleS
        memset(&msg.data[2], 0xFF, 4);
    }

    switch (baikal->algorithm.type) {
    case ALGO_BLAKECOIN:        // blake256r8
        if (work->pool->algorithm.calc_midstate) {   // use midstate
            msg.data[0] += 1;

            memcpy(&msg.data[10], work->midstate, 32);
            memcpy(&msg.data[42], &work->data[64], 16);
            be32enc_vect((uint32_t *)&msg.data[42], (const uint32_t *)&msg.data[42], 4);
            *((uint32_t *)&msg.data[58]) = 0x00000080;
            *((uint32_t *)&msg.data[94]) = 0x01000000;
            *((uint32_t *)&msg.data[102]) = 0x80020000;
            msg.len = 106;
        }
        else {
            memcpy(&msg.data[10], work->data, 80);
            be32enc_vect((uint32_t *)&msg.data[10], (const uint32_t *)&msg.data[10], 20);
            msg.len = 90;
        }
        break;

    case ALGO_DECRED:           // blake256r14
        if (work->pool->algorithm.calc_midstate) {   // use midstate
            msg.data[0] += 1;

            memcpy(&msg.data[10], work->midstate, 32);
            memcpy(&msg.data[42], &work->data[128], 52);
            *((uint32_t *)&msg.data[94]) = 0x01000080UL;
            *((uint32_t *)&msg.data[98]) = 0x00000000UL;
            *((uint32_t *)&msg.data[102]) = 0xa0050000UL;
            msg.len = 106;
        }
        else {
            memcpy(&msg.data[10], work->data, 180);
            msg.len = 190;
        }
        break;
    case ALGO_SIA:              // blake2b
        memcpy(&msg.data[10], work->data, 80);
        be32enc_vect((uint32_t *)&msg.data[10], (const uint32_t *)&msg.data[10], 20);
        msg.len = 90;
        break;

    case ALGO_LBRY:             // lbry-all
        memcpy(&msg.data[10], work->data, 112);
        be32enc_vect((uint32_t *)&msg.data[10], (const uint32_t *)&msg.data[10], 27);
        msg.len = 122;
        break;

    case ALGO_PASCAL:           // lbry-sha
        memcpy(&msg.data[10], work->data, 200);
        msg.len = 210;
        break;

    case ALGO_X11:
    case ALGO_X11GOST:
    case ALGO_SKEINCOIN:
    case ALGO_MYRIAD_GROESTL:
    case ALGO_QUARK:
    case ALGO_QUBIT:
    case ALGO_GROESTL:
    case ALGO_SKEIN2:
    case ALGO_NIST:
    case ALGO_CRYPTONIGHT:
    case ALGO_CRYPTONIGHT_LITE:
    case ALGO_BLAKE:
    case ALGO_VANILLA:
    case ALGO_VELTOR:
    default:
        memcpy(&msg.data[10], work->data, 80);
        msg.len = 90;
        break;
    }
    msg.miner_id    = miner_id;
    msg.cmd         = BAIKAL_SEND_WORK;
    msg.param       = info->work_idx;
    msg.dest        = 0;

    //mutex_lock(baikal->mutex);

    if (baikal_sendmsg(baikal, &msg) < 0) {
        applog(LOG_ERR, "baikal_send_work : sendmsg error[%d]", miner_id);
        mutex_unlock(baikal->mutex);
        return (false);
    }

    if (baikal_readmsg(baikal, &msg, 7) < 0) {
        applog(LOG_ERR, "baikal_send_work : readmsg error[%d]", miner_id);
        mutex_unlock(baikal->mutex);
        return (false);
    }

    /* update clock */
    miner->clock = msg.param << 1;

    info->work_idx++;
    if (info->work_idx >= BAIKAL_WORK_FIFO) {
        info->work_idx = 0;
    }

    if (info->works[info->work_idx] != NULL) {
        free_work(info->works[info->work_idx]);
        info->works[info->work_idx] = NULL;
    }
       
    cgtimer_time(&miner->start_time);
    mutex_unlock(baikal->mutex);

    return (true);
}
...
Code:
...
static int64_t baikal_hash_done(struct cgpu_info *baikal, struct miner_info *miner, int elpased)
{
    int64_t hash_done = 0;

    switch(baikal->algorithm.type) {       
    case ALGO_CRYPTONIGHT:
        hash_done = miner->clock * miner->asic_count * elapsed / 1776;
        break;
    case ALGO_CRYPTONIGHT_LITE:
        hash_done = miner->clock * miner->asic_count * elapsed / 888;
        break;
    case ALGO_X11:
    case ALGO_QUARK:
    case ALGO_QUBIT:
    case ALGO_NIST: 
    case ALGO_SKEINCOIN:
    case ALGO_SKEIN2:
    case ALGO_MYRIAD_GROESTL:
    case ALGO_GROESTL:
        hash_done = miner->clock * miner->asic_count * elapsed * 128;
        break;
    case ALGO_X11GOST:
    case ALGO_VELTOR:
        hash_done = miner->clock * miner->asic_count * elapsed * 18;
        break;
   
    case ALGO_BLAKECOIN
    case ALGO_DECRED
    case ALGO_VANILLA
    case ALGO_BLAKE
        hash_done = miner->clock * miner->asic_count * elapsed * 2048;
        break;

    case ALGO_SIA   
        hash_done = miner->clock * miner->asic_count * elapsed * 1024;
        break;   
    case ALGO_LBRY
    case ALGO_PASCAL
        hash_done = miner->clock * miner->asic_count * elapsed * 512;
        break;
    }

    return hash_done;
}
...


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: adra12 on March 24, 2018, 07:44:02 PM

I just used photorec to recovery any/all deleted files, then used astrogrep to do some searching.  The file names do not correlate.  Photorec just gives them a generic name.  We'll need more people searching for the other source files, my brain hurts.  ;o)  

Can someone post the very first image file for the X10? I have v1.0 and v1.1, but was thinking I heard someone mention an earlier one.

Nice find!
Actually the c file source code looks like that it belongs to a Giant B based on the static bool baikal_send_work function. And the DEVICE_BAIKAL_H header file that you posted seems to belong to a MINI or CUBE miner. Strange...

Could you please upload the v1.0 image file to mega.nz or google drive?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: adra12 on March 24, 2018, 08:26:29 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?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: cod3gen on March 24, 2018, 09:26:27 PM
Nice find! Actually the source code looks like that it belongs to a Giant B, is that correct?

From what ive found, source code is same for X10, B and CN.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tboy32c 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.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: fawasme on March 24, 2018, 11:23:30 PM
Hey guys,


two things to say,

We need to work on two things, overclocking to 420MHz and to recover the data of the two algorithms. missing:

1) Will upload to Mega the recovered data so you can see for yourself what you can work with..

2) Will it help (overclocking) this info found in the SD Image?

root@Baikal:/sys/bus/cpu/devices/cpu0/cpufreq# ls                         
affected_cpus      cpuinfo_transition_latency   scaling_governor         
boot_lock          dvfs_debug                   scaling_max_freq         
cpuinfo_boot_freq  related_cpus                 scaling_min_freq         
cpuinfo_cur_freq   scaling_available_governors  scaling_setspeed         
cpuinfo_max_freq   scaling_cur_freq             stats
cpuinfo_min_freq   scaling_driver     

---------------------------------
  GNU nano 2.5.3          File: cpuinfo_cur_freq                         
                                                                         
816000                                                                   
                --

Also while messing with the terminal, an auto generated mail went to the root folder saying

Subject: *** SECURITY information for baikal ***                         

baikal : Feb 10 07:34:20 : www-data : user NOT in sudoers ; TTY=unknown ;$
                                                                         
From www-data@baikal  Fri Feb 10 07:35:24 2017                           
Return-Path: <www-data@baikal>                                           
Received: from baikal (baikal [127.0.0.1])                               
        by baikal (8.15.2/8.15.2/Debian-3) with ESMTP id v1A7ZOC3017405   
        for <root@baikal>; Fri, 10 Feb 2017 07:35:24 GMT                 
Received: (from www-data@localhost)                                       
        by baikal (8.15.2/8.15.2/Submit) id v1A7ZOLM017255;               
        Fri, 10 Feb 2017 07:35:24 GMT                                     
Date: Fri, 10 Feb 2017 07:35:24 GMT                                       
Message-Id: <201702100735.v1A7ZOLM017255@baikal>                         
To: root@baikal                                                           
From: www-data@baikal                                                     
Auto-Submitted: auto-generated                                           
Subject: *** SECURITY information for baikal ***                         
                                                                         
baikal : Feb 10 07:34:24 : www-data : user NOT in sudoers ; TTY=unknown ;$



Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: CNoteFan on March 25, 2018, 12:14:54 AM

I just used photorec to recovery any/all deleted files, then used astrogrep to do some searching.  The file names do not correlate.  Photorec just gives them a generic name.  We'll need more people searching for the other source files, my brain hurts.  ;o)  

Can someone post the very first image file for the X10? I have v1.0 and v1.1, but was thinking I heard someone mention an earlier one.

Nice find!
Actually the c file source code looks like that it belongs to a Giant B based on the static bool baikal_send_work function. And the DEVICE_BAIKAL_H header file that you posted seems to belong to a MINI or CUBE miner. Strange...

Could you please upload the v1.0 image file to mega.nz or google drive?

Here's a link to the undeleted bin (PiZero_GX10_171229_V1.1.img) file:

https://drive.google.com/file/d/14__gwiueXt-OBfkveUK_eMqmNhKxajni/view?usp=sharing (https://drive.google.com/file/d/14__gwiueXt-OBfkveUK_eMqmNhKxajni/view?usp=sharing)

I haven't started uploading the 4 gig (PiZero_GX10_171229_V1.0.img) file.  I'll do it if you really need it and of course if no one else uploads it!


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: pikachuy on March 25, 2018, 03:07:43 AM
If anyone have the Giant B and Giant x10 and don't mind doing a little work, can you take out the controller board (the board that goes on top of the 3 hash boards) and also the orange pi and swap them?

Want to see if the 3 hashing boards on the Giant B and Giant x10 are the same. If it works, then that means you will only need to update the controller board first, since just swapping out SD Cards does nothing.

It will be pointless trying to compile a custom sgminer if you require to update the controller board first.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: cod3gen on March 25, 2018, 02:53:49 PM
Ive been able to recompile sgminer based on files from X10 and CN, however some problems at hand with USB communcation to the boards, guess ill figure out those in a while. As an example i found nothing less than 33 different versions of driver-baikalu.c, so there will be some sorting before everythings ok.

Code:
sgminer 5.6.2-cod3gen - Started: [2018-03-25 16:45:04] - [0 days 00:00:16]
--------------------------------------------------------------------------------
(5s):0.000 (avg):0.000h/s | A:0  R:0  HW:0  WU:0.000/m
ST: 1  SS: 0  NB: 1  LW: 17  GF: 0  RF: 0
Connected to quark.eu.nicehash.com (stratum) diff 40 as user XXX
Block: 51abe371...  Diff:101M  Started: [16:45:03]  Best share: 0
--------------------------------------------------------------------------------
 [U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
--------------------------------------------------------------------------------
 [2018-03-25 16:45:02.877] Started sgminer 5.6.2-cod3gen
 [2018-03-25 16:45:02.877] * using Jansson 2.7
 [2018-03-25 16:45:02.878] Loaded configuration file /opt/scripta/etc/miner.conf

[b] [2018-03-25 16:45:03.098] No devices detected!
 [2018-03-25 16:45:03.099] Waiting for USB hotplug devices or press q to quit[/b]
 [2018-03-25 16:45:03.099] Probing for an alive pool
 [2018-03-25 16:45:03.480] Startup BaikalMiner initialization... Using settings
from pool quark.eu.nicehash.com.
 [2018-03-25 16:45:03.480] Startup Pool No = 0
 [2018-03-25 16:45:03.498] quark.eu.nicehash.com difficulty changed to 40.960
 [2018-03-25 16:45:09.102] API running in IP access mode on port 4028 (11)

If anyone have the Giant B and Giant x10 and don't mind doing a little work, can you take out the controller board (the board that goes on top of the 3 hash boards) and also the orange pi and swap them?

Want to see if the 3 hashing boards on the Giant B and Giant x10 are the same. If it works, then that means you will only need to update the controller board first, since just swapping out SD Cards does nothing.

It will be pointless trying to compile a custom sgminer if you require to update the controller board first.

X10, B and CN all have different chips, so i dont think it will be possible to cross them, i would not suggest that any one tries this unless they have no problem risking their hardware.

X10 seems to be able to support additional coins: groestl, nist5, x11-gost and veltor, thats atleast what im trying to figure out.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Selector79 on March 25, 2018, 03:08:43 PM
If anyone have the Giant B and Giant x10 and don't mind doing a little work, can you take out the controller board (the board that goes on top of the 3 hash boards) and also the orange pi and swap them?

Want to see if the 3 hashing boards on the Giant B and Giant x10 are the same. If it works, then that means you will only need to update the controller board first, since just swapping out SD Cards does nothing.

It will be pointless trying to compile a custom sgminer if you require to update the controller board first.

We tryed it.  It does not work.  They are different!


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Ironeinstein on March 25, 2018, 05:09:15 PM
Uploaded the three firmwares I have here:

https://drive.google.com/open?id=1Xyn5R6X38Jx4i9J50pF_upwgs0hdoXGN (https://drive.google.com/open?id=1Xyn5R6X38Jx4i9J50pF_upwgs0hdoXGN)

Files are PiZero_GX10_171111_V1.0.img, PiZero_GX10_171229_V1.1.img, PiZero_GB_180105_V1.0.img


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: CNoteFan on March 25, 2018, 06:25:37 PM
Ive been able to recompile sgminer based on files from X10 and CN, however some problems at hand with USB communcation to the boards, guess ill figure out those in a while. As an example i found nothing less than 33 different versions of driver-baikalu.c, so there will be some sorting before everythings ok.

Code:
sgminer 5.6.2-cod3gen - Started: [2018-03-25 16:45:04] - [0 days 00:00:16]
--------------------------------------------------------------------------------
(5s):0.000 (avg):0.000h/s | A:0  R:0  HW:0  WU:0.000/m
ST: 1  SS: 0  NB: 1  LW: 17  GF: 0  RF: 0
Connected to quark.eu.nicehash.com (stratum) diff 40 as user XXX
Block: 51abe371...  Diff:101M  Started: [16:45:03]  Best share: 0
--------------------------------------------------------------------------------
 [U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
--------------------------------------------------------------------------------
 [2018-03-25 16:45:02.877] Started sgminer 5.6.2-cod3gen
 [2018-03-25 16:45:02.877] * using Jansson 2.7
 [2018-03-25 16:45:02.878] Loaded configuration file /opt/scripta/etc/miner.conf

[b] [2018-03-25 16:45:03.098] No devices detected!
 [2018-03-25 16:45:03.099] Waiting for USB hotplug devices or press q to quit[/b]
 [2018-03-25 16:45:03.099] Probing for an alive pool
 [2018-03-25 16:45:03.480] Startup BaikalMiner initialization... Using settings
from pool quark.eu.nicehash.com.
 [2018-03-25 16:45:03.480] Startup Pool No = 0
 [2018-03-25 16:45:03.498] quark.eu.nicehash.com difficulty changed to 40.960
 [2018-03-25 16:45:09.102] API running in IP access mode on port 4028 (11)

If anyone have the Giant B and Giant x10 and don't mind doing a little work, can you take out the controller board (the board that goes on top of the 3 hash boards) and also the orange pi and swap them?

Want to see if the 3 hashing boards on the Giant B and Giant x10 are the same. If it works, then that means you will only need to update the controller board first, since just swapping out SD Cards does nothing.

It will be pointless trying to compile a custom sgminer if you require to update the controller board first.

X10, B and CN all have different chips, so i dont think it will be possible to cross them, i would not suggest that any one tries this unless they have no problem risking their hardware.

X10 seems to be able to support additional coins: groestl, nist5, x11-gost and veltor, thats atleast what im trying to figure out.


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")
...


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: cod3gen on March 25, 2018, 06:47:48 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.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: adra12 on March 25, 2018, 08:54:38 PM
Also while messing with the terminal, an auto generated mail went to the root folder saying

Subject: *** SECURITY information for baikal ***                          

baikal : Feb 10 07:34:20 : www-data : user NOT in sudoers ; TTY=unknown ;$
                                                                          
From www-data@baikal  Fri Feb 10 07:35:24 2017                            
Return-Path: <www-data@baikal>                                            
Received: from baikal (baikal [127.0.0.1])                                
        by baikal (8.15.2/8.15.2/Debian-3) with ESMTP id v1A7ZOC3017405  
        for <root@baikal>; Fri, 10 Feb 2017 07:35:24 GMT                  
Received: (from www-data@localhost)                                      
        by baikal (8.15.2/8.15.2/Submit) id v1A7ZOLM017255;              
        Fri, 10 Feb 2017 07:35:24 GMT                                    
Date: Fri, 10 Feb 2017 07:35:24 GMT                                      
Message-Id: <201702100735.v1A7ZOLM017255@baikal>                          
To: root@baikal                                                          
From: www-data@baikal                                                    
Auto-Submitted: auto-generated                                            
Subject: *** SECURITY information for baikal ***                          
                                                                          
baikal : Feb 10 07:34:24 : www-data : user NOT in sudoers ; TTY=unknown ;$

Don't worry about the mail part. It is the mail service of Ubuntu, which sends a mail to your own device if you log in, or you encounter an error, or security issue, etc.
Usually it is just bullshit.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: adra12 on March 25, 2018, 11:33:53 PM
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.

Nice job! This is what I call an achievement.

If everything is properly configured, then the hardware errors should be 0 on the X10. This indicates a slight misconfiguration in the driver-baikal header file. Probably some of the given values did not belong to the X10, but to another miner.

You should also try another pool other than Nicehash. If you are lucky, then your hardware errors might disappear.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tboy32c 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?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: CNoteFan on March 26, 2018, 01:48:29 AM
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.

Great job again!
We might just need to go through all the different versions of each source file to find which one is the most up to date.  For instance I "think" this is the latest/greatest device_baikal.h file:
Code:
#ifndef __DEVICE_BAIKAL_H__
#define __DEVICE_BAIKAL_H__

#include "miner.h"

#define BAIKAL_1751             (0x1)
#define BAIKAL_1772             (0x2)
#define BAIKAL_1791             (0x4)
#define BAIKAL_ALL              (0x7)
#define BAIKAL_TYPE             (BAIKAL_ALL)

#define BAIKAL_MAXMINERS     (5)
#define BAIKAL_MAXUNIT          (4)
#define BAIKAL_MAXASICS         (16)
#define BAIKAL_WORK_FIFO        (200)

#define BAIKAL_CLK_MIN  (150)
#define BAIKAL_CLK_MAX     (300)

#if BAIKAL_TYPE == BAIKAL_1751
#define BAIKAL_CLK_DEF  (200)
#elif BAIKAL_TYPE == BAIKAL_1791
#define BAIKAL_CLK_DEF  (400)
#else
#define BAIKAL_CLK_DEF  (300)
#endif

#define BAIKAL_CUTOFF_TEMP      (60)
#define BAIKAL_FANSPEED_DEF     (100)
#define BAIKAL_FANSPEED_MAX     (100)
#define BAIKAL_RECOVER_TEMP     (40)

#define BAIKAL_RESET     (0x01)
#define BAIKAL_GET_INFO         (0x02)
#define BAIKAL_SET_OPTION     (0x03)
#define BAIKAL_SEND_WORK     (0x04)
#define BAIKAL_GET_RESULT     (0x05)
#define BAIKAL_SET_ID     (0x06)
#define BAIKAL_SET_IDLE     (0x07)

#define BAIKAL_MINER_TYPE_NONE  (0x00)
#define BAIKAL_MINER_TYPE_MINI  (0x01)
#define BAIKAL_MINER_TYPE_CUBE  (0x02)

#define BAIKAL_ENABLE_SETCLK    (0)

#define BAIKAL_CHECK_STALE      (0)
#define BAIKAL_EN_HWE           (0)
#define BAIKAL_CLK_FIX          (1)

struct asic_info {
    uint32_t nonce;
    uint32_t error;
};

struct miner_info {
    int     thr_id;
    int     asic_count; 
    int     asic_count_r; 
    int     unit_count;
int temp; 
    int     clock;
    int     bbg;
    bool    working;
    bool    overheated;
    uint8_t fw_ver;
    uint8_t hw_ver;
    uint8_t asic_ver;   
    uint32_t nonce;
    uint32_t error;   
    double working_diff;   
    struct asic_info asics[BAIKAL_MAXUNIT][BAIKAL_MAXASICS];
    uint8_t work_idx;
    struct work *works[BAIKAL_WORK_FIFO];
    cgtimer_t start_time;
};


struct baikal_info {
    struct pool pool;
    int miner_count;
    int clock;
    uint8_t cutofftemp;
    uint8_t fanspeed; // percent
    uint8_t recovertemp;
pthread_t *process_thr;
    struct miner_info miners[BAIKAL_MAXMINERS];   
    uint8_t miner_type;
};

typedef struct {
    uint8_t     miner_id;
    uint8_t     cmd;
    uint8_t     param;
    uint8_t     dest;
    uint8_t     data[512];
    uint32_t    len;
} baikal_msg;


#endif /* __DEVICE_BAIKAL_H__ */


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Selector79 on March 26, 2018, 04:09:02 AM
Anybody knows if it is possible to get android system on baikal X10?

I think than is another way possible to hack the system!


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: cod3gen on March 26, 2018, 09:27:59 AM

Great job again!
We might just need to go through all the different versions of each source file to find which one is the most up to date.  For instance I "think" this is the latest/greatest device_baikal.h file:
Code:
#ifndef __DEVICE_BAIKAL_H__
#define __DEVICE_BAIKAL_H__

#include "miner.h"

#define BAIKAL_1751             (0x1)
#define BAIKAL_1772             (0x2)
#define BAIKAL_1791             (0x4)
#define BAIKAL_ALL              (0x7)
#define BAIKAL_TYPE             (BAIKAL_ALL)

#define BAIKAL_MAXMINERS     (5)
#define BAIKAL_MAXUNIT          (4)
#define BAIKAL_MAXASICS         (16)
#define BAIKAL_WORK_FIFO        (200)

#define BAIKAL_CLK_MIN  (150)
#define BAIKAL_CLK_MAX     (300)

#if BAIKAL_TYPE == BAIKAL_1751
#define BAIKAL_CLK_DEF  (200)
#elif BAIKAL_TYPE == BAIKAL_1791
#define BAIKAL_CLK_DEF  (400)
#else
#define BAIKAL_CLK_DEF  (300)
#endif

#define BAIKAL_CUTOFF_TEMP      (60)
#define BAIKAL_FANSPEED_DEF     (100)
#define BAIKAL_FANSPEED_MAX     (100)
#define BAIKAL_RECOVER_TEMP     (40)

#define BAIKAL_RESET     (0x01)
#define BAIKAL_GET_INFO         (0x02)
#define BAIKAL_SET_OPTION     (0x03)
#define BAIKAL_SEND_WORK     (0x04)
#define BAIKAL_GET_RESULT     (0x05)
#define BAIKAL_SET_ID     (0x06)
#define BAIKAL_SET_IDLE     (0x07)

#define BAIKAL_MINER_TYPE_NONE  (0x00)
#define BAIKAL_MINER_TYPE_MINI  (0x01)
#define BAIKAL_MINER_TYPE_CUBE  (0x02)

#define BAIKAL_ENABLE_SETCLK    (0)

#define BAIKAL_CHECK_STALE      (0)
#define BAIKAL_EN_HWE           (0)
#define BAIKAL_CLK_FIX          (1)

struct asic_info {
    uint32_t nonce;
    uint32_t error;
};

struct miner_info {
    int     thr_id;
    int     asic_count; 
    int     asic_count_r; 
    int     unit_count;
int temp; 
    int     clock;
    int     bbg;
    bool    working;
    bool    overheated;
    uint8_t fw_ver;
    uint8_t hw_ver;
    uint8_t asic_ver;   
    uint32_t nonce;
    uint32_t error;   
    double working_diff;   
    struct asic_info asics[BAIKAL_MAXUNIT][BAIKAL_MAXASICS];
    uint8_t work_idx;
    struct work *works[BAIKAL_WORK_FIFO];
    cgtimer_t start_time;
};


struct baikal_info {
    struct pool pool;
    int miner_count;
    int clock;
    uint8_t cutofftemp;
    uint8_t fanspeed; // percent
    uint8_t recovertemp;
pthread_t *process_thr;
    struct miner_info miners[BAIKAL_MAXMINERS];   
    uint8_t miner_type;
};

typedef struct {
    uint8_t     miner_id;
    uint8_t     cmd;
    uint8_t     param;
    uint8_t     dest;
    uint8_t     data[512];
    uint32_t    len;
} baikal_msg;


#endif /* __DEVICE_BAIKAL_H__ */

this is the current driver-baikal.h file that i use. Very similiar to the one you have

Code:
#ifndef __DEVICE_BAIKAL_H__
#define __DEVICE_BAIKAL_H__

#include "miner.h"

#define BAIKAL_1751             (0x1)
#define BAIKAL_1772             (0x2)
#define BAIKAL_1791             (0x4)
#define BAIKAL_ALL              (0x7)
#define BAIKAL_TYPE             (BAIKAL_ALL)

#define BAIKAL_MAXMINERS     (5)
#define BAIKAL_MAXUNIT          (4)
#define BAIKAL_MAXASICS         (16)
#define BAIKAL_WORK_FIFO        (200)

#define BAIKAL_CLK_MIN  (150)
#define BAIKAL_CLK_DEF  (400)
#define BAIKAL_CLK_MAX     (400)
#define BAIKAL_CUTOFF_TEMP      (55)
#define BAIKAL_FANSPEED_DEF     (100)
#define BAIKAL_FANSPEED_MAX     (100)
#define BAIKAL_RECOVER_TEMP     (40)

#define BAIKAL_RESET     (0x01)
#define BAIKAL_GET_INFO         (0x02)
#define BAIKAL_SET_OPTION     (0x03)
#define BAIKAL_SEND_WORK     (0x04)
#define BAIKAL_GET_RESULT     (0x05)
#define BAIKAL_SET_ID     (0x06)
#define BAIKAL_SET_IDLE     (0x07)

#define BAIKAL_MINER_TYPE_NONE  (0x00)
#define BAIKAL_MINER_TYPE_MINI  (0x01)
#define BAIKAL_MINER_TYPE_CUBE  (0x02)

#define BAIKAL_ENABLE_SETCLK    (0)

#define BAIKAL_CHECK_STALE      (0)
#define BAIKAL_EN_HWE           (0)
#define BAIKAL_CLK_FIX          (1)

struct asic_info {
    uint32_t nonce;
    uint32_t error;
};

struct miner_info {
    int     thr_id;
    int     asic_count; 
    int     asic_count_r; 
    int     unit_count;
int temp; 
    int     clock;
    int     bbg;
    bool    working;
    bool    overheated;
    uint8_t fw_ver;
    uint8_t hw_ver;
    uint8_t asic_ver;   
    uint32_t nonce;
    uint32_t error;   
    double working_diff;   
    struct asic_info asics[BAIKAL_MAXUNIT][BAIKAL_MAXASICS];
    uint8_t work_idx;
    struct work *works[BAIKAL_WORK_FIFO];
    cgtimer_t start_time;
};


struct baikal_info {
    struct pool pool;
    int miner_count;
    int clock;
    uint8_t cutofftemp;
    uint8_t fanspeed; // percent
    uint8_t recovertemp;
pthread_t *process_thr;
    struct miner_info miners[BAIKAL_MAXMINERS];   
    uint8_t miner_type;
};

typedef struct {
    uint8_t     miner_id;
    uint8_t     cmd;
    uint8_t     param;
    uint8_t     dest;
    uint8_t     data[512];
    uint32_t    len;
} baikal_msg;


#endif /* __DEVICE_BAIKAL_H__ */

Only difference is that in your version it sets clock depending on Baikal chip type(1751: CN, 1791: B), so it does no difference on X10, however it does difference to CN and B.

Ive tried to overclock it but its not possible at this moment, both by enabling ENABLE_SETCLK and disabling CLK_FIX, and even tried another definition of CLK_DEF. Even though sgminer says its set to 400 Mhz, it aint - seems to be limited on firmware level!

When it comes to different algo`s, none of them work (gives only HW errors) - either needed some updates in algo files, or what i think it is also limited at firmware level. However, i did gather some different power usages:
Quote
Groestl: Unknown @ 690w
Nist5: Unknown @ 690w
X11Gost: Unknown, but possibly 450MHs @ 450w

Code:
sgminer 5.6.2-cod3gen - Started: [2018-03-26 00:38:34] - [0 days 10:12:35]
--------------------------------------------------------------------------------
(5s):10.82G (avg):10.81Gh/s | A:9148  R:78  HW:381  WU:33820.422/m
ST: 1  SS: 0  NB: 638  LW: 2261672  GF: 0  RF: 0
Connected to quark.eu.nicehash.com (stratum) diff 5.24K as user XXX
Block: 57e616c6...  Diff:117M  Started: [10:48:08]  Best share: 10.8M
--------------------------------------------------------------------------------
 [U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
BKLU 0: 38C 400MHz [ASICS #64] | 3.604G/3.604Gh/s | A:2763 R: 21 HW: 54 WU:9921.705/m
BKLU 1: 38C 400MHz [ASICS #64] | 3.604G/3.604Gh/s | A:3194 R: 27 HW:150 WU:11941.753/m
BKLU 2: 38C 400MHz [ASICS #64] | 3.604G/3.604Gh/s | A:3191 R: 30 HW:177 WU:11956.965/m

Actual stats on nicehash is slightly lower than orginal version.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: cod3gen on March 26, 2018, 10:57:15 AM
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?

I will be adding current extracted code on github shortly, and hope that others can contribute.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: adra12 on March 26, 2018, 11:58:10 AM
this is the current driver-baikal.h file that i use. Very similiar to the one you have

Code:
#ifndef __DEVICE_BAIKAL_H__
#define __DEVICE_BAIKAL_H__

#include "miner.h"

#define BAIKAL_1751             (0x1)
#define BAIKAL_1772             (0x2)
#define BAIKAL_1791             (0x4)
#define BAIKAL_ALL              (0x7)
#define BAIKAL_TYPE             (BAIKAL_ALL)

#define BAIKAL_MAXMINERS    (5)
#define BAIKAL_MAXUNIT          (4)
#define BAIKAL_MAXASICS        (16)
#define BAIKAL_WORK_FIFO        (200)

#define BAIKAL_CLK_MIN   (150)
#define BAIKAL_CLK_DEF   (400)
#define BAIKAL_CLK_MAX    (400)
#define BAIKAL_CUTOFF_TEMP      (55)
#define BAIKAL_FANSPEED_DEF     (100)
#define BAIKAL_FANSPEED_MAX     (100)
#define BAIKAL_RECOVER_TEMP     (40)

#define BAIKAL_RESET    (0x01)
#define BAIKAL_GET_INFO        (0x02)
#define BAIKAL_SET_OPTION    (0x03)
#define BAIKAL_SEND_WORK    (0x04)
#define BAIKAL_GET_RESULT    (0x05)
#define BAIKAL_SET_ID    (0x06)
#define BAIKAL_SET_IDLE    (0x07)

#define BAIKAL_MINER_TYPE_NONE  (0x00)
#define BAIKAL_MINER_TYPE_MINI  (0x01)
#define BAIKAL_MINER_TYPE_CUBE  (0x02)

#define BAIKAL_ENABLE_SETCLK    (0)

#define BAIKAL_CHECK_STALE      (0)
#define BAIKAL_EN_HWE           (0)
#define BAIKAL_CLK_FIX          (1)

struct asic_info {
    uint32_t nonce;
    uint32_t error;
};

struct miner_info {
    int     thr_id;
    int     asic_count;  
    int     asic_count_r;  
    int     unit_count;
int temp;  
    int     clock;
    int     bbg;
    bool    working;
    bool    overheated;
    uint8_t fw_ver;
    uint8_t hw_ver;
    uint8_t asic_ver;    
    uint32_t nonce;
    uint32_t error;    
    double working_diff;    
    struct asic_info asics[BAIKAL_MAXUNIT][BAIKAL_MAXASICS];
    uint8_t work_idx;
    struct work *works[BAIKAL_WORK_FIFO];
    cgtimer_t start_time;
};


struct baikal_info {
    struct pool pool;
    int miner_count;
    int clock;
    uint8_t cutofftemp;
    uint8_t fanspeed; // percent
    uint8_t recovertemp;
pthread_t *process_thr;
    struct miner_info miners[BAIKAL_MAXMINERS];    
    uint8_t miner_type;
};

typedef struct {
    uint8_t     miner_id;
    uint8_t     cmd;
    uint8_t     param;
    uint8_t     dest;
    uint8_t     data[512];
    uint32_t    len;
} baikal_msg;


#endif /* __DEVICE_BAIKAL_H__ */

If you are already experimenting, then my recommendation is the following for the hardware errors:

Set the hardware error handling to 1 in the header file:
#define BAIKAL_EN_HWE           (1)

Comment out the following lines like this:
/*
#define BAIKAL_MINER_TYPE_NONE  (0x00)
#define BAIKAL_MINER_TYPE_MINI  (0x01)
#define BAIKAL_MINER_TYPE_CUBE  (0x02)
*/

Please let me know about the result.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: CNoteFan on March 26, 2018, 02:15:33 PM
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?

I will be adding current extracted code on github shortly, and hope that others can contribute.

Agreed, you have done an amazing job.  I'd be surprised if we can't at least get the code up to par with the compiled sgminer.  Do you make changes on the orange pi itself and compile/test or do you do all of that on a separate pc?  From reading the bash history, of which there is a ton of, it appears they were compiling on the device during testing. 

Here's a chunk of it:
Code:
./configure 
make
ls
chmod a+x ./update.sh
ls
sudo ./update.sh
sudo screen -r
sudo /opt/scripta/startup/miner-stop.sh
sudo screen -r
sudo reboot
vi /etc/rc.local
ls
cd
ls
ls -al
rm -rf .subversion/
ls
sudo shutdown -h now
sudo chmod 755 /etc/rc.local
sudo reboot
lsmod
sudo shutdown -h now
ls
vi /etc/rc.local
sudo screen -r
ls
cd scripta/
ls
cd etc/
ls
sudo cp /etc/rc.local  rc.local.zero
ls
svn diff
cd
ls
cd ls
sudo vi /etc/rc.local
sudo reboot
ls
sudo vi /etc/rc.local
sudo reboot
ls
sudo /etc/rc.local
sudo vi /etc/rc.local
sudo reboot
ls
sudo ntpd -qg
date
suvo vi /etc/rc.local
sudo vi /etc/rc.local
sudo reboot
sudo screen -r
ls
sudo vi /etc/rc.local
sudo reboot
ls
sudo vi /etc/rc.local
reboot
sudo reboot
sudo screen -r
ls
sudo vi /etc/rc.local
sudo reboot
sudo /etc/rc.local
sudo vi /etc/rc.local
sudo reboot
sudo vi /etc/rc.local
sudo reboot
ls
sudo vi  /etc/rc.local
sudo vi /etc/default/ntp
sduo vi /etc/ntp.conf
sudo vi /etc/ntp.conf
sudo reboot
sudo screen -r
ls
sudo vi /etc/rc.local
ls
sudo vi /etc/rc.local
sudo reboot
ls
cd scripta/
ls
cd etc/
ls
vi rc.local.zero
sudo screen -r
sudo reboot
cd scripta/etc/
ls
vi rc.local
vi rc.local.zero
sudo screen -r
ls
sudo vi /etc/rc.local
sudo reboot
ls
sudo vi /etc/rc.local
sudo reboot
sudo screen -r
sudo vi /etc/rc.local
sudo hwclock --show
sudo hwclock --systohc
sudo hwclock --show
sudo apt-get install fake-hwclock
sudo /etc/init.d/fake-hwclock start
sudo reboot
date
sudo screen -r
ls
sudo vi /etc/rc.local
sudo reboot
ls
cd scripta/
ls
vi install_zero.sh
date
sudo screen -r
cd
ls
cd scripta/
ls
cd etc/
ls
cp /etc/rc.local rc.local.zero
svn commit -m "modify rc.local.zero" .
cd ..
svn update
ls
cp update_one.sh update_zero.sh
vi update_zero.sh
ls
svn add update_zero.sh
svn update
svn diff
svn status
svn commit -m ""
ls
chmod a+x ./update_zero.sh
ls
sudo ./update_zero.sh
sudo reboot
ls
cd sgminer-5.5.0/
ls
chmod a+x ./autogen.sh
./autogen.sh
ls
./configure
make
ls
sudo ./update.sh
cd
ls
sudo screen -r
sudo reboot
sudo screen -r
ls
rm -rf sgminer-5.5.0/
ls
sudo shutdown -h
sudo shutdown -h now
sudo screen -r
sudo apt-get install samba
sudo shutdonw -h now
sudo shutdown -h now
cd /opt/
ls
cd baikal_back20161213185554/
ls
cd e
cd www/
ls
cd html/
ls
cd
ls
cd /opt/
ls
cd scripta/
ls
cd etc/
ls
cd backup/
ls
cd Example/
ls
cd etc/
ls
vi miner.options.json
sudo vi miner.pools.json
ls
vi scripta.conf
ls
vi miner.conf
sudo vi miner.conf
cd ..
ls
cd ..
ls
sudo rm -rf Example/
sudo mv 20170209-1925/ Example
cd
ls
sudo cp miner.html /var/www/partials/
sudo cp login.php /var/www/
ls
cd /var/www/
ls
ls -l
vi login.php
sudo vi login.php
cd /var/www/partials/
ls
vi miner.html
cd ..
ls
sudo vi login.php
ls
sudo shutdown -h now
cd /var/www/
ls
cd
ls
ifconfig
sudo cp login.php /var/www/
ls
sudo cp login.php /var/www/
ls
cd /opt/
ls
cd scripta/
ls
cd etc/
ls
cd backup/
ls
rm -rf Example/
sudo rm -rf Example/
ls
sudo mv 20170210-1625/
sudo mv 20170210-1625/ Example
ls
sudo cp 20170210-1627/* Nicehash-USA/
sudo cp -a  20170210-1627/* Nicehash-USA/
ls
rm -rf 20170210-1627/
sudo rm -rf 20170210-1627/
ls
sudo cp -a 20170210-1630/* Zpool/
sudo rm -rf 20170210-1630/
ls
sudo cp -a 20170210-1631/* Nicehash-Japan/
sudo rm -rf 20170210-1631/
ls
sudo cp -a 20170210-1632/ Zpool/
sudo rm -rf 20170210-1632/
ls -l
ls
l s-l
ls -l;
ls -l
sudo chown -R www-data.www-data .
ls -l
sudo cp -a 20170210-1633/* Nicehash-USA/
ls
cat 20170210-1633/etc/miner.conf
q
ls
rm -rf 20170210-1633/
sudo rm -rf 20170210-1633/
ls
cd 20170210-1635/
ls
cd etc/
ls
vi miner.
vi miner.conf
cd ..
ls
sudo cp -a 20170210-1635/* Nicehash-Japan/
sudo rm -rf 20170210-1635/
ls
sudo cp -a 20170210-1652/* Nicehash-Europe/
ls
sudo rm 20170210-1652/
sudo rm -rf 20170210-1652/
ls
sudo cp -a 20170210-1656/* Nicehash-China/
cd Nicehash-
cd Nicehash-China/
cd etc/
ls
vi miner.conf
cd ..
ls
sudo rm -rf 20170210-1656/
ls
sudo cp -a 20170210-1657/* Miningpoolhub/
sudo rm -rf 20170210-1657/
ls
sudo cp -a 20170210-1702/* Zpool/
sudo rm -rf 20170210-1702/
ls
cd
ls
cp -a /opt/scripta/etc/backup/* .
ls
rm -rf Example/
rm -rf Miningpoolhub/
rm -rf Nicehash-China/
rm -rf Nicehash-*
ls
rm -rf Zpool/
ls
rm -rf login.php
rm -rf miner.html
ls
cd
ls
cd
ls
ls -al
cd .cache/
ls
ls -al
rm -rf motd.legal-displayed
ls
cd ..
ls
sudo shutdown -h now
ls
df
cd
ls
sudo cp f_settings.php /var/www/
sudo cp miner.html  /var/www/partials/
cd /var/www/
ls
ls -l
cd partials/
ls
ls -l
cd
ls
cd /opt/scripta/etc/
ls
cd backup/
ls
ls -l
sudo cp -a /home/baikal/backup/* .
ls -l
cd ..
ls
ls -l
sudo chown -R www-data.root backup/
ls -l
cd backup/
ls -l
cd Example/
ls
ls -l
cd etc/
ls -l
ls
cd
ls
rm -rf f_settings.php
rm -rf miner.html
ls
cd /opt/scripta/etc/
ls
vi miner.conf
ls
sudo shutdown -h now
ls
cd backup/
ls
cd
ls
rm -rf backup/
ls
sudo svn co svn://192.168.0.5/baikal/software/trunk/sgminer-5.5.0
ls
cd sgminer-5.5.0/
ls
chmod a+x autogen.sh
sudo ./autogen.sh
ls
./autogen.sh
ls -l
sudo chown -R baikal.baikal .
ls -l
./autogen.sh
./configure
make
ls
sudo ./update.sh
ls
cd
ls
sudo rm -rf sgminer-5.5.0/
ls
ls -al
rm -rf .subversion/
ls
sudo shutdown -h now
cd /opt/scripta/etc/
ls
sudo vi /etc/rc.local
sync
sudo shutdown -h ow
sudo shutdown -h now
sudo halt
sudo cp f_settings.php /var/www/
cd /var/www/
ls
ls -l
vi f_settings.php
cd
ls
rm f_settings.php
ls
sudo reboot
sudo halt
vi /var/www/f_settings.php
ls
sudo screen -r
ls
sudo rm -rf /opt/scripta/bin/sgminer
sudo screen -r
ls -l /opt/scripta/bin/
ls
sudo cp ./sgminer  /opt/scripta/bin/
cd /opt/scripta/bin/
ls
sudo chmod 755 sgminer
ls -l
cd
ls
rm -rf sgminer
sudo screen -r
sudo halt
ls
sudo vi /etc/rc.local
ls
sudo rm -rf /opt/scripta/bin/sgminer
sudo cp ./sgminer  /opt/scripta/bin/
cd /opt/scripta/bin/
ls
sudo chmod a+x sgminer
ls
cd
ls
rm sgminer
sudo screen -r
sudo reboot
sudo screen -r
ls
sudo vi /etc/rc.local
sudo reboot
cd /opt/scripta/etc/
ols
ls
sudo vi miner.conf
sudo vi miner.pools.json
sudo vi miner.conf
ls
cd backup/
ls
cd Example/
ls
ced etc/
ls
cd etc/
ls
sudo cp /opt/scripta/etc/miner.conf  .
ls -l
sudo cp /opt/scripta/etc/miner.pools.json  .
ls
vi miner.conf
ls
sudo vi miner.pools.json
ls
cd
ls
sudo halt
sudo vi /etc/rc.local
sync
sudo reboot
svn co
svn co svn://bkls.asuscomm.com/baikal/software/trunk/sgminer-5.5.0
ls
cd sgminer-5.5.0/
ls
chmod a+x autogen.sh
./autogen.sh
./configure
make
chmod a+x ./update.sh
sudo ./update.sh
sudo reboot
ls
sudo rm -rf sgminer-5.5.0/
ls
ls -al
rm -rf .subversion/
sudo halt
sudo screen -r
cd /var/www/
ls
vi login.php
sudo vi login.php
cd
ls
htop
top
ls
svn co svn://bkls.asuscomm.com/baikal/software/trunk/sgminer-5.5.0
ls
cd sgminer-5.5.0/
ls
chmod a+x ./autogen.sh
./autogen.sudo apt-get update
sudo dpkg --configure -a
sudo apt-get update
sudo dpkg --configure -a
sudo dpkg --configure
sudo apt-get autoremove
sudo apt-get clean
sudo apt-get update
dmesg
top
ls
sudo apt-get update
dmesg
sudo vi /etc/sysctl.conf
top
ls
cd /opt/scripta/bin/
ls
mv sgminer sgminer_org
sudo mv sgminer sgminer_org
sudos screen -r
sudo screen -r
qq
sudo screen -r
top
q
sudo apt-get update
dmesg
ls
cd
ls
sudo reboot
ls
top
sudo apt-get update
sudo /etc/init.d/lighttpd stop
sudo /etc/init.d/samba stop
sudo apt-get update
ls
sudo apt-get upgrade
ls
sudo reboot
top
sudo apt-get remove samba
sudo reboot
ls
cd /opt/scripta/bin/
ls
sudo mv sgminer_org sgminer
ls
cd
ls
top
sudo apt-get update
sudo halt
ls
top
sudo apt-get upgrade
sudo apt-get install -y samba avahi-daemon dnsmasq
ls
sudo apt-get upgrade
ls
sudo rm -rf /opt/scripta/bin/sgminer
sudo mv sgminer  /opt/scripta/bin/
cd /opt/scripta/bin/
ls
sudo chmod a+x sgminer
ls -l
sudo screen -r
q
sudo /etc/init.d/samba restart
sudo /etc/init.d/avahi-daemon restart
sudo /etc/init.d/dnsmasq restart
sudo reboot
ls
ls -al
rm -rf .subversion/
ls
sudo screen -r
ls
sudo halt
sudo screen -r
sudo halt
ls
ls -al
ls
sudo rm -rf /opt/scripta/bin/sgminer
sudo mv ./sgminer  /opt/scripta/bin/
sudo screen -r
ls
sudo screen -r
ls
cd
ls
cd /etc/cron.d
ls
vi scripta
ls
sudo screen -r
cd
ls
cd /opt/scripta/bin/
ls
sudo chmod a+x ./sgminer
ls
sync
sudo halt
sudo screen -r
ls
kls
sudo vi /etc/rc.local
sudo shutdown -h now
sudo vi /etc/rc.local
sudo vi /etc/rc.local
sudo rm /etc/.rc.local.swp
sudo vi /etc/rc.local
sync
sudo reboot
sudo vi /etc/rc.local
ls
top
sudo halt
sudo /etc/init.d/watchdog start
sync
sudo reboot
htop
sudo service watchdog init
sudo service watchdog  start
sync
sudo reboot
htop
sudo update-rc.d
sudo update-rc.d watchdog defaults
sudo reboot
ls
htop
sudo /etc/init.d/watchdog start
htop
sudo service watchdog start
sudo service watchdog restart
sudo service watchdog start
sudo reboot
cd /sys/devices/platform/sunxi-ddrfreq/
ls
cd devfreq/
ls
cd sunxi-ddrfreq/
ls
cat scaling_max_freq
ls
cat scaling_min_freq
cat cur_freq
cat max_freq
sudo reboot
htop
ps aux
ps aux | grep watch
ls
serice watchdog status
service watchdog status
sudo vi /etc/rc.local
serice watchdog status
sudo service watchdog status
sudo vi /etc/watchdog.conf
sudo service watchdog restart
sudo service watchdog status
sudo reboot
service watchdog status
sync
sudo service watchdog status
sudo vi /etc/watchdog.conf
ls
cd
ls
svn co svn://bkls.asuscomm.com/baikal/software/trunk/sgminer-5.5.0
ls
cd sgminer-5.5.0/
ls
svn update
cd ..
ls
rm -rf .subversion/
ls
ls -al
cd sgminer-5.5.0/
ls
chmod a+x autogen.sh
./autogen.sh
./configure
make
sudo ./update.sh
ls
sudo shutdown -h now
ls
cd sgminer-5.5.0/
ls
svn update
ls
cd .svn/
ls
vi entries
ls
cd ..
svn relocate
svn help relocate
ls
rm -rf *
ls
ls -al
rm -rf .svn/
ls
cd ..
ls
rm -rf sgminer-5.5.0/
ls
svn co svn://192.168.0.5/baikal/software/trunk/sgminer-5.5.0
cd sgminer-5.5.0/
ls
chmod a+x autogen.sh
./autogen.sh
./configure
make
ls
sudo ./update.sh
ls
sudo shutdown -h now
ls
rm -rf sgminer-5.5.0/
ls
cd
ls
ls -al
rm -rf .subversion/
ls
ls -al
sudo shutdown -h now
cd /opt/scripta/etc/
ls
cd backup/
ls
cd 20170321-1917/
ls
cd etc/
ls
cd ..
ls
cd ..
ls
cd Example/
ls
cd etc/
ls
ls -l
sudo cp ../../20170321-1917/etc/* .
ls
ls -l
cd ..
ls
cd ..
ls
sudo rm -rf 20170321-1917/
ls
cd ..
sudo screen -r
sudo halt
ls
sudo visudo
sudo visudo
ls
sudo /etc/sudoers
sudo visudo
sudo reboot
ls
sudo visudo
ls
sudo screen -r
sudo reboot
sudo screen -r
sudo ls
sudo shutdown -h now
ls
sudo screen -r
sudo shutdown
sudo shutdown -h now
ls
cd
ls
sudo sudo ln -fs /usr/share/zoneinfo/Asia/Shanghai /etc/localtime
date
sudo apt-get install ntp
ls
date

sudo timedatectl
sudo /etc/init.d/ntp stop
sudo timedatectl
top
cd /etc/cron.d
ls
vi scripta
sudo apt-get remove ntp
ntpdate --help
ntpdate /?
ntpdate --help
ntpdate -b
cd
ls
sudo ntpdate -b -u 0.pool.ntp.org
sudo ntpdate -b -u 0.pool.ntp.orgg
sudo ntpdate -b -u 0.pool.ntp.org
ls
cd ~
ls
sudo vi /etc/rc.local
sudo reboot
dmesg
:q
ls
sudo vi /etc/rc.local
sudo screen -r
ls
sudo vi /etc/rc.local
sudo reboot
dmesg
sudo screen -r
ls
sudo vi /etc/rc.local
sudo reboot
ls
sudo vi /etc/rc.local
sudo reboot
date
cd
ls
dmesg
sudo /etc/init.d/watchdog start
dmesg
date
dmesg
sudo vi /etc/watchdog.conf
sudo /etc/init.d/watchdog restart
dmesg
sudo vi /etc/watchdog.conf
ls
cd
ls
sync
sudo vi /etc/rc.local
sudo /etc/init.d/watchdog restart
dmesg
ls
sudo visudo
sudo screen -r
ls
cd
ls
sudo screen -r
ls
ls -l /opt/scripta/bin/
ls
sudo rm /opt/scripta/bin/sgminer
sudo screen -r
sudo mv sgminer /opt/scripta/bin/
cd /opt/scripta/bin/
ls
sudo chmod a+x sgminer
ls
ls -l
sudo chmod 755 sgminer
ls
ls -l
sudo screen -r
ls
sudo sync
sudo shutdown -h now
ls -al
cd
ls
sudo screen -r
ls
sudo rm /opt/scripta/bin/sgminer
cd
ls
cd /opt/scripta/bin/
ls
sudo mv /home/baikal/sgminer  .
ls
sudo chmod a+x ./sgminer
sudo screen -r
sudo halt
cd /oppu
sudo screen -r
sudo apt-get update baikal
sudo apt-get install gdb
gdb
sudo apt-get update
sudo apt-get install gdb
ls
sudo /opt/scripta/bin/
ls
sudo /opt/scripta/bin/
ls
cd /opt/scripta/bin/
ls
sudo rm sgminer
sudo reboot
ls
cd sgminer-5.6/
ls
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
ls
sudo screen -r
sudo screen -rd
sudo screen -r
sudo apt-get install gdb
cd /opt/scripta/bin/
ls
sudo mv sgminer sgminer_new
cd
ls
cd sgminer-5.6/
ls
vi sgminer.conf
cd
ls
cd /opt/scripta/bin/
ls
sudo mv sgminer_new sgminer
ls
sudo screen -r
ls
cd sgminer-5.6/
ls
vi sgminer.c
make
sudo ./update.sh
sudo screen -r
ifconfig
ls
cd sgminer-5.6/
cd /opt/scripta/bin/
ls
sudo rm sgminer
ls
sudo screen -r
q
cd
ls
cd sgminer-5.6/
ls
gdb ./sgminer
./sgminer
cd
ls
cd .sgminer/
ls
ls -al
cd
ls
cd sgminer-5.6/
ls
sudo ./update.sh
sudo screen -r
cd
ls
vi sgminer.conf
sudo vi sgminer.conf
ls
sudo chmod 777 sgminer.conf
ls
mv sgminer.conf sgminer-5.6/
cd sgminer-5.6/
ls
./sgminer
./sgminer -c ./sgminer.c
./sgminer -c ./sgminer.conf
sudo cp sgminer.conf ../.sgminer/
./sgminer
sudo gdb
sudo gdb ./sgminer
ls
vi Makefile
ls
vi driver-baikalu.c
ls
vi sgminer.c
ls
make
sudo ./update.sh
sudo screen -r
ls
sudo screen -r
ls
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
ls
vi driver-baikalu.c
make
ls
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
vi driver-baikalu.c
vi driver-baikal.h
make
sudo ./update.sh
sudo screen -r
ls
cd sgminer-5.6/
ls
make
sudo ./update.sh
sudo screen -r
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
sudo ./update.sh
sudo screen -r
sudo ./update.sh
sudo screen -r
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
sudo ./update.sh
sudo screen -r
vi driver-baikalu.c
vi sgminer.c
vi driver-baikal.h
vi driver-baikalu.c
grep -Rni "update_work" .
sudo screen -r
ks
cd sgminer-5.6/
ls
grep -Rni "inappropiate" .
grep -Rni "inappropriately" .
sudo screen -r
vi driver-baikalu.c
vi sgminer.c
make
ls
sudo ./update.sh
sudo screen -r
vi driver-baikalu.c
vi sgminer.c
make
vi sgminer.c
make
sudo ./update.sh
sudo screen -r
top
ls
cd
ls
ls -al
su root
ls
cd
ls
cd sgminer-5.6/
ls
cd /opt/scripta/
lsl
ls
cd bin/
ls
cd
ls
cd sgminer-5.6/
ls
cd ..
ls
ls -al
cd .sgminer/
ls
cd
ls
finels
ls
cd
ls
su root
htop
ls
cd sgminer-5.6/
ls
make
sudo ./update.sh
sudo screen -r
ls
make
sudo ./update.sh
sudo screen -r
ls
cd sgminer-5.6/
ls
vi driver-baikal.h
ls
vi driver-baikalu.c
make
cd
ls
cd /opt/scripta/etc/
ls
vi miner.conf
ls
cd
cd sgminer-5.6/
ls
sudo ./update.sh
sudo screen -r
sudo ./update.sh
sudo screen -r
top
htop
cd sgminer-5.6/
ls
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
cd
ls
su root
su root
ls
cd
ls
su root
sudo screen -r
ls
cd
su root
cd
ls
cd sgminer-5.6/
ls
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
sudo reboot
ls
cd sgminer-5.6/
ls
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
vi driver-baikalu.c
ls
sudo ./update.sh
sudo screen -r
cd
su root
ls
su root
htop
ls
cd sgminer-5.6/
ls
vi driver-baikalu.c
make
sudo ./update.sh
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
ls
cd sgminer-5.6/
ls
vi driver-baikalu.c
sudo screen -r
sudo ./update.sh
sudo screen -r
cd
ls
cd cd sgminer-5.6/
ls
vcd sgminer-5.6/
ls
cd sgminer-5.6/
ls
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
sudo screen -rd
sudo ./update.sh
sudo screen -r
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
sudo ./update.sh
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
ls
cd sgminer-5.6/
ls
make
sudo ./update.sh
sudo screen -r
sudo screen -rd
ls
cd sgminer-5.6/
ls
vi driver-baikalu.c
make
vi driver-baikalu.c
make
vi driver-baikalu.c
make
ls
vi driver-baikalu.c
make
vi driver-baikalu.c
make
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
vi sgminer.c
make
sudo ./update.sh
sudo screen -r
make
sudo ./update.sh
sudo screen -r
ls
vi sgminer.c
make
sudo ./update.sh
sudo screen -r
vi driver-baikalu.c
vi sgminer.c
make
sudo ./update.sh
sudo screen -r
vi sgminer.c
make
vi miner.h
make
sudo ./update.sh
sudo screen -r
vi sgminer.c
make
sudo ./update.sh
sudo screen -r
ls
vi sgminer.c
make
sudo ./update.sh
sudo screen -r
vi sgminer.c
make
sudo ./update.sh
sduo screen -r
sudo u./upda
sudo ./update.sh
sudo screen -r
make
sudo ./update.sh
sudo screen -r
make
sudo ./update.sh
sudo screen -r
amke
make
sudo ./update.sh
sudo screen -r
make
sudo ./update.sh
sudo screen -r
make
sudo ./update.sh
sudo screen -r
make
sudo ./update.sh
sudo screen -r
cd sgminer-5.6/
ls
vi algorithm.c
make
sudo ./update.sh
sudo screen -r
ls
vi algorithm.c
make
vi algorithm.c
make
vi algorithm.c
make
sudo ./update.sh
sudo screen -r
ls
vi driver-baikalu.c
make
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
vi algorithm.c
make
sudo ./update.sh
sudo screen -r
df
htop
cd sgminer-5.6/
ls
make
sudo reboot
cd sgminer-5.6/
ls
make
sudo ./update.sh
sudo screen -r
ls
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
ls
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
ls
make
vi driver-baikalu.c
sudo ./update.sh
sudo screen -r
ls
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
htop
sudo screen -r
cd sgminer-5.6/
ls
vi algorithm.h
make
sudo ./update.sh
sudo screen -r
ls
vi algorithm.
vi algorithm.h
make
vi algorithm.h
make
vi algorithm.h
make
sudo ./update.sh
sudo screen -r
make
sudo ./update.sh
sudo screen -r
sudo ./update.sh
sudo screen -r
sudo ./update.sh
make
sudo ./update.sh
ls
rm -rf *
svn co svn://192.168.0.5/pacific/software/sgminer_5.6.x .
cd ..
ls
svn co svn://192.168.0.5/pacific/software/sgminer_5.6.x .
cd sgminer-5.6/
ls
cd
ls
cd
ls
chmod a+x ./autogen.sh
./autogen.sh
./configure
ls
make
sudo ./update.sh
chmod a+x ./update.sh
sudo ./update.sh
chmod a+x ./update.sh
ls
sudo screen -r
sudo ./update.sh
df
sudo reboot
ls
cd sgminer-5.6/
ls
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
ls
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
top
sudo screen -r
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
ls
vi driver-baikalu.c
vi sgminer.c
ks
ls
sudo ./update.sh
sudo screen -r
ls
cd
sudo screen -r
cd /opt/scripta/bin/
ls
ls 0l
ls -l
ls
cd
ls
vi driver-baikalu.c
make
ls
vi sgminer.c
make
sudo ./update.sh
vi driver-baikalu.c
make
vi sgminer.c
make
sudo ./update.sh
make
sudo ./update.sh
ls
sudo ./sgminer /opt/scripta/etc/miner.conf
sudo ./sgminer -c /opt/scripta/etc/miner.conf
sudo ./update.sh
sudo reboot
sudo ./update.sh
sudo screen -r
ls
svn update
vi sgminer.c
svn diff | ^M
svn diff
q
svn diff | ^M
svn diff | ^M
svn diff | grep ^M
make
sudo ./update.sh
sudo screen -r
sudo ./update.sh
sudo screen -r
vi driver-baikalu.c
make
sudo screen -r
vi driver-baikalu.c
make
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
sudo screen 0r
sudo screen -r
ls
vi usbutils.c
make
sudo ./update.sh
sudo screen -r
ls
cd /var/www/
cd partials/
ls
vi miner.html
sudo vi miner.html
sudo screen -r
ls
cd
ls
cd driver-baikalu.c
vi driver-baikalu.c
make
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
vi driver-baikalu.c
sudo screen -r
vi driver-baikalu.c
sudo screen -r
vi driver-baikalu.c
sudo screen -r
sudo lsusb
sudo shutdown -h now
sudo screen -r
vi usbutils.c
make
sudo ./update.sh
sudo screen -r
ls
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
ls
vi usbutils.c
sudo screen -r
ls
rm *.h
ls
rm *.o
rm *.c
ls
rm *.php
ls
rm Makefile.am
ls
rm missing NEWS.md sgminer
ls
rm algorithm/
ls -al
ls
rm algorithm/
rm aclocal.m4 API.* AUTHORS.md config*
ls
rm -rf ADL_SDK/ api-example.py  auto* C* doc
ls
rm -rf a* c* e* i* l*
ls
rm -rf depcomp kernel/ m4 Makefile* man/ M*
ls
rm -rf mknsis.sh ocl/ README.md  sgminer.c.edited sph stamp-h1 submodules/ tools/ update.sh  winbuild/
ls
ls -al
rm -rf *.swp
ls
ls -al
rm -rf *.*.cwp
l
rm -rf *.*.swp
ls
ls -al
rm -rf .sgminer/
ls
cd .svn/
ls
cd ..
ls
rm -rf .svn/
ls
ls -al
rm .driver-baikalu.c.swp
rm .git*
ls
rm -rf .libs/
rm -rf .nano/
ls
ls -al
rm -rf .deps/
ls
cd sgminer-5.6/
ls
svn update
cd ..
ls
rm -rf sgminer-5.6/
ls
ls -al
rm -rf .subversion/
ls
cd /opt/scripta/etc/
ls
cd /opt/scripta/
ls
rm -rf 20170210-1632/
sudo rm -rf 20170210-1632/
ls
cd etc/
ls
cd backup/
ls
rm -rf 20170*
sudo rm -rf 20170*
ls
cd
ls
cd
ls
svn co svn://192.168.0.5/pacific/software/sgminer_5.6.x
ls
cd sgminer_5.6.x/
ls
chmod a+x autogen.sh
ls
./autogen.sh
ls
./configure
make
sudo ./update.sh
chomod a+x ./update.sh
chmod a+x ./update.sh
ls
vi algorithm.h
vi algorithm.c
sudo screen -r
cd /var/www/partials/
ls
vi miner.html
sudo vi miner.html
sudo screen -=r
sudo screen -r
sudo shutdown -h now
sudo screen -r
sudo shutdown -h now
ls
cd sgminer_5.6.x/
ls
vi usbutils.c
make
sudo ./update.sh
sudo screen -r
ls
vi driver-baikalu.c
vi sgminer
vi sgminer.c
cd /opt/scripta/
ls
cd etc/
ls
cd backup/
ls
cd 20170913-2245/
ls
cd etc/
ls
vi miner.conf
ls
cd ..
ls
cd ..
ls
cd 20170913-2314/
ls
cd etc/
ls
vi miner.conf
cd ..
ls
rm -rf 20170913-2314/
sudo rm -rf 20170913-2*
ls
exit
ls
sudo vi /etc/rc.local
sync
sudo reboot
ls
cd sgminer_5.6.x/
ls
svn update
cd sgminer_5.6.x/
ls
svn update
ifconfig
svn update
ipconfig
ifconfig
ls
svn update
exit
cd sgminer_5.6.x/
ls
vi sgminer.c
ls
./autogen.sh
./configure
make
sudo ./update.sh
ls
sudo shutdown -h now
sudo lsusb
cd /sys/class/gpio_sw/
ls
cd PA18/
ls
cd
ls
echo 0 > /sys/class/gpio_sw/PA10/data
ls
chmod a+x reset
chmod a+x reset.sh
sudo ./reset.sh
echo 0 > /sys/class/gpio_sw/PA18/data
sudo ./reset.sh
lsusb
ls
sudo ./reset.sh
lsusb
ls
vi reset.sh
mv reset.sh downmode.sh
cp downmode.sh normalmode.sh
vi normalmode.sh
sl
ls
sudo ./normalmode.sh
lsusb
sudo ./downmode.sh
lsusb
ls
vi downmode.sh
./downmode.sh
sudo ./downmode.sh
lsusb
sudo ./normalmode.sh
lsusb
sudo ./downmode.sh
lsusb
vi downmode.sh
sudo ./downmode.sh
lsusb
sudo ./normalmode.sh
ls
vi reset_usb.c
ls
vi downmode.sh
ls
dfu-utils
dfu-util
ls
sudo apt-get install dfu-util
sudo apt-get install dfu-utils
sudo screen -r
q
sudo apt-get install dfu-utils
lks
ls
vi normalmode.sh
lsusb
ls
vi ret.sh
ls
vi reset_usb.c
ls
gcc -o reset_usb reset_usb.c `pkg-config --libs libusb-1.0`
vi reset_usb.c
make
gcc -o reset_usb reset_usb.c `pkg-config --libs libusb-1.0`
ls
sudo ./reset_usb
vi reset_usb.c
gcc -o reset_usb reset_usb.c `pkg-config --libs libusb-1.0`
sudo ./reset_usb
vi update_firmware.sh
vi update_firmware.sh
sudo reboot
tail -f dmesg
tail -f /var/log/dmesg
sudo tail -f /var/log/dmesg
ls
vi reset.sh
vi reset.sh
su root
ls
vi reset_usb.c
gcc -o reset_usb reset_usb.c `pkg-config --libs libusb-1.0`
ls
mv reset_usb exit_dfu
ls
sudo ./exit_dfu
vi downmode.sh
ls
sudo ./downmode.sh
vi update_firmware.sh
ls
mv exit_dfu reset_dfu
mv enter_dfu reset_stm
ls
w
ls
sudo enter_normalmode.sh
sudo ./enter_normalmode.sh
ls
mv enter_downmmode.sh enter_dfumode.sh
mv enter_normalmode.sh enter_runmode.sh
ls
vi update_firmware.sh
ls
sudo ./update_firmware.sh
lsusb
sudo ./update_firmware.sh
ls
vi update_firmware.sh
ls
sudo ./update_firmware.sh
ls
slmod
lsusb
sudo ./enter_dfumode.sh
lsusb
ls
vi update_firmware.sh
sudo ./update_firmware.sh
ls
sudo ./enter_runmode.sh
sudo lsusb
vi update_firmware.sh
ls
sudo ./update_firmware.sh
lsusb
ls
sudo ./enter_dfumode.sh
sudo ./update_firmware.sh
lsusb
sudo ./enter_dfumode.sh
sudo ./update_firmware.sh
sudo ./reset_dfu
sudo ./reset_stm
lsusb
ls
sudo ./enter_dfumode.sh
lsusb
sudo ./reset_stm
lsusb
sudo ./reset_dfu
lsusb
sudo ./update_firmware.sh
lsusb
sudo ./enter_dfumode.sh
lsusb
ls
vi enter_dfumode.sh
ls
sudo ./update_firmware.sh
sudo ./enter_runmode.sh
ls
mkdir firmware
ls
mv enter_*.sh firmware/
ls
vm reset_*fir
vm reset_* firmware/
ls
mv reset_* firmware/
ls
mv pacific.bin update_firmware.sh firmware/
ls
cd firmware/
ls
rm reset_usb.c
ls
sync
cd
ls
cd sgminer_5.6.x/
ls
vi driver-baikal.h
ls
sudo shutdown -h now
lsusb
cd firmware/
ls
sudo ./enter_runmode.sh
sudo lsmod
lsusb
ls
vi enter_dfumode.sh
ls
cat enter_runmode.sh
cd
ls
cd /opt/scripta/etc/
ls
cd backup/
ls
mv 20171002-1613/ X11
sudo mv 20171002-1613/ X11
ls
sudo mv 20171002-1614/ DC
ls
sudo rm -rf DC
ls
cd sgminer_5.6.x/
ls
cd
su root
ls
cd sgminer_5.6.x/
ls
vi Makefile
ls
./autogen.sh
ls
vi Makefile.am
vi configure.ac
./autogen.sh
./configure
make
sudo ./update.sh
sync
ls
cd
ls
cd firmware/
ls
sudo halt
ls
cd firmware/
ls
vi enter_dfumode.sh
vi update_firmware.sh
cd
ls
ifconfig
ls
cd sgminer_5.6.x/
ls
vi driver-baikalu.c
make
sudo ./update.sh
sudo screen -r
ls
sync
make
sudo ./update.sh
ls
vi driver-baikalu.c
sudo halt
ls
cd firmware/
ls
vi enter_dfumode.sh
sudo /opt/scripta/startup/miner-stop.sh
vi update_firmware.sh
ls
vi enter_dfumode.sh
ls
vi update_firmware.sh
./update_firmware.sh 1
vi update_firmware.sh
./update_firmware.sh 1
ls
./update_firmware.sh pacific.bin
dfu-util
ls
ls
cd sgminer_5.6.x/
ls
make
sudo ./update.sh
sudo screen -r
ls
sudo sync
sudo halt


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: arma33 on March 27, 2018, 10:06:19 AM
put a new update management program BaikalMonitor. Two days one of the Baikal began to glitch ( became often turn on the fan). Turned off, turned on and as wrote above Hashrate av showed 44 GH. Within a few minutes fell to 16 GC. Then another few minutes went down to 14 GC. And smoothly fell to 10.14 GH. Neither of which is not pierced. The question, maybe already from the factory to have the firmware and how to find it? But you can get to see the traffic from each machine. Possible hidden traffic, that is, the main to another address..


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: adra12 on March 27, 2018, 10:26:55 AM
put a new update management program BaikalMonitor. Two days one of the Baikal began to glitch ( became often turn on the fan). Turned off, turned on and as wrote above Hashrate av showed 44 GH. Within a few minutes fell to 16 GC. Then another few minutes went down to 14 GC. And smoothly fell to 10.14 GH. Neither of which is not pierced. The question, maybe already from the factory to have the firmware and how to find it? But you can get to see the traffic from each machine. Possible hidden traffic, that is, the main to another address..

If you read back in this topic, then you can find the firmware of the X10. Still don't expect to edit the binary file without a hex editor.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: arma33 on March 27, 2018, 11:01:02 AM
put a new update management program BaikalMonitor. Two days one of the Baikal began to glitch ( became often turn on the fan). Turned off, turned on and as wrote above Hashrate av showed 44 GH. Within a few minutes fell to 16 GC. Then another few minutes went down to 14 GC. And smoothly fell to 10.14 GH. Neither of which is not pierced. The question, maybe already from the factory to have the firmware and how to find it? But you can get to see the traffic from each machine. Possible hidden traffic, that is, the main to another address..

If you read back in this topic, then you can find the firmware of the X10. Still don't expect to edit the binary file without a hex editor.



So it is not clear if the actual machine produces such power. Why once they have been declared. And as all??? their include. Or in part include?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: chup on March 27, 2018, 12:06:32 PM
Only difference is that in your version it sets clock depending on Baikal chip type(1751: CN, 1791: B), so it does no difference on X10, however it does difference to CN and B.

Ive tried to overclock it but its not possible at this moment, both by enabling ENABLE_SETCLK and disabling CLK_FIX, and even tried another definition of CLK_DEF. Even though sgminer says its set to 400 Mhz, it aint - seems to be limited on firmware level!

When it comes to different algo`s, none of them work (gives only HW errors) - either needed some updates in algo files, or what i think it is also limited at firmware level. However, i did gather some different power usages:

Code:
sgminer 5.6.2-cod3gen - Started: [2018-03-26 00:38:34] - [0 days 10:12:35]
--------------------------------------------------------------------------------
(5s):10.82G (avg):10.81Gh/s | A:9148  R:78  HW:381  WU:33820.422/m
ST: 1  SS: 0  NB: 638  LW: 2261672  GF: 0  RF: 0
Connected to quark.eu.nicehash.com (stratum) diff 5.24K as user XXX
Block: 57e616c6...  Diff:117M  Started: [10:48:08]  Best share: 10.8M
--------------------------------------------------------------------------------
 [U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
BKLU 0: 38C 400MHz [ASICS #64] | 3.604G/3.604Gh/s | A:2763 R: 21 HW: 54 WU:9921.705/m
BKLU 1: 38C 400MHz [ASICS #64] | 3.604G/3.604Gh/s | A:3194 R: 27 HW:150 WU:11941.753/m
BKLU 2: 38C 400MHz [ASICS #64] | 3.604G/3.604Gh/s | A:3191 R: 30 HW:177 WU:11956.965/m

Actual stats on nicehash is slightly lower than orginal version.

Please note Your DGB address so I can mine at least one day for You, to compensate what You are losing tinkering with X10. Thx.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: cashen on March 27, 2018, 02:57:18 PM
Only difference is that in your version it sets clock depending on Baikal chip type(1751: CN, 1791: B), so it does no difference on X10, however it does difference to CN and B.

Ive tried to overclock it but its not possible at this moment, both by enabling ENABLE_SETCLK and disabling CLK_FIX, and even tried another definition of CLK_DEF. Even though sgminer says its set to 400 Mhz, it aint - seems to be limited on firmware level!

When it comes to different algo`s, none of them work (gives only HW errors) - either needed some updates in algo files, or what i think it is also limited at firmware level. However, i did gather some different power usages:

Code:
sgminer 5.6.2-cod3gen - Started: [2018-03-26 00:38:34] - [0 days 10:12:35]
--------------------------------------------------------------------------------
(5s):10.82G (avg):10.81Gh/s | A:9148  R:78  HW:381  WU:33820.422/m
ST: 1  SS: 0  NB: 638  LW: 2261672  GF: 0  RF: 0
Connected to quark.eu.nicehash.com (stratum) diff 5.24K as user XXX
Block: 57e616c6...  Diff:117M  Started: [10:48:08]  Best share: 10.8M
--------------------------------------------------------------------------------
 [U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
BKLU 0: 38C 400MHz [ASICS #64] | 3.604G/3.604Gh/s | A:2763 R: 21 HW: 54 WU:9921.705/m
BKLU 1: 38C 400MHz [ASICS #64] | 3.604G/3.604Gh/s | A:3194 R: 27 HW:150 WU:11941.753/m
BKLU 2: 38C 400MHz [ASICS #64] | 3.604G/3.604Gh/s | A:3191 R: 30 HW:177 WU:11956.965/m

Actual stats on nicehash is slightly lower than orginal version.

Please note Your DGB address so I can mine at least one day for You, to compensate what You are losing tinkering with X10. Thx.

I'd like to donate too.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: cod3gen on March 27, 2018, 05:35:11 PM
New thread containing more information and link to source.

https://bitcointalk.org/index.php?topic=3206908.new#new

Please note Your DGB address so I can mine at least one day for You, to compensate what You are losing tinkering with X10. Thx.

Sounds great @ DABjUQjcmYmuiVgZUvGBKuvbTQyCH9UMEG


I'd like to donate too.

Feel free to do :-)
Addresses at bottom of new thread ;-)


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Abdurrahman Yalcin on March 27, 2018, 08:54:08 PM
When baikal invent a device baikal workers and another persons in china is use this device
We cant use this profitable. İn first baikal B mining 500 dolar per day
But today Only 15 usd per day


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: dmanukr on March 28, 2018, 12:57:17 AM
Great work guys.. really good. 


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: chup on March 28, 2018, 06:22:27 AM

Sounds great @ DABjUQjcmYmuiVgZUvGBKuvbTQyCH9UMEG


One experimental day covered:

e74152daafaa96170df1696c946d167565de9380daa7fa5c8f53de6a2183a166

Keep going.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: cod3gen on March 28, 2018, 08:20:55 AM

Sounds great @ DABjUQjcmYmuiVgZUvGBKuvbTQyCH9UMEG


One experimental day covered:

e74152daafaa96170df1696c946d167565de9380daa7fa5c8f53de6a2183a166

Keep going.

Thanks chup, its appreciated :-)


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: stash2coin on March 28, 2018, 09:31:05 AM
My suspicion is that these chips frequency is not controlled by software, if they were the circuity in every chip will be much more complex do you think the chinese will go with the harder and more complex way? Also there seems to be a software method to control the load of the chips but not with frequency change. If you want to overclock them just change the crystal oscillator value if it is 12.5Mhz you may try 12.66Mhz or more in small increments and monitor the temperatures of the chips if its rising the mode is successful but then there will be the problem with the firmware if these machines are capped to produce fixed amount of shares custom firmware is needed along with the hardware mod.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: elmond on March 29, 2018, 08:22:03 AM

Great job again!
We might just need to go through all the different versions of each source file to find which one is the most up to date.  For instance I "think" this is the latest/greatest device_baikal.h file:
Code:
#ifndef __DEVICE_BAIKAL_H__
#define __DEVICE_BAIKAL_H__

#include "miner.h"

#define BAIKAL_1751             (0x1)
#define BAIKAL_1772             (0x2)
#define BAIKAL_1791             (0x4)
#define BAIKAL_ALL              (0x7)
#define BAIKAL_TYPE             (BAIKAL_ALL)

#define BAIKAL_MAXMINERS     (5)
#define BAIKAL_MAXUNIT          (4)
#define BAIKAL_MAXASICS         (16)
#define BAIKAL_WORK_FIFO        (200)

#define BAIKAL_CLK_MIN  (150)
#define BAIKAL_CLK_MAX     (300)

#if BAIKAL_TYPE == BAIKAL_1751
#define BAIKAL_CLK_DEF  (200)
#elif BAIKAL_TYPE == BAIKAL_1791
#define BAIKAL_CLK_DEF  (400)
#else
#define BAIKAL_CLK_DEF  (300)
#endif

#define BAIKAL_CUTOFF_TEMP      (60)
#define BAIKAL_FANSPEED_DEF     (100)
#define BAIKAL_FANSPEED_MAX     (100)
#define BAIKAL_RECOVER_TEMP     (40)

#define BAIKAL_RESET     (0x01)
#define BAIKAL_GET_INFO         (0x02)
#define BAIKAL_SET_OPTION     (0x03)
#define BAIKAL_SEND_WORK     (0x04)
#define BAIKAL_GET_RESULT     (0x05)
#define BAIKAL_SET_ID     (0x06)
#define BAIKAL_SET_IDLE     (0x07)

#define BAIKAL_MINER_TYPE_NONE  (0x00)
#define BAIKAL_MINER_TYPE_MINI  (0x01)
#define BAIKAL_MINER_TYPE_CUBE  (0x02)

#define BAIKAL_ENABLE_SETCLK    (0)

#define BAIKAL_CHECK_STALE      (0)
#define BAIKAL_EN_HWE           (0)
#define BAIKAL_CLK_FIX          (1)

struct asic_info {
    uint32_t nonce;
    uint32_t error;
};

struct miner_info {
    int     thr_id;
    int     asic_count; 
    int     asic_count_r; 
    int     unit_count;
int temp; 
    int     clock;
    int     bbg;
    bool    working;
    bool    overheated;
    uint8_t fw_ver;
    uint8_t hw_ver;
    uint8_t asic_ver;   
    uint32_t nonce;
    uint32_t error;   
    double working_diff;   
    struct asic_info asics[BAIKAL_MAXUNIT][BAIKAL_MAXASICS];
    uint8_t work_idx;
    struct work *works[BAIKAL_WORK_FIFO];
    cgtimer_t start_time;
};


struct baikal_info {
    struct pool pool;
    int miner_count;
    int clock;
    uint8_t cutofftemp;
    uint8_t fanspeed; // percent
    uint8_t recovertemp;
pthread_t *process_thr;
    struct miner_info miners[BAIKAL_MAXMINERS];   
    uint8_t miner_type;
};

typedef struct {
    uint8_t     miner_id;
    uint8_t     cmd;
    uint8_t     param;
    uint8_t     dest;
    uint8_t     data[512];
    uint32_t    len;
} baikal_msg;


#endif /* __DEVICE_BAIKAL_H__ */

this is the current driver-baikal.h file that i use. Very similiar to the one you have

Code:
#ifndef __DEVICE_BAIKAL_H__
#define __DEVICE_BAIKAL_H__

#include "miner.h"

#define BAIKAL_1751             (0x1)
#define BAIKAL_1772             (0x2)
#define BAIKAL_1791             (0x4)
#define BAIKAL_ALL              (0x7)
#define BAIKAL_TYPE             (BAIKAL_ALL)

#define BAIKAL_MAXMINERS     (5)
#define BAIKAL_MAXUNIT          (4)
#define BAIKAL_MAXASICS         (16)
#define BAIKAL_WORK_FIFO        (200)

#define BAIKAL_CLK_MIN  (150)
#define BAIKAL_CLK_DEF  (400)
#define BAIKAL_CLK_MAX     (400)
#define BAIKAL_CUTOFF_TEMP      (55)
#define BAIKAL_FANSPEED_DEF     (100)
#define BAIKAL_FANSPEED_MAX     (100)
#define BAIKAL_RECOVER_TEMP     (40)

#define BAIKAL_RESET     (0x01)
#define BAIKAL_GET_INFO         (0x02)
#define BAIKAL_SET_OPTION     (0x03)
#define BAIKAL_SEND_WORK     (0x04)
#define BAIKAL_GET_RESULT     (0x05)
#define BAIKAL_SET_ID     (0x06)
#define BAIKAL_SET_IDLE     (0x07)

#define BAIKAL_MINER_TYPE_NONE  (0x00)
#define BAIKAL_MINER_TYPE_MINI  (0x01)
#define BAIKAL_MINER_TYPE_CUBE  (0x02)

#define BAIKAL_ENABLE_SETCLK    (0)

#define BAIKAL_CHECK_STALE      (0)
#define BAIKAL_EN_HWE           (0)
#define BAIKAL_CLK_FIX          (1)

struct asic_info {
    uint32_t nonce;
    uint32_t error;
};

struct miner_info {
    int     thr_id;
    int     asic_count; 
    int     asic_count_r; 
    int     unit_count;
int temp; 
    int     clock;
    int     bbg;
    bool    working;
    bool    overheated;
    uint8_t fw_ver;
    uint8_t hw_ver;
    uint8_t asic_ver;   
    uint32_t nonce;
    uint32_t error;   
    double working_diff;   
    struct asic_info asics[BAIKAL_MAXUNIT][BAIKAL_MAXASICS];
    uint8_t work_idx;
    struct work *works[BAIKAL_WORK_FIFO];
    cgtimer_t start_time;
};


struct baikal_info {
    struct pool pool;
    int miner_count;
    int clock;
    uint8_t cutofftemp;
    uint8_t fanspeed; // percent
    uint8_t recovertemp;
pthread_t *process_thr;
    struct miner_info miners[BAIKAL_MAXMINERS];   
    uint8_t miner_type;
};

typedef struct {
    uint8_t     miner_id;
    uint8_t     cmd;
    uint8_t     param;
    uint8_t     dest;
    uint8_t     data[512];
    uint32_t    len;
} baikal_msg;


#endif /* __DEVICE_BAIKAL_H__ */

Only difference is that in your version it sets clock depending on Baikal chip type(1751: CN, 1791: B), so it does no difference on X10, however it does difference to CN and B.

Ive tried to overclock it but its not possible at this moment, both by enabling ENABLE_SETCLK and disabling CLK_FIX, and even tried another definition of CLK_DEF. Even though sgminer says its set to 400 Mhz, it aint - seems to be limited on firmware level!

When it comes to different algo`s, none of them work (gives only HW errors) - either needed some updates in algo files, or what i think it is also limited at firmware level. However, i did gather some different power usages:
Quote
Groestl: Unknown @ 690w
Nist5: Unknown @ 690w
X11Gost: Unknown, but possibly 450MHs @ 450w

Code:
sgminer 5.6.2-cod3gen - Started: [2018-03-26 00:38:34] - [0 days 10:12:35]
--------------------------------------------------------------------------------
(5s):10.82G (avg):10.81Gh/s | A:9148  R:78  HW:381  WU:33820.422/m
ST: 1  SS: 0  NB: 638  LW: 2261672  GF: 0  RF: 0
Connected to quark.eu.nicehash.com (stratum) diff 5.24K as user XXX
Block: 57e616c6...  Diff:117M  Started: [10:48:08]  Best share: 10.8M
--------------------------------------------------------------------------------
 [U]SB management [P]ool management [S]ettings [D]isplay options [Q]uit
BKLU 0: 38C 400MHz [ASICS #64] | 3.604G/3.604Gh/s | A:2763 R: 21 HW: 54 WU:9921.705/m
BKLU 1: 38C 400MHz [ASICS #64] | 3.604G/3.604Gh/s | A:3194 R: 27 HW:150 WU:11941.753/m
BKLU 2: 38C 400MHz [ASICS #64] | 3.604G/3.604Gh/s | A:3191 R: 30 HW:177 WU:11956.965/m

Actual stats on nicehash is slightly lower than orginal version.

did the the raspberry and sam3 communicate on usb?
i'm guess some hardware limitation, do you try with single hash board?



Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: cod3gen on March 29, 2018, 09:46:38 AM
My suspicion is that these chips frequency is not controlled by software, if they were the circuity in every chip will be much more complex do you think the chinese will go with the harder and more complex way? Also there seems to be a software method to control the load of the chips but not with frequency change. If you want to overclock them just change the crystal oscillator value if it is 12.5Mhz you may try 12.66Mhz or more in small increments and monitor the temperatures of the chips if its rising the mode is successful but then there will be the problem with the firmware if these machines are capped to produce fixed amount of shares custom firmware is needed along with the hardware mod.

I actually went down that road for a while also. There are 4 Tri-state 12.5 Mhz oscillators on each hashboard on the X10 - However the Giant N have what seems to be 12.5 Mhz oscillator on board also(P12 50W - 121C), and its frequency is supposed to be lower(200 Mhz) than X10(300 Mhz). If the chip speed was based on the oscillators, would not that mean the N should have had a much lower frequency on its oscillator? But then again, no one knows for sure that frequencies the chips are running at since the software simply is a pre fixed clock and got nothing to do with actual chip clock, for all we know they might operate on the same frequency(N/X10).

Sure would like to test out the theory, but then again im not so sure i want to waste a hashboard :-S


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: [SLA5][ANAQC]man-FIRE on March 30, 2018, 04:10:28 PM
hi,

What i need to do for win the reward 0.2 bitcoin ?

5s):184.8G (avg):185.7Gh/s | A:2141  R:0  HW:22  WU:1027.095/m
ST: 1  SS: 0  NB: 2  LW: 2188  GF: 0  RF: 0
Connected to lbry.eu.nicehash.com (stratum) diff  as user *****
Block: a24f8128...  Diff:26.4M  Started: [00:09:01]  Best share: 90.6K
--------------------------------------------------------------------------------
 SB management [P]ool management ettings [D]isplay options [Q]uit
BKLU 0: 28C 800MHz [ASICS #64] | 61.44G/64.34Gh/s | A:768 R: 0 HW:12 WU:367.401/m
BKLU 1: 28C 800MHz [ASICS #64] | 61.44G/64.29Gh/s | A:700 R: 0 HW:11 WU:336.305/m
BKLU 2: 28C 800MHz [ASICS #64] | 61.44G/64.31Gh/s | A:782 R: 0 HW: 0 WU:374.098/m
--------------------------------------------------------------------------------
 [2018-03-31 00:09:49.329] Accepted 258afbfb Diff 1.75K/128 BKLU 2
 [2018-03-31 00:09:49.406] Accepted 017242de Diff 176/128 BKLU 2
 [2018-03-31 00:09:49.438] Accepted 01d038c0 Diff 141/128 BKLU 0
 [2018-03-31 00:09:49.469] Accepted 01e0b067 Diff 136/128 BKLU 1
 [2018-03-31 00:09:49.502] Accepted 012f5942 Diff 216/128 BKLU 0
 [2018-03-31 00:09:49.531] Accepted e9b08f8e Diff 280/128 BKLU 1
 [2018-03-31 00:09:49.532] Accepted 0117ad05 Diff 234/128 BKLU 0
 [2018-03-31 00:09:49.595] Accepted b490479e Diff 362/128 BKLU 0
 [2018-03-31 00:09:49.611] Accepted 01b7b739 Diff 149/128 BKLU 0
 [2018-03-31 00:09:49.658] Accepted c5ca4236 Diff 331/128 BKLU 0
 [2018-03-31 00:09:49.689] Accepted 011f8baa Diff 227/128 BKLU 1
 [2018-03-31 00:09:49.690] Accepted e378bb69 Diff 288/128 BKLU 2
 [2018-03-31 00:09:49.691] Accepted 0190b98d Diff 163/128 BKLU 0
 [2018-03-31 00:09:49.752] Accepted 8e865c00 Diff 459/128 BKLU 0
 [2018-03-31 00:09:49.766] Accepted 0129fe22 Diff 219/128 BKLU 0
 [2018-03-31 00:09:49.814] Accepted 4a15d498 Diff 884/128 BKLU 1
 [2018-03-31 00:09:49.830] Accepted 0133a9d9 Diff 213/128 BKLU 0
 [2018-03-31 00:09:49.831] Accepted c74c16ab Diff 328/128 BKLU 2
 [2018-03-31 00:09:50.017] Accepted 018d87c9 Diff 164/128 BKLU 0
 [2018-03-31 00:09:50.047] Accepted d408e015 Diff 309/128 BKLU 0
 [2018-03-31 00:09:50.064] Accepted 01703018 Diff 177/128 BKLU 2
 [2018-03-31 00:09:50.157] Accepted 34fc5b0b Diff 1.24K/128 BKLU 0
 [2018-03-31 00:09:50.173] Accepted b3659a9f Diff 365/128 BKLU 2
 [2018-03-31 00:09:50.188] Accepted 8ca0a1ac Diff 466/128 BKLU 1
 [2018-03-31 00:09:50.203] Accepted 01397083 Diff 209/128 BKLU 1
 [2018-03-31 00:09:50.345] Accepted 0deca14b Diff 4.71K/128 BKLU 1
 [2018-03-31 00:09:50.346] Accepted df941aea Diff 293/128 BKLU 1
 [2018-03-31 00:09:50.439] Accepted b9ce3296 Diff 352/128 BKLU 1
 [2018-03-31 00:09:50.454] Accepted 13c5270c Diff 3.31K/128 BKLU 0
 [2018-03-31 00:09:50.484] Accepted 01213cc7 Diff 226/128 BKLU 2
 [2018-03-31 00:09:50.599] Accepted 017e6611 Diff 171/128 BKLU 0
 [2018-03-31 00:09:50.678] Accepted 01658067 Diff 183/128 BKLU 0
 [2018-03-31 00:09:50.772] Accepted 1f91b852 Diff 2.08K/128 BKLU 2
 [2018-03-31 00:09:50.787] Accepted 38d2e387 Diff 1.15K/128 BKLU 1


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: cod3gen on March 30, 2018, 05:00:25 PM
hi,
What i need to do for win the reward 0.2 bitcoin ?

 ;D

replacing BAIKAL_CLK_DEF with 800, does not mean that you are overclocking it. Its limited at firmware level on atleast X10, but it is Giant B you have.

Ohh, and you should not use "Issues" section on github to ask questions.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: [SLA5][ANAQC]man-FIRE on March 30, 2018, 06:30:17 PM
I dont need to go on your issues section....

When your turn the clk to 1, this enabled to option baikal-option to communication with the firmware inside the second head.

1. first enable clk to 1

2. after call sgminer with --baikal-options 800:(100/300 depend of your quality room air flow):32  (max degree)
(the second number on the baikal option is the recovery time, if your delay is to short .... you dont find any block.)

3. I have fixed your lbry.h/c and recompile it

4. that it

voila




Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: cod3gen on March 30, 2018, 07:11:37 PM
When your turn the clk to 1, this enabled to option baikal-option to communication with the firmware inside the second head.

1. first enable clk to 1

2. after call sgminer with --baikal-options 800:(100/300 depend of your quality room air flow):32  (max degree)

Thats more or less the same thing as changing BAIKAL_CLK_DEF. Does not work on X10, but may work on Giant B. Verify hashrate on pool side over 24h period.
It is interesting that it return a 800 Mhz value. X10 only return 440 Mhz and i have had reports from Giant B users of 480 Mhz return value. While N have 420 Mhz return value.

Have you enabled BAIKAL_CLK_FIX also?
Even weirder is that if it did return 800 Mhz value from firmware chip, that would mean that a 8-bit integer would have a value of 400...... :D


(the second number on the baikal option is the recovery time, if your delay is to short .... you dont find any block.)


Second number is recover temp... Using this as a example: 800:40:55 means;

When one chip(or hashboard) goes to a temp higher than 55c, that is disabled until it reaches its recover temp(40c) when it can start again.

3. I have fixed your lbry.h/c and recompile it

4. that it

voila


Then, what was wrong with them?

When the miner starts, the first 5-10 seconds are you able to copy information about Firmware Version: XX - Hardware Version etc.? What frequency is stated there?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: [SLA5][ANAQC]man-FIRE on March 30, 2018, 08:44:41 PM
baikal giant B on mineral water my friend, 800hmz is overload but i have laboratory condition for -30 degree, please use 16v dc + 100a


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: rogerthat55 on March 30, 2018, 09:32:27 PM
Quote
call sgminer with --baikal-options

This might be a dumb linux question, but how do you call sgminer while it's running? When I try to issue a command in the terminal, it wants to start a new instance.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: [SLA5][ANAQC]man-FIRE on March 30, 2018, 09:41:32 PM
sudo killall -9 sgminer
"you have 2 second for start a new instance"
./sgminer --kernel lbry -o stratum -u user -p x --baikal-options clock:recoveryclock:maxtemp


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheLiZArD_24 on March 30, 2018, 10:58:12 PM
sudo killall -9 sgminer
"you have 2 second for start a new instance"
./sgminer --kernel lbry -o stratum -u user -p x --baikal-options clock:recoveryclock:maxtemp

This part is ok, but where do I have to "enable clk to 1"?
Is there more to do (I have fixed your lbry.h/c and recompile it)?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: [SLA5][ANAQC]man-FIRE on March 30, 2018, 11:39:37 PM
you need to recompile the code ..


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: TheLiZArD_24 on March 30, 2018, 11:56:18 PM
you need to recompile the code ..

Can you please pm me (you do not accept pm from newbie) with more details, I would like to test it.
Thanks!


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: [SLA5][ANAQC]man-FIRE on March 31, 2018, 07:35:07 PM
Sorry about that, I am to busy for help everybody for compiling sample source code but just search on the internet i am sure you going to find the anwser at your question.

cod3gen do you reserve download the firmware from the 3 way chip ?




Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: cod3gen on March 31, 2018, 08:56:46 PM
cod3gen do you reserve download the firmware from the 3 way chip ?

Not sure what you mean there..


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: ra_XOr on March 31, 2018, 08:57:35 PM
you need to recompile the code ..

Can you please pm me (you do not accept pm from newbie) with more details, I would like to test it.
Thanks!

You can find the walkthrough for compiling the code in Code3gen GitHub page.. https://github.com/cod3gen/sgminer-baikal/blob/dev/README.md (https://github.com/cod3gen/sgminer-baikal/blob/dev/README.md)


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: [SLA5][ANAQC]man-FIRE on April 01, 2018, 09:52:50 PM
Boy, I talking about the firmware inside the STMCHIP 3 way board controller, find / -name fw_upgrade.sh

cod3gen, I love your work, so I give you a hint,

the original code show

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

so your chip frequency is 2 + result of modulos....

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...


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: cod3gen on April 01, 2018, 10:37:32 PM
Boy, I talking about the firmware inside the STMCHIP 3 way board controller, find / -name fw_upgrade.sh

cod3gen, I love your work, so I give you a hint,

the original code show

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

so your chip frequency is 2 + result of modulos....

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...

Ive actually had other users also telling me that the software does provide overclock options to Giant B, nice for B owners :-P

Lets keep it in the other thread i created: https://bitcointalk.org/index.php?topic=3206908.0

It does not seem to apply to either Giant X10(and not N either)



Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tboy32c 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?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: namsss on April 02, 2018, 07:01:28 PM
Dear
Someone please help me Baikal N , Stm32 chip image . My controller dead


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: cod3gen on April 02, 2018, 08:34:23 PM
Dear
Someone please help me Baikal N , Stm32 chip image . My controller dead

You can find it here; https://bitcointalk.org/index.php?topic=3206908.0


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: adra12 on April 02, 2018, 09:33:12 PM
Boy, I talking about the firmware inside the STMCHIP 3 way board controller, find / -name fw_upgrade.sh

cod3gen, I love your work, so I give you a hint,

the original code show

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

so your chip frequency is 2 + result of modulos....

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...

To be honest this doesn't make any sense. Here is the baikal msg structure that is used in that case:

Code:
typedef struct {
    uint8_t     miner_id;
    uint8_t     cmd;
    uint8_t     param;
    uint8_t     dest;
    uint8_t     data[512];
    uint32_t    len;
} baikal_msg;

As you can see the data field consists of 8 bit integer values. So by adding a floating point number of 2.2 makes absolutely no difference compared to the standard 2. Both numbers (2 and 2.2) are converted to uint8_t resulting in a value of 2.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: [SLA5][ANAQC]man-FIRE on April 04, 2018, 03:49:15 AM
adra12 good job pumpkin and now I give you candy stick you find the anwser for the 0.2 btc !

just put float for the data and  remove the 1 on the clock value on the 2 file.

and comment the app_log for data info

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

to

miner->clock        = msg.data[3];

enjoy !!!

baikal mhz clock protection removed !



Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: namsss on April 04, 2018, 04:36:18 AM
Dear
Someone please help me Baikal N , Stm32 chip image . My controller dead

You can find it here; https://bitcointalk.org/index.php?topic=3206908.0

Thank so much !


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: chup on April 04, 2018, 09:16:21 AM
adra12 good job pumpkin and now I give you candy stick you find the anwser for the 0.2 btc !

just put float for the data and  remove the 1 on the clock value on the 2 file.

and comment the app_log for data info

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

to

miner->clock        = msg.data[3];

enjoy !!!

baikal mhz clock protection removed !



I don't see OP author confirming overclocking and sending reward.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: cod3gen on April 04, 2018, 09:42:33 AM
I don't see OP author confirming overclocking and sending reward.

Probably because [SLA5][ANAQC]man-FIRE is still mixing Giant B which can be overclocked with X10..?

No one with X10 have confirmed overclock, while Giant B is overclocked with the sgminer i have on Github, it does about ~46 GH on LBRY, and potential much more with some smaller changes.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: wholly on April 04, 2018, 02:54:17 PM

HI.... watching this story unfold..

Can we successfully overclock the X10???

I have very little linux skills... but would love to know?

I must say THANKS to all that have provided content to get it this far!

Once again thank you.

Look forward TO THE END RESULT!


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: ruplikminer on April 04, 2018, 04:43:04 PM
I don't see OP author confirming overclocking and sending reward.



Probably because [SLA5][ANAQC]man-FIRE is still mixing Giant B which can be overclocked with X10..?

No one with X10 have confirmed overclock, while Giant B is overclocked with the sgminer i have on Github, it does about ~46 GH on LBRY, and potential much more with some smaller changes.

Is there a thread on how to overclock the B?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: rogerthat55 on April 04, 2018, 05:02:13 PM
So are we waiting for someone to try it out on an X10, or is it still being looked into? I can try it out on mine if we need a guinea pig.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: cod3gen on April 04, 2018, 05:08:02 PM
So are we waiting for someone to try it out on an X10, or is it still being looked into? I can try it out on mine if we need a guinea pig.

Ive tried as hell on my own X10 :-D

I don't see OP author confirming overclocking and sending reward.



Probably because [SLA5][ANAQC]man-FIRE is still mixing Giant B which can be overclocked with X10..?

No one with X10 have confirmed overclock, while Giant B is overclocked with the sgminer i have on Github, it does about ~46 GH on LBRY, and potential much more with some smaller changes.

Is there a thread on how to overclock the B?

There is a pretty straight forward guide on my github that will allow you to OC. Change SET_ENABLE to 1 and you will be able to OC more by setting set_baikal command.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: ruplikminer on April 04, 2018, 05:11:41 PM
So are we waiting for someone to try it out on an X10, or is it still being looked into? I can try it out on mine if we need a guinea pig.

Ive tried as hell on my own X10 :-D

I don't see OP author confirming overclocking and sending reward.



Probably because [SLA5][ANAQC]man-FIRE is still mixing Giant B which can be overclocked with X10..?

No one with X10 have confirmed overclock, while Giant B is overclocked with the sgminer i have on Github, it does about ~46 GH on LBRY, and potential much more with some smaller changes.

Is there a thread on how to overclock the B?

There is a pretty straight forward guide on my github that will allow you to OC. Change SET_ENABLE to 1 and you will be able to OC more by setting set_baikal command.

Been searching for your github but not sure where ti find it?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: cod3gen on April 04, 2018, 05:39:11 PM
Been searching for your github but not sure where ti find it?
You can find it here; https://bitcointalk.org/index.php?topic=3206908.0


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: ruplikminer on April 04, 2018, 05:50:04 PM
Been searching for your github but not sure where ti find it?
You can find it here; https://bitcointalk.org/index.php?topic=3206908.0

Thanks!


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: ra_XOr on April 05, 2018, 02:50:19 AM
adra12 good job pumpkin and now I give you candy stick you find the anwser for the 0.2 btc !

just put float for the data and  remove the 1 on the clock value on the 2 file.

and comment the app_log for data info

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

to

miner->clock        = msg.data[3];

enjoy !!!

baikal mhz clock protection removed !



Is this doable on X10 ?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: whitefire990 on April 05, 2018, 10:40:31 PM
I think someone has already cracked the X10.  Difficulty on Groestl coin has increased 4x in the last few days from 5630 to 19226.



Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: ron1989 on April 07, 2018, 05:48:08 PM
I think someone has already cracked the X10.  Difficulty on Groestl coin has increased 4x in the last few days from 5630 to 19226.



i think you are right. could be baikal themselves mining with unsold units... would be typical of them to mine the new algos until profitability drops and then release them to the public saying "look, we weren't lying!"


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: pikachuy on April 07, 2018, 07:17:53 PM
I think someone has already cracked the X10.  Difficulty on Groestl coin has increased 4x in the last few days from 5630 to 19226.



i think you are right. could be baikal themselves mining with unsold units... would be typical of them to mine the new algos until profitability drops and then release them to the public saying "look, we weren't lying!"

Duh, it's rinse and repeat. Like how they were mining cryptonight themselves until it made chump change. Right now Groestl is HIGHLY profitable, so why would they release it right now? 2 new algos will be released when they turn into chump change too.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: xxALEXANDRxx on April 10, 2018, 10:10:23 PM
Can somewone check this driver on x10? Working set_option or not.
https://drive.google.com/open?id=1W3UJmcm2oDje656Kd2KYFPIZvFj0U4wp (https://drive.google.com/open?id=1W3UJmcm2oDje656Kd2KYFPIZvFj0U4wp)


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Grumo on April 11, 2018, 05:30:48 AM
with baikal n there  must be some problem , it overclocked from 200 mhz to 420 mhz , it mined one minute then it died :'(


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: xxALEXANDRxx on April 11, 2018, 07:18:54 AM
Just x10 user`s


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: tboy32c 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! ;D


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: CNoteFan on April 11, 2018, 04:06:57 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! ;D

LOL, that is hilarious!  Too bad they forgot to securely delete the 3 earlier versions of the STM firmware on the fat32 partition. 

Nice find!


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: wholly on April 13, 2018, 12:45:53 AM

Guinea Pig for X10 ready for duty!!!

Lets get this bastard overclocked!!!


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: dmanukr on April 13, 2018, 01:42:40 AM
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! ;D

LOL, that is hilarious!  Too bad they forgot to securely delete the 3 earlier versions of the STM firmware on the fat32 partition. 

Nice find!

Good job guys


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Ironeinstein on April 13, 2018, 12:57:57 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! ;D

LOL, that is hilarious!  Too bad they forgot to securely delete the 3 earlier versions of the STM firmware on the fat32 partition. 

Nice find!

Anything useful in the old firmwares?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: as1an on April 18, 2018, 08:12:16 AM
hi,

What i need to do for win the reward 0.2 bitcoin ?

5s):184.8G (avg):185.7Gh/s | A:2141  R:0  HW:22  WU:1027.095/m
ST: 1  SS: 0  NB: 2  LW: 2188  GF: 0  RF: 0
Connected to lbry.eu.nicehash.com (stratum) diff  as user *****
Block: a24f8128...  Diff:26.4M  Started: [00:09:01]  Best share: 90.6K
--------------------------------------------------------------------------------
 SB management [P]ool management ettings [D]isplay options [Q]uit
BKLU 0: 28C 800MHz [ASICS #64] | 61.44G/64.34Gh/s | A:768 R: 0 HW:12 WU:367.401/m
BKLU 1: 28C 800MHz [ASICS #64] | 61.44G/64.29Gh/s | A:700 R: 0 HW:11 WU:336.305/m
BKLU 2: 28C 800MHz [ASICS #64] | 61.44G/64.31Gh/s | A:782 R: 0 HW: 0 WU:374.098/m


Hi All,

Does giant b lbry have a maximum of 46gh? If I am writing 184gh in the display, how can I do it, I have 46gh with the ones written on the forum.
Do we need to change the lbry.h and lbry.c files? Do you have a link to your recompile?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: dmanukr on April 21, 2018, 05:14:15 PM
Quick update on the hardware hack of the x10 ..  I received reply from my Baikal Electronics VP in Russia and he confirmed the asic chips used in the miner are not theirs but are in fact from a manufacturer in China by the same name which I've not been able to locate.  The baikalminer guys aren't the manufacturer of the chips.  Also it seems the x10 uses at minimum of 3 or 4 and possibly more.. different asic chips in their miner, which would make sense. The company I've made agreement with to produce a version of the boards has told me that if the asic chips aren't available in the market they could create a similar product but I'm hesitant at the moment given the investment I'd still need to make and need for a hash board to send.. and the fact that there are now competing products for some of the algos coming to market and one in particular that will match or exceed the x10 capability. 


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: wholly on April 23, 2018, 05:54:04 AM

Is there a way to overclock the X10 from 200Mhz to 4700Mhz????

Thanks


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: BubbaBooeee on April 23, 2018, 06:17:57 PM

Is there a way to overclock the X10 from 200Mhz to 4700Mhz????

Thanks


I would buy an X10 if it can be overclocked to 100000 Th/s ....    :o :o


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: minerbeasts on April 25, 2018, 12:42:32 AM
There's a problem with libusb in the modified X10 code. It's not recognizing or loading the BLKU driver.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Microcosm on April 25, 2018, 11:38:54 PM
hi,

What i need to do for win the reward 0.2 bitcoin ?

5s):184.8G (avg):185.7Gh/s | A:2141  R:0  HW:22  WU:1027.095/m
ST: 1  SS: 0  NB: 2  LW: 2188  GF: 0  RF: 0
Connected to lbry.eu.nicehash.com (stratum) diff  as user *****
Block: a24f8128...  Diff:26.4M  Started: [00:09:01]  Best share: 90.6K
--------------------------------------------------------------------------------
 SB management [P]ool management ettings [D]isplay options [Q]uit
BKLU 0: 28C 800MHz [ASICS #64] | 61.44G/64.34Gh/s | A:768 R: 0 HW:12 WU:367.401/m
BKLU 1: 28C 800MHz [ASICS #64] | 61.44G/64.29Gh/s | A:700 R: 0 HW:11 WU:336.305/m
BKLU 2: 28C 800MHz [ASICS #64] | 61.44G/64.31Gh/s | A:782 R: 0 HW: 0 WU:374.098/m
--------------------------------------------------------------------------------
 [2018-03-31 00:09:49.329] Accepted 258afbfb Diff 1.75K/128 BKLU 2
 [2018-03-31 00:09:49.406] Accepted 017242de Diff 176/128 BKLU 2
 [2018-03-31 00:09:49.438] Accepted 01d038c0 Diff 141/128 BKLU 0
 [2018-03-31 00:09:49.469] Accepted 01e0b067 Diff 136/128 BKLU 1
 [2018-03-31 00:09:49.502] Accepted 012f5942 Diff 216/128 BKLU 0
 [2018-03-31 00:09:49.531] Accepted e9b08f8e Diff 280/128 BKLU 1
 [2018-03-31 00:09:49.532] Accepted 0117ad05 Diff 234/128 BKLU 0
 [2018-03-31 00:09:49.595] Accepted b490479e Diff 362/128 BKLU 0
 [2018-03-31 00:09:49.611] Accepted 01b7b739 Diff 149/128 BKLU 0
 [2018-03-31 00:09:49.658] Accepted c5ca4236 Diff 331/128 BKLU 0
 [2018-03-31 00:09:49.689] Accepted 011f8baa Diff 227/128 BKLU 1
 [2018-03-31 00:09:49.690] Accepted e378bb69 Diff 288/128 BKLU 2
 [2018-03-31 00:09:49.691] Accepted 0190b98d Diff 163/128 BKLU 0
 [2018-03-31 00:09:49.752] Accepted 8e865c00 Diff 459/128 BKLU 0
 [2018-03-31 00:09:49.766] Accepted 0129fe22 Diff 219/128 BKLU 0
 [2018-03-31 00:09:49.814] Accepted 4a15d498 Diff 884/128 BKLU 1
 [2018-03-31 00:09:49.830] Accepted 0133a9d9 Diff 213/128 BKLU 0
 [2018-03-31 00:09:49.831] Accepted c74c16ab Diff 328/128 BKLU 2
 [2018-03-31 00:09:50.017] Accepted 018d87c9 Diff 164/128 BKLU 0
 [2018-03-31 00:09:50.047] Accepted d408e015 Diff 309/128 BKLU 0
 [2018-03-31 00:09:50.064] Accepted 01703018 Diff 177/128 BKLU 2
 [2018-03-31 00:09:50.157] Accepted 34fc5b0b Diff 1.24K/128 BKLU 0
 [2018-03-31 00:09:50.173] Accepted b3659a9f Diff 365/128 BKLU 2
 [2018-03-31 00:09:50.188] Accepted 8ca0a1ac Diff 466/128 BKLU 1
 [2018-03-31 00:09:50.203] Accepted 01397083 Diff 209/128 BKLU 1
 [2018-03-31 00:09:50.345] Accepted 0deca14b Diff 4.71K/128 BKLU 1
 [2018-03-31 00:09:50.346] Accepted df941aea Diff 293/128 BKLU 1
 [2018-03-31 00:09:50.439] Accepted b9ce3296 Diff 352/128 BKLU 1
 [2018-03-31 00:09:50.454] Accepted 13c5270c Diff 3.31K/128 BKLU 0
 [2018-03-31 00:09:50.484] Accepted 01213cc7 Diff 226/128 BKLU 2
 [2018-03-31 00:09:50.599] Accepted 017e6611 Diff 171/128 BKLU 0
 [2018-03-31 00:09:50.678] Accepted 01658067 Diff 183/128 BKLU 0
 [2018-03-31 00:09:50.772] Accepted 1f91b852 Diff 2.08K/128 BKLU 2
 [2018-03-31 00:09:50.787] Accepted 38d2e387 Diff 1.15K/128 BKLU 1


Is this mod of giantB legit? Can’t be, right? 185Gh/s? I have 4 pcs and will direct them all for some time it’s true and someone’s willing to help a fellow out?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: adra12 on April 30, 2018, 07:16:44 PM
Is this mod of giantB legit? Can’t be, right? 185Gh/s? I have 4 pcs and will direct them all for some time it’s true and someone’s willing to help a fellow out?

After modifying the code it doesn't matter what you see in sgminer. You should check the hash rate on the pool side, and it should be pretty close to 46 GH/s.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: whitefire990 on May 01, 2018, 01:43:52 AM
If you are interested I created a separate thread on the DIY FPGA mining rig with pics & video:
https://bitcointalk.org/index.php?topic=3459858


Eric


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Baikalek on May 01, 2018, 06:41:08 AM
If you are interested I created a separate thread on the DIY FPGA mining rig with pics & video:
https://bitcointalk.org/index.php?topic=3459858


Eric
WTF its for Baikal miners here...??!!


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: wholly on May 25, 2018, 05:13:12 AM





























































































Any Updates for The Baikal X10 Giant Please????














Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: sergey1301 on June 07, 2018, 08:38:10 AM
Hello!! 0.2 btc is a lot, for-Blake2b! Update the firmware to Blake2s. Will it even work?? I think not. But You did a great job, thank you for that!


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Andartis on June 21, 2018, 02:57:06 AM
I am confused. So can we overclock the Baikals or not?  ;D


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: namsss on July 07, 2018, 11:03:16 AM
Hi everyone !
I think hash board need more power to overlock , i saw many version of hash board . 6 and 8 power chip .


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: chinalovebtc on July 26, 2018, 04:11:16 PM
We are committed to the Baikal machine cracking, we have been studying the firmware for a long time, and have made some progress. If a friend wants to join our research team, we are very welcome to contact us.

Discord: greatwallbtc#5210


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: afrodisio on August 07, 2018, 02:17:17 PM
Just thought I'd drop off one more piece of good news.

This was inside the X10 image.
File name: miner.html-gzip-1547-8889-1508339623       
Dated 10/18/2017

Notice, Nist5 and Groestl were options in the drop down.

Gotta love Scripta, lol.

Code:

        <div class="col-sm-2">       
  <select class="form-control" ng-model="pool.algo" required>
    <option>x11</option>   
    <option>quark</option>
    <option>qubit</option>   
    <option>nist5</option>
    <option>skein</option>
    <option>groestl</option>
    <option>myr-gr</option>   
  </select>
      </div>
Code:
xxx

Please enter long source code into xxx.
Between labels [ code] and [ /code] without space [_c.....



hi ,我該怎麼去尋找到 miner.html-gzip-1547-8889-1508339623 這個檔案
我尋找了 x10 firmware,並沒找看到你說的這個檔案。

我正在測試是否能從baikal n+ 去使用其它算法。

115/5000
Hi, wǒ gāi zěnme qù xúnzhǎo dào miner.Html-gzip-1547-8889-1508339623 zhège dǎng'àn
wǒ xúnzhǎole x10 firmware, bìng méi zhǎo kàn dào nǐ shuō de zhège dǎng'àn.

Wǒ zhèngzài cèshì shìfǒu néng cóng baikal n+ qù shǐyòng qítā suànfǎ.
Hi, how can I find the file miner.html-gzip-1547-8889-1508339623
I looked for x10 firmware and didn't look for the file you said.

I am testing whether I can use other algorithms from baikal n+.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: piccolobit on August 07, 2018, 02:41:13 PM


I am testing whether I can use other algorithms from baikal n+.


what algorithms are you testing?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: afrodisio on August 08, 2018, 11:27:46 AM


I am testing whether I can use other algorithms from baikal n+.


what algorithms are you testing?


I confirmed that other algorithms can be executed on n+. 

The X11 algorithm can be executed on n+.
Like BKX, there can be 10G Harsh
But the machine will automatically recover to cryptonight after a while

I need people who are interested in using c language to study and test together.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: piccolobit on August 08, 2018, 12:53:28 PM


I am testing whether I can use other algorithms from baikal n+.


what algorithms are you testing?


I confirmed that other algorithms can be executed on n+. 

The X11 algorithm can be executed on n+.
Like BKX, there can be 10G Harsh
But the machine will automatically recover to cryptonight after a while

I need people who are interested in using c language to study and test together.

I have 2 N + to be used for testing, but I do not know the C language, I have updated the firmware with the custom cod3gen ones, if I can be useful let me know ...


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: afrodisio on August 08, 2018, 08:33:30 PM


I am testing whether I can use other algorithms from baikal n+.


what algorithms are you testing?


I confirmed that other algorithms can be executed on n+. 

The X11 algorithm can be executed on n+.
Like BKX, there can be 10G Harsh
But the machine will automatically recover to cryptonight after a while

I need people who are interested in using c language to study and test together.

I have 2 N + to be used for testing, but I do not know the C language, I have updated the firmware with the custom cod3gen ones, if I can be useful let me know ...



I am currently testing n + and n
A few days ago, one of the N+ machines burned out during the test.

I also don't use the c programming language, but I am also trying to refer to it.
X10, N+ configuration documentation.

If we want to discuss, we need a software that can chat instantly. Maybe wechat or line


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: elmond on August 11, 2018, 09:59:32 AM
@cod3gen

do this portion of code really working in x10?
 //#if 0 Removed to allow test of other algos
  ALGO_ALIAS("groestlcoin",  "groestl");
  ALGO_ALIAS("talkcoin",     "nist5");
  ALGO_ALIAS("talkcoin-mod", "nist5");
  ALGO_ALIAS("x11gost",      "x11-gost");
  ALGO_ALIAS("sibcoin",      "x11-gost");
  ALGO_ALIAS("sibcoin-mod",  "x11-gost");
  //#endif 0 Removed to allow test of other algos


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: afrodisio on August 12, 2018, 06:21:07 PM
@cod3gen

do this portion of code really working in x10?
 //#if 0 Removed to allow test of other algos
  ALGO_ALIAS("groestlcoin",  "groestl");
  ALGO_ALIAS("talkcoin",     "nist5");
  ALGO_ALIAS("talkcoin-mod", "nist5");
  ALGO_ALIAS("x11gost",      "x11-gost");
  ALGO_ALIAS("sibcoin",      "x11-gost");
  ALGO_ALIAS("sibcoin-mod",  "x11-gost");
  //#endif 0 Removed to allow test of other algos

I measured that gn can execute x11 to 10gh/s, but it will restart every 5~6 minutes.

Can someone test the 1751 carrier board?


Can someone teach me how to post a picture on a reply?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: elmond on August 13, 2018, 01:27:25 AM
@cod3gen

do this portion of code really working in x10?
 //#if 0 Removed to allow test of other algos
  ALGO_ALIAS("groestlcoin",  "groestl");
  ALGO_ALIAS("talkcoin",     "nist5");
  ALGO_ALIAS("talkcoin-mod", "nist5");
  ALGO_ALIAS("x11gost",      "x11-gost");
  ALGO_ALIAS("sibcoin",      "x11-gost");
  ALGO_ALIAS("sibcoin-mod",  "x11-gost");
  //#endif 0 Removed to allow test of other algos

I measured that gn can execute x11 to 10gh/s, but it will restart every 5~6 minutes.

Can someone test the 1751 carrier board?


Can someone teach me how to post a picture on a reply?

interesting. can yo udescribe in detail how you do that?
x11 is using 630watt on x10, what is yours?

you can you some free upload webiste then paste the link here
https://imgur.com/upload
https://imgur.com/a/enuN1VY



Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: afrodisio on August 14, 2018, 10:09:37 PM
@cod3gen

do this portion of code really working in x10?
 //#if 0 Removed to allow test of other algos
  ALGO_ALIAS("groestlcoin",  "groestl");
  ALGO_ALIAS("talkcoin",     "nist5");
  ALGO_ALIAS("talkcoin-mod", "nist5");
  ALGO_ALIAS("x11gost",      "x11-gost");
  ALGO_ALIAS("sibcoin",      "x11-gost");
  ALGO_ALIAS("sibcoin-mod",  "x11-gost");
  //#endif 0 Removed to allow test of other algos

I measured that gn can execute x11 to 10gh/s, but it will restart every 5~6 minutes.

Can someone test the 1751 carrier board?


Can someone teach me how to post a picture on a reply?

interesting. can yo udescribe in detail how you do that?
x11 is using 630watt on x10, what is yours?

you can you some free upload webiste then paste the link here
https://imgur.com/upload
https://imgur.com/a/enuN1VY


https://imgur.com/5cg8bkI

Sorry, I don't know English, I only use google translation

This is the test today, I made some changes on N, trying to let the machine mine aeon, but the data presented in the figure is as follows:
1. The power cannot achieve the performance of asic
2. But be sure to connect with aeonpool on algorithm changes
3. I am even more skeptical that baikal is decoded from the control board to the asic blade for computational analysis.

Does anyone change the algo menu at the front desk?
Can you pm me, make one for me...?


Ps. If you have difficulty reading the word, it must be a google translation problem, please understand.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: elmond on August 15, 2018, 02:51:42 AM
@cod3gen

do this portion of code really working in x10?
 //#if 0 Removed to allow test of other algos
  ALGO_ALIAS("groestlcoin",  "groestl");
  ALGO_ALIAS("talkcoin",     "nist5");
  ALGO_ALIAS("talkcoin-mod", "nist5");
  ALGO_ALIAS("x11gost",      "x11-gost");
  ALGO_ALIAS("sibcoin",      "x11-gost");
  ALGO_ALIAS("sibcoin-mod",  "x11-gost");
  //#endif 0 Removed to allow test of other algos

I measured that gn can execute x11 to 10gh/s, but it will restart every 5~6 minutes.

Can someone test the 1751 carrier board?


Can someone teach me how to post a picture on a reply?

interesting. can yo udescribe in detail how you do that?
x11 is using 630watt on x10, what is yours?

you can you some free upload webiste then paste the link here
https://imgur.com/upload
https://imgur.com/a/enuN1VY


https://imgur.com/5cg8bkI

Sorry, I don't know English, I only use google translation

This is the test today, I made some changes on N, trying to let the machine mine aeon, but the data presented in the figure is as follows:
1. The power cannot achieve the performance of asic
2. But be sure to connect with aeonpool on algorithm changes
3. I am even more skeptical that baikal is decoded from the control board to the asic blade for computational analysis.

Does anyone change the algo menu at the front desk?
Can you pm me, make one for me...?


Ps. If you have difficulty reading the word, it must be a google translation problem, please understand.

you shall explain how you make the change.

the algo menu list can be modify in /var/www/partials/miner.html


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: kineda on August 15, 2018, 12:07:28 PM

you shall explain how you make the change.

the algo menu list can be modify in /var/www/partials/miner.html

thanks! i've been wondering where this was


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: afrodisio on August 22, 2018, 11:54:33 AM
http://imgur.com/a/Wa7HaxB


Where do these coded codes find other algorithmic use addresses?

Suppose I want to add a lyra2z


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: piccolobit on August 22, 2018, 12:54:22 PM


Does anyone change the algo menu at the front desk?
Can you pm me, make one for me...?




you need change the file in the /var/www root


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: afrodisio on August 23, 2018, 04:11:48 AM


Does anyone change the algo menu at the front desk?
Can you pm me, make one for me...?




you need change the file in the /var/www root

The menu is already a trivial matter.
Currently testing cnv7,

In a known file
Cn0 is 0x20
CN-lite is 0X22

Some people know what to use Lyra2Z, cnv7


======================================================
#define VARIANT1_PARAMS , const uint tweak1
#define VARIANT1_1(p) \
  do \
  { \
    uint table = 0x75310U; \
    uint index = (((p).s2 >> 26) & 12) | (((p).s2 >> 23) & 2); \
    (p).s2 ^= ((table >> index) & 0x30U) << 24; \
  } while(0)

#define VARIANT1_2(p) \
    (p) ^= tweak1_2

#define VARIANT1_INIT() \
    uint2 tweak1_2; \
    tweak1_2.s0 = tweak1; \
    tweak1_2.s1 = get_global_id(0); \
    tweak1_2 ^= as_uint2(states[24]);


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: piccolobit on August 23, 2018, 04:14:54 PM
You are testing cnv7 on baikal N series?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: afrodisio on August 24, 2018, 04:28:27 AM
You are testing cnv7 on baikal N series?

yes

https://i.imgur.com/rl6Am8s.jpg

I don't have the basics of a programming language, so it's very difficult. I hope that users with c can help me.

In this picture, baikal should be reserved for the upgrade of v7 in sgminer


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: piccolobit on August 24, 2018, 09:04:54 AM
You are testing cnv7 on baikal N series?

yes

https://i.imgur.com/rl6Am8s.jpg

I don't have the basics of a programming language, so it's very difficult. I hope that users with c can help me.

In this picture, baikal should be reserved for the upgrade of v7 in sgminer

very interesting .... also I am not practical of the language c ... but I'm trying some changes


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: afrodisio on August 24, 2018, 03:52:34 PM
You are testing cnv7 on baikal N series?

yes

https://i.imgur.com/rl6Am8s.jpg

I don't have the basics of a programming language, so it's very difficult. I hope that users with c can help me.

In this picture, baikal should be reserved for the upgrade of v7 in sgminer

very interesting .... also I am not practical of the language c ... but I'm trying some changes

Unfortunately, we don't know baikal's engineers, or masters of c programming languages; they can only test themselves.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: kineda on August 29, 2018, 01:17:45 AM

the algo menu list can be modify in /var/www/partials/miner.html

i edited /var/www/partials/miner.html but my changes don't show up in the dashboard? i even rebooted and looked at all of the php files but no change.  am i missing something?  thanks!


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: elmond on August 29, 2018, 02:09:50 AM

the algo menu list can be modify in /var/www/partials/miner.html

i edited /var/www/partials/miner.html but my changes don't show up in the dashboard? i even rebooted and looked at all of the php files but no change.  am i missing something?  thanks!

it's a cache problem, you might need to press ctrl + F5 on chrome, for other bowser please ggole it.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: kineda on August 29, 2018, 12:09:12 PM

the algo menu list can be modify in /var/www/partials/miner.html

i edited /var/www/partials/miner.html but my changes don't show up in the dashboard? i even rebooted and looked at all of the php files but no change.  am i missing something?  thanks!

it's a cache problem, you might need to press ctrl + F5 on chrome, for other bowser please ggole it.

worked thanks!


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: afrodisio on September 02, 2018, 12:18:30 PM
You are testing cnv7 on baikal N series?

yes

https://i.imgur.com/rl6Am8s.jpg

I don't have the basics of a programming language, so it's very difficult. I hope that users with c can help me.

In this picture, baikal should be reserved for the upgrade of v7 in sgminer

very interesting .... also I am not practical of the language c ... but I'm trying some changes

https://imgur.com/a/AW61Ep0

I found that it lacks two files in the kernel path.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: piccolobit on September 02, 2018, 03:54:13 PM
You are testing cnv7 on baikal N series?

yes

https://i.imgur.com/rl6Am8s.jpg

I don't have the basics of a programming language, so it's very difficult. I hope that users with c can help me.

In this picture, baikal should be reserved for the upgrade of v7 in sgminer

very interesting .... also I am not practical of the language c ... but I'm trying some changes

https://imgur.com/a/AW61Ep0

I found that it lacks two files in the kernel path.

Is on the Baikal N series?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: afrodisio on September 03, 2018, 06:46:43 PM
You are testing cnv7 on baikal N series?

yes

https://i.imgur.com/rl6Am8s.jpg

I don't have the basics of a programming language, so it's very difficult. I hope that users with c can help me.

In this picture, baikal should be reserved for the upgrade of v7 in sgminer

very interesting .... also I am not practical of the language c ... but I'm trying some changes

https://imgur.com/a/AW61Ep0



I found that it lacks two files in the kernel path.

Is on the Baikal N series?


yes. baikal for cod3gen version .  lacks two files  ..lwolf-aes.cl & wolf-skein.cl in the kernel path


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: afrodisio on September 05, 2018, 01:54:31 PM
You are testing cnv7 on baikal N series?

yes

https://i.imgur.com/rl6Am8s.jpg

I don't have the basics of a programming language, so it's very difficult. I hope that users with c can help me.

In this picture, baikal should be reserved for the upgrade of v7 in sgminer

very interesting .... also I am not practical of the language c ... but I'm trying some changes

https://imgur.com/a/AW61Ep0

I found that it lacks two files in the kernel path.

Is on the Baikal N series?


Someone will write the algorithm of cn v7, in the n series has completed the reverse engineering and compilation of the firmware, only the formula of the lack of algorithm


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: piccolobit on September 06, 2018, 09:43:06 AM
You are testing cnv7 on baikal N series?

yes

https://i.imgur.com/rl6Am8s.jpg

I don't have the basics of a programming language, so it's very difficult. I hope that users with c can help me.

In this picture, baikal should be reserved for the upgrade of v7 in sgminer

very interesting .... also I am not practical of the language c ... but I'm trying some changes

https://imgur.com/a/AW61Ep0

I found that it lacks two files in the kernel path.

Is on the Baikal N series?


Someone will write the algorithm of cn v7, in the n series has completed the reverse engineering and compilation of the firmware, only the formula of the lack of algorithm

someone sure knows how to do it, or has already done it .... but they do not say it ....


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: HE[A]RTLESS on September 07, 2018, 01:05:25 AM
how much profit for today?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: serjorossi on September 20, 2018, 11:23:04 AM
Interesting fact. The boards for x10 and Giant B are the same. Is it possible to make X10 from Giant B Huh?? What is the difference?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: elmond on September 21, 2018, 02:23:22 AM
Interesting fact. The boards for x10 and Giant B are the same. Is it possible to make X10 from Giant B Huh?? What is the difference?


the asic chip was different.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: afrodisio on September 22, 2018, 12:17:44 PM
Does anyone know how to get Baikan N to execute sgminer synchronization instructions -- monero ??

Can you help me with php compilers?


Or join the discussion together  https://hangouts.google.com/group/oYiLWNsVuy5k9Kqk1


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: elmond on September 24, 2018, 02:43:31 AM
Does anyone know how to get Baikan N to execute sgminer synchronization instructions -- monero ??

Can you help me with php compilers?


Or join the discussion together  https://hangouts.google.com/group/oYiLWNsVuy5k9Kqk1

you are no idea what are you doing. that not how the miner works....


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: okyanus58 on October 10, 2018, 07:21:20 PM
https://www.youtube.com/watch?v=AiJA_2ZNVlM


Is it real


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: rogerthat55 on October 10, 2018, 10:40:39 PM
https://www.youtube.com/watch?v=AiJA_2ZNVlM


Is it real

Good question. I would think I would see their username on this list https://grs.suprnova.cc/index.php?page=statistics&action=pool unless they only mined as anonymous for a short amount of time. The last found block on grs.suprnova.cc was October 2nd, so I would think with that hash rate, they would of found a block already. On the Groestlcoin difficulty chart https://www.coinwarz.com/difficulty-charts/groestlcoin-difficulty-chart you can see some major activity on October 3, the date the YouTube video was posted. They want 0.1 BTC to load the software. Kind of hard to justify that amount of money just to see if it's real. I think it would give me more proof if they showed their mining username on https://grs.suprnova.cc/index.php?page=statistics&action=pool with their hashrate.

... and I checked their BTC address and they have zero transactions, so nobody has paid them their fee.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Allats on October 13, 2018, 06:22:48 AM
Rogue employee leaked that?
And also what's up with the price? They have one price for 1 BKX and another price for 10. If you download the firmware, can't you use it for more that one miner?


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: carlosSantana on October 22, 2018, 07:56:34 PM
video seems to be true , but I am not sure if it can work stabilized for long periods overclocked.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: onegiantcock on October 23, 2018, 03:18:23 AM
.1BTC to overclock your X10?!  What a gouge. Can almost buy another X10 for that.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Tarlatata on November 12, 2018, 11:14:53 PM
Anyone managed to overclock some Baikal ? Got some G28 and at start I can see it do Skein at over 40GH until software seems to lower it to the capped 14gh.

https://i.imgur.com/XZHNveB.png


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: ldcomp on May 06, 2019, 05:13:32 PM
is there a firmware baikal x10 that has updated algo?  :'(


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: sgenuine on May 08, 2019, 06:02:15 PM
is there a firmware baikal x10 that has updated algo?  :'(

As soon as I know, the latest one which is called PiZero GX10 v.1.2. is dated 2018. I do not have any information about the new firmware. I know that some people meet problems with this stuff. Probably, they will be decided.


Title: Re: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡
Post by: Google+ on May 08, 2019, 09:15:45 PM
if you always use overclock every day, will this make my device break fast? because I think performance is too high even though the benefits obtained are also high, I hope this also does not have an effect on increasing electricity use.