LeggoMyEggo, You can use the same addresses you are using right now to boot Debian for these images: openwrt-oxnas-pogoplug-pro.dtb 01-Apr-2015 21:24 6993 openwrt-oxnas-uImage 01-Apr-2015 21:25 1682760 openwrt-oxnas-uImage-initramfs 01-Apr-2015 21:25 3377656by bodhi - uBoot
LeggoMyEggo, I see where you would have problem booting from the tld-5 u-boot . This OpenWRT image is FIT image, not legacy image (i.e. uImage). Therefore the name is: openwrt-oxnas-pogoplug-pro-fit-uImage-initramfs.itb. And according to your boot log, it does not contain an initrd. But it does contain the DTB file. And the boot address is 0x62000000. So the correct way to boot using tlby bodhi - uBoot
@restamp, I see what you meant. FWIW, I recall that I used to have a setup with only Debian ntp pool servers, sometime it took forever to sync. I switched to a group of specific ntp servers that geographically near me (only hope it will be faster) , and have never seen the long wait again. Also, I use Google DNS 8.8.8.8 in the resolver.by bodhi - Debian
Thanks restamp, Arrg.. Pogo E02 seems to have different kernel versions. This might be the reason that sometime users have problem booting back to the stock OS. My Pogo E02 has a different kernel. This kernel behaves badly when I chainload it: QuoteLinux version 2.6.22.18 (bdietrich@buildman) (gcc version 4.2.1) #81 Tue Oct 19 16:05:00 PDT 2010 Errors in mounting rootfs. This error repby bodhi - uBoot
@Joey, Gravelrash said it well. You will benefit greatly with a Gbit switch, if you transfer large files among the Poplugs that plug in to that switch (they are going to be operating at Gbit speed doing that). OTOH, any thing that wired through the router communicating with others will be at 100Mbs speed.by bodhi - Off-Topic
LeggoMyEggo, > I think the plug combined with a > managed switch (for VLAN support) or with second > usb ethernet adapter would make a great router / > AP. Without the switch, it would be at least a > great AP. Dual core and 128Mb of ram and nand is > a whole lot more than most routers (even expensive > ones) come with. All the parts are there it's > justby bodhi - Off-Topic
LeggoMyEggo, > In other words, > could I just use your u-boot and through uEnv.txt > load the OpenWRT uImage file into memory and boot > that? This is what I think you should try.by bodhi - uBoot
rkrug Wrote: ------------------------------------------------------- > I guess that I need to use a netconsole. A > comprehensive portscan using zenmap / nmap only > showed the following ports open: > > > PORT STATE SERVICE VERSION > 2343/udp open|filtered nati-logos > 16498/udp open|filtered unknown > 19374/udp open|filtered unknown >by bodhi - uBoot
TEN/restamp et al, If you happen to have an unmodded Pogo E02, and with serial console connected, could you capture a serial boot log and post here? The boot log should be from the time u-boot starts until the Pogo OS login prompt. Thanks!by bodhi - uBoot
LeggoMyEggo, > Per the above, two u-boots are loaded in > sequence. Ah! sorry I did not read the log closely, you are chainloading the OpenWrt u-boot from my u-boot, both were flashed to NAND. I don't think this chainloading is needed. Have you tried to boot without chainloading? Or you could have just coppied the OpenWrt u-boot envs and put that in uEnv.txt, and boot. I haveby bodhi - uBoot
Perhaps the time server that you use would make a difference? When your ntpd failed to start, what was the time relative to when ntpdate finished? and what versions are ntpd and ntpdate?by bodhi - Debian
@Ingmar, Hey, busy is good :) and congrat on your new job!by bodhi - Debian
restamp Wrote: ------------------------------------------------------- > But, as I said, setting the date on boot for a > machine that has no RTC is anything but > straightforward. Could be. But I have all my boxes without RTC and with RTC, never failed to set the date. Just wonder what could be the difference?by bodhi - Debian
LeggoMyEggo, > > Notice I have overlapping u-boots. > Why would you have overlaping u-boot?by bodhi - uBoot
I have 3 GFHome and they are running OK with RTC. Fwiw, you could also try SNTP in U-boot. It is a good solution, no need to run ntpdate. And the dockstar does not have RTC.by bodhi - Debian
ingmar_k Wrote: ------------------------------------------------------- > Hi guys, > > just out of curiosity: > Anyone tried anything else than a mini pcie > wireless card in the mini pcie slot of the pro, > lately? > I remember trying a mini pcie usb3.0 and sata > card, a while back. But without success, as far as > I can remember. > Could have been a poby bodhi - Debian
@John, I think this is a good hint on running systemd, no doubt. However, I still don't see ntp and ntpdate have problem at all since I've been running them for a few years. Here is a just rebooted Dockstar log: root@Dockstar:/localdisk/linux/uboot# logread | grep ntp Mar 30 02:33:28 Dockstar daemon.notice ntpdate[1087]: step time server 164.67.62.194 offset 1427707973.00886by bodhi - Debian
LeggoMyEggo, 1. How far did you go in booting with NAND u-boot? pls post serial console log. 2. If you've already doing that what are the show stoppers now?by bodhi - uBoot
LeggoMyEggo, > Hoping > someone could figure it out as I think the Pro / > V3 with built in mPCI-e wifi with Atheros 300M > card would make a perfect router / AP: Not taking > anything away from this site, I've got my other > plugs running bodhi's Debian :) If you post your problem booting OpenWRT here in u-boot section, I will help. Don't worry aboutby bodhi - Off-Topic
Adam Wrote: ------------------------------------------------------- > I have been doing some searching here on the forum > to get started on one of these POGO-V4-A1-01 > units. > > It would seem that in the past, this model was > harder to get working, but now it is simple as the > others? I would like to boot from SD so that I can > actually use the one USB portby bodhi - Debian
@TEN, > Pogoplug E02 that will be used for your FDT Debian > jessie keeping Stock Pogo OS (minus hbwd) as a > fallback. See this for the current status of Pogo E02 u-boot: http://forum.doozan.com/read.php?3,12381,20793#msg-20793by bodhi - uBoot
Ok, thanks boss :)by bodhi - uBoot
@restamp, > Can anyone confirm that the 2014.07 fsload > works OK on their E02? I've just run a test and got the same errors! so I think you're right. It does seem to be an issue with u-boot configuration regarding this jffs2 partition. UPDATE: I've just peeked at the code (difference between Dockstar and Pogo E02). Yes, there was a missing configuration for jffsby bodhi - uBoot
grayman4hire > FYI - the PPV4 uses UBI (ubifsload) versus JFFS2 > on the E02 so I haven't personally tested fsload. > I'm still using Jeff's uBoot on my E02 and haven't > found a reason to upgrade yet. Ah! thanks for that gray! I've since verified that fsload loads the dockstar orginal u-boot image just fine on my Dockstar. I will try the Pogo E02 shoby bodhi - uBoot
@restamp, Thanks restamp! forgot about that, fat fingers :) in any case, e2fsck won't check the mounted file system even if we try.by bodhi - Rescue System
@twinclouds, > Will this rescue system work on Pogoplug Mobile? > or we do have one for it? You probably already figured this out? (the post is old). In case you did not attempt: no I dont' think it will work on the Pogo Moible.by bodhi - Rescue System
nicco, Your Arch rootfs must have been corrupted by the power outage. Take it to another Linux box and: 1. run fsck to repair the filesystem errors (if the stick is assigned as /dev/sdb1) e2fsck /dev/sdb1 sync sync 2. And try boot up the box again. 3. If it does not work, you will need to either restore this kernel file from a backup, or download Arch rootfs archive and copy it ovby bodhi - Rescue System
restamp, > 1. Has anyone gotten fsload to work under > 2014.07 (and if so, what's the secret)? I can confirm that fsload works on my Dockstar with the original Jeff's setup: pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fiby bodhi - uBoot
FelipeC, Cool! Glad it worked out well for you.by bodhi - uBoot
Ack210, > set_bootargs_usb=setenv bootargs console=$console > root=$usb_root rootdelay=$rootdelay > rootfstype=$rootfstype $mtdparts > rootfstype=ext2 > > Also, when I went in to edit /media/sdb1/etc/fstab > (actually on my computer it was > /media/rootfs/etc/fstab), I found no reference to > > /dev/root / ext2 > noatime,errorsby bodhi - Debian