Welcome! Log In Create A New Profile

Advanced

PogoPlug Mobile SSH?

Posted by Darkphyer 
Wes
Re: PogoPlug Mobile SSH?
November 29, 2016 06:32PM
Bodhi,

Here is the output from the filesystem check:
 
ubuntu@ubuntu:~$ umount /dev/mmcblk0p1
ubuntu@ubuntu:~$ sudo e2fsck /dev/mmcblk0p1
e2fsck 1.42.13 (17-May-2015)
rootfs has gone 17134 days without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
rootfs: 17651/120720 files (2.0% non-contiguous), 160552/482670 blocks
ubuntu@ubuntu:~$ sudo e2label /dev/mmcblk0p1
rootfs
ubuntu@ubuntu:~$

After that I put the SD card into the Pogo and here is the output from serial:

U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   kwsdio: 0
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Error: egiga0 address not set.

Hit any key to stop autoboot:  0
Pogov4> printenv
baudrate=115200
bootcmd=mmc rescan; run set_bootargs_mmc; run mmc_boot; reset
bootdelay=5
ethact=egiga0
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; run mmc_load_dtb; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi
mmc_load_dtb=load mmc 0:1 0x1c00000 /boot/dts/kirkwood-pogoplug_v4.dtb
mmc_load_uimage=load mmc 0:1 0x800000 /boot/uImage\
setenv mmc_load_uinitrd load mmc 0:1 0x1100000 /boot/uInitrd
set_bootargs_mmc=setenv bootargs console=$console root=LABEL=rootfs  rootdelay=10 $mtdparts $custom_params
stderr=serial
stdin=serial
stdout=serial

Environment size: 626/131068 bytes
Pogov4> boot

MMC rescan: current device # 0 initialized OK
3232368 bytes read in 1414 ms (2.2 MiB/s)
10266 bytes read in 4547 ms (2 KiB/s)
6531090 bytes read in 2128 ms (2.9 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.8.3-kirkwood-tld-1
   Created:      2016-11-26  23:57:49 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3232304 Bytes = 3.1 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.8.3-kirkwood-tld-1
   Created:      2016-11-26  23:58:20 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6531026 Bytes = 6.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
   Booting using the fdt blob at 0x1c00000
   Loading Kernel Image ... OK
   Loading Ramdisk to 074d4000, end 07b0e7d2 ... OK
   Loading Device Tree to 074ce000, end 074d3819 ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

-Wes
Re: PogoPlug Mobile SSH?
November 29, 2016 08:03PM
You said it has booted into Debian before saving the envs ? Did I understand you correctly?

Do you have a USB thumb drive you can use to create the rootfs on it?

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



Edited 1 time(s). Last edit at 11/29/2016 08:05PM by bodhi.
Wes
Re: PogoPlug Mobile SSH?
November 29, 2016 08:24PM
Bodhi,

The very first time I booted into serial, interrupted, and put in the temporary envs it booted into Debian. While I was in Debian, I put in the permanent env's you sent me, and then after that reboot, I'm where I am now, where temporary env's no longer work, and just leaving it freezes it at the loading kernal phase.

I have an extra 8gb usb stick I can use, but I'll need instructions. I am also up for just resetting the SD card entirely, as it's seeming super troublesome, and starting fresh would fix all of the problems that have been occuring.

-Wes
Re: PogoPlug Mobile SSH?
November 30, 2016 01:07AM
Wes,

All you need to do is to create a rootfs just like what you did before with the SD card. Using a USB drive is the same, except that the drive letter is mmcblk0p1 instead of sda1, sdb1, sdc1,...

Just follow the same instruction as before. Go ahead, start it, stop and post the log whenever you need to ask questions before you can proceed.

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



Edited 1 time(s). Last edit at 11/30/2016 01:08AM by bodhi.
Re: PogoPlug Mobile SSH?
November 30, 2016 04:26PM
Wes,

The instruction is in this thread: http://forum.doozan.com/read.php?2,12096

Scrol down to the section

Quote

Updated 20 Feb 2016:

This Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is to keep in sync with kernel Linux-4.4.0-kirkwood-tld-1.

Basic minimal Debian Kirkwood rootfs for most Kirwood plugs:

- tarball size: 137M
- install size: 398M
- a basic jessie rootfs.
- The init system used in this rootfs is sysvinit . To boot with systemd, see note 2 below.
- Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs server/client, iperf, ethtool, sysvinit-core, sysvinit, and sysvinit-utils.
- see LED controls in /etc/rc.local, and /etc/init.d/halt
- see some useful aliases in /root/.profile
- root password: root

Download at Dropbox:

Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
md5:
9f957e1dc5a36f90a285ab4615cb02fd
sha256:
d33349118e34bd078ca635cd2d6776f3e312accfc77d29da5870b9980add5c36

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

Installation:

Installation can be done on any Linux box, with a fresh USB drive (SD card or HDD would work fine too).

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

1. Format a new USB drive with a single Ext3 partition, and label it rootfs.

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

3. Adjust fstab. Skip this step if you have installed the latest U-Boot for Kirkwood (or are installing this u-boot at the same time).

Edit /media/sdb1/etc/fstab entry for /dev/root to match the rootfstype of your usb_rootfstype. However, you can keep it as is without problem in booting since the u-boot env bootargs takes precedent.
/dev/root / ext3 noatime,errors=remount-ro 0 1

4. Create uImage with embedded DTB for booting with older u-boots (2012 or earlier). Skip this step if you have installed the latest U-Boot for Kirkwood (or are installing this u-boot at the same time).

Please replace kirkwood-goflexnet.dtb below with the correct DTB name for your box (see the folder /media/sdb1/boot/dts).

Generate the uImage with DTB embedded inside:
cd /media/sdb1/boot
cp -a zImage-4.4.0-kirkwood-tld-1 zImage.fdt
cat dts/kirkwood-goflexnet.dtb >> zImage.fdt
mv uImage uImage.orig
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.4.0-kirkwood-tld-1 -d zImage.fdt uImage
sync

Note: if your Linux box does not have mkimage, then install it

apt-get install u-boot-tools

5. Done. Take this USB rootfs to your plug and cold start. After booted into Debian, see Note1 and Note2 below. It is very important that you do Note1 steps to secure your box.

Note1:

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

apt-get update
apt-get upgrade

Note2:

To boot with systemd, add this parameter to your u-boot env bootargs. If you are booting with my latest u-boot images then use the uEnv.txt capability to do this. See the instruction about uEnvt.txt in that thread.
init=/bin/systemd
For example,
fw_setenv usb_set_bootargs 'setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts init=/bin/systemd'

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


The best way to learn Linux is you would make a list of commands you will execute from the instruction above, and post here. And then I'll check to see if you miss anything and correct it.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: PogoPlug Mobile SSH?
March 16, 2017 04:45PM
Hey Bodhi,

Not sure if you remember, but I was the guy who was having all sorts of issues with his Pogoplug, just trying to get it to work as a server. My apologies for not giving you a heads up about my haitus, but I had some birthdays, xmas, new years, just general life get in the way, and I shoved the Pogo into a literal corner.

I've been cleaning up and throwing out a bunch of things this week, and came across the Pogo, and I thought I'd give it one more shot at making it work before I just bin it permanently.

You have no obligation to help me, as last I can remember was that I had somehow close-to-bricked the pogo. It's been a long time so I'm even having a hard time remembering how to connect up the pogo and what programs I had used to communicate with it.

So I'd like to start clean, any way I can wipe this thing and run some sort of script like this one on github I had used orginally, but hopefully this time installing the updated software instead of the outdated stuff.

So help in getting me to that point would be extremely appreciated.

-Wes
Re: PogoPlug Mobile SSH?
March 16, 2017 04:51PM
Wes,

Can you run pepas's procedure as described in that GitHub? that would be a good starting point if you're already familiar with it. After that, upgrading kernel is quite easy.

If you have difficulty understanding that instruction, let me know.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: PogoPlug Mobile SSH?
March 17, 2017 05:46AM
Bodhi,

After installing putty and associated drivers again, I connected via serial into the Pogo. This is the output:



U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   kwsdio: 0
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Error: egiga0 address not set.

Hit any key to stop autoboot:  0

MMC rescan: current device # 0 initialized OK
reading /boot/uImage
** Unable to read file /boot/uImage **
reading /boot/dts/kirkwood-pogoplug_v4.dtb
** Unable to read file /boot/dts/kirkwood-pogoplug_v4.dtb **
reading /boot/uInitrd
** Unable to read file /boot/uInitrd **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
resetting ...


U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   kwsdio: 0
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Error: egiga0 address not set.

Hit any key to stop autoboot:  0
Pogov4> cd /tmp
Unknown command 'cd' - try 'help'
Pogov4>

I plugged the SD card into my windows machine, and it looks to have been wiped. On the physical machine, I get a blinking green light the whole time, if that matters.

-Wes
Re: PogoPlug Mobile SSH?
March 17, 2017 05:48PM
Wes,

Your box is in good shape with new u-boot installed.

Now your problem is the SD card. You will need a Linux box or Linux VM to untar the rootfs Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 to it as root user. Using Windows will never work.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: PogoPlug Mobile SSH?
March 18, 2017 04:33AM
Bodhi,

I got a VM running for Manjaro. I am having a lot of trouble trying to extract the tarball to my sd card, I am stuck on a "Operation not permitted" error right now.

This is the output:

[manjaro@manjaro ~]$ sudo mount /dev/sdc1 Downloads/usb
mount: /dev/sdc1 is already mounted or /home/manjaro/Downloads/usb busy
       /dev/sdc1 is already mounted on /run/media/manjaro/3CF9-4AE7
       /dev/sdc1 is already mounted on /home/manjaro/Downloads/usb
[manjaro@manjaro ~]$ cd Downloads/
[manjaro@manjaro Downloads]$ sudo tar -jxvf Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 -C usb
./
./proc/
./sbin/
tar: ./proc: Cannot change ownership to uid 0, gid 0: Operation not permitted
./sbin/poweroff
tar: ./sbin/poweroff: Cannot create symlink to ‘halt’: Operation not permitted
./sbin/ldconfig
tar: ./sbin/ldconfig: Cannot change ownership to uid 0, gid 0: Operation not permitted
./sbin/capsh
tar: ./sbin/capsh: Cannot change ownership to uid 0, gid 0: Operation not permitted
./sbin/dhclient-script
tar: ./sbin/dhclient-script: Cannot change ownership to uid 0, gid 0: Operation not permitted
./sbin/rpcbind
tar: ./sbin/rpcbind: Cannot change ownership to uid 0, gid 0: Operation not permitted
./sbin/rpc.statd
tar: ./sbin/rpc.statd: Cannot change ownership to uid 0, gid 0: Operation not permitted
./sbin/showmount
tar: ./sbin/showmount: Cannot change ownership to uid 0, gid 0: Operation not permitted
./sbin/fsck.minix
tar: ./sbin/fsck.minix: Cannot change ownership to uid 0, gid 0: Operation not permitted
./sbin/debugfs
tar: ./sbin/debugfs: Cannot change ownership to uid 0, gid 0: Operation not permitted
./sbin/badblocks
tar: ./sbin/badblocks: Cannot change ownership to uid 0, gid 0: Operation not permitted
./sbin/swaplabel
tar: ./sbin/swaplabel: Cannot change ownership to uid 0, gid 0: Operation not permitted
./sbin/blockdev
tar: ./sbin/blockdev: Cannot change ownership to uid 0, gid 0: Operation not permitted
./sbin/fsck.ext4
tar: ./sbin/fsck.ext4: Cannot create symlink to ‘e2fsck’: Operation not permitted
./sbin/shutdown
....

I'm not sure if it's my commands or if I'm not root user or something else.

-Wes
Re: PogoPlug Mobile SSH?
March 18, 2017 04:53AM
Wes,

http://forum.doozan.com/read.php?2,12096


Quote

Updated 20 Feb 2016:

This Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is to keep in sync with kernel Linux-4.4.0-kirkwood-tld-1.

Basic minimal Debian Kirkwood rootfs for most Kirwood plugs:

- tarball size: 137M
- install size: 398M
- a basic jessie rootfs.
- The init system used in this rootfs is sysvinit . To boot with systemd, see note 2 below.
- Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs server/client, iperf, ethtool, sysvinit-core, sysvinit, and sysvinit-utils.
- see LED controls in /etc/rc.local, and /etc/init.d/halt
- see some useful aliases in /root/.profile
- root password: root

Download at Dropbox:

Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
md5:
9f957e1dc5a36f90a285ab4615cb02fd
sha256:
d33349118e34bd078ca635cd2d6776f3e312accfc77d29da5870b9980add5c36

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

Installation:

Installation can be done on any Linux box, with a fresh USB drive (SD card or HDD would work fine too).

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

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: PogoPlug Mobile SSH?
March 18, 2017 08:18AM
Bodhi,

My apologies for glossing over the most important part of those steps, remembering all the programs and commands from 4 months ago has my brain filled!

I did the same commands while logged in as Su on the virtual machine, and it gave me more "Operation not permitted" errors. But I remembered that you said VM's have problems with root sometimes.

So I went to my full install of Ubuntu on my laptop and ran the commands. Unfortunately, I am still getting "Operation not permitted" errors, this is what I've entered on the Ubuntu install with root access:

wes@wes-Satellite-C55-A:~$ su -
Password:
root@wes-Satellite-C55-A:~# mount /dev/mmcblk0p1 /home/wes/usb
mount: /dev/mmcblk0p1 is already mounted or /home/wes/usb busy
       /dev/mmcblk0p1 is already mounted on /home/wes/usb
root@wes-Satellite-C55-A:~# cd /home/wes/Downloads
root@wes-Satellite-C55-A:/home/wes/Downloads# tar -jxvf Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 -C /home/wes/usb
./
./proc/
./sbin/
./sbin/poweroff
tar: ./sbin/poweroff: Cannot create symlink to ‘halt’: Operation not permitted
./sbin/ldconfig
./sbin/capsh
...
...
...
tar: ./sbin/udevadm: Cannot create symlink to ‘/bin/udevadm’: Operation not permitted
tar: ./sbin/depmod: Cannot create symlink to ‘/bin/kmod’: Operation not permitted
tar: ./sbin/rmmod: Cannot create symlink to ‘/bin/kmod’: Operation not permitted
tar: Exiting with failure status due to previous errors

Full log at pastebin (500kb)

So I decided to google the "Operation not permitted" error, and it looks to be an issue with "immutable flag"?

So I tried the command listed in the webpage, and ran the tar (extract) command again, unfortunately the same output.

This was the command I used:
root@wes-Satellite-C55-A:/home/wes/Downloads# chattr -i Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2

-Wes


Bodhi,

Good news and bad news

I think I finally got the top portion to work, I basically worked with my friend that dabbles in linux, and he suggested just extracting the files into a folder, then copying to the SD card. I thought this wouldn't work, and it didn't, but I think one of the commands I ran that gave me more permissions to the folders did.

I'm not sure which one it was, as we went through about 12 different errors before scrapping that idea, and I was going to run the commands one more time to show him the full error log, but the commands just worked...

So I thought I was in the clear to boot up the Pogo with the SD card, but it seems to be hanging when it wants to boot the kernel;



U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   kwsdio: 0
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Error: egiga0 address not set.

Hit any key to stop autoboot:  0

MMC rescan: current device # 0 initialized OK
3154896 bytes read in 1190 ms (2.5 MiB/s)
10246 bytes read in 2219 ms (3.9 KiB/s)
7179935 bytes read in 1414 ms (4.8 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.4.0-kirkwood-tld-1
   Created:      2016-02-19   5:55:25 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3154832 Bytes = 3 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.4.0-kirkwood-tld-1
   Created:      2016-02-19   7:33:04 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7179871 Bytes = 6.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
   Booting using the fdt blob at 0x1c00000
   Loading Kernel Image ... OK
   Loading Ramdisk to 07435000, end 07b0de5f ... OK
   Loading Device Tree to 0742f000, end 07434805 ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

So that is where I am at now.

-Wes

Edit: If possible, I would like to update the Uboot to the latest version while we are at it, but that is a lower priority over getting the machine to work.



Edited 7 time(s). Last edit at 03/18/2017 02:21PM by Wesy32.
Re: PogoPlug Mobile SSH?
March 18, 2017 03:50PM
Wes,

Your rootfs will not work.

As I mentioned often, when you install either u-boot or rootfs, you should run the commands from the instruction exactly as it stated. Don't try to change to something you think is compatible. If for whatever reason, the commands are not working, then you should post that log, and I will help explain why!

Here is the installation instruction (I removed unecessary steps).


1. Format a new USB drive with a single Ext3 partition, and label it rootfs.

After done this, if the drive is not automatically mounted, then remove the drive (using Ubuntu context menu with righ-click). And reinsert it, Ubuntu will mount the drive


2. At this point, you must be root. Become root and doublecheck:

su
whoami



3. Mount the drive on a Linux box. cd to top level directory and extract it. It is assuming the USB drive is mounted at /media/sdb1

cd /media/sdb1 
tar -xjf Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
sync


Note here: if you use the SD card then it will not be sdb1. However, on Ubuntu, the drive is mounted at whatever the parttion label (not the drive letter) is so if you did step 1 correctly, it will be mounted at /media/wes/rootfs (not /media/sdb1).

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

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



Edited 4 time(s). Last edit at 03/18/2017 04:07PM by bodhi.
Re: PogoPlug Mobile SSH?
March 18, 2017 04:37PM
Bodhi,

Ok I'll make sure to follow the instructions to a T, when I don't, I just end up confusing myself haha

Anyhow, this is the output from running the exact commands;

wes@wes-Satellite-C55-A:~$ su
Password:
root@wes-Satellite-C55-A:/home/wes# whoami
root
root@wes-Satellite-C55-A:/home/wes# cd /media/wes/rootfs
root@wes-Satellite-C55-A:/media/wes/rootfs# tar -xjf Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
tar (child): Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2: Cannot open: No such file or directory
tar (child): Error is not recoverable: exiting now
tar: Child returned status 2
tar: Error is not recoverable: exiting now
root@wes-Satellite-C55-A:/media/wes/rootfs# tar -xjf Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2
root@wes-Satellite-C55-A:/media/wes/rootfs# sync
root@wes-Satellite-C55-A:/media/wes/rootfs#

You can see the tarball didn't extract the first time, that was just because I still had the file in my /Downloads instead of on the card.

Unfortunantly, I am still getting stuck at the same place as last time;

...
...
...
   Loading Kernel Image ... OK
   Loading Ramdisk to 07435000, end 07b0de5f ... OK
   Loading Device Tree to 0742f000, end 07434805 ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

I think something might be up with the software (Uboot I think?) I installed on the Pogo? If you don't think it is, I have a couple more SD cards and USB sticks I can clear out and use for testing.

-Wes



Edited 1 time(s). Last edit at 03/18/2017 05:01PM by Wesy32.
Re: PogoPlug Mobile SSH?
March 18, 2017 05:20PM
Well, you did not follow the instructions!
http://forum.doozan.com/read.php?2,28710,33189#msg-33189

> You can see the tarball didn't extract the first t
> ime, that was just because I still had the file in
> my /Downloads instead of on the card.

So it did extract OK now?

> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.

This likely mean the u-boot envs are not correct. At serial console,

printenv

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: PogoPlug Mobile SSH?
March 19, 2017 11:16AM
Bodhi,

Yes I do believe that it did extract correctly, I can't be 100% sure as it doesn't give any confirmation prompts, but there were no error prompts either, I posted the full log.

Here is the output from printenv;



U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   kwsdio: 0
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Error: egiga0 address not set.

Hit any key to stop autoboot:  0
Pogov4> printenv
baudrate=115200
bootcmd=mmc rescan; run set_bootargs_mmc; run mmc_boot; reset
bootdelay=5
ethact=egiga0
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; run mmc_load_dtb; if run mmc_load              _uinitrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c000              00; fi
mmc_load_dtb=load mmc 0:1 0x1c00000 /boot/dts/kirkwood-pogoplug_v4.dtb
mmc_load_uimage=load mmc 0:1 0x800000 /boot/uImage\
setenv mmc_load_uinitrd load mmc 0:1 0x1100000 /boot/uInitrd
set_bootargs_mmc=setenv bootargs console=$console root=LABEL=rootfs  rootdelay=1              0 $mtdparts $custom_params
stderr=serial
stdin=serial
stdout=serial

Environment size: 626/131068 bytes
Pogov4>

-Wes
Re: PogoPlug Mobile SSH?
March 19, 2017 05:46PM
Wes,

The envs is a wrong set! when you flashed the new u-boot, you did not do step 8 to flash the default envs image that came with it.

Quote

8. Flashing default u-boot envs image:

As described in step 1, u-boot envs must be defined in etc/fw_env.config as

# MTD device name Device offset Env. size Flash sector size Number of sectors
/dev/mtd0 0xc0000 0x20000 0x20000

A special section (B. Flashing default u-boot envs image) about flashing default u-boot envs is included at the end of this installation procedure. Please follow the instruction in this section B to perform this step before continuing with step 9.

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

Here is how to fix that.

http://forum.doozan.com/read.php?3,29362,29390#msg-29390

In the above linked post, the procedure was written for the GoFlexNet. So you need to change these 3 lines in that instruction to ones appropriate for the Pogo Mobile:

setenv devices 'mmc usb'
setenv ethaddr xx:xx:xx:xx:xx:xx
setenv dtb_file '/boot/dts/kirkwood-pogoplug_v4.dtb'

(replace the ethaddr xx:xx:xx:xx:xx:xx above with the real Pogo Mobile MAC address).

and then

boot

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: PogoPlug Mobile SSH?
March 20, 2017 12:36PM
Bodhi,

I have some questions before I start entering commands.

- How can I find the mac address of my device?

- When I went to the Uboot post for kirkwood devices, I could not find the
kirkwood-pogoplug_v4.dtb
or the
uboot.2016.05-tld-1.environment.scr
file, only a .tar file.

- You mention that after I do the commands I should

Quote

Once you are in Debian, flash the uboot.2016.05-tld-1 and its default envs images like you did for the orignal box,
and then adjust envs,...

So should I just continue on with the other steps in the Uboot post? Ex: Step 9, 10, etc.

-Wes
Re: PogoPlug Mobile SSH?
March 20, 2017 02:56PM
Wes,

> - How can I find the mac address of my device?

It's on the box, should be a sticker on the case. If you cannot find it, then it is OK to keep using the random local MAC that I have in the default envs already. After you've source the script, this local MAC env will be populated along with other envs.

> I could not find the
kirkwood-pogoplug
> _v4.dtb

This file is on the Debian rootfs folder /boot/dts

> or the
uboot.2016.05-tld-1.en
> vironment.scr
file, only a .tar file.

This file is not part of the released tarball. I created this script for recovery purpose only. It was attached in the linked post.

Quote

On another Linux box, mount the Debian rootfs that you meant to run on this box and put the attached u-boot script in the /boot folder (if it was mounted at /media/sdb1):


> So should I just continue on with the other steps
> in the Uboot post? Ex: Step 9, 10, etc.

Let's get it booted with source envs script this way first! And then we can worry about saving it or flash the envs image.

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



Edited 2 time(s). Last edit at 03/20/2017 02:59PM by bodhi.
Re: PogoPlug Mobile SSH?
March 20, 2017 04:12PM
Bodhi,

Ok, I've found the mac address on my Pogo. I got the file copied over to /boot/ (Log from this at pastebin). But I got an error;



U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   kwsdio: 0
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Error: egiga0 address not set.

Hit any key to stop autoboot:  0
Pogov4> usb start
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Pogov4> ext2load usb 0:1 0x800000 /boot/uboot.2016.05-tld-1.environment.scr
** Bad device usb 0 **
Pogov4>

I'm guessing this is due to me using an SD card instead of a USB stick?

-Wes
Re: PogoPlug Mobile SSH?
March 20, 2017 07:35PM
>
> U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700
> )
> Pogoplug V4
>
> SoC: Kirkwood 88F6192_A1
> DRAM: 128 MiB
> WARNING: Caches not enabled
> NAND: 128 MiB
> MMC: kwsdio: 0
> In: serial
> Out: serial
> Err: serial
> Net: egiga0
> Error: egiga0 address not set.
>
> Hit any key to stop autoboot: 0
> Pogov4> usb start
> starting USB...
> USB0: USB EHCI 1.00
> scanning bus 0 for devices... 1 USB Device(s) foun
> d
> scanning usb for storage devices... 0 Stora
> ge Device(s) found
> Pogov4> ext2load usb 0:1 0x800000 /boot/uboot.2016
> .05-tld-1.environment.scr
> ** Bad device usb 0 **
> Pogov4>
> [/code]
>
> I'm guessing this is due to me using an SD card in
> stead of a USB stick?
>
> -Wes

Yes it is.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: PogoPlug Mobile SSH?
March 20, 2017 08:46PM
Bodhi,

Cool, I actually understood an error! But I don't really know how to fix it, so I was wondering if you know the correct command, or would I want to put the script onto a usb stick, then just run the commands with that?

-Wes
Re: PogoPlug Mobile SSH?
March 22, 2017 10:22PM
Wesy32 Wrote:
-------------------------------------------------------
> Bodhi,
>
> Cool, I actually understood an error! But I don't
> really know how to fix it, so I was wondering if y
> ou know the correct command, or would I want to pu
> t the script onto a usb stick, then just run the c
> ommands with that?
>
> -Wes

Let me write SD commands for you to try later tonight.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: PogoPlug Mobile SSH?
March 23, 2017 01:47AM
On another Linux box, mount the Debian rootfs that you meant to run on this box and put the attached u-boot script in the /boot folder (it is an SD card then it is probably mounted at /media/mmcblk0p1 ):

Download the script here:
http://forum.doozan.com/file.php?3,file=980,filename=uboot.2016.05-tld-1.environment.scr

cp -a uboot.2016.05-tld-1.environment.scr /media/mmcblk0p1/boot/
sync

Now unmount the SD card rootfs and take it to the Pogo Mobile. Plug in. Run serial console, power up and and interrupt serial console.

And then run the script loading commands at the u-boot prompt:
mmc rescan
load mmc 0:1 0x800000 /boot/uboot.2016.05-tld-1.environment.scr
source 0x800000
printenv

Verify that the default envs look good as the source uboot.2016.05-tld-1.environment (which you've already downloaded).

Adjust the other specific envs and then boot the rootfs:
setenv devices 'mmc'
setenv ethaddr xx:xx:xx:xx:xx:xx
setenv dtb_file '/boot/dts/kirkwood-pogoplug_v4.dtb'
boot

Once you can log into Debian, you can either:

1. Boot back using the same procedure above and save the envs in u-boot console (if not sure how, post the question).
OR
2. In Debian, flash the uboot.2016.05-tld-1 default envs images. And adjust the envs (if not sure how, post the question).

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



Edited 1 time(s). Last edit at 03/23/2017 01:48AM by bodhi.
Re: PogoPlug Mobile SSH?
March 24, 2017 01:30AM
Bodhi,

I ran the commands and they all went through. When I went to boot Debian, It stopped in the middle of booting, log here:



U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   kwsdio: 0
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Error: egiga0 address not set.

Hit any key to stop autoboot:  0
Pogov4> mmc rescan

MMC rescan: current device # 0 initialized OK
Pogov4> load mmc 0:1 0x800000 /boot/uboot.2016.05-tld-1.environment.scr
3232 bytes read in 1032 ms (2.9 KiB/s)
Pogov4> source 0x800000
## Executing script at 00800000
Pogov4> printenv
arcNumber=2097
baudrate=115200
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-pogo_e02.dtb
ethact=egiga0
ethaddr=52:3b:20:9c:11:51
fileaddr=800000
filesize=ca0
if_netconsole=ping $serverip
ipaddr=192.168.0.231
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
machid=0x831
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; run mmc_load_dtb; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi
mmc_load_dtb=load mmc 0:1 0x1c00000 /boot/dts/kirkwood-pogoplug_v4.dtb
mmc_load_uimage=load mmc 0:1 0x800000 /boot/uImage\
setenv mmc_load_uinitrd load mmc 0:1 0x1100000 /boot/uInitrd
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
serverip=192.168.0.220
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
set_bootargs_mmc=setenv bootargs console=$console root=LABEL=rootfs  rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_ready_retry=15

Environment size: 3377/131068 bytes
Pogov4> setenv devices 'mmc'
Pogov4> setenv ethaddr xxxxxxxxxxxx
## Error: flags type check failure for "ethaddr" <= "xxxxxxxxxxxx" (type: m)
## Error inserting "ethaddr" variable, errno=1
Pogov4> setenv ethaddr xx:xx:xx:xx:xx:xx
Pogov4> setenv dtb_file '/boot/dts/kirkwood-pogoplug_v4.dtb'
Pogov4> boot

MMC rescan: current device # 0 initialized OK

Partition Map for MMC device 0  --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
  1     61              3861361         00000000-01     83
loading envs from mmc 0 ...
** File not found /boot/uEnv.txt **
running scan_disk ...
Scan device mmc

MMC rescan: current device # 0 initialized OK
device mmc 0:1
1 bytes read in 919 ms (0 Bytes/s)
Found bootable drive on mmc 0
loading uImage ...
3154896 bytes read in 1425 ms (2.1 MiB/s)
loading uInitrd ...
7179935 bytes read in 1661 ms (4.1 MiB/s)
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtb ...
10246 bytes read in 2255 ms (3.9 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.4.0-kirkwood-tld-1
   Created:      2016-02-19   5:55:25 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3154832 Bytes = 3 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.4.0-kirkwood-tld-1
   Created:      2016-02-19   7:33:04 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7179871 Bytes = 6.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
   Booting using the fdt blob at 0x1c00000
   Loading Kernel Image ... OK
   Loading Ramdisk to 07435000, end 07b0de5f ... OK
   Loading Device Tree to 0742f000, end 07434805 ... OK
Using machid 0x831 from environment

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.4.0-kirkwood-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Mon Jan 25 20:35:24 PST 2016
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine model: Pogoplug v4
[    0.000000] Memory policy: Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 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: 113628K/131072K available (6007K kernel code, 573K rwdata, 1992K rodata, 296K init, 312K bss, 17444K reserved, 0K cma-reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xc8800000 - 0xff800000   ( 880 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc07d7ef4   (8000 kB)
[    0.000000]       .init : 0xc07d8000 - 0xc0822000   ( 296 kB)
[    0.000000]       .data : 0xc0822000 - 0xc08b169c   ( 574 kB)
[    0.000000]        .bss : 0xc08b169c - 0xc08ff9d0   ( 313 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]  Build-time adjustment of leaf fanout to 32.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 11467562657 ns
[    0.000014] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every 12884901885ns
[    0.000500] Console: colour dummy device 80x30
[    0.000548] Calibrating delay loop... 795.44 BogoMIPS (lpj=3977216)
[    0.090136] pid_max: default: 32768 minimum: 301
[    0.090298] Security Framework initialized
[    0.090414] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090444] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.091654] Initializing cgroup subsys io
[    0.091705] Initializing cgroup subsys devices
[    0.091743] Initializing cgroup subsys freezer
[    0.091792] Initializing cgroup subsys net_cls
[    0.091920] CPU: Testing write buffer coherency: ok
[    0.092629] Setting up static identity map for 0x8200 - 0x8258
[    0.093090] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[    0.098784] devtmpfs: initialized
[    0.105728] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.106430] prandom: seed boundary self test passed
[    0.112162] prandom: 100 self tests passed
[    0.112217] pinctrl core: initialized pinctrl subsystem
[    0.114350] NET: Registered protocol family 16
[    0.115066] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.140167] cpuidle: using governor ladder
[    0.170163] cpuidle: using governor menu
[    0.170799] Feroceon L2: Enabling L2
[    0.170864] Feroceon L2: Cache support initialised.
[    0.171429] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[    0.178999] No ATAGs?
[    0.212290] vgaarb: loaded
[    0.212810] usbcore: registered new interface driver usbfs
[    0.212927] usbcore: registered new interface driver hub
[    0.213045] usbcore: registered new device driver usb
[    0.214649] clocksource: Switched to clocksource orion_clocksource
[    0.296277] NET: Registered protocol family 2
[    0.297461] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.297500] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.297530] TCP: Hash tables configured (established 1024 bind 1024)
[    0.297632] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.297667] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.297944] NET: Registered protocol family 1
[    0.298527] RPC: Registered named UNIX socket transport module.
[    0.298545] RPC: Registered udp transport module.
[    0.298556] RPC: Registered tcp transport module.
[    0.298567] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.298969] Unpacking initramfs...
[    1.249136] Freeing initrd memory: 7012K (c7435000 - c7b0e000)
[    1.249323] NetWinder Floating Point Emulator V0.97 (double precision)
[    1.250942] futex hash table entries: 256 (order: -1, 3072 bytes)
[    1.251047] audit: initializing netlink subsys (disabled)
[    1.251122] audit: type=2000 audit(1.240:1): initialized
[    1.251623] Initialise system trusted keyring
[    1.252202] zbud: loaded
[    1.252623] VFS: Disk quotas dquot_6.6.0
[    1.252706] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.253495] NFS: Registering the id_resolver key type
[    1.253551] Key type id_resolver registered
[    1.253565] Key type id_legacy registered
[    1.253602] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.253623] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    1.253950] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    1.254776] Key type big_key registered
[    1.284002] Key type asymmetric registered
[    1.284035] Asymmetric key parser 'x509' registered
[    1.284182] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    1.284213] io scheduler noop registered
[    1.284236] io scheduler deadline registered
[    1.284328] io scheduler cfq registered (default)
[    1.285946] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 36
[    1.285970] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 37
[    1.285987] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 38
[    1.286006] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 39
[    1.286023] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 40
[    1.286041] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 41
[    1.286058] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 42
[    1.286075] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 43
[    1.286093] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 44
[    1.286111] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 45
[    1.286128] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 46
[    1.286145] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 47
[    1.286163] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 48
[    1.286180] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 49
[    1.286669] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[    1.287657] irq: Cannot allocate irq_descs @ IRQ34, assuming pre-allocated
[    1.288264] irq: Cannot allocate irq_descs @ IRQ66, assuming pre-allocated
[    1.289485] mvebu-pcie mbus:pcie-controller: PCI host bridge to bus 0000:00
[    1.289514] pci_bus 0000:00: root bus resource [io  0x1000-0xfffff]
[    1.289534] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[    1.289554] pci_bus 0000:00: root bus resource [bus 00-ff]
[    1.290139] PCI: bus0: Fast back to back transfers disabled
[    1.290177] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    1.290482] PCI: bus1: Fast back to back transfers enabled
[    1.290617] pci 0000:00:01.0: PCI bridge to [bus 01]
[    1.291093] mv_xor f1060800.xor: Marvell shared XOR driver
[    1.325696] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    1.326036] mv_xor f1060900.xor: Marvell shared XOR driver
[    1.365657] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    1.366368] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    1.368484] console [ttyS0] disabled
[    1.368574] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 25, base_baud = 10416666) is a 16550A
[    2.112886] console [ttyS0] enabled
[    2.118324] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[    2.124702] nand: Hynix H27U1G8F2BTR-BC
[    2.128529] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    2.136106] Scanning device for bad blocks
[    2.145862] Bad eraseblock 68 at 0x000000880000
[    2.229175] 4 cmdlinepart partitions found on MTD device orion_nand
[    2.235444] Creating 4 MTD partitions on "orion_nand":
[    2.240575] 0x000000000000-0x000000100000 : "u-boot"
[    2.247412] 0x000000100000-0x000000500000 : "uImage"
[    2.254118] 0x000000500000-0x000002500000 : "rootfs"
[    2.260964] 0x000002500000-0x000008000000 : "data"
[    2.269338] libphy: Fixed MDIO Bus: probed
[    2.273910] libphy: orion_mdio_bus: probed
[    2.285199] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    3.362856] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:00:00:00:00:00
[    3.371788] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    3.378364] ehci-pci: EHCI PCI platform driver
[    3.382901] ehci-orion: EHCI orion driver
[    3.387190] orion-ehci f1050000.ehci: EHCI Host Controller
[    3.392699] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    3.400590] orion-ehci f1050000.ehci: irq 29, io mem 0xf1050000
[    3.424697] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[    3.431001] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    3.437805] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.445032] usb usb1: Product: EHCI Host Controller
[    3.449896] usb usb1: Manufacturer: Linux 4.4.0-kirkwood-tld-1 ehci_hcd
[    3.456512] usb usb1: SerialNumber: f1050000.ehci
[    3.462323] hub 1-0:1.0: USB hub found
[    3.466186] hub 1-0:1.0: 1 port detected
[    3.471570] mousedev: PS/2 mouse device common for all mice
[    4.484693] rtc-mv f1010300.rtc: internal RTC not ticking
[    4.490375] i2c /dev entries driver
[    4.495728] hidraw: raw HID events driver (C) Jiri Kosina
[    4.501659] drop_monitor: Initializing network drop monitor service
[    4.508328] NET: Registered protocol family 17
[    4.513165] Key type dns_resolver registered
[    4.518679] registered taskstats version 1
[    4.522830] Loading compiled-in X.509 certificates
[    4.527732] zswap: loaded using pool lzo/zbud
[    4.545049] Key type encrypted registered
[    4.549847] hctosys: unable to open rtc device (rtc0)
[    4.558423] Freeing unused kernel memory: 296K (c07d8000 - c0822000)
Loading, please wait...
[    4.666065] systemd-udevd[82]: starting version 215
[    4.673760] random: systemd-udevd urandom read with 6 bits of entropy available
[    4.931252] SCSI subsystem initialized
[    4.954050] mvsdio f1090000.mvsdio: Got CD GPIO
[    5.033708] sata_mv f1080000.sata: slots 32 ports 1
[    5.068335] scsi host0: sata_mv
[    5.075869] mmc0: host does not support reading read-only switch, assuming write-enable
[    5.089912] ata1: SATA max UDMA/133 irq 32
[    5.094209] mmc0: new SD card at address bc6a
[    5.202932] mmcblk0: mmc0:bc6a SU02G 1.84 GiB
[    5.212312]  mmcblk0: p1
[    5.434719] ata1: SATA link down (SStatus 0 SControl F300)
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Checking root file system ... fsck from util-linux 2.25.2
rootfs was not cleanly unmounted, check forced.
rootfs: 14509/120720 files (6.2% non-contiguous), 139819/482670 blocks
fsck exited with status code 1
done.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
mount: mounting /sys on /root/sys failed: No such file or directory
switch_root: can't execute '/sbin/init': Accessing a corrupted shared library
[   21.076109] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[   21.076109]
[   21.085220] CPU: 0 PID: 1 Comm: switch_root Not tainted 4.4.0-kirkwood-tld-1 #1
[   21.092494] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[   21.098783] [<c0016784>] (unwind_backtrace) from [<c00129f8>] (show_stack+0x10/0x14)
[   21.106507] [<c00129f8>] (show_stack) from [<c00c2200>] (panic+0x80/0x214)
[   21.113368] [<c00c2200>] (panic) from [<c001fae4>] (do_exit+0x52c/0x978)
[   21.120050] [<c001fae4>] (do_exit) from [<c0021214>] (do_group_exit+0x4c/0xf0)
[   21.127247] [<c0021214>] (do_group_exit) from [<c00212c8>] (__wake_up_parent+0x0/0x18)
[   21.135135] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[   21.135135]
[   79.374685] random: nonblocking pool is initialized

Also I would like to save the envs in uboot console. But I do not know how.

-Wes
Re: PogoPlug Mobile SSH?
March 24, 2017 04:45AM
Wes,

There are 2 problems.

1.
Pogov4> setenv ethaddr xxxxxxxxxxxx
## Error: flags type check failure for "ethaddr" <= "xxxxxxxxxxxx" (type: m)
## Error inserting "ethaddr" variable, errno=1
This xxxxxxxxxxxx must be replaced with your real MAC address. I thought I covered this before several posts ago?

2.
mount: mounting /sys on /root/sys failed: No such file or directory
switch_root: can't execute '/sbin/init': Accessing a corrupted shared library
[   21.076109] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[   21.076109]
[   21.085220] CPU: 0 PID: 1 Comm: switch_root Not tainted 4.4.0-kirkwood-tld-1 #1
[   21.092494] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[   21.098783] [<c0016784>] (unwind_backtrace) from [<c00129f8>] (show_stack+0x10/0x14)
[   21.106507] [<c00129f8>] (show_stack) from [<c00c2200>] (panic+0x80/0x214)
[   21.113368] [<c00c2200>] (panic) from [<c001fae4>] (do_exit+0x52c/0x978)
[   21.120050] [<c001fae4>] (do_exit) from [<c0021214>] (do_group_exit+0x4c/0xf0)
[   21.127247] [<c0021214>] (do_group_exit) from [<c00212c8>] (__wake_up_parent+0x0/0x18)
[   21.135135] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
[   21.135135]
[   79.374685] random: nonblocking pool is initialized
This error indicated that your rootfs was created incorrectly. If you need helps, just go ahead and do that on another Linux box, and copy/paste the entire session while you are doing that here.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
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: