[PlanetCCRMA] alsa kernel modules: invalid module format

[Aaron Heller]

--On Monday, November 8, 2004 10:28 -0800 Fernando Pablo Lopez-Lezcano
<nando@ccrma.Stanford.EDU> wrote:

> On Sun, 2004-11-07 at 13:29, Samuel Sieb wrote:
>> Fernando Pablo Lopez-Lezcano wrote:
>> > On Sat, 2004-11-06 at 19:31, Samuel Sieb wrote:
>> >> Fernando Pablo Lopez-Lezcano wrote:
>> >>> On Sat, 2004-11-06 at 14:46, Samuel Sieb wrote:
>> >>>> I installed FC2 on a computer, then upgraded to Planet CCRMA, but I 
>> >>>> can't get the sound to work now.  It's a Pentium 133.  I get a
>> >>>> stream of  the following messages when I try to load a sound module:
>> >>>> WARNING: Error inserting snd_sb16_dsp 
>> >>>> (/lib/modules/2.6.7-1.437.1.ll.rhfc2.ccrma/updates/isa/sb/snd-sb16-
>> >>>> dsp.ko):  Invalid module format
>> > 
>> > And you did not get any complains from rpm? (about missed
>> > dependencies?). That is strange. The kernel and the kernel-module-alsa
>> > packages have built in dependencies so that you should not be able to
>> > install kernel-module-alsa if the proper matching kernel is not
>> > installed. 
>>  
>> As far as I can tell, rpm doesn't know any distinction between i586 and 
>> i686 versions (at least for dependencies).
> 
> Rpm itself does not, and that is why I added explicit dependencies to
> the kernels and all kernel module package so that the kernel module
> package has to match the architecture of the kernel it is installed with
> (check what packages provide with "rpm -q --provides package_name", and
> what they need with "rpm -q --requires package_name). 
> 
> So, if you have a Planet CCRMA kernel with architecture i586 and you try
> to install a kernel-module-alsa package with architecture i686, rpm
> should complain about a missing dependency. If it does not, then there's
> a bug in my packages. 

A year or so ago, when I was trying to use alsa kernel modules compiled for
i686 on my M9000 (this is a low-power processor that is missing some
optional i686 instructions), I did not get invalid module format error
messages like the above.  The modules loaded just fine, but then raised
SIGILL (illegal instruction) errors the first time the code was invoked,
e.g., when alsactl loads the saved mixer settings.