ipkg kernel/module upgrade regression

[cwixon@…]

My bleeding-edge build within the last couple of days built a new kernel and
modules, but they did not install correctly onto my GTA01 via ipkg.

In the recent past (see, e.g., #1175), upgrading the kernel package via ipkg
would result in the kernel partition being flashed and the new kernel and module
packages being installed. Before that, the kernel and module packages would
install, but I would have to flash the kernel manually.

But on this upgrade (2.6.22.5-moko11+svnr3874-r13 to 2.6.24+svnr4013-r4014-r3),
*only* the kernel ipkg packages installed.

See the following excerpt from ipkg list_installed, following the upgrade:

kernel - 2.6.24+svnr4013-r4014-r3 - Linux 2.6.x (development) kernel for FIC
SmartPhones? shipping w/ OpenMoko?
kernel- - 2.6.24+svnr4013-r4014-r3 - Linux 2.6.x (development) kernel for FIC
SmartPhones? shipping w/ OpenMoko?
kernel-image- - 2.6.24+svnr4013-r4014-r3 - Linux 2.6.x (development) kernel for
FIC SmartPhones? shipping w/ OpenMoko?

And:

root@thrakkorzog:~$ ls -l /boot
-rw-r--r-- 1 root root 1761992 Feb 4 18:33 uImage-2.6.24
lrwxrwxrwx 1 root root 7 Feb 4 21:30 zImage -> zImage-

Kernel modules did not upgrade:

kernel-module-af-packet - 2.6.22.5-moko11+svnr3874-r13 - af-packet kernel module
kernel-module-bluetooth - 2.6.22.5-moko11+svnr3874-r13 - bluetooth kernel
module; Bluetooth Core ver 2.11
kernel-module-bnep - 2.6.22.5-moko11+svnr3874-r13 - bnep kernel module;
Bluetooth BNEP ver 1.2

... etc. etc. etc. During the ipkg upgrade, each module threw an error that the
corresponding kernel image 2.6.24 was not installed.

And the kernel did not get flashed. Following reboot:

root@thrakkorzog:~$ uname -r
2.6.22.5-moko11

Finally, I don't know whether this is related to this bug or not, but I should
also ask -- why are there three separate packages:

kernel
kernel-
kernel-image-

only "kernel-image-" has a file associated with it, the uimage in /boot.

[andy@…]

Don't think there's anything we can do about this on the kernel side --
changing to be against "OE bitbake recipes / build system"

[john_lee@…]

Hi Graeme, could you please take a look? Thank you!

[cwixon@…]

Well, I ended up reflashing to fresh kernel/rootfs images that used 2.6.24, and
a subsequent kernel upgrade (to 2.6.24+svnr4194-r4165-r4) performed as expected.

I hadn't reflashed in a couple of months before that, so it's possible that this
bug resulted from either

• some problem going from 2.6.22.5 to 2.6.24; or

• cruft that had built up on my machine in the intervening time and over the

course of many ipkg upgrades

I don't really know enough about this to mark it as FIXED at this point, so I'll
leave it to those who know better . . .

[cwixon@…]

To be more specific, the upgrade

FROM

2.6.24+svnr4154-r4165-r3

TO

2.6.24+svnr4194-r4165-r4

is the one that appears to have worked correctly.

[graeme]

Not sure what has happened here, but it seems to work for me, I shall close for now, please reopen if it re-occurs.