OpenWrt Forum Archive

Topic: davidc502 1900ac 3200acm builds

The content of this topic has been archived between 26 Feb 2018 and 7 May 2018. Unfortunately there are posts – most likely complete pages – missing.

davidc502 wrote:

Actually, the server network was down for around an hour. It's back up now.

I've been working on a new build, but can't release it because users on the 1900ac V1 would likely have serious issues. Will be monitoring over the next few days to hear if there's a fix being worked on. If not, I'll revert the major kernel change, before rebuilding.

@davidc502, I'm happy to test your 4.9.* build on my v1 and I have usb to serial adapter in case it doesn't go well.

I've tested the official LEDE (4.9) builds a couple of times and haven't had much luck with them. It flashes fine and I can get all my packages installed but I get random reboots (longest uptime ~1hr).

(Last edited by listerwrt on 22 Feb 2017, 15:39)

CC with kernel 3.18.36 with all your settings is still on the router. Use the recovery method to revert back to it.

Hey man,

thanks that worked!

I'm back to the Chaos Calmer [CC] Build, my question now is how do i fix the other partition where I installed your LEDE version?

Should I just flash the stock firmware again and then try to flash your LEDE version afterwards?

If I flash the stock version in the Chaos Calmer build will it put it on the other partition (like it did when I flashed the LEDE FW)?

Do you have any idea if my Issue was caused because I went from the chaos calmer build to LEDE (instead through the stock and then to LEDE)

Many thanks for the support and sorry for the noob questions.

(Last edited by tsuri19 on 22 Feb 2017, 17:01)

listerwrt wrote:
davidc502 wrote:

Actually, the server network was down for around an hour. It's back up now.

I've been working on a new build, but can't release it because users on the 1900ac V1 would likely have serious issues. Will be monitoring over the next few days to hear if there's a fix being worked on. If not, I'll revert the major kernel change, before rebuilding.

@davidc502, I'm happy to test your 4.9.* build on my v1 and I have usb to serial adapter in case it doesn't go well.

I've tested the official LEDE (4.9) builds a couple of times and haven't had much luck with them. It flashes fine and I can get all my packages installed but I get random reboots (longest uptime ~1hr).

Okay, I've put the images and packages on the server. Please download v1 images, and let me know when you've done so.  I plan to keep the images from being downloadable unless by request.

https://davidc502sis.dynamic-dns.net/sn … u/generic/

I'm trying to setup two local (NAT'ed) networks, both 192.168.1.x and 10.1.1.x
I've done this on an older box using the switch config, but it turns out switch config is not supported on the Linksys AC series (too bad).
Does anyone have suggestions for me how I might do this with the wrt3200acm?
Alternatively, are there any widely available gigabit routers that run OpenWRT well and that supports switch configuration (with per-port VLAN settings)?
Thanks

[ Follow-up:  The LEDE build appears to support the network/switch tab on the wrt3200acm
Trying that now... ]

(Last edited by gordon4959 on 22 Feb 2017, 18:47)

tsuri19 wrote:

CC with kernel 3.18.36 with all your settings is still on the router. Use the recovery method to revert back to it.

Hey man,

thanks that worked!

I'm back to the Chaos Calmer [CC] Build, my question now is how do i fix the other partition where I installed your LEDE version?

Should I just flash the stock firmware again and then try to flash your LEDE version afterwards?

If I flash the stock version in the Chaos Calmer build will it put it on the other partition (like it did when I flashed the LEDE FW)?

Do you have any idea if my Issue was caused because I went from the chaos calmer build to LEDE (instead through the stock and then to LEDE)

Many thanks for the support and sorry for the noob questions.

You can go back and forth between partitions as many times as you want. Just do the recovery procedure to go back to LEDE or there is a SSH command  to boot to the other partition as it's easier to SSH then to turn off and on 4 times..

Actually, there would have been no difference if you would have flashed from the Stock Firmware. This is because there have been a few others who have had issues with PPOE with some of the latest LEDE builds. If you're interested in getting it fixed, I would recommend creating an account over at the LEDE forum, and describe the issue, and see if it's something one of the developers would pick up. They may ask your help in troubleshooting to figure out how to patch the problem.

Also, you can fail over to LEDE and see if there's anything in the system logs on why it can't connect to PPOE. Otherwise you can leave LEDE on the other partition as it isn't going to hurt anything.

By the way, everyone starts at ground zero sometime... Don't worry about your questions as we don't judge here smile

Best Regards,

davidc502 wrote:
tsuri19 wrote:

CC with kernel 3.18.36 with all your settings is still on the router. Use the recovery method to revert back to it.

Hey man,

thanks that worked!

I'm back to the Chaos Calmer [CC] Build, my question now is how do i fix the other partition where I installed your LEDE version?

Should I just flash the stock firmware again and then try to flash your LEDE version afterwards?

If I flash the stock version in the Chaos Calmer build will it put it on the other partition (like it did when I flashed the LEDE FW)?

Do you have any idea if my Issue was caused because I went from the chaos calmer build to LEDE (instead through the stock and then to LEDE)

Many thanks for the support and sorry for the noob questions.

You can go back and forth between partitions as many times as you want. Just do the recovery procedure to go back to LEDE or there is a SSH command  to boot to the other partition as it's easier to SSH then to turn off and on 4 times..

Actually, there would have been no difference if you would have flashed from the Stock Firmware. This is because there have been a few others who have had issues with PPOE with some of the latest LEDE builds. If you're interested in getting it fixed, I would recommend creating an account over at the LEDE forum, and describe the issue, and see if it's something one of the developers would pick up. They may ask your help in troubleshooting to figure out how to patch the problem.

Also, you can fail over to LEDE and see if there's anything in the system logs on why it can't connect to PPOE. Otherwise you can leave LEDE on the other partition as it isn't going to hurt anything.

By the way, everyone starts at ground zero sometime... Don't worry about your questions as we don't judge here smile

Best Regards,

Thanks a lot for all the info it's really worth gold to me!

Do you know why the flashing of a different firmware in the LEDE GUI produces the error I described in my first post?
Basically at the moment one of my partitions is stuck with the LEDE firmware.
Is there some other way to overwrite the LEDE build with the firmware of my choice?

tsuri19 wrote:
davidc502 wrote:
tsuri19 wrote:

Hey man,

thanks that worked!

I'm back to the Chaos Calmer [CC] Build, my question now is how do i fix the other partition where I installed your LEDE version?

Should I just flash the stock firmware again and then try to flash your LEDE version afterwards?

If I flash the stock version in the Chaos Calmer build will it put it on the other partition (like it did when I flashed the LEDE FW)?

Do you have any idea if my Issue was caused because I went from the chaos calmer build to LEDE (instead through the stock and then to LEDE)

Many thanks for the support and sorry for the noob questions.

You can go back and forth between partitions as many times as you want. Just do the recovery procedure to go back to LEDE or there is a SSH command  to boot to the other partition as it's easier to SSH then to turn off and on 4 times..

Actually, there would have been no difference if you would have flashed from the Stock Firmware. This is because there have been a few others who have had issues with PPOE with some of the latest LEDE builds. If you're interested in getting it fixed, I would recommend creating an account over at the LEDE forum, and describe the issue, and see if it's something one of the developers would pick up. They may ask your help in troubleshooting to figure out how to patch the problem.

Also, you can fail over to LEDE and see if there's anything in the system logs on why it can't connect to PPOE. Otherwise you can leave LEDE on the other partition as it isn't going to hurt anything.

By the way, everyone starts at ground zero sometime... Don't worry about your questions as we don't judge here smile

Best Regards,

Thanks a lot for all the info it's really worth gold to me!

Do you know why the flashing of a different firmware in the LEDE GUI produces the error I described in my first post?
Basically at the moment one of my partitions is stuck with the LEDE firmware.
Is there some other way to overwrite the LEDE build with the firmware of my choice?

Yes, flashing via the gui is broke, but the developers are aware and I believe have submitted a patch for the fix. Unknown on when it will be in the next release though. However, you can still flash by transferring a new image over to the router's /tmp directory, and issuing the "sysupgrade -F  /tmp/image_name.bin"  The sysupgrade method does work in flashing a new image to the other partition.

To your second question... Yes, from C.C. you can flash another image, and it will over-write whatever is on the other partition.

The way it works....  if you're on partition 1 it over writes partition 2. If you're on partition 2, it over writes partition 1.

(Last edited by davidc502 on 22 Feb 2017, 20:25)

davidc502 wrote:
tsuri19 wrote:
davidc502 wrote:

You can go back and forth between partitions as many times as you want. Just do the recovery procedure to go back to LEDE or there is a SSH command  to boot to the other partition as it's easier to SSH then to turn off and on 4 times..

Actually, there would have been no difference if you would have flashed from the Stock Firmware. This is because there have been a few others who have had issues with PPOE with some of the latest LEDE builds. If you're interested in getting it fixed, I would recommend creating an account over at the LEDE forum, and describe the issue, and see if it's something one of the developers would pick up. They may ask your help in troubleshooting to figure out how to patch the problem.

Also, you can fail over to LEDE and see if there's anything in the system logs on why it can't connect to PPOE. Otherwise you can leave LEDE on the other partition as it isn't going to hurt anything.

By the way, everyone starts at ground zero sometime... Don't worry about your questions as we don't judge here smile

Best Regards,

Thanks a lot for all the info it's really worth gold to me!

Do you know why the flashing of a different firmware in the LEDE GUI produces the error I described in my first post?
Basically at the moment one of my partitions is stuck with the LEDE firmware.
Is there some other way to overwrite the LEDE build with the firmware of my choice?

Yes, flashing via the gui is broke, but the developers are aware and I believe have submitted a patch for the fix. Unknown on when it will be in the next release though. However, you can still flash by transferring a new image over to the router's /tmp directory, and issuing the "sysupgrade -F  /tmp/image_name.bin"  The sysupgrade method does work in flashing a new image to the other partition.

To your second question... Yes, from C.C. you can flash another image, and it will over-write whatever is on the other partition.

The way it works....  if you're on partition 1 it over writes partition 2. If you're on partition 2, it over writes partition 1.

great this makes things so much clearer!

Thanks

Lazy I'm just gonna ask if @davidc502 if he considers his current LEDE build a daily driver candidate? I'm thinking of replacing the 1900 with the 3200 as the main router in the house. I'm aware of the flashing/upgrade issue. Just wondering if there are any other major issues to be aware of?

Redferne wrote:

Lazy I'm just gonna ask if @davidc502 if he considers his current LEDE build a daily driver candidate? I'm thinking of replacing the 1900 with the 3200 as the main router in the house. I'm aware of the flashing/upgrade issue. Just wondering if there are any other major issues to be aware of?

IMHO - Yes, the LEDE build is a daily home driver for the 1900 series.     However! wifi is still being worked on for the 3200acm, but is nearing completion. Keep in mind, when the new wifi driver is release there will probably be a few bugs to work out.

If you can get the 3200acm, I recommend one, but keep the 1900ac as your regular workhorse until the wifi driver is completed.

As of yesterday this was a comment from a Linksys developer who is working on the new 3200acm driver --

"Re-architecture is done. Adding support for the same firmware used by stock firmware to this new architecture now."

So, it probably won't be too much longer before wifi is working on the 3200.

**EDIT**

One other thing worth mentioning... If you need switch configurations on the 3200acm, that may not be working right now. There are plans to get it working with the new chipset, but there may be delays.

another **EDIT**

There is a separate flash warning I have issued for the 3200acm. After flashing to LEDE from the stock firmware, to flash again, you will probably need to use the USB/TTL method. In other words, the GUI and sysupgrade may be broke. Others have noticed the same issue, and someone is probably working on a fix.

(Last edited by davidc502 on 22 Feb 2017, 23:40)

davidc502 wrote:
listerwrt wrote:
davidc502 wrote:

Actually, the server network was down for around an hour. It's back up now.

I've been working on a new build, but can't release it because users on the 1900ac V1 would likely have serious issues. Will be monitoring over the next few days to hear if there's a fix being worked on. If not, I'll revert the major kernel change, before rebuilding.

@davidc502, I'm happy to test your 4.9.* build on my v1 and I have usb to serial adapter in case it doesn't go well.

I've tested the official LEDE (4.9) builds a couple of times and haven't had much luck with them. It flashes fine and I can get all my packages installed but I get random reboots (longest uptime ~1hr).

Okay, I've put the images and packages on the server. Please download v1 images, and let me know when you've done so.  I plan to keep the images from being downloadable unless by request.

https://davidc502sis.dynamic-dns.net/sn … u/generic/

Downloaded. It booted and logs look normal, I'll keep you posted on uptime. Was there anything else you wanted to test?

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.9.10 (ag33e33@ubuntu) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3526-bececcc) ) #0 SMP Sat Feb 18 15:51:31 2017
[    0.000000] CPU: ARMv7 Processor [562f5842] revision 2 (ARMv7), cr=10c5387d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000] OF: fdt:Machine model: Linksys WRT1900AC
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 65536
[    0.000000] free_area_init_node: node 0, pgdat c0644900, node_mem_map cfdf9000
[    0.000000]   Normal zone: 512 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 65536 pages, LIFO batch:15
[    0.000000] percpu: Embedded 13 pages/cpu @cfdcf000 s22732 r8192 d22324 u53248
[    0.000000] pcpu-alloc: s22732 r8192 d22324 u53248 alloc=13*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
[    0.000000] Kernel command line: console=ttyS0,115200 mtdparts=armada-nand:1024K(uboot)ro,256K(u_env),256K(s_env),1m@9m(devinfo),40m@10m(kernel),37m@13m(rootfs),40m@50m(alt_kernel),37m@53m(alt_rootfs),80m@10m(ubifs),-@90m(syscfg) root=/dev/mtdblock7 ro rootfstype=jffs2 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] Memory: 252952K/262144K available (4541K kernel code, 180K rwdata, 1244K rodata, 276K init, 310K bss, 9192K reserved, 0K cma-reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                   vmalloc : 0xd0800000 - 0xff800000   ( 752 MB)
                   lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
                   pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
                   modules : 0xbf000000 - 0xbfe00000   (  14 MB)
                     .text : 0xc0008000 - 0xc04777f0   (4542 kB)
                     .init : 0xc05d3000 - 0xc0618000   ( 276 kB)
                     .data : 0xc0618000 - 0xc0645200   ( 181 kB)
                      .bss : 0xc0645200 - 0xc0692a00   ( 310 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] Aurora cache controller enabled, 32 ways, 2048 kB
[    0.000000] Aurora: CACHE_ID 0x00000100, AUX_CTRL 0x1a69ef12
[    0.000000] Switching to timer-based delay loop, resolution 40ns
[    0.000005] sched_clock: 32 bits at 25MHz, resolution 40ns, wraps every 85899345900ns
[    0.000016] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 76450417870 ns
[    0.000212] Calibrating delay loop (skipped), value calculated using timer frequency.. 50.00 BogoMIPS (lpj=250000)
[    0.000223] pid_max: default: 32768 minimum: 301
[    0.000286] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000294] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000627] CPU: Testing write buffer coherency: ok
[    0.000778] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.000902] Setting up static identity map for 0x8280 - 0x82d8
[    0.001141] mvebu-soc-id: MVEBU SoC ID=0x7823, Rev=0x2
[    0.001242] mvebu-pmsu: Initializing Power Management Service Unit
[    0.002110] Booting CPU 1
[    0.004524] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.004592] Brought up 2 CPUs
[    0.004603] SMP: Total of 2 processors activated (100.00 BogoMIPS).
[    0.004608] CPU: All CPU(s) started in SVC mode.
[    0.008056] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6
[    0.008156] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.008185] pinctrl core: initialized pinctrl subsystem
[    0.008784] NET: Registered protocol family 16
[    0.009007] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.030073] cpuidle: using governor ladder
[    0.061026] SCSI subsystem initialized
[    0.061209] libata version 3.00 loaded.
[    0.061410] usbcore: registered new interface driver usbfs
[    0.061463] usbcore: registered new interface driver hub
[    0.061508] usbcore: registered new device driver usb
[    0.062351] clocksource: Switched to clocksource armada_370_xp_clocksource
[    0.062953] NET: Registered protocol family 2
[    0.063339] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[    0.063363] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
[    0.063386] TCP: Hash tables configured (established 2048 bind 2048)
[    0.063421] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.063436] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.063527] NET: Registered protocol family 1
[    0.063548] PCI: CLS 0 bytes, default 64
[    0.064621] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.064678] Crashlog allocated RAM at address 0x3f00000
[    0.065210] workingset: timestamp_bits=30 max_order=16 bucket_order=0
[    0.069734] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.069742] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.071491] io scheduler noop registered
[    0.071499] io scheduler deadline registered (default)
[    0.072077] armada-xp-pinctrl f1018000.pin-ctrl: registered pinctrl driver
[    0.073355] mvebu-pcie soc:pcie-controller: PCI host bridge to bus 0000:00
[    0.073368] pci_bus 0000:00: root bus resource [io  0x1000-0xfffff]
[    0.073377] pci_bus 0000:00: root bus resource [mem 0xf8000000-0xffdfffff]
[    0.073386] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.073412] pci 0000:00:01.0: [11ab:7823] type 01 class 0x060400
[    0.073576] pci 0000:00:02.0: [11ab:7823] type 01 class 0x060400
[    0.073728] pci 0000:00:03.0: [11ab:7823] type 01 class 0x060400
[    0.073882] PCI: bus0: Fast back to back transfers disabled
[    0.073893] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.073905] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.073915] pci 0000:00:03.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.074013] pci 0000:01:00.0: [1b6f:7023] type 00 class 0x0c0330
[    0.074040] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00007fff 64bit]
[    0.074133] pci 0000:01:00.0: supports D1 D2
[    0.074139] pci 0000:01:00.0: PME# supported from D0 D1 D2 D3hot
[    0.074266] PCI: bus1: Fast back to back transfers disabled
[    0.074278] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    0.074380] pci 0000:02:00.0: [11ab:2a55] type 00 class 0x020000
[    0.074406] pci 0000:02:00.0: reg 0x10: [mem 0x00000000-0x000fffff 64bit pref]
[    0.074423] pci 0000:02:00.0: reg 0x18: [mem 0x00000000-0x000fffff 64bit pref]
[    0.074517] pci 0000:02:00.0: supports D1 D2
[    0.074523] pci 0000:02:00.0: PME# supported from D0 D1 D3hot D3cold
[    0.074647] PCI: bus2: Fast back to back transfers disabled
[    0.074658] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[    0.074758] pci 0000:03:00.0: [11ab:2a55] type 00 class 0x020000
[    0.074782] pci 0000:03:00.0: reg 0x10: [mem 0x00000000-0x000fffff 64bit pref]
[    0.074797] pci 0000:03:00.0: reg 0x18: [mem 0x00000000-0x000fffff 64bit pref]
[    0.074878] pci 0000:03:00.0: supports D1 D2
[    0.074884] pci 0000:03:00.0: PME# supported from D0 D1 D3hot D3cold
[    0.075005] PCI: bus3: Fast back to back transfers disabled
[    0.075016] pci_bus 0000:03: busn_res: [bus 03-ff] end is updated to 03
[    0.075196] pci 0000:00:01.0: BAR 8: assigned [mem 0xf8000000-0xf80fffff]
[    0.075208] pci 0000:00:02.0: BAR 8: assigned [mem 0xf8200000-0xf83fffff]
[    0.075218] pci 0000:00:03.0: BAR 8: assigned [mem 0xf8400000-0xf85fffff]
[    0.075230] pci 0000:01:00.0: BAR 0: assigned [mem 0xf8000000-0xf8007fff 64bit]
[    0.075247] pci 0000:00:01.0: PCI bridge to [bus 01]
[    0.075258] pci 0000:00:01.0:   bridge window [mem 0xf8000000-0xf80fffff]
[    0.075271] pci 0000:02:00.0: BAR 0: assigned [mem 0xf8200000-0xf82fffff 64bit pref]
[    0.075288] pci 0000:02:00.0: BAR 2: assigned [mem 0xf8300000-0xf83fffff 64bit pref]
[    0.075304] pci 0000:00:02.0: PCI bridge to [bus 02]
[    0.075313] pci 0000:00:02.0:   bridge window [mem 0xf8200000-0xf83fffff]
[    0.075326] pci 0000:03:00.0: BAR 0: assigned [mem 0xf8400000-0xf84fffff 64bit pref]
[    0.075343] pci 0000:03:00.0: BAR 2: assigned [mem 0xf8500000-0xf85fffff 64bit pref]
[    0.075357] pci 0000:00:03.0: PCI bridge to [bus 03]
[    0.075366] pci 0000:00:03.0:   bridge window [mem 0xf8400000-0xf85fffff]
[    0.075414] pci 0000:00:01.0: enabling device (0140 -> 0142)
[    0.075436] pci 0000:01:00.0: enabling device (0140 -> 0142)
[    0.075822] mv_xor f1060900.xor: Marvell shared XOR driver
[    0.133052] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    0.133167] mv_xor f10f0900.xor: Marvell shared XOR driver
[    0.193043] mv_xor f10f0900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    0.193238] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.194849] console [ttyS0] disabled
[    0.214967] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 19, base_baud = 15625000) is a 16550A
[    0.916299] console [ttyS0] enabled
[    0.923690] loop: module loaded
[    0.927216] sata_mv f10a0000.sata: version 1.28
[    0.927340] sata_mv f10a0000.sata: slots 32 ports 1
[    0.932736] scsi host0: sata_mv
[    0.936048] ata1: SATA max UDMA/133 irq 28
[    0.940542] pxa3xx-nand f10d0000.nand: This platform can't do DMA on this device
[    0.948457] nand: device found, Manufacturer ID: 0x01, Chip ID: 0xf1
[    0.954846] nand: AMD/Spansion S34ML01G1
[    0.958781] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    0.966391] pxa3xx-nand f10d0000.nand: ECC strength 16, ECC step size 2048
[    0.973597] Bad block table found at page 65472, version 0x01
[    0.979875] Bad block table found at page 65408, version 0x01
[    0.986076] 10 ofpart partitions found on MTD device pxa3xx_nand-0
[    0.992274] Creating 10 MTD partitions on "pxa3xx_nand-0":
[    0.997794] 0x000000000000-0x000000100000 : "u-boot"
[    1.003344] 0x000000100000-0x000000140000 : "u_env"
[    1.008752] 0x000000140000-0x000000180000 : "s_env"
[    1.014159] 0x000000900000-0x000000a00000 : "devinfo"
[    1.019723] 0x000000a00000-0x000003200000 : "kernel1"
[    1.025517] 0x000000d00000-0x000003200000 : "rootfs1"
[    1.031288] 0x000003200000-0x000005a00000 : "kernel2"
[    1.037094] 0x000003500000-0x000005a00000 : "ubi"
[    1.042526] 0x000005a00000-0x000008000000 : "syscfg"
[    1.048201] 0x000000180000-0x000000900000 : "unused_area"
[    1.054944] m25p80 spi0.0: mr25h256 (32 Kbytes)
[    1.060386] libphy: Fixed MDIO Bus: probed
[    1.064953] libphy: orion_mdio_bus: probed
[    1.069297] mvneta_bm f10c0000.bm: Buffer Manager for network controller enabled
[    1.079511] mvneta f1070000.ethernet eth0: Using random mac address 72:bd:76:4a:6f:1f
[    1.089410] mvneta f1074000.ethernet eth1: Using random mac address 4a:78:00:2b:29:1d
[    1.097365] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.103925] ehci-pci: EHCI PCI platform driver
[    1.108426] ehci-platform: EHCI generic platform driver
[    1.113805] ehci-orion: EHCI orion driver
[    1.117914] orion-ehci f1050000.usb: EHCI Host Controller
[    1.123369] orion-ehci f1050000.usb: new USB bus registered, assigned bus number 1
[    1.131020] orion-ehci f1050000.usb: irq 25, io mem 0xf1050000
[    1.162348] orion-ehci f1050000.usb: USB 2.0 started, EHCI 1.00
[    1.168731] hub 1-0:1.0: USB hub found
[    1.172551] hub 1-0:1.0: 1 port detected
[    1.176776] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    1.182031] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[    1.189586] xhci_hcd 0000:01:00.0: hcc params 0x040050af hci version 0x100 quirks 0x00080490
[    1.198601] hub 2-0:1.0: USB hub found
[    1.202412] hub 2-0:1.0: 2 ports detected
[    1.206652] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    1.211901] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 3
[    1.219398] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.227917] hub 3-0:1.0: USB hub found
[    1.231706] hub 3-0:1.0: 2 ports detected
[    1.236306] usbcore: registered new interface driver usb-storage
[    1.242613] i2c /dev entries driver
[    1.248258] orion_wdt: Initial timeout 171 sec
[    1.253378] of: dev_pm_opp_of_cpumask_add_table: couldn't find opp table for cpu:0, -19
[    1.261415] cpu cpu1: opp_list_debug_create_link: Failed to create link
[    1.268066] cpu cpu1: _add_opp_dev: Failed to register opp debugfs (-12)
[    1.268787] ata1: SATA link down (SStatus 0 SControl F300)
[    1.282612] sdhci: Secure Digital Host Controller Interface driver
[    1.288817] sdhci: Copyright(c) Pierre Ossman
[    1.293529] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.304344] marvell-cesa f1090000.crypto: CESA device successfully registered
[    1.312804] NET: Registered protocol family 10
[    1.318226] NET: Registered protocol family 17
[    1.322729] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    1.335744] 8021q: 802.1Q VLAN Support v1.8
[    1.340031] Registering SWP/SWPB emulation handler
[    1.347074] UBI: auto-attach mtd7
[    1.350229] ubi0: attaching mtd7
[    1.369509] random: fast init done
[    1.560169] ubi0: scanning is finished
[    1.572112] ubi0: attached mtd7 (name "ubi", size 37 MiB)
[    1.577550] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    1.584452] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    1.591259] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[    1.598248] ubi0: good PEBs: 296, bad PEBs: 0, corrupted PEBs: 0
[    1.604278] ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128
[    1.611521] ubi0: max/mean erase counter: 17/11, WL threshold: 4096, image sequence number: 1685340794
[    1.620865] ubi0: available PEBs: 0, total reserved PEBs: 296, PEBs reserved for bad PEB handling: 20
[    1.630146] ubi0: background thread "ubi_bgt0d" started, PID 637
[    1.636762] block ubiblock0_0: created from ubi0:0(rootfs)
[    1.642265] ubiblock: device ubiblock0_0 (rootfs) set to be root filesystem
[    1.649505] mvsw61xx 1000000003.mvsw61xx: Found MV88E6172 at f1072004.mdio-mi:10
[    1.656941] mvsw61xx 1000000003.mvsw61xx: Using direct addressing
[    1.673117] hctosys: unable to open rtc device (rtc0)
[    1.681907] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[    1.689368] Freeing unused kernel memory: 276K (c05d3000 - c0618000)
[    1.695753] This architecture does not have kernel memory protection.
[    2.016428] init: Console is alive
[    2.019997] init: - watchdog -
[    2.513613] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    2.573890] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    2.580456] ohci-platform: OHCI generic platform driver
[    2.586407] uhci_hcd: USB Universal Host Controller Interface driver
[    2.593240] ohci-pci: OHCI PCI platform driver
[    2.597892] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    2.614951] init: - preinit -
[    3.977210] mvneta f1070000.ethernet eth0: configuring for fixed link mode
[    3.984931] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    3.991127] mvneta f1070000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[    4.000722] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    6.155415] mount_root: loading kmods from internal overlay
[    6.182646] kmodloader: loading kernel modules from //etc/modules-boot.d/*
[    6.191862] kmodloader: done loading kernel modules from //etc/modules-boot.d/*
[    6.820415] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 752
[    6.937536] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
[    6.945463] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    6.955467] UBIFS (ubi0:1): FS size: 26664960 bytes (25 MiB, 210 LEBs), journal size 1396736 bytes (1 MiB, 11 LEBs)
[    6.965986] UBIFS (ubi0:1): reserved for root: 1259451 bytes (1229 KiB)
[    6.972680] UBIFS (ubi0:1): media format: w4/r0 (latest is w4/r0), UUID D49D5549-5F23-49B0-AE25-63B7F293B07A, small LPT model
[    6.984996] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
[    6.992156] block: unable to load configuration (fstab: Entry not found)
[    6.999085] block: attempting to load /tmp/ubifs_cfg/etc/config/fstab
[    7.005773] block: unable to load configuration (fstab: Entry not found)
[    7.012658] block: attempting to load /etc/config/fstab
[    7.021886] block: unable to load configuration (fstab: Entry not found)
[    7.028866] block: no usable configuration
[    7.085385] UBIFS (ubi0:1): un-mount UBI device 0
[    7.090185] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" stops
[    7.102169] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 755
[    7.219517] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
[    7.227445] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    7.237447] UBIFS (ubi0:1): FS size: 26664960 bytes (25 MiB, 210 LEBs), journal size 1396736 bytes (1 MiB, 11 LEBs)
[    7.248033] UBIFS (ubi0:1): reserved for root: 1259451 bytes (1229 KiB)
[    7.254740] UBIFS (ubi0:1): media format: w4/r0 (latest is w4/r0), UUID D49D5549-5F23-49B0-AE25-63B7F293B07A, small LPT model
[    7.788772] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
[    7.796010] block: unable to load configuration (fstab: Entry not found)
[    7.802908] block: attempting to load /tmp/ubifs_cfg/etc/config/fstab
[    7.809534] block: unable to load configuration (fstab: Entry not found)
[    7.816420] block: attempting to load /etc/config/fstab
[    7.821797] block: unable to load configuration (fstab: Entry not found)
[    7.828668] block: no usable configuration
[    7.873201] mount_root: overlay filesystem has not been fully initialized yet
[    7.881792] mount_root: switching to ubifs overlay
[    7.920778] random: crng init done
[    8.084808] ubi1: attaching mtd8
[    8.333219] ubi1: scanning is finished
[    8.346599] ubi1 warning: ubi_eba_init: cannot reserve enough PEBs for bad PEB handling, reserved 2, need 12
[    8.357182] ubi1: attached mtd8 (name "syscfg", size 38 MiB)
[    8.362915] ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[    8.369822] ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[    8.376671] ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
[    8.383689] ubi1: good PEBs: 296, bad PEBs: 8, corrupted PEBs: 0
[    8.389716] ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
[    8.396992] ubi1: max/mean erase counter: 76/73, WL threshold: 4096, image sequence number: 687528873
[    8.406273] ubi1: available PEBs: 0, total reserved PEBs: 296, PEBs reserved for bad PEB handling: 2
[    8.415492] ubi1: background thread "ubi_bgt1d" started, PID 769
[    8.435362] UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 774
[    8.521302] UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "syscfg"
[    8.528807] UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[    8.538812] UBIFS (ubi1:0): FS size: 35680256 bytes (34 MiB, 281 LEBs), journal size 1777664 bytes (1 MiB, 14 LEBs)
[    8.549349] UBIFS (ubi1:0): reserved for root: 1685265 bytes (1645 KiB)
[    8.556043] UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 854C2D23-2108-4E2A-AE06-78D7120E32CC, small LPT model
[    8.730422] urandom-seed: Seed file not found (/etc/urandom.seed)
[    8.839971] procd: - early -
[    8.843504] procd: - watchdog -
[    9.580124] procd: - ubus -
[    9.735524] procd: - init -
[   10.165927] kmodloader: loading kernel modules from /etc/modules.d/*
[   10.186386] tun: Universal TUN/TAP device driver, 1.6
[   10.191467] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[   10.201991] Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
[   10.214337] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   10.225322] cryptodev: driver 1.8 loaded.
[   10.230293] Loading modules backported from Linux version wt-2017-01-31-0-ge882dff19e7f
[   10.238404] Backport generated by backports.git backports-20160324-13-g24da7d3c
[   10.259798] <<Marvell 802.11ac Wireless Network Driver version 10.3.2.0-20170110>>
[   10.267517] pci 0000:00:02.0: enabling device (0140 -> 0142)
[   10.273283] mwlwifi 0000:02:00.0: enabling device (0140 -> 0142)
[   10.279452] ieee80211 phy0: priv->iobase0 = d0f80000
[   10.279479] ieee80211 phy0: priv->iobase1 = d1100000
[   10.279499] ieee80211 phy0: priv->pcmd_buf = ce200000  priv->pphys_cmd_buf = 0e200000
[   10.342431] ieee80211 phy0: fw download start
[   10.460806] ieee80211 phy0: FwSize = 118776 downloaded Size = 118776 curr_iteration 65511
[   11.322457] ieee80211 phy0: fw download complete
[   11.323337] ieee80211 phy0: pcmd = ce200000
[   11.341625] ieee80211 phy0: firmware version: 0x702091a
[   11.365316] ieee80211 phy0: firmware region code: 0
[   11.394688] ieee80211 phy0: regdomain: FCC
[   11.394701] ieee80211 phy0: Channel: 1: 0x0 0x0 0xf
[   11.394713] ieee80211 phy0: 17 11 11 11 10 10 10 10 f f f f 0 0 0 0
[   11.394719] ieee80211 phy0: Channel: 2: 0x0 0x0 0xf
[   11.394731] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0
[   11.394737] ieee80211 phy0: Channel: 3: 0x0 0x0 0xf
[   11.394748] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0
[   11.394754] ieee80211 phy0: Channel: 4: 0x0 0x0 0xf
[   11.394766] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0
[   11.394772] ieee80211 phy0: Channel: 5: 0x0 0x0 0xf
[   11.394783] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0
[   11.394789] ieee80211 phy0: Channel: 6: 0x0 0x0 0xf
[   11.394801] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0
[   11.394807] ieee80211 phy0: Channel: 7: 0x0 0x0 0xf
[   11.394819] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0
[   11.394824] ieee80211 phy0: Channel: 8: 0x0 0x0 0xf
[   11.394836] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0
[   11.394842] ieee80211 phy0: Channel: 9: 0x0 0x0 0xf
[   11.394853] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0
[   11.394860] ieee80211 phy0: Channel: 10: 0x0 0x0 0xf
[   11.394871] ieee80211 phy0: 17 16 16 16 16 16 16 14 10 10 10 10 0 0 0 0
[   11.394878] ieee80211 phy0: Channel: 11: 0x0 0x0 0xf
[   11.394889] ieee80211 phy0: 17 11 11 11 11 11 11 11 10 10 10 10 0 0 0 0
[   11.396275] ieee80211 phy0: 2G enabled, 5G disabled
[   11.401190] ieee80211 phy0: 4 TX antennas, 4 RX antennas
[   11.406724] pci 0000:00:03.0: enabling device (0140 -> 0142)
[   11.412481] mwlwifi 0000:03:00.0: enabling device (0140 -> 0142)
[   11.418627] ieee80211 phy1: priv->iobase0 = d1280000
[   11.418656] ieee80211 phy1: priv->iobase1 = d1400000
[   11.418679] ieee80211 phy1: priv->pcmd_buf = ce204000  priv->pphys_cmd_buf = 0e204000
[   11.425488] ieee80211 phy1: fw download start
[   11.542617] ieee80211 phy1: FwSize = 118776 downloaded Size = 118776 curr_iteration 65499
[   12.418502] ieee80211 phy1: fw download complete
[   12.419391] ieee80211 phy1: pcmd = ce204000
[   12.437529] ieee80211 phy1: firmware version: 0x702091a
[   12.461229] ieee80211 phy1: firmware region code: 0
[   12.490832] ieee80211 phy1: regdomain: FCC
[   12.490845] ieee80211 phy1: Channel: 36: 0x0 0x0 0xf
[   12.490857] ieee80211 phy1: 8 8 8 8 8 8 8 8 9 9 9 9 9 9 9 9
[   12.490863] ieee80211 phy1: Channel: 40: 0x0 0x0 0xf
[   12.490874] ieee80211 phy1: 8 8 8 8 9 9 9 9 9 9 9 9 9 9 9 9
[   12.490881] ieee80211 phy1: Channel: 44: 0x0 0x0 0xf
[   12.490892] ieee80211 phy1: 8 8 8 8 9 9 9 9 9 9 9 9 9 9 9 9
[   12.490898] ieee80211 phy1: Channel: 48: 0x0 0x0 0xf
[   12.490909] ieee80211 phy1: 8 8 8 8 9 9 9 9 9 9 9 9 9 9 9 9
[   12.490915] ieee80211 phy1: Channel: 52: 0x0 0x0 0xf
[   12.490927] ieee80211 phy1: f f f f f f f f 12 12 12 12 12 12 12 12
[   12.490932] ieee80211 phy1: Channel: 56: 0x0 0x0 0xf
[   12.490944] ieee80211 phy1: f f f f f f f f 12 12 12 12 12 12 12 12
[   12.490950] ieee80211 phy1: Channel: 60: 0x0 0x0 0xf
[   12.490961] ieee80211 phy1: f f f f f f f f 12 12 12 12 12 12 12 12
[   12.490967] ieee80211 phy1: Channel: 64: 0x0 0x0 0xf
[   12.490979] ieee80211 phy1: f f f f f f f f 12 12 12 12 12 12 12 12
[   12.490985] ieee80211 phy1: Channel: 100: 0x0 0x0 0xf
[   12.490997] ieee80211 phy1: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14
[   12.491003] ieee80211 phy1: Channel: 104: 0x0 0x0 0xf
[   12.491015] ieee80211 phy1: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14
[   12.491021] ieee80211 phy1: Channel: 108: 0x0 0x0 0xf
[   12.491032] ieee80211 phy1: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14
[   12.491038] ieee80211 phy1: Channel: 112: 0x0 0x0 0xf
[   12.491050] ieee80211 phy1: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14
[   12.491056] ieee80211 phy1: Channel: 116: 0x0 0x0 0xf
[   12.491068] ieee80211 phy1: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14
[   12.491074] ieee80211 phy1: Channel: 120: 0x0 0x0 0xf
[   12.491086] ieee80211 phy1: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14
[   12.491092] ieee80211 phy1: Channel: 124: 0x0 0x0 0xf
[   12.491104] ieee80211 phy1: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14
[   12.491109] ieee80211 phy1: Channel: 128: 0x0 0x0 0xf
[   12.491121] ieee80211 phy1: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14
[   12.491127] ieee80211 phy1: Channel: 132: 0x0 0x0 0xf
[   12.491139] ieee80211 phy1: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14
[   12.491145] ieee80211 phy1: Channel: 136: 0x0 0x0 0xf
[   12.491157] ieee80211 phy1: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14
[   12.491163] ieee80211 phy1: Channel: 140: 0x0 0x0 0xf
[   12.491175] ieee80211 phy1: 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14 14
[   12.491181] ieee80211 phy1: Channel: 149: 0x0 0x0 0xf
[   12.491193] ieee80211 phy1: 16 16 16 16 14 14 14 14 15 15 15 15 14 14 14 14
[   12.491199] ieee80211 phy1: Channel: 153: 0x0 0x0 0xf
[   12.491211] ieee80211 phy1: 15 15 15 15 15 15 15 15 15 15 15 15 14 14 14 14
[   12.491217] ieee80211 phy1: Channel: 157: 0x0 0x0 0xf
[   12.491229] ieee80211 phy1: 15 15 15 15 15 15 15 15 15 15 15 15 14 14 14 14
[   12.491237] ieee80211 phy1: Channel: 161: 0x0 0x0 0xf
[   12.491257] ieee80211 phy1: 15 15 15 15 15 15 15 15 15 15 15 15 14 14 14 14
[   12.491264] ieee80211 phy1: Channel: 165: 0x0 0x0 0xf
[   12.491276] ieee80211 phy1: 16 16 16 16 16 16 16 16 15 15 15 15 14 14 14 14
[   12.492637] ieee80211 phy1: 2G disabled, 5G enabled
[   12.497547] ieee80211 phy1: 4 TX antennas, 4 RX antennas
[   12.543589] u32 classifier
[   12.546316]     input device check on
[   12.549992]     Actions configured
[   12.554665] Mirror/redirect action on
[   12.562053] nf_conntrack version 0.5.0 (4096 buckets, 16384 max)
[   12.585617] ip_tables: (C) 2000-2006 Netfilter Core Team
[   12.661781] usbcore: registered new interface driver ums-alauda
[   12.668652] usbcore: registered new interface driver ums-cypress
[   12.675449] usbcore: registered new interface driver ums-datafab
[   12.682138] usbcore: registered new interface driver ums-freecom
[   12.689113] usbcore: registered new interface driver ums-isd200
[   12.695920] usbcore: registered new interface driver ums-jumpshot
[   12.702752] usbcore: registered new interface driver ums-karma
[   12.709329] usbcore: registered new interface driver ums-sddr09
[   12.716049] usbcore: registered new interface driver ums-sddr55
[   12.722741] usbcore: registered new interface driver ums-usbat
[   12.751221] xt_time: kernel timezone is -0000
[   12.764628] PPP generic driver version 2.4.2
[   12.770079] NET: Registered protocol family 24
[   12.776578] kmodloader: done loading kernel modules from /etc/modules.d/*
[   16.956384] mvneta f1070000.ethernet eth0: configuring for fixed link mode
[   16.963573] mvneta f1070000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[   16.973493] br-lan: port 1(eth0) entered blocking state
[   16.978759] br-lan: port 1(eth0) entered disabled state
[   16.984609] device eth0 entered promiscuous mode
[   16.993532] br-lan: port 1(eth0) entered blocking state
[   16.998806] br-lan: port 1(eth0) entered forwarding state
[   17.028797] mvneta f1074000.ethernet eth1: configuring for fixed link mode
[   17.036674] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   17.042718] mvneta f1074000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
[   17.050608] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[   18.102126] ieee80211 phy1: regdomain: ETSI
[   18.106398] ieee80211 phy1: Channel: 36: 0x0 0x0 0xf
[   18.111400] ieee80211 phy1: c c c c c c c c d d d d c c c c
[   18.117153] ieee80211 phy1: Channel: 40: 0x0 0x0 0xf
[   18.122145] ieee80211 phy1: c c c c c c c c d d d d c c c c
[   18.127840] ieee80211 phy1: Channel: 44: 0x0 0x0 0xf
[   18.132851] ieee80211 phy1: c c c c c c c c d d d d c c c c
[   18.138529] ieee80211 phy1: Channel: 48: 0x0 0x0 0xf
[   18.143570] ieee80211 phy1: c c c c c c c c d d d d c c c c
[   18.149265] ieee80211 phy1: Channel: 52: 0x0 0x0 0xf
[   18.154342] ieee80211 phy1: c c c c c c c c d d d d c c c c
[   18.160057] ieee80211 phy1: Channel: 56: 0x0 0x0 0xf
[   18.165100] ieee80211 phy1: c c c c c c c c d d d d c c c c
[   18.170794] ieee80211 phy1: Channel: 60: 0x0 0x0 0xf
[   18.175830] ieee80211 phy1: c c c c c c c c d d d d c c c c
[   18.181530] ieee80211 phy1: Channel: 64: 0x0 0x0 0xf
[   18.186587] ieee80211 phy1: c c c c c c c c d d d d c c c c
[   18.192287] ieee80211 phy1: Channel: 100: 0x0 0x0 0xf
[   18.197422] ieee80211 phy1: c c c c c c c c d d d d c c c c
[   18.203160] ieee80211 phy1: Channel: 104: 0x0 0x0 0xf
[   18.208252] ieee80211 phy1: c c c c c c c c d d d d c c c c
[   18.213985] ieee80211 phy1: Channel: 108: 0x0 0x0 0xf
[   18.219072] ieee80211 phy1: c c c c c c c c d d d d c c c c
[   18.224801] ieee80211 phy1: Channel: 112: 0x0 0x0 0xf
[   18.229889] ieee80211 phy1: c c c c c c c c d d d d c c c c
[   18.235618] ieee80211 phy1: Channel: 116: 0x0 0x0 0xf
[   18.240706] ieee80211 phy1: c c c c c c c c d d d d c c c c
[   18.246445] ieee80211 phy1: Channel: 120: 0x0 0x0 0xf
[   18.251549] ieee80211 phy1: c c c c c c c c d d d d c c c c
[   18.257278] ieee80211 phy1: Channel: 124: 0x0 0x0 0xf
[   18.262415] ieee80211 phy1: c c c c c c c c d d d d c c c c
[   18.268114] ieee80211 phy1: Channel: 128: 0x0 0x0 0xf
[   18.273245] ieee80211 phy1: c c c c c c c c d d d d c c c c
[   18.278939] ieee80211 phy1: Channel: 132: 0x0 0x0 0xf
[   18.284072] ieee80211 phy1: c c c c c c c c d d d d c c c c
[   18.289768] ieee80211 phy1: Channel: 136: 0x0 0x0 0xf
[   18.294897] ieee80211 phy1: c c c c c c c c d d d d c c c c
[   18.300599] ieee80211 phy1: Channel: 140: 0x0 0x0 0xf
[   18.305736] ieee80211 phy1: c c c c c c c c d d d d c c c c
[   18.311437] ieee80211 phy1: Channel: 149: 0x0 0x0 0xf
[   18.316564] ieee80211 phy1: c c c c c c c c d d d d c c c c
[   18.322283] ieee80211 phy0: regdomain: ETSI
[   18.326542] ieee80211 phy0: Channel: 1: 0x0 0x0 0xf
[   18.331456] ieee80211 phy0: b b b b b b b b b b b b 0 0 0 0
[   18.337190] ieee80211 phy0: Channel: 2: 0x0 0x0 0xf
[   18.342122] ieee80211 phy0: b b b b b b b b b b b b 0 0 0 0
[   18.347872] ieee80211 phy0: Channel: 3: 0x0 0x0 0xf
[   18.352844] ieee80211 phy0: b b b b b b b b b b b b 0 0 0 0
[   18.358540] ieee80211 phy0: Channel: 4: 0x0 0x0 0xf
[   18.363489] ieee80211 phy0: b b b b b b b b b b b b 0 0 0 0
[   18.369185] ieee80211 phy0: Channel: 5: 0x0 0x0 0xf
[   18.374160] ieee80211 phy0: b b b b b b b b b b b b 0 0 0 0
[   18.379861] ieee80211 phy0: Channel: 6: 0x0 0x0 0xf
[   18.384823] ieee80211 phy0: b b b b b b b b b b b b 0 0 0 0
[   18.390519] ieee80211 phy0: Channel: 7: 0x0 0x0 0xf
[   18.395479] ieee80211 phy0: b b b b b b b b b b b b 0 0 0 0
[   18.401184] ieee80211 phy0: Channel: 8: 0x0 0x0 0xf
[   18.406142] ieee80211 phy0: b b b b b b b b b b b b 0 0 0 0
[   18.411844] ieee80211 phy0: Channel: 9: 0x0 0x0 0xf
[   18.416800] ieee80211 phy0: b b b b b b b b b b b b 0 0 0 0
[   18.422529] ieee80211 phy0: Channel: 10: 0x0 0x0 0xf
[   18.427547] ieee80211 phy0: b b b b b b b b b b b b 0 0 0 0
[   18.433292] ieee80211 phy0: Channel: 11: 0x0 0x0 0xf
[   18.438296] ieee80211 phy0: b b b b b b b b b b b b 0 0 0 0
[   18.444027] ieee80211 phy0: Channel: 12: 0x0 0x0 0xf
[   18.449029] ieee80211 phy0: b b b b b b b b b b b b 0 0 0 0
[   18.454748] ieee80211 phy0: Channel: 13: 0x0 0x0 0xf
[   18.459735] ieee80211 phy0: b b b b b b b b b b b b 0 0 0 0
[   19.632481] ieee80211 phy0: change: 0xffffffff
[   19.755338] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   19.888847] ieee80211 phy1: change: 0xffffffff
[   20.046952] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[   20.053642] br-lan: port 2(wlan0) entered blocking state
[   20.059008] br-lan: port 2(wlan0) entered disabled state
[   20.064721] device wlan0 entered promiscuous mode
[   20.073383] br-lan: port 3(wlan1) entered blocking state
[   20.078735] br-lan: port 3(wlan1) entered disabled state
[   20.084469] device wlan1 entered promiscuous mode
[   20.099538] ieee80211 phy0: change: 0x100
[   20.112620] ieee80211 phy0: change: 0x40
[   20.114333] ieee80211 phy1: change: 0x100
[   20.122490] ieee80211 phy1: change: 0x40
[   20.362455] ieee80211 phy0: change: 0x40
[   20.373857] ieee80211 phy1: change: 0x40
[   20.572488] ieee80211 phy0: change: 0x40
[   20.602553] ieee80211 phy1: change: 0x40
[   20.792424] ieee80211 phy0: change: 0x40
[   20.822477] ieee80211 phy1: change: 0x40
[   21.003365] ieee80211 phy0: change: 0x40
[   21.042435] ieee80211 phy1: change: 0x60
[   21.212444] ieee80211 phy0: change: 0x40
[   21.272580] ieee80211 phy1: change: 0x40
[   21.429183] ieee80211 phy0: change: 0x40
[   21.494850] ieee80211 phy1: change: 0x40
[   21.642472] ieee80211 phy0: change: 0x40
[   21.753613] ieee80211 phy1: change: 0x40
[   21.862453] ieee80211 phy0: change: 0x40
[   21.993333] ieee80211 phy1: change: 0x40
[   22.082446] ieee80211 phy0: change: 0x40
[   22.238609] ieee80211 phy1: change: 0x40
[   22.297579] ieee80211 phy0: change: 0x40
[   22.492468] ieee80211 phy1: change: 0x40
[   22.523743] ieee80211 phy0: change: 0x40
[   22.689673] ieee80211 phy0: change: 0x100
[   22.752449] ieee80211 phy1: change: 0x40
[   22.918306] ieee80211 phy0: change: 0x100
[   22.931670] ieee80211 phy0: change: 0x42
[   22.982447] ieee80211 phy1: change: 0x40
[   23.195661] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   23.202203] br-lan: port 2(wlan0) entered blocking state
[   23.207592] br-lan: port 2(wlan0) entered forwarding state
[   23.302442] ieee80211 phy1: change: 0x40
[   23.562486] ieee80211 phy1: change: 0x40
[   23.802463] ieee80211 phy1: change: 0x40
[   24.074294] ieee80211 phy1: change: 0x40
[   24.342437] ieee80211 phy1: change: 0x40
[   24.602521] ieee80211 phy1: change: 0x40
[   24.832449] ieee80211 phy1: change: 0x60
[   25.062826] ieee80211 phy1: change: 0x40
[   25.288542] ieee80211 phy1: change: 0x40
[   25.512469] ieee80211 phy1: change: 0x40
[   25.762483] ieee80211 phy1: change: 0x60
[   25.872422] ieee80211 phy1: change: 0x100
[   25.885649] ieee80211 phy1: change: 0x100
[   25.898992] ieee80211 phy1: change: 0x40
[   26.122453] ieee80211 phy1: change: 0x40
[   26.342426] ieee80211 phy1: change: 0x40
[   26.573738] ieee80211 phy1: change: 0x40
[   26.812435] ieee80211 phy1: change: 0x60
[   27.032448] ieee80211 phy1: change: 0x40
[   27.262496] ieee80211 phy1: change: 0x40
[   27.482463] ieee80211 phy1: change: 0x40
[   27.712444] ieee80211 phy1: change: 0x40
[   27.942442] ieee80211 phy1: change: 0x40
[   28.162448] ieee80211 phy1: change: 0x40
[   28.392454] ieee80211 phy1: change: 0x40
[   28.612430] ieee80211 phy1: change: 0x40
[   28.832439] ieee80211 phy1: change: 0x40
[   29.052469] ieee80211 phy1: change: 0x40
[   29.272435] ieee80211 phy1: change: 0x40
[   29.492531] ieee80211 phy1: change: 0x40
[   29.722434] ieee80211 phy1: change: 0x40
[   29.942434] ieee80211 phy1: change: 0x40
[   30.172445] ieee80211 phy1: change: 0x60
[   30.402428] ieee80211 phy1: change: 0x40
[   30.642446] ieee80211 phy1: change: 0x40
[   30.862449] ieee80211 phy1: change: 0x40
[   31.072470] ieee80211 phy1: change: 0x60
[   31.180846] ieee80211 phy1: change: 0x100
[   31.192504] ieee80211 phy1: change: 0x100
[   31.205833] ieee80211 phy1: change: 0x40
[   31.432479] ieee80211 phy1: change: 0x40
[   31.652488] ieee80211 phy1: change: 0x40
[   31.872496] ieee80211 phy1: change: 0x40
[   32.102459] ieee80211 phy1: change: 0x60
[   32.332660] ieee80211 phy1: change: 0x40
[   32.562496] ieee80211 phy1: change: 0x40
[   32.782522] ieee80211 phy1: change: 0x40
[   33.002558] ieee80211 phy1: change: 0x40
[   33.232675] ieee80211 phy1: change: 0x40
[   33.462775] ieee80211 phy1: change: 0x40
[   33.692580] ieee80211 phy1: change: 0x40
[   33.912845] ieee80211 phy1: change: 0x40
[   34.132557] ieee80211 phy1: change: 0x40
[   34.362528] ieee80211 phy1: change: 0x40
[   34.582557] ieee80211 phy1: change: 0x40
[   34.792659] ieee80211 phy1: change: 0x40
[   35.022614] ieee80211 phy1: change: 0x40
[   35.242681] ieee80211 phy1: change: 0x40
[   35.462636] ieee80211 phy1: change: 0x60
[   35.682641] ieee80211 phy1: change: 0x40
[   35.892652] ieee80211 phy1: change: 0x40
[   36.112683] ieee80211 phy1: change: 0x40
[   36.322830] ieee80211 phy1: change: 0x60
[   36.431156] ieee80211 phy1: change: 0x100
[   36.442887] ieee80211 phy1: change: 0x100
[   36.456830] ieee80211 phy1: change: 0x40
[   36.682742] ieee80211 phy1: change: 0x40
[   36.902728] ieee80211 phy1: change: 0x40
[   37.122690] ieee80211 phy1: change: 0x40
[   37.352705] ieee80211 phy1: change: 0x60
[   37.572712] ieee80211 phy1: change: 0x40
[   37.792708] ieee80211 phy1: change: 0x40
[   38.012693] ieee80211 phy1: change: 0x40
[   38.232735] ieee80211 phy1: change: 0x40
[   38.462752] ieee80211 phy1: change: 0x40
[   38.682786] ieee80211 phy1: change: 0x40
[   38.902783] ieee80211 phy1: change: 0x40
[   39.122741] ieee80211 phy1: change: 0x40
[   39.342805] ieee80211 phy1: change: 0x40
[   39.562830] ieee80211 phy1: change: 0x40
[   39.782777] ieee80211 phy1: change: 0x40
[   40.002794] ieee80211 phy1: change: 0x40
[   40.222833] ieee80211 phy1: change: 0x40
[   40.442806] ieee80211 phy1: change: 0x40
[   40.662814] ieee80211 phy1: change: 0x60
[   40.882850] ieee80211 phy1: change: 0x40
[   41.102832] ieee80211 phy1: change: 0x40
[   41.312828] ieee80211 phy1: change: 0x40
[   41.522821] ieee80211 phy1: change: 0x60
[   41.632087] ieee80211 phy1: change: 0x100
[   41.645490] ieee80211 phy1: change: 0x100
[   41.658512] ieee80211 phy1: change: 0x40
[   41.882852] ieee80211 phy1: change: 0x40
[   42.102875] ieee80211 phy1: change: 0x40
[   42.322925] ieee80211 phy1: change: 0x40
[   42.542915] ieee80211 phy1: change: 0x60
[   42.762879] ieee80211 phy1: change: 0x40
[   42.982943] ieee80211 phy1: change: 0x40
[   43.202904] ieee80211 phy1: change: 0x40
[   43.422897] ieee80211 phy1: change: 0x40
[   43.642959] ieee80211 phy1: change: 0x40
[   43.862925] ieee80211 phy1: change: 0x40
[   44.082935] ieee80211 phy1: change: 0x40
[   44.302975] ieee80211 phy1: change: 0x40
[   44.522902] ieee80211 phy1: change: 0x40
[   44.742950] ieee80211 phy1: change: 0x40
[   44.963011] ieee80211 phy1: change: 0x40
[   45.182955] ieee80211 phy1: change: 0x40
[   45.402971] ieee80211 phy1: change: 0x40
[   45.623050] ieee80211 phy1: change: 0x40
[   45.842978] ieee80211 phy1: change: 0x60
[   46.063010] ieee80211 phy1: change: 0x40
[   46.273022] ieee80211 phy1: change: 0x40
[   46.483009] ieee80211 phy1: change: 0x40
[   46.693012] ieee80211 phy1: change: 0x60
[   46.801460] ieee80211 phy1: change: 0x100
[   46.813206] ieee80211 phy1: change: 0x100
[   46.827042] ieee80211 phy1: change: 0x60
[   47.053031] ieee80211 phy1: change: 0x40
[   47.263054] ieee80211 phy1: change: 0x60
[   47.371530] ieee80211 phy1: change: 0x100
[   47.580273] ieee80211 phy1: change: 0x100
[   47.593165] ieee80211 phy1: change: 0x62
[   47.771575] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[   47.778255] br-lan: port 3(wlan1) entered blocking state
[   47.783665] br-lan: port 3(wlan1) entered forwarding state
[   47.917065] ieee80211 phy1: change: 0x20

I was just curious about the v1 booting every hour, like you eluded to. This build can't be released with a major issue like that.

Thanks,

(Last edited by davidc502 on 23 Feb 2017, 02:33)

NM it was because the Vlan box was checked!

Linksys 1900ACS after doing the upgrade to the newest firmware everything works except for the switch ports on the back of the router. Can anyone point me in the right direction. everything was working fine on the last build.

Thanks!

-CK

(Last edited by cknisley on 23 Feb 2017, 04:01)

davidc502 wrote:

I was just curious about the v1 booting every hour, like you eluded to. This build can't be released with a major issue like that.

Thanks,

Ok, looks like it has the same issue. Uptime at most 1hr, sometimes as short as 10-15 minutes. I haven't managed to catch anything in logs though I guess I'd have to log to a usb to have much hope of doing that.

Anyway, not working on my device so I'll return to my alt. image. I've mentioned it in the main thread and on LEDE forums and nobody else seems to have run into this problem.

listerwrt wrote:
davidc502 wrote:

I was just curious about the v1 booting every hour, like you eluded to. This build can't be released with a major issue like that.

Thanks,

Ok, looks like it has the same issue. Uptime at most 1hr, sometimes as short as 10-15 minutes. I haven't managed to catch anything in logs though I guess I'd have to log to a usb to have much hope of doing that.

Anyway, not working on my device so I'll return to my alt. image. I've mentioned it in the main thread and on LEDE forums and nobody else seems to have run into this problem.

Thanks for testing... It's what I expected, but wanted to be sure.

I've locked the images so they can't be downloaded anymore, unless someone else wants to volunteer to test.

(Last edited by davidc502 on 23 Feb 2017, 17:38)

davidc502 wrote:
listerwrt wrote:
davidc502 wrote:

I was just curious about the v1 booting every hour, like you eluded to. This build can't be released with a major issue like that.

Thanks,

Ok, looks like it has the same issue. Uptime at most 1hr, sometimes as short as 10-15 minutes. I haven't managed to catch anything in logs though I guess I'd have to log to a usb to have much hope of doing that.

Anyway, not working on my device so I'll return to my alt. image. I've mentioned it in the main thread and on LEDE forums and nobody else seems to have run into this problem.

Thanks for testing... It's what I expected, but wanted to be sure.

I've locked the images so they can't be downloaded anymore, unless someone else wants to volunteer to test.

Unfortunate but I was expecting this being the odd one out hardware wise  Hopefully it'll be resolved eventually.

I've been tempted to get the WRT3200ACM, this maybe the deciding factor. That 1.8GHz CPU and wave-2 ac wifi do sound awfully good big_smile

Edit: if you need a tester don't hesitate to ask me. If LEDE has PM I use the same user name (ListerWRT)

(Last edited by listerwrt on 23 Feb 2017, 19:01)

@listerwrt

Appreciate it.

Thanks,

@davidc502 I decided to test the build by cybrnook on the LEDE forum and so far I've had no reboots (2hrs 22m uptime). I'll update this post if I get any reboots, I could just be lucky so far.

---removed incorrect statement---

Edit: Ah, spoke too soon sad

(Last edited by listerwrt on 24 Feb 2017, 16:23)

listerwrt wrote:

Edit: Ah, spoke too soon sad

It rebooted, or you noticed it WAS 3556 in the folder, and not 3526 like you initially thought?

cybrnook2002 wrote:
listerwrt wrote:

Edit: Ah, spoke too soon sad

It rebooted, or you noticed it WAS 3556 in the folder, and not 3526 like you initially thought?

It rebooted about twenty minutes after my post.

The build in the 3556 folder is marked 3526 in LUCI.

Lede leviathan IV SNAPSHOT r3526-bececcc / LuCI Master (git-17.050.51199-0f5321d)

Just realised that's davids build name and build number... For some reason I can't write over his image with sysupgrade... Very confused.

In the morning I'll use serial to write the factory image over both partitions and start from scratch. I see a user on the LEDE forum is running your builds with no issues so maybe it is something wrong with my device.

(Last edited by listerwrt on 24 Feb 2017, 16:35)

listerwrt wrote:
cybrnook2002 wrote:
listerwrt wrote:

Edit: Ah, spoke too soon sad

It rebooted, or you noticed it WAS 3556 in the folder, and not 3526 like you initially thought?

It rebooted about twenty minutes after my post.

The build in the 3556 folder is marked 3526 in LUCI.

Lede leviathan IV SNAPSHOT r3526-bececcc / LuCI Master (git-17.050.51199-0f5321d)

Just realised that's davids build name and build number... For some reason I can't write over his image with sysupgrade... Very confused.

In the morning I'll use serial to write the factory image over both partitions and start from scratch. I see a user on the LEDE forum is running your builds with no issues so maybe it is something wrong with my device.

According to your info you are still on Davids build, and likely never flashed over to mine :-)

For flashing of these units, my recommendation is to keep the factory firmware on your alt nand, and flash the "factory" image from the Linksys UI. It just makes life easier....

In my builds you can execute /usr/sbin/bootTaOther.sh for a nice little script that will switch you to the other nand when you are ready to upgrade.

@davidc502, might be a good idea to copy that into your builds as well. Just a little easter egg for the users to be able to switch back and forth. (and not have to explain how to change partitions each time. It's in my "manipulation" folder on dropbox)

(Last edited by cybrnook2002 on 24 Feb 2017, 19:20)

Agree about keeping the Linksys firmware available. Makes life easier switching between different builds. I have at times installed cybrnook, davidc502, Gargoyle, and DD-WRT. Would not have been as easy switching between these builds if I had not kept the stock partition available. The /usr/sbin/bootTaOther.sh is a nice touch in cybrnook's builds.

(Last edited by bill1228 on 24 Feb 2017, 23:50)

fw_printenv boot_part

will show you what partition is active (1 or 2), while

fw_setenv boot_part <the other partition>

followed by

reboot

will get you into the other one.

nitroshift

r3582 is released today. I held the kernel back to 4.4.50 and not 4.9.x because the newest kernel introduces some problems that still need sorting out.  One issue for v1 users is a hourly reboot < it's a feature right wink

Unknown, if the Rango issue of future flashes has been sorted out, but will do some testing to see if that's the case or not.

It's been on my todo list to make a video for USB/TTL instructions, but I know as soon as I spend the time, the new Rango wifi driver will be out...  So, I've been holding back for it.

Let me know if you have questions.

Best Regards,

(Last edited by davidc502 on 26 Feb 2017, 21:55)

davidc502 wrote:

r3582 is released today. I held the kernel back to 4.4.50 and not 4.9.x because the newest kernel introduces some problems that still need sorting out.  One issue for v1 users is a hourly reboot < it's a feature right wink

Nice!! Downloading!