Bitcoin Forum

Alternate cryptocurrencies => Mining (Altcoins) => Topic started by: blissz on January 05, 2018, 01:01:55 PM



Title: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: blissz on January 05, 2018, 01:01:55 PM
WARNING THIS FIRMWARE MIGHT VOID THE WARRANTY ON YOUR MINER

https://img4.hostingpics.net/pics/145857banner.jpg



https://img15.hostingpics.net/pics/893377382.jpg

https://img15.hostingpics.net/pics/550407481.jpg

v1.02 :: 14/01/2018 :: L3+ recommended update

Download:
temporary removed, see last message in this topic


Upgrade instructions:
  • Recommended, at your current firmware, set the miner frequency at 350mhz before flashing.
  • Download the custom firmware. (don't unpack it)
  • Flash by going to "System" -> "Upgrade" -> "Flash new firmware image" and select the custom firmware.
  • When the reboot is complete: please clear your browser cache or use ctrl + f5 if you don't see the pages  properly loaded
  • Then check the advanced settings page and set the global values to the lowest voltage setting and 375mhz. From there increase your frequency to see how high you can go at the lowest voltage setting.
  • Start tweaking some more. See the profile suggestions below.

v1.02 L3+ version 14/01/2018:
- adds power usage (Watt) indication per chain in the mining status overview. Really useful for if you don't own a wattage meter
- cleaned kernel logging when not using all the pools
- cleaned API code for faster miner status update speed.

v1.01 L3+ version 13/01/2018:
- Fixed an issue where the status page was empty on lowest voltage setting.

v1.0 L3+ version 12/01/2018:
- first stable release  8)
- reboot (and cool down) on too high temperatures (PCB temp > 85 deg celcius)
- optional: reboot on too high ASIC fail count
- optional: reboot on detection of low hashrate (if falls down 8% under the expected hashrate)
- now shows the voltage setting on the overview page
- fixed showing high FAN speed RPM's
- added option to mine the dev fee one time a day (increases daily profit a bit in case you run it on one pool)

v0.02 L3+ version 05/01/2018:
- awesome miner support / other API tools now compatible
- fixed frequency ranges in advanced miner page

First L3+ version 05/01/2018:
- Adds unlocked voltage global or individual per chain. Saves up to 20% energy usage compared to the stock firmware. (unit runs ~500Mh/s @ ~670watt)
- Adds frequency setting per individual chain.
- cgminer update to 4.10
- Adds 3 fan profile modes
- No more high fan speed durings startup
- Faster startup time
- Cleaned up web interface
- Cleaned up kernel log
- Possible to flash back to the default firmware (see guide below)
- Possible to change the stock fans for custom fans

know issues:
- Only tested on L3+. Unsure if this runs on the a normal L3 (non plus).

Important:
- As this firmware allows extreme overclocking / reduce fan speeds, I am not responsible for any damage to your miner. So flash at your own risk and please use the firmware wisely.
- There is a 1,5% mining fee as compensation for the effort I put into this project.

Some startup settings to get you going:

stock speeds @ low power -> silenced and improved miner lifetime (my personal preference)

Expected hashrate: 480MH/s to 540 MH/s
Expected power usage: 600 - 770 watt

set the global frequency at "375" and increase upto 425mhz (depends per unit how far it clocks stable), set the global voltage to "lowest". Now slowly increase the frequency from 375Mhz to 425 until you see HW errors. When you have a few HW errors an hour you found the sweet spot
set the fan speed to silent for silent operation.

More profiles to come...
...


Back to bitmain stock firmware:
In case you want to go back to the original firmware:
- set the voltage of all boards to 12 or 13 before flashing back (just to make sure...)
- download and flash the stock firmware image: https://shop.bitmain.com/support.htm?pid=0072017042706354248975UNDh65062D (https://shop.bitmain.com/support.htm?pid=0072017042706354248975UNDh65062D)
- reset to defaults

Guide if your boards doesn't get recognized / if you accidently flashed the D3 firmware on your L3+
- set the global voltage to 13 (as it can be the case that your boards don't like a low voltage)
if that doesn't work:
- disconnect all hashing boards from the controller and start it up. Try to flash the stock firmware
Then reconnect the hashing boards.
- if flashing doesn't work: do the same but use the micro sd card recovery (see topic start).
- if the stock firmware doesn't work, have a look here: https://bitcointalk.org/index.php?topic=2383200.0 then your hashing boards needs to be recovered one by one.

Firmware recovery:
This is only needed if the miner doesn't boot anymore (In case you had a bad / interrupted) flash:
- get a microsd card
- write this image to it with win32diskimager: https://shop.bitmain.com/support.htm?pid=007201604120945219855QObfk20066C (https://shop.bitmain.com/support.htm?pid=007201604120945219855QObfk20066C)
- insert the micro sd card in the d3 controller board and power it on. The miner webinterface will come up again. (maybe under another ip)
- redownload the firmware and flash again.
- remove the micro sd card

Special thanks goes to:
- cryptonitro for this awesome new Antminer icon

D3 custom firmware available here:
https://bitcointalk.org/index.php?topic=2346161.0 (https://bitcointalk.org/index.php?topic=2346161.0)


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: blissz on January 05, 2018, 01:02:07 PM
reserved


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: blissz on January 05, 2018, 01:04:09 PM
As requested by a lot of people through PM, I am happy to announce the first Beta for the L3+. Please read the above carefully and let me know how it works for you 8)

Important: This have not been tested on a standard L3 (non plus). I am not sure if it will work, it might need a different build. Let me know if you're brave enough to try it


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: Littledragons on January 05, 2018, 02:43:18 PM
YESSS Im pumped!
Ill flash it up right now.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: blissz on January 05, 2018, 02:45:23 PM
YESSS Im pumped!
Ill flash it up right now.

:D Let me know how it goes for you. You got a wattmeter?


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: Littledragons on January 05, 2018, 03:05:37 PM
YESSS Im pumped!
Ill flash it up right now.

:D Let me know how it goes for you. You got a wattmeter?
I do I just got one of mine steady with low/no HW - Ill have to go check it really quick


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: Littledragons on January 05, 2018, 03:23:56 PM
Welp - I was able to get 510 MHs on 394Mhz on the lowest setting - sadly it looks like my OG killawatt comitted sepuku and I cant get a reading for ya though - I figured I would at least report back that it does indeed work and no issues as far as I can tell!
Im about to flash it again on the 2nd machine I have. Ill report back with any progress.
I love the silent mode - definitely a must have for apartment living.
Does the addition of awesomeminer increase hash? Just curious as Ive had splendid success with the D3 version!
I followed your suggestion, its in the living room =D


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: blissz on January 05, 2018, 03:37:05 PM
Welp - I was able to get 510 MHs on 394Mhz on the lowest setting - sadly it looks like my OG killawatt comitted sepuku and I cant get a reading for ya though - I figured I would at least report back that it does indeed work and no issues as far as I can tell!
Im about to flash it again on the 2nd machine I have. Ill report back with any progress.
I love the silent mode - definitely a must have for apartment living.
Does the addition of awesomeminer increase hash? Just curious as Ive had splendid success with the D3 version!
I followed your suggestion, its in the living room =D

Ok probably someone else will have a wattmeter to do some measurements. But good to hear it works well for you!


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: cryptonitro on January 05, 2018, 03:39:10 PM
Hey, nice news , thanks to warn me about it
will test :)


got wattmeter but only 3 boards working , so may be not precise result


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: blissz on January 05, 2018, 03:40:08 PM
Hey, nice news , thanks to warn me about it
will test :)


Thank, let me know how it works! You're still on 3 chains by the way? Or got that broken chain working again?


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: r00tdude on January 05, 2018, 03:40:54 PM
Thanks for the firmware - before I load in on my rigs, how is the mining fee handled so I know what to expect? Any chance I can just pay up front and not have my mining interrupted? I rent my rigs and if the rigs change pools it will interrupt renting.

Thanks!


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: blissz on January 05, 2018, 03:47:55 PM
Thanks for the firmware - before I load in on my rigs, how is the mining fee handled so I know what to expect? Any chance I can just pay up front and not have my mining interrupted? I rent my rigs and if the rigs change pools it will interrupt renting.

Thanks!

It's yet the same as on the D3's: 5 minutes after startup it will mine 1 minute and 50 seconds and then 2 hours on your configured pool. After those 2 hours, 1 min 50 on the dev pool again etc...
Regarding the rental: just indicate you have 1,5% less hashrate then calculated and it will be fine as your rigs will always be rented for a longer period...
Probably this firmware will allow you to save quite some energy (upto 20%) or allow you to overclock 5 to 10 percent more.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: cryptonitro on January 05, 2018, 03:48:37 PM
see that on logs , dont know if it s normal , can someone check to confirm ?

Code:
Jan  5 15:46:14 (none) local0.err cgminer: Invalid config option --bitmain-freq1: '_ant_reboot_switch_asic=false' is not a number
Jan  5 15:46:14 (none) local0.err cgminer: Invalid config option --bitmain-freq2: '' is not a number
Jan  5 15:46:14 (none) local0.err cgminer: Invalid config option --bitmain-freq3: '' is not a number
Jan  5 15:46:14 (none) local0.err cgminer: Invalid config option --bitmain-freq4: '' is not a number
Jan  5 15:46:14 (none) local0.err cgminer: Invalid config option --bitmain-voltage: '_ant_reboot_switch=false' is not a number
Jan  5 15:46:14 (none) local0.err cgminer: Invalid config option --bitmain-voltage1: '' is not a number
Jan  5 15:46:14 (none) local0.err cgminer: Invalid config option --bitmain-voltage2: '' is not a number
Jan  5 15:46:14 (none) local0.err cgminer: Invalid config option --bitmain-voltage3: '' is not a number
Jan  5 15:46:14 (none) local0.err cgminer: Invalid config option --bitmain-voltage4: '' is not a number

Hey, nice news , thanks to warn me about it
will test :)


Thank, let me know how it works! You're still on 3 chains by the way? Or got that broken chain working again?

yes still 0x0 for my 3rd board , try all chain and lot of flash , all cable etc ...





Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: blissz on January 05, 2018, 03:55:29 PM
see that on logs , dont know if it s normal , can someone check to confirm ?

Code:
Jan  5 15:46:14 (none) local0.err cgminer: Invalid config option --bitmain-freq1: '_ant_reboot_switch_asic=false' is not a number
Jan  5 15:46:14 (none) local0.err cgminer: Invalid config option --bitmain-freq2: '' is not a number
Jan  5 15:46:14 (none) local0.err cgminer: Invalid config option --bitmain-freq3: '' is not a number
Jan  5 15:46:14 (none) local0.err cgminer: Invalid config option --bitmain-freq4: '' is not a number
Jan  5 15:46:14 (none) local0.err cgminer: Invalid config option --bitmain-voltage: '_ant_reboot_switch=false' is not a number
Jan  5 15:46:14 (none) local0.err cgminer: Invalid config option --bitmain-voltage1: '' is not a number
Jan  5 15:46:14 (none) local0.err cgminer: Invalid config option --bitmain-voltage2: '' is not a number
Jan  5 15:46:14 (none) local0.err cgminer: Invalid config option --bitmain-voltage3: '' is not a number
Jan  5 15:46:14 (none) local0.err cgminer: Invalid config option --bitmain-voltage4: '' is not a number

Hey, nice news , thanks to warn me about it
will test :)


Thank, let me know how it works! You're still on 3 chains by the way? Or got that broken chain working again?

yes still 0x0 for my 3rd board , try all chain and lot of flash , all cable etc ...



Change some of your settings so it will save a valid config. Let me know if it works


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: cryptonitro on January 05, 2018, 04:01:52 PM
yes because it was blank , i dont have those logs now

with 384 Mhz and lowest asic i think consumation is less about 30w~ per board.




Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: blissz on January 05, 2018, 04:06:25 PM
yes because it was blank , i dont have those logs now

with 384 Mhz and lowest asic i think consumation is less about 30~35w per board.


Sounds good! That means this saves 130 - 145 watts for 4 boards. Thanks for the input. I will experiment with some overclocking / overvolting tonight  8)


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: Littledragons on January 05, 2018, 04:08:20 PM
Thanks for the firmware - before I load in on my rigs, how is the mining fee handled so I know what to expect? Any chance I can just pay up front and not have my mining interrupted? I rent my rigs and if the rigs change pools it will interrupt renting.

Thanks!

It's yet the same as on the D3's: 5 minutes after startup it will mine 1 minute and 50 seconds and then 2 hours on your configured pool. After those 2 hours, 1 min 50 on the dev pool again etc...
Regarding the rental: just indicate you have 1,5% less hashrate then calculated and it will be fine as your rigs will always be rented for a longer period...
Probably this firmware will allow you to save quite some energy (upto 20%) or allow you to overclock 5 to 10 percent more.
More than worth it IMO.

Especially with being able to clock it like crazy up or down.
I have actually just set it back to 13 v - to see what kind of clocks I could play up to, and got somewhere in the ballpark of 680 stable(ish).
I know its silly, but since then Ive been pushing up from 13 just to see what level it will spit HWs at me - and its so friggin high its obscene. Obviously not good for the machine, but interesting to know for sure.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: EEM on January 05, 2018, 04:16:45 PM
Thanks for the firmware - before I load in on my rigs, how is the mining fee handled so I know what to expect? Any chance I can just pay up front and not have my mining interrupted? I rent my rigs and if the rigs change pools it will interrupt renting.

Thanks!

It's yet the same as on the D3's: 5 minutes after startup it will mine 1 minute and 50 seconds and then 2 hours on your configured pool. After those 2 hours, 1 min 50 on the dev pool again etc...
Regarding the rental: just indicate you have 1,5% less hashrate then calculated and it will be fine as your rigs will always be rented for a longer period...
Probably this firmware will allow you to save quite some energy (upto 20%) or allow you to overclock 5 to 10 percent more.
Will the ASIC reboot before your 1.5 minutes of mining and than reboot for my 2 hours? Thank you for the answer. I have no experience with your soft.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: Littledragons on January 05, 2018, 04:17:45 PM
Thanks for the firmware - before I load in on my rigs, how is the mining fee handled so I know what to expect? Any chance I can just pay up front and not have my mining interrupted? I rent my rigs and if the rigs change pools it will interrupt renting.

Thanks!

It's yet the same as on the D3's: 5 minutes after startup it will mine 1 minute and 50 seconds and then 2 hours on your configured pool. After those 2 hours, 1 min 50 on the dev pool again etc...
Regarding the rental: just indicate you have 1,5% less hashrate then calculated and it will be fine as your rigs will always be rented for a longer period...
Probably this firmware will allow you to save quite some energy (upto 20%) or allow you to overclock 5 to 10 percent more.
Will the ASIC reboot before your 1.5 minutes of mining and than reboot for my 2 hours? Thank you for the answer. I have no experience with your soft.
No it simply swaps pools and then swaps back over


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: CointoHash411 on January 05, 2018, 04:18:11 PM
Wondering if their is also Blissz firmware to allow all those D3's out there to mine other x algos without being locked to x11. This firmware does seem pretty awesome, an I will be testing it out on the L3+'s coming inbound.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: Bajula on January 05, 2018, 06:00:49 PM
woo hoo! anyway gonna sleep then try this out later.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: blissz on January 05, 2018, 07:00:45 PM
More than worth it IMO.

Especially with being able to clock it like crazy up or down.
I have actually just set it back to 13 v - to see what kind of clocks I could play up to, and got somewhere in the ballpark of 680 stable(ish).
I know its silly, but since then Ive been pushing up from 13 just to see what level it will spit HWs at me - and its so friggin high its obscene. Obviously not good for the machine, but interesting to know for sure.

Yeah undervolting is really useful to tame the beast for the people that run these units in their houses, but I am also curious how far it can  be overclocked with a bit more voltage :P I will play around with one of the chains first to see how it goes.
Edit: 680 MH/s is really nice, can you share your settings?


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.01 first beta)
Post by: dottat on January 05, 2018, 08:56:29 PM
@blissz not sure if you know this already or not but if your pools arent reachable during the switchover the unit reboots.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 05, 2018, 10:32:06 PM
v0.02 :: 05/01/2018 :: L3+ BETA recommended update

Download:
https://mega.nz/#!a9QzSaaQ!Mz3lB3Kh7CZsrWWMl2qtUhLIfqJWpCbS-zddLBWVdOg (https://mega.nz/#!a9QzSaaQ!Mz3lB3Kh7CZsrWWMl2qtUhLIfqJWpCbS-zddLBWVdOg)

v0.02 L3+ version 05/01/2018:
- awesome miner support / other API tools now compatible
- fixed frequency ranges in advanced miner page


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 05, 2018, 10:47:11 PM
Because of PM limit per hour posting here.
Fan RPM is also broken: on stock firmware 100% fan is 6600 RPM, while on your FW I get 3600. IDK if this is real value, but nevertheless, I'm concerned about this issue.

Also I repeat an issue about devpools: using Pool Groups for Profit Switching in Awesome Miner leads to removing of the pools in cgminer, therefore cgminer restores pool list after about 5 mins and removes my Profit Switching.
Can't reply you in PM: I'm using it on L3+.

Thanks for the info! I am not yet familiar with pool groups, but can you try the pool groups on the version I just posted? Thanks!


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 05, 2018, 11:04:06 PM

The fan speed is still not 6600, it is 4100 on 100%.
Setting pool groups resets the dev pool list no more. The only remaining issue is fan RPM issue. Again, IDK if it is real.

Thanks for the update on the pool groups. I checked the code and the displayed fan RPM is limited to 4100... Nothing to worry about, but I will remove this in the next version.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: vagueink on January 05, 2018, 11:35:39 PM
Thanks for putting this out there!

Running into some issues after the upgrade...none of my ASIC boards are showing.

Steps I have followed

1. Set frequency to 375
2. Downloaded firmware
3. Flashed firmware (kept settings)
4. Confirmed firmware after reboot but no ASIC cards showing
5. Flashed firmware (didn't keep settings)
6. Confirmed firmware after reboot still no ASIC cards


Here is a screenshot

https://imgur.com/stLP1WZ

Thank you  :)


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 05, 2018, 11:39:46 PM
Thanks for putting this out there!

Running into some issues after the upgrade...none of my ASIC boards are showing.

Steps I have followed

1. Set frequency to 375
2. Downloaded firmware
3. Flashed firmware (kept settings)
4. Confirmed firmware after reboot but no ASIC cards showing
5. Flashed firmware (didn't keep settings)
6. Confirmed firmware after reboot still no ASIC cards


Here is a screenshot

https://imgur.com/stLP1WZ

Thank you  :)

assuming you flashed it on a L3+? :)
There is a flaw in the guide yet, so I will change it: you need to change one of the settings after upgrading the firmware to make sure the config is valid. So change the frequency to let's say 400 and it should all start working


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: vagueink on January 05, 2018, 11:55:25 PM
assuming you flashed it on a L3+? :)
There is a flaw in the guide yet, so I will change it: you need to change one of the settings after upgrading the firmware to make sure the config is valid. So change the frequency to let's say 400 and it should all start working


Yes, it is an L3+ (December batch)

Set frequency to 400...same issue. No ASIC boards showing.

I am also unable to flash back to OEM firmware I get a "tar: invalid magic tar: short read" error message.

https://imgur.com/K27CCIL

Whatcha think?


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 05, 2018, 11:59:59 PM
assuming you flashed it on a L3+? :)
There is a flaw in the guide yet, so I will change it: you need to change one of the settings after upgrading the firmware to make sure the config is valid. So change the frequency to let's say 400 and it should all start working


Yes, it is an L3+ (December batch)

Set frequency to 400...same issue. No ASIC boards showing.

I am also unable to flash back to OEM firmware I get a "tar: invalid magic tar: short read" error message.

https://imgur.com/K27CCIL

Whatcha think?

copy paste and PM your kernel log, so I can have a look

edit: if you're really stuck you can always use the micro sd card recovery method, but I don't think it's needed...


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: Bajula on January 06, 2018, 12:02:04 AM
assuming you flashed it on a L3+? :)
There is a flaw in the guide yet, so I will change it: you need to change one of the settings after upgrading the firmware to make sure the config is valid. So change the frequency to let's say 400 and it should all start working


Yes, it is an L3+ (December batch)

Set frequency to 400...same issue. No ASIC boards showing.

I am also unable to flash back to OEM firmware I get a "tar: invalid magic tar: short read" error message.

https://imgur.com/K27CCIL

Whatcha think?

Doesn't help with the rest but for the back to stock bit.. re-download the bitmain firmware first.  Gonna see if I can flash back real quick on this end.

edit to add just for clarity flashed back fine on this end. Hey I know the odds were it would be fine, but thought it was a good idea to check.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: vagueink on January 06, 2018, 12:06:56 AM
copy paste and PM your kernel log, so I can have a look

edit: if you're really stuck you can always use the micro sd card recovery method, but I don't think it's needed...

[    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.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: 238772k/238772k available, 23372k 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.000356] Calibrating delay loop... 545.07 BogoMIPS (lpj=531968)
[    0.015438] pid_max: default: 32768 minimum: 301
[    0.015671] Security Framework initialized
[    0.015766] Mount-cache hash table entries: 512
[    0.024599] Initializing cgroup subsys cpuacct
[    0.024631] Initializing cgroup subsys memory
[    0.024693] Initializing cgroup subsys blkio
[    0.024829] CPU: Testing write buffer coherency: ok
[    0.025398] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[    0.025472] Setting up static identity map for 0x8038c820 - 0x8038c86c
[    0.026800] Brought up 1 CPUs
[    0.026824] SMP: Total of 1 processors activated (545.07 BogoMIPS).
[    0.028118] devtmpfs: initialized
[    0.092498] pinctrl core: initialized pinctrl subsystem
[    0.092714] rstctl core: initialized rstctl subsystem
[    0.093211] regulator-dummy: no parameters
[    0.093783] NET: Registered protocol family 16
[    0.094485] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.104164] pinctrl-single 44e10800.pinmux: prop pinctrl-0 index 0 invalid phandle
[    0.104346] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[    0.105432] platform 49000000.edma: alias fck already exists
[    0.105467] platform 49000000.edma: alias fck already exists
[    0.105495] platform 49000000.edma: alias fck already exists
[    0.106649] gpiochip_add: registered GPIOs 0 to 31 on device: gpio
[    0.106831] OMAP GPIO hardware version 0.1
[    0.108241] gpiochip_add: registered GPIOs 32 to 63 on device: gpio
[    0.109556] gpiochip_add: registered GPIOs 64 to 95 on device: gpio
[    0.110873] gpiochip_add: registered GPIOs 96 to 127 on device: gpio
[    0.111506] of_get_named_gpio_flags exited with status 52
[    0.111536] gpio-rctrl rstctl.3: loaded OK
[    0.116643] omap-gpmc 50000000.gpmc: GPMC revision 6.0
[    0.119850] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.122039] cpsw.0: No hwaddr in dt. Using 94:e3:6d:e1:8e:58 from efuse
[    0.122072] cpsw.1: No hwaddr in dt. Using 94:e3:6d:e1:8e:5a from efuse
[    0.137625] bio: create slab <bio-0> at 0
[    0.149752] edma-dma-engine edma-dma-engine.0: TI EDMA DMA engine driver
[    0.149992] of_get_named_gpio_flags: can't parse gpios property
[    0.150284] vmmcsd_fixed: 3300 mV
[    0.153406] SCSI subsystem initialized
[    0.153855] usbcore: registered new interface driver usbfs
[    0.153971] usbcore: registered new interface driver hub
[    0.154302] usbcore: registered new device driver usb
[    0.156406] omap_i2c 4819c000.i2c: bus 0 rev0.11 at 100 kHz
[    0.156440] omap_i2c 4819c000.i2c: unable to select pin group
[    0.156637] media: Linux media interface: v0.10
[    0.156732] Linux video capture interface: v2.00
[    0.156847] pps_core: LinuxPPS API ver. 1 registered
[    0.156863] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.157584] Advanced Linux Sound Architecture Driver Initialized.
[    0.158776] Switching to clocksource gp_timer
[    0.176790] NET: Registered protocol family 2
[    0.177786] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[    0.177876] TCP bind hash table entries: 2048 (order: 3, 40960 bytes)
[    0.177966] TCP: Hash tables configured (established 2048 bind 2048)
[    0.178059] TCP: reno registered
[    0.178086] UDP hash table entries: 256 (order: 1, 12288 bytes)
[    0.178131] UDP-Lite hash table entries: 256 (order: 1, 12288 bytes)
[    0.178622] NET: Registered protocol family 1
[    0.179209] RPC: Registered named UNIX socket transport module.
[    0.179231] RPC: Registered udp transport module.
[    0.179245] RPC: Registered tcp transport module.
[    0.179259] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.179645] Trying to unpack rootfs image as initramfs...
[    1.936839] Freeing initrd memory: 12144K
[    1.937487] CPU PMU: probing PMU on CPU 0
[    1.937520] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available
[    1.938068] omap2_mbox_probe: platform not supported
[    1.941902] VFS: Disk quotas dquot_6.5.2
[    1.942232] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.943584] NFS: Registering the id_resolver key type
[    1.943689] Key type id_resolver registered
[    1.943707] Key type id_legacy registered
[    1.943774] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    1.944300] msgmni has been set to 490
[    1.947113] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[    1.947139] io scheduler noop registered
[    1.947155] io scheduler deadline registered
[    1.947204] io scheduler cfq registered (default)
[    1.951225] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    1.953692] omap_uart 44e09000.serial: did not get pins for uart0 error: -19
[    1.954069] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88) is a OMAP UART0
[    2.614902] console [ttyO0] enabled
[    2.619425] 48022000.serial: ttyO1 at MMIO 0x48022000 (irq = 89) is a OMAP UART1
[    2.628135] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 90) is a OMAP UART2
[    2.636779] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 61) is a OMAP UART4
[    2.645431] 481aa000.serial: ttyO5 at MMIO 0x481aa000 (irq = 62) is a OMAP UART5
[    2.654404] [drm] Initialized drm 1.1.0 20060810
[    2.673102] brd: module loaded
[    2.683387] loop: module loaded
[    2.687575] bone-capemgr bone_capemgr.8: Failed to find baseboard eeprom node
[    2.697518] nand_get_flash_type: 2c,f1 against 2c,f1
[    2.703041] ONFI param page 0 valid
[    2.706713] ONFI flash detected
[    2.710034] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xf1 (Micron MT29F1G08ABAEAWP), 128MiB, page size: 2048, OOB size: 64
[    2.721946] omap2-nand: detected x8 NAND flash
[    2.726611] nand: using OMAP_ECC_BCH8_CODE_HW ECC scheme
[    2.732193] omap2-nand: using custom ecc layout
[    2.737061] 10 ofpart partitions found on MTD device omap2-nand.0
[    2.743455] Creating 10 MTD partitions on "omap2-nand.0":
[    2.749132] 0x000000000000-0x000000020000 : "spl"
[    2.755942] 0x000000020000-0x000000040000 : "spl_backup1"
[    2.763392] 0x000000040000-0x000000060000 : "spl_backup2"
[    2.770812] 0x000000060000-0x000000080000 : "spl_backup3"
[    2.778217] 0x000000080000-0x000000240000 : "u-boot"
[    2.786454] 0x000000240000-0x000000260000 : "bootenv"
[    2.793350] 0x000000260000-0x000000280000 : "fdt"
[    2.799983] 0x000000280000-0x000000780000 : "kernel"
[    2.810952] 0x000000800000-0x000001c00000 : "root"
[    2.834415] 0x000001c00000-0x000003000000 : "config"
[    2.858200] OneNAND driver initializing
[    2.863887] usbcore: registered new interface driver asix
[    2.869712] usbcore: registered new interface driver cdc_ether
[    2.875958] usbcore: registered new interface driver smsc95xx
[    2.882077] usbcore: registered new interface driver net1080
[    2.888103] usbcore: registered new interface driver cdc_subset
[    2.894398] usbcore: registered new interface driver zaurus
[    2.900405] usbcore: registered new interface driver cdc_ncm
[    2.907194] usbcore: registered new interface driver cdc_acm
[    2.913146] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    2.921527] Initializing USB Mass Storage driver...
[    2.926767] usbcore: registered new interface driver usb-storage
[    2.933067] USB Mass Storage support registered.
[    2.938110] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
[    2.944823] musb-hdrc musb-hdrc.0.auto: pdev->id = 0
[    2.950069] musb-hdrc musb-hdrc.0.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK
[    2.958840] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    2.958863] musb-hdrc: MHDRC RTL version 2.0
[    2.958878] musb-hdrc: setup fifo_mode 4
[    2.958906] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    2.959055] musb-hdrc musb-hdrc.0.auto: *** mode=3
[    2.964101] musb-hdrc musb-hdrc.0.auto: *** power=250
[    2.970127] musb-hdrc musb-hdrc.1.auto: pdev->id = 1
[    2.975377] musb-hdrc musb-hdrc.1.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK
[    2.984149] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    2.984169] musb-hdrc: MHDRC RTL version 2.0
[    2.984183] musb-hdrc: setup fifo_mode 4
[    2.984205] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    2.984345] musb-hdrc musb-hdrc.1.auto: *** mode=1
[    2.989389] musb-hdrc musb-hdrc.1.auto: *** power=250
[    2.994698] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[    3.001325] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 1
[    3.009584] musb-hdrc musb-hdrc.1.auto: supports USB remote wakeup
[    3.009689] usb usb1: default language 0x0409
[    3.009747] usb usb1: udev 1, busnum 1, minor = 0
[    3.009770] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    3.016899] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.024470] usb usb1: Product: MUSB HDRC host driver
[    3.029685] usb usb1: Manufacturer: Linux 3.8.13 musb-hcd
[    3.035352] usb usb1: SerialNumber: musb-hdrc.1.auto
[    3.041320] usb usb1: usb_probe_device
[    3.041348] usb usb1: configuration #1 chosen from 1 choice
[    3.041412] usb usb1: adding 1-0:1.0 (config #1, interface 0)
[    3.041610] hub 1-0:1.0: usb_probe_interface
[    3.041633] hub 1-0:1.0: usb_probe_interface - got id
[    3.041708] hub 1-0:1.0: USB hub found
[    3.045695] hub 1-0:1.0: 1 port detected
[    3.049834] hub 1-0:1.0: standalone hub
[    3.049853] hub 1-0:1.0: individual port power switching
[    3.049871] hub 1-0:1.0: no over-current protection
[    3.049889] hub 1-0:1.0: Single TT
[    3.049910] hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns)
[    3.049929] hub 1-0:1.0: power on to power good time: 10ms
[    3.049985] hub 1-0:1.0: local power source is good
[    3.050099] hub 1-0:1.0: enabling power on all ports
[    3.051169] mousedev: PS/2 mouse device common for all mice
[    3.059097] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0
[    3.066604] 44e3e000.rtc: already running
[    3.071135] i2c /dev entries driver
[    3.076154] pps_ldisc: PPS line discipline registered
[    3.081639] Driver for 1-wire Dallas network protocol.
[    3.088922] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[    3.096525] cpuidle: using governor ladder
[    3.100845] cpuidle: using governor menu
[    3.105419] of_get_named_gpio_flags exited with status 6
[    3.105439] of_get_named_gpio_flags: can't parse gpios property
[    3.105455] of_get_named_gpio_flags: can't parse gpios property
[    3.105492] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' failed
[    3.112716] omap_hsmmc mmc.4: Failed to get rstctl; not using any
[    3.119527] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25
[    3.126749] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24
[    3.134066] mmc.4 supply vmmc_aux not found, using dummy regulator
[    3.141021] omap_hsmmc mmc.4: pins are not configured from the driver
[    3.151194] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
[    3.175096] of_get_named_gpio_flags exited with status -517
[    3.175163] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[    3.182944] ledtrig-cpu: registered to indicate activity on CPUs
[    3.189719] edma-dma-engine edma-dma-engine.0: allocated channel for 0:36
[    3.196916] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
[    3.205073] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
[    3.211359] edma-dma-engine edma-dma-engine.0: allocated channel for 0:5
[    3.218537] edma-dma-engine edma-dma-engine.0: allocated channel for 0:6
[    3.230816] usbcore: registered new interface driver usbhid
[    3.236737] usbhid: USB HID core driver
[    3.243654] TCP: cubic registered
[    3.247179] Initializing XFRM netlink socket
[    3.251757] NET: Registered protocol family 17
[    3.256619] NET: Registered protocol family 15
[    3.261465] Key type dns_resolver registered
[    3.266106] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    3.274221] ThumbEE CPU extension supported.
[    3.278735] Registering SWP/SWPB emulation handler
[    3.284737] registered taskstats version 1
[    3.291363] of_get_named_gpio_flags exited with status -517
[    3.291434] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[    3.348387] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[    3.354801] davinci_mdio 4a101000.mdio: detected phy mask fffffffe
[    3.369415] libphy: 4a101000.mdio: probed
[    3.373760] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
[    3.383985] Detected MACID = 94:e3:6d:e1:8e:58
[    3.388672] cpsw 4a100000.ethernet: NAPI disabled
[    3.394062] of_get_named_gpio_flags exited with status -517
[    3.394129] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[    3.402847] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[    3.412128] cpu0 supply cpu0 not found, using dummy regulator
[    3.418655] cpufreq_cpu0: failed to scale voltage up: -22
[    3.424462] cpufreq_cpu0: failed to scale voltage up: -22
[    3.437234] ALSA device list:
[    3.440473]   No soundcards found.
[    3.445022] Freeing init memory: 264K
[    3.449076] Failed to execute /init
[    4.440750] 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.777397] net eth0: initializing cpsw version 1.12 (0)
[    5.786449] net eth0: phy found : id is : 0x7c0f1
[    5.791899] libphy: PHY 4a101000.mdio:01 not found
[    5.797092] net eth0: phy 4a101000.mdio:01 not found on slave 1
[    8.864527] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
Jan  5 23:19:32 (none) local0.err cgminer: Miner compile time: Fri Jan 05 23:17:57 CST 2018 type: Antminer L3+ Blissz v0.02 beta
Jan  5 23:19:32 (none) local0.warn cgminer: Started cgminer 4.10.0
Jan  5 23:19:32 (none) local0.notice cgminer[381]:  detected at /sys/class/gpio/gpio51/value  chain 0
Jan  5 23:19:32 (none) local0.notice cgminer[381]:  detected at /sys/class/gpio/gpio48/value  chain 1
Jan  5 23:19:32 (none) local0.notice cgminer[381]:  detected at /sys/class/gpio/gpio47/value  chain 2
Jan  5 23:19:32 (none) local0.notice cgminer[381]:  detected at /sys/class/gpio/gpio44/value  chain 3
Jan  5 23:19:32 (none) local0.notice cgminer[381]: detect total chain num 4
Jan  5 23:19:32 (none) local0.notice cgminer[381]: i2c init ok
Jan  5 23:19:44 (none) local0.notice cgminer[381]: in tty_init
Jan  5 23:19:44 (none) local0.notice cgminer[381]: tty_init 0
Jan  5 23:19:44 (none) local0.notice cgminer[381]: Start A New Asic Response.Chain Id:[0]
Jan  5 23:19:44 (none) local0.notice cgminer[381]: tty_init 1
Jan  5 23:19:44 (none) local0.notice cgminer[381]: Start A New Asic Response.Chain Id:[1]
Jan  5 23:19:44 (none) local0.notice cgminer[381]: tty_init 2
Jan  5 23:19:44 (none) local0.notice cgminer[381]: Start A New Asic Response.Chain Id:[2]
Jan  5 23:19:45 (none) local0.notice cgminer[381]: tty_init 3
Jan  5 23:19:45 (none) local0.notice cgminer[381]: Start A New Asic Response.Chain Id:[3]
Jan  5 23:19:45 (none) local0.notice cgminer[381]: open device over
Jan  5 23:19:45 (none) local0.notice cgminer[381]: send cmd to get chip address
Jan  5 23:19:47 (none) local0.notice cgminer[381]: Chain 0 ASIC 0 !!!
Jan  5 23:19:47 (none) local0.notice cgminer[381]: Chain 1 ASIC 0 !!!
Jan  5 23:19:47 (none) local0.notice cgminer[381]: Chain 2 ASIC 0 !!!
Jan  5 23:19:47 (none) local0.notice cgminer[381]: Chain 3 ASIC 0 !!!
Jan  5 23:19:47 (none) local0.notice cgminer[381]: Need to recheck asic num !!!
Jan  5 23:19:53 (none) local0.err cgminer: Miner compile time: Fri Jan 05 23:17:57 CST 2018 type: Antminer L3+ Blissz v0.02 beta
Jan  5 23:19:53 (none) local0.warn cgminer: Started cgminer 4.10.0
Jan  5 23:19:53 (none) local0.notice cgminer[456]:  detected at /sys/class/gpio/gpio51/value  chain 0
Jan  5 23:19:53 (none) local0.notice cgminer[456]:  detected at /sys/class/gpio/gpio48/value  chain 1
Jan  5 23:19:53 (none) local0.notice cgminer[456]:  detected at /sys/class/gpio/gpio47/value  chain 2
Jan  5 23:19:53 (none) local0.notice cgminer[456]:  detected at /sys/class/gpio/gpio44/value  chain 3
Jan  5 23:19:53 (none) local0.notice cgminer[456]: detect total chain num 4
Jan  5 23:19:53 (none) local0.notice cgminer[456]: i2c init ok
Jan  5 23:20:04 (none) local0.notice cgminer[456]: in tty_init
Jan  5 23:20:04 (none) local0.notice cgminer[456]: tty_init 0
Jan  5 23:20:04 (none) local0.notice cgminer[456]: Start A New Asic Response.Chain Id:[0]
Jan  5 23:20:04 (none) local0.notice cgminer[456]: tty_init 1
Jan  5 23:20:04 (none) local0.notice cgminer[456]: Start A New Asic Response.Chain Id:[1]
Jan  5 23:20:05 (none) local0.notice cgminer[456]: tty_init 2
Jan  5 23:20:05 (none) local0.notice cgminer[456]: Start A New Asic Response.Chain Id:[2]
Jan  5 23:20:05 (none) local0.notice cgminer[456]: tty_init 3
Jan  5 23:20:05 (none) local0.notice cgminer[456]: Start A New Asic Response.Chain Id:[3]
Jan  5 23:20:05 (none) local0.notice cgminer[456]: open device over
Jan  5 23:20:05 (none) local0.notice cgminer[456]: send cmd to get chip address
Jan  5 23:20:07 (none) local0.notice cgminer[456]: Chain 0 ASIC 0 !!!
Jan  5 23:20:07 (none) local0.notice cgminer[456]: Chain 1 ASIC 0 !!!
Jan  5 23:20:07 (none) local0.notice cgminer[456]: Chain 2 ASIC 0 !!!
Jan  5 23:20:07 (none) local0.notice cgminer[456]: Chain 3 ASIC 0 !!!
Jan  5 23:20:07 (none) local0.notice cgminer[456]: Need to recheck asic num !!!
Jan  5 23:20:09 (none) local0.notice cgminer[456]: Chain 0 ASIC 0 !!!
Jan  5 23:20:09 (none) local0.notice cgminer[456]: Chain 1 ASIC 0 !!!
Jan  5 23:20:09 (none) local0.notice cgminer[456]: Chain 2 ASIC 0 !!!
Jan  5 23:20:09 (none) local0.notice cgminer[456]: Chain 3 ASIC 0 !!!
Jan  5 23:20:10 (none) local0.notice cgminer[456]: frequency = '384'
Jan  5 23:20:10 (none) local0.notice cgminer[456]: dev.timeout = 46
Jan  5 23:20:10 (none) local0.notice cgminer[456]: opt_bitmain_L3_core_temp : 2
Jan  5 23:20:11 (none) local0.notice cgminer[456]: send cmd to open block
Jan  5 23:20:15 (none) local0.warn cgminer[456]: Pool 1 stratum+tcp://stratum-ltc.antpool.com:443 alive, testing stability
Jan  5 23:20:15 (none) local0.warn cgminer[456]: Switching to pool 1 stratum+tcp://stratum-ltc.antpool.com:443
Jan  5 23:20:15 (none) local0.warn cgminer[456]: Pool 0 stratum+tcp://stratum-ltc.antpool.com:8888 alive, testing stability
Jan  5 23:20:15 (none) local0.warn cgminer[456]: Switching to pool 0 stratum+tcp://stratum-ltc.antpool.com:8888
Jan  5 23:20:20 (none) local0.warn cgminer[456]: API running in IP access mode on port 4028 (16)
Jan  5 23:24:54 (none) local0.warn cgminer[456]: Switching to pool 3 stratum+tcp://litecoinpool.org:3333
Jan  5 23:26:44 (none) local0.warn cgminer[456]: Switching to pool 0 stratum+tcp://stratum-ltc.antpool.com:8888
Jan  5 23:29:47 (none) local0.err cgminer: Miner compile time: Fri Jan 05 23:17:57 CST 2018 type: Antminer L3+ Blissz v0.02 beta
Jan  5 23:29:47 (none) local0.warn cgminer: Started cgminer 4.10.0
Jan  5 23:29:47 (none) local0.notice cgminer[14451]:  detected at /sys/class/gpio/gpio51/value  chain 0
Jan  5 23:29:47 (none) local0.notice cgminer[14451]:  detected at /sys/class/gpio/gpio48/value  chain 1
Jan  5 23:29:47 (none) local0.notice cgminer[14451]:  detected at /sys/class/gpio/gpio47/value  chain 2
Jan  5 23:29:47 (none) local0.notice cgminer[14451]:  detected at /sys/class/gpio/gpio44/value  chain 3
Jan  5 23:29:47 (none) local0.notice cgminer[14451]: detect total chain num 4
Jan  5 23:29:47 (none) local0.notice cgminer[14451]: i2c init ok
Jan  5 23:29:59 (none) local0.notice cgminer[14451]: in tty_init
Jan  5 23:29:59 (none) local0.notice cgminer[14451]: tty_init 0
Jan  5 23:29:59 (none) local0.notice cgminer[14451]: Start A New Asic Response.Chain Id:[0]
Jan  5 23:29:59 (none) local0.notice cgminer[14451]: tty_init 1
Jan  5 23:29:59 (none) local0.notice cgminer[14451]: Start A New Asic Response.Chain Id:[1]
Jan  5 23:29:59 (none) local0.notice cgminer[14451]: tty_init 2
Jan  5 23:29:59 (none) local0.notice cgminer[14451]: Start A New Asic Response.Chain Id:[2]
Jan  5 23:30:00 (none) local0.notice cgminer[14451]: tty_init 3
Jan  5 23:30:00 (none) local0.notice cgminer[14451]: Start A New Asic Response.Chain Id:[3]
Jan  5 23:30:00 (none) local0.notice cgminer[14451]: open device over
Jan  5 23:30:00 (none) local0.notice cgminer[14451]: send cmd to get chip address
Jan  5 23:30:02 (none) local0.notice cgminer[14451]: Chain 0 ASIC 0 !!!
Jan  5 23:30:02 (none) local0.notice cgminer[14451]: Chain 1 ASIC 0 !!!
Jan  5 23:30:02 (none) local0.notice cgminer[14451]: Chain 2 ASIC 0 !!!
Jan  5 23:30:02 (none) local0.notice cgminer[14451]: Chain 3 ASIC 0 !!!
Jan  5 23:30:02 (none) local0.notice cgminer[14451]: Need to recheck asic num !!!
Jan  5 23:30:16 (none) local0.err cgminer: Miner compile time: Fri Jan 05 23:17:57 CST 2018 type: Antminer L3+ Blissz v0.02 beta
Jan  5 23:30:16 (none) local0.warn cgminer: Started cgminer 4.10.0
Jan  5 23:30:16 (none) local0.notice cgminer[14528]:  detected at /sys/class/gpio/gpio51/value  chain 0
Jan  5 23:30:16 (none) local0.notice cgminer[14528]:  detected at /sys/class/gpio/gpio48/value  chain 1
Jan  5 23:30:16 (none) local0.notice cgminer[14528]:  detected at /sys/class/gpio/gpio47/value  chain 2
Jan  5 23:30:16 (none) local0.notice cgminer[14528]:  detected at /sys/class/gpio/gpio44/value  chain 3
Jan  5 23:30:16 (none) local0.notice cgminer[14528]: detect total chain num 4
Jan  5 23:30:16 (none) local0.notice cgminer[14528]: i2c init ok
Jan  5 23:30:28 (none) local0.notice cgminer[14528]: in tty_init
Jan  5 23:30:28 (none) local0.notice cgminer[14528]: tty_init 0
Jan  5 23:30:28 (none) local0.notice cgminer[14528]: Start A New Asic Response.Chain Id:[0]
Jan  5 23:30:28 (none) local0.notice cgminer[14528]: tty_init 1
Jan  5 23:30:28 (none) local0.notice cgminer[14528]: Start A New Asic Response.Chain Id:[1]
Jan  5 23:30:28 (none) local0.notice cgminer[14528]: tty_init 2
Jan  5 23:30:28 (none) local0.notice cgminer[14528]: Start A New Asic Response.Chain Id:[2]
Jan  5 23:30:28 (none) local0.notice cgminer[14528]: tty_init 3
Jan  5 23:30:28 (none) local0.notice cgminer[14528]: Start A New Asic Response.Chain Id:[3]
Jan  5 23:30:29 (none) local0.notice cgminer[14528]: open device over
Jan  5 23:30:29 (none) local0.notice cgminer[14528]: send cmd to get chip address
Jan  5 23:30:31 (none) local0.notice cgminer[14528]: Chain 0 ASIC 0 !!!
Jan  5 23:30:31 (none) local0.notice cgminer[14528]: Chain 1 ASIC 0 !!!
Jan  5 23:30:31 (none) local0.notice cgminer[14528]: Chain 2 ASIC 0 !!!
Jan  5 23:30:31 (none) local0.notice cgminer[14528]: Chain 3 ASIC 0 !!!
Jan  5 23:30:31 (none) local0.notice cgminer[14528]: Need to recheck asic num !!!
Jan  5 23:30:33 (none) local0.notice cgminer[14528]: Chain 0 ASIC 0 !!!
Jan  5 23:30:33 (none) local0.notice cgminer[14528]: Chain 1 ASIC 0 !!!
Jan  5 23:30:33 (none) local0.notice cgminer[14528]: Chain 2 ASIC 0 !!!
Jan  5 23:30:33 (none) local0.notice cgminer[14528]: Chain 3 ASIC 0 !!!
Jan  5 23:30:33 (none) local0.notice cgminer[14528]: frequency = '375'
Jan  5 23:30:33 (none) local0.notice cgminer[14528]: dev.timeout = 47
Jan  5 23:30:33 (none) local0.notice cgminer[14528]: opt_bitmain_L3_core_temp : 2
Jan  5 23:30:35 (none) local0.notice cgminer[14528]: send cmd to open block
Jan  5 23:30:38 (none) local0.warn cgminer[14528]: Pool 1 stratum+tcp://stratum-ltc.antpool.com:443 alive, testing stability
Jan  5 23:30:38 (none) local0.warn cgminer[14528]: Switching to pool 1 stratum+tcp://stratum-ltc.antpool.com:443
Jan  5 23:30:38 (none) local0.warn cgminer[14528]: Pool 0 stratum+tcp://stratum-ltc.antpool.com:8888 alive, testing stability
Jan  5 23:30:38 (none) local0.warn cgminer[14528]: Switching to pool 0 stratum+tcp://stratum-ltc.antpool.com:8888
Jan  5 23:30:43 (none) local0.warn cgminer[14528]: API running in IP access mode on port 4028 (15)
Jan  5 23:35:17 (none) local0.warn cgminer[14528]: Switching to pool 3 stratum+tcp://litecoinpool.org:3333
Jan  5 23:37:07 (none) local0.warn cgminer[14528]: Switching to pool 0 stratum+tcp://stratum-ltc.antpool.com:8888
Jan  5 23:45:19 (none) local0.err cgminer: Miner compile time: Fri Jan 05 23:17:57 CST 2018 type: Antminer L3+ Blissz v0.02 beta
Jan  5 23:45:19 (none) local0.warn cgminer: Started cgminer 4.10.0
Jan  5 23:45:19 (none) local0.notice cgminer[13505]:  detected at /sys/class/gpio/gpio51/value  chain 0
Jan  5 23:45:19 (none) local0.notice cgminer[13505]:  detected at /sys/class/gpio/gpio48/value  chain 1
Jan  5 23:45:19 (none) local0.notice cgminer[13505]:  detected at /sys/class/gpio/gpio47/value  chain 2
Jan  5 23:45:19 (none) local0.notice cgminer[13505]:  detected at /sys/class/gpio/gpio44/value  chain 3
Jan  5 23:45:19 (none) local0.notice cgminer[13505]: detect total chain num 4
Jan  5 23:45:19 (none) local0.notice cgminer[13505]: i2c init ok
Jan  5 23:45:31 (none) local0.notice cgminer[13505]: in tty_init
Jan  5 23:45:31 (none) local0.notice cgminer[13505]: tty_init 0
Jan  5 23:45:31 (none) local0.notice cgminer[13505]: Start A New Asic Response.Chain Id:[0]
Jan  5 23:45:31 (none) local0.notice cgminer[13505]: tty_init 1
Jan  5 23:45:31 (none) local0.notice cgminer[13505]: Start A New Asic Response.Chain Id:[1]
Jan  5 23:45:31 (none) local0.notice cgminer[13505]: tty_init 2
Jan  5 23:45:31 (none) local0.notice cgminer[13505]: Start A New Asic Response.Chain Id:[2]
Jan  5 23:45:31 (none) local0.notice cgminer[13505]: tty_init 3
Jan  5 23:45:31 (none) local0.notice cgminer[13505]: Start A New Asic Response.Chain Id:[3]
Jan  5 23:45:32 (none) local0.notice cgminer[13505]: open device over
Jan  5 23:45:32 (none) local0.notice cgminer[13505]: send cmd to get chip address
Jan  5 23:45:34 (none) local0.notice cgminer[13505]: Chain 0 ASIC 0 !!!
Jan  5 23:45:34 (none) local0.notice cgminer[13505]: Chain 1 ASIC 0 !!!
Jan  5 23:45:34 (none) local0.notice cgminer[13505]: Chain 2 ASIC 0 !!!
Jan  5 23:45:34 (none) local0.notice cgminer[13505]: Chain 3 ASIC 0 !!!
Jan  5 23:45:34 (none) local0.notice cgminer[13505]: Need to recheck asic num !!!
Jan  5 23:45:41 (none) local0.err cgminer: Miner compile time: Fri Jan 05 23:17:57 CST 2018 type: Antminer L3+ Blissz v0.02 beta
Jan  5 23:45:41 (none) local0.warn cgminer: Started cgminer 4.10.0
Jan  5 23:45:41 (none) local0.notice cgminer[13582]:  detected at /sys/class/gpio/gpio51/value  chain 0
Jan  5 23:45:41 (none) local0.notice cgminer[13582]:  detected at /sys/class/gpio/gpio48/value  chain 1
Jan  5 23:45:41 (none) local0.notice cgminer[13582]:  detected at /sys/class/gpio/gpio47/value  chain 2
Jan  5 23:45:41 (none) local0.notice cgminer[13582]:  detected at /sys/class/gpio/gpio44/value  chain 3
Jan  5 23:45:41 (none) local0.notice cgminer[13582]: detect total chain num 4
Jan  5 23:45:41 (none) local0.notice cgminer[13582]: i2c init ok
Jan  5 23:45:53 (none) local0.notice cgminer[13582]: in tty_init
Jan  5 23:45:53 (none) local0.notice cgminer[13582]: tty_init 0
Jan  5 23:45:53 (none) local0.notice cgminer[13582]: Start A New Asic Response.Chain Id:[0]
Jan  5 23:45:53 (none) local0.notice cgminer[13582]: tty_init 1
Jan  5 23:45:53 (none) local0.notice cgminer[13582]: Start A New Asic Response.Chain Id:[1]
Jan  5 23:45:53 (none) local0.notice cgminer[13582]: tty_init 2
Jan  5 23:45:53 (none) local0.notice cgminer[13582]: Start A New Asic Response.Chain Id:[2]
Jan  5 23:45:53 (none) local0.notice cgminer[13582]: tty_init 3
Jan  5 23:45:53 (none) local0.notice cgminer[13582]: Start A New Asic Response.Chain Id:[3]
Jan  5 23:45:54 (none) local0.notice cgminer[13582]: open device over
Jan  5 23:45:54 (none) local0.notice cgminer[13582]: send cmd to get chip address
Jan  5 23:45:56 (none) local0.notice cgminer[13582]: Chain 0 ASIC 0 !!!
Jan  5 23:45:56 (none) local0.notice cgminer[13582]: Chain 1 ASIC 0 !!!
Jan  5 23:45:56 (none) local0.notice cgminer[13582]: Chain 2 ASIC 0 !!!
Jan  5 23:45:56 (none) local0.notice cgminer[13582]: Chain 3 ASIC 0 !!!
Jan  5 23:45:56 (none) local0.notice cgminer[13582]: Need to recheck asic num !!!
Jan  5 23:45:58 (none) local0.notice cgminer[13582]: Chain 0 ASIC 0 !!!
Jan  5 23:45:58 (none) local0.notice cgminer[13582]: Chain 1 ASIC 0 !!!
Jan  5 23:45:58 (none) local0.notice cgminer[13582]: Chain 2 ASIC 0 !!!
Jan  5 23:45:58 (none) local0.notice cgminer[13582]: Chain 3 ASIC 0 !!!
Jan  5 23:45:58 (none) local0.notice cgminer[13582]: frequency = '384'
Jan  5 23:45:58 (none) local0.notice cgminer[13582]: dev.timeout = 46
Jan  5 23:45:58 (none) local0.notice cgminer[13582]: opt_bitmain_L3_core_temp : 2
Jan  5 23:46:00 (none) local0.notice cgminer[13582]: send cmd to open block
Jan  5 23:46:04 (none) local0.warn cgminer[13582]: Pool 1 stratum+tcp://stratum-ltc.antpool.com:443 alive, testing stability
Jan  5 23:46:04 (none) local0.warn cgminer[13582]: Switching to pool 1 stratum+tcp://stratum-ltc.antpool.com:443
Jan  5 23:46:04 (none) local0.warn cgminer[13582]: Pool 0 stratum+tcp://stratum-ltc.antpool.com:8888 alive, testing stability
Jan  5 23:46:04 (none) local0.warn cgminer[13582]: Switching to pool 0 stratum+tcp://stratum-ltc.antpool.com:8888
Jan  5 23:46:08 (none) local0.warn cgminer[13582]: API running in IP access mode on port 4028 (15)
Jan  5 23:48:03 (none) local0.err cgminer: Miner compile time: Fri Jan 05 23:17:57 CST 2018 type: Antminer L3+ Blissz v0.02 beta
Jan  5 23:48:03 (none) local0.warn cgminer: Started cgminer 4.10.0
Jan  5 23:48:03 (none) local0.notice cgminer[1016]:  detected at /sys/class/gpio/gpio51/value  chain 0
Jan  5 23:48:03 (none) local0.notice cgminer[1016]:  detected at /sys/class/gpio/gpio48/value  chain 1
Jan  5 23:48:03 (none) local0.notice cgminer[1016]:  detected at /sys/class/gpio/gpio47/value  chain 2
Jan  5 23:48:03 (none) local0.notice cgminer[1016]:  detected at /sys/class/gpio/gpio44/value  chain 3
Jan  5 23:48:03 (none) local0.notice cgminer[1016]: detect total chain num 4
Jan  5 23:48:03 (none) local0.notice cgminer[1016]: i2c init ok
Jan  5 23:48:15 (none) local0.notice cgminer[1016]: in tty_init
Jan  5 23:48:15 (none) local0.notice cgminer[1016]: tty_init 0
Jan  5 23:48:15 (none) local0.notice cgminer[1016]: Start A New Asic Response.Chain Id:[0]
Jan  5 23:48:15 (none) local0.notice cgminer[1016]: tty_init 1
Jan  5 23:48:15 (none) local0.notice cgminer[1016]: Start A New Asic Response.Chain Id:[1]
Jan  5 23:48:15 (none) local0.notice cgminer[1016]: tty_init 2
Jan  5 23:48:15 (none) local0.notice cgminer[1016]: Start A New Asic Response.Chain Id:[2]
Jan  5 23:48:15 (none) local0.notice cgminer[1016]: tty_init 3
Jan  5 23:48:15 (none) local0.notice cgminer[1016]: Start A New Asic Response.Chain Id:[3]
Jan  5 23:48:15 (none) local0.notice cgminer[1016]: open device over
Jan  5 23:48:16 (none) local0.notice cgminer[1016]: send cmd to get chip address
Jan  5 23:48:18 (none) local0.notice cgminer[1016]: Chain 0 ASIC 0 !!!
Jan  5 23:48:18 (none) local0.notice cgminer[1016]: Chain 1 ASIC 0 !!!
Jan  5 23:48:18 (none) local0.notice cgminer[1016]: Chain 2 ASIC 0 !!!
Jan  5 23:48:18 (none) local0.notice cgminer[1016]: Chain 3 ASIC 0 !!!
Jan  5 23:48:18 (none) local0.notice cgminer[1016]: Need to recheck asic num !!!
Jan  5 23:48:22 (none) local0.err cgminer: Miner compile time: Fri Jan 05 23:17:57 CST 2018 type: Antminer L3+ Blissz v0.02 beta
Jan  5 23:48:22 (none) local0.warn cgminer: Started cgminer 4.10.0
Jan  5 23:48:22 (none) local0.notice cgminer[1082]:  detected at /sys/class/gpio/gpio51/value  chain 0
Jan  5 23:48:22 (none) local0.notice cgminer[1082]:  detected at /sys/class/gpio/gpio48/value  chain 1
Jan  5 23:48:22 (none) local0.notice cgminer[1082]:  detected at /sys/class/gpio/gpio47/value  chain 2
Jan  5 23:48:22 (none) local0.notice cgminer[1082]:  detected at /sys/class/gpio/gpio44/value  chain 3
Jan  5 23:48:22 (none) local0.notice cgminer[1082]: detect total chain num 4
Jan  5 23:48:22 (none) local0.notice cgminer[1082]: i2c init ok
Jan  5 23:48:34 (none) local0.notice cgminer[1082]: in tty_init
Jan  5 23:48:34 (none) local0.notice cgminer[1082]: tty_init 0
Jan  5 23:48:34 (none) local0.notice cgminer[1082]: Start A New Asic Response.Chain Id:[0]
Jan  5 23:48:34 (none) local0.notice cgminer[1082]: tty_init 1
Jan  5 23:48:34 (none) local0.notice cgminer[1082]: Start A New Asic Response.Chain Id:[1]
Jan  5 23:48:34 (none) local0.notice cgminer[1082]: tty_init 2
Jan  5 23:48:34 (none) local0.notice cgminer[1082]: Start A New Asic Response.Chain Id:[2]
Jan  5 23:48:34 (none) local0.notice cgminer[1082]: tty_init 3
Jan  5 23:48:34 (none) local0.notice cgminer[1082]: Start A New Asic Response.Chain Id:[3]
Jan  5 23:48:35 (none) local0.notice cgminer[1082]: open device over
Jan  5 23:48:35 (none) local0.notice cgminer[1082]: send cmd to get chip address
Jan  5 23:48:37 (none) local0.notice cgminer[1082]: Chain 0 ASIC 0 !!!
Jan  5 23:48:37 (none) local0.notice cgminer[1082]: Chain 1 ASIC 0 !!!
Jan  5 23:48:37 (none) local0.notice cgminer[1082]: Chain 2 ASIC 0 !!!
Jan  5 23:48:37 (none) local0.notice cgminer[1082]: Chain 3 ASIC 0 !!!
Jan  5 23:48:37 (none) local0.notice cgminer[1082]: Need to recheck asic num !!!
Jan  5 23:48:39 (none) local0.notice cgminer[1082]: Chain 0 ASIC 0 !!!
Jan  5 23:48:39 (none) local0.notice cgminer[1082]: Chain 1 ASIC 0 !!!
Jan  5 23:48:39 (none) local0.notice cgminer[1082]: Chain 2 ASIC 0 !!!
Jan  5 23:48:39 (none) local0.notice cgminer[1082]: Chain 3 ASIC 0 !!!
Jan  5 23:48:39 (none) local0.notice cgminer[1082]: frequency = '400'
Jan  5 23:48:39 (none) local0.notice cgminer[1082]: dev.timeout = 44
Jan  5 23:48:39 (none) local0.notice cgminer[1082]: opt_bitmain_L3_core_temp : 2
Jan  5 23:48:41 (none) local0.notice cgminer[1082]: send cmd to open block
Jan  5 23:48:44 (none) local0.warn cgminer[1082]: Pool 2 stratum+tcp://stratum.f2pool.com:8888 alive, testing stability
Jan  5 23:48:44 (none) local0.warn cgminer[1082]: Switching to pool 2 stratum+tcp://stratum.f2pool.com:8888
Jan  5 23:48:45 (none) local0.warn cgminer[1082]: Pool 1 stratum+tcp://stratum-ltc.antpool.com:443 alive, testing stability
Jan  5 23:48:45 (none) local0.warn cgminer[1082]: Switching to pool 1 stratum+tcp://stratum-ltc.antpool.com:443
Jan  5 23:48:45 (none) local0.warn cgminer[1082]: Pool 0 stratum+tcp://stratum-ltc.antpool.com:8888 alive, testing stability
Jan  5 23:48:45 (none) local0.warn cgminer[1082]: Switching to pool 0 stratum+tcp://stratum-ltc.antpool.com:8888
Jan  5 23:48:49 (none) local0.warn cgminer[1082]: API running in IP access mode on port 4028 (18)
Jan  5 23:53:23 (none) local0.warn cgminer[1082]: Switching to pool 3 stratum+tcp://litecoinpool.org:3333
Jan  5 23:55:13 (none) local0.warn cgminer[1082]: Switching to pool 0 stratum+tcp://stratum-ltc.antpool.com:8888
Jan  5 23:56:24 (none) local0.err cgminer: Miner compile time: Fri Jan 05 23:17:57 CST 2018 type: Antminer L3+ Blissz v0.02 beta
Jan  5 23:56:24 (none) local0.warn cgminer: Started cgminer 4.10.0
Jan  5 23:56:24 (none) local0.notice cgminer[29778]:  detected at /sys/class/gpio/gpio51/value  chain 0
Jan  5 23:56:24 (none) local0.notice cgminer[29778]:  detected at /sys/class/gpio/gpio48/value  chain 1
Jan  5 23:56:24 (none) local0.notice cgminer[29778]:  detected at /sys/class/gpio/gpio47/value  chain 2
Jan  5 23:56:24 (none) local0.notice cgminer[29778]:  detected at /sys/class/gpio/gpio44/value  chain 3
Jan  5 23:56:24 (none) local0.notice cgminer[29778]: detect total chain num 4
Jan  5 23:56:24 (none) local0.notice cgminer[29778]: i2c init ok
Jan  5 23:56:36 (none) local0.notice cgminer[29778]: in tty_init
Jan  5 23:56:36 (none) local0.notice cgminer[29778]: tty_init 0
Jan  5 23:56:36 (none) local0.notice cgminer[29778]: Start A New Asic Response.Chain Id:[0]
Jan  5 23:56:36 (none) local0.notice cgminer[29778]: tty_init 1
Jan  5 23:56:36 (none) local0.notice cgminer[29778]: Start A New Asic Response.Chain Id:[1]
Jan  5 23:56:36 (none) local0.notice cgminer[29778]: tty_init 2
Jan  5 23:56:36 (none) local0.notice cgminer[29778]: Start A New Asic Response.Chain Id:[2]
Jan  5 23:56:37 (none) local0.notice cgminer[29778]: tty_init 3
Jan  5 23:56:37 (none) local0.notice cgminer[29778]: Start A New Asic Response.Chain Id:[3]
Jan  5 23:56:37 (none) local0.notice cgminer[29778]: open device over
Jan  5 23:56:37 (none) local0.notice cgminer[29778]: send cmd to get chip address
Jan  5 23:56:39 (none) local0.notice cgminer[29778]: Chain 0 ASIC 0 !!!
Jan  5 23:56:39 (none) local0.notice cgminer[29778]: Chain 1 ASIC 0 !!!
Jan  5 23:56:39 (none) local0.notice cgminer[29778]: Chain 2 ASIC 0 !!!
Jan  5 23:56:39 (none) local0.notice cgminer[29778]: Chain 3 ASIC 0 !!!
Jan  5 23:56:39 (none) local0.notice cgminer[29778]: Need to recheck asic num !!!
Jan  5 23:56:45 (none) local0.err cgminer: Miner compile time: Fri Jan 05 23:17:57 CST 2018 type: Antminer L3+ Blissz v0.02 beta
Jan  5 23:56:45 (none) local0.warn cgminer: Started cgminer 4.10.0
Jan  5 23:56:45 (none) local0.notice cgminer[29849]:  detected at /sys/class/gpio/gpio51/value  chain 0
Jan  5 23:56:45 (none) local0.notice cgminer[29849]:  detected at /sys/class/gpio/gpio48/value  chain 1
Jan  5 23:56:45 (none) local0.notice cgminer[29849]:  detected at /sys/class/gpio/gpio47/value  chain 2
Jan  5 23:56:45 (none) local0.notice cgminer[29849]:  detected at /sys/class/gpio/gpio44/value  chain 3
Jan  5 23:56:45 (none) local0.notice cgminer[29849]: detect total chain num 4
Jan  5 23:56:45 (none) local0.notice cgminer[29849]: i2c init ok
Jan  5 23:56:56 (none) local0.notice cgminer[29849]: in tty_init
Jan  5 23:56:56 (none) local0.notice cgminer[29849]: tty_init 0
Jan  5 23:56:56 (none) local0.notice cgminer[29849]: Start A New Asic Response.Chain Id:[0]
Jan  5 23:56:57 (none) local0.notice cgminer[29849]: tty_init 1
Jan  5 23:56:57 (none) local0.notice cgminer[29849]: Start A New Asic Response.Chain Id:[1]
Jan  5 23:56:57 (none) local0.notice cgminer[29849]: tty_init 2
Jan  5 23:56:57 (none) local0.notice cgminer[29849]: Start A New Asic Response.Chain Id:[2]
Jan  5 23:56:57 (none) local0.notice cgminer[29849]: tty_init 3
Jan  5 23:56:57 (none) local0.notice cgminer[29849]: Start A New Asic Response.Chain Id:[3]
Jan  5 23:56:57 (none) local0.notice cgminer[29849]: open device over
Jan  5 23:56:57 (none) local0.notice cgminer[29849]: send cmd to get chip address
Jan  5 23:57:00 (none) local0.notice cgminer[29849]: Chain 0 ASIC 0 !!!
Jan  5 23:57:00 (none) local0.notice cgminer[29849]: Chain 1 ASIC 0 !!!
Jan  5 23:57:00 (none) local0.notice cgminer[29849]: Chain 2 ASIC 0 !!!
Jan  5 23:57:00 (none) local0.notice cgminer[29849]: Chain 3 ASIC 0 !!!
Jan  5 23:57:00 (none) local0.notice cgminer[29849]: Need to recheck asic num !!!
Jan  5 23:57:02 (none) local0.notice cgminer[29849]: Chain 0 ASIC 0 !!!
Jan  5 23:57:02 (none) local0.notice cgminer[29849]: Chain 1 ASIC 0 !!!
Jan  5 23:57:02 (none) local0.notice cgminer[29849]: Chain 2 ASIC 0 !!!
Jan  5 23:57:02 (none) local0.notice cgminer[29849]: Chain 3 ASIC 0 !!!
Jan  5 23:57:02 (none) local0.notice cgminer[29849]: frequency = '384'
Jan  5 23:57:02 (none) local0.notice cgminer[29849]: dev.timeout = 46
Jan  5 23:57:02 (none) local0.notice cgminer[29849]: opt_bitmain_L3_core_temp : 2
Jan  5 23:57:03 (none) local0.notice cgminer[29849]: send cmd to open block
Jan  5 23:57:07 (none) local0.warn cgminer[29849]: Pool 2 stratum+tcp://stratum.f2pool.com:8888 alive, testing stability
Jan  5 23:57:07 (none) local0.warn cgminer[29849]: Switching to pool 2 stratum+tcp://stratum.f2pool.com:8888
Jan  5 23:57:07 (none) local0.warn cgminer[29849]: Pool 0 stratum+tcp://stratum-ltc.antpool.com:8888 alive, testing stability
Jan  5 23:57:07 (none) local0.warn cgminer[29849]: Switching to pool 0 stratum+tcp://stratum-ltc.antpool.com:8888
Jan  5 23:57:12 (none) local0.warn cgminer[29849]: API running in IP access mode on port 4028 (16)
Jan  6 00:01:46 (none) local0.warn cgminer[29849]: Switching to pool 3 stratum+tcp://litecoinpool.org:3333
Jan  6 00:03:36 (none) local0.warn cgminer[29849]: Switching to pool 0 stratum+tcp://stratum-ltc.antpool.com:8888


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 06, 2018, 12:14:23 AM

*large log file*


I've seen this on people who accidentally flashed the D3 firmware on a L3+...
As it's constantly rebooting try this:

1) set the global voltage to 13 (as it can be the case that your boards don't like a low voltage)
if that doesn't work:
2) disconnect all hashing boards from the controller and start it up. Try to flash the stock firmware
Then reconnect the hashing boards.
3) if flashing doesn't work: do the same but use the micro sd card recovery (see topic start).
4) if the stock firmware doesn't work, have a look here: https://bitcointalk.org/index.php?topic=2383200.0 (https://bitcointalk.org/index.php?topic=2383200.0) then your hashing boards needs to be recovered one by one.

please report to me which method fixed your problem as that's quite useful information for me.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: Bajula on January 06, 2018, 12:18:56 AM
OH! a bitmain thing (in general - though less often needed on the newer machines) after doing anything that alters voltage SOMETIMES you need to power cycle it.. though this won't do you any good until after you can fix whatever the flash issue is. I.e. flash back to bitmain..  (even if you have to do the sd card bit) then power cycle.. then flash blissz's firmware on, change whatever settings you are aiming for.. power cycle.. After that freq change fan speed etc.. no biggie but IF yours is one of the ones that doesn't like on the fly voltage changes (not sure if this would even apply with newer bitmains anyway, but they have a system and kinda build everything the same so who knows) any time you change voltage you would have to power cycle... no .. no idea why but I have had a few bitmains that have this issue and almost all of the really old ones have it.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 06, 2018, 12:21:10 AM
OH! a bitmain thing (in general - though less often needed on the newer machines) after doing anything that alters voltage SOMETIMES you need to power cycle it.. though this won't do you any good until after you can fix whatever the flash issue is. I.e. flash back to bitmain..  (even if you have to do the sd card bit) then power cycle.. then flash blissz's firmware on, change whatever settings you are aiming for.. power cycle.. After that freq change fan speed etc.. no biggie but IF yours is one of the ones that doesn't like on the fly voltage changes (not sure if this would even apply with newer bitmains anyway, but they have a system and kinda build everything the same so who knows) any time you change voltage you would have to power cycle... no .. no idea why but I have had a few bitmains that have this issue and almost all of the really old ones have it.


useful information, thanks for sharing!


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: Bajula on January 06, 2018, 12:21:36 AM

*large log file*


I've seen this on people who accidentally flashed the D3 firmware on a L3+...
As it's constantly rebooting try this:

1) set the global voltage to 13 (as it can be the case that your boards don't like a low voltage)
if that doesn't work:
2) disconnect all hashing boards from the controller and start it up. Try to flash the stock firmware
Then reconnect the hashing boards.
3) if flashing doesn't work: do the same but use the micro sd card recovery (see topic start).
4) if the stock firmware doesn't work, have a look here: https://bitcointalk.org/index.php?topic=2383200.0 (https://bitcointalk.org/index.php?topic=2383200.0) then your hashing boards needs to be recovered one by one.

please report to me which method fixed your problem as that's quite useful information for me.


Oh man! *rofl* glad you brought that up.. I gotta move all these to diff directories now. :) I have them all piled together and looking at the file list.. one day I know I'd get an updated version of d3 or l3 and pre-coffee me would flash the wrong one.  I mean really the file names all look VERY close especially through blurry morning vision.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 06, 2018, 12:26:15 AM
[
Oh man! *rofl* glad you brought that up.. I gotta move all these to diff directories now. :) I have them all piled together and looking at the file list.. one day I know I'd get an updated version of d3 or l3 and pre-coffee me would flash the wrong one.  I mean really the file names all look VERY close especially through blurry morning vision.

haha actually I made that mistake myself as well ^^ I can confirm this special firmware I made one day will recover your boards, but it takes some time as you need to flash them one by one.
I will change the first step of the flashing guide ;) coffee first haha


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: vagueink on January 06, 2018, 02:54:25 AM
I've seen this on people who accidentally flashed the D3 firmware on a L3+...
As it's constantly rebooting try this:

1) set the global voltage to 13 (as it can be the case that your boards don't like a low voltage)
if that doesn't work:
2) disconnect all hashing boards from the controller and start it up. Try to flash the stock firmware
Then reconnect the hashing boards.
3) if flashing doesn't work: do the same but use the micro sd card recovery (see topic start).
4) if the stock firmware doesn't work, have a look here: https://bitcointalk.org/index.php?topic=2383200.0 (https://bitcointalk.org/index.php?topic=2383200.0) then your hashing boards needs to be recovered one by one.

please report to me which method fixed your problem as that's quite useful information for me.

My results

1) Voltage was set already
2) All boards disconnected, flash stock firmware still fails...this is true for 2 other L3+s I have...both December batches. I have an open ticket with Bitmain that hasn't been replied to.
3) Haven't done this yet...felt 4 was less time consuming
4) Worked like a champ...card by card came back online...take approx 10 minutes per card


Still quite baffled why my December L3+s can't flash Bitmain's default firmware (0825 and 0427) but happy to have a functional L3+ again!

Thank you, I will report back any bugs.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: unreal1 on January 06, 2018, 03:21:57 AM
Is there a source to this? I'm assuming this is built on
https://github.com/bitmaintech/setup-A8


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: unreal1 on January 06, 2018, 03:35:03 AM
Btw here is a screenshot of my dirty overclock  ;) I appreciate your effort

https://imgur.com/5i1rg9y

https://i.imgur.com/usSGf4y.png


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 06, 2018, 08:41:37 AM
....
4) Worked like a champ...card by card came back online...take approx 10 minutes per card


Still quite baffled why my December L3+s can't flash Bitmain's default firmware (0825 and 0427) but happy to have a functional L3+ again!

Thank you, I will report back any bugs.
Good to hear you're back on track ;D


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 06, 2018, 08:43:05 AM
Btw here is a screenshot of my dirty overclock  ;) I appreciate your effort

https://imgur.com/5i1rg9y

https://i.imgur.com/usSGf4y.png


nice one! You might want to clock the last chain a little lower to get rid of the HW errors. (one or two steps down)


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: unreal1 on January 06, 2018, 09:02:32 AM
Btw here is a screenshot of my dirty overclock  ;) I appreciate your effort

https://imgur.com/5i1rg9y

https://i.imgur.com/usSGf4y.png


nice one! You might want to clock the last chain a little lower to get rid of the HW errors. (one or two steps down)

Is it beneficial to keep HW errors at 0? With your D3 firmware I was able to get 0 HW errors running 20.6 GH/s. The thing is even at stock I was getting HW errors on my L3+, are they just more common on the L3+ rather than D3?


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 06, 2018, 09:39:09 AM
Btw here is a screenshot of my dirty overclock  ;) I appreciate your effort

https://imgur.com/5i1rg9y

https://i.imgur.com/usSGf4y.png


nice one! You might want to clock the last chain a little lower to get rid of the HW errors. (one or two steps down)

Is it beneficial to keep HW errors at 0? With your D3 firmware I was able to get 0 HW errors running 20.6 GH/s. The thing is even at stock I was getting HW errors on my L3+, are they just more common on the L3+ rather than D3?

zero is not needed, one or two HW errors a minute is fine, but I found the L3+ is more sensitive to HW errors, as your average hashrate will lower once you get too many.
It's a bit different on the D3, as it the D3 can still run fine when having upto 10 HW errors a minute or so.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: EEM on January 06, 2018, 12:32:19 PM
Thanks for your firmware. I have some questions. Thanks for the answers.

1. I'm worried about chips temperature. After the switching to the silent mode, the temperature of chips were ~63. I switched to Fan mode: "Auto Performance" - what it means? Will fans be too noisy at this mode? And why isn't there option "Stop running when temprerature is over 80℃"
2. I did in another way than you had adwiced. I set 425mh/s with the lowest voltage, and had ~8-hw per a minute!. Then I set voltage to 10 and hw were ok (0 hw per an hour). Tomorrow I want to set voltage to 9, 8, 7, 6. Is it an effective way?
3. Every 2 hours the ASIC will connect to your pool. Is it safety for ASIC to launch on/off another pool every 2 hours? Can you think about making switches avery 5 or 6 hours for 3 or more mins for you?


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: Shitcointalk on January 06, 2018, 02:50:52 PM
Awesome Blissz ! Working great. I am using your D3 FW since the beginning (as a useless heater may as well run silent). Didn't really have a reason to mod my L3+, but just gave it a try, in case.

I did well ! I can't give you precise number because my electricity sucks (220v but can go down to 195v, so kill a watt readings might differ more than 50watts). But I estimate at least 120watts gain for same frequency, running at 425 and voltage 5, without HW.

Thank you.



Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 06, 2018, 04:02:29 PM
Thanks for your firmware. I have some questions. Thanks for the answers.

1. I'm worried about chips temperature. After the switching to the silent mode, the temperature of chips were ~63. I switched to Fan mode: "Auto Performance" - what it means? Will fans be too noisy at this mode? And why isn't there option "Stop running when temprerature is over 80℃"
2. I did in another way than you had adwiced. I set 425mh/s with the lowest voltage, and had ~8-hw per a minute!. Then I set voltage to 10 and hw were ok (0 hw per an hour). Tomorrow I want to set voltage to 9, 8, 7, 6. Is it an effective way?
3. Every 2 hours the ASIC will connect to your pool. Is it safety for ASIC to launch on/off another pool every 2 hours? Can you think about making switches avery 5 or 6 hours for 3 or more mins for you?

1)Auto silent mode will run the fans at a bit lower speed, but will increase to higher speeds when temps go up. Auto performance does basicly the same, but tries to keep the temps ~8 degrees lower, so the fans will run a bit louder.
2) yes that a fine way of doing it, I expect you will end up at voltage setting 2 to 5 or something for that frequency. That will save some heat and energy as the bitmain default is a lot higher (12 / 13)
3) It's save, but doing it less often is slightly more effective so I might build in an option later, so the user can choose the period.



Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 06, 2018, 04:02:53 PM
Awesome Blissz ! Working great. I am using your D3 FW since the beginning (as a useless heater may as well run silent). Didn't really have a reason to mod my L3+, but just gave it a try, in case.

I did well ! I can't give you precise number because my electricity sucks (220v but can go down to 195v, so kill a watt readings might differ more than 50watts). But I estimate at least 120watts gain for same frequency, running at 425 and voltage 5, without HW.

Thank you.


That's great to hear! Thanks for sharing!


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: Sfitzjava on January 06, 2018, 05:34:16 PM
This is another great job at firmware mods!!
I had raised my stock firmware up to 397mhz and was getting about 511mhs but I am sure at more than 800w advertised.  I think I remember initially testing and it was running at 820w stock.

Anyway, now I have it tuned at about 406 freq 5 power level on most of the chains and getting 520mhs and only pulling 755w.   Also running the fan lower and it’s not making a lot of noice, albeit nothing like a d3 before your firmware. :)

Thanks!!


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: ibinsad on January 06, 2018, 07:25:07 PM
I wish to install this firmware, is working well for everybody?

Which is the best conf you use?


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 06, 2018, 09:53:01 PM
I wish to install this firmware, is working well for everybody?

Which is the best conf you use?

See the messages in the topic. I think it's quite stable already. I run my own L3+ now at 425 Mhz @ voltage setting 2. That means 560 Mh/s @ 770Watts. Stock would be 500Mh/s @ 800 Watts, so that's 12% extra performance and a 4% decrease in power usage.

Make sure to read the topic start and the instructions to prevent mistakes with the flash procedure.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: CointoHash411 on January 07, 2018, 01:16:10 AM
I wish to install this firmware, is working well for everybody?

Which is the best conf you use?

See the messages in the topic. I think it's quite stable already. I run my own L3+ now at 425 Mhz @ voltage setting 2. That means 560 Mh/s @ 770Watts. Stock would be 500Mh/s @ 800 Watts, so that's 12% extra performance and a 4% decrease in power usage.

Make sure to read the topic start and the instructions to prevent mistakes with the flash procedure.
blissz have you managed to create the D3 firmware that will allow it to mine other x algos yet?

-CointoHash411


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: alikas74 on January 07, 2018, 08:04:35 AM
hi.

i just want to flash l3+. using file tar.gz not unpack it. but cant flash it.
upload file. upload 2% and system up cooling to 100% and reboot.
after reboot saying
tar: invalid magic tar: short read

Hardware Version   1.0.1.3
Kernel Version   Linux 3.8.13 #22 SMP Tue Dec 2 15:26:11 CST 2014
File System Version   Fri Aug 25 17:28:57 CST 2017
CGminer Version   4.9.0

my os. win8.1 x64 chrome browser



Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: unreal1 on January 07, 2018, 09:20:17 AM

[/quote]

zero is not needed, one or two HW errors a minute is fine, but I found the L3+ is more sensitive to HW errors, as your average hashrate will lower once you get too many.
It's a bit different on the D3, as it the D3 can still run fine when having upto 10 HW errors a minute or so.
[/quote]

So I tried keeping it to a couple errors a minute, but I endedup with asic errors, after I reset the boards everything went back to normal, whew. It's strange cause my D3 runs fine wother 550 mhz each board with no errors and one of the boards is as 16V and it's running at 74C, I guess I got the winter to thank for that. But yeah I'm trying to run a maximum overclock, but this L3 is being a pain so far.



Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 07, 2018, 10:12:02 AM
hi.

i just want to flash l3+. using file tar.gz not unpack it. but cant flash it.
upload file. upload 2% and system up cooling to 100% and reboot.
after reboot saying
tar: invalid magic tar: short read

Hardware Version   1.0.1.3
Kernel Version   Linux 3.8.13 #22 SMP Tue Dec 2 15:26:11 CST 2014
File System Version   Fri Aug 25 17:28:57 CST 2017
CGminer Version   4.9.0

my os. win8.1 x64 chrome browser



the firmware file you downloaded got corrupted. Download it in another browser might help.
I will release them with md5sum next time.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 07, 2018, 10:15:50 AM


zero is not needed, one or two HW errors a minute is fine, but I found the L3+ is more sensitive to HW errors, as your average hashrate will lower once you get too many.
It's a bit different on the D3, as it the D3 can still run fine when having upto 10 HW errors a minute or so.
[/quote]

So I tried keeping it to a couple errors a minute, but I endedup with asic errors, after I reset the boards everything went back to normal, whew. It's strange cause my D3 runs fine wother 550 mhz each board with no errors and one of the boards is as 16V and it's running at 74C, I guess I got the winter to thank for that. But yeah I'm trying to run a maximum overclock, but this L3 is being a pain so far.

[/quote]

The L3 is great for running at a lower voltage at a nice overclock, but it doesn't overclock as good as the D3 does. 640 - 700 MH/s is really the limit from what I've seen so far.
ASIC errors just indicate you clocked it too high (for the voltage set). Don;t worry, it won't kill your ASIC's permanently.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: alikas74 on January 07, 2018, 10:48:17 AM
hi.

i just want to flash l3+. using file tar.gz not unpack it. but cant flash it.
upload file. upload 2% and system up cooling to 100% and reboot.
after reboot saying
tar: invalid magic tar: short read

Hardware Version   1.0.1.3
Kernel Version   Linux 3.8.13 #22 SMP Tue Dec 2 15:26:11 CST 2014
File System Version   Fri Aug 25 17:28:57 CST 2017
CGminer Version   4.9.0

my os. win8.1 x64 chrome browser



the firmware file you downloaded got corrupted. Download it in another browser might help.
I will release them with md5sum next time.

my friend who upload firmware properly also resend to me firmware in telegram. also this shi* happens.
then i try to extract all files from firmware i dont have checksumm error. all extracts without any errors. and i see what archieve not corrupted


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 07, 2018, 10:54:07 AM
hi.

i just want to flash l3+. using file tar.gz not unpack it. but cant flash it.
upload file. upload 2% and system up cooling to 100% and reboot.
after reboot saying
tar: invalid magic tar: short read

Hardware Version   1.0.1.3
Kernel Version   Linux 3.8.13 #22 SMP Tue Dec 2 15:26:11 CST 2014
File System Version   Fri Aug 25 17:28:57 CST 2017
CGminer Version   4.9.0

my os. win8.1 x64 chrome browser



the firmware file you downloaded got corrupted. Download it in another browser might help.
I will release them with md5sum next time.

my friend who upload firmware properly also resend to me firmware in telegram. also this shi* happens.
then i try to extract all files from firmware i dont have checksumm error. all extracts without any errors. and i see what archieve not corrupted

strange, actually I have no clue why it won't flash. Did you try to flash it using firefox for example? Anybody other suggestions for this problem?


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: unreal1 on January 07, 2018, 12:12:08 PM
hi.

i just want to flash l3+. using file tar.gz not unpack it. but cant flash it.
upload file. upload 2% and system up cooling to 100% and reboot.
after reboot saying
tar: invalid magic tar: short read

Hardware Version   1.0.1.3
Kernel Version   Linux 3.8.13 #22 SMP Tue Dec 2 15:26:11 CST 2014
File System Version   Fri Aug 25 17:28:57 CST 2017
CGminer Version   4.9.0

my os. win8.1 x64 chrome browser



the firmware file you downloaded got corrupted. Download it in another browser might help.
I will release them with md5sum next time.

my friend who upload firmware properly also resend to me firmware in telegram. also this shi* happens.
then i try to extract all files from firmware i dont have checksumm error. all extracts without any errors. and i see what archieve not corrupted

Did you try repacking it after you unpacked it, and then trying to upgrade?
Also try using Internet Explorer, you might have to take a small does of cancer but you'll live.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: Sylar49 on January 07, 2018, 01:38:36 PM
I'm wondering.. where can I obtain and inspect the source code used to create the CGMiner binary included in this distribution?

Isn't that a GPL3 compliance issue that people bashed another firmware hacker about a couple of years back?


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 07, 2018, 03:33:35 PM

Did you try repacking it after you unpacked it, and then trying to upgrade?
Also try using Internet Explorer, you might have to take a small does of cancer but you'll live.

It should not be necessary to repack the firmware. I will add the md5sum next time


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: ethron on January 07, 2018, 05:23:59 PM
Thanks!!!  :) i have 689 watts at 381, lowest voltage and 493 Mh/s, 1 to 2 HW errors per 10 minutes. It runs really cool.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: dottat on January 07, 2018, 06:32:49 PM
I'm wondering.. where can I obtain and inspect the source code used to create the CGMiner binary included in this distribution?

Isn't that a GPL3 compliance issue that people bashed another firmware hacker about a couple of years back?


If it helps you out with your fears I already took a look.  I have no affiliation with blissz but felt the same as you.  I can confirm the dev mining works exactly like he's stated it does.  There's no back door etc included.  It's just a customized version of the firmware/binaries.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: nolazybits on January 07, 2018, 08:05:54 PM
Hi there,

Thanks for the firmware.
I've been able to flash it no pb and have no problem so far.
This is my settings

https://i.imgur.com/Jua6idQ.png


https://i.imgur.com/JEX4jtg.png

Running 580 Mh/s with average 3hw per minute. <- is this too high btw?

Thanks again!


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 07, 2018, 08:12:15 PM
Hi there,

Thanks for the firmware.
I've been able to flash it no pb and have no problem so far.
This is my settings

https://i.imgur.com/Jua6idQ.png


https://i.imgur.com/JEX4jtg.png

Running 580 Mh/s with average 3hw per minute. <- is this too high btw?

Thanks again!

Hi looks like you got some nice ASIC's. They  perform really good for the voltage setting. My guess is it runs at about stock wattage now (800 watts) and does bring you a nice performance increase (15%).
My advice: chain 2 is on the limit with 7 HW errors in 4 minutes, I would set it one step down in the frequency. Chain 1 is running a bit hotter and a bit too many HW errors I would say, so I would set it one or two steps down in frequency. I think that will make it run around 570 MH/s rock solid stable and silent for 24/7 use. Good stuff!  8)


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: nolazybits on January 07, 2018, 08:48:19 PM
Thanks much for the fast reply.

I have updated the settings as follow and it seems way better. Thanks again
https://i.imgur.com/osexxzg.png
https://i.imgur.com/YR2SDGW.png

570Mh/s at voltage setting 2 and frequency as on screenshot.

Thanks :)


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 07, 2018, 10:52:28 PM
Thanks much for the fast reply.

I have updated the settings as follow and it seems way better. Thanks again
https://i.imgur.com/osexxzg.png
https://i.imgur.com/YR2SDGW.png

570Mh/s at voltage setting 2 and frequency as on screenshot.

Thanks :)

Looks good now! Enjoy!


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: Sylar49 on January 07, 2018, 11:20:20 PM
I'm wondering.. where can I obtain and inspect the source code used to create the CGMiner binary included in this distribution?

Isn't that a GPL3 compliance issue that people bashed another firmware hacker about a couple of years back?


If it helps you out with your fears I already took a look.  I have no affiliation with blissz but felt the same as you.  I can confirm the dev mining works exactly like he's stated it does.  There's no back door etc included.  It's just a customized version of the firmware/binaries.

I appreciate the assurance, but that side-steps the point. If it's based on or derived from GPLv3 code, it must be made available once distributed. It's OK to make a buck off of distributing the modified product, but you can't go closed-source and withhold your modifications to GPL3-based code or binaries you're distributing.

There was another firmware hacker case a few months back:    
Re: Bounty for Cracking Bitmain S9 BMminer (https://bitcointalk.org/index.php?topic=1569129.200)

At least Blissz here actually put in some work (albeit source code yet to be published), whereas -- from what I observed in the Github repositories -- fubly seems to have simply rebadged Bitmain's source code, and removed irrelevant hardware support to slim things down. The guy also had the audacity to remove Colin Kolivas (original author) from the credits and also send a $120K invoice to Bitmain (https://github.com/bitmaintech/bmminer-mix/issues/3).

Anyway, cgminer is GPL3, so I look forward to examining the source in the near future. Thanks!


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: dottat on January 07, 2018, 11:59:54 PM
I'm wondering.. where can I obtain and inspect the source code used to create the CGMiner binary included in this distribution?

Isn't that a GPL3 compliance issue that people bashed another firmware hacker about a couple of years back?


If it helps you out with your fears I already took a look.  I have no affiliation with blissz but felt the same as you.  I can confirm the dev mining works exactly like he's stated it does.  There's no back door etc included.  It's just a customized version of the firmware/binaries.

I appreciate the assurance, but that side-steps the point. If it's based on or derived from GPLv3 code, it must be made available once distributed. It's OK to make a buck off of distributing the modified product, but you can't go closed-source and withhold your modifications to GPL3-based code or binaries you're distributing.

There was another firmware hacker case a few months back:    
Re: Bounty for Cracking Bitmain S9 BMminer (https://bitcointalk.org/index.php?topic=1569129.200)

At least Blissz here actually put in some work (albeit source code yet to be published), whereas -- from what I observed in the Github repositories -- fubly seems to have simply rebadged Bitmain's source code, and removed irrelevant hardware support to slim things down. The guy also had the audacity to remove Colin Kolivas (original author) from the credits and also send a $120K invoice to Bitmain (https://github.com/bitmaintech/bmminer-mix/issues/3).

Anyway, cgminer is GPL3, so I look forward to examining the source in the near future. Thanks!


Yep I hear ya.  I'm well familiar with GPL as most of my online presence has been on the phone hacking/rooting/rom'ing side of the world.  Investigated a great number of GPL complaints while i was a moderator at XDA as well.  That's part of why I tore this package apart. 

Pretty sure blissz used the source here to compile from..  http://ck.kolivas.org/apps/cgminer/  Though that maintainer was for bitcoin only.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: Littledragons on January 08, 2018, 01:17:50 AM
More than worth it IMO.

Especially with being able to clock it like crazy up or down.
I have actually just set it back to 13 v - to see what kind of clocks I could play up to, and got somewhere in the ballpark of 680 stable(ish).
I know its silly, but since then Ive been pushing up from 13 just to see what level it will spit HWs at me - and its so friggin high its obscene. Obviously not good for the machine, but interesting to know for sure.

Yeah undervolting is really useful to tame the beast for the people that run these units in their houses, but I am also curious how far it can  be overclocked with a bit more voltage :P I will play around with one of the chains first to see how it goes.
Edit: 680 MH/s is really nice, can you share your settings?

I actually dont remember, but I do know it was because I was tuning both my d3s and L3s at the same time. Got the stock Mhs confused from x11 miner to L3 - actually ended up killing my miner at one point I was quite worried. Not willing to really risk that.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: 1manshow on January 08, 2018, 06:59:45 AM
Thank you for your valuable efforts to release this improved firmware for L3+. Do you or anyone know if something similar is available for Antminer S9 as well?


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: wedwo on January 08, 2018, 12:06:45 PM
Fantastic job Blissz!  Running at stock frequency on lowest voltage... very stable.  I'll post current draw as shown on my UPS shortly!

*EDIT* 1.3kW reported at the UPS = 650W each!  Noice!


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: Sylar49 on January 08, 2018, 01:11:57 PM
I appreciate the assurance, but that side-steps the point. If it's based on or derived from GPLv3 code, it must be made available once distributed. It's OK to make a buck off of distributing the modified product, but you can't go closed-source and withhold your modifications to GPL3-based code or binaries you're distributing.

There was another firmware hacker case a few months back:    
Re: Bounty for Cracking Bitmain S9 BMminer (https://bitcointalk.org/index.php?topic=1569129.200)

At least Blissz here actually put in some work (albeit source code yet to be published), whereas -- from what I observed in the Github repositories -- fubly seems to have simply rebadged Bitmain's source code, and removed irrelevant hardware support to slim things down. The guy also had the audacity to remove Colin Kolivas (original author) from the credits and also send a $120K invoice to Bitmain (https://github.com/bitmaintech/bmminer-mix/issues/3).

Anyway, cgminer is GPL3, so I look forward to examining the source in the near future. Thanks!


Yep I hear ya.  I'm well familiar with GPL as most of my online presence has been on the phone hacking/rooting/rom'ing side of the world.  Investigated a great number of GPL complaints while i was a moderator at XDA as well.  That's part of why I tore this package apart. 

Pretty sure blissz used the source here to compile from..  http://ck.kolivas.org/apps/cgminer/  Though that maintainer was for bitcoin only.

With all that's going on in blissz's webUI adjustments to support the voltage and frequency settings (especially by individual hash card), it's prety clear the driver-bitmain.c was nicely customized to support the additional individual cards' settings. If I had the time to hack on firmware (no, I've long since retired from Firmware and BIOS hacking), I'd probably start from from Bitmain's Github (https://github.com/bitmaintech/cgminer-dash) and merge driver-bitmain.c, driver-btm-DASH.c, and driver-btm-L3.c from there against a clean cgminer-4.10.0 code base to get it all up to current cgminer code.

Since the driver-bitmain.c is identical for DASH and L3 versions of cgminer, I'd expect the Voltage/Frequency customizations coded for one can be copied verbatim to the other.

It's interesting to note that the stock D3 and L3 firmware always had support for using --bitmain-voltage to tweak voltages (if you were to modify cgminer.conf by hand and restart the cgminer service), but the webUI completely lacked the proper fields to make that setting adjustable via web page, unlike the S5/S7, and presumably S9's webUI.

Blissz's addition of auto-tuning is definitely a nice touch, and I'm looking forward to reading that enhancement's source code once published per GPL3.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: CointoHash411 on January 08, 2018, 02:07:43 PM
Awesome,

I will be adding this to my L3+'s as soon as they come in. Blissz, so the firmware is also compatible with the D3's or is that a misconception? Just want to make sure before I start pushing firmware updates out.

-CointoHash411


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 08, 2018, 02:10:54 PM
Awesome,

I will be adding this to my L3+'s as soon as they come in. Blissz, so the firmware is also compatible with the D3's or is that a misconception? Just want to make sure before I start pushing firmware updates out.

-CointoHash411

For the L3+ you need the firmware in this topic. For the D3 you need the firmware from the other topic (there is a link to it in this topic start if you can't find it)


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 08, 2018, 02:11:50 PM
Fantastic job Blissz!  Running at stock frequency on lowest voltage... very stable.  I'll post current draw as shown on my UPS shortly!

*EDIT* 1.3kW reported at the UPS = 650W each!  Noice!

You're welcome! Yep that's a nice decrease from 800W  8) 8) 8)


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: zerp86 on January 08, 2018, 04:23:36 PM
i will try out for my L3+ tomorrow.. ;D


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: Sylar49 on January 08, 2018, 05:26:54 PM
Still waiting for a response, btw.

What's the word on making the GPL3 source code available for review, Blissz?


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blackburst67 on January 08, 2018, 05:36:51 PM
Thank you !
I will try this tonight..


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: trackers on January 08, 2018, 05:54:48 PM
This is amazing, great work dude


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: tiger909 on January 09, 2018, 01:15:24 PM
Great work, thank you Blissz


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: wedwo on January 10, 2018, 05:57:42 PM
Fantastic job Blissz!  Running at stock frequency on lowest voltage... very stable.  I'll post current draw as shown on my UPS shortly!

*EDIT* 1.3kW reported at the UPS = 650W each!  Noice!

You're welcome! Yep that's a nice decrease from 800W  8) 8) 8)
In total on 2x L3+ and 2x D3 I am using 2700W instead of 4000W - a saving of 1300W!  At our local rates of around $0.15 / kWh that's $140 a month savings on electricity... very happy!


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: Crazytoo on January 10, 2018, 06:03:36 PM
Hey can you also have a look at S4 S7 S9
    greate work btw


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: Littledragons on January 10, 2018, 06:04:09 PM
Yeah this firmware has been great! Really killin it by allowing me to finally alter these stupid locked up bitmain bits - especially my D3 heaters =)
Finally worth a damn - +rep Bliz


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: manu82 on January 11, 2018, 10:22:05 AM
Hey can you also have a look at S4 S7 S9
    greate work btw

Me too interested on S9. I hate the noise who make when go over 77°.

Just a suggestion for Blissz, I prefer to pay a license (like 100$ forever blocked on the serial number of the miner) instead to give you a fee, but it's only my opinion.

Anyway, great works! Thank you


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: EEM on January 11, 2018, 01:47:38 PM
Thanks for your firmware. I have some questions. Thanks for the answers.

1. I'm worried about chips temperature. After the switching to the silent mode, the temperature of chips were ~63. I switched to Fan mode: "Auto Performance" - what it means? Will fans be too noisy at this mode? And why isn't there option "Stop running when temprerature is over 80℃"


1)Auto silent mode will run the fans at a bit lower speed, but will increase to higher speeds when temps go up. Auto performance does basicly the same, but tries to keep the temps ~8 degrees lower, so the fans will run a


When the temperature became over 80℃ Would ASIC stop?
Thanks.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: olebol on January 11, 2018, 10:03:00 PM
Hey Blissz

first of all, thx again for such a good firmware (like for D3)

i got following message on Kernel since i use the Firmware :

[    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.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: 238772k/238772k available, 23372k 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.000355] Calibrating delay loop... 545.07 BogoMIPS (lpj=531968)
[    0.015438] pid_max: default: 32768 minimum: 301
[    0.015670] Security Framework initialized
[    0.015765] Mount-cache hash table entries: 512
[    0.024584] Initializing cgroup subsys cpuacct
[    0.024616] Initializing cgroup subsys memory
[    0.024677] Initializing cgroup subsys blkio
[    0.024814] CPU: Testing write buffer coherency: ok
[    0.025389] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[    0.025467] Setting up static identity map for 0x8038c820 - 0x8038c86c
[    0.026795] Brought up 1 CPUs
[    0.026819] SMP: Total of 1 processors activated (545.07 BogoMIPS).
[    0.028111] devtmpfs: initialized
[    0.092466] pinctrl core: initialized pinctrl subsystem
[    0.092682] rstctl core: initialized rstctl subsystem
[    0.093174] regulator-dummy: no parameters
[    0.093747] NET: Registered protocol family 16
[    0.094451] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.104120] pinctrl-single 44e10800.pinmux: prop pinctrl-0 index 0 invalid phandle
[    0.104305] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[    0.105387] platform 49000000.edma: alias fck already exists
[    0.105422] platform 49000000.edma: alias fck already exists
[    0.105450] platform 49000000.edma: alias fck already exists
[    0.106593] gpiochip_add: registered GPIOs 0 to 31 on device: gpio
[    0.106775] OMAP GPIO hardware version 0.1
[    0.108174] gpiochip_add: registered GPIOs 32 to 63 on device: gpio
[    0.109494] gpiochip_add: registered GPIOs 64 to 95 on device: gpio
[    0.110811] gpiochip_add: registered GPIOs 96 to 127 on device: gpio
[    0.111443] of_get_named_gpio_flags exited with status 52
[    0.111473] gpio-rctrl rstctl.3: loaded OK
[    0.116580] omap-gpmc 50000000.gpmc: GPMC revision 6.0
[    0.119786] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.121976] cpsw.0: No hwaddr in dt. Using 50:8c:b1:fa:fa:83 from efuse
[    0.122007] cpsw.1: No hwaddr in dt. Using 50:8c:b1:fa:fa:85 from efuse
[    0.137544] bio: create slab <bio-0> at 0
[    0.149668] edma-dma-engine edma-dma-engine.0: TI EDMA DMA engine driver
[    0.149911] of_get_named_gpio_flags: can't parse gpios property
[    0.150151] vmmcsd_fixed: 3300 mV
[    0.153308] SCSI subsystem initialized
[    0.153759] usbcore: registered new interface driver usbfs
[    0.153873] usbcore: registered new interface driver hub
[    0.154199] usbcore: registered new device driver usb
[    0.156316] omap_i2c 4819c000.i2c: bus 0 rev0.11 at 100 kHz
[    0.156351] omap_i2c 4819c000.i2c: unable to select pin group
[    0.156548] media: Linux media interface: v0.10
[    0.156644] Linux video capture interface: v2.00
[    0.156761] pps_core: LinuxPPS API ver. 1 registered
[    0.156777] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.157494] Advanced Linux Sound Architecture Driver Initialized.
[    0.158674] Switching to clocksource gp_timer
[    0.176685] NET: Registered protocol family 2
[    0.177679] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[    0.177769] TCP bind hash table entries: 2048 (order: 3, 40960 bytes)
[    0.177859] TCP: Hash tables configured (established 2048 bind 2048)
[    0.177951] TCP: reno registered
[    0.177978] UDP hash table entries: 256 (order: 1, 12288 bytes)
[    0.178024] UDP-Lite hash table entries: 256 (order: 1, 12288 bytes)
[    0.178516] NET: Registered protocol family 1
[    0.179106] RPC: Registered named UNIX socket transport module.
[    0.179126] RPC: Registered udp transport module.
[    0.179140] RPC: Registered tcp transport module.
[    0.179154] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.179540] Trying to unpack rootfs image as initramfs...
[    1.936008] Freeing initrd memory: 12144K
[    1.936733] CPU PMU: probing PMU on CPU 0
[    1.936766] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available
[    1.937297] omap2_mbox_probe: platform not supported
[    1.941236] VFS: Disk quotas dquot_6.5.2
[    1.941476] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.942862] NFS: Registering the id_resolver key type
[    1.942957] Key type id_resolver registered
[    1.942974] Key type id_legacy registered
[    1.943041] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    1.943474] msgmni has been set to 490
[    1.946366] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[    1.946393] io scheduler noop registered
[    1.946409] io scheduler deadline registered
[    1.946467] io scheduler cfq registered (default)
[    1.950521] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    1.952952] omap_uart 44e09000.serial: did not get pins for uart0 error: -19
[    1.953241] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88) is a OMAP UART0
[    2.614087] console [ttyO0] enabled
[    2.618637] 48022000.serial: ttyO1 at MMIO 0x48022000 (irq = 89) is a OMAP UART1
[    2.627308] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 90) is a OMAP UART2
[    2.635995] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 61) is a OMAP UART4
[    2.644603] 481aa000.serial: ttyO5 at MMIO 0x481aa000 (irq = 62) is a OMAP UART5
[    2.653626] [drm] Initialized drm 1.1.0 20060810
[    2.672260] brd: module loaded
[    2.682555] loop: module loaded
[    2.686778] bone-capemgr bone_capemgr.8: Failed to find baseboard eeprom node
[    2.696719] nand_get_flash_type: 2c,da against 2c,da
[    2.702244] ONFI param page 0 valid
[    2.705917] ONFI flash detected
[    2.709236] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron MT29F2G08ABAEAWP), 256MiB, page size: 2048, OOB size: 64
[    2.721149] omap2-nand: detected x8 NAND flash
[    2.725815] nand: using OMAP_ECC_BCH8_CODE_HW ECC scheme
[    2.731398] omap2-nand: using custom ecc layout
[    2.736241] 10 ofpart partitions found on MTD device omap2-nand.0
[    2.742635] Creating 10 MTD partitions on "omap2-nand.0":
[    2.748313] 0x000000000000-0x000000020000 : "spl"
[    2.755121] 0x000000020000-0x000000040000 : "spl_backup1"
[    2.762583] 0x000000040000-0x000000060000 : "spl_backup2"
[    2.769931] 0x000000060000-0x000000080000 : "spl_backup3"
[    2.777352] 0x000000080000-0x000000240000 : "u-boot"
[    2.785571] 0x000000240000-0x000000260000 : "bootenv"
[    2.792522] 0x000000260000-0x000000280000 : "fdt"
[    2.799107] 0x000000280000-0x000000780000 : "kernel"
[    2.810123] 0x000000800000-0x000001c00000 : "root"
[    2.833636] 0x000001c00000-0x000003000000 : "config"
[    2.857422] OneNAND driver initializing
[    2.863163] usbcore: registered new interface driver asix
[    2.868981] usbcore: registered new interface driver cdc_ether
[    2.875226] usbcore: registered new interface driver smsc95xx
[    2.881344] usbcore: registered new interface driver net1080
[    2.887368] usbcore: registered new interface driver cdc_subset
[    2.893661] usbcore: registered new interface driver zaurus
[    2.899667] usbcore: registered new interface driver cdc_ncm
[    2.906400] usbcore: registered new interface driver cdc_acm
[    2.912361] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    2.920743] Initializing USB Mass Storage driver...
[    2.925985] usbcore: registered new interface driver usb-storage
[    2.932285] USB Mass Storage support registered.
[    2.937326] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
[    2.944086] musb-hdrc musb-hdrc.0.auto: pdev->id = 0
[    2.949322] musb-hdrc musb-hdrc.0.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK
[    2.958094] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    2.958116] musb-hdrc: MHDRC RTL version 2.0
[    2.958131] musb-hdrc: setup fifo_mode 4
[    2.958159] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    2.958307] musb-hdrc musb-hdrc.0.auto: *** mode=3
[    2.963350] musb-hdrc musb-hdrc.0.auto: *** power=250
[    2.969399] musb-hdrc musb-hdrc.1.auto: pdev->id = 1
[    2.974639] musb-hdrc musb-hdrc.1.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK
[    2.983408] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    2.983428] musb-hdrc: MHDRC RTL version 2.0
[    2.983442] musb-hdrc: setup fifo_mode 4
[    2.983464] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    2.983601] musb-hdrc musb-hdrc.1.auto: *** mode=1
[    2.988642] musb-hdrc musb-hdrc.1.auto: *** power=250
[    2.993951] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[    3.000326] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 1
[    3.008803] musb-hdrc musb-hdrc.1.auto: supports USB remote wakeup
[    3.008910] usb usb1: default language 0x0409
[    3.008970] usb usb1: udev 1, busnum 1, minor = 0
[    3.008993] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    3.016138] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.023712] usb usb1: Product: MUSB HDRC host driver
[    3.028928] usb usb1: Manufacturer: Linux 3.8.13 musb-hcd
[    3.034595] usb usb1: SerialNumber: musb-hdrc.1.auto
[    3.040586] usb usb1: usb_probe_device
[    3.040614] usb usb1: configuration #1 chosen from 1 choice
[    3.040680] usb usb1: adding 1-0:1.0 (config #1, interface 0)
[    3.040881] hub 1-0:1.0: usb_probe_interface
[    3.040903] hub 1-0:1.0: usb_probe_interface - got id
[    3.040930] hub 1-0:1.0: USB hub found
[    3.044939] hub 1-0:1.0: 1 port detected
[    3.049079] hub 1-0:1.0: standalone hub
[    3.049098] hub 1-0:1.0: individual port power switching
[    3.049117] hub 1-0:1.0: no over-current protection
[    3.049134] hub 1-0:1.0: Single TT
[    3.049155] hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns)
[    3.049175] hub 1-0:1.0: power on to power good time: 10ms
[    3.049230] hub 1-0:1.0: local power source is good
[    3.049345] hub 1-0:1.0: enabling power on all ports
[    3.050460] mousedev: PS/2 mouse device common for all mice
[    3.058427] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0
[    3.065919] 44e3e000.rtc: already running
[    3.070415] i2c /dev entries driver
[    3.075477] pps_ldisc: PPS line discipline registered
[    3.080953] Driver for 1-wire Dallas network protocol.
[    3.088216] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[    3.095793] cpuidle: using governor ladder
[    3.100124] cpuidle: using governor menu
[    3.104705] of_get_named_gpio_flags exited with status 6
[    3.104726] of_get_named_gpio_flags: can't parse gpios property
[    3.104742] of_get_named_gpio_flags: can't parse gpios property
[    3.104779] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' failed
[    3.112006] omap_hsmmc mmc.4: Failed to get rstctl; not using any
[    3.118818] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25
[    3.126041] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24
[    3.133407] mmc.4 supply vmmc_aux not found, using dummy regulator
[    3.140357] omap_hsmmc mmc.4: pins are not configured from the driver
[    3.151085] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
[    3.175004] of_get_named_gpio_flags exited with status -517
[    3.175071] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[    3.182857] ledtrig-cpu: registered to indicate activity on CPUs
[    3.189638] edma-dma-engine edma-dma-engine.0: allocated channel for 0:36
[    3.196835] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
[    3.204993] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
[    3.211283] edma-dma-engine edma-dma-engine.0: allocated channel for 0:5
[    3.218456] edma-dma-engine edma-dma-engine.0: allocated channel for 0:6
[    3.230736] usbcore: registered new interface driver usbhid
[    3.236661] usbhid: USB HID core driver
[    3.243539] TCP: cubic registered
[    3.247060] Initializing XFRM netlink socket
[    3.251634] NET: Registered protocol family 17
[    3.256525] NET: Registered protocol family 15
[    3.261375] Key type dns_resolver registered
[    3.266009] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    3.274090] ThumbEE CPU extension supported.
[    3.278601] Registering SWP/SWPB emulation handler
[    3.284616] registered taskstats version 1
[    3.291233] of_get_named_gpio_flags exited with status -517
[    3.291309] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[    3.348283] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[    3.354734] davinci_mdio 4a101000.mdio: detected phy mask fffffffe
[    3.369255] libphy: 4a101000.mdio: probed
[    3.373567] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
[    3.383809] Detected MACID = 50:8c:b1:fa:fa:83
[    3.388490] cpsw 4a100000.ethernet: NAPI disabled
[    3.393884] of_get_named_gpio_flags exited with status -517
[    3.393950] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[    3.402673] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[    3.411956] cpu0 supply cpu0 not found, using dummy regulator
[    3.418439] cpufreq_cpu0: failed to scale voltage up: -22
[    3.424259] cpufreq_cpu0: failed to scale voltage up: -22
[    3.437041] ALSA device list:
[    3.440275]   No soundcards found.
[    3.444827] Freeing init memory: 264K
[    3.448879] Failed to execute /init
[    4.467953] 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.970295] net eth0: initializing cpsw version 1.12 (0)
[    5.979284] net eth0: phy found : id is : 0x7c0f1
[    5.984691] libphy: PHY 4a101000.mdio:01 not found
[    5.989886] net eth0: phy 4a101000.mdio:01 not found on slave 1
[   10.126094] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
Jan 11 21:53:44 (none) local0.err cgminer: Miner compile time: Fri Jan 05 23:17:57 CST 2018 type: Antminer L3+ Blissz v0.02 beta
Jan 11 21:53:44 (none) local0.warn cgminer: Started cgminer 4.10.0
Jan 11 21:53:44 (none) local0.notice cgminer[375]:  detected at /sys/class/gpio/gpio51/value  chain 0
Jan 11 21:53:44 (none) local0.notice cgminer[375]:  detected at /sys/class/gpio/gpio48/value  chain 1
Jan 11 21:53:44 (none) local0.notice cgminer[375]:  detected at /sys/class/gpio/gpio47/value  chain 2
Jan 11 21:53:44 (none) local0.notice cgminer[375]:  detected at /sys/class/gpio/gpio44/value  chain 3
Jan 11 21:53:44 (none) local0.notice cgminer[375]: detect total chain num 4
Jan 11 21:53:44 (none) local0.notice cgminer[375]: i2c init ok
Jan 11 21:53:55 (none) local0.notice cgminer[375]: in tty_init
Jan 11 21:53:55 (none) local0.notice cgminer[375]: tty_init 0
Jan 11 21:53:55 (none) local0.notice cgminer[375]: Start A New Asic Response.Chain Id:[0]
Jan 11 21:53:56 (none) local0.notice cgminer[375]: tty_init 1
Jan 11 21:53:56 (none) local0.notice cgminer[375]: Start A New Asic Response.Chain Id:[1]
Jan 11 21:53:56 (none) local0.notice cgminer[375]: tty_init 2
Jan 11 21:53:56 (none) local0.notice cgminer[375]: Start A New Asic Response.Chain Id:[2]
Jan 11 21:53:56 (none) local0.notice cgminer[375]: tty_init 3
Jan 11 21:53:56 (none) local0.notice cgminer[375]: Start A New Asic Response.Chain Id:[3]
Jan 11 21:53:56 (none) local0.notice cgminer[375]: open device over
Jan 11 21:53:56 (none) local0.notice cgminer[375]: send cmd to get chip address
Jan 11 21:53:58 (none) local0.notice cgminer[375]: Chain 0 ASIC 72 !!!
Jan 11 21:53:58 (none) local0.notice cgminer[375]: Chain 1 ASIC 72 !!!
Jan 11 21:53:58 (none) local0.notice cgminer[375]: Chain 2 ASIC 72 !!!
Jan 11 21:53:58 (none) local0.notice cgminer[375]: Chain 3 ASIC 72 !!!
Jan 11 21:53:58 (none) local0.notice cgminer[375]: addrInterval = '3'
Jan 11 21:53:58 (none) local0.notice cgminer[375]: software_set_address: chain 0 has 72 ASIC, and addrInterval is 3
Jan 11 21:53:59 (none) local0.notice cgminer[375]: Now Set
  • Chain Address
Jan 11 21:53:59 (none) local0.notice cgminer[375]: software_set_address: chain 1 has 72 ASIC, and addrInterval is 3
Jan 11 21:53:59 (none) local0.notice cgminer[375]: Now Set [1] Chain Address
Jan 11 21:54:00 (none) local0.notice cgminer[375]: software_set_address: chain 2 has 72 ASIC, and addrInterval is 3
Jan 11 21:54:00 (none) local0.notice cgminer[375]: Now Set [2] Chain Address
Jan 11 21:54:01 (none) local0.notice cgminer[375]: software_set_address: chain 3 has 72 ASIC, and addrInterval is 3
Jan 11 21:54:01 (none) local0.notice cgminer[375]: Now Set [3] Chain Address
Jan 11 21:54:02 (none) local0.notice cgminer[375]: frequency = '469'
Jan 11 21:54:02 (none) local0.notice cgminer[375]: dev.timeout = 15
Jan 11 21:54:03 (none) local0.notice cgminer[375]: opt_bitmain_L3_core_temp : 2
Jan 11 21:54:06 (none) local0.notice cgminer[375]: send cmd to open block
Jan 11 21:54:08 (none) local0.warn cgminer[375]: Failed to resolve (?wrong URL) stratum+tcp://:(null)
Jan 11 21:54:09 (none) local0.info cgminer[375]: Send extranonce.subscribe for stratum pool 1
Jan 11 21:54:13 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:54:14 (none) local0.warn cgminer[375]: API running in IP access mode on port 4028 (15)
Jan 11 21:54:18 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:54:23 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:54:28 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:54:33 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:54:38 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:54:43 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:54:48 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:54:53 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:54:58 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:55:03 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:55:08 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:55:13 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:55:18 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:55:23 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:55:28 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:55:33 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:55:38 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:55:43 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:55:48 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:55:53 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:55:58 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:56:03 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:56:08 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:56:14 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:56:19 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:56:24 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:56:29 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:56:34 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:56:39 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:56:44 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:56:49 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:56:54 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:56:59 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:57:04 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:57:09 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:57:14 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:57:19 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:57:24 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:57:29 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:57:34 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:57:39 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:57:44 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:57:49 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:57:54 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:57:59 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:58:04 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:58:09 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:58:14 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:58:19 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:58:24 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:58:29 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:58:34 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:58:39 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:58:44 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:58:45 (none) local0.warn cgminer[375]: Switching to pool 3 stratum+tcp://litecoinpool.org:3333
Jan 11 21:58:49 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:58:54 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:58:59 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:59:04 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:59:09 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:59:14 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:59:19 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:59:24 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:59:29 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:59:34 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:59:39 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:59:44 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:59:49 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:59:54 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 21:59:59 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:00:04 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:00:09 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:00:14 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:00:19 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:00:24 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:00:29 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:00:34 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:00:35 (none) local0.warn cgminer[375]: Switching to pool 0 stratum+tcp://hash-to-coins.com:4444
Jan 11 22:00:39 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:00:44 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:00:49 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:00:54 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:00:59 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:01:04 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:01:09 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:01:14 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:01:19 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:01:24 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:01:29 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:01:34 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:01:39 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:01:44 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:01:49 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:01:54 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blastar on January 11, 2018, 10:20:48 PM
Hey can you also have a look at S4 S7 S9
    greate work btw

Me too interested on S9. I hate the noise who make when go over 77°.

Just a suggestion for Blissz, I prefer to pay a license (like 100$ forever blocked on the serial number of the miner) instead to give you a fee, but it's only my opinion.

Anyway, great works! Thank you

I suggested the same early on when he started with D3, with detailed info about how to do it using the MAC address of the miner, but Blissz never replied! I guess he wants to keep it this way! :(


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: dottat on January 12, 2018, 04:22:16 AM
Hey Blissz

first of all, thx again for such a good firmware (like for D3)


Jan 11 22:01:39 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:01:44 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:01:49 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:01:54 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)

Do you happen to have miner pool 1 blank on the miner configuration page?  If you do, you will see this error.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: olebol on January 12, 2018, 09:31:15 AM
Hey Blissz

first of all, thx again for such a good firmware (like for D3)


Jan 11 22:01:39 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:01:44 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:01:49 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 11 22:01:54 (none) local0.info cgminer[375]: Failed to getaddrinfo for stratum+tcp://:(null)

Do you happen to have miner pool 1 blank on the miner configuration page?  If you do, you will see this error.


no ... my first pool is the same like before... dont know why this is shown
i have no problems but the kernel log show that errors, any ideas Blissz?


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: majdi105 on January 12, 2018, 03:12:10 PM
we need one for s9 but l3+ is very slient and it consume only 750w


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: dlezama on January 12, 2018, 05:27:30 PM
If anybody is interested in buying an L3+ Jan batch for 0.3 BTC + shipping drop me a PM. It's still under warranty as I haven't installed blissz firmware yet. If I don't sell it I'll probably give this a try soon, since the D3 version is working really well for me.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: dottat on January 12, 2018, 10:03:41 PM
If anybody is interested in buying an L3+ Jan batch for 0.3 BTC + shipping drop me a PM. It's still under warranty as I haven't installed blissz firmware yet. If I don't sell it I'll probably give this a try soon, since the D3 version is working really well for me.

And what might you be asking for that?  stateside or not?


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: xcajun21 on January 12, 2018, 10:29:36 PM
I have a hosted miner so would like to ask some questions. I have no access to the miner settings.

1. Restart on low hash rate is available on stock firmware? Is this option really useful?
2. Lower voltage come default with this firmware? if not, what settings are recommended for ultra stability, but a bit lower consumption?
3. Are Fan speeds changed after updating?
4. The fee from changing to dev pool and the restart of work loads, does affect the profitability a lot?

Thanks.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 13, 2018, 02:04:12 AM
I have a hosted miner so would like to ask some questions. I have no access to the miner settings.

1. Restart on low hash rate is available on stock firmware? Is this option really useful?
In case you run it on the limit yes, as it will automatically restart in case one of your chains fail.
2. Lower voltage come default with this firmware? if not, what settings are recommended for ultra stability, but a bit lower consumption?
voltage to lowest, and frequency ~400 Mhz
3. Are Fan speeds changed after updating?
Only during startup it runs slow. After that it starts on the default fan speed. But at lowest voltage I can recommend the silent preset.
4. The fee from changing to dev pool and the restart of work loads, does affect the profitability a lot?
Not much, but the v1.0 will have the 24h defvee mode, so it will only mine on the devfee pool once a day

Thanks.

comments inside the quote ;)


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 13, 2018, 02:07:00 AM
v1.0 :: 12/01/2018 :: L3+ recommended update

Download:
https://mega.nz/#!z9gklSSL!jBfvhN-YRiC417_GQwon9-O0PCbXbIqTdXCSt7evF80 (https://mega.nz/#!z9gklSSL!jBfvhN-YRiC417_GQwon9-O0PCbXbIqTdXCSt7evF80)

changelog v1.0 L3+ version 12/01/2018:
- first stable release  8)
- reboot (and cool down) on too high temperatures (PCB temp > 85 deg celcius)
- optional: reboot on too high ASIC fail count
- optional: reboot on detection of low hashrate (if falls down 8% under the expected hashrate)
- now shows the voltage setting on the overview page
- fixed showing high FAN speed RPM's
- added option to mine the dev fee one time a day (increases daily profit a bit in case you run it  constantly on one pool)


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: unreal1 on January 13, 2018, 04:24:23 AM
v1.0 :: 12/01/2018 :: L3+ recommended update

Download:
https://mega.nz/#!z9gklSSL!jBfvhN-YRiC417_GQwon9-O0PCbXbIqTdXCSt7evF80 (https://mega.nz/#!z9gklSSL!jBfvhN-YRiC417_GQwon9-O0PCbXbIqTdXCSt7evF80)

changelog v1.0 L3+ version 12/01/2018:
- first stable release  8)
- reboot (and cool down) on too high temperatures (PCB temp > 85 deg celcius)
- optional: reboot on too high ASIC fail count
- optional: reboot on detection of low hashrate (if falls down 8% under the expected hashrate)
- now shows the voltage setting on the overview page
- fixed showing high FAN speed RPM's
- added option to mine the dev fee one time a day (increases daily profit a bit in case you run it  constantly on one pool)

Thanks, appreciate the dev fee once a day since I mine from the same pool.


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: mettalmag on January 13, 2018, 04:59:58 AM
WARNING THIS FIRMWARE MIGHT VOID THE WARRANTY ON YOUR MINER

https://img4.hostingpics.net/pics/145857banner.jpg



https://img15.hostingpics.net/pics/893377382.jpg

https://img15.hostingpics.net/pics/550407481.jpg

v1.0 :: 12/01/2018 :: L3+ stable


Download:
https://mega.nz/#!z9gklSSL!jBfvhN-YRiC417_GQwon9-O0PCbXbIqTdXCSt7evF80 (https://mega.nz/#!z9gklSSL!jBfvhN-YRiC417_GQwon9-O0PCbXbIqTdXCSt7evF80)


Upgrade instructions:
  • Recommended, at your current firmware, set the miner frequency at 350mhz before flashing.
  • Download the custom firmware. (don't unpack it)
  • Flash by going to "System" -> "Upgrade" -> "Flash new firmware image" and select the custom firmware.
  • After flashing, check the advanced settings page and set the global values to the lowest voltage setting and 375mhz. From there increase your frequency to see how high you can go at the lowest voltage setting.
  • Start tweaking some more. See the profile suggestions below.

v1.0 L3+ version 12/01/2018:
- first stable release  8)
- reboot (and cool down) on too high temperatures (PCB temp > 85 deg celcius)
- optional: reboot on too high ASIC fail count
- optional: reboot on detection of low hashrate (if falls down 8% under the expected hashrate)
- now shows the voltage setting on the overview page
- fixed showing high FAN speed RPM's
- added option to mine the dev fee one time a day (increases daily profit a bit in case you run it on one pool)

v0.02 L3+ version 05/01/2018:
- awesome miner support / other API tools now compatible
- fixed frequency ranges in advanced miner page

First L3+ version 05/01/2018:
- Adds unlocked voltage global or individual per chain. Saves up to 20% energy usage compared to the stock firmware. (unit runs ~500Mh/s @ ~670watt)
- Adds frequency setting per individual chain.
- cgminer update to 4.10
- Adds 3 fan profile modes
- No more high fan speed durings startup
- Faster startup time
- Cleaned up web interface
- Cleaned up kernel log
- Possible to flash back to the default firmware (see guide below)
- Possible to change the stock fans for custom fans

know issues:
- Only tested on L3+. Unsure if this runs on the a normal L3 (non plus).
- This is beta firmware, so please report the issues you have

Important:
- As this firmware allows extreme overclocking / reduce fan speeds, I am not responsible for any damage to your miner. So flash at your own risk and please use the firmware wisely.
- There is a 1,5% mining fee as compensation for the effort I put into this project.

Some startup settings to get you going:

stock speeds @ low power -> silenced and improved miner lifetime (my personal preference)

Expected hashrate: 480MH/s to 540 MH/s
Expected power usage: 600 - 770 watt

set the global frequency at "375" and increase upto 425mhz (depends per unit how far it clocks stable), set the global voltage to "lowest". Now slowly increase the frequency from 375Mhz to 425 until you see HW errors. When you have a few HW errors an hour you found the sweet spot
set the fan speed to silent for silent operation.

More profiles to come...
...


Back to bitmain stock firmware:
In case you want to go back to the original firmware:
- set the voltage of all boards to 12 or 13 before flashing back (just to make sure...)
- download and flash the stock firmware image: https://shop.bitmain.com/support.htm?pid=0072017042706354248975UNDh65062D (https://shop.bitmain.com/support.htm?pid=0072017042706354248975UNDh65062D)
- reset to defaults

Guide if your boards doesn't get recognized / if you accidently flashed the D3 firmware on your L3+
- set the global voltage to 13 (as it can be the case that your boards don't like a low voltage)
if that doesn't work:
- disconnect all hashing boards from the controller and start it up. Try to flash the stock firmware
Then reconnect the hashing boards.
- if flashing doesn't work: do the same but use the micro sd card recovery (see topic start).
- if the stock firmware doesn't work, have a look here: https://bitcointalk.org/index.php?topic=2383200.0 then your hashing boards needs to be recovered one by one.

Firmware recovery:
This is only needed if the miner doesn't boot anymore (In case you had a bad / interrupted) flash:
- get a microsd card
- write this image to it with win32diskimager: https://shop.bitmain.com/support.htm?pid=007201604120945219855QObfk20066C (https://shop.bitmain.com/support.htm?pid=007201604120945219855QObfk20066C)
- insert the micro sd card in the d3 controller board and power it on. The miner webinterface will come up again. (maybe under another ip)
- redownload the firmware and flash again.
- remove the micro sd card

Special thanks goes to:
- cryptonitro for this awesome new Antminer icon

D3 custom firmware available here:
https://bitcointalk.org/index.php?topic=2346161.0 (https://bitcointalk.org/index.php?topic=2346161.0)

this is amazing really!
I used you firmware on couple of my D3s and it is perfect, even if the response time is a bit slower than original it is still better!
keep it up and hope to see firmware for S9s as well


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: dganm on January 13, 2018, 08:56:09 AM
I'm testing my l3+ with the new 1.0 stable version and every time I restart the miner, after some minutes it begins to mine the dev fee.

I have selected the option "Mine dev fee daily instead of every 2 hours".


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: Michi_A on January 13, 2018, 09:03:28 AM
Same here. Moreover the Miner Status page shows no entries.


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: blissz on January 13, 2018, 09:11:02 AM
I'm testing my l3+ with the new 1.0 stable version and every time I restart the miner, after some minutes it begins to mine the dev fee.

I have selected the option "Mine dev fee daily instead of every 2 hours".

While still tuning / restarting a lot, please don't use the the daily option as it will always start with the devfee after 5 minutes. Once you found your settings, the daily option is the most effective.


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: blissz on January 13, 2018, 09:11:34 AM
Same here. Moreover the Miner Status page shows no entries.

can you make a screen shot?


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: Michi_A on January 13, 2018, 09:21:19 AM
Same here. Moreover the Miner Status page shows no entries.

can you make a screen shot?

http://i64.tinypic.com/2ir6vdj.jpg

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: 238776k/238776k available, 23368k 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.000357] Calibrating delay loop... 545.07 BogoMIPS (lpj=531968)
[    0.015438] pid_max: default: 32768 minimum: 301
[    0.015667] Security Framework initialized
[    0.015762] Mount-cache hash table entries: 512
[    0.024595] Initializing cgroup subsys cpuacct
[    0.024628] Initializing cgroup subsys memory
[    0.024693] Initializing cgroup subsys blkio
[    0.024829] CPU: Testing write buffer coherency: ok
[    0.025407] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[    0.025482] Setting up static identity map for 0x8038c820 - 0x8038c86c
[    0.026804] Brought up 1 CPUs
[    0.026827] SMP: Total of 1 processors activated (545.07 BogoMIPS).
[    0.028119] devtmpfs: initialized
[    0.092469] pinctrl core: initialized pinctrl subsystem
[    0.092682] rstctl core: initialized rstctl subsystem
[    0.093176] regulator-dummy: no parameters
[    0.093739] NET: Registered protocol family 16
[    0.094441] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.104111] pinctrl-single 44e10800.pinmux: prop pinctrl-0 index 0 invalid phandle
[    0.104293] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[    0.105376] platform 49000000.edma: alias fck already exists
[    0.105410] platform 49000000.edma: alias fck already exists
[    0.105437] platform 49000000.edma: alias fck already exists
[    0.106593] gpiochip_add: registered GPIOs 0 to 31 on device: gpio
[    0.106777] OMAP GPIO hardware version 0.1
[    0.108192] gpiochip_add: registered GPIOs 32 to 63 on device: gpio
[    0.109516] gpiochip_add: registered GPIOs 64 to 95 on device: gpio
[    0.110834] gpiochip_add: registered GPIOs 96 to 127 on device: gpio
[    0.111465] of_get_named_gpio_flags exited with status 52
[    0.111498] gpio-rctrl rstctl.3: loaded OK
[    0.116594] omap-gpmc 50000000.gpmc: GPMC revision 6.0
[    0.119807] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.121996] cpsw.0: No hwaddr in dt. Using b0:d5:cc:ac:bf:36 from efuse
[    0.122028] cpsw.1: No hwaddr in dt. Using b0:d5:cc:ac:bf:38 from efuse
[    0.137596] 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.150258] vmmcsd_fixed: 3300 mV
[    0.153377] SCSI subsystem initialized
[    0.153827] usbcore: registered new interface driver usbfs
[    0.153941] usbcore: registered new interface driver hub
[    0.154282] usbcore: registered new device driver usb
[    0.156399] omap_i2c 4819c000.i2c: bus 0 rev0.11 at 100 kHz
[    0.156432] omap_i2c 4819c000.i2c: unable to select pin group
[    0.156625] media: Linux media interface: v0.10
[    0.156719] 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.157572] Advanced Linux Sound Architecture Driver Initialized.
[    0.158755] Switching to clocksource gp_timer
[    0.176783] NET: Registered protocol family 2
[    0.177772] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[    0.177861] TCP bind hash table entries: 2048 (order: 3, 40960 bytes)
[    0.177951] TCP: Hash tables configured (established 2048 bind 2048)
[    0.178042] TCP: reno registered
[    0.178069] UDP hash table entries: 256 (order: 1, 12288 bytes)
[    0.178115] UDP-Lite hash table entries: 256 (order: 1, 12288 bytes)
[    0.178609] NET: Registered protocol family 1
[    0.179198] RPC: Registered named UNIX socket transport module.
[    0.179218] RPC: Registered udp transport module.
[    0.179231] RPC: Registered tcp transport module.
[    0.179245] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.179632] Trying to unpack rootfs image as initramfs...
[    1.937204] Freeing initrd memory: 12140K
[    1.937893] CPU PMU: probing PMU on CPU 0
[    1.937928] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available
[    1.938548] omap2_mbox_probe: platform not supported
[    1.942421] VFS: Disk quotas dquot_6.5.2
[    1.942660] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.943967] NFS: Registering the id_resolver key type
[    1.944124] Key type id_resolver registered
[    1.944143] Key type id_legacy registered
[    1.944211] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    1.944651] msgmni has been set to 490
[    1.947452] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[    1.947478] io scheduler noop registered
[    1.947494] io scheduler deadline registered
[    1.947551] io scheduler cfq registered (default)
[    1.951494] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    1.954104] omap_uart 44e09000.serial: did not get pins for uart0 error: -19
[    1.954382] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88) is a OMAP UART0
[    2.615278] console [ttyO0] enabled
[    2.619862] 48022000.serial: ttyO1 at MMIO 0x48022000 (irq = 89) is a OMAP UART1
[    2.628506] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 90) is a OMAP UART2
[    2.637157] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 61) is a OMAP UART4
[    2.645820] 481aa000.serial: ttyO5 at MMIO 0x481aa000 (irq = 62) is a OMAP UART5
[    2.654805] [drm] Initialized drm 1.1.0 20060810
[    2.673474] brd: module loaded
[    2.683730] loop: module loaded
[    2.687919] bone-capemgr bone_capemgr.8: Failed to find baseboard eeprom node
[    2.697853] nand_get_flash_type: 2c,da against 2c,da
[    2.703387] ONFI param page 0 valid
[    2.707060] ONFI flash detected
[    2.710382] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron MT29F2G08ABAEAWP), 256MiB, page size: 2048, OOB size: 64
[    2.722296] omap2-nand: detected x8 NAND flash
[    2.726961] nand: using OMAP_ECC_BCH8_CODE_HW ECC scheme
[    2.732544] omap2-nand: using custom ecc layout
[    2.737391] 10 ofpart partitions found on MTD device omap2-nand.0
[    2.743786] Creating 10 MTD partitions on "omap2-nand.0":
[    2.749464] 0x000000000000-0x000000020000 : "spl"
[    2.756244] 0x000000020000-0x000000040000 : "spl_backup1"
[    2.763713] 0x000000040000-0x000000060000 : "spl_backup2"
[    2.771126] 0x000000060000-0x000000080000 : "spl_backup3"
[    2.778540] 0x000000080000-0x000000240000 : "u-boot"
[    2.786795] 0x000000240000-0x000000260000 : "bootenv"
[    2.793735] 0x000000260000-0x000000280000 : "fdt"
[    2.800358] 0x000000280000-0x000000780000 : "kernel"
[    2.811394] 0x000000800000-0x000001c00000 : "root"
[    2.834927] 0x000001c00000-0x000003000000 : "config"
[    2.858726] OneNAND driver initializing
[    2.864489] usbcore: registered new interface driver asix
[    2.870307] usbcore: registered new interface driver cdc_ether
[    2.876553] usbcore: registered new interface driver smsc95xx
[    2.882672] usbcore: registered new interface driver net1080
[    2.888698] usbcore: registered new interface driver cdc_subset
[    2.894995] usbcore: registered new interface driver zaurus
[    2.901004] usbcore: registered new interface driver cdc_ncm
[    2.907742] usbcore: registered new interface driver cdc_acm
[    2.913703] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    2.922084] Initializing USB Mass Storage driver...
[    2.927326] usbcore: registered new interface driver usb-storage
[    2.933628] USB Mass Storage support registered.
[    2.938672] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
[    2.945390] musb-hdrc musb-hdrc.0.auto: pdev->id = 0
[    2.950634] musb-hdrc musb-hdrc.0.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK
[    2.959404] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    2.959427] musb-hdrc: MHDRC RTL version 2.0
[    2.959442] musb-hdrc: setup fifo_mode 4
[    2.959470] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    2.959652] musb-hdrc musb-hdrc.0.auto: *** mode=3
[    2.964691] musb-hdrc musb-hdrc.0.auto: *** power=250
[    2.970703] musb-hdrc musb-hdrc.1.auto: pdev->id = 1
[    2.975951] musb-hdrc musb-hdrc.1.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK
[    2.984721] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    2.984742] musb-hdrc: MHDRC RTL version 2.0
[    2.984756] musb-hdrc: setup fifo_mode 4
[    2.984778] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    2.984921] musb-hdrc musb-hdrc.1.auto: *** mode=1
[    2.989965] musb-hdrc musb-hdrc.1.auto: *** power=250
[    2.995274] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[    3.001897] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 1
[    3.010156] musb-hdrc musb-hdrc.1.auto: supports USB remote wakeup
[    3.010260] usb usb1: default language 0x0409
[    3.010319] usb usb1: udev 1, busnum 1, minor = 0
[    3.010342] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    3.017470] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.025042] usb usb1: Product: MUSB HDRC host driver
[    3.030257] usb usb1: Manufacturer: Linux 3.8.13 musb-hcd
[    3.035925] usb usb1: SerialNumber: musb-hdrc.1.auto
[    3.041931] usb usb1: usb_probe_device
[    3.041959] usb usb1: configuration #1 chosen from 1 choice
[    3.042023] usb usb1: adding 1-0:1.0 (config #1, interface 0)
[    3.042224] hub 1-0:1.0: usb_probe_interface
[    3.042246] hub 1-0:1.0: usb_probe_interface - got id
[    3.042273] hub 1-0:1.0: USB hub found
[    3.046271] hub 1-0:1.0: 1 port detected
[    3.050409] hub 1-0:1.0: standalone hub
[    3.050429] hub 1-0:1.0: individual port power switching
[    3.050448] hub 1-0:1.0: no over-current protection
[    3.050465] hub 1-0:1.0: Single TT
[    3.050487] hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns)
[    3.050506] hub 1-0:1.0: power on to power good time: 10ms
[    3.050561] hub 1-0:1.0: local power source is good
[    3.050674] hub 1-0:1.0: enabling power on all ports
[    3.051789] mousedev: PS/2 mouse device common for all mice
[    3.059739] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0
[    3.067230] 44e3e000.rtc: already running
[    3.071735] i2c /dev entries driver
[    3.076745] pps_ldisc: PPS line discipline registered
[    3.082231] Driver for 1-wire Dallas network protocol.
[    3.089491] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[    3.097054] cpuidle: using governor ladder
[    3.101381] cpuidle: using governor menu
[    3.105959] of_get_named_gpio_flags exited with status 6
[    3.105978] of_get_named_gpio_flags: can't parse gpios property
[    3.105994] of_get_named_gpio_flags: can't parse gpios property
[    3.106031] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' failed
[    3.113253] omap_hsmmc mmc.4: Failed to get rstctl; not using any
[    3.120102] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25
[    3.127320] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24
[    3.134645] mmc.4 supply vmmc_aux not found, using dummy regulator
[    3.141630] omap_hsmmc mmc.4: pins are not configured from the driver
[    3.151167] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
[    3.175080] of_get_named_gpio_flags exited with status -517
[    3.175146] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[    3.182923] ledtrig-cpu: registered to indicate activity on CPUs
[    3.189695] edma-dma-engine edma-dma-engine.0: allocated channel for 0:36
[    3.196892] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
[    3.205057] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
[    3.211354] edma-dma-engine edma-dma-engine.0: allocated channel for 0:5
[    3.218536] edma-dma-engine edma-dma-engine.0: allocated channel for 0:6
[    3.230796] usbcore: registered new interface driver usbhid
[    3.236715] usbhid: USB HID core driver
[    3.243632] TCP: cubic registered
[    3.247157] Initializing XFRM netlink socket
[    3.251737] NET: Registered protocol family 17
[    3.256594] NET: Registered protocol family 15
[    3.261466] Key type dns_resolver registered
[    3.266115] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    3.274231] ThumbEE CPU extension supported.
[    3.278743] Registering SWP/SWPB emulation handler
[    3.284757] registered taskstats version 1
[    3.291381] of_get_named_gpio_flags exited with status -517
[    3.291456] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[    3.348367] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[    3.354782] davinci_mdio 4a101000.mdio: detected phy mask fffffffe
[    3.369338] libphy: 4a101000.mdio: probed
[    3.373660] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
[    3.383897] Detected MACID = b0:d5:cc:ac:bf:36
[    3.388580] cpsw 4a100000.ethernet: NAPI disabled
[    3.393970] of_get_named_gpio_flags exited with status -517
[    3.394037] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[    3.402766] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[    3.412052] cpu0 supply cpu0 not found, using dummy regulator
[    3.418542] cpufreq_cpu0: failed to scale voltage up: -22
[    3.424364] cpufreq_cpu0: failed to scale voltage up: -22
[    3.437140] ALSA device list:
[    3.440373]   No soundcards found.
[    3.444922] Freeing init memory: 264K
[    3.448972] Failed to execute /init
[    4.521946] 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.
[    6.111067] net eth0: initializing cpsw version 1.12 (0)
[    6.119979] net eth0: phy found : id is : 0x7c0f1
[    6.125399] libphy: PHY 4a101000.mdio:01 not found
[    6.130596] net eth0: phy 4a101000.mdio:01 not found on slave 1
[   10.266852] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
Jan 13 08:34:39 (none) local0.err cgminer: Miner compile time: Fri Jan 12 19:41:57 CST 2018 type: Antminer L3+ Blissz v1.0
Jan 13 08:34:39 (none) local0.warn cgminer: Started cgminer 4.10.0
Jan 13 08:34:39 (none) local0.notice cgminer[361]:  detected at /sys/class/gpio/gpio51/value  chain 0
Jan 13 08:34:39 (none) local0.notice cgminer[361]:  detected at /sys/class/gpio/gpio48/value  chain 1
Jan 13 08:34:39 (none) local0.notice cgminer[361]:  detected at /sys/class/gpio/gpio47/value  chain 2
Jan 13 08:34:39 (none) local0.notice cgminer[361]:  detected at /sys/class/gpio/gpio44/value  chain 3
Jan 13 08:34:39 (none) local0.notice cgminer[361]: detect total chain num 4
Jan 13 08:34:39 (none) local0.notice cgminer[361]: i2c init ok
Jan 13 08:34:50 (none) local0.notice cgminer[361]: in tty_init
Jan 13 08:34:50 (none) local0.notice cgminer[361]: tty_init 0
Jan 13 08:34:50 (none) local0.notice cgminer[361]: Start A New Asic Response.Chain Id:[0]
Jan 13 08:34:51 (none) local0.notice cgminer[361]: tty_init 1
Jan 13 08:34:51 (none) local0.notice cgminer[361]: Start A New Asic Response.Chain Id:[1]
Jan 13 08:34:51 (none) local0.notice cgminer[361]: tty_init 2
Jan 13 08:34:51 (none) local0.notice cgminer[361]: Start A New Asic Response.Chain Id:[2]
Jan 13 08:34:51 (none) local0.notice cgminer[361]: tty_init 3
Jan 13 08:34:51 (none) local0.notice cgminer[361]: Start A New Asic Response.Chain Id:[3]
Jan 13 08:34:51 (none) local0.notice cgminer[361]: open device over
Jan 13 08:34:51 (none) local0.notice cgminer[361]: send cmd to get chip address
Jan 13 08:34:53 (none) local0.notice cgminer[361]: Chain 0 ASIC 72 !!!
Jan 13 08:34:53 (none) local0.notice cgminer[361]: Chain 1 ASIC 72 !!!
Jan 13 08:34:53 (none) local0.notice cgminer[361]: Chain 2 ASIC 72 !!!
Jan 13 08:34:53 (none) local0.notice cgminer[361]: Chain 3 ASIC 72 !!!
Jan 13 08:34:53 (none) local0.notice cgminer[361]: addrInterval = '3'
Jan 13 08:34:53 (none) local0.notice cgminer[361]: software_set_address: chain 0 has 72 ASIC, and addrInterval is 3
Jan 13 08:34:53 (none) local0.notice cgminer[361]: Now Set [0] Chain Address
Jan 13 08:34:54 (none) local0.notice cgminer[361]: software_set_address: chain 1 has 72 ASIC, and addrInterval is 3
Jan 13 08:34:54 (none) local0.notice cgminer[361]: Now Set [1] Chain Address
Jan 13 08:34:55 (none) local0.notice cgminer[361]: software_set_address: chain 2 has 72 ASIC, and addrInterval is 3
Jan 13 08:34:55 (none) local0.notice cgminer[361]: Now Set [2] Chain Address
Jan 13 08:34:56 (none) local0.notice cgminer[361]: software_set_address: chain 3 has 72 ASIC, and addrInterval is 3
Jan 13 08:34:56 (none) local0.notice cgminer[361]: Now Set [3] Chain Address
Jan 13 08:34:57 (none) local0.notice cgminer[361]: frequency = '394'
Jan 13 08:34:57 (none) local0.notice cgminer[361]: dev.timeout = 19
Jan 13 08:34:57 (none) local0.notice cgminer[361]: opt_bitmain_L3_core_temp : 2
Jan 13 08:35:01 (none) local0.notice cgminer[361]: send cmd to open block
Jan 13 08:35:03 (none) local0.err cgminer[361]: low hashrate detection trigger: 476.037734 Mh/s
Jan 13 08:35:03 (none) local0.warn cgminer[361]: Failed to resolve (?wrong URL) stratum+tcp://:(null)
Jan 13 08:35:04 (none) local0.warn cgminer[361]: Pool 2 stratum+tcp://hub.miningpoolhub.com:17001 alive, testing stability
Jan 13 08:35:04 (none) local0.warn cgminer[361]: Switching to pool 2 stratum+tcp://hub.miningpoolhub.com:17001
Jan 13 08:35:04 (none) local0.warn cgminer[361]: Pool 1 stratum+tcp://prohashing.com:3333 alive, testing stability
Jan 13 08:35:04 (none) local0.warn cgminer[361]: Switching to pool 1 stratum+tcp://prohashing.com:3333
Jan 13 08:35:08 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:09 (none) local0.warn cgminer[361]: API running in IP access mode on port 4028 (15)
Jan 13 08:35:13 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:18 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:23 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:28 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:33 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:38 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:43 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:48 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:53 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:58 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:03 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:08 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:13 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:18 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:23 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:28 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:33 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:38 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:43 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:48 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:53 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:58 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:03 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:08 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:13 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:18 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:23 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:28 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:33 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:38 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:43 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:48 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:53 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:58 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:03 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:08 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:13 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:18 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:24 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:29 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:34 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:39 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:44 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:49 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:54 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:59 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:04 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:09 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:14 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:19 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:24 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:29 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:34 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:39 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:40 (none) local0.warn cgminer[361]: Switching to pool 3 stratum+tcp://litecoinpool.org:3333
Jan 13 08:39:44 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:49 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:54 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:59 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:04 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:09 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:14 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:19 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:24 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:29 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:34 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:39 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:44 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:49 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:54 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:59 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:41:04 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:41:09 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:41:14 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:41:19 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:41:24 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:41:29 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:41:31 (none) local0.err cgminer: Miner compile time: Fri Jan 12 19:41:57 CST 2018 type: Antminer L3+ Blissz v1.0
Jan 13 08:41:31 (none) local0.warn cgminer: Started cgminer 4.10.0
Jan 13 08:41:31 (none) local0.notice cgminer[31059]:  detected at /sys/class/gpio/gpio51/value  chain 0
Jan 13 08:41:31 (none) local0.notice cgminer[31059]:  detected at /sys/class/gpio/gpio48/value  chain 1
Jan 13 08:41:31 (none) local0.notice cgminer[31059]:  detected at /sys/class/gpio/gpio47/value  chain 2
Jan 13 08:41:31 (none) local0.notice cgminer[31059]:  detected at /sys/class/gpio/gpio44/value  chain 3
Jan 13 08:41:31 (none) local0.notice cgminer[31059]: detect total chain num 4
Jan 13 08:41:31 (none) local0.notice cgminer[31059]: i2c init ok
Jan 13 08:41:42 (none) local0.notice cgminer[31059]: in tty_init
Jan 13 08:41:42 (none) local0.notice cgminer[31059]: tty_init 0
Jan 13 08:41:42 (none) local0.notice cgminer[31059]: Start A New Asic Response.Chain Id:[0]
Jan 13 08:41:42 (none) local0.notice cgminer[31059]: tty_init 1
Jan 13 08:41:42 (none) local0.notice cgminer[31059]: Start A New Asic Response.Chain Id:[1]
Jan 13 08:41:43 (none) local0.notice cgminer[31059]: tty_init 2
Jan 13 08:41:43 (none) local0.notice cgminer[31059]: Start A New Asic Response.Chain Id:[2]
Jan 13 08:41:43 (none) local0.notice cgminer[31059]: tty_init 3
Jan 13 08:41:43 (none) local0.notice cgminer[31059]: Start A New Asic Response.Chain Id:[3]
Jan 13 08:41:43 (none) local0.notice cgminer[31059]: open device over
Jan 13 08:41:43 (none) local0.notice cgminer[31059]: send cmd to get chip address
Jan 13 08:41:45 (none) local0.notice cgminer[31059]: Chain 0 ASIC 72 !!!
Jan 13 08:41:45 (none) local0.notice cgminer[31059]: Chain 1 ASIC 72 !!!
Jan 13 08:41:45 (none) local0.notice cgminer[31059]: Chain 2 ASIC 72 !!!
Jan 13 08:41:45 (none) local0.notice cgminer[31059]: Chain 3 ASIC 72 !!!
Jan 13 08:41:45 (none) local0.notice cgminer[31059]: addrInterval = '3'
Jan 13 08:41:45 (none) local0.notice cgminer[31059]: software_set_address: chain 0 has 72 ASIC, and addrInterval is 3
Jan 13 08:41:45 (none) local0.notice cgminer[31059]: Now Set [0] Chain Address
Jan 13 08:41:46 (none) local0.notice cgminer[31059]: software_set_address: chain 1 has 72 ASIC, and addrInterval is 3
Jan 13 08:41:46 (none) local0.notice cgminer[31059]: Now Set [1] Chain Address
Jan 13 08:41:47 (none) local0.notice cgminer[31059]: software_set_address: chain 2 has 72 ASIC, and addrInterval is 3
Jan 13 08:41:47 (none) local0.notice cgminer[31059]: Now Set [2] Chain Address
Jan 13 08:41:48 (none) local0.notice cgminer[31059]: software_set_address: chain 3 has 72 ASIC, and addrInterval is 3
Jan 13 08:41:48 (none) local0.notice cgminer[31059]: Now Set [3] Chain Address
Jan 13 08:41:49 (none) local0.notice cgminer[31059]: frequency = '394'
Jan 13 08:41:49 (none) local0.notice cgminer[31059]: dev.timeout = 19
Jan 13 08:41:49 (none) local0.notice cgminer[31059]: opt_bitmain_L3_core_temp : 2
Jan 13 08:41:52 (none) local0.notice cgminer[31059]: send cmd to open block
Jan 13 08:41:55 (none) local0.err cgminer[31059]: low hashrate detection trigger: 476.037734 Mh/s
Jan 13 08:41:55 (none) local0.warn cgminer[31059]: Pool 3 stratum+tcp://litecoinpool.org:3333 alive, testing stability
Jan 13 08:41:55 (none) local0.warn cgminer[31059]: Switching to pool 3 stratum+tcp://litecoinpool.org:3333
Jan 13 08:41:55 (none) local0.info cgminer[31059]: Send extranonce.subscribe for stratum pool 2
Jan 13 08:41:55 (none) local0.warn cgminer[31059]: Pool 2 stratum+tcp://scrypt.eu.nicehash.com:3333 alive, testing stability
Jan 13 08:41:55 (none) local0.warn cgminer[31059]: Switching to pool 2 stratum+tcp://scrypt.eu.nicehash.com:3333
Jan 13 08:41:56 (none) local0.warn cgminer[31059]: Pool 1 stratum+tcp://hub.miningpoolhub.com:17001 alive, testing stability
Jan 13 08:41:56 (none) local0.warn cgminer[31059]: Switching to pool 1 stratum+tcp://hub.miningpoolhub.com:17001
Jan 13 08:41:56 (none) local0.warn cgminer[31059]: Pool 0 stratum+tcp://prohashing.com:3333 alive, testing stability
Jan 13 08:41:56 (none) local0.warn cgminer[31059]: Switching to pool 0 stratum+tcp://prohashing.com:3333
Jan 13 08:42:01 (none) local0.warn cgminer[31059]: API running in IP access mode on port 4028 (19)
Jan 13 08:46:32 (none) local0.warn cgminer[31059]: Switching to pool 3 stratum+tcp://litecoinpool.org:3333
Jan 13 09:00:40 (none) local0.err cgminer: Miner compile time: Fri Jan 12 19:41:57 CST 2018 type: Antminer L3+ Blissz v1.0
Jan 13 09:00:40 (none) local0.warn cgminer: Started cgminer 4.10.0
Jan 13 09:00:40 (none) local0.notice cgminer[11315]:  detected at /sys/class/gpio/gpio51/value  chain 0
Jan 13 09:00:40 (none) local0.notice cgminer[11315]:  detected at /sys/class/gpio/gpio48/value  chain 1
Jan 13 09:00:40 (none) local0.notice cgminer[11315]:  detected at /sys/class/gpio/gpio47/value  chain 2
Jan 13 09:00:40 (none) local0.notice cgminer[11315]:  detected at /sys/class/gpio/gpio44/value  chain 3
Jan 13 09:00:40 (none) local0.notice cgminer[11315]: detect total chain num 4
Jan 13 09:00:40 (none) local0.notice cgminer[11315]: i2c init ok
Jan 13 09:00:51 (none) local0.notice cgminer[11315]: in tty_init
Jan 13 09:00:51 (none) local0.notice cgminer[11315]: tty_init 0
Jan 13 09:00:51 (none) local0.notice cgminer[11315]: Start A New Asic Response.Chain Id:[0]
Jan 13 09:00:51 (none) local0.notice cgminer[11315]: tty_init 1
Jan 13 09:00:51 (none) local0.notice cgminer[11315]: Start A New Asic Response.Chain Id:[1]
Jan 13 09:00:52 (none) local0.notice cgminer[11315]: tty_init 2
Jan 13 09:00:52 (none) local0.notice cgminer[11315]: Start A New Asic Response.Chain Id:[2]
Jan 13 09:00:52 (none) local0.notice cgminer[11315]: tty_init 3
Jan 13 09:00:52 (none) local0.notice cgminer[11315]: Start A New Asic Response.Chain Id:[3]
Jan 13 09:00:52 (none) local0.notice cgminer[11315]: open device over
Jan 13 09:00:52 (none) local0.notice cgminer[11315]: send cmd to get chip address
Jan 13 09:00:54 (none) local0.notice cgminer[11315]: Chain 0 ASIC 72 !!!
Jan 13 09:00:54 (none) local0.notice cgminer[11315]: Chain 1 ASIC 72 !!!
Jan 13 09:00:54 (none) local0.notice cgminer[11315]: Chain 2 ASIC 72 !!!
Jan 13 09:00:54 (none) local0.notice cgminer[11315]: Chain 3 ASIC 72 !!!
Jan 13 09:00:54 (none) local0.notice cgminer[11315]: addrInterval = '3'
Jan 13 09:00:54 (none) local0.notice cgminer[11315]: software_set_address: chain 0 has 72 ASIC, and addrInterval is 3
Jan 13 09:00:54 (none) local0.notice cgminer[11315]: Now Set [0] Chain Address
Jan 13 09:00:55 (none) local0.notice cgminer[11315]: software_set_address: chain 1 has 72 ASIC, and addrInterval is 3
Jan 13 09:00:55 (none) local0.notice cgminer[11315]: Now Set [1] Chain Address
Jan 13 09:00:56 (none) local0.notice cgminer[11315]: software_set_address: chain 2 has 72 ASIC, and addrInterval is 3
Jan 13 09:00:56 (none) local0.notice cgminer[11315]: Now Set [2] Chain Address
Jan 13 09:00:57 (none) local0.notice cgminer[11315]: software_set_address: chain 3 has 72 ASIC, and addrInterval is 3
Jan 13 09:00:57 (none) local0.notice cgminer[11315]: Now Set [3] Chain Address
Jan 13 09:00:58 (none) local0.notice cgminer[11315]: frequency = '394'
Jan 13 09:00:58 (none) local0.notice cgminer[11315]: dev.timeout = 19
Jan 13 09:00:58 (none) local0.notice cgminer[11315]: opt_bitmain_L3_core_temp : 2
Jan 13 09:01:01 (none) local0.notice cgminer[11315]: send cmd to open block
Jan 13 09:01:04 (none) local0.err cgminer[11315]: low hashrate detection trigger: 476.037734 Mh/s
Jan 13 09:01:04 (none) local0.warn cgminer[11315]: Pool 3 stratum+tcp://litecoinpool.org:3333 alive, testing stability
Jan 13 09:01:04 (none) local0.warn cgminer[11315]: Switching to pool 3 stratum+tcp://litecoinpool.org:3333
Jan 13 09:01:04 (none) local0.info cgminer[11315]: Send extranonce.subscribe for stratum pool 2
Jan 13 09:01:04 (none) local0.warn cgminer[11315]: Pool 2 stratum+tcp://scrypt.eu.nicehash.com:3333 alive, testing stability
Jan 13 09:01:04 (none) local0.warn cgminer[11315]: Switching to pool 2 stratum+tcp://scrypt.eu.nicehash.com:3333
Jan 13 09:01:05 (none) local0.warn cgminer[11315]: Pool 1 stratum+tcp://hub.miningpoolhub.com:17001 alive, testing stability
Jan 13 09:01:05 (none) local0.warn cgminer[11315]: Switching to pool 1 stratum+tcp://hub.miningpoolhub.com:17001
Jan 13 09:01:05 (none) local0.warn cgminer[11315]: Pool 0 stratum+tcp://prohashing.com:3333 alive, testing stability
Jan 13 09:01:05 (none) local0.warn cgminer[11315]: Switching to pool 0 stratum+tcp://prohashing.com:3333
Jan 13 09:01:10 (none) local0.warn cgminer[11315]: API running in IP access mode on port 4028 (15)
Jan 13 09:05:41 (none) local0.warn cgminer[11315]: Switching to pool 3 stratum+tcp://litecoinpool.org:3333
Jan 13 09:07:31 (none) local0.warn cgminer[11315]: Switching to pool 0 stratum+tcp://prohashing.com:3333

The daily option for devfee did not work. After start it mines to dev. When the options "Automatic Reboot on low hashrate" and "Automatic Reboot on high number of ASIC failures" are selected the miner will mine more then the daily fee time.


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: blissz on January 13, 2018, 09:28:08 AM
Same here. Moreover the Miner Status page shows no entries.

can you make a screen shot?

http://i64.tinypic.com/2ir6vdj.jpg

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: 238776k/238776k available, 23368k 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.000357] Calibrating delay loop... 545.07 BogoMIPS (lpj=531968)
[    0.015438] pid_max: default: 32768 minimum: 301
[    0.015667] Security Framework initialized
[    0.015762] Mount-cache hash table entries: 512
[    0.024595] Initializing cgroup subsys cpuacct
[    0.024628] Initializing cgroup subsys memory
[    0.024693] Initializing cgroup subsys blkio
[    0.024829] CPU: Testing write buffer coherency: ok
[    0.025407] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[    0.025482] Setting up static identity map for 0x8038c820 - 0x8038c86c
[    0.026804] Brought up 1 CPUs
[    0.026827] SMP: Total of 1 processors activated (545.07 BogoMIPS).
[    0.028119] devtmpfs: initialized
[    0.092469] pinctrl core: initialized pinctrl subsystem
[    0.092682] rstctl core: initialized rstctl subsystem
[    0.093176] regulator-dummy: no parameters
[    0.093739] NET: Registered protocol family 16
[    0.094441] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.104111] pinctrl-single 44e10800.pinmux: prop pinctrl-0 index 0 invalid phandle
[    0.104293] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[    0.105376] platform 49000000.edma: alias fck already exists
[    0.105410] platform 49000000.edma: alias fck already exists
[    0.105437] platform 49000000.edma: alias fck already exists
[    0.106593] gpiochip_add: registered GPIOs 0 to 31 on device: gpio
[    0.106777] OMAP GPIO hardware version 0.1
[    0.108192] gpiochip_add: registered GPIOs 32 to 63 on device: gpio
[    0.109516] gpiochip_add: registered GPIOs 64 to 95 on device: gpio
[    0.110834] gpiochip_add: registered GPIOs 96 to 127 on device: gpio
[    0.111465] of_get_named_gpio_flags exited with status 52
[    0.111498] gpio-rctrl rstctl.3: loaded OK
[    0.116594] omap-gpmc 50000000.gpmc: GPMC revision 6.0
[    0.119807] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.121996] cpsw.0: No hwaddr in dt. Using b0:d5:cc:ac:bf:36 from efuse
[    0.122028] cpsw.1: No hwaddr in dt. Using b0:d5:cc:ac:bf:38 from efuse
[    0.137596] 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.150258] vmmcsd_fixed: 3300 mV
[    0.153377] SCSI subsystem initialized
[    0.153827] usbcore: registered new interface driver usbfs
[    0.153941] usbcore: registered new interface driver hub
[    0.154282] usbcore: registered new device driver usb
[    0.156399] omap_i2c 4819c000.i2c: bus 0 rev0.11 at 100 kHz
[    0.156432] omap_i2c 4819c000.i2c: unable to select pin group
[    0.156625] media: Linux media interface: v0.10
[    0.156719] 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.157572] Advanced Linux Sound Architecture Driver Initialized.
[    0.158755] Switching to clocksource gp_timer
[    0.176783] NET: Registered protocol family 2
[    0.177772] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[    0.177861] TCP bind hash table entries: 2048 (order: 3, 40960 bytes)
[    0.177951] TCP: Hash tables configured (established 2048 bind 2048)
[    0.178042] TCP: reno registered
[    0.178069] UDP hash table entries: 256 (order: 1, 12288 bytes)
[    0.178115] UDP-Lite hash table entries: 256 (order: 1, 12288 bytes)
[    0.178609] NET: Registered protocol family 1
[    0.179198] RPC: Registered named UNIX socket transport module.
[    0.179218] RPC: Registered udp transport module.
[    0.179231] RPC: Registered tcp transport module.
[    0.179245] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.179632] Trying to unpack rootfs image as initramfs...
[    1.937204] Freeing initrd memory: 12140K
[    1.937893] CPU PMU: probing PMU on CPU 0
[    1.937928] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available
[    1.938548] omap2_mbox_probe: platform not supported
[    1.942421] VFS: Disk quotas dquot_6.5.2
[    1.942660] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.943967] NFS: Registering the id_resolver key type
[    1.944124] Key type id_resolver registered
[    1.944143] Key type id_legacy registered
[    1.944211] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    1.944651] msgmni has been set to 490
[    1.947452] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[    1.947478] io scheduler noop registered
[    1.947494] io scheduler deadline registered
[    1.947551] io scheduler cfq registered (default)
[    1.951494] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    1.954104] omap_uart 44e09000.serial: did not get pins for uart0 error: -19
[    1.954382] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88) is a OMAP UART0
[    2.615278] console [ttyO0] enabled
[    2.619862] 48022000.serial: ttyO1 at MMIO 0x48022000 (irq = 89) is a OMAP UART1
[    2.628506] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 90) is a OMAP UART2
[    2.637157] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 61) is a OMAP UART4
[    2.645820] 481aa000.serial: ttyO5 at MMIO 0x481aa000 (irq = 62) is a OMAP UART5
[    2.654805] [drm] Initialized drm 1.1.0 20060810
[    2.673474] brd: module loaded
[    2.683730] loop: module loaded
[    2.687919] bone-capemgr bone_capemgr.8: Failed to find baseboard eeprom node
[    2.697853] nand_get_flash_type: 2c,da against 2c,da
[    2.703387] ONFI param page 0 valid
[    2.707060] ONFI flash detected
[    2.710382] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron MT29F2G08ABAEAWP), 256MiB, page size: 2048, OOB size: 64
[    2.722296] omap2-nand: detected x8 NAND flash
[    2.726961] nand: using OMAP_ECC_BCH8_CODE_HW ECC scheme
[    2.732544] omap2-nand: using custom ecc layout
[    2.737391] 10 ofpart partitions found on MTD device omap2-nand.0
[    2.743786] Creating 10 MTD partitions on "omap2-nand.0":
[    2.749464] 0x000000000000-0x000000020000 : "spl"
[    2.756244] 0x000000020000-0x000000040000 : "spl_backup1"
[    2.763713] 0x000000040000-0x000000060000 : "spl_backup2"
[    2.771126] 0x000000060000-0x000000080000 : "spl_backup3"
[    2.778540] 0x000000080000-0x000000240000 : "u-boot"
[    2.786795] 0x000000240000-0x000000260000 : "bootenv"
[    2.793735] 0x000000260000-0x000000280000 : "fdt"
[    2.800358] 0x000000280000-0x000000780000 : "kernel"
[    2.811394] 0x000000800000-0x000001c00000 : "root"
[    2.834927] 0x000001c00000-0x000003000000 : "config"
[    2.858726] OneNAND driver initializing
[    2.864489] usbcore: registered new interface driver asix
[    2.870307] usbcore: registered new interface driver cdc_ether
[    2.876553] usbcore: registered new interface driver smsc95xx
[    2.882672] usbcore: registered new interface driver net1080
[    2.888698] usbcore: registered new interface driver cdc_subset
[    2.894995] usbcore: registered new interface driver zaurus
[    2.901004] usbcore: registered new interface driver cdc_ncm
[    2.907742] usbcore: registered new interface driver cdc_acm
[    2.913703] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    2.922084] Initializing USB Mass Storage driver...
[    2.927326] usbcore: registered new interface driver usb-storage
[    2.933628] USB Mass Storage support registered.
[    2.938672] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
[    2.945390] musb-hdrc musb-hdrc.0.auto: pdev->id = 0
[    2.950634] musb-hdrc musb-hdrc.0.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK
[    2.959404] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    2.959427] musb-hdrc: MHDRC RTL version 2.0
[    2.959442] musb-hdrc: setup fifo_mode 4
[    2.959470] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    2.959652] musb-hdrc musb-hdrc.0.auto: *** mode=3
[    2.964691] musb-hdrc musb-hdrc.0.auto: *** power=250
[    2.970703] musb-hdrc musb-hdrc.1.auto: pdev->id = 1
[    2.975951] musb-hdrc musb-hdrc.1.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK
[    2.984721] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    2.984742] musb-hdrc: MHDRC RTL version 2.0
[    2.984756] musb-hdrc: setup fifo_mode 4
[    2.984778] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    2.984921] musb-hdrc musb-hdrc.1.auto: *** mode=1
[    2.989965] musb-hdrc musb-hdrc.1.auto: *** power=250
[    2.995274] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[    3.001897] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 1
[    3.010156] musb-hdrc musb-hdrc.1.auto: supports USB remote wakeup
[    3.010260] usb usb1: default language 0x0409
[    3.010319] usb usb1: udev 1, busnum 1, minor = 0
[    3.010342] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    3.017470] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.025042] usb usb1: Product: MUSB HDRC host driver
[    3.030257] usb usb1: Manufacturer: Linux 3.8.13 musb-hcd
[    3.035925] usb usb1: SerialNumber: musb-hdrc.1.auto
[    3.041931] usb usb1: usb_probe_device
[    3.041959] usb usb1: configuration #1 chosen from 1 choice
[    3.042023] usb usb1: adding 1-0:1.0 (config #1, interface 0)
[    3.042224] hub 1-0:1.0: usb_probe_interface
[    3.042246] hub 1-0:1.0: usb_probe_interface - got id
[    3.042273] hub 1-0:1.0: USB hub found
[    3.046271] hub 1-0:1.0: 1 port detected
[    3.050409] hub 1-0:1.0: standalone hub
[    3.050429] hub 1-0:1.0: individual port power switching
[    3.050448] hub 1-0:1.0: no over-current protection
[    3.050465] hub 1-0:1.0: Single TT
[    3.050487] hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns)
[    3.050506] hub 1-0:1.0: power on to power good time: 10ms
[    3.050561] hub 1-0:1.0: local power source is good
[    3.050674] hub 1-0:1.0: enabling power on all ports
[    3.051789] mousedev: PS/2 mouse device common for all mice
[    3.059739] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0
[    3.067230] 44e3e000.rtc: already running
[    3.071735] i2c /dev entries driver
[    3.076745] pps_ldisc: PPS line discipline registered
[    3.082231] Driver for 1-wire Dallas network protocol.
[    3.089491] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[    3.097054] cpuidle: using governor ladder
[    3.101381] cpuidle: using governor menu
[    3.105959] of_get_named_gpio_flags exited with status 6
[    3.105978] of_get_named_gpio_flags: can't parse gpios property
[    3.105994] of_get_named_gpio_flags: can't parse gpios property
[    3.106031] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' failed
[    3.113253] omap_hsmmc mmc.4: Failed to get rstctl; not using any
[    3.120102] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25
[    3.127320] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24
[    3.134645] mmc.4 supply vmmc_aux not found, using dummy regulator
[    3.141630] omap_hsmmc mmc.4: pins are not configured from the driver
[    3.151167] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
[    3.175080] of_get_named_gpio_flags exited with status -517
[    3.175146] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[    3.182923] ledtrig-cpu: registered to indicate activity on CPUs
[    3.189695] edma-dma-engine edma-dma-engine.0: allocated channel for 0:36
[    3.196892] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
[    3.205057] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
[    3.211354] edma-dma-engine edma-dma-engine.0: allocated channel for 0:5
[    3.218536] edma-dma-engine edma-dma-engine.0: allocated channel for 0:6
[    3.230796] usbcore: registered new interface driver usbhid
[    3.236715] usbhid: USB HID core driver
[    3.243632] TCP: cubic registered
[    3.247157] Initializing XFRM netlink socket
[    3.251737] NET: Registered protocol family 17
[    3.256594] NET: Registered protocol family 15
[    3.261466] Key type dns_resolver registered
[    3.266115] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    3.274231] ThumbEE CPU extension supported.
[    3.278743] Registering SWP/SWPB emulation handler
[    3.284757] registered taskstats version 1
[    3.291381] of_get_named_gpio_flags exited with status -517
[    3.291456] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[    3.348367] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[    3.354782] davinci_mdio 4a101000.mdio: detected phy mask fffffffe
[    3.369338] libphy: 4a101000.mdio: probed
[    3.373660] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
[    3.383897] Detected MACID = b0:d5:cc:ac:bf:36
[    3.388580] cpsw 4a100000.ethernet: NAPI disabled
[    3.393970] of_get_named_gpio_flags exited with status -517
[    3.394037] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[    3.402766] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[    3.412052] cpu0 supply cpu0 not found, using dummy regulator
[    3.418542] cpufreq_cpu0: failed to scale voltage up: -22
[    3.424364] cpufreq_cpu0: failed to scale voltage up: -22
[    3.437140] ALSA device list:
[    3.440373]   No soundcards found.
[    3.444922] Freeing init memory: 264K
[    3.448972] Failed to execute /init
[    4.521946] 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.
[    6.111067] net eth0: initializing cpsw version 1.12 (0)
[    6.119979] net eth0: phy found : id is : 0x7c0f1
[    6.125399] libphy: PHY 4a101000.mdio:01 not found
[    6.130596] net eth0: phy 4a101000.mdio:01 not found on slave 1
[   10.266852] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
Jan 13 08:34:39 (none) local0.err cgminer: Miner compile time: Fri Jan 12 19:41:57 CST 2018 type: Antminer L3+ Blissz v1.0
Jan 13 08:34:39 (none) local0.warn cgminer: Started cgminer 4.10.0
Jan 13 08:34:39 (none) local0.notice cgminer[361]:  detected at /sys/class/gpio/gpio51/value  chain 0
Jan 13 08:34:39 (none) local0.notice cgminer[361]:  detected at /sys/class/gpio/gpio48/value  chain 1
Jan 13 08:34:39 (none) local0.notice cgminer[361]:  detected at /sys/class/gpio/gpio47/value  chain 2
Jan 13 08:34:39 (none) local0.notice cgminer[361]:  detected at /sys/class/gpio/gpio44/value  chain 3
Jan 13 08:34:39 (none) local0.notice cgminer[361]: detect total chain num 4
Jan 13 08:34:39 (none) local0.notice cgminer[361]: i2c init ok
Jan 13 08:34:50 (none) local0.notice cgminer[361]: in tty_init
Jan 13 08:34:50 (none) local0.notice cgminer[361]: tty_init 0
Jan 13 08:34:50 (none) local0.notice cgminer[361]: Start A New Asic Response.Chain Id:[0]
Jan 13 08:34:51 (none) local0.notice cgminer[361]: tty_init 1
Jan 13 08:34:51 (none) local0.notice cgminer[361]: Start A New Asic Response.Chain Id:[1]
Jan 13 08:34:51 (none) local0.notice cgminer[361]: tty_init 2
Jan 13 08:34:51 (none) local0.notice cgminer[361]: Start A New Asic Response.Chain Id:[2]
Jan 13 08:34:51 (none) local0.notice cgminer[361]: tty_init 3
Jan 13 08:34:51 (none) local0.notice cgminer[361]: Start A New Asic Response.Chain Id:[3]
Jan 13 08:34:51 (none) local0.notice cgminer[361]: open device over
Jan 13 08:34:51 (none) local0.notice cgminer[361]: send cmd to get chip address
Jan 13 08:34:53 (none) local0.notice cgminer[361]: Chain 0 ASIC 72 !!!
Jan 13 08:34:53 (none) local0.notice cgminer[361]: Chain 1 ASIC 72 !!!
Jan 13 08:34:53 (none) local0.notice cgminer[361]: Chain 2 ASIC 72 !!!
Jan 13 08:34:53 (none) local0.notice cgminer[361]: Chain 3 ASIC 72 !!!
Jan 13 08:34:53 (none) local0.notice cgminer[361]: addrInterval = '3'
Jan 13 08:34:53 (none) local0.notice cgminer[361]: software_set_address: chain 0 has 72 ASIC, and addrInterval is 3
Jan 13 08:34:53 (none) local0.notice cgminer[361]: Now Set [0] Chain Address
Jan 13 08:34:54 (none) local0.notice cgminer[361]: software_set_address: chain 1 has 72 ASIC, and addrInterval is 3
Jan 13 08:34:54 (none) local0.notice cgminer[361]: Now Set [1] Chain Address
Jan 13 08:34:55 (none) local0.notice cgminer[361]: software_set_address: chain 2 has 72 ASIC, and addrInterval is 3
Jan 13 08:34:55 (none) local0.notice cgminer[361]: Now Set [2] Chain Address
Jan 13 08:34:56 (none) local0.notice cgminer[361]: software_set_address: chain 3 has 72 ASIC, and addrInterval is 3
Jan 13 08:34:56 (none) local0.notice cgminer[361]: Now Set [3] Chain Address
Jan 13 08:34:57 (none) local0.notice cgminer[361]: frequency = '394'
Jan 13 08:34:57 (none) local0.notice cgminer[361]: dev.timeout = 19
Jan 13 08:34:57 (none) local0.notice cgminer[361]: opt_bitmain_L3_core_temp : 2
Jan 13 08:35:01 (none) local0.notice cgminer[361]: send cmd to open block
Jan 13 08:35:03 (none) local0.err cgminer[361]: low hashrate detection trigger: 476.037734 Mh/s
Jan 13 08:35:03 (none) local0.warn cgminer[361]: Failed to resolve (?wrong URL) stratum+tcp://:(null)
Jan 13 08:35:04 (none) local0.warn cgminer[361]: Pool 2 stratum+tcp://hub.miningpoolhub.com:17001 alive, testing stability
Jan 13 08:35:04 (none) local0.warn cgminer[361]: Switching to pool 2 stratum+tcp://hub.miningpoolhub.com:17001
Jan 13 08:35:04 (none) local0.warn cgminer[361]: Pool 1 stratum+tcp://prohashing.com:3333 alive, testing stability
Jan 13 08:35:04 (none) local0.warn cgminer[361]: Switching to pool 1 stratum+tcp://prohashing.com:3333
Jan 13 08:35:08 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:09 (none) local0.warn cgminer[361]: API running in IP access mode on port 4028 (15)
Jan 13 08:35:13 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:18 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:23 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:28 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:33 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:38 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:43 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:48 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:53 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:58 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:03 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:08 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:13 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:18 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:23 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:28 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:33 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:38 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:43 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:48 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:53 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:58 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:03 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:08 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:13 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:18 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:23 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:28 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:33 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:38 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:43 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:48 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:53 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:58 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:03 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:08 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:13 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:18 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:24 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:29 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:34 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:39 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:44 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:49 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:54 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:59 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:04 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:09 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:14 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:19 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:24 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:29 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:34 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:39 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:40 (none) local0.warn cgminer[361]: Switching to pool 3 stratum+tcp://litecoinpool.org:3333
Jan 13 08:39:44 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:49 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:54 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:59 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:04 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:09 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:14 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:19 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:24 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:29 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:34 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:39 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:44 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:49 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:54 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:59 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:41:04 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:41:09 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:41:14 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:41:19 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:41:24 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:41:29 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:41:31 (none) local0.err cgminer: Miner compile time: Fri Jan 12 19:41:57 CST 2018 type: Antminer L3+ Blissz v1.0
Jan 13 08:41:31 (none) local0.warn cgminer: Started cgminer 4.10.0
Jan 13 08:41:31 (none) local0.notice cgminer[31059]:  detected at /sys/class/gpio/gpio51/value  chain 0
Jan 13 08:41:31 (none) local0.notice cgminer[31059]:  detected at /sys/class/gpio/gpio48/value  chain 1
Jan 13 08:41:31 (none) local0.notice cgminer[31059]:  detected at /sys/class/gpio/gpio47/value  chain 2
Jan 13 08:41:31 (none) local0.notice cgminer[31059]:  detected at /sys/class/gpio/gpio44/value  chain 3
Jan 13 08:41:31 (none) local0.notice cgminer[31059]: detect total chain num 4
Jan 13 08:41:31 (none) local0.notice cgminer[31059]: i2c init ok
Jan 13 08:41:42 (none) local0.notice cgminer[31059]: in tty_init
Jan 13 08:41:42 (none) local0.notice cgminer[31059]: tty_init 0
Jan 13 08:41:42 (none) local0.notice cgminer[31059]: Start A New Asic Response.Chain Id:[0]
Jan 13 08:41:42 (none) local0.notice cgminer[31059]: tty_init 1
Jan 13 08:41:42 (none) local0.notice cgminer[31059]: Start A New Asic Response.Chain Id:[1]
Jan 13 08:41:43 (none) local0.notice cgminer[31059]: tty_init 2
Jan 13 08:41:43 (none) local0.notice cgminer[31059]: Start A New Asic Response.Chain Id:[2]
Jan 13 08:41:43 (none) local0.notice cgminer[31059]: tty_init 3
Jan 13 08:41:43 (none) local0.notice cgminer[31059]: Start A New Asic Response.Chain Id:[3]
Jan 13 08:41:43 (none) local0.notice cgminer[31059]: open device over
Jan 13 08:41:43 (none) local0.notice cgminer[31059]: send cmd to get chip address
Jan 13 08:41:45 (none) local0.notice cgminer[31059]: Chain 0 ASIC 72 !!!
Jan 13 08:41:45 (none) local0.notice cgminer[31059]: Chain 1 ASIC 72 !!!
Jan 13 08:41:45 (none) local0.notice cgminer[31059]: Chain 2 ASIC 72 !!!
Jan 13 08:41:45 (none) local0.notice cgminer[31059]: Chain 3 ASIC 72 !!!
Jan 13 08:41:45 (none) local0.notice cgminer[31059]: addrInterval = '3'
Jan 13 08:41:45 (none) local0.notice cgminer[31059]: software_set_address: chain 0 has 72 ASIC, and addrInterval is 3
Jan 13 08:41:45 (none) local0.notice cgminer[31059]: Now Set [0] Chain Address
Jan 13 08:41:46 (none) local0.notice cgminer[31059]: software_set_address: chain 1 has 72 ASIC, and addrInterval is 3
Jan 13 08:41:46 (none) local0.notice cgminer[31059]: Now Set [1] Chain Address
Jan 13 08:41:47 (none) local0.notice cgminer[31059]: software_set_address: chain 2 has 72 ASIC, and addrInterval is 3
Jan 13 08:41:47 (none) local0.notice cgminer[31059]: Now Set [2] Chain Address
Jan 13 08:41:48 (none) local0.notice cgminer[31059]: software_set_address: chain 3 has 72 ASIC, and addrInterval is 3
Jan 13 08:41:48 (none) local0.notice cgminer[31059]: Now Set [3] Chain Address
Jan 13 08:41:49 (none) local0.notice cgminer[31059]: frequency = '394'
Jan 13 08:41:49 (none) local0.notice cgminer[31059]: dev.timeout = 19
Jan 13 08:41:49 (none) local0.notice cgminer[31059]: opt_bitmain_L3_core_temp : 2
Jan 13 08:41:52 (none) local0.notice cgminer[31059]: send cmd to open block
Jan 13 08:41:55 (none) local0.err cgminer[31059]: low hashrate detection trigger: 476.037734 Mh/s
Jan 13 08:41:55 (none) local0.warn cgminer[31059]: Pool 3 stratum+tcp://litecoinpool.org:3333 alive, testing stability
Jan 13 08:41:55 (none) local0.warn cgminer[31059]: Switching to pool 3 stratum+tcp://litecoinpool.org:3333
Jan 13 08:41:55 (none) local0.info cgminer[31059]: Send extranonce.subscribe for stratum pool 2
Jan 13 08:41:55 (none) local0.warn cgminer[31059]: Pool 2 stratum+tcp://scrypt.eu.nicehash.com:3333 alive, testing stability
Jan 13 08:41:55 (none) local0.warn cgminer[31059]: Switching to pool 2 stratum+tcp://scrypt.eu.nicehash.com:3333
Jan 13 08:41:56 (none) local0.warn cgminer[31059]: Pool 1 stratum+tcp://hub.miningpoolhub.com:17001 alive, testing stability
Jan 13 08:41:56 (none) local0.warn cgminer[31059]: Switching to pool 1 stratum+tcp://hub.miningpoolhub.com:17001
Jan 13 08:41:56 (none) local0.warn cgminer[31059]: Pool 0 stratum+tcp://prohashing.com:3333 alive, testing stability
Jan 13 08:41:56 (none) local0.warn cgminer[31059]: Switching to pool 0 stratum+tcp://prohashing.com:3333
Jan 13 08:42:01 (none) local0.warn cgminer[31059]: API running in IP access mode on port 4028 (19)
Jan 13 08:46:32 (none) local0.warn cgminer[31059]: Switching to pool 3 stratum+tcp://litecoinpool.org:3333
Jan 13 09:00:40 (none) local0.err cgminer: Miner compile time: Fri Jan 12 19:41:57 CST 2018 type: Antminer L3+ Blissz v1.0
Jan 13 09:00:40 (none) local0.warn cgminer: Started cgminer 4.10.0
Jan 13 09:00:40 (none) local0.notice cgminer[11315]:  detected at /sys/class/gpio/gpio51/value  chain 0
Jan 13 09:00:40 (none) local0.notice cgminer[11315]:  detected at /sys/class/gpio/gpio48/value  chain 1
Jan 13 09:00:40 (none) local0.notice cgminer[11315]:  detected at /sys/class/gpio/gpio47/value  chain 2
Jan 13 09:00:40 (none) local0.notice cgminer[11315]:  detected at /sys/class/gpio/gpio44/value  chain 3
Jan 13 09:00:40 (none) local0.notice cgminer[11315]: detect total chain num 4
Jan 13 09:00:40 (none) local0.notice cgminer[11315]: i2c init ok
Jan 13 09:00:51 (none) local0.notice cgminer[11315]: in tty_init
Jan 13 09:00:51 (none) local0.notice cgminer[11315]: tty_init 0
Jan 13 09:00:51 (none) local0.notice cgminer[11315]: Start A New Asic Response.Chain Id:[0]
Jan 13 09:00:51 (none) local0.notice cgminer[11315]: tty_init 1
Jan 13 09:00:51 (none) local0.notice cgminer[11315]: Start A New Asic Response.Chain Id:[1]
Jan 13 09:00:52 (none) local0.notice cgminer[11315]: tty_init 2
Jan 13 09:00:52 (none) local0.notice cgminer[11315]: Start A New Asic Response.Chain Id:[2]
Jan 13 09:00:52 (none) local0.notice cgminer[11315]: tty_init 3
Jan 13 09:00:52 (none) local0.notice cgminer[11315]: Start A New Asic Response.Chain Id:[3]
Jan 13 09:00:52 (none) local0.notice cgminer[11315]: open device over
Jan 13 09:00:52 (none) local0.notice cgminer[11315]: send cmd to get chip address
Jan 13 09:00:54 (none) local0.notice cgminer[11315]: Chain 0 ASIC 72 !!!
Jan 13 09:00:54 (none) local0.notice cgminer[11315]: Chain 1 ASIC 72 !!!
Jan 13 09:00:54 (none) local0.notice cgminer[11315]: Chain 2 ASIC 72 !!!
Jan 13 09:00:54 (none) local0.notice cgminer[11315]: Chain 3 ASIC 72 !!!
Jan 13 09:00:54 (none) local0.notice cgminer[11315]: addrInterval = '3'
Jan 13 09:00:54 (none) local0.notice cgminer[11315]: software_set_address: chain 0 has 72 ASIC, and addrInterval is 3
Jan 13 09:00:54 (none) local0.notice cgminer[11315]: Now Set [0] Chain Address
Jan 13 09:00:55 (none) local0.notice cgminer[11315]: software_set_address: chain 1 has 72 ASIC, and addrInterval is 3
Jan 13 09:00:55 (none) local0.notice cgminer[11315]: Now Set [1] Chain Address
Jan 13 09:00:56 (none) local0.notice cgminer[11315]: software_set_address: chain 2 has 72 ASIC, and addrInterval is 3
Jan 13 09:00:56 (none) local0.notice cgminer[11315]: Now Set [2] Chain Address
Jan 13 09:00:57 (none) local0.notice cgminer[11315]: software_set_address: chain 3 has 72 ASIC, and addrInterval is 3
Jan 13 09:00:57 (none) local0.notice cgminer[11315]: Now Set [3] Chain Address
Jan 13 09:00:58 (none) local0.notice cgminer[11315]: frequency = '394'
Jan 13 09:00:58 (none) local0.notice cgminer[11315]: dev.timeout = 19
Jan 13 09:00:58 (none) local0.notice cgminer[11315]: opt_bitmain_L3_core_temp : 2
Jan 13 09:01:01 (none) local0.notice cgminer[11315]: send cmd to open block
Jan 13 09:01:04 (none) local0.err cgminer[11315]: low hashrate detection trigger: 476.037734 Mh/s
Jan 13 09:01:04 (none) local0.warn cgminer[11315]: Pool 3 stratum+tcp://litecoinpool.org:3333 alive, testing stability
Jan 13 09:01:04 (none) local0.warn cgminer[11315]: Switching to pool 3 stratum+tcp://litecoinpool.org:3333
Jan 13 09:01:04 (none) local0.info cgminer[11315]: Send extranonce.subscribe for stratum pool 2
Jan 13 09:01:04 (none) local0.warn cgminer[11315]: Pool 2 stratum+tcp://scrypt.eu.nicehash.com:3333 alive, testing stability
Jan 13 09:01:04 (none) local0.warn cgminer[11315]: Switching to pool 2 stratum+tcp://scrypt.eu.nicehash.com:3333
Jan 13 09:01:05 (none) local0.warn cgminer[11315]: Pool 1 stratum+tcp://hub.miningpoolhub.com:17001 alive, testing stability
Jan 13 09:01:05 (none) local0.warn cgminer[11315]: Switching to pool 1 stratum+tcp://hub.miningpoolhub.com:17001
Jan 13 09:01:05 (none) local0.warn cgminer[11315]: Pool 0 stratum+tcp://prohashing.com:3333 alive, testing stability
Jan 13 09:01:05 (none) local0.warn cgminer[11315]: Switching to pool 0 stratum+tcp://prohashing.com:3333
Jan 13 09:01:10 (none) local0.warn cgminer[11315]: API running in IP access mode on port 4028 (15)
Jan 13 09:05:41 (none) local0.warn cgminer[11315]: Switching to pool 3 stratum+tcp://litecoinpool.org:3333
Jan 13 09:07:31 (none) local0.warn cgminer[11315]: Switching to pool 0 stratum+tcp://prohashing.com:3333

The daily option for devfee did not work. After start it mines to dev. When the options "Automatic Reboot on low hashrate" and "Automatic Reboot on high number of ASIC failures" are selected the miner will mine more then the daily fee time.

The daily dev fee mining also starts mining on the devfee pool after 5 minutes, but then for a longer period (21 minutes) before switching to your own pools for a full day. Some like this better as it won't switch pools every two hours. Don't use this option when you're still tuning your miner.

About the empty status page: can you press ctrl + f5 / empty your browser cache. it didn't load the new webpage correctly. I will put that in the flash instructions


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: gigidinizza on January 13, 2018, 09:29:38 AM
Hello, the result look great, there is not much info about the silent mode, I mean how silent is that ? anyone measured it and compared it ? Any impact on the hash rate ?
I'm talking about an apartment environment for exemple...


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: blissz on January 13, 2018, 09:36:03 AM
Hello, the result look great, there is not much info about the silent mode, I mean how silent is that ? anyone measured it and compared it ? Any impact on the hash rate ?
I'm talking about an apartment environment for exemple...

You're welcome. It will adjust the fan speed automatically like the stock firmware, but runs them at a bit lower speed compared to the stock firmware. Your miner will run a bit hotter if you leave it at the default voltage, so if you're living in an apartment I would set the voltage to the lowest setting, fan speed "silent auto" and then see at what frequency your boards can run. (somewhere between 350 and 425)
That will give a real silent experience compared to the stock firmware. (at least half the loudness I would say, but maybe here can do a comparison?)
If you do so you can still run it around 500Mh/s (this differs from unit to unit) but with less noise / less power usage.
I hope this helps


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: Michi_A on January 13, 2018, 09:38:06 AM
Same here. Moreover the Miner Status page shows no entries.

can you make a screen shot?

http://i64.tinypic.com/2ir6vdj.jpg

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: 238776k/238776k available, 23368k 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.000357] Calibrating delay loop... 545.07 BogoMIPS (lpj=531968)
[    0.015438] pid_max: default: 32768 minimum: 301
[    0.015667] Security Framework initialized
[    0.015762] Mount-cache hash table entries: 512
[    0.024595] Initializing cgroup subsys cpuacct
[    0.024628] Initializing cgroup subsys memory
[    0.024693] Initializing cgroup subsys blkio
[    0.024829] CPU: Testing write buffer coherency: ok
[    0.025407] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[    0.025482] Setting up static identity map for 0x8038c820 - 0x8038c86c
[    0.026804] Brought up 1 CPUs
[    0.026827] SMP: Total of 1 processors activated (545.07 BogoMIPS).
[    0.028119] devtmpfs: initialized
[    0.092469] pinctrl core: initialized pinctrl subsystem
[    0.092682] rstctl core: initialized rstctl subsystem
[    0.093176] regulator-dummy: no parameters
[    0.093739] NET: Registered protocol family 16
[    0.094441] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.104111] pinctrl-single 44e10800.pinmux: prop pinctrl-0 index 0 invalid phandle
[    0.104293] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[    0.105376] platform 49000000.edma: alias fck already exists
[    0.105410] platform 49000000.edma: alias fck already exists
[    0.105437] platform 49000000.edma: alias fck already exists
[    0.106593] gpiochip_add: registered GPIOs 0 to 31 on device: gpio
[    0.106777] OMAP GPIO hardware version 0.1
[    0.108192] gpiochip_add: registered GPIOs 32 to 63 on device: gpio
[    0.109516] gpiochip_add: registered GPIOs 64 to 95 on device: gpio
[    0.110834] gpiochip_add: registered GPIOs 96 to 127 on device: gpio
[    0.111465] of_get_named_gpio_flags exited with status 52
[    0.111498] gpio-rctrl rstctl.3: loaded OK
[    0.116594] omap-gpmc 50000000.gpmc: GPMC revision 6.0
[    0.119807] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.121996] cpsw.0: No hwaddr in dt. Using b0:d5:cc:ac:bf:36 from efuse
[    0.122028] cpsw.1: No hwaddr in dt. Using b0:d5:cc:ac:bf:38 from efuse
[    0.137596] 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.150258] vmmcsd_fixed: 3300 mV
[    0.153377] SCSI subsystem initialized
[    0.153827] usbcore: registered new interface driver usbfs
[    0.153941] usbcore: registered new interface driver hub
[    0.154282] usbcore: registered new device driver usb
[    0.156399] omap_i2c 4819c000.i2c: bus 0 rev0.11 at 100 kHz
[    0.156432] omap_i2c 4819c000.i2c: unable to select pin group
[    0.156625] media: Linux media interface: v0.10
[    0.156719] 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.157572] Advanced Linux Sound Architecture Driver Initialized.
[    0.158755] Switching to clocksource gp_timer
[    0.176783] NET: Registered protocol family 2
[    0.177772] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[    0.177861] TCP bind hash table entries: 2048 (order: 3, 40960 bytes)
[    0.177951] TCP: Hash tables configured (established 2048 bind 2048)
[    0.178042] TCP: reno registered
[    0.178069] UDP hash table entries: 256 (order: 1, 12288 bytes)
[    0.178115] UDP-Lite hash table entries: 256 (order: 1, 12288 bytes)
[    0.178609] NET: Registered protocol family 1
[    0.179198] RPC: Registered named UNIX socket transport module.
[    0.179218] RPC: Registered udp transport module.
[    0.179231] RPC: Registered tcp transport module.
[    0.179245] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.179632] Trying to unpack rootfs image as initramfs...
[    1.937204] Freeing initrd memory: 12140K
[    1.937893] CPU PMU: probing PMU on CPU 0
[    1.937928] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available
[    1.938548] omap2_mbox_probe: platform not supported
[    1.942421] VFS: Disk quotas dquot_6.5.2
[    1.942660] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.943967] NFS: Registering the id_resolver key type
[    1.944124] Key type id_resolver registered
[    1.944143] Key type id_legacy registered
[    1.944211] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    1.944651] msgmni has been set to 490
[    1.947452] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[    1.947478] io scheduler noop registered
[    1.947494] io scheduler deadline registered
[    1.947551] io scheduler cfq registered (default)
[    1.951494] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    1.954104] omap_uart 44e09000.serial: did not get pins for uart0 error: -19
[    1.954382] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88) is a OMAP UART0
[    2.615278] console [ttyO0] enabled
[    2.619862] 48022000.serial: ttyO1 at MMIO 0x48022000 (irq = 89) is a OMAP UART1
[    2.628506] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 90) is a OMAP UART2
[    2.637157] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 61) is a OMAP UART4
[    2.645820] 481aa000.serial: ttyO5 at MMIO 0x481aa000 (irq = 62) is a OMAP UART5
[    2.654805] [drm] Initialized drm 1.1.0 20060810
[    2.673474] brd: module loaded
[    2.683730] loop: module loaded
[    2.687919] bone-capemgr bone_capemgr.8: Failed to find baseboard eeprom node
[    2.697853] nand_get_flash_type: 2c,da against 2c,da
[    2.703387] ONFI param page 0 valid
[    2.707060] ONFI flash detected
[    2.710382] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron MT29F2G08ABAEAWP), 256MiB, page size: 2048, OOB size: 64
[    2.722296] omap2-nand: detected x8 NAND flash
[    2.726961] nand: using OMAP_ECC_BCH8_CODE_HW ECC scheme
[    2.732544] omap2-nand: using custom ecc layout
[    2.737391] 10 ofpart partitions found on MTD device omap2-nand.0
[    2.743786] Creating 10 MTD partitions on "omap2-nand.0":
[    2.749464] 0x000000000000-0x000000020000 : "spl"
[    2.756244] 0x000000020000-0x000000040000 : "spl_backup1"
[    2.763713] 0x000000040000-0x000000060000 : "spl_backup2"
[    2.771126] 0x000000060000-0x000000080000 : "spl_backup3"
[    2.778540] 0x000000080000-0x000000240000 : "u-boot"
[    2.786795] 0x000000240000-0x000000260000 : "bootenv"
[    2.793735] 0x000000260000-0x000000280000 : "fdt"
[    2.800358] 0x000000280000-0x000000780000 : "kernel"
[    2.811394] 0x000000800000-0x000001c00000 : "root"
[    2.834927] 0x000001c00000-0x000003000000 : "config"
[    2.858726] OneNAND driver initializing
[    2.864489] usbcore: registered new interface driver asix
[    2.870307] usbcore: registered new interface driver cdc_ether
[    2.876553] usbcore: registered new interface driver smsc95xx
[    2.882672] usbcore: registered new interface driver net1080
[    2.888698] usbcore: registered new interface driver cdc_subset
[    2.894995] usbcore: registered new interface driver zaurus
[    2.901004] usbcore: registered new interface driver cdc_ncm
[    2.907742] usbcore: registered new interface driver cdc_acm
[    2.913703] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    2.922084] Initializing USB Mass Storage driver...
[    2.927326] usbcore: registered new interface driver usb-storage
[    2.933628] USB Mass Storage support registered.
[    2.938672] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
[    2.945390] musb-hdrc musb-hdrc.0.auto: pdev->id = 0
[    2.950634] musb-hdrc musb-hdrc.0.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK
[    2.959404] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    2.959427] musb-hdrc: MHDRC RTL version 2.0
[    2.959442] musb-hdrc: setup fifo_mode 4
[    2.959470] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    2.959652] musb-hdrc musb-hdrc.0.auto: *** mode=3
[    2.964691] musb-hdrc musb-hdrc.0.auto: *** power=250
[    2.970703] musb-hdrc musb-hdrc.1.auto: pdev->id = 1
[    2.975951] musb-hdrc musb-hdrc.1.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK
[    2.984721] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    2.984742] musb-hdrc: MHDRC RTL version 2.0
[    2.984756] musb-hdrc: setup fifo_mode 4
[    2.984778] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    2.984921] musb-hdrc musb-hdrc.1.auto: *** mode=1
[    2.989965] musb-hdrc musb-hdrc.1.auto: *** power=250
[    2.995274] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[    3.001897] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 1
[    3.010156] musb-hdrc musb-hdrc.1.auto: supports USB remote wakeup
[    3.010260] usb usb1: default language 0x0409
[    3.010319] usb usb1: udev 1, busnum 1, minor = 0
[    3.010342] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    3.017470] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.025042] usb usb1: Product: MUSB HDRC host driver
[    3.030257] usb usb1: Manufacturer: Linux 3.8.13 musb-hcd
[    3.035925] usb usb1: SerialNumber: musb-hdrc.1.auto
[    3.041931] usb usb1: usb_probe_device
[    3.041959] usb usb1: configuration #1 chosen from 1 choice
[    3.042023] usb usb1: adding 1-0:1.0 (config #1, interface 0)
[    3.042224] hub 1-0:1.0: usb_probe_interface
[    3.042246] hub 1-0:1.0: usb_probe_interface - got id
[    3.042273] hub 1-0:1.0: USB hub found
[    3.046271] hub 1-0:1.0: 1 port detected
[    3.050409] hub 1-0:1.0: standalone hub
[    3.050429] hub 1-0:1.0: individual port power switching
[    3.050448] hub 1-0:1.0: no over-current protection
[    3.050465] hub 1-0:1.0: Single TT
[    3.050487] hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns)
[    3.050506] hub 1-0:1.0: power on to power good time: 10ms
[    3.050561] hub 1-0:1.0: local power source is good
[    3.050674] hub 1-0:1.0: enabling power on all ports
[    3.051789] mousedev: PS/2 mouse device common for all mice
[    3.059739] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0
[    3.067230] 44e3e000.rtc: already running
[    3.071735] i2c /dev entries driver
[    3.076745] pps_ldisc: PPS line discipline registered
[    3.082231] Driver for 1-wire Dallas network protocol.
[    3.089491] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[    3.097054] cpuidle: using governor ladder
[    3.101381] cpuidle: using governor menu
[    3.105959] of_get_named_gpio_flags exited with status 6
[    3.105978] of_get_named_gpio_flags: can't parse gpios property
[    3.105994] of_get_named_gpio_flags: can't parse gpios property
[    3.106031] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' failed
[    3.113253] omap_hsmmc mmc.4: Failed to get rstctl; not using any
[    3.120102] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25
[    3.127320] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24
[    3.134645] mmc.4 supply vmmc_aux not found, using dummy regulator
[    3.141630] omap_hsmmc mmc.4: pins are not configured from the driver
[    3.151167] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
[    3.175080] of_get_named_gpio_flags exited with status -517
[    3.175146] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[    3.182923] ledtrig-cpu: registered to indicate activity on CPUs
[    3.189695] edma-dma-engine edma-dma-engine.0: allocated channel for 0:36
[    3.196892] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
[    3.205057] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
[    3.211354] edma-dma-engine edma-dma-engine.0: allocated channel for 0:5
[    3.218536] edma-dma-engine edma-dma-engine.0: allocated channel for 0:6
[    3.230796] usbcore: registered new interface driver usbhid
[    3.236715] usbhid: USB HID core driver
[    3.243632] TCP: cubic registered
[    3.247157] Initializing XFRM netlink socket
[    3.251737] NET: Registered protocol family 17
[    3.256594] NET: Registered protocol family 15
[    3.261466] Key type dns_resolver registered
[    3.266115] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    3.274231] ThumbEE CPU extension supported.
[    3.278743] Registering SWP/SWPB emulation handler
[    3.284757] registered taskstats version 1
[    3.291381] of_get_named_gpio_flags exited with status -517
[    3.291456] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[    3.348367] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[    3.354782] davinci_mdio 4a101000.mdio: detected phy mask fffffffe
[    3.369338] libphy: 4a101000.mdio: probed
[    3.373660] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
[    3.383897] Detected MACID = b0:d5:cc:ac:bf:36
[    3.388580] cpsw 4a100000.ethernet: NAPI disabled
[    3.393970] of_get_named_gpio_flags exited with status -517
[    3.394037] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[    3.402766] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[    3.412052] cpu0 supply cpu0 not found, using dummy regulator
[    3.418542] cpufreq_cpu0: failed to scale voltage up: -22
[    3.424364] cpufreq_cpu0: failed to scale voltage up: -22
[    3.437140] ALSA device list:
[    3.440373]   No soundcards found.
[    3.444922] Freeing init memory: 264K
[    3.448972] Failed to execute /init
[    4.521946] 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.
[    6.111067] net eth0: initializing cpsw version 1.12 (0)
[    6.119979] net eth0: phy found : id is : 0x7c0f1
[    6.125399] libphy: PHY 4a101000.mdio:01 not found
[    6.130596] net eth0: phy 4a101000.mdio:01 not found on slave 1
[   10.266852] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
Jan 13 08:34:39 (none) local0.err cgminer: Miner compile time: Fri Jan 12 19:41:57 CST 2018 type: Antminer L3+ Blissz v1.0
Jan 13 08:34:39 (none) local0.warn cgminer: Started cgminer 4.10.0
Jan 13 08:34:39 (none) local0.notice cgminer[361]:  detected at /sys/class/gpio/gpio51/value  chain 0
Jan 13 08:34:39 (none) local0.notice cgminer[361]:  detected at /sys/class/gpio/gpio48/value  chain 1
Jan 13 08:34:39 (none) local0.notice cgminer[361]:  detected at /sys/class/gpio/gpio47/value  chain 2
Jan 13 08:34:39 (none) local0.notice cgminer[361]:  detected at /sys/class/gpio/gpio44/value  chain 3
Jan 13 08:34:39 (none) local0.notice cgminer[361]: detect total chain num 4
Jan 13 08:34:39 (none) local0.notice cgminer[361]: i2c init ok
Jan 13 08:34:50 (none) local0.notice cgminer[361]: in tty_init
Jan 13 08:34:50 (none) local0.notice cgminer[361]: tty_init 0
Jan 13 08:34:50 (none) local0.notice cgminer[361]: Start A New Asic Response.Chain Id:[0]
Jan 13 08:34:51 (none) local0.notice cgminer[361]: tty_init 1
Jan 13 08:34:51 (none) local0.notice cgminer[361]: Start A New Asic Response.Chain Id:[1]
Jan 13 08:34:51 (none) local0.notice cgminer[361]: tty_init 2
Jan 13 08:34:51 (none) local0.notice cgminer[361]: Start A New Asic Response.Chain Id:[2]
Jan 13 08:34:51 (none) local0.notice cgminer[361]: tty_init 3
Jan 13 08:34:51 (none) local0.notice cgminer[361]: Start A New Asic Response.Chain Id:[3]
Jan 13 08:34:51 (none) local0.notice cgminer[361]: open device over
Jan 13 08:34:51 (none) local0.notice cgminer[361]: send cmd to get chip address
Jan 13 08:34:53 (none) local0.notice cgminer[361]: Chain 0 ASIC 72 !!!
Jan 13 08:34:53 (none) local0.notice cgminer[361]: Chain 1 ASIC 72 !!!
Jan 13 08:34:53 (none) local0.notice cgminer[361]: Chain 2 ASIC 72 !!!
Jan 13 08:34:53 (none) local0.notice cgminer[361]: Chain 3 ASIC 72 !!!
Jan 13 08:34:53 (none) local0.notice cgminer[361]: addrInterval = '3'
Jan 13 08:34:53 (none) local0.notice cgminer[361]: software_set_address: chain 0 has 72 ASIC, and addrInterval is 3
Jan 13 08:34:53 (none) local0.notice cgminer[361]: Now Set [0] Chain Address
Jan 13 08:34:54 (none) local0.notice cgminer[361]: software_set_address: chain 1 has 72 ASIC, and addrInterval is 3
Jan 13 08:34:54 (none) local0.notice cgminer[361]: Now Set [1] Chain Address
Jan 13 08:34:55 (none) local0.notice cgminer[361]: software_set_address: chain 2 has 72 ASIC, and addrInterval is 3
Jan 13 08:34:55 (none) local0.notice cgminer[361]: Now Set [2] Chain Address
Jan 13 08:34:56 (none) local0.notice cgminer[361]: software_set_address: chain 3 has 72 ASIC, and addrInterval is 3
Jan 13 08:34:56 (none) local0.notice cgminer[361]: Now Set [3] Chain Address
Jan 13 08:34:57 (none) local0.notice cgminer[361]: frequency = '394'
Jan 13 08:34:57 (none) local0.notice cgminer[361]: dev.timeout = 19
Jan 13 08:34:57 (none) local0.notice cgminer[361]: opt_bitmain_L3_core_temp : 2
Jan 13 08:35:01 (none) local0.notice cgminer[361]: send cmd to open block
Jan 13 08:35:03 (none) local0.err cgminer[361]: low hashrate detection trigger: 476.037734 Mh/s
Jan 13 08:35:03 (none) local0.warn cgminer[361]: Failed to resolve (?wrong URL) stratum+tcp://:(null)
Jan 13 08:35:04 (none) local0.warn cgminer[361]: Pool 2 stratum+tcp://hub.miningpoolhub.com:17001 alive, testing stability
Jan 13 08:35:04 (none) local0.warn cgminer[361]: Switching to pool 2 stratum+tcp://hub.miningpoolhub.com:17001
Jan 13 08:35:04 (none) local0.warn cgminer[361]: Pool 1 stratum+tcp://prohashing.com:3333 alive, testing stability
Jan 13 08:35:04 (none) local0.warn cgminer[361]: Switching to pool 1 stratum+tcp://prohashing.com:3333
Jan 13 08:35:08 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:09 (none) local0.warn cgminer[361]: API running in IP access mode on port 4028 (15)
Jan 13 08:35:13 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:18 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:23 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:28 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:33 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:38 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:43 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:48 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:53 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:35:58 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:03 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:08 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:13 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:18 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:23 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:28 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:33 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:38 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:43 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:48 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:53 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:36:58 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:03 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:08 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:13 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:18 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:23 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:28 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:33 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:38 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:43 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:48 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:53 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:37:58 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:03 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:08 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:13 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:18 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:24 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:29 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:34 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:39 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:44 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:49 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:54 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:38:59 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:04 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:09 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:14 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:19 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:24 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:29 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:34 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:39 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:40 (none) local0.warn cgminer[361]: Switching to pool 3 stratum+tcp://litecoinpool.org:3333
Jan 13 08:39:44 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:49 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:54 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:39:59 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:04 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:09 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:14 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:19 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:24 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:29 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:34 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:39 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:44 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:49 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:54 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:40:59 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:41:04 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:41:09 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:41:14 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:41:19 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:41:24 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:41:29 (none) local0.info cgminer[361]: Failed to getaddrinfo for stratum+tcp://:(null)
Jan 13 08:41:31 (none) local0.err cgminer: Miner compile time: Fri Jan 12 19:41:57 CST 2018 type: Antminer L3+ Blissz v1.0
Jan 13 08:41:31 (none) local0.warn cgminer: Started cgminer 4.10.0
Jan 13 08:41:31 (none) local0.notice cgminer[31059]:  detected at /sys/class/gpio/gpio51/value  chain 0
Jan 13 08:41:31 (none) local0.notice cgminer[31059]:  detected at /sys/class/gpio/gpio48/value  chain 1
Jan 13 08:41:31 (none) local0.notice cgminer[31059]:  detected at /sys/class/gpio/gpio47/value  chain 2
Jan 13 08:41:31 (none) local0.notice cgminer[31059]:  detected at /sys/class/gpio/gpio44/value  chain 3
Jan 13 08:41:31 (none) local0.notice cgminer[31059]: detect total chain num 4
Jan 13 08:41:31 (none) local0.notice cgminer[31059]: i2c init ok
Jan 13 08:41:42 (none) local0.notice cgminer[31059]: in tty_init
Jan 13 08:41:42 (none) local0.notice cgminer[31059]: tty_init 0
Jan 13 08:41:42 (none) local0.notice cgminer[31059]: Start A New Asic Response.Chain Id:[0]
Jan 13 08:41:42 (none) local0.notice cgminer[31059]: tty_init 1
Jan 13 08:41:42 (none) local0.notice cgminer[31059]: Start A New Asic Response.Chain Id:[1]
Jan 13 08:41:43 (none) local0.notice cgminer[31059]: tty_init 2
Jan 13 08:41:43 (none) local0.notice cgminer[31059]: Start A New Asic Response.Chain Id:[2]
Jan 13 08:41:43 (none) local0.notice cgminer[31059]: tty_init 3
Jan 13 08:41:43 (none) local0.notice cgminer[31059]: Start A New Asic Response.Chain Id:[3]
Jan 13 08:41:43 (none) local0.notice cgminer[31059]: open device over
Jan 13 08:41:43 (none) local0.notice cgminer[31059]: send cmd to get chip address
Jan 13 08:41:45 (none) local0.notice cgminer[31059]: Chain 0 ASIC 72 !!!
Jan 13 08:41:45 (none) local0.notice cgminer[31059]: Chain 1 ASIC 72 !!!
Jan 13 08:41:45 (none) local0.notice cgminer[31059]: Chain 2 ASIC 72 !!!
Jan 13 08:41:45 (none) local0.notice cgminer[31059]: Chain 3 ASIC 72 !!!
Jan 13 08:41:45 (none) local0.notice cgminer[31059]: addrInterval = '3'
Jan 13 08:41:45 (none) local0.notice cgminer[31059]: software_set_address: chain 0 has 72 ASIC, and addrInterval is 3
Jan 13 08:41:45 (none) local0.notice cgminer[31059]: Now Set [0] Chain Address
Jan 13 08:41:46 (none) local0.notice cgminer[31059]: software_set_address: chain 1 has 72 ASIC, and addrInterval is 3
Jan 13 08:41:46 (none) local0.notice cgminer[31059]: Now Set [1] Chain Address
Jan 13 08:41:47 (none) local0.notice cgminer[31059]: software_set_address: chain 2 has 72 ASIC, and addrInterval is 3
Jan 13 08:41:47 (none) local0.notice cgminer[31059]: Now Set [2] Chain Address
Jan 13 08:41:48 (none) local0.notice cgminer[31059]: software_set_address: chain 3 has 72 ASIC, and addrInterval is 3
Jan 13 08:41:48 (none) local0.notice cgminer[31059]: Now Set [3] Chain Address
Jan 13 08:41:49 (none) local0.notice cgminer[31059]: frequency = '394'
Jan 13 08:41:49 (none) local0.notice cgminer[31059]: dev.timeout = 19
Jan 13 08:41:49 (none) local0.notice cgminer[31059]: opt_bitmain_L3_core_temp : 2
Jan 13 08:41:52 (none) local0.notice cgminer[31059]: send cmd to open block
Jan 13 08:41:55 (none) local0.err cgminer[31059]: low hashrate detection trigger: 476.037734 Mh/s
Jan 13 08:41:55 (none) local0.warn cgminer[31059]: Pool 3 stratum+tcp://litecoinpool.org:3333 alive, testing stability
Jan 13 08:41:55 (none) local0.warn cgminer[31059]: Switching to pool 3 stratum+tcp://litecoinpool.org:3333
Jan 13 08:41:55 (none) local0.info cgminer[31059]: Send extranonce.subscribe for stratum pool 2
Jan 13 08:41:55 (none) local0.warn cgminer[31059]: Pool 2 stratum+tcp://scrypt.eu.nicehash.com:3333 alive, testing stability
Jan 13 08:41:55 (none) local0.warn cgminer[31059]: Switching to pool 2 stratum+tcp://scrypt.eu.nicehash.com:3333
Jan 13 08:41:56 (none) local0.warn cgminer[31059]: Pool 1 stratum+tcp://hub.miningpoolhub.com:17001 alive, testing stability
Jan 13 08:41:56 (none) local0.warn cgminer[31059]: Switching to pool 1 stratum+tcp://hub.miningpoolhub.com:17001
Jan 13 08:41:56 (none) local0.warn cgminer[31059]: Pool 0 stratum+tcp://prohashing.com:3333 alive, testing stability
Jan 13 08:41:56 (none) local0.warn cgminer[31059]: Switching to pool 0 stratum+tcp://prohashing.com:3333
Jan 13 08:42:01 (none) local0.warn cgminer[31059]: API running in IP access mode on port 4028 (19)
Jan 13 08:46:32 (none) local0.warn cgminer[31059]: Switching to pool 3 stratum+tcp://litecoinpool.org:3333
Jan 13 09:00:40 (none) local0.err cgminer: Miner compile time: Fri Jan 12 19:41:57 CST 2018 type: Antminer L3+ Blissz v1.0
Jan 13 09:00:40 (none) local0.warn cgminer: Started cgminer 4.10.0
Jan 13 09:00:40 (none) local0.notice cgminer[11315]:  detected at /sys/class/gpio/gpio51/value  chain 0
Jan 13 09:00:40 (none) local0.notice cgminer[11315]:  detected at /sys/class/gpio/gpio48/value  chain 1
Jan 13 09:00:40 (none) local0.notice cgminer[11315]:  detected at /sys/class/gpio/gpio47/value  chain 2
Jan 13 09:00:40 (none) local0.notice cgminer[11315]:  detected at /sys/class/gpio/gpio44/value  chain 3
Jan 13 09:00:40 (none) local0.notice cgminer[11315]: detect total chain num 4
Jan 13 09:00:40 (none) local0.notice cgminer[11315]: i2c init ok
Jan 13 09:00:51 (none) local0.notice cgminer[11315]: in tty_init
Jan 13 09:00:51 (none) local0.notice cgminer[11315]: tty_init 0
Jan 13 09:00:51 (none) local0.notice cgminer[11315]: Start A New Asic Response.Chain Id:[0]
Jan 13 09:00:51 (none) local0.notice cgminer[11315]: tty_init 1
Jan 13 09:00:51 (none) local0.notice cgminer[11315]: Start A New Asic Response.Chain Id:[1]
Jan 13 09:00:52 (none) local0.notice cgminer[11315]: tty_init 2
Jan 13 09:00:52 (none) local0.notice cgminer[11315]: Start A New Asic Response.Chain Id:[2]
Jan 13 09:00:52 (none) local0.notice cgminer[11315]: tty_init 3
Jan 13 09:00:52 (none) local0.notice cgminer[11315]: Start A New Asic Response.Chain Id:[3]
Jan 13 09:00:52 (none) local0.notice cgminer[11315]: open device over
Jan 13 09:00:52 (none) local0.notice cgminer[11315]: send cmd to get chip address
Jan 13 09:00:54 (none) local0.notice cgminer[11315]: Chain 0 ASIC 72 !!!
Jan 13 09:00:54 (none) local0.notice cgminer[11315]: Chain 1 ASIC 72 !!!
Jan 13 09:00:54 (none) local0.notice cgminer[11315]: Chain 2 ASIC 72 !!!
Jan 13 09:00:54 (none) local0.notice cgminer[11315]: Chain 3 ASIC 72 !!!
Jan 13 09:00:54 (none) local0.notice cgminer[11315]: addrInterval = '3'
Jan 13 09:00:54 (none) local0.notice cgminer[11315]: software_set_address: chain 0 has 72 ASIC, and addrInterval is 3
Jan 13 09:00:54 (none) local0.notice cgminer[11315]: Now Set [0] Chain Address
Jan 13 09:00:55 (none) local0.notice cgminer[11315]: software_set_address: chain 1 has 72 ASIC, and addrInterval is 3
Jan 13 09:00:55 (none) local0.notice cgminer[11315]: Now Set [1] Chain Address
Jan 13 09:00:56 (none) local0.notice cgminer[11315]: software_set_address: chain 2 has 72 ASIC, and addrInterval is 3
Jan 13 09:00:56 (none) local0.notice cgminer[11315]: Now Set [2] Chain Address
Jan 13 09:00:57 (none) local0.notice cgminer[11315]: software_set_address: chain 3 has 72 ASIC, and addrInterval is 3
Jan 13 09:00:57 (none) local0.notice cgminer[11315]: Now Set [3] Chain Address
Jan 13 09:00:58 (none) local0.notice cgminer[11315]: frequency = '394'
Jan 13 09:00:58 (none) local0.notice cgminer[11315]: dev.timeout = 19
Jan 13 09:00:58 (none) local0.notice cgminer[11315]: opt_bitmain_L3_core_temp : 2
Jan 13 09:01:01 (none) local0.notice cgminer[11315]: send cmd to open block
Jan 13 09:01:04 (none) local0.err cgminer[11315]: low hashrate detection trigger: 476.037734 Mh/s
Jan 13 09:01:04 (none) local0.warn cgminer[11315]: Pool 3 stratum+tcp://litecoinpool.org:3333 alive, testing stability
Jan 13 09:01:04 (none) local0.warn cgminer[11315]: Switching to pool 3 stratum+tcp://litecoinpool.org:3333
Jan 13 09:01:04 (none) local0.info cgminer[11315]: Send extranonce.subscribe for stratum pool 2
Jan 13 09:01:04 (none) local0.warn cgminer[11315]: Pool 2 stratum+tcp://scrypt.eu.nicehash.com:3333 alive, testing stability
Jan 13 09:01:04 (none) local0.warn cgminer[11315]: Switching to pool 2 stratum+tcp://scrypt.eu.nicehash.com:3333
Jan 13 09:01:05 (none) local0.warn cgminer[11315]: Pool 1 stratum+tcp://hub.miningpoolhub.com:17001 alive, testing stability
Jan 13 09:01:05 (none) local0.warn cgminer[11315]: Switching to pool 1 stratum+tcp://hub.miningpoolhub.com:17001
Jan 13 09:01:05 (none) local0.warn cgminer[11315]: Pool 0 stratum+tcp://prohashing.com:3333 alive, testing stability
Jan 13 09:01:05 (none) local0.warn cgminer[11315]: Switching to pool 0 stratum+tcp://prohashing.com:3333
Jan 13 09:01:10 (none) local0.warn cgminer[11315]: API running in IP access mode on port 4028 (15)
Jan 13 09:05:41 (none) local0.warn cgminer[11315]: Switching to pool 3 stratum+tcp://litecoinpool.org:3333
Jan 13 09:07:31 (none) local0.warn cgminer[11315]: Switching to pool 0 stratum+tcp://prohashing.com:3333

The daily option for devfee did not work. After start it mines to dev. When the options "Automatic Reboot on low hashrate" and "Automatic Reboot on high number of ASIC failures" are selected the miner will mine more then the daily fee time.

The daily dev fee mining also starts mining on the devfee pool after 5 minutes, but then for a longer period (21 minutes) before switching to your own pools for a full day. Some like this better as it won't switch pools every two hours. Don't use this option when you're still tuning your miner.

About the empty status page: can you press ctrl + f5 / empty your browser cache. it didn't load the new webpage correctly. I will put that in the flash instructions

Did not work. I tried it on 3 different Browser. Same problem on all my L3+.


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: blissz on January 13, 2018, 09:46:47 AM
...
Did not work. I tried it on 3 different Browser. Same problem on all my L3+.

Make sure you clear your browser cache and try again with firefox or chrome.
I am not sure if it's related, but there is also something wrong with one of your pools...
Failed to resolve (?wrong URL) stratum+tcp://:(null)
Can you PM your pool settings? Then I will try them on my unit. Or can you try to set them all three to the same value and see which pool is causing these errors? Thank you!


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: mendo on January 13, 2018, 10:05:27 AM
hello.

i flasyhed the firmware over 4x L3+.
same batch.

all previously had your Beta firmware, with 0 problem.

i had to phisically switch off and then off to have them working.

but......  when i set up frequency and voltage
ie
freq 400
voltage LOWEST

following problem appear (see attached picture)

https://drive.google.com/file/d/1LIkHR5cFsP87Slh6qOLkDsbyfDfQKrp8/view?usp=sharing

if i set back the frequency to 350 and voltage to 13.....
EVERYTHING GETS BACK TO NORMAL.

so, i will load again the previous beta firmware, which had no problem.

i f i can make any further test, you are welcome to ask.

your product is great.

Andrea


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: Michi_A on January 13, 2018, 10:09:55 AM
...
Did not work. I tried it on 3 different Browser. Same problem on all my L3+.

Make sure you clear your browser cache and try again with firefox or chrome.
I am not sure if it's related, but there is also something wrong with one of your pools...
Failed to resolve (?wrong URL) stratum+tcp://:(null)
Can you PM your pool settings? Then I will try them on my unit. Or can you try to set them all three to the same value and see which pool is causing these errors? Thank you!

After a reboot:

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: 238776k/238776k available, 23368k 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.000355] Calibrating delay loop... 545.07 BogoMIPS (lpj=531968)
[    0.015439] pid_max: default: 32768 minimum: 301
[    0.015669] Security Framework initialized
[    0.015765] Mount-cache hash table entries: 512
[    0.024591] Initializing cgroup subsys cpuacct
[    0.024623] Initializing cgroup subsys memory
[    0.024686] Initializing cgroup subsys blkio
[    0.024824] CPU: Testing write buffer coherency: ok
[    0.025402] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[    0.025478] Setting up static identity map for 0x8038c820 - 0x8038c86c
[    0.026815] Brought up 1 CPUs
[    0.026839] SMP: Total of 1 processors activated (545.07 BogoMIPS).
[    0.028131] devtmpfs: initialized
[    0.092532] pinctrl core: initialized pinctrl subsystem
[    0.092748] rstctl core: initialized rstctl subsystem
[    0.093242] regulator-dummy: no parameters
[    0.093812] NET: Registered protocol family 16
[    0.094516] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.104183] pinctrl-single 44e10800.pinmux: prop pinctrl-0 index 0 invalid phandle
[    0.104367] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[    0.105458] platform 49000000.edma: alias fck already exists
[    0.105492] platform 49000000.edma: alias fck already exists
[    0.105521] platform 49000000.edma: alias fck already exists
[    0.106668] gpiochip_add: registered GPIOs 0 to 31 on device: gpio
[    0.106850] OMAP GPIO hardware version 0.1
[    0.108262] gpiochip_add: registered GPIOs 32 to 63 on device: gpio
[    0.109584] gpiochip_add: registered GPIOs 64 to 95 on device: gpio
[    0.110900] gpiochip_add: registered GPIOs 96 to 127 on device: gpio
[    0.111525] of_get_named_gpio_flags exited with status 52
[    0.111557] gpio-rctrl rstctl.3: loaded OK
[    0.116651] omap-gpmc 50000000.gpmc: GPMC revision 6.0
[    0.119868] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.122061] cpsw.0: No hwaddr in dt. Using b0:d5:cc:ac:bf:36 from efuse
[    0.122093] cpsw.1: No hwaddr in dt. Using b0:d5:cc:ac:bf:38 from efuse
[    0.137657] bio: create slab <bio-0> at 0
[    0.149790] edma-dma-engine edma-dma-engine.0: TI EDMA DMA engine driver
[    0.150029] of_get_named_gpio_flags: can't parse gpios property
[    0.150320] vmmcsd_fixed: 3300 mV
[    0.153431] SCSI subsystem initialized
[    0.153889] usbcore: registered new interface driver usbfs
[    0.154001] usbcore: registered new interface driver hub
[    0.154330] usbcore: registered new device driver usb
[    0.156432] omap_i2c 4819c000.i2c: bus 0 rev0.11 at 100 kHz
[    0.156466] omap_i2c 4819c000.i2c: unable to select pin group
[    0.156661] media: Linux media interface: v0.10
[    0.156756] Linux video capture interface: v2.00
[    0.156873] pps_core: LinuxPPS API ver. 1 registered
[    0.156889] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.157608] Advanced Linux Sound Architecture Driver Initialized.
[    0.158802] Switching to clocksource gp_timer
[    0.176830] NET: Registered protocol family 2
[    0.177822] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[    0.177911] TCP bind hash table entries: 2048 (order: 3, 40960 bytes)
[    0.178001] TCP: Hash tables configured (established 2048 bind 2048)
[    0.178092] TCP: reno registered
[    0.178119] UDP hash table entries: 256 (order: 1, 12288 bytes)
[    0.178164] UDP-Lite hash table entries: 256 (order: 1, 12288 bytes)
[    0.178659] NET: Registered protocol family 1
[    0.179247] RPC: Registered named UNIX socket transport module.
[    0.179268] RPC: Registered udp transport module.
[    0.179282] RPC: Registered tcp transport module.
[    0.179296] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.179687] Trying to unpack rootfs image as initramfs...
[    1.937268] Freeing initrd memory: 12140K
[    1.937956] CPU PMU: probing PMU on CPU 0
[    1.937989] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available
[    1.938603] omap2_mbox_probe: platform not supported
[    1.942481] VFS: Disk quotas dquot_6.5.2
[    1.942718] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.944022] NFS: Registering the id_resolver key type
[    1.944192] Key type id_resolver registered
[    1.944210] Key type id_legacy registered
[    1.944279] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    1.944715] msgmni has been set to 490
[    1.947509] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[    1.947536] io scheduler noop registered
[    1.947552] io scheduler deadline registered
[    1.947610] io scheduler cfq registered (default)
[    1.951540] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    1.954137] omap_uart 44e09000.serial: did not get pins for uart0 error: -19
[    1.954415] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88) is a OMAP UART0
[    2.615249] console [ttyO0] enabled
[    2.619779] 48022000.serial: ttyO1 at MMIO 0x48022000 (irq = 89) is a OMAP UART1
[    2.628473] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 90) is a OMAP UART2
[    2.637113] 481a8000.serial: ttyO4 at MMIO 0x481a8000 (irq = 61) is a OMAP UART4
[    2.645773] 481aa000.serial: ttyO5 at MMIO 0x481aa000 (irq = 62) is a OMAP UART5
[    2.654767] [drm] Initialized drm 1.1.0 20060810
[    2.673427] brd: module loaded
[    2.683666] loop: module loaded
[    2.687853] bone-capemgr bone_capemgr.8: Failed to find baseboard eeprom node
[    2.697791] nand_get_flash_type: 2c,da against 2c,da
[    2.703321] ONFI param page 0 valid
[    2.706995] ONFI flash detected
[    2.710315] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron MT29F2G08ABAEAWP), 256MiB, page size: 2048, OOB size: 64
[    2.722226] omap2-nand: detected x8 NAND flash
[    2.726891] nand: using OMAP_ECC_BCH8_CODE_HW ECC scheme
[    2.732474] omap2-nand: using custom ecc layout
[    2.737318] 10 ofpart partitions found on MTD device omap2-nand.0
[    2.743713] Creating 10 MTD partitions on "omap2-nand.0":
[    2.749389] 0x000000000000-0x000000020000 : "spl"
[    2.756175] 0x000000020000-0x000000040000 : "spl_backup1"
[    2.763637] 0x000000040000-0x000000060000 : "spl_backup2"
[    2.771043] 0x000000060000-0x000000080000 : "spl_backup3"
[    2.778457] 0x000000080000-0x000000240000 : "u-boot"
[    2.786718] 0x000000240000-0x000000260000 : "bootenv"
[    2.793617] 0x000000260000-0x000000280000 : "fdt"
[    2.800255] 0x000000280000-0x000000780000 : "kernel"
[    2.811272] 0x000000800000-0x000001c00000 : "root"
[    2.834802] 0x000001c00000-0x000003000000 : "config"
[    2.858610] OneNAND driver initializing
[    2.864354] usbcore: registered new interface driver asix
[    2.870168] usbcore: registered new interface driver cdc_ether
[    2.876410] usbcore: registered new interface driver smsc95xx
[    2.882526] usbcore: registered new interface driver net1080
[    2.888550] usbcore: registered new interface driver cdc_subset
[    2.894846] usbcore: registered new interface driver zaurus
[    2.900851] usbcore: registered new interface driver cdc_ncm
[    2.907626] usbcore: registered new interface driver cdc_acm
[    2.913585] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    2.921967] Initializing USB Mass Storage driver...
[    2.927208] usbcore: registered new interface driver usb-storage
[    2.933510] USB Mass Storage support registered.
[    2.938556] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
[    2.945274] musb-hdrc musb-hdrc.0.auto: pdev->id = 0
[    2.950517] musb-hdrc musb-hdrc.0.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK
[    2.959288] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    2.959309] musb-hdrc: MHDRC RTL version 2.0
[    2.959325] musb-hdrc: setup fifo_mode 4
[    2.959353] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    2.959502] musb-hdrc musb-hdrc.0.auto: *** mode=3
[    2.964547] musb-hdrc musb-hdrc.0.auto: *** power=250
[    2.970566] musb-hdrc musb-hdrc.1.auto: pdev->id = 1
[    2.975816] musb-hdrc musb-hdrc.1.auto: drivers/usb/musb/musb_dsps.c:468 dsps_musb_init: OK
[    2.984584] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    2.984605] musb-hdrc: MHDRC RTL version 2.0
[    2.984619] musb-hdrc: setup fifo_mode 4
[    2.984642] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    2.984781] musb-hdrc musb-hdrc.1.auto: *** mode=1
[    2.989824] musb-hdrc musb-hdrc.1.auto: *** power=250
[    2.995132] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[    3.001762] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 1
[    3.010021] musb-hdrc musb-hdrc.1.auto: supports USB remote wakeup
[    3.010126] usb usb1: default language 0x0409
[    3.010184] usb usb1: udev 1, busnum 1, minor = 0
[    3.010208] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    3.017338] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.024910] usb usb1: Product: MUSB HDRC host driver
[    3.030126] usb usb1: Manufacturer: Linux 3.8.13 musb-hcd
[    3.035793] usb usb1: SerialNumber: musb-hdrc.1.auto
[    3.041804] usb usb1: usb_probe_device
[    3.041831] usb usb1: configuration #1 chosen from 1 choice
[    3.041898] usb usb1: adding 1-0:1.0 (config #1, interface 0)
[    3.042099] hub 1-0:1.0: usb_probe_interface
[    3.042121] hub 1-0:1.0: usb_probe_interface - got id
[    3.042148] hub 1-0:1.0: USB hub found
[    3.046144] hub 1-0:1.0: 1 port detected
[    3.050283] hub 1-0:1.0: standalone hub
[    3.050303] hub 1-0:1.0: individual port power switching
[    3.050321] hub 1-0:1.0: no over-current protection
[    3.050339] hub 1-0:1.0: Single TT
[    3.050360] hub 1-0:1.0: TT requires at most 8 FS bit times (666 ns)
[    3.050379] hub 1-0:1.0: power on to power good time: 10ms
[    3.050434] hub 1-0:1.0: local power source is good
[    3.050548] hub 1-0:1.0: enabling power on all ports
[    3.051666] mousedev: PS/2 mouse device common for all mice
[    3.059612] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0
[    3.067133] 44e3e000.rtc: already running
[    3.071630] i2c /dev entries driver
[    3.076630] pps_ldisc: PPS line discipline registered
[    3.082116] Driver for 1-wire Dallas network protocol.
[    3.089341] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[    3.096907] cpuidle: using governor ladder
[    3.101238] cpuidle: using governor menu
[    3.105813] of_get_named_gpio_flags exited with status 6
[    3.105833] of_get_named_gpio_flags: can't parse gpios property
[    3.105849] of_get_named_gpio_flags: can't parse gpios property
[    3.105885] omap_hsmmc mmc.4: of_parse_phandle_with_args of 'reset' failed
[    3.113114] omap_hsmmc mmc.4: Failed to get rstctl; not using any
[    3.119976] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25
[    3.127184] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24
[    3.134512] mmc.4 supply vmmc_aux not found, using dummy regulator
[    3.141511] omap_hsmmc mmc.4: pins are not configured from the driver
[    3.151214] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
[    3.175134] of_get_named_gpio_flags exited with status -517
[    3.175204] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[    3.182978] ledtrig-cpu: registered to indicate activity on CPUs
[    3.189758] edma-dma-engine edma-dma-engine.0: allocated channel for 0:36
[    3.196953] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
[    3.205121] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
[    3.211407] edma-dma-engine edma-dma-engine.0: allocated channel for 0:5
[    3.218589] edma-dma-engine edma-dma-engine.0: allocated channel for 0:6
[    3.230859] usbcore: registered new interface driver usbhid
[    3.236778] usbhid: USB HID core driver
[    3.243679] TCP: cubic registered
[    3.247208] Initializing XFRM netlink socket
[    3.251788] NET: Registered protocol family 17
[    3.256642] NET: Registered protocol family 15
[    3.261490] Key type dns_resolver registered
[    3.266134] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    3.274250] ThumbEE CPU extension supported.
[    3.278760] Registering SWP/SWPB emulation handler
[    3.284771] registered taskstats version 1
[    3.291391] of_get_named_gpio_flags exited with status -517
[    3.291465] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[    3.348411] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[    3.354825] davinci_mdio 4a101000.mdio: detected phy mask fffffffe
[    3.369407] libphy: 4a101000.mdio: probed
[    3.373761] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720
[    3.383992] Detected MACID = b0:d5:cc:ac:bf:36
[    3.388676] cpsw 4a100000.ethernet: NAPI disabled
[    3.394067] of_get_named_gpio_flags exited with status -517
[    3.394133] platform gpio-leds.7: Driver leds-gpio requests probe deferral
[    3.402858] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[    3.412138] cpu0 supply cpu0 not found, using dummy regulator
[    3.418677] cpufreq_cpu0: failed to scale voltage up: -22
[    3.424519] cpufreq_cpu0: failed to scale voltage up: -22
[    3.437310] ALSA device list:
[    3.440547]   No soundcards found.
[    3.445090] Freeing init memory: 264K
[    3.449142] Failed to execute /init
[    4.516284] 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.
[    6.121910] net eth0: initializing cpsw version 1.12 (0)
[    6.130838] net eth0: phy found : id is : 0x7c0f1
[    6.136290] libphy: PHY 4a101000.mdio:01 not found
[    6.141494] net eth0: phy 4a101000.mdio:01 not found on slave 1
[   10.278621] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
Jan 13 10:02:03 (none) local0.err cgminer: Miner compile time: Fri Jan 12 19:41:57 CST 2018 type: Antminer L3+ Blissz v1.0
Jan 13 10:02:03 (none) local0.warn cgminer: Started cgminer 4.10.0
Jan 13 10:02:03 (none) local0.notice cgminer[361]:  detected at /sys/class/gpio/gpio51/value  chain 0
Jan 13 10:02:03 (none) local0.notice cgminer[361]:  detected at /sys/class/gpio/gpio48/value  chain 1
Jan 13 10:02:03 (none) local0.notice cgminer[361]:  detected at /sys/class/gpio/gpio47/value  chain 2
Jan 13 10:02:03 (none) local0.notice cgminer[361]:  detected at /sys/class/gpio/gpio44/value  chain 3
Jan 13 10:02:03 (none) local0.notice cgminer[361]: detect total chain num 4
Jan 13 10:02:03 (none) local0.notice cgminer[361]: i2c init ok
Jan 13 10:02:14 (none) local0.notice cgminer[361]: in tty_init
Jan 13 10:02:14 (none) local0.notice cgminer[361]: tty_init 0
Jan 13 10:02:14 (none) local0.notice cgminer[361]: Start A New Asic Response.Chain Id:[0]
Jan 13 10:02:15 (none) local0.notice cgminer[361]: tty_init 1
Jan 13 10:02:15 (none) local0.notice cgminer[361]: Start A New Asic Response.Chain Id:[1]
Jan 13 10:02:15 (none) local0.notice cgminer[361]: tty_init 2
Jan 13 10:02:15 (none) local0.notice cgminer[361]: Start A New Asic Response.Chain Id:[2]
Jan 13 10:02:15 (none) local0.notice cgminer[361]: tty_init 3
Jan 13 10:02:15 (none) local0.notice cgminer[361]: Start A New Asic Response.Chain Id:[3]
Jan 13 10:02:15 (none) local0.notice cgminer[361]: open device over
Jan 13 10:02:15 (none) local0.notice cgminer[361]: send cmd to get chip address
Jan 13 10:02:17 (none) local0.notice cgminer[361]: Chain 0 ASIC 72 !!!
Jan 13 10:02:17 (none) local0.notice cgminer[361]: Chain 1 ASIC 72 !!!
Jan 13 10:02:17 (none) local0.notice cgminer[361]: Chain 2 ASIC 72 !!!
Jan 13 10:02:17 (none) local0.notice cgminer[361]: Chain 3 ASIC 72 !!!
Jan 13 10:02:17 (none) local0.notice cgminer[361]: addrInterval = '3'
Jan 13 10:02:17 (none) local0.notice cgminer[361]: software_set_address: chain 0 has 72 ASIC, and addrInterval is 3
Jan 13 10:02:17 (none) local0.notice cgminer[361]: Now Set [0] Chain Address
Jan 13 10:02:18 (none) local0.notice cgminer[361]: software_set_address: chain 1 has 72 ASIC, and addrInterval is 3
Jan 13 10:02:18 (none) local0.notice cgminer[361]: Now Set [1] Chain Address
Jan 13 10:02:19 (none) local0.notice cgminer[361]: software_set_address: chain 2 has 72 ASIC, and addrInterval is 3
Jan 13 10:02:19 (none) local0.notice cgminer[361]: Now Set [2] Chain Address
Jan 13 10:02:20 (none) local0.notice cgminer[361]: software_set_address: chain 3 has 72 ASIC, and addrInterval is 3
Jan 13 10:02:20 (none) local0.notice cgminer[361]: Now Set [3] Chain Address
Jan 13 10:02:21 (none) local0.notice cgminer[361]: frequency = '397'
Jan 13 10:02:21 (none) local0.notice cgminer[361]: dev.timeout = 18
Jan 13 10:02:21 (none) local0.notice cgminer[361]: opt_bitmain_L3_core_temp : 2
Jan 13 10:02:25 (none) local0.notice cgminer[361]: send cmd to open block
Jan 13 10:02:27 (none) local0.err cgminer[361]: low hashrate detection trigger: 479.662387 Mh/s
Jan 13 10:02:27 (none) local0.warn cgminer[361]: Pool 3 stratum+tcp://litecoinpool.org:3333 alive, testing stability
Jan 13 10:02:27 (none) local0.warn cgminer[361]: Switching to pool 3 stratum+tcp://litecoinpool.org:3333
Jan 13 10:02:28 (none) local0.warn cgminer[361]: Pool 1 stratum+tcp://hub.miningpoolhub.com:17001 alive, testing stability
Jan 13 10:02:28 (none) local0.warn cgminer[361]: Switching to pool 1 stratum+tcp://hub.miningpoolhub.com:17001
Jan 13 10:02:28 (none) local0.info cgminer[361]: Send extranonce.subscribe for stratum pool 2
Jan 13 10:02:28 (none) local0.warn cgminer[361]: Pool 0 stratum+tcp://prohashing.com:3333 alive, testing stability
Jan 13 10:02:28 (none) local0.warn cgminer[361]: Switching to pool 0 stratum+tcp://prohashing.com:3333
Jan 13 10:02:33 (none) local0.warn cgminer[361]: API running in IP access mode on port 4028 (16)

I cleared the browser cache... still no info shown.

I think the wrong URL thing was your second dev pool.

*EDIT
Output of /cgi-bin/get_status_api.cgi
Code:
STATUS=S,When=1515838669,Code=11,Msg=Summary,Description=cgminer 4.10.0|SUMMARY,Elapsed=921,GHS 5s=519.35,GHS av=514.64,Found Blocks=0,Getworks=99,Accepted=93,Rejected=9,Hardware Errors=16,Utility=6.06,Discarded=624,Stale=0,Get Failures=0,Local Work=1120,Remote Failures=0,Network Blocks=72,Total MH=473841.0000,Work Utility=605376.63,Difficulty Accepted=8421376.00000000,Difficulty Rejected=868352.00000000,Difficulty Stale=0.00000000,Best Share=7495504,Device Hardware%=0.0002,Device Rejected%=9.3474,Pool Rejected%=9.3474,Pool Stale%=0.0000,Last getwork=1515838668|
STATUS=S,When=1515838669,Code=70,Msg=CGMiner stats,Description=cgminer 4.10.0|CGMiner=4.10.0,Miner=1.0.1.3,CompileTime=Fri Jan 12 19:41:57 CST 2018,Type=Antminer L3+ Blissz v1.0|STATS=0,ID=L30,Elapsed=921,Calls=0,Wait=0.000000,Max=0.000000,Min=99999999.000000,GHS 5s=519.351,GHS av=514.64,miner_count=4,frequency=397,frequency1=397,frequency2=397,frequency3=397,frequency4=397,volt1=lowest,volt2=lowest,volt3=lowest,volt4=lowest,fan_num=2,fan1=2778,fan2=2808,temp_num=4,temp1=52,temp2=51,temp3=50,temp4=49,temp2_1=56,temp2_2=57,temp2_3=55,temp2_4=54,temp31=0,temp32=0,temp33=0,temp34=0,temp4_1=0,temp4_2=0,temp4_3=0,temp4_4=0,temp_max=52,Device Hardware%=-0.0000,no_matching_work=16,chain_acn1=72,chain_acn2=72,chain_acn3=72,chain_acn4=72,chain_acs1= oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo,chain_acs2= oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo,chain_acs3= oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo,chain_acs4= oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo,chain_hw1=2,chain_hw2=0,chain_hw3=14,chain_hw4=0,chain_rate1=130.42,chain_rate2=129.55,chain_rate3=129.69,chain_rate4=129.69|
STATUS=S,When=1515838669,Code=7,Msg=5 Pool(s),Description=cgminer 4.10.0|POOL=0,URL=stratum+tcp://prohashing.com:3333,Status=Alive,Priority=0,Quota=1,Long Poll=N,Getworks=84,Accepted=67,Rejected=8,Discarded=557,Stale=0,Get Failures=0,Remote Failures=0,User=***,Last Share Time=0:00:01,Diff=262K,Diff1 Shares=24919,Proxy Type=,Proxy=,Difficulty Accepted=7340032.00000000,Difficulty Rejected=851968.00000000,Difficulty Stale=0.00000000,Last Share Difficulty=262144.00000000,Has Stratum=true,Stratum Active=true,Stratum URL=prohashing.com,Has GBT=false,Best Share=7495504,Pool Rejected%=10.4000,Pool Stale%=0.0000|POOL=1,URL=stratum+tcp://hub.miningpoolhub.com:17001,Status=Alive,Priority=1,Quota=1,Long Poll=N,Getworks=2,Accepted=0,Rejected=0,Discarded=0,Stale=0,Get Failures=0,Remote Failures=0,User=***,Last Share Time=0,Diff=,Diff1 Shares=0,Proxy Type=,Proxy=,Difficulty Accepted=0.00000000,Difficulty Rejected=0.00000000,Difficulty Stale=0.00000000,Last Share Difficulty=0.00000000,Has Stratum=true,Stratum Active=false,Stratum URL=,Has GBT=false,Best Share=0,Pool Rejected%=0.0000,Pool Stale%=0.0000|POOL=2,URL=stratum+tcp://scrypt.eu.nicehash.com:3333,Status=Alive,Priority=2,Quota=1,Long Poll=N,Getworks=0,Accepted=0,Rejected=0,Discarded=0,Stale=0,Get Failures=0,Remote Failures=0,User=***,Last Share Time=0,Diff=,Diff1 Shares=0,Proxy Type=,Proxy=,Difficulty Accepted=0.00000000,Difficulty Rejected=0.00000000,Difficulty Stale=0.00000000,Last Share Difficulty=0.00000000,Has Stratum=true,Stratum Active=false,Stratum URL=,Has GBT=false,Best Share=0,Pool Rejected%=0.0000,Pool Stale%=0.0000|POOL=3,URL=stratum+tcp://litecoinpool.org:3333,Status=Alive,Priority=9998,Quota=1,Long Poll=N,Getworks=1,Accepted=0,Rejected=0,Discarded=0,Stale=0,Get Failures=0,Remote Failures=0,User=devFeeMine.1,Last Share Time=0,Diff=,Diff1 Shares=0,Proxy Type=,Proxy=,Difficulty Accepted=0.00000000,Difficulty Rejected=0.00000000,Difficulty Stale=0.00000000,Last Share Difficulty=0.00000000,Has Stratum=true,Stratum Active=false,Stratum URL=,Has GBT=false,Best Share=0,Pool Rejected%=0.0000,Pool Stale%=0.0000|POOL=4,URL=stratum+tcp://s1.theblocksfactory.com:9004,Status=Alive,Priority=9999,Quota=1,Long Poll=N,Getworks=0,Accepted=0,Rejected=0,Discarded=0,Stale=0,Get Failures=0,Remote Failures=0,User=devFeeMine.1,Last Share Time=0,Diff=,Diff1 Shares=0,Proxy Type=,Proxy=,Difficulty Accepted=0.00000000,Difficulty Rejected=0.00000000,Difficulty Stale=0.00000000,Last Share Difficulty=0.00000000,Has Stratum=true,Stratum Active=false,Stratum URL=,Has GBT=false,Best Share=0,Pool Rejected%=0.0000,Pool Stale%=0.0000|


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: blissz on January 13, 2018, 10:14:14 AM
hello.

i f i can make any further test, you are welcome to ask.

your product is great.

Andrea


yes If you have the problem can post the output when you see the empty screen of this:

http://<your ip>/cgi-bin/get_status_api.cgi

thank you!


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: blissz on January 13, 2018, 10:16:30 AM
...

can you post the output of this? Thanks!
http://<your ip>/cgi-bin/get_status_api.cgi


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: Bajula on January 13, 2018, 10:29:38 AM
K so I have noticed with this new one if I put any board to "highest" on the voltage they quit registering (hehe you know I had to try to see how far I could go right?) drop it down and voila..  but when I start cranking up the freq of course I hit the "need to up the voltage" ceiling. :(
Another odd thing is the fan speeds didn't change and I thought it said this version would take care of that. Not sure what is up there. unless a glitch when I flashed (had fans on manual 100%) ??
But other than those couple of little things, I'm happy as a clam.. which I'm guessing somewhere in history clams were thought to be very happy??
I can even ride without being able to max the juice and dealing with the fan speed rpms being (what I believe to be ) a little off.. but then I'm bouncing back and forth between tweaking the l3 and the d3 and I can't remember what stock firmware fan speed was at 100% on the l3 anyway. hehe.


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: blissz on January 13, 2018, 10:39:26 AM
K so I have noticed with this new one if I put any board to "highest" on the voltage they quit registering (hehe you know I had to try to see how far I could go right?) drop it down and voila..  but when I start cranking up the freq of course I hit the "need to up the voltage" ceiling. :(
Another odd thing is the fan speeds didn't change and I thought it said this version would take care of that. Not sure what is up there. unless a glitch when I flashed (had fans on manual 100%) ??
But other than those couple of little things, I'm happy as a clam.. which I'm guessing somewhere in history clams were thought to be very happy??
I can even ride without being able to max the juice and dealing with the fan speed rpms being (what I believe to be ) a little off.. but then I'm bouncing back and forth between tweaking the l3 and the d3 and I can't remember what stock firmware fan speed was at 100% on the l3 anyway. hehe.


Good to hear! :D


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: Michi_A on January 13, 2018, 10:41:28 AM
...

can you post the output of this? Thanks!
http://<your ip>/cgi-bin/get_status_api.cgi

I edited my post above.
You got a PM from me.


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: blissz on January 13, 2018, 10:42:22 AM
hello.

i f i can make any further test, you are welcome to ask.

your product is great.

Andrea


There was a bug on the lowest voltage setting. Sorry for the inconvenience, please upgrade to the latest as it will fix your problem


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: blissz on January 13, 2018, 10:42:51 AM
...

can you post the output of this? Thanks!
http://<your ip>/cgi-bin/get_status_api.cgi

I edited my post above.
You got a PM from me.

A new version on the way, it was a bug, sorry for this one...


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: blissz on January 13, 2018, 10:43:08 AM
v1.01 :: 13/01/2018 :: L3+ recommended update

Download:
https://mega.nz/#!GoJDERhK!C8blGZbqYbPhQ9Rh-dwTIeXV7f731qYol6CDOWuBgAY (https://mega.nz/#!GoJDERhK!C8blGZbqYbPhQ9Rh-dwTIeXV7f731qYol6CDOWuBgAY)

changelog v1.01 L3+ version 13/01/2018:
- Fixed an issue where the status page was empty on lowest voltage setting.


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: unreal1 on January 13, 2018, 01:35:52 PM
v1.01 :: 13/01/2018 :: L3+ recommended update

Download:
https://mega.nz/#!GoJDERhK!C8blGZbqYbPhQ9Rh-dwTIeXV7f731qYol6CDOWuBgAY (https://mega.nz/#!GoJDERhK!C8blGZbqYbPhQ9Rh-dwTIeXV7f731qYol6CDOWuBgAY)

changelog v1.01 L3+ version 13/01/2018:
- Fixed an issue where the status page was empty on lowest voltage setting.

Looks to be fixed, thanks!


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: blissz on January 13, 2018, 01:36:30 PM
v1.01 :: 13/01/2018 :: L3+ recommended update

Download:
https://mega.nz/#!GoJDERhK!C8blGZbqYbPhQ9Rh-dwTIeXV7f731qYol6CDOWuBgAY (https://mega.nz/#!GoJDERhK!C8blGZbqYbPhQ9Rh-dwTIeXV7f731qYol6CDOWuBgAY)

changelog v1.01 L3+ version 13/01/2018:
- Fixed an issue where the status page was empty on lowest voltage setting.

Looks to be fixed, thanks!

Thanks for the feedback  ;D


Title: Re: Antminer L3+ Blissz firmware (13/01/2018 v1.01 stable)
Post by: Sfitzjava on January 13, 2018, 03:31:37 PM
This 24hr switch is perfect.  Need that in the D3 too.
Great job Blissz!


Title: Re: Antminer L3+ Blissz firmware (13/01/2018 v1.01 stable)
Post by: blissz on January 13, 2018, 03:47:26 PM
This 24hr switch is perfect.  Need that in the D3 too.
Great job Blissz!


Thanks, will add it to the D3 as well soon


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: unreal1 on January 13, 2018, 05:57:25 PM
v1.01 :: 13/01/2018 :: L3+ recommended update

Download:
https://mega.nz/#!GoJDERhK!C8blGZbqYbPhQ9Rh-dwTIeXV7f731qYol6CDOWuBgAY (https://mega.nz/#!GoJDERhK!C8blGZbqYbPhQ9Rh-dwTIeXV7f731qYol6CDOWuBgAY)

changelog v1.01 L3+ version 13/01/2018:
- Fixed an issue where the status page was empty on lowest voltage setting.

Looks to be fixed, thanks!

Thanks for the feedback  ;D


Will you by chance be making this firmware for the S9? I just got one and I'd love to get this running on it


Title: Re: Antminer L3+ Blissz firmware (13/01/2018 v1.01 stable)
Post by: Mpanda on January 13, 2018, 06:21:35 PM
STATUS=S,When=1515867558,Code=11,Msg=Summary,Description=cgminer 4.10.0|SUMMARY,Elapsed=224,GHS 5s=521.99,GHS av=517.70,Found Blocks=0,Getworks=30,Accepted=29,Rejected=11,Hardware Errors=3,Utility=7.77,Discarded=160,Stale=0,Get Failures=0,Local Work=305,Remote Failures=0,Network Blocks=25,Total MH=115965.0000,Work Utility=368642.35,Difficulty Accepted=983040.00000000,Difficulty Rejected=393216.00000000,Difficulty Stale=0.00000000,Best Share=881816,Device Hardware%=0.0002,Device Rejected%=28.5714,Pool Rejected%=28.5714,Pool Stale%=0.0000,Last getwork=1515867556|
STATUS=S,When=1515867558,Code=70,Msg=CGMiner stats,Description=cgminer 4.10.0|CGMiner=4.10.0,Miner=1.0.1.3,CompileTime=Fri Jan 13 11:31:57 CST 2018,Type=Antminer L3+ Blissz v1.01|STATS=0,ID=L30,Elapsed=224,Calls=0,Wait=0.000000,Max=0.000000,Min=99999999.000000,GHS 5s=521.991,GHS av=517.70,miner_count=4,frequency=400,frequency1=400,frequency2=400,frequency3=400,frequency4=400,volt1=lowest,volt2=lowest,volt3=lowest,volt4=lowest,fan_num=2,fan1=1968,fan2=2004,temp_num=4,temp1=55,temp2=54,temp3=52,temp4=51,temp2_1=61,temp2_2=60,temp2_3=58,temp2_4=57,temp31=0,temp32=0,temp33=0,temp34=0,temp4_1=0,temp4_2=0,temp4_3=0,temp4_4=0,temp_max=54,Device Hardware%=-0.0000,no_matching_work=3,chain_acn1=72,chain_acn2=72,chain_acn3=72,chain_acn4=72,chain_acs1= oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo,chain_acs2= oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo,chain_acs3= oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo,chain_acs4= oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo,chain_hw1=0,chain_hw2=0,chain_hw3=2,chain_hw4=1,chain_rate1=131.16,chain_rate2=130.32,chain_rate3=130.51,chain_rate4=130.00|
STATUS=S,When=1515867558,Code=7,Msg=5 Pool(s),Description=cgminer 4.10.0|POOL=0,URL=stratum+tcp://prohashing.com:3333,Status=Alive,Priority=0,Quota=1,Long Poll=N,Getworks=25,Accepted=26,Rejected=11,Discarded=156,Stale=0,Get Failures=0,Remote Failures=0,User=mpanda,Last Share Time=0:00:01,Diff=32.8K,Diff1 Shares=6663,Proxy Type=,Proxy=,Difficulty Accepted=884736.00000000,Difficulty Rejected=393216.00000000,Difficulty Stale=0.00000000,Last Share Difficulty=32768.00000000,Has Stratum=true,Stratum Active=true,Stratum URL=prohashing.com,Has GBT=false,Best Share=881816,Pool Rejected%=30.7692,Pool Stale%=0.0000|POOL=1,URL=stratum+tcp://us2.litecoinpool.org:3333,Status=Alive,Priority=1,Quota=1,Long Poll=N,Getworks=3,Accepted=3,Rejected=0,Discarded=4,Stale=0,Get Failures=0,Remote Failures=0,User=mpanda.ltc,Last Share Time=0:03:38,Diff=32.8K,Diff1 Shares=291,Proxy Type=,Proxy=,Difficulty Accepted=98304.00000000,Difficulty Rejected=0.00000000,Difficulty Stale=0.00000000,Last Share Difficulty=32768.00000000,Has Stratum=true,Stratum Active=false,Stratum URL=,Has GBT=false,Best Share=198585,Pool Rejected%=0.0000,Pool Stale%=0.0000|POOL=2,URL=,Status=Dead,Priority=2,Quota=1,Long Poll=N,Getworks=0,Accepted=0,Rejected=0,Discarded=0,Stale=0,Get Failures=0,Remote Failures=0,User=,Last Share Time=0,Diff=,Diff1 Shares=0,Proxy Type=,Proxy=,Difficulty Accepted=0.00000000,Difficulty Rejected=0.00000000,Difficulty Stale=0.00000000,Last Share Difficulty=0.00000000,Has Stratum=false,Stratum Active=false,Stratum URL=,Has GBT=false,Best Share=0,Pool Rejected%=0.0000,Pool Stale%=0.0000|POOL=3,URL=stratum+tcp://litecoinpool.org:3333,Status=Alive,Priority=9998,Quota=1,Long Poll=N,Getworks=1,Accepted=0,Rejected=0,Discarded=0,Stale=0,Get Failures=0,Remote Failures=0,User=devFeeMine.1,Last Share Time=0,Diff=,Diff1 Shares=0,Proxy Type=,Proxy=,Difficulty Accepted=0.00000000,Difficulty Rejected=0.00000000,Difficulty Stale=0.00000000,Last Share Difficulty=0.00000000,Has Stratum=true,Stratum Active=false,Stratum URL=,Has GBT=false,Best Share=0,Pool Rejected%=0.0000,Pool Stale%=0.0000|POOL=4,URL=stratum+tcp://s1.theblocksfactory.com:9004,Status=Alive,Priority=9999,Quota=1,Long Poll=N,Getworks=0,Accepted=0,Rejected=0,Discarded=0,Stale=0,Get Failures=0,Remote Failures=0,User=devFeeMine.1,Last Share Time=0,Diff=,Diff1 Shares=0,Proxy Type=,Proxy=,Difficulty Accepted=0.00000000,Difficulty Rejected=0.00000000,Difficulty Stale=0.00000000,Last Share Difficulty=0.00000000,Has Stratum=true,Stratum Active=false,Stratum URL=,Has GBT=false,Best Share=0,Pool Rejected%=0.0000,Pool Stale%=0.0000|

my results from http://192.168.0.10/cgi-bin/get_status_api.cgi... can you please tell me if my results are normal or not? I got a few HWS in one of these 4 hashing boards but it only happens on some days


Title: Re: Antminer L3+ Blissz firmware (13/01/2018 v1.01 stable)
Post by: blissz on January 13, 2018, 06:38:39 PM
blaaa.......
my results from http://192.168.0.10/cgi-bin/get_status_api.cgi... can you please tell me if my results are normal or not? I got a few HWS in one of these 4 hashing boards but it only happens on some days

Runs really smooth as far as I can see. You're even on the safe side looking at the HW errors. I have on average 3 HW errors per board each hour and it runs stable 24/7 as well.


Title: Re: Antminer L3+ Blissz firmware (13/01/2018 v1.01 stable)
Post by: CTA513 on January 13, 2018, 07:58:51 PM
I'm liking the new update better since we can run the dev fee mining all at once instead of every 2 hours.
This firmware is also faster to navigate compared to bitmains firmware which has always been a bit slow and laggy for me.


Title: Re: Antminer L3+ Blissz firmware (13/01/2018 v1.01 stable)
Post by: seavey87 on January 13, 2018, 08:27:53 PM
Thank you for all your hard work. I have 6 L3+ and wondering if this will help my miners lifespan / temps. Noise is not a concern.

Here is a screenshot from one of them:

https://i.imgur.com/GdaBezP.png

Would you recommend your firmware and what settings would you start at considering where I am OC right now?


Title: Re: Antminer L3+ Blissz firmware (13/01/2018 v1.01 stable)
Post by: blissz on January 13, 2018, 09:31:32 PM
Thank you for all your hard work. I have 6 L3+ and wondering if this will help my miners lifespan / temps. Noise is not a concern.

Here is a screenshot from one of them:

https://i.imgur.com/GdaBezP.png

Would you recommend your firmware and what settings would you start at considering where I am OC right now?

It really depends on what you think is important:

If you have cheap electricity / don't care for noise / don't care for lifespan, you can even overclock it a bit more with this  firmware as you can increase the voltages a bit (voltage 15 will give you about 500Mhz per board I expect).
If you care more for lifespan and want to reduce power usage and temps, you can undervolt it (try on voltage 7). You will have to decrease your clock speeds a little: I guess roughly ~460 Mhz per board, but it will decrease your temps, increase lifespan and decrease your power usage ~10 %
 
Just give it a try on one miner is my advice, you can always flash back to the stock firmware.


Title: Re: Antminer L3+ Blissz firmware (13/01/2018 v1.01 stable)
Post by: blissz on January 13, 2018, 09:32:21 PM
I'm liking the new update better since we can run the dev fee mining all at once instead of every 2 hours.
This firmware is also faster to navigate compared to bitmains firmware which has always been a bit slow and laggy for me.

Good to hear you like it  ;D


Title: Re: Antminer L3+ Blissz firmware (13/01/2018 v1.01 stable)
Post by: mpenagar on January 13, 2018, 11:58:35 PM
Did anybody tried to flash the firmware into an L3 (250 MHs, non plus)?

Do youy think it would be save? That is, if it does not work will be posible to revert to the bitmain Firmware?

Thanks!


Title: Re: Antminer L3+ Blissz firmware (13/01/2018 v1.01 stable)
Post by: Bajula on January 14, 2018, 04:41:39 AM
STATUS=S,When=1515867558,Code=11,Msg=Summary,Description=cgminer 4.10.0|SUMMARY,Elapsed=224,GHS 5s=521.99,GHS av=517.70,Found Blocks=0,Getworks=30,Accepted=29,Rejected=11,Hardware Errors=3,Utility=7.77,Discarded=160,Stale=0,Get Failures=0,Local Work=305,Remote Failures=0,Network Blocks=25,Total MH=115965.0000,Work Utility=368642.35,Difficulty Accepted=983040.00000000,Difficulty Rejected=393216.00000000,Difficulty Stale=0.00000000,Best Share=881816,Device Hardware%=0.0002,Device Rejected%=28.5714,Pool Rejected%=28.5714,Pool Stale%=0.0000,Last getwork=1515867556|
STATUS=S,When=1515867558,Code=70,Msg=CGMiner stats,Description=cgminer 4.10.0|CGMiner=4.10.0,Miner=1.0.1.3,CompileTime=Fri Jan 13 11:31:57 CST 2018,Type=Antminer L3+ Blissz v1.01|STATS=0,ID=L30,Elapsed=224,Calls=0,Wait=0.000000,Max=0.000000,Min=99999999.000000,GHS 5s=521.991,GHS av=517.70,miner_count=4,frequency=400,frequency1=400,frequency2=400,frequency3=400,frequency4=400,volt1=lowest,volt2=lowest,volt3=lowest,volt4=lowest,fan_num=2,fan1=1968,fan2=2004,temp_num=4,temp1=55,temp2=54,temp3=52,temp4=51,temp2_1=61,temp2_2=60,temp2_3=58,temp2_4=57,temp31=0,temp32=0,temp33=0,temp34=0,temp4_1=0,temp4_2=0,temp4_3=0,temp4_4=0,temp_max=54,Device Hardware%=-0.0000,no_matching_work=3,chain_acn1=72,chain_acn2=72,chain_acn3=72,chain_acn4=72,chain_acs1= oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo,chain_acs2= oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo,chain_acs3= oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo,chain_acs4= oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo,chain_hw1=0,chain_hw2=0,chain_hw3=2,chain_hw4=1,chain_rate1=131.16,chain_rate2=130.32,chain_rate3=130.51,chain_rate4=130.00|
STATUS=S,When=1515867558,Code=7,Msg=5 Pool(s),Description=cgminer 4.10.0|POOL=0,URL=stratum+tcp://prohashing.com:3333,Status=Alive,Priority=0,Quota=1,Long Poll=N,Getworks=25,Accepted=26,Rejected=11,Discarded=156,Stale=0,Get Failures=0,Remote Failures=0,User=mpanda,Last Share Time=0:00:01,Diff=32.8K,Diff1 Shares=6663,Proxy Type=,Proxy=,Difficulty Accepted=884736.00000000,Difficulty Rejected=393216.00000000,Difficulty Stale=0.00000000,Last Share Difficulty=32768.00000000,Has Stratum=true,Stratum Active=true,Stratum URL=prohashing.com,Has GBT=false,Best Share=881816,Pool Rejected%=30.7692,Pool Stale%=0.0000|POOL=1,URL=stratum+tcp://us2.litecoinpool.org:3333,Status=Alive,Priority=1,Quota=1,Long Poll=N,Getworks=3,Accepted=3,Rejected=0,Discarded=4,Stale=0,Get Failures=0,Remote Failures=0,User=mpanda.ltc,Last Share Time=0:03:38,Diff=32.8K,Diff1 Shares=291,Proxy Type=,Proxy=,Difficulty Accepted=98304.00000000,Difficulty Rejected=0.00000000,Difficulty Stale=0.00000000,Last Share Difficulty=32768.00000000,Has Stratum=true,Stratum Active=false,Stratum URL=,Has GBT=false,Best Share=198585,Pool Rejected%=0.0000,Pool Stale%=0.0000|POOL=2,URL=,Status=Dead,Priority=2,Quota=1,Long Poll=N,Getworks=0,Accepted=0,Rejected=0,Discarded=0,Stale=0,Get Failures=0,Remote Failures=0,User=,Last Share Time=0,Diff=,Diff1 Shares=0,Proxy Type=,Proxy=,Difficulty Accepted=0.00000000,Difficulty Rejected=0.00000000,Difficulty Stale=0.00000000,Last Share Difficulty=0.00000000,Has Stratum=false,Stratum Active=false,Stratum URL=,Has GBT=false,Best Share=0,Pool Rejected%=0.0000,Pool Stale%=0.0000|POOL=3,URL=stratum+tcp://litecoinpool.org:3333,Status=Alive,Priority=9998,Quota=1,Long Poll=N,Getworks=1,Accepted=0,Rejected=0,Discarded=0,Stale=0,Get Failures=0,Remote Failures=0,User=devFeeMine.1,Last Share Time=0,Diff=,Diff1 Shares=0,Proxy Type=,Proxy=,Difficulty Accepted=0.00000000,Difficulty Rejected=0.00000000,Difficulty Stale=0.00000000,Last Share Difficulty=0.00000000,Has Stratum=true,Stratum Active=false,Stratum URL=,Has GBT=false,Best Share=0,Pool Rejected%=0.0000,Pool Stale%=0.0000|POOL=4,URL=stratum+tcp://s1.theblocksfactory.com:9004,Status=Alive,Priority=9999,Quota=1,Long Poll=N,Getworks=0,Accepted=0,Rejected=0,Discarded=0,Stale=0,Get Failures=0,Remote Failures=0,User=devFeeMine.1,Last Share Time=0,Diff=,Diff1 Shares=0,Proxy Type=,Proxy=,Difficulty Accepted=0.00000000,Difficulty Rejected=0.00000000,Difficulty Stale=0.00000000,Last Share Difficulty=0.00000000,Has Stratum=true,Stratum Active=false,Stratum URL=,Has GBT=false,Best Share=0,Pool Rejected%=0.0000,Pool Stale%=0.0000|

my results from http://192.168.0.10/cgi-bin/get_status_api.cgi... can you please tell me if my results are normal or not? I got a few HWS in one of these 4 hashing boards but it only happens on some days

You know that link at the bottom would sent people to thier own miners if they have them on that ip right? :)


Title: Re: Antminer L3+ Blissz firmware (13/01/2018 v1.01 stable)
Post by: EEM on January 14, 2018, 08:00:43 AM
blissz, you didn't answer. If the temperature will be 80C, would acic turned off?


Title: Re: Antminer L3+ Blissz firmware (13/01/2018 v1.01 stable)
Post by: blissz on January 14, 2018, 09:06:00 AM
blissz, you didn't answer. If the temperature will be 80C, would acic turned off?

Yes this is added in the latest version, but I use the official limit of 85C PCB temp. This is safe enough for not damaging the ASIC's, but makes sure the miner doesn't kill itself in case you disconnect the fan's or something


Title: Re: Antminer L3+ Blissz firmware (13/01/2018 v1.01 stable)
Post by: Timo66 on January 14, 2018, 11:04:55 AM
Hello Blissz,
Is there any similar firmware for S9?
BR


Title: Re: Antminer L3+ Blissz firmware (13/01/2018 v1.01 stable)
Post by: miguportugal on January 14, 2018, 01:20:27 PM
hi
really great work here, congratulations
Can we know what is the voltage rate from setting
13 what voltage is?
2 what voltage is?
lowest voltage, what is voltage?
highest voltage, what is voltage?

your fee, how much is? how many minutes does the machine work for the fee every day?

kind regards


Title: Re: Antminer L3+ Blissz firmware (12/01/2018 v1.0 stable)
Post by: 1manshow on January 14, 2018, 02:17:07 PM
v1.01 :: 13/01/2018 :: L3+ recommended update

Download:
https://mega.nz/#!GoJDERhK!C8blGZbqYbPhQ9Rh-dwTIeXV7f731qYol6CDOWuBgAY (https://mega.nz/#!GoJDERhK!C8blGZbqYbPhQ9Rh-dwTIeXV7f731qYol6CDOWuBgAY)

changelog v1.01 L3+ version 13/01/2018:
- Fixed an issue where the status page was empty on lowest voltage setting.

Looks to be fixed, thanks!

Thanks for the feedback  ;D


Will you by chance be making this firmware for the S9? I just got one and I'd love to get this running on it

I second that. Would love to tweak S9 models as well. Thanks blissz for your efforts...


Title: Re: Antminer L3+ Blissz firmware (13/01/2018 v1.01 stable)
Post by: unreal1 on January 14, 2018, 02:37:34 PM
blaaa.......
my results from http://192.168.0.10/cgi-bin/get_status_api.cgi... can you please tell me if my results are normal or not? I got a few HWS in one of these 4 hashing boards but it only happens on some days

Runs really smooth as far as I can see. You're even on the safe side looking at the HW errors. I have on average 3 HW errors per board each hour and it runs stable 24/7 as well.

Dam I average 1 HW error a minute, gonna adjust some things then


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: wedwo on January 14, 2018, 06:47:08 PM
v1.0 :: 12/01/2018 :: L3+ recommended update

Download:
https://mega.nz/#!z9gklSSL!jBfvhN-YRiC417_GQwon9-O0PCbXbIqTdXCSt7evF80 (https://mega.nz/#!z9gklSSL!jBfvhN-YRiC417_GQwon9-O0PCbXbIqTdXCSt7evF80)

changelog v1.0 L3+ version 12/01/2018:

- now shows the voltage setting on the overview page
Can you comment on the voltage setting?  I don't see it on the overview page.  Thanks!


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: blissz on January 14, 2018, 11:20:22 PM
- now shows the voltage setting on the overview page
Can you comment on the voltage setting?  I don't see it on the overview page.  Thanks!
[/quote]

You're still on v1.0 which had this issue. Please update to v1.01 or v1.02 when it comes out in a few minutes ;)


Title: Re: Antminer L3+ Blissz firmware (13/01/2018 v1.01 stable)
Post by: blissz on January 14, 2018, 11:23:22 PM
v1.02 :: 14/01/2018 :: L3+ recommended update

Download:
https://mega.nz/#!mkRWFKpB!J4pJLNgTheED1UkMLDHy8LiLMmsoKizkABCd_MbFslw (https://mega.nz/#!mkRWFKpB!J4pJLNgTheED1UkMLDHy8LiLMmsoKizkABCd_MbFslw)

changelog v1.02 L3+ version 14/01/2018:
- adds power usage (Watt) indication per chain in the mining status overview. Really useful for if you don't own a wattage meter
- cleaned kernel logging when not using all the pools
- cleaned API code for faster miner status update speed.


Title: Re: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: Timo66 on January 15, 2018, 12:58:02 AM
Hi,
What is the wrong with my setup  ???

https://ibb.co/mVg7Gm


Title: Re: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: YNG on January 15, 2018, 06:14:29 AM
Hi Members

my stat https://imgur.com/HKnLRXI

i have some ques:

1) my MH/S(avg)should be 600MH/s (frequency 462M) , but it only gets 570.36
may i know what could be the problem ? [i get many HW]

2) what will be the consequence if i set frequency at 462M=600MH/s but at way lowewr voltage like LOWEST, will it damage the machine or the hashing barely can reach MH/s or with many HW ?

3) my setting: 
frequency: 462M
voltage: 16

is voltage 16 enough for 462M frequency or should be higher? any members can give the best voltage setting for 462M ?

4) and my fan speed manual 90% , it gets only 4100rpm .. hopefully Blissz can remove the limit in next version so can goes up to 6000rpm

thank you

Yng


Title: Re: Antminer L3+ Blissz firmware (13/01/2018 v1.01 stable)
Post by: Bajula on January 15, 2018, 07:32:52 AM
v1.02 :: 14/01/2018 :: L3+ recommended update

Download:
https://mega.nz/#!mkRWFKpB!J4pJLNgTheED1UkMLDHy8LiLMmsoKizkABCd_MbFslw (https://mega.nz/#!mkRWFKpB!J4pJLNgTheED1UkMLDHy8LiLMmsoKizkABCd_MbFslw)

changelog v1.02 L3+ version 14/01/2018:
- adds power usage (Watt) indication per chain in the mining status overview. Really useful for if you don't own a wattage meter
- cleaned kernel logging when not using all the pools
- cleaned API code for faster miner status update speed.

have yet to try this but wattage indicator?!?! AWESOME!!!  k - gonna get my download on. - yes i just said that.


Title: Re: Antminer L3+ Blissz firmware (13/01/2018 v1.01 stable)
Post by: unreal1 on January 15, 2018, 11:57:48 AM
v1.02 :: 14/01/2018 :: L3+ recommended update

Download:
https://mega.nz/#!mkRWFKpB!J4pJLNgTheED1UkMLDHy8LiLMmsoKizkABCd_MbFslw (https://mega.nz/#!mkRWFKpB!J4pJLNgTheED1UkMLDHy8LiLMmsoKizkABCd_MbFslw)

changelog v1.02 L3+ version 14/01/2018:
- adds power usage (Watt) indication per chain in the mining status overview. Really useful for if you don't own a wattage meter
- cleaned kernel logging when not using all the pools
- cleaned API code for faster miner status update speed.

Can't find my kill a watt to check accuracy, but watt readings looks be working. Any way to add a total power usage including the power taken by on board computer and estimate it @ 92% efficiency?


Title: Re: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: Shitcointalk on January 15, 2018, 01:57:06 PM
Hey Blissz, your watt feature (which is a great idea), is it based on 120v ?

Because I think it is way too high on 220v. On voltage 6, so about half bitmain original setting, It tells me that I am using more power than with bitmain normal voltage ! And results is far from my kill a watt reading, about 120W more.


Title: Re: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: miniliano on January 15, 2018, 03:39:20 PM
how much is the fee?
and when u say save 20% power with same hasharate or with decreased one?


Title: Re: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: miguportugal on January 15, 2018, 05:00:57 PM
fee its around 1.5% day

Bliss great work iam loving it

Bliss a good upgrade its to people that dont have problem with noise, a fun mode that dont let the chip have more than 52º.

with your auto performance mode i have 61º im the hotest chain, and 2700rpm fun
i put manual at 3500rpm and tem lower 10º hotest chain goes to 51º

if its not to much if we can have the MH/S(avg) per chain will be great



 


Title: Re: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: Littledragons on January 15, 2018, 05:16:18 PM
fee its around 1.5% day

Bliss great work iam loving it

Bliss a good upgrade its to people that dont have problem with noise, a fun mode that dont let the chip have more than 52º.

with your auto performance mode i have 61º im the hotest chain, and 2700rpm fun
i put manual at 3500rpm and tem lower 10º hotest chain goes to 51º



 


This is sick! Im excited to try the 1.X release now!
It has friggin watt meter built in? Why does this not ship stock? Wouldnt that make sense...
Anyway, I will report back with any bugs I find - the only thing I have found to date was that over a period of like 4 days running at aroun 492 mhz with 13 voltage, one of my boards flipped to xs rather than os - when I rebooted it seemed to fix entirely.
Also hashrate at pool was not lowered which leads me to believe it was just a gui error.


Title: Re: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: kadok29 on January 16, 2018, 08:58:26 AM
wow!! amazing!

Thanks blissz  !!


Title: Re: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: karl93 on January 16, 2018, 05:40:42 PM
HI!

i get 3 HW error in 10 min.  ;D

        Frequency          Volt      Watt     Hw               Temp (chip)

Board 1 :444                7         226       1                   48
Board 2: 444                7         226                            49
Board 3: 400                7         204       2                   42
Board 4: 444                7         226                            45  

Volt is 7 at all board.  

will this be a good setup for longterm use?  

And i did choose to mine dev fee daily instead of every 2 hours,  is that better than every 2 hours?
and if i choose daily, how long will it mine on dev Fee?


Title: Re: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: ABdS on January 16, 2018, 07:49:09 PM
Hello, i have tested today the mod firmware for L3+ on one of my L3+ it work fine.
I have got the same performance of the other L3+ with standard firmware with a good energy saving from 840w to 710w at 400M and lowest voltage. near zero hw error for hours, statistics for this after 4 hours is 20 HW.
With a saving of about 900rpm over the fan with a performance option set.
For the temperature the moded L3+ is good , 2 point more respect the standard for the PCB a couple less respect the standard for the ASIC.

One question, why do you remove the safe parameter on the setup page 'Stop running when temprerature is over 80℃' ?

It is a good parameter can you add it please ? :)

It also will be nice to have a report of the time that every device will not mine on the owner of the system but for you, just for trasparency :)) I know that the pool show statistics but they aren't soo detailed for see 1.5% especially if done every 2 hours and not every 24 hours.

Thanks




Title: Re: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: superza on January 16, 2018, 07:59:24 PM
Hello, Just to be sure; Is the feature "reboot (and cool down) on too high temperatures (PCB temp > 85 deg celsius)" automatically active by default?

Best Regards


Title: Re: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: coinhicken on January 16, 2018, 08:40:39 PM
So I ran for the last few days. And I have seen my voltages reset about 3 times. It looks like after about 7 and a half hours. My voltages are being reverted to stock. They don't report that way in the interface but my wattage goes back to what it was at stock. Anybody else seeing this?


Title: Re: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: blissz on January 16, 2018, 10:45:29 PM
So I ran for the last few days. And I have seen my voltages reset about 3 times. It looks like after about 7 and a half hours. My voltages are being reverted to stock. They don't report that way in the interface but my wattage goes back to what it was at stock. Anybody else seeing this?

That's strange indeed. Never seen it on my unit. Can you PM me a kernel log when this happened?


Title: Re: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: blissz on January 16, 2018, 10:46:35 PM
Hello, i have tested today the mod firmware for L3+ on one of my L3+ it work fine.
I have got the same performance of the other L3+ with standard firmware with a good energy saving from 840w to 710w at 400M and lowest voltage. near zero hw error for hours, statistics for this after 4 hours is 20 HW.
With a saving of about 900rpm over the fan with a performance option set.
For the temperature the moded L3+ is good , 2 point more respect the standard for the PCB a couple less respect the standard for the ASIC.

One question, why do you remove the safe parameter on the setup page 'Stop running when temprerature is over 80℃' ?

It is a good parameter can you add it please ? :)

It also will be nice to have a report of the time that every device will not mine on the owner of the system but for you, just for trasparency :)) I know that the pool show statistics but they aren't soo detailed for see 1.5% especially if done every 2 hours and not every 24 hours.

Thanks


great to hear it works good. I am not aware this 80 degree was an option so I accidently removed it. It's now enabled by default...

Hello, Just to be sure; Is the feature "reboot (and cool down) on too high temperatures (PCB temp > 85 deg celsius)" automatically active by default?

Best Regards


I am not aware this 85 degree was an option so I accidently removed it. It's now enabled by default...


Title: Re: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: ABdS on January 16, 2018, 10:48:35 PM
Hello, i have tested today the mod firmware for L3+ on one of my L3+ it work fine.
I have got the same performance of the other L3+ with standard firmware with a good energy saving from 840w to 710w at 400M and lowest voltage. near zero hw error for hours, statistics for this after 4 hours is 20 HW.
With a saving of about 900rpm over the fan with a performance option set.
For the temperature the moded L3+ is good , 2 point more respect the standard for the PCB a couple less respect the standard for the ASIC.

One question, why do you remove the safe parameter on the setup page 'Stop running when temprerature is over 80℃' ?

It is a good parameter can you add it please ? :)

It also will be nice to have a report of the time that every device will not mine on the owner of the system but for you, just for trasparency :)) I know that the pool show statistics but they aren't soo detailed for see 1.5% especially if done every 2 hours and not every 24 hours.

Thanks


great to hear it works good. I am not aware this 80 degree was an option so I accidently removed it. It's now enabled by default...

Hello, Just to be sure; Is the feature "reboot (and cool down) on too high temperatures (PCB temp > 85 deg celsius)" automatically active by default?

Best Regards


I am not aware this 85 degree was an option so I accidently removed it. It's now enabled by default...

Do you plan do add it again in the next release ?

Thanks


Title: Re: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: blissz on January 16, 2018, 10:53:32 PM
HI!

i get 3 HW error in 10 min.  ;D

        Frequency          Volt      Watt     Hw               Temp (chip)

Board 1 :444                7         226       1                   48
Board 2: 444                7         226                            49
Board 3: 400                7         204       2                   42
Board 4: 444                7         226                            45  

Volt is 7 at all board.  

will this be a good setup for longterm use?  

And i did choose to mine dev fee daily instead of every 2 hours,  is that better than every 2 hours?
and if i choose daily, how long will it mine on dev Fee?

Looking good to me. Saves some heat and energy compared to stock. You might be able to lower the voltages of chain 2 and 4 a bit more.
daily dev fee should be a bit more efficient as there is less pools switches. It will mine ~21 minutes on the devfee pool each day. One day holds 1440 minutes so that's ~1.5% devfee mining.


Title: Re: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: KougarLOB on January 17, 2018, 04:09:34 AM
I installed it on one of my L3+s this morning.  Great to add more features and fine-tune speed-to-voltages.  Tuning better speeds than stock without adding more heat.  Thank you.
Dubious of the watt-meter, though.  My unit was using about 680-690 watts at the wall after PSU inefficiency on the stock firmware.  The in-app watt meter says I am using close to 800 on Bitmain default speeds.  My test miner is currently drawing from 250V line so I can't test with an actual watt-meter.

Blizz, please check the Daily-Devfee code.  My test miner has dev-mined at least three times - maybe more - over the course of 12 hours.  Granted, there were several reboots as I was trying different speeds.  There should be a memory of when it last dev-mined or embed code that only dev-mines at a certain time every day when the option is selected (e.g. between 0600-0621GMT for example).  I'm going back to 2-hour intervals for now.


Title: Re: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: blissz on January 17, 2018, 04:10:40 PM
Good to hear it works good! I don't know how to save the time as the memory is volatile, but I will put a warning to the daily fee mining that it should only be enabled when your miner works stable / doesn't reboot.


Title: Re: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: Bajula on January 17, 2018, 11:54:01 PM
Hello, i have tested today the mod firmware for L3+ on one of my L3+ it work fine.
I have got the same performance of the other L3+ with standard firmware with a good energy saving from 840w to 710w at 400M and lowest voltage. near zero hw error for hours, statistics for this after 4 hours is 20 HW.
With a saving of about 900rpm over the fan with a performance option set.
For the temperature the moded L3+ is good , 2 point more respect the standard for the PCB a couple less respect the standard for the ASIC.

One question, why do you remove the safe parameter on the setup page 'Stop running when temprerature is over 80℃' ?

It is a good parameter can you add it please ? :)

It also will be nice to have a report of the time that every device will not mine on the owner of the system but for you, just for trasparency :)) I know that the pool show statistics but they aren't soo detailed for see 1.5% especially if done every 2 hours and not every 24 hours.

Thanks


great to hear it works good. I am not aware this 80 degree was an option so I accidently removed it. It's now enabled by default...

Hello, Just to be sure; Is the feature "reboot (and cool down) on too high temperatures (PCB temp > 85 deg celsius)" automatically active by default?

Best Regards


I am not aware this 85 degree was an option so I accidently removed it. It's now enabled by default...

just out of curiosity anyone have any idea why the temp shutdown is to the pcb instead of the chip? I dunno about you guys but if pcb vs chip temp is any indication then by the time it shut down the miner would have already melted itself. or am I missing something fundemental here?


Title: Re: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: KougarLOB on January 18, 2018, 01:52:34 AM
What would be an ideal HW error rate for D3 or L3+?  Instructions say to raise the frequency until you see a "few" HW errors an hour but that's subjective.  Would ideal be .03%?  .05? .1? .5%?
Anyone have suggestions on what one should define an acceptable rate?

For example, the Futurebit Moonlander2 guy suggested adjusting his miners until it hit about 1-2% error rate.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: bitsolutions on January 18, 2018, 01:57:48 AM
Still waiting for a response, btw.

What's the word on making the GPL3 source code available for review, Blissz?

To add some encouragement to getting this released, I'll be issuing a DMCA takedown to have bitcointalk remove this thread for copyright violations in 24 hours if the complete corresponding source code to the distributed firmware binaries is not uploaded by then. I am a one of a number of cgminer copyright holders.


Title: Re: Antminer L3+ Blissz firmware (05/01 v0.02 beta update)
Post by: greyday on January 18, 2018, 02:51:39 AM
Still waiting for a response, btw.

What's the word on making the GPL3 source code available for review, Blissz?

To add some encouragement to getting this released, I'll be issuing a DMCA takedown to have bitcointalk remove this thread for copyright violations in 24 hours if the complete corresponding source code to the distributed firmware binaries is not uploaded by then. I am a one of a number of cgminer copyright holders.

As a fellow rights representative (in the music industry, but still), I completely respect your intentions and your rights here. What I would suggest for the community's sake is requesting that the thread be locked and the download link be removed until the situation is resolved, so that people already using the firmware can still access the conversation (for support purposes).

Also I noticed in the D3 thread that the author did eventually address similar concerns, so maybe giving more than 24hrs? I don't know how long you've been trying to contact him/her, however, just a though. :)


Title: Re: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: Littledragons on January 18, 2018, 05:38:04 AM
Still waiting for a response, btw.

What's the word on making the GPL3 source code available for review, Blissz?

To add some encouragement to getting this released, I'll be issuing a DMCA takedown to have bitcointalk remove this thread for copyright violations in 24 hours if the complete corresponding source code to the distributed firmware binaries is not uploaded by then. I am a one of a number of cgminer copyright holders.

Yeah man. Definitely take a breather. The guys probably got a day job and f doing this on the side. He's done some great work, I do understand where you're coming from, but the only other people in the space want 40+ dollars per machine to download their firmware.
Having a decently open dev working on this is pretty nice for all if us.


Title: Re: Antminer L3+ Blissz firmware (14/01/2018 v1.02 stable)
Post by: blissz on January 18, 2018, 10:11:36 AM
Hi all,

As you might have noticed there is some discussion going on about the GPL license of the cgminer software that's used in my firmware.
I was not aware of this GPL license, but I am now, and I am quite sure the source should be published.
As I don't have enough time to do it now and want to do it properly I decided to temporary remove the download link to the modified firmware and lock the topic until this GPL issue is resolved. This will prevent that this topic get's locked / removed for ever and valuable information gets lost.
I hope I can resolve this issue as soon as possible. Sorry for the inconvenience,

ciao Blissz

ps. Please respect this and don't PM me for links to the firmware.