Welcome! Log In Create A New Profile

Advanced

NSA 325 V2 Debian Is Possible!

Posted by Buttzy10169 
marcint43
Re: NSA 325 V2 Debian Is Possible!
February 27, 2014 05:05PM
Marvell>> setenv arcNumber
Marvell>> setenv mainlineLinux no
Marvell>> printenv mainlineLinux
mainlineLinux=no
Marvell>> boot

NAND read: device 0 offset 0x4640000, size 0xa00000

Reading data from 0x503f800 -- 100% complete.
 10485760 bytes read: OK
## Booting image at 02000000 ...
   Image Name:   Linux-2.6.31.8
   Created:      2013-08-22   9:04:41 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5754856 Bytes =  5.5 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux..................................................................................................................................................................................
............................................................................................ done, booting the kernel.


and nothing happens next ...
marcint43
Re: NSA 325 V2 Debian Is Possible!
February 27, 2014 05:21PM
OK, I've got it :D

Answer:
just run:

Marvell>> run to_stock


everything is automaticaly changed to stock version, save uboot env and reboot device in original firmware :)


to go back:
Marvell>>  run to_linux

Marvel... ous idea :D !!!
Re: NSA 325 V2 Debian Is Possible!
February 27, 2014 09:29PM
bodhi Wrote:
-------------------------------------------------------
> Guys,
>
> Could you post your dmesg output for NSA325?
> (running kernel 3.xx.xx whether Debian or Arch).
>
> Thanks!

Anybody?

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: NSA 325 V2 Debian Is Possible!
February 28, 2014 04:09AM
Here is the dmesg from my nsa325 running the 3.13.2 kernel on debian.



Edited 1 time(s). Last edit at 02/28/2014 04:10AM by Buttzy10169.
Attachments:
open | download - nsa325-3-13-2.dmesg (16.6 KB)
Re: NSA 325 V2 Debian Is Possible!
February 28, 2014 08:38AM
I need to plug-in my 325, but when that is up I will get you a log with that latest Arch kernel.

Oh, and @marcint43 , yeah, that was the idea :)



Edited 1 time(s). Last edit at 02/28/2014 08:39AM by WarheadsSE.
Re: NSA 325 V2 Debian Is Possible!
February 28, 2014 02:05PM
Thanks Buttzy!

-bodhi
===========================
Forum Wiki
bodhi's corner
marcint43
Re: NSA 325 V2 Debian Is Possible!
March 01, 2014 01:20PM
FYI: I just submitted bug in LVM2 package in that debian wheezy with kirkwood instalation:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740456

LVM seems to works but message during any manipulation of lvm volumes is strange ... I am seriously afraid of that ...

Maybe you know what does it mean: ?

lvcreate, lvremove, lvchange...evertime I see that:

ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors]: mlock failed: Cannot allocate memory
4 logical volume(s) in volume group "eld4" now active
ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors]: munlock failed: Cannot allocate memory
Re: NSA 325 V2 Debian Is Possible!
March 01, 2014 02:11PM
since its a memory error is it possible they are just using too much memory and since memory is so limited in the device its running out?

( I don't know much about lvm and such )
Re: NSA 325 V2 Debian Is Possible!
March 02, 2014 05:52AM
Here is dmesg from Arch
Linux nsa325 3.13.5-1-ARCH #1 PREEMPT Sun Feb 23 02:58:30 MST 2014 armv5tel GNU/Linux
Attachments:
open | download - nsa325-dmesg.txt (16.1 KB)
marcint43
Re: NSA 325 V2 Debian Is Possible!
March 02, 2014 04:45PM
probably found solution.

From version: lvm2: 2.02.99 -> changelog: Skip mlocking [vectors] on arm architecture.

...this probably will be solution. Just not to allocate not necessary memory (I guess).
Now I am in the middle of copying terabytes of data so I need to wait, but tommorow I will install lvm2 from debian testing:

lvm2:
Installed: 2.02.95-8
Candidate: 2.02.104-2
...loooooooot of bug fixes

dependency:
dmsetup libc6 libdevmapper1.02.1 lvm2

dmsetup:
Installed: 2:1.02.74-8
Candidate: 2:1.02.83-2

libdevmapper1.02.1:
Installed: 2:1.02.74-8
Candidate: 2:1.02.83-2

I little afraid of that:
libc6:
Installed: 2.13-38
Candidate: 2.17-97
marcint43
Re: NSA 325 V2 Debian Is Possible!
March 02, 2014 04:46PM
One thing is little irritating: there is no any LED blinking during HDD work ... anyone know how to do that feature ?
Re: NSA 325 V2 Debian Is Possible!
March 02, 2014 04:58PM
WarheadsSE Wrote:
-------------------------------------------------------
> Here is dmesg from Arch
>
> Linux nsa325 3.13.5-1-ARCH #1 PREEMPT Sun Feb 23
> 02:58:30 MST 2014 armv5tel GNU/Linux
>

Thanks WarheadsSE!

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: NSA 325 V2 Debian Is Possible!
March 02, 2014 05:28PM
there are posts about the LEDs in Bodhi's thread I guess I forgot to add them here.

basically you do:
ls -l /sys/class/leds
find the hdd leds then:
cat /sys/class/leds/(led name)/trigger
it gives a list of triggers then:
echo (trigger you want) > /sys/class/leds/(led name)/trigger

(on my tablet so difficult to give proper full instructions)
marcint43
Re: NSA 325 V2 Debian Is Possible!
March 03, 2014 03:11PM
yeah, I found that "led's triggers" ... but I have no idea how to script that ? permanent iostat in the background and echo commands to that trigger file ? ;-) ...cpu will do nothing except blinking led :D
I guess that there are other "more normal" solutions ...


Just one info about LVM... version 2.02.104-2 (available in testing now) is not affected with this bugs of "vector" memory allocations :) LVM works fantastic :)

Now I have stable 135MBytes/sec transfer in write to my disks :D (during mdadm sync)
(sometimes up to 154MBytes/sec)
Re: NSA 325 V2 Debian Is Possible!
March 04, 2014 02:47AM
if you cat the trigger file you will get a small list 2 of the options should be for hdd.

like ide1 something and ide2 ( not sure what they are don't have access to mine at the minute to check)

then you can just put in your rc.local file:
echo (trigger name) > "/sys/class/leds/(led name)/trigger"

or something to that effect then the hdd led will blink whenever the hdd is being accessed.
Re: NSA 325 V2 Debian Is Possible!
March 04, 2014 03:41PM
Hi,
i installed it on a usb flash drive, and it boots fine as long as I have a HDD in the system. When I remove it, the system goes in to a bootloop, right after
[   26.902833] orion_wdt: Initial timeout 21 sec

How can I fix this?
thanks



Edited 1 time(s). Last edit at 03/04/2014 03:53PM by mali.
marcint43
Re: NSA 325 V2 Debian Is Possible!
March 04, 2014 04:31PM
At the beginning I was testing this solution without any HDD , just serial cable and creating flash drive ...
So absence of HDD is not a problem, probably you have sth wrong with your OS...

give us more details...

at which stage this message appears ?

Do you have serial ? could you attach output of "printenv" from u-boot (or sth like similar - type "help" if not sure) command ?
could you attach here all messages appears on your screen ? (minicom log file)

How you prepared ?

1st you have to have pendrive with "u-boot" configurator, when this is done, you have to insert another (or the same after formating) pendrive with 2 partitions - 1st - boot files without ANY directory (even lost+found), and 2nd - normal partition with OS (in example debian wheezy with kirkwood).
2nd partition must have label "rootfs".
marcint43
Re: NSA 325 V2 Debian Is Possible!
March 04, 2014 04:32PM
*How you prepared ? .... pendrives
marcint43
Re: NSA 325 V2 Debian Is Possible!
March 04, 2014 04:39PM
> echo (trigger name) > "/sys/class/leds/(led name)/trigger"

bingo! this was so simple ...

possibilities:
[none] nand-disk timer oneshot ide-disk1 ide-disk2 heartbeat gpio default-on

Do you know what are "oneshot/heartbeat/gpio" for ?
Re: NSA 325 V2 Debian Is Possible!
March 04, 2014 11:23PM
marcint43 Wrote:
-------------------------------------------------------
>
> > echo (trigger name) > "/sys/class/leds/(led
> name)/trigger"
>
>
> bingo! this was so simple ...
>
> possibilities:
> [none] nand-disk timer oneshot ide-disk1 ide-disk2
> heartbeat gpio default-on
>
> Do you know what are "oneshot/heartbeat/gpio" for
> ?

one-shot: blink once
heartbeat: continuously flashing at a slow rate like a heartbeat.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: NSA 325 V2 Debian Is Possible!
March 05, 2014 03:25AM
Sorry for the lack of information, i tought this may be a known issue.
marcint43 Wrote:
-------------------------------------------------------
> give us more details...
>
> at which stage this message appears ?
Uboot starts, reads and boots the kernel, after some lines of kernel log, with the last one alwaysbeing:
[   26.314925] orion_wdt: Initial timeout 21 sec
the systems resets, and Uboot starts again.

> Do you have serial ? could you attach output of
> "printenv" from u-boot (or sth like similar - type
bootargs=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/nfs rw init=/init
bootdelay=2
baudrate=115200
loads_echo=0
ipaddr=10.4.52.165
serverip=10.4.52.7
rootpath=/srv/ubuntu
netmask=255.255.255.0
nandEcc=1bit
MODEL_ID=AE03
PRODUCT_NAME=NSA-325v2
FEATURE_BIT=00
CONTRY_TYPE=FF
VENDOR_NAME=MitraStar Technology Corp.
run_diag=yes
console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x7f00000@0x100000(root)
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
lcd0_enable=0
lcd0_params=640x480-16@60
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev[0]:fxs,dev[1]:fxo
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
image_multi=yes
ethact=egiga0
arcNumber=4495
bootargs_stock=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/nfs rw init=/init
bootargs_linux=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=LABEL=rootfs loglevel=8
bootcmd_linux=setenv bootargs $(bootargs_linux); mw.l f1010100 0020c000; usb reset; ext2load usb 0:1 $(loadaddr) /uImage; ext2load usb 0:1 0x01100000 /uInitrd; bootm $(loadaddr) 0x01100000
bootcmd_stock=setenv bootargs $(bootargs_stock); nand read.e $(loadaddr) $(kernel_addr) 0xA00000; bootm $(loadadr)
to_stock=setenv mainlineLinux no; setenv bootcmd \'run bootcmd_stock\'; saveenv; reset
to_linux=setenv mainlineLinux yes; setenv bootcmd \'run bootcmd_linux\'; saveenv; reset
bootcmd='run bootcmd_linux'
ethaddr=10:7b:ef:bc:57:9f
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=yes
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
disaMvPnp=no
enaAutoRecovery=yes
kernel_addr=0xc80000
pcieTune=no
pcieTune1=no

> could you attach here all messages appears on your
> screen ? (minicom log file)

         __  __                      _ _                                                       
        |  \/  | __ _ _ ____   _____| | |                                                        
        | |\/| |/ _` | '__\ \ / / _ \ | |                                                           
        | |  | | (_| | |   \ V /  __/ | |                                                                  
        |_|  |_|\__,_|_|    \_/ \___|_|_|                                                                  
 _   _     ____              _                                                                             
| | | |   | __ )  ___   ___ | |_                                                                           
| | | |___|  _ \ / _ \ / _ \| __|                                                                                  
| |_| |___| |_) | (_) | (_) | |_                                                                                   
 \___/    |____/ \___/ \___/ \__|                                                                                  
 ** MARVELL BOARD: DB-88F6282A-BP LE                                                                                       
                                                                                                                           
U-Boot 1.1.4 (Jul 18 2013 - 10:47:29) Marvell version: 3.5.9                                                               
                                                                                                                           
U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00                                                                           

Soc: 88F6282 A1CPU running @ 1600Mhz L2 running @ 533Mhz
SysClock = 533Mhz , TClock = 200Mhz 

DRAM (DDR3) CAS Latency = 7 tRP = 8 tRAS = 24 tRCD=8
DRAM CS[0] base 0x00000000   size 512MB 
DRAM Total size 512MB  16bit width
Addresses 10M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (10M - 7M): Done
NAND:128 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)
Kernel address is 0xc80000.

Streaming disabled 
Write allocate disabled


USB 0: host mode
        [BlueDBG] reseting SoC Pex[0]  0 ...
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
        [BlueDBG] reseting SoC Pex[1]  0 ...
        [BlueDBG] reseting SoC Pex[1]  1 ...
        [BlueDBG] reseting SoC Pex[1]  2 ...
        [BlueDBG] reseting SoC Pex[1]  3 ...
        [BlueDBG] reseting SoC Pex[1]  4 ...
        [BlueDBG] reseting SoC Pex[1]  5 ...
        [BlueDBG] reseting SoC Pex[1]  6 ...
        [BlueDBG] reseting SoC Pex[1]  7 ...
        [BlueDBG] reseting SoC Pex[1]  8 ...
        [BlueDBG] reseting SoC Pex[1]  9 ...
        [BlueDBG] reseting SoC Pex[1]  10 ...
PEX 1: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0 
(Re)start USB...
USB:   scanning bus for devices... 3 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
1 Storage Device(s) found
.
.........................
....................
.....
.........................
.........................
.........................
.........................
.........................
.........................
.........................
..

2399792 bytes read
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
.........................
............
.............
.........................

6568066 bytes read
## Booting image at 02000000 ...
   Image Name:   Linux-3.13.1-kirkwood-tld-2
   Created:      2014-02-05  19:30:49 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2399728 Bytes =  2.3 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 01100000 ...
   Image Name:   initramfs-3.13.1-kirkwood-tld-2
   Created:      2014-02-05  19:31:01 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6568002 Bytes =  6.3 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

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.13.1-kirkwood-tld-2 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 PREEMPT Tue Feb 4 03:19:07 PST 2014
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: ZyXEL NSA325 2-Bay Power Media Server
[    0.000000] Memory policy: Data cache writeback
[    0.000000] On node 0 totalpages: 131072
[    0.000000] free_area_init_node: node 0, pgdat c06aa824, node_mem_map c0719000
[    0.000000]   Normal zone: 1024 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal 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=LABEL=rootfs loglevel=8
[    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: 506064K/524288K available (4659K kernel code, 346K rwdata, 1588K rodata, 211K init, 425K bss, 18224K reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 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 - 0xc06220ac   (6249 kB)
[    0.000000]       .init : 0xc0623000 - 0xc0657e4c   ( 212 kB)
[    0.000000]       .data : 0xc0658000 - 0xc06ae824   ( 347 kB)
[    0.000000]        .bss : 0xc06ae824 - 0xc0718d6c   ( 426 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:114
[    0.000000] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474836475ns
[    0.000000] Console: colour dummy device 80x30
[   20.186154] Calibrating delay loop... 1594.16 BogoMIPS (lpj=7970816)
[   20.225969] pid_max: default: 32768 minimum: 301
[   20.226055] Security Framework initialized
[   20.226113] Mount-cache hash table entries: 512
[   20.226612] Initializing cgroup subsys devices
[   20.226632] Initializing cgroup subsys freezer
[   20.226643] Initializing cgroup subsys net_cls
[   20.226651] Initializing cgroup subsys blkio
[   20.226715] CPU: Testing write buffer coherency: ok
[   20.227016] Setting up static identity map for 0x469248 - 0x469284
[   20.228681] devtmpfs: initialized
[   20.230530] prandom: seed boundary self test passed
[   20.233527] prandom: 100 self tests passed
[   20.233535] pinctrl core: initialized pinctrl subsystem
[   20.233790] regulator-dummy: no parameters
[   20.234053] NET: Registered protocol family 16
[   20.234346] DMA: preallocated 256 KiB pool for atomic coherent allocations
[   20.234824] cpuidle: using governor ladder
[   20.234839] cpuidle: using governor menu
[   20.234912] Kirkwood: MV88F6282-Rev-A1, TCLK=200000000.
[   20.234928] Feroceon L2: Enabling L2
[   20.234958] Feroceon L2: Cache support initialised.
[   20.235209] initial MPP regs: 21111111 00103311 00051100 00000000 00000000 00000000 00000000
[   20.235232]   final MPP regs: 21111111 00003311 00051100 00000000 00000000 00000000 00000000
[   20.235723] Kirkwood PCIe port 0: link up
[   20.235732] PCI: bus0 uses PCIe port 0
[   20.235815] PCI host bridge to bus 0000:00
[   20.235831] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xe7ffffff]
[   20.235840] pci_bus 0000:00: root bus resource [io  0x1000-0xffff]
[   20.235849] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[   20.235878] pci 0000:00:00.0: [11ab:6282] type 00 class 0x058000
[   20.235900] pci 0000:00:00.0: reg 0x10: [mem 0xf1000000-0xf10fffff 64bit pref]
[   20.235912] pci 0000:00:00.0: reg 0x18: [mem 0x00000000-0x1fffffff]
[   20.236002] pci 0000:00:00.0: supports D1 D2
[   20.236110] pci 0000:00:01.0: [1033:0194] type 00 class 0x0c0330
[   20.236143] pci 0000:00:01.0: reg 0x10: [mem 0x90000000-0x90001fff 64bit]
[   20.236244] pci 0000:00:01.0: PME# supported from D0 D3hot
[   20.236353] PCI: bus0: Fast back to back transfers disabled
[   20.236365] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 00
[   20.236392] pci 0000:00:01.0: BAR 0: assigned [mem 0xe0000000-0xe0001fff 64bit]
[   20.238719] bio: create slab <bio-0> at 0
[   20.239062] vgaarb: loaded
[   20.239224] usbcore: registered new interface driver usbfs
[   20.239270] usbcore: registered new interface driver hub
[   20.239353] usbcore: registered new device driver usb
[   20.239816] Switched to clocksource orion_clocksource
[   20.255782] NET: Registered protocol family 2
[   20.256323] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[   20.256379] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[   20.256430] TCP: Hash tables configured (established 4096 bind 4096)
[   20.256483] TCP: reno registered
[   20.256493] UDP hash table entries: 256 (order: 0, 4096 bytes)
[   20.256513] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[   20.256678] NET: Registered protocol family 1
[   20.256929] RPC: Registered named UNIX socket transport module.
[   20.256938] RPC: Registered udp transport module.
[   20.256943] RPC: Registered tcp transport module.
[   20.256949] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   20.257029] PCI: CLS 32 bytes, default 32
[   20.257221] Unpacking initramfs...
[   20.662196] Freeing initrd memory: 6408K (c1101000 - c1743000)
[   20.662274] NetWinder Floating Point Emulator V0.97 (double precision)
[   20.662759] audit: initializing netlink socket (disabled)
[   20.662805] type=2000 audit(0.470:1): initialized
[   20.663459] zbud: loaded
[   20.663593] VFS: Disk quotas dquot_6.5.2
[   20.663637] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[   20.663932] NFS: Registering the id_resolver key type
[   20.663986] Key type id_resolver registered
[   20.663993] Key type id_legacy registered
[   20.664007] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[   20.664014] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   20.664143] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[   20.664355] msgmni has been set to 1000
[   20.664455] Key type big_key registered
[   20.665843] alg: No test for stdrng (krng)
[   20.665916] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[   20.665925] io scheduler noop registered
[   20.665931] io scheduler deadline registered
[   20.665955] io scheduler cfq registered (default)
[   20.666133] mv_xor mv_xor.0: Marvell shared XOR driver
[   20.699875] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   20.739862] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   20.739945] mv_xor mv_xor.1: Marvell shared XOR driver
[   20.779862] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[   20.819857] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[   20.820058] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[   20.840457] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33, base_baud = 12500000) is a 16550A
[   21.528957] console [ttyS0] enabled
[   21.533165] NAND device: Manufacturer ID: 0x92, Chip ID: 0xf1 (Eon NAND 128MiB 3,3V 8-bit)
[   21.541490] NAND device: 128MiB, SLC, page size: 2048, OOB size: 64
[   21.547785] Scanning device for bad blocks
[   21.613341] Creating 9 MTD partitions on "orion_nand":
[   21.618520] 0x000000000000-0x000000100000 : "uboot"
[   21.623683] 0x000000100000-0x000000180000 : "uboot_env"
[   21.629095] 0x000000180000-0x000000200000 : "key_store"
[   21.634549] 0x000000200000-0x000000280000 : "info"
[   21.639507] 0x000000280000-0x000000c80000 : "etc"
[   21.644446] 0x000000c80000-0x000001680000 : "kernel_1"
[   21.649763] 0x000001680000-0x000004640000 : "rootfs1"
[   21.655050] 0x000004640000-0x000005040000 : "kernel_2"
[   21.660415] 0x000005040000-0x000008000000 : "rootfs2"
[   21.666071] libphy: Fixed MDIO Bus: probed
[   21.680669] libphy: orion_mdio_bus: probed
[   21.684841] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[   21.694015] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 10:7b:ef:bc:57:9f
[   21.702915] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   21.709467] ehci-pci: EHCI PCI platform driver
[   21.714005] ehci-orion: EHCI orion driver
[   21.718077] orion-ehci orion-ehci.0: EHCI Host Controller
[   21.723534] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[   21.731257] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[   21.749838] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[   21.755911] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   21.762747] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   21.770014] usb usb1: Product: EHCI Host Controller
[   21.774912] usb usb1: Manufacturer: Linux 3.13.1-kirkwood-tld-2 ehci_hcd
[   21.781654] usb usb1: SerialNumber: orion-ehci.0
[   21.786647] hub 1-0:1.0: USB hub found
[   21.790460] hub 1-0:1.0: 1 port detected
[   21.794770] mousedev: PS/2 mouse device common for all mice
[   22.109858] usb 1-1: new high-speed USB device number 2 using orion-ehci
[   22.261267] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[   22.268001] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[   22.275190] usb 1-1: Product: USB2.0 Hub
[   22.279724] hub 1-1:1.0: USB hub found
[   22.283765] hub 1-1:1.0: 4 ports detected
[   22.560142] usb 1-1.2: new high-speed USB device number 3 using orion-ehci
[   22.671015] usb 1-1.2: New USB device found, idVendor=1f75, idProduct=0916
[   22.677929] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   22.685292] usb 1-1.2: Product: Intenso Speed Line
[   22.690129] usb 1-1.2: Manufacturer: Innostor Technology
[   22.695480] usb 1-1.2: SerialNumber: 13100900032031
[   22.809839] rtc-mv rtc-mv: internal RTC not ticking
[   22.814813] i2c /dev entries driver
[   22.818703] orion_gpio_is_valid: invalid GPIO 12
[   22.823817] drop_monitor: Initializing network drop monitor service
[   22.830268] TCP: cubic registered
[   22.833598] NET: Registered protocol family 17
[   22.838143] Key type dns_resolver registered
[   22.842777] registered taskstats version 1
[   22.847510] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[   22.854648] Freeing unused kernel memory: 208K (c0623000 - c0657000)
Loading, please wait...
[   22.910389] udevd[56]: starting version 175
[   22.999511] xhci_hcd 0000:00:01.0: xHCI Host Controller
[   23.034690] xhci_hcd 0000:00:01.0: new USB bus registered, assigned bus number 2
[   23.087887] SCSI subsystem initialized
[   23.108587] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[   23.138535] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   23.162468] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[   23.177716] libata version 3.00 loaded.
[   23.189908] usb usb2: Product: xHCI Host Controller
[   23.194807] usb usb2: Manufacturer: Linux 3.13.1-kirkwood-tld-2 xhci_hcd
[   23.205107] sata_mv sata_mv.0: version 1.28
[   23.209375] sata_mv sata_mv.0: cannot get optional clkdev
[   23.230395] scsi0 : usb-storage 1-1.2:1.0
[   23.245159] usbcore: registered new interface driver usb-storage
[   23.262186] usb usb2: SerialNumber: 0000:00:01.0
[   23.267024] sata_mv sata_mv.0: slots 32 ports 2
[   23.289226] hub 2-0:1.0: USB hub found
[   23.297810] scsi1 : sata_mv
[   23.308083] hub 2-0:1.0: 2 ports detected
[   23.314415] xhci_hcd 0000:00:01.0: xHCI Host Controller
[   23.319685] xhci_hcd 0000:00:01.0: new USB bus registered, assigned bus number 3
[   23.327250] scsi2 : sata_mv
[   23.330578] ata1: SATA max UDMA/133 irq 21
[   23.334693] ata2: SATA max UDMA/133 irq 21
[   23.339036] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003
[   23.345883] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   23.354007] usb usb3: Product: xHCI Host Controller
[   23.358909] usb usb3: Manufacturer: Linux 3.13.1-kirkwood-tld-2 xhci_hcd
[   23.365777] usb usb3: SerialNumber: 0000:00:01.0
[   23.371166] hub 3-0:1.0: USB hub found
[   23.374965] hub 3-0:1.0: 2 ports detected
[   23.679851] ata1: SATA link down (SStatus 0 SControl F300)
[   24.049852] ata2: SATA link down (SStatus 0 SControl F300)
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Waiting for root file system ... [   24.230724] scsi 0:0:0:0: Direct-Access     Intenso  Speed Line       1.00 PQ: 0 ANSI: 6
[   24.261193] sd 0:0:0:0: [sda] 15257600 512-byte logical blocks: (7.81 GB/7.27 GiB)
[   24.269220] sd 0:0:0:0: [sda] Write Protect is off
[   24.274179] sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
[   24.279665] sd 0:0:0:0: [sda] No Caching mode page found
[   24.285035] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   24.294536] sd 0:0:0:0: [sda] No Caching mode page found
[   24.299907] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   24.309409]  sda: sda1 sda2 sda3
[   24.316294] sd 0:0:0:0: [sda] No Caching mode page found
[   24.322202] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   24.328323] sd 0:0:0:0: [sda] Attached SCSI removable disk
[   24.342002] sd 0:0:0:0: Attached scsi generic sg0 type 0
done.
Begin: Running /scripts/local-premount ... done.
[   24.806402] EXT3-fs (sda2): mounted filesystem with ordered data mode
[   24.812961] kjournald starting.  Commit interval 5 seconds
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
INIT: version 2.88 booting
[info] Using makefile-style concurrent boot in runlevel S.
[....] Starting the hotplug events dispatcher: udevd[   25.780406] udevd[263]: starting version 175
. ok 
[ ok ] Synthesizing the initial hotplug events...[   26.043614] input: gpio-keys as /devices/platform/gpio-keys/input/input0
done.
[....] Waiting for /dev to be fully populated...[   26.159288] nsa3xx-hwmon nsa3xx-hwmon: initialized
[   26.166839] rtc-pcf8563 0-0051: chip found, driver version 0.4.3
[   26.201927] rtc-pcf8563 0-0051: rtc core: registered rtc-pcf8563 as rtc0
[   26.283315] alg: hash: Test 1 failed for mv-hmac-sha1
[   26.291040] 00000000: 0c aa 9f d5 37 c3 79 3a 91 d9 21 5f 42 2b 2c 24
[   26.305785] 00000010: b7 c3 16 0c
[   26.314925] orion_wdt: Initial timeout 21 sec
After this it restarts with uboot

> How you prepared ?
>
> 1st you have to have pendrive with "u-boot"
> configurator, when this is done, you have to
> insert another (or the same after formating)
> pendrive with 2 partitions - 1st - boot files
> without ANY directory (even lost+found), and 2nd -
> normal partition with OS (in example debian wheezy
> with kirkwood).
> 2nd partition must have label "rootfs".
yes, i did this:
i used a small pendrive with fat32 for the usb-debian-uboot.tar.gz

On the second drive that I intend to use for the system I have 3 partitions
1. primary, ext2, labeld boot, 256MB
2. primary, ext3, labeld rootfs, 6000MB
3. primary, swap, 512MB
and some 600MB are unpartitioned.

i extracted bodhi's rootfs to the 2nd partition and copied the content of the /boot/ directory to the 1th partition.
/boot$ ls -l
total 19340
-rw-r--r-- 1 root root 1698808 Feb  4 15:20 System.map-3.13.1-kirkwood-tld-2
-rw-r--r-- 1 root root  121807 Feb  4 11:45 config-3.13.1-kirkwood-tld-2
-rw-r--r-- 1 root root 6568002 Feb  5 20:30 initrd.img-3.13.1-kirkwood-tld-2
-rw-r--r-- 1 root root 2399792 Feb  5 20:30 uImage
-rw-r--r-- 1 root root 6568066 Feb  5 20:31 uInitrd
-rw-r--r-- 1 root root 2399728 Feb  4 15:20 vmlinuz-3.13.1-kirkwood-tld-2

I found out that this seems to be some kind of timing issue: yesterday i let the system rebooted non-stop, today I interrupted the bootloop by entering uboot and getting the printenv information. After a reboot with the command reset, debian booted without an issue.

Has anyone experienced something similar, or knows how to fix this?
marcint43
Re: NSA 325 V2 Debian Is Possible!
March 05, 2014 07:51AM
orion_wdt is a watchdog driver for Orion/Kirkwood processors ... this seems that kernel code is to busy to reset timer of watchdog... some problems with hardware probably.

http://lxr.free-electrons.com/source/drivers/watchdog/orion_wdt.c
166 wdt_max_duration = WDT_MAX_CYCLE_COUNT / wdt_tclk;
179 pr_info("Initial timeout %d sec%s\n",
180 orion_wdt.timeout, nowayout ? ", nowayout" : "");

0xffffffff / 0xC30C30C = 0x15 == 21 seconds

I don tknow how "wdt_tclk" is set, and why to 0xC30C30C value...




System loading kernel properly so this seems not to be strictly OS but rather hardware issue ...rather....

Let's look at line 0,2sec before timeout:
[....] Waiting for /dev to be fully populated... <<<without newline char, there are other messages, so seems like not finished process of /dev populating...


What devices do you have plugged into ports ?
usb pendrive... ?
(disks internal ??)
(disk external maybe ??)


When you entered into u-boot you gave time to - for example some device connected to your system - to "be ready to use" ... so when you type reset - device is powered for some time and "has time to be ready"...

I have had pendrive before (patriot memory, 16G, one of the very fast pendrive series) which one was not initialized at all... even at uboot stage.
Maybe you have one which one gives similar effects ?

Maybe you have very slow pendrive or not fully recognized by kernel ?

FIRST TRY: Could you use any other pendrive ?
Re: NSA 325 V2 Debian Is Possible!
March 05, 2014 11:45AM
No other devices are connected, just the pendrive.
I'm using an Intenso Speed Line 8GB with USB 3.0 (but on the backside).
I also thought it could be an issue with the pendrive being to slow on initialisation.
The strange thing is, that if I plug in the internal harddrive, booting from the pendrive works everytime. Shouldn't it take even longer to fully initialize an additional device?

Will try with a different pendrive. thanks
Re: NSA 325 V2 Debian Is Possible!
March 05, 2014 01:33PM
Due to the order of initialization, the delay introduced by the IDE reset command & related initialization/filesystem read, etc could have provided you the time for the USB to properly cycle up before the usb boot sequence.
Re: NSA 325 V2 Debian Is Possible!
March 05, 2014 02:54PM
@mali, if you can get a Sandisk brand thumb drive, try that. Also, Patriot brand is very unreliable for booting.

-bodhi
===========================
Forum Wiki
bodhi's corner
marcint43
Re: NSA 325 V2 Debian Is Possible!
March 05, 2014 05:53PM
[....] Synthesizing the initial hotplug events...[   30.453726] input: gpio-keys as /devices/platform/gpio-keys/input/input0
done.
[....] Waiting for /dev to be fully populated...[   30.603350] alg: hash: Test 1 failed for mv-hmac-sha1
[   30.608451] 00000000: 0c aa 9f d5 37 c3 79 3a 91 d9 21 5f 42 2b 2c 24
[   30.626183] 00000010: b7 c3 16 0c
[   30.631806] nsa3xx-hwmon nsa3xx-hwmon: initialized
[   30.652746] rtc-pcf8563 0-0051: chip found, driver version 0.4.3
[   30.686584] orion_wdt: Initial timeout 21 sec
[   30.705766] rtc-pcf8563 0-0051: rtc core: registered rtc-pcf8563 as rtc0
done.   <<<<<------ THIS LINE SHOULD APPEAR, BECAUSE IS NOT - YOU HAVE PROBLEMS (I guess)
[....] Setting parameters of disc: (none). ok 
[   32.276615] md: md13 stopped.
[   32.286661] md: bind<sdc13>
[   32.296878] md: bind<sda13>
[   32.324409] md: raid1 personality registered for level 1
[   32.333299] md/raid1:md13: active with 2 out of 2 mirrors
(...)

starting of md devices

Re: NSA 325 V2 Debian Is Possible!
March 06, 2014 07:04AM
Ok, i switched to a Lexar JumpDrive Firefly 8G, and it worked the first boot. After that Uboot stopped at
USB:   scanning bus for devices... 3 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
T
Also no luck with a Sandisk Cruzer Edge, same issue as with the Intenso.
Somewhere I should have another Sandisk drive, maybe that one works.
marcint43
Re: NSA 325 V2 Debian Is Possible!
March 06, 2014 07:20AM
exactly the same problem when I was trying tu use patriot memory, ...this pendrive never worked for my under zyxel
Now I am using veeery old sandisk 512mb.

try another
marcint43
Re: NSA 325 V2 Debian Is Possible!
March 25, 2014 01:30AM
@mali: any results ?
Re: NSA 325 V2 Debian Is Possible!
March 25, 2014 05:06PM
@marcint43: yes, I bought a new Pendrive: Hama FlashPen Probo 16GB USB-Stick USB 3.0 ( http://www.amazon.de/Hama-FlashPen-Probo-USB-Stick-schwarz/dp/B004WNFFTC/ref=cm_cr_pr_product_top ). It seems to be relabeled Kingston drive.
Works perfectly, can boot with inserted HDDs, and also with just the Pendrive connected.
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: