PogoPlug Mobile SSH?

Bodhi,

I'm curious as to what the optimal way to update my pogoplus is? I think I need to update everything, including uboot, kernal and Debian.

Thanks, Wes

Wes Wrote:
-------------------------------------------------------
> The SD card commands worked! You are a magician,
> haha. I guess I should try to either update Uboot
> and the Debian kernal at this stage? My final goal
> for the system, is as mentioned briefly, a NAS
> that can stream media and store files on a 750gb
> external HDD.

Your kernel is the latest now. So only the rootfs needs to be

apt-get update
apt-get upgrade

Your u-boot is not too old, but since you have serial console, you can recover from any problem in installing u-boot if you would make sure to try UART booting before installing new u-boot u-boot-2016.05: http://forum.doozan.com/read.php?3,12381

In the u-boot installation instruction:

Quote

Important Note: If possible, try to test this boot image with UART booting before flashing to NAND. See davygravy's UART booting using kwboot instruction here in this thread. The latest u-boot image released here should be used for UART booting, if your box is the type that supports it (these do not: Dockstar, Pogo E02, iConnect).

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

Wes,

- Kernel upgraded (4.8.3 is already latest)
- Debian upgrade
- u-boot uprade.

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

Bodhi,

I think I just bricked it, and It's all my fault for not wanting to ask anymore questions. I got an error on this part of the 2016.05 u-boot install "/usr/sbin/nandwrite -s 786432 /dev/mtd0 uboot.2016.05-tld-1.environment.img" and like a tired idiot decided rebooting would get me through it.

Here is the pastebin with my history and the error booting near the bottom. I'm going to get some rest for now, and try to learn more a different time. Thanks for all the help along the way though. Pastebin: http://pastebin.com/5ZHQ1p00

Hi Wes,

It happens to all of us, yours truly included :)

Recovering from this is not hard. You have not bricked it at all! You have flashed the new u-boot successfully. But now your envs are all messed up (because of the error while flashing that).

Now it's time to use the uEnv.txt to boot. This file will be read by u-boot during boot phase, and whatever envs in there will be used to overwrite what's in memory.

Booting with uEnv.txt:

- Plug in your Debian rootfs to another Linux box. I am assuming that you have Ubuntu or another Linux Desktop/Laptop or can boot with Linux Live CD.

- Mount it and go to the boot folder.I assume it was assigned the drive letter sdb1.

mount /dev/sdb1 /media/sdb1
cd /media/sdb1/boot

- Copy the env text file in the new u-boot tarball that you have downloaded before.

cp -a uboot.2016.05-tld-1.environment uEnv.txt

- modify the envs in uEnv.txt to use Pogo V4/Mobile settings

dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtb
arcNumber=3960
machid=F78

The rest of the envs can be adjusted later.

- Sync the drive and unmount

sync
umount /media/sdb1

Take it to the Pogo Mobile and boot. After booted back to Debian, you can try to flash the default envs image again. Post the output if there is any error, and don't reboot, just leave it running.

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

Hey Bodhi,

Today I went right to making a live Ubuntu stick, and booting my laptop into linux. I put the SD card in, and on the first command,

mount /dev/sdb1 /media/sdb1

I get the error

mount: mount point /media/sbd1 does not exist

I am attaching a screenshot of the files on the SD card just incase it might help. http://i.imgur.com/qt5lRIK.png

Wes,

Try:

mkdir -p /media/sdb1
mount /dev/sdb1 /media/sdb1

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

Bodhi,

The command

mkdir -p /media/sdb1

worked for me, but when I tried the command

mount /dev/sdb1 /media/sdb1

it returned

mount: special device /dev/sbd1 does not exist

I had thought maybe I had to create a partition for /dev/sdb1 as well, so I entered

mkdir -p /dev/sdb1

which worked, but when I tried to mount

mount /dev/sdb1 /media/sdb1

it gave me a line

mount:    /dev/sdb1 is not a block device

Wes,

The USB drive letter is assigned by the system. So when I wrote "/dev/sdb1" or "/media/sdb1" I meant: I assume that is what Ubuntu has assigned it. The drive letter will be different, depending on how many drives/partitions you already have in this box.

So do this:

Take out the stick, plug it back in, and then find out which drive letter was assigned:

dmesg | tail -20

And replace sdxx with that in the 2 commands to mount.

mkdir -p /media/sdxx
mount /dev/sdb1 /media/sdxx

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

Bodhi,

I think I got the drive letter, if I am reading correct, it is p1?

I am still running into problems at

cd /media/sdb1/boot

Here is a pastebin of me running all of the commands: http://pastebin.com/ng57mgar

Quote

Copy the env text file in the new u-boot tarball that you have downloaded before.

I am confused as to where I have downloaded the tarball, and if I need to copy it from my live linux system to the sd card, I do not know how to do that either.

Thanks,
Wes

Wes Wrote:
-------------------------------------------------------
> Bodhi,
>
> I think I got the drive letter, if I am reading
> correct, it is p1?
>
> I am still running into problems at

cd
> /media/sdb1/boot

Here is a pastebin of me
> running all of the commands:
> http://pastebin.com/ng57mgar
>
>
>

Quote

Copy the env text file in the new u-boot
> tarball that you have downloaded before.

>
> I am confused as to where I have downloaded the
> tarball, and if I need to copy it from my live
> linux system to the sd card, I do not know how to
> do that either.
>
> Thanks,
> Wes


Wes,

The drive letter is mmcblk0p1. So adjust it for the 2 commands:

mkdir -p /media/mmcblk0p1
mount /dev/mmcblk0p1 /media/mmcblk0p1

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

Bodhi,

I've ran into another problem at the next command. Pastebin: http://pastebin.com/egfmvaxm

Wes Wrote:
-------------------------------------------------------
> Bodhi,
>
> I've ran into another problem at the next command.
> Pastebin: http://pastebin.com/egfmvaxm

That environment file is in the uboot environment tarball that you have downloaded:
uboot.2016.05-tld-1.environment.bodhi.tar

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

Bodhi,

I think I have downloaded them onto the SD card / when I was using the pogo box, but is there any way to check? Or was I supposed to download it on my live linux boot?

Just incase I do not have it downloaded, would I just

wget --no-check-certificate https://www.dropbox.com/s/sn5w1a7dc71385p/uboot.2016.05-tld-1.pogo_v4.bodhi.tar#

On the correct machine to get it? Or is there a command to put it in a specific directory?

Thanks,
Wes

Bodhi,

I'm honestly perfectly fine if you want me to just start over, now that I have gone through the install process (mainly) this time I can install it faster and also install the correct, updated files. I'm only good at following guides and crashing brush with your help is really hard for me, haha.

-Wes

Wes,

On Ubuntu, go ahead and change directory to the SD card /boot folder

cd /media/mmcblk0p1/boot

Get the tarball

wget --no-check-certificate https://bitly.com/1sMwD7b -O uboot.2016.05-tld-1.environment.bodhi.tar

Extract the tarball

tar -xf uboot.2016.05-tld-1.environment.bodhi.tar

See if the files are all there:

ls -l | grep uboot.2016.05-tld-1

expected output:

-rw-r--r--  1 root root   2773 Jun 11 22:17 uboot.2016.05-tld-1.environment
-rw-r-----  1 root root 131072 Jun 11 22:22 uboot.2016.05-tld-1.environment.img
-rw-r-----  1 root root  65536 Jun 11 23:44 uboot.2016.05-tld-1.environment.64K.img
-rw-r--r--  1 root root 524288 Jun 12 13:44 uboot.2016.05-tld-1.pogo_v4.mtd0.kwb

Copy:

cd /media/mmcblk0p1/boot
cp -a uboot.2016.05-tld-1.environment uEnv.txt

Now, continue with editing the uEnv.txt file to adjust the 3 envs, like I posted above:
http://forum.doozan.com/read.php?2,28710,31212#msg-31212

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



Edited 1 time(s). Last edit at 11/27/2016 11:37PM by bodhi.

Bodhi,

I'm pretty sure all of the commands worked in the live linux machine (I wish there was a better way to get feedback from entering each command), here is the full pastebin log of that: http://pastebin.com/spvjf5hv

When I just booted the pogo with the SD card, I am getting the same error as before

ERROR: can't get kernel image!

Here is the pastebin of that if it matters: http://pastebin.com/cdVX9dV1

-Wes

Wes,

1.

> I'm pretty sure all of the commands worked in the
> live linux machine (I wish there was a better way
> to get feedback from entering each command), here
> is the full pastebin log of that:
> http://pastebin.com/spvjf5hv

You need to be root user while doing this. That's the permission error when you can't extract or copy files.

2.

> When I just booted the pogo with the SD card, I am
> getting the same error as before

ERROR: can't
> get kernel image!

Here is the pastebin of
> that if it matters: http://pastebin.com/cdVX9dV1
>

Of course, you can't boot because the uEnv.txt was not created successfully in number 1 above.

Try number 1 again after gaining root. However, if this is too difficult to get it done in a Live CD, let's go to plan B . I'll upload an envs script for you to run at u-boot prompt after interrupt it, and the commands to executed it.

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

Bodhi,

Now, when I plug the SD card into my live linux machine, I'm getting the error

Unable to mount rootfs

Here is a screenshot of the message: http://imgur.com/a/nIYfu

-Wes

Wes Wrote:
-------------------------------------------------------
> Bodhi,
>
> Now, when I plug the SD card into my live linux
> machine, I'm getting the error

Unable to
> mount rootfs

Here is a screenshot of the
> message: http://imgur.com/a/nIYfu
>
> -Wes

Wes,

The trouble you have is that you don't have a real Linux box, and the Live CD Ubuntu made learning how to do this quite cumbersome.

Let's go to plan B! plug in the SD card, power up, interrupt serial console and get the listing of the u-boot internal default envs:

printenv

And post the output here inside the post (don't post picture). Just copy/paste the text from your serial console terminal and paste here.

We are going to set a few envs on top of the internal default envs to get it to boot into Debian.

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



Edited 1 time(s). Last edit at 11/28/2016 02:16AM by bodhi.

Bodhi,

Here is the output from printenvs:

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
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Hit any key to stop autoboot:  0
Pogov4>

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
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Hit any key to stop autoboot:  0
Pogov4> printenv
arcNumber=3960
baudrate=115200
bootcmd=run bootcmd_uenv; run bootcmd_usb; reset
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
ethaddr=b6:d0:5e:0f:a1:17
led_error=orange blinking
led_exit=green off
led_init=green blinking
machid=f78
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M     (root)
partition=nand0,2
rootdelay=10
rootfstype=ext2
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$root     delay rootfstype=$rootfstype $mtdparts
stderr=serial
stdin=serial
stdout=serial
uenv_import=echo importing envs ...; env import -t 0x810000
uenv_load=usb start; mmc rescan; ide reset; setenv uenv_loaded 0; for devtype in      usb mmc ide; do for disknum in 0; do run uenv_read_disk; done; done
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknu     m:1 0x810000 /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_re     ad;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_boot=mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then boo     tm 0x800000 0x1100000; else bootm 0x800000; fi
usb_init=usb start
usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1

Environment size: 1574/131068 bytes
Pogov4>

I am also open to installing linux fully on my laptop if it has to be done.

-Wes

Wes,

Plug in the SD card, power up, and interrupt serial console, and then execute these commands (copy/paste each one to the u-boot prompt).

setenv set_bootargs_mmc 'setenv bootargs console=$console root=LABEL=rootfs  rootdelay=10 $mtdparts $custom_params'
setenv mmc_load_uimage 'load mmc 0:1 0x800000 /boot/uImage
setenv mmc_load_uinitrd 'load mmc 0:1 0x1100000 /boot/uInitrd
setenv mmc_load_dtb 'load mmc 0:1 0x1c00000 /boot/dts/kirkwood-pogoplug_v4.dtb'
setenv 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'
setenv bootcmd 'mmc rescan; run set_bootargs_mmc; run mmc_boot; reset'
boot

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

Bodhi,

The pogo booted correctly into Debian, and now as the forum thread is so long, I'm not sure where I should continue, haha.

-Wes

Cool :) OK now that you have a running system, start a new Debian thread when you have question while doing kernel upgrade. And start new U-boot thread when you have question while flashing the new default envs.

-----

Or you could just use the current system as is, to do what you want to do: set up a NAS. These installation can be postponed till later. However, you need to save the envs permanently, since you did a whole bunch of setenvs during boot, and those will disappear when you reboot the system. So reboot a few times to verify it works consistently. Then while in Debian, do it for real (basically the same commands, but using fw_setenv at Linux command line):

fw_setenv set_bootargs_mmc 'setenv bootargs console=$console root=LABEL=rootfs  rootdelay=10 $mtdparts $custom_params'
fw_setenv mmc_load_uimage 'load mmc 0:1 0x800000 /boot/uImage
fw_setenv mmc_load_uinitrd 'load mmc 0:1 0x1100000 /boot/uInitrd
fw_setenv mmc_load_dtb 'load mmc 0:1 0x1c00000 /boot/dts/kirkwood-pogoplug_v4.dtb'
fw_setenv 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'
fw_setenv bootcmd 'mmc rescan; run set_bootargs_mmc; run mmc_boot; reset'

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

Bodhi,

I'll probably start a new thread in the future if I want to go for updating the box, but unfortunately, I got another error when trying to set the envs in Debian permanently:

root@debian:~# fw_setenv set_bootargs_mmc 'setenv bootargs console=$console root    =LABEL=rootfs  rootdelay=10 $mtdparts $custom_params'
Warning: Bad CRC, using default environment

I continued on entering the other commands in the list, which none came of error. When I rebooted, the boot process worked up until

Uncompressing Linux... done, booting the kernel.

At which the system froze and I had to pull the power.

I tried re-entering the setenv commands in serial mode, but it still would not boot, stuck at the same place.

Agh I wish this thing would just work already! haha

-Wes

Wes,

Ah! I forgot :) my bad. You can't use fw_setenv until after you flashed the default envs image. For now, do the same step but add a saveenv:


Plug in the SD card, power up, and interrupt serial console, and then execute these commands (copy/paste each one to the u-boot prompt).

setenv set_bootargs_mmc 'setenv bootargs console=$console root=LABEL=rootfs  rootdelay=10 $mtdparts $custom_params'
setenv mmc_load_uimage 'load mmc 0:1 0x800000 /boot/uImage
setenv mmc_load_uinitrd 'load mmc 0:1 0x1100000 /boot/uInitrd
setenv mmc_load_dtb 'load mmc 0:1 0x1c00000 /boot/dts/kirkwood-pogoplug_v4.dtb'
setenv 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'
setenv bootcmd 'mmc rescan; run set_bootargs_mmc; run mmc_boot; reset'
saveenv
boot

This makes it permanent.

After booted into Debian, reboot and dont interrupt it, let it go and watch the serial console for any problem

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

Bodhi,

Hmm. the Pogo still seems to be stuck at the same place, even after using saveenv, here is the full log:

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> setenv set_bootargs_mmc 'setenv bootargs console=$console root=LABEL=roo   tfs  rootdelay=10 $mtdparts $custom_params'
Pogov4> setenv mmc_load_uimage 'load mmc 0:1 0x800000 /boot/uImage
> setenv mmc_load_uinitrd 'load mmc 0:1 0x1100000 /boot/uInitrd
Pogov4> setenv mmc_load_dtb 'load mmc 0:1 0x1c00000 /boot/dts/kirkwood-pogoplug_   v4.dtb'
Pogov4> setenv 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 0x   800000 - 0x1c00000; fi'
Pogov4> setenv bootcmd 'mmc rescan; run set_bootargs_mmc; run mmc_boot; reset'
Pogov4> saveenv
Saving Environment to NAND...
Erasing NAND...
Erasing at 0xc0000 -- 100% complete.
Writing to NAND... OK
Pogov4> boot

MMC rescan: current device # 0 initialized OK
3232368 bytes read in 1414 ms (2.2 MiB/s)
10266 bytes read in 4546 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,

- Take this SD card back to your Linux Live and run file system check.

e2fsck /dev/mmcblk0p1

and see if the label is rootfs

e2label /dev/mmcblk0p1

Note: if mmcblk0p1 does not exist then find it with

dmesg | tail -20

- After verify that it has no error. Bring it to the Pogo.

Power up. Interrupt serial console and

printenv
boot

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

Bodhi,

I went to enter the first command, but it gave me a warning

ubuntu@ubuntu:~$ e2fsck /dev/mmcblk0p1
e2fsck 1.42.13 (17-May-2015)
/dev/mmcblk0p1 is mounted.



WARNING!!!  The filesystem is mounted.   If you continue you ***WILL***
cause ***SEVERE*** filesystem damage.


Do you really want to continue<n>?

Should I continue or is there something else I have to do first?

-Wes

Wes Wrote:
-------------------------------------------------------
> Bodhi,
>
> I went to enter the first command, but it gave me
> a warning

ubuntu@ubuntu:~$ e2fsck
> /dev/mmcblk0p1
> e2fsck 1.42.13 (17-May-2015)
> /dev/mmcblk0p1 is mounted.
> 
> 
> 
> WARNING!!!  The filesystem is mounted.   If you
> continue you ***WILL***
> cause ***SEVERE*** filesystem damage.
> 
> 
> Do you really want to continue<n>?

>
> Should I continue or is there something else I
> have to do first?
>
> -Wes

Need to unmount it before you can do check disk.

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