I think you used the wrong link for the Debian (rootfs) install procedure. It should be https://forum.doozan.com/read.php?2,12096 for Dockstarby cdlenfert - Debian
I did the lookup. It said my local store had 18 in stock. However when I got there they couldn't even find 1. This has happened to me at OfficeMax before. Luckily the were accommodating and sold me a 2 pack of the same model and capacity for $6.by cdlenfert - Off-Topic
Thanks for finding that. I'm not sure what to do with it however. My EO2 is running stock OS, so shouldn't these stock envs already be set? I don't have serial console hooked up (though I could if I had to, but would rather not disasemble if I don't need to). I'm not sure what next steps are given my current situation. Do I make some kind of image? Do a standard Debian inby cdlenfert - Debian
Will the same chainloading approach (post 1 with updated boot command in this post) I did on the pogoplug mobile work for the pogoplug E-02 model? I'm ready to make the leap on that device over to Debian, but still want the stock OS as a fallback recovery system. Thanks for any confirmation.by cdlenfert - Debian
And thanks to you in my other thread, I now know how to make and restore backups, so the next failure will be a breeze :)by cdlenfert - Debian
Update: I was able to get the problematic Pogoplug Pro to connect to the network and get an IP over the Ethernet connection. However still no SSH access. The issue was a failing or corrupt rootfs drive (probably failing hardware). Attempts to reformat the drive failed. I used a new flash drive and installed a fresh rootfs and was good to go again. It worked with my older uBoot and env settings. Aby cdlenfert - Debian
Had an issue with my original Pogoplug Pro (one that's running an older uBoot and rootfs). I couldn't SSH into it, though it was on the network and I could ping it with a response. As a precaution, before I tried rebooting, I inserted the rootfs USB drive into my Mac (did not initialize) and did a full backup. This seemed to go flawlessly and I've had good luck creating iso backupsby cdlenfert - Debian
Got it done! Nice to have the USB port free for my sound card as I'm using this as an Airplay receiver. Nice and tidy!! Thank youby cdlenfert - Debian
So I have to mount my current USB rootfs on another box in order to create the tarball right? I can't do it on the box that's actively running the USB rootfs? Or can I if I create a basic rootfs on the SD card, remove the USB, reboot (running off SD rootfs temporarily), then remount the USB rootfs and create the tarball, reboot again with USB rootfs, remount SD rootfs, and restore tby cdlenfert - Debian
Things are working great with the USB rootfs drive. It's an 8GB flash drive. I'd like to move to an SD, but I'm not sure the best approach to take to clone everything over. I'm also fine starting from scratch with a new rootfs, but I'd rather clone if I can. I could make a backup image on my mac, and restore it to an SD card using something like Etcher, but I think that wby cdlenfert - Debian
very cool. And BTW it all worked! I rebooted into Debian and had SSH access and then was able to unplug the USB and SSH back into stock Pogoplug OS. Thanks for all the help along the way and wonderful files and guides. If there's any interest I'm happy to post a complete set of commands to take Pogoplug Mobile from stock to Debian with a recovery stock OS.by cdlenfert - Debian
Thank you. That's quite different. I'm curious to know why the bootcmd_exec was expanded in this way. But I've updated regardless :) Final fw_printenv for reference # /tmp/fw_printenv bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi bootdelay=10 bootdev=usb device=0:1 devices=usb ide mmc disks=0 1 2 3 ethact=egiga0 ethaddr=52:3b:20:9by cdlenfert - Debian
the last thing I want to check before attempting a reboot goes back to chain loading the pogo OS as a rescue system: Qui's bootcmd=run bootcmd_usb; run bootcmd_mmc; run bootcmd_pogo; reset Bodhi's bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec Because these are so different I wanted to be extra sure this is ok and won't cause any boot issueby cdlenfert - Debian
thanks for the update on the .dtb name for the pogo mobile. I've mad that adjustment. What I meant before was that I wouldn't know what file name to put without having the file on my rootfs drive. I tried unzipping the rootfs file from dropbox to see the structure but I couldn't unzip it on my Mac.by cdlenfert - Debian
Cool. thanks. I see that I'll need to create the rootfs before I can set the correct dtb file I imagine I'll have to do something like this fw_setenv dtb_file '/boot/dts/pogoplug_v4.dtb' swapping in (if needed) the exact file name for the pogoplug v4 dtb file that resides in /boot/dts Sound correct?by cdlenfert - Debian
Awesome! any problem with the MAC address not matching the sticker? and me not being able to change it with fw_printenv? ... quoted from above Now for my next stumper. I'm unable to overwrite my ethernet address. The last 2 commands show where it fails to overwrite. How big of a problem is this? # cat /sys/class/net/eth0/address 00:25:31:03:49:49 #from router #00:25:31:03:49by cdlenfert - Debian
Also if I could get another set of eyes on the fw_printenv output to make sure I'v got things set up right, or if there's an existing file to check against, that would be awesome. # /tmp/fw_printenv bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fby cdlenfert - Debian
Thanks renojim (JT). The issue was with the domain. My hosting company recently disbanded and pawned my account over to a new host and things are pretty jacked up and confusing. I was able to get to the correct files and they are validating now. Thanks for taking a look Now for my next stumper. I'm unable to overwrite my ethernet address. The last 2 commands show where it fails to oveby cdlenfert - Debian
Thanks. I tried that and can't pull it down of https. I don't think my version of wget on stock pogo (from 2011 because it's not possible to update the pogo OS anymore) supports it. Also when I pull from dropbox or my server and check the MD5 hash on my Mac, it's correct on both files. Could my wget on the pogo be messing up the file from my server? I've also confirmed thby cdlenfert - Debian
Update: In this case I'm also seeing the same hash for multiple files # md5sum uboot.2017.07-tld-1.pogo_v4.bodhi.tar 62b5bf1fc998b35626bdca6106677fbd uboot.2017.07-tld-1.pogo_v4.bodhi.tar # md5sum uboot.2016.05-tld-1.environment.bodhi.tar 62b5bf1fc998b35626bdca6106677fbd uboot.2016.05-tld-1.environment.bodhi.tarby cdlenfert - Debian
I hit a snag. I admittedly don't do this sort of thing too often, but I can't get a correct MD5 hash on the first file I've downloaded to the Pogo. In this case it's uboot.2017.07-tld-1.pogo_v4.bodhi.tar # ls flash_erase hbplug.log resolv.conf fw_printenv nanddumpby cdlenfert - Debian
Good to know and thanks for clarifying. Out of curiosity why would anyone choose to run the old stock u-boot. I've seen it mentioned in the instructions, but don't understand the "advantages". Thanks!by cdlenfert - Debian
One more question. It says to ask if I'm not sure and I'm not. Step F from https://forum.doozan.com/read.php?3,12381 ++++++++++++++ f. Adjust the DTB name to boot with a rootfs that has FDT kernel 3.17+ (this is the normal case): Find your box DTB file in the rootfs /boot/dts directory and adjust the env to it. For example, if the box is the Dockstar fw_setenv dtb_fileby cdlenfert - Debian
Thank you again. I've added it to my install process. I'll give it all a go later tonight or tomorrow.by cdlenfert - Debian
Thanks for the confirmations. I'm not sure I understand what exactly you mean by... QuoteBut it will not be running correctly as Pogo V4 I'd expect to primarily be running Debian, but in the event the rootfs drive fails and I remove it, it would fall back to Pogo OS as a rescue system right? Would it be my current stock OS which already has SSH enabled, or would I have to find a wayby cdlenfert - Debian
I'm in the process of installing Debian on a Pogoplug mobile running the stock OS. I'm trying to get all my ducks in a row with complete instructions before I jump in. I'm cross referencing Bodhi's threads for rootfs and uboot with Qui Hong's old guides on qnology.com. I'm interested in retaining the stock Pogoplug OS as a backup system in case my rootfs USB or SDby cdlenfert - Debian
One thing I caught in this thread is that you can put rootfs on a USB, then clone that to and SD card and swap them out? Is that correct?by cdlenfert - Debian
Pogo is definitely aware of the USB sound card. I've been able to get audio to play through it and it shows up when I: root@debian:~# aplay -l **** List of PLAYBACK Hardware Devices **** card 1: Device , device 0: USB Audio Subdevices: 1/1 Subdevice #0: subdevice #0 And yet root@debian:~# amixer amixer: Mixer attach default error: No such file or directory So I try re-insby cdlenfert - Debian
Haven't had much luck in troubleshooting. On Wheezy it worked out of the gate. root@debian:~# alsamixer cannot open mixer: No such file or directory root@debian:~# amixer amixer: Mixer attach default error: No such file or directory root@debian:~#by cdlenfert - Debian
Finally figured out that the output device I was using was incorrect. I had thought it was hw:0, but it was really hw:1,0 alsa = { output_device = "hw:1,0"; This got audio to output through Shairport-Sync to my cheapo USB sound card. I still don't know how to get audio control from the Pogo side of things without Alsamixer, but that can wait.by cdlenfert - Debian