Welcome! Log In Create A New Profile

Advanced

Linux Kernel 4.4.79 Oxnas (OX820) Pogo V3 package and Debian rootfs

Posted by bodhi 
Linux Kernel 4.4.79 Oxnas (OX820) Pogo V3 package and Debian rootfs
May 09, 2014 10:08PM
Linux Kernel 4.4.79 Oxnas package and rootfs for Pogoplug Pro V3 (with PCI) and Classic V3 (no PCI). Also the Medion Life P89626, Akitio Mycloud mini, and the possibly other OXNAS boxes such as Silverstone DC01. If you install this kernel on Silverstone DC01 or other OX820 boxes, please post your finding so it can be added to the supported list.

Latest released kernel: linux-4.4.79-oxnas-tld-1.bodhi.tar.bz2 (05 Aug 2017)
Latest released rootfs: Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2 (02 Aug 2017)


These OXNAS boxes uses the ARM11 MPCore, which has some internal CPU bugs, and has proven to be problematic any time there is significant upstream modification in SMP related code. Thus, I've chosen to stay tracked with an LTS kernel to ensure there is enough upstream tests before moving on to the next version. And therefore I will release a minor version in the series 4.4.x whenever there will be kernel security fixes. When an LTS version will have been released, I will build that major upgraded kernel so we can get the latest Linux features.

With this kernel we can run the Pogo V3 boxes with the latest U-Boot (e.g. 2013.10 and later). To run with stock U-Boot, use kernel 3.18.5 or earlier.

Summary decription:

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

The released tarball Debian-x.xx.x-oxnas-tld-xx-rootfs-bodhi.tar.bz2 is a basic armel rootfs (a completed Debian system with kernel already installed) for Oxnas OX820 boxes ready to be used. It is a basic system where you can build upon by installing packages. This rootfs was created by Debian debootstrap and then a few packages were installed for user’s convenience. This rootfs is dedicated for the purpose of upgrading and release distribution.


Historical Background:

These 2 threads are included here for information and credits only, Dropbox download links and installation procedure are after the break below.
  • Booting Debian on Pogoplug Pro. This is the oldest thread, where we started with Arch Linux ARM kernel, and Debian squeeze rootfs. In the first post, you can find links for Varkey's squeeze rootfs, shv's wheezy rootfs, ingmar_k's Emdebian installation, and navym (kref)'s Arch thread about kernel 3.12+ and u-boot.
  • New uboot and kernel for Pogoplug v3/Pro. This thread is more recent, shv started this thread to bring attention about the new 3.12+ kernel activity at Arch site.

==============================================================
Updated 05 Aug 2017:

Kernel linux-4.4.79-oxnas-tld-1 package was uploaded.

Warning: This kernel has grown too big, so it will not work for stock u-boot or its Arch u-boot variant. Stock u-boot has a limitation of 4M uImage, so it will not boot. Please stay with kernel 3.18.5 if you're still booting with stock u-boot. The new u-boot works without limitation.

New/Update features:

- Incorporated kernel 4.4.79 mainline security bugs fixes.

Latest Linux kernel 4.x general release information can be found at:
LinuxChanges log

Download at Dropbox

linux-4.4.79-oxnas-tld-1.bodhi.tar.bz2

md5:
09228f4ba9e64798595dd8744d9d0d3d
sha256:
6d0be800bea66407103f4358a29e7adb482004f34719a897be6bf86b0e356911

And remember to check the hash of what you download, as always.

Installation:

Please use the same installation instruction in linux-4.4.54-oxnas-tld-1 (updated 02 Aug 2017) right below. Simply replace 4.4.54-oxnas-tld-1 with 4.4.79-oxnas-tld-1 in the instruction.


==============================================================
Updated 02 Aug 2017:

Rootfs Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2 was uploaded.

Basic Debian stretch Oxnas rootfs for Popo Pro/Classic V3 plug:

- tarball size: 180M
- install size: 477M
- Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, dialog, bz2, iperf, ethtool, sysvinit-core, sysvinit, sysvinit-utils, mtd-utils.
- see LED controls in /etc/rc.local, and /etc/rc0.d/K08halt
- see some useful aliases in /root/.profile
- root password: root

Download at Dropbox:

Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2

md5sum
48f68566cb9dbb1a95ca5457bee8f13d

sha256sum
00d9cea83acc4696afed1ad267e86d64d99557c26a17770116dd5443e322cf83


And remember to check the hash of what you download, as always.

INSTALLATION:

Installation can be done on any Linux box, with a fresh USB drive (HDD would work fine too). It is assuming the USB drive is mounted at /media/sdb1.

Note: all steps below must be done while logging in as root user (not sudo). If you are not the root user then don't continue, because the rootfs will not work.

1. Format a new USB drive with a single Ext3 partition, and label it rootfs. If you are running the latest released uboot for OXNAS then you can use Ext4.

2. Mount the drive on a Linux box. cd to top level directory and extract it. It is assuming the USB drive is mounted at /media/sdb1
cd /media/sdb1 
tar -xjf Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2

3. Adjust fstab (optional).

Edit /media/sdb1/etc/fstab entry for root device to match the rootfstype of your rootfstype if you use Ext4 or Ext2. However, you can keep it as is without problem in booting since the kernel will figure out which file system the rootfs was formatted.

LABEL=rootfs    /               ext3    noatime,errors=remount-ro 0 1


4. Create uImage with embedded DTB for booting with stock u-boot. Skip this step if you have installed the latest released uboot for OXNAS, or are installing this u-boot at the same time.

- If you have the Pogo V3 Classic (without Wifi), then the DTB name below should be ox820-pogoplug-classic.dtb.

cd /media/sdb1/boot
cp -a zImage-4.4.54-oxnas-tld-1 zImage.fdt
cat dts/ox820-pogoplug-pro.dtb >> zImage.fdt
mkimage  -A arm -O linux -C none -T kernel -a 0x60008000 -e 0x60008000 -n 'Linux-4.4.54-oxnas-tld-1' -d zImage.fdt  uImage
sync

- If your Linux box does not have mkimage, then install it

apt-get install u-boot-tools

5. Done installation. Take this USB rootfs to your plug and cold start.

After booted into Debian, see Note1, 2, and 3 below. It is very important that you do Note1 steps to secure your box.

=====

Note1:

After logging in this rootf the first time, remember to generate new SSH key to make it your own unique rootfs. And also update your rootfs to get the latest Debian package security updates:

rm /etc/ssh/ssh_host*
ssh-keygen -A

apt-get update
apt-get upgrade


Warning: Watch the apt-get upgrade progress. If the apt-get upgrade results in a new initramfs, the log would shows this message:

Quote

update-initramfs: Generating /boot/initrd.img-4.4.54-oxnas-tld-1

Then you need to regenerate the uInitrd boot file:

cd /boot
cp -a uInitrd.bak
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x60000000 -e 0x60000000 -n initramfs-4.4.54-oxnas-tld-1 -d initrd.img-4.4.54-oxnas-tld-1 uInitrd

Note2:

To boot with systemd, add this parameter to your u-boot env bootargs. If you are booting with my latest released uboot for OXNAS then use the uEnv.txt capability to do this. See the instruction about uEnvt.txt in that thread.

init=/bin/systemd

For example, the bootarg for systemd was added to the end of this usb_set_bootargs env to set bootargs (on your box it might be different env):

fw_setenv usb_set_bootargs 'setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts init=/bin/systemd'


If that's still not possible to run systemd, you might want to install it again:
apt-get install systemd


Note3:

For setting up wireless on the Pogo Pro, please see: http://forum.doozan.com/read.php?2,16044,20964#msg-20964

==============================================================
Updated 28 Mar 2017:

Fix to improve Ethernet perfornance

The network performance is degraded on the Pogo V3 OXNAS because the OXNAS ethernet driver turn on flow control by default. We need to turn it off in the driver, and that will be incorprated in the next kernel release. At the moment, the workaround is to do turn it off with ethtool.

Boot into Debian and:
ethtool -A eth0 rx off tx off


==============================================================

Updated 19 Mar 2017:

Kernel linux-4.4.54-oxnas-tld-1 package was uploaded.

Warning: This kernel has grown too big, so it will not work for stock u-boot or its Arch u-boot variant. Stock u-boot has a limitation of 4M uImage, so it will not boot. Please stay with kernel 3.18.5 if you're still booting with stock u-boot. The new u-boot works without limitation.

New/Update features:

- Incorporated kernel 4.4.54 mainline to fix security bugs.
- Added USB printer support (as a module).

Latest Linux kernel 4.x general release information can be found at:
LinuxChanges log

Download at Dropbox

linux-4.4.54-oxnas-tld-1.bodhi.tar.bz2

md5:
2003e95e6149ffc649e5e567375342d7
sha256:
ef6c4df9061aced43a2c75519e69d00cc84c1c8c388799d0af728cf7b8d031eb

INSTALLATION:

Please use the same installation instruction in linux-4.4.48-oxnas-tld-5 (updated 01 Mar 2017) right below. Simply replace 4.4.48-oxnas-tld-5 with 4.4.54-oxnas-tld-1 in the instruction.


==============================================================

Updated 01 Mar 2017:

Kernel linux-4.4.48-oxnas-tld-1 package was uploaded.

Warning: This kernel has grown too big, so it will not work for stock u-boot or its Arch u-boot variant. Stock u-boot has a limitation of 4M uImage, so it will not boot. Please stay with kernel 3.18.5 if you're still booting with stock u-boot. The new u-boot works without limitation.

- [Expiremental] Added USB 3.0 support in the kernel. This is to support potential mPCIe USB 3.0 interface cards.
- All DTS were updated to removed write restriction to ethaddr (MAC address).

Latest Linux kernel 4.x general release information can be found at:
LinuxChanges log

Download at Dropbox

linux-4.4.48-oxnas-tld-1.bodhi.tar.bz2

md5:
eb7ccf5ed563e7fde20dee92e07edc61
sha256:
a6111f0f27ac60a9b270bac3b6d466feb73326eb2f665f0a55d6ab431a6c6478

INSTALLATION:

Please use the same installation instruction in linux-4.4.38-oxnas-tld-5 (updated 12 Dec 2016) right below. Simply replace 4.4.38-oxnas-tld-5 with 4.4.48-oxnas-tld-1 in the instruction.

==============================================================

Updated 12 Dec 2016:

Kernel linux-4.4.38-oxnas-tld-5 package was uploaded.

Warning: This kernel has grown too big, so it will not work for stock u-boot or its Arch u-boot variant. Stock u-boot has a limitation of 4M uImage, so it will not boot. Please stay with kernel 3.18.5 if you're still booting with stock u-boot. The new u-boot works without limitation.

Credits: Thanks Daniel Golle (LEDE) for the updated patches, and Neil Armstrong for upstreaming activities. I've incorporated the code and ideas from both of these sources to build this kernel.

Latest Linux kernel 4.x general release information can be found at:
LinuxChanges log

Download at Dropbox

linux-4.4.38-oxnas-tld-5.bodhi.tar.bz2
md5:
663df6cee6f8124d829051d0e75c5592
sha256:
300810b969a8282c1b6df9e08a3434a8b826c6fa4796bc8917f42f8bfc9fea44


This tarball contains 6 files:

linux-image-4.4.38-oxnas-tld-5_5_armel.deb
linux-headers-4.4.38-oxnas-tld-5_5_armel.deb
config-4.4.38-oxnas-tld-5
zImage-4.4.38-oxnas-tld-5
linux-dtb-4.4.38-oxnas-tld-5.tar
linux-4.4.38-oxnas-tld-5.patch


INSTALLATION:

A. Installation to run with new U-Boot in NAND (see new U-Boot thread here)

1. Backup your current uImage and uInitrd and other kernel files. In the /boot directory, these are files for your current kernel (xx.xx.xx is the version number):

uInitrd
uImage
initrd.img-xx.xx.xx-xxx
System.map-xx.xx.xx-xxx
vmlinuz-xx.xx.xx-xxx
config-xx.xx.xx-xxx

2. Extract the kernel in the archive:
cd /boot
tar -xjf linux-4.4.38-oxnas-tld-5.bodhi.tar.bz2

3. Extract the dts tarball for the dtb files
cd /boot
tar -xf linux-dtb-4.4.38-oxnas-tld-5.tar

4. And install it with dpkg. If you encounter error with flash-kernel when running dpkg, then remove flash-kernel first to avoid potential problem (It is much better to generate uImage and uInitrd manually anyway):
cd /boot
apt-get remove flash-kernel 
dpkg -i linux-image-4.4.38-oxnas-tld-5_5_armel.deb

5. Create uImage and uInitrd manually:
cd /boot
mv uImage uImage.bak
mv uInitrd uInitrd.bak
mkimage -A arm -O linux -T kernel -C none -a 0x60008000 -e 0x60008000 -n Linux-4.4.38-oxnas-tld-5 -d vmlinuz-4.4.38-oxnas-tld-5 uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x60000000 -e 0x60000000 -n initramfs-4.4.38-oxnas-tld-5  -d initrd.img-4.4.38-oxnas-tld-5 uInitrd

6. Setup U-Boot envs:

Note: you must have the latest U-Boot (e.g. 2013.10 and later) installed to do this step.

If you have the Pogo Pro (with PCI) then there is no need to adjust the DTB variable. If you have other boxes such as the Pogo Classic (no PCI), then adjust the DTB name. Other envs in the default can be adjusted later after booted into Debian.

fw_setenv dtb_file '/boot/dts/ox820-pogoplug-classic.dtb'

Note: DTBs for supported and potentially support boxes:
ox820-pogoplug-pro.dtb
ox820-kd20.dtb
ox820-akitio.dtb
ox820-pogoplug-classic.dtb
ox820-stg212.dtb


7. Sync. Double check your u-boot envs, make sure there is no error. And reboot
sync
fw_printenv
reboot

B. Installation to run with stock U-Boot in NAND

This method is deprecated due to the kernel 4.0 Oxnas size and stock u-boot limitation. Please see kernel linux-3.18.5-oxnas-tld-1for instruction to install that kernel version if you are still running stock u-boot.

DONE.


==============================================================

Updated 03 July 2015:

Kernel linux-4.1.0-oxnas-tld-1 package was uploaded. The following features are new in this version:

- CONFIG_USB_HIDDEV

Latest Linux kernel 4.0 general release information can be found at:
LinuxChanges log

Please use the same installation instruction in linux-4.0.0-oxnas-tld-1 (updated 16 April 2015) below. Simply replace 4.0.0-oxnas-tld-1 with 4.1.0-oxnas-tld-1 in the instruction.


Download at Dropbox
linux-4.1.0-oxnas-tld-1.bodhi.tar.bz2
4fa1cd9aeb081f168a2e859b44e47d96


==============================================================

Updated 06 May 2015:

Kernel linux-4.0.0-oxnas-tld-2 package was uploaded. The following features are new in this version:

1. Automount (AUTOFS), pNFS, XFS
2. MD (Raid)
3. Zswap
4. All NLS codepages

There was no bug fixed in this release, only new capabilities added to the kernel configuration as stated above. There is no need to upgrade the kernel if you don't need those capabilities.

Please use the same installation instruction in linux-4.0.0-oxnas-tld-1 (updated 16 April 2015) right below. Simply replace 4.0.0-oxnas-tld-1 with 4.0.0-oxnas-tld-2 in the instruction.


Download at Dropbox
linux-4.0.0-oxnas-tld-2.bodhi.tar.bz2
md5:
a10462cfd86828ff4bfcc868ee76f0de


==============================================================

Updated 16 April 2015:

Kernel linux-4.0.0-oxnas-tld-1 package was uploaded. The following features are new in this version:

- Added keyboard supports
- Added bluetooth supports, including ath3k
- Added nls-utf-8 supports.
- Add various kernel configs that are new in 4.0 (e.g. device tree overlay).

Warning: This kernel has grown too big, so it will not work for stock u-boot or its Arch u-boot variant. Stock u-boot has a limitation of 4M uImage, so it will not boot. Please stay with kernel 3.18.5 if you're still booting with stock u-boot. The new u-boot works without limitation. In the future, if requested, I could try to move some module to initramfs to shrink it. However, I'm not sure about the timeline, and whether it is worthwhile to spend time to do.

Credits: thanks to various forum members (LeggoMyEggo, Gravelrash, Robert, denexo, and many others) to report and request the missing features above.

Latest Linux kernel 4.0 general release information can be found at:
LinuxChanges log

Download at Dropbox
linux-4.0.0-oxnas-tld-1-bodhi.tar.bz2
md5:
65b4f2404378c6fd4ac3e1339b0d264d

This tarball contains 7 files:

linux-image-4.0.0-oxnas-tld-1_1.0_armel.deb
linux-headers-4.0.0-oxnas-tld-1_1.0_armel.deb
config-4.0.0-oxnas-tld-1
zImage-4.0.0-oxnas-tld-1
ox820-pogoplug-pro.dtb
ox820-pogoplug-classic.dtb
linux-4.0.0-oxnas-tld-1.patch

INSTALLATION:

A. Installation to run with new U-Boot in NAND (see new U-Boot thread here)

1. Backup your current uImage and uInitrd and other kernel files. In the /boot directory, these are files for your current kernel (xx.xx.xx is the version number):

uInitrd
uImage
initrd.img-xx.xx.xx-xxx
System.map-xx.xx.xx-xxx
vmlinuz-xx.xx.xx-xxx
config-xx.xx.xx-xxx

2. Extract the kernel in the archive:
cd /boot
tar -xjf linux-4.0.0-oxnas-tld-1-bodhi.tar.bz2

3. Create a dts directory for the dtb files
cd /boot
mkdir dts
mv ox820-pogoplug-pro.dtb dts/
mv ox820-pogoplug-classic.dtb dts/

4. And install it with dpkg. If you encounter error with flash-kernel when running dpkg, then remove flash-kernel first to avoid potential problem (It is much better to generate uImage and uInitrd manually anyway):
cd /boot
apt-get remove flash-kernel 
dpkg -i linux-image-4.0.0-oxnas-tld-1_1.0_armel.deb

5. Create uImage and uInitrd manually:
cd /boot
mkimage -A arm -O linux -T kernel -C none -a 0x60008000 -e 0x60008000 -n Linux-4.0.0-oxnas-tld-1 -d vmlinuz-4.0.0-oxnas-tld-1 uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x60000000 -e 0x60000000 -n initramfs-4.0.0-oxnas-tld-1  -d initrd.img-4.0.0-oxnas-tld-1 uInitrd

6. Setup U-Boot envs:

The u-boot envs below are for 1st time upgrading, you don't need to do this step if you've installed the latest U-Boot for Oxnas. Just make sure the DTB file is the correct one for your box, replace ox820-pogoplug-pro.dtb below with the correct DTB name for your box (if you have other OXNAS box).

Pogo Pro vs. Pogo Classic: If you're installing this on a Pogo V3 Classic (no PCI), replace the ox820-pogoplug-pro.dtb below with ox820-pogoplug-classic.dtb.

Set up booting envs:
fw_setenv uinitrd_addr '0x60e00000'
fw_setenv uimage_addr '0x60500000'
fw_setenv dtb_addr '0x62c00000'
fw_setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10'
fw_setenv dt_bootm 'bootm $uimage_addr $uinitrd_addr $dtb_addr'
fw_setenv dt_load_dtb 'ext2load usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb'
fw_setenv dt_load_initrd 'ext2load usb 0:1 $uinitrd_addr /boot/uInitrd'
fw_setenv dt_load_uimage 'ext2load usb 0:1 $uimage_addr /boot/uImage'
fw_setenv dt_usb_boot 'run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm'
fw_setenv dt_usb_bootcmd 'run usb_set_bootargs; run dt_usb_boot'
fw_setenv dt_bootcmd_usb 'usb start; run dt_usb_bootcmd; usb stop'
fw_setenv bootcmd 'run dt_bootcmd_usb;  reset'

7. Sync. Double check your u-boot envs, make sure there is no error. And reboot
sync
fw_printenv
reboot

B. Installation to run with stock U-Boot in NAND

This method is deprecated due to the kernel 4.0 Oxnas size and stock u-boot limitation. Please see kernel linux-3.18.5-oxnas-tld-1for instruction to install that kernel version if you are still running stock u-boot.

DONE.

==============================================================

Updated 12 Feb 2015:

Kernel linux-3.18.5-oxnas-tld-1 package was uploaded. The following features are new in this version:

- Added various kernel configuration that are newly available in 3.18, and also various kernel configuration per forum users requests: loop device, stock wifi supports, encrypted fs.

Note: beginning this version, we can dist-upgrade to jessie (not possible with previous kernel version 3.17.0-oxnas-tld-1 or earlier).


Latest Linux kernel 3.18 general release information can be found at:
LinuxChanges log

Download at Dropbox
linux-3.18.5-oxnas-tld-1-bodhi.tar.bz2
md5:
df386f09cf7323472d40432d3da382d5

This tarball contains 7 files:

linux-image-3.18.5-oxnas-tld-1_1_armel.deb
linux-headers-3.18.5-oxnas-tld-1_1_armel.deb
config-3.18.5-oxnas-tld-1
zImage-3.18.5-oxnas-tld-1
ox820-pogoplug-pro.dtb
ox820-pogoplug-classic.dtb
linux-3.18.5-oxnas-tld-1.patch

INSTALLATION:

A. Installation to run with new U-Boot in NAND (see new U-Boot thread here)

1. Backup your current uImage and uInitrd and other kernel files. In the /boot directory, these are files for your current kernel (xx.xx.xx is the version number):

uInitrd
uImage
initrd.img-xx.xx.xx-xxx
System.map-xx.xx.xx-xxx
vmlinuz-xx.xx.xx-xxx
config-xx.xx.xx-xxx

2. Extract the kernel in the archive:
cd /boot
tar -xjf linux-3.18.5-oxnas-tld-1-bodhi.tar.bz2

3. Create a dts directory for the dtb files
cd /boot
mkdir dts
mv ox820-pogoplug-pro.dtb dts/
mv ox820-pogoplug-classic.dtb dts/

4. And install it with dpkg. If you encounter error with flash-kernel when running dpkg, then remove flash-kernel first to avoid potential problem (It is much better to generate uImage and uInitrd manually anyway):
apt-get remove flash-kernel 
dpkg -i linux-image-3.18.5-oxnas-tld-1_1_armel.deb

5. Create uImage and uInitrd manually:
mkimage -A arm -O linux -T kernel -C none -a 0x60008000 -e 0x60008000 -n Linux-3.18.5-oxnas-tld-1 -d /boot/vmlinuz-3.18.5-oxnas-tld-1 /boot/uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x60000000 -e 0x60000000 -n initramfs-3.18.5-oxnas-tld-1  -d /boot/initrd.img-3.18.5-oxnas-tld-1 /boot/uInitrd

6. Setup U-Boot envs:

Disclaimer: The following U-Boot envs settings are recommendation only. If you don't have serial console connected, please do not attempt. Be aware that changing U-Boot env settings to the wrong values will lock you out of the box until you can connect a serial console.

Pogo Pro vs. Pogo Classic: If you're installing this on a Pogo V3 Classic (no PCI), replace the ox820-pogoplug-pro.dtb below with ox820-pogoplug-classic.dtb.

Set up booting envs:
fw_setenv uinitrd_addr '0x60e00000'
fw_setenv uimage_addr '0x60500000'
fw_setenv dtb_addr '0x62c00000'
fw_setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10'
fw_setenv dt_bootm 'bootm $uimage_addr $uinitrd_addr $dtb_addr'
fw_setenv dt_load_dtb 'ext2load usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb'
fw_setenv dt_load_initrd 'ext2load usb 0:1 $uinitrd_addr /boot/uInitrd'
fw_setenv dt_load_uimage 'ext2load usb 0:1 $uimage_addr /boot/uImage'
fw_setenv dt_usb_boot 'run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm'
fw_setenv dt_usb_bootcmd 'run usb_set_bootargs; run dt_usb_boot'
fw_setenv dt_bootcmd_usb 'usb start; run dt_usb_bootcmd; usb stop; reset'
fw_setenv bootcmd 'run dt_bootcmd_usb'

7. Sync. Double check your u-boot envs, make sure there is no error. And reboot
sync
fw_printenv
reboot

B. Installation to run with stock U-Boot in NAND

If you're running the Pogoplug V3 with stock U-Boot (or the ALAM variant by installing Arch Linux before), the easy way to boot your rootfs with the new kernel is to boot with stock U-Boot tftp. The instruction is the same for section 1 (Installation to run with new U-Boot in NAND), but the uImage needs to be created with the DTB file embedded inside it, and the u-boot environment varialbes need to be setup differently. Assuming you've already set up tftp server on another Linux box.

1. Create uImage and uInitrd manually:

Pogo Pro vs. Pogo Classic: If you're installing this on a Pogo V3 Classic (no PCI), replace the ox820-pogoplug-pro.dtb below with ox820-pogoplug-classic.dtb.

cp -a zImage-3.18.5-oxnas-tld-1 zImage-3.18.5-oxnas-tld-1.fdt
cat dts/ox820-pogoplug-pro.dtb >> zImage-3.18.5-oxnas-tld-1.fdt
mkimage  -A arm -O linux -C none -T kernel -a 0x60008000 -e 0x60008000 -n Linux-3.18.5-oxnas-tld-1 -d zImage-3.18.5-oxnas-tld-1.fdt  uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x60000000 -e 0x60000000 -n initramfs-3.18.5-oxnas-tld-1  -d /boot/initrd.img-3.18.5-oxnas-tld-1 /boot/uInitrd

Copy both uImage and uInitrd to your tftproot server directory

2. Setup U-Boot envs:

Disclaimer: The following U-Boot envs settings are recommendation only. If you don't have serial console connected, please do not attempt. Be aware that changing U-Boot env settings to the wrong values will lock you out of the box until you can connect a serial console.

Set up booting envs. Please adjust the ipaddr (the Pogo V3 IP address) and serverip (the tftp server IP address) to your specific local network settings.
fw_setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10'
fw_setenv ipaddr '192.168.0.222'
fw_setenv serverip '192.168.0.224'
fw_setenv uinitrd_addr '0x60e00000'
fw_setenv uimage_addr '0x60500000'
fw_setenv tftp_bootcmd 'run bootcmd_tftp'
fw_setenv tftp_boot 'bootm $uimage_addr $uinitrd_addr'
fw_setenv tftp_load_uinitrd 'tftpboot $uinitrd_addr uInitrd'
fw_setenv tftp_load_uimage 'tftpboot $uimage_addr uImage'
fw_setenv bootcmd_tftp 'run usb_set_bootargs; run tftp_load_uimage; run tftp_load_uinitrd; run tftp_boot'

3. Test the tftp booting in serial console:
> run bootcmd_tftp

4. After verifying it works, set bootcmd permanently in Debian:
fw_setenv bootcmd  'run bootcmd_tftp'


==============================================================

Updated 02 Nov 2014:

Rootfs Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2 was uploaded. This rootfs is to keep in sync with kernel Linux-3.17.0-oxnas-tld-1.

Basic minimal Debian Oxnas rootfs for Popo Pro/Classic V3 plug:

- tarball size: 83M
- install size: 251M
- a basic wheezy rootfs
- Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, dialog, bz2.
- see LED controls in /etc/rc.local, and /etc/rc0.d/K08halt
- see some useful aliases in /root/.profile
- root password: root

Download at Dropbox:

Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2
md5:
c8e9df471f331c56befc4051a754bfea

And remember to check the hash of what you download, as always.


INSTALLATION:

Installation can be done on any Linux box, with a fresh USB drive (SD card or HDD would work fine too). It is assuming the USB drive is mounted at /media/sdb1.

1. Format a new Ext3 USB drive, and label it rootfs. Note: if your existing uBoot env for rootfs type is ext2, then you might want to keep it consistent and use Ext2 USB drive. It will work with Ext3 drive without problem, though.

For example:
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
rootfstype=ext2

2. Mount the drive on a Linux box. As root user, cd to top level directory and extract it.
cd /media/sdb1 
tar -xjf Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2

3. edit /media/sdb1/etc/fstab entry for /dev/root to match the rootfstype of your usb_rootfstype (however, you can keep it as Ext2 without problem in booting an Ext3 partition).
/dev/root      /               ext2    noatime,errors=remount-ro 0 1

4. Create uImage with embbeded DTB to run with older u-boot. Please see Note 2 below if you are running this kernel witht the new U-Boot.

Pogo Pro vs. Pogo Classic: If you're installing this on a Pogo V3 Classic (no PCI), replace the ox820-pogoplug-pro.dtb below with ox820-pogoplug-classic.dtb.

cd /media/sdb1/boot
cp -a zImage-3.17.0-oxnas-tld-1 zImage-3.17.0-oxnas-tld-1.fdt
cat dts/ox820-pogoplug-pro.dtb >> zImage-3.17.0-oxnas-tld-1.fdt
mkimage  -A arm -O linux -C none -T kernel -a 0x60008000 -e 0x60008000 -n 'Linux-3.3.17.0-oxnas-tld-1' -d zImage-3.17.0-oxnas-tld-1.fdt  uImage
sync

5. Done. Take this USB rootfs to your plug and cold start.

Note1: After logging in this rootf the first time, remember to generate new SSH key to make it your own unique rootfs. And also update your rootfs to get the latest Debian package updates:
rm /etc/ssh/ssh_host*
ssh-keygen -A

apt-get update
apt-get upgrade

Note2: To simplify the first time installation process, the uImage is recreated with the DTB embedded in step 4. If you are familiar with FDT kernel booting, and want to boot with separate DTB, see the Kernel 3.17 installation section A.6 in this thread for instruction about setting up u-boot envs. Or if you are going run this kernel with the new u-boot as mentioned, then do set up booting as described in section A.6.


Note3: if the Linux box that you are using to create rootfs does not already have mkimage installed then install u-boot-tools package to make it available:
apt-get install u-boot-tools

Note4: For setting up wireless on the Pogo Pro, please see: http://forum.doozan.com/read.php?2,16044,20964#msg-20964

==============================================================

Updated 29 Oct 2014:

Kernel linux-3.17.0-oxnas-tld-1 package was uploaded. The following features are new in this version:

- Supports for CIFS

Latest Linux kernel 3.17 general release information can be found at:
LinuxChanges log

Download at Dropbox
linux-3.17.0-oxnas-tld-1-bodhi.tar.bz2
md5:
4aaff07a9e6e988d81f19c0c517b8f5c

This tarball contains 7 files:

linux-image-3.17.0-oxnas-tld-1_1_armel.deb
linux-headers-3.17.0-oxnas-tld-1_1_armel.deb
config-3.17.0-oxnas-tld-1
zImage-3.17.0-oxnas-tld-1
ox820-pogoplug-pro.dtb
ox820-pogoplug-classic.dtb
linux-3.17.0-oxnas-tld-1.patch

INSTALLATION:

A. Installation to run with new U-Boot in NAND (see new U-Boot thread here)

1. Backup your current uImage and uInitrd and other kernel files. In the /boot directory, these are files for your current kernel (xx.xx.xx is the version number):

uInitrd
uImage
initrd.img-xx.xx.xx-xxx
System.map-xx.xx.xx-xxx
vmlinuz-xx.xx.xx-xxx
config-xx.xx.xx-xxx

2. Extract the kernel in the archive:
cd /boot
tar -xjf linux-3.17.0-oxnas-tld-1-bodhi.tar.bz2

3. Create a dts directory for the dtb files
cd /boot
mkdir dts
mv ox820-pogoplug-pro.dtb dts/
mv ox820-pogoplug-classic.dtb dts/

4. And install it with dpkg. If you encounter error with flash-kernel when running dpkg, then remove flash-kernel first to avoid potential problem (It is much better to generate uImage and uInitrd manually anyway):
apt-get remove flash-kernel 
dpkg -i linux-image-3.17.0-oxnas-tld-1_1_armel.deb

5. Create uImage and uInitrd manually:
mkimage -A arm -O linux -T kernel -C none -a 0x60008000 -e 0x60008000 -n Linux-3.17.0-oxnas-tld-1 -d /boot/vmlinuz-3.17.0-oxnas-tld-1 /boot/uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x60000000 -e 0x60000000 -n initramfs-3.17.0-oxnas-tld-1  -d /boot/initrd.img-3.17.0-oxnas-tld-1 /boot/uInitrd

6. Setup U-Boot envs:

Disclaimer: The following U-Boot envs settings are recommendation only. If you don't have serial console connected, please do not attempt. Be aware that changing U-Boot env settings to the wrong values will lock you out of the box until you can connect a serial console.

Pogo Pro vs. Pogo Classic: If you're installing this on a Pogo V3 Classic (no PCI), replace the ox820-pogoplug-pro.dtb below with ox820-pogoplug-classic.dtb.

Set up booting envs:
fw_setenv uinitrd_addr '0x60e00000'
fw_setenv uimage_addr '0x60500000'
fw_setenv dtb_addr '0x62c00000'
fw_setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10'
fw_setenv dt_bootm 'bootm $uimage_addr $uinitrd_addr $dtb_addr'
fw_setenv dt_load_dtb 'ext2load usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb'
fw_setenv dt_load_initrd 'ext2load usb 0:1 $uinitrd_addr /boot/uInitrd'
fw_setenv dt_load_uimage 'ext2load usb 0:1 $uimage_addr /boot/uImage'
fw_setenv dt_usb_boot 'run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm'
fw_setenv dt_usb_bootcmd 'run usb_set_bootargs; run dt_usb_boot'
fw_setenv dt_bootcmd_usb 'usb start; run dt_usb_bootcmd; usb stop; reset'
fw_setenv bootcmd 'run dt_bootcmd_usb'

7. Sync. Double check your u-boot envs, make sure there is no error. And reboot
sync
fw_printenv
reboot

B. Installation to run with stock U-Boot in NAND

If you're running the Pogoplug V3 with stock U-Boot (or the ALAM variant by installing Arch Linux before), the easy way to boot your rootfs with the new kernel is to boot with stock U-Boot tftp. The instruction is the same for section 1 (Installation to run with new U-Boot in NAND), but the uImage needs to be created with the DTB file embedded inside it, and the u-boot environment varialbes need to be setup differently. Assuming you've already set up tftp server on another Linux box.

1. Create uImage and uInitrd manually:

Pogo Pro vs. Pogo Classic: If you're installing this on a Pogo V3 Classic (no PCI), replace the ox820-pogoplug-pro.dtb below with ox820-pogoplug-classic.dtb.

cp -a zImage-3.17.0-oxnas-tld-1 zImage-3.17.0-oxnas-tld-1.fdt
cat dts/ox820-pogoplug-pro.dtb >> zImage-3.17.0-oxnas-tld-1.fdt
mkimage  -A arm -O linux -C none -T kernel -a 0x60008000 -e 0x60008000 -n Linux-3.17.0-oxnas-tld-1 -d zImage-3.17.0-oxnas-tld-1.fdt  uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x60000000 -e 0x60000000 -n initramfs-3.17.0-oxnas-tld-1  -d /boot/initrd.img-3.17.0-oxnas-tld-1 /boot/uInitrd

Copy both uImage and uInitrd to your tftproot server directory

2. Setup U-Boot envs:

Disclaimer: The following U-Boot envs settings are recommendation only. If you don't have serial console connected, please do not attempt. Be aware that changing U-Boot env settings to the wrong values will lock you out of the box until you can connect a serial console.

Set up booting envs. Please adjust the ipaddr (the Pogo V3 IP address) and serverip (the tftp server IP address) to your specific local network settings.
fw_setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10'
fw_setenv ipaddr '192.168.0.222'
fw_setenv serverip '192.168.0.224'
fw_setenv uinitrd_addr '0x60e00000'
fw_setenv uimage_addr '0x60500000'
fw_setenv tftp_bootcmd 'run bootcmd_tftp'
fw_setenv tftp_boot 'bootm $uimage_addr $uinitrd_addr'
fw_setenv tftp_load_uinitrd 'tftpboot $uinitrd_addr uInitrd'
fw_setenv tftp_load_uimage 'tftpboot $uimage_addr uImage'
fw_setenv bootcmd_tftp 'run usb_set_bootargs; run tftp_load_uimage; run tftp_load_uinitrd; run tftp_boot'

3. Test the tftp booting in serial console:
> run bootcmd_tftp

4. After verifying it works, set bootcmd permanently in Debian:
fw_setenv bootcmd  'run bootcmd_tftp'

==============================================================
Updated 02 Oct 2014:

Kernel linux-3.16.0-oxnas-tld-4 package was uploaded. The following features are new in this version:

- Wireless (added several wifi driver modules)
- 3G
- i2c
- Webcam (most of multimedia modules are now included)
- problem with SAMBA files transfer (TCP segmentation offload) has been verified that this bug did not affect this kernel.

Download at Dropbox
linux-3.16.0-oxnas-tld-4-bodhi.tar.bz2
md5:
ecd6ce5eece557c85b6bcb694adf7b31

This tarball contains 7 files:

linux-image-3.16.0-oxnas-tld-4_4_armel.deb
linux-headers-3.16.0-oxnas-tld-4_4_armel.deb
zImage-3.16.0-oxnas-tld-4
config-3.16.0-oxnas-tld-4
ox820-pogoplug-pro.dtb
ox820-pogoplug-classic.dtb
linux-3.16.0-oxnas-tld-1.patch

Installation:

Please follow the same installation instruction for kernel linux-3.15.3-oxnas-tld-1 below (replace 3.15.3-oxnas-tld-1 with 3.16.0-oxnas-tld-4 in the instruction).

==============================================================
Updated 24 Aug 2014:

Kernel linux-3.16.0-oxnas-tld-1 package was uploaded. The following features are new in this version:

- CONFIG_USB_ACM
- Supports for CPU Frequency governor, with CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
- Wireless supports.

Also see kernel 3.16 new features described here: LinuxChanges

Download at Dropbox:

linux-3.16.0-oxnas-tld-1-bodhi.tar.bz2
md5:
89b77478515c58d3149511275fbc2bfd

This tarball contains 7 files:

linux-image-3.16.0-oxnas-tld-1_1_armel.deb
linux-headers-3.16.0-oxnas-tld-1_1_armel.deb
zImage-3.16.0-oxnas-tld-1
config-3.16.0-oxnas-tld-1
ox820-pogoplug-pro.dtb
ox820-pogoplug-classic.dtb
linux-3.16.0-oxnas-tld-1.patch (for compiling kernel: this patch should be applied to the kernel source from mainline)

Installation:

Please follow the same installation instruction for kernel linux-3.15.3-oxnas-tld-1 below (replace 3.15.3-oxnas-tld-1 with 3.16.0-oxnas-tld-1 in the instruction).

==============================================================

Updated 05 July 2014:

Kernel linux-3.15.3-oxnas-tld-1 package was uploaded. See kernel 3.15 new features described here:
LinuxChanges

Download at Dropbox:

linux-3.15.3-oxnas-tld-1-bodhi.tar.bz2
md5:
e2dc126c44d59fdf251d55dcafcdbc9d

This tarball contains 7 files:

linux-image-3.15.3-oxnas-tld-1_1.0_armel.deb
linux-headers-3.15.3-oxnas-tld-1_1.0_armel.deb
zImage-3.15.3-oxnas-tld-1
config-3.15.3-oxnas-tld-1
ox820-pogoplug-pro.dtb
ox820-pogoplug-classic.dtb
linux-3.15.3-tld-1-oxnas.patch (for compiling kernel: this patch should be applied to the kernel source from mainline)

Pogo Pro vs. Pogo Classic:

If you're installing this on a Pogo V3 Classic (no PCI), replace the ox820-pogoplug-pro.dtb with ox820-pogoplug-classic.dtb.


INSTALLATION:

1. Installation to run with new U-Boot in NAND (see new U-Boot thread here)

- Backup your rootfs to another USB stick or HDD.

- Boot into your Pogo V3 and change directory to:
cd /boot

- Backup your current uImage and uInitrd (if there is any). In the /boot directory, these are files for your current kernel (xx.xx.xx is the version number):
uInitrd
uImage
initrd.img-xx.xx.xx-xxx
System.map-xx.xx.xx-xxx
vmlinuz-xx.xx.xx-xxx
config-xx.xx.xx-xxx

- Extract the kernel in the archive:
tar -xjf linux-3.15.3-oxnas-tld-1-bodhi.tar.bz2

- Create a dts directory for the dtb (just for organization purpose)
mkdir dts
mv ox820-pogoplug-pro.dtb dts/

- And install it with dpkg. If you encounter error with flash-kernel when running dpkg, then remove flash-kernel first to avoid potential problem (It is much better to generate uImage and uInitrd manually anyway):
apt-get remove flash-kernel 
dpkg -i linux-image-3.15.3-oxnas-tld-1_5_armel.deb

- Create uImage and uInitrd manually:
mkimage -A arm -O linux -T kernel -C none -a 0x60008000 -e 0x60008000 -n Linux-3.15.3-oxnas-tld-1 -d /boot/vmlinuz-3.15.3-oxnas-tld-1 /boot/uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x60000000 -e 0x60000000 -n initramfs-3.15.3-oxnas-tld-1  -d /boot/initrd.img-3.15.3-oxnas-tld-1 /boot/uInitrd

- Setup U-Boot envs:

Disclaimer: The following U-Boot envs settings are recommendation only. If you don't have serial console connected, please do not attempt. Be aware that changing U-Boot env settings to the wrong values will lock you out of the box until you can connect a serial console.

Your booting envs should look like below. These are only for demonstration for the correct load addresses (not to be cut/paste as is). However these are my current u-boot envs.
uinitrd_addr=0x60e00000
uimage_addr=0x60500000
dtb_addr=0x62c00000
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10
dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr
dt_load_dtb=ext2load usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb
dt_load_initrd=ext2load usb 0:1 $uinitrd_addr /boot/uInitrd
dt_load_uimage=ext2load usb 0:1 $uimage_addr /boot/uImage
dt_usb_boot=run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm
dt_usb_bootcmd=run usb_set_bootargs; run dt_usb_boot
dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; reset
bootcmd=run dt_bootcmd_usb

- Connect serial console/netconsole and monitor the boot log.

- Sync. Double check your u-boot envs, make sure there is no error. And reboot
sync
fw_printenv
reboot

2. Installation to run with stock U-Boot in NAND

If you're running the Pogoplug V3 with stock U-Boot (or the ALAM variant by installing Arch Linux before), the easy way to boot your rootfs with the new kernel is to boot with stock U-Boot tftp. The instruction is the same for section 1 (Installation to run with new U-Boot in NAND), but the uImage needs to be created with the DTB file embedded inside it, and the u-boot environment varialbes need to be setup differently. Assuming you've already set up tftp server on another Linux box.

- Create uImage and uInitrd manually:

cp -a zImage-3.15.3-oxnas-tld-1 zImage-3.15.3-oxnas-tld-1.fdt
cat dts/ox820-pogoplug-pro.dtb >> zImage-3.15.3-oxnas-tld-1.fdt
mkimage  -A arm -O linux -C none -T kernel -a 0x60008000 -e 0x60008000 -n 'Linux-3.15.3-oxnas-tld-1' -d zImage-3.15.3-oxnas-tld-1.fdt  uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x60000000 -e 0x60000000 -n initramfs-3.15.3-oxnas-tld-1  -d /boot/initrd.img-3.15.3-oxnas-tld-1 /boot/uInitrd

Copy both uImage and uInitrd to your tftproot server directory

- Setup U-Boot envs:

Disclaimer: The following U-Boot envs settings are recommendation only. If you don't have serial console connected, please do not attempt. Be aware that changing U-Boot env settings to the wrong values will lock you out of the box until you can connect a serial console.

Your booting envs should look like below. These are only for demonstration for the correct load addresses (not to be cut/paste as is). However these are my current u-boot envs. Please adjust the ipaddr (the Pogo V3 IP address) and serverip (the tftp server IP address) to your specific local network settings.
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10
ipaddr=192.168.0.222
serverip=192.168.0.224
uinitrd_addr=0x60e00000
uimage_addr=0x60500000
tftp_bootcmd=run bootcmd_tftp
tftp_boot=bootm $uimage_addr $uinitrd_addr
tftp_load_uinitrd=tftpboot $uinitrd_addr uInitrd
tftp_load_uimage=tftpboot $uimage_addr uImage
bootcmd_tftp=run usb_set_bootargs; run tftp_load_uimage; run tftp_load_uinitrd; run tftp_boot

- Test the tftp booting in serial console:
> run bootcmd_tftp

After verifying it works, set bootcmd permanently in Debian:
fw_setenv bootcmd  'run bootcmd_tftp'

==========================================================
Updated 18 May 2014:

Kernel linux-3.14.0-oxnas-tld-5 package was uploaded. The kernel 3.14 has lot of new features which are described here:
LinuxChanges

Download at Dropbox:

linux-3.14.0-oxnas-tld-5-bodhi.tar.bz2
md5:
654ae31c0a0c7d4169719d51a85d6443

This tarball contains 5 files:

linux-image-3.14.0-oxnas-tld-5_5_armel.deb
zImage-3.14.0-oxnas-tld-5
config-3.14.0-oxnas-tld-5
linux-headers-3.14.0-oxnas-tld-5_5_armel.deb
ox820-pogoplug-pro.dtb

Also, the linux-oxnas-3.14-tld-5.patch is attached in this post.

Download ox820-pogoplug-classic.dtb:

If you're installing this on a Pogo V3 Classic (no PCI), also download the attached ox820-pogoplug-classic.dtb in this post. And replace the ox820-pogoplug-pro.dtb with this DTB.

Installation:

Please follow the same installation instruction as in previous version:
Kernel linux-3.12.13-oxnas-tld-5 package (Updated 12 May 2014)

==============================================================

Updated 13 May 2014:

Rootfs Debian-3.12.13-oxnas-tld-5-rootfs-bodhi.tar.bz2 was uploaded.

Basic minimal Debian Oxnas rootfs for Popo Pro V3 plug:

- tarball size: 76M
- install size: 229M
- a basic wheezy rootfs
- Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, dialog.
- see LED controls in /etc/rc.local, and /etc/rc0.d/K08halt
- see some useful aliases in /root/.profile
- root password: root

Download at Dropbox:

Debian-3.12.13-oxnas-tld-5-rootfs-bodhi.tar.bz2
md5:
62e700af606dc7a686d9aa4f2e702998

Download ox820-pogoplug-classic.dtb:

If you're installing this on a Pogo V3 Classic (no PCI), also download the attached ox820-pogoplug-classic.dtb in this post.

Installation:

- format a new ext3 USB drive, and label it rootfs. Note: your uBoot env for usb_rootfstype must match your USB file system, and it can be Ext2, Ext3 or Ext4. To be able to use this rootfs with stock u-boot, it should be formatted as Ext3. But if you're running new u-boot then it could be Ext4.

- As root user, cd to top level directory and extract it (assuming the USB drive is mounted at /media/sdb1)
cd /media/sdb1 
tar -xjf Debian-3.12.13-oxnas-tld-5-rootfs-bodhi.tar.bz2
- Edit /media/sdb1/etc/fstab entry for /dev/root to match the rootfstype of your usb_rootfstype.

- If you have the Pogoplug V3 Classic (with no PCI) then replace the DTB
mv boot/dts/ox820-pogoplug-pro.dtb boot/dts/ox820-pogoplug-pro.dtb.bak 
mv ox820-pogoplug-classic.dtb boot/dts/ox820-pogoplug-pro.dtb

- Sync to complete .
sync

- On your Pogo Pro, modify your u-boot envs as decribed in the kernel installtion section (updated 12 May 2014), if you have not done so. And please be sure that you read the Disclaimer in that paragraph!
- Connect serial console/netconsole and monitor the boot log
- Cold start your Pogo with this USB rootfs.

Note:

After logging in this rootf the first time, remember to do update your rootfs to get the latest Debian package updates:

apt-get update
apt-get upgrade


==============================================================

Updated 12 May 2014:

Kernel linux-3.12.13-oxnas-tld-5 package was uploaded. The following features were added:

- The kernel is now running with PREEMPT scheduling.
- Ability to boot with root=LABEL=rootfs in kernel parameters so the rootfs will be correctly identified by initrd always (i.e. among multiple attached SATA/USB disks).
- Ability to use Ext2/Ext3/Ext4 rootfs.
- LED is turned on green correctly when the kernel has booted.

Download at Dropbox:
linux-3.12.13-oxnas-tld-5-bodhi.tar.bz2
md5:
123c20dd6a5970aaa3028edf9e5fb72f

This tarball contains 4 files:

linux-image-3.12.13-oxnas-tld-5_5_armel.deb
zImage.3.12.13-oxnas-tld-5
config-3.12.13-oxnas-tld-5
ox820-pogoplug-pro.dtb

Also, the linux-oxnas-3.12.13-tld-5.patch is attached in this post.

INSTALLATION:

1. Installation to run with new U-Boot in NAND (see new U-Boot thread here)

- Backup your rootfs to another USB stick or HDD.

- Boot into your Pogo V3 and change directory to:
cd /boot

- Backup your current uImage and uInitrd (if there is any). In the /boot directory, these are files for your current kernel (xx.xx.xx is the version number):
uInitrd
uImage
initrd.img-xx.xx.xx-xxx
System.map-xx.xx.xx-xxx
vmlinuz-xx.xx.xx-xxx
config-xx.xx.xx-xxx

- Extract the kernel in the archive:
tar -xjf linux-3.12.13-oxnas-tld-5-bodhi.tar.bz2

- Create a dts directory for the dtb (just for organization purpose)
mkdir dts
mv ox820-pogoplug-pro.dtb dts/

- And install it with dpkg. If you encounter error with flash-kernel when running dpkg, then remove flash-kernel first to avoid potential problem (It is much better to generate uImage and uInitrd manually anyway):
apt-get remove flash-kernel 
dpkg -i linux-image-3.12.13-oxnas-tld-5_5_armel.deb

- Create uImage and uInitrd manually:
mkimage -A arm -O linux -T kernel -C none -a 0x60008000 -e 0x60008000 -n Linux-3.12.13-oxnas-tld-5 -d /boot/vmlinuz-3.12.13-oxnas-tld-5 /boot/uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x60000000 -e 0x60000000 -n initramfs-3.12.13-oxnas-tld-5  -d /boot/initrd.img-3.12.13-oxnas-tld-5 /boot/uInitrd

- Setup U-Boot envs:

Disclaimer: The following U-Boot envs settings are recommendation only. If you don't have serial console connected, please do not attempt. Be aware that changing U-Boot env settings to the wrong values will lock you out of the box until you can connect a serial console.

Your booting envs should look like below. These are only for demonstration for the correct load addresses (not to be cut/paste as is). However these are my current u-boot envs.
uinitrd_addr=0x60e00000
uimage_addr=0x60500000
dtb_addr=0x62c00000
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10
dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr
dt_load_dtb=ext2load usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb
dt_load_initrd=ext2load usb 0:1 $uinitrd_addr /boot/uInitrd
dt_load_uimage=ext2load usb 0:1 $uimage_addr /boot/uImage
dt_usb_boot=run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm
dt_usb_bootcmd=run usb_set_bootargs; run dt_usb_boot
dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; reset
bootcmd=run dt_bootcmd_usb

- Connect serial console/netconsole and monitor the boot log.

- Sync. Double check your u-boot envs, make sure there is no error. And reboot
sync
fw_printenv
reboot

2. Installation to run with stock U-Boot in NAND

If you're running the Pogoplug V3 with stock U-Boot (or the ALAM variant by installing Arch Linux before), the easy way to boot your rootfs with the new kernel is to boot with stock U-Boot tftp. The instruction is the same for section 1 (Installation to run with new U-Boot in NAND), but the uImage needs to be created with the DTB file embedded inside it, and the u-boot environment varialbes need to be setup differently. Assuming you've already set up tftp server on another Linux box.

- Create uImage and uInitrd manually:

cp -a zImage.3.12.13-oxnas-tld-5 zImage.3.12.13-oxnas-tld-5.fdt
cat dts/ox820-pogoplug-pro.dtb >> zImage.3.12.13-oxnas-tld-5.fdt
mkimage  -A arm -O linux -C none -T kernel -a 0x60008000 -e 0x60008000 -n 'Linux-3.12.13-oxnas-tld-5' -d zImage.3.12.13-oxnas-tld-5.fdt  uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x60000000 -e 0x60000000 -n initramfs-3.12.13-oxnas-tld-5  -d /boot/initrd.img-3.12.13-oxnas-tld-5 /boot/uInitrd

Copy both uImage and uInitrd to your tftproot server directory

- Setup U-Boot envs:

Disclaimer: The following U-Boot envs settings are recommendation only. If you don't have serial console connected, please do not attempt. Be aware that changing U-Boot env settings to the wrong values will lock you out of the box until you can connect a serial console.

Your booting envs should look like below. These are only for demonstration for the correct load addresses (not to be cut/paste as is). However these are my current u-boot envs. Please adjust the ipaddr (the Pogo V3 IP address) and serverip (the tftp server IP address) to your specific local network settings.
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10
ipaddr=192.168.0.222
serverip=192.168.0.224
uinitrd_addr=0x60e00000
uimage_addr=0x60500000
tftp_bootcmd=run bootcmd_tftp
tftp_boot=bootm $uimage_addr $uinitrd_addr
tftp_load_uinitrd=tftpboot $uinitrd_addr uInitrd
tftp_load_uimage=tftpboot $uimage_addr uImage
bootcmd_tftp=run usb_set_bootargs; run tftp_load_uimage; run tftp_load_uinitrd; run tftp_boot

- Test the tftp booting in serial console:
> run bootcmd_tftp

After verifying it works, set bootcmd permanently in Debian:
fw_setenv bootcmd  'run bootcmd_tftp'

==============================================================

Updated 09 May 2014:

Kernel linux-3.12.13-oxnas-tld-4.2 package was uploaded.

Download at Dropbox:
linux-3.12.13-oxnas-tld-4.2-bodhi.tar.bz2
md5:
ddf820216c7be59740962a1011db2913

This tarball contains 4 files:

linux-image-3.12.13-oxnas-tld-4.2_4.2_armel.deb
zImage.3.12.13-oxnas-tld-4.2
config-3.12.13-oxnas-tld-4.2
ox820-pogoplug-pro.dtb

-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 74 time(s). Last edit at 08/05/2017 05:27AM by bodhi.
FYI.

I'm going to upload another kernel version soon. A few things will be added:

- Switch to PREEMPT scheduling
- Ability to boot with root=LABEL=rootfs in kernel parameters so the rootfs will be correctly identified by initrd always.
- Add netconsole in Debian to monitor kernel booting

-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
I recently acquired 3 PPV3 devices with the B01 revision. They all work perfectly. Along with my arudino projects and raspberrypi projects I've decided to add these low powered devices. I am a long time user of Debian on a lot of different hardware platforms and would like to install it on at least one of these devices. That said, I'm new to this forum and I'm having a hard time wading into the pool. The process of installing to this specific hardware has been frustrating me. Mostly the frustration I am having is trying to find the most current installation information that is viable and still down-load-able. I was able to install the Arch linux distro to a 4GB usb drive but after that I've had little success getting Squeeze or Wheezy to install.

For some reason I seem to get stuck in a loop while searching for the installation instructions. They point back around to the same point and I can't find any current or up to date info. Google is your friend and it almost all seems to point back to the doozan web site for this topic. If it doesn't diretly then the pages link back or give it as the source of their information so one way or another it links back here.

Any light you can shine on the topic at hand would be greatly appreciated.
thebladerunner,

The kernel/rootfs that I uploaded in this thread is the latest out there. Thanks to kref works.

The summary for the current status re Pogo V3:
- new U-Boot is available (but I have not uploaded it yet). See here.
- new Debian kernel and wheezy rootfs are available.
- installation must be done manually (no script)

You are running the B01, which does not have PCI, I assume. This kernel/rootfs could work with it using the Pogo V3 Classic Device Tree file. I have not tried it on my V3 Classic (it's somewhere still in the box since I bought it on a fire sale last year).

In the past, we run Debian rootfs with Arch kernel in NAND, because nobody has compiled Debian kernel for it. But now we do now, so it is full blown Debian.

Feel free to ask questions, I know it's a little bit confusing re this Pogoplug. I just never have time to write up more details description.

-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 2 time(s). Last edit at 05/13/2014 08:13PM by bodhi.
@bodhi:
Did you have time to try the openwrt kernel patches for the 3.13 kernel sources?
I know that they are there and I actually compiled a 3.13 kernel once, but I never found the the time to test the uImage on one of my Pogoplugs..
@Ingmar,

No, I haven't. I did try to bring it to 3.14, but patching has some strange problem and I have not looked further. I thought the openwrt is a straight patch from kref sources. Perhaps you know there is more patch on top ?

-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
Here is post that has Pogo V3 Classic DTB attached (it's untested). It might work with the Pogo Pro kernel.
http://forum.doozan.com/read.php?3,15912,16053#msg-16053

And I've updated 1st post to add more info.

-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 05/13/2014 11:38PM by bodhi.
The openwrt guys seem to have brought it to 3.14, already. Have a look here:
https://gitorious.org/openwrt-oxnas/openwrt-oxnas/commit/6f090b045b00f1739b292d14c1bbf5f84eaa345b
I've also posted this problem at Arch site to get more feedback.

----------------------------------------------------------------
Netconsole problem in kernel 3.12.13 oxnas.

Did anybody set up netconsole in Arch successfully? I'm seeing this problem running Debian and I thought it is probaly in Arch, too. Apparently, the carrier detect happened so fast that it was deemed untrustworthy by netpoll. The end result: eth0 is not brought up properly later. I've tracked it down to this code, and it does not seem to a bug, just the way it was designed:
http://lxr.free-electrons.com/source/net/core/netpoll.c?v=3.12#L1137

Log:
[   12.476695] netpoll: netconsole: local IPv4 address 192.168.0.222
[   12.482792] netpoll: netconsole: interface 'eth0'
[   12.487470] netpoll: netconsole: remote port 6666
[   12.492177] netpoll: netconsole: remote IPv4 address 192.168.0.220
[   12.498327] netpoll: netconsole: remote ethernet address ff:ff:ff:ff:ff:ff
[   12.505198] netpoll: netconsole: device eth0 not up yet, forcing it
[   12.511472] eth0: device MAC address 00:25:31:xx:xx:xx
[   12.518630] netpoll: netconsole: carrier detect appears untrustworthy, waiting 4 seconds
[   14.510635] libphy: stmmac-0:00 - Link is Up - 1000/Full
[   16.533734] console [netcon0] enabled
[   16.537390] netconsole: network logging started
..
..
[....] Configuring network interfaces...SIOCSIFHWADDR: Device or resource busy - you may need to down the interface
Failed to bring up eth0.
done.

So is netpoll a little too strict in determining how trustworthy the carrier detect is?
TIA for any feedback,

-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 05/14/2014 07:41PM by bodhi.
VERY NICE work my friend!
Thank you for sharing.
I will be sure to test both your new U-Boot and kernel, once I find the time. Keep up the good work.. ;-)
My pleasure :) It took some minor retrofitting to rebase this Oxnas 3.12 kernel to 3.14 (common PCIe kernel interface changes). I did try to look at OpenWrt patch, but due to my unfamiliarity with it, I could not see exactly what changes they've made!

-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
WOW! A new kernel for the EOL Oxnas! EPIC!
I'll try it asap!

Edit:
Does it work with Pogoplug V3 non Pro too? (I only have the non-WIFI version)

I tried it now with Pogoplug V3 non Pro ("classic"), and it doesn't work for me. Don't know if I did anything wrong.
I screwed it up anyway: I first updated the UBoot, that worked without any problems. But after that I couldn't boot back into my Debian Squeeze rootfs; obviously in my rootfs there wasn't anything in /boot; I thought I had a backup of /boot but sadly I can't find it anymore.

So I tried using the new rootfs with the new kernel, but the Pogoplug V3 gets stuck at
Uncompressing Linux... done, booting the kernel.
Full output (read via serial console)

U-Boot SPL 2013.10 (Apr 27 2014 - 19:08:27)
  Boot device: NAND
Attempting to set PLLA to 800 MHz ...
  plla_ctrl0 : 0000030a
  plla_ctrl1 : 00400000
  plla_ctrl2 : 007f0068
  plla_ctrl3 : 00000193

PLLA Set


U-Boot 2013.10-tld-3 (May 15 2014 - 14:54:14) for OXNAS

DRAM:  128 MiB
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:
Led:    GREEN
mii0
Main Loop
Hit any key to stop autoboot:  0
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
3676848 bytes read in 335 ms (10.5 MiB/s)
1852456 bytes read in 213 ms (8.3 MiB/s)
7029 bytes read in 215 ms (31.3 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
   Image Name:   Linux-3.12.13-oxnas-tld-5
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3676784 Bytes = 3.5 MiB
   Load Address: 60008000
   Entry Point:  60008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
   Image Name:   initramfs-3.12.13-oxnas-tld-5
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    1852392 Bytes = 1.8 MiB
   Load Address: 60000000
   Entry Point:  60000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 62c00000
   Booting using the fdt blob at 0x62c00000
   Loading Kernel Image ... OK
   Loading Ramdisk to 67c66000, end 67e2a3e8 ... OK
   Loading Device Tree to 67c61000, end 67c65b74 ... OK

Led:    GREEN

Starting kernel ...

Uncompressing Linux... done, booting the kernel.


Is there any way how I can revive that device?



Edited 3 time(s). Last edit at 05/23/2014 03:43PM by theliquid.
theliquid,

This kernel is for the Pro with PCI.

You can try to use the ox820-pogoplug-classic.dtb file that I've attached in this post:
http://forum.doozan.com/read.php?3,15912,16053#msg-16053

Save your ox820-pogoplug-pro.dtb and replace this dtb to the same place, same name. And see if you can boot with it. The Classic does not have PCI controller, hopefully the DTB will tell it that there is no PCI and it will boot OK.

If this does not work, I'll compile the Classic version. I meant to do this eventually, but have not got time to do it :)

-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
bodhi Wrote:
-------------------------------------------------------
> theliquid,
>
> This kernel is for the Pro with PCI.
>
> You can try to use the ox820-pogoplug-classic.dtb
> file that I've attached in this post:
> http://forum.doozan.com/read.php?3,15912,16053#msg
> -16053
>
> Save your ox820-pogoplug-pro.dtb and replace this
> dtb to the same place, same name. And see if you
> can boot with it. The Classic does not have PCI
> controller, hopefully the DTB will tell it that
> there is no PCI and it will boot OK.
>
> If this does not work, I'll compile the Classic
> version. I meant to do this eventually, but have
> not got time to do it :)


Hi bodhi!

Thank you for your fast reply! It's working now!!!! :)
Thanks a lot for your help and your hard work in developing for the Pogoplug v3!



Edited 1 time(s). Last edit at 05/23/2014 05:14PM by theliquid.
Hi theliquid,

Cool! so the classic DTB works fine after you've replaced it? I would like to include that fact in the 1st post.

-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 05/23/2014 05:18PM by bodhi.
Yes. I just renamed it to ox820-pogoplug-pro.dtb as you said. Now the PogoV3 is booting normally!
Addition: I successfully upgraded to kernel version 3.14.0. I just let the ox820-pogoplug-pro.dtb in place.

The best feature of your uboot/kernel is that I can finally boot up that Pogoplug with more than one usb drive attached. (With the older kernel/uboot it didn't start when I attached more than the rootfs-usb-device).
Awesome!

Note in booting multiple USB/SATA. If only one partition is labeled rootfs, then it will be found correctly. And it does not matter how many devices that contain Debian installation . But if more than one partition are labeled rootfs then you might run into the situation when the kernel uImage and uInitrd from one partition, but the actual rootfs is from another! In this situation, their labels should be different (e.g. rootfs1, rootfs2,….)

-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
Hi, I have a problem...

Quote

root@debian:/boot# mkimage -A arm -O linux -T kernel -C none -a 0x60008000 -e 0x60008000 -n linux-3.12.13-oxnas-tld-5 -d /boot/vmlinuz-3.12.13-oxnas-tld-5 /boot/uImage
Image Name: linux-3.12.13-oxnas-tld-5
Created: Sat May 24 01:29:05 2014
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3676784 Bytes = 3590.61 kB = 3.51 MB
Load Address: 60008000
Entry Point: 60008000
root@debian:/boot# mkimage -A arm -O linux -T ramdisk -C gzip -a 0x60000000 -n initramfs-3.12.13-oxnas-tld-5 -d /boot/initrd.img-3.12.13-oxnas-tld-5 /boot/uInitrd
Image Name: initramfs-3.12.13-oxnas-tld-5
Created: Sat May 24 01:31:50 2014
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 1852162 Bytes = 1808.75 kB = 1.77 MB
Load Address: 60000000
Entry Point: 60000000
root@debian:/boot# sync
root@debian:/boot# fw_printenv
Warning: Bad CRC, using default environment
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
baudrate=115200
Any help?
Sorry.. I have Pogoplug Pro
effendi,

- Which U-Boot and kernel was you running on this Pogo before installing the new kernel?
- Did you follow the instruction to set up U-Boot envs? This section:
- Setup U-Boot envs: 

Disclaimer: The following U-Boot envs settings are recommendation only. If you don't have serial console connected, please do not attempt. Be aware that changing U-Boot env settings to the wrong values will lock you out of the box until you can connect a serial console. 

Your booting envs should look like below. These are only for demonstration for the correct load addresses (not to be cut/paste as is). However these are my current u-boot envs. 
uinitrd_addr=0x60e00000
uimage_addr=0x60500000
dtb_addr=0x62c00000
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10
dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr
dt_load_dtb=ext2load usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb
dt_load_initrd=ext2load usb 0:1 $uinitrd_addr /boot/uInitrd
dt_load_uimage=ext2load usb 0:1 $uimage_addr /boot/uImage
dt_usb_boot=run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm
dt_usb_bootcmd=run usb_set_bootargs; run dt_usb_boot
dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; reset
bootcmd=run dt_bootcmd_usb

- Does your /etc/fw_env.config look like this?
root@PogoPro:/localdisk/linux/uboot# cat /etc/fw_env.config 
# pogoplug pro
  /dev/mtd0               0x00100000      0x20000         0x20000

-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
After hacking around a bit with this kernel I realized that I'm missing compatibility for tun devices. It seems tun.ko is missing. Is there any way to support it?
theliquid,

TUN It is not included in the current config, and I could build a new version to include it. But I'm about to be on the road for a while, so probably about late next month is when I can test and release.

-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
Ok, thanks for the reply. No need to rush. I still have my Pogoplug V1 :)
hello

does the wifi board work with this package?
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: