Pogoplug E04 not booting from SD Card or USB

Hi bodhi,

I have restored my original uImage, so I'm ready to reboot and just wanted to ensure I'm good.

I don't think I need to setup netconsole if I have my serial connection and for uenvs.txt in step C, I can add that later if needed correct?

I see the pogo options are gone from the boot cmd, so does that mean it will not boot at all without anything plugged in?

Below is my final printenv, can you take a look to see if I should add anything for the pogo, or if anything is missing

root@debian:/boot# fw_printenv
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
ethact=egiga0
if_netconsole=ping $serverip
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb_addr=0x1c00000
load_initrd_addr=0x1100000
load_uimage_addr=0x800000
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
mainlineLinux=yes
mtdids=nand0=orion_nand
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
usb_ready_retry=15
arcNumber=3960
machid=f78
ethaddr=00:25:31:05:f5:25
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtb
ipaddr=10.0.1.231
serverip=10.0.1.220
root@debian:/boot#

If all looks good, then I think I am good to reboot



Edited 12 time(s). Last edit at 01/17/2021 01:29AM by Rhodess.

One further question bodhi,

Assuming all goes well, does that mean I should stay on version 5.2.9, or would I be free to upgrade to the latest 5.9.12? I'm not planning to get too far ahead of myself, just curious as to the limitations with the current hardware and u-boot and also a little confused on the opening post statement in Linux Kernel 5.9.12 Kirkwood package and Debian rootfs since uname, proc/version and dmesg all show 5.2.9 for the kernel so I'm unsure what the 5.9.12 latest kernel if referring to

Thanks



Edited 1 time(s). Last edit at 01/17/2021 03:19PM by Rhodess.

Rhodess.

Quote

If all looks good, then I think I am good to reboot

Yes all looks good.

Quote

Assuming all goes well, does that mean I should stay on version 5.2.9, or would I be free to upgrade to the latest 5.9.12? I'm not planning to get too far ahead of myself, just curious as to the limitations with the current hardware and u-boot and also a little confused on the opening post statement in Linux Kernel 5.9.12 Kirkwood package and Debian rootfs since uname, proc/version and dmesg all show 5.2.9 for the kernel so I'm unsure what the 5.9.12 latest kernel if referring to

Once you booted into this Debian rootfs, the kernel is 5.2.9. And after checking the system to see it is running well, you can proceed to install the latest kernel. You don't need to set up netconsole, since you have serial console. In the furture, if you intend to remove the serial connection (e.g. to use it on other boxes), then you might want to setup netconsole so you can see the boot log if and when you need it,

The release thread is on going for each new kernel version (when I have time to build it). So you see a lot of kernel package releases after the rootfs 5.2.9 was released. The most recent kernel is on top. Currently we are at 5.9.12. I'm about to release 5.10.7, so you might hold on a day or two, and install kernel 5.10.7.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

awesome, thanks for all your help. It's been a good learning experience

Also,

Quote

I see the pogo options are gone from the boot cmd, so does that mean it will not boot at all without anything plugged in?

Yes.

Make sure you keep the mtd0 backup like I recommended in the u-boot installation instruction. That will allow you to setup to boot to stock if you want later. That the run_pogo env was for.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)