step by step of how to install Debian on stock PogoplugPro

I am reading posts here about installing Debian with the latest rootfs and the latest uBoot and I am jumping around between references to topics and I am getting utterly confused.
Where exactly do I need to start if I want to install the latest Debian with the latest file system on a stock Pogoplug Pro?

Besides that I have SSH access to the device, everything else is stock - stock uBoot, stock OS.
I guess I have to start with updating uBoot, but then that seems to go hand in hand with the decision, what rootfs I am going to install, etc.
In any case - I need some guidance here, please.
Thanks!

You can load the 3.17.0 rootfs on a flash drive and boot using the stock u-boot by following the directions here: http://forum.doozan.com/read.php?2,16044 . Look for the section with the 3.17.0 Debian rootfs dowload link and follow the directions underneath it to flash it to a drive. Also note the specific mkimage command to modify uImage to boot with the stock u-boot. I've reprinted the section you need to use here:

Download at Dropbox: 

Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2 
md5: 
c8e9df471f331c56befc4051a754bfea 

INSTALLATION: 

Installation can be done on any Linux box, with a fresh USB drive (SD card or HDD would work fine too). It is assuming the USB drive is mounted at /media/sdb1. 

1. Format a new Ext3 USB drive, and label it rootfs. Note: if your existing uBoot env for rootfs type is ext2, then you might want to keep it consistent and use Ext2 USB drive. It will work with Ext3 drive without problem, though. 

For example: 
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
rootfstype=ext2

2. Mount the drive on a Linux box. As root user, cd to top level directory and extract it. 
cd /media/sdb1 
tar -xjf Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2

3. edit /media/sdb1/etc/fstab entry for /dev/root to match the rootfstype of your usb_rootfstype (however, you can keep it as Ext2 without problem in booting an Ext3 partition). 
/dev/root      /               ext2    noatime,errors=remount-ro 0 1

4. Create uImage with embbeded DTB to run with older u-boot. Please see Note 2 below if you are running this kernel witht the new U-Boot. 

Pogo Pro vs. Pogo Classic: If you're installing this on a Pogo V3 Classic (no PCI), replace the ox820-pogoplug-pro.dtb below with ox820-pogoplug-classic.dtb. 

cd /media/sdb1/boot
cp -a zImage-3.17.0-oxnas-tld-1 zImage-3.17.0-oxnas-tld-1.fdt
cat dts/ox820-pogoplug-pro.dtb >> zImage-3.17.0-oxnas-tld-1.fdt
mkimage  -A arm -O linux -C none -T kernel -a 0x60008000 -e 0x60008000 -n 'Linux-3.3.17.0-oxnas-tld-1' -d zImage-3.17.0-oxnas-tld-1.fdt  uImage
sync

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

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 updates: 
rm /etc/ssh/ssh_host*
ssh-keygen -A

apt-get update
apt-get upgrade

Note2: To simplify the first time installation process, the uImage is recreated with the DTB embedded in step 4. If you are familiar with FDT kernel booting, and want to boot with separate DTB, see the Kernel 3.17 installation section A.6 in this thread for instruction about setting up u-boot envs. Or if you are going run this kernel with the new u-boot as mentioned, then do set up booting as described in section A.6. 


Note3: if the Linux box that you are using to create rootfs does not already have mkimage installed then install u-boot-tools package to make it available: 
apt-get install u-boot-tools

Note4: For setting up wireless on the Pogo Pro, please see: http://forum.doozan.com/read.php?2,16044,20964#msg-20964

Once you get 3.17.0 running, upgrade the u-boot to the latest by following the directions at the top of the Oxnas u-boot thread here: http://forum.doozan.com/read.php?3,16017. Note the decision you will have to make whether you want to boot with dtb embedded or not.

Once you upgrade u-boot, go back to the Oxnas Debian thread referenced above and look at the sections on top which tell you how to upgrade Debian to the latest 4.0.0-tld-2 kernel.

Important note: Forum member bodhi creates both the Debian rootfs' and the new u-boots. He is the forum God. Listen to him and ask his advice (politely) and he will get you through to success.



Edited 1 time(s). Last edit at 05/30/2015 10:08PM by LeggoMyEggo.

Thanks so much LeggoMyEggo!

I will work through this. I am asuming these

set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
rootfstype=ext2

are uBoot environment settings, to be set with fw_setenv?

At the moment I am not sure, how I will do the necessary mkimage. I am on OS X and currently don't have a Linux box available.

During my research on this - very helpful, indeed! - forum, I already noticed, that bodhi is the forum God. He already gave me important and helpful hints and pointers in some other topics, taht I asked today.
Thanks again!



Edited 1 time(s). Last edit at 06/01/2015 02:37AM by zwalex.

@zwalex,

Leggo did a fine job laying out the steps! We don't have the script yet to automate this. So atm, these are the manual steps.

To add a little clarifying step to make it easier (I wrote those instructions separately for u-boot and rootf threads, so they don't have to rely on one another).

After you create the basic rootfs, it already contains all the NAND tools, mtd-utils. So to run fw_setenv, fw_printenvs, mkimage,... you can run these binaries from the rootfs itself. No need to rely on another box or download the binaries, if the rootfs is created first.

@Leggo, that could be added to your instruction above.

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



Edited 1 time(s). Last edit at 05/31/2015 03:32AM by bodhi.

> set_bootargs_usb=setenv bootargs console=$console
> root=$usb_root rootdelay=$rootdelay
> rootfstype=$rootfstype $mtdparts
> rootfstype=ext2
>
> are uBoot environment settings, to be set with
> fw_setenv?
>

Yes.

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

Thanks bodhi!
I ran the setup looking at the instructions above as well as the ones from here, which are essentially identical - besides that it doesn't [have to ...] use mkimage. I am not reallu sure, why mkimage is even necessary ... (?).

In any case - I have Debian running on my Pogoplug Pro now.

root@DebianPlug:~# uname -a
Linux DebianPlug 3.17.0-oxnas-tld-1 #1 SMP PREEMPT Sat Oct 25 15:59:43 PDT 2014 armv6l GNU/Linux

I will follow some post-install tips from here (sudo, samba, ...) and here (WiFi, as I have the Pro).

Something in the first link, talking about swapping on USB stick made me think about 'swappiness' - what are your guys recommendations for that?
Thanks again for all your help, Leggo and bodhi!

zwalex,

> why mkimage is even necessary ... (?).

Kernel 3.16 is non-FDT, so the DTB is not needed to be appended. In fact, I usually recommend that rootfs for people who install from stock. But for people who is well verse in Linux, 3.17, which is FDT, is not that much more difficult. Just a newer rootfs.

> In any case - I have Debian running on my Pogoplug
> Pro now.

Evidently you did not have trouble, you saw the extra step it's for! which is appending the DTB to the zImage to make the uImage.

> Something in the first link, talking about
> swapping on USB stick made me think about
> 'swappiness' - what are your guys recommendations
> for that?

For headless server (NAS), use the default which is 60. And use zswap to help making the 128MB RAM more efficient. But you need to install the latest kernel 4.0 to use that. For running the Pogo with a remote desktop GUI, I would use swappiness less/equal 10.

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



Edited 1 time(s). Last edit at 05/31/2015 04:17AM by bodhi.

I wasn't ignoring grayman4hire's (Qnology) blog, I was just trying to prevent confusion by referring to steps to get his Pro booting Debian using only threads in this forum. But no question gm4h's instructions work very well. His instructions get you started but you will end up coming back here if you want to update rootfs / u-boot to the latest and keep both updated. Plus if you frequent this forum you can ask bodhi to include things in his updates if you find that a function you need is not included in the current kernel. Bodhi updates Debian usually every three months +/-.

bodhi Wrote:
-------------------------------------------------------
> Evidently you did not have trouble, you saw the
> extra step it's for! which is appending the DTB to
> the zImage to make the uImage.

Thanks bodhi!
I am a little confused. I am running a 3.17 kernel and I did not had to run mkimage - just untared your package. The instructions I followed only mention mkimage when upgrading to a 3.18 kernel.
You mention that is already necessary for a 3.17 kernel (that I am on, but didn't had to do mkimage ...) - what am I missing?

zwalex Wrote:
> I am a little confused. I am running a 3.17 kernel
> and I did not had to run mkimage - just untared
> your package. The instructions
> [url=http://blog.qnology.com/2015/04/hacking-pogop
> lug-v3oxnas-proclassic.html]I followed[/url] only
> mention mkimage when upgrading to a 3.18 kernel.
> You mention that is already necessary for a 3.17
> kernel (that I am on, but didn't had to do mkimage
> ...) - what am I missing?

The blog.qnology.com site took bodhi's rootfs and already completed the mkimage step for you. Look at the download links from that site, they aren't Dropbox like you get if downloading directly from here. Nothing wrong with that, the qnology site has made life easier for those new to all of this. I'm just saying that's why you didn't need to complete mkimage.

Thanks Leggo!
Yes, I will slowly upgrade to kernel and rootfs.
My kernel is only 3.17 right now

# uname -r

-> 3.17.0-oxnas-tld-1
How can I find out my rootfs 'version'?

I think, I have the latest U-Boot version, though.
If I do

# sudo grep -a --null-data U-Boot /dev/mtd0

the output is
U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for OXNASBT

It's because in my tutorial included the necessary dtb uboot variables. I did not run the mkimage steps (it's not needed if you set the dtb uboot variables).

Also for clarification, bodhi's files are re-hosted unmodified. The reason is the wget command on the default Pogoplug OS is not able to handle SSL/HTTPS connection from dropbox.

#default to pogoplug classic dtb
/tmp/fw_setenv fdt_file '/boot/dts/ox820-pogoplug-classic.dtb'
/tmp/fw_setenv dt_load_dtb 'ext2load usb 0:1 $dtb_addr $fdt_file'

LeggoMyEggo Wrote:
-------------------------------------------------------
> zwalex Wrote:
> > I am a little confused. I am running a 3.17
> kernel
> > and I did not had to run mkimage - just untared
> > your package. The instructions
> >
> url=http://blog.qnology.com/2015/04/hacking-pogop
>
> > lug-v3oxnas-proclassic.html]I followed[/url]
> only
> > mention mkimage when upgrading to a 3.18
> kernel.
> > You mention that is already necessary for a
> 3.17
> > kernel (that I am on, but didn't had to do
> mkimage
> > ...) - what am I missing?
>
> The blog.qnology.com site took bodhi's rootfs and
> already completed the mkimage step for you. Look
> at the download links from that site, they aren't
> Dropbox like you get if downloading directly from
> here. Nothing wrong with that, the qnology site
> has made life easier for those new to all of this.
> I'm just saying that's why you didn't need to
> complete mkimage.

-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)



Edited 2 time(s). Last edit at 05/31/2015 05:39PM by grayman4hire.

It now appears that my comments in this thread make it evident that I've been suffering from D.O.T.P. (Diarrhea Of The Post). I need to stop posting and recuperate so that in the future I can better pay attention.

So I'm now going to STFU :)...............



Edited 1 time(s). Last edit at 05/31/2015 08:26PM by LeggoMyEggo.

grayman4hire,

> wget
> command on the default Pogoplug OS is not able to
> handle SSL/HTTPS connection from dropbox.

I think it does work fine now. I'm not sure when it was working, but I think lot of people are currently using https to wget from dropbox.

zwalex,

Either rootfs 3.16, 3.17, or 3.18 is fine. All you need to do to get the latest is upgrading kernel later. You could start with 3.18 rootfs then upgrading to kernel 4.0.

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

@ zwalex ,

> How can I find out my rootfs 'version'?

Rootfs version is same as kernel version if you've not upgraded the kernel on it.

>
> I think, I have the latest U-Boot version,
> though.
> If I do
>

# sudo grep -a --null-data U-Boot
> /dev/mtd0

> the output is
> U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for
> OXNASBT

Yes, it is the latest release u-boot. There is a new version (tld-5), but it does not really add anything important so I have not made it a formal release.

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



Edited 1 time(s). Last edit at 06/01/2015 08:55AM by bodhi.

Thanks bodhi!
What kernel version do I have to go to so that the PogoplugPro's on-board WiFi will work?
I don't get it working with the 3.17 kernel.
Thanks and Cheers!

@zwalex,

I'm not using wifi on my box for a while. But here is a report from gregg_a_g, who got the wifi working from a default installation (meaning the latest rootfs), starting from this post and a few posts after:
http://forum.doozan.com/read.php?2,16044,21638#msg-21638

You'll need to install firmware-ralink first (for the driver) and then set up wpa supplicant. If it does not work for whatever reason, you should install the latest kernel linux-4.0.0-oxnas-tld-2. See how it goes. Or perhaps post your steps here for us to see if anything is missing?

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

Thanks bodhi!
Yes, I installed firmware-ralink and wpasupplicant (and wireless-tools, ...) according to this post on qnology.com from grayman4hire.
I will try upgrading to the latest kernel and then report back.
Thanks again!

@zwalex,

I would recommend following my tutorial as it's been tested as published. Did you upgrade to 3.18 as instructed? Did you update the FDT to the Pogoplug Pro as instructed?

-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)

@grayman4hire - I am running the Pogoplug Pro FDT, but I have not yet upgraded to the 3.18 kernel.

From your response I am assuming that the RT3090 on-board wifi will work with the 3.18 (and higher ...) kernel?

Again, the tutorial is tested as published. Wi-fi will work with kernel 3.18.5. Cannot comment on "and higher" kernel.

zwalex Wrote:
-------------------------------------------------------
> @grayman4hire - I am running the Pogoplug Pro FDT,
> but I have not yet upgraded to the 3.18 kernel.
>
> From your response I am assuming that the RT3090
> on-board wifi will work with the 3.18 (and higher
> ...) kernel?

-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)

here is my problem.
evns:
hardware:
pogoplug pro.
a 3.5 Inch sata hdd without sata-usb cable.
a 2.5 inch sata hdd with sata-usb cable(this cable can only use at this 2.5 inch hdd cause it's a portable hdd).
a serial console cable.
a macbook pro for operations.
software:
uboot.2013.10-tld-4.ox820.bodhi.tar on NAND
a debian 6.0 rescue system on 2.5 hdd.

before this, my pogoplug pro was running a openwrt with a openwrt-uboot. a 3.5inch hdd pluged inside. And last night, I tried to install debian.
here is what i done:
1. install uboot.2013.10-tld-4.ox820.bodhi.tar on openwrt with mtd tool come from openwrt(so stupid cause it bricked my box).
2. reboot.no ttl output:( it bricked!
3. I searched for help and found that I could boot it from sata. and I downloaded a hdd image with debian 6.0. dd this image to a portable hdd(2.5inch hdd i mentioned above).
4. unpluged the 3.5inch hdd and pluged this 2.5inch one.
5. booting well.
6.Installed uboot.2013.10-tld-4.ox820.bodhi.tar following the instruction.
7.unpluged the 2.5inch hdd and pluged the 3.5 inch one.
8. booting. and now i can see the output from serial console. because i don't have a OS in NAND and that 3.5inch hdd.
9. it get stuck at uboot now.

what's the next if i want to install a lastest debian on the 3.5inch hdd. I have no other device to write data to that 3.5inch hdd.
Do I need to make a USB system on the portable hdd,boot from USB and do the operation on it?
I saw this uboot support booting from tftp/nfs, can i just boot from network?if so, how?

I am new to uboot. and I am not sure I understand all the documents correctly since I am a Chinese who not confident with my English.
Appreciate for the help.

@dalin,

> Do I need to make a USB system on the portable
> hdd,boot from USB and do the operation on it?

This is the best approach. Since you have installed the new u-boot, you can boot from either USB or HDD.

> I saw this uboot support booting from tftp/nfs,
> can i just boot from network?if so, how?
>

You can load the kernel that way, but you still need the whole rootfs resides on either USB or HDD.

> I am new to uboot. and I am not sure I understand
> all the documents correctly.

When you feel that you're stuck at some point, please post your serial console bootlog (the entire log). That way I can tell where you are at and suggest the next action to take.

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

Quote
root@debian:~# fw_printenv
autoload=no
baudrate=115200
bootargs=console=ttyS0,115200n8
bootdelay=10
console=console=ttyS0,115200n8
ethact=mii0
ethaddr=5e:2b:15:71:ec:b6
mtdids=nand0=41000000.nand
mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
stderr=serial
stdin=serial
stdout=serial
usb_device=0:1
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10
uinitrd_addr=0x60e00000
uimage_addr=0x60500000
dtb_addr=0x62c00000
dt_load_dtb=ext2load usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb
dt_load_initrd=ext2load usb 0:1 $uinitrd_addr /boot/uInitrd
dt_load_uimage=ext2load usb 0:1 $uimage_addr /boot/uImage
dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr
dt_usb_boot=run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm
dt_usb_bootcmd=run usb_set_bootargs; run dt_usb_boot
dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; reset
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
preboot=run preboot_nc
ipaddr=192.168.10.10
serverip=192.168.10.121
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
uenv_import=echo importing envs ...; env import -t 0x60500000
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_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
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 0x60500000 /boot/uEnv.txt; then setenv uenv_loaded 1; fi
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;
bootcmd=run bootcmd_uenv; run dt_bootcmd_usb; reset
devices=ide usb

the uboot evns like above.
it wouldn't boot from sata. if i don't plug a usb stick,it won't boot.

Quote
U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12)
Boot device: NAND
Attempting to set PLLA to 850 MHz ...
plla_ctrl0 : 0000020a
plla_ctrl1 : 00330000
plla_ctrl2 : 0065008b
plla_ctrl3 : 000000f1

PLLA Set


U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for OXNAS

DRAM: 128 MiB
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net:
Led: GREEN
mii0
Main Loop
Waiting for PHY auto negotiation to complete.. done
ENET Speed is 1000 Mbps - FULL duplex connection
Using mii0 device
host 192.168.10.121 is alive
Using mii0 device
host 192.168.10.121 is alive
Using mii0 device
host 192.168.10.121 is alive
Using mii0 device
host 192.168.10.121 is alive
Using mii0 device
host 192.168.10.121 is alive

U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12)
Boot device: NAND
Attempting to set PLLA to 850 MHz ...
plla_ctrl0 : 0000020a
plla_ctrl1 : 00330000
plla_ctrl2 : 0065008b
plla_ctrl3 : 000000f1

PLLA Set

what should i do if i want boot from sata?
second problem is i can't set the ethaddr.

Quote
root@debian:~# fw_setenv ethaddr '00:25:31:01:66:5F'
Can't overwrite "ethaddr"

dalin,

> what should i do if i want boot from sata?

You and Peter are looking for the same thing:
http://forum.doozan.com/read.php?3,22226

I'm on the road, away from my development environment, so I was hoping others who have installed this u-boot and boots from SATA will help by posting their u-boot envs.

Let's wait for a day or two to see if anybody is going to do that. I'll come back and help if nobody will.

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

Not working for me. Now, I have a particular situation with *my* PogoplugPro. Way back when ArchArm still supported the PogoPro, I had done the various tweaks necessary for it to run Arch. Unfortunately, I did a package update on it before I knew the kernel no longer supported the PogoPro. At which point I had a fubarred setup on the flash drive, and no leads on how to fix it. So I unplugged my pogopro, and re-used the flash/usb stick for other things.

So I have an already modified pogo, with no way to connect to it, and I need to build a completely functional flash/usb using my x64 linux box to build it (Mint 17.2, if it matters). Tried working through the instructions at http://forum.doozan.com/read.php?2,16044, but still can't get a drive the pogo will boot from. The green light on the front will just quickly flash endlessly, and nothing will happen otherwise.

Still trying to find what to do with your "set_bootargs_usb..." line in the directions, or if it's even relevant to my setup. I can use ext3, since I'm starting almost from scratch here (other than the pogo being set to boot from a long-lost USB).

jelabarre59 Wrote:
-------------------------------------------------------
> Not working for me. Now, I have a particular
> situation with *my* PogoplugPro. Way back when
> ArchArm still supported the PogoPro, I had done
> the various tweaks necessary for it to run Arch.
> Unfortunately, I did a package update on it before
> I knew the kernel no longer supported the PogoPro.
> At which point I had a fubarred setup on the
> flash drive, and no leads on how to fix it. So I
> unplugged my pogopro, and re-used the flash/usb
> stick for other things.
>
> So I have an already modified pogo, with no way to
> connect to it, and I need to build a completely
> functional flash/usb using my x64 linux box to
> build it (Mint 17.2, if it matters). Tried
> working through the instructions at
> http://forum.doozan.com/read.php?2,16044, but
> still can't get a drive the pogo will boot from.
> The green light on the front will just quickly
> flash endlessly, and nothing will happen
> otherwise.
>
> Still trying to find what to do with your
> "set_bootargs_usb..." line in the directions, or
> if it's even relevant to my setup. I can use
> ext3, since I'm starting almost from scratch here
> (other than the pogo being set to boot from a
> long-lost USB).

I suspect that the new rootfs will have some problem with the old kernel installation.

If you have serial console then it is easy to get it booting the latest Debian rootfs. If you don't, I think the quickest way is to get the old roofs from: shv, varkey, or ingmar_k, and put it on a USB stick (see the first post of the kernel thread). Try booting with it.

Serial console on the Pogo Pro is quite easy, the header is already there, you'll just need to get the module converter, open the case and connect it.

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

I have a cable (old CD-ROM redbook cable) that plugs right onto the serial header on the Pogoplug Pro. I have seen a picture taht labels the pins as "Gnd | RXD | TXD | 3.3v", so now all I need is to find how to attach a 9-pin port to it (I think it will be pins 5, 2 and 3 respectively, but have no idea of what to do with the 3.3v pin). Then I can connect my serial-to-usb adapter to that.

jelabarre59,

> I have a cable (old CD-ROM redbook cable) that
> plugs right onto the serial header on the Pogoplug
> Pro. I have seen a picture taht labels the pins
> as "Gnd | RXD | TXD | 3.3v", so now all I need is
> to find how to attach a 9-pin port to it

Which plug do you have? If it has the header already, you only need to either plug the jumper wire directly to 3 pins (GND, RXD, TXD) or use a matching header. See this thread:

http://forum.doozan.com/read.php?8,13263,13264#msg-13264

> it will be pins 5, 2 and 3 respectively, but have
> no idea of what to do with the 3.3v pin).

Never connect the 3.3V. You could kill the serial port that way (your TTL module converter draw power from its USB port).

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