From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: Suse 8.0 Alsa CVS compile problem (possibly snd-hammerfall-mem problem?) Date: Tue, 21 May 2002 12:38:59 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <000401c1ffa3$302e0900$ac1f830a@ico> Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <000401c1ffa3$302e0900$ac1f830a@ico> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Ivica Bukvic Cc: alsa-devel@lists.sourceforge.net, alsa-user@lists.sourceforge.net, 'Paul Davis' List-Id: alsa-devel@alsa-project.org 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