Baikal Giant X10

[DVD_GR]

when nist5 algo goes live , the device will cost 20k in ebay wait and see

[1714981832]

1714981832

[1714981832]

1714981832

[1714981832]

1714981832

[1714981832]

1714981832

[1714981832]

1714981832

[cryptonitro]

when nist5 algo goes live , the device will cost 20k in ebay wait and see

no because the profit will fall

[tomwrx]

when nist5 algo goes live , the device will cost 20k in ebay wait and see

no because the profit will fall

yup, everyone will jump on nist5 and profit will be like for other algo's today. Don't have any ilusion about that.

[ismurdegus]

Hi guys

Not sure where to post this maybe useful information.....

I did some test with my X10 and I find that the Giant-B and X10 are the same machine.

The only difference is of course the OS inside the SD card and the firmware inside the controller board (blue card with ST microcontroller)

So, what I did is install the Giant-B image on my X10 .... :-0

The miner start like normal. The interface show all correct and also the hash cards show the right frequency and right hash power.

At this point I try to connect my unit at a lby pool..... The pool accept the connection but the miner reject the data to decrypt.

Ask me some question if you want...


Ciao

[burnsauce]

when nist5 algo goes live , the device will cost 20k in ebay wait and see

no because the profit will fall

It will spike the cost on ebay because ebay buyers are stupid.  They will look at what the calculator is telling them today, and dream about the possibilities with stars in their eyes. They'll see that paypal credit ad (6 months no payments!) looking them right in the face and figure it's a sure thing. 

Of course it's going up to $20k on ebay.  No, not because it's worth it.  If people were paying what they were 'worth' now, no one would be shelling out $6500 for one.

[cryptonitro]

Hi guys

Not sure where to post this maybe useful information.....

I did some test with my X10 and I find that the Giant-B and X10 are the same machine.

The only difference is of course the OS inside the SD card and the firmware inside the controller board (blue card with ST microcontroller)

So, what I did is install the Giant-B image on my X10 .... :-0

The miner start like normal. The interface show all correct and also the hash cards show the right frequency and right hash power.

At this point I try to connect my unit at a lby pool..... The pool accept the connection but the miner reject the data to decrypt.

Ask me some question if you want...


Ciao

someone still try that , there is difference between miners i think , may be in memory data / pic or else , it cant be exctly the same , or your miner wont reject data

[burnsauce]

Hi guys

Not sure where to post this maybe useful information.....

I did some test with my X10 and I find that the Giant-B and X10 are the same machine.

The only difference is of course the OS inside the SD card and the firmware inside the controller board (blue card with ST microcontroller)

So, what I did is install the Giant-B image on my X10 .... :-0

The miner start like normal. The interface show all correct and also the hash cards show the right frequency and right hash power.

At this point I try to connect my unit at a lby pool..... The pool accept the connection but the miner reject the data to decrypt.

Ask me some question if you want...


Ciao

I don't think you've uncovered anything that anyone doesn't know.  While the controller board is the same (Orange Pi I believe?), from your report it also appears that the hash-boards themselves are different because the hash boards in your x10 do not have the capability to do lby... hence your rejections.

[ismurdegus]

Hi guys

Not sure where to post this maybe useful information.....

I did some test with my X10 and I find that the Giant-B and X10 are the same machine.

The only difference is of course the OS inside the SD card and the firmware inside the controller board (blue card with ST microcontroller)

So, what I did is install the Giant-B image on my X10 .... :-0

The miner start like normal. The interface show all correct and also the hash cards show the right frequency and right hash power.

At this point I try to connect my unit at a lby pool..... The pool accept the connection but the miner reject the data to decrypt.

Ask me some question if you want...


Ciao

I don't think you've uncovered anything that anyone doesn't know.  While the controller board is the same (Orange Pi I believe?), from your report it also appears that the hash-boards themselves are different because the hash boards in your x10 do not have the capability to do lby... hence your rejections.

There are 3 parts inside the Bikal miner

1) OrangePi
2) Control Board
3) Hashing boards

When I try to mine lbry, the miner was up and running. Temperature of chips went UP and was generating 40GH/s
The rejection was from the pool not from the miner.

I think I did a screenshot, let me find it

[ismurdegus]

Screen shot

https://i.imgur.com/5C9aZ16.png

[DVD_GR]

If the device's asics are fpga's and programmed differently at B it will just never work...

[ismurdegus]

If the device's asics are fpga's and programmed differently at B it will just never work...

On the control board there is a micro usb connector. I am sure is used to flash the controller onboard.

If we had the possibility to extract the firmware from a Giant B and flash it on an X10 board, I am sure will work

[mano237]

Is there a video available where I can see how to unbox the Pi for flashing firmware?

[burnsauce]

Hi guys

Not sure where to post this maybe useful information.....

I did some test with my X10 and I find that the Giant-B and X10 are the same machine.

The only difference is of course the OS inside the SD card and the firmware inside the controller board (blue card with ST microcontroller)

So, what I did is install the Giant-B image on my X10 .... :-0

The miner start like normal. The interface show all correct and also the hash cards show the right frequency and right hash power.

At this point I try to connect my unit at a lby pool..... The pool accept the connection but the miner reject the data to decrypt.

Ask me some question if you want...


Ciao

I don't think you've uncovered anything that anyone doesn't know.  While the controller board is the same (Orange Pi I believe?), from your report it also appears that the hash-boards themselves are different because the hash boards in your x10 do not have the capability to do lby... hence your rejections.

There are 3 parts inside the Bikal miner

1) OrangePi
2) Control Board
3) Hashing boards

When I try to mine lbry, the miner was up and running. Temperature of chips went UP and was generating 40GH/s
The rejection was from the pool not from the miner.

I think I did a screenshot, let me find it

I have no doubt that it's "mining". I have doubt that what is coming out is lbry hashes (my doubts are confirmed by your rejections).  The issue is likely that the software is saying 'give me algorithm 1' to the hash boards (thinking algorithm 1 is lbry), but your hashboards aren't b+ boards, so 'algorithm 1' on them is something different.  I'm not saying this is "proof", but I could certainly see how this situation would lead to what you are experiencing.

[pikachuy]

There are 3 parts inside the Bikal miner

1) OrangePi
2) Control Board
3) Hashing boards

Can you try swapping the OrangePi and Control Board and leaving the hashing boards the same between the x10 and Giant B?

[Baikalek]

Hi guys

Not sure where to post this maybe useful information.....

I did some test with my X10 and I find that the Giant-B and X10 are the same machine.

The only difference is of course the OS inside the SD card and the firmware inside the controller board (blue card with ST microcontroller)

So, what I did is install the Giant-B image on my X10 .... :-0

The miner start like normal. The interface show all correct and also the hash cards show the right frequency and right hash power.

At this point I try to connect my unit at a lby pool..... The pool accept the connection but the miner reject the data to decrypt.

Ask me some question if you want...


Ciao

Read this please, not only overclocking.
https://bitcointalk.org/index.php?topic=2790982

[DVD_GR]

If the device's asics are fpga's and programmed differently at B it will just never work...

On the control board there is a micro usb connector. I am sure is used to flash the controller onboard.

If we had the possibility to extract the firmware from a Giant B and flash it on an X10 board, I am sure will work

possibly but it is surely locked by baikal , only if their support could give us information but i think they will not

[Hellracer]

Hi,

have the problem that my Baikal Gaint X10 will fail about 1 time a day.

I have to restart the miner every time.


If there is a remedy, the blue LEDs on the hashboard light up.

new Firmware update did not bring any improvement

[GunsN]

Hi,

have the problem that my Baikal Gaint X10 will fail about 1 time a day.

I have to restart the miner every time.


If there is a remedy, the blue LEDs on the hashboard light up.

new Firmware update did not bring any improvement

everyone have the same problem, there is no solution yet

[TheCubanMiner]

You are missing the crucial part when replacing the images of the OrangePI. The firmware bin file for the STM chip.

The STM chip has a specific set of algorithms pre-coded into the firmware code. You cannot get around it.

You will have to get the running bin file from a Giant B or X10's STM chip and place it in the "/media/boot/" folder and call it, "G*.bin"

When the miner reboots on the new image of the miner it will compare versions and replace the existing flashed image by entering DFU Mode.

Once updated, it will reenable the hash boards and being mining.

It's doable.



The reason behind that is that the file location and name is here, 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"

[Hellracer]

ok so you also have problems with the Baikal giant X10. The funny thing is that a miner runs normally and the 2 te fails again and again does not restart by itself. will help a new control board