Kernel install fails with Wheezy script

I've been struggling with a problem for the last couple of days, and I tested everything I came to think of but still no solution!

I bought a GoFlex Home and went about to install debian on it. I've installed the latest U-boot ("U-Boot 2011.12 (Apr 18 2012 - 23:08:20)" according to netconsole) and the V2.8 Recovery System which works like a charm. When I use this image on a USB-stick (or the SATA drive) it boots up and runs fine. What I want to do is to install a fresh Debian Wheezy with for example Jeff's script. However when I run the script everything work as expected until debootstrap is configuring initramfs-tools and it post the following message:

I: Configuring libapt-pkg4.12:armel...
I: Configuring libreadline6:armel...
I: Configuring gnupg...
I: Configuring libgnutls26:armel...
I: Configuring libkrb5-3:armel...
I: Configuring initramfs-tools...
I: Configuring module-init-tools...
I: Configuring libgssapi-krb5-2:armel...
I: Configuring apt...
I: Configuring flash-kernel...
I: Configuring linux-image-3.2.0-3-kirkwood...
I: Configuring wget...
I: Configuring linux-image-kirkwood...
I: Configuring openssh-client...
I: Configuring openssh-server...
I: Configuring initramfs-tools...
W: Failure while configuring base packages.  This will be re-attempted up to five times.
W: See /tmp/debian/debootstrap/debootstrap.log for details (possibly the package initramfs-tools is at fault)
I: Configuring flash-kernel...
I: Configuring initramfs-tools...
W: Failure while configuring base packages.  This will be re-attempted up to five times.
W: See /tmp/debian/debootstrap/debootstrap.log for details (possibly the package initramfs-tools is at fault)
I: Configuring initramfs-tools...
W: Failure while configuring base packages.  This will be re-attempted up to five times.
W: See /tmp/debian/debootstrap/debootstrap.log for details (possibly the package initramfs-tools is at fault)
I: Configuring initramfs-tools...
W: Failure while configuring base packages.  This will be re-attempted up to five times.
W: See /tmp/debian/debootstrap/debootstrap.log for details (possibly the package initramfs-tools is at fault)
I: Configuring initramfs-tools...
W: Failure while configuring base packages.  This will be re-attempted up to five times.
W: See /tmp/debian/debootstrap/debootstrap.log for details (possibly the package initramfs-tools is at fault)
debootstrap failed.
See /tmp/debian/debootstrap/debootstrap.log for more information.

The relevant part from /tmp/debian/debootstrap/debootstrap.log is:

Setting up openssh-client (1:6.0p1-2) ...
Setting up openssh-server (1:6.0p1-2) ...
Creating SSH2 RSA key; this may take some time ...
Creating SSH2 DSA key; this may take some time ...
Creating SSH2 ECDSA key; this may take some time ...
Restarting OpenBSD Secure Shell server: sshd
Warning: Fake start-stop-daemon called, doing nothing

Warning: Fake start-stop-daemon called, doing nothing
.
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.2.0-3-kirkwood
Warning: root device  does not exist

Unable to abort; system will probably be broken!
Unsupported platform.
run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1
dpkg: error processing initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for flash-kernel ...
Unsupported platform.
dpkg: error processing flash-kernel (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 initramfs-tools
 flash-kernel
Setting up initramfs-tools (0.107) ...
update-initramfs: deferring update (trigger activated)
Setting up flash-kernel (3.2) ...
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.2.0-3-kirkwood
Warning: root device  does not exist

Unable to abort; system will probably be broken!
Unsupported platform.

Do anyone have any idea what could be the problem?

I've already tried debootstraping without a kernel which works but when installing it chrooted after the installation the same problem arises (that is also the case when trying to install davygravy's 3.3.2 kernel). Jeff's squeeze script on the other hand can be installed and booted by U-boot according to netconsole ("Loading file "/boot/uImage" from usb device 0:1 (usbda1)" and so on) but I can't ssh into it no matter which arcNumber I use (I've tested 2097, 2998, 3089 and 3338).

I've solved it now, I write this up for reference if someone runs into the same problem. I used the V2.8 Recovery System to do the debootstraping, and got the error each time (even after re-installing the Recovery System). However running debootstrap on another system (in my case an old dockstar with squeeze) it works as it should.

Hi Fredrik,
Can you please elaborate on how you solved this problem? I am getting the same message trying to install wheezy on a USB stick booting from rescue v2 installed in nand in a goflexnet device. Any insight appreciated.

Thanks

alexisazen Wrote:
-------------------------------------------------------
> Hi Fredrik,
> Can you please elaborate on how you solved this
> problem? I am getting the same message trying to
> install wheezy on a USB stick booting from rescue
> v2 installed in nand in a goflexnet device. Any
> insight appreciated.
>
> Thanks

Edit the wheezy install script and delete the reference to "flash-kernel" in the EXTRA_PACKAGES - then run the script.

When the install ended successful I wasn't able to start it directly - first I had to boot the rescue system again, chroot to the debian system and install a recent kernel (v3.3.2) - All fine then :)

netconsole/UART is adviced - as always!

greetz

Hi tuxuser,

Many thanks for your input. Omitting the "flash-kernel" reference allows for the installation to conclude succesfully. In the chroot environment trying to install a newer kernel by issuing a dpkg -i linux-image-3.3.2-kirkwood-dg_1.1_armel.deb command yields the following errorsQ

Selecting previously unselected package linux-image-3.3.2-kirkwood-dg.
(Reading database ... 10119 files and directories currently installed.)
Unpacking linux-image-3.3.2-kirkwood-dg (from linux-image-3.3.2-kirkwood-dg_1.1_armel.deb) ...
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (Can't locate Term/ReadLine.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14 /usr/local/lib/site_perl .) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.)
debconf: falling back to frontend: Teletype
Done.
Setting up linux-image-3.3.2-kirkwood-dg (1.1) ...
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
debconf: unable to initialize frontend: Dialog
debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (Can't locate Term/ReadLine.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14 /usr/local/lib/site_perl .) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.)
debconf: falling back to frontend: Teletype

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


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

Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.3.2-kirkwood-dg /boot/vmlinuz-3.3.2-kirkwood-dg
update-initramfs: Generating /boot/initrd.img-3.3.2-kirkwood-dg
df: Warning: cannot read table of mounted file systems: No such file or directory
warning: failed to read mtab
run-parts: executing /etc/kernel/postinst.d/zz-flash-kernel 3.3.2-kirkwood-dg /boot/vmlinuz-3.3.2-kirkwood-dg

Any ideas?


------------------------------------------------------------------EDIT---------------------------------------------------------------------------------------------
Despite the frightening messages the kernel was installed fine and boots just fine. Many thanks to everyone! Great community!



Edited 1 time(s). Last edit at 10/15/2012 12:38PM by alexisazen.

Since I never activly "chrooted" myself, can one point me the steps necessary?

Assuming that you have booted from rescue and your unbootable wheezy installation is in /dev/sda1

Create mountpoint:

mkdir /tmp/wheezy

Mount wheezy partition

mount /dev/sda1 /tmp/wheezy

chroot

chroot /tmp/wheezy /bin/bash

No you're in the wheezy install. Do the kernel update and then exit with

exit

Hope this helps.



Edited 1 time(s). Last edit at 10/18/2012 07:49AM by alexisazen.

alexisazen Wrote:
-------------------------------------------------------
> Assuming that you have booted from rescue and
> your unbootable wheezy installation is in
> /dev/sda1
>
> Create mountpoint:
>

> mkdir /tmp/wheezy
>

>
> Mount wheezy partition
>

> mount /dev/sda1 /tmp/wheezy
>

>
> chroot
>

> chroot /tmp/wheezy /bin/bash
>

>
> No you're in the wheezy install. Do the kernel
> update and then exit with
>

> exit
>

Thats how I did it -> Maybe overkill.. but thought I would share

# Mount roofs
mkdir /tmp/wheezy
mount /dev/sda1 /tmp/wheezy
cd /tmp/wheezy

# Prepare chroot-environment
mount -t proc proc proc/
mount -t sysfs sys sys/
mount -o bind /dev dev/
mount -t devpts pts dev/pts/
chroot /tmp/wheezy /bin/bash

# Now here we go with the kernel install

#Dependencies
apt-get update
apt-get install dialog ca-certificates openssl

wget https://dl.dropbox.com/sh/nwt2kbvetvgvroo/661x9b5PLg/Kirkwood/kernel/linux-image-3.3.2-kirkwood-dg_1.1_armel.deb?dl=1 -O linux-image-3.3.2-kirkwood-dg_1.1_armel.deb

# Safety
cp -r /boot /boot-backup

# flash-kernel never installed for me successfully for me -> removing postinstall-script, otherways update-initramfs will bug around
rm /etc/kernel/postinst.d/zz-flash-kernel

# Install Kernel
dpkg -i linux-image-3.3.2-kirkwood-dg_1.1_armel.deb

# Build proper uboot images
cd /boot
mkimage -A arm -O linux -T kernel  -C none -a 0x00008000 -e 0x00008000 -n Linux-3.3.2 -d vmlinuz-3.3.2-kirkwood-dg uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.3.2-kirkwood-dg -d initrd.img-3.3.2-kirkwood-dg uInitrd

# Exit chroot
exit

# Unmount chroot-environment
umount /tmp/wheezy/dev/pts
umount /tmp/wheezy/dev
umount /tmp/wheezy/sys
umount /tmp/wheezy/proc
cd /
umount /tmp/wheezy

#Reboot
init 6

I cannot create a working wheezy USB stick.

using jeffs method it ends with

/usr/bin/mkimage: Can't open /boot/vmlinuz-3.2.0-3-kirkwood: No such file or directory
/usr/bin/mkimage: Can't open /boot/initrd.img-3.2.0-3-kirkwood: No such file or directory

when I try to repair with the instructions from above everything works until I get

Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.3.2-kirkwood-dg /boot/vmlinuz-3.3.2-kirkwood-dg
update-initramfs: Generating /boot/initrd.img-3.3.2-kirkwood-dg
Warning: root device /dev/root does not exist

Press Ctrl-C to abort build, or Enter to continue

I can hit enter as often as I like, nothing continues...
If I break I get

Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.3.2-kirkwood-dg.postinst line 341, <STDIN> line 2.
Errors were encountered while processing:
 linux-image-3.3.2-kirkwood-dg

How to proceed from here?

EDIT: I managed myself:
1. the reason why Jeff's script fails may be due to the fact that the kernel version is 3.2.0-4. No idea how to fix.
2. it is not a good idea to try to repair the failed installation with kernel 3.3.2. If I repair with

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

it seems to work. At least it booted 2-3 times, now it is booting but cannot be reached via network. Sigh. but this is a different problem...


Thanks
Thomas



Edited 1 time(s). Last edit at 11/06/2012 03:17PM by Thk.

Found this thread very helpful along with many others.

I had to do a bunch of searching and piecing together of information so I thought I'd share my install process to get wheezy installed on my Seagate Dockstar in one post pulling from various sources.

I was getting FATAL: kernel too old errors.

1) Install the Rescue System V2 (Very Very awesome and extremely useful: Make sure to boot from USB device I used a Squeeze USB)
Rescue System v2

2) Boot your Dockstar with no USB Drive attached (you should be in the Rescue system from Step 1 rescue:#)
a) Insert your clean USB stick (redo Fdisk partitions if you want to be 100% sure)
Fdisk table for my 4GB USB
Device Boot Start End Blocks Id System
/dev/sda1 * 1 2454 3455221 83 Linux
/dev/sda2 2455 2781 460416 82 Linux swap / Solaris



you need to delete old debootstrap and remove link to perl for whezzy install script

mount -o remount,rw /
rm /usr/sbin/debootstrap
rm -rf /usr/share/debootstrap
chmod 666 /usr/bin/microperl

b) Run the wheezy install script (follow the default directions from http://projects.doozan.com/debian/ if you are lost)

cd /tmp
wget http://projects.doozan.com/debian/kirkwood.debian-wheezy.sh
chmod +x kirkwood.debian-wheezy.sh
export PATH=$PATH:/usr/sbin:/sbin
./kirkwood.debian-wheezy.sh

3) Everything installed successfully but I had errors

I: Base system installed successfully.
/usr/bin/mkimage: Can't open /boot/vmlinuz-3.2.0-3-kirkwood: No such file or directory
/usr/bin/mkimage: Can't open /boot/initrd.img-3.2.0-3-kirkwood: No such file or directory




Installation complete

You can now reboot your device into Debian.
If your device does not start Debian after rebooting,
you may need to restart the device by disconnecting the power.

The new root password is 'root'  Please change it immediately after
logging in.

Reboot now? [Y/n] Y

4)FIx errors if applicable
Mount the wheezy install while in the rescue v2 from step #1

# Mount roofs
mkdir /tmp/wheezy
mount /dev/sda1 /tmp/wheezy
cd /tmp/wheezy

chroot the wheezy install

chroot /tmp/wheezy /bin/bash

change directory to /boot and run the commands from Thk's post

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

exit chroot

exit

5) Reboot system you're done!

Hope this helps!

Sw1val Wrote:
-------------------------------------------------------
> 3) Everything installed successfully but I had
> errors
>
>

> I: Base system installed successfully.
> /usr/bin/mkimage: Can't open
> /boot/vmlinuz-3.2.0-3-kirkwood: No such file or
> directory
> /usr/bin/mkimage: Can't open
> /boot/initrd.img-3.2.0-3-kirkwood: No such file or
> directory
> 
> 
> 
> 
> Installation complete
> 
> You can now reboot your device into Debian.
> If your device does not start Debian after
> rebooting,
> you may need to restart the device by
> disconnecting the power.
> 
> The new root password is 'root'  Please change it
> immediately after
> logging in.
> 
> Reboot now? [Y/n] Y
> 
>

Just edit Jeff's script and replace 'KERNEL_VERSION=3.2.0-3-kirkwood' by 'KERNEL_VERSION=3.2.0-4-kirkwood'
;)



Edited 1 time(s). Last edit at 11/14/2012 11:02AM by ARJunior.

Thank you so much for this thread! I was banging my head against the wall trying to get debian installed on my Pogoplug, and this seemed to do the trick!

I, too, was getting "FATAL: kernel too old" errors.

Yes, This helped. Thanks.

Dear all,

after following this and other threads - and struggling for days now - the wheezy install-script did not report any errors, but does not boot afterwards. What I did:

- fresh dockstar
- installed latest uboot via uboot script (Jeff)
- installed RescueV2 from debian embed-install (i.e. Jeffs NAND Debian on USB http://forum.doozan.com/read.php?2,72, it was not possible to install the RescueV2 from the RescueV3 USB from DavyGravy, it complained that the uboot md5 was not the latest one although using the uboot install script it definitely states it is the latest one:

U-Boot 2011.12 (Feb 12 2012 - 21:33:07)

?? It was not clear to me whether this is critical for the RescueV2 installation, so I switched to embed-debian on USB and this worked very well)
- btw - booting from RescueV3 usb works very well too, it just does not install RescueV2
- boot from Rescue V2 without anything connected to USB
- remount / -> rw
- mv debootstrap (binary and folder)
- mv microperl
- adjust wheezy install script to kernel 3.2.0-4
- insert USB drive (sda1 -> ext2, sda2 -> swap with sda1 bootable)
- run wheezy installation script
- script did not report any errors (see attachment)
- reboot (I tried also to disconnect the power of the dockstar)
- netconsole output shows "starting kernel..." (netconsole output see attached)
- nothing happens, ie. it cannot be reached via network

add-ons:
- I tried this also with the squeeze install adjusted (went ok, it booted according to netconsole, but then nothing happened anymore, ie. the same problem like it is with wheezy)
- RescueV2 (now in flash) works very well
- RescueV3 USB boots well too
- first stage of Jeff's Debian NAND (ie. written on USB) boots as well
- all get the same IP (my router does this according to the MAC, so no problem with that), otherwise it should get a new via dhcp
-> therefor it seems to be something connected to the installation itself and not to uboot

Any ideas? ... any help is appreciated, this matter is new to me.

thanks a lot!
best
leo

Don't you forget to change arcNumber to 2998 ?

