archlinux sheeva, pacman installed Linux 3.1, still get 2.6

[fovea1959]

Have a Sheevaplug that's been up for quite a while (last August?), running Archlinux.

just did a pacman -Syu. Linux 3.1 installed correctly (according to pacman), but the system still boots into 2.6:
$this->bbcode_second_pass_code('', '
$ uname -a
Linux plug 2.6.39.2 #2 PREEMPT Sun Jun 26 00:20:28 MDT 2011 armv5tel GNU/Linux
')

/boot/uImage is correct:
$this->bbcode_second_pass_code('', '
$ file /boot/uImage
/boot/uImage: u-boot legacy uImage, Linux-3.1.10-11-ARCH, Linux/ARM, OS Kernel Image (Not compressed), 2951500 bytes, Mon May 21 02:00:00 2012, Load Address: 0x00008000, Entry Point: 0x00008000, Header CRC: 0x97547A6B, Data CRC: 0x7162740A
')

but it appears that my unit is still booting from an old image on the SD card. Subset of output from fw_printenv:
$this->bbcode_second_pass_code('', '
bootargs_console=console=ttyS0,115200
bootargs_root=root=/dev/mmcblk0p2 rootdelay=10
bootdelay=3
bootargs=console=ttyS0,115200 root=/dev/mmcblk0p2 rootdelay=10
bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); mmcinit; mmcinit; ext2load mmc 0:1 0x800000 /uImage; bootm 0x00800000
')

as I'm reading this, my plug is booting from the /uImage file on /dev/mmcblk0p1, and the root filesystem is /dev/mmcblk0p2.
$this->bbcode_second_pass_code('', '
$ mount /dev/mmcblk0p1 /media/mmcblk0p1
$ file /media/mmcblk0p1/uImage
/media/mmcblk0p1/uImage: u-boot legacy uImage, Linux-2.6.39.2, Linux/ARM, OS Kernel Image (Not compressed), 2818620 bytes, Sun Jun 26 02:20:32 2011, Load Address: 0x00008000, Entry Point: 0x00008000, Header CRC: 0x864105AE, Data CRC: 0xAB703FF1
')

is the correct fix at this point for me simply to copy the updated kernel from /boot/uImage to /media/mmcblk0p1, umount /media/mmcblk0p1, and reboot?

[WarheadsSE]

Yup.

[fovea1959]

because of computer induced paranoia, I went out and bought another (bigger faster) SD card, partitioned it, used tar to get the stuff off the old card and create it on the new card, *then* did the change on the new card. Successful all along the way...

thank you, bang on correct answer...

I'm so scared of bricking it...

[xenoxaos]

I don't think that you can really brick the Sheeva. IIRC, you can always reprogram the bootloader with openocd.