[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: dpkg problems with own compiled kernel



On Tue, 26 Apr 2005 06:35 am, Martin Juhlin wrote:
> Hi
>
> I'm running sarge and having some problems when installing my own
> compiled kernel. Then problem occures in the decompression face when
> running dpkg on the deb-package, the output is included below. The
> package is built with make-kpkg. The following thing is checked :
>
> * Free disc space is 40G and .deb is about 2M.
> * fsck and smartctl report no errors
> * the file that dpkg complane about is included in the .deb package
> * tried both an old known to work package and a new compiled, both
> return the same error. Both package have the same configuration.
> * apt-get dist-upgrade is working without any problem
>
> My current kernel is 2.4.27-2-386 and the sarge system is up-to-date.
> Any ideas is welcome....
>
> # dpkg -i kernel-image-2.4.27_custom.1.0_i386.deb
> (Reading database ... 154390 files and directories currently
> installed.) Preparing to replace kernel-image-2.4.27 custom1.0 (using
> kernel-image-2.4.27_custom.1.0_i386.deb) ...
> Unpacking replacement kernel-image-2.4.27 ...
> dpkg: error processing kernel-image-2.4.27_custom.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_custom.1.0_i386.deb
>
>
> Best regards
>     Martin

Hi Martin

If I understand you correctly, you're trying to in install a complete 
custom compiled kernel.  

Your .deb is 2Mb.  Thats a lot smaller than the standard debian 2.4.27 
kernel 10781.3 Kb.  Unless you changed the disabled a lot of modules, 
2M is too small?

Are you sure it built correctly?

Can you unpack manually? 
Is `./lib/modules/2.4.27/kernel/drivers/i2c/i2c-core.o' present? 
(kpackage or ark will allow you to list the files within a .deb)

Hope this helps.
-- 
Andrew V.



Reply to: