Pages:
Author

Topic: Baikal X10 ⚡OVERCLOCK⚡ Claim reward 0.2 BTC for TUTORIAL HOW TO :)⚡⚡⚡⚡ - page 15. (Read 22768 times)

newbie
Activity: 39
Merit: 0
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.
newbie
Activity: 28
Merit: 0
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..........

 

Monero Pools


   


      Click to add pool to pool's list
   


   
     
       
     SupportXMR       
   XMRPool           
        DwarfPool
        NanoPool               
        Nicehash                       
   

   

Aeon Pools


   


      Click to add pool to pool's list
   



   

       AeonMiningPool
        Sumominer       
        RuPool
   
   

 
 

   
 

      

         

            

            


               
            


            


               Ordered from gentle to rough.
            


            

               Cgminer soft reset (RPC)
               
               Restart cgminer linux process(30s)
               
               
            

         

      


   

Pools



   


      The settings below serve as direct input to the miner. One little error can and will let the miner crash.
   


   

     

       
       
       
       
       
     

     

       

         
       

       
       
           
                                
         

       
       

         
       

     

         
     

newbie
Activity: 39
Merit: 0
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\
jr. member
Activity: 56
Merit: 1
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.
jr. member
Activity: 42
Merit: 25
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.

That's good but someone with a Giant-B needs to do it.
newbie
Activity: 39
Merit: 0
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.
newbie
Activity: 39
Merit: 0
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.
jr. member
Activity: 42
Merit: 25
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.
full member
Activity: 308
Merit: 107
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
hero member
Activity: 980
Merit: 1000
.
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
jr. member
Activity: 56
Merit: 1
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.
newbie
Activity: 39
Merit: 0

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?
hero member
Activity: 1118
Merit: 541

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

newbie
Activity: 39
Merit: 0
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?
newbie
Activity: 39
Merit: 0
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!
full member
Activity: 448
Merit: 100
You have any evidence to show your proof? anyone sends him money ?
full member
Activity: 584
Merit: 106
Looks like it stays on 10GH/s.

Show us a print screen of improved hashrate please.
hero member
Activity: 980
Merit: 1000
.
Here 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.



OC Working or not ? hash rate up , more than 10GHS ?
newbie
Activity: 39
Merit: 0
Here 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.

Pages:
Jump to: