S19pro review. now open.

[philipma1957]

Went to Clifton cleaned gear.

ON the way home buysolar took me to his house and gave me the s19pro.


I will do review today  and tommorrow.

[1715193397]

1715193397

[1715193397]

1715193397

[philipma1957]

spacer

it is doing close to spec  at the pool

[philipma1957]

I have an hourly watt meter.

so   723.53 is the reading at 720pm EST

and 726.86 is the reading at 820pm EST. so 3.33 kwatts. for 111 on the gui and 121 at the pool

and 729.98 is the reading at 920pm EST so 6.45 kwatts/2 = 3.225 kwatts for 110.6  on the gui and 112.1pool

and 733.17 is the reading at 1020pm EST so 9.645/3 = 3.215 kwatts for 110.1 on the gui and 109.78pool

and 739.64 is the reading at 1220am EST so 16.11/5 = 3.222 kwatts for 111.6 on the gui and 110.9pool

and 773.53 is the reading at 10:20 am EST so 50/15 = 3.333 kwatts

a 1 hour test is simply not very accurate.
a 2 hour test is not long enough.
a 3 hour test gets power use closer to accurate
a 5 hour test show that same 3.2xx kwatt number.

a 15 hour test shows that we rose to 3.333 kwatts. and the most likely reason is the room went from 85f to 96f

I will do a few more power hash tests tonight.

I will post back on power and hash for a day or 2.


Gui has changed bigly.

notice first pool is missing one 3   should be 3333 at the end and is 333 cue skips and labels it abnormal
notice second pool is rejected mmpool.org has this issue with a lot of mining gear and it is labeled abnormal
third pool is good.

fan speeds are decent as room is not crazy hot.

I suspect room will heat up and fans will get louder.




I will play with inspect elemental options.

Not much luck so far.

[mikeywith]

notice second pool is rejected mmpool.org has this issue with a lot of mining gear and it is labeled abnormal

I believe this has to do with the fact the mmpool doesn't support AsicBoost and most gears nowadays come with Asicboost enabled by default.

I will play with inspect elemental options.

Not much luck so far.

I wouldn't be surprised if they changed the way they hide those settings, I mean look at how much access we had to settings that Bitmain thought they kept hidden using some simple methods, anyway, I heard that Vnish are close to finishing their custom firmware for the S19 series, It would be very interesting to see what this beast is capable of with custom firmware.

[philipma1957]

It is pretty quiet for a 85f room.

Would have been nice to get five of  these a while ago.

Looks like it uses 3225 watts for 110 th

that is 29.3 watts a th

so far the one vnish test miner I had did 25 watts a th running an s17pro at lowest power setting.

roughly 990 watts and 39.96 th

pretty good. I have to think this gear could approach 22-25 watts if it clocks to 95th

it is about 1 inch taller 1 inch wider 1 inch deeper.

the psu fans are bigger which cuts down noise.

[generalt]

Thanks for the sneak peek Phil.  Looking forward for the full review. 

[mikeywith]

that is 29.3 watts a th

so far the one vnish test miner I had did 25 watts a th running an s17pro at lowest power setting.

How ironic does it sound that the S17 pro on a custom firmware is more efficient than the S19 pro on stock? I wonder what does it take for bitmain to start thinking about adding more power modes for its new gears? I personally would love to use the stock firmware with a lot more settings available to me, but I am forced to use custom firmware because Bitmain is too lazy to do anything about their stock firmware, which not only lacks tunning and all the stuff you get on the custom firmware, it lacks basic functions like frequency, heck, even fan speed is disabled on the stock firmware.

[philipma1957]

Thanks for the sneak peek Phil.  Looking forward for the full review. 

Yeah buysolar and I spent the day cleaning 🧹 🧼 the gear. I was driving back to Howell in his tesla and he said I could have the s19pro for a few days to review. I will do a youtube and let people hear how loud it is.
I have the dead avalon 1066 I can stack them together to show size.

Have to say these are very likely the same chips as the s17pro  just a ton of them per board 114.

freq is 525 . I will give the log tomorrow.

[thierry4wd]

interesting !!! so see a fasson for me, to see the thing clearer .... esseyon to identify the chips:

S17 pro has 48 chips per board ... so a total of 144.
I took at asar a status on google of S17, which shows 57th with an average of 595mhz on the maps ... https://support.bitmain.com/hc/article_attachments/360031053654/2.jpg

Now let's see the S19 ... 114 chip x 3 cards, 342 chips, for 110th and an average of 525mhz, are you following me? let's go on !!!

the calculation, simulate an S17 at 525mhz: (57000/595) x525 = 50300ghs
see the speed per chip, 50300/144 = 349.3ghs per chip so ...

Let's compare to the S19 ... 349.26 x 342chips which gives us 119000ghs ...

thanks to this little calculation, we have noticed, that in fact, even the S17pro is faster for a given chip speed! not by much ...

add the rounded comma, the different miner efficiency (all different), the different models of S17 ...
I also believe that Phil is right, the S19, contains the same chips as the S17 ...

[philipma1957]

that said i am guessing decent firmware rather than bitmain shitware would help the gear.

history log.

Code:

free_area_init_node: node 0, pgdat c0b3c040, node_mem_map cde10000
  Normal zone: 480 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 61440 pages, LIFO batch:15
percpu: Embedded 12 pages/cpu @cddf0000 s19916 r8192 d21044 u49152
pcpu-alloc: s19916 r8192 d21044 u49152 alloc=12*4096
pcpu-alloc: [0] 0 [0] 1 
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 60960
Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 209672K/245760K available (6317K kernel code, 243K rwdata, 1932K rodata, 1024K init, 232K bss, 19704K reserved, 16384K cma-reserved, 0K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xcf800000 - 0xff800000   ( 768 MB)
    lowmem  : 0xc0000000 - 0xcf000000   ( 240 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc090e410   (9242 kB)
      .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
      .data : 0xc0b00000 - 0xc0b3cda0   ( 244 kB)
       .bss : 0xc0b3cda0 - 0xc0b77024   ( 233 kB)
Preemptible hierarchical RCU implementation.
	Build-time adjustment of leaf fanout to 32.
	RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
NR_IRQS:16 nr_irqs:16 16
efuse mapped to cf800000
ps7-slcr mapped to cf802000
L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 1 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 8 ways, 512 kB
L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
zynq_clock_init: clkc starts at cf802100
Zynq clock init
sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
Switching to timer-based delay loop, resolution 3ns
clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
ps7-ttc #0 at cf80a000, irq=18
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x100000 - 0x100058
CPU1: failed to boot: -1
Brought up 1 CPUs
SMP: Total of 1 processors activated (666.66 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
media: Linux media interface: v0.10
Linux video capture interface: v2.00
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
EDAC MC: Ver: 3.0.0
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource arm_global_timer
NET: Registered protocol family 2
TCP established hash table entries: 2048 (order: 1, 8192 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 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.
PCI: CLS 0 bytes, default 64
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 6632K (cd480000 - cdafa000)
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
futex hash table entries: 512 (order: 3, 32768 bytes)
workingset: timestamp_bits=28 max_order=16 bucket_order=0
jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
dma-pl330 f8003000.ps7-dma: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 159, base_baud = 6249999) is a xuartps
console [ttyPS0] enabled
xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
CAN device driver interface
gpiod_set_value: invalid GPIO
libphy: MACB_mii_bus: probed
macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-pci: EHCI PCI platform driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
cdns-i2c e0005000.ps7_i2c: 100 kHz mmio e0005000 irq 154
Xilinx Zynq CpuIdle Driver started
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
ledtrig-cpu: registered to indicate activity on CPUs
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
nand: disable subpage write
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
nand: NAND_ECC_HW
nand: NAND_ECC_HW_SYNDROME
mtd->writesize = 2048
ecc->strength = 1
ecc->size = 2048
mtd->writesize = 2048
chip->ecc_strength_ds = 4
chip->ecc_step_ds = 512
nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
8 ofpart partitions found on MTD device pl35x-nand
Creating 8 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-dts-marker-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000005200000 : "sig"
0x000005200000-0x000006000000 : "reserve1"
0x000006000000-0x000007000000 : "upgrade-ramfs"
0x000007000000-0x00000a800000 : "upgrade-file"
0x00000a800000-0x000010000000 : "reserve2"
nf_conntrack version 0.5.0 (3635 buckets, 14540 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
NET: Registered protocol family 10
ip6_tables: (C) 2000-2006 Netfilter Core Team
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
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
zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
zynq_pm_late_init: Unable to map DDRC IO memory.
Registering SWP/SWPB emulation handler
hctosys: unable to open rtc device (rtc0)
ALSA device list:
  No soundcards found.
RAMDISK: gzip image found at block 0
EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
EXT4-fs warning (device ram0): ext4_update_dynamic_rev:746: updating to rev 1 because of new feature flag, running e2fsck is recommended
EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 1:0.
devtmpfs: mounted
Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr,errors=remount-ro
devpts: called with bogus options
ubi0: attaching mtd2
ubi0: scanning is finished
ubi0: attached mtd2 (name "configs", size 8 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 262741923
ubi0: available PEBs: 36, total reserved PEBs: 28, PEBs reserved for bad PEB handling: 4
ubi0: background thread "ubi_bgt0d" started, PID 729
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 733
UBIFS (ubi0:0): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID A9E8BDA4-70DE-45D9-83BE-2DD9F129C0C6, small LPT model
ubi2: attaching mtd4
ubi2: scanning is finished
ubi2: attached mtd4 (name "reserve1", size 14 MiB)
ubi2: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi2: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi2: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi2: good PEBs: 112, bad PEBs: 0, corrupted PEBs: 0
ubi2: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi2: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 4054018534
ubi2: available PEBs: 0, total reserved PEBs: 112, PEBs reserved for bad PEB handling: 4
ubi2: background thread "ubi_bgt2d" started, PID 740
UBIFS (ubi2:0): background thread "ubifs_bgt2_0" started, PID 744
UBIFS (ubi2:0): recovery needed
UBIFS (ubi2:0): recovery completed
UBIFS (ubi2:0): UBIFS: mounted UBI device 2, volume 0, name "misc"
UBIFS (ubi2:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi2:0): FS size: 11935744 bytes (11 MiB, 94 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
UBIFS (ubi2:0): reserved for root: 563754 bytes (550 KiB)
UBIFS (ubi2:0): media format: w4/r0 (latest is w4/r0), UUID 272071AF-FB6C-428F-A430-DD964D7BD84E, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
random: avahi-daemon urandom read with 2 bits of entropy available
macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
macb e000b000.ethernet eth0: link up (100/Full)
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
In axi fpga driver!
request_mem_region OK!
AXI fpga dev virtual address is 0xcfbc8000
*base_vir_addr = 0xb031
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized


===========================================Miner log===========================================
1970-01-01 00:00:09 Miner compile time: Fri Dec 11 11:23:44 CST 2020 type: Antminer S19 Pro
1970-01-01 00:00:10 This is fix-freq version
1970-01-01 00:00:10 Miner compile time: Fri Dec 11 11:23:44 CST 2020 type: Antminer S19 Pro
1970-01-01 00:00:10 commit version: 1821c90 2020-11-16 16:05:37, build by: jenkins 2020-12-11 11:35:43
1970-01-01 00:00:10 opt_multi_version     = 1
1970-01-01 00:00:10 opt_bitmain_ab        = 1
1970-01-01 00:00:10 mid_auto_gen          = 0
1970-01-01 00:00:10 opt_bitmain_work_mode = 0
1970-01-01 00:00:10 mmap fpga_mem_addr_hal = 0xb5800000
1970-01-01 00:00:10 HASH_ON_PLUG V9 = 0x7
1970-01-01 00:00:10 Note: front fan is power on!
1970-01-01 00:00:10 Note: rear fan is power on!
1970-01-01 00:00:10 start the http log.
1970-01-01 00:00:10 httpListenThread start ret=0
1970-01-01 00:00:10 start listen on 6060 ...
1970-01-01 00:00:10 load machine NBP1901 conf
1970-01-01 00:00:10 machine : NBP1901 
1970-01-01 00:00:10 chain_num 4, chain_domain_num 38, chain_asic_num 114, domain_asic_num 3
1970-01-01 00:00:16 miner ID : 8034f40457104814
1970-01-01 00:00:16 FPGA Version = 0xB031
1970-01-01 00:00:16 HASH_ON_PLUG V9 = 0x7
1970-01-01 00:00:16 ==========================capability start==========================
1970-01-01 00:00:16 board num = 3
1970-01-01 00:00:16 board id = 0, chain num = 1
1970-01-01 00:00:16 	chain id = 0
1970-01-01 00:00:16 board id = 1, chain num = 1
1970-01-01 00:00:16 	chain id = 1
1970-01-01 00:00:16 board id = 2, chain num = 1
1970-01-01 00:00:16 	chain id = 2
1970-01-01 00:00:16 ==========================capability end============================
1970-01-01 00:00:16 chain num = 3
1970-01-01 00:00:18 [chain 0]
1970-01-01 00:00:18 0x0000 11 42 9F A0 0A E0 5A AA   31 B3 5A 56 D3 35 29 31 
1970-01-01 00:00:18 0x0010 BE CA 84 2D 6D D7 B7 13   93 0A 4A 15 50 A5 8B 0F 
1970-01-01 00:00:18 0x0020 DB 93 99 A6 F7 62 F4 3D   82 A6 BF 8B F4 39 96 63 
1970-01-01 00:00:18 0x0030 C4 57 DB F2 C1 BD 39 AB   7D CF 22 12 8E F7 A6 07 
1970-01-01 00:00:18 0x0040 CA 0A FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:18 0x0050 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:18 0x0060 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:18 0x0070 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:18 0x0080 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:18 0x0090 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:18 0x00A0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:18 0x00B0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:18 0x00C0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:18 0x00D0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:18 0x00E0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:18 0x00F0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF 5A 
1970-01-01 00:00:18 
1970-01-01 00:00:20 [chain 1]
1970-01-01 00:00:20 0x0000 11 42 03 AC F0 B9 39 41   E1 84 2E F2 E5 67 4F 51 
1970-01-01 00:00:20 0x0010 6D BF E5 57 83 9D ED EA   C5 4A FC 27 E9 B2 B9 93 
1970-01-01 00:00:20 0x0020 7B 36 81 82 67 CC 83 B9   26 DE 0C BF 5D AD 79 F5 
1970-01-01 00:00:20 0x0030 61 93 C4 6C 8B 53 0D E8   AA D8 9A 6A B9 47 80 B3 
1970-01-01 00:00:20 0x0040 EF 81 FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:20 0x0050 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:20 0x0060 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:20 0x0070 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:20 0x0080 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:20 0x0090 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:20 0x00A0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:20 0x00B0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:20 0x00C0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:20 0x00D0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:20 0x00E0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:20 0x00F0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF 5A 
1970-01-01 00:00:20 
1970-01-01 00:00:22 [chain 2]
1970-01-01 00:00:22 0x0000 11 42 1D 50 B7 46 F4 79   F5 5A 1C ED 2A FD D3 A8 
1970-01-01 00:00:22 0x0010 7A 45 93 79 EE 2F 1E 1A   40 09 B9 C6 2C 14 14 D0 
1970-01-01 00:00:22 0x0020 BA B3 76 7D 11 75 E9 25   3B 09 74 15 CE 20 86 D8 
1970-01-01 00:00:22 0x0030 E3 B1 68 A3 6B 00 E6 CF   34 05 0E 28 3F 21 72 86 
1970-01-01 00:00:22 0x0040 11 7D FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:22 0x0050 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:22 0x0060 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:22 0x0070 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:22 0x0080 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:22 0x0090 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:22 0x00A0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:22 0x00B0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:22 0x00C0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:22 0x00D0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:22 0x00E0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF FF 
1970-01-01 00:00:22 0x00F0 FF FF FF FF FF FF FF FF   FF FF FF FF FF FF FF 5A 
1970-01-01 00:00:22 
1970-01-01 00:00:22 fan_eft : 1  fan_pwm : 70
1970-01-01 00:00:22 create thread
1970-01-01 00:00:22 fixed working voltage = 1260
1970-01-01 00:00:22 Chain [0] PCB Version: 0x0100
1970-01-01 00:00:22 Chain [0] BOM Version: 0x0100
1970-01-01 00:00:22 Chain [1] PCB Version: 0x0100
1970-01-01 00:00:22 Chain [1] BOM Version: 0x0100
1970-01-01 00:00:22 Chain [2] PCB Version: 0x0100
1970-01-01 00:00:22 Chain [2] BOM Version: 0x0100
1970-01-01 00:00:26 Fan check passed.
1970-01-01 00:00:27 chain[0] PIC jump to app
1970-01-01 00:00:28 Check chain[0] PIC fw version=0x89
1970-01-01 00:00:29 chain[1] PIC jump to app
1970-01-01 00:00:31 Check chain[1] PIC fw version=0x89
1970-01-01 00:00:32 chain[2] PIC jump to app
1970-01-01 00:00:34 Check chain[2] PIC fw version=0x89
1970-01-01 00:00:34 create thread
1970-01-01 00:00:34 max sensor num = 4
1970-01-01 00:00:34 temperature_monitor_thread start...
1970-01-01 00:00:38 power type version: 0x0071
1970-01-01 00:00:38 Enter sleep to make sure power release finish.
1970-01-01 00:02:39 Slept 120 seconds, diff = 5.
1970-01-01 00:02:39 set_voltage_by_steps to 1500.
1970-01-01 00:02:44 start up min temp by 75a = 22
1970-01-01 00:02:44 set UART baud to 115200
1970-01-01 00:02:49 chain avg vol rise to 15.19
1970-01-01 00:02:53 Chain[0]: find 114 asic, times 0
1970-01-01 00:03:00 Chain[1]: find 114 asic, times 0
1970-01-01 00:03:08 Chain[2]: find 114 asic, times 0
1970-01-01 00:03:08 pulse_mode = 1, ccdly_sel = 1, pwth_sel = 1
1970-01-01 00:03:13 min freq in eeprom = 525
1970-01-01 00:03:13 fixed frequency is 525
1970-01-01 00:03:13 Bring up temperature is 23
1970-01-01 00:03:13 set UART baud to 12000000
1970-01-01 00:03:13 set_voltage_by_steps to 1260.
1970-01-01 00:03:20 STATUS_INITED: soc init done!
1970-01-01 00:03:20 create thread
1970-01-01 00:03:20 create thread
1970-01-01 00:03:20 fan_etf: Set fixed fan speed=70
1970-01-01 00:03:23 start to init...
1970-01-01 00:03:31 Init done!
1970-01-01 00:03:31 STATUS_OKAY
1970-01-01 00:03:31 start the cached job
1970-01-01 00:03:31 Version num 8
1970-01-01 00:03:31 Mask num 0xe000
1970-01-01 00:03:31 freq = 525, percent = 90, hcn = 12480, timeout = 449
1970-01-01 00:03:31 set_start_time_point total_tv_start_sys=212 total_tv_end_sys=213

there is a very interesting line in the log

1970-01-01 00:00:10 This is fix-freq version

and it did let me set fans to 70%

1970-01-01 00:00:22 fan_eft : 1  fan_pwm : 70

note 1 freq:

1970-01-01 00:03:13 min freq in eeprom = 525
1970-01-01 00:03:13 fixed frequency is 525

I am not sure what dc power is:

Code:

1970-01-01 00:02:39 set_voltage_by_steps to [b]1500.[/b]
1970-01-01 00:02:44 start up min temp by 75a = 22
1970-01-01 00:02:44 set UART baud to 115200
1970-01-01 00:02:49 chain avg vol rise to 15.19
1970-01-01 00:02:53 Chain[0]: find 114 asic, times 0
1970-01-01 00:03:00 Chain[1]: find 114 asic, times 0
1970-01-01 00:03:08 Chain[2]: find 114 asic, times 0
1970-01-01 00:03:08 pulse_mode = 1, ccdly_sel = 1, pwth_sel = 1
1970-01-01 00:03:13 min freq in eeprom = 525
1970-01-01 00:03:13 fixed frequency is 525
1970-01-01 00:03:13 Bring up temperature is 23
1970-01-01 00:03:13 set UART baud to 12000000
1970-01-01 00:03:13 set_voltage_by_steps to 1260.

[thierry4wd]

ho yes, very good info !!! you don't have hidden menu ? fax fix is hidden ?

And, you have "save config" on this miner ? if yes... is the backdoor to crack it

[mikeywith]

I also believe that Phil is right, the S19, contains the same chips as the S17 ...

I enjoyed the math, but the S19/S19 pro use BM1398BB chips while the S17/S17pro both use BM1397AD, both look very different and their cost is a lot different, what is your opinion?

[NotFuzzyWarm]

AFAIK wasn't the s19 advertised as using the 5nm node chips vs 7nm for the s17's?

[philipma1957]

well bottom line is either they suck as a new chip design or the firmware is terrible.

in 30 minutes I am going to have a 50 38 hour meter reading. And since the garage is now a very warm room over 92f I suspect this will show 3.333 kwatts x 50 hour.

The measurement will be  more accurate. Since it is done over 50 hours.

I seem to get a steady 110-111 th number.

If indeed the chip is new and different and if the firmware is not crippling it that would be very bad news for bitmain as it sucks.

When compared to the s17pro chip which did 25 watts a th with vnish firmware.

38 hour readings

723.53
845.65

122.12/38 = 3.213 k- watts  this is decent number and gui says  110.0 real 111.7 avg.

pool reads 111.2 for 24 hour read.

here is a you tube video

https://www.youtube.com/watch?v=pqoQ0jPxs14

note I don't do sponsorships it is not click bait.

[baro0k]

you mentioned "firmware rather than bitmain shitware would help the gear."

I tried to find a firmware for my S19Pro but can't find anything available yet! while I can see some of the pools are giving me way less than others ( comparing between pools by connecting every 2 in a different pool).

[philipma1957]

you mentioned "firmware rather than bitmain shitware would help the gear."

I tried to find a firmware for my S19Pro but can't find anything available yet! while I can see some of the pools are giving me way less than others ( comparing between pools by connecting every 2 in a different pool).

I don't know how you did the test or what pools you tested.

Variance is possible. At the moment no one has issued aftermarket firmware.

[baro0k]

I run 2 devices on Slushpool and another 2 on f2pool at the moment I got on f2pool 0.0027 - 0.0030 in slushpool we're talking between 0.0025-0.0022 and the hash rate wasn't jumping upve the 110TH per devices one of them was reading less when I fully transferred them f2pool faced another issue " device disconnected ".

[mikeywith]

I run 2 devices on Slushpool and another 2 on f2pool at the moment I got on f2pool 0.0027 - 0.0030 in slushpool we're talking between 0.0025-0.0022 and the hash rate wasn't jumping upve the 110TH per devices one of them was reading less.

Slushpool pays in PPLNS, your payouts will heavily (in fact almost completely) depend on Slushpool's luck, if their luck for that day is 50% your payouts will be 50% less than on F2pool, of course, the opposite is also true and there are a few other factors involved, and since luck doesn't even out in days, sometimes not even in weeks, you should never use the payout as any means of measurement in comparing pools with different payouts.

What matters here (the only thing that matters) would be your average ACCEPTED hashrate at each pool, so you allow the miner to run for 24-48 hours, and then look at the average accepted, if they are more or less the same (which is most likely) then there is nothing wrong.

Another point is your connection to each of these pools, ping both pools and see if one is over 200ms then avoid it.

... when I fully transferred them f2pool faced another issue " device disconnected ".

Where does this error show? did you use the correct worker? confirmed there are no leading/trailing spaces in all 3 fields?

[baro0k]

thank you for explaining the pools difference I got the same point on twitter today while asking someone who showed that his 1 85t devices making way more than my 4 S19PRO.

it's showed in my user account tried today to reset all the devices and reconnect them and now am facing 2 overheat devices tooked the log and just now get back from the mining area so give me some time I'll upload the log if you allow me to complete the case am facing (cause I feel that I jumped off topic).

[mikeywith]

Only the admins will have the authority to delete your post, and I suspect that they will since it would be kind of off-topic, so the best thing to do would be to start your own topic in the proper section which is the support board, try to be as detailed as possible, post the kernel log, screenshots of the miner status page as well the pool settings.