Show all posts by user

Re: me too plz - 10 years ago

@Joey, No, it meant the the rescue system rootfs has a problem. So it must be fixed, or reinstalled. The best way to fix this is to connect serial console. And watch the boot process. Log in to the rescue system through serial console connection and then fix the problem. Or take the shortcut by reinstalling it. Btw, serial console is the indispensible tool for embedded Linux device :) get

by bodhi - Rescue System

Re: Pogoplug V3 (Pro and Classic) - Sample u-boot Env's for uEnv.txt - 10 years ago

@LeggoMyEggo, > The diskscan can't > be called for out of uEnv.txt because u-boot has > to know which disk is the rootfs before it will > search for the uEnv.txt file in that rootfs' /boot > folder. Not really. The scan disk has nothing to do with rootfs yet. If you reread my post: http://forum.doozan.com/read.php?3,19093,19093#msg-19093 we are still in Secti

by bodhi - uBoot

Re: Possible to install Debian on Seagate Business Storage 2? - 10 years ago

@Yama, On the latest 3.18 I still get the cryptic symbols, which makes serial unusable, but network works and I can ssh to it. Which 3.18 version? And these weird chars might just be the box's serial baud rate/parity/... parameters are different than we expected.

by bodhi - Debian

Re: Pogoplug v2 doesn't show up on LAN after Archlinux install - 10 years ago

TEN, Quoteget the most versatile, reliable U-Boot (presumably http://forum.doozan.com/read.php?3,12381). Yes, and set up netconsole right away, especially with no serial console set up. Furthermore, with this new u-boot, you will have the LED flashing correctly in the boot sequence, so the quick visual indicator is available (most of the time, it is enough to tell that something went wrong b

by bodhi - uBoot

Re: Pogoplug V3 (Pro and Classic) - Sample u-boot Env's for uEnv.txt - 10 years ago

Scan disk: http://forum.doozan.com/read.php?3,19093,20399#msg-20399

by bodhi - uBoot

Re: TUN/TAP problems with Kirkwood kernel - 10 years ago

@Gravelrash, Thanks! corrected.

by bodhi - Debian

Re: TUN/TAP problems with Kirkwood kernel - 10 years ago

tufkal, > As long as the kernel has the tun.ko driver > enabled or as a module, the binary takes care of > the rest. Based on what you mentioned above and everybody's suggestions: - On a fresh 3.18.5-kirkwood-tld-1 rootfs - Add tun module to /etc/initramfs-tools/modules so it will tell initrd to load during boot. echo tun >> /etc/initramfs-tools/modules - Reg

by bodhi - Debian

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

@Tomas, > Still I would like to try to build my own kernel. > So I need solve issue with "make: *** > Error 2". You have not applied the patch correctly if you see this error.

by bodhi - Debian

Re: Kirkwood U-boot - Getting all supported Kirkwoods on-board - 10 years ago

@WarheadsSE, I've pushed out to u-boot-kirkwood GitHub all the changes I have for NSA325 and NSA320. Please make modification to anything that you see fit. commit bb8ac0e067f6f42d8832c11c9266707bcba419f9 branch 2014.07.c-kirkwood Also included in this commit, for all supported Kirkwood u-boots: uEnv.txt loading capability, better default envs, and miscellaneous editorial changes.

by bodhi - uBoot

Re: TUN/TAP problems with Kirkwood kernel - 10 years ago

@tutkal, If you do what Almaz suggested, I am sure it will work. At the end of the day, once it is working, we all will learn something. That's I think the best contribution, because others will then know where to go for solution. After that, there is plenty of time to figure out the differences.

by bodhi - Debian

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

@Joe, Thank you also. It's a very helpful description of the process.

by bodhi - Debian

Re: NSA 325 Bricked - 10 years ago

dirixmjm, The smallest one is attached in this post: http://forum.doozan.com/read.php?2,14351,17193#msg-17193 It does not depend on any host speed, since you are connecting with serial console to boot UART. QuoteUPDATE: My thought was incorrect. The loading is affected by the how noisy the network environment is. See post below this for how dirixmjm solved it. If it does not load compl

by bodhi - uBoot

Re: NSA 325 Bricked - 10 years ago

dirixmjm Wrote: ------------------------------------------------------- > I think I did it. My NSA 325 is bricked. > > I followed these instructions, where I did the > MTD0 flash using the stock NSA 325 firmware, and I > also did rewrite the environment to 0xc0000. > > http://forum.doozan.com/read.php?3,12381,17420#msg > -17420 > > If I now boot I get n

by bodhi - uBoot

Re: U-Boot - Booting process in multiple drives configuration - 10 years ago

I've updated the 1st post to include new scanning script. With the new script, we can scan all types of drives in a multi-drive configuration to find the boot partition. In the near future, I will post another set of default u-boot envs to simplify the booting envs substantially (generalize all device types in booting using the same approach in this script). Please see section A.2 for

by bodhi - uBoot

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

@DavideDG, Thanks for the helpful description! > Still - it may very well be that CodeSourcery has > problems with CODA source code, I'm no expert in > this field. It might be the case. I'm compiling natively with distcc. > Another option is to first install the NAS without > MD, let it boot, then regenerate initrd by > installing mdadm. > Then s

by bodhi - Debian

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

@Tomas, I don't know, never had problem with compiling CODA. The errors you've listed did not ring any bell for me. include/uapi/linux/coda.h:221:2: error: unknown type name 'u_quad_t' According to Davide said above, MD works in his initrd. Perhaps you should look at your log to see how you set it up in initrramfs? Also since Davide got it working, may be we should see

by bodhi - Debian

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

@Tomas, > Yes I tried it. My uImage and uInitrd are on small > /boot parition that is not RAID device. Also the > documentation explicitly says it won't work: It is not clearly say that it won't work even if you loaded the module early enough in initrd. In any case, I thought that's what davidedg meant to say above: QuoteI don't know if Bodhi's init

by bodhi - Debian

Re: Pogoplug V3 (Pro and Classic) - Sample u-boot Env's for uEnv.txt - 10 years ago

@ LeggoMyEggo, Two comments: 1. The below variable is a leftover default value from the original GitHub u-boot. We should take it out to avoid confusion: preboot=run safeboot Furthermore, in uboot.2013.10-tld-4 u-boot version, if loaded from uEnv.txt, the variable preboot does not serve its purpose anyway. Because the uEnv.txt is loaded by the bootcmd, and preboot happened before boot

by bodhi - uBoot

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

@Davide, The kernel has MDADM supports, but as Toms mentioned, it's loaded as module. @Tomas, Have you tried to load it as earlier as possible (i.e. in /etc/initramfs-tools/modules)? would that work (are your uImage and uInitrd in a normal Ext partition)?

by bodhi - Debian

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

t00 Wrote: ------------------------------------------------------- > Hello. > http://hajduk.one.pl/Netgear%20Stora%20MS2000%20MS > 2110%20kernel%203.18/kernel-3.18-netgear_stora_ms2 > 000_ms2110.patch > This patch adds support for FDT for Stora. > Found it at: > http://hajduk.one.pl/Netgear%20Stora%20MS2000%20MS > 2110%20kernel%203.18/ Thanks t00.

by bodhi - Debian

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

@Davide, > I don't know if Bodhi's initrd has MDADM support, > but I think it could be easily extended. > @bodhi: if it is not supported, you may consider > this script as a starting point to include it? I'll take a look and include it if it's not.

by bodhi - Debian

Re: TUN/TAP problems with Kirkwood kernel - 10 years ago

> Lies! Bodhi knows all! :P :)) I wish there were a tiny grain of truth in that:))

by bodhi - Debian

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

@tanya, I don't see the card being detected at all in serial boot log either. It seems to point to a HW problem, i.e. it's incompatible. However, I will have to verify that. When I have sometime, I'll plug in my Atheros card and see what happen. Usually even if the kernel does not have driver for it (this kernel does), the device is stil detected by the kernel.

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

AA666, > Works fine for me on NSA320. Just booted from USB > stick 3.18.5-kirkwood-tld-1 kernel and rootfs. Thanks for confirming.

by bodhi - uBoot

Re: TUN/TAP problems with Kirkwood kernel - 10 years ago

I don't have anything better to offer other than Almaz and Gravelrash already said, but am interested in how this problem is solved! @tufkal, Even though the kernel config is mostly the same between mainline Debianwheezy and my config, I think you've probly overlooked this point: if you install from mainline, there are a lot of default configurations settings were done by that p

by bodhi - Debian

Re: Pogoplug v2 doesn't show up on LAN after Archlinux install - 10 years ago

@Waynosan, You need to verify these: - Check if you have used the copy command cp -aR while logged in as root. - After cloning the rootfs, check udev rules files: http://forum.doozan.com/read.php?2,18007,18008#msg-18008 Also, if the USB flash drive is plugged in, u-boot envs should be modified to boot with both drives attached.

by bodhi - uBoot

Re: Debian Wheezy on Pogoplug Pro V3 - 10 years ago

InfoScav, > 2. will also be connecting an HDD via SATA to the > plug. would you recommend installing debian to > that instead and booting from it? or USB is fine? As Gravelrash said, if you're going to do something that will be disk I/O intensive then HDD is a must. However, it does not mean in all cases that the rootfs must be on it. 1) if you are going to compile appli

by bodhi - Debian

Re: TUN/TAP problems with Kirkwood kernel - 10 years ago

@Almaz, Which kernel are you running (uname -a) that works for TUN/TAP as you've mentioned here?

by bodhi - Debian

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

@Felipe, Please redo the flashing, get only the relevant commands and their output and post here.

by bodhi - uBoot

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

@Joe, It looks normal. And you've already swapped the cable and switch port. So I think could it be other software you have running in your system? Are there daemons running that could have been monitoring the network status, i.e. errounously brought the link down? 5 minutes interval is very suspected.

by bodhi - Debian