Topic: Baikal Giant X10 - page 84. (Read 132901 times)

Yes. I'll give it until I go to get my next cup of coffee and check again.  So far, so good, though.

Edit: Everything still looks to be working well! Hashrate is right on target.

I do not use more than one PSU for my miner.  I could certainly see that causing issues though.

It may make it hard for the individual supplies to keep themselves regulated when they are all tied together like that.

It depends on the PSU, but some also will not regulate properly (or even turn on) if there is not enough load on the outputs. One board might not be enough of a draw to keep an entire PSU functioning by itself when it's not mining.

Most of my 'miner down' problems seem related to how the giant interacts with my local network environment.

sounds good. Is your hashrate on the pool displayed correctly ? It will take probably 5-15 mins until it's stable but after then it should be displayed correctly

My four X10 ran good for 2 days then one of them had the blue blinking light.

This little guy make problems now again and again. Maybe it is because he got his power supply from 3 different psus.
I don‘t had enough cable to use a single one for two X10‘s.

They definitely have to be started all at a time, because if not the orange pi will detect not all of the boards.


People with the blue light problem, do you use more then one psu for one miner?


I have
- Static IP via MAC
- Named them unique in the router
- Unique worker name
-> now I have  set my timezone to the correct (maybe this works)

I can login to the problem child and do a restart via commands but only power reset works.

I'm pointed at you right now. Took a little bit, but my diff is definitely adjusting. Went from 0.1 to 17.

Right after typing this it jumped me up to 263.552

It now has me set at 20. That's about where I might put it myself, so it looks to be working fine.

Hey folks,

I'm testing a XVG myriad-groestl pool:

https://xvg-mg.suprnova.cc

Can someone point a Baikal and report if the diff retarget etc. is working fine ?

Thanks,

oc

PS: it's a new database format, you'll need to re-register and set up workers even if you already got a suprnova account, I'm in the progress of migrating to a new DB design.

First you must sign up in the site.  Once you are logged in, you need to create a "worker" by going to the 'My Account -> My Workers' link.

Next use this to setup baikal miner:

URL: stratum+tcp://xvg-mine.idcray.com:10061
Algo: myr-gr
User:  youUserName.yourWorkerName
Pass: yourWorkerPassword

(of course, replace the "yourXXXX" with the username and password you created when setting up the worker.)

Let me know if that doesn't do it for ya.


(Note: You may want to use a port other than 10061 to get the best difficulty setting.  The available ports with respective diffuculties are listed on the 'home' page.)

Hi. Does anyone know how to set up baikal interface to mine XVG on idcray? I mean stratum server and what to write on user and password. Thanks

Urgh after two days my x10 is down. can't login through webGUI. pool is showing nothing.

ofcourse I am like 8000 miles away from my machine. hope my family can turn it off and back on quickly.

or that it didn't die

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


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):


But if you get this:


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:


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:

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

Please do a quick Google search of these commands first to know that they're actually doing what I've explained above. You should default to not trusting random internet stranger's instructions if you're not familiar with what you're doing. Hopefully this helps someone solve their miner issues. Please post if you tried these steps and it solved the issue for you so I know if this is a common problem or if I'm the only one who had trouble with it. Happy mining!


My ("tboy32c") PGP fingerprint: 02F2 B257 1793 8F10 3089 F951 2EE7 F90A 2A75 9BC6
Message signature:
iQEzBAABCAAdFiEEAvKyVxeTjxAwiflRLuf5Cip1m8YFAlpIW7gACgkQLuf5Cip1m8bLJgf/
TmL2jFsaknETS81QkLdsoqE4RDpW5Wn2/fU40K8PfNz3BupfE/htC+weOgw0TBtTgdg+loTT
OWeevU51BoiAbQVAsJesAy4MSqDpAasX1raS1bwOAz21fbf+0mYYDiRJChNrrIThJJT+wFLL
zy1z47LE/msYvv4UY23P0GABXKf36kALBQCJXTMgnSFAl7XrP6hEH9MslV2XDe+4crtBzt1q
Y+xDhLqPsNomtDNqPH7M/wi8GItT5rXk8Cb3lIDVB1mzump/c4YLWse1KTR93KTpoyg/l++d
1ORVlJ+SX724d6nNX75UeAz1R3E8hh8+M/9AKg8YIipMEjKNzuJD8A==

Yes, idcray is paying, I am receiving my mined XVG.
Web frontend is too laggy though, maybe they are overloeded or ddossed.

I have no problems on MPH switching to Skein and back. It sometimes take some seconds, so the miner goes to another pool that is set as failover, but then it goes back to MPH. What network settings do you use? DHCP, Static IP?

i earned since last saturday 7k verge on idcray and get every single verge on my wallet
just to say of someone want to mine verge and dont find any other pool

got my x10's from 2nd batch yesterday, arrived in promised time frame. Monitored Shipping process, took 3 days from china.
Had to deal with the miner down issue a few times because of deleted pools but was always able to bring em back online with proper backup.

One hashboard of a miner has only 48 out of 64 chips active which is a bit of a bummer.. resulting in a ~8% decreased performance for this unit - contacted Support, awaiting reply.
Otherwise all running stable since 24h now with static IP set over Router and a 2200w murata PSU powering both (yea, overkill but got it cheap..).

First Asic's for me in the mix while mining with GPU's and Cloud - profit is pretty decent, so far no regrets.

BLINKING BLUE LIGHT FIX

I may have just stumbled on a fix for the blinking blue light issue. I haven't had a problem with it until last night. I restored one of my miners' settings from a backup and forgot to change the username under the pool configs, so two of my machines were hashing on the same pool with the same username. Got the blinking blue light. Reset the machines to have different usernames and everything has been working fine. This was mining on idcray-xvg pool, haven't observed the issue with other pools.

Hope this helps someone!
-Iron

Tips:
LTC - LMP2zZQpgcb3HQk364vjSAgC1po5yYFQ2G

Update: just tried switching to MPH and got blinking blue on every machine. Checked the "Extranonce" box and did a power cycle, and so far, so good. Will post again if I continue to get errors on MPH.

Update2: I've had the miners go down several times on MPH, always when switching to the Skein algo. Qubit/Myr-Groestl seem to switch fine. Once the miners are running on Skein, it seems stable, just switching over causes a problem. I'm wondering if this has something to do with the miner going from 10GH/s down to 5GH/s?

As there are a lot of users, that are complaining about devices that stop mining and so on, and i had some problems changing the IP-Adress of my devices with the Baikal Tool, because it just didnt work, i made a little Guide how to change IP-Address via SSH.

I can say, that all my 10 Miners are running stable and not even one of them stopped mining for several days. So maybe this problem was caused by wrong IP-settings or problems with DHCP. I dont know, but maybe it helps anyone.

As i dont know how to add a Attachment here in the Forum, you can download the Guide here:

bilder.lallax.de/staticIP.pdf

It is a pdf-document with a pictured step-by-step guide. Maybe it helps someone.

I know they use a custom sgminer, and there are some indications on the x10 filesystem that they had applied a sgminer "300mhz" patch (early images of the web interface showed the x10 running at 420mhz), but that doesn't mean that the 300mhz is locked in to sgminer.  It could be locked in to the device drivers... and the 300mhz reference to sgminer was merely adding support for this device at 300mhz, or was a fix for running at 300mhz, as opposed to code locking it in to 300mhz.

Depending on how their SD images were created (if it was a bit-for-bit clone of the original drive contents) you _might_ be able to "un-delete" some things from a fresh copy of their image. Although a long-shot for sure, I think that would be the best bet towards getting a copy of the source.

The binary is fairly large, so I don't think you will get very far with a decompiler, but I admit I don't have a ton of experience binary-hacking executables like this. I disassembled it, but I didn't see anything obvious that I could make out. There may be some technique that I'm not aware of...  

There also might be something that could be gained by reverse engineering, or hacking the hardware, but I'm not ready to tear my x10 apart yet.

In the end, the hashrate may be limited by the pi device being used.  It's under a lot of load when you are doing any algorithm at 10gh/s. While it's not responsible for creating the hashes, it is responsible for coordinating everything and delivering the hashes to the web at that high rate. It typically runs with a load average around 4.15. That means this poor little 4-core thing is already working over capacity all day every day. I would hesitate to add much more load and expect the system to stay stable.  I'm not sure how much effect over-clocking the "ASICs" (I've been told they are actually FPGA devices in the Baikals) would have on that, but I tend to think this is the limiting factor.  It certainly isn't limited by it's cooling system at 150 watts... or even 390.

Ihr unterhaltet euch in der falschen Sprache über das falsche Gerät. Ihr bringt dadurch andere User "durcheinander"..vor allem wenn ihr dann noch über andere Baikals redet.

 

Meint ihr nicht, dass da ein bisschen warm ist? Ich habe nachgefragt und laut Baikal sollten die temperaturen unter 40°C bleiben.
Meine laufen auf Quark mit 50% Fanspeed bei 31°C (14°C Umgebungstemperatur).

Don´t you think that´s a bit hot? Ask asked Baikal and they say that the recommended temperature is unter 40°C.
Mine are mining Quark with 50% fanspeed at 31°C (14°C ambient temperature).