Well, I've tried a lot of things. I think that the problems where the kernel is not booting stem from when the DTB is loaded ... and I've never been able to get your rootfs to work for me (or the kernel netconsole, for that matter). So I ended up going back to my upgraded-from-Jeff's-Wheezy-script installation (labeling it rootfs). Looking at that, if I actually point $dtb_fby klou - uBoot
Hi bodhi, Again, thanks for all of your help with this. I'm so close, I can almost taste it. While/before I was wrestling with the uboot envs, I ran Jeff's old Wheezy install script on a PNY flash drive and then updated it to Jessie. Then I was able to figure out uboot successfully, and after labeling the PNY as 'rootfs' was able to boot it. However, I'd like aby klou - uBoot
Sticky please. A lot of good info here.by klou - uBoot
I'm learning. If I were to modify your set of default envs, would the bootcmd be as below? (already adding rescue_set_bootargs, etc.) This would be using your uenv variables for usb scanning, instead of the "original" Jeff/davygravy ones from 2012. bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run rescue_bootcmd Or could I just completely rby klou - uBoot
If I'm reading this right, I can append "run rescue_bootcmd" to your default envs bootcmd (after "run bootcmd_exec") to force boot into rescue if no USB rootfs are found? Or does the default envs have a "fallback to default pogo/rescue environment if no USB installed"?by klou - uBoot
Thanks for your help with all of this. I've flashed the newer uBoot and the default env, but haven't rebooted yet. I'd still like to preserve the rescue environment, so do I need to migrate all of the old envs? Looking at the below list, I'm guessing that I can omit everything that starts with "usb" (-->marked, as this is duplicated somehow in the new envs?by klou - uBoot
OK, so I'm still confused about the order of operations here. 1) Flash new uBoot from the rescue image. Do I need to flash the u-boot default envs image (B)? If I do so, and make sure that the 4Requirements are met, then I assume that (D) creating a custom /boot/uEnv.txt is unnecessary? 2) Prepare the media/flash rootfs image. Hopefully the Dockstar will boot directly into a Debby klou - uBoot
Hi bodhi, Thanks for the answers! But I still have a few Q's... >You are running an older u-boot, so you should make sure that the current (old) u-boot envs is saved into a text file. And later retrofit a few u-boot >envs that are related to rescue system booting. Rescue image will remain intact. So I can update u-boot from rescue, correct? And what do you mean by retrofit uby klou - uBoot
Hey all, I played with the Dockstar several years ago, and shelved it after it either had a failed kernel upgrade (kirkwood from debian-backports) or the USB drive took a dump. However, I have a need for it and have a few questions regarding updates, especially since Jeff's original scripts were for Lenny/Squeeze, and not Jessie/Stretch. I booted it up today, and found that it has the 2by klou - uBoot