On Mon, Jan 24, 2005 at 10:14:59PM +0100, J G Miller wrote: > Package: i2c-source > Version: 1:2.9.0-11 > Severity: wishlist > > > When installing a custome kernel image, the on screen blurb advises, > if a /lib/modules/<same_kernel_version> directory is detected, to move > that directory out of the way. If that is done, then on trying to > install the kernel image, if a i2c-<same_kernel_verion> built from > source module has previously been installed, the following problem > occurs > > # dpkg -i kernel-image-2.4.27_wolverine.1.0_i386.deb > > (Reading database ... 349758 files and directories currently installed.) > Preparing to replace kernel-image-2.4.27 wolverine.1.0 (using > kernel-image-2.4.27_wolverine.1.0_i386.deb) ... > Unpacking replacement kernel-image-2.4.27 ... > dpkg: error processing kernel-image-2.4.27_wolverine.1.0_i386.deb > (--install): > unable to create `./lib/modules/2.4.27/kernel/drivers/i2c/i2c-core.o': No > such file or directory > dpkg-deb: subprocess paste killed by signal (Broken pipe) > Errors were encountered while processing: > kernel-image-2.4.27_wolverine.1.0_i386.deb > > However, if the i2c and lm-sensors module packages are first purged, before > the kernel-image installation is attemtped, then the problem does not occur. > > # dpkg --purge i2c-2.4.27 lm-sensors-2.4.27 > (Reading database ... 349757 files and directories currently installed.) > Removing lm-sensors-2.4.27 ... > Purging configuration files for lm-sensors-2.4.27 ... > Removing i2c-2.4.27 ... > Purging configuration files for i2c-2.4.27 ... > > # dpkg -i kernel-image-2.4.27_wolverine.1.0_i386.deb > (Reading database ... 349649 files and directories currently installed.) > Preparing to replace kernel-image-2.4.27 wolverine.1.0 (using > kernel-image-2.4.27_wolverine.1.0_i386.deb) ... > Unpacking replacement kernel-image-2.4.27 ... > Setting up kernel-image-2.4.27 (wolverine.1.0) ... > You are attempting to install a kernel version that is the same as > the version you are currently running (version 2.4.27). The modules > list is quite likely to have been changed, and the modules dependency > file /lib/modules/2.4.27/modules.dep needs to be re-built. It can > not be built correctly right now, since the module list for the > running kernel are likely to be different from the kernel installed. > I am creating a new modules.dep file, but that may not be > correct. It shall be regenerated correctly at next reboot. > > I repeat: you have to reboot in order for the modules file to be > created correctly. Until you reboot, it may be impossible to load > some modules. Reboot as soon as this install is finished (Do not > reboot right now, since you may not be able to boot back up until > installation is over, but boot immediately after). I can not stress > that too much. You need to reboot soon. > > Please Hit return to continue. > Not updating image symbolic links since we are being updated (wolverine.1.0) > > [... succesfully completed ...] > > Should it be the case that one needs to remove the i2c package prior > to a kernel update, or should one always install the freshly built module > packages (built at the same time of the new kernel version) BEFORE the > kernel-image > package? Theoretically that should not be done. However, there was a series of bugs in the first version of the i2c modules. If you installed such a version, it could lead to the problems you describe.
Could you please tell me the version of the i2c modules you are using? I mean the version returned by 'dpkg -l i2c-2.4.27*'. It may be possible that the modules you have generated are not from the latest source package. In that case, please remove /usr/src/modules/i2c/ and rebuilt them. -- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `- people.debian.org/~aurel32 | www.aurel32.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
