Darn :) Warhead, so is it possible that the watchdog was temporarily resurrected somehow when the kernel start booting? Our GPIO setting in u-boot was unset somehow?by bodhi - uBoot
Peacemaker Wrote: ------------------------------------------------------- > Bodhi, do you really think this will work? The > nas320 is a krikwood divice and not like the kd20 > a oxnas? > > I think I'll just use for the first time the > Vendor stage1+uboot. As the new U-Boot need's a > lot of changes as well (and I'm not realy good in > modifying kby bodhi - Debian
Peacemaker Wrote: ------------------------------------------------------- > Bodhi, do you really think this will work? The > nas320 is a krikwood divice and not like the kd20 > a oxnas? > > I think I'll just use for the first time the > Vendor stage1+uboot. As the new U-Boot need's a > lot of changes as well (and I'm not realy good in > modifying kby bodhi - Debian
sunfire Wrote: ------------------------------------------------------- > Hi bodhi, > > thanks for this great advice. > > Can i set the correct MAC address in the u-boot > enviroment and replace the old 00:50:43.... ? > > -sunfire Yes. I set it to the original value.by bodhi - Debian
Florian, Use the latest wheezy rootfs from here: http://forum.doozan.com/read.php?2,12096by bodhi - Debian
As requested by a forum member, attached is the patch for kernel linux-oxnas-3.14-tld-5. Note that it is almost the same as kref's patch in GitHub. The only change in this patch is the LED is set to green explicitly when the kernel has booted.by bodhi - Debian
For Wake on LAN: http://forum.doozan.com/read.php?2,12960,17419#msg-17419by bodhi - Debian
Peacemaker Wrote: ------------------------------------------------------- > Okay, maybe someone has an idea what is wrong > here, this this kernel boot perfect with vendors > uboot, but with bodhi's or kref's Uboot I got > this: > > > OX820 # ide reset > > Reset IDE: Bus 0: OK > Device 0: Model: SAMSUNG HD204UI Firm: 1AQ10001 > Ser#: Sby bodhi - Debian
@shv, Also,keep in mind that this u-boot supports non-FDT and FDT automatically, so when you boot with 2.6.3x, you can't have anything in the bootm command that triggers the FDT path: Quote** File not found /boot/dts/ox820-pogoplug-pro.dtb ** Quote## Flattened Device Tree blob at 62c00000by bodhi - uBoot
@sunfire, With bootdelay less than 20, does it always reset after the kernel is loaded, i.e. during the rootfs mounting? when it reset what did the output look like? it has to show something, such as u-boot banner, can you post it?by bodhi - uBoot
Herb & Davidedg, I agree with Davide, kwboot would not really affect the serial speed. The speed varies due to the condition or hardware, though. I've noticed that sometime it took different time to load the UART image on my box. The last time I looked at the stopwatch, it took 28 seconds to load (could be 27 seconds, since I used the phone's stopwatch).by bodhi - Debian
@sunfire, I saw the error below too, but have not got the time to investigate. If anybody know why, please respond! Loading ACPI kernel modules... failed! [....] Starting ACPI services...RTNETLINK1 answers: No such file or directory acpid: error talking to the kernel via netlink Please repost this in the NSA325 thread: http://forum.doozan.com/read.php?2,14351by bodhi - Debian
@sunfire, I did not see anything wrong in your boot log. So hard to say what went wrong. However, to have a peace of mind, you can verify that the watchdog has been killed by doing this: - boot with serial and stop it at the count down. - and stay at the prompt for more than 30 seconds (executing some commands or just wait at the prompt). - after 30 seconds, if the watchdog is still alivby bodhi - uBoot
Peacemaker, So did you compile either mine or kref's u-boot? if you did, try to regenerate your Linux-2.6.32.fake+ uImage with tools/mkimage from that u-boot build. This error usually caused by a badly generated uImage (file system was not sync properly, nfs timeout, mismatched checksum,…). If you don't have 2013.10 u-boot mkimage, I'll post the binary here.by bodhi - Debian
@shv, Kernel 2.6.3x does not have supports for Device Tree. If you happen to have the DTB embedded in uImage, then it won't boot.by bodhi - uBoot
novaforme, It seems either the file system on the USB drive is bad, or the drive itself is bad. Try - Refortmat it completely as Ext3, download Arch rootfs and extract to it. And boot. - If the above did not work, try to use a different USB thumb drive (some brand is not good for booting, Sandisk is among the best to use as boot drive).by bodhi - uBoot
herb, > The version of kwboot is unlnown. I cannot see any > version info anywhere! It is in the mainline u-boot, so it takes the u-boot version implicitly. If you've downloaded my uploaded kwboot binary then it's ARM, circa sometime 2013 (check the timestamp).by bodhi - Debian
Pogov4> setenv bootcmd run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset should be in single quotes so that the spaces is escaped and multiple commands are taken: Pogov4> setenv 'bootcmd run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset' That why this was good: setenv bootcmd run bootcmd_usb; Once you got here, it means that the kernel was loaded OKby bodhi - uBoot
It is all messed up :) what happended? These are correct values and need to be set: arcNumber=3960 machid=f78by bodhi - uBoot
Peacemaker Wrote: ------------------------------------------------------- > Thx for this, but oob it is not working :-|, and > only working without ethernet :-( Sorry, I don't get what you meant to say! what problem are you trying to solve? If you ask a specific question, I might be able to help.by bodhi - Debian
herb, Try this test version, it is a little bit smaller: http://forum.doozan.com/read.php?2,14351,17193#msg-17193 If it works then save it as a rescue mechanism.by bodhi - Debian
novaforme, Your bootcmd is messed up! > bootcmd=nand read.e 0x800000 0x100000 0x300000; setenv bootargs $(console)\ > $(bootargs_root); bootm 0x800000 Should be bootcmd=run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset Update: And this is wrong too: mainlineLinux=no should be mainlineLinux=yesby bodhi - uBoot
Peacemaker, For some info about GPIO and U-Boot take a look at 2013.10 U-Boot for Pogoplug V3 (OXNAS). I've added some code to control the LED during booting. And I've updated the SPL to 850MHz: http://forum.doozan.com/read.php?3,16017,page=3by bodhi - Debian
herb Wrote: ------------------------------------------------------- > bodhi consider the 4TB a full success! > I pulled the drive from my NSA320 and stuffed it > in the NSA325 and it simoly came up no > problems;-) > > Herb Cool! thanks for testing. That's the last checkmark. I am adding the uEnv loading capability, and we'll be done.by bodhi - Debian
Paging gnexus !!! http://linuxgizmos.com/hackable-39-allwinner-a20-sbc-packs-hdmi-and-gbe/by bodhi - Allwinner A10
@jfharper, Before you flash the orignal u-boot to the bad GFH, try booting it with my uploaded Debian rootfs: http://forum.doozan.com/read.php?2,12096 I looked over u-boot envs listed in serial console for the bad GFH, and did not see anything wrong. So perhaps something wrong with your Arch rootfs? best to try booting with Debian rootfs that we know working.by bodhi - uBoot
jfharper, I will respond in detail when I got home. Pls see below for short answers. Wrote: ------------------------------------------------------- > So the way I understand it, the NAND is my Flash > memory on the GFH board. It contains some > partitions, and each partition has some stuff > written on each partition. The stuff are > utilities know as MTD utilitiesby bodhi - uBoot
herb Wrote: ------------------------------------------------------- > command line: > time ./kwboot -t -B 115200 /dev/ttyUSB0 -b > ./uboot.2013.10-tld-1.nsa325.uart.kwb -p > > result: > real 0m32.111s > user 0m0.076s > sys 0m0.270s > > bodhi, you say you've been using the nand version. > Are there any problems??? > I'll flash it to nanby bodhi - Debian
jfharper, Your dmesg shows: Creating 3 MTD partitions on "nand_mtd": 0x00000000-0x00100000 : "u-boot" 0x00100000-0x00700000 : "uImage" 0x00700000-0x10000000 : "root" So you should go with this actual layout as the original MTD parts.by bodhi - uBoot