Suse 8.0 Alsa CVS compile problem (possibly snd-hammerfall-mem problem?)

Suse 8.0 Alsa CVS compile problem (possibly snd-hammerfall-mem problem?)

[Ivica Bukvic]

Hi all, I am having an odd problem with the ALSA cvs compile on SUSE
8.0. I am trying to do this in order to get the hdsp driver. However,
whenever I compile the driver it stores all the modules in the
/lib/modules/2.4.18-4GB/ folder assuming that my kernel is 2.4.18-4GB.
However, when I open the k control center it tells me that I am using
2.4.18-64GB-SMP kernel (which makes no sense since I am using it on a
single processor laptop).

So, when I try to install the module for the built-in soundcard (intel
8x0), it installs fine, but when I try to modprobe snd-hammerfall-mem,
it fails saying that it has been compiled for the 2.4.18-4GB kernel and
that I am using 2.4.18-64GB-SMP kernel -> hence the kernel mismatch ->
modprobe failed.

Anyone has a clue as to why is this happening?

(Paul, I'm cc'ing this to you since it seems to me like it may be
another problem with the new hdsp driver, not sure as of yet).

Ico



_______________________________________________________________
Hundreds of nodes, one monster rendering program.
Now that's a super model! Visit http://clustering.foundries.sf.net/

Re: Suse 8.0 Alsa CVS compile problem (possibly snd-hammerfall-mem problem?)

[Paul Davis]

>Hi all, I am having an odd problem with the ALSA cvs compile on SUSE
>8.0. I am trying to do this in order to get the hdsp driver. However,
>whenever I compile the driver it stores all the modules in the
>/lib/modules/2.4.18-4GB/ folder assuming that my kernel is 2.4.18-4GB.
>However, when I open the k control center it tells me that I am using
>2.4.18-64GB-SMP kernel (which makes no sense since I am using it on a
>single processor laptop).
>
>So, when I try to install the module for the built-in soundcard (intel
>8x0), it installs fine, but when I try to modprobe snd-hammerfall-mem,
>it fails saying that it has been compiled for the 2.4.18-4GB kernel and
>that I am using 2.4.18-64GB-SMP kernel -> hence the kernel mismatch ->
>modprobe failed.
>
>Anyone has a clue as to why is this happening?

k control center is broken.

simple enough?

as nice as these tools may be, they are not to be trusted in
situations like this. as regrettable as it may be, you need to be able
to use the actual toolset that k control center "wraps". if you still
get the error, i'll rescind my judgement.

--p

ps. ico - sorry i haven't logged into your machine yet. evidence from
another poster here suggests there are issues with the cardbus code in
the linux kernel right now (not related to ALSA or the H-DSP
driver). i'll do some more work on this next week.



_______________________________________________________________
Hundreds of nodes, one monster rendering program.
Now that's a super model! Visit http://clustering.foundries.sf.net/

Re: Suse 8.0 Alsa CVS compile problem (possibly snd-hammerfall-mem problem?)

[Takashi Iwai]

At Sun, 19 May 2002 22:08:06 -0400,
Ivica Bukvic wrote:
> 
> Hi all, I am having an odd problem with the ALSA cvs compile on SUSE
> 8.0. I am trying to do this in order to get the hdsp driver. However,
> whenever I compile the driver it stores all the modules in the
> /lib/modules/2.4.18-4GB/ folder assuming that my kernel is 2.4.18-4GB.
> However, when I open the k control center it tells me that I am using
> 2.4.18-64GB-SMP kernel (which makes no sense since I am using it on a
> single processor laptop).
> 
> So, when I try to install the module for the built-in soundcard (intel
> 8x0), it installs fine, but when I try to modprobe snd-hammerfall-mem,
> it fails saying that it has been compiled for the 2.4.18-4GB kernel and
> that I am using 2.4.18-64GB-SMP kernel -> hence the kernel mismatch ->
> modprobe failed.
> 
> Anyone has a clue as to why is this happening?

i guess the header files included in the kernel tree don't match with
the version of the kernel you're using.
as default, kernel-source package includes the configuration for the
default kernel (i.e. 2.4.18-4GB).

i recommend to replace the kernel with the default one instead of smp.
(it happens often that the installer chooses an smp kernel on pentium
 4 is found.)

or, if you insist to use the current smp kernel, copy the version.h
and autoconf.h under /boot directory (renamed with vmlinuz. prefix) to
/usr/src/linux/include/linux directory and reconfigure the driver,
clean and reinstall it.


Takashi

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm