Bitcoin Forum
April 28, 2024, 05:48:18 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 [60] 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 ... 2279 »
1181  Bitcoin / Bitcoin Technical Support / Re: Outrageous Bitcoin Fees on: January 02, 2024, 04:43:39 PM
We will likely have high fees until LN gets far more adaptation.

Options now are join an exchange that allows LN use.

Kraken does. do Kyc give 500 cash buy BTC. All low cost so far.

You can then use their LN wallet.

Just remember you can have all that money frozen or stolen classic not your keys not your coins.

It you want a second LN setup.

join nicehash do KYC

Transfer 250 usd worth of btc via LN to nicehash.

you then can use two different LN wallets without complicated work.

I have about $350 worth of Btc on kraken and I mine about $100 a day to my nicehash wallet.

so I can easily pay and receive btc with two different companies.

I am well aware I can lose my coin 🪙

I have a small amount on those companies . Plus cold wallets.
1182  Bitcoin / Mining / Re: Centralization in mining. on: January 02, 2024, 04:26:50 PM
it does match.  slow first 5 days fast last 9 days. end of day 5 -1%. end of 14 days +3 or 4%

Here are the blocks Foundry mined the last two epoch by date:

10  37    26 48
11  48    27 36
12  34    28 33
13  43    29 37    
14  35    30 31
15  35    01 49
16  44    02 43
17  43    03 45
18  43    04 53
19  50    05 30  
20  53    06 40
21  53    07 29
             08 30
             09 37

Last epoch Foundry had it's three lowest block digging days in the last 5 days, just because something happened once it doesn't make it a rule Phil.

Second, if Foundry was now back at it's full power, then it means it has run underclock forever!

Current reported hashrate is 148 Exahas, Foundry never had this hashrate ever till now, their November one day high is 140exa, so where would this extra hashrate come from? New gear and luck, the same new gear that is making them have the biggest share of the pie in months:
https://explorer.btc.com/btc/insights-pools
They are at 37.12% over the last theree days and compared to 28.24% over 1 month!

Third, don't you think it's really a bad strategy to mine more block on Friday and Saturday right before a holiday, when the reward will probably hit record lows?

Just saying that they can do it and we can’t track it a lot. Other than daily block counts.

Besides with software that can downclock or upclock a thousand units in 1 minute. The downclock is basically doable when ever.  It also becomes cheaper when the ½ ing comes. As the penalty for losing a block reward drops from 6.25 to 3.125  is an extra incentive to manipulate fees upwards.

I think they are fine tuning it for the ½ ing. Learning how fast they can clog the mempool via under clock.

then overclock to grab the high fee blocks.
1183  Bitcoin / Mining / Re: Is There A Guide to Help Me Start Solo Mining? on: January 02, 2024, 03:55:26 PM
I read somewhere that a solo miner mined a block. As big a gamble as that is, I'm considering solo mining with just one machine. I'm not bothered if I never mine a block but I just want to give it a shot. Is there a guide somewhere on the best miner to buy and how to set it up. Has someone here tried solo mining. I just need some sort of guidance. Thanks.

just mine at ckpool

https://bitcointalk.org/index.php?topic=5237323.0

or kano solo

https://bitcointalk.org/index.php?topic=789369.0

what miner to use is the hard question.

do you have 120 or 240 volt power?

you have very limited choice if you have 120 volt power.

if you have 240 volt.

look for a two board s19 set it to low power and it will do about 50 th and fairly efficient and quiet.
1184  Other / Meta / Re: Mixers to be banned on: January 02, 2024, 03:34:27 PM
The best we could do now is mirror it in a more friendly country and we lose the security of having one guy you really need to trust (theymos) the mirror back up in a second country would mean at least one other person needs full access to the entire forum since theymos cannot be in two places at the same time.

Also you are still asking theymos to put him or herself at risk from the USA based system since theymos is USA based.  Nevermind the second country could turn on you and go after that mirror setup.
Your post gave me an idea like what we seen Binance and Stake have their own dedicated sites for US jurisdiction. If bitcointalk.org is subject to US laws, maybe we need a second domain like bitcointalkall.org that's subject to friendly country laws. Maybe Cyrus might be able to help Tongue , not sure if Romania is friendly with privacy, to be more specify a tumbler.

I agree that looks more possible than wanting a decentralized forum, not even to mention epochtalk.

This a clever improvement or spin on my idea.  Maybe it is the way to go.
1185  Other / Meta / Re: Mixers to be banned on: January 02, 2024, 02:45:36 PM
Arguing for the sake of arguing much?  Roll Eyes

You didn't answer my questions, you just keep making new questions demanding answers...

What answer do you want me to answer?
How am I going to talk about a technology that doesn't exist today, or rather that isn't viable for a forum of this size, mainly because I don't have the resources to invent something like that?

What I can say is that creating a decentralized forum today is impossible and completely unfeasible.

The example I gave was torrent, not BitTorrent. BitTorrent is a torrent client, which is clearly not decentralized.
Do you know how torrent works? So imagine the same for the website. How can an ordinary person access a website, without having to install specific software, download the entire database that can be larger than a 4K Blu-ray movie, and then browse?

But wait, it only takes 1 byte to depend on one person, so it won't be decentralized.

Is Bitcoin decentralized? Yes, yours because anyone can set up a node and run it. But, Bitcoin is linear and not dynamic. It is mathematical work, always the same, that always produces the same type of data. A forum is highly dynamic, where all users produce different content, where features change over time, and many other things happen in a matter of seconds.

It cannot be compared when the type of data transmitted is always the same, with other services that are very varied in terms of data. The greater the data variation, the more complex and longer the processing process.

I'm not saying that in the future there won't be something really functional that makes this type of site decentralized. But at the moment it doesn't exist. Therefore, I cannot demand the forum to become decentralized.



The best we could do now is mirror it in a more friendly country and we lose the security of having one guy you really need to trust (theymos) the mirror back up in a second country would mean at least one other person needs full access to the entire forum since theymos cannot be in two places at the same time.

Also you are still asking theymos to put him or herself at risk from the USA based system since theymos is USA based.  Nevermind the second country could turn on you and go after that mirror setup.
1186  Economy / Speculation / Re: Wall Observer BTC/USD - Bitcoin price movement tracking & discussion on: January 02, 2024, 03:50:02 AM
Get the chopper ready!... And i mean, the original chopper!

okay lets do the 45 over night and wake up to 46k on the 2nd.

Bring it on!!!

we passed 45k again and I think we hit a two year high at 45.5k.

edit

we need 47.9k to get a two year high.
1187  Economy / Speculation / Re: Wall Observer BTC/USD - Bitcoin price movement tracking & discussion on: January 02, 2024, 02:04:06 AM
failed at this pop over 45k maybe the next one breaks the dam.

but my posts are at 44.2k and price is 44.8k not bad.

Buddy is really close to passing me by I have a month at most.
1188  Economy / Speculation / Re: Wall Observer BTC/USD - Bitcoin price movement tracking & discussion on: January 02, 2024, 01:14:36 AM
$45k+

Racing to $46k...

Only thing missing now is a "going to zero" post by proudhon.  Cheesy

I want to wake up to 46.6k tues morning.

I did predict 42.3k on dec 1   we hit it on dec 4/5

I did predict 48.1k on Jan 1 maybe it comes just a tiny bit later Jan 2-5 works


https://bitcointalk.org/index.php?topic=5472517.msg63090856#msg63090856
1189  Local / Deutsch (German) / Re: Gewinnspiel: (neues?) Bitcoin Allzeithoch im Jahr 2023 on: January 01, 2024, 11:57:59 PM
Vielen Dank für eure schnellen Antworten, auf welche Adressen das BTC gesendet werden soll.

bc1qhf2kn9ej8zucgxq64nc3tp0c7czy4tj6yp3aj0

Meine Bitcoin Adresse: bc1qsrh2pu5l4ctysujwu957xuswy7hhxqj0rcrajy

Meine Adresse ist: bc1qlwxqcku2q9lxvwhpymzwy7uexx6krlwws0re5e

Da die Transaktionsgebühren aktuell wieder relativ niedrig sind, habe ich es direkt an euch versendet: https://blockchair.com/bitcoin/transaction/d29904c64f8f4d20f7dadb93ebabb666f412fd5c5a2c418d9a1c31f0c1a99a99

philipma1957 = 3,5 mBTC
NeuroticFish = 1,75 mBTC
Mauser        = 1 mBTC

Gratulation zum Gewinn und hoffen wir einmal, dass die Transaktionsgebühren nicht direkt wieder ansteigen, denn wer weiß, wie lange das so bleibt.  Cheesy
Auf ein neues Allzeithoch in 2024.  Smiley

got it thanks again !
1190  Economy / Speculation / Re: Wall Observer BTC/USD - Bitcoin price movement tracking & discussion on: January 01, 2024, 11:55:18 PM
Get the chopper ready!... And i mean, the original chopper!

okay lets do the 45 over night and wake up to 46k on the 2nd.
1191  Bitcoin / Mining / Re: Bitcoin faces risk of protocol-level censorship as miners under increasing regul on: January 01, 2024, 11:53:51 PM
In short, they are nicely asking for a hard fork, as the current hashrate percentage is not enough for them to make the OFAC list mandatory. However, if the United States puts pressure on all countries of the world, the percentage of unknown mining pools is less than 2%. If all governments were united, passing such regulations would be easy.




The big question remains: If governments do not unite at the climate summit, something that harms humanity, will they unite in creating a blacklist of addresses for Bitcoin?

yes of course they will cause it hurts their own pockets.
1192  Other / Meta / Re: Decentralize Bitcointalk on: January 01, 2024, 10:03:41 PM
Banning bitcointalk is not affecting the Bitcoin network in any way. Sure, it's the digital museum of Bitcoin, but enthusiasts can already migrate elsewhere.

Decentralizing a forum is not proved sustainable. Scaling is a nightmare, works more complexly, moderation is minimum if not zero (which is pretty much the same as here), and will probably incentivize users to use a third party. I have used nostr, which is a decentralized social network like Twitter, and it's even worse than Twitter.

And BTW, bitcointalk is not scheduled to be banned.

Hey I am married and depend on 3 US fed gov pensions.

So moving to El Salvador to run a mirror image of this forum is not in the cards for me.

We would need a single person to do it.

I am not sure what country you would want the mirror backup to be in.

What would it cost in time and money to do.

Also a mirror image means two point of attack to hack.

So yeah it is not that practical.


Lastly bitcointalk was the startup forum for btc. It did a good job. It is no longer the influencer that it once was.
1193  Bitcoin / Mining speculation / Re: 2024 Diff thread happy New Years. on: January 01, 2024, 09:46:23 PM
With rewards dropping to 3.125 miners (kingpin massive mines) will want high fees

Without a doubt, this will be difficult to combat.
I just hope that people don't get used to this, and stop debating the subject, ending up being forgotten and leaving us with these levels of super high rates.

The easy short-term solve is do KYC with an exchange that allow use of LN.

Kraken does it.


hodl 90% of your coins in your wallet

put 10% in kraken.
1194  Bitcoin / Mining speculation / Re: 2024 Diff thread happy New Years. on: January 01, 2024, 09:05:42 PM
we are right at 100%

Taking into account the situation we have been experiencing in recent times, very high fees, the fact that there are no major changes in speed, could this be a sign that we will continue to see high fees?

High are going to last for at least 5 months. Say may 31.

Just look at last year.  they were high for over 6 out of 12 months.

With rewards dropping to 3.125 miners (kingpin massive mines) will want high fees

1195  Bitcoin / Mining support / Re: S17 Pro hashboard 2/3 mining on: January 01, 2024, 08:02:17 PM
Code:
Booting Linux on physical CPU 0x0
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
CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Xilinx Zynq
cma: Reserved 16 MiB at 0x0e000000
Memory policy: Data cache writealloc
On node 0 totalpages: 61440
free_area_init_node: node 0, pgdat c0b39280, 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 @cddf1000 s19776 r8192 d21184 u49152
pcpu-alloc: s19776 r8192 d21184 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: 203608K/245760K available (6345K kernel code, 231K rwdata, 1896K rodata, 1024K init, 223K bss, 25768K 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 - 0xc090c424   (9234 kB)
      .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
      .data : 0xc0b00000 - 0xc0b39fe0   ( 232 kB)
       .bss : 0xc0b39fe0 - 0xc0b71c28   ( 224 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: 12728K (cce93000 - cdb01000)
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 = 158, 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
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: 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: 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
nand_read_bbt: bad block at 0x000002420000
nand_read_bbt: bad block at 0x000002440000
nand_read_bbt: bad block at 0x000002460000
6 ofpart partitions found on MTD device pl35x-nand
Creating 6 MTD partitions on "pl35x-nand":
0x000000000000-0x000002800000 : "BOOT.bin-env-dts-kernel"
0x000002800000-0x000004800000 : "ramfs"
0x000004800000-0x000005000000 : "configs"
0x000005000000-0x000006000000 : "reserve"
0x000006000000-0x000008000000 : "ramfs-bak"
0x000008000000-0x000010000000 : "reserve1"
NET: Registered protocol family 10
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 (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
random: dd urandom read with 0 bits of entropy available
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: 9/3, WL threshold: 4096, image sequence number: 1843227590
ubi0: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 40
ubi0: background thread "ubi_bgt0d" started, PID 708
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 711
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 6982C89C-4654-4723-9D9F-4839010383A9, small LPT model
ubi1: attaching mtd5
ubi1: scanning is finished
ubi1: attached mtd5 (name "reserve1", size 128 MiB)
ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi1: good PEBs: 1020, bad PEBs: 4, corrupted PEBs: 0
ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi1: max/mean erase counter: 179/67, WL threshold: 4096, image sequence number: 1483908108
ubi1: available PEBs: 0, total reserved PEBs: 1020, PEBs reserved for bad PEB handling: 36
ubi1: background thread "ubi_bgt1d" started, PID 720
UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 723
UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "reserve1"
UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi1:0): FS size: 123039744 bytes (117 MiB, 969 LEBs), journal size 6221824 bytes (5 MiB, 49 LEBs)
UBIFS (ubi1:0): reserved for root: 4952683 bytes (4836 KiB)
UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID E4D4A67A-EAF7-4612-8A0B-95DB85171497, small LPT model
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
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 0xcfb38000
*base_vir_addr = 0xab013
In fpga mem driver!
request_mem_region OK!
fpga mem virtual address is 0xd2000000
random: nonblocking pool is initialized
Jan  1 19:05:12 (none) user.notice kernel: random: nonblocking pool is initialized
Jan  1 19:05:27 (none) local0.notice bmminer: set_start_time_point total_tv_start_sys=244 total_tv_end_sys=245
Jan  1 19:05:30 (none) local0.notice cgminer: cgminer_socket_init reg bitmain_api_detect return: 0
Jan  1 19:05:30 (none) local0.notice cgminer: cgminer_socket_init reg bitmain_update_job return: 0
Jan  1 19:05:31 (none) local0.notice cgminer: cgminer_socket_init reg bitmain_shutdown return: 0
Jan  1 19:05:31 (none) local0.err cgminer: Miner compile time: Mon Apr 27 13:25:08 CST 2020 type: Antminer S17 Pro
Jan  1 19:05:31 (none) local0.notice cgminer[996]: about to send detect
Jan  1 19:05:31 (none) local0.notice cgminer[996]: set_start_time_point total_tv_start_sys=248 total_tv_end_sys=249
Jan  1 19:05:31 (none) local0.notice cgminer[996]: Probing for an alive pool
Jan  1 19:05:31 (none) local0.notice cgminer[996]: LOW POWER MODE!
Jan  1 19:05:31 (none) local0.notice cgminer[996]: Switching to pool 1 stratum+tcp://btc.ss.poolin.one:443 - first alive pool
Jan  1 19:05:31 (none) local0.notice cgminer[996]: Pool 1 difficulty changed to 65536
Jan  1 19:05:31 (none) local0.notice cgminer[996]: in stratum_sthread
Jan  1 19:05:31 (none) local0.notice cgminer[996]: LOW POWER MODE!
Jan  1 19:05:31 (none) local0.notice cgminer[996]: LOW POWER MODE!
Jan  1 19:05:31 (none) local0.warn cgminer[996]: Pool 0 stratum+tcp://btc.ss.poolin.one:443 alive, testing stability
Jan  1 19:05:31 (none) local0.notice cgminer[996]: in stratum_sthread
Jan  1 19:05:31 (none) local0.notice cgminer[996]: Pool 0 difficulty changed to 65536
Jan  1 19:05:31 (none) local0.notice cgminer[996]: Pool 2 difficulty changed to 65536
Jan  1 19:05:31 (none) local0.notice cgminer[996]: in stratum_sthread
Jan  1 19:05:31 (none) local0.notice cgminer[996]: Network diff set to 72T
Jan  1 19:05:31 (none) local0.notice cgminer[996]: POOL 1 support ab mode!
Jan  1 19:05:31 (none) local0.notice cgminer[996]: POOL 0 support ab mode!
Jan  1 19:05:32 (none) local0.notice cgminer[996]: update job
Jan  1 19:05:32 (none) local0.notice cgminer[996]: job buf total len:2541, offset:2541
Jan  1 19:05:32 (none) local0.notice cgminer[996]: about to send job, size is 2541
Jan  1 19:05:32 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4000480 size: 2541
Jan  1 19:05:32 (none) local0.notice bmminer: parse job buf len:2541
Jan  1 19:05:32 (none) local0.warn cgminer[996]: Pool 0 stratum+tcp://btc.ss.poolin.one:443 stable for >120 seconds
Jan  1 19:05:32 (none) local0.warn cgminer[996]: Switching to pool 0 stratum+tcp://btc.ss.poolin.one:443
Jan  1 19:05:34 (none) local0.notice cgminer[996]: update job
Jan  1 19:05:34 (none) local0.notice cgminer[996]: job buf total len:2541, offset:2541
Jan  1 19:05:34 (none) local0.notice cgminer[996]: about to send job, size is 2541
Jan  1 19:05:34 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4000480 size: 2541
Jan  1 19:05:34 (none) local0.notice bmminer: parse job buf len:2541
Jan  1 19:05:37 (none) local0.warn cgminer[996]: API running in IP access mode on port 4028 (14)
Jan  1 19:05:55 (none) local0.notice bmminer: need data size:481, actual size:481
Jan  1 19:05:55 (none) local0.notice cgminer[996]: got nonce sz 481
Jan  1 19:05:55 (none) local0.notice cgminer[996]: Pool 0 stale share detected, submitting as user requested
Jan  1 19:05:55 (none) local0.notice cgminer[996]: cb_bitmain_submit_nonce nonce submited
Jan  1 19:05:55 (none) local0.notice cgminer[996]: Accepted 23756f3b Diff 473K/65536 BTM_SOC 0 pool 0
Jan  1 19:06:04 (none) local0.notice bmminer: need data size:481, actual size:481
Jan  1 19:06:04 (none) local0.notice cgminer[996]: got nonce sz 481
Jan  1 19:06:04 (none) local0.notice cgminer[996]: Pool 0 stale share detected, submitting as user requested
Jan  1 19:06:04 (none) local0.notice cgminer[996]: cb_bitmain_submit_nonce nonce submited
Jan  1 19:06:04 (none) local0.notice cgminer[996]: Accepted ff1f855c Diff 65.8K/65536 BTM_SOC 0 pool 0
Jan  1 19:06:04 (none) local0.notice cgminer[996]: update job
Jan  1 19:06:04 (none) local0.notice cgminer[996]: job buf total len:2541, offset:2541
Jan  1 19:06:04 (none) local0.notice cgminer[996]: about to send job, size is 2541
Jan  1 19:06:04 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4000480 size: 2541
Jan  1 19:06:04 (none) local0.notice bmminer: parse job buf len:2541
Jan  1 19:06:11 (none) local0.notice bmminer: need data size:481, actual size:481
Jan  1 19:06:11 (none) local0.notice cgminer[996]: got nonce sz 481
Jan  1 19:06:11 (none) local0.notice cgminer[996]: Pool 0 stale share detected, submitting as user requested
Jan  1 19:06:11 (none) local0.notice cgminer[996]: cb_bitmain_submit_nonce nonce submited
Jan  1 19:06:11 (none) local0.notice cgminer[996]: Accepted 28b93a5a Diff 412K/65536 BTM_SOC 0 pool 0
Jan  1 19:06:16 (none) local0.notice bmminer: need data size:481, actual size:481
Jan  1 19:06:16 (none) local0.notice cgminer[996]: got nonce sz 481
Jan  1 19:06:16 (none) local0.notice cgminer[996]: Pool 0 stale share detected, submitting as user requested
Jan  1 19:06:16 (none) local0.notice cgminer[996]: cb_bitmain_submit_nonce nonce submited
Jan  1 19:06:16 (none) local0.notice cgminer[996]: Accepted b721a2d5 Diff 91.6K/65536 BTM_SOC 0 pool 0
Jan  1 19:06:23 (none) local0.notice bmminer: need data size:481, actual size:481
Jan  1 19:06:23 (none) local0.notice cgminer[996]: got nonce sz 481
Jan  1 19:06:23 (none) local0.notice cgminer[996]: Pool 0 stale share detected, submitting as user requested
Jan  1 19:06:23 (none) local0.notice cgminer[996]: cb_bitmain_submit_nonce nonce submited
Jan  1 19:06:23 (none) local0.notice cgminer[996]: Accepted 0165b8e0 Diff 12M/65536 BTM_SOC 0 pool 0
Jan  1 19:06:29 (none) local0.notice bmminer: need data size:481, actual size:481
Jan  1 19:06:29 (none) local0.notice cgminer[996]: got nonce sz 481
Jan  1 19:06:29 (none) local0.notice cgminer[996]: Pool 0 stale share detected, submitting as user requested
Jan  1 19:06:29 (none) local0.notice cgminer[996]: cb_bitmain_submit_nonce nonce submited
Jan  1 19:06:29 (none) local0.notice cgminer[996]: Accepted 1fed9f32 Diff 525K/65536 BTM_SOC 0 pool 0
Jan  1 19:06:30 (none) local0.notice bmminer: need data size:481, actual size:481
Jan  1 19:06:30 (none) local0.notice cgminer[996]: got nonce sz 481
Jan  1 19:06:30 (none) local0.notice cgminer[996]: Pool 0 stale share detected, submitting as user requested
Jan  1 19:06:30 (none) local0.notice cgminer[996]: cb_bitmain_submit_nonce nonce submited
Jan  1 19:06:30 (none) local0.notice cgminer[996]: Accepted 43a7bb57 Diff 248K/65536 BTM_SOC 0 pool 0
Jan  1 19:06:34 (none) local0.notice cgminer[996]: update job
Jan  1 19:06:34 (none) local0.notice cgminer[996]: job buf total len:2541, offset:2541
Jan  1 19:06:34 (none) local0.notice cgminer[996]: about to send job, size is 2541
Jan  1 19:06:34 (none) local0.notice bmminer: bitmain_update_job_cb, rec job data 0xb4000480 size: 2541
Jan  1 19:06:34 (none) local0.notice bmminer: parse job buf len:2541
2024-01-01 19:02:05 driver-btm-api.c:542:init_freq_mode: This is scan-user version
2024-01-01 19:02:05 driver-btm-api.c:1877:bitmain_soc_init: opt_multi_version     = 1
2024-01-01 19:02:05 driver-btm-api.c:1878:bitmain_soc_init: opt_bitmain_ab        = 1
2024-01-01 19:02:05 driver-btm-api.c:1879:bitmain_soc_init: opt_bitmain_work_mode = 0
2024-01-01 19:02:05 driver-btm-api.c:1880:bitmain_soc_init: Miner compile time: Mon Apr 27 13:25:08 CST 2020 type: Antminer S17
2024-01-01 19:02:05 driver-btm-api.c:1881:bitmain_soc_init: commit version: d22f356 2020-04-24 18:30:49, build by: lol 2020-04-27 13:31:45
2024-01-01 19:02:05 driver-btm-api.c:1691:show_sn: no SN got, please write SN to /nvdata/sn
2024-01-01 19:02:05 driver-btm-api.c:1040:miner_device_init: Detect 256MB control board of XILINX
2024-01-01 19:02:05 driver-btm-api.c:988:init_fan_parameter: fan_eft : 0  fan_pwm : 0
2024-01-01 19:02:05 thread.c:783:create_read_nonce_reg_thread: create thread
2024-01-01 19:02:11 driver-btm-api.c:972:init_miner_version: miner ID : 8118e4442b10481c
2024-01-01 19:02:11 driver-btm-api.c:978:init_miner_version: FPGA Version = 0xB013
2024-01-01 19:02:17 driver-btm-api.c:616:get_product_id: product_id[0] = 0
2024-01-01 19:02:17 driver-btm-api.c:616:get_product_id: product_id[1] = 0
2024-01-01 19:02:17 driver-btm-api.c:616:get_product_id: product_id[2] = 0
2024-01-01 19:02:17 driver-btm-api.c:560:_set_project_type: project:0
2024-01-01 19:02:17 driver-btm-api.c:585:_set_project_type: Project type: Antminer S17 Pro
2024-01-01 19:02:17 driver-btm-api.c:596:dump_pcb_bom_version: Chain [0] PCB Version: 0x0101
2024-01-01 19:02:17 driver-btm-api.c:597:dump_pcb_bom_version: Chain [0] BOM Version: 0x0103
2024-01-01 19:02:17 driver-btm-api.c:596:dump_pcb_bom_version: Chain [1] PCB Version: 0x0101
2024-01-01 19:02:17 driver-btm-api.c:597:dump_pcb_bom_version: Chain [1] BOM Version: 0x0103
2024-01-01 19:02:17 driver-btm-api.c:596:dump_pcb_bom_version: Chain [2] PCB Version: 0x0101
2024-01-01 19:02:17 driver-btm-api.c:597:dump_pcb_bom_version: Chain [2] BOM Version: 0x0103
2024-01-01 19:02:19 driver-btm-api.c:1802:bitmain_board_init: Fan check passed.
2024-01-01 19:02:20 board.c:36:jump_and_app_check_restore_pic: chain[0] PIC jump to app
2024-01-01 19:02:22 board.c:40:jump_and_app_check_restore_pic: Check chain[0] PIC fw version=0xb9
2024-01-01 19:02:23 board.c:36:jump_and_app_check_restore_pic: chain[1] PIC jump to app
2024-01-01 19:02:25 board.c:40:jump_and_app_check_restore_pic: Check chain[1] PIC fw version=0xb9
2024-01-01 19:02:26 board.c:36:jump_and_app_check_restore_pic: chain[2] PIC jump to app
2024-01-01 19:02:28 board.c:40:jump_and_app_check_restore_pic: Check chain[2] PIC fw version=0xb9
2024-01-01 19:02:28 thread.c:778:create_pic_heart_beat_thread: create thread
2024-01-01 19:02:28 power_api.c:207:power_init: Power init:
2024-01-01 19:02:28 power_api.c:208:power_init: current_voltage_raw = 0
2024-01-01 19:02:28 power_api.c:209:power_init: highest_voltage_raw = 2100
2024-01-01 19:02:28 power_api.c:210:power_init: working_voltage_raw = 1830
2024-01-01 19:02:28 power_api.c:211:power_init: higher_voltage_raw  = 1950
2024-01-01 19:02:28 driver-btm-api.c:1812:bitmain_board_init: Enter 30s sleep to make sure power release finish.
2024-01-01 19:02:28 power_api.c:181:power_off: init gpio907
2024-01-01 19:03:00 power_api.c:251:set_to_highest_voltage: Set to voltage raw 2100, one step.
2024-01-01 19:03:02 power_api.c:87:check_voltage_multi: retry time: 0
2024-01-01 19:03:03 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 21.057158
2024-01-01 19:03:04 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 21.008174
2024-01-01 19:03:05 power_api.c:37:_get_avg_voltage: chain = 2, voltage = 20.922451
2024-01-01 19:03:05 power_api.c:50:_get_avg_voltage: average_voltage = 20.995927
2024-01-01 19:03:05 power_api.c:68:check_voltage: target_vol = 21.00, actural_vol = 21.00, check voltage passed.
2024-01-01 19:03:05 uart.c:71:set_baud: set fpga_baud to 115200
2024-01-01 19:03:17 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[0]: find 48 asic, times 0
2024-01-01 19:03:28 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[1]: find 48 asic, times 0
2024-01-01 19:03:38 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2024-01-01 19:03:49 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2024-01-01 19:04:00 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2
2024-01-01 19:04:00 driver-btm-api.c:942:check_asic_number: Chain 2 only find 0 asic, will power off hash board 2
2024-01-01 19:04:04 driver-btm-api.c:345:set_order_clock: chain[0]: set order clock, stragegy 3
2024-01-01 19:04:04 driver-btm-api.c:345:set_order_clock: chain[1]: set order clock, stragegy 3
2024-01-01 19:04:04 driver-hash-chip.c:502:set_clock_delay_control: core_data = 0x34
2024-01-01 19:04:04 uart.c:71:set_baud: set fpga_baud to 3000000
2024-01-01 19:04:04 driver-btm-api.c:1574:check_clock_counter: freq 50 clock_counter_limit 6
2024-01-01 19:04:06 uart.c:71:set_baud: set fpga_baud to 115200
2024-01-01 19:04:06 voltage[0] = 1700
2024-01-01 19:04:06 voltage[1] = 1700
2024-01-01 19:04:06 power_api.c:219:set_working_voltage_raw: working_voltage_raw = 1700
2024-01-01 19:04:07 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 0 success.
2024-01-01 19:04:09 temperature.c:281:calibrate_temp_sensor_one_chain: Temperature sensor calibration: chain 1 success.
2024-01-01 19:04:09 uart.c:71:set_baud: set fpga_baud to 6000000
2024-01-01 19:04:10 driver-btm-api.c:245:check_bringup_temp: Bring up temperature is 23
2024-01-01 19:04:10 thread.c:798:create_check_miner_status_thread: create thread
2024-01-01 19:04:10 thread.c:788:create_set_miner_status_thread: create thread
2024-01-01 19:04:10 thread.c:773:create_temperature_monitor_thread: create thread
2024-01-01 19:04:10 frequency.c:749:inc_freq_with_fixed_vco: chain = 255, freq = 425, is_higher_voltage = true
2024-01-01 19:04:10 power_api.c:287:set_to_voltage_by_steps: Set to voltage raw 2020, step by step.
2024-01-01 19:04:27 power_api.c:87:check_voltage_multi: retry time: 0
2024-01-01 19:04:29 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 20.248916
2024-01-01 19:04:30 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 20.206054
2024-01-01 19:04:30 power_api.c:50:_get_avg_voltage: average_voltage = 20.227485
2024-01-01 19:04:30 power_api.c:68:check_voltage: target_vol = 20.20, actural_vol = 20.23, check voltage passed.
2024-01-01 19:05:01 frequency.c:801:inc_freq_with_fixed_step: chain = 0, freq_start = 425, freq_end = 440, freq_step = 5, is_higher_voltage = true
2024-01-01 19:05:02 driver-btm-api.c:528:set_timeout: freq = 440, percent = 90, hcn = 73728, timeout = 167
2024-01-01 19:05:02 power_api.c:269:set_to_working_voltage_by_steps: Set to voltage raw 1700, step by step.
2024-01-01 19:05:19 power_api.c:87:check_voltage_multi: retry time: 0
2024-01-01 19:05:21 power_api.c:37:_get_avg_voltage: chain = 0, voltage = 17.022070
2024-01-01 19:05:22 power_api.c:37:_get_avg_voltage: chain = 1, voltage = 16.979209
2024-01-01 19:05:22 power_api.c:50:_get_avg_voltage: average_voltage = 17.000639
2024-01-01 19:05:22 power_api.c:68:check_voltage: target_vol = 17.00, actural_vol = 17.00, check voltage passed.
2024-01-01 19:05:22 thread.c:793:create_check_system_status_thread: create thread
2024-01-01 19:05:23 driver-btm-api.c:1988:bitmain_soc_init: Init done!
2024-01-01 19:05:23 driver-btm-api.c:198:set_miner_status: STATUS_INIT
2024-01-01 19:05:27 driver-btm-api.c:198:set_miner_status: STATUS_OKAY
2024-01-01 19:05:28 frequency.c:216:get_ideal_hash_rate_GH: ideal_hash_rate = 27577
2024-01-01 19:05:28 frequency.c:236:get_sale_hash_rate_GH: sale_hash_rate = 26000
2024-01-01 19:05:32 driver-btm-api.c:1199:dhash_chip_send_job: Version num 4


you very likely have a dead board

2024-01-01 19:03:38 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 0
2024-01-01 19:03:49 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 1
2024-01-01 19:04:00 driver-btm-api.c:915:check_asic_number_with_power_on: Chain[2]: find 0 asic, times 2




I would set to high.  rather than low .

high will give you 34th vs 26th

a dead board is likely not easy to fix.


maybe you have a bad white info cable connection.  you could pull all them off carefully dip in 99% alcohol dry them and then see if the board reads the asics.

https://www.amazon.com/Isopropyl-Alcohol-99-IPA-Made/dp/B08JZJ5QV2/ref=sr_1_9?


must be 99% do not use 91% or 70%
1196  Economy / Speculation / Re: Wall Observer BTC/USD - Bitcoin price movement tracking & discussion on: January 01, 2024, 08:00:35 PM
Jan 1 2023 = 16.6k

Jan 1 2024 = 43.4k

Jan 1 2025 = ? 


my guess is  $113,467.47
1197  Economy / Speculation / Re: Wall Observer BTC/USD - Bitcoin price movement tracking & discussion on: January 01, 2024, 07:43:00 PM
Happy New Year guys!

I predict 2024 will be a very prosperous one for us. 2025 will be better but let’s not wish this year away.

Hope you all have a great 2024.

2024 will bring us a new ATH which works for me.

Happy new years.
1198  Local / Deutsch (German) / Re: Gewinnspiel: (neues?) Bitcoin Allzeithoch im Jahr 2023 on: January 01, 2024, 06:06:52 PM
I am not very good with German.

Thank you for prize.

Send it to:


bc1qhf2kn9ej8zucgxq64nc3tp0c7czy4tj6yp3aj0

thank you and Happy New Year to all.


Google translate to German below:


Ich bin nicht sehr gut in Deutsch. Vielen Dank für den Preis.

Senden Sie es an:

bc1qhf2kn9ej8zucgxq64nc3tp0c7czy4tj6yp3aj0

Vielen Dank und allen ein frohes neues Jahr.
1199  Bitcoin / Bitcoin Technical Support / Re: Good portable HDD for cold wallet on: January 01, 2024, 05:54:27 PM
I want to use a portable HDD wallet for the airgapped laptop so I can bring it with me when needed. Does anyone know a good model that does not have any of the dodgy firmware stuff, that isnt a weird HDD/SSD hybrid, and that has decent performance?

I would like to have both cold and hot drives to be portable, so in case of an emergency or something, you can easily pick 2 small things and run, instead of having to carry 2 laptops.

The cold wallet I want an HDD in case full wipe is needed. See this for more context:
https://bitcointalk.org/index.php?topic=5479284.msg63393713#msg63393713

Also edited thread because I switched cold with hot wallet by mistake because I was posting after xmas dinner.

I used to do this with my mac minis full os and bitcoincore node full.

I would use samsung ssd

https://www.amazon.com/SAMSUNG-Portable-Photographers-MU-PE1T0S-AM/dp/B09VLK9W3S/ref=sr_1_3?


and this hdd

https://www.amazon.com/Toshiba-Canvio-Basics-Portable-External/dp/B0BQX6DVWY/ref=sr_1_4?


put your os on them and bitcoincore or a wallet like electrum


frankly A lot depends if you have these cloned and in a safe place.

say a safe deposit box.

I may say do electrum and make a safe seed
1200  Bitcoin / Mining support / Re: Antminer S9 SE Troubleshooting on: January 01, 2024, 05:20:32 PM
So testing a PSU looks pretty straight forward, just probe the leads for 12v DC, plus or minus a half volt and it should be ok if it falls in those parameters, right?

testing the psu is best done on a fully working unit as it will draw enough amps.

you can test a psu on an s9 by just plugging in the controller. and make sure  all white info cables connect to hash boards.

the fans will run. and you will have nine unplugged leads.

just see if a few of the lead cables are over 11.9 volts. first test.

if you are 11.9 to 12.9 good.

shut gear off.

plug three leads into 1 board.

fire it up 🆙. test a few leads  to see if you are at 11.9 to 12.9 volts.

I suspect one of two issues weak psu or some poor boards that draw to much current.


So at this point you have 1 controller and 1 board hook up 🆙.
 if it all runs you know that board is good. and you still are not sure of the psu.

power off. unplug just the one working board say on the left.

all white info cable stay plugged in.

now plug in the three jacks to the center board.

run a while and see if it works. if it works you know that it is a good board.


shut gear done

do the same for third board. if it works all three boards are good.

an you likely have a weak psu.

next series of tests are try boards left side and center .


see what happens.

if it is a weak psu you may notice a drop in volts.

many of the psus can do 1 or 2 boards but not 3.

or some times 1 board is shitty and draws a lot of power.

you have the worst s9 model that has had the worst record of not working well.

but I suspect we can get one or two boards working. on it.


Pages: « 1 ... 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 [60] 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 ... 2279 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!