BTW, I am close to release u-boot version 201.07 for all Kirkwood plugs, including the Pogo V4/mobile. When you got the replacement, see this thread for the new U-Boot: http://forum.doozan.com/read.php?3,12381by bodhi - uBoot
vaidyasr, The only way to recover now is connecting a serial console and fix any missing u-boot envs or other problems. See this thread for what to buy for serial console: http://forum.doozan.com/read.php?8,13263 Since the Pogo V4/Mobile does not have a serial header installed, you'll need to solder it in. So if you're not up to that, then get a replacement would be a safe choicby bodhi - uBoot
vaidyasr Wrote: ------------------------------------------------------- > But not done the below steps. > Quote# fw_setenv arcNumber 3960 > # fw_setenv machid F78 It should boot my Debian rootfs even if you've missed this step. If there is no green LED, then U-boot has not gotten to the kernel loading phase. - Was the green LED light flashing initially? - If you have the lby bodhi - uBoot
Hi Gray, It does look sane to me. I think it's time to watch netconsole/serial console boot log! I can only think off the only thing that might have happened: perhaps the drive letter of the mmc was somehow mis-assigned to something other than mmcblk0p1. Yes, ext2load mmc 0:1 0x00800000 /boot/uImage would load correctly if the SD card is plugged in. And your u-boot env mmc_boot is handby bodhi - uBoot
vaidyasr, Don't worry, we all made little missteps in the begnning :) QuoteI have flashed the uboot steps as I have mentioned, haven't changed the default variables. Let me make sure I understand what you did so far. You've followed the instruction in this thread: http://forum.doozan.com/read.php?2,11663 But did not do this part: Quote- Flash uboot.environment to 0xCby bodhi - uBoot
Download the latest Debian rootfs from here: http://forum.doozan.com/read.php?2,12096 Untar it to a USB thub drive following the instruction and boot with it.by bodhi - uBoot
Thanks ingmar, No wonder, I kept looking in here: https://dev.openwrt.org/browser/trunk/target/linux?order=nameby bodhi - Debian
vaidyasr Wrote: ------------------------------------------------------- > I think I bricked my pogoplug v4. I installed the > uboot from the above link, but haven't installed > arch or debian. I just gave reboot, now no green > LED. How can I install the debian now?. Which link? do you have a log of what you did?by bodhi - uBoot
@Ingmar_k or Daniel Golle, I give up, I could not find where the Oxnas patch is :) is it in a single folder or do I need to diff the source tree?by bodhi - Debian
Neptune, The general idea is that you should try booting with Arch or Debian stick, and capture the entire boot log as it shown in serial console. And while in serial console prompt, printenv to get the settings of all u-boot envs. Perhaps the error is something easy to fix. Only if you can't boot back into either Arch or Debian, then perhaps think about installing new U-boot from theby bodhi - Rescue System
Sriram, Yes. There should be no problem doing what you want to do in either Debian or Arch.by bodhi - uBoot
Gray, Verify u-boot bootm and bootargs. They are slighly different between Debian and Arch. bootm: bootcmd_mmc=mmc init; ext2load mmc 0:1 0x00800000 /uImage; ext2load mmc 0:1 0x01100000 /uInitrd bootcmd=run bootcmd_usb; bootm 0x00800000 0x01100000 Is your mmc bootm similar to the above? For ALARM, bootm needs only uImage (there is no uInitrd), so bootm 0x00800000 has only one argumentby bodhi - uBoot
Looker, Some of your u-boot envs have incorrect syntax: correct: usb_scan_list=1 2 3 4 incorrect: console=‘ttyS0,115200’ When you list the envs with printenv, there should be no single quote. For example, the correct setting for the variable console above is: console=ttyS0,115200by bodhi - uBoot
@Peter, The bad stick is slow and the kernel has not gotten executed far enough to shut it off. As WarheadsSE explained here: http://forum.doozan.com/read.php?2,14484,14487#msg-14487by bodhi - Debian
@shv, I've not yet built the SATA version. It's on my Todo list, but lower priority than the next item (Kirkwood U-boot). I think you could use WarheadsSE files to boot new kernel uImage with embedded DTB. In the OXNAS kernel thread, I've shown how we can boot it with stock U-Boot using tftp.by bodhi - uBoot
@Daniel, Thanks for the offer! I have not looked into your patch set for openWRT yet so don't know if we have redundancy. I've never use openWRT so don't know my way around the code source tree :) but will try to browse your Git source.by bodhi - Debian
@Peter, See this thread for discussion about watchdog: http://forum.doozan.com/read.php?2,14351by bodhi - Debian
joerg_999, Quote> In Debian you can solve the problem with: apt-get > install ca-certificates and everything is fine, > but with my knowlege i´m not able to do the > similary in rescuesystem or Pogo OS (the 2nd > isn´t realy necessary for me) You could remount the root as rw and install new packages. But as it is a rescue system in NAND, I would not recommend changing anby bodhi - Rescue System
joerg_999, Your download link seems incompleted. Which rootfs are you trying to download?by bodhi - Rescue System
Gray, The last option is possible, but no procedure/setup is avalable for Debian. I suspect U-boot version has little or nothing to do with it (any version will work). But I am not interested in booting Pogo OS so never looked into this setup.by bodhi - uBoot
@gray, This is how you can install davygravy's U-boot build (I think this is at the moment the one to use, for simplicity and expediency). http://forum.doozan.com/read.php?2,11663 And you can also use ebbes's build (newer): http://forum.doozan.com/read.php?3,14697,15533#msg-15533 or malc's build (variant of stock): http://forum.doozan.com/read.php?3,15091 And yes,by bodhi - uBoot
Neptune, I think it is best that you connect serial console before flashing the latest U-Boot. See varkey's instruction: http://varkey.in/seagate-goflex-net-serial-connection/ Also this discussion about where to get the parts: http://forum.doozan.com/read.php?8,13263by bodhi - Rescue System
/dev/null, > CONFIG_USB_ACM=y > CONFIG_USB_SERIAL=y > > root@debian:~# ls /dev/ttyACM0 > /dev/ttyACM0 > Cool, thanks for posting your solution. These config will be included in my next realease.by bodhi - Debian
For various reasons, with U-Bit, I am hesitated to recommend you to go straight to install my latest U-boot build . However, let's look at your U-Bit environment to see if it is safe to install it. At U-Bit prompt, pls get output of these commands and post them here: uname -a cat /proc/mtd cat /etc/fw_env.config fw_printenv which flash_erase which nandwrite dmesgby bodhi - Rescue System
Neptune, OK. It sounds like you should update U-Boot anyway. Here is a post where vlad successfully installed U-boot using Jeff's script (this is an older version of U-boot, but should work and revive your box). After you've done this, boot with Arch rootfs. http://forum.doozan.com/read.php?3,6965,9111#msg-9111 Warning: updating U-boot always has some risk of bricking. Using Jeffby bodhi - Rescue System
Try to boot with Arch rootfs first. And install u-boot form inside Arch.by bodhi - Rescue System
absintos Wrote: ------------------------------------------------------- > zyxel nas320. the problem is that the fan is full > throttle by default...which is really loud. would > love if i could get it to quiet down a bit... It is supported. So please post your question/problem in a new NSA320 thread. I'm sure someone will answer.by bodhi - Debian
absintos, > also, i have this terrible feeling that the box is > generally behaving slower than the original latest > stock. Speed over samba has decreased > substantially from a stable 39MBps to somewhere > around 30MBps (samba 4.1 instead of samba3 > though). Perhaps it is true to the news/rumor: users have reported that kernel 3.15 suffers some performance regressiby bodhi - Debian
absintos Wrote: ------------------------------------------------------- > hi, > > does this kernel (3.15) support fan speed control > ? If yes, how would that get configured ? > > Abs It depends on the box that you have. And if it does, then it is really something specific to that box that might or might not need to be configured (kernel driver might have some defaulby bodhi - Debian
Neptune, If you plan to run Arch then it is best to install the Arch's build of latest U-boot, and use the same Arch rootfs you've already have. Follow steps 13 and 14 here: http://archlinuxarm.org/platforms/armv5/seagate-goflex-netby bodhi - Rescue System