Yesterday, I sent the following message to debian-user.  Still trying to
figure out how to fix this problem.  Is it possible that the error is a
result of a bug in the alsa-source package?  Or is it something else?
I am afraid I don't know much about ELF headers.

Thanks!
Bryan

Greetings!
        I am running frozen on an IBM Thinkpad 390E with a 2.0.36
kernel.  This morning, I compiled a new kernel (2.2.15) using
make-kpkg.  I also built the pcmcia and ALSA modules using kpkg.  All
seems to have gone well (I have done this before on another
box).  However, when I installed the newly compiled ALSA modules deb
package, this is what happens:

work:/usr/src# dpkg -i alsa-modules-2.2.15_0.4.1i-5+2.2.15-90_i386.deb 
Selecting previously deselected package alsa-modules-2.2.15.
(Reading database ... 52672 files and directories currently installed.)
Unpacking alsa-modules-2.2.15 (from
alsa-modules-2.2.15_0.4.1i-5+2.2.15-90_i386.deb) ...
Setting up alsa-modules-2.2.15 (0.4.1i-5+2.2.15-90) ...
depmod: error reading ELF header: No such file or directory
depmod: error reading ELF header: No such file or directory

work:/usr/src#

Any ideas as to what this means?  How can I fix this?

Thanks!!
Bryan Walton
  


Reply via email to