Shv, I dont think my spl image works in SATA mode. But you could try. NAND and SATA versions are built differently. I'd doubt that it would work.by bodhi - Debian
grayman4hire, > I'm a little confused regarding the mtd > partitions. So can we leave the mtd partition as > stock? You could set them back to stock, I don't see any problem with doing that.by bodhi - uBoot
vaidyasr, > Great. I think I have extracted arch in sd card by > mistake. I have extracted and now it is working. > Thanks bodhi. Now that's great to hear you can boot both USb and SD card! Any other problem please post them in a new thread and I'll respond.by bodhi - uBoot
Since a lot of people have been getting the Pogo V4/Mobile lately, just thought I'd repost the download link to one of my Pogo V4s original MTDs here. In case anybody wants to revert to stock, and can't do it because they have already installed newer U-Boot. Dowload at Dropbox: pogoplug_v4_mtd_original.tar.bz2 md5 064a298c89ae5a1b207061e11b401930 You only need to use mtd0 to reby bodhi - uBoot
purplelizard, Try these in order: 1. First, make sure you've created the rootfs as root user. If you did then try the next 2 tests. 2. Format the single partition to ext3, re-extract the rootfs to it, again as root. In netconsole, change rootfs type to ext3 using setenv, but don't save. Boot. 3. If no 2 did not work, restart. And in netconsole, remove the rootfstype using setenvby bodhi - uBoot
@gaogao, pbg4, and others NSA320 users, I've built a test version for U-Boot-2013.10 NSA320 from WarheasSE's GitHub. Please test with UART first if you have serial console. Download at Dropbox: uboot.2013.10-tld-1.nsa320.bodhi.tar md5 a828e4ccf905db76914f63b1cfc0807c Instruction for flashing to NAND is the same as for the NSA325 and in the main u-boot thread.by bodhi - uBoot
vaidyasr Wrote: ------------------------------------------------------- > done. can I reboot? Yes, but start netconsole on the other box first and cross fingers :) power up the Pogo.by bodhi - uBoot
vaidyasr, - You are not running (Flatten Device Tree) FDT kernel, so don't worry about it. - Your u-boot envs look good! except that you don't have netconsole running at boot. If you want to run it so you can observe boot progress: ./fw_setenv preboot 'run preboot_nc'by bodhi - uBoot
FYI, u-boot-kirkwood repo is now 2014.07. New branch 2014.07.b-kirkwood. New tag v2014.07-kirkwood.by bodhi - uBoot
absintos, You can add earlyprintk to kernel bootargs (depending what your bootargs looks like, just add it to the end). For example: usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts earlyprintk=serial And look at dmesg in serial console ouput. Perhaps stock U-Boot has different memory allocation, it's quiteby bodhi - Debian
Looker, You can see the version in netconsole or serial console.by bodhi - uBoot
vaidyasr, > My debian sd card was ext2. So I set > # ./fw_setenv rootfstype 'ext2' > > and mtdparts as > # ./fw_setenv mtdparts > 'mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uIma > ge2),8M(failsafe),112M(root)' > > Can I reboot with the Debian SDcard? Cool! you're almost there. - Did you set ethaddr to your box value? - Dby bodhi - uBoot
vaidyasr Wrote: ------------------------------------------------------- > Hi bodhi, > Any idea how to mount the pogoplug partitions > inside arch?. Otherwise I have to revert back to > stock using a pen drive. I never done this, so not sure how.by bodhi - uBoot
vaidyasr, Quote# ls -l > total 844 > -rwxr-xr-x 1 root root 12819 Jul 22 17:23 > flash_erase > -rwxr-xr-x 1 root root 329 Jul 22 17:23 > fw_env.config > -rwxr-xr-x 1 root root 668497 Jul 22 17:23 > fw_printenv > -rwxr-xr-x 1 root root 21286 Jul 22 17:23 > nanddump > -rwxr-xr-x 1 root root 11500 Jul 22 17:23 > nandwrite > -rw-r--r-- 1 root rby bodhi - uBoot
Hi vaidyasr, > Thanks bodhi. But when I use the instructions on > page 1 on step 2, I can't use fw_printenv. It says > error, which I have already posted. I'm quoting what I wrote in the 1st post: QuoteAlso, if you are running stock kernel, which usually does not provide NAND tools, you can download it here in this thread. Because Arch rootfs (like stock kernel) doesby bodhi - uBoot
absintos, The new kernel has more modules compiled in so it's quite a bit larger than before. > ext2load ide 0:1 0x00800000 /uImage; ext2load ide > 0:1 0x01100000 /uInitrd This should boot fine with uncompressed 6.9MB kernel (0x01100000 = 17MB, 0x00800000 = 8MB).by bodhi - Debian
Hi restamp, The L2 cache is re-enabled by the kernel during boot, we can see this in dmesg: root@tldDebian:~# dmesg | grep -i l2 [ 16.769392] Feroceon L2: Enabling L2 [ 16.769431] Feroceon L2: Cache support initialised.by bodhi - Debian
vaidyasr, You're confused 2 different instructions (the 1st were written long ago for a different purpose). 1. Using new kernel with stock u-boot (blparam is needed) QuoteI believe the link above you have shared should be http://forum.doozan.com/read.php?3,11538,11706 2. Installing new-uboot (this thread) (blparam does not come in to play at all). Ignore every thread that you havby bodhi - uBoot
OK. Got rid of this error after refetch every thing. git fetch --allby bodhi - uBoot
Tinkerer, It does not sound there was any hanshake occured. It occurs when the spinning | changes speed. So I think it could be either: - Your kwboot binary is not working. or - Your GoFlexHome does not have correct Boot ROM. or - Your serial console does not work (can you test it somehow?). If you have the dmesg log after you SSH in, and before you installed Arch, please post here.by bodhi - uBoot
@WarheadsSE, I'm rebasing u-boot-kirwood and got this error: # git checkout -b 2014.07-kirkwood 524123a70761110c5cf3ccc5f52f6d4da071b959 fatal: reference is not a tree: 524123a70761110c5cf3ccc5f52f6d4da071b959 Any idea why? I've used this same command before to rebase 2014.01. In the second attempt, I've created the branch 2014.07-kirkwood first and then got the sameby bodhi - uBoot
vaidyasr, Please reread the first post. The link I've included above is only for information. The 1st post in this thread is what you need to follow. Take your time.by bodhi - uBoot
@vaidyasr, Here is the thread that shows similar instruction about how to install new U-Boot manually. The starting point is from the Arch Linux installation of Pogo V4/Mobile: Install uBoot/Debian From this post, you can see the NAND tools set is needed to do the installation, if you are installing from a system that does not provide it (stock Pogo OS, Pogo V4 Arch Linux). And as theby bodhi - uBoot
vaidyasr Wrote: ------------------------------------------------------- > Ok, thank you. One more question. I found the > script in arch linux installation called > ppv4-install.sh. which contains similar steps on > page 1, but dealt with bldparm, so can I just use > the same script by making appropriate changes (not > to download uboot from web) and use your uboot?. Nby bodhi - uBoot
See this post: http://forum.doozan.com/read.php?3,8044,8152#msg-8152by bodhi - Debian
@gray It is more complicated than just adding the file. @vaidyasr, When you boot with Arch installation on Pogo V4/Mobile, you're not using the uboot-env-tools that newer systems are using. You are using blparam (cloudengines tool to deal with NAND). So let me get you the links to different threads here, and once you've read them, I'll write more explanation.by bodhi - uBoot
FYI, I've re-upload uboot.2014.07-tld-1.environment.img.bodhi.tar to fix typos in bootcmd which was reported in this post.by bodhi - uBoot
vaidyasr, If your question is about the Pogo V4 or Mobile with Arch installed, then 3TB is not supported and netconsole is not supported either. This is because current ALARM Pogo V4 U-boot is a variant of stock U-Boot. So you can install the latest U-Boot in this thread and boot the same Arch rootfs. But with your current U-Boot and Arch installation, you will need to download NAND tools (by bodhi - uBoot
shv, Have you tried this instruction ? also in the working thread at ALARM site, I recall some have succesfully prepared and booted with SATA.by bodhi - Debian
agiorgio, I would recommend to recreate the partitions after booting into your current rootfs on USB (to take advantage of the latest Debian packages). Live CD is usually old and only good for emergency usage. And I think the latest U-Boot code does GPT detection properly, perhaps something is not quite right in your drive partitions? it's best to start from scratch in Debian.by bodhi - Debian