Maybe a dumb question. But why is this needed? If you brake something, why don't you just reinstall the OS on the USB-stick/SD-card? Or repair the install by putting the media in another computer? What i've done is when i've damaged the installationen on the SD-card (for example), i've booted from a USB-drive instead (uboot = higher boot-priority) - with both units availablby JohnW - Rescue System
I've had these problems from the beginning - all since last year when i started off with your 3.16 image. It's that ntp is started to close to ntpdate. I've have never had it working correct. I can see that your ntpd is starting 9 seconds after ntpdate. At that time ntpdate is probably done and the sockets are free again. I guess you Dockstar doesn't have an RTC-clock eby JohnW - Debian
Bodhi, with systemvinit i had to add "mount -a -t nfs4" to rc.local to have the second nfs-share mounted at boot. With systemd i did not need to do that. My idea is that systemd is a bit more intelligent when it comes to pick the moment when to run stuff... Case closed.by JohnW - uBoot
I've been running ntpdate & ntp for a long time. The problem has always been that the ntp-service doesn't start at boot cos the sockets are in use (thanks to ntpdate). And if you uninstall ntpdate, ntp will fail 'cos the gap from 1970 is to big... And the -g option won't work either... You could always add a line to rc.local etc if you want but that's a bit mesby JohnW - Debian
TEN Wrote: ------------------------------------------------------- > JohnW Wrote: > > Too bad shipping to Sweden is $80 USD... Doh... > > Would non-U.S. addresses be eligible to rebate at > all (standard "mail-in your immortal soul, SSN, > Driver's License etc. in hope for a refund cheque > - that cannot be cashed at a foreign bank anyway" > proby JohnW - Debian
Yes you're absolutely right, i did read about it earlier - don't know why didn't think of it now, doh... Even qdftowner wrote about it above... Yes, i'm not fully aware of how and at which time the lines in fstab are processed - but you're probably right about it.by JohnW - uBoot
Hi Bodhi, I tested without the v3-syntax and it worked anyway. Theres no change in the output of "mount" if you add it, i choosed to include it anyway. Mount gave me: 10.0.0.22:/srv/nfs/hosts/pp02 on / type nfs (rw,relatime,vers=3,rsize=16384,wsize=16384,namlen=255,hard,nolock,proto=tcp,port=2049,timeo=7,retrans=3,sec=sys,local_lock=all,addr=10.0.0.22) My export is so standarby JohnW - uBoot
Haven't tried v4 either. By default it will use v3, even if you don't specify it. By default (comes with the new kernel) the rootfs will be mounted as read-only, so you'll need to add "rw" to "net_set_bootargs" as i did. Wasn't needed earlier. Anyways i'm happy with my NFS-setup... My PogoPlug V4 with a 2.5"-drive is exporting the rootfs forby JohnW - uBoot
Congrats on your success with the Pogo...! :-)by JohnW - Debian
Too bad shipping to Sweden is $80 USD... Doh...by JohnW - Debian
You'll have to edit your bootcmd aswall. Just add "net_bootcmd;" before reset in the end... fw_setenv bootcmd 'run bootcmd_mmc; run bootcmd_usb; run bootcmd_sata; net_bootcmd; reset'by JohnW - uBoot
Hi, i updated the envs a bit for use with my PogoPlug Mobile. Works great. It's using NFS only, no TFTP. I added DTB-support also. Bootlog: U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45) Pogoplug V4 gcc (Debian 4.6.3-14) 4.6.3 GNU ld (GNU Binutils for Debian) 2.22 Hit any key to stop autoboot: 0 ** Bad device mmc 0 ** ** Bad device mmc 0 ** Card did not respond to voltage seby JohnW - uBoot
That's awesome. Upload the mp3 files also please.by JohnW - Debian
Hi, Did you follow some old guide on how to hack the GoFlex? I know that theres people from time to time that runs Jeffs script that are no longer working correct. Just asking because the Kernel seems old. You would want 3.18.5 from here: http://forum.doozan.com/read.php?2,12096 If you did run Jeffs script maybe your Uboot isn't updated either. Any error messages?by JohnW - uBoot
Download the script here from now: Hi Don, thank you for asking the questions - always nice! :) You should be able to run this script on a ordinary PC with Debian or Ubuntu, the output will be the exact same! I myself ran it on my PogoPlug V4 (running Bodhis rootfs!), just that it took a bit longer on it (about 30-40 minutes?). Debootstrap is the component that does the magic and downloaby JohnW - Debian
Hi, I made a script that creates a complete "minbase" Wheezy-rootfs with the necessary modifications. It even installs the kernel for you. Yes i'm not the first one here that has done it. https://www.dropbox.com/s/424e2w7bkkcgld3/build_rootfs_kirkwood.sh?dl=0 It's based Klaus M's "build_rpi_sd_card.sh"-script (http://blog.kmp.or.at/2012/05/build-your-oby JohnW - Debian
Just a big note!!! When following Qui's blog on "hacking" the Pogoplugs you download nanddump. This seems to be a old version of the program in which "-o" means "omit oob-data". In Debian this is the other way around. If you're backing up a mtd-partition to write it to another Pogoplug you don't want the oob-data-version because it contains baby JohnW - uBoot
Just installed ntpdate again and rebooted and guess what... root@pogo01:~# ps ax|grep ntp 2053 pts/0 S+ 0:00 grep ntp And when you look at the bootlog... Jan 1 01:00:41 pogo01 daemon.notice ntpd[1898]: ntpd 4.2.6p5@1.2349-o Sat Dec 20 18:42:15 UTC 2014 (1) Jan 1 01:00:41 pogo01 daemon.notice ntpd[1899]: proto: precision = 2.130 usec Jan 1 01:00:41 pogo01 daemon.err ntpd[1by JohnW - Debian
Hi, trust me somethings wierd. I started off with a fresh 3.17 rootfs and ntp started OK manually. I rebooted 5-6 times after trying some update-rc.d-stuff, but the service wouldn't start automatically. "S01ntp" existed in "/etc/rc5.d/", so that's fine. Hmm. I can install ntpdate again and look if i can find wierd in the logs!by JohnW - Debian
Exactly, if others could check if they got "ntp" running after boot... ps -ax|grep ntpby JohnW - Debian
WD My Passport Essential 500GB USB 3.0: dd count=100 bs=1M if=/dev/zero of=./test.img 100+0 records in 100+0 records out 104857600 bytes (105 MB) copied, 4.51808 s, 23.2 MB/s Interesting...by JohnW - Debian
Sandisk Ultra SDHC 8GB (40mb/s): dd count=100 bs=1M if=/dev/zero of=./test.img 100+0 records in 100+0 records out 104857600 bytes (105 MB) copied, 10.6813 s, 9.8 MB/sby JohnW - Debian
These work to boot from. USB: Sandisk Cruzer Blade 4GB WD My Passport Essential 500GB USB 3.0 MMC: Sandisk Ultra SDHC 8GB (40mb/s) Haven't tested the speed though... The startup-time is the same with the slow Cruzer Blade and the Sandisk Ultra... (35 sec after kernel-boot).by JohnW - Debian
Hi, Correction! Reinstallationen of ntp did not fix it, i had to uninstall ntpdate to make it work! I had this problem on two Pogoplugs (V4/Mobile) running 3.16 in October. I tried a bunch of things and thought the reinstallation of ntp did the trick. But this didn't help on my new third 3.17 installation, so i took a look at the others which didn't have ntpdate installed. Sby JohnW - Debian
Also, since we all use the exact same rootfs with the same SSH-keys in common, it's recommended to regenerate these. # /bin/rm -v /etc/ssh/ssh_host_* # dpkg-reconfigure openssh-server Sample output: Creating SSH2 RSA key; this may take some time ... Creating SSH2 DSA key; this may take some time ... Restarting OpenBSD Secure Shell server: sshd.by JohnW - Debian
Just a note... The ntp-daemon doesn't autostart with Debian on the 3.16 and 3.17 rootfs. You can start in manually. Tried some stuff recommended by others on different forums to make it work but didn't succeed. I have had to reinstall it to make it work with "dpkg --purge ntp & apt-get install ntp"...by JohnW - Debian
You can restore dumps with oob-data using "-o", my bad...by JohnW - uBoot
You are right Bodhi... I've got the answer why the files turn up different. -o = Dump OOB data... nanddump -nof mtd0 /dev/mtd0 = filesize 2162688 (don't fit when writing to mtd0), the original envs get pushed to A5000... nandwrite /dev/mtd0 uboot.mtd0.pogo02.original.kwb Image 2162688 bytes, NAND page 2048 bytes, OOB area 64 bytes, device size 2097152 bytes nandwrite: error!: Iby JohnW - uBoot
As we all know on the Pogoplug V4, the original U-Boot envs are stored at address A5000 (dec 675840) in mtd0. However when backing up mtd0 from Debian, the original envs are now located at A0000 (dec 655360). How come? I did take a backup of mtd0 before upgrading U-Boot under the main Debian installation, this was done from Pogoplug OS. If i compare the two nanddumps, they differ in sizeby JohnW - uBoot
Thanks Bodhi! The config above did not work, this one does! arcNumber=3960 machid=f78 ethaddr=00:25:31:06:xx:xx ipaddr=192.168.0.231 serverip=192.168.0.220 baudrate=115200 bootcmd=run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; run bootcmd_pogo; reset bootcmd_usb=usb start; setenv root /dev/sda1; setenv interface usb; run set_bootargs; run boot; bootcmd_mmc=mmc rescan; setenvby JohnW - Debian