I dug up my Pogoplug Pro and tried to install Debian on it this weekend. I followed the steps from this thread https://forum.doozan.com/read.php?2,16044 using the Debian-4.14.180-oxnas-tld-1-rootfs-bodhi.tar.bz2 tarball. Something must have gone wrong with my uBoot setup or the Debian usb boot disk setup because my pogoplug won't boot. It stopped with a kernel panic with the following error:

[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Attached it the serial output during the boot process. Any help will be greatly appreciated. Thanks in advance.

scavenger,

You should not do Step 4 when booting with new u-boot,

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


4. Create uImage with embedded DTB for booting with stock u-boot. Skip this step if you have installed the latest released uboot for OXNAS, or are installing this u-boot at the same time.

- If you have the Pogo V3 Classic (without Wifi), then the DTB name below should be ox820-pogoplug-classic.dtb (see below for the list of OX820 DTBs).

cd /media/sdb1/boot
cp -a uImage uImage.orig
cp -a zImage-4.14.180-oxnas-tld-1 zImage.fdt
cat dts/ox820-pogoplug-pro.dtb >> zImage.fdt
mkimage -A arm -O linux -C none -T kernel -a 0x60008000 -e 0x60008000 -n 'Linux-4.14.180-oxnas-tld-1' -d zImage.fdt uImage
sync

So reverse Step 4:

cd /media/sdb1/boot
cp -a uImage.orig uImage
sync

And bring the USB rootfs back to the Pogo and boot.

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



Edited 1 time(s). Last edit at 10/23/2022 09:38PM by bodhi.

bodhi Wrote:
-------------------------------------------------------

> So reverse Step 4:
>
>

> cd /media/sdb1/boot
> cp -a uImage.orig uImage
> sync
>

>
> And bring the USB rootfs back to the Pogo and
> boot.

Thanks bodhi. I reverted back to the original uImage and my pogoplug pro booted debian successfully. I went ahead and did the update and upgrade. During the update, I got the following warnings:

Reading package lists... Done
N: Skipping acquire of configured file 'main/binary-armel/Packages' as repository 'http://security.debian.org buster/updates InRelease' doesn't support architecture 'armel'
N: Skipping acquire of configured file 'contrib/binary-armel/Packages' as repository 'http://security.debian.org buster/updates InRelease' doesn't support architecture 'armel'
N: Skipping acquire of configured file 'non-free/binary-armel/Packages' as repository 'http://security.debian.org buster/updates InRelease' doesn't support architecture 'armel'
E: Could not open file /var/lib/apt/lists/http.debian.net_debian_dists_buster-updates_main_source_Sources.diff_Index - open (2: No such file or directory)
E: Could not open file /var/lib/apt/lists/http.debian.net_debian_dists_buster-updates_main_binary-armel_Packages.diff_Index - open (2: No such file or directory)
E: Could not open file /var/lib/apt/lists/http.debian.net_debian_dists_buster-updates_main_i18n_Translation-en.diff_Index - open (2: No such file or directory)

which didn't seem to have caused any harm, so I ignored them. Other than that, everything went smoothly.

What's the difference between the newest version of the kernel (5.4.210) vs the one that I'm using (4.14.180)? Did the kernel upgrade to the newest version after I ran "apt-get upgrade"?

Thanks again!

scavenger ,

> What's the difference between the newest version
> of the kernel (5.4.210) vs the one that I'm using
> (4.14.180)?

> Did the kernel upgrade to the newest
> version after I ran "apt-get upgrade"?
>

No, "apt-get upgrade" is for Debian packages in the rootfs (i.e. userland).

When you want to upgrade the kernel, follow the instruction in the release thread.

Quote

Updated 26 Aug 2022:

Kernel linux-5.4.210-oxnas-tld-1 package was uploaded.
....

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