On Fre, 2003-02-21 at 23:19, Todd Marek wrote: > Unpacking replacement alsa-modules-2.4.18-newpmac ... > Setting up alsa-modules-2.4.18-newpmac (0.9.0rc7-3) ... > Configuration file for ALSA 0.9 exists. > Attempting to start. > > depmod: *** Unresolved symbols in > /lib/modules/2.4.18-newpmac/alsa/snd-emu10k1-synth.o > depmod: *** Unresolved symbols in > /lib/modules/2.4.18-newpmac/alsa/snd-emu8000-synth.o > depmod: *** Unresolved symbols in > /lib/modules/2.4.18-newpmac/alsa/snd-emux-synth.o > depmod: *** Unresolved symbols in > /lib/modules/2.4.18-newpmac/alsa/snd-gus-synth.o > depmod: *** Unresolved symbols in > /lib/modules/2.4.18-newpmac/alsa/snd-seq-midi.o > depmod: *** Unresolved symbols in > /lib/modules/2.4.18-newpmac/alsa/snd-seq-virmidi.o > depmod: *** Unresolved symbols in > /lib/modules/2.4.18-newpmac/alsa/snd-trident-synth.o > dpkg: error processing alsa-modules-2.4.18-newpmac (--install): > subprocess post-installation script returned error exit status 1 > Errors were encountered while processing: > alsa-modules-2.4.18-newpmac
I also get these unresolved symbols, installation doesn't fail though. After some digging around, it turns out that depmod from modutils around 2.4.13 returned a non-zero exit code under these circumstances, which would cause the alsa-modules postinst script to fail. Upgrading modutils (or installing module-init-tools) and/or changing the alsa-modules postinst to use depmod -a || true instead of just depmod -a should fix this. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast
