Hiya bodhi, You helped me out on a thread about two years ago with my PogoPlug E02. Logged into the device today randomely to run an update via apt-get and figured I'd check the forums. After the update I'm running: root@PogoPlug:~# uname -a Linux PogoPlug 5.3.2-kirkwood-tld-1 #1.0 PREEMPT Wed Oct 2 00:06:56 PDT 2019 armv5tel GNU/Linux root@PogoPlug:~# cat /etc/debian_verby wooglez - Debian
Hey @bodhi you may want to add a section in the rootfs tutorial about running ntpdate for first login after ssh-keys cuz otherwise apt-get will screw up.by wooglez - uBoot
Hey @bodhi, Yea I was just coming here to update this post, I decided to follow the rootfs tutorial next and after doing so on my new usb device it booted like a charm. Would be nice to let new or returning users know what order the process should be for updating devices, UBoot first then rootfs especially since some of the end instructions for Uboot mention modifying (the dtb step) /boot buby wooglez - uBoot
I was following the UBoot instructions from an older pogoplug I had set up here back in 2014-15, I think the pendrive eventually went bad. I was still able to boot into the stock pogo OS and was following these instructions . I noticed I didn't have an /boot folder towards the end, setup netconsole and rebooted. Below is the output from booting. Where did I go wrong? U-Boot 2017.07-tlby wooglez - uBoot
revisiting this thread again, turns out I didn't have the crypto headers in /usr/include/crypto like t1m was suggesting. re-installing crypto-dev with make make install added them correctly now. I then re-ran as root. dpkg-buildpackage -us -uc runs much longer now, the end however still errors out. link to output/errorby wooglez - Debian
hey t1m, I'm pretty sure I did make install when getting compiling the cryptodev module. Perhaps I'm misunderstanding. I redid make install in my cryptodev-20091126/ directory and it shows some headers in /usr/include/crypto as well as having a module that inserts correctly. I'm still getting the same error running dpkg-buildpackage -us -uc however. Let me know if there's aby wooglez - Debian
hey t1m, I've actually got libc6-dev installed, I can't find a good way to log the output from the dpkg-buildpakage command. I'm attempting to tee it to a seperate file but it's ending before the error messages start occuring. Here's my command : dpkg-buildpackage -us -uc |tee -i ../build_openssl_output.log (moved up a directory so it doesn't try to build it)by wooglez - Debian
t1m thanks so much for your excellent response, you have no idea how much I've been searching to get this working on my pogo. I actually prefer to do things the debian way but I was finding very little in the way of steps or resources to get this working. So I truly appreciate the time you put into such a detailed post. However I'm still failing at the last step. I'm currently re-rby wooglez - Debian
I got as far as make with openssl and then it spazzed out on me. Could you take a look? You did this all on debian squeeze also? I'd already successfully compiled and loaded / unloaded the module.by wooglez - Debian
Has anyone succesfully gotten openssl patched to use the Marvell Kirkwoods AES hardware acceleration? I've found these links detailing part of the process : link1 link2 link3 But I'm running kernel 2.6.32-5-kirkwood and some of the links in the scripts are dead (http://archlinuxarm.org/mirror/with-linux/kernel/2/2.6/2.6.38/2.6.38.8/sheeva-2.6.38.8.config) Any help appreciated.by wooglez - Debian