ARJunior Wrote:
-------------------------------------------------------
> Don't you forget to change arcNumber to 2998 ?

Thanks for the hint. After checking with RescueV2 -> arcNumber=2097.
One question before applying a new arcNumber:

- Why does RescueV2/ RescueV3 (USB) boot without any problem but neither squeeze or wheezy?

-> Update: netconsole works now while using two windows (or one) and invoking it from remote (Debian Wheezy) with:

nc -klup 6666 &
socat STDIO UDP-SENDTO:192.168.1.14:6666

All other options mentioned in the thread about netconsole (http://forum.doozan.com/read.php?3,14) did not work or did not work reliably.
best
leo



Edited 1 time(s). Last edit at 11/28/2012 02:39PM by lcg.

Yes, Kernel of Rescue v2 and V3 supports Dockstar arcNumber...you can change it safely.
You can change it from Rescue without any problem.
Use fw_setenv command for write new arcNumber but verify new value with fw_printenv before reboot the device.

I don't really know why neither Squeeze or Wheezy doesn't boot but putting the good arcNumber value is mandatory for Kernel to identify your device correctly...
Maybe arcNumber 2097 doesn't prevent Squeeze or Wheezy to boot in your case but you should try to be sure...



Edited 1 time(s). Last edit at 11/28/2012 12:27PM by ARJunior.

ok, arcNumber changed, but no success - boot hangs, here fw_printenv:

rescue:~# fw_printenv 
ethact=egiga0
bootdelay=3
baudrate=115200
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_rootfstype=ext2
usb_rootdelay=10
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
ethaddr=00:10:75:1A:DD:43
usb_root=/dev/sda1 ro
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts init=/sbin/init-ro
serverip=192.168.1.6
ipaddr=192.168.1.14
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
rescue_installed=1
arcNumber=2998

and uboot (no update needed):

# Validating existing uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to jeff.doozan.com (50.116.34.13:80)
Connecting to projects.doozan.com (50.116.34.13:80)
valid-uboot.md5      100% |****************************************************************************|  1133   0:00:00 ETA
## Valid uBoot detected: [dockstar davygravy-2012-02-12-current]
## The newest uBoot is already installed on mtd0.

Again, RescueV3 with kernel 'Linux-3.3.2-kirkwide' boots perfectly, so it should not be anything related to a 3er kernel (and kernel 2.6 does not boot too, ie. Squeeze).

@lcg,

You might want to rerun the UBoot installation script, and reset UBoot environment:

You are already running the latest uBoot.
Would you like to reset the uBoot environment? [N/y] y

@bodhi - pretty cool. Yes, that worked for Squeeze as well as for Wheezy. Thanks! Is the correct explanation the read-only part or did the 'uboot reset' more?

@lcg, I recalled that your installation was not completed because of 'kernel too old" problem, even though UBoot was installed successfully.

Basically, during UBoot installation, the UBoot envs reset question should be answered YES is if you're trying to recover from a previous incompleted UBoot-Debian installation. This question should be answered NO if you're only updating UBoot to a new version (because you might have modified some envs for you own setup).

What a bloody pain, why did ever install this stupid u-Boot

Thanks, me (or you?), for this deep insight and extremely useful comment! We have all been waiting for constructive contributions like this one. Keep up the good work!

Oh, I guess the latter was meant more for people like bodhi, davygravy, shyd, varkey, rudolf (to mention just a few), people at archlinuxarm and many others and above all Jeff, who are really trying to help people with getting their plugs up and running. So, I believe the last five letters in "stupid u-Boot" are superfluous and, in fact, incorrect.

---
Standart ist der Standardfehler

Regarding your message about "Unsupported platform" - a workaround:

You should fix /etc/initramfs/post-update.d/flash-kernel so that it successfully flashes your kernel & initrd. It's in /etc, so you're free to edit it to make it work on your board.

If you can't edit it to make it work (e.g., flashing is done with JTAG), then you ought to have it print out a big warning reminding you to flash it, and exit 0.

Once you've fixed it, then you can run dpkg --configure -a.

However, you will need to flash a firmware by yourself, later

On my system, I had to repeat the same procedure for /etc/kernel/postinst.d/zz-flash-kernel