The last error above is complaining that you don't have "bc" installed. apt-get install bc Should get you going. I just tried building this under the 5.7.1-kirkwood-tld-1 kernel and it built just fine. I didn't use DKMS, just git cloned the repo, edited the Makefile and made the following changes: CONFIG_PLATFORM_I386_PC = n CONFIG_PLATFORM_ARM_RPI = y After that makeby alexr - Debian
Hey bodhi, I have not actually. I ran this setup for about a week doing minimal operations with a user base of 1 (myself). I didn't notice much of an issue besides some slowness. You're right about the slow usb bus, but I have observed varying performance issues/boosts when using different brands of usb thumb drives and usb hard drives as they pertain to sustained reads/writes. Runby alexr - Debian
It will be slow just due to hardware limitations but it should be usable. I only had timeout issues during initial setup. You can make things slightly faster by making sure your rootfs is on a decently fast usb disk/hard drive and performing the tweaks I outlined. Beyond that there's not much more that can be done unfortunately. As I said nextcloud is very sluggish, even on most anything befby alexr - Debian
Hey jrey, 1) The only issue you'll have running it on 128MB of RAM (with swap) is degraded performance. Nextcloud can be sluggish on far more capable hardware. There should be no downsides to setting a large swap partition in this case, no. 2) Newer versions of Nextcloud usually have more features, which often (not always) translates to more demand on the machine you install it to. Thby alexr - Debian
It should be possible to run Debian off a USB and host the airprint server off that. I was also working on installing a read only Debian install for the NAND but I haven't had time to continue work on that. So it is possible to install to NAND but it takes some work. The easiest solution would be to install Debian to a USB drive and run an airprint server from that.by alexr - Debian
Hey bodhi, Thanks for the reply! I agree, having it all in one small self contained little package simplifies things greatly. A small Debian rescue system would allow the user to fix most if not all issues that might arise right from their own device and provides a familiar system for them to work within. I've had moderate success with my tiny kernel builds so far. They work, and the oveby alexr - Debian
There's actually no real reason beyond wanting to have a self contained, read only recovery system to boot into when no drives are connected. That coupled with the fact that I'm still pretty ignorant as to the workings of u-boot and working with the mtd partitions in general (mostly this). Honestly, if I can keep everything small enough I might just be able to stick everything in the 9by alexr - Debian
So I've been trying to create a Debian rootfs tiny enough to fit into the limited NAND storage found on the Pogoplug (E02/Mobile) which is only 128 MB. The goal being to produce an embedded Debian rescue system now that Embedian is no longer around. My first attempt using debootstrap --arch=armel --variant=minbase stretch . http://SomeDebianMirror Created a rootfs that was still much tooby alexr - Debian
I thought I'd write a quick guide on installing Nextcloud 17 after seeing the Owncloud thread on this forum. It borrows heavily from a linuxbabe install guide linked here: https://www.linuxbabe.com/ubuntu/install-nextcloud-ubuntu-18-04-nginx-lemp . I've only tried this on a Pogoplug E02 with it's 256MB RAM but i don't see it being an issue on 128MB RAM Kirkwood devices as thby alexr - Debian
Edit: the pihole-FTL-armel-native binary seems to crash the moment someone tries to connect. Disregard post. So I was looking through the pihole installer when I noticed they provide a pre-built armel compatible binary in their repository. The problem is the way they go about detecting your device architecture is somewhat flawed. It will only download the armel binary if it detects you'by alexr - Debian
Just tried compiling new pihole version on a new Debian Stretch rootfs with latest kernel, worked fine. Just had to make sure i was using a swap file as noted by rsinklair.by alexr - Debian
You just need to separate entries with a space like so: custom_params=init=/bin/systemd initramfs.runsize=23M follows the same syntax as the "set_bootargs" variable where it's called: set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_paramsby alexr - Debian
Installed armbian a few days ago, so far no issues compiling aria2, pihole-FTL, and a couple other things here and there. Even with a fan the cpu gets pretty toasty at around ~60C with all 4 cores going, Still well within the operating spec though. Still pretty impressive considering ambient temp here in Southern California has been in the high 80's to low 90'sby alexr - Off-Topic
That's fair, i've yet to try to compile something for long periods of time on it yet. When i was first testing it out (no heatsink or fan) I noticed temps were nearing the 80C range doing some very light web browsing. Decided not try again till i put a heatsink and a fan on it. Will try installing armbian and doing further tests during the week.by alexr - Off-Topic
Could be a quality control issue with these boards? I bought this same deal, but I opted not to flash the "boot from usb" uboot linked above. Instead I picked up a small heatsink meant for the RPI 3/4 as well as a fan + case. So far it's been pretty stable. Temps hover around 45C-52C. I'm running a Recalbox/Retropie/Lakka community image with a slight overclock and soby alexr - Off-Topic
I can confirm the newest kernel release solves the build issues some were having with kernel modules. You no longer have to symlink the header files to get them to compile. Thanks for all your hard work Bodhi, it's very much appreciated!by alexr - Debian
This is interesting as i remember having a similar issue when I was trying to compile unofficial drivers for the Edimax EW-7811UN. There was some issue that needed to be solved by creating symlinks from the "build" dir to the headers as outlined in this post by Mieki: https://forum.doozan.com/read.php?2,26114,26160#msg-26160 after doing that I was able to compile the driver succeby alexr - Debian
I remember thinking it was attached in a very flimsy manner when I opened up one of my E02's. There are no anchor points holding it to the board, just the two power pins soldered to the board. It could definitely do with some kind of epoxy holding it down.by alexr - Debian
The compiling sqlite3 step in the compilation process is the longest step by far and definitely requires a swap file on any machine running less than 256MB of RAM.by alexr - Debian
I've found some usb keys just aren't compatible. Mostly Kingston brand usb keys. I've had no issue with Sandisk branded ones.by alexr - Debian
Are you using ext4 for your rootfs drive? Any chance it's related to this bug/issue? https://bugzilla.redhat.com/show_bug.cgi?id=1527783by alexr - Debian
Any chance it's a spotty usb thumb drive? I've seen behavior much like this on a pogo-e02 of mine which was tracked down to a bad usb thumb drive. New sandisk drive fixed it right up.by alexr - Debian
I actually wrote up a quick guide on how to install the pi-hole software on a pogoplug a few days ago. You can find it here: https://www.reddit.com/r/pihole/comments/abgrog/quick_pihole_install_guide_for/ Doing a basic install with the default block-lists on a pogoplug mobile (v4-a1-01) has it idling at roughly 50MB of RAM consumed according to htop. This is using bodhi's latest rooby alexr - Off-Topic
It does not. You'd need to use something like checkinstall for that. I've built it with checkinstall in the past, but I don't think it produces a .deb package that is meant to be redistributed. That said it has installed properly on several Pogoplugs for me before in the past: https://www.dropbox.com/s/k1zbvqcdtpjpvfn/node_0.10.48-1_armel-stretch.deb?dl=0 I figured i'by alexr - Debian
You might have an issue as the last version of nodejs I've been able to compile/get working was v0.10.48. There's apparently some issue with V8 dropping support for non-armhf processors. If this version is compatible with the software you're trying to run I've taken the liberty of writing up a quick guide to compiling it from source on your pogo: Prerequisites: sudo apt-gby alexr - Debian