saschadd, Here is another revised envs set. The bold line is the modifcation: setenv bootdev usb setenv device '0:1' setenv dtb_file '/boot/dts/armada-388-db.dtb' setenv load_dtb_addr 0x1000000 setenv load_initrd_addr 0x2900000 setenv load_image_addr 0x02000000 setenv load_dtb 'echo loading DTB $dtb_file ...; ext2load $bootdev $device $load_dtb_addr $dtb_fby bodhi - Debian
ming, See here: http://forum.doozan.com/read.php?3,34013,34190#msg-34190by bodhi - uBoot
balanga, You can use one from the u-boot installation thread: http://forum.doozan.com/read.php?3,12381 QuoteA. Flashing Instruction: Installation is the same for each u-Boot image, the instruction below is written to include all boxes. So choose the platform name that you are installing for, and copy/paste the appropriate commands. If you are running kernel that do not provby bodhi - uBoot
saschadd, It's not possible to boot USB 3.0. We can only use USB 2.0 for booting. For now, the next 2 things to try. 1. Logging into stock OS and copy the DTB file that the stock kernel uses for booting to the Debian rootfs /boot/dts/. fdtfile=armada-38x-modular.dtb And adjust the env to boot with this DTB. 2. I need to compile the DTS from the second link (armada-385-ex2uby bodhi - Debian
saschadd, Here is the revised envs: setenv bootdev usb setenv device '0:1' setenv dtb_file '/boot/dts/armada-388-db.dtb' setenv load_dtb_addr 0x1000000 setenv load_initrd_addr 0x2900000 setenv load_image_addr 0x02000000 setenv load_dtb 'echo loading DTB $dtb_file ...; ext2load $bootdev $device $load_dtb_addr $dtb_file' setenv load_initrd 'echo loaby bodhi - Debian
ming Wrote: ------------------------------------------------------- > > root@PogoPlug:/media/sdb1/boot# mkimage -A arm -O > linux -C none -T kernel -a 0x > 60008000 -e 0x60008000 -n 'Linux-3.3.17.0-oxnas-tl > d-1' -d zImage-3.17.0-oxnas-tl > d-1.fdt uImage sync > /bin/ash: mkimage: not found > Look for mkimage binary: find /media/sdb1/ mkimageby bodhi - uBoot
saschadd, Interrupt serial console, get the syntax for env command: env env help help env Please post output.by bodhi - Debian
pengu Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > > So using the Wiki simple smb.conf, the xfer spee > d > > for 10GB file is 85MB/s and 92MB/s? > > this were the rates without the mentiond line. > I cannot do more on this atm because my NAS326 is &gby bodhi - Debian
Yes:) I saw where the problem is, will post a revised envs set.by bodhi - Debian
ming Wrote: ------------------------------------------------------- > How to set up to boot USB rootfs first.Is there an > y blog that you can learn from? Right here in this forum: http://forum.doozan.com/read.php?2,16044by bodhi - uBoot
balanga Wrote: ------------------------------------------------------- > Ok I've finally got a chance to follow the instruc > tions cited and have a few questions.... The examp > le uses kirkwood-goflexnet.dtb... should I substit > ute kirkwood-goflex.home.dtb? Not sure of the diff > erences between the two. > Yes, use kirkwood-goflexhome.dtb > Also I'by bodhi - uBoot
habibie Wrote: ------------------------------------------------------- > Hello Bodhi and thank you for your response. > > Sorry that I forgot to mention I have a working uE > nv.txt file when OpenWRT/LEDE still provided the . > dtb file. Unfortunately, now the .dtb file has bee > n depricated when they started supporting DTS form > at. I am not sure that makes any seby bodhi - uBoot
phileblunt86, > > Okay, my PP booted with the Debian rootfs in the t > hread you referenced, and im able to ssh in. I'm h > appy to know my plug isn't borked! Cool! > However I still > can't get the standard Arch Kirkwood build to load > . Could this have to do with my U-boot? No, not your uboot. > And how wo > uld I go about fixingby bodhi - uBoot
saschadd, Good progress :) Here is the revised envs setenv bootdev usb setenv device '0:1' setenv dtb_file '/boot/dts/armada-388-db.dtb' setenv load_dtb_addr 0x1000000 setenv load_initrd_addr 0x2900000 setenv load_uimage_addr 0x02000000 setenv load_dtb 'echo loading DTB $dtb_file ...; ext2load $bootdev $device $load_dtb_addr $dtb_file' setenv load_iby bodhi - Debian
saschadd, 1. No private stuff remained in the envs 2. All envs look good except one (my omission): This line should have double quotes: setenv usb_set_bootargs 'setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts"' After setting this, and other envs like before, you can try booting: boot See how far we will get. You can post tby bodhi - Debian
Here is u-boot installation thread: 2015.10 U-Boot for Pogoplug V3 (OXNAS OX820) Section: QuoteA. How to use the uEnv.txt script This uEnv.txt script can be used to further customizing u-boot envs without saving to NAND or to boot with a completely different set of u-boot envs. Create a text file in /boot directory with the content in the format that u-boot envs are listed. Exaby bodhi - uBoot
The envs got cut off on the right side. Please repost.by bodhi - Debian
lille, Power up, interrupt serial console and printenv boot Please post the entire serial console log (meaning from u-boot banner till the end, where it fails to boot).by bodhi - Debian
Cisco, How about: > Environment size: 2586/131068 bytes > Pogov4> At this point, without the USB or SD attached, try booting with serial console setenv archNumber 3960 boot Please post the entire log. ------ Note: I am not at home so I can't really see everything in the Pogo V4 box. I could revisit this subject in 2-3 weeks.by bodhi - uBoot
saschadd, The nanddump looks good. And I had a typo in previous post. So now, try again setenv bootdev usb setenv device '0:1' setenv dtb_file '/boot/dts/armada-388-db.dtb' setenv load_dtb_addr 0x1000000 setenv load_initrd_addr 0x2900000 setenv load_uimage_addr 0x02000000 setenv load_dtb 'echo loading DTB $dtb_file ...; ext2load $bootdev $device $load_by bodhi - Debian
phileblunt86, Since you have installed Arch u-boot, try booting Debian rootfs following this instruction: http://forum.doozan.com/read.php?3,23727 And then you can decide whether keeping Debian or go back to Arch.by bodhi - uBoot
Nucleorptoein, It is best that you start with shv SATA boot setup: http://forum.doozan.com/read.php?3,16017,17297#msg-17297 And then we'll go from there.by bodhi - uBoot
saschadd, Your dmesg showed 8 partitions 8 ofpart partitions found on MTD device armada-nand Creating 8 MTD partitions on "armada-nand": 0x000000000000-0x000000500000 : "U-Boot" 0x000000500000-0x000000a00000 : "uImage" 0x000000a00000-0x000000f00000 : "uRamdisk" 0x000000f00000-0x00001c800000 : "image.cfs" 0x00001c800000-0x00001d700000 :by bodhi - Debian
Cisco, > > > U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700 > ) > Pogoplug V4 > > SoC: Kirkwood 88F6192_A1 > DRAM: 128 MiB > WARNING: Caches not enabled > NAND: 128 MiB > MMC: kwsdio: 0 > In: serial > Out: serial > Err: serial > Net: egiga0 > Using egiga0 device > > ARP Retry count exceeded; starting agby bodhi - uBoot
woody, > there a fairly simple way to change or reset the r > oot password from TFTP login without reflashing th > e rescue system? You meant SSH login? Are you not able to log in at all even with serial console? If that is true, then you need to boot in to Debian, mount the NAND rescue rootfs , and then modify the root login password file.by bodhi - Rescue System
Cisco, To turn off netconsole, change the IP address of your host that you are using to connect to the Pogo: host 192.168.1.15 Change thiis host IP to something else, such as 192.168.1.16. Power up, and let it boot all the way. Post entire serial console log.by bodhi - uBoot
Cisco, The code tags is the right most button in this text window when you are writing the post.by bodhi - uBoot
Quote1. If you have serial console, - Post the entire serial boot log - Log into stock OS or Debian and get the output of cat /proc/mtd fw_printenv The entire bootlog means from the u-boot prompt until the failed boot. Marvell>> boot And seeing this entore serial boot log I will be able to see if you failed or succcessful booting to stock OS.by bodhi - Debian
Cisco, Your netconsole is activated, so the serial boot log was not compeleted. Using egiga0 device host 192.168.1.15 is alive Using egiga0 device There should be a lot more info at this point. But you did not interrupt u-boot and post your u-boot envs so I can't tell you how to modify the envs to turn it off. ---- Power up, interrupt serial console and printenv Pleaby bodhi - uBoot