Re: [Alsa-user] modprobe - unresolved symbols in snd.o
Brought to you by:
perex
From: Paul S. <so...@us...> - 2002-09-14 00:44:16
|
Fedor, Thanks again. modversions.h was indeed missing. After searching around for the source rpm on my system (I use up2date for updates and I am not sure how long downloaded packages are cached for) I just ran up2date again because the updates included 2.4.18-10 (and I chose only the athlon and source packages). After installing the new kernel and source the driver compiled no problems and modprobe snd-ens1371 went without a hitch. I can run alsaplayer with no errors. There is no sound so I am currently trying to unmute. Unfortuately the ./configure in alsa-utils barfed with the error "no linkable libasound was found", in actual fact it appears in /var/lib and running ./configure --libdir=/var/lib resulted in the same error. Without being able to compile the utils I am not sure how to unmute (KMix won't run anymore). sosman ----- Original Message ----- From: "Fedor G. Pikus" <fe...@wv...> To: "Paul Sorenson" <so...@us...> Sent: Friday, September 13, 2002 2:28 AM Subject: Re: [Alsa-user] modprobe - unresolved symbols in snd.o > This is an odd error to get. You are including > /usr/include/linux/modversions.h > when you should be including > /lib/modules/2.4.18-5/build/include/linux/modversions.h > > There can be only two explanations. > 1) Check that you have > /lib/modules/2.4.18-5/build/include/linux/modversions.h. It should contain > something like this: > #ifndef _LINUX_MODVERSIONS_H > #define _LINUX_MODVERSIONS_H > #include <linux/modsetver.h> > #include <linux/modules/53c700.ver> > .... lots of stuff > #endif > > If you do not have it, your kernel-source rpm is missing some files, > reinstall it. > If you do have it, something must be wrong in the results of .configure. > Remove your alsa-drivers directory, untar the tarball again (remove > isapnp.h as the web page says) and run .configure again (this is a bit too > drastic, you could probably just do make clean and remove config.cache, > config.log, and config.status). > > On Thu, 12 Sep 2002, Paul Sorenson wrote: > > > Date: Thu, 12 Sep 2002 18:09:20 +1000 > > From: Paul Sorenson <so...@us...> > > To: "Pikus, Fedor" <fed...@me...> > > Subject: Re: [Alsa-user] modprobe - unresolved symbols in snd.o > > > > Fidor, > > > > The bits and pieces. > > > > paul > > > > ----- Original Message ----- > > From: "Fedor G. Pikus" <fe...@wv...> > > To: "Paul Sorenson" <so...@us...> > > Cc: "alsa user" <als...@li...> > > Sent: Monday, September 09, 2002 4:25 PM > > Subject: Re: [Alsa-user] modprobe - unresolved symbols in snd.o > > > > > > > Hmm, hard to say. I compiled alsa 0.9rc3 against 2.4.18 Redhat kernel, > > > with Athlon config. > > > Could you post the output of "uname -a" and "ls -l /usr/src/"? > > > Also attach your /usr/src/linux/.config file (perhaps that one you can > > > send to me instead of the list, I want to diff it against mine to see if > > > there is something wrong there). > > > > > > -- > Fedor G. Pikus > Mentor Graphics Corporation | Phone: (503) 685-4857 > 8405 SW Boeckman Road | FAX: (503) 685-1239 > Wilsonville, Oregon 97070 | http://www.pikus.net/~pikus/ > |