Linux Kernel 6.7.5 Kirkwood package and Debian rootfs

Hmm issue seems to have been $(variable) instead of $variable (new uboot changed syntax it seems)...

anyway, 317 works now...stock still hangs though with power led (1st led immediately under power button) rapidly blinking green

Anyway, for reference, bootlog:

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.17.0-kirkwood-tld-1 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #4 PREEMPT Wed Oct 22 00:55:17 PDT 2014
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine model: Zyxel NSA320
[    0.000000] bootconsole [earlycon0] enabled
[    0.000000] Memory policy: Data cache writeback
[    0.000000] On node 0 totalpages: 131072
[    0.000000] free_area_init_node: node 0, pgdat c07e3078, node_mem_map dfbfa000
[    0.000000]   DMA zone: 1024 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 131072 pages, LIFO batch:31
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
[    0.000000] Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/md1 rw rootwait loglevel=8 earlyprintk=serial
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 504404K/524288K available (5553K kernel code, 358K rwdata, 1892K rodata, 262K init, 302K bss, 19884K reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xffe00000   (2048 kB)
[    0.000000]     vmalloc : 0xe0800000 - 0xff000000   ( 488 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc074d83c   (7447 kB)
[    0.000000]       .init : 0xc074e000 - 0xc078f90c   ( 263 kB)
[    0.000000]       .data : 0xc0790000 - 0xc07e998c   ( 359 kB)
[    0.000000]        .bss : 0xc07e998c - 0xc08352dc   ( 303 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000015] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474836475ns
[    0.008304] Console: colour dummy device 80x30
[    0.012871] Calibrating delay loop... 1196.85 BogoMIPS (lpj=5984256)
[    0.100934] pid_max: default: 32768 minimum: 301
[    0.105769] Security Framework initialized
[    0.110065] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.116808] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.124715] Initializing cgroup subsys devices
[    0.129332] Initializing cgroup subsys freezer
[    0.133899] Initializing cgroup subsys net_cls
[    0.138501] Initializing cgroup subsys blkio
[    0.142969] CPU: Testing write buffer coherency: ok
[    0.148432] Setting up static identity map for 0x542138 - 0x542190
[    0.155033] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[    0.162578] devtmpfs: initialized
[    0.168545] prandom: seed boundary self test passed
[    0.177524] prandom: 100 self tests passed
[    0.181813] pinctrl core: initialized pinctrl subsystem
[    0.187638] regulator-dummy: no parameters
[    0.197050] NET: Registered protocol family 16
[    0.202117] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.210269] cpuidle: using governor ladder
[    0.214483] cpuidle: using governor menu
[    0.219001] Feroceon L2: Enabling L2
[    0.222716] Feroceon L2: Cache support initialised.
[    0.228149] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[    0.243710] No ATAGs?
[    0.279671] vgaarb: loaded
[    0.283132] usbcore: registered new interface driver usbfs
[    0.288861] usbcore: registered new interface driver hub
[    0.294390] usbcore: registered new device driver usb
[    0.300727] Switched to clocksource orion_clocksource
[    0.344525] NET: Registered protocol family 2
[    0.349924] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.357244] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    0.363861] TCP: Hash tables configured (established 4096 bind 4096)
[    0.370388] TCP: reno registered
[    0.373745] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.379705] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.386294] NET: Registered protocol family 1
[    0.391078] RPC: Registered named UNIX socket transport module.
[    0.397114] RPC: Registered udp transport module.
[    0.401972] RPC: Registered tcp transport module.
[    0.406784] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.413367] PCI: CLS 0 bytes, default 32
[    0.417661] Unpacking initramfs...
[    1.006799] Freeing initrd memory: 6876K (cf948000 - cffff000)
[    1.012958] NetWinder Floating Point Emulator V0.97 (double precision)
[    1.021022] futex hash table entries: 256 (order: -1, 3072 bytes)
[    1.027251] Initialise system trusted keyring
[    1.031840] audit: initializing netlink subsys (disabled)
[    1.037399] audit: type=2000 audit(1.020:1): initialized
[    1.043620] zpool: loaded
[    1.046349] zbud: loaded
[    1.049264] VFS: Disk quotas dquot_6.5.2
[    1.053369] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.060560] NFS: Registering the id_resolver key type
[    1.065809] Key type id_resolver registered
[    1.070097] Key type id_legacy registered
[    1.074250] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.081096] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    1.087730] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    1.095237] msgmni has been set to 998
[    1.099250] Key type big_key registered
[    1.105510] alg: No test for stdrng (krng)
[    1.109811] bounce: pool size: 64 pages
[    1.113902] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    1.121471] io scheduler noop registered
[    1.125500] io scheduler deadline registered
[    1.129902] io scheduler cfq registered (default)
[    1.136044] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[    1.144215] irq: Cannot allocate irq_descs @ IRQ34, assuming pre-allocated
[    1.151674] irq: Cannot allocate irq_descs @ IRQ66, assuming pre-allocated
[    1.159505] mvebu-pcie mbus:pcie-controller: PCI host bridge to bus 0000:00
[    1.166651] pci_bus 0000:00: root bus resource [io  0x1000-0xfffff]
[    1.173056] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[    1.180053] pci_bus 0000:00: root bus resource [bus 00-ff]
[    1.185696] pci 0000:00:01.0: [11ab:6281] type 01 class 0x060400
[    1.192114] PCI: bus0: Fast back to back transfers disabled
[    1.197799] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    1.206104] PCI: bus1: Fast back to back transfers enabled
[    1.211731] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    1.218483] pci 0000:00:01.0: PCI bridge to [bus 01]
[    1.223856] mv_xor f1060800.xor: Marvell shared XOR driver
[    1.260798] mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
[    1.300795] mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
[    1.306479] mv_xor f1060900.xor: Marvell shared XOR driver
[    1.350793] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[    1.390794] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[    1.396709] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    1.404533] console [ttyS0] disabled
[    1.408263] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 27, base_baud = 12500000) is a 16550A
[    1.417440] console [ttyS0] enabled
[    1.417440] console [ttyS0] enabled
[    1.424576] bootconsole [earlycon0] disabled
[    1.424576] bootconsole [earlycon0] disabled
[    1.434724] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xf1
[    1.441141] nand: Samsung NAND 128MiB 3,3V 8-bit
[    1.445782] nand: 128MiB, SLC, page size: 2048, OOB size: 64
[    1.451495] Scanning device for bad blocks
[    1.478268] Bad eraseblock 235 at 0x000001d60000
[    1.497486] Bad eraseblock 387 at 0x000003060000
[    1.569928] libphy: Fixed MDIO Bus: probed
[    1.574483] libphy: orion_mdio_bus: probed
[    1.583457] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    1.591507] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address fc:f5:28:30:0c:4e
[    1.600484] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.607160] ehci-pci: EHCI PCI platform driver
[    1.611749] ehci-orion: EHCI orion driver
[    1.615951] orion-ehci f1050000.ehci: EHCI Host Controller
[    1.621543] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    1.629375] orion-ehci f1050000.ehci: irq 30, io mem 0xf1050000
[    1.650765] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[    1.656977] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.663820] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.671093] usb usb1: Product: EHCI Host Controller
[    1.675992] usb usb1: Manufacturer: Linux 3.17.0-kirkwood-tld-1 ehci_hcd
[    1.682743] usb usb1: SerialNumber: f1050000.ehci
[    1.688217] hub 1-0:1.0: USB hub found
[    1.692066] hub 1-0:1.0: 1 port detected
[    1.696929] mousedev: PS/2 mouse device common for all mice
[    1.703204] rtc-mv f1010300.rtc: rtc core: registered f1010300.rtc as rtc0
[    1.710284] i2c /dev entries driver
[    1.718849] rtc-pcf8563 0-0051: chip found, driver version 0.4.3
[    1.730135] rtc-pcf8563 0-0051: rtc core: registered rtc-pcf8563 as rtc1
[    1.739231] hidraw: raw HID events driver (C) Jiri Kosina
[    1.745136] drop_monitor: Initializing network drop monitor service
[    1.751712] TCP: cubic registered
[    1.755055] NET: Registered protocol family 17
[    1.759669] Key type dns_resolver registered
[    1.764753] Loading compiled-in X.509 certificates
[    1.769592] registered taskstats version 1
[    1.774774] rtc-mv f1010300.rtc: setting system clock to 2014-12-05 20:05:16 UTC (1417809916)
[    1.784434] PM: Hibernation image not present or could not be loaded.
[    1.792067] Freeing unused kernel memory: 260K (c074e000 - c078f000)
Loading, please wait...
[    1.866069] systemd-udevd[59]: starting version 215
[    1.883090] random: systemd-udevd urandom read with 3 bits of entropy available
[    2.010888] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    2.048807] SCSI subsystem initialized
[    2.089578] libata version 3.00 loaded.
[    2.104687] sata_mv f1080000.sata: version 1.28
[    2.109504] sata_mv f1080000.sata: slots 32 ports 2
[    2.170926] scsi host0: sata_mv
[    2.175519] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[    2.187636] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    2.202521] usb 1-1: Product: USB2.0 Hub
[    2.206634] scsi host1: sata_mv
[    2.210130] ata1: SATA max UDMA/133 irq 33
[    2.215273] hub 1-1:1.0: USB hub found
[    2.220808] hub 1-1:1.0: 4 ports detected
[    2.246241] ata2: SATA max UDMA/133 irq 33
[    2.750778] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[    2.770870] ata1.00: ATA-8: WDC WD6400AAKS-65A7B0, 01.03B01, max UDMA/133
[    2.777697] ata1.00: 1250263728 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    2.800860] ata1.00: configured for UDMA/133
[    2.821125] scsi 0:0:0:0: Direct-Access     ATA      WDC WD6400AAKS-6 3B01 PQ: 0 ANSI: 5
[    3.340779] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[    3.360865] ata2.00: ATA-8: WDC WD6400AAKS-65A7B0, 01.03B01, max UDMA/133
[    3.367692] ata2.00: 1250263728 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    3.390859] ata2.00: configured for UDMA/133
[    3.411067] scsi 1:0:0:0: Direct-Access     ATA      WDC WD6400AAKS-6 3B01 PQ: 0 ANSI: 5
[    3.439533] sd 0:0:0:0: [sda] 1250263728 512-byte logical blocks: (640 GB/596 GiB)
[    3.450949] sd 1:0:0:0: [sdb] 1250263728 512-byte logical blocks: (640 GB/596 GiB)
[    3.459838] sd 0:0:0:0: [sda] Write Protect is off
[    3.465002] sd 1:0:0:0: [sdb] Write Protect is off
[    3.469821] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    3.474949] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    3.480144] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.489382] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    3.526867]  sda: sda1 sda2
[    3.531916] sd 0:0:0:0: [sda] Attached SCSI disk
[    3.536741]  sdb: sdb1 sdb2
[    3.541734] sd 1:0:0:0: [sdb] Attached SCSI disk
[    3.549641] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    3.557112] sd 1:0:0:0: Attached scsi generic sg1 type 0
[    3.791832] md: bind<sdb1>
[    3.801430] md: bind<sda1>
[    3.814028] md: bind<sdb2>
[    3.831073] md: raid1 personality registered for level 1
[    3.837370] md/raid1:md0: active with 2 out of 2 mirrors
[    3.843095] md0: detected capacity change from 0 to 213712896
[    3.851710]  md0: unknown partition table
[    3.861103] md: bind<sda2>
[    3.881906] md/raid1:md1: active with 2 out of 2 mirrors
[    3.888130] md1: detected capacity change from 0 to 16112200704
[    3.907781]  md1: unknown partition table
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Assembling all MD arrays ... Failure: failed to assemble all arrays.
done.
done.
Begin: Running /scripts/local-premount ... done.
[    4.154846] EXT4-fs (md1): mounted filesystem with ordered data mode. Opts: (null)
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
[    4.869323] systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
[    4.883094] systemd[1]: Detected architecture 'arm'.

Welcome to Debian GNU/Linux jessie/sid!

[    5.015678] systemd[1]: Inserted module 'autofs4'
[    5.046301] NET: Registered protocol family 10
[    5.051867] systemd[1]: Inserted module 'ipv6'
[    5.057487] systemd[1]: Set hostname to <debian>.
[    5.590656] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
[    5.609070] systemd[1]: Expecting device dev-ttyS0.device...
         Expecting device dev-ttyS0.device...
[    5.630926] systemd[1]: Starting Forward Password Requests to Wall Directory Watch.
[    5.639023] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    5.646809] systemd[1]: Starting Remote File Systems (Pre).
[  OK  ] Reached target Remote File Systems (Pre).
[    5.670877] systemd[1]: Reached target Remote File Systems (Pre).
[    5.677203] systemd[1]: Starting Arbitrary Executable File Formats File System Automount Point.
[  OK  ] Set up automount Arbitrary Executable File Formats F...utomount Point.
[    5.710894] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[    5.720455] systemd[1]: Starting Encrypted Volumes.
[  OK  ] Reached target Encrypted Volumes.
[    5.740881] systemd[1]: Reached target Encrypted Volumes.
[    5.746444] systemd[1]: Starting Dispatch Password Requests to Console Directory Watch.
[    5.754810] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[    5.762908] systemd[1]: Starting Paths.
[  OK  ] Reached target Paths.
[    5.780881] systemd[1]: Reached target Paths.
[    5.785352] systemd[1]: Starting Swap.
[  OK  ] Reached target Swap.
[    5.810875] systemd[1]: Reached target Swap.
[    5.815269] systemd[1]: Expecting device dev-disk-by\x2duuid-3282fd60\x2db992\x2d4a6b\x2d84a9\x2ddf1be6dc1048.device...
         Expecting device dev-disk-by\x2duuid-3282fd60\x2db99...c1048.device...
[    5.850887] systemd[1]: Starting Root Slice.
[  OK  ] Created slice Root Slice.
[    5.910899] systemd[1]: Created slice Root Slice.
[    5.915747] systemd[1]: Starting /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[    5.940894] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[    5.947987] systemd[1]: Starting Delayed Shutdown Socket.
[  OK  ] Listening on Delayed Shutdown Socket.
[    5.970884] systemd[1]: Listening on Delayed Shutdown Socket.
[    5.976763] systemd[1]: Starting Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket (/dev/log).
[    6.000885] systemd[1]: Listening on Journal Socket (/dev/log).
[    6.006938] systemd[1]: Starting User and Session Slice.
[  OK  ] Created slice User and Session Slice.
[    6.030899] systemd[1]: Created slice User and Session Slice.
[    6.036810] systemd[1]: Starting udev Control Socket.
[  OK  ] Listening on udev Control Socket.
[    6.060891] systemd[1]: Listening on udev Control Socket.
[    6.066450] systemd[1]: Starting udev Kernel Socket.
[  OK  ] Listening on udev Kernel Socket.
[    6.090887] systemd[1]: Listening on udev Kernel Socket.
[    6.096354] systemd[1]: Starting Journal Socket.
[  OK  ] Listening on Journal Socket.
[    6.120884] systemd[1]: Listening on Journal Socket.
[    6.126058] systemd[1]: Starting System Slice.
[  OK  ] Created slice System Slice.
[    6.150899] systemd[1]: Created slice System Slice.
[    6.155965] systemd[1]: Started File System Check on Root Device.
[    6.162230] systemd[1]: Starting system-systemd\x2dfsck.slice.
[  OK  ] Created slice system-systemd\x2dfsck.slice.
[    6.190910] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[    6.197358] systemd[1]: Mounting POSIX Message Queue File System...
         Mounting POSIX Message Queue File System...
[    6.223626] systemd[1]: Mounted Huge Pages File System.
[    6.229980] random: nonblocking pool is initialized
[    6.235973] systemd[1]: Starting Load Kernel Modules...
         Starting Load Kernel Modules...
[    6.269027] systemd[1]: Starting Create list of required static device nodes for the current kernel...
         Starting Create list of required static device nodes...rrent kernel...
[    6.314183] systemd[1]: Starting udev Coldplug all Devices...
         Starting udev Coldplug all Devices...
[    6.344368] systemd[1]: Mounting Debug File System...
         Mounting Debug File System...
[    6.359489] systemd[1]: Started Set Up Additional Binary Formats.
[    6.379862] systemd[1]: Starting system-getty.slice.
[  OK  ] Created slice system-getty.slice.
[    6.411065] systemd[1]: Created slice system-getty.slice.
[    6.416613] systemd[1]: Starting system-serial\x2dgetty.slice.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[    6.450998] systemd[1]: Created slice system-serial\x2dgetty.slice.
[    6.457449] systemd[1]: Starting Journal Service...
         Starting Journal Service...
[  OK  ] Started Journal Service.
[    6.489319] systemd[1]: Started Journal Service.
[  OK  ] Reached target Slices.
         Starting Remount Root and Kernel File Systems...
[  OK  ] Mounted Debug File System.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Started Load Kernel Modules.
[    6.578246] EXT4-fs (md1): re-mounted. Opts: errors=remount-ro
[  OK  ] Started Create list of required static device nodes ...current kernel.
[  OK  ] Started Remount Root and Kernel File Systems.
[  OK  ] Started udev Coldplug all Devices.
         Starting Load/Save Random Seed...
         Starting Create Static Device Nodes in /dev...
         Starting Apply Kernel Variables...
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Started Apply Kernel Variables.
         Starting udev Kernel Device Manager...
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /tmp...
[    7.190600] systemd-udevd[166]: starting version 215
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Mounted /tmp.
         Starting Copy rules generated while the root was ro...
         Starting LSB: MD array assembly...
[  OK  ] Started Copy rules generated while the root was ro.
[    7.796948] input: gpio_keys as /devices/gpio_keys/input/input0
[  OK  ] Found device /dev/ttyS0.
[  OK  [    7.903947] orion_wdt: Initial timeout 21 sec
] Started LSB: MD array assembly.
[    7.990703] USB Power: 5000 mV
[  OK  ] Found device /dev/disk/by-uuid/3282fd60-b992-4a6b-84a9-df1be6dc1048.
         Starting MD array monitor...
         Starting File System Check on /dev/disk/by-uuid/3282...df1be6dc1048...
[  OK  ] Started MD array monitor.
[    8.756943] systemd-fsck[226]: /dev/md0: clean, 98/52208 files, 83336/208704 blocks
[  OK  ] Started File System Check on /dev/disk/by-uuid/3282f...9-df1be6dc1048.
         Mounting /boot...
[  OK  ] Mounted /boot.
[  OK  ] Reached target Local File Systems.
         Starting Create Volatile Files and Directories...
         Starting LSB: Raise network interfaces....
[  OK  ] Reached target Remote File Systems.
         Starting Trigger Flushing of Journal to Persistent Storage...
[  OK  ] Started Create Volatile Files and Directories.
         Starting Update UTMP about System Boot/Shutdown...
[    9.192793] systemd-journald[153]: Received request to flush runtime journal from PID 1
[  OK  ] Started Trigger Flushing of Journal to Persistent Storage.
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[    9.850211] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   12.870754] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[   12.880677] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  OK  ] Started LSB: Raise network interfaces..
[  OK  ] Reached target Network.
[  OK  ] Reached target Network is Online.
         Starting LSB: RPC portmapper replacement...
[  OK  ] Started LSB: RPC portmapper replacement.
[  OK  ] Reached target RPC Port Mapper.
         Starting LSB: NFS support files common to client and server...
[  OK  ] Started LSB: NFS support files common to client and server.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Timers.
[  OK  ] Reached target Basic System.
         Starting Regular background program processing daemon...
[  OK  ] Started Regular background program processing daemon.
         Starting Avahi mDNS/DNS-SD Stack...
         Starting OpenBSD Secure Shell server...
[  OK  ] Started OpenBSD Secure Shell server.
         Starting /etc/rc.local Compatibility...
         Starting Login Service...
         Starting Permit User Sessions...
         Starting D-Bus System Message Bus...
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
         Starting LSB: start Samba daemons for the AD DC...
         Starting LSB: start Samba NetBIOS nameserver (nmbd)...
         Starting LSB: Starts syslogd...
[  OK  ] Started /etc/rc.local Compatibility.
[  OK  ] Started Permit User Sessions.
[  OK  ] Started Login Service.
         Starting Getty on tty1...
[  OK  ] Started Getty on tty1.
         Starting Serial Getty on ttyS0...
[  OK  ] Started Serial Getty on ttyS0.
[  OK  ] Reached target Login Prompts.
[  OK  ] Started LSB: Starts syslogd.

Debian GNU/Linux jessie/sid debian ttyS0

bodhi I have a problem with kernel 3.17(FTD) on a couple of NSA320 boxes.
After the kernel boots, the following lines are printed on my serial console (not on ssh console):

[ 431.463359] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down
[ 431.469384] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full
duplex, flow control disabled
[ 743.225273] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down
[ 743.231259] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full
duplex, flow control disabled
[ 1042.101049] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down
[ 1042.107312] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full
duplex, flow control disabled
[ 1042.117233] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full
duplex, flow control disabled

Do you have any idea what might be causing this?
It does tend to fill up my logs :-)

Herb

Herb,

If you have other plugs running 3.17, do you see this on them? these type of notification should be in dmesg too. If you do then it's perhaps it's your network. I don't see this in any of my boxes (but I don't have the NSA320).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Im having issues with this new rootfs on an NSA320 no devices pluged into the usb's are being detected any idea whats going on?

Also is there a new uboot for the NSA320? absintos mentoned up above uboot.2013.10-tld-1.nsa320.mtd0.kwb.

edit:
looks like no modules are being loaded for usb.



Edited 1 time(s). Last edit at 12/10/2014 02:52PM by Buttzy10169.

Buttzy,

Do you have a boot log?

Yes, this is the NSA320 u-boot. It has been tested by gaogao:
http://forum.doozan.com/read.php?3,12381,16787#msg-16787

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I dont have a bootlog handy at the minute but i remember it did say something about detecting usb's.

I will try get a dmesg later. I remember others had issues after installing openmediavault (which i have done). I might try with the stock rootfs again to see if that brings the usb's back.

EDIT:

Finaly got the dmesg everything looks ok to me but lets see what you think.

Also before i go flashing the new uboot on the NSA320 what commands do i need this is the output of cat /proc/mtd:

mtd0: 00100000 00020000 "u-boot"
mtd1: 00080000 00020000 "uboot_env"
mtd2: 00080000 00020000 "key_store"
mtd3: 00080000 00020000 "info"
mtd4: 00a00000 00020000 "etc"
mtd5: 00a00000 00020000 "kernel_1"
mtd6: 02fc0000 00020000 "rootfs1"
mtd7: 00a00000 00020000 "kernel_2"
mtd8: 02fc0000 00020000 "rootfs2"

this is the kernel commandline from dmesg:

mtdparts=orion_nand:1M(u-boot),512K(uboot_env),512K(key_store),512K(info),10M(etc),10M(kernel_1),48896K(rootfs1),10M(kernel_2),-(rootfs2)

and the dmesg mtd parts says:

[    1.743659] 9 cmdlinepart partitions found on MTD device orion_nand
[    1.749956] Creating 9 MTD partitions on "orion_nand":
[    1.755143] 0x000000000000-0x000000100000 : "u-boot"
[    1.760554] 0x000000100000-0x000000180000 : "uboot_env"
[    1.766213] 0x000000180000-0x000000200000 : "key_store"
[    1.771831] 0x000000200000-0x000000280000 : "info"
[    1.777037] 0x000000280000-0x000000c80000 : "etc"
[    1.782164] 0x000000c80000-0x000001680000 : "kernel_1"
[    1.787752] 0x000001680000-0x000004640000 : "rootfs1"
[    1.793274] 0x000004640000-0x000005040000 : "kernel_2"
[    1.798870] 0x000005040000-0x000008000000 : "rootfs2"

Wanna make sure I get the commands right dont want to brick another nasbox.



Edited 1 time(s). Last edit at 12/14/2014 04:32PM by Buttzy10169.

ZyXel nsa320
segate baracuda 7200. 1TB nas compatible
on boot i have this message

[sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Buttzy,

Looks good to me. U-boot is in the 1st 1M and no bad block in it. But please try UART booting first to make sure you have a rescue mechanism.

Also, remember to save your envs listing, you will need to copy/paste them back in serial console (new u-boot envs are at different location).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 12/16/2014 03:00PM by bodhi.

Thanks Bodhi.

Will the commands for flashing be the same as for absintos?

And any idea on the usb's problem?

Buttzy10169 Wrote:
-------------------------------------------------------
> Thanks Bodhi.
>
> Will the commands for flashing be the same as for
> absintos?
>
> And any idea on the usb's problem?

It's same as in this thread:
http://forum.doozan.com/read.php?3,12381

Sorry I am not sure what USB problem?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

The USB issue i mentioned a few posts back.

Basically no usb drives i plug into the usb's are showing up. I posted the dmesg a few posts back aswel. and if i do an lsmod it looks like there is no usb modules loaded.

I have openmediavault installed on the nsa32. I remember something before about issue's with openmediavault on these box's. Also i wasnt able to boot from usb either before the installation of openmediavault.

After the uImage and uInitrd are loaded from the usb the usb's seem to stop functioning with your rootfs and 3.17 dt kernel.

Buttzy,

It's hard to tell what the problem was without seeing the log. But as a reminder, if booting kernel 3.17 with stock u-boot, dtb must be embedded inside uImage. And with this booting method, u-boot envs changes must be the same as in kernel 3.16.

If you can boot the new u-boot with UART, then I would upgrade it.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I dont have serial access to the device at the minute as its a gift for someone for xmas so its all back together for now.

Its not the stock uboot though i upgraded it a few months ago i think its daveygravey's?(i forget the name) uboot from a while back. im also using the 3.17 kernel with the dtb appended as per your instructions on the first page.

Which log do you need to see is it the syslog? the dmesg is attached to this post if thats any help.



Edited 1 time(s). Last edit at 12/22/2014 03:25PM by Buttzy10169.

Buttzy,

Yes, with davygravy's u-boot (which does not have FDT support), the DTB must be appended to uImage.

Everything looks great to me, espcially this about USB

[    2.243635] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    2.405385] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[    2.412145] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    2.433574] usb 1-1: Product: USB2.0 Hub
[    2.441144] hub 1-1:1.0: USB hub found
[    2.451392] hub 1-1:1.0: 4 ports detected

So what happen when you plug in the USB drive? does dmesg show the device connected? and if not was there error message?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 2 time(s). Last edit at 12/22/2014 04:10PM by bodhi.

bodhi,

After plugging in the usb nothing at all happens in dmesg or any where else as far as i can tell no errors or anything.

this is the output of lsmod:

Module                  Size  Used by
softdog                 1995  0 
quota_v2                3820  2 
quota_tree              6884  1 quota_v2
ipv6                  301690  54 
evdev                   9355  1 
fixed                   2289  0 
orion_wdt               5721  1 
hmac                    2441  0 
sha1_generic            1712  0 
sha1_arm                3362  0 
mv_cesa                10633  0 
gpio_keys               7522  0 
uio_pdrv_genirq         2857  0 
uio                     6877  1 uio_pdrv_genirq
dm_mod                 78639  0 
md_mod                104907  0 
sg                     21787  0 
sd_mod                 35448  3 
crc_t10dif              1032  1 sd_mod
crct10dif_common        1126  1 crc_t10dif
sata_mv                25912  2 
libata                149841  1 sata_mv
scsi_mod              170004  3 sg,libata,sd_mod

looks to me like theres no modules for usb loaded at all.

Buttzy,

Your dmesg looks OK:

[    1.838190] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.844847] ehci-pci: EHCI PCI platform driver
[    1.849391] ehci-orion: EHCI orion driver
[    1.853641] orion-ehci f1050000.ehci: EHCI Host Controller
[    1.859174] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    1.867110] orion-ehci f1050000.ehci: irq 30, io mem 0xf1050000
[    1.883496] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[    1.889721] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.896573] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.903851] usb usb1: Product: EHCI Host Controller
[    1.908751] usb usb1: Manufacturer: Linux 3.17.0-kirkwood-tld-1 ehci_hcd
[    1.915501] usb usb1: SerialNumber: f1050000.ehci
[    1.920979] hub 1-0:1.0: USB hub found
[    1.924832] hub 1-0:1.0: 1 port detected

So I'm not sure why. Regarding usb module, if you don't have any USB drive plugged in during boot then it's OK if it's not there. When you plug in one, the usb_storage module will load.

Anybody else using new kernel 3.17 on NSA320? do you see this problem?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Buttzy,

It sounds as though there is no power to the USB port.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

There is power to the usb ports as i load the uImage and uInitrd from a usb stick then the rootfs is on a sata drive inside the nas.

So somwhere between the loading of the kernel and the finished boot something is going wrong with the usb's.

The only thing changed between your stock roofs and what im using is the installation of openmediavault i think.

As in i used your rootfs booted and installed openmedia vault, But even before that any time tried to boot frm usb (with rootfs on the usb) the rootfs couldnt be found.

Buttzy,

So the problem is only after you've installed OMV? booting USB with the basic rootfs is OK?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

No even before installing OMV i could load uImage and uInitrd from usb but not rootfs.

I think i tried rootfs as ext3 and 4 but it would not boot tried different settings in uboot and nothing.

Then i put rootfs on sata out of curiosity and it booted straight away but the usb did not show up in debian after boot.

Buttzy,

Do you have serial console log for this? dmesg is not enough, rootfs mounting progress is shown only in serial console.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

No unfortunatly wont be able to get serial console until after xmas as i have the box packaged up as a gift at the moment.

So I will try get it asap.

It's possible it could end up being a problem with cheap usb stick but will have to wait and see.

Thank you for the given materials.
They helped run Debian 7 on Asus NAS-M25 with full equipment.




ps Sorry for machine translation, , I do not speak English.

balbes150,

Cool! can you post the output of dmesg? and boot log if you have serial console.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 12/25/2014 04:19PM by bodhi.

The console is, the conclusion from it in the file, additional information on the Asus NAS-M25 launch Debian can be found on the forum

Awesome!

Next question: which DTB you have used to append to the uImage? the link you posted above could not be translated to English!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

This file does not work yet support MTD partitions.

I posted it in the u-boot thread, but now I think it rather belongs here: http://forum.doozan.com/read.php?3,12381,19091#msg-19091
I have the same problem, usb is not powered after kernel start, thus usb boot device is missing.

Sorry to sound like a n00b, but I'm more than a little confused where some of these files come from.
I have a Pogoplug Mobile running linux-image-3.14.0-kirkwood-tld-1 thanks to Qui's and bodhi's help.

Do files like Debian-3.17.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 come from the process described at
http://projects.doozan.com/debian/ and in particular the http://projects.doozan.com/debian/kirkwood.debian-wheezy.sh script?

linux-3.17.0-kirkwood-tld-1-bodhi.tar.bz2 sounds like it comes from bodhi's patches to tld's patches to stock linux-3.17.0 configured for kirkwood; but after 15 minutes of web searching I can't find the source for either patch set. Where are these patches or source trees kept? The closest I can find in stock Debian is linux-image-3.16.0-0.bpo.4-kirkwood (where the bpo refers to Wheezy backports).

Finally, has anyone started to try migrating to Debian Jessie? If there are problems, now would be a good time to find them.

I'd like to claim I read all the relevant posts in this forum, but that seems not humanly possible!

ldoolitt,

linux-image-3.14.0-kirkwood-tld-1 is the kernel image which is included in my kernel released tarball linux-3.14.0-kirkwood-tld-1-bodhi.tar.bz2. Debian-3.14.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is the rootfs tarball. The 1st post of this thread describes the process how to install kernel and/or rootfs.

These are my ongoing released Kirkwood kernel builds. tld-xx is my own convention for a minor version in a kernel. So 3.14.0-kirkwood-tld-1 is version 3.14.0, minor version tld-1. When you see -kirkwood-tld-xx postfix, it's my build.

The released tarball linux-3.xx.0-kirkwood-tld-x-bodhi.tar.bz2 includes everything you need to build your own kernel from mainline kernel source tree (patches and config file are all you need). The kernel image is included in it for users who just want to install kernel.

The released tarball Debian-3.xx.0-kirkwood-tld-xx-rootfs-bodhi.tar.bz2 is the basic rootfs which is a complete Debian system ready to be used. It is basic Debian system where you can build upon by installing packages.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 3 time(s). Last edit at 01/29/2015 11:10AM by bodhi.