ubermacin Wrote: ------------------------------------------------------- > > debconf: unable to initialize frontend: Dialog > debconf: (No usable dialog-like program is > installed, so the dialog based frontend cannot be > used. at > /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line > 76.) > debconf: falling back to frontend: Readline > Done. > Setting uby bodhi - Debian
nekitp Wrote: > If you are lucky, it wil also blink leds. On > nsa310 it does not. > cat /sys/class/leds/nsa310:green:hdd/trigger > shows > none nand-disk timer oneshot heartbeat gpio > default-on > but no sata-disk, or at least ide-disk Did you compile with the patch? if not then that was the reason.by bodhi - Debian
Your rescue system arcNumber must be something other than the GoFlex Home (3338). Looks like it's a Dockstar. Check it with: fw_printenv arcNumber But before setting this arcNumber, make sure you can boot it with a kernel that supports it (I don't know if your rescue system supports it) . But first, make sure you can boot with the rootfs above (it works for most Kirwood plugs). Iby bodhi - uBoot
earl, If it's a GoFlex Home then try UART booting: http://forum.doozan.com/read.php?3,7852,7852 And you can use uBoot image from this thread for UART booting: http://forum.doozan.com/read.php?3,12381 After verifying that it booted, put this rootfs on a USB thumb drive: http://forum.doozan.com/read.php?2,12096 If everything boots OK into Debian, then while in Debian, flash thisby bodhi - uBoot
Yes, setup tftp on another Linux or OSX box and flash the current uBoot image. In the example below, 192.168.0.100 is the ip address of the other Linux box 192.168.0.200 is the ip address of this Dockstar (assuming it is the Dockstar) uboot.kwb is the uBoot image that is retrieved by Jeff script (http://projects.doozan.com/uboot/install_uboot_mtd0.sh) for the Dockstar. and all commanby bodhi - uBoot
ingmar_k Wrote: ------------------------------------------------------- > Great to hear that my little theory worked out > like expected. Nice solution!by bodhi - uBoot
nekitip, See this post by pbg4 for setting NSA3xx LEDs. http://forum.doozan.com/read.php?2,12096,13642#msg-13642 It is the normal way to control the LEDs in all these Linux ARM boxes. The color for each LED is whatever you want it to be. Setting them in the kernel is unecessary. The necessary part is to specify the addresses in the code so that the /sys/class/leds triggers are available. Rby bodhi - Debian
@nekitip, It's very possible that I've missed part of the NSA310 patch. It was extracted from Arch Linux ARM patch. Don't worry about pointing out problems! I don't have any of the NSA3xx series boxes and have no way of testing the patch, so other users have been testing these boxes and reported problems in this thread. Especially the NSA310, only you and another user haveby bodhi - Debian
davidedg, > But how can I do with bootargs? I may end up > running from NAND, but using USB bootargs. > > Or am I missing something? > Ty! No, you did not miss any thing. It's a limitation of stock uBoot where you can't use "if else" syntax (contrary to the newer uBoot that I've built recently for other plugs). With stock uBoot, the envs forby bodhi - uBoot
The reason is the bootm was executed at the end of this command: setenv boot_from_usb 'usb reset; run usb_load_uImage; run usb_load_uInitramfs; run usb_setbootargs; bootm ${uImageAddr} ${uInitramfsAddr}' So take out the bootm and commonize it, something like this: setenv bootm_cmd 'bootm ${uImageAddr} ${uInitramfsAddr}' setenv bootcmd 'run boot_from_usb; run bootby bodhi - uBoot
kraqh3d, > I'll regen the uInitrd tonight and give that a > shot and report back tomorrow. Come to think of > it, I should've done that last night. It was late > and I wasn't thinking. > ** edit ** > > Generating a new initrd worked. Did you mean the rootfs mounted with new initrd?by bodhi - Debian
nekitip, The kernel was never intended for flashing in NAND. Hence, the patch was provided so you can compile your own kernel for that purpose. If you had installed Arch, then everything should be in the kernel (they don't use initrd). In any case, what you should do is following kraqh3d 's advice to boot the kernel first from memory or USB, make sure everything works to your satisfaby bodhi - Debian
johnklos, > Are all PogoPlugs configured from factory to the > same 192.168.58.x network? I noticed that the > netmask is 255.255.0.0, but I don't think people > should create an alias with such a large netmask > because some people will already be using another > 192.168 network. > No. 192.168.58.x is the local network IP subnet determined by your router. Iby bodhi - uBoot
nekitip, > the reason i had to do this is because bodhi's > configuration couldn't access file sistem and > thus, not been able to boot the system, so i had > to include ext4, and also, in my case, i had to > have ftdi_sio.ko. I have included them all in > uImage. The kernel has ext2, ext3, and ext4 supports loaded as modules.by bodhi - Debian
The original Pogoplug uBoot envs is at 0xa0000. The new uBoot uses 0xc0000. Also, for the Pogo Mobile original uBoot, blparam must be used, not fw_setenv and fw_printenv. You can find blparam in the Pogo OS rootfs (iirc, it's under /usr/local/cloudengines/bin). The syntax is slightly different, and blparam calculates a different checksum for the envs, so dont use fw_setenv. Here is anby bodhi - uBoot
kraqh3d, I had run into similar problem before (same behavior, but it could be a different problem). It's rare, but it seems the initrd creation could produce a messed up initrd. I would check the following: - if you have flash-kernel installed, then apt-get remove it first before dpkg the new kernel. And then mkimage the uImage and uInitrd manually. - if you did not have flash-kernelby bodhi - Debian
nekitip, I would not recommend flashing the kernel in NAND before you can boot with USB or SATA. And yes, unless the kernel uImage was built with all necessary modules (3.12.0-kirkwood-tld-5 was not), you do need uInitrd.by bodhi - Debian
3.12.0-kirkwood-tld3 rootfs should boot with all versions of uBoots that Jeff's script installed (i.e. even one with L2 cache enable). So chances is that it will boot this Pogo E02.by bodhi - Debian
kraqh3d, Check your uBoot envs, must be some changes you've made? I'm using the same Ext3 rootfs for all these boxes, including the Pogo V4. The symptom does indicate it could be either uBoot envs or messed up rootfs partition. I would try booting with my original rootfs untarred to a newly formatted Ext3 USB stick first.by bodhi - uBoot
Rick, Perhaps compiling the kernel with approriate config switches turned on is a better solution? If you still have problem in a couple weeks from now, remind me and I will see if I can release new kernel with the modules you need. My plan for the next kernel release will be 3.13.by bodhi - Debian
kraqh3d, Thanks, indeed I have not thought about the case where the disk label has embedded spaces!by bodhi - Debian
@NSA325tvheadend, The kernel-headers for linux-3.12.0-kirkwood-tld-5 is included in the tarball in the first post. Let me know if you want to include this config option in the next release, and so which config switches should be turned on. Quotebodhi This tarball contains 4 files (the patch stays the same as in tld-3): linux-image-3.12.0-kirkwood-tld-5_5.0_armel.deb linux-headers-3.1by bodhi - Debian
ch, Other than using serial console, you can try to boot with my latest rootfs (in my signature). See instruction to put it on a USB thumb. After you've booted into Debian, SSH in and then you could fix your stick, or put a fresh Arch Linux ARM rootfs on it.by bodhi - Debian
Warhead, I will be back home in about a couple weeks. Will do it then.by bodhi - uBoot
Hi pgb4, Thanks for your NSA320 contribution! I will incorporate your config changes and LED settings to the next kernel/rootfs release. It's good to know the ide1/2 trigger works on NSA320 also (some forum member needs that info). Regarding the SATA error above. Yes, I think timing must be the cause, because with my new 2013.10 uBoot build, the Sandisk Readycache shows the same errorby bodhi - Debian
@WarheadsSE It should be 2013.10, same as in this thread (2014.01 is not out yet): http://forum.doozan.com/read.php?3,12381by bodhi - uBoot
Tj, Your problem is with machid. It needs to be set to the hex value dd6 (3542 decimal). Set it in console. More info: my kernel build has patches to work with older uBoot (I believe that it should also work with 2011 uBoot, i.e ones without L2 patch).by bodhi - uBoot
optim Wrote: > Can I hotplug the SATA HD? I can try that and > look at dmesg if it would help but don't wnat to > do it if thats a no-no. Back up the HDD first. For the GoFlex Home/Net, yes should be no problem.by bodhi - Rescue System
It looks very good. Now when you plug in the HDD,what dmesg says?by bodhi - Rescue System