Pogoplug v3/Oxnas (EOL)
If you have not purchased a device yet, we recommend you look into other options as this device is no longer being supported by Arch Linux ARM.
Pogoplug Pro is the first of a new variety of hardware from Pogoplug. They are based on the PLX/Oxford Semiconductor NAS7820 SoC, which provides two ARMv6 cores clocked at 700MHz. The Pro has an onboard mini-PCIe slot that is used for a WiFi module.
Pogoplug V3 and the new pink colored Classic models are the continuation of the "oxnas" hardware from Pogoplug. They are based on the same PLX/Oxford Semiconductor NAS7820 SoC. Unlike the Pro/Video varieties, these do not have a mini-PCIe controller or slot.
The SoC used in these models is not supported in the mainline Linux kernel, and all sources are covered under an NDA with PLX. We support these devices with a custom kernel that is flashed alongside the original kernel in flash memory. This is a safe and non-destructive process, and allows the devices to use all of the software in our repositories.
Model numbers located on bottom of foot:
POGO-P01 - Pro
POGO-P21 - V3
POGO-P24 - V3
POGO-P25 - V3
POGO-B01 - Classic
POGO-B02 - Classic
POGO-B03 - Classic
POGO-B04 - Classic
- VERIFY YOUR MODEL NUMBER! These instructions only apply to models listed below.
- DO NOT re-run the installer script if you have already done so.
- These instructions will void your warranty. While every precaution is taken to ensure nothing bad happens, all actions are at your own risk.
- My.pogoplug.com, the mobile applications, and the desktop Pogoplug connector will no longer work.
- This does not include the wireless drivers for the Pro. These will be added later, as a separate package.
These instructions will install the kernel to NAND (safely) and the root file system 'rootfs' to a USB drive. If you wish to boot purely from SATA, there is a forum thread, but it is NOT for the timid.
Supported OXNAS 7820 Boards
Overview and Caveat
Unlike it's Marvell based brethren, a modern U-Boot has not been created for the OXNAS line as of this time. As such, our available method is the use of /dev/sda1. The selection of a particular usb drive as sda is not perfect, and thus can sometimes come up in the wrong order based on drive response times at boot. (e.g. first to respond gets sda). As a result, you may need to test for yourself to see the pattern in which your drives "spin up". USB flash drives tend to come up faster than spinning hard drives in many cases. There is a special exception to this rule, because the OXNAS kernel initializes the SATA code first, so this problem never exists on systems with a SATA boot drive.
- With the device on and online, register and enable SSH through my.pogoplug.com.
- Power down the original, unmodified Pogoplug.
- Unplug all disk drives.
- With only the drive you intend to install Arch Linux ARM to plugged in (all data will be erased), switch on the power.
- Log in to Pogoplug over SSH using the IP address of the Pogoplug (from your router's DHCP table), with "root" as the username and the password you set up on my.pogoplug.com.
- Stop the Pogoplug software, so it doesn't interfere with the install process:killall hbwd
- Start fdisk to partition the USB or SATA drive:
- At the fdisk prompt, delete old partitions and create a new one:
- Type o. This will clear out any partitions on the drive.
- Type p to list partitions. There should be no partitions left.
- Now type n, then p for primary, 1 for the first partition on the drive, and then press ENTER, accepting default values.
- Exit by typing w.
- Create the ext3 filesystem:
sync cd /tmp wget http://archlinuxarm.org/os/pogoplug/mke2fs chmod 755 mke2fs ./mke2fs -j /dev/sda1
- Download the install script and execute
cd /tmp wget http://archlinuxarm.org/os/oxnas/oxnas-install.sh chmod 755 oxnas-install.sh ./oxnas-install.sh
The installer will ensure that the Pogoplug services are not running and that it has sda1 mounted where it wants it. Then, it will collect some information from the system, download the rootfs tarball, verify it, extract it, and finally use spare space in the NAND for the updated kernel before making modifications to the u-boot environment. If something goes wrong, it will be darn sure to tell you.
- In the end, this is what the last lines of blparam output should look like:
bootargs_stock=root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M poweroutage=yes load_custom_nand=nboot 60500000 0 500000 load_custom_nand2=nboot 60500000 0 B00000 boot_custom=run load_custom_nand boot || run load_custom_nand2 boot bootargs=root=/dev/sda1 ubi.mtd=2,512 rootfstype=ext3 console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M poweroutage=yes rootdelay=15 bootcmd=run boot_custom
Note that there are no " (double quote) characters here.
- The install script will automatically unmount /dev/sda1. If everything went OK, reboot:
- Login to Arch Linux ARM (note: The IP address may have changed. Check your router's DHCP assignments if you can't log in.)
- If you want to have your plug automount drives when they're plugged in. Install the udev rules:
pacman -Sy udev-automount
If the LED on the front is still blinking after booting, rebuild the module dependencies.
Then, reboot again:
- Login again with root/root. Now would be a good time to change your root password.
- Most likely there are several packages that are now out of date. Update them with pacman:
You may have to run pacman a few more times. Accept any default answers (hit enter) and follow any instructions it gives you.
Welcome to Arch Linux ARM. Any questions, stop by the forums or on IRC.
Help! It stopped working!
First, the install script automated a lot of the process, and this can all be done by hand. The really dangerous part has been done via the script, and that is setting the U-Boot environment. Screw that up and you've got serious problems, hence this script instead of a bunch of steps to type by hand.
Second, if your Pogoplug suddenly doesn't come up, and you're freaking out, keep this in mind: You have not bricked your plug! The most likely cause is the order of drives attached at boot, or the filesystem on the boot drive! You can replace it with a matched filesystem fresh from the tarball, and so long as you make sure it's formatted Ext3, you ought to be ''perfectly'' fine.
Place your boot drive in another Linux computer/device and check the file system. If you're still having issues then we'll proceed with starting from scratch on the rootfs. Following steps 7 and 8 above, partition and format the drive (using the correct /dev device, highly likely NOT sda). Download and extract the root filesystem tarball onto the new ext3 partition as the root user, not just sudo. Create a file at /usr/local/mac_addr and place in it your Pro's MAC address (its on the bottom of the unit) in the format XX:XX:XX:XX:XX:XX. Safely umount the drive from the computer, plug it back in to the powered-off Pogoplug, and then plug in the Pogoplug.
If your Pogoplug boots and the front LED blinks wildly for about 15-20 seconds and then TURNS OFF, you're in business when it comes to booting, but there is likely something that has stopped the network. It's not a brick, but be ready to troubleshoot.