Bitcoin Forum>Bitcoin>Mining
Author

Topic: What Exactly Happens right after you power up your Miner (Read 134 times)

Daltonik
legendary
Activity: 2520
Merit: 1490
What Exactly Happens right after you power up your Miner
February 06, 2023, 08:53:01 AM
#7
Quote from: rere2113 on January 17, 2023, 04:07:13 AM
Hi. I was always wondering , technically what happens after the startup of a Miner. I mean I know that's too basic but I always loved getting deep. I mean what does the cpu do ? what parameters does it check ? what is the architecture ? what does every part inside the cpu do when its running ? And how does handle the Algorithms of BitCoin.

After launching your miner, if it is configured to work in the pool, the following processes occur, if in simple words without logs:

1.BIOS initialization: the miner's Basic Input/Output System (BIOS) checks the hardware components and initializes the settings required for the operating system to load.

2.Operating system boot: the miner loads the operating system and starts the required drivers and services.

3.Mining software launch: the miner starts the mining software, which is designed to solve complex mathematical problems in order to validate and add transactions to the blockchain.

4.Communication with mining pool: the miner establishes a connection to the mining pool and receives the necessary parameters, such as the pool address, port number, and miner's unique identifier.

5.Cryptographic hash function: the miner uses a cryptographic hash function, such as SHA-256, to perform a series of mathematical operations on the data in a block and produce a unique output, known as a hash.

6.PoW calculation: the miner performs a proof-of-work calculation by repeatedly hashing the block data and comparing the hash to a target value. The target value is adjusted by the network to maintain the average time required to mine a block at a consistent rate.

7.Block validation: if the miner is the first to solve the proof-of-work calculation and produce a hash that meets the target value, the block is considered valid, and the miner can broadcast the block to the network and receive a block reward.

8.Continuous mining: the miner continues to mine by repeating the process, starting with the next block of transactions waiting to be validated and added to the blockchain.

These steps are performed continuously by the CPU, which is the central processing unit of the miner. The CPU performs the necessary calculations, manages the memory and storage, and communicates with other components to ensure that the miner is able to continuously mine for cryptocurrency.



philipma1957
legendary
Activity: 4116
Merit: 7849
'The right to privacy matters'
Re: What Exactly Happens right after you power up your Miner
January 20, 2023, 01:34:24 AM
#6
Quote from: rere2113 on January 19, 2023, 04:03:24 PM
People , I can't Thank you enough. You've helped me a lot. Logs where really helpful.
I'll ask further questions , if something wasn't obvious.

always ask you will find a lot of knowledge on this forum
rere2113
newbie
Activity: 2
Merit: 1
Re: What Exactly Happens right after you power up your Miner
January 19, 2023, 04:03:24 PM
#5
People , I can't Thank you enough. You've helped me a lot. Logs where really helpful.
I'll ask further questions , if something wasn't obvious.
paid2
hero member
Activity: 504
Merit: 1065
Crypto Swap Exchange
Re: What Exactly Happens right after you power up your Miner
January 17, 2023, 09:51:18 PM
#4
Quote from: philipma1957 on January 17, 2023, 08:42:34 PM

to mods please do not delete as this is more about the controller/cpu action prior to the algo mined.

Here is an other example of a log with a SHA256 ASIC

It is from one of my Antminer R4 with Braiinos (S9 firmware)

https://pastebin.com/DAesx5SE
philipma1957
legendary
Activity: 4116
Merit: 7849
'The right to privacy matters'
Re: What Exactly Happens right after you power up your Miner
January 17, 2023, 08:42:34 PM
#3
you can look at the log it shows a lot.

I can show you a l3+ log

Code:
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.8.13 (xxl@armdev01) (gcc version 4.7.4 20130626 (prerelease) (Linaro GCC 4.7-2013.07) ) #22 SMP Tue Dec 2 15:26:11 CST 2014
[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=50c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine: Generic AM33XX (Flattened Device Tree), model: TI AM335x BeagleBone
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] On node 0 totalpages: 65280
[    0.000000] free_area_init_node: node 0, pgdat c06cb100, node_mem_map c0726000
[    0.000000]   Normal zone: 512 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 64768 pages, LIFO batch:15
[    0.000000] AM335X ES1.0 (neon )
[    0.000000] PERCPU: Embedded 8 pages/cpu @c0933000 s9408 r8192 d15168 u32768
[    0.000000] pcpu-alloc: s9408 r8192 d15168 u32768 alloc=8*4096
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 64768
[    0.000000] Kernel command line: console=ttyO0,115200n8 init=/sbin/init
[    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] __ex_table already sorted, skipping sort
[    0.000000] allocated 524288 bytes of page_cgroup
[    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[    0.000000] Memory: 255MB = 255MB total
[    0.000000] Memory: 238900k/238900k available, 23244k reserved, 0K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xd0800000 - 0xff000000   ( 744 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf800000 - 0xbfe00000   (   6 MB)
[    0.000000]       .text : 0xc0008000 - 0xc0612cf0   (6188 kB)
[    0.000000]       .init : 0xc0613000 - 0xc06554c0   ( 266 kB)
[    0.000000]       .data : 0xc0656000 - 0xc06cc020   ( 473 kB)
[    0.000000]        .bss : 0xc06cc020 - 0xc0725e3c   ( 360 kB)
[    0.000000] Hierarchical RCU implementation.
[    0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
[    0.000000] Total of 128 interrupts on 1 active controller
[    0.000000] OMAP clockevent source: GPTIMER1 at 24000000 Hz
[    0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
[    0.000000] OMAP clocksource: GPTIMER2 at 24000000 Hz
[    0.000000] Console: colour dummy device 80x30
[    0.000354] Calibrating delay loop... 545.07 BogoMIPS (lpj=531968)
[    0.015442] pid_max: default: 32768 minimum: 301
[    0.015674] Security Framework initialized
[    0.015772] Mount-cache hash table entries: 512
[    0.024603] Initializing cgroup subsys cpuacct
[    0.024636] Initializing cgroup subsys memory
[    0.024698] Initializing cgroup subsys blkio
[    0.024835] CPU: Testing write buffer coherency: ok
[    0.025403] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[    0.025480] Setting up static identity map for 0x8038c820 - 0x8038c86c
[    0.026807] Brought up 1 CPUs
[    0.026831] SMP: Total of 1 processors activated (545.07 BogoMIPS).
[    0.028129] devtmpfs: initialized
[    0.092506] pinctrl core: initialized pinctrl subsystem
[    0.092721] rstctl core: initialized rstctl subsystem
[    0.093211] regulator-dummy: no parameters
[    0.093780] NET: Registered protocol family 16
[    0.094487] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.104154] pinctrl-single 44e10800.pinmux: prop pinctrl-0 index 0 invalid phandle
[    0.104337] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[    0.105434] platform 49000000.edma: alias fck already exists
[    0.105469] platform 49000000.edma: alias fck already exists
[    0.105496] platform 49000000.edma: alias fck already exists
[    0.106652] gpiochip_add: registered GPIOs 0 to 31 on device: gpio
[    0.106837] OMAP GPIO hardware version 0.1
[    0.108247] gpiochip_add: registered GPIOs 32 to 63 on device: gpio
[    0.109569] gpiochip_add: registered GPIOs 64 to 95 on device: gpio
[    0.110879] gpiochip_add: registered GPIOs 96 to 127 on device: gpio
[    0.111509] of_get_named_gpio_flags exited with status 52
[    0.111541] gpio-rctrl rstctl.3: loaded OK
[    0.116647] omap-gpmc 50000000.gpmc: GPMC revision 6.0
[    0.119866] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.122070] cpsw.0: No hwaddr in dt. Using c4:f3:12:d6:c1:00 from efuse
[    0.122103] cpsw.1: No hwaddr in dt. Using c4:f3:12:d6:c1:02 from efuse
[    0.137654] bio: create slab at 0
[    0.149777] edma-dma-engine edma-dma-engine.0: TI EDMA DMA engine driver
[    0.150019] of_get_named_gpio_flags: can't parse gpios property
[    0.150313] vmmcsd_fixed: 3300 mV
[    0.153434] SCSI subsystem initialized
[    0.153891] usbcore: registered new interface driver usbfs
[    0.154005] usbcore: registered new interface driver hub
[    0.154345] usbcore: registered new device driver usb
[    0.156453] omap_i2c 4819c000.i2c: bus 0 rev0.11 at 100 kHz
[    0.156487] omap_i2c 4819c000.i2c: unable to select pin group
[    0.156685] media: Linux media interface: v0.10
[    0.156781] Linux video capture interface: v2.00
[    0.156898] pps_core: LinuxPPS API ver. 1 registered
[    0.156914] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti
[    0.157634] Advanced Linux Sound Architecture Driver Initialized.
[    0.158822] Switching to clocksource gp_timer
[    0.176842] NET: Registered protocol family 2
[    0.177835] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[    0.177923] TCP bind hash table entries: 2048 (order: 3, 40960 bytes)
[    0.178013] TCP: Hash tables configured (established 2048 bind 2048)
[    0.178106] TCP: reno registered
[    0.178132] UDP hash table entries: 256 (order: 1, 12288 bytes)
[    0.178178] UDP-Lite hash table entries: 256 (order: 1, 12288 bytes)
[    0.178676] NET: Registered protocol family 1
[    0.179263] RPC: Registered named UNIX socket transport module.
[    0.179284] RPC: Registered udp transport module.
[    0.179298] RPC: Registered tcp transport module.
[    0.179312] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.179701] Trying to unpack rootfs image as initramfs...
[    1.918982] Freeing initrd memory: 12016K
[    1.919632] CPU PMU: probing PMU on CPU 0
[    1.919664] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available
[    1.920208] omap2_mbox_probe: platform not supported
[    1.924111] VFS: Disk quotas dquot_6.5.2
[    1.924348] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.925779] NFS: Registering the id_resolver key type
[    1.925910] Key type id_resolver registered
[    1.925927] Key type id_legacy registered
[    1.925994] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    1.926449] msgmni has been set to 490
[    1.929322] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[    1.929349] io scheduler noop registered
[    1.929366] io scheduler deadline registered
[    1.929414] io scheduler cfq registered (default)
[    1.933470] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    1.935924] omap_uart 44e09000.serial: did not get pins for uart0 error: -19
[    1.936205] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88) is a OMAP UART0
[    2.597120] console [ttyO0] enabled
[    2.601664] 48022000.serial: ttyO1 at MMIO 0x48022000 (irq = 89) is a OMAP UART1
[    2.610406] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 90) is a OMAP UART2
[    2.619041] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 61) is a OMAP UART4
[    2.627708] 481aa000.serial: ttyO5 at MMIO 0x481aa000 (irq = 62) is a OMAP UART5
[    2.636692] [drm] Initialized drm 1.1.0 20060810
[    2.655333] brd: module loaded
[    2.665612] loop: module loaded
[    2.669783] bone-capemgr bone_capemgr.8: Failed to find baseboard eeprom node
[    2.679753] nand_get_flash_type: 2c,da against 2c,da
[    2.685281] ONFI param page 0 valid
[    2.688953] ONFI flash detected
[    2.692273] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron MT29F2G08ABAEAWP), 256MiB, page size: 2048, OOB size: 64
[    2.704185] omap2-nand: detected x8 NAND flash
[    2.708850] nand: using OMAP_ECC_BCH8_CODE_HW ECC scheme
[    2.714432] omap2-nand: using custom ecc layout
[    2.719266] 10 ofpart partitions found on MTD device omap2-nand.0
[    2.725658] Creating 10 MTD partitions on "omap2-nand.0":
[    2.731331] 0x000000000000-0x000000020000 : "spl"
[    2.738135] 0x000000020000-0x000000040000 : "spl_backup1"
[    2.745568] 0x000000040000-0x000000060000 : "spl_backup2"
[    2.752995] 0x000000060000-0x000000080000 : "spl_backup3"
[    2.760346] 0x000000080000-0x000000240000 : "u-boot"
[    2.768610] 0x000000240000-0x000000260000 : "bootenv"
[    2.775533] 0x000000260000-0x000000280000 : "fdt"
[    2.782165] 0x000000280000-0x000000780000 : "kernel"
[    2.793163] 0x000000800000-0x000001c00000 : "root"
[    2.816641] 0x000001c00000-0x000003000000 : "config"
[    2.840415] OneNAND driver initializing
[    2.846104] usbcore: registered new interface driver asix
[    2.851914] usbcore: registered new interface driver cdc_ether
[    2.858183] usbcore: registered new interface driver smsc95xx
[    2.864292] usbcore: registered new interface driver net1080
[    2.870311] usbcore: registered new interface driver cdc_subset
[    2.876598] usbcore: registered new interface driver zaurus
[    2.882597] usbcore: registered new interface driver cdc_ncm
[    2.889323] usbcore: registered new interface driver cdc_acm
[    2.895280] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    2.903659] Initializing USB Mass Storage driver...
[    2.908921] usbcore: registered new interface driver usb-storage
[    2.915218] USB Mass Storage support registered.
[    2.920253] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
[    2.926959] musb-hdrc musb-hdrc.0.auto: pdev->id = 0
[    2.932199] musb-hdrc musb-hdrc.0.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK
[    2.940964] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    2.940985] musb-hdrc: MHDRC RTL version 2.0
[    2.941000] musb-hdrc: setup fifo_mode 4
[    2.941028] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    2.941173] musb-hdrc musb-hdrc.0.auto: *** mode=3
[    2.946217] musb-hdrc musb-hdrc.0.auto: *** power=250
[    2.952274] musb-hdrc musb-hdrc.1.auto: pdev->id = 1
[    2.957524] musb-hdrc musb-hdrc.1.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK
[    2.966287] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    2.966306] musb-hdrc: MHDRC RTL version 2.0
[    2.966321] musb-hdrc: setup fifo_mode 4
[    2.966343] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    2.966493] musb-hdrc musb-hdrc.1.auto: *** mode=1
[    2.971537] musb-hdrc musb-hdrc.1.auto: *** power=250
[    2.976844] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[    2.983256] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 1
[    2.991490] musb-hdrc musb-hdrc.1.auto: supports USB remote wakeup
[    2.991594] usb usb1: default language 0x0409
[    2.991653] usb usb1: udev 1, busnum 1, minor = 0
[    2.991676] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.998804] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.006400] usb usb1: Product: MUSB HDRC host driver
[    3.011618] usb usb1: Manufacturer: Linux 3.8.13 musb-hcd
[    3.017285] usb usb1: SerialNumber: musb-hdrc.1.auto
[    3.023478] usb usb1: usb_probe_device
[    3.023507] usb usb1: configuration #1 chosen from 1 choice
[    3.023578] usb usb1: adding 1-0:1.0 (config #1, interface 0)
[    3.023780] hub 1-0:1.0: usb_probe_interface
[    3.023802] hub 1-0:1.0: usb_probe_interface - got id
[    3.023831] hub 1-0:1.0: USB hub found
[    3.027896] hub 1-0:1.0: 1 port detected
[    3.032067] hub 1-0:1.0: standalone hub
[    3.032087] hub 1-0:1.0: individual port power switching
[    3.032106] hub 1-0:1.0: no over-current protection
[    3.032123] hub 1-0:1.0: Single TT
[    3.032144] hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns)
[    3.032164] hub 1-0:1.0: power on to power good time: 10ms
[    3.032221] hub 1-0:1.0: local power source is good
[    3.032336] hub 1-0:1.0: enabling power on all ports
[    3.033376] mousedev: PS/2 mouse device common for all mice
[    3.041420] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0
[    3.049200] i2c /dev entries driver
[    3.054244] pps_ldisc: PPS line discipline registered
[    3.059709] Driver for 1-wire Dallas network protocol.
[    3.066957] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[    3.074524] cpuidle: using governor ladder
[    3.078845] cpuidle: using governor menu
[    3.083404] of_get_named_gpio_flags exited with status 6
[    3.083424] of_get_named_gpio_flags: can't parse gpios property
[    3.083440] of_get_named_gpio_flags: can't parse gpios property
[    3.083476] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' failed
[    3.090714] omap_hsmmc mmc.4: Failed to get rstctl; not using any
[    3.097521] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25
[    3.104741] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24
[    3.112103] mmc.4 supply vmmc_aux not found, using dummy regulator
[    3.119035] omap_hsmmc mmc.4: pins are not configured from the driver
[    3.133676] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
[    3.153780] of_get_named_gpio_flags exited with status -517
[    3.153847] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[    3.161495] ledtrig-cpu: registered to indicate activity on CPUs
[    3.168260] edma-dma-engine edma-dma-engine.0: allocated channel for 0:36
[    3.175448] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
[    3.183565] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
[    3.189918] edma-dma-engine edma-dma-engine.0: allocated channel for 0:5
[    3.197106] edma-dma-engine edma-dma-engine.0: allocated channel for 0:6
[    3.209402] usbcore: registered new interface driver usbhid
[    3.215327] usbhid: USB HID core driver
[    3.222232] TCP: cubic registered
[    3.225756] Initializing XFRM netlink socket
[    3.230326] NET: Registered protocol family 17
[    3.235176] NET: Registered protocol family 15
[    3.240042] Key type dns_resolver registered
[    3.244687] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    3.252801] ThumbEE CPU extension supported.
[    3.257313] Registering SWP/SWPB emulation handler
[    3.263330] registered taskstats version 1
[    3.269933] of_get_named_gpio_flags exited with status -517
[    3.270007] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[    3.326948] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[    3.333360] davinci_mdio 4a101000.mdio: detected phy mask fffffffe
[    3.347930] libphy: 4a101000.mdio: probed
[    3.352283] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
[    3.362508] Detected MACID = c4:f3:12:d6:c1:00
[    3.367188] cpsw 4a100000.ethernet: NAPI disabled
[    3.372577] of_get_named_gpio_flags exited with status -517
[    3.372642] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[    3.381361] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[    3.390641] cpu0 supply cpu0 not found, using dummy regulator
[    3.397134] cpufreq_cpu0: failed to scale voltage up: -22
[    3.402952] cpufreq_cpu0: failed to scale voltage up: -22
[    3.415728] ALSA device list:
[    3.418963]   No soundcards found.
[    3.423504] Freeing init memory: 264K
[    3.427557] Failed to execute /init
[    4.401499] jffs2: notice: (122) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[    5.749292] net eth0: initializing cpsw version 1.12 (0)
[    5.758239] net eth0: phy found : id is : 0x7c0f1
[    5.763675] libphy: PHY 4a101000.mdio:01 not found
[    5.768871] net eth0: phy 4a101000.mdio:01 not found on slave 1
[    9.903618] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
Jan 17 01:54:57 (none) local0.notice cgminer[8981]: Dump IIC Data:[41][98][1][0]@ChainID:[2], Chip[C9]
Jan 17 01:54:57 (none) local0.notice cgminer[8981]: Dump IIC Data:[41][98][1][0]@ChainID:[3], Chip[C9]...


I cut the log off at the point it reached cgminer

at this point most ant miners do something similar anything after this will involve the algo you are trying to mine.

Since this is btc area of mining and I do not have a btc log access I stopped at this point.

Note that the time begins to show Jan 17


to mods please do not delete as this is more about the controller/cpu action prior to the algo mined.
DaveF
legendary
Activity: 3458
Merit: 6231
Crypto Swap Exchange
Re: What Exactly Happens right after you power up your Miner
January 17, 2023, 08:48:37 AM
#2
More or less the same as what happens when you boot any other computer.

The firmware (BIOS) does a quick check of some things same as your PC, then it loads an OS, in the case of miners it's linux.
Then it start running some programs. A web server so you can see whats going on and a mining program so it can mine.

That is it. There will be some slight differences based on manufacturer but not much.

You can go out and buy a USB stick miner and run cgminer yourself on any PC and are doing the exact same thing that a full miner is doing.
Just a lot slower.....

You should move this to the hardware board. https://bitcointalk.org/index.php?board=76.0

-Dave
rere2113
newbie
Activity: 2
Merit: 1
Re: What Exactly Happens right after you power up your Miner
January 17, 2023, 04:07:13 AM
#1
Hi. I was always wondering , technically what happens after the startup of a Miner. I mean I know that's too basic but I always loved getting deep. I mean what does the cpu do ? what parameters does it check ? what is the architecture ? what does every part inside the cpu do when its running ? And how does handle the Algorithms of BitCoin.
I would also like some information about firmware , what happens when you transfer updated firmware using the sd card.
Sorry if my questions are too basic but knowing a lot about bit I always liked to know about what actually happening inside of that noisy box!!
Thanks in Advance
Bitcoin Forum>Bitcoin>Mining
Jump to: