Well, that got me into the boot process, but during the boot, several systemd processes fail, including network name resolution and login service. I'm trying to use the 5.2.9-1 kernel. Using TTY, I get a login prompt, but authentication fails. I think that this is an Arch problem, not a U-boot problem. I will see if I can find any discussion on how to fix this.by woody - uBoot
Ok, I created a test installation of Arch Arm and got it booting up with your U-boot. I then upgraded to the mainline kernel. Now I have a zimage file and a dtb file, but no uimage file. I think that I should be able to boot with the dtb file, but I can't get it to work. I'm using these env settings: set_bootargs=setenv bootargs console=ttyS0,115200 root=$usb_root rootdelay=10 $mtby woody - uBoot
I'll check it out. Do you think it's ok to use this u-boot with Arch Linux?by woody - uBoot
Sorry, I didn't see any indication that this is a Debian forum. The heading I saw was for U-Boot. I thought people were probably using various OS's. Yes, it's Arch Linux Arm. What's the extra step I need?by woody - uBoot
Ok, seems like things are generally working ok, except I still can't boot when I have set_bootargs pointing to 'root=LABEL=rootfs'. I'm running Arch Linux. My root drive is on /dev/sda1 and is labeled 'rootfs'. I changed the partition label to 'rootfs'. The /boot folder is also on that partition. It appears that it should boot that way, but it's not wby woody - uBoot
Ok, I'm going to relabel my rootfs and try it again Another question: I previously had Jeff's rescue system installed, but it's not working with the new environment variables. I think I need to add these back: force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fiby woody - uBoot
In my case, the ones I'm updating still have an old u-boot, so I have to reflash mtd0 anyway. This way, I should be able to flash the nanddump from the one I already converted and fix the environment variables at the same time. One issue I had with the first one is that it would not boot into my root partition using the partition label. The first partition is labeled ROOTFS in all caps. Iby woody - uBoot
Thanks for the quick reply! That helps a lot.by woody - uBoot
I have several Pogoplug E02 devices. I recently updated u-boot on one of them to the 2017-07 U-Boot using the instructions posted by Bodhi. I managed to bork up some of the environment settings, so I had to crack open the Pogo and use a serial console to get it working again. I want to upgrade my other devices, but I don't want to have to set the environment settings for each one. I haveby woody - uBoot
I have the Doozan rescue system installed on my PogoPlug E02. For some reason the rescue root password that I have in my records is not working. Is there a fairly simple way to change or reset the root password from TFTP login without reflashing the rescue system?by woody - Rescue System
I got a good rescue system working by copying mtd1 and mtd2 partitions from another Pogo that had a working rescue system, so the new Pogo is all set. Sorry if this is a dumb question, but can I safely clone the updated U-boot from my new Pogo to my older ones by using nandwrite to mtd0? Will this transfer the environment variables, also?by woody - uBoot
I'll look at moonman's rescue system. Thanks much for all your help! By the way, once I get this Pogo set up correctly, is there an easy way to clone the environment settings from one Pogo to a different one?by woody - uBoot
OK, rescue_installed=1 force_rescue is not definedby woody - uBoot
Thanks much for your help! I made the changes you recommended and it appears that I'm now booting into rescue, however, I don't see the Pogo getting an IP address and it does not allow me to ssh into the IP address that's set in the environment variable. Here's what showed up in the boot log: NAND read: device 0 offset 0x100000, size 0x400000 4194304 bytes read: OKby woody - uBoot
OK, setting the preboot variable fixed it. I'm now able to use Netconsole and normal booting up to Arch Linux is working too. The only thing that does not appear to be working is that I'm not able to ssh into rescue, as I was able to do with the old u-boot/rescue. Is that function supposed to be working with this release? Is there something I need to do to enable it?by woody - uBoot
So, can 'fw_setenv preboot 'run preboot_nc'' be called from a uEnv.txt file? Because I think that's working in my setup.by woody - uBoot
I have installed the latest release on one of my Pogoplug E02 devices, but it appears that I've hosed up the environment variables. I'm able to boot in Arch Linux, but Netconsole/Rescue isn't working. I'm wondering if I should go back to Jeff's old release and start over again. Here are the variables I have configured: baudrate=115200 bootcmd_usb=run usb_init; ruby woody - uBoot