Bitcoin Forum
December 02, 2024, 01:53:28 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1] 2 »
1  Bitcoin / Hardware / Running a one Blade S9 vs. running a three blade S7? on: November 04, 2017, 02:04:58 PM
Good morning folks.
I'm still on my first cup of coffee, so I hope this isn't a very stupid question for the hardware pro's.

I am running two S7's now along with my S9's. I have another S9 with a new auto-tune controller but only one card in that S9 appears to be working correctly. I have spent hours trying to get another blade hashing in it (I thought I had two good blades). I have tried different freq's, different PSU's, different cables, etc. Nothing seems to get more than the one card running.

Now, my question is: Is it better to run the single S9 with only one working card than running an S7 with all cards working? Energy consumption-wise?

I don't feel bad about pushing the S7 to 725mHz. I would probably set the S9 to 600mHz during the first boot in the auto-tune controller.

I feel like I'm wasting hash with a good board sitting around gathering dust. Any thoughts are greatly appreciated!!

Thanks all! Have a great day! :-)
2  Other / Meta / Quick Question... Thread for testing? on: September 05, 2017, 03:58:15 AM
Is there a sub-forum somewhere on the board for test posting? I've looked but didn't see it if it exists.

The reason I ask is that I want to test some different style posting of the "Subject" and don't want to clutter up normal space.

Thanks for any reply!!

~wp
3  Bitcoin / Mining / Mixed Up Post - One Third Hardware, One Third Kano Pool, One Third Miscellaneous on: September 02, 2017, 04:41:11 AM
A little preface for explanation:

I began this post as a reply in the Hardware thread. Along the way, I got lost and forgot that I was in the hardware thread and began writing as if I was in the Kano Pool thread. Mixed in with all of that is a smorgasbord of other info.
After I started to finish and submit the post I realized I was all mixed up! LOL Grin

So instead of deleting all of my "wonderful" post, I decided to post it here. Somewhat in the middle of all those topics. Anyway, I didn't want to delete it after spending so much time writing itl

Goodnight, folks. I'm beat! Sleep well! Smiley Smiley Smiley Smiley Smiley Smiley Smiley

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Thanks for reminding me... I have a dead s9 B11 board I gotta sent to CO for repair. Together with a Gimpy R4 that's over 8THs down...
I keep putting it off/forgetting...

Whoda thunk when I started in Feb 2014 with 2 lil' 10GHs BLF Jalas I'd ever say that about 8THs but now is still just blip in the total mining away for me. Dumbfounding that after the first 500GHs worth of s1's (and $4k for a long-delayed 1TH rig from AMT) ALL expansion and upgrades were paid from farm income (with a tidy bit left over Wink ) !

That is most definitely great if all of your expansion and upgrades to your farm is the result of mining profits!!  Grin
Wish I could have followed that path myself. But unfortunately I have had to sell my coins on a pretty regular schedule in order to pay bills and deal with unexpected financial requirements.

I have been very lucky in the past year or so that with my meager twice-monthly paycheck along with BTC profits, I've been able to take care of the household bills, credit card balances, and the electric bills! If I had only been able to pay those damn things off without touching my BTC, according to my Mining Rewards page, mining on Kano only, I have earned a Total: 49.55635393 BTC! That's a very sweet earning of coins if I were only able to keep them all. One of the days I'll be able to start accumulating again!  Smiley

Miners and hardware do definitely "reproduce" or "procreate". LOL
I started out with a single S7 which morphed into a total of three which begot an S9 which morphed into five S9's.  However, after illness and contagion dangled it's dark, ugly, clouds over my mining room, I am down to two fully functioning S7's and three and two thirds S9's.

What I know is that I have one S9, 600Mhz controller card (the black card) that needs to be repaired or most likely replaced. Two S9 boards (One 550Mhz and the other 600Mhz) that need replacing or repaired. And finally, a lowly S7, 700Mhz board that needs repair or replaced.

I'm going to have to do this a little at a time to stretch out the financials. First piece will probably be the S9 controller. I "MAY" send the whole S9 back to Bitmain Warranty to repair or replace the black controller card and the S9 -600Mhz board. If the price is going to be too steep, I'll just have them fix/replace the black controller card and I will run two of three cards only. Or perhaps I will just send off to Bitmain Warranty and purchase the one-piece controller card that replaces the S9 two-piece and just run two of three boards.

May or may not get the S7 hash board fixed. Might just be cheaper to buy another S7 if I can get it real cheap. OR..., hold off on doing that and just save up for another S9.

With the coin price where it is, I'm very happy to be able to run my old S7's. Can't beat them with current parameters. Each of the S7's running at stock 700Mhz is projected to earn a little over $200 per month. With the electric cost of the S7 averaging about ~$50 per month, a nice return of ~$150 each makes me smile!!

So, I'll take it step by step starting with grabbing the one-piece BB Black S9 controller from BM Warranty. That will allow me to get one more fully functioning S9 back into the battle.
After that, I'll sit back with a cold beverage and take my time figuring out what to do next!  Grin

I really needed to write this out like this so I could get all the jumbled thoughts out of my head and into some coherent, workable plan of action where I can check things off my list and see my progress. A flow chart would work great for me! LOL Shocked Definitely getting mentally disorganized in my older-years. Not that I have ever been extremely organized in any ways!! Tongue

Our pool had some fairly sucky parts of August which made August overall pretty sucky. But being only 10 blocks behind at the end of the month was actually better than I expected as it was occurring to us, day by day.
It seemed like it would be worse as it was happening. LOL

But September has started off pretty well. (Just noticed in my Awesome Miner application that I forgot to switch my pool back to Kano after I bumped one of my S9's frequency from 575-> 600Mhz. So Slush just got 1 hour and 49 minutes of hash that was intended for my Kano account. Oh well, at least it wasn't antpoo! The only reason I noticed it before I went to bed and left it pointing there overnight was because I too a quick glance at my shift graph and saw a BIG dip down the graph. )

Well, as I was starting to say, September is looking like it is off to a good start. That VERY, RED BLOCKS Stats page is looking much too red and black for my liking. A lot moreGREEN is what I would like to see creeping back onto that page before the end of this long, Labor Day weekend holiday. I'd like to see two or three blocks for each of the next four days!  Cheesy That certainly doesn't seem like too much to ask or want!  Cool

I have to work a half day tomorrow at my IT job and then I don't have to work again until next Wednesday. Not too shabby except I'm not getting paid for my time off. I suppose tomorrow afternoon it will be time to watch some football, then I will take a good S9 board out one otherwise dead miner and put it in another S9 to get a fully functioning, three-board miner.

Well, I intended to post about getting my mining hardware straightened out tomorrow by swapping out a good board for a bad one in another miner. Once again my wandering mind (along with a few Corona Extra Cerveza's Tongue) have turned a short post into the beginnings of a small short-story. I apologize about taking up forum space with my roaming thoughts. I hope it wasn't too boring.

Oh, yeah, I meant to originally reply to @NotFuzzyWarm about your hardware issue. I forgot what I was going to say regarding the hardware. But I do know I should remind you about "dead s9 B11 board I gotta sent to CO for repair. Together with a Gimpy R4 that's over 8THs down...  I keep putting it off/forgetting..."
Maybe that'll be of some help! Cheesy Cheesy

Also, let's hope that in the next few days we will know better where that next hurricane (Irma) is going to end up. I hope like hell it won't hit the US, especially the gulf coast states. I think they have had enough for now! I also need to fill my gas tank up. Gas prices have gone from $2.19 to $2.59 in the last two days.

Okay, enough! Goodnight Ladies and Gents, Boys and Girls! Sleep well and may the BLOCKS roll in overnight as the fog and clouds mingle and flow upwards filling the valleys to the peaks.  Grin Grin Grin Grin

COMEONBLOCKSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!  Cheesy Grin Cheesy Grin Cheesy Grin Cool

Happy mining ya'll!!   Cheesy

Mine On!!!  Cool Cool Cool Cool Cool Cool Cool
4  Bitcoin / Hardware / Lost Another S9 Board... ^%#@$@!^&*:-( on: September 01, 2017, 09:09:01 PM
So yeah, the subject says it all.  Angry

I'm gonna have to cannibalize a board from another S9 whose controller has gone bad.

Here's my question:

The S9 that lost the board is an older S9 rated at 550 Mhz. I'm gonna pull the 550 bad board and replace it with a board from a 600 Mhz S9.

I'm almost 99.9% sure that putting a faster rated board (600mhz) into a 550Mhz miner will not cause any problems. I am still going to only run it at 550.

Any of you "pros" see any problems? I almost feel that it's a stupid question... but better safe than sorry!  Roll Eyes

Thanks for the input!
~wp
5  Bitcoin / Hardware / Just a bit of unsolicited Hardware Advice! :-) on: August 27, 2017, 01:49:39 AM
Good Evening Ladies & Gents, Boys & Girls (or whatever part of the day it is for you),  Grin

Having built and rebuilt computers and other electronics for more than the last two decades, I know this inside and out and have also learned it the hard way!  Huh

Do NOT get overly confident when putting hardware together and go on auto-pilot (with a slight beer-buzz). It can easily bite you in the butt and make you feel like the dumb-ass you are!  Shocked Shocked Shocked Shocked

So I took my three S7's apart to brush out the dust and also use an electronics duster/vacuum to get all of the crap, dust, cat hair, etc. from the nooks and crannies.

After putting them back together all nice and clean, I decided I would fire them up and run them along with the S9's for the weekend. After all, with the coin price what it is, the S7's should theoretically pull in ~$6.00 a day. ~$18.00 extra a day is always nice.  Cool

As the S7's were starting up, I monitored them in Awesome Miner.... Man, those boards were getting hot!!! Too hot!  Angry Time to shut them down and investigate...

Can you guess?? I knew what I had done right off the bat. I put one of the fans in each of the three S7's in backwards.  Sad Sad Sad  Cry Cry Cry

What a dumb-ass I am.

So an hour later, all is as it should be. Definitely time for another beer! LOL  Tongue Tongue Tongue Tongue Tongue Tongue Cheers! Wink

~Goodnight!
6  Bitcoin / Hardware / Older S9 Controller Appears to be Failing. Thoughts? Thanks. on: August 14, 2017, 12:17:16 AM
Hey folks,

I've got an older S9 - might have been the first one I got. It has been running like a champ for a long time. Always running cool and with very few HW errors.

Anyway, I noticed today it suddenly popped up in Awesome Miner as being disconnected. So I unplugged and re-plugged the power. It came up again all boards hashing normally with good speed, temp and all-around good numbers on all boards.

But after 15-20 minutes it stopped hashing again. Power cycle brought it back again but after 15 minutes or so, it stopped hashing again.

Since the boards seem to be running OK, I'm guessing the controller is dying.

I have other S9's I could swap out the controller with and test. But I REALLY hate to have another miner off line now as the coin price continues to rise. But to pinpoint the problem, I guess I will do that tomorrow.

Any thoughts from the hardware pros appreciated. Thanks!

Edit: I'm not looking for a solution or fix if it is the controller. All I'm asking is if the symptoms match a failing controller. Thanks. :-)

EDIT2: I just powered up the misbehaving S9 to see if a good nights rest would help it out. LOL
No such luck. Stopped hashing completely in about 5 minutes. Grrrr. :-(

Time to swap out some hardware after a little more coffee.
7  Other / Off-topic / The TRUTH about the Eligius Mining Pool on: May 07, 2017, 04:06:16 PM
I had posted this in the Eligius Mining Pool thread earlier this morning to help calm fears that the Eligius Pool had stopped making payouts to its miners. Unfortunately someone with some kind of authority has deleted this post from the pool thread.
Perhaps this is a better location for the post.  Tongue

i am courious about this new eligius feature..seems interesting
What feature would that be, invisible payouts? Some of ya'll have some amazing faith.   Cool

But as North Korea has confirmed, The Eligius Bitcoin Mining Pool continues to make payouts on a regular, daily basis to its more than 6.3 million BTC miners. These payouts, the Korean Central News Agency reported, are on average 323.9% of Pay Per Share (PPS) norms.

The News Agency went on to say that with the addition of the newest Bitcoin mining farm opened on April 1, 2017, pictured below, North Korea now provides over 800,000,000 petahashes per second of the worlds BTC mining power.



The Korean Central News Agency was also the first to report the breaking, and verified, news that the North Korean peninsula is home to the 2,504 remaining unicorns on Earth.

North Korea's beloved president, Kim Jong-un, has easily become an expert in the taming and riding of these magical creatures. President Jong-Un is seen below preparing for a morning ride on one of his favorite unicorns, Cup Cake.



https://www.usnews.com/news/articles/2012/11/30/north-korea-says-its-found-a-unicorn-lair

-
8  Bitcoin / Hardware / "Lucky Drawing (Repair Ticket) $50 Refund" from Bitmain Warranty? :) on: March 18, 2017, 01:38:08 AM
I sent an S9 hash board in for repair with Bitmain Warranty in Colorado. Yesterday I got an email that it had been repaired and a bill for $175 + $25 for shipping. It was a very quick repair. So I paid right away with PayPal.

This morning I got an email from PayPal saying Bitmain Warranty had sent a $50 refund. The note from merchant states:
"Lucky Drawing (Repair Ticket) $50 Refund"

I have never heard of this, but I'm certainly not complaining at all! That's fantastic, with total repair costs at $150!! Smiley

Has anyone else had a "Lucky Drawing" repair ticket?

Thank you, Bitmain Warranty! Can't wait to get my hash board back and get my hash rate back up!  Grin Grin Grin
9  Bitcoin / Hardware / S9 Board Repair in Colorado? on: March 11, 2017, 08:06:49 PM
Does anyone know the approximate cost of having an S9 hash board repaired in CO?

Thanks for any replies!  Cheesy
10  Bitcoin / Mining support / All of my S9's stopped hashing overnight at same time! Please take a look! on: February 24, 2017, 12:03:31 PM
Just woke up to find all S9's with zero hash. Tried rebooting, reset router and a few other things. I've got them unplugged now and have to go to work. Sad

Can anyone here decipher the kernel log and try to tell me what's going on? Thank you very much!

Kernel Log:

Booting Linux on physical CPU 0x0
Initializing cgroup subsys cpuset
Linux version 3.10.31-ltsi-00003-gcf03eb9 (lzq@armdev01) (gcc version 4.7.3 20121106 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2012.11-20121123 - Linaro GCC 2012.11) ) #81 SMP Mon Apr 25 11:20:36 CST 2016
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Altera SOCFPGA, model: Altera SOCFPGA Cyclone V
Memory policy: ECC disabled, Data cache writealloc
On node 0 totalpages: 258048
free_area_init_node: node 0, pgdat 806e5cc0, node_mem_map 8072a000
  Normal zone: 2016 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 258048 pages, LIFO batch:31
PERCPU: Embedded 8 pages/cpu @80f17000 s11200 r8192 d13376 u32768
pcpu-alloc: s11200 r8192 d13376 u32768 alloc=8*4096
pcpu-alloc:
  • 0
  • 1
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 256032
Kernel command line: mem=1008M console=ttyS0,115200 root=/dev/mtdblock3 rw rootfstype=jffs2
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1008MB = 1008MB total
Memory: 1015844k/1015844k available, 16348k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xbf800000 - 0xff000000   (1016 MB)
    lowmem  : 0x80000000 - 0xbf000000   (1008 MB)
    modules : 0x7f000000 - 0x80000000   (  16 MB)
      .text : 0x80008000 - 0x8065a930   (6475 kB)
      .init : 0x8065b000 - 0x806adbc0   ( 331 kB)
      .data : 0x806ae000 - 0x806e9990   ( 239 kB)
       .bss : 0x806e9990 - 0x80729384   ( 255 kB)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:16 nr_irqs:16 16
sched_clock: 32 bits at 100MHz, resolution 10ns, wraps every 42949ms
Console: colour dummy device 80x30
Calibrating delay loop... 1196.85 BogoMIPS (lpj=5984256)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
ftrace: allocating 17687 entries in 52 pages
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x804ab220 - 0x804ab278
CPU1: failed to come online
Brought up 1 CPUs
SMP: Total of 1 processors activated (1196.85 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
NET: Registered protocol family 16
fpga bridge driver
DMA: preallocated 256 KiB pool for atomic coherent allocations
L310 cache controller enabled
l2x0: 8 ways, CACHE_ID 0x410030c9, AUX_CTRL 0x32460000, Cache size: 524288 B
syscon fffef000.l2-cache: regmap [mem 0xfffef000-0xfffeffff] registered
syscon ffd05000.rstmgr: regmap [mem 0xffd05000-0xffd05fff] registered
syscon ffc25000.sdrctl: regmap [mem 0xffc25000-0xffc25fff] registered
syscon ff800000.l3regs: regmap [mem 0xff800000-0xff800fff] registered
syscon ffd08000.sysmgr: regmap [mem 0xffd08000-0xffd0bfff] registered
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
altera_hps2fpga_bridge fpgabridge.2: fpga bridge [hps2fpga] registered as device hps2fpga
altera_hps2fpga_bridge fpgabridge.2: init-val not specified
altera_hps2fpga_bridge fpgabridge.3: fpga bridge [lshps2fpga] registered as device lwhps2fpga
altera_hps2fpga_bridge fpgabridge.3: init-val not specified
altera_hps2fpga_bridge fpgabridge.4: fpga bridge [fpga2hps] registered as device fpga2hps
altera_hps2fpga_bridge fpgabridge.4: init-val not specified
bio: create slab <bio-0> at 0
FPGA Mangager framework driver
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
Switching to clocksource timer0
NET: Registered protocol family 2
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP: reno registered
UDP hash table entries: 512 (order: 2, 16384 bytes)
UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available
arm-pmu arm-pmu: PMU:CTI successfully enabled for 1 cores
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
NTFS driver 2.1.30 [Flags: R/W].
jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 1984
io scheduler noop registered (default)
Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
ffc02000.serial0: ttyS0 at MMIO 0xffc02000 (irq = 194) is a 16550A
console [ttyS0] enabled
altera_fpga_manager ff706000.fpgamgr: fpga manager [Altera FPGA Manager] registered as minor 0
brd: module loaded
denali-nand-dt ff900000.nand: Dump timing register values:acc_clks: 4, re_2_we: 20, re_2_re: 20
we_2_re: 12, addr_2_data: 14, rdwr_en_lo_cnt: 2
rdwr_en_hi_cnt: 2, cs_setup_cnt: 2
ONFI param page 0 valid
ONFI flash detected
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron MT29F2G08ABAEAWP), 256MiB, page size: 2048, OOB size: 64
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
5 ofpart partitions found on MTD device denali-nand
Creating 5 MTD partitions on "denali-nand":
0x000000000000-0x000001000000 : "NAND Flash Boot Area 16MB"
0x000001000000-0x000002000000 : "NAND Flash Boot Area backup1 16MB"
0x000002000000-0x000003000000 : "NAND Flash Boot Area backup2 16MB"
0x000003000000-0x00000b000000 : "NAND Flash jffs2 Root Filesystem 128MB"
0x00000b000000-0x000010000000 : "NAND Flash jffs2 Root Filesystem 80MB"
dw_spi_mmio fff00000.spi: master is unqueued, this is deprecated
CAN device driver interface
c_can_platform ffc00000.d_can: invalid resource
c_can_platform ffc00000.d_can: control memory is not used for raminit
c_can_platform ffc00000.d_can: c_can_platform device registered (regs=bf8dc000, irq=163)
stmmac_hw_init: 1000M
stmmac - user ID: 0x10, Synopsys ID: 0x37
 Ring mode enabled
 DMA HW capability register supported
 Enhanced/Alternate descriptors
   Enabled extended descriptors
 RX Checksum Offload Engine supported (type 2)
 TX Checksum insertion supported
 Enable RX Mitigation via HW Watchdog Timer
libphy: stmmac: probed
eth0: PHY ID 0007c0f1 at 0 IRQ POLL (stmmac-0:00) active
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
Synopsys Designware Multimedia Card Interface Driver
dwmmc_socfpga ff704000.dwmmc0: couldn't determine pwr-en, assuming pwr-en = 0
dwmmc_socfpga ff704000.dwmmc0: Using internal DMA controller.
dwmmc_socfpga ff704000.dwmmc0: Version ID is 240a
dwmmc_socfpga ff704000.dwmmc0: DW MMC controller at irq 171, 32 bit host data width, 1024 deep fifo
mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
dwmmc_socfpga ff704000.dwmmc0: 1 slots initialized
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
oprofile: using arm/armv7-ca9
TCP: cubic registered
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 15
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
8021q: 802.1Q VLAN Support v1.8
Key type dns_resolver registered
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
ThumbEE CPU extension supported.
Registering SWP/SWPB emulation handler
mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84)
mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125)
mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250)
mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84)
mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125)
mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250)
VFS: Mounted root (jffs2 filesystem) on device 31:3.
devtmpfs: mounted
Freeing unused kernel memory: 328K (8065b000 - 806ad000)
eth0: device MAC address 6e:3b:29:ad:a3:1c
init phy ok
PHY DMA init OK
eth0: device MAC address 46:84:fb:cd:15:18
init phy ok
PHY DMA init OK
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
libphy: stmmac-0:00 - Link is Up - 100/Full
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
Original value in RESET_MANAGER_BASE_ADDR + BRGMODRST_ADDR is 0x0
request_mem_region OK!
AXI fpga dev virtual address is 0xbf942000
*base_vir_addr = 0xc504
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xc0000000
eth0: device MAC address 46:84:fb:cd:15:18
init phy ok
PHY DMA init OK
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
eth0: device MAC address 46:84:fb:cd:15:18
init phy ok
PHY DMA init OK
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
libphy: stmmac-0:00 - Link is Up - 100/Full
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
jffs2: notice: (280) check_node_data: wrong data CRC in data node at 0x07128fb4: read 0x3c88ca34, calculated 0x9ca1d6fa.
libphy: stmmac-0:00 - Link is Down
libphy: stmmac-0:00 - Link is Up - 100/Full
prepare send works thread on chain[0]
prepare send works thread on chain[1]
prepare send works thread on chain[2]
prepare send works thread on chain[3]
prepare send works thread on chain[4]
prepare send works thread on chain[5]
prepare send works thread on chain[6]
prepare send works thread on chain[7]
prepare send works thread on chain[8]
prepare send works thread on chain[9]
prepare send works thread on chain[10]
prepare send works thread on chain[11]
prepare send works thread on chain[12]
prepare send works thread on chain[13]
prepare send works thread on chain[14]
prepare send works thread on chain[15]
Find hashboard on Chain[0]
Find hashboard on Chain[2]
Find hashboard on Chain[3]
Check chain[0] PIC fw version=0x02
Check chain[2] PIC fw version=0x02
Check chain[3] PIC fw version=0x02
chain[0] has no freq in PIC! Will use default freq=550 and jump over...
Check chain[0] PIC fw version=0x02
chain[2] has no freq in PIC! Will use default freq=550 and jump over...
Check chain[2] PIC fw version=0x02
chain[3] has no freq in PIC! Will use default freq=550 and jump over...
Check chain[3] PIC fw version=0x02
get PIC voltage=6 on chain[0], value=940
get PIC voltage=6 on chain[2], value=940
get PIC voltage=6 on chain[3], value=940
chain[0] temp offset record: 62,-72,0,0,0,0,0,0
chain[2] temp offset record: 62,-68,0,0,0,0,0,0
chain[3] temp offset record: 62,-76,0,0,0,0,0,0
check PIC voltage=940 on chain[0]
check PIC voltage=940 on chain[2]
check PIC voltage=940 on chain[3]
set command mode to VIL

singleBoardTest: AsicType = 1387

singleBoardTest: asicNum = 64

singleBoardTest: real AsicNum = 63

--- check asic number
set_baud=0, ought to be 1
The min freq=700
set real timeout 52, need sleep=379392
search freq for 1 times, completed chain = 3, total chain num = 3
disable_pic_dac on chain[0]
disable_pic_dac on chain[2]
disable_pic_dac on chain[3]
restart Miner chance num=2
waiting for send_func to exit of chain[0]
waiting for send_func to exit of chain[1]
waiting for send_func to exit of chain[2]
waiting for send_func to exit of chain[3]
waiting for send_func to exit of chain[4]
waiting for send_func to exit of chain[5]
waiting for send_func to exit of chain[6]
waiting for send_func to exit of chain[7]
waiting for send_func to exit of chain[8]
waiting for send_func to exit of chain[9]
waiting for send_func to exit of chain[10]
waiting for send_func to exit of chain[11]
waiting for send_func to exit of chain[12]
waiting for send_func to exit of chain[13]
waiting for send_func to exit of chain[14]
waiting for send_func to exit of chain[15]
waiting for receive_func to exit!
waiting for pic heart to exit!
Start bmminer ...
This is C5 board.
Check chain[0] PIC fw version=0x02
Check chain[2] PIC fw version=0x02
Check chain[3] PIC fw version=0x02
Chain[J1] will use highest voltage=940 [6] to open core
Chain[J3] will use highest voltage=940 [6] to open core
Chain[J4] will use highest voltage=940 [6] to open core
Chain[J1] orignal chain_voltage=6 value=940
Chain[J3] orignal chain_voltage=6 value=940
Chain[J4] orignal chain_voltage=6 value=940
Chain[J1] has 63 asic
Chain[J3] has 63 asic
Chain[J4] has 63 asic
Chain[J1] has no freq in PIC, set default freq=550M
Chain[J1] has no core num in PIC
Chain[J3] has no freq in PIC, set default freq=550M
Chain[J3] has no core num in PIC
Chain[J4] has no freq in PIC, set default freq=550M
Chain[J4] has no core num in PIC
read PIC voltage=940 on chain[0]
Chain:0 chipnum=63
Chain[J1] voltage added=0.0V
Chain[J1] [minerMAC: 46:84:fb:cd:15:18 hashMAC: 00:00:00:00:00:00]
Chain:0 temp offset=0
Chain:0 base freq=100
Asic[ 0]:550
Asic[ 1]:550 Asic[ 2]:550 Asic[ 3]:550 Asic[ 4]:550 Asic[ 5]:550 Asic[ 6]:550 Asic[ 7]:550 Asic[ 8]:550
Asic[ 9]:550 Asic[10]:550 Asic[11]:550 Asic[12]:550 Asic[13]:550 Asic[14]:550 Asic[15]:550 Asic[16]:550
Asic[17]:550 Asic[18]:550 Asic[19]:550 Asic[20]:550 Asic[21]:550 Asic[22]:550 Asic[23]:550 Asic[24]:550
Asic[25]:550 Asic[26]:550 Asic[27]:550 Asic[28]:550 Asic[29]:550 Asic[30]:550 Asic[31]:550 Asic[32]:550
Asic[33]:550 Asic[34]:550 Asic[35]:550 Asic[36]:550 Asic[37]:550 Asic[38]:550 Asic[39]:550 Asic[40]:550
Asic[41]:550 Asic[42]:550 Asic[43]:550 Asic[44]:550 Asic[45]:550 Asic[46]:550 Asic[47]:550 Asic[48]:550
Asic[49]:550 Asic[50]:550 Asic[51]:550 Asic[52]:550 Asic[53]:550 Asic[54]:550 Asic[55]:550 Asic[56]:550
Asic[57]:550 Asic[58]:550 Asic[59]:550 Asic[60]:550 Asic[61]:550 Asic[62]:550
Chain:0 max freq=550
Chain:0 min freq=550

read PIC voltage=940 on chain[2]
Chain:2 chipnum=63
Chain[J3] voltage added=0.0V
Chain[J3] [minerMAC: 46:84:fb:cd:15:18 hashMAC: 00:00:00:00:00:00]
Chain:2 temp offset=0
Chain:2 base freq=100
Asic[ 0]:550
Asic[ 1]:550 Asic[ 2]:550 Asic[ 3]:550 Asic[ 4]:550 Asic[ 5]:550 Asic[ 6]:550 Asic[ 7]:550 Asic[ 8]:550
Asic[ 9]:550 Asic[10]:550 Asic[11]:550 Asic[12]:550 Asic[13]:550 Asic[14]:550 Asic[15]:550 Asic[16]:550
Asic[17]:550 Asic[18]:550 Asic[19]:550 Asic[20]:550 Asic[21]:550 Asic[22]:550 Asic[23]:550 Asic[24]:550
Asic[25]:550 Asic[26]:550 Asic[27]:550 Asic[28]:550 Asic[29]:550 Asic[30]:550 Asic[31]:550 Asic[32]:550
Asic[33]:550 Asic[34]:550 Asic[35]:550 Asic[36]:550 Asic[37]:550 Asic[38]:550 Asic[39]:550 Asic[40]:550
Asic[41]:550 Asic[42]:550 Asic[43]:550 Asic[44]:550 Asic[45]:550 Asic[46]:550 Asic[47]:550 Asic[48]:550
Asic[49]:550 Asic[50]:550 Asic[51]:550 Asic[52]:550 Asic[53]:550 Asic[54]:550 Asic[55]:550 Asic[56]:550
Asic[57]:550 Asic[58]:550 Asic[59]:550 Asic[60]:550 Asic[61]:550 Asic[62]:550
Chain:2 max freq=550
Chain:2 min freq=550

read PIC voltage=940 on chain[3]
Chain:3 chipnum=63
Chain[J4] voltage added=0.0V
Chain[J4] [minerMAC: 46:84:fb:cd:15:18 hashMAC: 00:00:00:00:00:00]
Chain:3 temp offset=0
Chain:3 base freq=100
Asic[ 0]:550
Asic[ 1]:550 Asic[ 2]:550 Asic[ 3]:550 Asic[ 4]:550 Asic[ 5]:550 Asic[ 6]:550 Asic[ 7]:550 Asic[ 8]:550
Asic[ 9]:550 Asic[10]:550 Asic[11]:550 Asic[12]:550 Asic[13]:550 Asic[14]:550 Asic[15]:550 Asic[16]:550
Asic[17]:550 Asic[18]:550 Asic[19]:550 Asic[20]:550 Asic[21]:550 Asic[22]:550 Asic[23]:550 Asic[24]:550
Asic[25]:550 Asic[26]:550 Asic[27]:550 Asic[28]:550 Asic[29]:550 Asic[30]:550 Asic[31]:550 Asic[32]:550
Asic[33]:550 Asic[34]:550 Asic[35]:550 Asic[36]:550 Asic[37]:550 Asic[38]:550 Asic[39]:550 Asic[40]:550
Asic[41]:550 Asic[42]:550 Asic[43]:550 Asic[44]:550 Asic[45]:550 Asic[46]:550 Asic[47]:550 Asic[48]:550
Asic[49]:550 Asic[50]:550 Asic[51]:550 Asic[52]:550 Asic[53]:550 Asic[54]:550 Asic[55]:550 Asic[56]:550
Asic[57]:550 Asic[58]:550 Asic[59]:550 Asic[60]:550 Asic[61]:550 Asic[62]:550
Chain:3 max freq=550
Chain:3 min freq=550


Miner fix freq ...
read PIC voltage=940 on chain[0]
Chain:0 chipnum=63
Chain[J1] voltage added=0.0V
Chain[J1] [minerMAC: 46:84:fb:cd:15:18 hashMAC: 00:00:00:00:00:00]
Chain:0 temp offset=0
Chain:0 base freq=100
Asic[ 0]:550
Asic[ 1]:550 Asic[ 2]:550 Asic[ 3]:550 Asic[ 4]:550 Asic[ 5]:550 Asic[ 6]:550 Asic[ 7]:550 Asic[ 8]:550
Asic[ 9]:550 Asic[10]:550 Asic[11]:550 Asic[12]:550 Asic[13]:550 Asic[14]:550 Asic[15]:550 Asic[16]:550
Asic[17]:550 Asic[18]:550 Asic[19]:550 Asic[20]:550 Asic[21]:550 Asic[22]:550 Asic[23]:550 Asic[24]:550
Asic[25]:550 Asic[26]:550 Asic[27]:550 Asic[28]:550 Asic[29]:550 Asic[30]:550 Asic[31]:550 Asic[32]:550
Asic[33]:550 Asic[34]:550 Asic[35]:550 Asic[36]:550 Asic[37]:550 Asic[38]:550 Asic[39]:550 Asic[40]:550
Asic[41]:550 Asic[42]:550 Asic[43]:550 Asic[44]:550 Asic[45]:550 Asic[46]:550 Asic[47]:550 Asic[48]:550
Asic[49]:550 Asic[50]:550 Asic[51]:550 Asic[52]:550 Asic[53]:550 Asic[54]:550 Asic[55]:550 Asic[56]:550
Asic[57]:550 Asic[58]:550 Asic[59]:550 Asic[60]:550 Asic[61]:550 Asic[62]:550
Chain:0 max freq=550
Chain:0 min freq=550

read PIC voltage=940 on chain[2]
Chain:2 chipnum=63
Chain[J3] voltage added=0.0V
Chain[J3] [minerMAC: 46:84:fb:cd:15:18 hashMAC: 00:00:00:00:00:00]
Chain:2 temp offset=0
Chain:2 base freq=100
Asic[ 0]:550
Asic[ 1]:550 Asic[ 2]:550 Asic[ 3]:550 Asic[ 4]:550 Asic[ 5]:550 Asic[ 6]:550 Asic[ 7]:550 Asic[ 8]:550
Asic[ 9]:550 Asic[10]:550 Asic[11]:550 Asic[12]:550 Asic[13]:550 Asic[14]:550 Asic[15]:550 Asic[16]:550
Asic[17]:550 Asic[18]:550 Asic[19]:550 Asic[20]:550 Asic[21]:550 Asic[22]:550 Asic[23]:550 Asic[24]:550
Asic[25]:550 Asic[26]:550 Asic[27]:550 Asic[28]:550 Asic[29]:550 Asic[30]:550 Asic[31]:550 Asic[32]:550
Asic[33]:550 Asic[34]:550 Asic[35]:550 Asic[36]:550 Asic[37]:550 Asic[38]:550 Asic[39]:550 Asic[40]:550
Asic[41]:550 Asic[42]:550 Asic[43]:550 Asic[44]:550 Asic[45]:550 Asic[46]:550 Asic[47]:550 Asic[48]:550
Asic[49]:550 Asic[50]:550 Asic[51]:550 Asic[52]:550 Asic[53]:550 Asic[54]:550 Asic[55]:550 Asic[56]:550
Asic[57]:550 Asic[58]:550 Asic[59]:550 Asic[60]:550 Asic[61]:550 Asic[62]:550
Chain:2 max freq=550
Chain:2 min freq=550

read PIC voltage=940 on chain[3]
Chain:3 chipnum=63
Chain[J4] voltage added=0.0V
Chain[J4] [minerMAC: 46:84:fb:cd:15:18 hashMAC: 00:00:00:00:00:00]
Chain:3 temp offset=0
Chain:3 base freq=100
Asic[ 0]:550
Asic[ 1]:550 Asic[ 2]:550 Asic[ 3]:550 Asic[ 4]:550 Asic[ 5]:550 Asic[ 6]:550 Asic[ 7]:550 Asic[ 8]:550
Asic[ 9]:550 Asic[10]:550 Asic[11]:550 Asic[12]:550 Asic[13]:550 Asic[14]:550 Asic[15]:550 Asic[16]:550
Asic[17]:550 Asic[18]:550 Asic[19]:550 Asic[20]:550 Asic[21]:550 Asic[22]:550 Asic[23]:550 Asic[24]:550
Asic[25]:550 Asic[26]:550 Asic[27]:550 Asic[28]:550 Asic[29]:550 Asic[30]:550 Asic[31]:550 Asic[32]:550
Asic[33]:550 Asic[34]:550 Asic[35]:550 Asic[36]:550 Asic[37]:550 Asic[38]:550 Asic[39]:550 Asic[40]:550
Asic[41]:550 Asic[42]:550 Asic[43]:550 Asic[44]:550 Asic[45]:550 Asic[46]:550 Asic[47]:550 Asic[48]:550
Asic[49]:550 Asic[50]:550 Asic[51]:550 Asic[52]:550 Asic[53]:550 Asic[54]:550 Asic[55]:550 Asic[56]:550
Asic[57]:550 Asic[58]:550 Asic[59]:550 Asic[60]:550 Asic[61]:550 Asic[62]:550
Chain:3 max freq=550
Chain:3 min freq=550

max freq = 550
Chain[J1] PIC temp offset=62,-72,0,0,0,0,0,0
Chain[J1] chip[244] use PIC middle temp offset=-72 typeID=1a
Chain[J3] PIC temp offset=62,-68,0,0,0,0,0,0
Chain[J3] chip[244] use PIC middle temp offset=-68 typeID=1a
Chain[J4] PIC temp offset=62,-76,0,0,0,0,0,0
Chain[J4] chip[244] use PIC middle temp offset=-76 typeID=1a
Chain[J1] set working voltage=940 [6]
Chain[J3] set working voltage=940 [6]
Chain[J4] set working voltage=940 [6]
prepare send works thread on chain[0]
prepare send works thread on chain[1]
prepare send works thread on chain[2]
prepare send works thread on chain[3]
prepare send works thread on chain[4]
prepare send works thread on chain[5]
prepare send works thread on chain[6]
prepare send works thread on chain[7]
prepare send works thread on chain[8]
prepare send works thread on chain[9]
prepare send works thread on chain[10]
prepare send works thread on chain[11]
prepare send works thread on chain[12]
prepare send works thread on chain[13]
prepare send works thread on chain[14]
prepare send works thread on chain[15]
do heat board 8xPatten for 1 times
Find hashboard on Chain[0]
Find hashboard on Chain[2]
Find hashboard on Chain[3]
Check voltage total rate=11850
get PIC voltage=940 on chain[0], check: must be < 940
get PIC voltage=940 on chain[2], check: must be < 940
get PIC voltage=940 on chain[3], check: must be < 940
start send works on chain[0]
start send works on chain[2]
start send works on chain[3]
wait send works done on chain[0]
get send work num :57456 on Chain[0]
get send work num :57456 on Chain[2]
get send work num :57456 on Chain[3]
wait send works done on chain[2]
wait send works done on chain[3]
wait recv nonce on chain[0]
wait recv nonce on chain[2]
wait recv nonce on chain[3]
get nonces on chain[0]
require nonce number:912
require validnonce number:57456
asic[00]=912   asic[01]=911   asic[02]=912   asic[03]=912   asic[04]=912   asic[05]=912   asic[06]=912   asic[07]=912   
asic[08]=912   asic[09]=912   asic[10]=912   asic[11]=912   asic[12]=908   asic[13]=912   asic[14]=912   asic[15]=912   
asic[16]=912   asic[17]=912   asic[18]=912   asic[19]=912   asic[20]=912   asic[21]=912   asic[22]=911   asic[23]=912   
asic[24]=912   asic[25]=912   asic[26]=912   asic[27]=912   asic[28]=912   asic[29]=912   asic[30]=912   asic[31]=912   
asic[32]=912   asic[33]=912   asic[34]=912   asic[35]=912   asic[36]=912   asic[37]=912   asic[38]=912   asic[39]=912   
asic[40]=912   asic[41]=912   asic[42]=912   asic[43]=912   asic[44]=912   asic[45]=912   asic[46]=912   asic[47]=912   
asic[48]=912   asic[49]=912   asic[50]=912   asic[51]=912   asic[52]=912   asic[53]=912   asic[54]=912   asic[55]=912   
asic[56]=912   asic[57]=912   asic[58]=912   asic[59]=912   asic[60]=912   asic[61]=912   asic[62]=912   


Below ASIC's core didn't receive all the nonce, they should receive 8 nonce each!

asic[01]=911
core[052]=7   

asic[12]=908
core[075]=4   

asic[22]=911
core[017]=7   



freq[00]=550   freq[01]=550   freq[02]=550   freq[03]=550   freq[04]=550   freq[05]=550   freq[06]=550   freq[07]=550   
freq[08]=550   freq[09]=550   freq[10]=550   freq[11]=550   freq[12]=550   freq[13]=550   freq[14]=550   freq[15]=550   
freq[16]=550   freq[17]=550   freq[18]=550   freq[19]=550   freq[20]=550   freq[21]=550   freq[22]=550   freq[23]=550   
freq[24]=550   freq[25]=550   freq[26]=550   freq[27]=550   freq[28]=550   freq[29]=550   freq[30]=550   freq[31]=550   
freq[32]=550   freq[33]=550   freq[34]=550   freq[35]=550   freq[36]=550   freq[37]=550   freq[38]=550   freq[39]=550   
freq[40]=550   freq[41]=550   freq[42]=550   freq[43]=550   freq[44]=550   freq[45]=550   freq[46]=550   freq[47]=550   
freq[48]=550   freq[49]=550   freq[50]=550   freq[51]=550   freq[52]=550   freq[53]=550   freq[54]=550   freq[55]=550   
freq[56]=550   freq[57]=550   freq[58]=550   freq[59]=550   freq[60]=550   freq[61]=550   freq[62]=550   

total valid nonce number:57450
total send work number:57456
require valid nonce number:57456
repeated_nonce_num:122
err_nonce_num:45381
last_nonce_num:1060
get nonces on chain[2]
require nonce number:912
require validnonce number:57456
asic[00]=912   asic[01]=912   asic[02]=912   asic[03]=912   asic[04]=912   asic[05]=912   asic[06]=912   asic[07]=912   
asic[08]=912   asic[09]=912   asic[10]=912   asic[11]=912   asic[12]=912   asic[13]=912   asic[14]=912   asic[15]=912   
asic[16]=912   asic[17]=912   asic[18]=912   asic[19]=912   asic[20]=912   asic[21]=912   asic[22]=912   asic[23]=911   
asic[24]=912   asic[25]=912   asic[26]=912   asic[27]=912   asic[28]=912   asic[29]=912   asic[30]=912   asic[31]=912   
asic[32]=912   asic[33]=912   asic[34]=911   asic[35]=911   asic[36]=912   asic[37]=912   asic[38]=912   asic[39]=912   
asic[40]=912   asic[41]=912   asic[42]=912   asic[43]=912   asic[44]=912   asic[45]=912   asic[46]=912   asic[47]=912   
asic[48]=912   asic[49]=912   asic[50]=912   asic[51]=912   asic[52]=912   asic[53]=912   asic[54]=912   asic[55]=912   
asic[56]=912   asic[57]=912   asic[58]=912   asic[59]=912   asic[60]=912   asic[61]=912   asic[62]=912   


Below ASIC's core didn't receive all the nonce, they should receive 8 nonce each!

asic[23]=911
core[041]=7   

asic[34]=911
core[043]=7   

asic[35]=911
core[045]=7   



freq[00]=550   freq[01]=550   freq[02]=550   freq[03]=550   freq[04]=550   freq[05]=550   freq[06]=550   freq[07]=550   
freq[08]=550   freq[09]=550   freq[10]=550   freq[11]=550   freq[12]=550   freq[13]=550   freq[14]=550   freq[15]=550   
freq[16]=550   freq[17]=550   freq[18]=550   freq[19]=550   freq[20]=550   freq[21]=550   freq[22]=550   freq[23]=550   
freq[24]=550   freq[25]=550   freq[26]=550   freq[27]=550   freq[28]=550   freq[29]=550   freq[30]=550   freq[31]=550   
freq[32]=550   freq[33]=550   freq[34]=550   freq[35]=550   freq[36]=550   freq[37]=550   freq[38]=550   freq[39]=550   
freq[40]=550   freq[41]=550   freq[42]=550   freq[43]=550   freq[44]=550   freq[45]=550   freq[46]=550   freq[47]=550   
freq[48]=550   freq[49]=550   freq[50]=550   freq[51]=550   freq[52]=550   freq[53]=550   freq[54]=550   freq[55]=550   
freq[56]=550   freq[57]=550   freq[58]=550   freq[59]=550   freq[60]=550   freq[61]=550   freq[62]=550   

total valid nonce number:57453
total send work number:57456
require valid nonce number:57456
repeated_nonce_num:0
err_nonce_num:45018
last_nonce_num:1240
get nonces on chain[3]
require nonce number:912
require validnonce number:57456
asic[00]=912   asic[01]=912   asic[02]=912   asic[03]=912   asic[04]=912   asic[05]=912   asic[06]=912   asic[07]=911   
asic[08]=912   asic[09]=912   asic[10]=912   asic[11]=912   asic[12]=912   asic[13]=912   asic[14]=912   asic[15]=912   
asic[16]=912   asic[17]=912   asic[18]=912   asic[19]=911   asic[20]=912   asic[21]=912   asic[22]=912   asic[23]=896   
asic[24]=912   asic[25]=904   asic[26]=912   asic[27]=912   asic[28]=911   asic[29]=912   asic[30]=912   asic[31]=912   
asic[32]=912   asic[33]=912   asic[34]=912   asic[35]=912   asic[36]=912   asic[37]=912   asic[38]=912   asic[39]=912   
asic[40]=912   asic[41]=912   asic[42]=912   asic[43]=912   asic[44]=911   asic[45]=912   asic[46]=912   asic[47]=912   
asic[48]=912   asic[49]=912   asic[50]=912   asic[51]=912   asic[52]=912   asic[53]=912   asic[54]=912   asic[55]=912   
asic[56]=912   asic[57]=912   asic[58]=912   asic[59]=912   asic[60]=912   asic[61]=912   asic[62]=911   


Below ASIC's core didn't receive all the nonce, they should receive 8 nonce each!

asic[07]=911
core[110]=7   

asic[19]=911
core[108]=7   

asic[23]=896
core[025]=0   core[081]=0   

asic[25]=904
core[011]=0   

asic[28]=911
core[110]=7   

asic[44]=911
core[103]=7   

asic[62]=911
core[105]=7   



freq[00]=550   freq[01]=550   freq[02]=550   freq[03]=550   freq[04]=550   freq[05]=550   freq[06]=550   freq[07]=550   
freq[08]=550   freq[09]=550   freq[10]=550   freq[11]=550   freq[12]=550   freq[13]=550   freq[14]=550   freq[15]=550   
freq[16]=550   freq[17]=550   freq[18]=550   freq[19]=550   freq[20]=550   freq[21]=550   freq[22]=550   freq[23]=550   
freq[24]=550   freq[25]=550   freq[26]=550   freq[27]=550   freq[28]=550   freq[29]=550   freq[30]=550   freq[31]=550   
freq[32]=550   freq[33]=550   freq[34]=550   freq[35]=550   freq[36]=550   freq[37]=550   freq[38]=550   freq[39]=550   
freq[40]=550   freq[41]=550   freq[42]=550   freq[43]=550   freq[44]=550   freq[45]=550   freq[46]=550   freq[47]=550   
freq[48]=550   freq[49]=550   freq[50]=550   freq[51]=550   freq[52]=550   freq[53]=550   freq[54]=550   freq[55]=550   
freq[56]=550   freq[57]=550   freq[58]=550   freq[59]=550   freq[60]=550   freq[61]=550   freq[62]=550   

total valid nonce number:57427
total send work number:57456
require valid nonce number:57456
repeated_nonce_num:122
err_nonce_num:45315
last_nonce_num:998
chain[0]: All chip cores are opened OK!
Test Patten on chain[0]: FAILED!
Try to add voltage on chain[0]...
chain[2]: All chip cores are opened OK!
Test Patten on chain[2]: FAILED!
Try to add voltage on chain[2]...
chain[3]: some chip cores are not opened FAILED!
Test Patten on chain[3]: FAILED!
Try to add voltage on chain[3]...
do heat board 8xPatten for 2 times
Find hashboard on Chain[0]
Find hashboard on Chain[2]
Find hashboard on Chain[3]
Check voltage total rate=11850
get PIC voltage=940 on chain[0], check: must be < 940
get PIC voltage=940 on chain[2], check: must be < 940
get PIC voltage=940 on chain[3], check: must be < 940
do open core on Chain[3]...
Done open core on Chain[3]!
start send works on chain[0]
start send works on chain[2]
start send works on chain[3]
wait send works done on chain[0]
get send work num :57456 on Chain[0]
get send work num :57456 on Chain[2]
get send work num :57456 on Chain[3]
wait send works done on chain[2]
wait send works done on chain[3]
wait recv nonce on chain[0]
wait recv nonce on chain[2]
wait recv nonce on chain[3]
get nonces on chain[0]
require nonce number:912
require validnonce number:57456
asic[00]=912   asic[01]=912   asic[02]=912   asic[03]=912   asic[04]=912   asic[05]=912   asic[06]=912   asic[07]=912   
asic[08]=912   asic[09]=912   asic[10]=912   asic[11]=912   asic[12]=906   asic[13]=912   asic[14]=912   asic[15]=912   
asic[16]=912   asic[17]=912   asic[18]=912   asic[19]=912   asic[20]=912   asic[21]=912   asic[22]=912   asic[23]=912   
asic[24]=912   asic[25]=912   asic[26]=912   asic[27]=912   asic[28]=912   asic[29]=912   asic[30]=912   asic[31]=912   
asic[32]=912   asic[33]=912   asic[34]=912   asic[35]=912   asic[36]=912   asic[37]=912   asic[38]=912   asic[39]=912   
asic[40]=912   asic[41]=912   asic[42]=912   asic[43]=912   asic[44]=912   asic[45]=912   asic[46]=912   asic[47]=912   
asic[48]=912   asic[49]=912   asic[50]=912   asic[51]=912   asic[52]=912   asic[53]=912   asic[54]=912   asic[55]=912   
asic[56]=912   asic[57]=912   asic[58]=912   asic[59]=912   asic[60]=912   asic[61]=912   asic[62]=912   


Below ASIC's core didn't receive all the nonce, they should receive 8 nonce each!

asic[12]=906
core[075]=2   



freq[00]=550   freq[01]=550   freq[02]=550   freq[03]=550   freq[04]=550   freq[05]=550   freq[06]=550   freq[07]=550   
freq[08]=550   freq[09]=550   freq[10]=550   freq[11]=550   freq[12]=550   freq[13]=550   freq[14]=550   freq[15]=550   
freq[16]=550   freq[17]=550   freq[18]=550   freq[19]=550   freq[20]=550   freq[21]=550   freq[22]=550   freq[23]=550   
freq[24]=550   freq[25]=550   freq[26]=550   freq[27]=550   freq[28]=550   freq[29]=550   freq[30]=550   freq[31]=550   
freq[32]=550   freq[33]=550   freq[34]=550   freq[35]=550   freq[36]=550   freq[37]=550   freq[38]=550   freq[39]=550   
freq[40]=550   freq[41]=550   freq[42]=550   freq[43]=550   freq[44]=550   freq[45]=550   freq[46]=550   freq[47]=550   
freq[48]=550   freq[49]=550   freq[50]=550   freq[51]=550   freq[52]=550   freq[53]=550   freq[54]=550   freq[55]=550   
freq[56]=550   freq[57]=550   freq[58]=550   freq[59]=550   freq[60]=550   freq[61]=550   freq[62]=550   

total valid nonce number:57450
total send work number:57456
require valid nonce number:57456
repeated_nonce_num:182
err_nonce_num:45442
last_nonce_num:942
get nonces on chain[2]
require nonce number:912
require validnonce number:57456
asic[00]=912   asic[01]=912   asic[02]=912   asic[03]=912   asic[04]=911   asic[05]=912   asic[06]=912   asic[07]=912   
asic[08]=912   asic[09]=911   asic[10]=912   asic[11]=912   asic[12]=912   asic[13]=912   asic[14]=912   asic[15]=912   
asic[16]=912   asic[17]=912   asic[18]=912   asic[19]=912   asic[20]=912   asic[21]=912   asic[22]=912   asic[23]=912   
asic[24]=912   asic[25]=912   asic[26]=912   asic[27]=912   asic[28]=912   asic[29]=912   asic[30]=911   asic[31]=912   
asic[32]=912   asic[33]=912   asic[34]=912   asic[35]=912   asic[36]=912   asic[37]=912   asic[38]=912   asic[39]=912   
asic[40]=912   asic[41]=912   asic[42]=912   asic[43]=912   asic[44]=912   asic[45]=912   asic[46]=912   asic[47]=912   
asic[48]=912   asic[49]=912   asic[50]=912   asic[51]=912   asic[52]=912   asic[53]=912   asic[54]=912   asic[55]=912   
asic[56]=912   asic[57]=912   asic[58]=912   asic[59]=912   asic[60]=912   asic[61]=912   asic[62]=912   


Below ASIC's core didn't receive all the nonce, they should receive 8 nonce each!

asic[04]=911
core[039]=7   

asic[09]=911
core[041]=7   

asic[30]=911
core[043]=7   



freq[00]=550   freq[01]=550   freq[02]=550   freq[03]=550   freq[04]=550   freq[05]=550   freq[06]=550   freq[07]=550   
freq[08]=550   freq[09]=550   freq[10]=550   freq[11]=550   freq[12]=550   freq[13]=550   freq[14]=550   freq[15]=550   
freq[16]=550   freq[17]=550   freq[18]=550   freq[19]=550   freq[20]=550   freq[21]=550   freq[22]=550   freq[23]=550   
freq[24]=550   freq[25]=550   freq[26]=550   freq[27]=550   freq[28]=550   freq[29]=550   freq[30]=550   freq[31]=550   
freq[32]=550   freq[33]=550   freq[34]=550   freq[35]=550   freq[36]=550   freq[37]=550   freq[38]=550   freq[39]=550   
freq[40]=550   freq[41]=550   freq[42]=550   freq[43]=550   freq[44]=550   freq[45]=550   freq[46]=550   freq[47]=550   
freq[48]=550   freq[49]=550   freq[50]=550   freq[51]=550   freq[52]=550   freq[53]=550   freq[54]=550   freq[55]=550   
freq[56]=550   freq[57]=550   freq[58]=550   freq[59]=550   freq[60]=550   freq[61]=550   freq[62]=550   

total valid nonce number:57453
total send work number:57456
require valid nonce number:57456
repeated_nonce_num:121
err_nonce_num:45263
last_nonce_num:877
get nonces on chain[3]
require nonce number:912
require validnonce number:57456
asic[00]=912   asic[01]=912   asic[02]=912   asic[03]=912   asic[04]=912   asic[05]=912   asic[06]=911   asic[07]=912   
asic[08]=912   asic[09]=912   asic[10]=912   asic[11]=912   asic[12]=912   asic[13]=911   asic[14]=912   asic[15]=912   
asic[16]=912   asic[17]=912   asic[18]=912   asic[19]=912   asic[20]=912   asic[21]=912   asic[22]=912   asic[23]=896   
asic[24]=912   asic[25]=903   asic[26]=912   asic[27]=912   asic[28]=912   asic[29]=912   asic[30]=912   asic[31]=912   
asic[32]=912   asic[33]=912   asic[34]=912   asic[35]=912   asic[36]=912   asic[37]=912   asic[38]=912   asic[39]=912   
asic[40]=912   asic[41]=912   asic[42]=912   asic[43]=912   asic[44]=912   asic[45]=912   asic[46]=912   asic[47]=912   
asic[48]=912   asic[49]=912   asic[50]=912   asic[51]=912   asic[52]=912   asic[53]=912   asic[54]=912   asic[55]=912   
asic[56]=912   asic[57]=912   asic[58]=912   asic[59]=912   asic[60]=912   asic[61]=912   asic[62]=912   


Below ASIC's core didn't receive all the nonce, they should receive 8 nonce each!

asic[06]=911
core[107]=7   

asic[13]=911
core[105]=7   

asic[23]=896
core[025]=0   core[081]=0   

asic[25]=903
core[011]=0   core[109]=7   



freq[00]=550   freq[01]=550   freq[02]=550   freq[03]=550   freq[04]=550   freq[05]=550   freq[06]=550   freq[07]=550   
freq[08]=550   freq[09]=550   freq[10]=550   freq[11]=550   freq[12]=550   freq[13]=550   freq[14]=550   freq[15]=550   
freq[16]=550   freq[17]=550   freq[18]=550   freq[19]=550   freq[20]=550   freq[21]=550   freq[22]=550   freq[23]=550   
freq[24]=550   freq[25]=550   freq[26]=550   freq[27]=550   freq[28]=550   freq[29]=550   freq[30]=550   freq[31]=550   
freq[32]=550   freq[33]=550   freq[34]=550   freq[35]=550   freq[36]=550   freq[37]=550   freq[38]=550   freq[39]=550   
freq[40]=550   freq[41]=550   freq[42]=550   freq[43]=550   freq[44]=550   freq[45]=550   freq[46]=550   freq[47]=550   
freq[48]=550   freq[49]=550   freq[50]=550   freq[51]=550   freq[52]=550   freq[53]=550   freq[54]=550   freq[55]=550   
freq[56]=550   freq[57]=550   freq[58]=550   freq[59]=550   freq[60]=550   freq[61]=550   freq[62]=550   

total valid nonce number:57429
total send work number:57456
require valid nonce number:57456
repeated_nonce_num:182
err_nonce_num:45504
last_nonce_num:1107
chain[0]: All chip cores are opened OK!
Test Patten on chain[0]: FAILED!
Try to add voltage on chain[0]...
chain[2]: All chip cores are opened OK!
Test Patten on chain[2]: FAILED!
Try to add voltage on chain[2]...
chain[3]: some chip cores are not opened FAILED!
Test Patten on chain[3]: FAILED!
Try to add voltage on chain[3]...
restartNum = 2 , auto-reinit enabled...
Chain[0] Chip[62] TempTypeID=1a middle offset=-72
Chain[0] Chip[62] local Temp=56
Chain[0] Chip[62] middle Temp=63
Chain[2] Chip[62] TempTypeID=1a middle offset=-68
Chain[2] Chip[62] local Temp=56
Chain[2] Chip[62] middle Temp=65
Chain[3] Chip[62] TempTypeID=1a middle offset=-76
Chain[3] Chip[62] local Temp=58
Chain[3] Chip[62] middle Temp=59
set FAN speed according to: temp_highest=65 temp_top1[PWM_T]=65 temp_top1[TEMP_POS_LOCAL]=58 temp_change=0 fix_fan_steps=-11
set normal FAN speed... with fix_fan_steps=-12
FAN PWM: 0
11  Bitcoin / Hardware / Someone on Ebay offering 10 Bitmain S9's & 10 Bitmain T9's on: February 06, 2017, 01:26:25 AM
I was browsing Ebay to see what crazy prices are being asked for the newer generation miners. I might even have grabbed one if they were anywhere close to reasonable.

Imagine my surprise to see these listing by the same person.  Tongue

http://www.ebay.com/itm/10-Bitmain-T9-bitcoin-miners-ANTMINER-IN-HAND-111-5TH-mini-farm-BRAND-NEW-/132081502154?hash=item1ec0abc7ca:g:guYAAOSw241YkMNL

and

http://www.ebay.com/itm/10-Bitmain-S9-Batch-22-16nm-Bitcoin-miners-ANTMINER-IN-HAND-111TH-mini-farm-/132087248625?hash=item1ec10376f1:g:m9MAAOSw5cNYl5vx

Of course this: "PAYMENT IS TO BE  BITCOIN/BTC , CASH  IN PERSON, OR BANK DEPO (NO CHECKS). NOTE WE WILL REFUND ANY PAYPAL PAYMENT OR CC PAYMENT ATTEMPTED  FOR THIS AUCTION."

Both sets of miners are priced at $19,999.99.

And part of the listing reads: "Up for grabs is 10 Bitmain batch 22 11TH S9 16nm bitcoin miners currently running strong for 9 weeks now.  Bitmain ANTMINER S9 111 TH/s mini farm money maker."

So they are USED.
Beside the fact that they are requiring payment in terms Ebay does not allow - BTC and Bank Deposits.

I smell a scam of some sort and wouldn't touch it with a ten-foot pole.
I reported both listings as in violation of EBay's payment policy. I'll do anything I can to help prevent people from being ripped off.

Maybe if we all do our part in some way, we can help to bring down these crazy prices for ASIC miners. [Wishful thinking, I know]
12  Bitcoin / Mining speculation / Bitcoin Diff Jump in About 7.5 hours. :( on: February 04, 2017, 01:55:54 PM
 I just took a look at Bitcoin Wisdom to see what may be in store for us.

Currently looks like a (+8.64%) jump in about 5.8 hours or about 39 blocks. Of course that may change either way before then, but we're getting close.

I'm just thankful it's not showing a 12-15% diff increase.

Good lucks boys and girls and hold on tight!
Mine on!!  Grin  Cheesy  Grin  Cheesy  Cool

EDIT: It's showing an average of right at 1 block per 9 minutes.  Shocked


Bitcoin Difficulty: 392,963,262,344
Estimated Next Difficulty: 426,926,642,622 (+8.64%) 
Adjust time: After 39 Blocks, About 5.8 hours 
Hashrate(?): 3,090,761,642 GH/s
Block Generation Time(?):
1 block: 9.0 minutes

3 blocks: 26.9 minutes

6 blocks: 53.9 minutes
13  Bitcoin / Hardware / Is the S7 Exhaust Fan the Same as the S9? One of my S9 Exhaust Fans is Dying on: September 23, 2016, 08:45:01 PM
Just looking at my Awesome Miner monitor and noticed one of my S9's was running much hotter than the others.

Upon close inspection, my exhaust fan was only spinning at 1500 RPM's. I checked the fan speed in the browser and tried rebooting. No luck.

If the fan is the same in the S7 I will pull an exhaust fan off of one of those. If not, I guess I'll be ordering a fan. Sad But I think they're the same.
Am I right?

THANKS!! Smiley
14  Bitcoin / Hardware / Email from Bitmain Re: Reapair Order for S9 - Interesting... on: September 07, 2016, 03:53:41 AM
Howdy folks,
I relieved this rather cryptic email from B-man tonight. All it said was:

Hi, xxxxxxx@xxxxx.com:
Your repair order has been Payed.
•   Expend: 0BTC
•   Order ID: xxxxxxxx
•   Repair ID: xxxxxxxxxxx
Order Details
Device Name   Count
Hashboard S9(12.93T 600M)    × 1
BB Board(S9-C5)    × 1
REPAIRORDER PAYED

I am assuming this means that my parts are covered by warranty and they aren't charging me anything. (Although it did cost a small fortune to send all 3.8 very heavy pounds of parts to China via UPS.) Sad

Also, on the repair ticket it's just as cryptic. It says under Pay Status "Payed" and under Replace Status it says "Hava Replace". Not sure what the "Hava" is supposed to mean. I thought it might be a truncated word, but I can't imagine what it might be. Hopefully it means my parts will be replaced by new boards.

Has anyone else going through B-man for a warranty repair received something similar? What was your experience and outcome, please?

Hopefully, it will be making it's way back to me soon. It's the only one of my S9's that has ever found a block!
It will be very nice to get this S9 up and running again, bringing my mini-farm up to 4 S9's - as long as the others keep hashing and don't start dying off one by one.

I will update this when I have more information and/or a tracking number. Then when my parts are received.

Also, thanks for any light from someone who has previously experienced this communication and similar notation on the repair ticket might be able to shed on this information.

Best wishes all and happy mining! Smiley Smiley
15  Bitcoin / Hardware / S9 with SD Card Slot,, but NO SD Drive on: August 18, 2016, 02:20:42 AM
Anyone else try to use the SD Card on their S9 only to discover it's just an empty hole?

There is no drive located behind the slot. The Micro SD just falls through.

What a pathetic way to cut corners.


Am I the ONLY one, or has anyone else even checked?
I would be interested in knowing.
Thanks.
16  Bitcoin / Bitcoin Technical Support / Monitoring Bitcoin Core Wallet Remotely? on: July 31, 2016, 08:27:49 PM
I apologize if this doesn't belong here, if not, someone please move it.

I have Bitcoin Core full node and my wallet on a separate PC. Is there a way to just monitor the wallet from a separate PC?

Thanks!
17  Bitcoin / Hardware / S9 Center Board Appears Dead?? on: July 30, 2016, 07:28:21 PM
I noticed the center board on one of my S9's was hashing 0.00 last night. It was still showing all O's across the ASIC chain for that board, but no hash.
I rebooted and it would come back hashing. But 30 minutes or so later, it would go back to 0.
The rebooting worked 2 or 3 times, but now the board is completely absent from the miner status page.

I have powered down a few times to see if it would come back but it didn't.

I tried to reset it a few minutes ago, but my few attempts at getting it to reset failed.

I can't try the reset again for a few hours as I had to shut down all my miners because of a major thunderstorm and my fans could suck in the pouring rain.

Any thoughts other than trying again to get it to reset? If the reset fails, would you suggest flashing as a possible solution? It's a batch 3.

Any suggestions welcome.

Thanks!
18  Bitcoin / Hardware / Down-clocking S7's to 500Mhz? on: July 10, 2016, 05:45:28 PM
I apologize if this is a dumb question, but I'm pretty electrically-challenged.

If I were to down-clock all of my S7's to, say, 500Mhz, would it save any measurable amount on electricity over the days/month?
Or does the PSU still pull a set amount from the wall vs. pulling the amount needed to run the miner?

Thanks for any replies! Smiley
19  Bitcoin / Mining software (miners) / Is there an app that can schedule frequency changes on S7/S9 ? Thanks! Anyone? on: July 03, 2016, 12:24:13 AM
Wondered if there was a "task scheduler" type app that can adjust the frequency on the Antminer depending on time of day.
Thanks for any responses.  Smiley
20  Bitcoin / Hardware / LONGER PCI-e Cables for S7? on: May 31, 2016, 04:25:16 PM
Would someone kindly please point me in the right direction for the best place to purchase LONGER PCI-e cables that are required for the S7 that come with the Bitman S7 PSU?

The cables that came with my power supply are very short and a pain in the *** to arrange for optimum use/cooling of the equipment.

Thanks for any replies!
Happy mining!  Grin
Pages: [1] 2 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!