now i'm getting this when i boot.. U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700) Pogoplug V4 gcc (Debian 6.3.0-18) 6.3.0 20170516 GNU ld (GNU Binutils for Debian) 2.28 Hit any key to stop autoboot: 0 starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices... Use USB retry period from the environmby yeehaa - uBoot
spoke too soon.. i created a new debian ext4 usb stick as shown in the thread here and got this when i booted.. U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700) Pogoplug V4 gcc (Debian 6.3.0-18) 6.3.0 20170516 GNU ld (GNU Binutils for Debian) 2.28 Hit any key to stop autoboot: 0 running scan_disk ... Scan device usb starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devicby yeehaa - uBoot
bodhi Wrote: ------------------------------------------------------- > yeehaa, > > > ok.. i may have confused the hell out of you.. > > here is what i did on this pogo plug mobile.. i > > have the arch rescue on the mtd1 partition.. i > > went ahead and flashed your uboot and uboot > envs > > to mtd0 as per the thread you linked.. then.... > &gby yeehaa - uBoot
bodhi Wrote: ------------------------------------------------------- > yeehaa, > > I am assuming you're running my released u-boot, > but apparently you are running Arch u-boot :) > That's why there were some envs error. > > What you should do is booting into Debian, and > > install u-boot > > QuoteLast Updated 28 Oct 2017 > Updatedby yeehaa - uBoot
bodhi Wrote: ------------------------------------------------------- > yeehaa, > > Here you go, give it a try. > > With the USB unplugged, power up and interrupt > netconsole, copy/paste and execute each command at > the prompt: > > > setenv bootcmd 'run scan_disk; run set_bootargs; > run bootcmd_exec; printenv; printenv bootargs; run >by yeehaa - uBoot
yep.. will hold till you've had a chance to rewrite the commands.. thanks! does this help btw? -> https://archlinuxarm.org/forum/viewtopic.php?f=30&t=8383#p46069by yeehaa - uBoot
bodhi Wrote: ------------------------------------------------------- > yeehaa, > > > seems like the third command doesnt execute > > fully.. some setenv restriction? > > Please post the full boot log. > > > btw.. my environment now looks a bit different > > from the one that i posted a couple days back.. > > dont know how/why because thisby yeehaa - uBoot
seems like the third command doesnt execute fully.. some setenv restriction? the first two executed correctly.. Pogoplugv4> setenv arch_rescue 'echo Trying to boot from NAND ...; setenv arch_dtb_file "/boot/dtbs/kirkwood-pogoplugv4.dtb"; setenv arch_mountubi "ubi part rootfs; ubifsmount ubi0:rootfs"; setenv arch_loadaddr "0x810000"; setenv arch_fdtaddby yeehaa - uBoot
thanks bodhi.. please see "since i do not have serial and the netconsole is showing only the uboot messages (once kernel loads, no more messages on the default 10.10.10.4 ip even when booting from the arch rescue".. i've ordered a serial cable.. hopefully will be here in a couple of weeks.. in the mean time, i will try this from the netconsole and report backby yeehaa - uBoot
bodhi Wrote: ------------------------------------------------------- > yeehaa, > > Please post your current Arch u-boot envs > information here: > > cat /etc/fw_env.config > fw_printenv > posted! thanksby yeehaa - uBoot
U-Boot 2016.09.01-1 (Oct 10 2016 - 23:13:37 -0600) Arch Linux ARM Pogoplug V4 From alarm rescue: cat /etc/fw_env.config # Configuration file for fw_(printenv/saveenv) utility. # Up to two entries are valid, in this case the redundand # environment sector is assumed present. # MTD device name Device offset Env. size Flash sector size #/dev/mtd2 0x0000by yeehaa - uBoot