[PlanetCCRMA] unresolved symbols from alsa drivers

[Fernando Pablo Lopez-Lezcano]

> I'm trying to move our laptop for on-stage use from Windows to Linux,
> since we had (who would have thought...) some problems with the current
> setup ;)
> I used to use Suse Linux until now, but now I got a RedHat 8.0 and gave
> it a try. While Suse recognized the ES1879 onboard device, RedHat
> doesn't, So I went and started with the Planet CCRMA which looks like
> great stuff. Downloaded kernel, alsa, etc, just like the tutorial
> states. When trying to load the alsa drivers though, I get errors:
> 
> modprobe snd-es18xx snd_port=0x220 snd_irq=5 snd_dma1=1 snd_dma2=3
> /lib/modules/2.4.19-1.ll/kernel/drivers/sound/acore/snd.o: unresolved
> symbol kill_fasync_R78a1638d
> 
> there are lots more, fasync_helper_, remove_proc_entry_ and so on, each
> with some random weird numbers/characters added (had to handtype this
> since email on the notebook isn't configured yet ;))
> 
> What could that be?

It looks like you have the i386 kernel installed, instead of the i686. I
think I had (blush) never even installed it. I'll check it out. There is
an extra incantation that is not yet in the planetccrma pages to force the
installation of a given kernel for the new version of apt (for some reason
the new version of apt <0.5.4> seems to install the i386 arch by default,
instead of the previous i686).

Do a:
  apt-get install kernel-up#2.4.19-1.ll at i686

That should install the i686 kernel which I know works (meaning no 
unresolved symbols). 

It is good that there is now a way for force the install of a given 
architecture in apt. 

I wonder why is there a problem with unresolved symbols. The kernel srpm 
is the same for both and (supposedly) the configuration file should be 
very similar. Oh well... I'll try to make sure this is fixed in the next 
kernel release. Or maybe I should just erase the i386 kernel from the 
repository so that this cannot happen, I don't think anyone would have a 
need to it. 

-- Fernando