by telzey » Wed Apr 11, 2012 3:07 pm
To use the 2.6.31.14 kernel for a USB install of ALARM you'll have to write the kernel to NAND memory and replace the default ALARM 2.6.31.6 kernel that was written during your initial installation of ALARM.
This isn't particularly difficult, but it must be done EXACTLY right. If you don't flash it to NAND correctly, or if your kernel doesn't work (because you didn't test it), then you can only recover if you either have a serial cable, or if you boot directly from SATA.
It should work fine, but I'm not in the position to help out tens or hundreds of angry users that failed to follow the correct steps. That's why I'm not recommending it, and not giving out instructions on how to do it.
If you have a working serial cable, then you can always build and test the kernel first by using a tftp boot. I believe that's what WarheadsSE does when testing his kernels. I just write mine to a SATA drive (but also with a serial cable to see the boot messages).
Either way you're going to have to open up your Pogoplug and spend a little money on cables.