Unresolved symbols potato and kernel 2.0.36
<depressed_tired_of_pointless_hacking_mode>
I suppose it's the height of naivite to expect an answer about Debian around
here, but here goes...
</depressed_tired_of_pointless_hacking_mode>
Once again... I upgraded to Potato. Yes, stupid, but I'm really really
tired of waiting.
The upgrade thought it a great idea to remove my working alsa-modules
package and replace it with... NOTHING! Poof, perfectly good sound is out
there, somewhere.
So I have tried to replace it... reinstalling, trying other kernel versions
(including this new-fangled kernel 2.2.x thing which is apparently the
greatest thing since sliced bread, but won't run on a computer with THREE
SERIAL PORTS!!! Ever heard of a machine so unusual? I mean a shared IRQ
that's like, IMPOSSIBLE isn't it??)
I tried recompiling my old drivers, 0.3.pre4 something, and could only do
that if I installed gcc272 as well, and actually got them compiled.
Now I come to the subject line. I have over a screenful of
depmod: *** Unresolved symbols in /lib/modules/2.0.36/misc/isapnp.o
depmod: *** Unresolved symbols in /lib/modules/2.0.36/misc/persist.o
depmod: *** Unresolved symbols in /lib/modules/2.0.36/misc/snd-ac97-codec.o
depmod: *** Unresolved symbols in /lib/modules/2.0.36/misc/snd-ad1848.o
depmod: *** Unresolved symbols in /lib/modules/2.0.36/misc/snd-audiodrive1688.o
depmod: *** Unresolved symbols in /lib/modules/2.0.36/misc/snd-audiodrive18xx.o
depmod: *** Unresolved symbols in /lib/modules/2.0.36/misc/snd-audiopci.o
depmod: *** Unresolved symbols in /lib/modules/2.0.36/misc/snd-card-ad1848.o
depmod: *** Unresolved symbols in /lib/modules/2.0.36/misc/snd-card-cs4231.o
depmod: *** Unresolved symbols in /lib/modules/2.0.36/misc/snd-card-cs4232.o
depmod: *** Unresolved symbols in /lib/modules/2.0.36/misc/snd-cs4231.o
depmod: *** Unresolved symbols in /lib/modules/2.0.36/misc/snd-card-cs4236.o
depmod: *** Unresolved symbols in /lib/modules/2.0.36/misc/snd-cs4236.o
depmod: *** Unresolved symbols in /lib/modules/2.0.36/misc/snd-detect.o
... and so on.
How on the planet do I resolve them? Yes, they're all the alsa modules, so
what? How do I fix this? I have a very limited time to hack and I don't
like spending 4 hours fixing something that was working fine.
Thanks for bearing with me in my misery, and please, give SOME indication
that someone is out there that has done this before???
<sigh>
--
Jonathan Markevich <jmarkevich@mad.scientist.com>
http://members.xoom.com/JMarkevich
There is no grief which time does not lessen and soften.
Reply to: