Updating with what I discovered today. Previously the Pogo was never available as an airplay endpoint (speaker) on my network. I went into the shairport-sync config file and set it up to output audio to a named pipe and configured the path to that pipe. Once I saved the config, I was able to get shairport-sync to start successfully and now see my PogoPlug in the list of airplay devices. Stillby cdlenfert - Debian
I've been trying to get shairport-sync running on my Pogo Pro running on Stretch. I initially came up against a 16mb limit during the install. Resolved by this thread - https://forum.doozan.com/read.php?2,34313 After removing and re-installing shairport-sync via: apt-get install shairport-sync Everything looked to go smoothly. And here is the status. root@debian:~# systemctl statuby cdlenfert - Debian
The backdoor method didn't work for me for a recent Pro and Mobile model that I purchased. I suppose it's possible it works still on a very specific firmware version, but both my devices were on older firmware 2.x and 3.x (not latest) and the backdoor failed.by cdlenfert - Off-Topic
Check this Ebay listing - Pogoplugs for $4 each. There's a gotcha though - https://www.ebay.com/itm/122780928535?rmvSB=trueby cdlenfert - Off-Topic
Hey Buck, I'll also add that I was able to enable SSH via serial without soldering on the connections. I just held them in place long enough to edit the startup script and was good to go after that. Cramped my hand a little, but saved the pain and worry of mini-soldering.by cdlenfert - Debian
Thanks bodhi. That did it. root@debian:~# pidof systemd && echo "systemd" || echo "other" 1 systemdby cdlenfert - Debian
I am running the latest uBoot and rootfs (Debian 9 Stretch) on my Pogoplug Pro and I'm trying to enable systemd via the following instructions: A. How to use the uEnv.txt script This uEnv.txt script can be used to further customizing u-boot envs without saving to NAND or to boot with a completely different set of u-boot envs. Create a text file in /boot directory with the contenby cdlenfert - Debian
I've installed the latest rootfs on my pogopro, have set up a 256mb swap file, set the locale to en_utf8 and am only running Plex. Still the plex server just crashes constantly. I'm just stuck at this point.by cdlenfert - Debian
Thanks! Did you set English as the default locale? I read on the Debian wiki that you're not supposed to do that if you are accessing the device primarily over ssh. https://wiki.debian.org/Locale Get root and type dpkg-reconfigure locales and select the locale(s) you want to generate. At the end, you'll be asked which one should be the default. If you have users who access the sysby cdlenfert - Debian
Yeah, it seems to be getting to that point. Can you tell me the output you get for the following? I'm thinking my locale still isn't set: root@DebianPlugPro:~# locale LANG=C LANGUAGE= LC_CTYPE="C" LC_NUMERIC="C" LC_TIME="C" LC_COLLATE="C" LC_MONETARY="C" LC_MESSAGES="C" LC_PAPER="C" LC_NAME="C&quby cdlenfert - Debian
I wasnt able to use the configuration tool to generate the locale, so I edited the local.gen file manually to uncomment the en_US.utf8 line: root@DebianPlugPro:~# nano /etc/locale.gen root@DebianPlugPro:~# locale-gen Generating locales (this might take a while)... en_US.UTF-8... done Generation complete. My order is different if that matters? root@DebianPlugPro:~# locale -a Cby cdlenfert - Debian
root@DebianPlugPro:~# locale -a C C.UTF-8 POSIXby cdlenfert - Debian
Disabled the DLNA server, but that didn't reduce the ram usage it showed for Plex. It actually was higher at 213mb. Editing the default script file the only change was to change: PLEX_MEDIA_SERVER_MAX_PLUGIN_PROCS=1 Which I did. I had it =2 before. Added a library (single folder with 2 albums of appx 128kbps mp3 files). The scan crashed the plex server. Running htop after theby cdlenfert - Debian
thanks Bodhi, Almaz. I can't recall the command I entered to see where the Plex process was killed. But I did manage to run htop to see the following: 1 [|| 1.9%] Tasks: 30, 25 thr; 1 running 2 [|||| 4.4%] Load average: 0.65 0.68 0.82 Memby cdlenfert - Debian
What size is your swap? I'll reboot and run again and see when the crash occursby cdlenfert - Debian
I think it was an issue with my client machine. At least partially. I changed some network settings and was able to connect to the SMB share and have been streaming a full album without a single buffer. For some basic use, the wifi looks like it's going to be adequate. Thanks againby cdlenfert - Debian
Thanks! Looks like it's wlp0s0 now [ 2.603220] rt2800pci 0000:00:00.0 wlp0s0: renamed from wlan0 after updating /etc/network/interfaces with the following auto wlp0s0 iface wlp0s0 inet dhcp wpa-ssid "mywifi" wpa-psk "mywifipassword" and then restarting activating the wifi via: ifup wlp0s0 I was able to get an IP on the wifi interface, and conneby cdlenfert - Debian
Still crashing on my after initiating a scan. Here is the output of vmstat after starting Plex. The second line was the point that it was up and running. 0 0 0 8692 4704 86024 0 0 0 0 202 12 0 0 100 0 0 2 0 0 2188 4712 84308 0 0 10 0 377 110 23 4 73 0 0 0 1 864 1888 5584 73572 0 173 1949 195 3974 1399 31 8 48 13by cdlenfert - Debian
bodhi Wrote: ------------------------------------------------------- > cdlenfert, > > This wifi/ethernet is a common problem with the Po > go Pro. I'll find the post where you can follow to > set it up correctly. On the latest rootfs, uboot, and kernel. I'm unable to get wifi working on the PogoPlug Pro. I tried working through Qui's old guide with some modby cdlenfert - Debian
Edit: Don't read below (unless you're bored). I was able to restart my router and get the connection working again. Moving on to trying to configure Wifi on the Pogoplug Pro. When I had things up and running at home I could do ifconfig and get the IPV4 address of my Pogo. After bring it to the office and trying the same, the IPV4 address is not longer listed. I can't find it anyby cdlenfert - Debian
I've decided to try Plex on my new PogoPro with the latest uBoot, Kernel, and rootfs. This is the result after a reboot. cat /proc/cmdline doesn't mention zswap. It is however in the demsg output. root@debian:~# cat /proc/cmdline console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=41000000.nand:14m(b oot),-(data) root@debian:~# cat /uEnv.txt custom_paramby cdlenfert - Debian
Way harder forehead palm!!!! Sorry for the trouble, and thanks for pointing it out. It all works now.by cdlenfert - Debian
Tried again from scratch on the rootfs drive. Everything seems to go fine. The thing I didn't expect is the lack of the /media/usb1/etc/fstab file. I created it and put the stuff from step 3 into it. Quoteguide Adjust fstab (optional). Edit /media/sdb1/etc/fstab entry for root device to match the rootfstype of your rootfstype if you use Ext4 or Ext2. However, you can keep it as isby cdlenfert - Debian
Forehead Palm ... Totally missed that label. Went back and changed label using: e2label /dev/sdc1 rootfs Was able to confirm the change, but the system still will not boot. root@DebianPlugPro:~# lsblk -o name,mountpoint,label,size NAME MOUNTPOINT LABEL SIZE sda 3.7G `-sda1 / rootfs 3.7G sdbby cdlenfert - Debian
Here were my steps in creating the new rootfs. Unfortunately I wasn't able to boot off it with the PogoPro with new uBoot. root@DebianPlugPro:~# fdisk -l Device Boot Start End Blocks Id System /dev/sdc1 2 15265791 7632895 b W95 FAT32 root@DebianPlugPro:~# mkfs.ext4 -L "EMTEC8GB" /dev/sdc1 mke2fs 1.42.5 (29-Jul-2012) Filby cdlenfert - Debian
Cool! I'll give it a shot. My only linux system is another PogoPlug, so I'll set up rootfs once I can get access to the other Pogo. Any idea why my fw_printenv output was so short? ## Result of fw_printenv (note: ethaddr and fdt_file are only there because I manually set them [# /tmp/fw_printenv bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipby cdlenfert - Debian
Hey Bodhi, it's me again! I decided I wanted to install Debian again (on a different Pogo Pro) and this time get on the latest kernel, uBoot, and rootfs. However midway through I LOST POWER!!!!!!. So it’s back to the serial console for me, and hopefully I can restore again. My main concern is that I was missing something in my approach because when I did a fw_printenv I did not see theby cdlenfert - Debian
They all say the same. # e2label /dev/sdb2 e2label: Bad magic number in super-block while trying to open /dev/sdb2 Couldn't find valid filesystem superblock.by cdlenfert - Off-Topic
I neglected to mention this is a stock Pogoplug E-02 running SMB shares via Optware. Here's the output on the kernel. # uname -a Linux Pogoplug 2.6.22.18 #81 Tue Oct 19 16:05:00 PDT 2010 armv5tejl unknown I put your script above in place and called it in the startup script "etc/init.d/rcS". The end result was the same, but I thought it was cool to see that I didn't boby cdlenfert - Off-Topic
I ordered 2 of the Pogoplug POGO-P01 devices from adorama this year and received a Pro with wifi both timesby cdlenfert - Off-Topic