@codier Looks like you did replace the envs with new default envs so you need to restore them on top of what you have: These are rescue system related envs installed by Jeff's script. Use fw_setenv to set each of these at comand line. rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params rescue_bootcmdby bodhi - uBoot
Adam, The below bold lines are my correction. First, because you are inside a live Pogo E02, and with 2 more sync commands to make sure: cd /boot cp -a zImage-3.17.0-kirkwood-tld-1 zImage.fdt cat dts/kirkwood-pogo_e02.dtb >> zImage.fdt # I added the following line to deal with the uImage.orig file that i created the first time i ran this script in december mv uImage.orig uImagby bodhi - Debian
Adam Wrote: ------------------------------------------------------- > i looked back at my install notes, and it is > definitely because i didnt change > "kirkwood-goflexnet.dtb" to > "kirkwood-pogo_e02.dtb" > > > ok so now i know that i improperly installed two > pogo e02 units, but they are both about 1000 miles > away right now. what elby bodhi - Debian
Adam, > status:green:health status:orange:fault > These are correct for Pogo E02 > in the other three, /sys/class/leds/ contains: > status:green:health status:white:left0 > status:white:left2 status:white:right0 > status:white:right2 > status:orange:fault status:white:left1 > status:white:left3 status:white:right1 > status:white:right3 >by bodhi - Debian
codier, You need to tell us which Linux system you can boot into, or if you can't boot at all. For example, stock Pogo OS, Debian, Arch, rescue system .... They are slightly different when it comes to how to make fw_printenv and fw_setenv available... I am not sure I undertand what your current system is, and what you are trying to get to.by bodhi - uBoot
codier Wrote: ------------------------------------------------------- > Hi Bodhi, > > I already made your latest one which is 31 Oct > 2014 version of 3.17 > I will start from there and if I can boot in then > I will my env. It's pain in the xxx as I really > have hard time to use putty to check each env > line. > is there any easy way to read the env?by bodhi - uBoot
Can you remote login to those boxes? if you can then it's easy to look at possible syntax errors in rc.local (most of the the time it is that simple).by bodhi - Debian
Waynosan, See this thread to see what needs to be done. Note that the instruction to backup NAND from Pogo POS is slightly different than from inside Debian or Arch. But it should give you some idea about the technical details (this instruction can not be used as is in your case). And, you don't need to connect serial console to the virgin E02 to do it. However, I'd say that you sby bodhi - uBoot
LeggoMyEggo Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > A small correction: kernel 3.17 for Oxnas was > not > > come from Jeff. It's my kernel build which is a > > derivative of kref's kernel build! > > > Hehe I thought your name was Jeffby bodhi - Debian
hachigo, > Is it necessary to flash the default u-boot env > when you update the U-Boot? All it seems to do for > my Pogoplug v2 is brick it. No, it is not necessary. And the flashing instruction in the 1st post advised you not to do it if your current u-boot is from Jeff's script, or your u-boot env is already at 0xC0000 . Only flash it if you are installing from stock.by bodhi - uBoot
Waynosan, I've noticed you said: QuoteI have at my disposal, a box with Linux Mint (I'm a linux noob though), Win 7 x64, and another E02 Pogoplug, which I do not want to modify in any way, but perhaps it may be helpful for troubleshooting. You could restore your modded Pogo E02 to factory using the other virgin Pogo E02 mtd0. Let me know once you decide one way or the other. Wouby bodhi - uBoot
@Buck, Looks like my hunch about kermel version is probably correct. It is an old bug, but don't know it has been fixed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=437466 In any case, good luck and let us know.by bodhi - Debian
A small correction: kernel 3.17 for Oxnas was not come from Jeff. It's my kernel build which is a derivative of kref's kernel build!by bodhi - Debian
BuckNaked, > Bad kernel version specification at > /usr/bin/module-assistant line 568, <$apt> line > 6. > Bodhi, do you think I should assume the problem is > in module-assistant and seek help at one of the > debian forums? From the looks of this, my guess is that module-asistant can't deal with a version number that does not match the formal convention.by bodhi - Debian
@hans, Good work! It will be a good reference for people who want to install with new Debian rootfs only. Suggestion: put these commands (and other commands in your post) in a code tag so it is easier to read (so lines don't wrap): fw_setenv arcNumber 4495 fw_setenv mainlineLinux yes fw_setenv bootargs_stock 'console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uby bodhi - Debian
holelee, > I found I should set > usb_ready_retry(http://forum.doozan.com/read.php?3 > ,12381,15608#msg-15608) and repeat "usb start" > command in order to reboot successfully. > usb_ready_retry setting without repeating "usb > start" command can't solve the problem. > Just repeating "usb start" without setting of > usb_ready_reby bodhi - uBoot
Waynosan, > I see. Is there a way to re-flash the original > boot code back onto the device and start over? I > think it will be quicker that me trying to fumble > around and troubleshoot it with my total lack of > kung-fu in this area. > > Thanks for your continued support! Yes there is. But it is even more prone to new problem!. I think you should resolve theby bodhi - uBoot
codier, > I have 2 dockstars. one can see it by using nc. I > think because I add following env > > fw_setenv if_netconsole 'ping $serverip' > fw_setenv start_netconsole 'setenv ncip $serverip; > setenv bootdelay 10; setenv stdin nc; setenv > stdout nc; setenv stderr nc; version;' > fw_setenv preboot 'run if_netconsole > start_netcby bodhi - uBoot
I'm not sure I get what you're trying to do! Why module-assistant is needed? Can't you just install this manually: apt-cache show xtables-addons-common And then install whatever is on the required list apt-get install xtables-addons-common .......... PS. nvm, I understood what you trying to do. Food for thought: even though kernel-package is obsolete, you couldby bodhi - Debian
Correct. Your u-boot is fine. And everything looks great, except systemd network service. Arch u-boot installation does not allow booting back to Pogo OS. That's why you cannot boot without USB.by bodhi - uBoot
Buck, Dowload the 3.17 kernel tarbal (same thread). Extract the headers from it. Copy it to rootfs /boot and install it from there while system is running. Sorry I forgot, basic rootfs doesnot have headers file on it! I make a note to do that.by bodhi - Debian
BuckNaked Wrote: ------------------------------------------------------- > The linux headers don't appear to be present and > don't appear to be available. Results: > > > root@debian:/etc/apt# cd /boot > root@debian:/boot# > root@debian:/boot# apt-get install > linux-headers-3.17.0-kirkwood-tld-1 > Reading package lists... Done > Building depeby bodhi - Debian
I've noticed you are not at /boot. Have you tried to install linux headers first? cd /boot apt-get install linux-headers-3.17.0-kirkwood-tld-1by bodhi - Debian
BuckNaked, Try cleaning up your dpkg and then execute module-assistant again: apt-get clean dpkg --clear-avail rm /var/lib/apt/lists/* --force dpkg --configure -aby bodhi - Debian
codier, > I followed your instruction but I couldn't boot > into rescue again. Did you have rescue system running before? the u-boot envs setup for rescue system needs to the same as installed by Jeff's script. If you have flashed the new default envs, then the rescue system setup were erased. - interrupt netconsle and get the envs listing: printenv - If you did reby bodhi - uBoot
Waynosan, > As suspected, something is messed up with the > network setup. Not sure what I need to do next to > proceed.... Excellent! and you're right. This systemd problem should be solvable, but Arch rootfs specific. I'd suggest you post this boot log at Arch site, someone there will know what needs to be done.by bodhi - uBoot
Waynosan, QuoteWhat I failed to do was sync after running the tar command so I'm not certain if all the files were written onto the USB drive. This could be the only reason you had problem booting with Arch rootfs. QuoteUnfortunately I didn't keep a log of the installation but I followed the process here: http://archlinuxarm.org/platforms/armv5/pogoplug-v2-pinkgray If you raby bodhi - uBoot
bonk1990, Sounds like you are trying to run the new rootfs with stock u-boot? Pls post in this NSA325 thread: http://forum.doozan.com/read.php?2,14351 It's best that someone who runs the NSA325 with stock u-boot and new rootfs would post a listing of their envs, and you can follow that.by bodhi - Debian
@Peacemaker, > @bodhi here is as well my problem, I've no idea > why Uboot doesn't load up the harddrives. If I > choose a newer Uboot (this is the vendors Uboot). > I's not working anything (as the original Stage1 > can't load fat partition or ext4) or only one disk > with only 128mb ram or these sort of thinks As I mentioned, I've lost trackby bodhi - Debian