Show all posts by user

Re: Issue with fresh install on Pogo-E02 - 10 years ago

Adam I always recommend upgrade u-uboot to take advantage of new features. But with pogo e02 you have to be extra careful, because recovery path is Jtag. There is no UART booting.

by bodhi - Debian

Re: Issue with fresh install on Pogo-E02 - 10 years ago

Adam, > if you would still like me to post the list of > u-boot envs, i will, but right now im just super > pumped that they are working! No need to. > cd /tmp > wget > http://projects.doozan.com/uboot/install_uboot_mtd > 0.sh > chmod +x install_uboot_mtd0.sh > ./install_uboot_mtd0.sh > > after the script was done, i put in the new flash > d

by bodhi - Debian

Re: Linux Kernel 3.17 (FDT) and 3.16 (non-FDT) Kirkwood package and rootfs - 10 years ago

Buttzy10169 Wrote: ------------------------------------------------------- > Thanks Bodhi. > > Will the commands for flashing be the same as for > absintos? > > And any idea on the usb's problem? It's same as in this thread: http://forum.doozan.com/read.php?3,12381 Sorry I am not sure what USB problem?

by bodhi - Debian

Re: iConnect starting from scratch - 10 years ago

cr2013, You can do all that with new u-boot and new Debian rootfs. But the first step is to connect serial console and get the listing of your u-boot envs: Interrupt serial console at countdown, and then > printenv Steps: 1. Try to boot the new Debian rootfs first 2. Update u-boot 3. Modify u-boot envs to boot correct drive in multiple drives configuration.

by bodhi - Debian

Re: Issue with fresh install on Pogo-E02 - 10 years ago

Adam, Don't worry about the errors you saw. Just download the latest rootfs (3.17). And put it on an EXT2 drive and boot with it. And please get a list of your u-boot envs and post here (there is further improvement to do, especially whether the rootfs type is ext2 or ext3) If you can't boot with the new rootfs, then in netconsole, use: printenv If you booted into Debian, us

by bodhi - Debian

Re: Pogoplug E02 - Warning - readenv() failed, using default environment - 10 years ago

droidbox, These are the relevant default envs: arcNumber=2097 bootcmd=run bootcmd_usb; usb stop; run bootcmd_pogo; reset bootcmd_usb=run usb_init; run usb_load_uimage; run set_bootargs_usb; run usb_boot; usb_boot=if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000;else bootm 0x800000;fi; set_bootargs_usb=setenv bootargs console=$console root=$usb_root root

by bodhi - uBoot

Re: Linux Kernel 3.17.0 Pogo V3 (Oxnas OX820) package and rootfs (Flattened Device Tree) - 10 years ago

I think perhaps it's time to do a serious merge from Kirkwood config to OXNAS config. Ingmar has not said so yet again, but I can read mind :))

by bodhi - Debian

Re: Pogoplug E02 - Warning - readenv() failed, using default environment - 10 years ago

droidbox, You are running Jeff/davygravy u-boot build so I need to see the default envs. Please interrupt serial console and print out your u-boot envs: u-boot>> printenv

by bodhi - uBoot

Re: Pogoplug E02 - Warning - readenv() failed, using default environment - 10 years ago

@droidbox, You can't completely repair this. The bad block is at the env location for this u-boot version. And also is for my u-boot build images. It's a common location we've chosen for these Kirkwood boxes. However, there is a work around that will allow you to boot successfully. I'll post the instruction later today.

by bodhi - uBoot

Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile - 10 years ago

jfp, Not very detailed, but this is all we got: http://www.denx.de/wiki/view/DULG/CommandLineParsing

by bodhi - uBoot

Re: 2014.07 U-Boot for FDT and Non-FDT Kernel - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug - 10 years ago

@Sagittarius, > EDIT: booting on a USB key made it possible. It is OK now?

by bodhi - uBoot

Re: Pogoplug pink Boot loop Problems - 10 years ago

droidbox Wrote: ------------------------------------------------------- > Hey bodi, > > thanks for your answer. I read the guide, but it > is for a Pogo V4/Mobile Device. > I have a Pogoplug E02. > > It is right? > > droidbox Yes. Just use it as a guide for comparing bootcmd. Pogo V4 has different mtdparts, archNumber, machid (so don't use that). Bu

by bodhi - uBoot

Re: Linux Kernel 3.17 (FDT) and 3.16 (non-FDT) Kirkwood package and rootfs - 10 years ago

Buttzy, Looks good to me. U-boot is in the 1st 1M and no bad block in it. But please try UART booting first to make sure you have a rescue mechanism. Also, remember to save your envs listing, you will need to copy/paste them back in serial console (new u-boot envs are at different location).

by bodhi - Debian

Re: Linux Kernel 3.17.0 Pogo V3 (Oxnas OX820) package and rootfs (Flattened Device Tree) - 10 years ago

automatux, I'll build the next version and include it.

by bodhi - Debian

Re: Linux Kernel 3.17.0 Pogo V3 (Oxnas OX820) package and rootfs (Flattened Device Tree) - 10 years ago

automatux, Do you know the modules names?

by bodhi - Debian

Re: Pogoplug pink Boot loop Problems - 10 years ago

Take a look at this post: http://forum.doozan.com/read.php?3,16148,16148#msg-16148 And use it as a guide to fix your missing envs,

by bodhi - uBoot

Re: Clustering Pogoplugs.. - 10 years ago

@Don, I've been using the Pogos cluster mostly as compile farm for home use. As far as other distributed processing researches using these, I'm afraid that I can't discuss.

by bodhi - Debian

Re: Working USB-Sticks - 10 years ago

Mark, Very good serial console instruction by varkey (it's for a GoFlex Net, but should give you an idea in general for how to unbrick these pogoplugs). You might have to do some soldering if your plug does not have a header. http://varkey.in/seagate-goflex-net-serial-connection/ The link you posted above is very good, too. Which plug do you have? If you decide to purchase and c

by bodhi - Debian

Re: Working USB-Sticks - 10 years ago

@restamp, >Since it broke the uBoot, I'm presuming that it > somehow altered the uBoot bootcmd environment > variable). Yes, I think there must have been other envs that were set incorrectly this way. We can't tell for sure because Mark did not list them. The wrong command above would create a variable "bootcmd=usb" and assigned "start;" to it. So a

by bodhi - Debian

Re: Working USB-Sticks - 10 years ago

Mark, It should be /usr/sbin/fw_setenv bootcmd 'usb start; usb stop; usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset'

by bodhi - Debian

Re: Bootting off network - 10 years ago

habibie, > > I plan to create an env image that default to > > booting FDT kernel (like the one available > right > > now for non-FDT). > > > Do you have an ETA on that? No I don't have an ETA. I'm really busy with year-end stuff so not sure when I can do this. In the mean time, you can flash the existing default envs, and then you set up FDT boo

by bodhi - uBoot

Re: NSA320 back to stock configuration - 10 years ago

enavarrocu, I don't have the NSA320. Perhaps other who has can post the orginal envs. If you connect serial console, it'll be easier to see the problem.

by bodhi - Debian

Re: Linux Kernel 3.17 (FDT) and 3.16 (non-FDT) Kirkwood package and rootfs - 10 years ago

Buttzy, Do you have a boot log? Yes, this is the NSA320 u-boot. It has been tested by gaogao: http://forum.doozan.com/read.php?3,12381,16787#msg-16787

by bodhi - Debian

Re: Bootting off network - 10 years ago

habibie Wrote: ------------------------------------------------------- > Bodhi, > > Is there any works/plans in progress update uboot > to support envs for FDT kernel? I plan to create an env image that default to booting FDT kernel (like the one available right now for non-FDT).

by bodhi - uBoot

Re: GoFlexNet not getting IP - 10 years ago

@Neptune, One more thing! I've noticed that your USB drive is a little slow coming up. It did not affect the boot process, though. However, if you'd like to be a little more sure about booting, add this env to your u-boot env (15 is number of seconds u-boot takes to detect the drive before timing out): fw_setenv usb_ready_retry 15 My u-boot build has an extra timeout period f

by bodhi - Rescue System

Re: GoFlexNet not getting IP - 10 years ago

Neptune Wrote: ------------------------------------------------------- > I was not able to capture the whole log earlier. > Anyways, here is the complete log > > http://pastebin.com/GEaVNyf4 Everything looks great!

by bodhi - Rescue System

Re: NSA320 back to stock configuration - 10 years ago

enavarrocu Wrote: ------------------------------------------------------- > Hello guys, > > I'm trying to get back my NSA320 to it original > firmware because I want to sell it. I don't > remember exactly which configuration I made > because was a while ago. I get back the original > kernel from upgrade firmware file but it get > frozen after: > &

by bodhi - Debian

Re: Bootting off network - 10 years ago

habibie, > is it still necessary to perform both steps #6 and > #7 before step B (Flashing default u-boot envs > image)? Yes, from stock you will need to flash the default envs in 6 and 7.

by bodhi - uBoot

Re: Pogoplug pro mtd2 original rootfs nanddump wanted - 10 years ago

@Stephan, Sorry I could not find it! :) I should have saved them somewhere when I found them. I was so sure I remember where they are ... in my 12 plugs!!! However, if you are running Arch install from way back, then everything is still in NAND (stock u-boot and kernel). All you need to do is to run the oxnas-revese script to set the envs back to boot stock. And you can do this in Arch. Is

by bodhi - Off-Topic

Re: Linux Kernel 3.17 (FDT) and 3.16 (non-FDT) Kirkwood package and rootfs - 10 years ago

Herb, If you have other plugs running 3.17, do you see this on them? these type of notification should be in dmesg too. If you do then it's perhaps it's your network. I don't see this in any of my boxes (but I don't have the NSA320).

by bodhi - Debian