Can it be done?

Does it work?

Of course it can be done. And it'll probably work. But I wouldn't attempt it without a backup. So make a cop of your Squeeze boot stick. Boot the copy. Edit /etc/apt/sources.list to reference wheezy instead of stable or squeeze.

apt-get update
apt-get dist-upgrade

Cross your fingers and wait.

When it's done, you'll need to generate new uImage and uInitrd files.

apt-get install uboot-mkimage
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-<version> -d /boot/vmlinuz-<version> /boot/uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n Initrd-<version> -d /boot/initrd.img-<version> /boot/uInitrd

Reboot and cross your fingers again. I'd suggest a serial console to watch the boot sequence.
And if it doesn't boot, you still have your Squeeze boot stick.

I'm finding it hard to believe, but it did actually seem to work w/o a single hiccup ... I just updated my sources.list from squeeze to wheezy, then ...

apt-get update
apt-get dist-upgrade

and away it went ... it even handed the uboot initrd commands for me. I did nothing except accepting two device-id-renames, and then reboot and

root@debian:~# uname -a
Linux debian 3.0.0-1-kirkwood #1 Sun Aug 28 14:30:35 UTC 2011 armv5tel GNU/Linux
root@debian:~# cat /etc/debian_version 
wheezy/sid

This was done on my newly acquired eBay-won $31 DockStar ... YMMV ... Still, I guess we have to remember that for now, Wheezy=Testing=PossibleBreakage ...

=====================================================

• davy's Github Repo's rescue-dg

Edited 3 time(s). Last edit at 10/15/2011 08:57PM by davygravy.

Nice. I actually have a system that I've dist-upgraded from Etch to Lenny to Squeeze in turn. (Yes it's still running.) The upgrade to Squeeze was not pretty. I had to correct a lot things by manually removing conflicting packages.

You can run a mixed environment based off Squeeze but intentionally pulling some packages from Wheezy. Put both squeeze and wheezy in /etc/apt/sources.list. Then set up /etc/apt/preferences to give squeeze a higher priority (say 700) than wheezy (say 600). Everything defaults to a priority of 500.

You then can force the installation of some packages from wheezy using apt-get -t wheezy install package.

This gets a bit more complicated if using other repositories. The command "apt-cache policy" will show you the priorities for every repository. You may have to tweak them.

Success !

I've followed the simple guidelines of replacing squeeze with wheezy within /etc/apt/sources.list and then
apt-get update && apt-get dist-upgrade

Upgrade went smoothly (besides 2 UUID questions mentioned on this thread to which i've answered "Yes").

I'm now running Kernel 3.0.0.1 under Debian Wheezy (woo hoo!)

On a Dockstar I did "apt-get update", "apt-get upgrade", the change to wheezy in sources.list, "apt-get update", "apt-get dist-upgrade", but I still have a 2.x kernel:

Linux dock85 2.6.37-dockstar #6 Mon Jan 17 01:55:44 CET 2011 armv5tel GNU/Linux

I looked into runing mkimage as in the kraqh3d post above, but have no /boot/vmlinuz or /boot/uInitrd, just /boot/uImage.

I have serial access, and just before the login prompt, get this line:

Debian GNU/Linux wheezy/sid dock85 ttyS0

so I have some sort of wheezy setup. How do I complete the upgrade to 3.x?

lyzby Wrote:
-------------------------------------------------------
> I looked into runing mkimage as in the kraqh3d post above,
> but have no /boot/vmlinuz or /boot/uInitrd, just /boot/uImage.
> [...]
> How do I complete the upgrade to 3.x?

If you have the flash-kernel package installed, update-initramfs will use it to create uImage and uInitrd during kernel installation.

I've been following this topic about kernel 3.2.x is having problem booting:
http://forum.doozan.com/read.php?3,6965

Is there a way to upgrade from Debian squeeze to wheezy version 3.0.x?

TIA
bodhi

My rtl8192cu wireless dongle requires a 3.x kernel, and I upgraded from squeeze to wheezy. The upgrade went great, but the new 3.2 kernel bugs resulted in an unbootable device. I've manually installed an older wheezy kernel and all is good.

http://snapshot.debian.org/archive/debian/20120114T153156Z/pool/main/l/linux-2.6/linux-image-3.1.0-1-kirkwood_3.1.6-1_armel.deb

root@canaco:/# uname -a
Linux canaco 3.1.0-1-kirkwood #1 Sat Dec 24 14:15:33 UTC 2011 armv5tel GNU/Linux

dpkg did not create the uImage and uInitrd which I had to manually create using:

mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.1.0-1-kirkwood -d /boot/vmlinuz-3.1.0-1-kirkwood /boot/uImage-3.1.0-1-kirkwood
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.1.0-1-kirkwood -d /boot/initrd.img-3.1.0-1-kirkwood /boot/uInitrd-3.1.0-1-kirkwood

Thanks raja! will try this.

@raja,

I'm having problem going to wheezy using this deb:

My current version:

root@Ds1:~# uname -a
Linux Ds1 2.6.32-5-kirkwood #1 Wed Jan 12 15:27:07 UTC 2011 armv5tel GNU/Linux

The error was about initramfs-tools:

root@Ds1:/# dpkg -i /localdisk/linux-image-3.1.0-1-kirkwood_3.1.6-1_armel.deb 

Selecting previously deselected package linux-image-3.1.0-1-kirkwood.
dpkg: regarding .../linux-image-3.1.0-1-kirkwood_3.1.6-1_armel.deb containing linux-image-3.1.0-1-kirkwood:
 linux-image-3.1.0-1-kirkwood breaks initramfs-tools (<< 0.99~)
  initramfs-tools (version 0.98.8) is present and installed.
dpkg: error processing /localdisk/linux-image-3.1.0-1-kirkwood_3.1.6-1_armel.deb (--install):
 installing linux-image-3.1.0-1-kirkwood would break initramfs-tools, and
 deconfiguration is not permitted (--auto-deconfigure might help)
Errors were encountered while processing:
 /localdisk/linux-image-3.1.0-1-kirkwood_3.1.6-1_armel.deb

I've tried --auto-deconfigure as suggested in the output above, and it did not work, either.

Current package status:

Package initramfs-tools
	•	lenny (oldstable) (utils): tools for generating an initramfs 
0.92o: all
	•	lenny-backports (utils): tools for generating an initramfs 
0.94.4~bpo50+1 [backports]: all
	•	squeeze (stable) (utils): tools for generating an initramfs 
0.98.8: all
	•	squeeze-backports (utils): tools for generating an initramfs 
0.99~bpo60+1 [backports]: all
	•	wheezy (testing) (utils): tools for generating an initramfs 
0.99: all
	•	sid (unstable) (utils): generic modular initramfs generator 
0.100: all

Any Idea how to proceed?
Thanks,
bodhi

First, back up any essential files that you need. Gone files are usually gone. Gone!

The 3.2 kernel has a problem in it that makes it unable to boot on many Kirkwood machines, due to a problem with L2Cache and uboot. There was some discussion about whether it was a bug in the kernel, obstinacy/borderline-arrogance from the kernel maintainers, or a bug in uboot. The question and answer are really academic, though, since I'm just plain grateful to both kernel maintainers and uboot maintainers - it was just really an unforeseen problem... they quickly spotted the problem and offered us fixes. If you are ever going to use a stock Debian kirkwood 3.2 or higher kernel, you will most likely eventually need to upgrade your u-boot. That doesn' look like your most pressing problem, though.

In addition to this L2Cache-related problem, users over at ArchLinuxArm have reported some problems w/ udev and kernel module loading.

Importantly (& first and foremost), though, what you mention there seems to be a problem w/ some sort of incompatibilty of the initramfs-tools. Could this be some Squeeze-to-Wheezy glitch?



In part, some of your choices are:

1. a 3.1 kernel, pre-L2Cache problem I posted my 3.1.10 kernel here: http://forum.doozan.com/read.php?2,6578,6830#msg-6830
2. a 3.2 or 3.3 kernel w/ a kernel config that "works around the problem" by enabling the EMBEDDED config set
3. trying to install a newer initramfs-tools
4. flashing a new uboot that will truly fix the problem the problem

My guess is that you want a or b. Actually, I would try c first. But... about that backup... make sure you do it. Gone is gone.

=====================================================

• davy's Github Repo's rescue-dg

Edited 2 time(s). Last edit at 02/16/2012 07:47PM by davygravy.

@davygravy,

Thanks! indeed, I've tried to install a newer initramfs-tools unsuccessfully (I followed kraqh3d's pointers in this thread about mixing wheezy packages with squeeze). I guessed the dependencies were problematic. I could not get wheezy or sid version of initramfs-tools automatically with apt. And I don't want to manually pull in the whole dependent group of packages, it does not seem to be a good approach because of potential future conflicts.

I'm inclined to go with your 3.1.10 kernel. I figure I will wait on 3.2 until later for newer UBoot in order to move forward. And thanks for your works on UBoot! it's quite interesting to see the progress!

And I'm using a backup USB thumb to do this. Not taking any chance :-)

Thanks,
bodhi

@davygravy,

There seems to be a MINOR problem:

root@Ds1:~# dpkg  -i /localdisk/linux-image-3.1.9-kirkwood_1.0_armel.deb 
Selecting previously deselected package linux-image-3.1.9-kirkwood.
(Reading database ... 18776 files and directories currently installed.)
Unpacking linux-image-3.1.9-kirkwood (from .../linux-image-3.1.9-kirkwood_1.0_armel.deb) ...
Done.
Setting up linux-image-3.1.9-kirkwood (1.0) ...

 Hmm. There is a symbolic link /lib/modules/3.1.9-kirkwood/build
 However, I can not read it: No such file or directory
 Therefore, I am deleting /lib/modules/3.1.9-kirkwood/build


 Hmm. The package shipped with a symbolic link /lib/modules/3.1.9-kirkwood/source
 However, I can not read the target: No such file or directory
 Therefore, I am deleting /lib/modules/3.1.9-kirkwood/source

Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.1.9-kirkwood /boot/vmlinuz-3.1.9-kirkwood
update-initramfs: Generating /boot/initrd.img-3.1.9-kirkwood
run-parts: executing /etc/kernel/postinst.d/zz-flash-kernel 3.1.9-kirkwood /boot/vmlinuz-3.1.9-kirkwood

I'm booting to 3.1.9 :-) thanks very much!

Thanks,
bodhi



Edited 1 time(s). Last edit at 02/16/2012 11:48PM by bodhi.

That message is in regards to the kernel source ... You can safely ignore it.

Glad it worked for you.

=====================================================

• davy's Github Repo's rescue-dg

Every thing seems to be OK running kernel 3.1.9. Then I ran "fdisk -l" to check for before mounting another USB thumb drive. I got the following errors:

root@Ds1:~# fdisk -l

Disk /dev/mtdblock0: 1 MB, 1048576 bytes
255 heads, 63 sectors/track, 0 cylinders, total 2048 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mtdblock0 doesn't contain a valid partition table

Disk /dev/mtdblock2: 33 MB, 33554432 bytes
255 heads, 63 sectors/track, 4 cylinders, total 65536 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mtdblock2 doesn't contain a valid partition table

Disk /dev/mtdblock3: 229 MB, 229638144 bytes
255 heads, 63 sectors/track, 27 cylinders, total 448512 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mtdblock3 doesn't contain a valid partition table

Disk /dev/sda: 4075 MB, 4075290624 bytes
255 heads, 63 sectors/track, 495 cylinders, total 7959552 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x59415ac4

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63      224909      112423+  83  Linux
/dev/sda2          224910     7807589     3791340   83  Linux

dmesg shows these errors:

125.456696] uncorrectable error : 
[  125.459997] end_request: I/O error, dev mtdblock0, sector 2040
[  125.466041] Buffer I/O error on device mtdblock0, logical block 255
[  125.472921] uncorrectable error : 
[  125.476166] end_request: I/O error, dev mtdblock0, sector 2040
[  125.482208] Buffer I/O error on device mtdblock0, logical block 255
[  125.502308] uncorrectable error : 
[  125.505561] end_request: I/O error, dev mtdblock1, sector 0
[  125.511340] Buffer I/O error on device mtdblock1, logical block 0
[  125.517955] uncorrectable error : 
[  125.521231] end_request: I/O error, dev mtdblock1, sector 8
[  125.527011] Buffer I/O error on device mtdblock1, logical block 1
[  125.533454] uncorrectable error : 
[  125.536699] end_request: I/O error, dev mtdblock1, sector 16
[  125.542566] Buffer I/O error on device mtdblock1, logical block 2
[  125.549462] uncorrectable error : 
[  125.552709] end_request: I/O error, dev mtdblock1, sector 24
[  125.558576] Buffer I/O error on device mtdblock1, logical block 3
[  125.565101] uncorrectable error : 
[  125.568363] end_request: I/O error, dev mtdblock1, sector 0
[  125.574142] Buffer I/O error on device mtdblock1, logical block 0
[  125.581787] uncorrectable error : 
[  125.585034] end_request: I/O error, dev mtdblock1, sector 0
[  125.590814] Buffer I/O error on device mtdblock1, logical block 0
[  125.597717] uncorrectable error : 
[  125.600984] end_request: I/O error, dev mtdblock1, sector 8
[  125.606763] Buffer I/O error on device mtdblock1, logical block 1
[  125.613131] uncorrectable error : 
[  125.616373] end_request: I/O error, dev mtdblock1, sector 16
[  125.622241] Buffer I/O error on device mtdblock1, logical block 2
[  125.629079] uncorrectable error : 
[  125.632322] end_request: I/O error, dev mtdblock1, sector 24
[  125.638525] uncorrectable error : 
[  125.641766] end_request: I/O error, dev mtdblock1, sector 0

The system is booting and running fine. Automounting with udev working correctly. Everything else seems normal.

These errors did not show on kernel 2.6.32-5 (I shutdown and booted back with kernel 2.6.32-5 to verify).

Any idea why?

bodhi



Edited 1 time(s). Last edit at 02/18/2012 03:15PM by bodhi.

Is there anybody running wheezy kernel having these error messages from fdisk? My Google searches turned up several similar reports from way back (months ago) with different kernel versions, but nobody had an explanation for it! I'm wondering if this is just a bug in fdisk reporting?

On top of 3.1.9, I've have installed flash-kernel package, and run "apt-get update" and "apt-get upgrade", which generated new uImage and uInitrd automatically. Still seeing these errors.



Edited 1 time(s). Last edit at 02/20/2012 01:58AM by bodhi.

Hi folks,
what is exactly in your /etc/apt/source.list ?

this is mine:

deb http://ftp.uk.debian.org/debian/ wheezy main
deb-src http://ftp.uk.debian.org/debian/ wheezy main

deb http://security.debian.org/ wheezy/updates main contrib non-free
deb-src http://security.debian.org/ wheezy/updates main contrib non-free

# Orion repository
#deb http://people.debian.org/~tbm/orion wheezy main

deb http://ftp.fr.debian.org/debian wheezy main contrib non-free
deb-src http://ftp.fr.debian.org/debian wheezy main contrib non-free

First I installed Lenny on anexternal usb hdd, then upgraded to Squeeze with success using doozan script, not shyd or gorgone.
it worked fine, I made a backup with acronis under windows
Boot under squeeze was perfect.

then I manually modified the source .list with content above. Then,
apt-get update
apt-get dist-upgrade
reboot

The installation of wheezy was like a charm
But after reboot, I was unable to connect via ssh, the dockstar does not get an ip from my router anymore.

I guess I made a mistake, somewhere. Do I have to comment out the line deb http://people ... ?
The set up will just tell me it cannot find packages not found.

What can I do now?

thanks.



Edited 1 time(s). Last edit at 02/27/2012 04:41PM by skyrail.

What was the version after you did the apt-get dist-upgrade ? if it is 3.2.x then it won't boot:
http://forum.doozan.com/read.php?3,6965

bodhi Wrote:
-------------------------------------------------------
> What was the version after you did the apt-get
> dist-upgrade ? if it is 3.2.x then it won't boot:
> http://forum.doozan.com/read.php?3,6965

3.2 indeed

This is what I get after apt-get dist-upgrade

debian:/tmp# uname -a
Linux debian 2.6.32-5-kirkwood #1 Tue Jan 17 05:11:52 UTC 2012 armv5tel GNU/Linux
debian:/tmp# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux testing (wheezy)
Release: testing
Codename: wheezy
debian:/tmp# uname -r
2.6.32-5-kirkwood
debian:/tmp# cat /etc/debian_version
wheezy/sid


First, I just rebooted and it never let me access by ssh. So I restored from squeeze backup image.
I did the process again.
Then applied kraqh3d fix http://forum.doozan.com/read.php?2,5746,5749#msg-5749
I checked linux version:
old : 2.6.32-5-kirkwood
new : 3.2.0-1-kirkwood
then create images

debian:/tmp# mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.2.0-1-kirkwood -d /boot/vmlinuz-3.2.0-1-kirkwood /boot/uImage
Image Name: Linux-3.2.0-1-kirkwood
Created: Tue Feb 28 20:27:35 2012
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1571504 Bytes = 1534.67 kB = 1.50 MB
Load Address: 00008000
Entry Point: 00008000

debian:/tmp# mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n Initrd-3.2.0-1-kirkwood -d /boot/initrd.img-3.2.0-1-kirkwood /boot/uInitrd
Image Name: Initrd-3.2.0-1-kirkwood
Created: Tue Feb 28 20:28:45 2012
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 7565572 Bytes = 7388.25 kB = 7.22 MB
Load Address: 00000000
Entry Point: 00000000

I just rebooted and got no ssh access. dockstar as no ip on the LAN. I guess it did not boot at all.

is there any detailed procedure to upgrade from squeeze to wheezy with kernel 3.0 or 3.3 ?

In this thread, these 2 posts have the links to kernel packages that can be installed using dpkg. Also, it has been pointed out that if flash-kernel was installed before the upgrade, then uImage and uInitrd will be automatically created.

Kernel package 3.1.0 (archive)
http://forum.doozan.com/read.php?2,5746,7124#msg-7124

Kernel package 3.1.9 (built by davygravy)
http://forum.doozan.com/read.php?2,6578,6830#msg-6830

It seems there is no way to do apt-get dist-upgrade to a version that is earlier than latest in wheezy. If anybody knows how, please post.

thank you bodhi.

so I gave a try to davygravy solution with kernel 3.9.
First, completely reinstalled Lenny, then upgrade to squeeze. I made some test to check it is stable and fonctionnal. Wifi G stick are recognized and get an IP which I can ping. But for all my 3 Wifi N stick driver loading failed or did not get an IP, when recognized as wlan1 instead of wlan0.

In a prior setup, I got fully functionnal server with samba, web server and minidla, working very well, either with G wifi stick or ethernet.

When Squeeze ready, I did install the 3.9 kernel, skipping wheezy upgrade, just like this:

wget http://ppl.ug/cnl1R63ZOBM/linux-image-3.1.9-kirkwood_1.0_armel.deb
dpkg -i linux-image-3.1.9-kirkwood_1.0_armel.deb
wget http://ppl.ug/vhmCIjv6zmk/linux-headers-3.1.9-kirkwood_1.0_armel.deb
dpkg -i linux-headers-3.1.9-kirkwood_1.0_armel.deb (failed install)

mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.1.9-kirkwood -d /boot/vmlinuz-3.1.9-kirkwood /boot/uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.1.9-kirkwood -d /boot/initrd.img-3.1.9-kirkwood /boot/uInitrd

reboot

I got kernel 3.9 ready (still squeeze) at boot, and check some common commands with success.
But when I plug the wifi stick, it's like a fireworks of error messages. then ssh is stuck, impossible to open another ssh session.
Just reboot to check, stick unplugged. Everything ok. Plug the stick. Issue is back.

Quote

debian:~# ifup wlan0
Internet Systems Consortium DHCP Client 4.1.1-P1
Copyright 2004-2010 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

SIOCSIFADDR: No such device
wlan0: ERROR while getting interface flags: No such device
wlan0: ERROR while getting interface flags: No such device
Bind socket to interface: No such device
Failed to bring up wlan0.
debian:~#
Message from syslogd@debian at Feb 29 21:17:07 ...
kernel:[ 213.135569] Internal error: Oops: 817 [#1]

Message from syslogd@debian at Feb 29 21:17:07 ...
kernel:[ 213.240269] Process wpa_supplicant (pid: 1667, stack limit = 0xc6a2a2 70)

I guess there is a mess in network driver compilation, that make wifi unusable.

skyrail Wrote:
-------------------------------------------------------

> I got kernel 3.9 ready (still squeeze) at boot,
> and check some common commands with success.

You probably forgot to change apt sources list? Starting from Debian squeeze, change sources list to wheezy first. I have only one line in my apt sources:
# cat /etc/apt/sources.list
deb http://ftp.us.debian.org/debian wheezy main

After that, run dpkg, mkimage and the rest. See if your wifi problem was because of the apt sources?



Edited 1 time(s). Last edit at 02/29/2012 06:07PM by bodhi.

I don't know how others are successfully a Wheezy build. After another two hour process I've once again got a Pogoplug which doesn't boot after trying to upgrade to wheezy from squeeze, based on the debian repositories and hitting the 3.2/uboot regression. Since 3.2 everything seems to be impossible, require serial hardware etc.

It would be REALLY valuable to have a statement of steps to get from a stock Pogoplug/Dockstar/Whatever to a working Wheezy build, whether it runs 3.2 or not, I don't really care. Getting a major kernel version upgrade and access to the unstable repositories would be useful enough. However, I can't get to a working version of Wheezy at all, with any kernel, and no statement seems to exist within the forum or site how to achieve this. Perhaps there's something with a manual install of 3.1.9 and a pin or hold of the linux-image package before switching to Wheezy repo which mortals could attempt.

After changing sources.list to point to wheezy, running update and dist-upgrade following outdated instructions in the first few hits of Google, and realising that it would be dead after a reboot, I tried to follow the example of raja who used a .deb to install a non-broken kernel, which he refers to as...
http://snapshot.debian.org/archive/debian/20120114T153156Z/pool/main/l/linux-2.6/linux-image-3.1.0-1-kirkwood_3.1.6-1_armel.deb
...but the link alone isn't enough information to install it in this case (downgrading), and I've been struggling for a long time trying to fill in the blanks.

I suspect there's a sequence which will give you wheezy, but with 3.1.9 which prevents it rolling forward to 3.2, but without some guidance I doubt I'll get there. A guide of the steps would be welcome.

P.S. Alarmingly, and perhaps revealingly whenever I follow the suggestion to download and install raja's linked package by dpkg -i it reports it's ignoring the version needed because of the Wheezy repos providing something newer...

Setting up linux-image-3.1.0-1-kirkwood (3.1.6-1) ...
Running depmod.
WARNING: could not open /lib/modules/3.1.0-1-kirkwood/modules.builtin: No such file or directory
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.1.0-1-kirkwood /boot/vmlinuz-3.1.0-1-kirkwood
update-initramfs: Generating /boot/initrd.img-3.1.0-1-kirkwood
WARNING: could not open /var/tmp/mkinitramfs_xZ1NfY/lib/modules/3.1.0-1-kirkwood/modules.builtin: No such file or directory
Ignoring old or unknown version 3.1.0-1-kirkwood (latest is 3.2.0-2-kirkwood)
run-parts: executing /etc/kernel/postinst.d/zz-flash-kernel 3.1.0-1-kirkwood /boot/vmlinuz-3.1.0-1-kirkwood
Ignoring old or unknown version 3.1.0-1-kirkwood (latest is 3.2.0-2-kirkwood)

For reference, the instructions suggested at http://fzr.squeenus.com/debian/ which have an equivalent to Jeff's Squeeze installer script, but for Wheezy, fail with the error...
"Kernel too old!"
...when running from the Pogoplug's regular shell.

I imagine this script can't be run from a Debian Squeeze shell, as it would be overwriting its own system partition. Having something like this which actually worked would be hugely valuable though. Perhaps there are those with the skills to choose the right kernel.

You'll need a newer uboot to run Wheezy from Debian repos. See "Newer UBoot..." in the uboot section.

=====================================================

• davy's Github Repo's rescue-dg

I thought I needed a new Uboot to run kernel 3.2, but use of wheezy packages itself should be fine on the Pogoplug. I'm basing this on the fact that the Wheezy upgrade used to work before the kernel upgrade. Is that mistaken?

Because of the complexity of fixing Uboot, my plan was to try and work out how to run a version of wheezy without completing the upgrade to 3.2, which I don't really care about (although I do care about using the Wheezy repositories for other packages). This procedure would be purely using apt against debian repositories.

If you know that this is impossible, then it would be very useful to know as it will save me trying.

Thanks for your work on this, everyone. Still figuring things out.

@davygravy if I was to go down the uboot route, I think the instructions you're referring to are these pretty long and detailed ones to build your own uBoot (note message id), figuring out the correct device identity (which I'm not sure of myself on my pink Pogoplug)...
http://forum.doozan.com/read.php?3,6965,6965#msg-6965
...or you might be referring to any of the other instructions in the same thread, some of which appear to fail. Along with the requirement to boot netconsole, have a working tftp on the network etc. it makes me nervous of trying something just in case, based on my own search through a 5 page thread of experiments and a guess as to what the correct instructions are.

By contrast, the uBoot script as described from the doozan Debian pages seemed to be stable and tested, and if I understand properly it incorporates a refresh of uBoot as well...
http://projects.doozan.com/uboot/

I don't understand why Jeff's scripted approach cannot be updated to work for kernel >= 3.2. Perhaps it's simply that the uboot image linked from the debian pages hasn't yet been updated.