Possible to install Debian on Seagate Business Storage 2?

Hm, not really.

If you have extracted your modules.tar.gz in root, the needed modules should be under /lib/modules/2.6blah.blah.blah/

You wanted to try to compile a newer kernel. Did you tried it directly on the NAS?
Yeah, I know, will take ages, but easier than making a toolchain.
I am currently compiling 3.19 with, hopfully, the network and USB drivers for Cavium inbuilt.

Did you manage to boot automatically to debian instead stock OS?



Edited 1 time(s). Last edit at 03/17/2015 02:45PM by Yama.

The modules are in the right path and are (maybe?) loaded, but no device is found.


The newer Kernel will not work because there are many sata patches. I havent tried to compile it on the device. I have a working toolchain, so there is no reason to do this.

I am not able to boot automatically to debian. The uboot env variable is not written to flash/eeprom/whatever.

Here are some logs:

[....] Starting the hotplug events dispatcher: udevd[   25.730000] <30>udevd[579]: starting version 175
. ok 
[....] Synthesizing the initial hotplug events...[   26.140000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   26.150000] 
[   26.150000]  drivers/usb/host/ehci-cns3xxx.c cns3xxx_ehci_probe 
[   26.160000] cns3xxx-ehci cns3xxx-ehci.0: CNS3XXX EHCI Host Controller
[   26.170000] cns3xxx-ehci cns3xxx-ehci.0: new USB bus registered, assigned bus number 1
[   26.180000] 
[   26.180000]  drivers/usb/host/ehci-cns3xxx.c cns3xxx_ehci_init 
[   26.190000] cns3xxx_ehci_init,***Threshold OUT=0x60,IN=0x60 ***
[   26.440000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[   26.750000] cns3xxx-ehci cns3xxx-ehci.0: irq 64, io mem 0x82000000
[   26.850000] cns3xxx-ehci cns3xxx-ehci.0: USB 0.0 started, EHCI 1.00
[   26.860000] hub 1-0:1.0: USB hub found
[   26.880000] hub 1-0:1.0: 1 port detected
[   26.890000] cns3xxx-ohci cns3xxx-ohci.0: CNS3XXX OHCI Host controller
[   26.900000] cns3xxx-ohci cns3xxx-ohci.0: new USB bus registered, assigned bus number 2
[   26.910000] cns3xxx-ohci cns3xxx-ohci.0: irq 91, io mem 0x88000000
[   26.980000] hub 2-0:1.0: USB hub found
[   26.990000] hub 2-0:1.0: 1 port detected
done.
[....] Waiting for /dev to be fully populated...[   27.260000] Unable to handle kernel paging request at virtual address 00080800
[   27.270000] pgd = bf40c000
[   27.280000] [00080800] *pgd=3f3d9031, *pte=00000000, *ppte=00000000
[   27.300000] Internal error: Oops: 17 [#1]
[   27.300000] last sysfs file: /sys/bus/platform/drivers/cns3xxx-ehci/uevent
[   27.300000] Modules linked in: ohci_hcd ehci_hcd
[   27.300000] CPU: 0    Tainted: G        W    (2.6.35.13-cavm1.whitney-econa #28)
[   27.300000] PC is at sys_recvfile+0x30/0x23c
[   27.300000] LR is at ret_fast_syscall+0x0/0x30
[   27.300000] pc : [<a00cc818>]    lr : [<a002aea0>]    psr: 80000013
[   27.300000] sp : bf419f48  ip : bf419fa8  fp : bf419fa4
[   27.300000] r10: a0671774  r9 : 00000003  r8 : 00000000
[   27.300000] r7 : 00000000  r6 : 00080800  r5 : 00000003  r4 : 00000000
[   27.300000] r3 : 00000000  r2 : 00000000  r1 : 00000000  r0 : 00000003
[   27.300000] Flags: Nzcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
[   27.300000] Control: 00c5787d  Table: 3f40c00a  DAC: 00000015
[   27.300000] Process udevd (pid: 579, stack limit = 0xbf418268)
[   27.300000] Stack: (0xbf419f48 to 0xbf41a000)
[   27.300000] 9f40:                   00000000 bf419f58 bf419f74 bf419f60 a005f12c a005f0f4
[   27.300000] 9f60: bf20e1e0 bf418000 bf419fac bf419f78 a0472f8c a003ee1c 58d29700 00000000
[   27.300000] 9f80: 00000003 00000000 0000016e a002b044 bf418000 00000000 00000000 bf419fa8
[   27.300000] 9fa0: a002aea0 a00cc7f4 00000000 00000003 00000003 00000000 00000000 00080800
[   27.300000] 9fc0: 00000000 00000003 00000000 0000016e 00080800 00000022 00000000 00032008
[   27.300000] 9fe0: 3571c000 9ede4dd8 000175f0 356b819c 60000010 00000003 00000000 00000000
[   27.300000] [<a00cc818>] (sys_recvfile+0x30/0x23c) from [<a002aea0>] (ret_fast_syscall+0x0/0x30)
[   27.300000] Code: e1a08001 e3530009 e1a07002 ca000009 (e1c640d0) 
[   27.310000] ---[ end trace 1b75b31a2719ed1e ]---
done.
[....] Setting parameters of disc:
/dev/sda:
 setting standby to 241 (30 minutes)
[ ok v/sda.
[ ok e).
[....] Checking root file system...fsck from util-linux 2.20.1
ROOTFS: clean, 28388/671744 files, 1389151/2686208 blocks
done.
[   31.450000] EXT3-fs (sda1): using internal journal
[ ok ] Cleaning up temporary files... /tmp /lib/init/rw.
.info] Loading kernel module cns3xxx
 not found.le cns3xxx
.info] Loading kernel module cns3xxx_pse_init
 not found.le cns3xxx_pse_init
.info] Loading kernel module ehci-hcd
 not found.le ehci-hcd
.info] Loading kernel module ohci-hcd
 not found.le ohci-hcd
[info] Loading kernel module xhci-hcd.
FATAL: Module xhci-hcd not found.
.info] Loading kernel module usblp
 not found.le usblp

FATAL: Module xhci-hcd not found.

Seems, that it can't find your module.
I would check again, if everything is in /lib/modules/
I only did:

cd / 
tar xf ~/modules.tar.gz

Since the tar has the whole tree, everything extracted perfectly in place.

What does lsmod show?
Mine (I don't have any USB devices attached currently):

lsmod
Module                  Size  Used by
xhci_hcd               51895  0
usblp                  10230  0
cns3xxx                63894  0
cns3xxx_pse_init       18909  1 cns3xxx

I hope you will be able to compile the kernel with the network and USB drivers and share it with me :D
So we can use a USB dongle as root, instead ugly and energy consuming 2.5" HDD in the front XD
(I don't want an OS on my data Harddisks and they should also idle^^)



Edited 1 time(s). Last edit at 03/17/2015 03:16PM by Yama.

The xhci_hcd was not found, because I disabled it for testing purposes, but it is in the /etc/modules file. The ehci and ohci modul has been loaded and are shown after lsmod.

Any other idea?

I like the 2.5" hdd in front, in needs less power than an usb dongle. I assume abount 0.5W. And it is nearly without any noise.

edit: yama, you got my pm?



Edited 1 time(s). Last edit at 03/17/2015 03:37PM by blackdevil.

Don't know why the module shouldn't work for you :/

OK, so we are stuck at kernel 2.6 and we must be afraid on every update I guess, that someday debian isn't support it.
We would need to compile the USB drivers to the kernel in order to be able to use USB dongle as rootfs.
And, the worst, we need to set the uboot variable on every damn boot....

You said earlier, that dhcp isn't always working. You fixed it?

Yama, i think you are right.

And i didnt get the ethernet bugs fixed. I think it is not a dhcp bug, because the network device didnt get up successfully and than the dhcp fails.

Finally, I compiled a kernel and made a initramfs for it.
Now the "root"-parameter is being replaced in the init-script in the initramfs.

So I am now able to boot directly to the partition I want to, instead of stock OS without interrupting uboot.

This creates a initramfs on the NAS, which can be used for a kernel, either as parameter or inbuilt.
Since we can't give parameters for autoboot, we will compile it in the kernel.

sudo mkinitramfs -o myownramfs.gz

Move "myownramfs.gz" to the machine you compile your kernels for the NAS.
Now we extract it.

mkdir ramfs
cd ramfs
gzip -dc /home/you/myownramfs.gz | cpio -ivd

Now we need to edit the file "init".
An if start with a comment on line 74, the command is "# Parse command line options".
On line 182 the if ends. Now do a new line (line 183) and type this in (of course, put your device and partition in it):

ROOT=/dev/sda2

Since our initramfs has the required modules from our working root, even USB should be bootable now, but I didn't test yet.

Only this modification is required, now we make a cpio archive of the files.

find . | cpio -H newc -o > ../initramfs.cpio

Now we have a file called initramfs.cpio on the above folder.
You can now copy this file to the root of the kernel-directory and run:

make ARCH=arm menuconfig

It should have load your existing configuration, else just navigate to load and load your .config.
Now go to "General Setup" (First entry) and navigate to "Initial RAM filesystem and RAM disk (initramfs/initrd) support".
Activate it with "y", move one down and press enter.
Enter the filename of your cpio archive. We named it "initramfs.cpio".
Press enter, go back and navigate to "Save an Alternate Configuration File" and just press enter, since the standard is ".config".

Now compile your kernel.

You should now have a new uImage. Move it to your NAS.
Mount the flash drive-partitions with the original uImage.

mkdir boot1
mkdir boot2
sudo mount /dev/mmcblk0p1 boot1
sudo mount /dev/mmcblk0p2 boot2

Backup the original, incase it is necessary.

mkdir stockuImage
sudo mv boot1/uImage stockuImage/uImage.p1
sudo mv boot2/uImage stockuImage/uImage.p2

Place your own kernel in the partitions.

sudo cp uImage boot1
sudo cp uImage boot2

Now you are done. Next time you dont need to interrupt uboot and pass new parameters and variables.
Uboot boots our kernel and our kernel doesn't uses the given "root"-parameter. Only the root-partition in the init-script is used.
Thats, btw, the reason why I currently don't provide prebuilt uImages, since the device and partition depends on your config and on the devices you have attached.

If you have only one HDD, it's of course sda. If you have all three sATA-ports full and your system is on the above 2.5" slot, it will be sdc.

First of all, congrats to the posters in this thread for their findings on how to get Debian on the Seagate NAS! I have a proposal for you, guys - could anyone of you prepare and post a step-by-step guide on the firmware change? I am pretty sure there are many others users, including myself, who would like to do it However, after studying the thread and links, although I think I could manage to change the firmware, I am still concerned I could screw something up. With a step-by-step solution it would definitely be a lot easier...

I don't know what you mean with "changing" the firmware.
You know which parameters to use on uboot to boot a kernel which is located on a harddrive and you have a step-by-step HowTo replace the original kernel in my last post.



Well, other things: People seem to be able to boot a kernel with the version 3.x on CNS boards, without network support and only in singlecore mode. But still I am not aware how to and I don't want to use it on singlecore mode...

And as I mentioned earlier, the current, shared kernel on this forum runs only on one core, too.
I also noticed, that the sources of Seagate Central were being used to compile it, not the original of our device.
I tried to compile it, but had some difficulties.

I am still on it to get something good to run on the NAS.



Edited 1 time(s). Last edit at 04/24/2015 04:44AM by Yama.

"Replace the firmware" - I mean to get rid of the current proprietary version of linux, install Debian instead and do the necessary changes to get the NAS to boot into it (automatically)

Suppose I start with a clean hdd and the NAS with stock firmware. Could you please enumerate and very briefly describe the steps to finish with the Debian box automatically booting into it?

How could you oversaw this post: http://forum.doozan.com/read.php?2,17868,20589#msg-20589
There is a step-by-step HowTo how you can modify the init-script of the initramfs to make it boot to your own Debian system located on a harddrive (what I have already described in my last post to you).
Then you can let it automatically boot to your Debian root on the harddrive.



Edited 1 time(s). Last edit at 04/24/2015 04:46AM by Yama.

I managed to boot into debian, however I still need to alter the uboot parameters at boot time. Network is working fine, I did not tested usb yet. Now is time for the final step - create initramfs and boot automatically.

So far I put my root system on 2.5 inch drive in the upper sata slot. Now it is the only disk and the system is on the first partition, so my root is /dev/sda1. But later I would like to have the possibility to use, add or remove 3.5 inch disks as I need, and the problem is if I add either one or two of them, the root device will become /dev/sdb1 or /dev/sdc1 respectively. So I am wondering if it is possible to specify disks in the init file in initramfs by its UUID. What do you think? The line "ROOT=UUID=XXX-XXX-XXX-XXX" instead "ROOT=/dev/sda1" would be ok?

The answer for my last question is yes, the UUID can be used to identify partition with root system in the way that I wrote.


However I am having issues with kernel compilation. All the kernels I got so far (with and without initramfs), compiled with different settings (based on config from this thread or config from /proc/config.gz on stock software) and different compiler flags, throw errors (eg. "Unable to handle kernel paging request at virtual address XXXXX") and most of the time the boot up process hangs. I can boot from the kernel provided by Yama, but it is also not perfect - the system seems to be usable, but it throws a few errors during boot-up. And the most important, I can't use the Yama's kernel for the uImage with initramfs, cause such a kernel I need to compile myself.

I used the sources for stock kernel, which have been posted in this thread (and also can be downloaded directly from Seagate website). I used the cross-compiler on PC in the up-to-date Debian Jessie. Most promising was using the flag -mno-unaligned-access for the compiler. Then there were no errors until the boot reached the init phase (INIT: version 2.88 booting), but hanged soon after (after "Activating swap" message). It sound for me like the executables from the arm-Debian root system were not compatible with such kernel and therefore I started wondering if I should build a self compiled distro from scratch with the same compiler settings. But it would be a really tedious job....

I really do not know where I make the mistakes, but I want to reach my goal. Could Yama or anyone else tell what toolchain/compiler version he is using and possibly share his config? Maybe this could help me to progress.

I also was only able to compile the source which is shared in this thread.
But this kernel works only on one CPU core. Thats why i tried to compile the right source for our device (the not-Central source) but the compiling fails. I will try again someday.

For cross-compiling you need the packages for cross-compiling.
Install gcc-arm-linux-gnueabi and always put ARCH=arm to your compiling commands like make and menuconfig.
You also should put -arm-linux-gnueabi as a prefix in the menuconfig.
The only config-file I used was the one from Blackdevil.

To clarify:

I used source code from here:

https://kimowe.de/owncloud/index.php/s/4LKjmPrbFSw9xEJ

and later directly from Seagate which with all their patches applied in the result seem to be exatcly the same sources as the first one.

Of course I installed the cross-compiler packages, so the arm-linux-gnueabi- stuff was used.

And did all the standard steps - make menuconfig, make uImage etc. using ARCH=arm (also -j3 for speed and V=1 for verbosity but this is irrelevant). The kernel made this way worked but the system was buggy.

I saw many errors during boot-up were related to aligning memory so I read somewhere that using the flag "-mno-unaligned-access" can be a remedy. In fact is was - but only for the first part of boot-up until it reached some init scripts from the /etc/rcS.d folder.

BTW, Yama, which version of arm-debian rootfs do you use? Is the Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (24 Feb 2015) from this thread http://forum.doozan.com/read.php?2,12096?

Yes, I am using the first Jessie rootfs "This rootfs is the first Debian jessie rootfs..."

Well, I'm not sure if there are errors, but my goal is to get a kernel on version 3 working, so Arch Linux boots on it.
The arm-code maintainer wrote me, that he is able to boot vanilla kernels on a CNS3XXX hardware, on only one core and without network support.
Well, the "one core" part is the case for us on the currently working kernel, too.
Really makes it unusable.

Currently I have no alternatives, but I am slowly working on it to get something good, either kernel 2 with SMP or 3 with SMP.

Hello everyone,

I read the topic without understanding all of what it contains, but I also have this NAS.

Can we make a small summary of what you can do with it? And I know how to compile a kernel in cross-compil ^^.

Cordially.

A forum member has suggested that I look into building a new u-boot for this box. It seems doable with available info out there.

To save me sometime, here are the questions:

- Has anyone attempted UART booting with any version of u-boot for this box?

- I got the bootlog from iamnewbie here:
http://forum.doozan.com/read.php?2,17868,17868#msg-17868

Does your box look like this or any differences? (I'm making sure there is only one version).

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

I can try today, i share result after.

Uh, this member just read randomly here and gave you ideas? :D

I did not tried UART booting.
My device has the exact same output like iamnewbie's device.

I am looking forward for your results, bodhi :D

The kernel source provided here works, but only on one CPU core.
And if I'm right, the kernel is from the Central source. Which isn't our device.

I'm trying to compile the correct sources (from the Seagate NAS, instead Seagate Central) with the same .config but it freezes...

Whitney # setenv stdin serial;setenv stdout serial;setenv stderr serial;setenv verify n;setenv num_boot_tries 3;setenv bootargs_console console=ttyS0,38400 mem=512m
Whitney # setenv bootargs_root root=/dev/sda2 rootwait;setenv bootcmd_scsi 'scsi init;fatload scsi 0 0x800000 /uImage.orig';setenv bootdelay 15;setenv bootcmd 'setenv bootargs $(bootargs_console) $(bootargs_root);run bootcmd_scsi;bootm'
Whitney # run bootcmd
Initialize SCSI                     
AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part 
scanning bus for devices...
Supprt LBA48 addressing.
Device 0: (1:0) Vendor: ATA Prod.: ST9100824AS Rev: 7.24
Type: Hard Disk
Supports 48-bit addressing
Capacity: 95396.2 MB = 93.1 GB (195371568 x 512)
reading /uImage.orig

8685576 bytes read
enter do_eth_down!!!
## Booting kernel from Legacy Image at 00800000 ...
Image Name:   Linux-2.6.35.yama
Created:      2015-05-24  11:40:10 UTC
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    8685512 Bytes =  8.3 MB
Load Address: 02000000
Entry Point:  02000000
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Li done, booting t

Edited 1 time(s). Last edit at 05/24/2015 07:11AM by Yama.

@Yama,

Quote

> Image Name: Linux-2.6.35.yama
> Created: 2015-05-24 11:40:10 UTC

I've assumed erronously that you and others have compiled newer kernel for it! now that I've read the entire thread, I realized that perhaps getting the newer kernel is more important than building newer u-boot.

Quote

> Starting kernel ...
> Uncompressing Li done, booting

If it freezezs like this, it's either the bootargs is wrong or the kernel image is a wrong one. If you have hardcoded the command line in .config then the image was built from the wrong source for this box.

Since this kernel is really old, I think it's better if it can be upgraded to a non-FDT kernel. Then we'll have full control. I'll take a look at the Seagate NAS source to see how hard/easy that will be.

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

I have a question, we are in the presence of an ARMv6 CPU can we use *.deb of Raspbian insted of Debian armel one ?

I think i can try in chroot.

I texted the ARM-Maintainer to get help regarding to make kernel v3 working. This is the answer:

Quote

Have you tried booting a recent kernel, something like 3.17 or later?
There were some issues in older kernels (I have to check if all of them
are resolved). Some stuff (IIRC Ethernet and SMP) is included in
OpenWrt and can quite easily be ported to Linux.

The official Linux may be missing support for your board, but this is
probably also easy to add. Or one could deceive Linux into thinking it's
booting on different board, e.g. the CNS3xxx demo platform (you may have
to alter some config variables, like RAM size, in platform support
code). The state of support of this CPU isn't great for sure, but a mere
booting shouldn't be a problem. What I'm using here is Gateworks Laguna
and I can definitely boot it (in single core mode and without Ethernet -
the official Linux from kernel.org) only changing the ARM platform
number in $LINUX_SRC/arch/arm/tools/mach-types.

I guess he means this patches, I tried a little, but wasn't successful applying them.

The original .config seems to has enabled the CNS3xxx hardware support, too. But these are Seagate's patches, since CNS3xxx support came on a v3 kernel.

Well, I have no idea how to go on and I couldn't answer him either.

@Yama,

We are getting really good info from him.

Quote

Some stuff (IIRC Ethernet and SMP) is included in OpenWrt and can quite easily be ported to Linux.

Quote

Gateworks Laguna and I can definitely boot it (in single core mode and without Ethernet the official Linux from kernel.org) only changing the ARM platform number in $LINUX_SRC/arch/arm/tools/mach-types.

These files from OpenWrt:
https://dev.openwrt.org/browser/trunk/target/linux/cns3xxx/files

How do you download a tarball from there? (I'm not familiar with OpenWrt).

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

Only via svn, which really sucked.

I attached it. I hope I didn't modified anything^^

@Yama,

I've built a test kernel 4.0 for it. I'm going to upload it to Dropbox and you can try.

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



Edited 3 time(s). Last edit at 05/25/2015 12:29AM by bodhi.

Here is the kernel image for testing:

Download at Dropbox
linux-image-4.0.0-cns3xxx-tld-1_0.1_armel.deb
md5
42d2dfa547b9c7621da27a023a572f70

Hopefully, you will be able to boot and get ethernet and SMP.

Patches for the following functionalities were not incorporated:

- Watchdog, CPU Hotplug, and Power Management.
- PCI might not work (look to see in dmesg if PCI is brought tup).

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

Nope...
The uImage is really smal, just 2.1mb.

Commands I used:

wget https://www.dropbox.com/s/9iwa5keqvbutevt/linux-image-4.0.0-cns3xxx-tld-1_0.1_armel.deb?dl=1
ar -x linux-image-4.0.0-cns3xxx-tld-1_0.1_armel.deb?dl=1
mkdir kernel-4.0
cd kernel-4.0
tar xf ../data.tar.xz
mkimage -A arm -O linux -a 0x2000000 -a 0x2000000 -T kernel -C none -d boot/vmlinuz-4.0.0-cns3xxx-tld-1 -n linux uImage

uBoot:

Whitney # setenv stdin serial;setenv stdout serial;setenv stderr serial;setenv verify n;setenv num_boot_tries 3;setenv bootargs_console console=ttyS0,38400
Whitney # setenv bootargs_root root=/dev/sda2 rootwait;setenv bootcmd_scsi 'scsi init;fatload scsi 0 0x800000 /uImage.400';setenv bootdelay 15;setenv bootcmd 'setenv bootargs $(bootargs_console) $(bootargs_root);run bootcmd_scsi;bootm'
Whitney # run bootcmd
Initialize SCSI
AHCI 0001.0100 32 slots 2 ports 3 Gbps 0x3 impl SATA mode
flags: ncq stag pm led clo only pmp pio slum part 
set feature error!
scanning bus for devices...
Supprt LBA48 addressing.
  Device 0: (1:0) Vendor: ATA Prod.: ST9100824AS Rev: 7.24
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 95396.2 MB = 93.1 GB (195371568 x 512)
reading /uImage.400

2164536 bytes read
enter do_eth_down!!!
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   linux
   Created:      2015-05-25  10:26:43 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2164472 Bytes =  2.1 MB
   Load Address: 02000000
   Entry Point:  02000000
   Loading Kernel Image ... OK
OK

Starting kernel ...

Yama,

Can you boot with both uImage and uInitrd? This kernel was built with initrd.

cd /boot
dpkg -i linux-image-4.0.0-cns3xxx-tld-1_0.1_armel.deb

- generate both uImage and uInitrd.
- change bootargs env


PS.

Also make sure your arcNumber is 2776.

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



Edited 1 time(s). Last edit at 05/25/2015 06:34AM by bodhi.

Like this?
Same result :/

> dpkg -i linux-image-4.0.0-cns3xxx-tld-1_0.1_armel.deb
Selecting previously unselected package linux-image-4.0.0-cns3xxx-tld-1.
(Reading database ... 21817 files and directories currently installed.)
Preparing to unpack linux-image-4.0.0-cns3xxx-tld-1_0.1_armel.deb ...
Examining /etc/kernel/preinst.d/
Done.
Unpacking linux-image-4.0.0-cns3xxx-tld-1 (0.1) ...
Setting up linux-image-4.0.0-cns3xxx-tld-1 (0.1) ...

 Hmm. There is a symbolic link /lib/modules/4.0.0-cns3xxx-tld-1/build
 However, I can not read it: No such file or directory
 Therefore, I am deleting /lib/modules/4.0.0-cns3xxx-tld-1/build


 Hmm. The package shipped with a symbolic link /lib/modules/4.0.0-cns3xxx-tld-1/source
 However, I can not read the target: No such file or directory
 Therefore, I am deleting /lib/modules/4.0.0-cns3xxx-tld-1/source

Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.0.0-cns3xxx-tld-1 /boot/vmlinuz-4.0.0-cns3xxx-tld-1
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.0.0-cns3xxx-tld-1 /boot/vmlinuz-4.0.0-cns3xxx-tld-1
update-initramfs: Generating /boot/initrd.img-4.0.0-cns3xxx-tld-1
run-parts: executing /etc/kernel/postinst.d/zz-flash-kernel 4.0.0-cns3xxx-tld-1 /boot/vmlinuz-4.0.0-cns3xxx-tld-1

> mkimage -A arm -O linux -a 0x2000000 -a 0x2000000 -T kernel -C none -d /boot/vmlinuz-4.0.0-cns3xxx-tld-1 -n linux uImage
Image Name:   linux
Created:      Mon May 25 04:57:06 2015
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    2164472 Bytes = 2113.74 kB = 2.06 MB
Load Address: 02000000
Entry Point:  02000000

>mkinitramfs -o /initramfs.gz

Bootargs:

Whitney # setenv stdin serial;setenv stdout serial;setenv stderr serial;setenv verify n;setenv num_boot_tries 3;setenv bootargs_console console=ttyS0,38400
Whitney # setenv bootargs_root root=/dev/sda2 rootwait;setenv bootcmd_scsi 'scsi init;fatload scsi 0 0x800000 /uImage.400';setenv bootdelay 15;setenv bootcmd 'setenv bootargs initrd=initramfs.gz  $(bootargs_console) $(bootargs_root);run bootcmd_scsi;bootm'
Whitney # run bootcmd