Yet Another cannot boot thread
Posted by dinjo
|
Yet Another cannot boot thread October 23, 2013 12:38AM |
Registered: 11 years ago Posts: 93 |
I ran the squeeze script(dockstar.debian-squeeze.sh) and everything went fine except that it was not able to get correct URL_BOOTSTRAP as it was failing so i had to change to use the July 2013 version and then i booted the device now no ssh , no ip is showing up.Blinking green and then blinking amber
Edited 1 time(s). Last edit at 10/23/2013 12:49AM by dinjo.
-bash-3.2# ./dockstar.debian-squeeze.sh !!!!!! DANGER DANGER DANGER DANGER DANGER DANGER !!!!!! This script will replace the bootloader on /dev/mtd0. If you lose power while the bootloader is being flashed, your device could be left in an unusable state. This script will configure your Dockstar to boot Debian Squeeze from a USB device. Before running this script, you should have used fdisk to create the following partitions: /dev/sda1 (Linux ext2, at least 400MB) /dev/sda2 (Linux swap, recommended 256MB) This script will DESTROY ALL EXISTING DATA on /dev/sda1 Please double check that the device on /dev/sda1 is the correct device. By typing ok, you agree to assume all liabilities and risks associated with running this installer. If everything looks good, type 'ok' to continue: ok Installing Bootloader # checking for /usr/sbin/nandwrite... # checking for /usr/sbin/nanddump... # checking for /usr/sbin/flash_erase... # checking for /usr/sbin/fw_printenv... # checking for /etc/fw_env.config... # Validating existing uBoot... Block size 131072, page size 2048, OOB size 64 Dumping data starting at 0x00000000 and ending at 0x00080000... Connecting to jeff.doozan.com (50.116.34.13:80) valid-uboot.md5 100% |********************************************************************************************************************************************************************************************| 1133 --:--:-- ETA ## Valid uBoot detected: [goflexnet davygravy-2012-04-19-current] ## The newest uBoot is already installed on mtd0. # uBoot installation has completed successfully. Setting up swapspace version 1, size = -1883246592 bytes Connecting to cdn.debian.net (128.30.2.36:80) debootstrap.deb 100% |********************************************************************************************************************************************************************************************| 60248 00:00:00 ETA rw-r--r-- 0/0 4 Jul 14 11:07 2013 debian-binary rw-r--r-- 0/0 1187 Jul 14 11:07 2013 control.tar.gz rw-r--r-- 0/0 58867 Jul 14 11:07 2013 data.tar.gz ./ ./usr/ ./usr/share/ ./usr/share/man/ ./usr/share/man/man8/ ./usr/share/man/man8/debootstrap.8.gz ./usr/share/doc/ ./usr/share/doc/debootstrap/ ./usr/share/doc/debootstrap/README ./usr/share/doc/debootstrap/copyright ./usr/share/doc/debootstrap/changelog.gz ./usr/share/debootstrap/ ./usr/share/debootstrap/devices.tar.gz ./usr/share/debootstrap/functions ./usr/share/debootstrap/scripts/ ./usr/share/debootstrap/scripts/potato ./usr/share/debootstrap/scripts/sid ./usr/share/debootstrap/scripts/breezy ./usr/share/debootstrap/scripts/hoary.buildd ./usr/share/debootstrap/scripts/woody ./usr/share/debootstrap/scripts/sarge.fakechroot ./usr/share/debootstrap/scripts/warty ./usr/share/debootstrap/scripts/warty.buildd ./usr/share/debootstrap/scripts/hoary ./usr/share/debootstrap/scripts/feisty ./usr/share/debootstrap/scripts/gutsy ./usr/share/debootstrap/scripts/sarge ./usr/share/debootstrap/scripts/sarge.buildd ./usr/share/debootstrap/scripts/edgy ./usr/share/debootstrap/scripts/woody.buildd ./usr/share/debootstrap/scripts/dapper ./usr/sbin/ ./usr/sbin/debootstrap ./usr/share/debootstrap/scripts/quantal ./usr/share/debootstrap/scripts/raring ./usr/share/debootstrap/scripts/precise ./usr/share/debootstrap/scripts/oldstable ./usr/share/debootstrap/scripts/jaunty ./usr/share/debootstrap/scripts/natty ./usr/share/debootstrap/scripts/karmic ./usr/share/debootstrap/scripts/oneiric ./usr/share/debootstrap/scripts/hardy ./usr/share/debootstrap/scripts/squeeze ./usr/share/debootstrap/scripts/intrepid ./usr/share/debootstrap/scripts/etch-m68k ./usr/share/debootstrap/scripts/etch ./usr/share/debootstrap/scripts/unstable ./usr/share/debootstrap/scripts/saucy ./usr/share/debootstrap/scripts/testing ./usr/share/debootstrap/scripts/maverick ./usr/share/debootstrap/scripts/lucid ./usr/share/debootstrap/scripts/lenny ./usr/share/debootstrap/scripts/wheezy ./usr/share/debootstrap/scripts/stable ./usr/share/debootstrap/scripts/jessie # checking for /usr/share/debootstrap/pkgdetails... # Installing /usr/share/debootstrap/pkgdetails... Connecting to download.doozan.com (50.116.34.13:80) pkgdetails.md5 100% |********************************************************************************************************************************************************************************************| 32 --:--:-- ETA Connecting to download.doozan.com (50.116.34.13:80) pkgdetails 100% |********************************************************************************************************************************************************************************************| 559k 00:00:00 ETA # Successfully installed /usr/share/debootstrap/pkgdetails. # 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: insserv libbz2-1.0 libdb4.8 libslang2 I: Found additional base dependencies: adduser cpio debian-archive-keyring devio gnupg gpgv initramfs-tools klibc-utils libbsd0 libcap2 libedit2 libgssapi-krb5-2 libk5crypto3 libkeyutils1 libklibc libkrb5-3 libkrb5support0 libncursesw5 libreadline6 libssl0.9.8 libudev0 libusb-0.1-4 libuuid-perl libwrap0 linux-base linux-image-2.6.32-5-kirkwood openssh-blacklist openssh-client procps readline-common vim-common I: Checking component main on http://cdn.debian.net/debian... I: Retrieving libacl1 2.2.49-4 I: Validating libacl1 2.2.49-4 I: Retrieving adduser 3.112+nmu2 I: Validating adduser 3.112+nmu2 I: Retrieving apt 0.8.10.3+squeeze1 I: Validating apt 0.8.10.3+squeeze1 I: Retrieving libattr1 1%3a2.4.44-2 I: Validating libattr1 1%3a2.4.44-2 I: Retrieving base-files 6.0squeeze8 I: Validating base-files 6.0squeeze8 I: Retrieving base-passwd 3.5.22 I: Validating base-passwd 3.5.22 I: Retrieving bash 4.1-3 I: Validating bash 4.1-3 I: Retrieving libbz2-1.0 1.0.5-6+squeeze1 I: Validating libbz2-1.0 1.0.5-6+squeeze1 I: Retrieving coreutils 8.5-1 I: Validating coreutils 8.5-1 I: Retrieving cpio 2.11-4 I: Validating cpio 2.11-4 I: Retrieving dash 0.5.5.1-7.4 I: Validating dash 0.5.5.1-7.4 I: Retrieving libdb4.8 4.8.30-2 I: Validating libdb4.8 4.8.30-2 I: Retrieving debconf-i18n 1.5.36.1 I: Validating debconf-i18n 1.5.36.1 I: Retrieving debconf 1.5.36.1 I: Validating debconf 1.5.36.1 I: Retrieving debian-archive-keyring 2010.08.28+squeeze1 I: Validating debian-archive-keyring 2010.08.28+squeeze1 I: Retrieving debianutils 3.4 I: Validating debianutils 3.4 I: Retrieving devio 1.2-1+b1 I: Validating devio 1.2-1+b1 I: Retrieving dhcpcd 1%3a3.2.3-5+squeeze1 I: Validating dhcpcd 1%3a3.2.3-5+squeeze1 I: Retrieving diffutils 1%3a3.0-1 I: Validating diffutils 1%3a3.0-1 I: Retrieving dpkg 1.15.8.13 I: Validating dpkg 1.15.8.13 I: Retrieving e2fslibs 1.41.12-4stable1 I: Validating e2fslibs 1.41.12-4stable1 I: Retrieving e2fsprogs 1.41.12-4stable1 I: Validating e2fsprogs 1.41.12-4stable1 I: Retrieving libcomerr2 1.41.12-4stable1 I: Validating libcomerr2 1.41.12-4stable1 I: Retrieving libss2 1.41.12-4stable1 I: Validating libss2 1.41.12-4stable1 I: Retrieving libc-bin 2.11.3-4 I: Validating libc-bin 2.11.3-4 I: Retrieving libc6 2.11.3-4 I: Validating libc6 2.11.3-4 I: Retrieving findutils 4.4.2-1+b1 I: Validating findutils 4.4.2-1+b1 I: Retrieving flash-kernel 2.37 I: Validating flash-kernel 2.37 I: Retrieving gcc-4.4-base 4.4.5-8 I: Validating gcc-4.4-base 4.4.5-8 I: Retrieving libgcc1 1%3a4.4.5-8 I: Validating libgcc1 1%3a4.4.5-8 I: Retrieving libstdc++6 4.4.5-8 I: Validating libstdc++6 4.4.5-8 I: Retrieving gnupg 1.4.10-4+squeeze3 I: Validating gnupg 1.4.10-4+squeeze3 I: Retrieving gpgv 1.4.10-4+squeeze3 I: Validating gpgv 1.4.10-4+squeeze3 I: Retrieving grep 2.6.3-3+squeeze1 I: Validating grep 2.6.3-3+squeeze1 I: Retrieving gzip 1.3.12-9+squeeze1 I: Validating gzip 1.3.12-9+squeeze1 I: Retrieving hostname 3.04 I: Validating hostname 3.04 I: Retrieving ifupdown 0.6.10 I: Validating ifupdown 0.6.10 I: Retrieving initramfs-tools 0.98.8 I: Validating initramfs-tools 0.98.8 I: Retrieving insserv 1.14.0-2 I: Validating insserv 1.14.0-2 I: Retrieving iproute 20100519-3 I: Validating iproute 20100519-3 I: Retrieving iputils-ping 3%3a20100418-3 I: Validating iputils-ping 3%3a20100418-3 I: Retrieving libkeyutils1 1.4-1 I: Validating libkeyutils1 1.4-1 I: Retrieving klibc-utils 1.5.20-1+squeeze1 I: Validating klibc-utils 1.5.20-1+squeeze1 I: Retrieving libklibc 1.5.20-1+squeeze1 I: Validating libklibc 1.5.20-1+squeeze1 I: Retrieving libgssapi-krb5-2 1.8.3+dfsg-4squeeze7 I: Validating libgssapi-krb5-2 1.8.3+dfsg-4squeeze7 I: Retrieving libk5crypto3 1.8.3+dfsg-4squeeze7 I: Validating libk5crypto3 1.8.3+dfsg-4squeeze7 I: Retrieving libkrb5-3 1.8.3+dfsg-4squeeze7 I: Validating libkrb5-3 1.8.3+dfsg-4squeeze7 I: Retrieving libkrb5support0 1.8.3+dfsg-4squeeze7 I: Validating libkrb5support0 1.8.3+dfsg-4squeeze7 I: Retrieving linux-base 2.6.32-48squeeze4 I: Validating linux-base 2.6.32-48squeeze4 I: Retrieving linux-image-2.6.32-5-kirkwood 2.6.32-48squeeze4 I: Validating linux-image-2.6.32-5-kirkwood 2.6.32-48squeeze4 I: Retrieving linux-image-kirkwood 2.6.32+29 I: Validating linux-image-kirkwood 2.6.32+29 I: Retrieving lsb-base 3.2-23.2squeeze1 I: Validating lsb-base 3.2-23.2squeeze1 I: Retrieving libbsd0 0.2.0-1 I: Validating libbsd0 0.2.0-1 I: Retrieving libcap2 1%3a2.19-3 I: Validating libcap2 1%3a2.19-3 I: Retrieving libedit2 2.11-20080614-2 I: Validating libedit2 2.11-20080614-2 I: Retrieving liblocale-gettext-perl 1.05-6 I: Validating liblocale-gettext-perl 1.05-6 I: Retrieving libselinux1 2.0.96-1 I: Validating libselinux1 2.0.96-1 I: Retrieving libsepol1 2.0.41-1 I: Validating libsepol1 2.0.41-1 I: Retrieving libtext-charwidth-perl 0.04-6 I: Validating libtext-charwidth-perl 0.04-6 I: Retrieving libtext-iconv-perl 1.7-2 I: Validating libtext-iconv-perl 1.7-2 I: Retrieving libtext-wrapi18n-perl 0.06-7 I: Validating libtext-wrapi18n-perl 0.06-7 I: Retrieving libusb-0.1-4 2%3a0.1.12-16 I: Validating libusb-0.1-4 2%3a0.1.12-16 I: Retrieving libuuid-perl 0.02-4 I: Validating libuuid-perl 0.02-4 I: Retrieving mawk 1.3.3-15 I: Validating mawk 1.3.3-15 I: Retrieving module-init-tools 3.12-2 I: Validating module-init-tools 3.12-2 I: Retrieving libncurses5 5.7+20100313-5 I: Validating libncurses5 5.7+20100313-5 I: Retrieving libncursesw5 5.7+20100313-5 I: Validating libncursesw5 5.7+20100313-5 I: Retrieving ncurses-base 5.7+20100313-5 I: Validating ncurses-base 5.7+20100313-5 I: Retrieving ncurses-bin 5.7+20100313-5 I: Validating ncurses-bin 5.7+20100313-5 I: Retrieving net-tools 1.60-23 I: Validating net-tools 1.60-23 I: Retrieving netbase 4.45 I: Validating netbase 4.45 I: Retrieving ntpdate 1%3a4.2.6.p2+dfsg-1+b1 I: Validating ntpdate 1%3a4.2.6.p2+dfsg-1+b1 I: Retrieving openssh-blacklist 0.4.1 I: Validating openssh-blacklist 0.4.1 I: Retrieving openssh-client 1%3a5.5p1-6+squeeze4 I: Validating openssh-client 1%3a5.5p1-6+squeeze4 I: Retrieving openssh-server 1%3a5.5p1-6+squeeze4 I: Validating openssh-server 1%3a5.5p1-6+squeeze4 I: Retrieving libssl0.9.8 0.9.8o-4squeeze14 I: Validating libssl0.9.8 0.9.8o-4squeeze14 I: Retrieving libpam-modules 1.1.1-6.1+squeeze1 I: Validating libpam-modules 1.1.1-6.1+squeeze1 I: Retrieving libpam-runtime 1.1.1-6.1+squeeze1 I: Validating libpam-runtime 1.1.1-6.1+squeeze1 I: Retrieving libpam0g 1.1.1-6.1+squeeze1 I: Validating libpam0g 1.1.1-6.1+squeeze1 I: Retrieving perl-base 5.10.1-17squeeze6 I: Validating perl-base 5.10.1-17squeeze6 I: Retrieving procps 1%3a3.2.8-9squeeze1 I: Validating procps 1%3a3.2.8-9squeeze1 I: Retrieving libreadline6 6.1-3 I: Validating libreadline6 6.1-3 I: Retrieving readline-common 6.1-3 I: Validating readline-common 6.1-3 I: Retrieving sed 4.2.1-7 I: Validating sed 4.2.1-7 I: Retrieving sensible-utils 0.0.4 I: Validating sensible-utils 0.0.4 I: Retrieving login 1%3a4.1.4.2+svn3283-2+squeeze1 I: Validating login 1%3a4.1.4.2+svn3283-2+squeeze1 I: Retrieving passwd 1%3a4.1.4.2+svn3283-2+squeeze1 I: Validating passwd 1%3a4.1.4.2+svn3283-2+squeeze1 I: Retrieving libslang2 2.2.2-4 I: Validating libslang2 2.2.2-4 I: Retrieving initscripts 2.88dsf-13.1+squeeze1 I: Validating initscripts 2.88dsf-13.1+squeeze1 I: Retrieving sysv-rc 2.88dsf-13.1+squeeze1 I: Validating sysv-rc 2.88dsf-13.1+squeeze1 I: Retrieving sysvinit-utils 2.88dsf-13.1+squeeze1 I: Validating sysvinit-utils 2.88dsf-13.1+squeeze1 I: Retrieving sysvinit 2.88dsf-13.1+squeeze1 I: Validating sysvinit 2.88dsf-13.1+squeeze1 I: Retrieving tar 1.23-3 I: Validating tar 1.23-3 I: Retrieving libwrap0 7.6.q-19 I: Validating libwrap0 7.6.q-19 I: Retrieving libudev0 164-3 I: Validating libudev0 164-3 I: Retrieving bsdutils 1%3a2.17.2-9 I: Validating bsdutils 1%3a2.17.2-9 I: Retrieving libblkid1 2.17.2-9 I: Validating libblkid1 2.17.2-9 I: Retrieving libuuid1 2.17.2-9 I: Validating libuuid1 2.17.2-9 I: Retrieving mount 2.17.2-9 I: Validating mount 2.17.2-9 I: Retrieving liblzma2 5.0.0-2 I: Validating liblzma2 5.0.0-2 I: Retrieving tzdata 2013d-0squeeze1 I: Validating tzdata 2013d-0squeeze1 I: Retrieving uboot-envtools 20081215-2 I: Validating uboot-envtools 20081215-2 I: Retrieving uboot-mkimage 0.4 I: Validating uboot-mkimage 0.4 I: Retrieving udev 164-3 I: Validating udev 164-3 I: Retrieving util-linux 2.17.2-9 I: Validating util-linux 2.17.2-9 I: Retrieving vim-common 2%3a7.2.445+hg~cb94c42c0e1a-1 I: Validating vim-common 2%3a7.2.445+hg~cb94c42c0e1a-1 I: Retrieving vim-tiny 2%3a7.2.445+hg~cb94c42c0e1a-1 I: Validating vim-tiny 2%3a7.2.445+hg~cb94c42c0e1a-1 I: Retrieving wget 1.12-2.1 I: Validating wget 1.12-2.1 I: Retrieving xz-utils 5.0.0-2 I: Validating xz-utils 5.0.0-2 I: Retrieving zlib1g 1%3a1.2.3.4.dfsg-3 I: Validating zlib1g 1%3a1.2.3.4.dfsg-3 I: Chosen extractor for .deb packages: ar I: Extracting libacl1... I: Extracting libattr1... I: Extracting base-files... I: Extracting base-passwd... I: Extracting bash... I: Extracting libbz2-1.0... I: Extracting coreutils... I: Extracting dash... I: Extracting libdb4.8... I: Extracting debconf-i18n... I: Extracting debconf... I: Extracting debianutils... I: Extracting diffutils... I: Extracting dpkg... I: Extracting e2fslibs... I: Extracting e2fsprogs... I: Extracting libcomerr2... I: Extracting libss2... I: Extracting libc-bin... I: Extracting libc6... I: Extracting findutils... I: Extracting gcc-4.4-base... I: Extracting libgcc1... I: Extracting libstdc++6... I: Extracting grep... I: Extracting gzip... I: Extracting hostname... I: Extracting insserv... I: Extracting lsb-base... I: Extracting liblocale-gettext-perl... I: Extracting libselinux1... I: Extracting libsepol1... I: Extracting libtext-charwidth-perl... I: Extracting libtext-iconv-perl... I: Extracting libtext-wrapi18n-perl... I: Extracting mawk... I: Extracting libncurses5... I: Extracting ncurses-base... I: Extracting ncurses-bin... I: Extracting libpam-modules... I: Extracting libpam-runtime... I: Extracting libpam0g... I: Extracting perl-base... I: Extracting sed... I: Extracting sensible-utils... I: Extracting login... I: Extracting passwd... I: Extracting libslang2... I: Extracting initscripts... I: Extracting sysv-rc... I: Extracting sysvinit-utils... I: Extracting sysvinit... I: Extracting tar... I: Extracting bsdutils... I: Extracting libblkid1... I: Extracting libuuid1... I: Extracting mount... I: Extracting liblzma2... I: Extracting tzdata... I: Extracting util-linux... I: Extracting xz-utils... I: Extracting zlib1g... I: Installing core packages... I: Unpacking required packages... I: Unpacking libacl1... I: Unpacking libattr1... I: Unpacking base-files... I: Unpacking base-passwd... I: Unpacking bash... I: Unpacking libbz2-1.0... I: Unpacking coreutils... I: Unpacking dash... I: Unpacking libdb4.8... I: Unpacking debconf-i18n... I: Unpacking debconf... I: Unpacking debianutils... I: Unpacking diffutils... I: Unpacking dpkg... I: Unpacking e2fslibs... I: Unpacking e2fsprogs... I: Unpacking libcomerr2... I: Unpacking libss2... I: Unpacking libc-bin... I: Unpacking libc6... I: Unpacking findutils... I: Unpacking gcc-4.4-base... I: Unpacking libgcc1... I: Unpacking libstdc++6... I: Unpacking grep... I: Unpacking gzip... I: Unpacking hostname... I: Unpacking insserv... I: Unpacking lsb-base... I: Unpacking liblocale-gettext-perl... I: Unpacking libselinux1... I: Unpacking libsepol1... I: Unpacking libtext-charwidth-perl... I: Unpacking libtext-iconv-perl... I: Unpacking libtext-wrapi18n-perl... I: Unpacking mawk... I: Unpacking libncurses5... I: Unpacking ncurses-base... I: Unpacking ncurses-bin... I: Unpacking libpam-modules... I: Unpacking libpam-runtime... I: Unpacking libpam0g... I: Unpacking perl-base... I: Unpacking sed... I: Unpacking sensible-utils... I: Unpacking login... I: Unpacking passwd... I: Unpacking libslang2... I: Unpacking initscripts... I: Unpacking sysv-rc... I: Unpacking sysvinit-utils... I: Unpacking sysvinit... I: Unpacking tar... I: Unpacking bsdutils... I: Unpacking libblkid1... I: Unpacking libuuid1... I: Unpacking mount... I: Unpacking liblzma2... I: Unpacking tzdata... I: Unpacking util-linux... I: Unpacking xz-utils... I: Unpacking zlib1g... I: Configuring required packages... I: Configuring ncurses-base... I: Configuring sensible-utils... I: Configuring libc-bin... I: Configuring gcc-4.4-base... I: Configuring libc6... I: Configuring debianutils... I: Configuring bsdutils... I: Configuring libsepol1... I: Configuring libgcc1... I: Configuring libncurses5... I: Configuring libattr1... I: Configuring e2fslibs... I: Configuring base-passwd... I: Configuring libcomerr2... I: Configuring mawk... I: Configuring libdb4.8... I: Configuring hostname... I: Configuring libacl1... I: Configuring libslang2... I: Configuring libss2... I: Configuring liblzma2... I: Configuring insserv... I: Configuring gzip... I: Configuring libbz2-1.0... I: Configuring libselinux1... I: Configuring libstdc++6... I: Configuring coreutils... I: Configuring ncurses-bin... I: Configuring diffutils... I: Configuring tar... I: Configuring zlib1g... I: Configuring base-files... I: Configuring xz-utils... I: Configuring dpkg... I: Configuring sysvinit-utils... I: Configuring dash... I: Configuring perl-base... I: Configuring libtext-iconv-perl... I: Configuring sed... I: Configuring grep... I: Configuring findutils... I: Configuring liblocale-gettext-perl... I: Configuring bash... I: Configuring libtext-charwidth-perl... I: Configuring libtext-wrapi18n-perl... I: Configuring lsb-base... I: Configuring debconf-i18n... I: Configuring debconf... I: Configuring libpam0g... I: Configuring sysv-rc... I: Configuring libpam-modules... I: Configuring tzdata... I: Configuring passwd... I: Configuring libpam-runtime... I: Configuring initscripts... I: Configuring login... I: Configuring libuuid1... I: Configuring sysvinit... I: Configuring libblkid1... I: Configuring util-linux... I: Configuring mount... I: Configuring e2fsprogs... I: Unpacking the base system... I: Unpacking adduser... I: Unpacking apt... I: Unpacking cpio... I: Unpacking debian-archive-keyring... I: Unpacking devio... I: Unpacking dhcpcd... I: Unpacking flash-kernel... I: Unpacking gnupg... I: Unpacking gpgv... I: Unpacking ifupdown... I: Unpacking initramfs-tools... I: Unpacking iproute... I: Unpacking iputils-ping... I: Unpacking libkeyutils1... I: Unpacking klibc-utils... I: Unpacking libklibc... I: Unpacking libgssapi-krb5-2... I: Unpacking libk5crypto3... I: Unpacking libkrb5-3... I: Unpacking libkrb5support0... I: Unpacking linux-base... I: Unpacking linux-image-2.6.32-5-kirkwood... I: Unpacking linux-image-kirkwood... I: Unpacking libbsd0... I: Unpacking libcap2... I: Unpacking libedit2... I: Unpacking libusb-0.1-4... I: Unpacking libuuid-perl... I: Unpacking module-init-tools... I: Unpacking libncursesw5... I: Unpacking net-tools... I: Unpacking netbase... I: Unpacking ntpdate... I: Unpacking openssh-blacklist... I: Unpacking openssh-client... I: Unpacking openssh-server... I: Unpacking libssl0.9.8... I: Unpacking procps... I: Unpacking libreadline6... I: Unpacking readline-common... I: Unpacking libwrap0... I: Unpacking libudev0... I: Unpacking uboot-envtools... I: Unpacking uboot-mkimage... I: Unpacking udev... I: Unpacking vim-common... I: Unpacking vim-tiny... I: Unpacking wget... I: Configuring the base system... I: Configuring uboot-envtools... I: Configuring module-init-tools... I: Configuring libusb-0.1-4... I: Configuring libssl0.9.8... I: Configuring vim-common... I: Configuring netbase... I: Configuring libudev0... I: Configuring adduser... I: Configuring libklibc... I: Configuring libuuid-perl... I: Configuring libkeyutils1... I: Configuring iproute... I: Configuring devio... I: Configuring klibc-utils... I: Configuring libkrb5support0... I: Configuring wget... I: Configuring net-tools... I: Configuring uboot-mkimage... I: Configuring libbsd0... I: Configuring linux-base... I: Configuring libncursesw5... I: Configuring openssh-blacklist... I: Configuring iputils-ping... I: Configuring libedit2... I: Configuring udev... I: Configuring cpio... I: Configuring vim-tiny... I: Configuring readline-common... I: Configuring libcap2... I: Configuring libwrap0... I: Configuring initramfs-tools... I: Configuring procps... I: Configuring dhcpcd... I: Configuring flash-kernel... I: Configuring libk5crypto3... I: Configuring ifupdown... I: Configuring libreadline6... I: Configuring linux-image-2.6.32-5-kirkwood... I: Configuring ntpdate... I: Configuring libkrb5-3... I: Configuring gpgv... I: Configuring libgssapi-krb5-2... I: Configuring gnupg... I: Configuring debian-archive-keyring... I: Configuring linux-image-kirkwood... I: Configuring openssh-client... I: Configuring apt... I: Configuring openssh-server... I: Configuring initramfs-tools... I: Base system installed successfully. Installation complete You can now reboot your device into Debian. If your device does not start Debian after rebooting, you may need to restart the device by disconnecting the power. The new root password is 'root' Please change it immediately after logging in. Reboot now? [Y/n] n
Edited 1 time(s). Last edit at 10/23/2013 12:49AM by dinjo.
|
Re: Yet Another cannot boot thread October 23, 2013 12:49AM |
Admin Registered: 13 years ago Posts: 18,580 |
See my response on the other thread. Now pls keep only this thread going.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Yet Another cannot boot thread October 23, 2013 01:06AM |
Registered: 11 years ago Posts: 93 |
As i mentioned here its rebooted , what options do i have i cannot setup rescue system since it can be done only after 1st boot , what options do i have, I connected the Flash drive to other pc and here is the contents of fstab
Edited 2 time(s). Last edit at 10/23/2013 01:10AM by dinjo.
# /etc/fstab: static file system information. # # <file system> <mount point> <type> <options> <dump> <pass> /dev/root / ext2 noatime,errors=remount-ro 0 1 /dev/sda2 none swap sw 0 0 tmpfs /tmp tmpfs defaults 0 0
root@debian:/media/hd-sdd1/etc# cat fw_env.config # Configuration file for fw_(printenv/saveenv) utility. # Up to two entries are valid; in this case the redundant # environment sector is assumed present. # Note that "Number of sectors" is ignored on NOR. # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x20000
Edited 2 time(s). Last edit at 10/23/2013 01:10AM by dinjo.
|
Re: Yet Another cannot boot thread October 23, 2013 02:21AM |
Admin Registered: 13 years ago Posts: 18,580 |
dinjo,
Please be more specific when you post, I did not realize that you have booted OK into Debian. Did you?
Rescue system is not really necessary if you have either serial console, or netconsole to recover from problem. So if you don't like messing up wth hardware, setup netconsole right away after you've booted successfully into Debian.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Please be more specific when you post, I did not realize that you have booted OK into Debian. Did you?
Rescue system is not really necessary if you have either serial console, or netconsole to recover from problem. So if you don't like messing up wth hardware, setup netconsole right away after you've booted successfully into Debian.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Yet Another cannot boot thread October 23, 2013 02:32AM |
Registered: 11 years ago Posts: 93 |
|
Re: Yet Another cannot boot thread October 23, 2013 02:35AM |
Admin Registered: 13 years ago Posts: 18,580 |
Have you tried booting with my rootfs?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Yet Another cannot boot thread October 23, 2013 02:43AM |
Registered: 11 years ago Posts: 93 |
|
Re: Yet Another cannot boot thread October 23, 2013 03:00AM |
Admin Registered: 13 years ago Posts: 18,580 |
dinjo,
Read the instruction! the rootfs has 3.11.1 kernel. Meaning the rootfs kernel is later than 3.9.x, 3.10.x.... :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Read the instruction! the rootfs has 3.11.1 kernel. Meaning the rootfs kernel is later than 3.9.x, 3.10.x.... :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Yet Another cannot boot thread October 23, 2013 03:38AM |
Registered: 11 years ago Posts: 93 |
|
Re: Yet Another cannot boot thread October 23, 2013 03:54AM |
Admin Registered: 13 years ago Posts: 18,580 |
dinjo Wrote:
-------------------------------------------------------
> I don't know which kernel did the squeeze script
> flashed hence i was asking this ,i tried your
> rootfs too blinking green and then lights goes
> off.
To prepare the rootfs, log on to another Linux box as root user, format a USB stick as Ext3, and follow the rest of the instruction to extract the roofs archive. Remember, we have to do everry thing as root.
I am quoting the instruction:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> I don't know which kernel did the squeeze script
> flashed hence i was asking this ,i tried your
> rootfs too blinking green and then lights goes
> off.
To prepare the rootfs, log on to another Linux box as root user, format a USB stick as Ext3, and follow the rest of the instruction to extract the roofs archive. Remember, we have to do everry thing as root.
I am quoting the instruction:
Quote
Updated 01 Oct 2013:
Rootfs 3.11.1 was uploaded. This rootfs is to keep in sync with kernel Linux-3.11.1-kirkwood-tld-1 (and its new features).
Basic minimal Debian Kirkwood rootfs for most Kirwood plugs:
- tarball size: 93M
- install size: 335M
- a basic wheezy rootfs
- Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, and nfs server/client packages.
- see LED controls in /etc/rc.local, and /etc/rc0.d/K07halt (for NSA320 LEDs control, see posts by pbg4 in this thread)
- see some useful aliases in /root/.profile
- root password: root
Download at Dropbox:
Debian-3.11.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2
md5:
bd364aee6bdcc3fccd8cd95b37c3bc74
Installation:
- format a new ext3 USB drive, and label it rootfs. Note: if your uBoot env for usb_rootfstype is ext2, then use an ext2 USB drive.
- cd to top level directory and extract it (assuming the USB drive is mounted at /media/sdb1)
cd /media/sdb1
tar -xjf Debian-3.11.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2
- edit /media/sdb1/etc/fstab entry for /dev/root to match the rootfstype of your usb_rootfstype.
sync
- reboot
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Yet Another cannot boot thread October 23, 2013 04:18AM |
Registered: 11 years ago Posts: 93 |
|
Re: Yet Another cannot boot thread October 23, 2013 08:27AM |
Registered: 11 years ago Posts: 93 |
|
Re: Yet Another cannot boot thread October 23, 2013 12:17PM |
Admin Registered: 13 years ago Posts: 18,580 |
Do you have the log when you run dockstar.debian-squeeze.sh the first time? It shows how uBoot was installed, and anything abnormal occurred during that step.
Blinking green and never got to solid green means that either the kernel (uImage) and initrd (uInitrd) were not loaded successfully. But it does not mean the box is bricked. If you have installed uBoot (part of the squeeze script) successfully, then it is just the matter of having a good rootfs. Try Ext3 rootfs to see if it makes any difference.
Also if you have the log when you create the rootfs, pls post here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Blinking green and never got to solid green means that either the kernel (uImage) and initrd (uInitrd) were not loaded successfully. But it does not mean the box is bricked. If you have installed uBoot (part of the squeeze script) successfully, then it is just the matter of having a good rootfs. Try Ext3 rootfs to see if it makes any difference.
Also if you have the log when you create the rootfs, pls post here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Yet Another cannot boot thread October 23, 2013 08:32PM |
Registered: 11 years ago Posts: 93 |
|
Re: Yet Another cannot boot thread October 24, 2013 12:38AM |
Admin Registered: 13 years ago Posts: 18,580 |
dinjo Wrote:
-------------------------------------------------------
> SInce the script has several issues in it i had to
> run some times and I have seen there were no
> issues installing uboot, the log is mentioned in
> first post itself
I see. uBoot installation does look good in this:
So now it's just the rootfs.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> SInce the script has several issues in it i had to
> run some times and I have seen there were no
> issues installing uboot, the log is mentioned in
> first post itself
I see. uBoot installation does look good in this:
# Validating existing uBoot... Block size 131072, page size 2048, OOB size 64 Dumping data starting at 0x00000000 and ending at 0x00080000... Connecting to jeff.doozan.com (50.116.34.13:80) valid-uboot.md5 100% |********************************************************************************************************************************************************************************************| 1133 --:--:-- ETA ## Valid uBoot detected: [goflexnet davygravy-2012-04-19-current] ## The newest uBoot is already installed on mtd0.
So now it's just the rootfs.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
dinjo1
Re: Yet Another cannot boot thread October 24, 2013 03:50AM |
|
Re: Yet Another cannot boot thread October 24, 2013 04:02AM |
Admin Registered: 13 years ago Posts: 18,580 |
Jeff's Squeeze script flashes kernel 2.6.3x.xx to the USB drive. The only thing that's changed in NAND is mtd0 for uBoot. Since your uBoot installation was good (according to the log), the problem is with the USB rootfs that you're using. So that's why I think it's worth trying to create USB boot drive using my uploaded rootfs. If you can post the log of how you create the stick, it would be helpful, because you might have missed something.
If for what ever reason it still does not work after you try this rootfs many times, then I think you should get serial console. BTW, the Goflex Net serial console is quite easy to setup, no soldering needed.
Another thought, have you tried to remove the stick and boot? if it booted into the orginal Pogo OS, then the problem is solved.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
If for what ever reason it still does not work after you try this rootfs many times, then I think you should get serial console. BTW, the Goflex Net serial console is quite easy to setup, no soldering needed.
Another thought, have you tried to remove the stick and boot? if it booted into the orginal Pogo OS, then the problem is solved.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
dinjo1
Re: Yet Another cannot boot thread October 24, 2013 07:32AM |
|
Re: Yet Another cannot boot thread October 24, 2013 11:18AM |
Registered: 11 years ago Posts: 93 |
|
Re: Yet Another cannot boot thread October 24, 2013 12:53PM |
Admin Registered: 13 years ago Posts: 18,580 |
dinjo1 Wrote:
-------------------------------------------------------
> I'll reach home and try again but i'm confused
> since the rootfs is 3.11.1 kernel compatible and
> device is flashed with 2.6 kernel is it expected
> to boot ?
>
> Serial Cable and how to open and connect the
> device ?
The device is not flashed with kernel. The script only flashed uBoot to NAND mtd0. The kernel is on USB.
In your USB stick, /boot directory is where the kernel files reside:
During boot, uBoot in mtd0 is executed, and then it will load uImage and uInitrd from the USB.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> I'll reach home and try again but i'm confused
> since the rootfs is 3.11.1 kernel compatible and
> device is flashed with 2.6 kernel is it expected
> to boot ?
>
> Serial Cable and how to open and connect the
> device ?
The device is not flashed with kernel. The script only flashed uBoot to NAND mtd0. The kernel is on USB.
In your USB stick, /boot directory is where the kernel files reside:
config-3.11.1-kirkwood-tld-1 initrd.img-3.11.1-kirkwood-tld-1 System.map-3.11.1-kirkwood-tld-1 vmlinuz-3.11.1-kirkwood-tld-1 uImage uInitrd
During boot, uBoot in mtd0 is executed, and then it will load uImage and uInitrd from the USB.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Yet Another cannot boot thread October 25, 2013 10:37PM |
Registered: 11 years ago Posts: 93 |
I tried it never worked , is the script even tested ? Is this labelling correct ?
Edited 1 time(s). Last edit at 10/25/2013 10:37PM by dinjo.
root@debian:~# blkid /dev/sdb1 /dev/sdb1: LABEL="rootfs" UUID="4a1ebf57-568b-4e01-9d54-ae85ea4e1f6d" TYPE="ext3" root@debian:~# blkid /dev/sdb2 /dev/sdb2: TYPE="swap"
Edited 1 time(s). Last edit at 10/25/2013 10:37PM by dinjo.
|
Re: Yet Another cannot boot thread October 26, 2013 01:19AM |
Admin Registered: 13 years ago Posts: 18,580 |
OK, let state the instruction from this thread http://forum.doozan.com/read.php?2,12096 once more time.
Updated 01 Oct 2013: Rootfs 3.11.1 was uploaded. This rootfs is to keep in sync with kernel Linux-3.11.1-kirkwood-tld-1 (and its new features). ..... Installation: - format a new ext3 USB drive, and label it rootfs (this means only one Ext3 partition on this USB stick). - cd to top level directory and extract it (assuming the USB drive is mounted at /media/sdb1) cd /media/sdb1 tar -xjf Debian-3.11.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2 - edit /media/sdb1/etc/fstab entry for /dev/root to match the rootfstype of your usb_rootfstype. sync - reboot (If the rootfs is prepared on another Linux box, then simply unmount it after sync, and take it to the box you're installing and cold start).
|
Re: Yet Another cannot boot thread October 26, 2013 01:57AM |
Registered: 11 years ago Posts: 93 |
|
Re: Yet Another cannot boot thread October 26, 2013 06:44PM |
Admin Registered: 13 years ago Posts: 18,580 |
dinjo Wrote:
-------------------------------------------------------
> I have done that exactly the same way
>
New USB stick formatted with Ext3: meaning using fdisk to delete all existing partitions, and create one and only one Ext3 partition. Also, in fdisk, make sure that the stick is MBR not GPT.
> Could changing URL_BOOTSTRAP have caused some
> issue ?
Does not affect uBoot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> I have done that exactly the same way
>
New USB stick formatted with Ext3: meaning using fdisk to delete all existing partitions, and create one and only one Ext3 partition. Also, in fdisk, make sure that the stick is MBR not GPT.
> Could changing URL_BOOTSTRAP have caused some
> issue ?
Does not affect uBoot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Yet Another cannot boot thread October 26, 2013 10:17PM |
Registered: 11 years ago Posts: 93 |
Is this ok ? Since i don't know how to make the drive as MBR , Boot label does not have a * to it
root@debian:~# fdisk /dev/sdc
WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
switch off the mode (command 'c') and change display units to
sectors (command 'u').
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-15300, default 1):
Using default value 1
Last cylinder, +cylinders or +size{K,M,G} (1-15300, default 15300):
Using default value 15300
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
root@debian:~# fdisk -l /dev/sdc
Disk /dev/sdc: 16.0 GB, 16043212800 bytes
64 heads, 32 sectors/track, 15300 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x5e575fc3
Device Boot Start End Blocks Id System
/dev/sdc1 1 15300 15667184 83 Linux
root@debian:~#
|
Re: Yet Another cannot boot thread October 26, 2013 10:51PM |
Registered: 11 years ago Posts: 93 |
I'm in now what should be the next steps ? Flash the new kernel ? or run a apt-dist Since its still squeeze not wheezy
This should be only one in sources.list right ? i.e remove the squeeze ? then apt-update and then apt-get dist-upgrade
Or Should i first install v2 rescue system ?
Edited 3 time(s). Last edit at 10/26/2013 11:09PM by dinjo.
This should be only one in sources.list right ? i.e remove the squeeze ? then apt-update and then apt-get dist-upgrade
deb http://ftp.us.debian.org/debian/ wheezy main deb-src http://ftp.us.debian.org/debian/ wheezy main deb http://security.debian.org/ wheezy/updates main deb-src http://security.debian.org/ wheezy/updates main # wheezy-updates, previously known as 'volatile' deb http://ftp.us.debian.org/debian/ wheezy-updates main deb-src http://ftp.us.debian.org/debian/ wheezy-updates main
Or Should i first install v2 rescue system ?
linux-3.11.1-kirkwood-tld-2-bodhi.tar.bz2 md5: dc306ed40cd5eab6fd0e81105a5cf82e This tarbal contains 4 files: linux-image-3.11.1-kirkwood-tld-2_2.0_armel.deb linux-headers-3.11.1-kirkwood-tld-2_2.0_armel.deb config-3.11.1-kirkwood-tld-2 linux-3.11.1-tld-2-kirkwood.patch Installation: - Backup your current uImage and uInitrd. 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-kirkwood System.map-xx.xx.xx-kirkwood vmlinuz-xx.xx.xx-kirkwood config-xx.xx.xx-kirkwood - Extract the kernel in the archive: tar -xjf linux-3.11.1-kirkwood-tld-2-bodhi.tar.bz2 - 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.11.1-kirkwood-tld-2_2.0_armel.deb - Create uImage and uInitrd manually: mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.11.1-kirkwood-tld-2 -d /boot/vmlinuz-3.11.1-kirkwood-tld-2 /boot/uImage mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.11.1-kirkwood-tld-2 -d /boot/initrd.img-3.11.1-kirkwood-tld-2 /boot/uInitrd - The new uImage and uInitrd files should be created in /boot directory now. You're ready to reboot the system: sync shutdown -r now Note: For completeness, create symlinks for the kernel in your / directory (in case the rootfs is ever used with different bootloader). But it is not necessary to do this for uBoot. cd / ln -s boot/vmlinuz-3.11.1-kirkwood-tld-2 vmlinuz ln -s boot/initrd.img-3.11.1-kirkwood-tld-2 initrd.img
Edited 3 time(s). Last edit at 10/26/2013 11:09PM by dinjo.
|
Re: Yet Another cannot boot thread October 27, 2013 07:06AM |
Registered: 11 years ago Posts: 93 |
|
Re: Yet Another cannot boot thread October 27, 2013 03:39PM |
Admin Registered: 13 years ago Posts: 18,580 |
While in Debian, pls get the output of
dmesg
fw_printenv
mount
and post here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
dmesg
fw_printenv
mount
and post here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Yet Another cannot boot thread October 27, 2013 10:45PM |
Registered: 11 years ago Posts: 93 |
Should i go ahead and install Rescue system v2.0 since when i ran it it showed me that its only for dockstar , also looked for 2.8 Rescue system but for that it requires higher kernel , so I'm not really sure what needs to be done here ? Also I'm setting it to have static ip now so that i can correctly set netconsole.
dmesg
auto lo eth0 iface lo inet loopback #iface eth0 inet dhcp iface eth0 inet static address 192.168.1.104 gateway 192.168.1.1 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 hwaddress ether 00:25:31:02:01:8B
dmesg
root@debian:~# dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.11.1-kirkwood-tld-1 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 PREEMPT Fri Sep 27 01:50:15 PDT 2013 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] Machine: Seagate GoFlex Net [ 0.000000] Memory policy: ECC disabled, Data cache writeback [ 0.000000] On node 0 totalpages: 32768 [ 0.000000] free_area_init_node: node 0, pgdat c05f0c74, node_mem_map c065d000 [ 0.000000] Normal zone: 256 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 32768 pages, LIFO batch:7 [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 [ 0.000000] pcpu-alloc: [0] 0 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 [ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext2 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) [ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes) [ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) [ 0.000000] Memory: 117020K/131072K available (4192K kernel code, 309K rwdata, 1368K rodata, 187K init, 420K bss, 14052K reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) [ 0.000000] vmalloc : 0xc8800000 - 0xff000000 ( 872 MB) [ 0.000000] lowmem : 0xc0000000 - 0xc8000000 ( 128 MB) [ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB) [ 0.000000] .text : 0xc0008000 - 0xc05761a0 (5561 kB) [ 0.000000] .init : 0xc0577000 - 0xc05a5cdc ( 188 kB) [ 0.000000] .data : 0xc05a6000 - 0xc05f3538 ( 310 kB) [ 0.000000] .bss : 0xc05f3538 - 0xc065c5cc ( 421 kB) [ 0.000000] Preemptible hierarchical RCU implementation. [ 0.000000] NR_IRQS:114 [ 0.000000] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms [ 0.000000] Console: colour dummy device 80x30 [ 10.299093] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584) [ 10.388888] pid_max: default: 32768 minimum: 301 [ 10.388991] Security Framework initialized [ 10.389061] Mount-cache hash table entries: 512 [ 10.389682] Initializing cgroup subsys devices [ 10.389704] Initializing cgroup subsys freezer [ 10.389717] Initializing cgroup subsys net_cls [ 10.389727] Initializing cgroup subsys blkio [ 10.389800] CPU: Testing write buffer coherency: ok [ 10.390186] Setting up static identity map for 0xc03f6900 - 0xc03f693c [ 10.392018] devtmpfs: initialized [ 10.394274] pinctrl core: initialized pinctrl subsystem [ 10.394607] regulator-dummy: no parameters [ 10.394924] NET: Registered protocol family 16 [ 10.395342] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 10.396114] Kirkwood: MV88F6281-A1, TCLK=200000000. [ 10.396135] Feroceon L2: Enabling L2 [ 10.396174] Feroceon L2: Cache support initialised. [ 10.396501] initial MPP regs: 01111111 11113322 00001111 00100000 00000000 00000000 00000000 [ 10.396529] final MPP regs: 01111111 11113322 00001111 00000000 00000000 00000000 00000000 [ 10.400011] bio: create slab <bio-0> at 0 [ 10.400436] vgaarb: loaded [ 10.400573] usbcore: registered new interface driver usbfs [ 10.400625] usbcore: registered new interface driver hub [ 10.400722] usbcore: registered new device driver usb [ 10.401339] Switched to clocksource orion_clocksource [ 10.415801] NET: Registered protocol family 2 [ 10.416443] TCP established hash table entries: 1024 (order: 1, 8192 bytes) [ 10.416480] TCP bind hash table entries: 1024 (order: 0, 4096 bytes) [ 10.416501] TCP: Hash tables configured (established 1024 bind 1024) [ 10.416567] TCP: reno registered [ 10.416581] UDP hash table entries: 256 (order: 0, 4096 bytes) [ 10.416605] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [ 10.416803] NET: Registered protocol family 1 [ 10.417112] RPC: Registered named UNIX socket transport module. [ 10.417123] RPC: Registered udp transport module. [ 10.417130] RPC: Registered tcp transport module. [ 10.417138] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 10.417150] PCI: CLS 0 bytes, default 32 [ 10.417351] Unpacking initramfs... [ 10.963775] Freeing initrd memory: 6360K (c1101000 - c1737000) [ 10.963877] NetWinder Floating Point Emulator V0.97 (double precision) [ 10.964483] audit: initializing netlink socket (disabled) [ 10.964529] type=2000 audit(0.660:1): initialized [ 10.965368] VFS: Disk quotas dquot_6.5.2 [ 10.965420] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 10.965780] NFS: Registering the id_resolver key type [ 10.965855] Key type id_resolver registered [ 10.965865] Key type id_legacy registered [ 10.965884] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 10.966048] jffs2: version 2.2. (NAND) (SUMMARY) \xffffffc2\xffffffa9 2001-2006 Red Hat, Inc. [ 10.966257] msgmni has been set to 240 [ 10.968122] alg: No test for stdrng (krng) [ 10.968214] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) [ 10.968226] io scheduler noop registered [ 10.968234] io scheduler deadline registered [ 10.968256] io scheduler cfq registered (default) [ 10.968451] mv_xor mv_xor.0: Marvell shared XOR driver [ 11.001419] mv_xor mv_xor.0: Marvell XOR: ( xor cpy ) [ 11.041399] mv_xor mv_xor.0: Marvell XOR: ( xor cpy ) [ 11.041503] mv_xor mv_xor.1: Marvell shared XOR driver [ 11.081398] mv_xor mv_xor.1: Marvell XOR: ( xor cpy ) [ 11.121396] mv_xor mv_xor.1: Marvell XOR: ( xor cpy ) [ 11.121649] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled [ 11.142200] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A [ 11.638818] console [ttyS0] enabled [ 11.643329] ONFI param page 0 valid [ 11.646836] ONFI flash detected [ 11.649998] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron MT29F2G08AAD), 256MiB, page size: 2048, OOB size: 64 [ 11.661116] Scanning device for bad blocks [ 11.711570] Bad eraseblock 440 at 0x000003700000 [ 11.885178] 4 cmdlinepart partitions found on MTD device orion_nand [ 11.891490] Creating 4 MTD partitions on "orion_nand": [ 11.896652] 0x000000000000-0x000000100000 : "u-boot" [ 11.901877] 0x000000100000-0x000000500000 : "uImage" [ 11.907073] 0x000000500000-0x000002500000 : "rootfs" [ 11.912337] 0x000002500000-0x000010000000 : "data" [ 11.917614] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 11.924188] ehci-pci: EHCI PCI platform driver [ 11.928692] ehci-orion: EHCI orion driver [ 11.932789] orion-ehci orion-ehci.0: EHCI Host Controller [ 11.938234] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1 [ 11.945988] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000 [ 11.971372] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00 [ 11.977395] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 11.984236] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 11.991503] usb usb1: Product: EHCI Host Controller [ 11.996406] usb usb1: Manufacturer: Linux 3.11.1-kirkwood-tld-1 ehci_hcd [ 12.003151] usb usb1: SerialNumber: orion-ehci.0 [ 12.008206] hub 1-0:1.0: USB hub found [ 12.012020] hub 1-0:1.0: 1 port detected [ 12.016373] mousedev: PS/2 mouse device common for all mice [ 12.331377] usb 1-1: new high-speed USB device number 2 using orion-ehci [ 12.483626] usb 1-1: New USB device found, idVendor=8564, idProduct=1000 [ 12.490371] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 12.497564] usb 1-1: Product: Mass Storage Device [ 12.502303] usb 1-1: Manufacturer: JetFlash [ 12.506509] usb 1-1: SerialNumber: 263S3FQI3XSUYB9W [ 13.031369] rtc-mv rtc-mv: internal RTC not ticking [ 13.036366] i2c /dev entries driver [ 13.039941] cpuidle: using governor ladder [ 13.044072] cpuidle: using governor menu [ 13.048851] drop_monitor: Initializing network drop monitor service [ 13.055455] TCP: cubic registered [ 13.058790] NET: Registered protocol family 17 [ 13.063362] Key type dns_resolver registered [ 13.068088] registered taskstats version 1 [ 13.073061] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 13.080157] Freeing unused kernel memory: 184K (c0577000 - c05a5000) [ 13.152053] udevd[52]: starting version 175 [ 13.257718] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 [ 13.339228] libphy: orion_mdio_bus: probed [ 13.399134] SCSI subsystem initialized [ 13.439629] usb-storage 1-1:1.0: USB Mass Storage device detected [ 13.483910] libata version 3.00 Edited 1 time(s). Last edit at 10/27/2013 10:46PM by dinjo.
|
Re: Yet Another cannot boot thread October 28, 2013 01:17AM |
Admin Registered: 13 years ago Posts: 18,580 |
dinjo,
Congrats! you are all set. I would not bother with rescue system. If you set up netconsole, and test it to make sure it is working, you don't need rescue system at all. If you encounter any problem in the future, then just use netconsole to monitor uBoot, get into uBoot prompt and recover. Rescues system also had caused some problems lately for some users, so if you can do without it then you'll spend less time to troubleshoot this installation. The best thing to do is just backup your USB stick image from time to time and you can always boot with the backup.
Now you can start using your plug. Please change root password, and generate new SSL key to secure it, and install whatever packages you'd need.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Congrats! you are all set. I would not bother with rescue system. If you set up netconsole, and test it to make sure it is working, you don't need rescue system at all. If you encounter any problem in the future, then just use netconsole to monitor uBoot, get into uBoot prompt and recover. Rescues system also had caused some problems lately for some users, so if you can do without it then you'll spend less time to troubleshoot this installation. The best thing to do is just backup your USB stick image from time to time and you can always boot with the backup.
Now you can start using your plug. Please change root password, and generate new SSL key to secure it, and install whatever packages you'd need.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
