Show all posts by user

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

@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

Re: Restore Pogoplug V4 to factory State - 10 years ago

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

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

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 DTB

by bodhi - Debian

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

@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 be

by bodhi - Debian

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

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 I

by bodhi - Debian

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

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 Kir

by bodhi - Debian

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

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 root

by bodhi - Debian

Re: No serial output from kernel on Iomega ix2-dl(ng) - 10 years ago

@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

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

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 en

by bodhi - uBoot

Re: UART Booting HowTo for Selected Kirkwood Devices - 10 years ago

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 s

by bodhi - uBoot

Re: A Suggestion - Stickies for Common Operations - Searches - 10 years ago

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

Re: Restore Pogoplug V4 to factory State - 10 years ago

cesvcid ethaddr Find them in you current envs, or in old log.

by bodhi - uBoot

Re: Restore Pogoplug V4 to factory State - 10 years ago

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

Re: USB Keyboard. How to start? - 10 years ago

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

Re: Restore Pogoplug V4 to factory State - 10 years ago

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 hy

by bodhi - uBoot

Re: How do i recover from this....... - 10 years ago

@Gravelrash, http://forum.doozan.com/read.php?2,7806,7806#msg-7806

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

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 is

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

It does not look like the rescue system. Perhaps it's an old version... What is your envs rescue_installed force_rescue

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

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 rescu

by bodhi - uBoot

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

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

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

No it can't. Because uEnv.txt is processed after preboot. I could set it up a little differently to allow that. But I need to document it very clearly, in another release of the default u-boot envs.

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

woody, To avoid mistake that could lock out users, I've set netconsole to this default: preboot_nc=run if_netconsole start_netconsole To activate netconsole, set the preboot env in Arch: fw_setenv preboot 'run preboot_nc' Be careful doing this (copy and paste is best). Preboot is the first thing that runs, even before other boot envs are to take effect.

by bodhi - uBoot

Re: UART Booting HowTo for Selected Kirkwood Devices - 10 years ago

megov Wrote: ------------------------------------------------------- > I think, it is ignore the handshake. The original > kwboot stuck in a loop, > waiting for NAK (as I can suppose from code). I > add some debug > hexdump to stderr code into kwboot_tty_recv and > can see the same > stock uBoot startup log. Nothing different from a > normal boot. Then it does

by bodhi - uBoot

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

grayman4hire Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > Rootfs Debian-3.18.5-kirkwood-tld-1 was > uploaded. > > Please see 1st post for download link. > > > > This rootfs is the first Debian jessie > > rootfs in my Kirkwood kernel/rootfs release

by bodhi - Debian

Re: after Poweroff command, Pogo still draws 4.5 watts! - 10 years ago

Frederick Grayson Wrote: ------------------------------------------------------- > That's surprising. I installed a switch on the > power cord, because after using the halt or > poweroff commands you need to power cycle it to > turn it on again. Yes. > On a related topic - do the Pogos support WOL? A few of them do, such as NSA325.

by bodhi - Off-Topic

Re: after Poweroff command, Pogo still draws 4.5 watts! - 10 years ago

> The > ethernet port is still lit but USB stick light is > off. > this is ArchLinux installed and maybe this > explains some of the boot corruption. No it does not. > If you know of a better shutdown command than > poweroff, I'll try it and see. > Do a few sync commands before shutting down. Use the standard "shutdown -h now" on system with

by bodhi - Off-Topic

Re: Restore Pogoplug V4 to factory State - 10 years ago

@gray, > Too funny. You've been in doubt ever since I > mentioned wanting to boot the default Pogoplug OS > on the PPV4. :) Now I really think it over (not the 1st time :)) I agree it would work. Because how I wrote the instruction to flash u-boot image, it would leave the stock envs untouched :) OTOH, the mtds restoration procedure would need CESVCID and MAC addr adjust

by bodhi - uBoot

Re: Overprovisioning A Flash Drive ? - 10 years ago

metric, > BTW Does anybody know > if ZFS is supported on our Dockstar Debian? I > cannot find anything. I want to boot with flash > but store data on a ZFS hard disc. No, it is not supported. ZFS takes too much memory to run (> 1GB), so I have given up on compiling it for ARM. Soon it'll be revisited given there are quite a few ARM boards now begin to support >= 1G

by bodhi - Debian

Re: eth0 and wlan0 on the same lan subnet ? - 10 years ago

@Don, It looks pretty fine and going to work to me. That's all it matters. As a more elegant solution, iirc, there is one in that you would perform all these routing table logics inside /etc/network/interfaces.

by bodhi - Debian

Re: Restore Pogoplug V4 to factory State - 10 years ago

@grayman4hire, Are you sure that it will help to run the Dockstar orgininal u-boot on the Pogo V4? I don't doubt it will run Pogo OS, but will that allow the CE Pogoplug service registration? i.e. as in the original condition with the serial number and all that?

by bodhi - uBoot