Do I need to update Uboot

I've got 4 pogo-plug mobiles. Getting ready to use them in a project. All have

U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45)

Linux-3.14.0-kirkwood-tld-1

installed. The installations are on very old, very slow 2GB SD cards & I want to move to larger, faster cards I made copy of the working good SD card with dd, then tried to "upgrade" the OS, found out the hard way not to do dist-upgrade.

No worries, it was copy. So now I'm dd'ing again. Understand that I want to avoid the dist-upgrade, just update my sources in apt, run "upgrade" (not dist-upgrade). Correct? & then if I want a newer kernel, download that here.

Questions:

instructions for a kernel upgrade are where?

Do I need to (should I) update uboot? I know it's an old version. If I don't really need to, then I won't since I don't anticipate using these things much longer (as RasbPi s are so cheap). But if I really should update uboot before spending the time to patch up the OS, this is the time to do it.

craigcoffman,

> Understand that I want to avoid the dist-upgrade,
> just update my sources in apt, run "upgrade" (not
> dist-upgrade). Correct? & then if I want a newer
> kernel, download that here.

If you don't care to run with all new Debian stretch packages, then don't do dist-upgrade. Just apt-get upgrade with be enough:

https://forum.doozan.com/read.php?2,35581

> Questions:
>
> instructions for a kernel upgrade are where?

https://forum.doozan.com/read.php?2,12096

> Do I need to (should I) update uboot? I know it's
> an old version. If I don't really need to, then I
> won't since I don't anticipate using these things
> much longer (as RasbPi s are so cheap). But if I
> really should update uboot before spending the
> time to patch up the OS, this is the time to do
> it.

You don't need to upgrade u-boot. U-Boot 2014.07-tld-1 is a pretty recent version that has all the modern features.

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

I cannot seem to get the new kernel 4.12.8 to work. here's my uboot env:

root@tweedledum:~# fw_printenv
baudrate=115200
bootcmd=run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
mtdids=nand0=orion_nand
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
rootdelay=10
rootfstype=ext3
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
stderr=serial
stdin=serial
stdout=serial
usb_init=usb start
usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1
ethaddr=00:25:31:03:e9:15
arcNumber=3960
machid=F78
usb_rootfstype=ext3
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
serverip=192.168.2.12
ipaddr=192.168.2.102
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole
load_dtb=ext2load usb 0:1 0x1c00000 /boot/dts/kirkwood-pogoplug_v4.dtb
load_initrd=ext2load usb 0:1 0x1100000 /boot/uInitrd
load_uimage=ext2load usb 0:1 0x800000 /boot/uImage
usb_boot=run load_dtb; run load_uimage; if run load_initrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi

as you can see, I did enter the uboot env lines as stated in the instructions

after un-taring the new kernel & the dts files, I installed the deb package as instructed. Then I created the images:

mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.12.8-kirkwood-tld-1 -d vmlinuz-4.12.8-kirkwood-tld-1 uImage

mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-4.12.8-kirkwood-tld-1 -d initrd.img-4.12.8-kirkwood-tld-1 uInitrd

watching through netconsole, both files load, but the machine never finishes it's boot. (the light on my pogoplug v4 (mobile) stays orange). copying the original uImage & uInitrd back allows me to boot again.

BTW, i notice in print the env that the ipaddr statement needs be changed to what I have in my /etc/interfaces.. it's doesn't seem to be a problem & with netconsole I specify the address in /etc/interfaces & connect just fine (*.9 instead of *.102) I should probably change that. Syntax:? fw_setenv ipaddr '192.168.2.9' ?? correct?

So, any clue what I've done wrong?

------
Moderator edit: please use code tags.



Edited 1 time(s). Last edit at 09/25/2017 01:22PM by bodhi.

Also installed the 4.12.1 rootfs on a separate sd-card just for a test.

no modifications other than /etc/interfaces /etc/hostname /etc/hosts.

Same behavoir... files are found, appear to load, process sticks, light stays orange. cannot ping or ssh to box.

just in case this helps.

another piece of information:

I have: custom_params=init=/bin/systemd

in my /boot/uEnv.txt

The "original" file system I'm trying to install the kernel on (& that I want to keep) has been updated to debian_ver 9.1 & has systemd fully installed. (sysvinit removed).

booting on the old kernel (3.14) all works fine.

craigcoffman,

If you don't have serial console, then post the netconsole log (everything from u-boot banner until the last thing you see on your terminal).

And also post the file listing. Mount your rootfs, which has 4.12.8, on another working box, and (assuming it is mounted as sdb1),

ls -lart /media/sdb1/
ls -lart /media/sdb1/boot

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

Also an advice:

Quote

The "original" file system I'm trying to install the kernel on (& that I want to keep) has been updated to debian_ver 9.1 & has systemd fully installed. (sysvinit removed).

Don't remove sysvinit. On your working systemd booting system, reinstall sysvinit, and use the uEnv.txt to boot systemd like you did.

I have: custom_params=init=/bin/systemd

Even you've chosen to use systemd solely, you can still use sysvinit as a fallback mechanism when systemd has problem booting. systemd is still a growing pain.

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

Here' you go. Very much appreciate your time.

root@sirguy:~# nc -u 192.168.2.9 6666

U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45)
Pogoplug V4
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot:  0 
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!

