Title: L3+ startup issue Post by: ccgllc on April 03, 2018, 11:33:42 PM Hi all.
I run over a 100 S9s so am somewhat familiar with Bitmains front ends. Just received my first (4) L3+s. Hooked them up, powered them up (with APW3++s running on 220V), and waited. And waited. And waited some more (now 53 minutes), and all I get is the basic web screen. S9s can take over 20 minutes during their first boot to scan the cards. Figured the L3+ has 4 cards vs. the S9s 3, so it might take a half hour or so. Now its been substantially longer than that. Also find it odd that the kernel log is blank on all 4. I can web into them, but otherwise zip. Any suggestions? Zero experience with these things. Bought them because I had room in my data center, $400 coupons to burn, and a strong curiosity. Correction: Kernel log was just VERY slow to respond. Looking for errors I found the following repeating in the logs: Code: Apr 3 23:38:37 (none) local0.err cgminer[8003]: Get [1]Temp Data Failed! Title: Re: L3+ startup issue Post by: Lafu on April 04, 2018, 12:53:47 AM You should be get this for start up the miner !
[ 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: 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) Apr 1 05:22:52 (none) local0.notice cgminer[17489]: Chain 1 chip 0 RemoteTemp 0x2a Apr 1 05:22:52 (none) local0.notice cgminer[17489]: Chain 2 chip 0 RemoteTemp 0x29 Apr 1 05:22:52 (none) local0.notice cgminer[17489]: Chain 3 chip 0 RemoteTemp 0x2a Looks like something wrong with Temp maybe , Fans are all conected right ? because if 1 Fan not conected it looks like the miner starts but he dosnt ! maybe try to press the reset button near the Lan conector maybe this helps , ! Regards Lafu Title: Re: L3+ startup issue Post by: ccgllc on April 04, 2018, 01:20:20 AM Found it. Stupid User Error.
S9s all come configured to mine on Antpool, and in fact will do so once powered up until you get around to changing it. I expected the same behavior from the L3s, and a quick glance showed they had pool definitions. What I didn't notice is that the pool definitions were all invalid. Once I pointed the miner to my chosen pools, they came up quickly. This was complicated by apparent support by Awesome Miner, which was a bad assumption on my part. AM can monitor them just fine, but apparently can't control them as well as it does S9s. So just a bit of newbie growing pains. |