Welcome! Log In Create A New Profile

Advanced

Howto: Install readonly emdebian on NAND

Posted by Jeff 
zussel
Re: Howto: Install readonly emdebian on NAND
January 21, 2011 07:41AM
Thank you very much for pointing out the solution for this problem! I tried to figured it out, but just found out that dash couldn't be installed. Thought it has something to do with a link from "sh" to "dash". Didn't believe that the solution is that simple :-)

Thanks again! Installation is running right now.
Sascha

Sven Wrote:
-------------------------------------------------------
> - last reply for today -- promised! -
>
> Hard to find, but easy to fix...
>
> I read the debootstrap.log to find the package
> 'dash' not installing. Then I chroot'ed into
> debian and manually tried to install it - then I
> got the error of a non existent path!
> Just add this line before the actual call of
> debootstrap (there is already another mkdir
> present):
> mkdir -p $ROOT/usr/share/man/man1
>
> Et voila!
> Installation continues...
Re: Howto: Install readonly emdebian on NAND
January 24, 2011 10:13AM
Quote
Jeff
  • Configure UBIFS booting
fw_setenv set_bootargs_ubi 'setenv bootargs console=$console ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs $mtdparts init=/sbin/init-ro'
fw_setenv bootcmd_ubi 'run set_bootargs_ubi; ubi part data; ubifsmount rootfs; ubifsload 0x800000 /boot/uImage; ubifsload 0x1100000 /boot/uInitrd; bootm 0x800000 0x1100000'

# Configure new bootloader to run old uBoot
fw_setenv bootcmd 'run bootcmd_ubi; run bootcmd_usb; run bootcmd_pogo; reset'
After first bricking my dockstar by not having any access to it any more, I finally managed to understand what was wrong (by grabbing a serial console port cable)...
Now I wanted to ask you to update this guide to match your current uBoot naming convention:
fw_setenv ubifs_set_bootargs 'setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts init=/sbin/init-ro'
fw_setenv ubifs_bootcmd 'run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi'

# Configure new bootloader to run old uBoot
fw_setenv bootcmd 'usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset'

The lines to make UBI booting first seems to be done already in current uBoot install scripts, so one only needs to restore the boot order to boot USB first if needed.
Furthermore I found it more suitable to add the required read-only hints to the custom parameters to make them survive any uBoot updates!

Here 'my' solution (leaving all original bootargs untouched):
  • In the install script replace the line
    fw_setenv usb_set_bootargs 'setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts init=/sbin/init-ro'
    With this:
    fw_setenv usb_custom_params 'init=/sbin/init-ro'
    If you already ran the provided way, additionally restore your usb_set_bootargs and maybe ubifs_set_bootargs:
    fw_setenv usb_set_bootargs 'setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params'  fw_setenv ubifs_set_bootargs 'setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params'
  • Configure UBIFS booting (init readonly)
    fw_setenv ubifs_custom_params 'init=/sbin/init-ro'
  • Restore order to boot USB first, then UBIFS
    fw_setenv bootcmd 'usb start; run force_rescue_bootcmd; run usb_bootcmd; run ubifs_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset'

...maybe it's even time to collect everything together in one single (and current) guide to match your current scripts!
I was some kind of impressed to find the ability to force rescue_boot by simply placing a file on my USB stick, although this did not work on the first try - but will go into this later...
Re: Howto: Install readonly emdebian on NAND
February 04, 2011 08:38PM
I just installed the rescue image. I am also able to boot from an external drive. Since I no longer have the original pogo image on the drive, how can I install debian to the NAND? I tried to install from the rescue image but it failed (even after renaming to dhclient to dhclient3).

Also, everytime I reboot my dockstar, it boots into the resuce image. I have to run e2fsck and mount and unmount the usb drive for it to boot from the usb drive again. Is there anyway around this? I would like the dockstar to come up on its own if for instance there is a power loss etc.
Re: Howto: Install readonly emdebian on NAND
February 07, 2011 08:16AM
jerome
Re: Howto: Install readonly emdebian on NAND
February 20, 2011 11:54AM
Hi everbody
I set the env with the command " fw_setenv bootcmd 'run bootcmd_usb; run bootcmd_ubi; run bootcmd_pogo; reset' ". After reboot, my dockstar is going green, off, green etc ... and i can't ssh to. Is it definitively down ?
I need help !

jerome
jerome
Re: Howto: Install readonly emdebian on NAND
February 20, 2011 12:03PM
jerome Wrote:
-------------------------------------------------------
> Hi everbody
> I set the env with the command " fw_setenv bootcmd
> 'run bootcmd_usb; run bootcmd_ubi; run
> bootcmd_pogo; reset' ". After reboot, my dockstar
> is going green, off, green etc ... and i can't ssh
> to. Is it definitively down ?
> I need help !
>
> jerome

To be more precise, it enter in a cycle of green blinks (~4s) and off (~3s) ...
I can confirm that the changing of dhcp-client to dhcp3-client and the "mkdir" are the two changes needed (as of 2011/02/20) to Jeff's script to allow emdebian to be installed.
schrad
Re: Howto: Install readonly emdebian on NAND
March 05, 2011 05:21AM
i made the two changes:
- mkdir
- dhcp3

but there is still a problem!!

Selecting previously deselected package uboot-envtools.
(Reading database ... 6459 files and directories currently installed.)
Unpacking uboot-envtools (from /tmp/envtools.deb) ...
Setting up uboot-envtools (20081215-2) ...
./dockstar.emdebian-squeeze-readonly.sh: line 249: /tmp/debian/usr/bin/mkimage: not found
./dockstar.emdebian-squeeze-readonly.sh: line 250: /tmp/debian/usr/bin/mkimage: not found
Yuriy
Re: Howto: Install readonly emdebian on NAND
March 25, 2011 08:08PM
After downloading and running ./dockstar.emdebian-squeeze-readonly.sh I got following errors.
Any help with it would be greatly appreciated.
Thanks.



# Starting debootstrap installation
I: Retrieving Release
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
I: Found additional required dependencies: debconf debconf-i18n dmsetup insserv libbz2-1.0 libdb4.8 libudev0
I: Found additional base dependencies: adduser cpio gnupg gpgv isc-dhcp-client isc-dhcp-common klibc-utils libbsd0 libcap2 libedit2 libgssapi-krb5-2 libk5crypto3 libkeyutils1 libklibc libkrb5-3 libkrb5support0 liblzo2-2 libncursesw5 libreadline6 libssl0.9.8 libusb-0.1-4 libuuid-perl libwrap0 linux-image-2.6.32-5-kirkwood openssh-blacklist openssh-client procps readline-common vim-common
I: Checking component main on http://www.emdebian.org/grip...
I: Retrieving adduser
I: Validating adduser
W: http://www.emdebian.org/grip/pool/main/a/adduser/adduser_3.112+nmu2em1_all.deb was corrupt
W: Couldn't download package adduser
I: Retrieving apt
I: Validating apt
W: http://www.emdebian.org/grip/pool/main/a/apt/apt_0.8.10.3em1_armel.deb was corrupt
W: Couldn't download package apt
I: Retrieving base-files
I: Validating base-files
W: http://www.emdebian.org/grip/pool/main/b/base-files/base-files_6.0em1_armel.deb was corrupt
W: Couldn't download package base-files
I: Retrieving base-passwd
I: Validating base-passwd
W: http://www.emdebian.org/grip/pool/main/b/base-passwd/base-passwd_3.5.22em1_armel.deb was corrupt
W: Couldn't download package base-passwd
I: Retrieving bash
I: Validating bash
W: http://www.emdebian.org/grip/pool/main/b/bash/bash_4.1-3em1_armel.deb was corrupt
W: Couldn't download package bash
I: Retrieving bsdutils
I: Validating bsdutils
W: http://www.emdebian.org/grip/pool/main/u/util-linux/bsdutils_2.17.2-9em1_armel.deb was corrupt
W: Couldn't download package bsdutils
I: Retrieving coreutils
I: Validating coreutils
W: http://www.emdebian.org/grip/pool/main/c/coreutils/coreutils_8.5-1em1_armel.deb was corrupt
W: Couldn't download package coreutils
I: Retrieving cpio
I: Validating cpio
W: http://www.emdebian.org/grip/pool/main/c/cpio/cpio_2.11-4em1_armel.deb was corrupt
W: Couldn't download package cpio
I: Retrieving dash
I: Validating dash
W: http://www.emdebian.org/grip/pool/main/d/dash/dash_0.5.5.1-7.4em1_armel.deb was corrupt
W: Couldn't download package dash
I: Retrieving debconf
I: Validating debconf
W: http://www.emdebian.org/grip/pool/main/d/debconf/debconf_1.5.36em1_all.deb was corrupt
W: Couldn't download package debconf
I: Retrieving debconf-i18n
I: Validating debconf-i18n
W: http://www.emdebian.org/grip/pool/main/d/debconf/debconf-i18n_1.5.36em1_all.deb was corrupt
W: Couldn't download package debconf-i18n
I: Retrieving debian-archive-keyring
I: Validating debian-archive-keyring
W: http://www.emdebian.org/grip/pool/main/d/debian-archive-keyring/debian-archive-keyring_2010.08.28em1_all.deb was corrupt
W: Couldn't download package debian-archive-keyring
I: Retrieving debianutils
I: Validating debianutils
W: http://www.emdebian.org/grip/pool/main/d/debianutils/debianutils_3.4em1_armel.deb was corrupt
W: Couldn't download package debianutils
I: Retrieving dhcp3-client
I: Validating dhcp3-client
W: http://www.emdebian.org/grip/pool/main/i/isc-dhcp/dhcp3-client_4.1.1-P1-15em1_all.deb was corrupt
W: Couldn't download package dhcp3-client
I: Retrieving diffutils
I: Validating diffutils
W: http://www.emdebian.org/grip/pool/main/d/diffutils/diffutils_3.0-1em1_armel.deb was corrupt
W: Couldn't download package diffutils
I: Retrieving dmsetup
I: Validating dmsetup
W: http://www.emdebian.org/grip/pool/main/l/lvm2/dmsetup_1.02.48-5em1_armel.deb was corrupt
W: Couldn't download package dmsetup
I: Retrieving dpkg
I: Validating dpkg
W: http://www.emdebian.org/grip/pool/main/d/dpkg/dpkg_1.15.8.10em1_armel.deb was corrupt
W: Couldn't download package dpkg
I: Retrieving e2fslibs
I: Validating e2fslibs
W: http://www.emdebian.org/grip/pool/main/e/e2fsprogs/e2fslibs_1.41.12-2em1_armel.deb was corrupt
W: Couldn't download package e2fslibs
I: Retrieving e2fsprogs
I: Validating e2fsprogs
W: http://www.emdebian.org/grip/pool/main/e/e2fsprogs/e2fsprogs_1.41.12-2em1_armel.deb was corrupt
W: Couldn't download package e2fsprogs
I: Retrieving emdebian-archive-keyring
I: Validating emdebian-archive-keyring
W: http://www.emdebian.org/grip/pool/main/e/emdebian-archive-keyring/emdebian-archive-keyring_2.0.2em1_all.deb was corrupt
W: Couldn't download package emdebian-archive-keyring
I: Retrieving findutils
I: Validating findutils
W: http://www.emdebian.org/grip/pool/main/f/findutils/findutils_4.4.2-1+b1em1_armel.deb was corrupt
W: Couldn't download package findutils
I: Retrieving gcc-4.4-base
I: Validating gcc-4.4-base
W: http://www.emdebian.org/grip/pool/main/g/gcc-4.4/gcc-4.4-base_4.4.5-8em1_armel.deb was corrupt
W: Couldn't download package gcc-4.4-base
I: Retrieving gnupg
I: Validating gnupg
W: http://www.emdebian.org/grip/pool/main/g/gnupg/gnupg_1.4.10-4em1_armel.deb was corrupt
W: Couldn't download package gnupg
I: Retrieving gpgv
I: Validating gpgv
W: http://www.emdebian.org/grip/pool/main/g/gnupg/gpgv_1.4.10-4em1_armel.deb was corrupt
W: Couldn't download package gpgv
I: Retrieving grep
I: Validating grep
W: http://www.emdebian.org/grip/pool/main/g/grep/grep_2.6.3-3em1_armel.deb was corrupt
W: Couldn't download package grep
I: Retrieving grip-config
I: Validating grip-config
W: http://www.emdebian.org/grip/pool/main/g/grip-config/grip-config_0.1.6em1_all.deb was corrupt
W: Couldn't download package grip-config
I: Retrieving gzip
I: Validating gzip
W: http://www.emdebian.org/grip/pool/main/g/gzip/gzip_1.3.12-9em1_armel.deb was corrupt
W: Couldn't download package gzip
I: Retrieving hostname
I: Validating hostname
W: http://www.emdebian.org/grip/pool/main/h/hostname/hostname_3.04em1_armel.deb was corrupt
W: Couldn't download package hostname
I: Retrieving ifupdown
I: Validating ifupdown
W: http://www.emdebian.org/grip/pool/main/i/ifupdown/ifupdown_0.6.10em1_armel.deb was corrupt
W: Couldn't download package ifupdown
I: Retrieving initramfs-tools
I: Validating initramfs-tools
W: http://www.emdebian.org/grip/pool/main/i/initramfs-tools/initramfs-tools_0.98.8em1_all.deb was corrupt
W: Couldn't download package initramfs-tools
I: Retrieving initscripts
I: Validating initscripts
W: http://www.emdebian.org/grip/pool/main/s/sysvinit/initscripts_2.88dsf-13.1em1_armel.deb was corrupt
W: Couldn't download package initscripts
I: Retrieving insserv
I: Validating insserv
W: http://www.emdebian.org/grip/pool/main/i/insserv/insserv_1.14.0-2em1_armel.deb was corrupt
W: Couldn't download package insserv
I: Retrieving iproute
I: Validating iproute
W: http://www.emdebian.org/grip/pool/main/i/iproute/iproute_20100519-3em1_armel.deb was corrupt
W: Couldn't download package iproute
I: Retrieving iputils-ping
I: Validating iputils-ping
W: http://www.emdebian.org/grip/pool/main/i/iputils/iputils-ping_20100418-3em1_armel.deb was corrupt
W: Couldn't download package iputils-ping
I: Retrieving isc-dhcp-client
I: Validating isc-dhcp-client
W: http://www.emdebian.org/grip/pool/main/i/isc-dhcp/isc-dhcp-client_4.1.1-P1-15em1_armel.deb was corrupt
W: Couldn't download package isc-dhcp-client
I: Retrieving isc-dhcp-common
I: Validating isc-dhcp-common
W: http://www.emdebian.org/grip/pool/main/i/isc-dhcp/isc-dhcp-common_4.1.1-P1-15em1_armel.deb was corrupt
W: Couldn't download package isc-dhcp-common
I: Retrieving klibc-utils
I: Validating klibc-utils
W: http://www.emdebian.org/grip/pool/main/k/klibc/klibc-utils_1.5.20-1em1_armel.deb was corrupt
W: Couldn't download package klibc-utils
I: Retrieving libacl1
I: Validating libacl1
W: http://www.emdebian.org/grip/pool/main/a/acl/libacl1_2.2.49-4em1_armel.deb was corrupt
W: Couldn't download package libacl1
I: Retrieving libattr1
I: Validating libattr1
W: http://www.emdebian.org/grip/pool/main/a/attr/libattr1_2.4.44-2em1_armel.deb was corrupt
W: Couldn't download package libattr1
I: Retrieving libblkid1
I: Validating libblkid1
W: http://www.emdebian.org/grip/pool/main/u/util-linux/libblkid1_2.17.2-9em1_armel.deb was corrupt
W: Couldn't download package libblkid1
I: Retrieving libbsd0
I: Validating libbsd0
W: http://www.emdebian.org/grip/pool/main/libb/libbsd/libbsd0_0.2.0-1em1_armel.deb was corrupt
W: Couldn't download package libbsd0
I: Retrieving libbz2-1.0
I: Validating libbz2-1.0
W: http://www.emdebian.org/grip/pool/main/b/bzip2/libbz2-1.0_1.0.5-6em1_armel.deb was corrupt
W: Couldn't download package libbz2-1.0
I: Retrieving libc-bin
I: Validating libc-bin
W: http://www.emdebian.org/grip/pool/main/e/eglibc/libc-bin_2.11.2-10em1_armel.deb was corrupt
W: Couldn't download package libc-bin
I: Retrieving libc6
I: Validating libc6
W: http://www.emdebian.org/grip/pool/main/e/eglibc/libc6_2.11.2-10em1_armel.deb was corrupt
W: Couldn't download package libc6
I: Retrieving libcap2
I: Validating libcap2
W: http://www.emdebian.org/grip/pool/main/libc/libcap2/libcap2_2.19-3em1_armel.deb was corrupt
W: Couldn't download package libcap2
I: Retrieving libcomerr2
I: Validating libcomerr2
W: http://www.emdebian.org/grip/pool/main/e/e2fsprogs/libcomerr2_1.41.12-2em1_armel.deb was corrupt
W: Couldn't download package libcomerr2
I: Retrieving libdb4.8
I: Validating libdb4.8
W: http://www.emdebian.org/grip/pool/main/d/db4.8/libdb4.8_4.8.30-2em1_armel.deb was corrupt
W: Couldn't download package libdb4.8
I: Retrieving libdevmapper1.02.1
I: Validating libdevmapper1.02.1
W: http://www.emdebian.org/grip/pool/main/l/lvm2/libdevmapper1.02.1_1.02.48-5em1_armel.deb was corrupt
W: Couldn't download package libdevmapper1.02.1
I: Retrieving libedit2
I: Validating libedit2
W: http://www.emdebian.org/grip/pool/main/libe/libedit/libedit2_2.11-20080614-2em1_armel.deb was corrupt
W: Couldn't download package libedit2
I: Retrieving libgcc1
I: Validating libgcc1
W: http://www.emdebian.org/grip/pool/main/g/gcc-4.4/libgcc1_4.4.5-8em1_armel.deb was corrupt
W: Couldn't download package libgcc1
I: Retrieving libgssapi-krb5-2
I: Validating libgssapi-krb5-2
W: http://www.emdebian.org/grip/pool/main/k/krb5/libgssapi-krb5-2_1.8.3+dfsg-4em1_armel.deb was corrupt
W: Couldn't download package libgssapi-krb5-2
I: Retrieving libk5crypto3
I: Validating libk5crypto3
W: http://www.emdebian.org/grip/pool/main/k/krb5/libk5crypto3_1.8.3+dfsg-4em1_armel.deb was corrupt
W: Couldn't download package libk5crypto3
I: Retrieving libkeyutils1
I: Validating libkeyutils1
W: http://www.emdebian.org/grip/pool/main/k/keyutils/libkeyutils1_1.4-1em1_armel.deb was corrupt
W: Couldn't download package libkeyutils1
I: Retrieving libklibc
I: Validating libklibc
W: http://www.emdebian.org/grip/pool/main/k/klibc/libklibc_1.5.20-1em1_armel.deb was corrupt
W: Couldn't download package libklibc
I: Retrieving libkrb5-3
I: Validating libkrb5-3
W: http://www.emdebian.org/grip/pool/main/k/krb5/libkrb5-3_1.8.3+dfsg-4em1_armel.deb was corrupt
W: Couldn't download package libkrb5-3
I: Retrieving libkrb5support0
I: Validating libkrb5support0
W: http://www.emdebian.org/grip/pool/main/k/krb5/libkrb5support0_1.8.3+dfsg-4em1_armel.deb was corrupt
W: Couldn't download package libkrb5support0
I: Retrieving liblocale-gettext-perl
I: Validating liblocale-gettext-perl
W: http://www.emdebian.org/grip/pool/main/libl/liblocale-gettext-perl/liblocale-gettext-perl_1.05-6em1_armel.deb was corrupt
W: Couldn't download package liblocale-gettext-perl
I: Retrieving liblzma2
I: Validating liblzma2
W: http://www.emdebian.org/grip/pool/main/x/xz-utils/liblzma2_5.0.0-2em1_armel.deb was corrupt
W: Couldn't download package liblzma2
I: Retrieving liblzo2-2
I: Validating liblzo2-2
W: http://www.emdebian.org/grip/pool/main/l/lzo2/liblzo2-2_2.03-2em1_armel.deb was corrupt
W: Couldn't download package liblzo2-2
I: Retrieving libncurses5
I: Validating libncurses5
W: http://www.emdebian.org/grip/pool/main/n/ncurses/libncurses5_5.7+20100313-5em1_armel.deb was corrupt
W: Couldn't download package libncurses5
I: Retrieving libncursesw5
I: Validating libncursesw5
W: http://www.emdebian.org/grip/pool/main/n/ncurses/libncursesw5_5.7+20100313-5em1_armel.deb was corrupt
W: Couldn't download package libncursesw5
I: Retrieving libpam-modules
I: Validating libpam-modules
W: http://www.emdebian.org/grip/pool/main/p/pam/libpam-modules_1.1.1-6.1em1_armel.deb was corrupt
W: Couldn't download package libpam-modules
I: Retrieving libpam-runtime
I: Validating libpam-runtime
W: http://www.emdebian.org/grip/pool/main/p/pam/libpam-runtime_1.1.1-6.1em1_all.deb was corrupt
W: Couldn't download package libpam-runtime
I: Retrieving libpam0g
I: Validating libpam0g
W: http://www.emdebian.org/grip/pool/main/p/pam/libpam0g_1.1.1-6.1em1_armel.deb was corrupt
W: Couldn't download package libpam0g
I: Retrieving libreadline6
I: Validating libreadline6
W: http://www.emdebian.org/grip/pool/main/r/readline6/libreadline6_6.1-3em1_armel.deb was corrupt
W: Couldn't download package libreadline6
I: Retrieving libselinux1
I: Validating libselinux1
W: http://www.emdebian.org/grip/pool/main/libs/libselinux/libselinux1_2.0.96-1em1_armel.deb was corrupt
W: Couldn't download package libselinux1
I: Retrieving libsepol1
I: Validating libsepol1
W: http://www.emdebian.org/grip/pool/main/libs/libsepol/libsepol1_2.0.41-1em1_armel.deb was corrupt
W: Couldn't download package libsepol1
I: Retrieving libslang2
I: Validating libslang2
W: http://www.emdebian.org/grip/pool/main/s/slang2/libslang2_2.2.2-4em1_armel.deb was corrupt
W: Couldn't download package libslang2
I: Retrieving libss2
I: Validating libss2
W: http://www.emdebian.org/grip/pool/main/e/e2fsprogs/libss2_1.41.12-2em1_armel.deb was corrupt
W: Couldn't download package libss2
I: Retrieving libssl0.9.8
I: Validating libssl0.9.8
W: http://www.emdebian.org/grip/pool/main/o/openssl/libssl0.9.8_0.9.8o-4em1_armel.deb was corrupt
W: Couldn't download package libssl0.9.8
I: Retrieving libstdc++6
I: Validating libstdc++6
W: http://www.emdebian.org/grip/pool/main/g/gcc-4.4/libstdc++6_4.4.5-8em1_armel.deb was corrupt
W: Couldn't download package libstdc++6
I: Retrieving libtext-charwidth-perl
I: Validating libtext-charwidth-perl
W: http://www.emdebian.org/grip/pool/main/libt/libtext-charwidth-perl/libtext-charwidth-perl_0.04-6em1_armel.deb was corrupt
W: Couldn't download package libtext-charwidth-perl
I: Retrieving libtext-iconv-perl
I: Validating libtext-iconv-perl
W: http://www.emdebian.org/grip/pool/main/libt/libtext-iconv-perl/libtext-iconv-perl_1.7-2em1_armel.deb was corrupt
W: Couldn't download package libtext-iconv-perl
I: Retrieving libtext-wrapi18n-perl
I: Validating libtext-wrapi18n-perl
W: http://www.emdebian.org/grip/pool/main/libt/libtext-wrapi18n-perl/libtext-wrapi18n-perl_0.06-7em1_all.deb was corrupt
W: Couldn't download package libtext-wrapi18n-perl
I: Retrieving libudev0
I: Validating libudev0
W: http://www.emdebian.org/grip/pool/main/u/udev/libudev0_164-3em1_armel.deb was corrupt
W: Couldn't download package libudev0
I: Retrieving libusb-0.1-4
I: Validating libusb-0.1-4
W: http://www.emdebian.org/grip/pool/main/libu/libusb/libusb-0.1-4_0.1.12-16em1_armel.deb was corrupt
W: Couldn't download package libusb-0.1-4
I: Retrieving libuuid-perl
I: Validating libuuid-perl
W: http://www.emdebian.org/grip/pool/main/libu/libuuid-perl/libuuid-perl_0.02-4em1_armel.deb was corrupt
W: Couldn't download package libuuid-perl
I: Retrieving libuuid1
I: Validating libuuid1
W: http://www.emdebian.org/grip/pool/main/u/util-linux/libuuid1_2.17.2-9em1_armel.deb was corrupt
W: Couldn't download package libuuid1
I: Retrieving libwrap0
I: Validating libwrap0
W: http://www.emdebian.org/grip/pool/main/t/tcp-wrappers/libwrap0_7.6.q-19em1_armel.deb was corrupt
W: Couldn't download package libwrap0
I: Retrieving linux-base
I: Validating linux-base
W: http://www.emdebian.org/grip/pool/main/l/linux-2.6/linux-base_2.6.32-30em1_all.deb was corrupt
W: Couldn't download package linux-base
I: Retrieving linux-image-2.6-kirkwood
I: Validating linux-image-2.6-kirkwood
W: http://www.emdebian.org/grip/pool/main/l/linux-latest-2.6/linux-image-2.6-kirkwood_2.6.32+29em1_armel.deb was corrupt
W: Couldn't download package linux-image-2.6-kirkwood
I: Retrieving linux-image-2.6.32-5-kirkwood
I: Validating linux-image-2.6.32-5-kirkwood
W: http://www.emdebian.org/grip/pool/main/l/linux-2.6/linux-image-2.6.32-5-kirkwood_2.6.32-27em1_armel.deb was corrupt
W: Couldn't download package linux-image-2.6.32-5-kirkwood
I: Retrieving login
I: Validating login
W: http://www.emdebian.org/grip/pool/main/s/shadow/login_4.1.4.2+svn3283-2em1_armel.deb was corrupt
W: Couldn't download package login
I: Retrieving lsb-base
I: Validating lsb-base
W: http://www.emdebian.org/grip/pool/main/l/lsb/lsb-base_3.2-23.1em1_all.deb was corrupt
W: Couldn't download package lsb-base
I: Retrieving mawk
I: Validating mawk
W: http://www.emdebian.org/grip/pool/main/m/mawk/mawk_1.3.3-15em1_armel.deb was corrupt
W: Couldn't download package mawk
I: Retrieving module-init-tools
I: Validating module-init-tools
W: http://www.emdebian.org/grip/pool/main/m/module-init-tools/module-init-tools_3.12-1em1_armel.deb was corrupt
W: Couldn't download package module-init-tools
I: Retrieving mount
I: Validating mount
W: http://www.emdebian.org/grip/pool/main/u/util-linux/mount_2.17.2-9em1_armel.deb was corrupt
W: Couldn't download package mount
I: Retrieving mtd-utils
I: Validating mtd-utils
W: http://www.emdebian.org/grip/pool/main/m/mtd-utils/mtd-utils_20090606-1em1_armel.deb was corrupt
W: Couldn't download package mtd-utils
I: Retrieving ncurses-base
I: Validating ncurses-base
W: http://www.emdebian.org/grip/pool/main/n/ncurses/ncurses-base_5.7+20100313-5em1_all.deb was corrupt
W: Couldn't download package ncurses-base
I: Retrieving ncurses-bin
I: Validating ncurses-bin
W: http://www.emdebian.org/grip/pool/main/n/ncurses/ncurses-bin_5.7+20100313-5em1_armel.deb was corrupt
W: Couldn't download package ncurses-bin
I: Retrieving net-tools
I: Validating net-tools
W: http://www.emdebian.org/grip/pool/main/n/net-tools/net-tools_1.60-23em1_armel.deb was corrupt
W: Couldn't download package net-tools
I: Retrieving netbase
I: Validating netbase
W: http://www.emdebian.org/grip/pool/main/n/netbase/netbase_4.45em1_all.deb was corrupt
W: Couldn't download package netbase
I: Retrieving ntpdate
I: Validating ntpdate
W: http://www.emdebian.org/grip/pool/main/n/ntp/ntpdate_4.2.6.p2+dfsg-1+b1em1_armel.deb was corrupt
W: Couldn't download package ntpdate
I: Retrieving openssh-blacklist
I: Validating openssh-blacklist
W: http://www.emdebian.org/grip/pool/main/o/openssh-blacklist/openssh-blacklist_0.4.1em1_all.deb was corrupt
W: Couldn't download package openssh-blacklist
I: Retrieving openssh-client
I: Validating openssh-client
W: http://www.emdebian.org/grip/pool/main/o/openssh/openssh-client_5.5p1-6em1_armel.deb was corrupt
W: Couldn't download package openssh-client
I: Retrieving openssh-server
I: Validating openssh-server
W: http://www.emdebian.org/grip/pool/main/o/openssh/openssh-server_5.5p1-6em1_armel.deb was corrupt
W: Couldn't download package openssh-server
I: Retrieving passwd
I: Validating passwd
W: http://www.emdebian.org/grip/pool/main/s/shadow/passwd_4.1.4.2+svn3283-2em1_armel.deb was corrupt
W: Couldn't download package passwd
I: Retrieving perl-base
I: Validating perl-base
W: http://www.emdebian.org/grip/pool/main/p/perl/perl-base_5.10.1-17em1_armel.deb was corrupt
W: Couldn't download package perl-base
I: Retrieving procps
I: Validating procps
W: http://www.emdebian.org/grip/pool/main/p/procps/procps_3.2.8-9em1_armel.deb was corrupt
W: Couldn't download package procps
I: Retrieving readline-common
I: Validating readline-common
W: http://www.emdebian.org/grip/pool/main/r/readline6/readline-common_6.1-3em1_all.deb was corrupt
W: Couldn't download package readline-common
I: Retrieving sed
I: Validating sed
W: http://www.emdebian.org/grip/pool/main/s/sed/sed_4.2.1-7em1_armel.deb was corrupt
W: Couldn't download package sed
I: Retrieving sensible-utils
I: Validating sensible-utils
W: http://www.emdebian.org/grip/pool/main/s/sensible-utils/sensible-utils_0.0.4em1_all.deb was corrupt
W: Couldn't download package sensible-utils
I: Retrieving sysv-rc
I: Validating sysv-rc
W: http://www.emdebian.org/grip/pool/main/s/sysvinit/sysv-rc_2.88dsf-13.1em1_all.deb was corrupt
W: Couldn't download package sysv-rc
I: Retrieving sysvinit
I: Validating sysvinit
W: http://www.emdebian.org/grip/pool/main/s/sysvinit/sysvinit_2.88dsf-13.1em1_armel.deb was corrupt
W: Couldn't download package sysvinit
I: Retrieving sysvinit-utils
I: Validating sysvinit-utils
W: http://www.emdebian.org/grip/pool/main/s/sysvinit/sysvinit-utils_2.88dsf-13.1em1_armel.deb was corrupt
W: Couldn't download package sysvinit-utils
I: Retrieving tar
I: Validating tar
W: http://www.emdebian.org/grip/pool/main/t/tar/tar_1.23-3em1_armel.deb was corrupt
W: Couldn't download package tar
I: Retrieving tzdata
I: Validating tzdata
W: http://www.emdebian.org/grip/pool/main/t/tzdata/tzdata_2010o-1em1_all.deb was corrupt
W: Couldn't download package tzdata
I: Retrieving udev
I: Validating udev
W: http://www.emdebian.org/grip/pool/main/u/udev/udev_164-3em1_armel.deb was corrupt
W: Couldn't download package udev
I: Retrieving util-linux
I: Validating util-linux
W: http://www.emdebian.org/grip/pool/main/u/util-linux/util-linux_2.17.2-9em1_armel.deb was corrupt
W: Couldn't download package util-linux
I: Retrieving vim-common
I: Validating vim-common
W: http://www.emdebian.org/grip/pool/main/v/vim/vim-common_7.2.445+hg~cb94c42c0e1a-1em1_armel.deb was corrupt
W: Couldn't download package vim-common
I: Retrieving vim-tiny
I: Validating vim-tiny
W: http://www.emdebian.org/grip/pool/main/v/vim/vim-tiny_7.2.445+hg~cb94c42c0e1a-1em1_armel.deb was corrupt
W: Couldn't download package vim-tiny
I: Retrieving wget
I: Validating wget
W: http://www.emdebian.org/grip/pool/main/w/wget/wget_1.12-2.1em1_armel.deb was corrupt
W: Couldn't download package wget
I: Retrieving xz-utils
I: Validating xz-utils
W: http://www.emdebian.org/grip/pool/main/x/xz-utils/xz-utils_5.0.0-2em1_armel.deb was corrupt
W: Couldn't download package xz-utils
I: Retrieving zlib1g
I: Validating zlib1g
W: http://www.emdebian.org/grip/pool/main/z/zlib/zlib1g_1.2.3.4.dfsg-3em1_armel.deb was corrupt
W: Couldn't download package zlib1g
I: Chosen extractor for .deb packages: ar
W: Failure trying to run: chroot /tmp/debian mount -t proc proc /proc
debootstrap failed.
See /tmp/debian/debootstrap/debootstrap.log for more information.
Pogoplug:/tmp$
Yuriy
Re: Howto: Install readonly emdebian on NAND
April 05, 2011 11:41AM
The problem I found is in checksum. Debootstrap verifies some packages against SHA256 and others against MD5, perhaps that configured in pckgdetailes coming from Jeff's page. Anyway, I modified checksum verification function in /usr/share/debootstrap/functions and everything worked beautifully. Here is modified version of the function:

verify_checksum () {
# args: dest checksum size
local expchecksum="$2"
local expsize="$3"
relchecksum=`sha${SHA_SIZE}sum < "$1" | sed 's/ .*$//'`
relsize=`wc -c < "$1"`
if [ "$expsize" -ne "$relsize" ] || [ "$expchecksum" != "$relchecksum" ]; then
relchecksum=`md5sum < "$1" | sed 's/ .*$//'`
if [ "$expsize" -ne "$relsize" ] || [ "$expchecksum" != "$relchecksum" ]; then
return 1
fi
fi
return 0
}


P.S. Make sure you have sha256sum and md5sum in /usr/bin
ldpinney
Re: Howto: Install readonly emdebian on NAND
May 05, 2011 07:41AM
dockstar.emdebian-squeeze-readonly.sh seems to need editing :
URL_DEBOOTSTRAP="$DEB_MIRROR/pool/main/d/debootstrap/debootstrap_1.0.30_all.deb"
as the older debootstrap is no longer available
Re: Howto: Install readonly emdebian on NAND
June 14, 2011 08:41PM
Just a little heads up for those of you wanting to use a custom kernel + emdebian in NAND with ubifs:

Don't check the kernel config option for NAND page write verification!
It will render the ubifs unusable due to it being unable to write anything. Just found that issue and wanted to let you know. Don't know yet if it's a bug or lack of knowledge on my part. Both scenarios seem plausible.

Edit:
OK, really seems to be a bug. This guy also had the same problem with YAFFS2:
http://drdobbs.com/article/print?articleId=226400083&siteSectionName=

And here another PDF as proof:
http://elinux.org/images/f/f8/CELFJamboree30-UBIFS_update.pdf



Edited 3 time(s). Last edit at 06/28/2011 07:07AM by ingmar_k.
Ivan
Re: Howto: Install readonly emdebian on NAND
October 11, 2011 02:04PM
Hi,
I would like to install (em)debian or archlinux on my nand's pogoplug...
anybody success to that?

thank you!
Re: Howto: Install readonly emdebian on NAND
October 27, 2011 03:02PM
I ran this script on my pogo..(e02)
http://dev.shyd.de/dockstar/dockstar.debian-squeeze.sh

Now emdebian runs on my pogo with USB root filesystem, great!

But I would like to install it permenantly on nand;

The problem is that emdebian on the USB drive is 232M big and only 82M is available on mtd3 (ubifs)...

How did you deal with that?

Thks



Edited 1 time(s). Last edit at 10/27/2011 03:05PM by ivan.
Re: Howto: Install readonly emdebian on NAND
November 02, 2011 05:23PM
@ivan:

1.) Ubifs uses compression if not explicitly specified otherwise. --> That 232M filesystem won't use 232M on ubifs.
2.) If there really that little flash space, or is it just partitioned strange? I mean the Dockstar has 256MB of NAND flash and one can use more than 200M for the root file system. Don't know about the pogo, though.
Re: Howto: Install readonly emdebian on NAND
November 20, 2011 03:40PM
I successfully installed debian on the nand memory and it booted. Now I'm asking myself how it is possible to install further packages e.g. encfs and nfs? I just tried to install them with apt-get but I'll get an error saying:

$ W: Not using locking for read only lock file /var/lib/dpkg/lock
$ E: Unable to write to /var/cache/apt/                                                                                                                                                                                        
$ E: The package lists or status file could not be parsed or opened.

Any suggestions?



Edited 1 time(s). Last edit at 11/20/2011 03:41PM by La_Tristesse.
Re: Howto: Install readonly emdebian on NAND
December 16, 2011 01:16PM
Do you guys think this script could be adopted to be use in a Netgear Stora?
Re: Howto: Install readonly emdebian on NAND
February 18, 2012 07:11PM
Installing emdebian right now... for it to work for me, two changes had to be made... as Yuriy says,

verify_checksum () {
# args: dest checksum size
local expchecksum="$2"
local expsize="$3"
relchecksum=`sha${SHA_SIZE}sum < "$1" | sed 's/ .*$//'`
relsize=`wc -c < "$1"`
if [ "$expsize" -ne "$relsize" ] || [ "$expchecksum" != "$relchecksum" ]; then
relchecksum=`md5sum < "$1" | sed 's/ .*$//'`
if [ "$expsize" -ne "$relsize" ] || [ "$expchecksum" != "$relchecksum" ]; then
return 1
fi
fi
return 0
}


And also in Jeff's script, change the debootstrap.deb to #30.
debootstrap_1.0.38_all.deb

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


Pallando
Re: Howto: Install readonly emdebian on NAND
April 13, 2012 06:20AM
Hi,

I've installed emdebian on mtd3, but I can't access my dockstar anymore...
I mixed Jeff's script for emdebian and shyd's script for debootstrap and easily obtained a bootable read-only usb with emdebian.
Afterwards, I installed several packages (lighttpd, samba (even though it doesn't work on a read-only partition), ...), changed the kernel (shyd's 3.1) and then copied the system on mtd3 to see if it fits...
There was 50 MB remaining, I thought it was good.

Then I typed :
fw_setenv usb_custom_params 'init=/sbin/init-ro'
... and rebooted.

My dockstar does boot. The light is solid green. I just can't connect to it.
So I tried with a "rescueme" file on a usb drive. The LED keeps blinking...

I don't have a CA-42 cable. I tried with a DCU-60, but it didn't work...
Eventually, I used my working dockstar to connect to the bricked one:
  • I commented out the "getty /dev/ttyS0" line in the inittab of my working debian
  • I connected GND to GND, TX to RX and RX to TX
  • I sshed to my working dockstar, used "screen /dev/ttyS0 115200" and booted the bricked one...
... and it worked !
Kinda...

I can see the messages from the bricked dockstar. Apparently, it cannot start the network because it needs write permissions... And when I use a USB dongle with a "rescueme" file, it hangs at:
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
 Scanning JFFS2 FS: ........ done.
 ### JFFS2 load complete: 524288 bytes loaded to 0x800000
 ## Starting application at 0x00800200 ...

The problem is that I can't write. I tried hitting a key at uboot. I tried with the "stuff" command.
Nothing happened. I'm stuck. I can see the login prompt, but I can't login.
What could I do ? Should I really go with a CA-42 ? Or am I close... ?
pallando
Re: Howto: Install readonly emdebian on NAND
April 13, 2012 11:44AM
Nevermind... It was a contact problem with the cable...

I managed to gain access to my dockstar and used what Sven posted to change some vars...
Essentially, I just needed :
setenv ubifs_custom_params 'init=/sbin/init-ro'

(In fact, I had "ubifs_" and "usb_" confused... -_-' )
Re: Howto: Install readonly emdebian on NAND
May 09, 2012 10:24PM
I installed emDebian on my dockstar a few years back but haven't touch it since and now I am lost and don't remember what I did. I took at look at dockstar.emdebian-squeeze-readonly.sh and it seems to be newer than what I used before (copyrighted 2012). My questions are is my version older, how do I upgrade, and can I run asterisk without an USB drive?

My current setup:
OS: Linux debian 2.6.32-dockstar #2 Mon Sep 6 15:43:50 EDT 2010 armv5tel (root/dadname+phonenumber)
Boot: U-Boot 2010.06-00695-gbd23130-dirty (Aug 30 2010 - 23:04:56) Marvell-Dockstar/Pogoplug by Jeff Doozan
root@debian:/tmp# cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00400000 00020000 "uImage"
mtd2: 02000000 00020000 "rootfs"
mtd3: 0db00000 00020000 "data"

Is this the correct procedure for upgrade? and what version should I upgrade to?
1) create a backup
a) plug in an USB drive
b) cd /tmp
c) mkdir usb
d) mount /dev/sda1 /tmp/usb
e) cd /tmp/usb
f) dd if=/dev/mtd0 of=mtd0.img
g) dd if=/dev/mtd1 of=mtd1.img
h) dd if=/dev/mtd2 of=mtd2.img
Are the backup commands correct? If I do screw up, do I recover by using the command dd if=mtd0.img of=/dev/mtd0 and etc?
2) make / rw
a) mount
I think my / might already be rw, output I get are "rootfs on / type rootfs (rw) ... ubi0:rootfs on / type ubifs (ro,noatime)", not sure.
3) Update sources.list to squeeze
a) cat /etc/apt/sources.list
The output I am got is "deb http://www.emdebian.org/grip squeeze main", means it already points to squeeze, should I upgrade to wheezy?
4) update
a) apt-get update
b) apt-get dist-upgrade
5) find out what version got installed
a) uname -a
6) make image
a) apt-get install uboot-mkimage
b) mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-<version> -d /boot/vmlinuz-<version> /boot/uImage
c) mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n Initrd-<version> -d /boot/initrd.img-<version> /boot/uInitrd
What is dpkg? What do I do with the image after I make them? Do I reboot now? How do I recover if reboot failed?
7) Install asterisk and check to see if sshd is running

I know this is a lot of questions but it's been a long time and I just don't know what to do. Thanks
Re: Howto: Install readonly emdebian on NAND
May 11, 2012 05:05PM
No one offer any comments or help?

For step 1, creating a backup, dd gives me bunch of errors. So I end up using nanddump instead. No error were generated. Now I just need to figure out how to recover from a backup.

My NAND is configured as such
root@debian:/tmp# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "u-boot"
mtd1: 00400000 00020000 "uImage"
mtd2: 02000000 00020000 "rootfs"
mtd3: 0db00000 00020000 "data"

[   22.506850] Creating 4 MTD partitions on "orion_nand":
[   22.512031] 0x000000000000-0x000000100000 : "u-boot"
[   22.517582] 0x000000100000-0x000000500000 : "uImage"
[   22.523053] 0x000000500000-0x000002500000 : "rootfs"
[   22.528533] 0x000002500000-0x000010000000 : "data"


//Backup Command from emDebian
//Based on http://projects.doozan.com/uboot/build_uboot.htm

nanddump -nof mtd0.nanddump /dev/mtd0
//Block size 131072, page size 2048, OOB size 64
//Dumping data starting at 0x00000000 and ending at 0x00100000...
//-rwxr-xr-x 1 root root 1048576 May 11 20:41 mtd0.nanddump

nanddump -nf mtd0.nanddump.oob /dev/mtd0
//Block size 131072, page size 2048, OOB size 64
//Dumping data starting at 0x00000000 and ending at 0x00100000...
//-rwxr-xr-x 1 root root 1081344 May 11 20:44 mtd0.nanddump.oob

nanddump -nof mtd0_0_0x100000.nanddump -s 0 -l 0x100000 /dev/mtd0
//Block size 131072, page size 2048, OOB size 64
//Dumping data starting at 0x00000000 and ending at 0x00100000...
//-rwxr-xr-x 1 root root 1048576 May 11 20:45 mtd0_0_0x100000.nanddump

//diff mtd0.nanddump mtd0_0_0x100000.nanddump did not output any difference

nanddump -nof mtd1.nanddump /dev/mtd1
//Block size 131072, page size 2048, OOB size 64
//Dumping data starting at 0x00000000 and ending at 0x00400000...
//-rwxr-xr-x 1 root root 4194304 May 11 20:48 mtd1.nanddump

nanddump -nf mtd1.nanddump.oob /dev/mtd1
//Block size 131072, page size 2048, OOB size 64
//Dumping data starting at 0x00000000 and ending at 0x00400000...
//-rwxr-xr-x 1 root root 4325376 May 11 20:48 mtd1.nanddump.oob

nanddump -nof mtd1_0x100000_0x400000.nanddump -s 0x100000 -l 0x400000 /dev/mtd1
//Block size 131072, page size 2048, OOB size 64
//Dumping data starting at 0x00100000 and ending at 0x00400000...
//-rwxr-xr-x 1 root root  3145728 May 11 20:52 mtd1_0x100000_0x400000.nanddump

nanddump -nof mtd2.nanddump /dev/mtd2
//Block size 131072, page size 2048, OOB size 64
//Dumping data starting at 0x00000000 and ending at 0x02000000...
//-rwxr-xr-x 1 root root 33554432 May 11 20:50 mtd2.nanddump

nanddump -nf mtd2.nanddump.oob /dev/mtd2
//Block size 131072, page size 2048, OOB size 64
//Dumping data starting at 0x00000000 and ending at 0x02000000...
//-rwxr-xr-x 1 root root 34603008 May 11 20:51 mtd2.nanddump.oob

nanddump -nof mtd2_0x500000_0x2000000.nanddump -s 0x500000 -l 0x2000000 /dev/mtd2
//Block size 131072, page size 2048, OOB size 64
//Dumping data starting at 0x00500000 and ending at 0x02000000...
//-rwxr-xr-x 1 root root 28311552 May 11 20:54 mtd2_0x500000_0x2000000.nanddump

nanddump -nof mtd3.nanddump /dev/mtd3
//Block size 131072, page size 2048, OOB size 64
//Dumping data starting at 0x00000000 and ending at 0x0db00000...
//-rwxr-xr-x 1 root root 229638144 May 11 20:56 mtd3.nanddump

nanddump -nf mtd3.nanddump.oob /dev/mtd3
//Block size 131072, page size 2048, OOB size 64
//Dumping data starting at 0x00000000 and ending at 0x0db00000...
//-rwxr-xr-x 1 root root 236814336 May 11 20:57 mtd3.nanddump.oob

nanddump -nof mtd3_0_0x100000.nanddump -s 0x2500000 -l 0xdb00000 /dev/mtd3
//Block size 131072, page size 2048, OOB size 64
//Dumping data starting at 0x02500000 and ending at 0x0db00000...
//-rwxr-xr-x 1 root root 190840832 May 11 20:58 mtd3_0_0x100000.nanddump


George White
Re: Howto: Install readonly emdebian on NAND
December 11, 2012 08:04PM
Thanks a lot for the great work.

I'm wondering if there is a way to install read-only debian on USB stick instead of NAND? (the reason is that, by doing so, if something goes wrong, I can always boot back to the original NAND)

Thanks a lot in advance!
George
Re: Howto: Install readonly emdebian on NAND
December 12, 2012 12:15PM
Hi.
since about a year, I am using three dockstars with debian and the dockstars work incredible solid.

Now i bought two pogoplugs (P24/V3) for only 25 € (both) and i want them to replace the dockstars, because there is more memory inside.

First i discovered the arch linux project for the pogoplug, but i also read a lot of trouble and problems. I know about the quality of jeff's debian installation, so i want to install and use debian on the pogoplug, too.

Question: Does it make sense to install the debian in the NAND? I will always use a debian with the pogoplug, so why not the NAND? Are there any disadvantage?

What i want to do with the pogoplug: I want to install a VDR (videodisk recorder), the logitech mediaserver (squeezebox) and a VPN.

Regards,
moddy
Re: Howto: Install readonly emdebian on NAND
December 12, 2012 04:14PM
The Pogo V3 is OXNAS. Currently the only working kernel installation is the Arch Linux ARM (ALARM). Arch kernel is installed in NAND, and Arch rootfs can be either on USB or SATA drive.

We did successfully install Debian rootfs on external drive, and run it with Arch kernel:
http://forum.doozan.com/read.php?3,6336

Since it is OXNAS, Jeff's installation can't be used (it's for Kirkwood). Hopefully in the future, somebody will make a go at flashing Debian kernel on NAND. That will make upgrading much easier.
nivekmai
Re: Howto: Install readonly emdebian on NAND
March 26, 2013 05:40PM
Is it safe to do this process but use the wheezy script from http://projects.doozan.com/debian/kirkwood.debian-wheezy.sh?
Re: Howto: Install readonly emdebian on NAND
March 28, 2013 08:54AM
With debian you will get a much bigger image, which probably won't fit into NAND.
And emdebian only builds reliably with squeeze/stable ATM.
WhiteFang
Re: Howto: Install readonly emdebian on NAND
August 11, 2013 12:36PM
Any chance to install it on a PP Mobile?
Jeff LaCoursiere
Re: Howto: Install readonly emdebian on NAND
August 19, 2013 10:23AM
Amazed to find that this *still* works with no modifications. I had a handful of these on a shelf and a need for a quickie OpenVPN client router. Had to remount rw and add an apt-source to get openvpn and iptables, but both fit with no problem. Thanks a ton!
Re: Howto: Install readonly emdebian on NAND
December 15, 2013 03:13PM
Can this be done on a zyxel nsa325? would be fun to make a makeshift alt firmware so to speak with basic raid1 or raid5 support and a small gui of such.

~SOL
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: