[Bug 910] New: When a kernel ipkg is released, "ipkg upgrade" breaks kernel modules
bugzilla-daemon at bugzilla.openmoko.org
bugzilla-daemon at bugzilla.openmoko.org
Thu Oct 4 21:31:28 CEST 2007
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=910
Summary: When a kernel ipkg is released, "ipkg upgrade" breaks
kernel modules
Product: OpenMoko
Version: 2007.2
Platform: Neo1973
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: kernel
AssignedTo: laforge at openmoko.org
ReportedBy: gnu at openmoko.toad.com
CC: buglog at lists.openmoko.org
Ipkg can't upgrade a kernel (it sits in its own partition), but it can upgrade
kernel modules (which are in the normal filesystem). So when somebody releases
a new kernel and modules, the new modules get loaded by "ipkg upgrade" and then
they don't work with the old kernel.
I flashed the 2007.2 release, then after getting my USB networking gatewayed
properly, did "ipkg update && ipkg upgrade". This installed new kernel modules
(and maybe tried to install a new kernel into the ordinary filesystem). This
broke my kernel modules (e.g. mounting vfat filesystems didn't work; the sound
stopped playing at reboot; etc) until I was able to figure out where to find the
new kernel and manually flash it into the kernel partition.
How to fix this? An obvious way would be to make the kernel ipkg install the
new kernel into the kernel's proper partition. Failing that, it may be possible
to circumvent the problem by administratively never releasing new incompatible
modules into a repository where "ipkg update" will install them for ordinary
naive users.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the buglog
mailing list