ueghio, You have not booted into Debian. When you see the initramfs prompt, it means that the rootfs has not been mounted successfully, so the kernel exited and you are in the temporary rootfs (i.e. the one provided by initramfs). I think your rootfs creation was not done properly. During rootfs creation, you must follow the instruction very closely (thing like being root user, and label thby bodhi - uBoot
nano326, > If you set "rtcwake -60 -m off", the system will s > huwdown completely and automatically wake up again > after 60 seconds. Cool! > Thanks. I was looking for the "heartbeat" trigger. > However, now I have to find out how to automatical > ly switch the LED to heartbeat when it is spun dow > n and vice versa. As you probably haveby bodhi - Debian
> What about this http://www.tmart.com/Lvpin-20 > 0W-12V-Super-Bass-Mini-Hi-Fi-Stereo-Amplifier-Boos > ter-Radio-MP3-Silver_p354908.html]Lvpin 200W 12V S > uper Bass Mini Hi-Fi Stereo Amplifier Booster Radi > o MP3 Silver? Thanks habibie. This is indeed a good and inexpensive amp! great for these small Kirkwood plugs. Note that GF Home power supply might be perfect for iby bodhi - Off-Topic
nano326, > I am also successfully using Debian on the NAS326 > now with openmediavault 3.x installed. > Works great so far. :-) > Thanks! Cool! > Do you know how to configure the wakeup? > Is it done through standard rtcwake way? I have not looked into this subject, it's one of the minor items along with SPI flash, that I've postponed until I have morby bodhi - Debian
sarcastic.mannequin, Thanks for your contribution! I will look at the DTS and boot log, and will add your DTS files to the kernel in the next release.by bodhi - uBoot
habibie, > Bodhi, the email notification is for any new users > only, right? Yes. New user registration was broken. PM email notification should be OK!by bodhi - Off-Topic
Marco, > U-Boot 2015.10-tld-1 (Nov 06 2015 - 15:46:25 -0800) > Pogo E02 Your envs are not correct, so we will need to put the envs in the /boot folder of the rootfs to recover. Your installed u-boot is relative new. So that will make it easier. > I formatted a usb pendrive in ext3 through my linu > x pc, created a boot folder in the root of the pen > drive, extractedby bodhi - uBoot
Instruction for Zyxel NAS326 Installation has been updated: added section B (setup without serial console). QuoteZyxel NAS326 Installation Updated 18 Feb 2017 (added Section B) Updated 05 Feb 2017by bodhi - Debian
jochen, > update: I executed the fw_setenv commands again an > d rebooted. Now it works! I really don't know what > 's different now... Thanks for testing :) I've confirmed that it is actually booting to kernel 2 if you set the envs the way I wrote for serial console. And when you booted back to stock OS and set it the 2nd time, it would work! One more fw_setenby bodhi - Debian
khongpt, > And box now boot successfully. I'm root# now. Great! However, you're booting the box as if it is with the old u-boot (one that does not support FDT so you have to append the DTB to uImage). The setup is not correct if you have to boot with tftp. So If you want to complete the setup to the way it should be, then in Debian, get the output of the following commandby bodhi - uBoot
khongpt Wrote: > So, Don't I need to upgrade kernel to 4.9.0 ? No, kernel 4.4 in the rootfs is fine. No need to upgrade the kernel until after you have booted into Debian. Try creating the rootfs again without step 4. Make sure you are root user when you create the rootfs, and the ext3 partition is labeled as rootfs. Every steps in the installation must be followed exactly, if yby bodhi - uBoot
FYI, Account registration for new users in the last couple weeks had been broken. Jeff has notified me that it's fixed now. If you have not received email notification during the last couple weeks, please try to register again.by bodhi - Off-Topic
Marco, Yes it is possible to boot Debian jessie on USB with your u-boot. See the rootfs release thread. However, your u-boot was not restored correctly. Your envs are not for the Pogo E02. It is for Pogo V4. Also, the envs are for an older u-boot version than the latest u-boot. Please post the whole serial console log (from the banner until you interrupt it, and printenv). I need to seeby bodhi - uBoot
jochen, Probably the box was booting back to kernel 2 when you set them the first time and missed something? Did you save the listing of the envs with fw_printenv after the first try? if you did please post here. It would be interesting to see what were the first time settings of the envs look like. But it's cool that it worked for you on 2nd try :)by bodhi - Debian
GeekSmith Wrote: ------------------------------------------------------- > Success! Even with the soldering skills of a softw > are engineer, I was able to attach the JST connect > or and use it without letting the smoke out. I rem > oved the solder from the 3 holes that go through t > he board. I also removed as much solder as I could > from the pad for ground. > &by bodhi - Off-Topic
khongpt, When you created the 4.4 rootfs, note step 4: Quote 4. Create uImage with embedded DTB for booting with older u-boots (2012 or earlier). Skip this step if you have installed the latest U-Boot for Kirkwood (or are installing this u-boot at the same time). You should not do step 4, since you are installing new uboot at the same time. So reverse step 4: Mount the HHD on anotherby bodhi - uBoot
Jochen, Thanks for pointing this out! I was thinking about using the USB script to do this (because it also serves as a recovery path when things go wrong). But web interface would be a more friendly way. So perhaps I will write installation instruction starting with this option. In the release thread: http://forum.doozan.com/read.php?2,32146, I've mentioned section B: QuoteInstallby bodhi - Debian
Hi khongpt, You are running an old script from Jeff to update u-boot. I have is a new procedure to update to the latest u-boot: http://forum.doozan.com/read.php?3,12381 If you are comfortable with flashing u-boot manually using this new procedure, you can do it from stock OS command line. Jeff has not been updating the script that you ran, or regression testing it for a while. So it isby bodhi - uBoot
Peacemaker, > Not working,... if you are nevertheless interested > in the sources, its form the mcm-gpl package form > wd. Strange! in my experience with booting kwboot, the xmodem bad message is a really good indicator that UART handshake is working, but out of sync. The source code most likely will not be useful in this case.by bodhi - Debian
schnee, I'll take a look at the SATA driver difference when I start building kernel 4.9 for this box. 4.9 is an LTS kernel so that's my current target for Popgo V3 Oxnas.by bodhi - Debian
cdlenfert, > Should those be safe to share here in a Pastebin? You should scrub the ethernet MAC address and serial numbers of the disk drives from dmesg log. And /proc/mtd does not have anything private. > > When I run blparam, I only get the message "-sh: b > lparam: not found" > blparam is in /usr/local/ somewhere that has cloudengines subfolder. Seaby bodhi - Debian
@Carl > ./a.out -b ./u-boot-a38x-RangerPeak_2014T3_PQ-nan > d-uart_1G.bin -B 115200 /dev/ttyUSB0 > Sending boot message. Please reboot the target...| > Sending boot image... > 0 % [+++++++++++++++++xmodem: Bad message This is actually a lot better than no response. When you see this xmodem bad message, up arow to recall the command and execute it again. Try repeating thiby bodhi - Debian
See if you can kwboot with this attached u-boot bin.by bodhi - Debian
And of course, the safest thing to do is to try kwboot this box. If you can do that then everything else is easy.by bodhi - Debian
Carl, Sounds like being able to read and write u-boot envs is something to do next. What is the DTS looks like? Eventhough you cannot use saveenv to change envs in u-boot, in Linux you can do that with the right DTS. If the kernel bootargs does not prevent it, then if all NAND mtds are defined in DTS, with the u-boot mtd being writable and the envs defined at correct location, then you can setby bodhi - Debian
cdlenfert, > Since Moonman's guide mentions ArmV5 plugs, maybe > I'm naive to think the firmware will also work on > the Pro (armV6). Any confirmation either way would > be much appreciated. Ah, I remember that moonman post. I don't think it will work for the Pogo V3 Oxnas. It is for the Kirkwood plugs (amrv5).by bodhi - Debian
NAZIM, QuoteWhen you ran kwboot and power up, the kwboot indicator was spinning for a while and then stopped. Nothing happened after that and the box did not reset? If the above is true, then it meant the NAS325-v2 has received the kwboot message (the fact that the watchdog did not run every 30 seconds). But it stuck waiting, it probably meant that the RX pin was OK when kwboot started, butby bodhi - uBoot
Carl, > At boot process systemd did not find partitons on > the lvm. > As soon as debian is booted i can just mount them > normal,..of cause a walk around is easy but I like > to fix this. This sounds like an initrd related problem (I assume you have one). Because that's where the volumes are mounted. Have you tried to to update it: update-initramfs -uby bodhi - Debian
cdlenfert, What moonman's upload file look like? Once you have serial console connected, it should be easy flash new stock FW, if the file is a correct one. Come back and post your serial console log with the following info. In stock OK, these info are needed before flashing dmesg cat /proc/mtd blparamby bodhi - Debian
cdlenfert, You might consider install Debian on this box: http://forum.doozan.com/read.php?2,16044by bodhi - Debian