LeggoMyEggo, If you have serial console, you don't need SATA to boot. If you already flashed my previous u-boot version, then it's simple to chain load the new u-boot, and then boot into Debian with USB.by bodhi - Debian
LeggoMyEggo, > I was just wondering if there was any hope for > having the boot.envs in nand for my one Oxnas > board with the bad blocks in mtd0 right in the > place where the boot.envs are stored. This will help to get around the bad block: http://forum.doozan.com/read.php?3,16017,20193,page=6#msg-20193by bodhi - Debian
I've uploaded the uboot.2013.10-tld-4 u-Boot image for Pogoplug V3 Oxnas. Please see 1st post for download link. This u-boot supports the following latest U-Boot features (among others): - Ability to customize u-boot envs in a script (uEnv.txt) during boot, without committing changes to NAND. This feature also can be used for rescue purpose where the u-boot envs were messed up, or whby bodhi - uBoot
LeggoMyEggo Wrote: ------------------------------------------------------- > > I just wish there were a lightweight alternative > for mysquirrel like lighttpd is to apache2. I've > checked and mariadb is not available for armel. > Bummer. sqlite?by bodhi - Debian
Was the usb formatted as EXT3? did you create the rootfs while logged in as root? and did you do a few sync commands before unmounting the USB drive? After that have been verified and it still has problem mounting rootfs. Then use the label approach: QuoteAnd see "B. Mounting rootfs in multi-drive configuration" in this post for how to set up to boot with multiple drives: http:/by bodhi - uBoot
FelipeC, Unplug everything else but the USB rootfs and reboot. The SD card presents has caused problem booting (need more envs adjustment if you want to boot with both plugged in). And see "B. Mounting rootfs in multi-drive configuration" in this post for how to set up to boot with multiple drives: http://forum.doozan.com/read.php?3,19093by bodhi - uBoot
LeggoMyEggo, I'm starting to look at rebasing the OXNAS u-boot to 2014, and realized that I have already have u-boot 2013.10-tld-4 for OXNAS version :) This version has caught up to the Kirkwood u-boot in most capabilities (EFI,,.. including uEnv.txt). I think I just forgot to add that release on my Todo list. Let me verify that and see if it should be released.by bodhi - Debian
I have a backup blog (link in my signature). I have not done anything with it yet, but it would be a good meet up place when the forum is down.by bodhi - Off-Topic
InfoScav, Summary of major steps: - It's best to connect a serial console first. - On a different Linux box, create a USB rootfs using this thread: Linux Kernel 3.18 Pogo V3 (Oxnas OX820) package and rootfs (Flattened Device Tree) - And then log in to Pogo OS, and install u-boot using this thread: 2013.10 U-Boot for Pogoplug V3 (OXNAS) - And plug in the the new rootfs, anby bodhi - Debian
LeggoMyEggo, > It looks like this technigue has been deprecated I > realize . My question is, could you put > boot.env's in mtd3 instead of mtd0 or is the > firmware always going to look to mtd0 for the > file? I'm curious This technique is still valid as always. But it depends on which version of u-boot being chainloaded. If it's old stock version, thenby bodhi - Debian
@LeggoMyEggo, Excellent! thanks for sharing your finding about Asterisk. It is very useful to a lot of users. > I do have my Pro > overclocked with WarheadSE's 850Mhz spl so I think > that makes a big difference. I did not know WarheadsSE has released a 850Mhz SPL, is that version on a SATA drive?by bodhi - Debian
FelipeC, Did you try this: http://forum.doozan.com/read.php?3,19081,19984#msg-19984 if you did, what did you see in serial console?by bodhi - uBoot
Tufkal, According to this output: > ## Flattened Device Tree blob at 62c00000 > Booting using the fdt blob at 0x62c00000 You have set up the new u-boot to boot the new rootfs with a separate DTB file. So recreate the USB rootfs Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2 per instruction in the first post, but be sure to skip this section: 4. Create uImage with embbeded DTBby bodhi - Debian
@sudos, > Now for the next question: , but I > want to know if it's correctly the same case to > edit using step 4b to update to kernel 3.18.5 for > 3.14, or if this step only applies to 3.16? I'm > going to make an educated guess that it is, Yes, it is. These steps can be applied the same to any kernel release version. So after step 3, go to 4b like you did beby bodhi - Debian
LeggoMyEggo, > a PP Biz which > wouldn't boot because the nand memory that holds > the boot.envs had some bad blocks which caused the > boot instructions (in nand) to be corrupted no > matter what I did to revise and save them. It > took me a while to figure out what was going on > and it was truly evidenced when I tried to reload > the latest u-boot and Iby bodhi - Debian
Tufkal, > Which way is less risky? Getting your newer uboot > installed, or giving the old uboot these > parameters manually? They are equally safe/risky. Given clear steps by steps instruction, carefully applied, the risk is minimized. Besides, there is a recovery path as described in the u-boot thread: Quotehttp://forum.doozan.com/read.php?3,16017 Recovery Unlike the Kirby bodhi - Debian
tufkal, You are stiil trying to boot with the old kernel in NAND. There is no need to do that. The new rootfs has the latest Debian kernel. So this needs to change boot_custom=run load_custom_nand boot || run load_custom_nand2 boot bootargs=root=/dev/sda1 ubi.mtd=2,512 rootfstype=ext3 console=ttyS0,115200 elev ator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M poweroutage=yes rootby bodhi - Debian
@megov, Have you tried to boot with arcNumber set to the NSA325, and earlyprintk=serial. - rootfs Debian-3.16.0-kirkwood-tld-2? - Or with kernel 3.16.0-kirkwood-tld-3 installed on top of tld-2?by bodhi - uBoot
woody, > Sorry if this is a dumb question, but can I safely > clone the updated U-boot from my new Pogo to my > older ones by using nandwrite to mtd0? Will this > transfer the environment variables, also? In fact, that's a really good question! because when you flash u-boot to mtd0, it only uses 512K, the remaining 512K is where the stock envs from old u-boot and new enby bodhi - uBoot
megov, > The 0x200 block from mtd0 is identical to kirkwood > - 32 bytes of main > header and 480 bytes of initial register content, > more or less similar > to kirkwood *.cfg. Same DRAM registers, same > window registers, > slightly different values (ddr3 differs). Perhaps it is like the NSA325. WarheadsSE u-boot build confirmed this. We used the 88F6281 and a sby bodhi - uBoot
Gravelrash Wrote: ------------------------------------------------------- > Theres nothing stopping anyone creating a subwiki > on wikipaedia with this info..... just a thought Jeff had a wiki. But not successful due to not enough volunteers. Perhaps we can resurect it.by bodhi - Off-Topic
cesvcid ethaddr Find them in you current envs, or in old log.by bodhi - uBoot
FelipeC Wrote: ------------------------------------------------------- > Im a bit traditional actually, so i prefer to > restore everything to stock, test it and then if > i'm feeling intrepid, i might go again and follow > gray's steps to make it samba enabled again!! > > Thanks for all your help, i will let you guys know > how did it go when i finish!!!!by bodhi - uBoot
Good job Robert! It is even a little better than having physical 2 buttons on the box if you use a wireless mouse :)by bodhi - Debian
FelipeC, > Bodhi, does that means that the suggestion from > grayman4hire is not entirely functional? Not really. gray's suggestion is perfectly OK if you want to continue having the new u-boot to boot back to newer Debian/Arch version. But it also has a setup where you can boot old u-boot and Pogo OS so you can use Pogo service. But it's not stock condition, it's a hyby bodhi - uBoot
@Gravelrash, http://forum.doozan.com/read.php?2,7806,7806#msg-7806by bodhi - uBoot
woody, Then it should work. The resuce system is a little old, but should be OK. You can either: - mount the rescue system rootfs in Arch and examine the rootfs content for /etc/network/interfaces, /lib/udev/rules.d/xx-persistent-net-rules, /etc/udev/rules.d/xxpersistent-net-xx for clues as why the network is not working. - reinstall the Jeff or davygravy's rescue system (this isby bodhi - uBoot
It does not look like the rescue system. Perhaps it's an old version... What is your envs rescue_installed force_rescueby bodhi - uBoot
woody, You need to restore your old rescue envs. The bold parts are missing. For example: bootcmd=run bootcmd_uenv; run bootcmd_usb; run rescue_bootcmd; reset force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi rescue_bootcmd=if test $rescue_installed -eq 1; then run rescuby bodhi - uBoot
isevewel, Yes. Because you're booting with multiple USB drives. Rootfs must be identified correctly as described here: http://forum.doozan.com/read.php?3,19093 Especially section B (Mounting rootfs in multi-drive configuration).by bodhi - Debian