Welcome! Log In Create A New Profile

Advanced

Difficulties setting up on Pogoplug v4

Posted by nufanDK 
Forum List Message List New Topic
nufanDK
Difficulties setting up on Pogoplug v4
August 07, 2025 08:47AM
Hi all

I have tried to use the guides in here to install Debian on my old Pogoplug v4.
I had previously "hacked" it so I could run archlinux arm on it, and it was booting and running it from the sdcard.
So first I tried to make that work again. Unfortunately, the previous version was discontinued (v5), but I found the image on internet archive, and was able (after a lot of work and complications) to make it boot the archlinux arm once again, and I was able to ssh into the machine.
With that working, I decided it would be worth the effort to upgrade it to run this Debian version.
I started with this guide:
Basic steps to install...

Following that, I went to this page:
https://forum.doozan.com/read.php?2,12096

This led me to this page for updating the uboot:
https://forum.doozan.com/read.php?3,12381

So I ssh'd into the old archlinux on the pogoplug, and followed the instructions for updating the uboot.
Most things were going as expected, with only this part being slightly different:
Quote

As long as mtd0 is defined as 1MB (0x00100000) or greater then it will be OK:
mtd0: 00100000 00020000 "u-boot"

Now on my machine it was:
mtd0: 00200000 00020000 "u-boot"

but since it stated it should just be greater than 0x0010000 I figured it was fine.


After rebooting the device, it tried to boot and ended up stuck on with the yellow/orange light.

I then tried to install Debian.kirkwood on a usb drive, and attach that, but then the device goes into boot loop (green led flashing and then restarting).
I observed that the usb drive also did not light up (it has an led for indicating activity).


I also tried installing the Debian.kirkwood on the sd-card, but same issues.
I tried with both ext4 filesystem and ext3.

I admit, I still have not connected the serial, and I am not able to do that until next week, but I wanted to document my process here, and ask if anyone might have any idea as to what might have gone wrong, or how I might address it?
Any links to appropriate threads are of course also valued.
I have been jumping a lot around between various posts in this forum, and while most have pieces of valuable information, I am starting to lose track of the order, and become a lot unsure on how it might be properly applied.

Thank you all for any and all help regarding this.
Reply Quote
bodhi
Re: Difficulties setting up on Pogoplug v4
August 07, 2025 11:34AM
nufanDK,

> So I ssh'd into the old archlinux on the pogoplug,
> and followed the instructions for updating the
> uboot.
> Most things were going as expected, with only this
> part being slightly different:
>
Quote

As long as mtd0 is defined as 1MB
> (0x00100000) or greater then it will be OK:
> mtd0: 00100000 00020000 "u-boot"
>
> Now on my machine it was:
> mtd0: 00200000 00020000 "u-boot"
>
> but since it stated it should just be greater than
> 0x0010000 I figured it was fine.
>

Yes. It should be OK.

> After rebooting the device, it tried to boot and
> ended up stuck on with the yellow/orange light.

You did not mention about updating u-boot envs. New u-boot installation requires flashing both the u-boot image and the new default envs image.

> I then tried to install Debian.kirkwood on a usb
> drive, and attach that, but then the device goes
> into boot loop (green led flashing and then
> restarting).

This is an indicator that the u-boot envs are probably not correct. Or the USB rootfs was not prepared correctly.

> I admit, I still have not connected the serial,
> and I am not able to do that until next week

The best next step is to connect serial console to observe the booting activities.

OTOH, if you have kept the log of everything you did during installation, most likely I could tell where thing went wrong by reviewing the log.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
nufanDK
Re: Difficulties setting up on Pogoplug v4
August 11, 2025 05:50AM
Thank you for the quick reply bodhi!

Of course I did not save the log of the steps I took, but looking through the guide, I believe you may be right that I forgot step 8 (or did not perform it properly).

Yesterday night I then tried to connect through serial, using a USB to UART TTL cable. (POWER, RX, TX and GROUND - I only used RX, TX and GROUND).
However, I was not able to connect.
My experience in soldering and working with PCB's are somewhat limited, so I was wondering if you could assist me with a guide for connecting serial to the pogoplug, to ensure I am doing it properly?

What I did do, was follow this guide to determine the proper places for RX, TX and GROUND. I also used chatGPT which suggested that TX of cable should go to RX of pogoplug, and RX from cable to TX for pogoplug.
I first tried simply holding and taping the wires onto the board at the appropriate places, which did not work.
Then I tried soldering. But my soldering iron seemed a bit to big, and now I may have damaged/ruined the points on the PCB board for the serial.
Basically, I first thought that there was solder on the points for the serial console on the PCB, but it did not melt, so I am guessing it was more like a place for the cables to be soldered to.
I then tried to solder some cables to those points, but it became messy, and they got soldered together. And now the PCB seems a bit burned at that spot. But it does turn on as it should.

Anyway, any assistance on the part of setting up the connection to the serial console is much appreciated.
Reply Quote
eno789
Re: Difficulties setting up on Pogoplug v4
August 11, 2025 10:58AM
I'm also not good at soldering at all. So I often use temporary workaround when there's no serial header.

* Sometimes I use "Goupchn" hook clip
* Sometimes use bare header connector + the wire so they jam into the holes to get good connection.
Reply Quote
bluzfanmr1
Re: Difficulties setting up on Pogoplug v4
August 11, 2025 12:42PM
Here is how I get a serial connection to my Pogoplug V4:

Pogoplug V4 Shirt Pin Serial Connection
Reply Quote
bodhi
Re: Difficulties setting up on Pogoplug v4
August 11, 2025 01:10PM
The Pogo V4 serial header is a row of 4 soft solder buttons. For a temporary serial connection: Use shirt pins (the pins that you usually find in a shirt box) and test clips like this.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
nufanDK
Re: Difficulties setting up on Pogoplug v4
August 12, 2025 02:32PM
Thank you all for all the good advice.
I bought some pins today and was actually planning to go to a local repair cafe next week to have them help me get it soldering. My electronics store suggested that my soldering iron was not hot enough, which different Reddit posts indicate as well (the solder should have been melting with 1 second, and I was holding my iron to it for 5 or more seconds).
However, luckily I am a curious and not too patient guy, so going home with the pins today, I ended up trying to just hold them on the serial (see image). It is highly unstable but it actually works!
So I was able to connect and abort the boot process and I am now in the console!
Going through the documentation again and will post my findings.
Reply Quote
Attachments:
open | download - Screenshot_2025-08-12_213112.jpeg (24.3 KB)
nufanDK
Re: Difficulties setting up on Pogoplug v4
August 12, 2025 02:50PM
Okay, so I got this from the boot:

Quote



U-Boot 2023.04-tld-1 (Jun 11 2023 - 16:24:44 -0700)
Pogoplug V4

SoC: Kirkwood 88F6192_A1
Model: Cloud Engines PogoPlug Series 4
DRAM: 128 MiB
Core: 20 devices, 16 uclasses, devicetree: separate
NAND: 128 MiB
MMC: mvsdio@90000: 0
Loading Environment from NAND... OK
Resetting console stdin/stdout/stderr to serial...
In: serial
Out: serial
Err: serial
pcie0.0: Link up
Net: eth0: ethernet-controller@72000
ethernet-controller@72000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Using ethernet-controller@72000 device

ARP Retry count exceeded; starting again
ping failed; host 192.168.86.87 is not alive
ethernet-controller@72000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
Using ethernet-controller@72000 device

I was able to interrupt this with Ctrl+C a couple of times and ended up at the console input.

Quote

Pogo_V4>

doing "printenv" gives me this:

Quote

Pogo_V4> printenv
baudrate=115200
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; reset
bootcmd_exec=if run load_uimage; then; 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; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
console=ttyS0,115200
device=0:1
devices=usb sata
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtbÃ
ethact=ethernet-controller@72000
ethaddr=00:25:31:04:ee:5b
fdtcontroladdr=7b51650
if_netconsole=ping $serverip
ipaddr=192.168.86.146
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x2100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
nc_ready=0
preboot=run preboot_nc
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb reset; sleep 1; usb reset"; setenv scan_sata "sata init"; 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
serverip=192.168.86.87
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 serial,nc; setenv stdout serial,nc; setenv stderr serial,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=echo Initializing devices...; setenv init_usb "usb reset; sleep 1; usb reset"; setenv init_sata sata init; 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 $disks; do if test $uenv_loaded -eq 0; then setenv device_type $devtype; setenv disk_number $disknum; run uenv_read; fi; done; done;
uenv_read=echo Loading envs from $device_type $disk_number...; if load $device_type $disk_number:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; echo ... envs loaded; fi
ver=U-Boot 2023.04-tld-1 (Jun 11 2023 - 16:24:44 -0700)\
Pogoplug V4

Environment size: 3015/131068 bytes
Pogo_V4>
baudrate=115200
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; reset
bootcmd_exec=if run load_uimage; then; 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; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
console=ttyS0,115200
device=0:1
devices=usb sata
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtbÃ
ethact=ethernet-controller@72000
ethaddr=00:25:31:04:ee:5b
fdtcontroladdr=7b51650
if_netconsole=ping $serverip
ipaddr=192.168.86.146
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x2100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
nc_ready=0
preboot=run preboot_nc
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb reset; sleep 1; usb reset"; setenv scan_sata "sata init"; 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
serverip=192.168.86.87
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 serial,nc; setenv stdout serial,nc; setenv stderr serial,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=echo Initializing devices...; setenv init_usb "usb reset; sleep 1; usb reset"; setenv init_sata sata init; 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 $disks; do if test $uenv_loaded -eq 0; then setenv device_type $devtype; setenv disk_number $disknum; run uenv_read; fi; done; done;
uenv_read=echo Loading envs from $device_type $disk_number...; if load $device_type $disk_number:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; echo ... envs loaded; fi
ver=U-Boot 2023.04-tld-1 (Jun 11 2023 - 16:24:44 -0700)\
Pogoplug V4

Environment size: 3015/131068 bytes
Pogo_V4>

I have not looked them over in more detail yet, but just to ensure I am following the right instructions for setting the correct environment variables, is this link the correct instructions:
2023.04 U-Boot Kirkwood - Pogo V4

Or should I use this link:
2017.07- 2024.10 U-Boot Kirkwood
And then follow the uboot instructions there in the top post (The part describing "Updated 06 Dec 2017")?
Reply Quote
bodhi
Re: Difficulties setting up on Pogoplug v4
August 13, 2025 12:10AM
nufanDK,

> U-Boot 2023.04-tld-1 (Jun 11 2023 - 16:24:44
> -0700)
> Pogoplug V4
>
> SoC: Kirkwood 88F6192_A1
> Model: Cloud Engines PogoPlug Series 4
> DRAM: 128 MiB
> Core: 20 devices, 16 uclasses, devicetree:
> separate
> NAND: 128 MiB
> MMC: mvsdio@90000: 0
> Loading Environment from NAND... OK
> Resetting console stdin/stdout/stderr to
> serial...
> In: serial
> Out: serial
> Err: serial
> pcie0.0: Link up
> Net: eth0: ethernet-controller@72000
> ethernet-controller@72000 Waiting for PHY auto
> negotiation to complete......... TIMEOUT !
> Using ethernet-controller@72000 device
>
> ARP Retry count exceeded; starting again
> ping failed; host 192.168.86.87 is not alive
> ethernet-controller@72000 Waiting for PHY auto
> negotiation to complete......... TIMEOUT !
> Using ethernet-controller@72000 device
> [/quote]

Looks good!

Your current installed u-boot 2023.04-tld-1 for Pogo V4 is fine.

https://forum.doozan.com/read.php?3,135041

Quote

In addition to the capabilties provided by u-boot 2017.07-tld-1 for Pogo V4 , this 2023.04-tld-1 Pogo V4 u-boot has the following new capabilties:

- Supports for USB 3.0. You can now boot with the rootfs in either one of the 2 USB 3.0 ports in the back.
- Netconsole enhancement. (See Note C.1.2).
- Distro boot (see Note C.2 after the Installation Steps for usage).

===

When you have serial console, it's best not to enable netconsole. 

preboot=run preboot_nc

To disable netconsole, at u-boot prompt 
setenv preboot
saveenv
And then connect the Ethernet cable.
Boot into USB rootfs 
boot

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
nufanDK
Re: Difficulties setting up on Pogoplug v4
August 15, 2025 02:43AM
Amazing! For making it boot from the usb, it was just the netconsole that was giving issues, because it could not resolve the server.
Thank you bodhi!

I believe I am very close now, but I am still getting some errors.
It proceeds to boot from the usb, but it gives an error that I was not able to resolve:

Quote

Initializing devices...
resetting USB...
Bus ehci@50000: USB EHCI 1.00
Bus xhci_pci: Register 400081f NbrPorts 4
Starting the controller
USB XHCI 1.00
scanning bus ehci@50000 for devices... 1 USB Device(s) found
scanning bus xhci_pci for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
resetting USB...
Bus ehci@50000: USB EHCI 1.00
Bus xhci_pci: Register 400081f NbrPorts 4
Starting the controller
USB XHCI 1.00
scanning bus ehci@50000 for devices... 1 USB Device(s) found
scanning bus xhci_pci for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
Loading envs from usb 0...
Failed to load '/boot/uEnv.txt'
Loading envs from usb 1...
** Bad device specification usb 1 **
Couldn't find partition usb 1:1
Can't set block device
Loading envs from usb 2...
** Bad device specification usb 2 **
Couldn't find partition usb 2:1
Can't set block device
Loading envs from usb 3...
** Bad device specification usb 3 **
Couldn't find partition usb 3:1
Can't set block device
Loading envs from sata 0...
** Bad device specification sata 0 **
Couldn't find partition sata 0:1
Can't set block device
Loading envs from sata 1...
** Bad device specification sata 1 **
Couldn't find partition sata 1:1
Can't set block device
Loading envs from sata 2...
** Bad device specification sata 2 **
Couldn't find partition sata 2:1
Can't set block device
Loading envs from sata 3...
** Bad device specification sata 3 **
Couldn't find partition sata 3:1
Can't set block device
running scan_disk ...
Scan device usb
resetting USB...
Bus ehci@50000: USB EHCI 1.00
Bus xhci_pci: Register 400081f NbrPorts 4
Starting the controller
USB XHCI 1.00
scanning bus ehci@50000 for devices... 1 USB Device(s) found
scanning bus xhci_pci for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
resetting USB...
Bus ehci@50000: USB EHCI 1.00
Bus xhci_pci: Register 400081f NbrPorts 4
Starting the controller
USB XHCI 1.00
scanning bus ehci@50000 for devices... 1 USB Device(s) found
scanning bus xhci_pci for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
device usb 0:1
1 bytes read in 8 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
6223944 bytes read in 310 ms (19.1 MiB/s)
loading uInitrd ...
5791271 bytes read in 288 ms (19.2 MiB/s)
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtbà ...
Failed to load '/boot/dts/kirkwood-pogoplug_v4.dtbÃ'
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-6.5.7-kirkwood-tld-1
Created: 2023-10-31 22:53:22 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 6223880 Bytes = 5.9 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02100000 ...
Image Name: initramfs-6.5.7-kirkwood-tld-1
Created: 2023-10-31 22:53:55 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 5791207 Bytes = 5.5 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Working FDT set to 0


Starting kernel ...

Loading Kernel Image
Loading Ramdisk to 075c7000, end 07b4cde7 ... OK

Starting kernel ...


Error: invalid dtb and unrecognized/unsupported machine ID
r1=0x00000000, r2=0x00000100
r2[]=05 00 00 00 01 00 41 54 00 00 00 00 00 00 00 00
Available machine support:

ID (hex).NAME
ffffffff.Generic DT based system
ffffffff.Marvell Kirkwood (Flattened Device Tree)

Please check your kernel config and/or bootloader.

I just tried a fresh install to a newly formatted usb following the instructions from 01 Nov here (I skipped step 4 as I have newer uBoot - right?):

https://forum.doozan.com/read.php?2,12096
Reply Quote
bodhi
Re: Difficulties setting up on Pogoplug v4
August 15, 2025 07:26AM
nufanDK,

> I just tried a fresh install to a newly formatted
> usb following the instructions from 01 Nov here (I
> skipped step 4 as I have newer uBoot - right?):
>
> https://forum.doozan.com/read.php?2,12096

Righ! Skip step 4. And make sure you format it as Ext3, for simplicity. If using Ext4, you'll need to "finalize" the file system as mentioned in the rootfs instruction.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
nufanDK
Re: Difficulties setting up on Pogoplug v4
August 15, 2025 02:49PM
I feel it is SOOO close.

So it went through the process again. On another linux installation I formatted the USB stick with ext3 using fdisk and mkfs.ext3.
I created a MBR (DOS) partitiontable with a single primary partition using fdisk, and I also set the flag for making the partition bootable (not sure if that is really necessary).

Then I formatted it using:
mkfs.ext3

and then I labelled that partition "rootfs" using: tune2fs -L "rootfs" /dev/sdb1

Then with the newly formatted usb stick, I mounted it, and I copied the tarball: Debian-5.6.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2

I then even renamed it as suggested to 6.5.7 instead, and extracted it using: tar xjf Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2

Everything extracts fine it seems, so I go to: /<USB stick mountpoint>/etc/ and examine fstab. This looks like in the instructions, so I close it again, and take my newly created usb stick to my pogoplug v4, and I try to run it.

The LED turns orange/yellow, and gives this output:

Quote

.@
U-Boot 2023.04-tld-1 (Jun 11 2023 - 16:24:44 -0700)
Pogoplug V4

SoC: Kirkwood 88F6192_A1
Model: Cloud Engines PogoPlug Series 4
DRAM: 128 MiB
Core: 20 devices, 16 uclasses, devicetree: separate
NAND: 128 MiB
MMC: mvsdio@90000: 0
Loading Environment from NAND... OK
Resetting console stdin/stdout/stderr to serial...
In: serial
Out: serial
Err: serial
pcie0.0: Link up
Net: eth0: ethernet-controller@72000
Hit any key to stop autoboot: 10 ... 9 ... 8 ... 7 ... 6 ... 5 ... 4 ... 3 ... 2 ... 1 ... 0
Initializing devices...
resetting USB...
Bus ehci@50000: USB EHCI 1.00
Bus xhci_pci: Register 400081f NbrPorts 4
Starting the controller
USB XHCI 1.00
scanning bus ehci@50000 for devices... 1 USB Device(s) found
scanning bus xhci_pci for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
resetting USB...
Bus ehci@50000: USB EHCI 1.00
Bus xhci_pci: Register 400081f NbrPorts 4
Starting the controller
USB XHCI 1.00
scanning bus ehci@50000 for devices... 1 USB Device(s) found
scanning bus xhci_pci for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
Loading envs from usb 0...
Failed to load '/boot/uEnv.txt'
Loading envs from usb 1...
** Bad device specification usb 1 **
Couldn't find partition usb 1:1
Can't set block device
Loading envs from usb 2...
** Bad device specification usb 2 **
Couldn't find partition usb 2:1
Can't set block device
Loading envs from usb 3...
** Bad device specification usb 3 **
Couldn't find partition usb 3:1
Can't set block device
Loading envs from sata 0...
** Bad device specification sata 0 **
Couldn't find partition sata 0:1
Can't set block device
Loading envs from sata 1...
** Bad device specification sata 1 **
Couldn't find partition sata 1:1
Can't set block device
Loading envs from sata 2...
** Bad device specification sata 2 **
Couldn't find partition sata 2:1
Can't set block device
Loading envs from sata 3...
** Bad device specification sata 3 **
Couldn't find partition sata 3:1
Can't set block device
running scan_disk ...
Scan device usb
resetting USB...
Bus ehci@50000: USB EHCI 1.00
Bus xhci_pci: Register 400081f NbrPorts 4
Starting the controller
USB XHCI 1.00
scanning bus ehci@50000 for devices... 1 USB Device(s) found
scanning bus xhci_pci for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
resetting USB...
Bus ehci@50000: USB EHCI 1.00
Bus xhci_pci: Register 400081f NbrPorts 4
Starting the controller
USB XHCI 1.00
scanning bus ehci@50000 for devices... 1 USB Device(s) found
scanning bus xhci_pci for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
device usb 0:1
1 bytes read in 10 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
6223944 bytes read in 315 ms (18.8 MiB/s)
loading uInitrd ...
5791271 bytes read in 294 ms (18.8 MiB/s)
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtbà ...
Failed to load '/boot/dts/kirkwood-pogoplug_v4.dtbÃ'
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-6.5.7-kirkwood-tld-1
Created: 2023-10-31 22:53:22 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 6223880 Bytes = 5.9 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02100000 ...
Image Name: initramfs-6.5.7-kirkwood-tld-1
Created: 2023-10-31 22:53:55 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 5791207 Bytes = 5.5 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Working FDT set to 0


Starting kernel ...

Loading Kernel Image
Loading Ramdisk to 075c7000, end 07b4cde7 ... OK

Starting kernel ...


Error: invalid dtb and unrecognized/unsupported machine ID
r1=0x00000000, r2=0x00000100
r2[]=05 00 00 00 01 00 41 54 00 00 00 00 00 00 00 00
Available machine support:

ID (hex).NAME
ffffffff.Generic DT based system
ffffffff.Marvell Kirkwood (Flattened Device Tree)

Please check your kernel config and/or bootloader.


Can anyone spot what I might be doing wrong?



Edited 1 time(s). Last edit at 08/15/2025 03:03PM by nufanDK.
Reply Quote
bodhi
Re: Difficulties setting up on Pogoplug v4
August 15, 2025 03:57PM
nufanDK,

Looks like there are some garbage characters in the env:

Quote

loading DTB /boot/dts/kirkwood-pogoplug_v4.dtbà ...
Failed to load '/boot/dts/kirkwood-pogoplug_v4.dtbÃ'

Try:

Interrupt u-boot count down at 
Hit any key to stop autoboot:
And reset the env to correct it: 
setenv dtb_file '/boot/dts/kirkwood-pogoplug_v4.dtb'

and then 
boot

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
nufanDK
Re: Difficulties setting up on Pogoplug v4
August 15, 2025 06:34PM
IT'S ALIVE!!!!

Thank you so much bodhi!
It was those garbage characters. I saw them at one point, but thought it was just due to my serial link being finicky, and then displaying some weird characters.
But it loads now from the USB.
So next step is transferring it to the SD-card, but that should not be a problem now that the bootloader works!

Thank you again. And thank you to all in here for the great work and quick responses. I love that I can still use these small devices, and that it is not just for the trash.
Reply Quote
nufanDK
Re: Difficulties setting up on Pogoplug v4
August 21, 2025 05:12AM
A small update from my part and another question.

I have it all booted up through the usb now, and I can ssh into the machine.
I would like to move the linux installation to a sd-card instead, so following the instructions on note 8 (for the 01 Nov instructions)
But when I try to install the updated kernel in step 3 using dpkg, I get this error: 


root@debian:/boot# dpkg -i linux-image-6.6.3-kirkwood-tld-1_1_armel.deb
Selecting previously unselected package linux-image-6.6.3-kirkwood-tld-1.
(Reading database ... 17532 files and directories currently installed.)
Preparing to unpack linux-image-6.6.3-kirkwood-tld-1_1_armel.deb ...
Unpacking linux-image-6.6.3-kirkwood-tld-1 (1) ...
dpkg-deb: error: <decompress> subprocess was killed by signal (Killed)
dpkg: error processing archive linux-image-6.6.3-kirkwood-tld-1_1_armel.deb (--install):
 cannot copy extracted data for './lib/modules/6.6.3-kirkwood-tld-1/kernel/crypto/rmd160.ko' to '/lib/modules/6.6.3-kirkwood-tld-1/kernel/crypto/rmd160.ko.dpkg-new': unexpected end of file or stream
Errors were encountered while processing:
 linux-image-6.6.3-kirkwood-tld-1_1_armel.deb

So before I screw things up, I wanted to check if anyone have any help to offer?
Should I upgrade to an even newer version an skip 6.6.3?

Thank you all in advance.
Reply Quote
bodhi
Re: Difficulties setting up on Pogoplug v4
August 21, 2025 12:43PM
nufanDK,

> A small update from my part and another question.
>
> I have it all booted up through the usb now, and I
> can ssh into the machine.
> I would like to move the linux installation to a
> sd-card instead, so following the instructions on
> note 8 (for the 01 Nov instructions)
> But when I try to install the updated kernel in
> step 3 using dpkg, I get this error:
>

> So before I screw things up, I wanted to check if
> anyone have any help to offer?
> Should I upgrade to an even newer version an skip
> 6.6.3?
>

You could upgrade to the latest kernel version.

Before doing any update/upgrade or running dpkg, you need to enable swap (especially that this box's RAM is too small).

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

Updated 01 Nov 2023:

Basic Debian bookworm Kirkwood rootfs for most Kirwood plugs:

....

Note 1 (Strongly Recommended):

To keep the rootfs extremely basic and small, there is no swap space set up for it. The first thing you should do after the 1st boot is to set up a swap file to make the system run better. In fact, system upgrades oftently fail to run without swap. Please see here for instruction how to do that.

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



Edited 1 time(s). Last edit at 08/21/2025 01:09PM by bodhi.
Reply Quote
nufanDK
Re: Difficulties setting up on Pogoplug v4
August 21, 2025 02:41PM
Okay great!

I did enable swap. I used the automatic swap (the dphys package).
So I will just upgrade to the newest kernel instead then.
Reply Quote
nufanDK
Re: Difficulties setting up on Pogoplug v4
August 27, 2025 03:09AM
I am still having some difficulties with this.
It runs fine off the USB. I have upgraded to the latest kernel, and when I ssh into the pogoplug using the usb, it shows this on startup: 

Linux debian 6.15.2-kirkwood-tld-1 #1 PREEMPT Tue Jun 17 17:38:35 PDT 2025 armv5tel

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Dec 31 16:02:12 1969 from 192.168.1.20
debian
192.168.1.25
Pogoplug v4
Linux version 6.15.2-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 PREEMPT Tue Jun 17 17:38:35 PDT 2025
Debian 12.2
Wed Dec 31 16:01:54 PST 1969 up 1 minute

So I took it to another linux box and used the following command to clone the usb to an sd-card:
dd if=/dev/sdc of=/dev/sdb bs=1M status=progress

it seemed to clone fine, but when I insert it into the pogoplug and try to boot from the sd-card, I just get this from the serial console: 

U-Boot 2023.04-tld-1 (Jun 11 2023 - 16:24:44 -0700)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
Model: Cloud Engines PogoPlug Series 4
DRAM:  128 MiB
Core:  20 devices, 16 uclasses, devicetree: separate
NAND:  128 MiB
MMC:   mvsdio@90000: 0
Loading Environment from NAND... OK
Resetting console stdin/stdout/stderr to serial...
In:    serial
Out:   serial
Err:   serial
pcie0.0: Link up
Net:   eth0: ethernet-controller@72000
Hit any key to stop autoboot: 10 ... 9 ... 8 ... 7 ... 6 ... 5 ... 4 ... 3 ... 2 ... 1 ... 0 
Initializing devices...
resetting USB...
Bus ehci@50000: USB EHCI 1.00
Bus xhci_pci: Register 400081f NbrPorts 4
Starting the controller
USB XHCI 1.00
scanning bus ehci@50000 for devices... 1 USB Device(s) found
scanning bus xhci_pci for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
resetting USB...
Bus ehci@50000: USB EHCI 1.00
Bus xhci_pci: Register 400081f NbrPorts 4
Starting the controller
USB XHCI 1.00
scanning bus ehci@50000 for devices... 1 USB Device(s) found
scanning bus xhci_pci for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Loading envs from usb 0...
** Bad device specification usb 0 **
Couldn't find partition usb 0:1
Can't set block device
Loading envs from usb 1...
** Bad device specification usb 1 **
Couldn't find partition usb 1:1
Can't set block device
Loading envs from usb 2...
** Bad device specification usb 2 **
Couldn't find partition usb 2:1
Can't set block device
Loading envs from usb 3...
** Bad device specification usb 3 **
Couldn't find partition usb 3:1
Can't set block device
Loading envs from sata 0...
** Bad device specification sata 0 **
Couldn't find partition sata 0:1
Can't set block device
Loading envs from sata 1...
** Bad device specification sata 1 **
Couldn't find partition sata 1:1
Can't set block device
Loading envs from sata 2...
** Bad device specification sata 2 **
Couldn't find partition sata 2:1
Can't set block device
Loading envs from sata 3...
** Bad device specification sata 3 **
Couldn't find partition sata 3:1
Can't set block device
running scan_disk ...
Scan device usb
resetting USB...
Bus ehci@50000: USB EHCI 1.00
Bus xhci_pci: Register 400081f NbrPorts 4
Starting the controller
USB XHCI 1.00
scanning bus ehci@50000 for devices... 1 USB Device(s) found
scanning bus xhci_pci for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
resetting USB...
Bus ehci@50000: USB EHCI 1.00
Bus xhci_pci: Register 400081f NbrPorts 4
Starting the controller
USB XHCI 1.00
scanning bus ehci@50000 for devices... 1 USB Device(s) found
scanning bus xhci_pci for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
device usb 0:1
** Bad device specification usb 0 **
Couldn't find partition usb 0:1
Can't set block device
device usb 1:1
** Bad device specification usb 1 **
Couldn't find partition usb 1:1
Can't set block device
device usb 2:1
** Bad device specification usb 2 **
Couldn't find partition usb 2:1
Can't set block device
device usb 3:1
** Bad device specification usb 3 **
Couldn't find partition usb 3:1
Can't set block device
Scan device sata
device sata 0:1
** Bad device specification sata 0 **
Couldn't find partition sata 0:1
Can't set block device
device sata 1:1
** Bad device specification sata 1 **
Couldn't find partition sata 1:1
Can't set block device
device sata 2:1
** Bad device specification sata 2 **
Couldn't find partition sata 2:1
Can't set block device
device sata 3:1
** Bad device specification sata 3 **
Couldn't find partition sata 3:1
Can't set block device
loading uImage ...
** Bad device specification usb 0 **
Couldn't find partition usb 0:1
Can't set block device
resetting ...
ÿ
Reply Quote
bodhi
Re: Difficulties setting up on Pogoplug v4
August 27, 2025 12:38PM
nufanDK,

> So I took it to another linux box and used the
> following command to clone the usb to an sd-card:
> dd if=/dev/sdc of=/dev/sdb bs=1M status=progress

Don't use dd to clone USB to SD. Use the procedure in the Wiki:

How to clone a rootfs from one Kirkwood box to another: Step 1
https://forum.doozan.com/read.php?2,12096,24034#msg-24034

> it seemed to clone fine, but when I insert it into
> the pogoplug and try to boot from the sd-card, I
> just get this from the serial console:

As usual, a failed boot log should include printenv so that it will be apparent right away what problem might be.

However, looking at the log, I see no mmc activities. This must have been when you tested USB booting and we changed the devices env to make it less noisy. Try this.

With the SD rootfs in the slot. Power up, interrupt serial console, and 
printenv
setenv devices 'mmc usb sata'
boot

Note that the devices env lists the order of scanning. So you can rearrange it to make the boot go faster. Or remove device that you don't want u-boot to consider.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
nufanDK
Re: Difficulties setting up on Pogoplug v4
August 27, 2025 03:40PM
Thanks bodhi!

Quote
bodhi
As usual, a failed boot log should include printenv so that it will be apparent right away what problem might be.

My apologies. Dearly noted for next time :-)

And thank you for explaining that I can rearrange the boot order. I'll look into that first thing in the morning.

Thank you again.
Reply Quote
nufanDK
Re: Difficulties setting up on Pogoplug v4
August 28, 2025 02:43AM
And just like that, it all worked out perfectly! :-D

The first time I forgot to do 

saveenv


so it did not save the change to the boot order, which is obvious, doh :-D
But after doing that it all works.

Thank you for all the help!



Edited 1 time(s). Last edit at 08/28/2025 02:43AM by nufanDK.
Reply Quote
bodhi
Re: Difficulties setting up on Pogoplug v4
August 28, 2025 12:14PM
> But after doing that it all works.

Cool!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
Newer Topic Older Topic
Author:

Your Email:


Subject:
Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: