I am having a similar issue.  My Baikal is connecting to the pools but no devices are running.  Also I only see red lights on the Baikal, no blue lights.  When I check with Baikal Monitor it shows this miner as 'sick'.  Anyone run into this?  Anyone have a fix?

Just received my Giant B on Friday.  After plugging it in and pointing it to nicehash it's not working.  The red lights show up but no blue lights.  It connects to the pools but doesn't do any work.  Has anyone else had this problem?  Has anyone solved this problem?  Any help would be greatly appreciated.

Update:  Fixed the problem.  The support staff at asicminermarket.com sent me the following instructions:

anyone having troubles with their Giant X10 or B, could you try logging into it (default user:pass is baikal:baikal) and running this command:

Code:
lsusb | grep 0483

This command will list the USB devices attached to the OrangePi and then filter those results to only show lines with "0483" (STMicroelectronics' USB vendor ID). The expected result is this (where things should be working properly):

Code:
Bus 007 Device 003: ID 0483:5740 STMicroelectronics STM32F407

But if you get this:

Code:
Bus 007 Device 002: ID 0483:df11 STMicroelectronics STM Device in DFU Mode

Then the STM32 microcontroller may need to be reset (it is stuck in firmware download mode). If this is the case, issue these two commands:

Code:
echo 0 > /sys/class/gpio_sw/PA10/data
echo 1 > /sys/class/gpio_sw/PA10/data

The first command sets the PA10 pin to 0 (off) on the OrangePi, which is connected to the STM32's reset pin, which in turn holds it in a reset state (it needs to be at 0v to reset). The second command de-asserts (sets to 1 in this case) the reset pin allowing the STM32 to begin normal operations. These steps fixed the issue with a Giant X10 I looked at. These commands may need to be run again after reboot, so you may want to write a script in your favorite language to do this at boot or to do a periodic check.

If you get "permission denied" (or something like that, I don't remember the exact message ATM) when trying those commands, try this first:

Code:
su
(then type "baikal" again for the password to elevate your terminal to root level)
Or simply log in as root:baikal instead.

Worked for me and I hope it helps other.