MMC rescan: current device # 0 initialized OK
3804408 bytes read in 1284 ms (2.8 MiB/s)
7350632 bytes read in 1554 ms (4.5 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.12.8-kirkwood-tld-1
   Created:      2017-09-25   1:15:03 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3804344 Bytes = 3.6 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.12.8-kirkwood-tld-1
   Created:      2017-09-25   1:18:20 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7350568 Bytes = 7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK


Starting kernel ...

root@sirguy:/media/craig/rootfs/boot# ls -lart *
-rw-r--r-- 1 root root   123040 Apr  2  2014 config-3.14.0-kirkwood-tld-1
-rw-r--r-- 1 root root  1736932 Apr  2  2014 System.map-3.14.0-kirkwood-tld-1
-rw-r--r-- 1 root root  2461352 Apr  2  2014 vmlinuz-3.14.0-kirkwood-tld-1
-rw-r--r-- 1 root root  2461416 Apr  6  2014 uImage.orig
-rw-r--r-- 1 root root  6362802 Apr  6  2014 uInitrd.orig
-rwxr-xr-x 1 root root  3804344 Aug 17 06:53 zImage-4.12.8-kirkwood-tld-1
-rw-r--r-- 1 root root   153512 Aug 18 01:17 config-4.12.8-kirkwood-tld-1
-rw------- 1 root root  2508981 Aug 18 02:01 System.map-4.12.8-kirkwood-tld-1
-rw------- 1 root root  3804344 Aug 18 02:01 vmlinuz-4.12.8-kirkwood-tld-1
-rw-r--r-- 1 root root 18443814 Aug 18 02:07 linux-image-4.12.8-kirkwood-tld-1_1.0_armel.deb
-rw-r--r-- 1 root root  8588292 Aug 18 02:24 linux-headers-4.12.8-kirkwood-tld-1_1.0_armel.deb
-rw-r--r-- 1 root root   146602 Aug 18 05:00 linux-4.12.8-kirkwood-tld-1.patch
-rw-r--r-- 1 root root  7738652 Sep 24 15:31 initrd.img-3.14.0-kirkwood-tld-1
-rw-r--r-- 1 root root  7350568 Sep 24 19:35 initrd.img-4.12.8-kirkwood-tld-1
-rw-r--r-- 1 root root       32 Sep 24 19:53 uEnv.txt
-rw-r--r-- 1 root root  3804408 Sep 24 20:15 uImage.new
-rw-r--r-- 1 root root  7350632 Sep 24 20:18 uInitrd.new
-rw-r--r-- 1 root root  3804408 Sep 25 13:31 uImage
-rw-r--r-- 1 root root  7350632 Sep 25 13:31 uInitrd

dts:
total 1400
-rw-r--r-- 1 root root 12772 Aug 18 02:28 kirkwood-dir665.dtb
-rw-r--r-- 1 root root 10392 Aug 18 02:28 kirkwood-db-88f6282.dtb
-rw-r--r-- 1 root root  9504 Aug 18 02:28 kirkwood-db-88f6281.dtb
-rw-r--r-- 1 root root 12284 Aug 18 02:28 kirkwood-d2net.dtb
-rw-r--r-- 1 root root  9944 Aug 18 02:28 kirkwood-cloudbox.dtb
-rw-r--r-- 1 root root 10769 Aug 18 02:28 kirkwood-canvio-home-nas.dtb
-rw-r--r-- 1 root root 10756 Aug 18 02:28 kirkwood-blackarmor-nas220.dtb
-rw-r--r-- 1 root root 10734 Aug 18 02:28 kirkwood-b3.dtb
-rw-r--r-- 1 root root 13516 Aug 18 02:28 kirkwood-asus_m25.dtb
-rw-r--r-- 1 root root 21874 Aug 18 02:28 kirkwood-ds209.dtb
-rw-r--r-- 1 root root 22862 Aug 18 02:28 kirkwood-ds112.dtb
-rw-r--r-- 1 root root 22766 Aug 18 02:28 kirkwood-ds111.dtb
-rw-r--r-- 1 root root 21914 Aug 18 02:28 kirkwood-ds110jv10.dtb
-rw-r--r-- 1 root root 21934 Aug 18 02:28 kirkwood-ds109.dtb
-rw-r--r-- 1 root root 10287 Aug 18 02:28 kirkwood-dreamplug.dtb
-rw-r--r-- 1 root root 10396 Aug 18 02:28 kirkwood-dockstar.dtb
-rw-r--r-- 1 root root 13473 Aug 18 02:28 kirkwood-dns325.dtb
-rw-r--r-- 1 root root 13425 Aug 18 02:28 kirkwood-dns320.dtb
-rw-r--r-- 1 root root 22770 Aug 18 02:28 kirkwood-ds411slim.dtb
-rw-r--r-- 1 root root 21874 Aug 18 02:28 kirkwood-ds411j.dtb
-rw-r--r-- 1 root root 22790 Aug 18 02:28 kirkwood-ds411.dtb
-rw-r--r-- 1 root root 21886 Aug 18 02:28 kirkwood-ds409slim.dtb
-rw-r--r-- 1 root root 21894 Aug 18 02:28 kirkwood-ds409.dtb
-rw-r--r-- 1 root root 21914 Aug 18 02:28 kirkwood-ds212j.dtb
-rw-r--r-- 1 root root 22906 Aug 18 02:28 kirkwood-ds212.dtb
-rw-r--r-- 1 root root 21958 Aug 18 02:28 kirkwood-ds210.dtb
-rw-r--r-- 1 root root  9540 Aug 18 02:28 kirkwood-iomega_ix4_200d.dtb
-rw-r--r-- 1 root root 12298 Aug 18 02:28 kirkwood-iomega_ix2_200.dtb
-rw-r--r-- 1 root root 11580 Aug 18 02:28 kirkwood-iconnect.dtb
-rw-r--r-- 1 root root 10867 Aug 18 02:28 kirkwood-ib62x0.dtb
-rw-r--r-- 1 root root 10522 Aug 18 02:28 kirkwood-guruplug-server-plus.dtb
-rw-r--r-- 1 root root 11895 Aug 18 02:28 kirkwood-goflexnet.dtb
-rw-r--r-- 1 root root 10603 Aug 18 02:28 kirkwood-goflexhome.dtb
-rw-r--r-- 1 root root 12785 Aug 18 02:28 kirkwood-ea4500.dtb
-rw-r--r-- 1 root root 12075 Aug 18 02:28 kirkwood-ea4500-dsa.dtb
-rw-r--r-- 1 root root 14321 Aug 18 02:28 kirkwood-linkstation-lswvl.dtb
-rw-r--r-- 1 root root 12558 Aug 18 02:28 kirkwood-linkstation-lswsxl.dtb
-rw-r--r-- 1 root root 13673 Aug 18 02:28 kirkwood-linkstation-lsvl.dtb
-rw-r--r-- 1 root root 14689 Aug 18 02:28 kirkwood-linkstation-lsqvl.dtb
-rw-r--r-- 1 root root 13091 Aug 18 02:28 kirkwood-lenovo-ix2-ng.dtb
-rw-r--r-- 1 root root 13095 Aug 18 02:28 kirkwood-lenovo-iomega-ez.dtb
-rw-r--r-- 1 root root 10774 Aug 18 02:28 kirkwood-laplug.dtb
-rw-r--r-- 1 root root  8544 Aug 18 02:28 kirkwood-km_kirkwood.dtb
-rw-r--r-- 1 root root 10282 Aug 18 02:28 kirkwood-is2.dtb
-rw-r--r-- 1 root root 13763 Aug 18 02:28 kirkwood-net5big.dtb
-rw-r--r-- 1 root root 12387 Aug 18 02:28 kirkwood-net2big.dtb
-rw-r--r-- 1 root root 12731 Aug 18 02:28 kirkwood-nas2big.dtb
-rw-r--r-- 1 root root 11279 Aug 18 02:28 kirkwood-mv88f6281gtw-ge.dtb
-rw-r--r-- 1 root root 11097 Aug 18 02:28 kirkwood-mplcec4.dtb
-rw-r--r-- 1 root root 12737 Aug 18 02:28 kirkwood-lsxhl.dtb
-rw-r--r-- 1 root root 12741 Aug 18 02:28 kirkwood-lschlv2.dtb
-rw-r--r-- 1 root root 12805 Aug 18 02:28 kirkwood-linksys-viper.dtb
-rw-r--r-- 1 root root 13429 Aug 18 02:28 kirkwood-linkstation-lswxl.dtb
-rw-r--r-- 1 root root 13074 Aug 18 02:28 kirkwood-nsa310.dtb
-rw-r--r-- 1 root root 10533 Aug 18 02:28 kirkwood-ns2mini.dtb
-rw-r--r-- 1 root root 10565 Aug 18 02:28 kirkwood-ns2max.dtb
-rw-r--r-- 1 root root 10179 Aug 18 02:28 kirkwood-ns2lite.dtb
-rw-r--r-- 1 root root 10278 Aug 18 02:28 kirkwood-ns2.dtb
-rw-r--r-- 1 root root 11869 Aug 18 02:28 kirkwood-netgear_stora_ms2000.dtb
-rw-r--r-- 1 root root 13304 Aug 18 02:28 kirkwood-netgear_readynas_nv+_v2.dtb
-rw-r--r-- 1 root root 13124 Aug 18 02:28 kirkwood-netgear_readynas_duo_v2.dtb
-rw-r--r-- 1 root root 12346 Aug 18 02:28 kirkwood-n1t1.dtb
-rw-r--r-- 1 root root 10382 Aug 18 02:28 kirkwood-openrd-client.dtb
-rw-r--r-- 1 root root  9913 Aug 18 02:28 kirkwood-openrd-base.dtb
-rw-r--r-- 1 root root 11721 Aug 18 02:28 kirkwood-openblocks_a7.dtb
-rw-r--r-- 1 root root 11681 Aug 18 02:28 kirkwood-openblocks_a6.dtb
-rw-r--r-- 1 root root 14548 Aug 18 02:28 kirkwood-nsa325.dtb
-rw-r--r-- 1 root root 13292 Aug 18 02:28 kirkwood-nsa320s.dtb
-rw-r--r-- 1 root root 13691 Aug 18 02:28 kirkwood-nsa320.dtb
-rw-r--r-- 1 root root 13296 Aug 18 02:28 kirkwood-nsa310s.dtb
-rw-r--r-- 1 root root 12636 Aug 18 02:28 kirkwood-nsa310b-lmsensor-redusbled.dtb
-rw-r--r-- 1 root root 12458 Aug 18 02:28 kirkwood-nsa310a.dtb
-rw-r--r-- 1 root root 22762 Aug 18 02:28 kirkwood-rs212.dtb
-rw-r--r-- 1 root root 10621 Aug 18 02:28 kirkwood-rd88f6281-z0.dtb
-rw-r--r-- 1 root root 10608 Aug 18 02:28 kirkwood-rd88f6281-a.dtb
-rw-r--r-- 1 root root  9784 Aug 18 02:28 kirkwood-rd88f6192.dtb
-rw-r--r-- 1 root root 11112 Aug 18 02:28 kirkwood-qizhitong_501m_v2.dtb
-rw-r--r-- 1 root root 10284 Aug 18 02:28 kirkwood-pogoplug_v4.dtb
-rw-r--r-- 1 root root 10444 Aug 18 02:28 kirkwood-pogo_e02.dtb
-rw-r--r-- 1 root root 10069 Aug 18 02:28 kirkwood-openrd-ultimate.dtb
-rw-r--r-- 1 root root 10604 Aug 18 02:28 kirkwood-ts419-6281.dtb
-rw-r--r-- 1 root root 11528 Aug 18 02:28 kirkwood-ts219-6282.dtb
-rw-r--r-- 1 root root 10640 Aug 18 02:28 kirkwood-ts219-6281.dtb
-rw-r--r-- 1 root root 12453 Aug 18 02:28 kirkwood-topkick.dtb
-rw-r--r-- 1 root root 11919 Aug 18 02:28 kirkwood-t5325.dtb
-rw-r--r-- 1 root root 10599 Aug 18 02:28 kirkwood-sheevaplug-esata.dtb
-rw-r--r-- 1 root root 10498 Aug 18 02:28 kirkwood-sheevaplug.dtb
-rw-r--r-- 1 root root 22790 Aug 18 02:28 kirkwood-rs411.dtb
-rw-r--r-- 1 root root 21874 Aug 18 02:28 kirkwood-rs409.dtb
-rw-r--r-- 1 root root 11492 Aug 18 02:28 kirkwood-ts419-6282.dtb
drwxr-xr-x 2 root root  4096 Aug 18 02:33 .
drwxr-xr-x 4 root root  4096 Sep 25 09:53 ..

backups:
total 20456
-rw-r--r-- 1 root root 1736932 Sep 24 19:03 System.map-3.14.0-kirkwood-tld-1
-rw-r--r-- 1 root root  123040 Sep 24 19:03 config-3.14.0-kirkwood-tld-1
-rw-r--r-- 1 root root 2461416 Sep 24 19:03 uImage
-rw-r--r-- 1 root root 7738652 Sep 24 19:03 initrd.img-3.14.0-kirkwood-tld-1
-rw-r--r-- 1 root root 6362802 Sep 24 19:03 uInitrd
drwxr-xr-x 2 root root    4096 Sep 24 19:03 .
-rw-r--r-- 1 root root 2461352 Sep 24 19:03 vmlinuz-3.14.0-kirkwood-tld-1
drwxr-xr-x 4 root root    4096 Sep 25 09:53 ..
root@sirguy:/media/craig/rootfs/boot#

Edited 1 time(s). Last edit at 09/25/2017 01:42PM by bodhi.

sysvinit seemed to be causing some grief with systemd (at least I suspect it was the case).

it's possible the systemd install was a partial failure or something, & I *think* I saw it install (again) when I removed sysvinit. (it's also possible I'm confused as I "installed" several different times).

what I was seeing with systemd was the inability to add new services, stop/start services & even give a "status" report.

once I removed sysvinit, systemd started behaving as I expected.

But, OK. Thanks. will keep that in mind for the next one.

Do you think this is the problem with booting the new kernel?

root@sirguy:/media/craig/rootfs/boot# ls -lart *

-rw-r--r-- 1 root root   123040 Apr  2  2014 config-3.14.0-kirkwood-tld-1
-rw-r--r-- 1 root root  1736932 Apr  2  2014 System.map-3.14.0-kirkwood-tld-1
-rw-r--r-- 1 root root  2461352 Apr  2  2014 vmlinuz-3.14.0-kirkwood-tld-1
-rw-r--r-- 1 root root  2461416 Apr  6  2014 uImage.orig
-rw-r--r-- 1 root root  6362802 Apr  6  2014 uInitrd.orig
-rwxr-xr-x 1 root root  3804344 Aug 17 06:53 zImage-4.12.8-kirkwood-tld-1
-rw-r--r-- 1 root root   153512 Aug 18 01:17 config-4.12.8-kirkwood-tld-1
-rw------- 1 root root  2508981 Aug 18 02:01 System.map-4.12.8-kirkwood-tld-1
-rw------- 1 root root  3804344 Aug 18 02:01 vmlinuz-4.12.8-kirkwood-tld-1
-rw-r--r-- 1 root root 18443814 Aug 18 02:07 linux-image-4.12.8-kirkwood-tld-1_1.0_armel.deb
-rw-r--r-- 1 root root  8588292 Aug 18 02:24 linux-headers-4.12.8-kirkwood-tld-1_1.0_armel.deb
-rw-r--r-- 1 root root   146602 Aug 18 05:00 linux-4.12.8-kirkwood-tld-1.patch
-rw-r--r-- 1 root root  7738652 Sep 24 15:31 initrd.img-3.14.0-kirkwood-tld-1
-rw-r--r-- 1 root root  7350568 Sep 24 19:35 initrd.img-4.12.8-kirkwood-tld-1
-rw-r--r-- 1 root root       32 Sep 24 19:53 uEnv.txt
-rw-r--r-- 1 root root  3804408 Sep 24 20:15 uImage.new
-rw-r--r-- 1 root root  7350632 Sep 24 20:18 uInitrd.new
-rw-r--r-- 1 root root  3804408 Sep 25 13:31 uImage
-rw-r--r-- 1 root root  7350632 Sep 25 13:31 uInitrd

Is this uImage has the DTB embedded inside? have you tried to regenerate this?

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

craigcoffman,

> once I removed sysvinit, systemd started behaving
> as I expected.

>
> But, OK. Thanks. will keep that in mind for the
> next one.
>
> Do you think this is the problem with booting the
> new kernel?

It is hard to say, becasue with netconsole, we can't see the kernel booting. At that point, there are many possible reasons why it stuck.

Because netconsole output always stops there, it might have booted, too. Did you check if the box has been asigned a different IP address (if you use dynamic IP)?

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

>Is this uImage has the DTB embedded inside? have you tried to regenerate this?

>-bodhi


uImage.new & uInitrd.new are the ones I generated. I copy them to the "active" filename
on & off.

Inititally I generated the uImage with & without the dtb file. Maybe I misunderstood, but I thought from one of you replies that the uboot version I was running was new enough to NOT need to do that... so I quit generating that one.

I did generate each file (uImage.dtb uImage.nodtb & uInitrd) several times & tried each of the Images at least twice. Only after my "take" on your comment about my uboot version did I quit generating the dtb image.

I take it I need to try that route again?

I give each a static IP by always creating/copying over the /etc/interfaces file. Too much trouble to go hunting it down each time. I would think that if the new kernel booted, it would be constrained by that file as well. Copying the original kernel image & ramdisk back into place always results in it coming back up correctly at the assigned static.

craigcoffman Wrote:
-------------------------------------------------------
> >Is this uImage has the DTB embedded inside? have
> you tried to regenerate this?
>
> >-bodhi
>
>
> uImage.new & uInitrd.new are the ones I generated.
> I copy them to the "active" filename
> on & off.
>
> Inititally I generated the uImage with & without
> the dtb file. Maybe I misunderstood, but I
> thought from one of you replies that the uboot
> version I was running was new enough to NOT need
> to do that... so I quit generating that one.

Ah, that's the problem. Your u-boot is relatively new. But it is not the latest. So the current envs require a embedded DTB in uImage.

> I take it I need to try that route again?

Yes.

After it booted OK, I'll show you how to set the envs to the latest (it will work with your version). With the latest envs, there is no need to append the DTB to uImage.

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

Take a look at these lines from the output of fw_printenv:

load_dtb=ext2load usb 0:1 0x1c00000 /boot/dts/kirkwood-pogoplug_v4.dtb
load_initrd=ext2load usb 0:1 0x1100000 /boot/uInitrd
load_uimage=ext2load usb 0:1 0x800000 /boot/uImage
usb_boot=run load_dtb; run load_uimage; if run load_initrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi

is this not correct for using the image without the embedded dtb?



Edited 1 time(s). Last edit at 09/25/2017 02:00PM by craigcoffman.

bohdi:

generated the uImage again with the dtb file embedded. re-generated the initrd too.
Still no joy.

actually re-downloaded the original tar ball, went thru it all step by step again. Even removed all 4 of the new lines from firmware... consulted another pogoplug mobile here & restored the usb_boot line to:

usb_boot=mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi

can still boot off of the preserved 3.14 image & initrd though.

I wonder if I need to drop back to an earlier kernel?

craigcoffman Wrote:
-------------------------------------------------------
> I wonder if I need to drop back to an earlier
> kernel?

craigcoffman,

Let's slowdown a bit! no need to change any kernel.

I need to show you a way to initialize and boot with a correct set of envs and a pristine rootfs.

This instruction should be in the Wiki but I forgot to do that.

I will be back in a few hours.

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

craigcoffman,

To boot this box with a rootfs that has the original uImage (just like when you first download it), and the original u-boot default envs.

1. Restore the uImage in your rootfs to the original copy. Or regenerate the uImage without the DTB appended to it.
2. Make sure that the rootfs label is rootfs.

3. Load the default envs back to the original state using the procedure in this post (it is for u-boot-2016.05, but should work for your current u-boot version, it is a better default envs set). You can use netconsole to do this.

https://forum.doozan.com/read.php?3,29362,29390#msg-29390

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

I realize I may have given too much information here & flooded you with a mix of relevant & possibly irrelevant data.... but to summarize

I never had any problem dropping back to the old kernel & booting. Not an issue.

BUT nothing I can do can get that new kernel (4.12.8) to boot. generated the Image & Initrd many times now.. always the same.

You may have missed it in my ealier posts, but I also cannot boot that box on a virgin/fresh 4.12.8 rootfs & kernel. followed the instructions & created an new Image with the dtb file embedded. Only other modifcations to that NEW rootfs was again the /etc/interfaces file, & the hostname & hosts file. Same. NetConsole shows both the image & the initrd getting picked up, starting kernel.. etc. What one would expect, but the box never "finishes" booting, is NOT live on the network & the pogoplug's light stays orange. Again, that's on a fresh install.

Anyone else running this kernel on a pogoplug mobile?

Update:

Downloaded the 4.4.0 rootfs kit, installed it a yet another different sd card. Built the uImage with the dtb file, same exact way as before. This booted 1st time.

Something up with the 4-12 kernel & the pogoplug v4 maybe?

craigcoffman,

> Update:
>
> Downloaded the 4.4.0 rootfs kit, installed it a
> yet another different sd card. Built the uImage
> with the dtb file, same exact way as before. This
> booted 1st time.
>

Cool!

> Something up with the 4-12 kernel & the pogoplug
> v4 maybe?

No, I have 4 Pogo V4/Mobile boxes running linux-4.12.8-kirkwood-tld-1 since I've released the kernel and rootfs. for 4.12.x

Your current rootfs is just not in sync with you current envs. That's why I tried to get you back to a good default envs above:
https://forum.doozan.com/read.php?3,37394,37614#msg-37614

This default envs set will boot the pristine Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2, or any of the FDT-kernel rootfs that I've released, such as the 4.4.

BTW, all you've been struggling to get working could have been solved in 10 minutes, if you have serial console connected. Netconsole does not show the kernel boot log, so all we have to go with is the envs, and the kernel files timestamp, size,... to troubleshoot.

But we'll go with what we have. If you want to restart troubleshooting the current rootfs, then post the netconsole bootlog, with printenv listing. And repost the rootfs /boot folder (again asuming it is mounted at /media/sdb1). The file size will tell us if the uImage is the right one. And the timestamp will tell us more about the files set.

ls -larth /media/sdb1/boot

And depending what I see, I will suggest some solution. Please post everything in one post.

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

bohdi:

I posted the output of fw_printenv in the vary 1st message. the firmware did have the 4 new lines related to booting a non-dtb image), but I have since removed them. I have verified the enviroment is the same as on "pristine" boxes.

Am I to understand that the uboot enviroment need to change from what it was even loading an image with the dtb file appended?

Yeah, never setup a serial on these pogos. did so on my dockstar, just went the net-console route on these pogoplugs.

EDIT: also want to add that yes, I have checked the fstab on each attempt at the 4.12 & changed (where needed) to LABEL=rootfs & made sure to label any "new" or dd'd fs where needed.



Edited 1 time(s). Last edit at 09/26/2017 05:20PM by craigcoffman.

craigcoffman,

Quote

But we'll go with what we have. If you want to restart troubleshooting the current rootfs, then post the netconsole bootlog, with printenv listing. And repost the rootfs /boot folder (again asuming it is mounted at /media/sdb1). The file size will tell us if the uImage is the right one. And the timestamp will tell us more about the files set.

It is always a little bit harder to try to help experienced users :) I know that you are trying to understand the problem. But once you see my recommended changes to your envs, or rootfs, I am sure you will recognize where it went wrong.

It is best that you can repost eveything in one post. Currently I need to go back too many posts to try to keep track where you are.

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

Got it. absolutely understand. I'm sure you read a dozen or more threads a day just like this one or close. I'm sure they all run together.

2 pogoplugs & dockstar now all on 4.4.0 which is good. It's simply easier to get them up & running on a fresh rootfs package, add packages & then move/restore data than to worry too much about all the nuances. Maybe good enough for present purposes. though it's sometimes hard to quit putzing with this stuff once you get so deep.

yes, I could see that the problem was *probably* with the rootfs not getting/found mounted after the kernel loads, etc.... BUT, as you say, hard to say much more without a serial, & I definitely was not/am not in the mood for breaking out the soldering iron, though I do have a few spare usb-serial converter lying around.. forget the chip-name. (FTD?) cheap off ebay from china.

the last two pogos are only getting put to work after being in drawers for the last year, so can be really patient on going through everything with those especially.. & now that i'm mostly re-educated on this stuff, will try the 4.12 again.

would volunteer to help write up some better documentation, but looks like a real job.

will follow up & have an article eventually on what i'm doing with these.
In short:

adding a usb display dongle, & using them to display on tvs & spare screens "slides" of stories scrapped via RSS. Text overlayed on (via image-majik tools) the images provided by the RSS provider Also current weather data "slides" generated the same way, with data from Internet scrapes, plus a few images generated by my local weather guys.

The dockstar is serving out it's remaining life providing wireless connectivity to a printer/scanner as well as controlling x10 devices.

Posted a follow up in the debian forum:

https://forum.doozan.com/read.php?2,37694