Welcome! Log In Create A New Profile

Advanced

[SOLVED] Pogo Plug v4 blinks green then red and reboots (Thank you Bodhi)

Posted by pratikworld 
[SOLVED] Pogo Plug v4 blinks green then red and reboots (Thank you Bodhi)
August 01, 2015 01:26PM
Hi,
I followed archlinuxarm.org installation guide a couple of times.
But it failed on wget http://archlinuxarm.org/os/ArchLinuxARM-kirkwood-latest.tar.gz. So i created a fat drive with revert folder and rebooted.

Then I tried and went ahead with http://blog.qnology.com/2014/07/hacking-pogoplug-v4-series-4-and-mobile.html

I could only go through to this command:
#SET MACADDRESS
/tmp/fw_setenv ethaddr "$(cat /sys/class/net/eth0/address)"

I replaced "address" with my MAC of the pogo plug. But I didn't put ":" (colons) after every 2 digits. So it gave me an error. And I panicked and rebooted.

Ever since its stuck on a boot loop. I tried everything from power cycling to fat32 drive with revert folder. But it doesn't seem to work.

What are my options now? Do I need to get a serial cable? If so will this work instead of CA-42:
http://www.ebay.in/itm/CP2102-USB-2-0-to-TTL-UART-Serial-Converter-KG074-/111724738805?hash=item1a035038f5

I did all this on a mac. But I have a dual boot system (Win+Mac). If I need to use Putty please link me a tutorial. Do I need to manually enter commands or is it an executable script?

Please help me out guys.
Re: Pogo Plug v4 blinks green then red and reboots
August 01, 2015 01:50PM
pratikworld,

> Ever since its stuck on a boot loop. I tried
> everything from power cycling to fat32 drive with
> revert folder. But it doesn't seem to work.

What is the LED behavior in the boot loop? does it flash green, then flashing red, then flashing green again? please describe it. And if you have a log of what you've done so far, then post it here, or pastebin it.

>
> What are my options now? Do I need to get a serial
> cable? If so will this work instead of CA-42:
> http://www.ebay.in/itm/CP2102-USB-2-0-to-TTL-UART-
> Serial-Converter-KG074-/111724738805?hash=item1a03
> 5038f5

Yes this will work. Depending on how far your installation went. This might be the only way to recover. Again, the installation log would be helpful to determine this.

>
> I did all this on a mac. But I have a dual boot
> system (Win+Mac). If I need to use Putty please
> link me a tutorial. Do I need to manually enter
> commands or is it an executable script?

Putty is self explanatory, when you run it you will see what need to be done. Here is a very good instruction from varkey (for GoFlex Net):
http://varkey.in/seagate-goflex-net-serial-connection/

If you're not sure, post back after you've connected serial console.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Pogo Plug v4 blinks green then red and reboots
August 01, 2015 10:32PM
bodhi Wrote:
-------------------------------------------------------

> What is the LED behavior in the boot loop? does
> it flash green, then flashing red, then flashing
> green again? please describe it. And if you have a
> log of what you've done so far, then post it here,
> or pastebin it.
>
Thanks for the quick reply. When I turn the power on it blinks green for like 5 seconds. Then blinks red for 2 seconds. And the light goes completely off for 2 secs. Then again the green for 5 secs. this keeps on happening.
I was following this tutorial: http://blog.qnology.com/2014/07/hacking-pogoplug-v4-series-4-and-mobile.html

And I went on till this point:

#stop my.pogoplug.com service
killall hbwd

#download firmware utilities
cd /tmp
wget http://download.qnology.com/pogoplug/v4/nanddump
wget http://download.qnology.com/pogoplug/v4/nandwrite
wget http://download.qnology.com/pogoplug/v4/flash_erase
wget http://download.qnology.com/pogoplug/v4/fw_printenv
wget http://download.qnology.com/pogoplug/v4/fw_setenv

#make execuable
chmod +x flash_erase fw_printenv fw_setenv nanddump nandwrite

#remount '/' as read/write
#by default the Pogoplug OS (internal flash) is read only
#skip if running from Debian/ALARM
mount -o remount,rw /

#setup fw_env.config
echo "/dev/mtd0 0xc0000 0x20000 0x20000">/etc/fw_env.config


Download and Flash new uBoot

#download uboot and md5
wget http://download.qnology.com/pogoplug/v4/uboot.2014.07-tld-1.pogo_v4.bodhi.tar
wget http://download.qnology.com/pogoplug/v4/uboot.2014.07-tld-1.pogo_v4.bodhi.tar.md5

#check md5sum
md5sum -c uboot.2014.07-tld-1.pogo_v4.bodhi.tar.md5

#extract uboot
tar -xf uboot.2014.07-tld-1.pogo_v4.bodhi.tar

#Erase and flash uboot on mtd0
#BE EXTRA CAREFUL WITH THE NEXT TWO COMMANDS. NO TYPOS! CUT AND PASTE.
/tmp/flash_erase /dev/mtd0 0 4
/tmp/nandwrite /dev/mtd0 /tmp/uboot.2014.07-tld-1.pogo_v4.mtd0.kwb


Download and Flash uBoot Environment Parameters

#download default uboot env settings and md5
wget http://download.qnology.com/pogoplug/v4/uboot.2014.07-tld-1.environment.img.bodhi.tar
wget http://download.qnology.com/pogoplug/v4/uboot.2014.07-tld-1.environment.img.bodhi.tar.md5

#check md5 sum
md5sum -c uboot.2014.07-tld-1.environment.img.bodhi.tar.md5

#extract uboot env settings
tar -xf uboot.2014.07-tld-1.environment.img.bodhi.tar

#Flash default uboot env setting
#BE EXTRA CAREFUL WITH THE NEXT TWO COMMANDS. NO TYPOS! CUT AND PASTE.
/tmp/flash_erase /dev/mtd0 0xc0000 1
/tmp/nandwrite -s 786432 /dev/mtd0 uboot.2014.07-tld-1.environment.img


Update uBoot Environment Parameters

#SET MACADDRESS
/tmp/fw_setenv ethaddr "$(cat /sys/class/net/eth0/address)"

Re: Pogo Plug v4 blinks green then red and reboots
August 02, 2015 02:01AM
pratikworld,

Ok, so you actually bailed out in the middle of the installation :) Fortunately, the command to set the MAC Address failed, so there is hope. However, the rest of the u-boot envs were not set (arcNumber, machid, and few other envs). The good thing is you've done the step about flashing u-boot envs.


At this point, I would try this as a best chance to get it boot Debian (it might boot OK even with the missing u-boot envs):

- Go to the kernel and rootfs thread and download the rootfs
Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2
This rootf is in this section

Quote

Updated 24 Feb 2015:

This rootfs is the first Debian jessie rootfs in my Kirkwood kernel/rootfs release series, and to keep in sync with kernel Linux-3.18.5-kirkwood-tld-1.

And on another Linux box (if you don't have one, download Linux Live CD and boot it on Mac/PC). Follow the instruction to create the 3.18.5 rootfs on a USB stick.

Note about step 4 in this installation section, you want to use the DTB for the Pogo V4:

Quote

4. Create uImage with embbeded DTB (If this is not first time installation, please see Note 2 below).
..
cat dts/kirkwood-pogoplug_v4.dtb >> zImage.fdt

And after it's done, take this USB rootfs to your Pogo V4 and power up with it. Observe the LED light behavior and record it. Look for the dynamic IP of the Pogo V4 to appear in the network router, or use some scanning apps such as Linux nmap or IOS Fing to find it. Hopefully you will!

If you're not sure about some steps, post question. Or you can prepare the steps as you understand, and post the whole procedure here, so I can verify it for you.

If this does not work, don't worry. Once you've connected serial console, this will be solved for sure.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Pogo Plug v4 blinks green then red and reboots
August 03, 2015 07:45AM
Hi Bodhi,
So I followed the tutorial. But I'm getting some errors on the second step. Also am I entering the third command correctly?

ubuntu@ubuntu:~$ cd /media/sdb1
ubuntu@ubuntu:/media/sdb1$ tar -xjf Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2
tar: ./dev/mem: Cannot mknod: Operation not permitted
tar: ./dev/loop4: Cannot mknod: Operation not permitted
tar: ./dev/port: Cannot mknod: Operation not permitted
tar: ./dev/loop1: Cannot mknod: Operation not permitted
tar: ./dev/ram8: Cannot mknod: Operation not permitted
tar: ./dev/ram11: Cannot mknod: Operation not permitted
tar: ./dev/ram16: Cannot mknod: Operation not permitted
tar: ./dev/ram1: Cannot mknod: Operation not permitted
tar: ./dev/ram14: Cannot mknod: Operation not permitted
tar: ./dev/tty: Cannot mknod: Operation not permitted
tar: ./dev/kmem: Cannot mknod: Operation not permitted
tar: ./dev/ram0: Cannot mknod: Operation not permitted
tar: ./dev/ram2: Cannot mknod: Operation not permitted
tar: ./dev/loop6: Cannot mknod: Operation not permitted
tar: ./dev/ram13: Cannot mknod: Operation not permitted
tar: ./dev/zero: Cannot mknod: Operation not permitted
tar: ./dev/ram6: Cannot mknod: Operation not permitted
tar: ./dev/ram15: Cannot mknod: Operation not permitted
tar: ./dev/loop7: Cannot mknod: Operation not permitted
tar: ./dev/tty0: Cannot mknod: Operation not permitted
tar: ./dev/loop5: Cannot mknod: Operation not permitted
tar: ./dev/loop3: Cannot mknod: Operation not permitted
tar: ./dev/urandom: Cannot mknod: Operation not permitted
tar: ./dev/ram10: Cannot mknod: Operation not permitted
tar: ./dev/console: Cannot mknod: Operation not permitted
tar: ./dev/ram12: Cannot mknod: Operation not permitted
tar: ./dev/random: Cannot mknod: Operation not permitted
tar: ./dev/loop2: Cannot mknod: Operation not permitted
tar: ./dev/full: Cannot mknod: Operation not permitted
tar: ./dev/ptmx: Cannot mknod: Operation not permitted
tar: ./dev/ram7: Cannot mknod: Operation not permitted
tar: ./dev/null: Cannot mknod: Operation not permitted
tar: ./dev/ram5: Cannot mknod: Operation not permitted
tar: ./dev/ram9: Cannot mknod: Operation not permitted
tar: ./dev/ram3: Cannot mknod: Operation not permitted
tar: ./dev/loop0: Cannot mknod: Operation not permitted
tar: ./dev/ram4: Cannot mknod: Operation not permitted
tar: ./lost+found: Cannot utime: Operation not permitted
tar: Exiting with failure status due to previous errors
ubuntu@ubuntu:/media/sdb1$ /dev/sdd1 /media/sdb1/etc/fstab ext2 noatime,errors=remount-ro 0 1
bash: /dev/sdd1: Permission denied
ubuntu@ubuntu:/media/sdb1$ 

Re: Pogo Plug v4 blinks green then red and reboots
August 03, 2015 02:08PM
Hey Bodhi,
Never mind. I figured it out. I got in as root user and went through step 2 successfully.

Now at step 3 it still showed "Permission denied" even when I copy pasted the command.

But I didn't bail this time. I went ahead with step 4 which went without any errors.

I connected the pen drive to the plug and cold booted. It blinks green for a while, becomes yellow and then steady green throughout.
But I'm not able to see the plug on my dhcp anywhere. Also the ethernet light is on steady yellow behind the plug.
When I boot both green and yellow blink on the ethernet. But after the front gets steady green, the back ethernet only shows yellow.

Please help. Is this because of the error in step 3? If so what is the exact command that should be executed?

Thanks a lot for your help and support.
Re: Pogo Plug v4 blinks green then red and reboots
August 03, 2015 03:14PM
pratikworld,

> Please help. Is this because of the error in step
> 3? If so what is the exact command that should be
> executed?

Yes. The solid greenLED is a good sign (kernel has started). But later the kernel has trouble mounting rootfs (because the errors in step 3). The error in step 3 is usually because you're not root user. You have to be root the entire time while you're extracting the rootfs. So it's best that you log in with "sudo su" first.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Pogo Plug v4 blinks green then red and reboots
August 03, 2015 09:19PM
Its still giving the same error. Please have a look
ubuntu@ubuntu:~$ sudo su
root@ubuntu:/home/ubuntu# mount /dev/sdc1 /media/sdb1
root@ubuntu:/home/ubuntu# cd /media/sdb1
root@ubuntu:/media/sdb1# tar -xjf Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2
root@ubuntu:/media/sdb1# /dev/root      /               ext2    noatime,errors=remount-ro 0 1
bash: /dev/root: No such file or directory
root@ubuntu:/media/sdb1# /dev/sdc1      /               ext2    noatime,errors=remount-ro 0 1
bash: /dev/sdc1: Permission denied
root@ubuntu:/media/sdb1# /dev/sdc      /               ext2    noatime,errors=remount-ro 0 1
bash: /dev/sdc: Permission denied

Re: Pogo Plug v4 blinks green then red and reboots
August 03, 2015 09:56PM
pratikworld,

This is all you need to do (if the sdb1 is the USB drive that you want to create the rootfs on).
sudo su
mount /media/sdb1
cd /media/sdb1
tar -xjf Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2
sync

And then do the rest of the installation, including modified step 4:
Quote

4. Create uImage with embbeded DTB (If this is not first time installation, please see Note 2 below).

cat dts/kirkwood-pogoplug_v4.dtb >> zImage.fdt

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



Edited 4 time(s). Last edit at 08/03/2015 10:04PM by bodhi.
Re: Pogo Plug v4 blinks green then red and reboots
August 04, 2015 11:49AM
Hey Bodhi,
Stuck with a new error now.
ubuntu@ubuntu:~$ sudo su
root@ubuntu:/home/ubuntu# mount /media/sdb1
mount: mount point /media/sdb1 does not exist
root@ubuntu:/home/ubuntu# mount /media/sdb1
mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

Then I tried entering the following codes after googling.
root@ubuntu:/home/ubuntu# # e2fsck -f /dev/sdc1
root@ubuntu:/home/ubuntu# # mke2fs -n /dev/sdc1
root@ubuntu:/home/ubuntu# # e2fsck -f -b 8193 /dev/sdc1
root@ubuntu:/home/ubuntu# sudo e2fsck -f -b 32768 -y /dev/sdc1
e2fsck 1.42.9 (4-Feb-2014)
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: ***** FILE SYSTEM WAS MODIFIED *****
rootfs: 11/475776 files (0.0% non-contiguous), 66855/1902968 blocks
root@ubuntu:/home/ubuntu# mount /media/sdb1/
mount: can't find /media/sdb1/ in /etc/fstab or /etc/mtab
root@ubuntu:/home/ubuntu# mount /media/sdb1
mount: can't find /media/sdb1 in /etc/fstab or /etc/mtab

Please help. I can't tell you how much I appreciate your help. :)
Re: Pogo Plug v4 blinks green then red and reboots
August 04, 2015 11:54AM
Also when I try and mount it in Disk Utility of Ubuntu it gives me the following error:

"Error mounting system-managed device /dev/sdc1: Command-line `mount "/media/sdb1/rootfs"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdc1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

(udisks-error-quark, 0)"


Here's how I created the thumb drive.

I go into disk utility, select my pen drive and delete partition. Then I create a new partition by clicking the plus button.
Then I select DONT OVERWRITE EXISTING DATA. under type: CUSTOM. name: rootfs. And filesystem:ext3. I have to manully type in ext3. Then I click create.
After that I click on the gear menu -> edit mount options.
I turn Automatic mount options off. Enter MOUNT POINT: /media/sdb1 or /media/sdb1/rootfs (tried both). click OK.

Then when I press the play button to mount the drive it gives me the above error.

I can only mount the drive via the follwing command
mount /dev/sdc1 /media/sdb1



Edited 1 time(s). Last edit at 08/04/2015 12:01PM by pratikworld.
Re: Pogo Plug v4 blinks green then red and reboots
August 04, 2015 02:52PM
pratikworld,

When you plug the USB stick into Ubuntu (or any Linux system), it will be assigned a mount letter. It could be: sda1, sdb1, sdc1, sdd1, ..... So that is the drive you need to use in the instruction. So if you format the drive like this successfully, then it must have been assigned as sdc1:
root@ubuntu:/home/ubuntu# # e2fsck -f /dev/sdc1
root@ubuntu:/home/ubuntu# # mke2fs -n /dev/sdc1
root@ubuntu:/home/ubuntu# # e2fsck -f -b 8193 /dev/sdc1
root@ubuntu:/home/ubuntu# sudo e2fsck -f -b 32768 -y /dev/sdc1

Then the sdb1 drive letter in the following commands should be replaced with sdc1. But the mount point in your Ubuntu system might have been: /mnt/sdc1. You have to find out what is the mount point and use it below (/media/sdb1 is an example of a typical mountpoint).
sudo su
cd /media/sdb1 
tar -xjf Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2

cd /media/sdb1/boot
cp -a zImage-3.18.5-kirkwood-tld-1  zImage.fdt
cat dts/kirkwood-pogoplug_v4.dtb  >> zImage.fdt
mv uImage uImage.orig
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.18.5-kirkwood-tld-1 -d zImage.fdt uImage
sync


Note that you have to do everything as root user. Not using sudo.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Pogo Plug v4 blinks green then red and reboots
August 04, 2015 03:43PM
I'm really sorry bodhi. But I'm not able to get it. How do I become root user, other than sudo su?
I'm a complete noobie, just know a few abbreviations. Please guide me. I did all the steps you described. Here:
root@ubuntu:~# e2fsck -f /dev/sde1
e2fsck 1.42.9 (4-Feb-2014)
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: 11/475776 files (0.0% non-contiguous), 66855/1902968 blocks
root@ubuntu:~# mke2fs -n /dev/sde1
mke2fs 1.42.9 (4-Feb-2014)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
475776 inodes, 1902968 blocks
95148 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1950351360
59 block groups
32768 blocks per group, 32768 fragments per group
8064 inodes per group
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

root@ubuntu:~# e2fsck -f -b 8193 /dev/sde1
e2fsck 1.42.9 (4-Feb-2014)
e2fsck: Bad magic number in super-block while trying to open /dev/sde1

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem.  If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 or
    e2fsck -b 32768 <device>

root@ubuntu:~# sudo e2fsck -f -b 32768 -y /dev/sde1
e2fsck 1.42.9 (4-Feb-2014)
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: ***** FILE SYSTEM WAS MODIFIED *****
rootfs: 11/475776 files (0.0% non-contiguous), 66855/1902968 blocks

Then I followed the link you sent me. Also attaching screengrabs of my disk utility. Please consider that I'm running ubuntu off a live usb.

root@ubuntu:~# cd /media/ubuntu/rootfs
root@ubuntu:/media/ubuntu/rootfs# tar -xjf Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2
root@ubuntu:/media/ubuntu/rootfs# /dev/sde1      /               ext2    noatime,errors=remount-ro 0 1
-bash: /dev/sde1: Permission denied
root@ubuntu:/media/ubuntu/rootfs# 

Attachments:
open | download - Screenshot from 2015-08-04 20:25:25.png (83.5 KB)
open | download - Screenshot from 2015-08-04 20:25:46.png (53.8 KB)
Re: Pogo Plug v4 blinks green then red and reboots
August 04, 2015 06:05PM
Please reread the installation instruction.

This is not a command to execute:
 /dev/sde1      /               ext2    noatime,errors=remount-ro 0 1

Actually, you can skip step 3. It is not necessary to do it now.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Pogo Plug v4 blinks green then red and reboots
August 04, 2015 07:23PM
pratikworld Wrote:
-------------------------------------------------------
>
> I could only go through to this command:
> #SET MACADDRESS
> /tmp/fw_setenv ethaddr "$(cat /sys/class/net/eth0/address)"
>
> I replaced "address" with my MAC of the pogo plug.
> But I didn't put ":" (colons) after every 2
> digits. So it gave me an error. And I panicked and
> rebooted.

FYI @pratikworld, you should have ran the command as is (cut/paste) like everything else in the tutorial. Not sure why you would change "address" with your MAC address when nothing of the sort was stated. I even provided a console log incase there was any confusion on the commands or it's output as a reference. Sorry, don't mean to be too harsh, just wanted to point out the mistake.

At any rate, all you really need to do is create a USB drive with the Debian rootfs and you should be fine. No need for a serial connection at this point.

I would recommend going with Debian-3.14.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 for the rootfs which is a little simpler since it doesn't require the fdt file and some of the extra commands.

-grayman4hire
======================================
Pogoplug V2 and V3 Serial Connection
Tutorial - Pogoplug v4 (Series 4 and Mobile) with Linux (Debian or Arch)

OpenWRT on Pogoplug Mobile
Tutorial - Pogoplug E02/V4 with Arch Linux ARM
Hacking the Pogoplug v3/Oxnas (Pro/Classic) with Debian

OpenWRT on Pogoplug v3/Oxnas (Pro/Classic)
Re: Pogo Plug v4 blinks green then red and reboots
August 04, 2015 08:08PM
Thanks for jumping in to help, gray!

There is small possibility that 3.14 or 3.16 will not work in this case (some envs are missing). So I played it safe and recommended 3.18 rootfs :) But it's true, I always recommend 3.16 rootfs because it is simpler.

Edit: typo

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



Edited 1 time(s). Last edit at 08/04/2015 10:34PM by bodhi.
Re: Pogo Plug v4 blinks green then red and reboots
August 06, 2015 09:26AM
grayman4hire Wrote:
-------------------------------------------------------
> pratikworld Wrote:
> --------------------------------------------------
> -----
> >
> > I could only go through to this command:
> > #SET MACADDRESS
> > /tmp/fw_setenv ethaddr "$(cat
> /sys/class/net/eth0/address)"
> >
> > I replaced "address" with my MAC of the pogo
> plug.
> > But I didn't put ":" (colons) after every 2
> > digits. So it gave me an error. And I panicked
> and
> > rebooted.
>
> FYI @pratikworld, you should have ran the command
> as is (cut/paste) like everything else in the
> tutorial. Not sure why you would change "address"
> with your MAC address when nothing of the sort was
> stated. I even provided a console log incase there
> was any confusion on the commands or it's output
> as a reference. Sorry, don't mean to be too harsh,
> just wanted to point out the mistake.

Hey grayman4hire,
The thing was that the MACADRESS command gave me an error when I copied and pasted. Hence I got confused and tried to modify it.


I also tried installing 3.16
ubuntu@ubuntu:~$ sudo su
root@ubuntu:/home/ubuntu# cd /media/ubuntu/rootfs
root@ubuntu:/media/ubuntu/rootfs# tar -xjf Debian-3.16.0-kirkwood-tld-2-rootfs-bodhi.tar.bz2
root@ubuntu:/media/ubuntu/rootfs# sync
root@ubuntu:/media/ubuntu/rootfs#

Pogoplug gets stuck at yellow led in the front.


Installing 3.18 also went through
ubuntu@ubuntu:~$ sudo su
root@ubuntu:/home/ubuntu# cd /media/ubuntu/rootfsroot@ubuntu:/media/ubuntu/rootfs# tar -xjf /home/ubuntu/Downloads/Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2
root@ubuntu:/media/ubuntu/rootfs# cd /media/ubuntu/rootfs/bootroot@ubuntu:/media/ubuntu/rootfs/boot# cp -a zImage-3.18.5-kirkwood-tld-1  zImage.fdt
root@ubuntu:/media/ubuntu/rootfs/boot# 
root@ubuntu:/media/ubuntu/rootfs/boot# cat dts/kirkwood-pogoplug_v4.dtb  >> zImage.fdt
root@ubuntu:/media/ubuntu/rootfs/boot# mv uImage uImage.orig
root@ubuntu:/media/ubuntu/rootfs/boot# mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.18.5-kirkwood-tld-1 -d zImage.fdt uImage
The program 'mkimage' is currently not installed. You can install it by typing:
apt-get install u-boot-tools
root@ubuntu:/media/ubuntu/rootfs/boot# mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.18.5-kirkwood-tld-1 -d zImage.fdt uImage
 
Image Name:   Linux-3.18.5-kirkwood-tld-1
Created:      Thu Aug  6 05:31:57 2015
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    2875628 Bytes = 2808.23 kB = 2.74 MB
Load Address: 00008000
Entry Point:  00008000
root@ubuntu:/media/ubuntu/rootfs/boot# 
root@ubuntu:/media/ubuntu/rootfs/boot# sync
root@ubuntu:/media/ubuntu/rootfs/boot#

But still doesnt show up on my router.

Also, the first time I tried to install arch, it was on an SD card. Now we are trying to get it to boot from a USB. Does that make a difference?
I am plugging in the usb on the top slot.

Again, thank a lot for taking the time out to help me. You guys are the best. :)



Edited 1 time(s). Last edit at 08/06/2015 11:37AM by pratikworld.
Re: Pogo Plug v4 blinks green then red and reboots
August 06, 2015 01:44PM
"Pogoplug gets stuck at yellow led in the front." - This might be okay. Did you check your router if your Pogoplug received an IP Address (or used a IP network scanner tool) like Bodhi suggested?

-grayman4hire
======================================
Pogoplug V2 and V3 Serial Connection
Tutorial - Pogoplug v4 (Series 4 and Mobile) with Linux (Debian or Arch)

OpenWRT on Pogoplug Mobile
Tutorial - Pogoplug E02/V4 with Arch Linux ARM
Hacking the Pogoplug v3/Oxnas (Pro/Classic) with Debian

OpenWRT on Pogoplug v3/Oxnas (Pro/Classic)
Re: Pogo Plug v4 blinks green then red and reboots
August 06, 2015 01:48PM
I did. It doesn't show up. :(
Should I try 3.14 as well?
Re: Pogo Plug v4 blinks green then red and reboots
August 06, 2015 01:53PM
pratikworld Wrote:
-------------------------------------------------------
> I did. It doesn't show up. :(
> Should I try 3.14 as well?

Yeah, it wouldn't hurt. Also are you using ext2 or ext3? Try both.

-grayman4hire
======================================
Pogoplug V2 and V3 Serial Connection
Tutorial - Pogoplug v4 (Series 4 and Mobile) with Linux (Debian or Arch)

OpenWRT on Pogoplug Mobile
Tutorial - Pogoplug E02/V4 with Arch Linux ARM
Hacking the Pogoplug v3/Oxnas (Pro/Classic) with Debian

OpenWRT on Pogoplug v3/Oxnas (Pro/Classic)
Re: Pogo Plug v4 blinks green then red and reboots
August 06, 2015 02:00PM
I'm using ext3.
Will try and update. Thanks.
Re: Pogo Plug v4 blinks green then red and reboots
August 06, 2015 03:16PM
As I've mentioned, the 3.14 and 3.16 rootfs might not work because of missing envs. If you can't get it boot then try 3.18 rootfs.

If neither works then serial console will solve it.

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



Edited 1 time(s). Last edit at 08/06/2015 03:18PM by bodhi.
Re: Pogo Plug v4 blinks green then red and reboots
August 07, 2015 01:47PM
So I tried everything that you guys suggested.

ext2 with 3.14 stayed on yellow led in the front, But the ethernet had both the LEDs blinking. So that was a progress in a way. But didnt show up in my dhcp clients. Neither on the Fing app.

ext2 with 3.18.5 also stayed on yellow. The ethernet port also was stuck on yellow light.

Then again I flashed with ext3 with 3.18.5. Now even that is stuck on yellow led in the front.

Now I also have the CP2102 serial cable soldered on the board. http://bit.ly/1eY1sOL

Please guide me how to proceed further.
Re: Pogo Plug v4 blinks green then red and reboots
August 07, 2015 02:44PM
pratikworld,

> Now I also have the CP2102 serial cable soldered
> on the board. http://bit.ly/1eY1sOL
>
> Please guide me how to proceed further.

Connect the serial console to your PC running WIndows/OSX/Linux. See varkey setup:
http://varkey.in/seagate-goflex-net-serial-connection/

- Plug in the current USB rootfs that you created (whether it's 3.14, 3.16 or 3.18, does not matter).
- Power up the Pogo and watch the boot log. Capture the boot and post it here.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Pogo Plug v4 blinks green then red and reboots
August 07, 2015 05:36PM
I tried in Putty as well as Ubuntu. The cursor stops blinking when I plug in the power. But nothing happens. There is no log. I checked all the connectors. They are perfectly in place.
The drivers load fine as well. I can change port numbers and all.

Do I have a bad converter?
Re: Pogo Plug v4 blinks green then red and reboots
August 07, 2015 06:01PM
pratikworld Wrote:
-------------------------------------------------------
> I tried in Putty as well as Ubuntu. The cursor
> stops blinking when I plug in the power. But
> nothing happens. There is no log. I checked all
> the connectors. They are perfectly in place.
> The drivers load fine as well. I can change port
> numbers and all.
>
> Do I have a bad converter?

Try switching TX and RX. This CPxxxx converter pins are already crossed. So Pogo TX should be connected to the converter TX.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Pogo Plug v4 blinks green then red and reboots
August 08, 2015 12:12AM
bodhi Wrote:
-------------------------------------------------------

> Try switching TX and RX.

Alright Bodhi. That worked brilliantly. Heres the log of booting thumb drive on 3.14
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2015.08.08 10:38:16 =~=~=~=~=~=~=~=~=~=~=~=
ÿ  

U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45)
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
Warning: failed to set MAC address

Hit any key to stop autoboot: 10  9  8  7  6  5  4  3  2  1  0 
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
2461416 bytes read in 368 ms (6.4 MiB/s)
6362802 bytes read in 491 ms (12.4 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.14.0-kirkwood-tld-1
   Created:      2014-04-06  20:44:27 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2461352 Bytes = 2.3 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.14.0-kirkwood-tld-1
   Created:      2014-04-06  20:44:41 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6362738 Bytes = 6.1 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... 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 3.14.0-kirkwood-tld-1 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 PREEMPT Tue Apr 1 22:54:58 PDT 2014
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Marvell SheevaPlug Reference Board
[    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=/dev/sda1 rootdelay=10 rootfstype=ext3 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: 116244K/131072K available (4779K kernel code, 352K rwdata, 1644K rodata, 213K init, 424K bss, 14828K 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 - 0xc064df14   (6424 kB)
[    0.000000]       .init : 0xc064e000 - 0xc0683444   ( 214 kB)
[    0.000000]       .data : 0xc0684000 - 0xc06dc3c4   ( 353 kB)
[    0.000000]        .bss : 0xc06dc3c4 - 0xc074665c   ( 425 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:114
[    0.000018] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every 25769803770ns
[    8.019893] Console: colour dummy device 80x30
[    8.019940] Calibrating delay loop... 795.44 BogoMIPS (lpj=3977216)
[    8.109532] pid_max: default: 32768 minimum: 301
[    8.109692] Security Framework initialized
[    8.109790] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    8.109818] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    8.110705] Initializing cgroup subsys devices
[    8.110742] Initializing cgroup subsys freezer
[    8.110762] Initializing cgroup subsys net_cls
[    8.110777] Initializing cgroup subsys blkio
[    8.110892] CPU: Testing write buffer coherency: ok
[    8.111469] Setting up static identity map for 0x485fa0 - 0x485fdc
[    8.114641] devtmpfs: initialized
[    8.118636] prandom: seed boundary self test passed
[    8.124696] prandom: 100 self tests passed
[    8.124716] pinctrl core: initialized pinctrl subsystem
[    8.125276] regulator-dummy: no parameters
[    8.125778] NET: Registered protocol family 16
[    8.126456] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    8.127641] cpuidle: using governor ladder
[    8.127667] cpuidle: using governor menu
[    8.127841] Kirkwood: MV88F6281-A1, TCLK=166666667.
[    8.127872] Feroceon L2: Enabling L2
[    8.127924] Feroceon L2: Cache support initialised.
[    8.135710] bio: create slab <bio-0> at 0
[    8.136347] vgaarb: loaded
[    8.136765] usbcore: registered new interface driver usbfs
[    8.136873] usbcore: registered new interface driver hub
[    8.137037] usbcore: registered new device driver usb
[    8.138103] Switched to clocksource orion_clocksource
[    8.173536] NET: Registered protocol family 2
[    8.174455] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    8.174493] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    8.174523] TCP: Hash tables configured (established 1024 bind 1024)
[    8.174627] TCP: reno registered
[    8.174649] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    8.174680] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    8.174957] NET: Registered protocol family 1
[    8.175409] RPC: Registered named UNIX socket transport module.
[    8.175425] RPC: Registered udp transport module.
[    8.175435] RPC: Registered tcp transport module.
[    8.175445] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    8.175805] Unpacking initramfs...
[    8.951858] Freeing initrd memory: 6208K (c1101000 - c1711000)
[    8.952021] NetWinder Floating Point Emulator V0.97 (double precision)
[    8.952815] futex hash table entries: 256 (order: -1, 3072 bytes)
[    8.953039] audit: initializing netlink subsys (disabled)
[    8.953116] audit: type=2000 audit(0.920:1): initialized
[    8.954068] bounce pool size: 64 pages
[    8.954166] zbud: loaded
[    8.954419] VFS: Disk quotas dquot_6.5.2
[    8.954495] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    8.954907] NFS: Registering the id_resolver key type
[    8.955005] Key type id_resolver registered
[    8.955018] Key type id_legacy registered
[    8.955044] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    8.955057] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    8.955282] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    8.955682] msgmni has been set to 239
[    8.955854] Key type big_key registered
[    8.958583] alg: No test for stdrng (krng)
[    8.958716] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    8.958732] io scheduler noop registered
[    8.958743] io scheduler deadline registered
[    8.958786] io scheduler cfq registered (default)
[    8.959160] mv_xor mv_xor.0: Marvell shared XOR driver
[    8.998191] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[    9.038183] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[    9.038353] mv_xor mv_xor.1: Marvell shared XOR driver
[    9.078193] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[    9.118190] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[    9.118614] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    9.139492] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33, base_baud = 10416666) is a 16550A
[    9.683422] console [ttyS0] enabled
[    9.688381] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[    9.694709] nand: Hynix H27U1G8F2BTR-BC
[    9.698550] nand: 128MiB, SLC, page size: 2048, OOB size: 64
[    9.704195] Scanning device for bad blocks
[    9.821495] 4 cmdlinepart partitions found on MTD device orion_nand
[    9.827741] Creating 4 MTD partitions on "orion_nand":
[    9.832884] 0x000000000000-0x000000100000 : "u-boot"
[    9.838272] 0x000000100000-0x000000500000 : "uImage"
[    9.843582] 0x000000500000-0x000002500000 : "rootfs"
[    9.848978] 0x000002500000-0x000008000000 : "data"
[    9.855121] libphy: Fixed MDIO Bus: probed
[    9.874702] libphy: orion_mdio_bus: probed
[    9.878982] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[   10.956475] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:00:00:00:00:00
[   10.965456] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   10.971988] ehci-pci: EHCI PCI platform driver
[   10.976495] ehci-orion: EHCI orion driver
[   10.980610] orion-ehci orion-ehci.0: EHCI Host Controller
[   10.986016] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[   10.993746] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[   11.018149] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[   11.024298] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   11.031092] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   11.038306] usb usb1: Product: EHCI Host Controller
[   11.043167] usb usb1: Manufacturer: Linux 3.14.0-kirkwood-tld-1 ehci_hcd
[   11.049865] usb usb1: SerialNumber: orion-ehci.0
[   11.055278] hub 1-0:1.0: USB hub found
[   11.059098] hub 1-0:1.0: 1 port detected
[   11.063777] mousedev: PS/2 mouse device common for all mice
[   11.378177] usb 1-1: new high-speed USB device number 2 using orion-ehci
[   11.529133] usb 1-1: New USB device found, idVendor=0781, idProduct=5567
[   11.535827] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   11.542963] usb 1-1: Product: Cruzer Blade
[   11.547049] usb 1-1: Manufacturer: SanDisk
[   11.551150] usb 1-1: SerialNumber: 20052444531D91A27698
[   12.078152] rtc-mv rtc-mv: internal RTC not ticking
[   12.083168] i2c /dev entries driver
[   12.087638] hidraw: raw HID events driver (C) Jiri Kosina
[   12.093638] drop_monitor: Initializing network drop monitor service
[   12.100191] TCP: cubic registered
[   12.103501] NET: Registered protocol family 17
[   12.108080] Key type dns_resolver registered
[   12.113049] registered taskstats version 1
[   12.117868] regulator-dummy: incomplete constraints, leaving on
[   12.124303] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[   12.132967] Freeing unused kernel memory: 212K (c064e000 - c0683000)
Loading, please wait...
[   12.228522] udevd[54]: starting version 175
[   12.450180] mvsdio mvsdio: no pins associated
[   12.472611] SCSI subsystem initialized
[   12.508246] mvsdio mvsdio: lacking card detect (fall back to polling)
[   12.535672] usb-storage 1-1:1.0: USB Mass Storage device detected
[   12.585140] scsi0 : usb-storage 1-1:1.0
[   12.594524] usbcore: registered new interface driver usb-storage
[   13.589662] scsi 0:0:0:0: Direct-Access     SanDisk  Cruzer Blade     1.27 PQ: 0 ANSI: 6
[   13.639343] sd 0:0:0:0: [sda] 15223808 512-byte logical blocks: (7.79 GB/7.25 GiB)
[   13.648934] sd 0:0:0:0: [sda] Write Protect is off
[   13.654420] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[   13.674127]  sda: sda1
[   13.681300] sd 0:0:0:0: [sda] Attached SCSI removable disk
[   13.702030] sd 0:0:0:0: Attached scsi generic sg0 type 0
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.
mount: mounting /dev/sda1 on /root failed: Invalid argument
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory
done.
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootarg.
modprobe: module i8042 not found in modules.dep
[   23.002116] uhci_hcd: USB Universal Host Controller Interface driver
[   23.018799] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[   23.036441] usbcore: registered new interface driver usbhid
[   23.042211] usbhid: USB HID core driver


BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs) 
Re: Pogo Plug v4 blinks green then red and reboots
August 08, 2015 01:01AM
This is the log of MMC on 3.18.5
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2015.08.08 10:52:21 =~=~=~=~=~=~=~=~=~=~=~=


U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45)
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
Warning: failed to set MAC address

Hit any key to stop autoboot: 10  9  8  7  6  5  4  3  2  1  0 
(Re)start 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
** Bad device usb 0 **
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!

MMC rescan: current device # 0 initialized OK
2877273 bytes read in 1413 ms (1.9 MiB/s)
6535284 bytes read in 1665 ms (3.7 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.18.5-kirkwood-tld-1
   Created:      2015-08-07  15:43:28 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2877209 Bytes = 2.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.18.5-kirkwood-tld-1
   Created:      2015-02-19   1:49:36 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6535220 Bytes = 6.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... 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 3.18.5-kirkwood-tld-1 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 PREEMPT Thu Feb 5 17:58:07 PST 2015
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine model: Seagate GoFlex Net
[    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=/dev/mmcblk0p1 rootdelay=10 rootfstype=ext3 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: 114936K/131072K available (5640K kernel code, 365K rwdata, 1920K rodata, 268K init, 305K bss, 16136K reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xffe00000   (2048 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 - 0xc076a240   (7561 kB)
[    0.000000]       .init : 0xc076b000 - 0xc07ae000   ( 268 kB)
[    0.000000]       .data : 0xc07ae000 - 0xc08096fc   ( 366 kB)
[    0.000000]        .bss : 0xc08096fc - 0xc0855d84   ( 306 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000024] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every 25769803770ns
[    0.000625] Console: colour dummy device 80x30
[    0.000670] Calibrating delay loop... 795.44 BogoMIPS (lpj=3977216)
[    0.090156] pid_max: default: 32768 minimum: 301
[    0.090365] Security Framework initialized
[    0.090517] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.090547] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.091663] Initializing cgroup subsys devices
[    0.091712] Initializing cgroup subsys freezer
[    0.091764] Initializing cgroup subsys net_cls
[    0.091797] Initializing cgroup subsys blkio
[    0.091955] CPU: Testing write buffer coherency: ok
[    0.092627] Setting up static identity map for 0x557418 - 0x557470
[    0.093093] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[    0.096811] devtmpfs: initialized
[    0.100888] prandom: seed boundary self test passed
[    0.106886] prandom: 100 self tests passed
[    0.106917] pinctrl core: initialized pinctrl subsystem
[    0.107666] regulator-dummy: no parameters
[    0.114754] NET: Registered protocol family 16
[    0.115485] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.140176] cpuidle: using governor ladder
[    0.170175] cpuidle: using governor menu
[    0.170811] Feroceon L2: Enabling L2
[    0.170876] Feroceon L2: Cache support initialised.
[    0.171461] [Firmware Info]: /ocp@f1000000/ethernet-controller@72000/ethernet0-port@0: local-mac-address is not set
[    0.177787] No ATAGs?
[    0.212568] vgaarb: loaded
[    0.213124] usbcore: registered new interface driver usbfs
[    0.213243] usbcore: registered new interface driver hub
[    0.213365] usbcore: registered new device driver usb
[    0.214962] Switched to clocksource orion_clocksource
[    0.270267] NET: Registered protocol family 2
[    0.271375] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.271410] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.271441] TCP: Hash tables configured (established 1024 bind 1024)
[    0.271544] TCP: reno registered
[    0.271567] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.271599] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.271890] NET: Registered protocol family 1
[    0.272409] RPC: Registered named UNIX socket transport module.
[    0.272426] RPC: Registered udp transport module.
[    0.272437] RPC: Registered tcp transport module.
[    0.272448] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.272832] Unpacking initramfs...
[    1.087512] Freeing initrd memory: 6384K (c1100000 - c173c000)
[    1.087707] NetWinder Floating Point Emulator V0.97 (double precision)
[    1.089673] futex hash table entries: 256 (order: -1, 3072 bytes)
[    1.089721] Initialise system trusted keyring
[    1.089865] audit: initializing netlink subsys (disabled)
[    1.089945] audit: type=2000 audit(1.080:1): initialized
[    1.091114] zpool: loaded
[    1.091137] zbud: loaded
[    1.091578] VFS: Disk quotas dquot_6.5.2
[    1.091665] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.092514] NFS: Registering the id_resolver key type
[    1.092573] Key type id_resolver registered
[    1.092586] Key type id_legacy registered
[    1.092624] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    1.092646] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    1.092960] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    1.093432] msgmni has been set to 236
[    1.093656] Key type big_key registered
[    1.098000] alg: No test for stdrng (krng)
[    1.098064] Key type asymmetric registered
[    1.098089] Asymmetric key parser 'x509' registered
[    1.098223] bounce: pool size: 64 pages
[    1.098357] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    1.098389] io scheduler noop registered
[    1.098411] io scheduler deadline registered
[    1.098492] io scheduler cfq registered (default)
[    1.100419] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[    1.101370] irq: Cannot allocate irq_descs @ IRQ33, assuming pre-allocated
[    1.101958] irq: Cannot allocate irq_descs @ IRQ65, assuming pre-allocated
[    1.102730] mv_xor f1060800.xor: Marvell shared XOR driver
[    1.135069] mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
[    1.175057] mv_xor f1060800.xor: Marvell XOR: ( xor cpy )
[    1.175333] mv_xor f1060900.xor: Marvell shared XOR driver
[    1.215055] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[    1.255053] mv_xor f1060900.xor: Marvell XOR: ( xor cpy )
[    1.255679] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    1.257636] console [ttyS0] disabled
[    1.257724] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 10416666) is a 16550A
[    1.854610] console [ttyS0] enabled
[    1.860340] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[    1.866716] nand: Hynix H27U1G8F2BTR-BC
[    1.870542] nand: 128MiB, SLC, page size: 2048, OOB size: 64
[    1.876212] Scanning device for bad blocks
[    1.995489] 4 cmdlinepart partitions found on MTD device orion_nand
[    2.001729] Creating 4 MTD partitions on "orion_nand":
[    2.006881] 0x000000000000-0x000000100000 : "u-boot"
[    2.012428] 0x000000100000-0x000000500000 : "uImage"
[    2.017966] 0x000000500000-0x000002500000 : "rootfs"
[    2.023506] 0x000002500000-0x000008000000 : "data"
[    2.030298] libphy: Fixed MDIO Bus: probed
[    2.034828] libphy: orion_mdio_bus: probed
[    2.047700] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    3.133146] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:00:00:00:00:00
[    3.142179] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    3.148724] ehci-pci: EHCI PCI platform driver
[    3.153247] ehci-orion: EHCI orion driver
[    3.157518] orion-ehci f1050000.ehci: EHCI Host Controller
[    3.163036] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    3.170917] orion-ehci f1050000.ehci: irq 29, io mem 0xf1050000
[    3.195012] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[    3.201254] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    3.208051] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.215273] usb usb1: Product: EHCI Host Controller
[    3.220138] usb usb1: Manufacturer: Linux 3.18.5-kirkwood-tld-1 ehci_hcd
[    3.226840] usb usb1: SerialNumber: f1050000.ehci
[    3.232583] hub 1-0:1.0: USB hub found
[    3.236444] hub 1-0:1.0: 1 port detected
[    3.241650] mousedev: PS/2 mouse device common for all mice
[    4.255015] rtc-mv f1010300.rtc: internal RTC not ticking
[    4.260695] i2c /dev entries driver
[    4.267771] hidraw: raw HID events driver (C) Jiri Kosina
[    4.273676] drop_monitor: Initializing network drop monitor service
[    4.280306] TCP: cubic registered
[    4.283626] NET: Registered protocol family 17
[    4.288290] Key type dns_resolver registered
[    4.293723] Loading compiled-in X.509 certificates
[    4.298585] registered taskstats version 1
[    4.304125] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    4.313671] Freeing unused kernel memory: 268K (c076b000 - c07ae000)
Loading, please wait...
[    4.417958] systemd-udevd[57]: starting version 215
[    4.435822] random: systemd-udevd urandom read with 6 bits of entropy available
[    4.657412] SCSI subsystem initialized
[    4.717977] sata_mv f1080000.sata: slots 32 ports 2
[    4.770116] scsi host0: sata_mv
[    4.787260] scsi host1: sata_mv
[    4.790893] ata1: SATA max UDMA/133 irq 32
[    4.817526] ata2: SATA max UDMA/133 irq 32
[    5.165031] ata1: SATA link down (SStatus 0 SControl F300)
[    5.535013] ata2: 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: Waiting for root file system ... done.
Gave up waiting for root device.  Common problems:
 - Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT!  /dev/mmcblk0p1 does not exist.  Dropping to a shell!
modprobe: module i8042 not found in modules.dep
[   26.062882] uhci_hcd: USB Universal Host Controller Interface driver
[   26.083725] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[   26.105328] usbcore: registered new interface driver usbhid
[   26.110888] usbhid: USB HID core driver


BusyBox v1.22.1 (Debian 1:1.22.0-9+b1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs) 
Re: Pogo Plug v4 blinks green then red and reboots
August 08, 2015 02:22AM
pratikworld,

Everything does look OK, the kernel has been started and running. The problem is the kernel could not mount the rootfs. Please interrupt serial console at countdown and
printenv
, and post the output here.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Pogo Plug v4 blinks green then red and reboots
August 08, 2015 02:59AM
Hey Bodhi, here you go

U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45)
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
Warning: failed to set MAC address

Hit any key to stop autoboot: 10  9  0 
Pogov4> printenc v
arcNumber=2097
baudrate=115200
bootcmd=run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
if_netconsole=ping $serverip
ipaddr=192.168.0.231
led_error=orange blinking
led_exit=green off
led_init=green blinking
machid=0x831
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
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
rootdelay=10
rootfstype=ext3
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
serverip=192.168.0.220
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
usb_boot=mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then bootm 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: 2193/131068 bytes
Pogov4> 

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: