|
Title: Antminer connected but isnt mining 0 hashrate issue Post by: TrophyMiner on March 29, 2021, 04:28:52 PM i have an l3++ antminer and its connected fine and working with the fans and light being on
my only issue is that i cant get it to mine and it keeps showing 0 hashrate I tried to reset it and also upgrade the firmware but same issue persists iam not sure what is the problem here since it shows alive in the miner status page i will attach a photo and logs i hope someone can help https://pasteboard.co/JUSDcrb.jpg Mar 29 16:04:14 (none) local0.err cgminer[368]: Miner compile time: Mon Jul 15 15:44:23 CST 2019 type: Antminer L3++ Mar 29 16:04:14 (none) local0.warn cgminer[368]: Started cgminer 4.9.0 Mar 29 16:04:14 (none) local0.notice cgminer[368]: detected at /sys/class/gpio/gpio51/value chain 0 Mar 29 16:04:14 (none) local0.notice cgminer[368]: detected at /sys/class/gpio/gpio48/value chain 1 Mar 29 16:04:14 (none) local0.notice cgminer[368]: detected at /sys/class/gpio/gpio47/value chain 2 Mar 29 16:04:14 (none) local0.notice cgminer[368]: detected at /sys/class/gpio/gpio44/value chain 3 Mar 29 16:04:14 (none) local0.notice cgminer[368]: detect total chain num 4 Mar 29 16:04:14 (none) local0.notice cgminer[368]: i2c init ok Mar 29 16:04:24 (none) local0.notice cgminer[368]: in tty_init Mar 29 16:04:24 (none) local0.notice cgminer[368]: tty_init 0 Mar 29 16:04:24 (none) local0.notice cgminer[368]: Start A New Asic Response.Chain Id:[0] Mar 29 16:04:24 (none) local0.notice cgminer[368]: tty_init 1 Mar 29 16:04:24 (none) local0.notice cgminer[368]: Start A New Asic Response.Chain Id:[1] Mar 29 16:04:24 (none) local0.notice cgminer[368]: tty_init 2 Mar 29 16:04:24 (none) local0.notice cgminer[368]: Start A New Asic Response.Chain Id:[2] Mar 29 16:04:24 (none) local0.notice cgminer[368]: tty_init 3 Mar 29 16:04:24 (none) local0.notice cgminer[368]: Start A New Asic Response.Chain Id:[3] Mar 29 16:04:25 (none) local0.notice cgminer[368]: open device over Mar 29 16:04:25 (none) local0.notice cgminer[368]: send cmd to get chip address Mar 29 16:04:27 (none) local0.notice cgminer[368]: Chain 0 ASIC 0 !!! Mar 29 16:04:27 (none) local0.notice cgminer[368]: Chain 1 ASIC 0 !!! Mar 29 16:04:27 (none) local0.notice cgminer[368]: Chain 2 ASIC 0 !!! Mar 29 16:04:27 (none) local0.notice cgminer[368]: Chain 3 ASIC 0 !!! Mar 29 16:04:27 (none) local0.notice cgminer[368]: Need to recheck asic num !!! Mar 29 16:04:35 (none) local0.err cgminer[442]: Miner compile time: Mon Jul 15 15:44:23 CST 2019 type: Antminer L3++ Mar 29 16:04:35 (none) local0.warn cgminer[442]: Started cgminer 4.9.0 Mar 29 16:04:35 (none) local0.notice cgminer[442]: detected at /sys/class/gpio/gpio51/value chain 0 Mar 29 16:04:35 (none) local0.notice cgminer[442]: detected at /sys/class/gpio/gpio48/value chain 1 Mar 29 16:04:35 (none) local0.notice cgminer[442]: detected at /sys/class/gpio/gpio47/value chain 2 Mar 29 16:04:35 (none) local0.notice cgminer[442]: detected at /sys/class/gpio/gpio44/value chain 3 Mar 29 16:04:35 (none) local0.notice cgminer[442]: detect total chain num 4 Mar 29 16:04:35 (none) local0.notice cgminer[442]: i2c init ok Mar 29 16:04:44 (none) local0.notice cgminer[442]: in tty_init Mar 29 16:04:44 (none) local0.notice cgminer[442]: tty_init 0 Mar 29 16:04:44 (none) local0.notice cgminer[442]: Start A New Asic Response.Chain Id:[0] Mar 29 16:04:44 (none) local0.notice cgminer[442]: tty_init 1 Mar 29 16:04:44 (none) local0.notice cgminer[442]: Start A New Asic Response.Chain Id:[1] Mar 29 16:04:45 (none) local0.notice cgminer[442]: tty_init 2 Mar 29 16:04:45 (none) local0.notice cgminer[442]: Start A New Asic Response.Chain Id:[2] Mar 29 16:04:45 (none) local0.notice cgminer[442]: tty_init 3 Mar 29 16:04:45 (none) local0.notice cgminer[442]: Start A New Asic Response.Chain Id:[3] Mar 29 16:04:45 (none) local0.notice cgminer[442]: open device over Mar 29 16:04:45 (none) local0.notice cgminer[442]: send cmd to get chip address Mar 29 16:04:47 (none) local0.notice cgminer[442]: Chain 0 ASIC 0 !!! Mar 29 16:04:47 (none) local0.notice cgminer[442]: Chain 1 ASIC 0 !!! Mar 29 16:04:47 (none) local0.notice cgminer[442]: Chain 2 ASIC 0 !!! Mar 29 16:04:47 (none) local0.notice cgminer[442]: Chain 3 ASIC 0 !!! Mar 29 16:04:47 (none) local0.notice cgminer[442]: Need to recheck asic num !!! Mar 29 16:04:49 (none) local0.notice cgminer[442]: Chain 0 ASIC 0 !!! Mar 29 16:04:49 (none) local0.notice cgminer[442]: Chain 1 ASIC 0 !!! Mar 29 16:04:49 (none) local0.notice cgminer[442]: Chain 2 ASIC 0 !!! Mar 29 16:04:49 (none) local0.notice cgminer[442]: Chain 3 ASIC 0 !!! Mar 29 16:04:50 (none) local0.notice cgminer[442]: frequency = '450' Mar 29 16:04:50 (none) local0.notice cgminer[442]: dev.timeout = 39 Mar 29 16:04:50 (none) local0.notice cgminer[442]: opt_bitmain_L3_core_temp : 2 Mar 29 16:04:51 (none) local0.notice cgminer[442]: send cmd to open block Mar 29 16:04:54 (none) local0.err cgminer[442]: cgminer time error total_secs = 1617033894.425380 last_total_secs = 1.000000 Mar 29 16:04:54 (none) local0.warn cgminer[442]: Pool 0 stratum+tcp://scrypt.eu-north.nicehash.com:3333 alive, testing stability Mar 29 16:04:54 (none) local0.warn cgminer[442]: Switching to pool 0 stratum+tcp://scrypt.eu-north.nicehash.com:3333 Mar 29 16:05:00 (none) local0.warn cgminer[442]: API running in IP access mode on port 4028 (16) Mar 29 16:05:02 (none) local0.warn cgminer[442]: Stratum reconnect requested from pool 0 to scrypt.eu-north.nicehash.com:3333 Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: philipma1957 on March 29, 2021, 04:37:24 PM this is BTC only.
I will ask mods to move this to alt coins. how to solve this. try a different pool. try viabtc.com stratum+tcp://ltc.viabtc.com:3333 user name = whatever password = x Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: TrophyMiner on March 29, 2021, 04:39:55 PM this is BTC only. I will ask mods to move this to alt coins. o sorry didnt notice Thanks Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: philipma1957 on March 29, 2021, 04:40:48 PM this is BTC only. I will ask mods to move this to alt coins. o sorry didnt notice Thanks no worries they will move it for you. Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: mikeywith on March 29, 2021, 11:17:42 PM Code: Mar 29 16:04:47 (none) local0.notice cgminer[442]: Chain 0 ASIC 0 !!! This part in the kernel log shows that all 4 hash boards are dead, so basically you have a dead miner and that's all about it, there isn't much you can do about it, but you could try a different PSU if you have one or custom firmware that might help revive a board or two. Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: MidNite36 on March 30, 2021, 05:20:36 AM Code: Mar 29 16:04:47 (none) local0.notice cgminer[442]: Chain 0 ASIC 0 !!! This part in the kernel log shows that all 4 hash boards are dead, so basically you have a dead miner and that's all about it, there isn't much you can do about it, but you could try a different PSU if you have one or custom firmware that might help revive a board or two. Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: TrophyMiner on March 30, 2021, 03:35:33 PM Code: Mar 29 16:04:47 (none) local0.notice cgminer[442]: Chain 0 ASIC 0 !!! This part in the kernel log shows that all 4 hash boards are dead, so basically you have a dead miner and that's all about it, there isn't much you can do about it, but you could try a different PSU if you have one or custom firmware that might help revive a board or two. how can they be dead its a brand new miner from bitmain never used is there anyway to fix this? i tried opening it and the boards all look clean and nothing unusual about them installed latest firmware form the l3++ also reseted the board and tried the board recovery sd flash method but still same issue is there what other options do i have? iam sure the boards are not dead i mean 1 or 2 could be dead but all 4 out of the box? Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: miner29 on March 30, 2021, 05:58:59 PM Code: Mar 29 16:04:47 (none) local0.notice cgminer[442]: Chain 0 ASIC 0 !!! This part in the kernel log shows that all 4 hash boards are dead, so basically you have a dead miner and that's all about it, there isn't much you can do about it, but you could try a different PSU if you have one or custom firmware that might help revive a board or two. how can they be dead its a brand new miner from bitmain never used is there anyway to fix this? i tried opening it and the boards all look clean and nothing unusual about them installed latest firmware form the l3++ also reseted the board and tried the board recovery sd flash method but still same issue is there what other options do i have? iam sure the boards are not dead i mean 1 or 2 could be dead but all 4 out of the box? New? It came out 3 years ago. Bitmain hasnt offered srcypt asics in quite some time...considering thier best offering is less than 1/3rd the speed of current scrypt asics. Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: TrophyMiner on March 30, 2021, 07:24:50 PM Code: Mar 29 16:04:47 (none) local0.notice cgminer[442]: Chain 0 ASIC 0 !!! This part in the kernel log shows that all 4 hash boards are dead, so basically you have a dead miner and that's all about it, there isn't much you can do about it, but you could try a different PSU if you have one or custom firmware that might help revive a board or two. how can they be dead its a brand new miner from bitmain never used is there anyway to fix this? i tried opening it and the boards all look clean and nothing unusual about them installed latest firmware form the l3++ also reseted the board and tried the board recovery sd flash method but still same issue is there what other options do i have? iam sure the boards are not dead i mean 1 or 2 could be dead but all 4 out of the box? New? It came out 3 years ago. Bitmain hasnt offered srcypt asics in quite some time...considering thier best offering is less than 1/3rd the speed of current scrypt asics. i bought them 3 years ago and never opened the box and decided to use them now Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: miner29 on March 30, 2021, 08:11:38 PM Code: Mar 29 16:04:47 (none) local0.notice cgminer[442]: Chain 0 ASIC 0 !!! This part in the kernel log shows that all 4 hash boards are dead, so basically you have a dead miner and that's all about it, there isn't much you can do about it, but you could try a different PSU if you have one or custom firmware that might help revive a board or two. how can they be dead its a brand new miner from bitmain never used is there anyway to fix this? i tried opening it and the boards all look clean and nothing unusual about them installed latest firmware form the l3++ also reseted the board and tried the board recovery sd flash method but still same issue is there what other options do i have? iam sure the boards are not dead i mean 1 or 2 could be dead but all 4 out of the box? New? It came out 3 years ago. Bitmain hasnt offered srcypt asics in quite some time...considering thier best offering is less than 1/3rd the speed of current scrypt asics. i bought them 3 years ago and never opened the box and decided to use them now Well the warranty period has expired for sure. Check power and make sure you have all boards hooked up properly. How many units you have (sounds like more than one)? If they are all doing this then i suspect something external is wrong...as it is very unlikely multiple new units would be DOA. Unless there is some other defect. Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: TrophyMiner on March 30, 2021, 09:02:50 PM Code: Mar 29 16:04:47 (none) local0.notice cgminer[442]: Chain 0 ASIC 0 !!! This part in the kernel log shows that all 4 hash boards are dead, so basically you have a dead miner and that's all about it, there isn't much you can do about it, but you could try a different PSU if you have one or custom firmware that might help revive a board or two. how can they be dead its a brand new miner from bitmain never used is there anyway to fix this? i tried opening it and the boards all look clean and nothing unusual about them installed latest firmware form the l3++ also reseted the board and tried the board recovery sd flash method but still same issue is there what other options do i have? iam sure the boards are not dead i mean 1 or 2 could be dead but all 4 out of the box? New? It came out 3 years ago. Bitmain hasnt offered srcypt asics in quite some time...considering thier best offering is less than 1/3rd the speed of current scrypt asics. i bought them 3 years ago and never opened the box and decided to use them now Well the warranty period has expired for sure. Check power and make sure you have all boards hooked up properly. How many units you have (sounds like more than one)? If they are all doing this then i suspect something external is wrong...as it is very unlikely multiple new units would be DOA. Unless there is some other defect. i bought 10 asics just to resell them the l3++ just didnt get sold so i decided to use it myself i got 4 other S9 SE units they all work perfectly ( bought used) its just this l3++ which isnt working for some reason.. the power cables and everything else is hooked up correctly.. i mean its new a new unit from bitmain it cant have all 4 boards dead lol there has to be a trick or something i can do to make it work Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: JayDDee on March 30, 2021, 09:31:08 PM I would agree that all 4 boards dead on a brand new unit would be very unusual.
I would suspect the fault is not the boards themselves, but something that would affect all 4. Did it come with a user guide? Maybe there's a first time setup step that wasn't done, some master switch that needs to be flipped, or some packing material that needs to be removed. I'm just guessing. If you have any electronic skills you can get out your voltmeter and check that the boards are getting power. If not power maybe the data connection. Make sure all the connectors are properly fastnened, give them a little push to make sure. That's all I got, good luck. Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: TrophyMiner on March 30, 2021, 10:06:41 PM I would agree that all 4 boards dead on a brand new unit would be very unusual. I would suspect the fault is not the boards themselves, but something that would affect all 4. Did it come with a user guide? Maybe there's a first time setup step that wasn't done, some master switch that needs to be flipped, or some packing material that needs to be removed. I'm just guessing. If you have any electronic skills you can get out your voltmeter and check that the boards are getting power. If not power maybe the data connection. Make sure all the connectors are properly fastnened, give them a little push to make sure. That's all I got, good luck. indeed.. there is no master switch on the miner and i the psu works fine 1 thing i noticed in the logs is this 3.492086] cpu0 supply cpu0 not found, using dummy regulator [ 3.498570] cpufreq_cpu0: failed to scale voltage up: -22 [ 3.504392] cpufreq_cpu0: failed to scale voltage up: -22 this could be the issue but i dont understand what it means i was thinking of installing a custom firmware from a website to test but not sure which 1 is the best of all and how to actually do it since bitmain put a signature on the miner with a custom firmware you can play around with numbers so maybe it can be tweaked and fixed Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: JayDDee on March 30, 2021, 10:35:02 PM Those logs weren't in your first post. Did you do something to cause a change? Anything that changes
the symptoms is a clue. In your first post I noticed it detected all 4 boards but they seem to have failed to respond. You could try removing one board to see if the logs change. That might identify a connectivity issue. Another thought is to call up old customers, they might be able to help. Edit: your second set of logs suggests a power issue. As cryptic as they are they contain a few keywords: supply, regulator, voltage. Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: TrophyMiner on March 30, 2021, 10:51:00 PM ok i didnt think the entire log was needed but here it is maybe it will help you guys out more
[ 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.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: 237964k/237964k available, 24180k 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.000359] Calibrating delay loop... 545.07 BogoMIPS (lpj=531968) [ 0.015436] pid_max: default: 32768 minimum: 301 [ 0.015669] Security Framework initialized [ 0.015764] Mount-cache hash table entries: 512 [ 0.024600] Initializing cgroup subsys cpuacct [ 0.024632] Initializing cgroup subsys memory [ 0.024696] Initializing cgroup subsys blkio [ 0.024832] CPU: Testing write buffer coherency: ok [ 0.025409] CPU0: thread -1, cpu 0, socket -1, mpidr 0 [ 0.025487] Setting up static identity map for 0x8038c820 - 0x8038c86c [ 0.026821] Brought up 1 CPUs [ 0.026846] SMP: Total of 1 processors activated (545.07 BogoMIPS). [ 0.028136] devtmpfs: initialized [ 0.092551] pinctrl core: initialized pinctrl subsystem [ 0.092764] rstctl core: initialized rstctl subsystem [ 0.093261] regulator-dummy: no parameters [ 0.093829] NET: Registered protocol family 16 [ 0.094531] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.104200] pinctrl-single 44e10800.pinmux: prop pinctrl-0 index 0 invalid phandle [ 0.104380] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568 [ 0.105476] platform 49000000.edma: alias fck already exists [ 0.105510] platform 49000000.edma: alias fck already exists [ 0.105537] platform 49000000.edma: alias fck already exists [ 0.106682] gpiochip_add: registered GPIOs 0 to 31 on device: gpio [ 0.106865] OMAP GPIO hardware version 0.1 [ 0.108272] gpiochip_add: registered GPIOs 32 to 63 on device: gpio [ 0.109588] gpiochip_add: registered GPIOs 64 to 95 on device: gpio [ 0.110904] gpiochip_add: registered GPIOs 96 to 127 on device: gpio [ 0.111537] of_get_named_gpio_flags exited with status 52 [ 0.111567] gpio-rctrl rstctl.3: loaded OK [ 0.116673] omap-gpmc 50000000.gpmc: GPMC revision 6.0 [ 0.119870] hw-breakpoint: debug architecture 0x4 unsupported. [ 0.122058] cpsw.0: No hwaddr in dt. Using c8:fd:19:1f:fb:47 from efuse [ 0.122090] cpsw.1: No hwaddr in dt. Using c8:fd:19:1f:fb:49 from efuse [ 0.137632] bio: create slab <bio-0> at 0 [ 0.149757] edma-dma-engine edma-dma-engine.0: TI EDMA DMA engine driver [ 0.149999] of_get_named_gpio_flags: can't parse gpios property [ 0.150292] vmmcsd_fixed: 3300 mV [ 0.153408] SCSI subsystem initialized [ 0.153858] usbcore: registered new interface driver usbfs [ 0.153972] usbcore: registered new interface driver hub [ 0.154303] usbcore: registered new device driver usb [ 0.156391] omap_i2c 4819c000.i2c: bus 0 rev0.11 at 100 kHz [ 0.156425] omap_i2c 4819c000.i2c: unable to select pin group [ 0.156620] media: Linux media interface: v0.10 [ 0.156718] Linux video capture interface: v2.00 [ 0.156835] pps_core: LinuxPPS API ver. 1 registered [ 0.156851] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 0.157571] Advanced Linux Sound Architecture Driver Initialized. [ 0.158760] Switching to clocksource gp_timer [ 0.176792] NET: Registered protocol family 2 [ 0.177782] TCP established hash table entries: 2048 (order: 2, 16384 bytes) [ 0.177871] TCP bind hash table entries: 2048 (order: 3, 40960 bytes) [ 0.177960] TCP: Hash tables configured (established 2048 bind 2048) [ 0.178051] TCP: reno registered [ 0.178079] UDP hash table entries: 256 (order: 1, 12288 bytes) [ 0.178125] UDP-Lite hash table entries: 256 (order: 1, 12288 bytes) [ 0.178623] NET: Registered protocol family 1 [ 0.179203] RPC: Registered named UNIX socket transport module. [ 0.179224] RPC: Registered udp transport module. [ 0.179237] RPC: Registered tcp transport module. [ 0.179251] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.179640] Trying to unpack rootfs image as initramfs... [ 2.020508] Freeing initrd memory: 12952K [ 2.021189] CPU PMU: probing PMU on CPU 0 [ 2.021222] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available [ 2.021763] omap2_mbox_probe: platform not supported [ 2.025652] VFS: Disk quotas dquot_6.5.2 [ 2.025888] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 2.027285] NFS: Registering the id_resolver key type [ 2.027379] Key type id_resolver registered [ 2.027397] Key type id_legacy registered [ 2.027463] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. [ 2.027898] msgmni has been set to 490 [ 2.030745] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249) [ 2.030772] io scheduler noop registered [ 2.030789] io scheduler deadline registered [ 2.030847] io scheduler cfq registered (default) [ 2.034876] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 2.037327] omap_uart 44e09000.serial: did not get pins for uart0 error: -19 [ 2.037615] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88) is a OMAP UART0 [ 2.698454] console [ttyO0] enabled [ 2.702999] 48022000.serial: ttyO1 at MMIO 0x48022000 (irq = 89) is a OMAP UART1 [ 2.711709] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 90) is a OMAP UART2 [ 2.720331] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 61) is a OMAP UART4 [ 2.728937] 481aa000.serial: ttyO5 at MMIO 0x481aa000 (irq = 62) is a OMAP UART5 [ 2.737962] [drm] Initialized drm 1.1.0 20060810 [ 2.756634] brd: module loaded [ 2.766926] loop: module loaded [ 2.771115] bone-capemgr bone_capemgr.8: Failed to find baseboard eeprom node [ 2.781073] nand_get_flash_type: 2c,da against 2c,da [ 2.786601] ONFI param page 0 valid [ 2.790276] ONFI flash detected [ 2.793596] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron MT29F2G08ABAEAWP), 256MiB, page size: 2048, OOB size: 64 [ 2.805509] omap2-nand: detected x8 NAND flash [ 2.810174] nand: using OMAP_ECC_BCH8_CODE_HW ECC scheme [ 2.815758] omap2-nand: using custom ecc layout [ 2.820600] 10 ofpart partitions found on MTD device omap2-nand.0 [ 2.826995] Creating 10 MTD partitions on "omap2-nand.0": [ 2.832686] 0x000000000000-0x000000020000 : "spl" [ 2.839508] 0x000000020000-0x000000040000 : "spl_backup1" [ 2.846970] 0x000000040000-0x000000060000 : "spl_backup2" [ 2.854380] 0x000000060000-0x000000080000 : "spl_backup3" [ 2.861743] 0x000000080000-0x000000240000 : "u-boot" [ 2.870018] 0x000000240000-0x000000260000 : "bootenv" [ 2.876970] 0x000000260000-0x000000280000 : "fdt" [ 2.883606] 0x000000280000-0x000000780000 : "kernel" [ 2.894603] 0x000000800000-0x000001c00000 : "root" [ 2.918120] 0x000001c00000-0x000003000000 : "config" [ 2.941894] OneNAND driver initializing [ 2.947609] usbcore: registered new interface driver asix [ 2.953436] usbcore: registered new interface driver cdc_ether [ 2.959718] usbcore: registered new interface driver smsc95xx [ 2.965839] usbcore: registered new interface driver net1080 [ 2.971866] usbcore: registered new interface driver cdc_subset [ 2.978162] usbcore: registered new interface driver zaurus [ 2.984167] usbcore: registered new interface driver cdc_ncm [ 2.990972] usbcore: registered new interface driver cdc_acm [ 2.996917] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 3.005325] Initializing USB Mass Storage driver... [ 3.010803] usbcore: registered new interface driver usb-storage [ 3.017128] USB Mass Storage support registered. [ 3.022231] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host) [ 3.028954] musb-hdrc musb-hdrc.0.auto: pdev->id = 0 [ 3.034198] musb-hdrc musb-hdrc.0.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK [ 3.042971] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn) [ 3.042992] musb-hdrc: MHDRC RTL version 2.0 [ 3.043006] musb-hdrc: setup fifo_mode 4 [ 3.043034] musb-hdrc: 28/31 max ep, 16384/16384 memory [ 3.043180] musb-hdrc musb-hdrc.0.auto: *** mode=3 [ 3.048223] musb-hdrc musb-hdrc.0.auto: *** power=250 [ 3.054228] musb-hdrc musb-hdrc.1.auto: pdev->id = 1 [ 3.059479] musb-hdrc musb-hdrc.1.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK [ 3.068249] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn) [ 3.068269] musb-hdrc: MHDRC RTL version 2.0 [ 3.068284] musb-hdrc: setup fifo_mode 4 [ 3.068305] musb-hdrc: 28/31 max ep, 16384/16384 memory [ 3.068444] musb-hdrc musb-hdrc.1.auto: *** mode=1 [ 3.073488] musb-hdrc musb-hdrc.1.auto: *** power=250 [ 3.078796] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver [ 3.085182] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 1 [ 3.093426] musb-hdrc musb-hdrc.1.auto: supports USB remote wakeup [ 3.093530] usb usb1: default language 0x0409 [ 3.093589] usb usb1: udev 1, busnum 1, minor = 0 [ 3.093613] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 3.100742] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.108314] usb usb1: Product: MUSB HDRC host driver [ 3.113529] usb usb1: Manufacturer: Linux 3.8.13 musb-hcd [ 3.119197] usb usb1: SerialNumber: musb-hdrc.1.auto [ 3.125154] usb usb1: usb_probe_device [ 3.125181] usb usb1: configuration #1 chosen from 1 choice [ 3.125246] usb usb1: adding 1-0:1.0 (config #1, interface 0) [ 3.125445] hub 1-0:1.0: usb_probe_interface [ 3.125466] hub 1-0:1.0: usb_probe_interface - got id [ 3.125494] hub 1-0:1.0: USB hub found [ 3.129495] hub 1-0:1.0: 1 port detected [ 3.133638] hub 1-0:1.0: standalone hub [ 3.133657] hub 1-0:1.0: individual port power switching [ 3.133675] hub 1-0:1.0: no over-current protection [ 3.133693] hub 1-0:1.0: Single TT [ 3.133714] hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns) [ 3.133734] hub 1-0:1.0: power on to power good time: 10ms [ 3.133790] hub 1-0:1.0: local power source is good [ 3.133903] hub 1-0:1.0: enabling power on all ports [ 3.134954] mousedev: PS/2 mouse device common for all mice [ 3.142894] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0 [ 3.150393] 44e3e000.rtc: already running [ 3.154886] i2c /dev entries driver [ 3.159927] pps_ldisc: PPS line discipline registered [ 3.165406] Driver for 1-wire Dallas network protocol. [ 3.172721] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec [ 3.180280] cpuidle: using governor ladder [ 3.184610] cpuidle: using governor menu [ 3.189188] of_get_named_gpio_flags exited with status 6 [ 3.189208] of_get_named_gpio_flags: can't parse gpios property [ 3.189224] of_get_named_gpio_flags: can't parse gpios property [ 3.189262] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' failed [ 3.196484] omap_hsmmc mmc.4: Failed to get rstctl; not using any [ 3.203299] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25 [ 3.210521] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24 [ 3.217853] mmc.4 supply vmmc_aux not found, using dummy regulator [ 3.224804] omap_hsmmc mmc.4: pins are not configured from the driver [ 3.235151] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000 [ 3.259065] of_get_named_gpio_flags exited with status -517 [ 3.259132] platform gpio-leds.7: Driver leds-gpio requests probe deferral [ 3.266912] ledtrig-cpu: registered to indicate activity on CPUs [ 3.273692] edma-dma-engine edma-dma-engine.0: allocated channel for 0:36 [ 3.280886] omap-sham 53100000.sham: hw accel on OMAP rev 4.3 [ 3.289043] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2 [ 3.295337] edma-dma-engine edma-dma-engine.0: allocated channel for 0:5 [ 3.302514] edma-dma-engine edma-dma-engine.0: allocated channel for 0:6 [ 3.314763] usbcore: registered new interface driver usbhid [ 3.320683] usbhid: USB HID core driver [ 3.327585] TCP: cubic registered [ 3.331107] Initializing XFRM netlink socket [ 3.335689] NET: Registered protocol family 17 [ 3.340582] NET: Registered protocol family 15 [ 3.345454] Key type dns_resolver registered [ 3.350088] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3 [ 3.358166] ThumbEE CPU extension supported. [ 3.362675] Registering SWP/SWPB emulation handler [ 3.368694] registered taskstats version 1 [ 3.375319] of_get_named_gpio_flags exited with status -517 [ 3.375393] platform gpio-leds.7: Driver leds-gpio requests probe deferral [ 3.432357] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6 [ 3.438767] davinci_mdio 4a101000.mdio: detected phy mask fffffffe [ 3.453288] libphy: 4a101000.mdio: probed [ 3.457601] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720 [ 3.467832] [ 3.472507] cpsw 4a100000.ethernet: NAPI disabled [ 3.477894] of_get_named_gpio_flags exited with status -517 [ 3.477960] platform gpio-leds.7: Driver leds-gpio requests probe deferral [ 3.486669] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800) [ 3.495951] cpu0 supply cpu0 not found, using dummy regulator [ 3.502437] cpufreq_cpu0: failed to scale voltage up: -22 [ 3.508271] cpufreq_cpu0: failed to scale voltage up: -22 [ 3.521063] ALSA device list: [ 3.524301] No soundcards found. [ 3.528873] Freeing init memory: 264K [ 3.532928] Failed to execute /init [ 4.533755] 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.846283] net eth0: initializing cpsw version 1.12 (0) [ 5.855234] net eth0: phy found : id is : 0x7c0f1 [ 5.862593] libphy: PHY 4a101000.mdio:01 not found [ 5.867838] net eth0: phy 4a101000.mdio:01 not found on slave 1 [ 8.930905] libphy: 4a101000.mdio:00 - Link is Up - 100/Full Mar 29 20:41:06 (none) local0.err cgminer[368]: Miner compile time: Mon Jul 15 15:44:23 CST 2019 type: Antminer L3++ Mar 29 20:41:06 (none) local0.warn cgminer[368]: Started cgminer 4.9.0 Mar 29 20:41:06 (none) local0.notice cgminer[368]: detected at /sys/class/gpio/gpio51/value chain 0 Mar 29 20:41:06 (none) local0.notice cgminer[368]: detected at /sys/class/gpio/gpio48/value chain 1 Mar 29 20:41:06 (none) local0.notice cgminer[368]: detected at /sys/class/gpio/gpio47/value chain 2 Mar 29 20:41:06 (none) local0.notice cgminer[368]: detected at /sys/class/gpio/gpio44/value chain 3 Mar 29 20:41:06 (none) local0.notice cgminer[368]: detect total chain num 4 Mar 29 20:41:06 (none) local0.notice cgminer[368]: i2c init ok Mar 29 20:41:15 (none) local0.notice cgminer[368]: in tty_init Mar 29 20:41:15 (none) local0.notice cgminer[368]: tty_init 0 Mar 29 20:41:15 (none) local0.notice cgminer[368]: Start A New Asic Response.Chain Id:[0] Mar 29 20:41:16 (none) local0.notice cgminer[368]: tty_init 1 Mar 29 20:41:16 (none) local0.notice cgminer[368]: Start A New Asic Response.Chain Id:[1] Mar 29 20:41:16 (none) local0.notice cgminer[368]: tty_init 2 Mar 29 20:41:16 (none) local0.notice cgminer[368]: Start A New Asic Response.Chain Id:[2] Mar 29 20:41:16 (none) local0.notice cgminer[368]: tty_init 3 Mar 29 20:41:16 (none) local0.notice cgminer[368]: Start A New Asic Response.Chain Id:[3] Mar 29 20:41:16 (none) local0.notice cgminer[368]: open device over Mar 29 20:41:16 (none) local0.notice cgminer[368]: send cmd to get chip address Mar 29 20:41:18 (none) local0.notice cgminer[368]: Chain 0 ASIC 0 !!! Mar 29 20:41:18 (none) local0.notice cgminer[368]: Chain 1 ASIC 0 !!! Mar 29 20:41:18 (none) local0.notice cgminer[368]: Chain 2 ASIC 0 !!! Mar 29 20:41:18 (none) local0.notice cgminer[368]: Chain 3 ASIC 0 !!! Mar 29 20:41:18 (none) local0.notice cgminer[368]: Need to recheck asic num !!! Mar 29 20:41:26 (none) local0.err cgminer[442]: Miner compile time: Mon Jul 15 15:44:23 CST 2019 type: Antminer L3++ Mar 29 20:41:26 (none) local0.warn cgminer[442]: Started cgminer 4.9.0 Mar 29 20:41:26 (none) local0.notice cgminer[442]: detected at /sys/class/gpio/gpio51/value chain 0 Mar 29 20:41:26 (none) local0.notice cgminer[442]: detected at /sys/class/gpio/gpio48/value chain 1 Mar 29 20:41:26 (none) local0.notice cgminer[442]: detected at /sys/class/gpio/gpio47/value chain 2 Mar 29 20:41:26 (none) local0.notice cgminer[442]: detected at /sys/class/gpio/gpio44/value chain 3 Mar 29 20:41:26 (none) local0.notice cgminer[442]: detect total chain num 4 Mar 29 20:41:26 (none) local0.notice cgminer[442]: i2c init ok Mar 29 20:41:36 (none) local0.notice cgminer[442]: in tty_init Mar 29 20:41:36 (none) local0.notice cgminer[442]: tty_init 0 Mar 29 20:41:36 (none) local0.notice cgminer[442]: Start A New Asic Response.Chain Id:[0] Mar 29 20:41:36 (none) local0.notice cgminer[442]: tty_init 1 Mar 29 20:41:36 (none) local0.notice cgminer[442]: Start A New Asic Response.Chain Id:[1] Mar 29 20:41:36 (none) local0.notice cgminer[442]: tty_init 2 Mar 29 20:41:36 (none) local0.notice cgminer[442]: Start A New Asic Response.Chain Id:[2] Mar 29 20:41:36 (none) local0.notice cgminer[442]: tty_init 3 Mar 29 20:41:36 (none) local0.notice cgminer[442]: Start A New Asic Response.Chain Id:[3] Mar 29 20:41:36 (none) local0.notice cgminer[442]: open device over Mar 29 20:41:37 (none) local0.notice cgminer[442]: send cmd to get chip address Mar 29 20:41:39 (none) local0.notice cgminer[442]: Chain 0 ASIC 0 !!! Mar 29 20:41:39 (none) local0.notice cgminer[442]: Chain 1 ASIC 0 !!! Mar 29 20:41:39 (none) local0.notice cgminer[442]: Chain 2 ASIC 0 !!! Mar 29 20:41:39 (none) local0.notice cgminer[442]: Chain 3 ASIC 0 !!! Mar 29 20:41:39 (none) local0.notice cgminer[442]: Need to recheck asic num !!! Mar 29 20:41:41 (none) local0.notice cgminer[442]: Chain 0 ASIC 0 !!! Mar 29 20:41:41 (none) local0.notice cgminer[442]: Chain 1 ASIC 0 !!! Mar 29 20:41:41 (none) local0.notice cgminer[442]: Chain 2 ASIC 0 !!! Mar 29 20:41:41 (none) local0.notice cgminer[442]: Chain 3 ASIC 0 !!! Mar 29 20:41:41 (none) local0.notice cgminer[442]: frequency = '450' Mar 29 20:41:41 (none) local0.notice cgminer[442]: dev.timeout = 39 Mar 29 20:41:41 (none) local0.notice cgminer[442]: opt_bitmain_L3_core_temp : 2 Mar 29 20:41:43 (none) local0.notice cgminer[442]: send cmd to open block Mar 29 20:41:45 (none) local0.err cgminer[442]: cgminer time error total_secs = 1617050505.868478 last_total_secs = 1.000000 Mar 29 20:41:46 (none) local0.warn cgminer[442]: Pool 1 stratum+tcp://scrypt.eu-west.nicehash.com:3333 alive, testing stability Mar 29 20:41:46 (none) local0.warn cgminer[442]: Switching to pool 1 stratum+tcp://scrypt.eu-west.nicehash.com:3333 Mar 29 20:41:46 (none) local0.warn cgminer[442]: Pool 0 stratum+tcp://scrypt.eu-north.nicehash.com:3333 alive, testing stability Mar 29 20:41:46 (none) local0.warn cgminer[442]: Switching to pool 0 stratum+tcp://scrypt.eu-north.nicehash.com:3333 Mar 29 20:41:51 (none) local0.warn cgminer[442]: API running in IP access mode on port 4028 (15) Mar 29 20:42:00 (none) local0.warn cgminer[442]: Stratum reconnect requested from pool 0 to scrypt.eu-north.nicehash.com:3333 Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: philipma1957 on March 31, 2021, 02:19:33 AM Did you try a different pool?
Nicehash has a lot of issues with a lot of gear. L3++ is not an L3+ so the issue could be nicehash not the miner. Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: TrophyMiner on March 31, 2021, 05:18:23 PM Did you try a different pool? Nicehash has a lot of issues with a lot of gear. L3++ is not an L3+ so the issue could be nicehash not the miner. yes i tried the antpool too what do you mean the l3++ is not the l3+? ye i know they are different machines but did you see anything unusual that i did? Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: philipma1957 on March 31, 2021, 06:21:40 PM Did you try a different pool? Nicehash has a lot of issues with a lot of gear. L3++ is not an L3+ so the issue could be nicehash not the miner. yes i tried the antpool too what do you mean the l3++ is not the l3+? ye i know they are different machines but did you see anything unusual that i did? I have 22 l3+ I have a few l3 I can see by the photo that you may have a firmware issue. try changing the names of your workers. btcaddress.l3++ make it btc address.l3a btcaddress.l3+++ make it btc address.l3b btcddress.l3++++ make it btcaddress.l3c I think the firmware can't handle the + signs https://i.imgur.com/NL5w9yJ.png Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: TrophyMiner on March 31, 2021, 07:12:39 PM Did you try a different pool? Nicehash has a lot of issues with a lot of gear. L3++ is not an L3+ so the issue could be nicehash not the miner. yes i tried the antpool too what do you mean the l3++ is not the l3+? ye i know they are different machines but did you see anything unusual that i did? I have 22 l3+ I have a few l3 I can see by the photo that you may have a firmware issue. try changing the names of your workers. btcaddress.l3++ make it btc address.l3a btcaddress.l3+++ make it btc address.l3b btcddress.l3++++ make it btcaddress.l3c I think the firmware can't handle the + signs https://i.imgur.com/NL5w9yJ.png o seriously? ;D can that really be a reason for the machine to not hash? lol i just put l3++ then +++ as another name il try it out and see now will just add the names you gave me and see Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: TrophyMiner on March 31, 2021, 07:41:11 PM nope.. sadly same issue no hash power and asic returns 0 :(
i think a custom firmware might solve this but not sure how to install it can you recommend 1? and the steps to install it please Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: LittleS on April 03, 2021, 06:23:15 PM Hi!
Is this your only l3 miner? If not then you can try to put those hashboards to another of your machines and see if they start to work. If you want to use firmware then i would suggest Vnish for l3+. https://vnish.net/ Vnish is also availiable in Telegram for further questions. LittleS Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: TrophyMiner on April 03, 2021, 06:38:22 PM Hi! Is this your only l3 miner? If not then you can try to put those hashboards to another of your machines and see if they start to work. If you want to use firmware then i would suggest Vnish for l3+. https://vnish.net/ Vnish is also availiable in Telegram for further questions. LittleS i got an s9 running but i dont want to swap boards and open it when i try to update through vnish it says signature failed so i guess i need the sd card method which i cannot find on there site do they have any sd card method? Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: LittleS on April 03, 2021, 06:59:16 PM Hi! Is this your only l3 miner? If not then you can try to put those hashboards to another of your machines and see if they start to work. If you want to use firmware then i would suggest Vnish for l3+. https://vnish.net/ Vnish is also availiable in Telegram for further questions. LittleS i got an s9 running but i dont want to swap boards and open it when i try to update through vnish it says signature failed so i guess i need the sd card method which i cannot find on there site do they have any sd card method? Here is info, how to do it: https://vnish-firmware.com/en/razgon-antminer-l3/ Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: TrophyMiner on April 03, 2021, 08:54:25 PM ok i have installed a custom firmware from vnish but it seems i still have the same issue :(
here are some screenshots https://i.postimg.cc/X7WCDm2K/1st.jpg https://i.postimg.cc/d3jLYQW2/2nd.jpg Quote Apr 3 21:17:16 (none) local0.err cgminer: Miner compile time: Wed Mar 10 12:00:25 CST 2021 type: Antminer L3+ (vnish 3.8.8) Apr 3 21:17:16 (none) local0.warn cgminer: Started cgminer 4.11.1 Apr 3 21:17:16 (none) local0.notice cgminer: Pool checking.. Apr 3 21:17:17 (none) local0.warn cgminer: Succeeded pool 0 Apr 3 21:17:18 (none) local0.warn cgminer: Succeeded pool 1 Apr 3 21:17:20 (none) local0.warn cgminer: Succeeded pool 2 Apr 3 21:17:24 (none) local0.notice cgminer[383]: Fan check skipped.. Apr 3 21:17:24 (none) local0.notice cgminer[383]: detected at /sys/class/gpio/gpio51/value chain 0 Apr 3 21:17:24 (none) local0.notice cgminer[383]: detected at /sys/class/gpio/gpio48/value chain 1 Apr 3 21:17:24 (none) local0.notice cgminer[383]: detected at /sys/class/gpio/gpio47/value chain 2 Apr 3 21:17:24 (none) local0.notice cgminer[383]: detected at /sys/class/gpio/gpio44/value chain 3 Apr 3 21:17:24 (none) local0.notice cgminer[383]: detect total chain num 4 Apr 3 21:17:24 (none) local0.notice cgminer[383]: i2c init ok Apr 3 21:17:33 (none) local0.notice cgminer[383]: in tty_init Apr 3 21:17:33 (none) local0.notice cgminer[383]: tty_init 0 Apr 3 21:17:33 (none) local0.notice cgminer[383]: Start A New Asic Response.Chain Id:[0] Apr 3 21:17:33 (none) local0.notice cgminer[383]: tty_init 1 Apr 3 21:17:33 (none) local0.notice cgminer[383]: Start A New Asic Response.Chain Id:[1] Apr 3 21:17:33 (none) local0.notice cgminer[383]: tty_init 2 Apr 3 21:17:33 (none) local0.notice cgminer[383]: Start A New Asic Response.Chain Id:[2] Apr 3 21:17:34 (none) local0.notice cgminer[383]: tty_init 3 Apr 3 21:17:34 (none) local0.notice cgminer[383]: Start A New Asic Response.Chain Id:[3] Apr 3 21:17:34 (none) local0.notice cgminer[383]: open device over Apr 3 21:17:34 (none) local0.notice cgminer[383]: Set Chain 0, Voltage: 0x05 Apr 3 21:17:35 (none) local0.notice cgminer[383]: Set Chain 1, Voltage: 0x05 Apr 3 21:17:35 (none) local0.notice cgminer[383]: Set Chain 2, Voltage: 0x05 Apr 3 21:17:36 (none) local0.notice cgminer[383]: Set Chain 3, Voltage: 0x05 Apr 3 21:17:36 (none) local0.notice cgminer[383]: send cmd to get chip address Apr 3 21:17:38 (none) local0.notice cgminer[383]: Chain 0 ASIC 0 !!! Apr 3 21:17:38 (none) local0.notice cgminer[383]: Chain 1 ASIC 0 !!! Apr 3 21:17:38 (none) local0.notice cgminer[383]: Chain 2 ASIC 0 !!! Apr 3 21:17:38 (none) local0.notice cgminer[383]: Chain 3 ASIC 0 !!! Apr 3 21:17:38 (none) local0.notice cgminer[383]: Need to recheck asic num !!! Apr 3 21:17:57 (none) local0.err cgminer: Miner compile time: Wed Mar 10 12:00:25 CST 2021 type: Antminer L3+ (vnish 3.8.8) Apr 3 21:17:57 (none) local0.warn cgminer: Started cgminer 4.11.1 Apr 3 21:17:57 (none) local0.notice cgminer: Pool checking.. Apr 3 21:17:57 (none) local0.warn cgminer: Succeeded pool 0 Apr 3 21:17:59 (none) local0.warn cgminer: Succeeded pool 1 Apr 3 21:18:00 (none) local0.warn cgminer: Succeeded pool 2 Apr 3 21:18:04 (none) local0.notice cgminer[549]: Fan check skipped.. Apr 3 21:18:04 (none) local0.notice cgminer[549]: detected at /sys/class/gpio/gpio51/value chain 0 Apr 3 21:18:04 (none) local0.notice cgminer[549]: detected at /sys/class/gpio/gpio48/value chain 1 Apr 3 21:18:04 (none) local0.notice cgminer[549]: detected at /sys/class/gpio/gpio47/value chain 2 Apr 3 21:18:04 (none) local0.notice cgminer[549]: detected at /sys/class/gpio/gpio44/value chain 3 Apr 3 21:18:04 (none) local0.notice cgminer[549]: detect total chain num 4 Apr 3 21:18:04 (none) local0.notice cgminer[549]: i2c init ok Apr 3 21:18:11 (none) local0.err cgminer: Miner compile time: Wed Mar 10 12:00:25 CST 2021 type: Antminer L3+ (vnish 3.8.8) Apr 3 21:18:11 (none) local0.warn cgminer: Started cgminer 4.11.1 Apr 3 21:18:11 (none) local0.notice cgminer: Pool checking.. Apr 3 21:18:12 (none) local0.warn cgminer: Succeeded pool 0 Apr 3 21:18:13 (none) local0.warn cgminer: Succeeded pool 1 Apr 3 21:18:14 (none) local0.warn cgminer: Succeeded pool 2 Apr 3 21:18:17 (none) local0.notice cgminer[602]: Fan check skipped.. Apr 3 21:18:17 (none) local0.notice cgminer[602]: detected at /sys/class/gpio/gpio51/value chain 0 Apr 3 21:18:17 (none) local0.notice cgminer[602]: detected at /sys/class/gpio/gpio48/value chain 1 Apr 3 21:18:17 (none) local0.notice cgminer[602]: detected at /sys/class/gpio/gpio47/value chain 2 Apr 3 21:18:17 (none) local0.notice cgminer[602]: detected at /sys/class/gpio/gpio44/value chain 3 Apr 3 21:18:17 (none) local0.notice cgminer[602]: detect total chain num 4 Apr 3 21:18:17 (none) local0.notice cgminer[602]: i2c init ok Apr 3 21:18:27 (none) local0.notice cgminer[602]: in tty_init Apr 3 21:18:27 (none) local0.notice cgminer[602]: tty_init 0 Apr 3 21:18:27 (none) local0.notice cgminer[602]: Start A New Asic Response.Chain Id:[0] Apr 3 21:18:27 (none) local0.notice cgminer[602]: tty_init 1 Apr 3 21:18:27 (none) local0.notice cgminer[602]: Start A New Asic Response.Chain Id:[1] Apr 3 21:18:27 (none) local0.notice cgminer[602]: tty_init 2 Apr 3 21:18:27 (none) local0.notice cgminer[602]: Start A New Asic Response.Chain Id:[2] Apr 3 21:18:27 (none) local0.notice cgminer[602]: tty_init 3 Apr 3 21:18:27 (none) local0.notice cgminer[602]: Start A New Asic Response.Chain Id:[3] Apr 3 21:18:28 (none) local0.notice cgminer[602]: open device over Apr 3 21:18:28 (none) local0.notice cgminer[602]: Set Chain 0, Voltage: 0x05 Apr 3 21:18:29 (none) local0.notice cgminer[602]: Set Chain 1, Voltage: 0x05 Apr 3 21:18:29 (none) local0.notice cgminer[602]: Set Chain 2, Voltage: 0x05 Apr 3 21:18:30 (none) local0.notice cgminer[602]: Set Chain 3, Voltage: 0x05 Apr 3 21:18:30 (none) local0.notice cgminer[602]: send cmd to get chip address Apr 3 21:18:32 (none) local0.notice cgminer[602]: Chain 0 ASIC 0 !!! Apr 3 21:18:32 (none) local0.notice cgminer[602]: Chain 1 ASIC 0 !!! Apr 3 21:18:32 (none) local0.notice cgminer[602]: Chain 2 ASIC 0 !!! Apr 3 21:18:32 (none) local0.notice cgminer[602]: Chain 3 ASIC 0 !!! Apr 3 21:18:32 (none) local0.notice cgminer[602]: Need to recheck asic num !!! Apr 3 21:18:34 (none) local0.notice cgminer[602]: Chain 0 ASIC 0 !!! Apr 3 21:18:34 (none) local0.notice cgminer[602]: Chain 1 ASIC 0 !!! Apr 3 21:18:34 (none) local0.notice cgminer[602]: Chain 2 ASIC 0 !!! Apr 3 21:18:34 (none) local0.notice cgminer[602]: Chain 3 ASIC 0 !!! Apr 3 21:18:34 (none) local0.notice cgminer[602]: Set CHIP PowerOff Temp=85C Apr 3 21:18:34 (none) local0.notice cgminer[602]: FAN mode auto, target temp 65C Apr 3 21:18:34 (none) local0.notice cgminer[602]: frequency = '600' Apr 3 21:18:34 (none) local0.notice cgminer[602]: dev.timeout = 29 Apr 3 21:18:34 (none) local0.notice cgminer[602]: opt_bitmain_L3_core_temp : 2 Apr 3 21:18:36 (none) local0.notice cgminer[602]: send cmd to open block Apr 3 21:18:39 (none) local0.warn cgminer[602]: Pool 0 alive, testing stability Apr 3 21:18:39 (none) local0.warn cgminer[602]: Switching to pool 0 stratum+tcp://scrypt.eu-west.nicehash.com:3333 Apr 3 21:18:45 (none) local0.warn cgminer[602]: API running in IP access mode on port 4028 (19) Apr 3 21:20:03 (none) local0.warn cgminer[602]: Stratum reconnect requested from pool 0 to scrypt.eu-west.nicehash.com:3333 Apr 3 21:21:20 (none) local0.warn cgminer[602]: Stratum reconnect requested from pool 0 to scrypt.eu-west.nicehash.com:3333 Apr 3 21:24:07 (none) local0.warn cgminer[602]: Stratum reconnect requested from pool 0 to scrypt.eu-west.nicehash.com:3333 other logs Quote [ 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.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: 239584k/239584k available, 22560k 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.015435] pid_max: default: 32768 minimum: 301 [ 0.015668] Security Framework initialized [ 0.015762] Mount-cache hash table entries: 512 [ 0.024585] Initializing cgroup subsys cpuacct [ 0.024618] Initializing cgroup subsys memory [ 0.024680] Initializing cgroup subsys blkio [ 0.024815] CPU: Testing write buffer coherency: ok [ 0.025373] CPU0: thread -1, cpu 0, socket -1, mpidr 0 [ 0.025449] Setting up static identity map for 0x8038c820 - 0x8038c86c [ 0.026771] Brought up 1 CPUs [ 0.026795] SMP: Total of 1 processors activated (545.07 BogoMIPS). [ 0.028101] devtmpfs: initialized [ 0.092493] pinctrl core: initialized pinctrl subsystem [ 0.092707] rstctl core: initialized rstctl subsystem [ 0.093199] regulator-dummy: no parameters [ 0.093768] NET: Registered protocol family 16 [ 0.094471] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.104143] pinctrl-single 44e10800.pinmux: prop pinctrl-0 index 0 invalid phandle [ 0.104324] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568 [ 0.105410] platform 49000000.edma: alias fck already exists [ 0.105444] platform 49000000.edma: alias fck already exists [ 0.105472] platform 49000000.edma: alias fck already exists [ 0.106619] gpiochip_add: registered GPIOs 0 to 31 on device: gpio [ 0.106803] OMAP GPIO hardware version 0.1 [ 0.108206] gpiochip_add: registered GPIOs 32 to 63 on device: gpio [ 0.109525] gpiochip_add: registered GPIOs 64 to 95 on device: gpio [ 0.110840] gpiochip_add: registered GPIOs 96 to 127 on device: gpio [ 0.111478] of_get_named_gpio_flags exited with status 52 [ 0.111509] gpio-rctrl rstctl.3: loaded OK [ 0.116621] omap-gpmc 50000000.gpmc: GPMC revision 6.0 [ 0.119823] hw-breakpoint: debug architecture 0x4 unsupported. [ 0.122007] cpsw.0: No hwaddr in dt. Using c8:fd:19:1f:fb:47 from efuse [ 0.122039] cpsw.1: No hwaddr in dt. Using c8:fd:19:1f:fb:49 from efuse [ 0.137585] bio: create slab <bio-0> at 0 [ 0.149730] edma-dma-engine edma-dma-engine.0: TI EDMA DMA engine driver [ 0.149973] of_get_named_gpio_flags: can't parse gpios property [ 0.150262] vmmcsd_fixed: 3300 mV [ 0.153384] SCSI subsystem initialized [ 0.153836] usbcore: registered new interface driver usbfs [ 0.153951] usbcore: registered new interface driver hub [ 0.154284] usbcore: registered new device driver usb [ 0.156394] omap_i2c 4819c000.i2c: bus 0 rev0.11 at 100 kHz [ 0.156428] omap_i2c 4819c000.i2c: unable to select pin group [ 0.156626] media: Linux media interface: v0.10 [ 0.156722] Linux video capture interface: v2.00 [ 0.156838] pps_core: LinuxPPS API ver. 1 registered [ 0.156854] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 0.157571] Advanced Linux Sound Architecture Driver Initialized. [ 0.158761] Switching to clocksource gp_timer [ 0.176783] NET: Registered protocol family 2 [ 0.177774] TCP established hash table entries: 2048 (order: 2, 16384 bytes) [ 0.177863] TCP bind hash table entries: 2048 (order: 3, 40960 bytes) [ 0.177953] TCP: Hash tables configured (established 2048 bind 2048) [ 0.178044] TCP: reno registered [ 0.178071] UDP hash table entries: 256 (order: 1, 12288 bytes) [ 0.178117] UDP-Lite hash table entries: 256 (order: 1, 12288 bytes) [ 0.178613] NET: Registered protocol family 1 [ 0.179199] RPC: Registered named UNIX socket transport module. [ 0.179220] RPC: Registered udp transport module. [ 0.179234] RPC: Registered tcp transport module. [ 0.179248] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.179637] Trying to unpack rootfs image as initramfs... [ 1.847941] Freeing initrd memory: 11332K [ 1.848697] CPU PMU: probing PMU on CPU 0 [ 1.848731] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available [ 1.849271] omap2_mbox_probe: platform not supported [ 1.853114] VFS: Disk quotas dquot_6.5.2 [ 1.853352] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 1.854740] NFS: Registering the id_resolver key type [ 1.854901] Key type id_resolver registered [ 1.854919] Key type id_legacy registered [ 1.854986] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. [ 1.855441] msgmni has been set to 490 [ 1.858350] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249) [ 1.858375] io scheduler noop registered [ 1.858391] io scheduler deadline registered [ 1.858448] io scheduler cfq registered (default) [ 1.862486] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 1.864921] omap_uart 44e09000.serial: did not get pins for uart0 error: -19 [ 1.865209] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88) is a OMAP UART0 [ 2.526097] console [ttyO0] enabled [ 2.530649] 48022000.serial: ttyO1 at MMIO 0x48022000 (irq = 89) is a OMAP UART1 [ 2.539315] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 90) is a OMAP UART2 [ 2.548004] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 61) is a OMAP UART4 [ 2.556616] 481aa000.serial: ttyO5 at MMIO 0x481aa000 (irq = 62) is a OMAP UART5 [ 2.565645] [drm] Initialized drm 1.1.0 20060810 [ 2.584275] brd: module loaded [ 2.594560] loop: module loaded [ 2.598787] bone-capemgr bone_capemgr.8: Failed to find baseboard eeprom node [ 2.608736] nand_get_flash_type: 2c,da against 2c,da [ 2.614259] ONFI param page 0 valid [ 2.617934] ONFI flash detected [ 2.621254] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron MT29F2G08ABAEAWP), 256MiB, page size: 2048, OOB size: 64 [ 2.633166] omap2-nand: detected x8 NAND flash [ 2.637831] nand: using OMAP_ECC_BCH8_CODE_HW ECC scheme [ 2.643414] omap2-nand: using custom ecc layout [ 2.648256] 10 ofpart partitions found on MTD device omap2-nand.0 [ 2.654650] Creating 10 MTD partitions on "omap2-nand.0": [ 2.660328] 0x000000000000-0x000000020000 : "spl" [ 2.667128] 0x000000020000-0x000000040000 : "spl_backup1" [ 2.674566] 0x000000040000-0x000000060000 : "spl_backup2" [ 2.681968] 0x000000060000-0x000000080000 : "spl_backup3" [ 2.689414] 0x000000080000-0x000000240000 : "u-boot" [ 2.697642] 0x000000240000-0x000000260000 : "bootenv" [ 2.704582] 0x000000260000-0x000000280000 : "fdt" [ 2.711199] 0x000000280000-0x000000780000 : "kernel" [ 2.722235] 0x000000800000-0x000001c00000 : "root" [ 2.745756] 0x000001c00000-0x000003000000 : "config" [ 2.769542] OneNAND driver initializing [ 2.775288] usbcore: registered new interface driver asix [ 2.781107] usbcore: registered new interface driver cdc_ether [ 2.787354] usbcore: registered new interface driver smsc95xx [ 2.793472] usbcore: registered new interface driver net1080 [ 2.799525] usbcore: registered new interface driver cdc_subset [ 2.805817] usbcore: registered new interface driver zaurus [ 2.811822] usbcore: registered new interface driver cdc_ncm [ 2.818539] usbcore: registered new interface driver cdc_acm [ 2.824499] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 2.832880] Initializing USB Mass Storage driver... [ 2.838123] usbcore: registered new interface driver usb-storage [ 2.844421] USB Mass Storage support registered. [ 2.849461] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host) [ 2.856213] musb-hdrc musb-hdrc.0.auto: pdev->id = 0 [ 2.861450] musb-hdrc musb-hdrc.0.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK [ 2.870222] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn) [ 2.870244] musb-hdrc: MHDRC RTL version 2.0 [ 2.870259] musb-hdrc: setup fifo_mode 4 [ 2.870287] musb-hdrc: 28/31 max ep, 16384/16384 memory [ 2.870432] musb-hdrc musb-hdrc.0.auto: *** mode=3 [ 2.875475] musb-hdrc musb-hdrc.0.auto: *** power=250 [ 2.881540] musb-hdrc musb-hdrc.1.auto: pdev->id = 1 [ 2.886776] musb-hdrc musb-hdrc.1.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK [ 2.895547] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn) [ 2.895567] musb-hdrc: MHDRC RTL version 2.0 [ 2.895581] musb-hdrc: setup fifo_mode 4 [ 2.895604] musb-hdrc: 28/31 max ep, 16384/16384 memory [ 2.895744] musb-hdrc musb-hdrc.1.auto: *** mode=1 [ 2.900786] musb-hdrc musb-hdrc.1.auto: *** power=250 [ 2.906095] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver [ 2.912469] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 1 [ 2.920712] musb-hdrc musb-hdrc.1.auto: supports USB remote wakeup [ 2.920816] usb usb1: default language 0x0409 [ 2.920874] usb usb1: udev 1, busnum 1, minor = 0 [ 2.920898] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 2.928026] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 2.935598] usb usb1: Product: MUSB HDRC host driver [ 2.940812] usb usb1: Manufacturer: Linux 3.8.13 musb-hcd [ 2.946479] usb usb1: SerialNumber: musb-hdrc.1.auto [ 2.952466] usb usb1: usb_probe_device [ 2.952495] usb usb1: configuration #1 chosen from 1 choice [ 2.952561] usb usb1: adding 1-0:1.0 (config #1, interface 0) [ 2.952762] hub 1-0:1.0: usb_probe_interface [ 2.952785] hub 1-0:1.0: usb_probe_interface - got id [ 2.952812] hub 1-0:1.0: USB hub found [ 2.956811] hub 1-0:1.0: 1 port detected [ 2.960951] hub 1-0:1.0: standalone hub [ 2.960971] hub 1-0:1.0: individual port power switching [ 2.960989] hub 1-0:1.0: no over-current protection [ 2.961007] hub 1-0:1.0: Single TT [ 2.961028] hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns) [ 2.961049] hub 1-0:1.0: power on to power good time: 10ms [ 2.961103] hub 1-0:1.0: local power source is good [ 2.961217] hub 1-0:1.0: enabling power on all ports [ 2.962295] mousedev: PS/2 mouse device common for all mice [ 2.970226] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0 [ 2.977719] 44e3e000.rtc: already running [ 2.982209] i2c /dev entries driver [ 2.987284] pps_ldisc: PPS line discipline registered [ 2.992756] Driver for 1-wire Dallas network protocol. [ 3.000050] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec [ 3.007891] cpuidle: using governor ladder [ 3.012237] cpuidle: using governor menu [ 3.016822] of_get_named_gpio_flags exited with status 6 [ 3.016842] of_get_named_gpio_flags: can't parse gpios property [ 3.016859] of_get_named_gpio_flags: can't parse gpios property [ 3.016897] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' failed [ 3.024122] omap_hsmmc mmc.4: Failed to get rstctl; not using any [ 3.030941] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25 [ 3.038161] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24 [ 3.045506] mmc.4 supply vmmc_aux not found, using dummy regulator [ 3.052457] omap_hsmmc mmc.4: pins are not configured from the driver [ 3.061362] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000 [ 3.087194] of_get_named_gpio_flags exited with status -517 [ 3.087261] platform gpio-leds.7: Driver leds-gpio requests probe deferral [ 3.095050] ledtrig-cpu: registered to indicate activity on CPUs [ 3.101834] edma-dma-engine edma-dma-engine.0: allocated channel for 0:36 [ 3.109032] omap-sham 53100000.sham: hw accel on OMAP rev 4.3 [ 3.117188] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2 [ 3.123481] edma-dma-engine edma-dma-engine.0: allocated channel for 0:5 [ 3.130654] edma-dma-engine edma-dma-engine.0: allocated channel for 0:6 [ 3.142919] usbcore: registered new interface driver usbhid [ 3.148838] usbhid: USB HID core driver [ 3.155747] TCP: cubic registered [ 3.159267] Initializing XFRM netlink socket [ 3.163824] NET: Registered protocol family 17 [ 3.168718] NET: Registered protocol family 15 [ 3.173569] Key type dns_resolver registered [ 3.178203] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3 [ 3.186285] ThumbEE CPU extension supported. [ 3.190795] Registering SWP/SWPB emulation handler [ 3.196828] registered taskstats version 1 [ 3.203436] of_get_named_gpio_flags exited with status -517 [ 3.203509] platform gpio-leds.7: Driver leds-gpio requests probe deferral [ 3.260479] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6 [ 3.266931] davinci_mdio 4a101000.mdio: detected phy mask fffffffe [ 3.281399] libphy: 4a101000.mdio: probed [ 3.285715] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720 [ 3.295958] Detected MACID = c9:f1:17:19:f6:47 [ 3.300640] cpsw 4a100000.ethernet: NAPI disabled [ 3.306038] of_get_named_gpio_flags exited with status -517 [ 3.306104] platform gpio-leds.7: Driver leds-gpio requests probe deferral [ 3.314823] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800) [ 3.324106] cpu0 supply cpu0 not found, using dummy regulator [ 3.330599] cpufreq_cpu0: failed to scale voltage up: -22 [ 3.336415] cpufreq_cpu0: failed to scale voltage up: -22 [ 3.349199] ALSA device list: [ 3.352434] No soundcards found. [ 3.357001] Freeing init memory: 264K [ 3.361054] Failed to execute /init [ 4.387335] 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.751675] net eth0: initializing cpsw version 1.12 (0) [ 5.760607] net eth0: phy found : id is : 0x7c0f1 [ 5.765989] libphy: PHY 4a101000.mdio:01 not found [ 5.771183] net eth0: phy 4a101000.mdio:01 not found on slave 1 [ 8.837124] libphy: 4a101000.mdio:00 - Link is Up - 100/Full i still cant believe the boards are broken since its a new machine and it cant be all 4 are not working is there any other solution? i have a custom firmware on it now from vnish as you see Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: philipma1957 on April 05, 2021, 02:49:22 AM could be a bad controller.
it does seem odd that all boards are dead ☠️ Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: JayDDee on April 05, 2021, 04:19:31 AM At the risk of stating the obvious, you can't find a solution until you've found the problem.
The only thing you know is all hash boards are not responding. You need to shift your focus on what could affect the hash boards, specifically all of them. 4 bad boards is a possibility but unlikely. The hash boards need power and a data connection to the controller. A problem with either one will make the boards invisible. I made a couple of troubleshooting suggestions in a previous post, maybe you missed them. Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: TrophyMiner on April 05, 2021, 10:58:54 AM At the risk of stating the obvious, you can't find a solution until you've found the problem. The only thing you know is all hash boards are not responding. You need to shift your focus on what could affect the hash boards, specifically all of them. 4 bad boards is a possibility but unlikely. The hash boards need power and a data connection to the controller. A problem with either one will make the boards invisible. I made a couple of troubleshooting suggestions in a previous post, maybe you missed them. can you please link me the post Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: JayDDee on April 05, 2021, 04:37:23 PM I made a couple of troubleshooting suggestions in a previous post, maybe you missed them. can you please link me the post It was a hint to re-read your own thread. There has been a lot of troubleshooting advice you seem to have either ignored or dismissed. Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: TrophyMiner on April 05, 2021, 06:20:32 PM I made a couple of troubleshooting suggestions in a previous post, maybe you missed them. can you please link me the post It was a hint to re-read your own thread. There has been a lot of troubleshooting advice you seem to have either ignored or dismissed. actually i have read a lot on this forum and googled a lot before opening a thread and asking but none of the solutions solved my issue i never saw a person with this issue that 4 boards arent being detected out of the box and even when i find a similiar case they just tell him your boards are fried or try it with another asic and see Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: JayDDee on April 05, 2021, 06:56:51 PM actually i have read a lot on this forum and googled a lot before opening a thread and asking but none of the solutions solved my issue i never saw a person with this issue that 4 boards arent being detected out of the box and even when i find a similiar case they just tell him your boards are fried or try it with another asic and see Don't expect any help if you are so dismissive of the advice you receive. Just do it or stop whining. Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: LittleS on April 06, 2021, 12:35:52 PM Have your tried to reset the machine and build up from ground 0 ?
Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: TrophyMiner on April 06, 2021, 06:44:46 PM actually i have read a lot on this forum and googled a lot before opening a thread and asking but none of the solutions solved my issue i never saw a person with this issue that 4 boards arent being detected out of the box and even when i find a similiar case they just tell him your boards are fried or try it with another asic and see Don't expect any help if you are so dismissive of the advice you receive. Just do it or stop whining. seriously? do you think i can even get my hands on an asic machine at the current market rate? the l3++ or l3+ are obsolete they are done and not in production anymore i came here asking for help and not to argue. if you have nothing to add which is valuable then dont post and turn this thread in to an argument thread please Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: TrophyMiner on April 06, 2021, 06:48:16 PM Have your tried to reset the machine and build up from ground 0 ? these are the steps i tried to do before posting install official firmware reset device leave device open for 2hours try to run board recovery tool from bitmain site steps i did after i opened thread installed vnish cfw changed miner worker name from l3++ to l3a boards still return 0 asic is there any other step i can do? i posted logs above Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: JayDDee on April 06, 2021, 07:28:37 PM actually i have read a lot on this forum and googled a lot before opening a thread and asking but none of the solutions solved my issue i never saw a person with this issue that 4 boards arent being detected out of the box and even when i find a similiar case they just tell him your boards are fried or try it with another asic and see Don't expect any help if you are so dismissive of the advice you receive. Just do it or stop whining. seriously? do you think i can even get my hands on an asic machine at the current market rate? the l3++ or l3+ are obsolete they are done and not in production anymore i came here asking for help and not to argue. if you have nothing to add which is valuable then dont post and turn this thread in to an argument thread please Yes seriously. I'm telling you what's needed to find the problem. Whether you have the tools and skills to do it doesn't change the problem. I gave you alternatives to using a second machine but you ignored those too. Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: TrophyMiner on April 06, 2021, 08:20:35 PM actually i have read a lot on this forum and googled a lot before opening a thread and asking but none of the solutions solved my issue i never saw a person with this issue that 4 boards arent being detected out of the box and even when i find a similiar case they just tell him your boards are fried or try it with another asic and see Don't expect any help if you are so dismissive of the advice you receive. Just do it or stop whining. seriously? do you think i can even get my hands on an asic machine at the current market rate? the l3++ or l3+ are obsolete they are done and not in production anymore i came here asking for help and not to argue. if you have nothing to add which is valuable then dont post and turn this thread in to an argument thread please Yes seriously. I'm telling you what's needed to find the problem. Whether you have the tools and skills to do it doesn't change the problem. I gave you alternatives to using a second machine but you ignored those too. how can i use a second machine if i dont have 1? the only machine i got is an s9 se and that is a different machine which isnt compatible with the l3++ the problem is the boards arent being detected i opened them and checked them with a microscope they are very clean and no signs of burn or anything else.. so the problem is why arent the board being detected? i tried installing a new firmware a custom firmware reset etc and none work.. i just cant seem to find anyone on the internet with the same problem Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: philipma1957 on April 06, 2021, 09:35:03 PM Have your tried to reset the machine and build up from ground 0 ? these are the steps i tried to do before posting install official firmware reset device leave device open for 2hours try to run board recovery tool from bitmain site steps i did after i opened thread installed vnish cfw changed miner worker name from l3++ to l3a boards still return 0 asic is there any other step i can do? i posted logs above yes can mail me 1 of the dead boards and let me test it on my working l3 gear . You only have 1 machine and you may have 4 dead boards you may have a dead controller you may have an incorrectly programmed controller. So you are dead in the water and need working gear to determine if your boards are dead. I am usa based I am running 20 plus l3 and l3+ units you have l3++ but the boards will work on an l3+ controller. there is simply no way to help you without working gear being put into the mix you can buy a controller on ebay usa based https://www.ebay.com/itm/USED-Antminer-L3-A3-D3-Control-Board-READY-TO-SHIP/264655329783?hash=item3d9eafd9f7:g:0iAAAOSwHwRejpUg europe based https://www.ebay.com/itm/antminer-L3-D3-A3-X3-control-board-NEW/274722462537?hash=item3ff6bc1b49:g:RToAAOSwp~RgUObP Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: JayDDee on April 06, 2021, 09:35:26 PM Those logs weren't in your first post. Did you do something to cause a change? Anything that changes the symptoms is a clue. In your first post I noticed it detected all 4 boards but they seem to have failed to respond. You could try removing one board to see if the logs change. That might identify a connectivity issue. Another thought is to call up old customers, they might be able to help. I hate repeating myself. Don't expect a miracle, there's a limit to how much troubleshooting you can do without swapping parts. At best you might get a clue as to which part you may want to replace first. Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: TrophyMiner on April 06, 2021, 11:20:24 PM Have your tried to reset the machine and build up from ground 0 ? these are the steps i tried to do before posting install official firmware reset device leave device open for 2hours try to run board recovery tool from bitmain site steps i did after i opened thread installed vnish cfw changed miner worker name from l3++ to l3a boards still return 0 asic is there any other step i can do? i posted logs above yes can mail me 1 of the dead boards and let me test it on my working l3 gear . You only have 1 machine and you may have 4 dead boards you may have a dead controller you may have an incorrectly programmed controller. So you are dead in the water and need working gear to determine if your boards are dead. I am usa based I am running 20 plus l3 and l3+ units you have l3++ but the boards will work on an l3+ controller. there is simply no way to help you without working gear being put into the mix you can buy a controller on ebay usa based https://www.ebay.com/itm/USED-Antminer-L3-A3-D3-Control-Board-READY-TO-SHIP/264655329783?hash=item3d9eafd9f7:g:0iAAAOSwHwRejpUg europe based https://www.ebay.com/itm/antminer-L3-D3-A3-X3-control-board-NEW/274722462537?hash=item3ff6bc1b49:g:RToAAOSwp~RgUObP actually i already bought a new controller the controller out of the box wasnt working for some reason the IP wasnt being detected no matter what i did to fix it it never worked.. the new board worked as soon as i started the asic so i think the board is good i could send you a board but i have to check with the post if the shipment is opened yet or not to usa Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: TrophyMiner on April 06, 2021, 11:23:25 PM Those logs weren't in your first post. Did you do something to cause a change? Anything that changes the symptoms is a clue. In your first post I noticed it detected all 4 boards but they seem to have failed to respond. You could try removing one board to see if the logs change. That might identify a connectivity issue. Another thought is to call up old customers, they might be able to help. I hate repeating myself. Don't expect a miracle, there's a limit to how much troubleshooting you can do without swapping parts. At best you might get a clue as to which part you may want to replace first. i tried this when you asked me too just forgot to post i checked boards 1 by 1 solo 1 controller cable conected from slot 1 to slot 1 + 2 psu slots per asic board and nothing changed it all returned 0 asic i tested this with all 4 boards Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: JayDDee on April 07, 2021, 12:05:57 AM Those logs weren't in your first post. Did you do something to cause a change? Anything that changes the symptoms is a clue. In your first post I noticed it detected all 4 boards but they seem to have failed to respond. You could try removing one board to see if the logs change. That might identify a connectivity issue. Another thought is to call up old customers, they might be able to help. I hate repeating myself. Don't expect a miracle, there's a limit to how much troubleshooting you can do without swapping parts. At best you might get a clue as to which part you may want to replace first. i tried this when you asked me too just forgot to post i checked boards 1 by 1 solo 1 controller cable conected from slot 1 to slot 1 + 2 psu slots per asic board and nothing changed it all returned 0 asic i tested this with all 4 boards That makes it even less likely it's a hash board problem. There are no obvious issues with the controller booting so it could be communications between the controller and the hash boards. Unless it's something simple like a bad cable it might require major surgery. However, I'm always suspicious when something fails out of the box. I always quadruple check everything in case I missed something in setup. Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: TrophyMiner on April 07, 2021, 06:54:10 PM Those logs weren't in your first post. Did you do something to cause a change? Anything that changes the symptoms is a clue. In your first post I noticed it detected all 4 boards but they seem to have failed to respond. You could try removing one board to see if the logs change. That might identify a connectivity issue. Another thought is to call up old customers, they might be able to help. I hate repeating myself. Don't expect a miracle, there's a limit to how much troubleshooting you can do without swapping parts. At best you might get a clue as to which part you may want to replace first. i tried this when you asked me too just forgot to post i checked boards 1 by 1 solo 1 controller cable conected from slot 1 to slot 1 + 2 psu slots per asic board and nothing changed it all returned 0 asic i tested this with all 4 boards That makes it even less likely it's a hash board problem. There are no obvious issues with the controller booting so it could be communications between the controller and the hash boards. Unless it's something simple like a bad cable it might require major surgery. However, I'm always suspicious when something fails out of the box. I always quadruple check everything in case I missed something in setup. yes i thought its a cable issue but 4 cables are all damaged? the control board connects to the IP shows the kernel log shows the network connecting successfully but doesnt hash. could it be that the control board is not compatible with the l3++? like i mentioned earlier the original control board had an issue with not getting the ip so i bought a new one but it has a green board instead of a black 1 but the version is the same L2_IO_Board_V1.2 maybe the l3++ is just different from the l3+ and l3 i could be wrong but just saying because its weird that its not hashing and all 4 hash boards arent being detected Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: mezerwi on July 15, 2021, 10:11:31 AM I have exact same issue.
Long time did not open the box when open, hashboard not detect. swap with other working machine same issue, it did not detect the hashboard. have you found solution? Title: Re: Antminer connected but isnt mining 0 hashrate issue Post by: bebote on November 14, 2021, 07:23:36 AM I have the same problem someone could solve I have an antminer l3 + that does not have the 4 hashoard
|
