Welcome! Log In Create A New Profile

Advanced

NSA 325 V2 Debian Is Possible!

Posted by Buttzy10169 
Eddie87
Re: NSA 325 V2 Debian Is Possible!
January 05, 2015 04:17PM
Hi Bodhi,

I think the issue was a faulty partition on my USB as I swear I had labeled the USB drive rootfs and it wasn't working. Either way, it's now booting 3.17 with a drive attached in slot 1. It's still not recognising the second SATA port though. There is no power to it it would appear. Is there anything I can do to get it working?

Thanks,

Ed
Re: NSA 325 V2 Debian Is Possible!
January 05, 2015 09:46PM
@Eddie,

Buttzy is having the same problem here: http://forum.doozan.com/read.php?2,12096,19102#msg-19102

Unfortunately, I'm away and dont have access to my NSA325. So I can only look for the problem in source code. Perhaps you should downgrade to 3.16 temporarily if you need the 2nd HDD.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: NSA 325 V2 Debian Is Possible!
January 05, 2015 09:57PM
@WarheadsSE,

From what I can tell (without close scrutity) the DTS has all definition that you have in your patch for non-FDT kernel (nsa_325_setup.c). GPIO 47 was defined, and showed up in the running device-tree. Buttzy has attached the proc device tree in this post: http://forum.doozan.com/read.php?2,12096,19109#msg-19109

I'm attaching in this post the 3.17 patch which includes the NSA325 DTS.

Coulld you take a look and see if there is any thing wrong that I've missed?.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Attachments:
open | download - linux-3.17.0-kirkwood-tld-1.patch (97.1 KB)
Re: NSA 325 V2 Debian Is Possible!
January 06, 2015 02:31AM
Re: NSA 325 V2 Debian Is Possible!
January 06, 2015 03:37AM
bodhi,

I have tried several times to boot the new uboot via UART but have not been successful. Maybe the cable / connection I'm using is to unstable.

Is it safe to just flash the new uboot? And is there anything I need to do after? Besides setup the uboot to boot Debian?

As in is there any special settings from the original uboot I need to keep / transfer?

edit:

I tried compileing the new 3.18.1 kernel with your patch (everything patches ok except 1 of the dvb frontends i think) and booted the device with that and the dtb with the same probem of second sata not working.



Edited 1 time(s). Last edit at 01/06/2015 08:32AM by Buttzy10169.
Re: NSA 325 V2 Debian Is Possible!
January 06, 2015 10:36AM
Buttzy,

The NSA325 u-boot is here in this thread:
http://forum.doozan.com/read.php?3,12381,17420#msg-17420

You should try UART booting with the small test version at the end of the above post (uboot.2013.10-tld-1-test.nsa325.uart.kwb)

Once you can UART booting with the small u-boot image, then you can flash the real version (U-Boot 2013.10-tld-1) without worrying.

> As in is there any special settings from the
> original uboot I need to keep / transfer?

Copy the list of old u-boot envs and save it to a text file. You can then past them back in serial console. The new u-boot uses a different location for envs from the stock u-boot, so it is safe to save them.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: NSA 325 V2 Debian Is Possible!
January 06, 2015 10:41AM
bodhi,

I have tried both versions of the uboot in that thread and so far have not been able to get it to boot.

I think the highest I got on it was about 30% yesterday.
Re: NSA 325 V2 Debian Is Possible!
January 06, 2015 11:32AM
Buttzy10169 Wrote:
-------------------------------------------------------
> bodhi,
>
> I have tried both versions of the uboot in that
> thread and so far have not been able to get it to
> boot.
>
> I think the highest I got on it was about 30%
> yesterday.

You meant that you have tried uboot.2013.10-tld-1-test.nsa325.uart.kwb ?

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: NSA 325 V2 Debian Is Possible!
January 06, 2015 11:38AM
bodhi,

Yes the UART version and the band version through UART but at most I think I got up to 30%.
Re: NSA 325 V2 Debian Is Possible!
January 06, 2015 12:21PM
Buttzy,

That's very strange. Perhaps your serial connection has something to do with it?

Usually:

uboot.2013.10-tld-1.nsa325.mtd0.kwb sometimes stop at 70%.

uboot.2013.10-tld-1.nsa325.uart.kwb always loaded 100% for me and many others, but not for some users.

uboot.2013.10-tld-1-test.nsa325.uart.kwb never failed to load 100%.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Eddie87
Re: NSA 325 V2 Debian Is Possible!
January 06, 2015 12:52PM
I've managed to use uboot.2013.10-tld-1-test.nsa325.uart.kwb without any problems and have upgraded the uboot to: U-Boot 2013.10-tld-1 (Aug 29 2014 - 22:07:26).

I had to use this version though (http://forum.doozan.com/read.php?3,12381,16787#msg-16787) as the one you link to Bodhi I couldn't get to work.

It still doesn't power on/recognise the second sata port though.... :)
Eddie87
Re: NSA 325 V2 Debian Is Possible!
January 06, 2015 12:56PM
Buttzy, I had issues with UART loading until I read somewhere that you need to wait until the blue power LED goes out and then quickly start the transfer of the file. It sounds like you know about that, but just in case :).
Re: NSA 325 V2 Debian Is Possible!
January 06, 2015 01:00PM
Yeah I've been trying that and just hasn't worked its possible I have a dodgy connection on the serial. I might just flash anyway since a few people have it working. Might try that uboot you linked first though Eddie87.
Re: NSA 325 V2 Debian Is Possible!
January 06, 2015 09:54PM
Re: NSA 325 V2 Debian Is Possible!
January 07, 2015 09:39PM
@Buttzy & Eddie,

davidedg has confirmed: with the new kernel 3.17 and new u-boot, both HDDs work. So the DTS is good.

Make sure you see this in dmesg:
[    1.327311] USB Power: 5000 mV
[    1.330613] SATA1 Power: 5000 mV

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner



Edited 1 time(s). Last edit at 01/07/2015 09:42PM by bodhi.
Re: NSA 325 V2 Debian Is Possible!
January 08, 2015 03:59AM
bodhi,

Took the plunge and flashed the new uboot and the second sata seems to be working now.

Im using the uboot you pointed to 2013.10 version and kernel 3.18.1.
Re: NSA 325 V2 Debian Is Possible!
January 08, 2015 04:16AM
Buttzy10169 Wrote:
-------------------------------------------------------
> bodhi,
>
> Took the plunge and flashed the new uboot and the
> second sata seems to be working now.
>
> Im using the uboot you pointed to 2013.10 version
> and kernel 3.18.1.

Awesome! Thanks for confirming.

Regarding UART, you could try to switch the usb serial module to another Linux plug if you have one. I would get a Pogo Mobile cheap if it's available in your locale and use it for testing purpose.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: NSA 325 V2 Debian Is Possible!
January 08, 2015 05:36AM
bodhi,

I have a second serial gadget somewhere in my little server room just gotta find it an see if its still working. I think the problem might be with the cable or the cable connections I use to connect the serial adapter to the 3.5mm jack.
Eddie87
Re: NSA 325 V2 Debian Is Possible!
January 08, 2015 02:04PM
Well I think it has to be a hardware issue as I see USB Power: 5000 mV and SATA1 Power: 5000 mV in the log but fdisk doesn't recognise the same drive that it recognises in SATA port 1 when placed in SATA port 2. When I run ide reset in uboot I get "Bus 0: OK Bus 1: not available".

I tried again with http://forum.doozan.com/read.php?3,12381,17420#msg-17420 which this time I got to boot. However, it's exactly the same thing when it comes to the second hard drive. I see USB Power: 5000 mV and SATA1 Power: 5000 mV but no second drive is listed under fdisk -l

On a more positive note this whole experience has taught be how to use UART which I've successfully used to recover by old DNS320 which I thought I had bricked. I think I'll just go back to using that with a custom linux booting from USB as I'd like to have two drives really :).

Thanks for all your help with this. If you have any other ideas I could try then I'm all ears :).

Cheers,

Ed
Re: NSA 325 V2 Debian Is Possible!
January 08, 2015 09:39PM
Re: NSA 325 V2 Debian Is Possible!
January 09, 2015 02:25AM
In case you haven't tried Eddie completely power off the box then turn on and check the box I had to do that after updating the uboot on my nsa325v2 before both drives were recognised.
marght
Re: NSA 325 V2 Debian Is Possible!
January 18, 2015 04:21PM
Hi all.

Great work, but solution from 1st post didn't work for me. I had to do extra two things:
1. copy all files from /boot directory on 2nd partition to root directory on first partition
2. change a variable in file usb_key_func.sh.2 file:

from

root=LABEL=rootfs

to

root=UUID=UID_OF_2ND_PARTION (in my case: root=UUID=4fafb3e7-0b05-40c8-98ff-4237739107d0)

Tx.
Re: NSA 325 V2 Debian Is Possible!
January 18, 2015 04:43PM
bodhi & warheadsSE
I notice that "the end might be in sight" ;-)
Is there any thought on when a release of u-boot for the NSA325 and NSA320 would be available?

herb
Re: NSA 325 V2 Debian Is Possible!
January 19, 2015 07:10AM
@ WaheadsSE,

I could merge what I have on NSA320/325 into the u-boot-kirkwood (2014.07 branch). And then you can modify it as you see appropriate for mainline, and then PR?

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: NSA 325 V2 Debian Is Possible!
January 25, 2015 11:38AM
Hi, I recently got an nsa-325 so I thought I share my experience running debian on it.
After reading and looking at all the excellent work from bodhi, buttzy and others I decided I go ahead
without a serial cable, so I hope its useful:

Procedure to run debian on nsa-325, no need for serial cable, no need to open the box,
no need to interact with u-boot.

# prepare usb stick to boot debian
Prepare a USB Stick with rootfs / bootfs as from bodhi's thread
I used a SanDisk Cruzer Fit 8GB USB stick which seems to be proven to work.
- Create 2 partitions on the usb stick:
one small (e.g. 100MB) ext2 filesystem named boot
one ext4 filesystem named rootfs
- expand the rootfs tar file from bodhi into rootfs, I used linux-3.16.0-kirkwood-tld-2-bodhi.tar.bz2,
which I understood is the latest that works with stock u-boot, so no flash of u-boot needed.
- copy files from rootfs /boot to boot filesystem
- edit etc/fstab in rootfs and adapt filesystem type (ext4)
# usb stick ready to boot debian

# change u-boot env.vars so that debian will be booted from usb
# we can do this from the userspace on nsa-325 without relying on usb_key_func stuff

telnet to nsa-325 box (I had stock firmware 4.71 on it), user admin default password 1234
su root (password 1234)
execute following commands (put into a script and execute):
(commands taken from usb-debian-uboot.tar.gz)

#
fw_setenv arcNumber 4495
fw_setenv mainlineLinux yes
fw_setenv 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'
fw_setenv 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'
fw_setenv 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'
fw_setenv bootcmd_stock 'setenv bootargs $(bootargs_stock); nand read.e $(loadaddr) $(kernel_addr) 0xA00000; bootm $(loadadr)'
fw_setenv to_stock "setenv mainlineLinux no; setenv bootcmd \'run bootcmd_stock\'; saveenv; reset"
fw_setenv to_linux "setenv mainlineLinux yes; setenv bootcmd \'run bootcmd_linux\'; saveenv; reset"
fw_setenv bootcmd 'run to_linux'
#

# boot env vars now correctly setup in uboot-env flash block
now (just to be on safe side), execute fw_printenv and doublecheck vars

now plug the usb stick into nsa-325 (rear usb-1 connector)
reboot

# nsa-325 should now boot into debian, using dhcp

locate IP address on router, ssh to nsa-325 box with root and password root
success :-)

Of course for eventual troubleshooting the serial cable will be needed, but
it looks like if sticking to instructions closely this is not mandatory for initial setup.

hans
Re: NSA 325 V2 Debian Is Possible!
January 25, 2015 12:39PM
@hans,

Good work! It will be a good reference for people who want to install with new Debian rootfs only.

Suggestion: put these commands (and other commands in your post) in a code tag so it is easier to read (so lines don't wrap):
fw_setenv arcNumber 4495 
fw_setenv mainlineLinux yes 
fw_setenv 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' 
fw_setenv 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' 
fw_setenv 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' 
fw_setenv bootcmd_stock 'setenv bootargs $(bootargs_stock); nand read.e $(loadaddr) $(kernel_addr) 0xA00000; bootm $(loadadr)' 
fw_setenv to_stock "setenv mainlineLinux no; setenv bootcmd \'run bootcmd_stock\'; saveenv; reset" 
fw_setenv to_linux "setenv mainlineLinux yes; setenv bootcmd \'run bootcmd_linux\'; saveenv; reset" 
fw_setenv bootcmd 'run to_linux'

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: NSA 325 V2 Debian Is Possible!
January 30, 2015 01:15PM
I don't understand the initial instructions in the first post.
I am irritated as hell right now. Can someone clarify please ?!

Quote
prepare a usb or hdd with 2 partitions the first ext2

If I want my Debian to end up on a HDD, then I need a HDD here or it doesn't matter if is a HDD or USB ?
"2 partitions the first ext2" seems incorrect grammatically too, very confusing.

Quote
download the sata-debian-uboot.tar.gz from this post
extract it to a fat 32 formated usb


This is a second USB drive? I need two USB drives ? One Ext2 and one Fat32 ?
Re: NSA 325 V2 Debian Is Possible!
January 30, 2015 01:20PM
Try reading all the instructions. The fat32 step is for a script that changes the uboot variables on the stock uboot. And these instructions were written a while ago so I dont know if they still work with Bodhi's latest roots.
Re: NSA 325 V2 Debian Is Possible!
January 30, 2015 10:25PM
@adrianTNT,

If running stock u-boot, use kernel 3.16.0-kirkwood-tld-2 from:
http://forum.doozan.com/read.php?2,12096

To run kernel 3.17, you need new u-boot. First, see if you can boot with UART if you have serial console, then update u-boot:
http://forum.doozan.com/read.php?3,12381,17420#msg-17420

Unfortunately, atm there is no combined installation instruction for the NSA325.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: NSA 325 V2 Debian Is Possible!
February 17, 2015 02:45PM
Hello Bodhi,

i'm sorry to disturb you.
My system worked as a charm until one hour ago. I tried to update to kernel 3.18 but i failed.

The system isn't booting anymore. Do you have any idea how can i fix it?

System-messages
U-Boot 2013.10-tld-1 (Aug 29 2014 - 22:07:26)
ZyXEL NSA325 2-Bay Power Media Server

SoC:   Kirkwood 88F6282_??
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0 [PRIME]
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot:  0
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **

Reset IDE: Bus 0: OK Bus 1: not available
  Device 0: Model: INTEL SSDSA2BW160G3L Firm: 4PC1LE04 Ser#: CVPR137009LE160DGN
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 152627.8 MB = 149.0 GB (312581808 x 512)
2879926 bytes read in 464 ms (5.9 MiB/s)
6441334 bytes read in 974 ms (6.3 MiB/s)
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   Linux-3.18.5-kirkwood-tld-1
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2879862 Bytes = 2.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.18.5-kirkwood-tld-1
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6441270 Bytes = 6.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... 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.18.5-kirkwood-tld-1 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 PREEMPT Thu Feb 5 17:58:07 PST 2015
[    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 NSA325
[    0.000000] Memory policy: Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
[    0.000000] Kernel command line: console=ttyS0,115200 rootfstype=ext4 root=LABEL=hdd-root rootdelay=25 :::orion:eth0:none
[    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: 504856K/524288K available (5640K kernel code, 365K rwdata, 1920K rodata, 268K init, 305K bss, 19432K 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 - 0xc076a240   (7561 kB)
[    0.000000]       .init : 0xc076b000 - 0xc07ae000   ( 268 kB)
[    0.000000]       .data : 0xc07ae000 - 0xc08096fc   ( 366 kB)
[    0.000000]        .bss : 0xc08096fc - 0xc0855d84   ( 306 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000013] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474836475ns
[    0.000347] Console: colour dummy device 80x30
[    0.000371] Calibrating delay loop... 1594.16 BogoMIPS (lpj=7970816)
[    0.090083] pid_max: default: 32768 minimum: 301
[    0.090198] Security Framework initialized
[    0.090286] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090303] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090904] Initializing cgroup subsys devices
[    0.090931] Initializing cgroup subsys freezer
[    0.090960] Initializing cgroup subsys net_cls
[    0.090979] Initializing cgroup subsys blkio
[    0.091065] CPU: Testing write buffer coherency: ok
[    0.091442] Setting up static identity map for 0x557418 - 0x557470
[    0.091708] mvebu-soc-id: MVEBU SoC ID=0x6282, Rev=0x1
[    0.093757] devtmpfs: initialized
[    0.095938] prandom: seed boundary self test passed
[    0.098939] prandom: 100 self tests passed
[    0.098955] pinctrl core: initialized pinctrl subsystem
[    0.099360] regulator-dummy: no parameters
[    0.103906] NET: Registered protocol family 16
[    0.104247] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.130098] cpuidle: using governor ladder
[    0.160098] cpuidle: using governor menu
[    0.160450] Feroceon L2: Enabling L2
[    0.160487] Feroceon L2: Cache support initialised.
[    0.160811] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[    0.164629] No ATAGs?
[    0.191441] vgaarb: loaded
[    0.191740] usbcore: registered new interface driver usbfs
[    0.191806] usbcore: registered new interface driver hub
[    0.191857] usbcore: registered new device driver usb
[    0.192713] Switched to clocksource orion_clocksource
[    0.222828] NET: Registered protocol family 2
[    0.223439] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.223494] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    0.223546] TCP: Hash tables configured (established 4096 bind 4096)
[    0.223600] TCP: reno registered
[    0.223611] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.223630] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.223795] NET: Registered protocol family 1
[    0.224095] RPC: Registered named UNIX socket transport module.
[    0.224105] RPC: Registered udp transport module.
[    0.224110] RPC: Registered tcp transport module.
[    0.224116] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.224341] Unpacking initramfs...
[    0.631001] Freeing initrd memory: 6292K (c1100000 - c1725000)
[    0.631114] NetWinder Floating Point Emulator V0.97 (double precision)
[    0.632224] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.632254] Initialise system trusted keyring
[    0.632335] audit: initializing netlink subsys (disabled)
[    0.632383] audit: type=2000 audit(0.620:1): initialized
[    0.633114] zpool: loaded
[    0.633128] zbud: loaded
[    0.633377] VFS: Disk quotas dquot_6.5.2
[    0.633428] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.633910] NFS: Registering the id_resolver key type
[    0.633950] Key type id_resolver registered
[    0.633958] Key type id_legacy registered
[    0.633980] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.633991] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    0.634166] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    0.634422] msgmni has been set to 998
[    0.634549] Key type big_key registered
[    0.636780] alg: No test for stdrng (krng)
[    0.636814] Key type asymmetric registered
[    0.636828] Asymmetric key parser 'x509' registered
[    0.636900] bounce: pool size: 64 pages
[    0.636980] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    0.636998] io scheduler noop registered
[    0.637010] io scheduler deadline registered
[    0.637054] io scheduler cfq registered (default)
[    0.638114] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[    0.638640] irq: Cannot allocate irq_descs @ IRQ33, assuming pre-allocated
[    0.638958] irq: Cannot allocate irq_descs @ IRQ65, assuming pre-allocated
[    0.639611] mvebu-pcie mbus:pcie-controller: PCI host bridge to bus 0000:00
[    0.639626] pci_bus 0000:00: root bus resource [io  0x1000-0xfffff]
[    0.639637] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[    0.639648] pci_bus 0000:00: root bus resource [bus 00-ff]
[    0.639898] PCI: bus0: Fast back to back transfers disabled
[    0.639911] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    0.640439] PCI: bus1: Fast back to back transfers disabled
[    0.640524] pci 0000:00:01.0: BAR 14: assigned [mem 0xe0000000-0xe00fffff]
[    0.640541] pci 0000:01:00.0: BAR 0: assigned [mem 0xe0000000-0xe0001fff 64bit]
[    0.640565] pci 0000:00:01.0: PCI bridge to [bus 01]
[    0.640578] pci 0000:00:01.0:   bridge window [mem 0xe0000000-0xe00fffff]
[    0.640654] pci 0000:00:01.0: enabling device (0140 -> 0142)
[    0.640674] pci 0000:01:00.0: enabling device (0140 -> 0142)
[    0.640897] mv_xor f1060800.xor: Marvell shared XOR driver
[    0.672784] mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
[    0.712766] mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
[    0.712912] mv_xor f1060900.xor: Marvell shared XOR driver
[    0.752764] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[    0.792762] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[    0.793101] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    0.794149] console [ttyS0] disabled
[    0.794201] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 27, base_baud = 12500000) is a 16550A
[    1.474286] console [ttyS0] enabled
[    1.478927] nand: device found, Manufacturer ID: 0x92, Chip ID: 0xf1
[    1.485334] nand: Eon NAND 128MiB 3,3V 8-bit
[    1.489622] nand: 128MiB, SLC, page size: 2048, OOB size: 64
[    1.495320] Scanning device for bad blocks
[    1.554171] libphy: Fixed MDIO Bus: probed
[    1.558558] libphy: orion_mdio_bus: probed
[    1.567112] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    1.574986] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 10:7b:ef:88:11:1e
[    1.583957] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.590516] ehci-pci: EHCI PCI platform driver
[    1.595106] ehci-orion: EHCI orion driver
[    1.599265] orion-ehci f1050000.ehci: EHCI Host Controller
[    1.604841] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    1.612649] orion-ehci f1050000.ehci: irq 30, io mem 0xf1050000
[    1.632734] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[    1.638917] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    1.645757] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.653024] usb usb1: Product: EHCI Host Controller
[    1.657920] usb usb1: Manufacturer: Linux 3.18.5-kirkwood-tld-1 ehci_hcd
[    1.664665] usb usb1: SerialNumber: f1050000.ehci
[    1.669975] hub 1-0:1.0: USB hub found
[    1.673816] hub 1-0:1.0: 1 port detected
[    1.678453] mousedev: PS/2 mouse device common for all mice
[    1.684366] i2c /dev entries driver
[    1.692448] rtc-pcf8563 0-0051: chip found, driver version 0.4.3
[    1.702228] rtc (null): invalid alarm value: 1970-1-1 40:54:0
[    1.708246] rtc-pcf8563 0-0051: rtc core: registered rtc-pcf8563 as rtc0
[    1.716931] hidraw: raw HID events driver (C) Jiri Kosina
[    1.722646] drop_monitor: Initializing network drop monitor service
[    1.729181] TCP: cubic registered
[    1.732515] NET: Registered protocol family 17
[    1.737118] Key type dns_resolver registered
[    1.742023] Loading compiled-in X.509 certificates
[    1.746901] registered taskstats version 1
[    1.753069] rtc-pcf8563 0-0051: setting system clock to 1970-01-01 01:17:42 UTC (4662)
[    1.762985] Freeing unused kernel memory: 268K (c076b000 - c07ae000)
Loading, please wait...
[    1.833561] udevd[62]: starting version 175
[    1.992896] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    2.154546] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[    2.161300] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    2.180921] usb 1-1: Product: USB2.0 Hub
[    2.190370] hub 1-1:1.0: USB hub found
[    2.198050] hub 1-1:1.0: 4 ports detected
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 ... done.
Gave up waiting for root device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/disk/by-label/hdd-root does not exist.  Dropping to a shell!
modprobe: chdir(3.18.5-kirkwood-tld-1): No such file or directory
modprobe: chdir(3.18.5-kirkwood-tld-1): No such file or directory
modprobe: chdir(3.18.5-kirkwood-tld-1): No such file or directory
modprobe: chdir(3.18.5-kirkwood-tld-1): No such file or directory
modprobe: chdir(3.18.5-kirkwood-tld-1): No such file or directory
modprobe: chdir(3.18.5-kirkwood-tld-1): No such file or directory


BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs)


This was how i tried to update. It fine with 3.16 / 3.17.
dpkg -i linux-image-3.18.5-kirkwood-tld-1_1_armel.deb

cp -a zImage-3.18.5-kirkwood-tld-1  zImage.fdt
cat dts/kirkwood-nsa325.dtb  >> zImage.fdt
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.18.5-kirkwood-tld-1 -d zImage.fdt /boot/uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.18.5-kirkwood-tld-1 -d /boot/initrd.img-3.18.5-kirkwood-tld-1 /boot/uInitrd
->
sync 
shutdown -r now
.
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: