Don't think more algorithms will come..... 
Almost batch 1 price
Almost batch 1 price
Yeah, sure... Almost batch 1 price and almost the same mining difficulty... Passing over till new algorithms announced.
Topic: Baikal Giant X10 - page 15. (Read 132901 times)
Yeah, sure... Almost batch 1 price and almost the same mining difficulty... Passing over till new algorithms announced.
They only take USD wires now? No Crypto?
X11/Quark/Quibt/Myriad-Groestl/Nist5/Skein/X11Gost/?(more algorithm will be added later)
Hash Rate:10GH/s(±5%)
Power supply:ATX Power（12V 6Pin connector * 6）
Interface:1 X Ethernet
Temp Operation：0 ~ 40 ℃
Dimension：312mm(L) x 125mm(W) x 130(H)
Weight：3800g
Price：1599
Announcement：On Sale
Purchase consulting:
Skype: baikalminer
E-mail: [email protected]
Don't think more algorithms will come.....
Almost batch 1 price
bbpqde1eKEU1mHmN5DZE23ctbwXpGzffkC
Baikal X10
Pool : http://poolovich.pro
Algo : QUARK
Coin : XUMA
Exchange : crypto-bridge.org
Here we dig with baical x10
Pool : http://poolovich.pro
Algo : QUARK
Coin : XUMA
Exchange : crypto-bridge.org
Here we dig with baical x10
can you put an example hoyo setup the baikal for minino is this pool? kind regards
Baikal X10
Pool : http://poolovich.pro
Algo : QUARK
Coin : XUMA
Exchange : crypto-bridge.org
Here we dig with baical x10
Pool : http://poolovich.pro
Algo : QUARK
Coin : XUMA
Exchange : crypto-bridge.org
Here we dig with baical x10
Hello friends , be careful to dont have a fix diff with var diff pool or multiport , it can cause terrible behavior to your miner
Well the miners do some crazy things with the LED‘s. I have some problem child but it doesn’t matter what they show if they work.
For the one who asked: I saw your temperature is 32 celcius or so, I have one miner which have 65 at the pi by 30 degrees at mining board.
I think some pi boards have heating problems. I will disassemble and put heatpipes on it.
Other miners I have 40-45 celcius for the pi‘s.
Maybe your one was getting 80 or so for long time, or humidity did not matched!
It have to be between 40-50% below 30% is dangerous as well, because electricity jumps over to other parts (sry for English).
I would suggest to try another pi.
At settings there is self recovery, amount is set at 1 but it got 3, maybe somebody help this. I tried it and atm looks good, but still testing.
For the one who asked: I saw your temperature is 32 celcius or so, I have one miner which have 65 at the pi by 30 degrees at mining board.
I think some pi boards have heating problems. I will disassemble and put heatpipes on it.
Other miners I have 40-45 celcius for the pi‘s.
Maybe your one was getting 80 or so for long time, or humidity did not matched!
It have to be between 40-50% below 30% is dangerous as well, because electricity jumps over to other parts (sry for English).
I would suggest to try another pi.
At settings there is self recovery, amount is set at 1 but it got 3, maybe somebody help this. I tried it and atm looks good, but still testing.
Hi,
Yesterday, on my X10, one of the blue LEDs went out, but the miner still hashes at the correct speed. I restarted, reset the pi and controller, and tried different SD card with no effect. Today, I spent a few hours online, looking for a reason/solution, but couldn't find any. When I went back to the miner, I found another blue LED has gone out (still hashing correctly). What could be causing this?
Yesterday, on my X10, one of the blue LEDs went out, but the miner still hashes at the correct speed. I restarted, reset the pi and controller, and tried different SD card with no effect. Today, I spent a few hours online, looking for a reason/solution, but couldn't find any. When I went back to the miner, I found another blue LED has gone out (still hashing correctly). What could be causing this?
I've seen this on quite a few of the X10's I've been working with. As long as the cards still occasionally get the flashing green LED (I believe 3 flashes/second when a share is found) it should still be mining. I've yet to find one that wasn't working fine when the blue LED was off or intermittent.
Definitely keep us up to date if you find otherwise.
My X10 is doing something really strange.
All lights are ok, but the 3rd BLKU (number 2) it is not accepting jobs, while the other 2 are working just fine. CPU Count looks fine, Hasharate on Baikals Page looks fine, but of course on Zpool is only 6 or 7 GHZ instead of about 10.
Tried reflashing 1.2 Pizero Image, no results, tried different algos, different pools, same thing.
Any suggestions?
I do attach somewhat of my screenshot:
Name ID Algo Temp Total Chips Clock Hashrate 5s Hashrate av Accepted Rejected HW Errors Utility Last Share Time Identify
BKLU 0 Quarkcoin 39 °C 64 300MHz 3.379 Gh/s 3.380 Gh/s 38183 173 [0.45%] 0 [0.00%] 412.9646 02:39:12
BKLU 1 Quarkcoin 38 °C 64 300MHz 3.379 Gh/s 3.380 Gh/s 38192 182 [0.47%] 0 [0.00%] 413.062 02:39:12
BKLU 2 Quarkcoin 37 °C 64 300MHz 3.379 Gh/s 3.380 Gh/s 27 0 [0.00%] 0 [0.00%] 0.292 02:10:14
3 devsTotals 10.14 Gh/s 10.14 Gh/s 76402 355 [0.46%] 0 [0.00%] 826.3186
All lights are ok, but the 3rd BLKU (number 2) it is not accepting jobs, while the other 2 are working just fine. CPU Count looks fine, Hasharate on Baikals Page looks fine, but of course on Zpool is only 6 or 7 GHZ instead of about 10.
Tried reflashing 1.2 Pizero Image, no results, tried different algos, different pools, same thing.
Any suggestions?
I do attach somewhat of my screenshot:
Name ID Algo Temp Total Chips Clock Hashrate 5s Hashrate av Accepted Rejected HW Errors Utility Last Share Time Identify
BKLU 0 Quarkcoin 39 °C 64 300MHz 3.379 Gh/s 3.380 Gh/s 38183 173 [0.45%] 0 [0.00%] 412.9646 02:39:12
BKLU 1 Quarkcoin 38 °C 64 300MHz 3.379 Gh/s 3.380 Gh/s 38192 182 [0.47%] 0 [0.00%] 413.062 02:39:12
BKLU 2 Quarkcoin 37 °C 64 300MHz 3.379 Gh/s 3.380 Gh/s 27 0 [0.00%] 0 [0.00%] 0.292 02:10:14
3 devsTotals 10.14 Gh/s 10.14 Gh/s 76402 355 [0.46%] 0 [0.00%] 826.3186
Try to set difficulty on the pool in the password, d=20.
Thanks for your reply. No difference in seeting diff......Its kind of weird that the "Last Share Time" in the status page keeps showing 20:00:00 while the other BLKU ID show the proper time.....look
Devices
Name ID Algo Temp Total Chips Clock Hashrate 5s Hashrate av Accepted Rejected HW Errors Utility Last Share Time Identify
BKLU 0 Quarkcoin 41 °C 64 300MHz 3.379 Gh/s 3.408 Gh/s 12 0 [0.00%] 0 [0.00%] 3.4171 14:25:04
BKLU 1 Quarkcoin 41 °C 64 300MHz 3.379 Gh/s 3.405 Gh/s 9 0 [0.00%] 0 [0.00%] 2.5628 14:24:49
BKLU 2 Quarkcoin 40 °C 64 300MHz 3.379 Gh/s 3.405 Gh/s 0 0 [%] 0 [%] 0 20:00:00
3 devsTotals 10.14 Gh/s 10.22 Gh/s 21 0 [0.00%] 0 [0.00%] 5.9799
Hi,
Yesterday, on my X10, one of the blue LEDs went out, but the miner still hashes at the correct speed. I restarted, reset the pi and controller, and tried different SD card with no effect. Today, I spent a few hours online, looking for a reason/solution, but couldn't find any. When I went back to the miner, I found another blue LED has gone out (still hashing correctly). What could be causing this?
Yesterday, on my X10, one of the blue LEDs went out, but the miner still hashes at the correct speed. I restarted, reset the pi and controller, and tried different SD card with no effect. Today, I spent a few hours online, looking for a reason/solution, but couldn't find any. When I went back to the miner, I found another blue LED has gone out (still hashing correctly). What could be causing this?
I encountered same problem few weeks ago. Sometimes one blue led light is gone, sometimes two, but never saw that all 3 were gone. Sometimes all 3 are shining
As longs as there is no diff in hashrate and chips are working as always I don't pay attention to it anymore. My X10 is doing something really strange.
All lights are ok, but the 3rd BLKU (number 2) it is not accepting jobs, while the other 2 are working just fine. CPU Count looks fine, Hasharate on Baikals Page looks fine, but of course on Zpool is only 6 or 7 GHZ instead of about 10.
Tried reflashing 1.2 Pizero Image, no results, tried different algos, different pools, same thing.
Any suggestions?
I do attach somewhat of my screenshot:
Name ID Algo Temp Total Chips Clock Hashrate 5s Hashrate av Accepted Rejected HW Errors Utility Last Share Time Identify
BKLU 0 Quarkcoin 39 °C 64 300MHz 3.379 Gh/s 3.380 Gh/s 38183 173 [0.45%] 0 [0.00%] 412.9646 02:39:12
BKLU 1 Quarkcoin 38 °C 64 300MHz 3.379 Gh/s 3.380 Gh/s 38192 182 [0.47%] 0 [0.00%] 413.062 02:39:12
BKLU 2 Quarkcoin 37 °C 64 300MHz 3.379 Gh/s 3.380 Gh/s 27 0 [0.00%] 0 [0.00%] 0.292 02:10:14
3 devsTotals 10.14 Gh/s 10.14 Gh/s 76402 355 [0.46%] 0 [0.00%] 826.3186
All lights are ok, but the 3rd BLKU (number 2) it is not accepting jobs, while the other 2 are working just fine. CPU Count looks fine, Hasharate on Baikals Page looks fine, but of course on Zpool is only 6 or 7 GHZ instead of about 10.
Tried reflashing 1.2 Pizero Image, no results, tried different algos, different pools, same thing.
Any suggestions?
I do attach somewhat of my screenshot:
Name ID Algo Temp Total Chips Clock Hashrate 5s Hashrate av Accepted Rejected HW Errors Utility Last Share Time Identify
BKLU 0 Quarkcoin 39 °C 64 300MHz 3.379 Gh/s 3.380 Gh/s 38183 173 [0.45%] 0 [0.00%] 412.9646 02:39:12
BKLU 1 Quarkcoin 38 °C 64 300MHz 3.379 Gh/s 3.380 Gh/s 38192 182 [0.47%] 0 [0.00%] 413.062 02:39:12
BKLU 2 Quarkcoin 37 °C 64 300MHz 3.379 Gh/s 3.380 Gh/s 27 0 [0.00%] 0 [0.00%] 0.292 02:10:14
3 devsTotals 10.14 Gh/s 10.14 Gh/s 76402 355 [0.46%] 0 [0.00%] 826.3186
Try to set difficulty on the pool in the password, d=20.
My X10 is doing something really strange.
All lights are ok, but the 3rd BLKU (number 2) it is not accepting jobs, while the other 2 are working just fine. CPU Count looks fine, Hasharate on Baikals Page looks fine, but of course on Zpool is only 6 or 7 GHZ instead of about 10.
Tried reflashing 1.2 Pizero Image, no results, tried different algos, different pools, same thing.
Any suggestions?
I do attach somewhat of my screenshot:
Name ID Algo Temp Total Chips Clock Hashrate 5s Hashrate av Accepted Rejected HW Errors Utility Last Share Time Identify
BKLU 0 Quarkcoin 39 °C 64 300MHz 3.379 Gh/s 3.380 Gh/s 38183 173 [0.45%] 0 [0.00%] 412.9646 02:39:12
BKLU 1 Quarkcoin 38 °C 64 300MHz 3.379 Gh/s 3.380 Gh/s 38192 182 [0.47%] 0 [0.00%] 413.062 02:39:12
BKLU 2 Quarkcoin 37 °C 64 300MHz 3.379 Gh/s 3.380 Gh/s 27 0 [0.00%] 0 [0.00%] 0.292 02:10:14
3 devsTotals 10.14 Gh/s 10.14 Gh/s 76402 355 [0.46%] 0 [0.00%] 826.3186
All lights are ok, but the 3rd BLKU (number 2) it is not accepting jobs, while the other 2 are working just fine. CPU Count looks fine, Hasharate on Baikals Page looks fine, but of course on Zpool is only 6 or 7 GHZ instead of about 10.
Tried reflashing 1.2 Pizero Image, no results, tried different algos, different pools, same thing.
Any suggestions?
I do attach somewhat of my screenshot:
Name ID Algo Temp Total Chips Clock Hashrate 5s Hashrate av Accepted Rejected HW Errors Utility Last Share Time Identify
BKLU 0 Quarkcoin 39 °C 64 300MHz 3.379 Gh/s 3.380 Gh/s 38183 173 [0.45%] 0 [0.00%] 412.9646 02:39:12
BKLU 1 Quarkcoin 38 °C 64 300MHz 3.379 Gh/s 3.380 Gh/s 38192 182 [0.47%] 0 [0.00%] 413.062 02:39:12
BKLU 2 Quarkcoin 37 °C 64 300MHz 3.379 Gh/s 3.380 Gh/s 27 0 [0.00%] 0 [0.00%] 0.292 02:10:14
3 devsTotals 10.14 Gh/s 10.14 Gh/s 76402 355 [0.46%] 0 [0.00%] 826.3186
Hi,
Yesterday, on my X10, one of the blue LEDs went out, but the miner still hashes at the correct speed. I restarted, reset the pi and controller, and tried different SD card with no effect. Today, I spent a few hours online, looking for a reason/solution, but couldn't find any. When I went back to the miner, I found another blue LED has gone out (still hashing correctly). What could be causing this?
Yesterday, on my X10, one of the blue LEDs went out, but the miner still hashes at the correct speed. I restarted, reset the pi and controller, and tried different SD card with no effect. Today, I spent a few hours online, looking for a reason/solution, but couldn't find any. When I went back to the miner, I found another blue LED has gone out (still hashing correctly). What could be causing this?
Anyone know something about the CE-Certificate debate?
It was on here some time ago and normally you cannot import things into EU without CE markings.
Will the next baikal products have it? As i read it’s a risk, if customs check it they don’t let it go through.
If there will be one day a new product and the MOQ is high (example 6) then probably customs will have a look and this maybe result in loosing a ton of money.
What do you think about that? Or anybody knows sth?
I think about buying a larger amount if there come new ones one day.
Thx (i‘m active in this thread nearly till start)
It was on here some time ago and normally you cannot import things into EU without CE markings.
Will the next baikal products have it? As i read it’s a risk, if customs check it they don’t let it go through.
If there will be one day a new product and the MOQ is high (example 6) then probably customs will have a look and this maybe result in loosing a ton of money.
What do you think about that? Or anybody knows sth?
I think about buying a larger amount if there come new ones one day.
Thx (i‘m active in this thread nearly till start)
They dont have a CE-Certificate and i am quite sure they wont have any in future. The chinese manufacturers of miners dont give a shit about there customers. They will promise you everything to make you buying. But if customs check the delivery and they wont let it through, you dont need to wait for any help from the manufacturers. From the time they have your money, it is completely your risk. Do not expect, they will refund only one dollar. This is a common problem from chinese suppliers, doesnt matter what they are selling. They know, you cant do anything to them. try to send a letter from an attorney or something like that to them. The only thing they will do about that is a big laugh.
Anyone know something about the CE-Certificate debate?
It was on here some time ago and normally you cannot import things into EU without CE markings.
Will the next baikal products have it? As i read it’s a risk, if customs check it they don’t let it go through.
If there will be one day a new product and the MOQ is high (example 6) then probably customs will have a look and this maybe result in loosing a ton of money.
What do you think about that? Or anybody knows sth?
I think about buying a larger amount if there come new ones one day.
Thx (i‘m active in this thread nearly till start)
It was on here some time ago and normally you cannot import things into EU without CE markings.
Will the next baikal products have it? As i read it’s a risk, if customs check it they don’t let it go through.
If there will be one day a new product and the MOQ is high (example 6) then probably customs will have a look and this maybe result in loosing a ton of money.
What do you think about that? Or anybody knows sth?
I think about buying a larger amount if there come new ones one day.
Thx (i‘m active in this thread nearly till start)
which is the maxium Celsius temperature (°C) that bailkal con works?
40C is what the site says but mines been running about 45C with 30% fan for pretty much its entire life and its been fine. The cooler the better though, sometimes the hashrate is affected for certain algos if the temp is too high. Ive mostly been on Nist5 which is lower power = lower temps.
which is the maxium Celsius temperature (°C) that bailkal con works?
Yeah. I did update a while ago and it was working just fine.
Untill yesterday. Unfortunately things do break...
Maybe i best start looking for a Pi Zero.
Hope you can solve your problem.
may be not big chance with that but do you have a fix IP for this miner (in DHCP?) try also to shut off your router or box. but yes is probably orange pi trouble Untill yesterday. Unfortunately things do break...
Maybe i best start looking for a Pi Zero.
Hope you can solve your problem.
Yeah. I did update a while ago and it was working just fine.
Untill yesterday. Unfortunately things do break...
Maybe i best start looking for a Pi Zero.
Hope you can solve your problem.
Untill yesterday. Unfortunately things do break...
Maybe i best start looking for a Pi Zero.
Hope you can solve your problem.
Jump to: