A bit of progress! This is UART catching warmboot. root@Dockstar:/localdisk/linux/uboot# ./kwboot-tool/kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.1.1.4-nsa325v2-uart.bin Sending boot message. Please reboot the target...\ Sending boot image... 0 % [......................................................................] 1 % [............................................................by bodhi - uBoot
@Peter, This is in continuing with the NSA325 booting problem starting at this post in the 3.16 kernel thread. QuoteThe corrupted FS - guess where it does come from: the watchdog resets the nsa35 just right after the sda2 has been mounted! Anyway: I set bootdelay to 1 . I fsck'ed sda2. I cold rebooted, watchdog strikes again ! At which line in the kernellog.txt can we sby bodhi - Debian
ptosch, Let's move this booting problem to the NSA325 thread.by bodhi - Debian
@CasperJim, It's a normal behavior. It got kicked out to the shell because the rootfs couldn't be mounted without correcting errors that are serious and need user interactions. OTOH, if the only thing needs to be done is recovering journal (as occurred during power outage) then it should recover OK and continue booting. And I don't think fstab is really important here. You coby bodhi - Debian
t3ch42, I realized now I should have mentioned netconsole in the instruction. For netconsole, set the preboot variable with fw_setenv. The default settings has only preboot_nc (since I don't want to assume that users want to activate netconsole by default). preboot_nc=run if_netconsole start_netconsole preboot=run preboot_nc To help the kernel to find the correct rootfs, use rootfby bodhi - uBoot
CasperJim, You could set the bootargs like this (the end of the bootargs): usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params usb_custom_params=zswap.enabled=1 As Warhead suggested, uEnv.txt in /boot is a less risky way to do this. But you're an experienced user so I would suggest the abovby bodhi - uBoot
Quoteptosch [ 15.033802] sd 0:0:0:0: Attached scsi generic sg0 type 0 …. [ 15.512530] EXT4-fs (sda2): INFO: recovery required on readonly filesystem [ 15.519558] EXT4-fs (sda2): write access will be enabled during recovery [ 15.559925] EXT4-fs (sda2): recovery complete [ 15.564567] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) …. [ 19.318375] randoby bodhi - Debian
razorboy, > SDCARD BOOTING: > I found this SD card booting tutorial: > Booting Debian with Arch Linux ARM > uBoot > but it seem to focus on the Pogoplug v4, which > makes me afraid it may not work correctly on the > Mobile. This works fine for the Mobile. > And it says I should go update to the new uBoot > first: > 2014 > .07 U-Boot for FDT andby bodhi - uBoot
WarheadsSE, I thought I'd move our discussion about NSA325 UART booting to this thread properly, starting from this post: http://forum.doozan.com/read.php?2,14351,17077#msg-17077 - I've tried 384K stock (extracted from mtd) U-boot image. - I've tried your NSA325 U-boot code, built with UART option (it is small enough to be loaded successfully every time from cold boot).by bodhi - uBoot
renojim, Quoteam I missing anything or being foolish in going with Squeeze instead of Wheezy? Yes. Wheezy is a minimum nowadays. QuoteMy Dockstar is acting as a poor man's NAS with a 4GB flash drive for the OS and 500GB hard disk for my music, videos, and other stuff. You can use 1 partition, and use a swap file on the HDD. It's more flexible that way.by bodhi - Debian
fsm, Try using static IP to see if it helps.by bodhi - uBoot
renojim, Regarding initrd.img-3.16.0-kirkwood-tld-1 in the 3.16. Install the kernel, and dpkg will create it automatically. And I see that you post in another thread about squeeze/wheezy. So after you've installed the kernel, to upgrade your rootfs: change your apt sources list to point to wheezy and do upgrade. And you can use a source that is close to your location instead of http://by bodhi - Debian
pboricha, There are numerous threads in this forum where people used UART booting to unbrick their boxes! Starting with instruction in davygravy's post: http://forum.doozan.com/read.php?3,7852,7852 You can download the latest GoFlex Net U-Boot and kwboot here: http://forum.doozan.com/read.php?3,12381by bodhi - uBoot
fsm, > Yeah, no clue about the netconsole thing - I only > hardwire :) > > Getting it booted is no issue anymore, it's the > darn network that won't come up (most likely due > to no MAC set?) I see! then you need 3 lines (replace xx:xx:xx with you MAC address) Pogov4> setenv ethaddr 'xx:xx:xx' Pogov4> setenv bootcmd 'run mmc_set_by bodhi - uBoot
fsm, > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. > > *Waiting forever for nothing to happen here :) > Yes, it is expected. Without the 2 setenv lines above in rickgtx's post, the mmc rootfs will not be mounted successfully. So it dropped out to the shell, you just can't see it in netconsole, only in serial console. So that wby bodhi - uBoot
fsm, Without UART, you must be running stock U-Boot. Look at the U-Boot banner in serial console. Or did you flash new u-boot image?by bodhi - uBoot
Kernel 3.16.0-kirkwood-tld-1 package was uploaded. Please see 1st post for download link.by bodhi - Debian
metric, Yes, netconsole works with wire or wifi. And for a quick peek to see U-Boot version: grep -a --null-data U-Boot /dev/mtd0roby bodhi - uBoot
FYI, The problem with booting kernel 3.15.x on Zyxel NSA3xx stock U-Boot has been fixed. The reason: kernel-package was broken! at some point during the build it could not figure out the path of where to put initrd modules. As the result of this, all modules were included in the kernel image redundantly, hence the size increase. This does not cause any problem running, except for the NSA3xxby bodhi - Debian
CasperJim Wrote: ------------------------------------------------------- > > It's in the tarball link in the first post. You > can get the source from mainline kernel source > tree and apply the patch to it. > > If they were in separate files I would have > probably spotted it immediately, haha. Thank you > for pointing that out. > > After downloadinby bodhi - Debian
Thanks III, Icinga looks very slick too!by bodhi - Debian
Hi metric, This location is in your data area in NAND (101M) which is the 4th partition. It's not used by anything when you run USB or SATA rootfs. So don't worry about it, it's normal. Unless you see a lot of blocks starting to go bad then it's cause for concern. To verify in Debian, look at these addresses and convert it to decimal: cat /proc/mdt To see u-boot versioby bodhi - uBoot
hey chris, > http://chrislamothe.blogspot.com/2014/08/openmediavault-06-kralizec-on-netgear.html Very nice! I've filed it away for when the need arises for me to do this!by bodhi - Debian
Quotebodhi Wrote: ------------------------------------------------------- > Eike Wrote: > -------------------------------------------------- > ----- > > Is there any chance to get this problem for the > > NSA325 solved? > > Since kernel 3.16 was released, I'll try that to > see any diffrent in size. The real solution is > that stock U-Boot should bby bodhi - Debian
CasperJim, It's in the tarball link in the first post. You can get the source from mainline kernel source tree and apply the patch to it. linux-image-3.15.3-kirkwood-tld-1_1.0_armel.deb linux-headers-3.15.3-kirkwood-tld-1_1.0_armel.deb config-3.15.3-tld-1 linux-3.15.3-tld-1.patchby bodhi - Debian
Eike Wrote: ------------------------------------------------------- > Is there any chance to get this problem for the > NSA325 solved? Since kernel 3.16 was released, I'll try that to see any diffrent in size. The real solution is that stock U-Boot should be replaced with modern version so we don't have to worry about any limitation.by bodhi - Debian
CasperJim, Quote> At the very least, it should be > possible to use Ext4 for the initial rootfs, then > let the kernel handle other filesystems after it > is loaded You could also use 2 partitions, Ext2/3/4 for boot files, and the other for rootfs with files system that you choose as long as the kernel supports it.by bodhi - Debian
@WarheadsSE, Looking at your GitHub: Shouldn't it be 6282? #define CONFIG_KW88F6281 1 /* SOC Name */ And I don't see kw88f6282.h in here either ?! -rw-r--r-- 1 root root 1560 Mar 12 14:34 spi.h -rw-r--r-- 1 root root 15202 Mar 12 14:34 mpp.h -rw-r--r-- 1 root root 573 Mar 12 14:34 kw88f6281.h -rw-r--r-- 1 root root 538 Mar 12 14:34 kw88f6192.h -rw-r--r-- 1 rby bodhi - Debian
> I am not a manufacturer, and I like Linus NOT > yelling at me for shit code. LOL! Yeah, I think if we can at least Uart stock UBoot then we can flash yours to mtd0 and test it that way without the watchdog barking. I've searched the GPL tarball and did not find any documentation about ideas how to turn off the watchdog.by bodhi - Debian