Ah! Sorry about that I should have read that more carefully. Anyhow.. latest uboot - confirmed working latest Debian with FDT - confirmed working latest envs - confirmed workingby heychris_1 - uBoot
Thank you for the quick reply. I appreciate you validating the mtd0 layout. What about using Jeff's rescue system in the rest of the mtd0? Would that boot OK?by heychris_1 - uBoot
Bodhi, I went ahead and tried FDT on my netgear stora. I updated uboot to uboot.2016.05-tld-1.netgear_ms2110.bodhi.tar I also rewrote the envs following your instructions With a USB stick formated to ext3 per your instructions with Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 . I got the following message. I can give you the full output if you'd like. Any ideas? [by heychris_1 - uBoot
I loaded uboot.2016.05-tld-1.netgear_ms2110.bodhi.tar It works well. I wanted to see if I could use FDT. I can't think of any reason why it would not work. My question is about using the uboot.2016.05-tld-1.environment.bodhi.tar The default mtdparts for a netgear stora are mtdparts=mtdparts=orion_nand:1M(u-boot),512K(uboot_env),512K(key_store),512K(info),10M(etc),10M(kernel_1),4by heychris_1 - uBoot
All, I wrote up my process of installing openmediavault on a netgear stora. Much thanks to all that have made it possible. A special thanks to Bodhi. Please let me know if I made any mistakes. http://chrislamothe.blogspot.com/2014/08/openmediavault-06-kralizec-on-netgear.htmlby heychris_1 - Debian
Also I noticed this message.. Using machid 0x691 from environment I wonder why that's different... Bodhi, Do you think this setup could work with grub-uboot or grub-efi-arm Kernel requirements for grub on ARM The only real requirement on the kernel is that: It is built as a simple zImage (none of that uImage wizardry!), it is built with Flattened Device Tree (FDTby heychris_1 - uBoot
My apologies. I must have made a mistake somewhere on the last attempt. From scratch, I built a hard drive with your latest rootfs. My understanding is that it doesn't have a stora compatible kernel. I then moved over your latest kernel with the latest rootfs and latest u-boot and they are all working without issue. As the u-boot is built with machid = ab7, I didn't have to speby heychris_1 - uBoot
For clarity.. I interrupt boot setenv serverip 192.168.0.100 setenv ipaddr 192.168.0.200 tftp 0x800000 uboot.2014.07-tld-1.netgear_ms2110.mtd0.kwb nand erase 0x0 0x80000 nand write.e 0x800000 0x0 0x80000 I then take a fresh drive format it /dev/sda1 to ext4, /dev/sda2 swap. I then extract Debian-3.14.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 to /dev/sda1 and extract linux-3.15.3by heychris_1 - uBoot
Bodhi,, Thanks again for all your hard work.. Similarly to what I mentioned earlier... I have 3 boxes.. They all run your rootfs and uboot: U-Boot 2013.10 (Feb 22 2014 - 15:26:05)-tld-2 Unfortunately your kernel still gives the machID 0x00000ab7 unknown error I'm running the kernel I mentioned earlier that I compiled from https://github.com/kirov/stora-debian-kernel I triedby heychris_1 - uBoot
I'm curious if anyone has tried grub for ARM u-boot on a kirkwood box? https://wiki.linaro.org/LEG/Engineering/Kernel/GRUBonUBOOTby heychris_1 - uBoot