Keep in mind you WILL need to remove the old modules either way, to avoid conflicts. Bjorn. --- Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: > While is shouldn't afffect functionality, a new > extra/ folder is the > preferred place for modules that don't come with the > distribution. > One can with root permission ( using sudo under > Ubuntu) first make a > temporary definition > SITE=/lib/modules/`uname -r`/extra > > Test with: > $ echo $SITE > /lib/modules/2.6.24-19-generic/extra > ---------- > for my system with 2.6.24-19-generic kernel > > Create the folder > $ sudo mkdir -p $SITE > > WIthin the folder in which the new drivers.ko are: > $ sudo cp*.ko $SITE/ > > Check > $ ls -l $SITE > should show agrmodem.ko & agrserial.ko > > MarvS > > On Fri, Jul 25, 2008 at 6:39 AM, Bjorn Wielens > <uniacke1@xxxxxxxx> wrote: > > Hi Max, > > ALSA-Lib shouldn't be a problem, since the symbols > are > > provided by the ALSA modules. > > The unknown symbols are probably because only the > > newer snd-hda-intel module is loaded, and not all > of > > the other newer ones. > > The newly made modules should all be copied to > > /lib/modules/(kernel version)/sound directory, if > I'm > > not mistaken. > > > > You can try copying the contents of that dir to a > safe > > place (e.g. your home directory) and then deleting > it. > > Then, fill it with the modules (.ko files ) in > (alsa > > source dir)/modules and run 'depmod -ae' to update > > dependencies. > > After this it should only load the new modules. > > Bjorn. > > > > > > > > --- Max <webmaster@xxxxxxxxxxxxxxxxxx> wrote: > > > >> I only installed alsa-driver, but system still > loads > >> older alsa driver, > >> after "make install" the new ones are copied in a > >> different folder. > >> I forced snd _hda_intel.ko and obtained lots of > >> unknown symbols in dmesg. > >> do I have to install alsa-lib before? > >> > >> > >> Thursday 24 July 2008 19:40:27 you wrote: > >> > Hi Max, > >> > Looks like you've got ALSA down pat (that's > half > >> the > >> > challenge). > >> > You shouldn't need any of the other tarballs > >> > (alsa-driver is the big one.) > >> > > >> > The modification to ALSA-driver is to edit the > >> file > >> > alsa-kernel/pci/hda/hda_codec.c (in the > >> alsa-driver > >> > source dir) > >> > and add the following two lines AFTER the > section > >> of > >> > '#include' statements at the beginning of the > >> file. > >> > these are the lines to add: > >> > > >> > EXPORT_SYMBOL(snd_hda_codec_read); > >> > EXPORT_SYMBOL(snd_hda_codec_write); > >> > > >> > Be wary of the trailing semicolons... Omitting > >> them > >> > will cause errors. > >> > > >> > After you've edited the file, rebuild the alsa > >> drivers > >> > (in the alsa-driver source dir) with the > following > >> > commands: > >> > 'make clean' > >> > 'make' > >> > and then 'sudo make install' > >> > (all minus quotes, wait for the previous > command > >> to > >> > finish cleanly (i.e. no errors, warnings are > OK) > >> > before moving on). > >> > > >> > After they're installed, reboot your machine to > >> > activate the new modules. Then, get this > tarball: > >> > > >> > > > http://linmodems.technion.ac.il/packages/ltmodem/11c11040/agrsm-HDA-2008072 > >> >1-ALSA15.tar.bz2 > >> > > >> > untar with 'tar -jxvf FILE_NAME' > >> > move into the directory, and do 'make module'. > >> > If you get any errors, be sure to paste the > output > >> of > >> > 'make module' in to your reply. > >> > > >> > After that is done, copy the two .ko files to > your > >> > modules directory as described in my earlier > HOWTO > >> > e-mail. After running 'sudo depmod -ae', you > >> should be > >> > able to do 'sudo modprobe agrmodem' and 'sudo > >> modprobe > >> > agrserial'after which /dev/ttyAGS3 will be the > >> port > >> > you can access your modem with. (for wvdial, > etc.) > >> > > >> > Good luck! > >> > Bjorn. > >> > > >> > --- Max <webmaster@xxxxxxxxxxxxxxxxxx> wrote: > >> > > Here I am again, > >> > > alsa-driver and alsa-lib 1.0.15rc3 (do I need > >> any > >> > > other alsa tarball?) > >> > > successfully compiled. > >> > > I didn't install them yet because, if I > >> understood, > >> > > they have to be modified > >> > > before compiling (am I right?). > >> > > Please let me know how I have to proceed. > >> > > Thanks again. > >> > > Max > >> > > > >> > > Thursday 24 July 2008 11:45:46 you wrote: > >> > > > Hi Max, > >> > > > That is quite likely. There are two > versions > >> of > >> > > > >> > > the > >> > > > >> > > > driver, and one relies on ALSA 1.0.16 or > 17, > >> the > >> > > > >> > > other > >> > > > >> > > > on 1.0.15 or earlier. > >> > > > You will, however, NEED to build ALSA from > the > >> > > > >> > > source > >> > > > >> > > > tarball, since we will be making > modifications > >> to > >> > > > >> > > the > >> > > > >> > > > ALSA code. > >> > > > At this point, I can offer two suggestions: > >> > > > 1. Try ALSA 1.0.15 from source > >> > > > (http://www.alsa-project.org) and see if > you > >> can > >> > > > >> > > get > >> > > > >> > > > it to compile. If so, let me know and we > can > >> > > > >> > > continue. > >> > > > >> > > > 2. Upgrade your kernel/OS and > kernel-sources > >> to a > >> > > > newer version (Say 2.6.22 or so. (The > driver > === message truncated === __________________________________________________________________ Yahoo! Canada Toolbar: Search from anywhere on the web, and bookmark your favourite sites. Download it now at http://ca.toolbar.yahoo.com.
