Skakz, I don't use Pogoplug services either. No worry! I just thought that mtd4 might conflict with your Pogoplug device ID so you would have problem registering the Pogo services if you plan to do so.by bodhi - uBoot
skakz, Sounds great :) sounds like you got a good plan. What I am interested to know is that if you're going to try to log into the Pogo V4 stock roofs? Just like when we usually started with a new Pogo V4. I'm not sure about that part, because the mtd4 backup is from my Pogo, so I'm wondering if you can log in, or you will need to re-register the Pogo. Or you don'tby bodhi - uBoot
Cool! let us know about the next steps you will take. Whether you need to go back to register your Pogoplug V4 at Cloudengines again? and the rest of the story :) for others who might need to do the same.by bodhi - uBoot
skakz, I looked at my log for the nanddump. Yes :) the nanddump was done with oob and noecc: /tmp # ./nanddump -nf usb/mtd0 /dev/mtd0 So to restore with nandwrite, we need -no option to indicate that the mtd0 file was dumped that way. To restate the steps: 1. make sure the mtparts are correct # fw_printenv mtdparts mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8by bodhi - uBoot
skakz, I think you should flash Davy's uBoot back to NAND with tftp and setup good envs like I mentioned above to boot normally with either USB or SD card. I'll double check the backup mtds.by bodhi - uBoot
:) Ok then you should reflash Davy's uBoot using tftp after you've booted with UART: Put the uBoot image uboot.nandpogoV4-MMC-mtdparts-noSATA.kwb in tftproot directory and then Pogov4> tftp 0x800000 uboot.nandpogoV4-MMC-mtdparts-noSATA.kwb Pogov4> nand erase 0x0 0x80000 Pogov4> nand write.e 0x800000 0x0 0x80000 After that, follow the rest of this Pogo Mobile post toby bodhi - uBoot
Yes, log into Debian and flash from command line. mtd0 backup file should be in the current directory where you reflash. So boot the box as usual into linux, and go to the directory where you have mtd0 backup file.by bodhi - uBoot
This post was updated 09/26/2013 to correct the nandwrite command See this post for explanation: http://forum.doozan.com/read.php?3,13603,13675#msg-13675 This post was updated 09/28/2013 to include hints about registering for original Pogoplug services after reflash the mtd backups (thanks spooky 2012). -------- My original Pogo V4 mtd backups (mtd0 to mtd4): Download at Dropbox:by bodhi - uBoot
skakz, Before doing the flash, you can try UART booting as described below. Yes it does work :) I recalled dhead's experience with the Pogo Mobile. Apparently, this Pogo V4 box and its cousin the Pogo Mobile has the same quirk. We have to try to run kwboot many times before it actually takes the handshake. 1. First, boot up both boxes, the one that you are going to run kwboot, and theby bodhi - uBoot
dinjo1 Wrote: ------------------------------------------------------- > I found these should i go ahead with them ? > > > http://www.ebay.com/itm/Seagate-STAK100-FreeAgent- > GoFlex-Net-Media-Sharing-Device-NEW-/390485796310? > pt=LH_DefaultDomain_0&hash=item5aeac465d6 > > http://www.ebay.com/itm/Seagate-FreeAgent-GoFlex-N > et-Media-Sharing-Transfer-Duby bodhi - Off-Topic
skakz, I did not forget about this! been pretty busy lately. Will post soon.by bodhi - uBoot
pbg4 Wrote: ------------------------------------------------------- > Hi enavarrocu, > > as bodhi pointed out you can change the leds > behaviour in rc.local and adapt it > to your specific needs, perhaps it is better to > use the ide-disk trigger, my rc.local on a nsa320 > with a > 3.10.1 ARCH ALARM type kernel contains something > like: > (which off coby bodhi - Debian
JohnXX, > I actually did see the uboot installation > instructions already, but I wanted to double check > since the page for the automated installer seems > to suggest it should be run from the Seagate > Dockstar distro with no USB devices plugged in. Yes, the installation instruction was written for people who have not installed the new uBoot and Debian, and they wouldby bodhi - uBoot
enavarrocu Wrote: ------------------------------------------------------- > I make the system led work add this in rc.local > before the exit 0 > > if [ -d /sys/class/leds/nsa320:green:sys ]; then > echo default-on > > /sys/class/leds/nsa320:green:sys/trigger > echo none > > /sys/class/leds/nsa320:orange:sys/trigger > fi > > Anything abouby bodhi - Debian
skakz, Your dmesg shows the SATA port. Have you tried to plug in your HDD after Debian is running? See after you do that what your dmesg will say, and if you can see the HDD. I can help you with the command to reflash the orginal NAND, but since you don't have UART booting working, it is risky :) BTW, I could not boot mine with UART, either. There is something strange with this Pogby bodhi - uBoot
JohnXX, Have you take a look at Jeffs uBoot installation instruction here? http://projects.doozan.com/uboot/ I never have the chained uBoot installed, so can't guarantee that it will work. However, if your mtd0 is what the Dockstar usually allocate then I think it wil work. You could post your output of the following commands here and we'll take a look. cat /proc/mtd cat /etby bodhi - uBoot
skakz, Looks like you also need to set machid so that it is recognized as the Pogo V4. fw_setenv arcNumber 3960 fw_setenv machid F78 Also, the kernel is Arch, not Debian, either! are you sure you're booting the right rootfs? [ 0.000000] Linux version 3.1.10-22-ARCH (nobody@) (gcc version 4.7.2 (GCC) ) #1 PREEMPT Fri Jun 28 21:43:02 CDT 2013by bodhi - uBoot
skakz, This seems to be dmesg from a different box. Definitely not Pogo V4!by bodhi - uBoot
skakz Wrote: ------------------------------------------------------- > thank you bodhi > yeah I didn't know :( I bought a sata hard drive > just for it! > so I see that is a very complicated subject! > mayabe the simpliest solution is to find a way to > restore those backups.. skakz, In Debian, run dmesg and post the output here! Thanks.by bodhi - uBoot
skakz, It is uBoot problem. Davy's uBoot does not have SATA support. So we only flash it to the Pogo Mobile. Only flash it to the Pogo V4 if SATA is not needed. I guess you were not aware of this. I also forgot about it because I don't use SATA on the Pogo V4. In any case, I got Davy's patch from his post here: http://forum.doozan.com/read.php?3,7601,7601#msg-7601 Will seby bodhi - uBoot
skakz Wrote: ------------------------------------------------------- > thanks bodhi, > finally with debian works fine. > > Now let's forget about nand and restoring original > fw. Llet's say I want boot from sata. > the easyst way is to put the kernel on the usb and > the rootfs on sata hard drive. > > the hardest way would be to install the alarmby bodhi - uBoot
skakz, Your bootcmd has a problem. That was the reason you could not boot Linux at all. Instead of flashing in serial console, it is much easier to flash in Linux. See this thread for how I prepared the Pogo Mobile (same as Pogo V4) to boot Linux: http://forum.doozan.com/read.php?2,11663 You already have Davy's uBoot installed. All you need is a correct uBoot envs set. In the aboveby bodhi - uBoot
skakz, Also, it would be helpful you interrupt uBoot and get the listing of envs: printenvby bodhi - uBoot
Skakz , See this post for example: http://forum.doozan.com/read.php?2,7806,13250#msg-13250 You could post your solution here and we'll double check!by bodhi - uBoot
DanK Wrote: ------------------------------------------------------- > Bodhi, > > thanks for all of your effort put into this > project. I am curious if debian can be installed > on a newly purchased pogo-p22. My attempts have > been unsuccessful. Should I keep trying? DanK, You'll need to verify whether the P22 is an OXNAS or Kirkwood. According to the Arch sby bodhi - Debian
optim, Back up your /boot/uInitrd and then regenerate it: mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.3.2-kirkwood-dg -d /boot/initrd.img-3.3.2-kirkwood-dg /boot/uInitrd The reason you see 3 versions listed because you did not remove old kernel images after you're installed 3.3.2-kirkwood-dg. Regenerate uInitrd will force the Linux to loaby bodhi - Debian
optim, IMPORTANT: since the apt-get upgrade got confused, I'm not positive that the commands below will remove the kernel cleanly. So back up your entire /boot directory somewhere first! and to be extra paranoid, you might also want to save the content of /lib/modules. The command to regenerate initrd.img is update-initramfs -u If you see errors, then you probably should removeby bodhi - Debian
optim, This looks OK. -rw-r--r-- 1 root root 1220456 Apr 23 2012 System.map-3.3.2-kirkwood-dg -rw-r--r-- 1 root root 107468 Apr 23 2012 config-3.3.2-kirkwood-dg -rw-r--r-- 1 root root 2279192 Apr 23 2012 vmlinuz-3.3.2-kirkwood-dg -rw-r--r-- 1 root root 6996747 May 24 2012 initrd.img-3.3.2-kirkwood-dg -rw-r--r-- 1 root root 2279256 May 24 2012 uImage -rw-r--r-- 1 root root 6by bodhi - Debian
optim Wrote: ------------------------------------------------------- > I have a Goflex home booting off of an 80G hd. I > am not much of a linux person, but I pick stuff up > here and there. > > I did a 'apt-get update', then I did a 'apt-get > upgrade' and it says that it replaced my 2.6.35 > kernel with 2.6.41 or something along those lines, &by bodhi - Debian
Hey Jake, Congrats! good to hear all system go :)by bodhi - Debian