Search content
Sort by
Showing 20 of 161 results by keksik
[ANN] [GPTC] GPTcash – AI-Powered Cryptocurrency | KawPow | No Pre-mine
Welcome to GPTcash (GPTC) – a revolutionary decentralized cryptocurrency of the new generation, inspired by the power of artificial intelligence and built on the reliable and fair KawPow algorithm.
About the Coin
Coin Name: GPTcash
Ticker: GPTC
Algorithm: KawPow
Blockchain Type: Proof of Work (PoW)
Block Time: 60 seconds
Block Reward: 50 GPTC
Max Supply: 21,000,000 GPTC
Premine: None
Dev Fee: None
Fair Launch: Yes, a fully fair launch with no privileges
Project Goals
Technical Details
Links
Wallet: https://github.com/GPTcash-dev/GPTcash/releases/download/1.1.3/GPTcash-win64-1.1.2.zip
Roadmap
Q2 2025
Network launch
Code release on GitHub
Mining start (fair launch)
Basic infrastructure: block explorer, mining pools
Q3 2025
Listings on first exchanges
Mobile wallet launch
Begin promoting in AI/ML communities
Q4 2025
AI platform integration
Bonus programs for developers and miners
AMA sessions, contests, team interaction
Join GPTcash
We are building a community where everyone has a voice. Whether you're a miner, developer, investor, or simply an enthusiast – GPTcash welcomes you. Help us shape the future of fair PoW!
Contact
✉ For inquiries and proposals: dev@gptcash.com
GPTcash – The cryptocurrency of the new generation. No pre-mine. No centralized control. Only decentralization, community, and technology.
About the Coin
Coin Name: GPTcash
Ticker: GPTC
Algorithm: KawPow
Blockchain Type: Proof of Work (PoW)
Block Time: 60 seconds
Block Reward: 50 GPTC
Max Supply: 21,000,000 GPTC
Premine: None
Dev Fee: None
Fair Launch: Yes, a fully fair launch with no privileges
Project Goals
- To create a fair and decentralized cryptocurrency for GPU miners
- To stimulate the AI and blockchain development community
- Integration with AI, machine learning, and data processing platforms
- Transparency, openness, and community involvement in project development
Technical Details
- KawPow – ASIC resistant, optimized for GPU mining
- Blockchain: completely independent
- API, RPC, and CLI available from day one
Links
Wallet: https://github.com/GPTcash-dev/GPTcash/releases/download/1.1.3/GPTcash-win64-1.1.2.zip
Roadmap
Q2 2025
Network launch
Code release on GitHub
Mining start (fair launch)
Basic infrastructure: block explorer, mining pools
Q3 2025
Listings on first exchanges
Mobile wallet launch
Begin promoting in AI/ML communities
Q4 2025
AI platform integration
Bonus programs for developers and miners
AMA sessions, contests, team interaction
Join GPTcash
We are building a community where everyone has a voice. Whether you're a miner, developer, investor, or simply an enthusiast – GPTcash welcomes you. Help us shape the future of fair PoW!
Contact
✉ For inquiries and proposals: dev@gptcash.com
GPTcash – The cryptocurrency of the new generation. No pre-mine. No centralized control. Only decentralization, community, and technology.
Hi
this error means ur hash boards from different miners or one or two or three of them repaired and u need code editor to read code from one of them and write to other two hash boards to match them together
this error means ur hash boards from different miners or one or two or three of them repaired and u need code editor to read code from one of them and write to other two hash boards to match them together
Hey can u elaborate what I need and what should i do? seems i have simialr problem, i mixed hashbaords together and now they shows 0asics all 3 chains.
Did you buy this unit directly from Bitmain?
It seems few of your hashboard have EEPROM issues that causes "ERROR_SOC_INIT"
If you bought this unit 2nd those 2 hashboard are replacements and they only flash it with modified firmware to bypass that issue. Usually, you need a code editor to be able to fix this issue.
However, since detected chips on two of your hashboard are abnormal you must hire a technician that could repair ASIC machines. Bitmain repair center is nice but I suggest you check this https://www.zeusbtc.com/ASIC-Miner-Repair/
Look for a repair center near your area because sending it back to Bitmain will cost you more than hiring ASIC tech near your location.
It seems few of your hashboard have EEPROM issues that causes "ERROR_SOC_INIT"
If you bought this unit 2nd those 2 hashboard are replacements and they only flash it with modified firmware to bypass that issue. Usually, you need a code editor to be able to fix this issue.
However, since detected chips on two of your hashboard are abnormal you must hire a technician that could repair ASIC machines. Bitmain repair center is nice but I suggest you check this https://www.zeusbtc.com/ASIC-Miner-Repair/
Look for a repair center near your area because sending it back to Bitmain will cost you more than hiring ASIC tech near your location.
thank you for your reply again, much appreciate your expert opinion. Yes i bought them from second hand...
I have reviewed the repair centers from Zeusbtc in Europe (as I am ehre) and repair cost range from 200-500EUR per one, so I decided I would like to repair them on my own. can you let me know what tools i would need? to repair 5 hashbaord it will cost 1000-1500Eur so i can do it(I repaired my S9 in the past with PICkit and some heatsink replacement, no chip replacement yet, but like to learn) on my own, save, learn something and have tools/knowledge for next repair.
I have glued the heatsink which fell off, lets see if it will work.
also meantime tested one s17+ with
Chain0 65asics
Chain1 28asics - disabled hashbaord
Chain2 0asics - disabled hashbaord
then original FW throw this:
also meantime tested one s17+ with
Chain0 65asics
Chain1 28asics - disabled hashbaord
Chain2 0asics - disabled hashbaord
then original FW throw this:
Code:
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:09 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:09 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:09 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:09 chain = 0, mode = 1, load_done = true.
2022-05-16 18:44:09 Voltage read fail. Will exit.
2022-05-16 18:44:09 driver-btm-api.c:222:set_miner_status: ERROR_SOC_INIT
2022-05-16 18:44:09 driver-btm-api.c:156:stop_mining: stop mining: soc init failed!
2022-05-16 18:44:09 thread.c:1403:cancel_read_nonce_reg_thread: cancel thread
2022-05-16 18:44:09 driver-btm-api.c:141:killall_hashboard: ****power off hashboard****
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:08 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:09 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:09 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:09 register.c:979:register_process_asic_response: Get another asic response: chain = 0, asic = 39
2022-05-16 18:44:09 chain = 0, mode = 1, load_done = true.
2022-05-16 18:44:09 Voltage read fail. Will exit.
2022-05-16 18:44:09 driver-btm-api.c:222:set_miner_status: ERROR_SOC_INIT
2022-05-16 18:44:09 driver-btm-api.c:156:stop_mining: stop mining: soc init failed!
2022-05-16 18:44:09 thread.c:1403:cancel_read_nonce_reg_thread: cancel thread
2022-05-16 18:44:09 driver-btm-api.c:141:killall_hashboard: ****power off hashboard****
How about multimeter? Because without tools you can't able to know if that chip near ASIC #20 is shorted or dead.
Check this troubleshooting guide from Zeusbtc below
- https://www.zeusbtc.com/articles/information/182-antminer-s17-manual-download
- https://www.zeusbtc.com/manuals/Antminer-S17-plus-Hash-Board-Repair-Guide.asp
Why not check that hashboard physically and maybe one of the heatsinks is loose.
Check this troubleshooting guide from Zeusbtc below
- https://www.zeusbtc.com/articles/information/182-antminer-s17-manual-download
- https://www.zeusbtc.com/manuals/Antminer-S17-plus-Hash-Board-Repair-Guide.asp
Why not check that hashboard physically and maybe one of the heatsinks is loose.
Hello,
yes i inspected hashboards physically and cleaned everting, was not dirty much but better than nothing. also one of the heatsing fall off. so how to put it back? may i use Arctic Silver 7g Premium Silver Thermal Cooling Adhesive Set (ASTA-7G) (which i used a year ago for S9) or only heatgun and basic solder?
second question, can u help me identify the chains physical position? I have J1-4J(using only J1,2,3) data cables connected to hasboard, but in system chain 0,1,2 are how related to J?
J1 is chain0, J2 is Chain1, J3 is chain2?
Is ok, if I pull only data cable from hashboard and let it still be connected to psu? ill just remove the data cable to test it with one chain at the time.
Is better to use for testing purpose original FW instead of hiveon FW i am currently running(underclock settings) so it will provide more V to the hashbaord for better stability?
thank you in advance, appreciate
Hello,
i have Bitmain Antminer S17+ and I am having problem with the hashboard now. it find some chips, then disable the chain and only chain 2 is working (using hiveon asic fw)
Would be someone kind and advice me what to do, before i must check physical chips on hashboard (as I dont have technical equipment for that, heat pistol, volt meter, etc)
here is log
i have Bitmain Antminer S17+ and I am having problem with the hashboard now. it find some chips, then disable the chain and only chain 2 is working (using hiveon asic fw)
Would be someone kind and advice me what to do, before i must check physical chips on hashboard (as I dont have technical equipment for that, heat pistol, volt meter, etc)
here is log
Quote
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
[ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Xilinx Zynq
[ 0.000000] cma: Reserved 16 MiB at 0x0e000000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] On node 0 totalpages: 61440
[ 0.000000] free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
[ 0.000000] Normal zone: 480 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 61440 pages, LIFO batch:15
[ 0.000000] percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
[ 0.000000] pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
[ 0.000000] pcpu-alloc:
[ 0.000000] Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Memory: 193872K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 35504K reserved, 16384K cma-reserved, 0K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc090c424 (9234 kB)
[ 0.000000] .init : 0xc0a00000 - 0xc0b00000 (1024 kB)
[ 0.000000] .data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
[ 0.000000] .bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Build-time adjustment of leaf fanout to 32.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] efuse mapped to cf800000
[ 0.000000] ps7-slcr mapped to cf802000
[ 0.000000] L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
[ 0.000000] L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
[ 0.000000] L2C-310 erratum 769419 enabled
[ 0.000000] L2C-310 enabling early BRESP for Cortex-A9
[ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[ 0.000000] L2C-310 ID prefetch enabled, offset 1 lines
[ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[ 0.000000] L2C-310 cache controller enabled, 8 ways, 512 kB
[ 0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
[ 0.000000] zynq_clock_init: clkc starts at cf802100
[ 0.000000] Zynq clock init
[ 0.000011] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
[ 0.000030] clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
[ 0.000054] Switching to timer-based delay loop, resolution 3ns
[ 0.000293] clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
[ 0.000319] ps7-ttc #0 at cf80a000, irq=18
[ 0.000554] Console: colour dummy device 80x30
[ 0.000570] Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
[ 0.000584] pid_max: default: 32768 minimum: 301
[ 0.000712] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000722] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.001328] CPU: Testing write buffer coherency: ok
[ 0.001530] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.001583] Setting up static identity map for 0x100000 - 0x100058
[ 0.100279] CPU1: failed to boot: -1
[ 0.100309] Brought up 1 CPUs
[ 0.100318] SMP: Total of 1 processors activated (666.66 BogoMIPS).
[ 0.100324] CPU: All CPU(s) started in SVC mode.
[ 0.101115] devtmpfs: initialized
[ 0.103197] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.103631] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.104580] pinctrl core: initialized pinctrl subsystem
[ 0.105689] NET: Registered protocol family 16
[ 0.107444] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.150232] cpuidle: using governor menu
[ 0.159126] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.159136] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.159283] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
[ 0.220810] vgaarb: loaded
[ 0.221160] SCSI subsystem initialized
[ 0.221440] usbcore: registered new interface driver usbfs
[ 0.221509] usbcore: registered new interface driver hub
[ 0.221943] usbcore: registered new device driver usb
[ 0.222487] media: Linux media interface: v0.10
[ 0.222601] Linux video capture interface: v2.00
[ 0.222759] pps_core: LinuxPPS API ver. 1 registered
[ 0.222767] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.222850] PTP clock support registered
[ 0.223029] EDAC MC: Ver: 3.0.0
[ 0.230624] Advanced Linux Sound Architecture Driver Initialized.
[ 0.241223] clocksource: Switched to clocksource arm_global_timer
[ 0.259551] NET: Registered protocol family 2
[ 0.260553] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.260589] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.260634] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.260683] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.260710] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.260916] NET: Registered protocol family 1
[ 0.271594] RPC: Registered named UNIX socket transport module.
[ 0.271602] RPC: Registered udp transport module.
[ 0.271608] RPC: Registered tcp transport module.
[ 0.271613] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.271636] PCI: CLS 0 bytes, default 64
[ 0.271857] Trying to unpack rootfs image as initramfs...
[ 0.272448] rootfs image is not initramfs (no cpio magic); looks like an initrd
[ 0.368042] Freeing initrd memory: 22464K (cc511000 - cdb01000)
[ 0.368388] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[ 0.370189] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.381981] workingset: timestamp_bits=28 max_order=16 bucket_order=0
[ 0.392825] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 0.393953] io scheduler noop registered
[ 0.393970] io scheduler deadline registered
[ 0.393999] io scheduler cfq registered (default)
[ 0.395675] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
[ 0.395689] dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.396856] e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
[ 0.900915] console [ttyPS0] enabled
[ 0.903809] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[ 0.909981] [drm] Initialized drm 1.1.0 20060810
[ 1.087612] brd: module loaded
[ 1.176549] loop: module loaded
[ 1.180498] CAN device driver interface
[ 1.186407] gpiod_set_value: invalid GPIO
[ 1.190186] libphy: MACB_mii_bus: probed
[ 1.271289] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
[ 1.279733] Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
[ 1.290031] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[ 1.294574] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 1.300452] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.306069] ehci-pci: EHCI PCI platform driver
[ 1.309377] usbcore: registered new interface driver usb-storage
[ 1.315929] mousedev: PS/2 mouse device common for all mice
[ 1.331304] i2c /dev entries driver
[ 1.336386] Xilinx Zynq CpuIdle Driver started
[ 1.340727] sdhci: Secure Digital Host Controller Interface driver
[ 1.345629] sdhci: Copyright(c) Pierre Ossman
[ 1.348606] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.392360] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[ 1.399267] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.404546] usbcore: registered new interface driver usbhid
[ 1.408726] usbhid: USB HID core driver
[ 1.412620] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[ 1.417581] nand: Micron MT29F2G08ABAGAWP
[ 1.420275] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
[ 1.426914] nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
[ 1.437072] Bad block table found at page 131008, version 0x01
[ 1.442029] Bad block table found at page 130944, version 0x01
[ 1.446800] 6 ofpart partitions found on MTD device pl35x-nand
[ 1.451319] Creating 6 MTD partitions on "pl35x-nand":
[ 1.455068] 0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
[ 1.471774] 0x000002800000-0x000004800000 : "ramfs"
[ 1.486774] 0x000004800000-0x000005000000 : "configs"
[ 1.501864] 0x000005000000-0x000006000000 : "reserve"
[ 1.516970] 0x000006000000-0x000008000000 : "ramfs-bak"
[ 1.532384] 0x000008000000-0x000010000000 : "reserve1"
[ 1.551389] NET: Registered protocol family 10
[ 1.565997] sit: IPv6 over IPv4 tunneling driver
[ 1.570216] NET: Registered protocol family 17
[ 1.573521] can: controller area network core (rev 20120528 abi 9)
[ 1.578359] NET: Registered protocol family 29
[ 1.581495] can: raw protocol (rev 20120528)
[ 1.584395] can: broadcast manager protocol (rev 20120528 t)
[ 1.588742] can: netlink gateway (rev 20130117) max_hops=1
[ 1.593210] zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
[ 1.599036] zynq_pm_late_init: Unable to map DDRC IO memory.
[ 1.603600] Registering SWP/SWPB emulation handler
[ 1.608925] hctosys: unable to open rtc device (rtc0)
[ 1.613182] ALSA device list:
[ 1.614755] No soundcards found.
[ 1.617214] RAMDISK: gzip image found at block 0
[ 4.183281] EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
[ 4.200756] EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
[ 4.206617] VFS: Mounted root (ext4 filesystem) on device 1:0.
[ 4.211226] devtmpfs: mounted
[ 4.214000] Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
[ 4.398523] EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
[ 4.425390] random: dd urandom read with 0 bits of entropy available
[ 4.473709] ubi0: attaching mtd2
[ 4.506219] ubi0: scanning is finished
[ 4.515229] ubi0: attached mtd2 (name "configs", size 8 MiB)
[ 4.519506] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 4.525255] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 4.530650] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 4.536407] ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
[ 4.540936] ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
[ 4.546878] ubi0: max/mean erase counter: 17/7, WL threshold: 4096, image sequence number: 237714726
[ 4.554690] ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
[ 4.562520] ubi0: background thread "ubi_bgt0d" started, PID 709
[ 4.580339] UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 712
[ 4.613332] UBIFS (ubi0:0): recovery needed
[ 4.695242] UBIFS (ubi0:0): recovery completed
[ 4.698298] UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
[ 4.704507] UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 4.713073] UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
[ 4.721745] UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
[ 4.726683] UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID FF09433B-E002-4C29-97EC-6220DDC4BB36, small LPT model
[ 4.759758] ubi1: attaching mtd5
[ 5.248389] ubi1: scanning is finished
[ 5.258690] ubi1: attached mtd5 (name "reserve1", size 128 MiB)
[ 5.263392] ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 5.268875] ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 5.274405] ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 5.279985] ubi1: good PEBs: 1020, bad PEBs: 4, corrupted PEBs: 0
[ 5.284797] ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
[ 5.290664] ubi1: max/mean erase counter: 3723/736, WL threshold: 4096, image sequence number: 3265111179
[ 5.298943] ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
[ 5.306938] ubi1: background thread "ubi_bgt1d" started, PID 721
[ 5.321227] UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 724
[ 5.357973] UBIFS (ubi1:0): recovery needed
[ 5.475411] UBIFS (ubi1:0): recovery completed
[ 5.478474] UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
[ 5.484746] UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 5.493333] UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
[ 5.502614] UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
[ 5.507901] UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 1AF6F1E1-61F0-462C-AE44-C7D9596CF7E2, small LPT model
[ 6.239438] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 6.268417] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 6.273123] macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
[ 6.273134] macb e000b000.ethernet eth0: link up (100/Full)
[ 6.284419] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 19.738347] In axi fpga driver!
[ 19.747888] request_mem_region OK!
[ 19.757112] AXI fpga dev virtual address is 0xcfb38000
[ 19.768053] *base_vir_addr = 0xb023
[ 19.810912] In fpga mem driver!
[ 19.816717] request_mem_region OK!
[ 19.820239] fpga mem virtual address is 0xd2000000
[ 243.450382] random: nonblocking pool is initialized
2022-05-14 14:31:12 Read tune config: tune_profile=4, tune_status=1, tune_frequency=500, tune_voltage=1880, tune_freq_step=5, tune_volt_step=20, tune_max_frequency=525, tune_power=2650, tune_bad_domains_threshold=1, tune_max_voltage=1900, tune_freq_yellow_step=10, tune_max_restarts=10, tune_restarts=2, voltage_increase=20, voltage_pre_heat_delay=30, tune_decrease_voltage_mode=1, tune_uptime=240, tune_chain_statuses=4, tune_bad_freq_step=25
2022-05-14 14:31:12 driver/driver-btm-api.c:278:init_freq_mode: This is scan-user version
2022-05-14 14:31:12 driver/driver-btm-api.c:1990:bitmain_soc_init: opt_multi_version = 1
2022-05-14 14:31:12 driver/driver-btm-api.c:1991:bitmain_soc_init: opt_bitmain_ab = 1
2022-05-14 14:31:12 driver/driver-btm-api.c:1992:bitmain_soc_init: opt_bitmain_work_mode = 0
2022-05-14 14:31:12 driver/driver-btm-api.c:1993:bitmain_soc_init: Miner compile time: Fri Apr 3 15:30:33 UTC 2020 type: Antminer S17+ Hiveon
2022-05-14 14:31:12 driver/driver-btm-api.c:1995:bitmain_soc_init: commit version: 3f36039 2020-04-01 16:04:28, build by: user 2020-04-01 19:37:05
2022-05-14 14:31:12 driver/driver-btm-api.c:1628:show_sn: 803c25064e10481c Zv
2022-05-14 14:31:12 driver/driver-btm-api.c:1636:show_sn: no SN got, please write SN to /nvdata/sn
2022-05-14 14:31:12 driver/fan.c:211:front_fan_power_on: Note: front fan is power on!
2022-05-14 14:31:12 driver/fan.c:217:rear_fan_power_on: Note: rear fan is power on!
2022-05-14 14:31:12 driver/driver-btm-api.c:1690:miner_device_init: Detect 256MB control board of XILINX
2022-05-14 14:31:12 driver/driver-btm-api.c:1664:init_fan_parameter: fan_eft : 0 fan_pwm : 100
2022-05-14 14:31:18 driver/driver-btm-api.c:1315:init_miner_version: miner ID : 803c25064e10481c
2022-05-14 14:31:18 driver/driver-btm-api.c:1320:init_miner_version: FPGA Version = 0xB023
2022-05-14 14:31:23 driver/thread.c:1671:create_read_nonce_reg_thread: create thread
2022-05-14 14:31:23 driver/driver-btm-api.c:1371:bitmain_board_init: product_id[0] = 0
2022-05-14 14:31:23 driver/driver-btm-api.c:1371:bitmain_board_init: product_id[1] = 0
2022-05-14 14:31:23 driver/driver-btm-api.c:1371:bitmain_board_init: product_id[2] = 0
2022-05-14 14:31:23 driver/driver-btm-api.c:1392:bitmain_board_init: project:0
2022-05-14 14:31:23 driver/driver-btm-api.c:1450:bitmain_board_init: Project type: Antminer S17+
2022-05-14 14:31:23 driver/driver-btm-api.c:1017:dump_pcb_bom_version: Chain
2022-05-14 14:31:23 driver/driver-btm-api.c:1018:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-05-14 14:31:23 driver/driver-btm-api.c:1017:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2022-05-14 14:31:23 driver/driver-btm-api.c:1018:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-05-14 14:31:25 driver/driver-btm-api.c:1489:bitmain_board_init: Fan check passed.
2022-05-14 14:31:26 driver/board.c:31:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2022-05-14 14:31:30 driver/board.c:34:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2022-05-14 14:31:31 driver/board.c:31:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-05-14 14:31:35 driver/board.c:34:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2022-05-14 14:31:35 driver/board.c:31:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-05-14 14:31:40 driver/board.c:34:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2022-05-14 14:31:40 driver/thread.c:1666:create_pic_heart_beat_thread: create thread
2022-05-14 14:31:40 driver/power_api.c:191:power_init: power init ...
2022-05-14 14:31:40 driver/power_api.c:265:power_init: highest_voltage = 21.000000
2022-05-14 14:31:40 driver/power_api.c:266:power_init: working_voltage = 19.500000
2022-05-14 14:31:40 driver/power_api.c:267:power_init: higher_voltage = 20.400000
2022-05-14 14:31:40 driver/driver-btm-api.c:1500:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2022-05-14 14:31:40 driver/power_api.c:177:power_off: init gpio907
2022-05-14 14:32:12 driver/power_api.c:448:set_to_highest_voltage: setting to voltage: 21.00 ...
2022-05-14 14:32:14 driver/power_api.c:571:check_voltage_multi: retry time: 0
2022-05-14 14:32:15 driver/power_api.c:539:_get_avg_voltage: average voltage = 21.105755
2022-05-14 14:32:15 driver/power_api.c:557:check_voltage: target_vol = 21.00, actural_vol = 21.11, check voltage passed.
2022-05-14 14:32:15 driver/uart.c:49:set_baud: set UART baud to 115200
2022-05-14 14:32:21 driver/driver-btm-api.c:1173:check_asic_number_with_power_on: Chain[0]: find 20 asic, times 0
2022-05-14 14:32:27 driver/driver-btm-api.c:1173:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 1
2022-05-14 14:32:32 driver/driver-btm-api.c:1173:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 2
2022-05-14 14:32:32 driver/driver-btm-api.c:1187:check_asic_number_with_power_on: Chain 0 only find 0 asic, will power off hash board 0
2022-05-14 14:32:38 driver/driver-btm-api.c:1173:check_asic_number_with_power_on: Chain[1]: find 28 asic, times 0
2022-05-14 14:32:44 driver/driver-btm-api.c:1173:check_asic_number_with_power_on: Chain[1]: find 28 asic, times 1
2022-05-14 14:32:49 driver/driver-btm-api.c:1173:check_asic_number_with_power_on: Chain[1]: find 28 asic, times 2
2022-05-14 14:32:49 driver/driver-btm-api.c:1187:check_asic_number_with_power_on: Chain 1 only find 28 asic, will power off hash board 1
2022-05-14 14:32:55 driver/driver-btm-api.c:1173:check_asic_number_with_power_on: Chain[2]: find 65 asic, times 0
2022-05-14 14:32:58 driver/driver-hash-chip.c:100:set_uart_relay: set uart relay to 0x330003
2022-05-14 14:32:58 driver/driver-btm-api.c:1000:set_order_clock: chain[2]: set order clock, stragegy 3
2022-05-14 14:32:58 driver/driver-hash-chip.c:292:set_clock_delay_control: core_data = 0x34
2022-05-14 14:32:58 voltage[2] = 1900
2022-05-14 14:32:58 Highest voltage is 21.00
2022-05-14 14:32:58 driver/power_api.c:279:set_working_voltage: working_voltage = 19.200000
2022-05-14 14:33:00 driver/temperature.c:321:calibrate_temp_sensor_all_chains: chain 2 temp sensor NCT218, offset -8
2022-05-14 14:33:00 driver/uart.c:49:set_baud: set UART baud to 12000000
2022-05-14 14:33:00 driver/driver-btm-api.c:662:check_bringup_temp: Bring up temperature is 23
2022-05-14 14:33:00 driver/thread.c:1686:create_check_miner_status_thread: create thread
2022-05-14 14:33:00 driver/thread.c:1676:create_set_miner_status_thread: create thread
2022-05-14 14:33:00 driver/thread.c:1701:create_auto_tune_thread: create thread
2022-05-14 14:33:00 driver/thread.c:1706:create_read_real_voltage_thread: create thread
2022-05-14 14:33:00 driver/frequency.c:759:inc_freq_with_fixed_vco: chain = 255, freq = 475, is_higher_voltage = true
2022-05-14 14:33:17 driver/driver-btm-api.c:983:set_timeout: freq = 475, percent = 90, hcn = 44236, timeout = 93
2022-05-14 14:33:17 driver/power_api.c:773:set_to_working_voltage_by_steps: Set to voltage 19.20, step by step.
2022-05-14 14:33:21 driver/power_api.c:571:check_voltage_multi: retry time: 0
2022-05-14 14:33:21 driver/power_api.c:539:_get_avg_voltage: average voltage = 19.291560
2022-05-14 14:33:21 driver/power_api.c:557:check_voltage: target_vol = 19.20, actural_vol = 19.29, check voltage passed.
2022-05-14 14:33:22 driver/power_api.c:497:get_average_voltage: average_voltage = 19.267263
2022-05-14 14:33:22 driver/thread.c:1661:create_temperature_monitor_thread: create thread
2022-05-14 14:33:22 driver/thread.c:1681:create_check_system_status_thread: create thread
2022-05-14 14:33:22 driver/thread.c:1693:create_read_hash_rate_thread: create thread
2022-05-14 14:33:23 driver/driver-btm-api.c:2219:bitmain_soc_init: Init done!
2022-05-14 14:33:23 driver/driver-btm-api.c:204:set_miner_status: STATUS_INIT
2022-05-14 14:33:23 driver/driver-btm-api.c:204:set_miner_status: STATUS_OKAY
2022-05-14 14:33:28 driver/driver-btm-api.c:2461:dhash_chip_send_job: Version num
[ 0.000000] Linux version 4.6.0-xilinx-gff8137b-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #25 SMP PREEMPT Fri Nov 23 15:30:52 CST 2018
[ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Xilinx Zynq
[ 0.000000] cma: Reserved 16 MiB at 0x0e000000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] On node 0 totalpages: 61440
[ 0.000000] free_area_init_node: node 0, pgdat c0b39280, node_mem_map cde10000
[ 0.000000] Normal zone: 480 pages used for memmap
[ 0.000000] Normal zone: 0 pages reserved
[ 0.000000] Normal zone: 61440 pages, LIFO batch:15
[ 0.000000] percpu: Embedded 12 pages/cpu @cddf1000 s19776 r8192 d21184 u49152
[ 0.000000] pcpu-alloc: s19776 r8192 d21184 u49152 alloc=12*4096
[ 0.000000] pcpu-alloc:
- 0
- 1
[ 0.000000] Kernel command line: mem=240M console=ttyPS0,115200 ramdisk_size=33554432 root=/dev/ram rw earlyprintk
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Memory: 193872K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 35504K reserved, 16384K cma-reserved, 0K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xcf800000 - 0xff800000 ( 768 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xcf000000 ( 240 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .text : 0xc0008000 - 0xc090c424 (9234 kB)
[ 0.000000] .init : 0xc0a00000 - 0xc0b00000 (1024 kB)
[ 0.000000] .data : 0xc0b00000 - 0xc0b39fe0 ( 232 kB)
[ 0.000000] .bss : 0xc0b39fe0 - 0xc0b71c28 ( 224 kB)
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] Build-time adjustment of leaf fanout to 32.
[ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=32, nr_cpu_ids=2
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] efuse mapped to cf800000
[ 0.000000] ps7-slcr mapped to cf802000
[ 0.000000] L2C: platform modifies aux control register: 0x72360000 -> 0x72760000
[ 0.000000] L2C: DT/platform modifies aux control register: 0x72360000 -> 0x72760000
[ 0.000000] L2C-310 erratum 769419 enabled
[ 0.000000] L2C-310 enabling early BRESP for Cortex-A9
[ 0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[ 0.000000] L2C-310 ID prefetch enabled, offset 1 lines
[ 0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[ 0.000000] L2C-310 cache controller enabled, 8 ways, 512 kB
[ 0.000000] L2C-310: CACHE_ID 0x410000c8, AUX_CTRL 0x76760001
[ 0.000000] zynq_clock_init: clkc starts at cf802100
[ 0.000000] Zynq clock init
[ 0.000011] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 4398046511103ns
[ 0.000030] clocksource: arm_global_timer: mask: 0xffffffffffffffff max_cycles: 0x4ce07af025, max_idle_ns: 440795209040 ns
[ 0.000054] Switching to timer-based delay loop, resolution 3ns
[ 0.000293] clocksource: ttc_clocksource: mask: 0xffff max_cycles: 0xffff, max_idle_ns: 537538477 ns
[ 0.000319] ps7-ttc #0 at cf80a000, irq=18
[ 0.000554] Console: colour dummy device 80x30
[ 0.000570] Calibrating delay loop (skipped), value calculated using timer frequency.. 666.66 BogoMIPS (lpj=3333333)
[ 0.000584] pid_max: default: 32768 minimum: 301
[ 0.000712] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000722] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.001328] CPU: Testing write buffer coherency: ok
[ 0.001530] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.001583] Setting up static identity map for 0x100000 - 0x100058
[ 0.100279] CPU1: failed to boot: -1
[ 0.100309] Brought up 1 CPUs
[ 0.100318] SMP: Total of 1 processors activated (666.66 BogoMIPS).
[ 0.100324] CPU: All CPU(s) started in SVC mode.
[ 0.101115] devtmpfs: initialized
[ 0.103197] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 0.103631] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.104580] pinctrl core: initialized pinctrl subsystem
[ 0.105689] NET: Registered protocol family 16
[ 0.107444] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.150232] cpuidle: using governor menu
[ 0.159126] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[ 0.159136] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.159283] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xcf880000
[ 0.220810] vgaarb: loaded
[ 0.221160] SCSI subsystem initialized
[ 0.221440] usbcore: registered new interface driver usbfs
[ 0.221509] usbcore: registered new interface driver hub
[ 0.221943] usbcore: registered new device driver usb
[ 0.222487] media: Linux media interface: v0.10
[ 0.222601] Linux video capture interface: v2.00
[ 0.222759] pps_core: LinuxPPS API ver. 1 registered
[ 0.222767] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.222850] PTP clock support registered
[ 0.223029] EDAC MC: Ver: 3.0.0
[ 0.230624] Advanced Linux Sound Architecture Driver Initialized.
[ 0.241223] clocksource: Switched to clocksource arm_global_timer
[ 0.259551] NET: Registered protocol family 2
[ 0.260553] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.260589] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.260634] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.260683] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.260710] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.260916] NET: Registered protocol family 1
[ 0.271594] RPC: Registered named UNIX socket transport module.
[ 0.271602] RPC: Registered udp transport module.
[ 0.271608] RPC: Registered tcp transport module.
[ 0.271613] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.271636] PCI: CLS 0 bytes, default 64
[ 0.271857] Trying to unpack rootfs image as initramfs...
[ 0.272448] rootfs image is not initramfs (no cpio magic); looks like an initrd
[ 0.368042] Freeing initrd memory: 22464K (cc511000 - cdb01000)
[ 0.368388] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[ 0.370189] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 0.381981] workingset: timestamp_bits=28 max_order=16 bucket_order=0
[ 0.392825] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 0.393953] io scheduler noop registered
[ 0.393970] io scheduler deadline registered
[ 0.393999] io scheduler cfq registered (default)
[ 0.395675] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-241330
[ 0.395689] dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16
[ 0.396856] e0000000.serial: ttyPS0 at MMIO 0xe0000000 (irq = 158, base_baud = 6249999) is a xuartps
[ 0.900915] console [ttyPS0] enabled
[ 0.903809] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to cf86e000
[ 0.909981] [drm] Initialized drm 1.1.0 20060810
[ 1.087612] brd: module loaded
[ 1.176549] loop: module loaded
[ 1.180498] CAN device driver interface
[ 1.186407] gpiod_set_value: invalid GPIO
[ 1.190186] libphy: MACB_mii_bus: probed
[ 1.271289] macb e000b000.ethernet eth0: Cadence GEM rev 0x00020118 at 0xe000b000 irq 31 (00:0a:35:00:00:00)
[ 1.279733] Generic PHY e000b000.etherne:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=e000b000.etherne:00, irq=-1)
[ 1.290031] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[ 1.294574] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 1.300452] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.306069] ehci-pci: EHCI PCI platform driver
[ 1.309377] usbcore: registered new interface driver usb-storage
[ 1.315929] mousedev: PS/2 mouse device common for all mice
[ 1.331304] i2c /dev entries driver
[ 1.336386] Xilinx Zynq CpuIdle Driver started
[ 1.340727] sdhci: Secure Digital Host Controller Interface driver
[ 1.345629] sdhci: Copyright(c) Pierre Ossman
[ 1.348606] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.392360] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA
[ 1.399267] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.404546] usbcore: registered new interface driver usbhid
[ 1.408726] usbhid: USB HID core driver
[ 1.412620] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[ 1.417581] nand: Micron MT29F2G08ABAGAWP
[ 1.420275] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
[ 1.426914] nand: WARNING: pl35x-nand: the ECC used on your system is too weak compared to the one required by the NAND chip
[ 1.437072] Bad block table found at page 131008, version 0x01
[ 1.442029] Bad block table found at page 130944, version 0x01
[ 1.446800] 6 ofpart partitions found on MTD device pl35x-nand
[ 1.451319] Creating 6 MTD partitions on "pl35x-nand":
[ 1.455068] 0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
[ 1.471774] 0x000002800000-0x000004800000 : "ramfs"
[ 1.486774] 0x000004800000-0x000005000000 : "configs"
[ 1.501864] 0x000005000000-0x000006000000 : "reserve"
[ 1.516970] 0x000006000000-0x000008000000 : "ramfs-bak"
[ 1.532384] 0x000008000000-0x000010000000 : "reserve1"
[ 1.551389] NET: Registered protocol family 10
[ 1.565997] sit: IPv6 over IPv4 tunneling driver
[ 1.570216] NET: Registered protocol family 17
[ 1.573521] can: controller area network core (rev 20120528 abi 9)
[ 1.578359] NET: Registered protocol family 29
[ 1.581495] can: raw protocol (rev 20120528)
[ 1.584395] can: broadcast manager protocol (rev 20120528 t)
[ 1.588742] can: netlink gateway (rev 20130117) max_hops=1
[ 1.593210] zynq_pm_ioremap: no compatible node found for 'xlnx,zynq-ddrc-a05'
[ 1.599036] zynq_pm_late_init: Unable to map DDRC IO memory.
[ 1.603600] Registering SWP/SWPB emulation handler
[ 1.608925] hctosys: unable to open rtc device (rtc0)
[ 1.613182] ALSA device list:
[ 1.614755] No soundcards found.
[ 1.617214] RAMDISK: gzip image found at block 0
[ 4.183281] EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities
[ 4.200756] EXT4-fs (ram0): mounted filesystem without journal. Opts: (null)
[ 4.206617] VFS: Mounted root (ext4 filesystem) on device 1:0.
[ 4.211226] devtmpfs: mounted
[ 4.214000] Freeing unused kernel memory: 1024K (c0a00000 - c0b00000)
[ 4.398523] EXT4-fs (ram0): re-mounted. Opts: block_validity,delalloc,barrier,user_xattr
[ 4.425390] random: dd urandom read with 0 bits of entropy available
[ 4.473709] ubi0: attaching mtd2
[ 4.506219] ubi0: scanning is finished
[ 4.515229] ubi0: attached mtd2 (name "configs", size 8 MiB)
[ 4.519506] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 4.525255] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 4.530650] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 4.536407] ubi0: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
[ 4.540936] ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
[ 4.546878] ubi0: max/mean erase counter: 17/7, WL threshold: 4096, image sequence number: 237714726
[ 4.554690] ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
[ 4.562520] ubi0: background thread "ubi_bgt0d" started, PID 709
[ 4.580339] UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 712
[ 4.613332] UBIFS (ubi0:0): recovery needed
[ 4.695242] UBIFS (ubi0:0): recovery completed
[ 4.698298] UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "configs"
[ 4.704507] UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 4.713073] UBIFS (ubi0:0): FS size: 1396736 bytes (1 MiB, 11 LEBs), journal size 888833 bytes (0 MiB, 5 LEBs)
[ 4.721745] UBIFS (ubi0:0): reserved for root: 65970 bytes (64 KiB)
[ 4.726683] UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID FF09433B-E002-4C29-97EC-6220DDC4BB36, small LPT model
[ 4.759758] ubi1: attaching mtd5
[ 5.248389] ubi1: scanning is finished
[ 5.258690] ubi1: attached mtd5 (name "reserve1", size 128 MiB)
[ 5.263392] ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 5.268875] ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 5.274405] ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 5.279985] ubi1: good PEBs: 1020, bad PEBs: 4, corrupted PEBs: 0
[ 5.284797] ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
[ 5.290664] ubi1: max/mean erase counter: 3723/736, WL threshold: 4096, image sequence number: 3265111179
[ 5.298943] ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
[ 5.306938] ubi1: background thread "ubi_bgt1d" started, PID 721
[ 5.321227] UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 724
[ 5.357973] UBIFS (ubi1:0): recovery needed
[ 5.475411] UBIFS (ubi1:0): recovery completed
[ 5.478474] UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
[ 5.484746] UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 5.493333] UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
[ 5.502614] UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
[ 5.507901] UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 1AF6F1E1-61F0-462C-AE44-C7D9596CF7E2, small LPT model
[ 6.239438] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 6.268417] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 6.273123] macb e000b000.ethernet eth0: unable to generate target frequency: 25000000 Hz
[ 6.273134] macb e000b000.ethernet eth0: link up (100/Full)
[ 6.284419] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 19.738347] In axi fpga driver!
[ 19.747888] request_mem_region OK!
[ 19.757112] AXI fpga dev virtual address is 0xcfb38000
[ 19.768053] *base_vir_addr = 0xb023
[ 19.810912] In fpga mem driver!
[ 19.816717] request_mem_region OK!
[ 19.820239] fpga mem virtual address is 0xd2000000
[ 243.450382] random: nonblocking pool is initialized
2022-05-14 14:31:12 Read tune config: tune_profile=4, tune_status=1, tune_frequency=500, tune_voltage=1880, tune_freq_step=5, tune_volt_step=20, tune_max_frequency=525, tune_power=2650, tune_bad_domains_threshold=1, tune_max_voltage=1900, tune_freq_yellow_step=10, tune_max_restarts=10, tune_restarts=2, voltage_increase=20, voltage_pre_heat_delay=30, tune_decrease_voltage_mode=1, tune_uptime=240, tune_chain_statuses=4, tune_bad_freq_step=25
2022-05-14 14:31:12 driver/driver-btm-api.c:278:init_freq_mode: This is scan-user version
2022-05-14 14:31:12 driver/driver-btm-api.c:1990:bitmain_soc_init: opt_multi_version = 1
2022-05-14 14:31:12 driver/driver-btm-api.c:1991:bitmain_soc_init: opt_bitmain_ab = 1
2022-05-14 14:31:12 driver/driver-btm-api.c:1992:bitmain_soc_init: opt_bitmain_work_mode = 0
2022-05-14 14:31:12 driver/driver-btm-api.c:1993:bitmain_soc_init: Miner compile time: Fri Apr 3 15:30:33 UTC 2020 type: Antminer S17+ Hiveon
2022-05-14 14:31:12 driver/driver-btm-api.c:1995:bitmain_soc_init: commit version: 3f36039 2020-04-01 16:04:28, build by: user 2020-04-01 19:37:05
2022-05-14 14:31:12 driver/driver-btm-api.c:1628:show_sn: 803c25064e10481c Zv
2022-05-14 14:31:12 driver/driver-btm-api.c:1636:show_sn: no SN got, please write SN to /nvdata/sn
2022-05-14 14:31:12 driver/fan.c:211:front_fan_power_on: Note: front fan is power on!
2022-05-14 14:31:12 driver/fan.c:217:rear_fan_power_on: Note: rear fan is power on!
2022-05-14 14:31:12 driver/driver-btm-api.c:1690:miner_device_init: Detect 256MB control board of XILINX
2022-05-14 14:31:12 driver/driver-btm-api.c:1664:init_fan_parameter: fan_eft : 0 fan_pwm : 100
2022-05-14 14:31:18 driver/driver-btm-api.c:1315:init_miner_version: miner ID : 803c25064e10481c
2022-05-14 14:31:18 driver/driver-btm-api.c:1320:init_miner_version: FPGA Version = 0xB023
2022-05-14 14:31:23 driver/thread.c:1671:create_read_nonce_reg_thread: create thread
2022-05-14 14:31:23 driver/driver-btm-api.c:1371:bitmain_board_init: product_id[0] = 0
2022-05-14 14:31:23 driver/driver-btm-api.c:1371:bitmain_board_init: product_id[1] = 0
2022-05-14 14:31:23 driver/driver-btm-api.c:1371:bitmain_board_init: product_id[2] = 0
2022-05-14 14:31:23 driver/driver-btm-api.c:1392:bitmain_board_init: project:0
2022-05-14 14:31:23 driver/driver-btm-api.c:1450:bitmain_board_init: Project type: Antminer S17+
2022-05-14 14:31:23 driver/driver-btm-api.c:1017:dump_pcb_bom_version: Chain
- PCB Version: 0x0100
- BOM Version: 0x0100
2022-05-14 14:31:23 driver/driver-btm-api.c:1018:dump_pcb_bom_version: Chain [1] BOM Version: 0x0100
2022-05-14 14:31:23 driver/driver-btm-api.c:1017:dump_pcb_bom_version: Chain [2] PCB Version: 0x0100
2022-05-14 14:31:23 driver/driver-btm-api.c:1018:dump_pcb_bom_version: Chain [2] BOM Version: 0x0100
2022-05-14 14:31:25 driver/driver-btm-api.c:1489:bitmain_board_init: Fan check passed.
2022-05-14 14:31:26 driver/board.c:31:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2022-05-14 14:31:30 driver/board.c:34:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0x88
2022-05-14 14:31:31 driver/board.c:31:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2022-05-14 14:31:35 driver/board.c:34:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0x88
2022-05-14 14:31:35 driver/board.c:31:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2022-05-14 14:31:40 driver/board.c:34:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0x88
2022-05-14 14:31:40 driver/thread.c:1666:create_pic_heart_beat_thread: create thread
2022-05-14 14:31:40 driver/power_api.c:191:power_init: power init ...
2022-05-14 14:31:40 driver/power_api.c:265:power_init: highest_voltage = 21.000000
2022-05-14 14:31:40 driver/power_api.c:266:power_init: working_voltage = 19.500000
2022-05-14 14:31:40 driver/power_api.c:267:power_init: higher_voltage = 20.400000
2022-05-14 14:31:40 driver/driver-btm-api.c:1500:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2022-05-14 14:31:40 driver/power_api.c:177:power_off: init gpio907
2022-05-14 14:32:12 driver/power_api.c:448:set_to_highest_voltage: setting to voltage: 21.00 ...
2022-05-14 14:32:14 driver/power_api.c:571:check_voltage_multi: retry time: 0
2022-05-14 14:32:15 driver/power_api.c:539:_get_avg_voltage: average voltage = 21.105755
2022-05-14 14:32:15 driver/power_api.c:557:check_voltage: target_vol = 21.00, actural_vol = 21.11, check voltage passed.
2022-05-14 14:32:15 driver/uart.c:49:set_baud: set UART baud to 115200
2022-05-14 14:32:21 driver/driver-btm-api.c:1173:check_asic_number_with_power_on: Chain[0]: find 20 asic, times 0
2022-05-14 14:32:27 driver/driver-btm-api.c:1173:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 1
2022-05-14 14:32:32 driver/driver-btm-api.c:1173:check_asic_number_with_power_on: Chain[0]: find 0 asic, times 2
2022-05-14 14:32:32 driver/driver-btm-api.c:1187:check_asic_number_with_power_on: Chain 0 only find 0 asic, will power off hash board 0
2022-05-14 14:32:38 driver/driver-btm-api.c:1173:check_asic_number_with_power_on: Chain[1]: find 28 asic, times 0
2022-05-14 14:32:44 driver/driver-btm-api.c:1173:check_asic_number_with_power_on: Chain[1]: find 28 asic, times 1
2022-05-14 14:32:49 driver/driver-btm-api.c:1173:check_asic_number_with_power_on: Chain[1]: find 28 asic, times 2
2022-05-14 14:32:49 driver/driver-btm-api.c:1187:check_asic_number_with_power_on: Chain 1 only find 28 asic, will power off hash board 1
2022-05-14 14:32:55 driver/driver-btm-api.c:1173:check_asic_number_with_power_on: Chain[2]: find 65 asic, times 0
2022-05-14 14:32:58 driver/driver-hash-chip.c:100:set_uart_relay: set uart relay to 0x330003
2022-05-14 14:32:58 driver/driver-btm-api.c:1000:set_order_clock: chain[2]: set order clock, stragegy 3
2022-05-14 14:32:58 driver/driver-hash-chip.c:292:set_clock_delay_control: core_data = 0x34
2022-05-14 14:32:58 voltage[2] = 1900
2022-05-14 14:32:58 Highest voltage is 21.00
2022-05-14 14:32:58 driver/power_api.c:279:set_working_voltage: working_voltage = 19.200000
2022-05-14 14:33:00 driver/temperature.c:321:calibrate_temp_sensor_all_chains: chain 2 temp sensor NCT218, offset -8
2022-05-14 14:33:00 driver/uart.c:49:set_baud: set UART baud to 12000000
2022-05-14 14:33:00 driver/driver-btm-api.c:662:check_bringup_temp: Bring up temperature is 23
2022-05-14 14:33:00 driver/thread.c:1686:create_check_miner_status_thread: create thread
2022-05-14 14:33:00 driver/thread.c:1676:create_set_miner_status_thread: create thread
2022-05-14 14:33:00 driver/thread.c:1701:create_auto_tune_thread: create thread
2022-05-14 14:33:00 driver/thread.c:1706:create_read_real_voltage_thread: create thread
2022-05-14 14:33:00 driver/frequency.c:759:inc_freq_with_fixed_vco: chain = 255, freq = 475, is_higher_voltage = true
2022-05-14 14:33:17 driver/driver-btm-api.c:983:set_timeout: freq = 475, percent = 90, hcn = 44236, timeout = 93
2022-05-14 14:33:17 driver/power_api.c:773:set_to_working_voltage_by_steps: Set to voltage 19.20, step by step.
2022-05-14 14:33:21 driver/power_api.c:571:check_voltage_multi: retry time: 0
2022-05-14 14:33:21 driver/power_api.c:539:_get_avg_voltage: average voltage = 19.291560
2022-05-14 14:33:21 driver/power_api.c:557:check_voltage: target_vol = 19.20, actural_vol = 19.29, check voltage passed.
2022-05-14 14:33:22 driver/power_api.c:497:get_average_voltage: average_voltage = 19.267263
2022-05-14 14:33:22 driver/thread.c:1661:create_temperature_monitor_thread: create thread
2022-05-14 14:33:22 driver/thread.c:1681:create_check_system_status_thread: create thread
2022-05-14 14:33:22 driver/thread.c:1693:create_read_hash_rate_thread: create thread
2022-05-14 14:33:23 driver/driver-btm-api.c:2219:bitmain_soc_init: Init done!
2022-05-14 14:33:23 driver/driver-btm-api.c:204:set_miner_status: STATUS_INIT
2022-05-14 14:33:23 driver/driver-btm-api.c:204:set_miner_status: STATUS_OKAY
2022-05-14 14:33:28 driver/driver-btm-api.c:2461:dhash_chip_send_job: Version num
at 24 x 150w its 3.6Kwh. so you need to produce at least 32.000 Kwh/year.
In order to do so, the minimum with the best orientation / inclination is 24 KW installed with a bare minimum of 48 Kwh battery pack . Cost in euro for such, vat included is maximum 2400 euro/kw + 1000 euro/Kwh for the battery itself. So its 57600 euro + 48000 euro a whopping total of 100.000 euro
So, at least in my country, this is NOT a civil installation, but an industrial one.
In fact the biggest similar I did ( and I do PV for a living) is just the half of what you think of.
A Fronious 24 10KW, with a 13.2 Kw of Sungrow panel installed and a 22 Kwh Byd battery
This is running in a NZE house and every watt that is not needed for the house goes towards 2 rig of Manli 3060ti Lhr that are operating with 2 different configuration: High, low for each rig.
The BYD interface does give information on the battery charges
When the battery is really low, mining is switched off. If the projection indicated that battery will be low that day miner is switching on low(Ton
)
Keep in mind that people did that just because of the sizable incentive of converting a normal house on a NZE house. Mining isn't not what's driving this, its just a nice way of optimizing the ROI
In order to do so, the minimum with the best orientation / inclination is 24 KW installed with a bare minimum of 48 Kwh battery pack . Cost in euro for such, vat included is maximum 2400 euro/kw + 1000 euro/Kwh for the battery itself. So its 57600 euro + 48000 euro a whopping total of 100.000 euro
So, at least in my country, this is NOT a civil installation, but an industrial one.
In fact the biggest similar I did ( and I do PV for a living) is just the half of what you think of.
A Fronious 24 10KW, with a 13.2 Kw of Sungrow panel installed and a 22 Kwh Byd battery
This is running in a NZE house and every watt that is not needed for the house goes towards 2 rig of Manli 3060ti Lhr that are operating with 2 different configuration: High, low for each rig.
The BYD interface does give information on the battery charges
When the battery is really low, mining is switched off. If the projection indicated that battery will be low that day miner is switching on low(Ton
)Keep in mind that people did that just because of the sizable incentive of converting a normal house on a NZE house. Mining isn't not what's driving this, its just a nice way of optimizing the ROI
I have no knowledge about it, however why only 24kW+48kWh battery, when his rigs would need 3.6x24=86.4kWh/day?
thank you
Hi guys,
i own Ryzen 7 5800X and wanted to ask what is there for mining on this cpu? i know about randomx Monero, but is there anything else? i checked whattomine and coincalculator.io and they dont have section for CPU.
thank you in advance
i own Ryzen 7 5800X and wanted to ask what is there for mining on this cpu? i know about randomx Monero, but is there anything else? i checked whattomine and coincalculator.io and they dont have section for CPU.
thank you in advance
The full speed of the card is unlocked in the GPU settings,for example in Afterburner which is a program to fine tune GPU settings.Correct settings for the RTX 3060 non LHR to get full speed at 49 Mhsh at 115 watts are as below :
Core clock -200
Memory Clock +1400
Fan settings-Whichever works best for you I use 60-75%
Core clock -200
Memory Clock +1400
Fan settings-Whichever works best for you I use 60-75%
are you using -lhr argument in bat file?
what driver u use? because i am using afterburner (PL 66, C0 M+1250) and 470.55driver and it wont work properly in my pc (with 2 cards only).
ok going to try newest driver and will see how it goes.
thank you
I have seen a lot of good offers for the RTX 3060 ti lately as little as 800 EUR new in box which for me is a good price.I have seen the normal hash rate of 31 Mhsh maximum.
My question is,can this card go up to at least 45-48 Mhsh with the unlocking that NBminer has done,does the unlock works in Windows or only in HiveOS.I am asking because I never have dealt with a LHR card but I am seriously thinking to expand my capacity in mining and this looks like a good option to me considering I got near this price the Gtx 1080 ti and used.
Read thisMy question is,can this card go up to at least 45-48 Mhsh with the unlocking that NBminer has done,does the unlock works in Windows or only in HiveOS.I am asking because I never have dealt with a LHR card but I am seriously thinking to expand my capacity in mining and this looks like a good option to me considering I got near this price the Gtx 1080 ti and used.
https://www.reddit.com/r/EtherMining/comments/okq6dh/3060_lhr_mines_at_397_mhs_with_miniz_miner/?
RTX 3080 Ti LHR: ~80 Mh/s | RTX 3080 no LHR: ~90 Mh/s
RTX 3070 Ti LHR: ~55 Mh/s | RTX 3070 no LHR: ~65 Mh/s
RTX 3060 Ti LHR: ~40 Mh/s | RTX 3060 no LHR: ~50 Mh/s
https://bitok.shop/blog/bitok/razblokirovka-videokart-lhr-3060-3070-3080-dlya-mayninga-instruktsiya-sravnenie-kheshreyta-i-dokhodnosti-2021-1/?
But know that electricity consumption will double
Use Windows if you prefer, just install the correct driver.
i have RTX 3060 (non LHR version) please can you help me how should i set up my bat file? i know the pool and worker staff, but what do i need to use to unlock it to full speed?
also what is the driver requirement? currently using 470.55 with 2 cards but want to move to my minig rig with 8rtx 3060 at full speed.
thank you
can someone help me clarify something? i don't really understand the resource allocation when plotting.
so for example i have:
ryzen 7 5800X 8core / 16threads
2x Corsair mp600 2TB (4TB together)
32 GB ram 3600mhz
what is the optimum settings to plot parallel?
how many plots, how much number of threads used for one plot, RAM max usage MiB
i read someone is ploting 10-14 plots at once...how so?
thank you in advance
so for example i have:
ryzen 7 5800X 8core / 16threads
2x Corsair mp600 2TB (4TB together)
32 GB ram 3600mhz
what is the optimum settings to plot parallel?
how many plots, how much number of threads used for one plot, RAM max usage MiB
i read someone is ploting 10-14 plots at once...how so?
thank you in advance
Re: PhoenixMiner 5.5c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
Nvidia cards have always been pretty kind to me tuning wise. I love my AMD cards, but they like to crash when pushed too far. On a 1080 you'll want to tweak it manually as much as possible since the base hash rate is just OK.
Manually overclock it using afterburner starting with memory. With phoenix miner running, just push the memory frequency up until you start to get artifacts or your hash rate drops, you can probably run the memory pretty close to a gaming overclock level. Once that's maxed out lower the core freq until the hash rate starts to drop. Once that's done just lower the power limit until you get a hash rate drop. You might get some lag or glitchiness, but like I said, Nvidia cards are usually pretty easy to tune this way.
Longer term you'll want to monitor for excess stale or incorrect shares, but unless you're on a 30 series card, the random incorrect/stale issues are pretty rare.
Manually overclock it using afterburner starting with memory. With phoenix miner running, just push the memory frequency up until you start to get artifacts or your hash rate drops, you can probably run the memory pretty close to a gaming overclock level. Once that's maxed out lower the core freq until the hash rate starts to drop. Once that's done just lower the power limit until you get a hash rate drop. You might get some lag or glitchiness, but like I said, Nvidia cards are usually pretty easy to tune this way.
Longer term you'll want to monitor for excess stale or incorrect shares, but unless you're on a 30 series card, the random incorrect/stale issues are pretty rare.
hello guys,
can someone help me what are the perfect settings for gtx1080? i have one in pc and want to mine a bit (i have adm rigs, so dont know about nvidia setttings much
)
what + core and mem, PL and other settings? straps or somethng?
thank you
can someone help me what are the perfect settings for gtx1080? i have one in pc and want to mine a bit (i have adm rigs, so dont know about nvidia setttings much
)what + core and mem, PL and other settings? straps or somethng?
thank you
thank you so much for your help. i have started like 20Mhs, now i am getting 32.3Mhs using PL65, core +100, mem +400
In command line using straps 2 (straps 3 results in artefact, mem 450-500 as well). i will probably play with straps 4-6 and will see if i will get something, aynway thank you a lot
Re: PhoenixMiner 5.5c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
hello guys,
can someone help me what are the perfect settings for gtx1080? i have one in pc and want to mine a bit (i have adm rigs, so dont know about nvidia setttings much)
what + core and mem, PL and other settings? straps or somethng?
thank you
can someone help me what are the perfect settings for gtx1080? i have one in pc and want to mine a bit (i have adm rigs, so dont know about nvidia setttings much
)what + core and mem, PL and other settings? straps or somethng?
thank you
Re: [ANN][POW][CLO] Callisto Network - Cold Staking & Security Audits
hello,
i wanted to withdraw coins from my cold wallet (using https://wallet.callisto.network/ for stacking) but it throws error when trying so:
red panel at bottom shows up with "execution reverted" information. i cannot move or send it as my coins are locked. any advise?
also is there other way to stack coins instead of only on above wallet?
thank you
i wanted to withdraw coins from my cold wallet (using https://wallet.callisto.network/ for stacking) but it throws error when trying so:
red panel at bottom shows up with "execution reverted" information. i cannot move or send it as my coins are locked. any advise?
also is there other way to stack coins instead of only on above wallet?
thank you
Re: T-Rex 0.20.0 NVIDIA GPU miner (Ethash, Octopus, Kawpow, MTP)
hello, i would like to mine CFX(octopus) with this miner on my rtx3060, however i get low hashrate (on some pages i found some people are getting 100+ with rtx3060 (non-Ti)).
my stats are around 65-70mhs with PL60, core -200, mem +1100. i tried various settings, core -100,-150,-300,-500 and stil same results. also played with PL to increased and decrease it, still no luck get more hashrate.
my old rx5704gb is getting 60Mhs...
please any advice?
my stats are around 65-70mhs with PL60, core -200, mem +1100. i tried various settings, core -100,-150,-300,-500 and stil same results. also played with PL to increased and decrease it, still no luck get more hashrate.
my old rx5704gb is getting 60Mhs...
please any advice?
Re: [ANN] Zilliqa Auto Switcher. Auto Mine ZIL, 0% Fees, HIVE + SMOS + more
hello can someone help me a bit? i am confused 
i am currently mining cfx with t-rex on nanopool. seems zilminer doesnt work with zilminer due iof cuda 11 or something? Please can someone help me with bat file for zilswitcher...?
i am currently mining cfx with t-rex on nanopool. seems zilminer doesnt work with zilminer due iof cuda 11 or something? Please can someone help me with bat file for zilswitcher...?
Re: Octopus mining on a Nvidia 3060 vs Eth mining on a Nvidia 3060ti
I`d preffered 3060ti. For ETH it`s much better then 3060(for this moment) and for other coins - it`s better or same. If ETH goes to PoS - 3060 hash will be little less then 3060ti, but if ETH will be PoW for 2-3 months - you will mine at this time all price difference.
yeah that might be true, however 3060Ti for 1200Eur or 3060 for 550-800 its big different here.. i can convert cfx to eth if needed, yes it will be less, but 400eur is big difference and i dont think i will mine 400 for each card in addition what i would mine regularly. however that's mine opinion taking into account my local situation.
Re: NVIDIA is cutting the 3060's Hash Rate in Half & NEW Mining specific GPU's
I dont think they will find solution for this in coming future:) so far it was only coincidence ppl are able to mine with 1-3 cards(depend on mobo) but no real wa/crack has been found yet.