[update] MWA HAW HAW HAW HAW. I found them. To be sure I should have tried --with-cards=all (or maybe just the modules I need) to save myself days of frustration. It's surprising how the easy things never have any damn instructions available through the magic all-knowing google. It's just assumed it's so easy so no one mentions how to do it, then a noob like me spends a week wasting time. Sound works for the first time on this machine ( in any linux) Thanks everyone (especially eriefisher, for the hard work and the winning suggestion)
-----------------------------------------------------------------------------------------------------------------------------------------------------
Okay, so this is kind of a general linux question, and as such i will also post it on LinuxQuestions.org. I'm a bit of a noob (just a bit) and I've only compiled kernel modules once or twice. Only once did I load any, and it was an experimental one that broke my whole kernel. That's my background experience with modules.
Now, to the meat of my problem, I'm using a Thinkpad 600E (old, I know) and antiX has so far been the perfect OS for it (although I have unusual problems with dosbox.) This model uses a sound card that does not work with linux out of box, any linux, at all, ever. I found a guide that explains which kernel modules I need to load to enable sound, but i have no clue about how to go about getting these modules. I've been googling and I can't find anywhere to download it.
So I'm working under the assumption that the modules all come with the kernel source, and that I should be able to find the module source somewhere on my system to compile and load. With other distros I've tried on this system I never felt a need to get the sound working, because the performance wasn't up to scratch (except with Vector Linux, which was approaching the performance of antiX, but crashed too often) but now that my system seems like a real computer I need sound.
This is the"guide" I'm using:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.linuxquestions.org/linux/ans"
linktext was:"http://www.linuxquestions.org/linux/ans"
====================================
" onclick="window.open(this.href);return false ... nkpad_600E
Now this guy or gal just assumes we know how to use modules, which I know isn't necessarily an outrageous assumption, but being dumbass, this guide does not help me.
I appreciate any help this community might provide, seeing as I'm asking a n00bish question.
topic title: [SOLVED] Kernel Modules Needed!!!
15 posts
• Page 1 of 1
-
indubitablenessPosts: 13
- Joined: 04 Mar 2009
#1
Last edited by indubitableness on 09 Mar 2009, 10:21, edited 3 times in total.
-
eriefisherPosts: 1,520
- Joined: 07 Oct 2007
#2
The first thing I would do is open the terminal and as root run alsaconf. This may or may not work. You may need to install oss via synaptic as well. If all else fails then contact the author of the how to you linked to for clarity.
-
indubitablenessPosts: 13
- Joined: 04 Mar 2009
#3
Cool, thanks eriefisher for the tips.
After I posted this problem here yesterday i went on to spend pretty much the rest of the night working on this. I think maybe I don't need all the modules mentioned in the how to I was using, but I don't know for sure.
I ended up getting my best lead from the alsa home page itself, I went and looked at their supported sound card section and found my card supported (I need the snd-cs4236 module)
The procedure I followed was far from clean, I forgot to uninstall alsa and related utilities before i started compiling and installing alsa from scratch. I was able to get the cs4236 module available when I used alsaconf from the CLI, but it did not load.
This of course was after i compiled the alsa-driver-1.0.19, alsa-lib, and alsa-utils packages and installed them (all 1.0.19) or tried to install them anyway, the alsa-utils package errors out when it gets to building alsamixer when i issue the make command.
I'm working with assumptions here, and i'm hoping the error is caused by conflicts or something with the previously installed alsa packages, but something makes me doubt it.
This time i'm going to try the same procedure, but i'm going to do it cleanly, and if that fails in the same way i guess i'll post the errors i get during the make process and see if anyone can help me figure out what's going on, it's all sorts of messages about how such and such can't be reduced to an integer, which is way above my head.
If all else fails i'll try to compile a kernel with support for my card configured as part of it.
Thanks for your help guys.
After I posted this problem here yesterday i went on to spend pretty much the rest of the night working on this. I think maybe I don't need all the modules mentioned in the how to I was using, but I don't know for sure.
I ended up getting my best lead from the alsa home page itself, I went and looked at their supported sound card section and found my card supported (I need the snd-cs4236 module)
The procedure I followed was far from clean, I forgot to uninstall alsa and related utilities before i started compiling and installing alsa from scratch. I was able to get the cs4236 module available when I used alsaconf from the CLI, but it did not load.
This of course was after i compiled the alsa-driver-1.0.19, alsa-lib, and alsa-utils packages and installed them (all 1.0.19) or tried to install them anyway, the alsa-utils package errors out when it gets to building alsamixer when i issue the make command.
I'm working with assumptions here, and i'm hoping the error is caused by conflicts or something with the previously installed alsa packages, but something makes me doubt it.
This time i'm going to try the same procedure, but i'm going to do it cleanly, and if that fails in the same way i guess i'll post the errors i get during the make process and see if anyone can help me figure out what's going on, it's all sorts of messages about how such and such can't be reduced to an integer, which is way above my head.
If all else fails i'll try to compile a kernel with support for my card configured as part of it.
Thanks for your help guys.
-
eriefisherPosts: 1,520
- Joined: 07 Oct 2007
#4
You maybe missing a dev package if your compiling. Post the error for a look.
The"CS" modules are not included in the debian kernels because they are NON-FREE and therefore against the debian social contract or what ever they call it. The errors you get should be a hint as to what you need to successfully compile it.
The"CS" modules are not included in the debian kernels because they are NON-FREE and therefore against the debian social contract or what ever they call it. The errors you get should be a hint as to what you need to successfully compile it.
-
indubitablenessPosts: 13
- Joined: 04 Mar 2009
#5
I've been using the source available from the ALSA home page. I am following the procedure outlined here:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.alsa-project.org/main/index"
linktext was:"http://www.alsa-project.org/main/index"
====================================
" onclick="window.open(this.href);return false. ... ule-cs4236
Here is the error I've been getting:
Thanks again.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.alsa-project.org/main/index"
linktext was:"http://www.alsa-project.org/main/index"
====================================
" onclick="window.open(this.href);return false. ... ule-cs4236
Here is the error I've been getting:
I hope it's missing devs, 'cause would explain a lot. At one point making the alsa-utils i had an error because i was missin xmlto, which i downloaded. Last time I tried this I tried"make -i" and it compiled everything after the alsamixer errors just fine.[update] I have removed this code to make this page more eye friendly, no further analyses of these error messages is required
Thanks again.
Last edited by indubitableness on 07 Mar 2009, 12:37, edited 1 time in total.
-
OU812Posts: 1,081
- Joined: 29 Sep 2007
#6
There may have been errors during the ./configure step. There should bea config.log file in the alsamixer folder that you dl'd - it of course is created during the config step. There might be something useful there.
john
john
-
indubitablenessPosts: 13
- Joined: 04 Mar 2009
#7
Thanks OU812, I just checked the log and found that there are indeed errors during the configuration. They are, however errors I don't understand.
This is the section of code that has errors in it
My googling of some of the errors have yielded only other people's config.log files and no mention of dev packages or anything. It seems that google always fails me when i need to actually make progress on something, but if i have some frivolous question it's reliable.... strange. Who would've thought the internet would contain frivolous information?
For now, since i was able to compile and install both the driver and lib packages i'm going to aptitude install the alsa-utils package again and run alsaconf. I'll post the results.
[update] well I reinstalled the the alsa-utils, and i don't think i need to even compile them anymore anyway (although i'd still like to) and i ran alsaconf. after telling it to use the cs4236 it tried to configure it and ended up giving me a"no legacy cards found" message at the end... awesome, just friggen awesome.
alsaconf failed at unloading the sound modules when it first started though, so maybe that's the problem.
Here is the error message i've always received from alsamixer no matter the distro i've used:
"alsamixer: function snd_ctl_open failed for default: No such device"
Like i said, this message is one i'm very used to seeing on this machine, as i've never had sound in linux on it.
I think i may need to change the name of the topic from"Kernel Modules needed" to something more relevant. I have a feeling that I can spend months on this and i'll still come out with no sound.
[update to the update] apparently i'm working with the wrong module entirely. While the alsa website says my card requires the cs4236 driver, the guide that supposedly works says i need the cs4232 driver. Soooo, i tried that, and i got an error message about no UART401 available, a quick search showed me that this is apparently part of the alsa-oss package, which i have just installed. more updates to come.
This is the section of code that has errors in it
So I'm assuming I've got to get this CFPreferences.h deal set up where it's supposed to be, and I'm also assuming this probably requires some kind of dev package or something (I'm really hoping so anyway, as that would be an easy"aptitude install something important" fix.)configure:4327: checking for CFPreferencesCopyAppValue
configure:4355: gcc -o conftest -g -O2 conftest.c -Wl,-framework -Wl,CoreFoundation >&5
conftest.c:10:42: error: CoreFoundation/CFPreferences.h: No such file or directory
conftest.c: In function 'main':
conftest.c:14: error: 'NULL' undeclared (first use in this function)
conftest.c:14: error: (Each undeclared identifier is reported only once
conftest.c:14: error: for each function it appears in.)
configure:4361: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME""
| #define PACKAGE_TARNAME""
| #define PACKAGE_VERSION""
| #define PACKAGE_STRING""
| #define PACKAGE_BUGREPORT""
| #define PACKAGE"alsa-utils"
| #define VERSION"1.0.19"
| /* end confdefs.h. */
| #include <CoreFoundation/CFPreferences.h>
| int
| main ()
| {
| CFPreferencesCopyAppValue(NULL, NULL)
| ;
| return 0;
| }
configure:4395: result: no
configure:4404: checking for CFLocaleCopyCurrent
configure:4432: gcc -o conftest -g -O2 conftest.c -Wl,-framework -Wl,CoreFoundation >&5
conftest.c:10:37: error: CoreFoundation/CFLocale.h: No such file or directory
configure:4438: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME""
| #define PACKAGE_TARNAME""
| #define PACKAGE_VERSION""
| #define PACKAGE_STRING""
| #define PACKAGE_BUGREPORT""
| #define PACKAGE"alsa-utils"
| #define VERSION"1.0.19"
| /* end confdefs.h. */
| #include <CoreFoundation/CFLocale.h>
| int
| main ()
| {
| CFLocaleCopyCurrent();
| ;
| return 0;
| }
configure:4472: result: no
configure:4503: checking for GNU gettext in libc
configure:4532: gcc -o conftest -g -O2 conftest.c >&5
configure:4538: $? = 0
configure:4545: test -z"$ac_c_werror_flag" || test ! -s conftest.err
configure:4548: $? = 0
configure:4555: test -s conftest
configure:4558: $? = 0
configure:4571: result: yes
configure:5334: checking whether to use NLS
configure:5336: result: yes
configure:5339: checking where the gettext function comes from
configure:5350: result: libc
configure:5416: checking for cross-compiler
configure:5425: result: gcc
configure:5477: checking for gcc
configure:5504: result: gcc
configure:5742: checking for C compiler version
configure:5749: gcc --version >&5
gcc (Debian 4.3.2-1.1) 4.3.2
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:5752: $? = 0
configure:5759: gcc -v >&5
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.2-1.1' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --enable-cld --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
Thread model: posix
gcc version 4.3.2 (Debian 4.3.2-1.1)
configure:5762: $? = 0
configure:5769: gcc -V >&5
gcc: '-V' option must have argument
configure:5772: $? = 1
configure:5775: checking whether we are using the GNU C compiler
configure:5844: result: yes
configure:5849: checking whether gcc accepts -g
configure:6035: result: yes
configure:6052: checking for gcc option to accept ISO C89
configure:6172: result: none needed
configure:6192: checking dependency style of gcc
configure:6282: result: gcc3
configure:6312: checking for a BSD-compatible install
configure:6368: result: /usr/bin/install -c
configure:6379: checking whether ln -s works
configure:6383: result: yes
configure:6421: checking for ALSA CFLAGS
configure:6427: result:
configure:6430: checking for ALSA LDFLAGS
configure:6439: result: -lasound -lm -ldl -lpthread
configure:6443: checking for libasound headers version >= 1.0.16
configure:6515: gcc -c -g -O2 conftest.c >&5
configure:6521: $? = 0
configure:6528: test -z"$ac_c_werror_flag" || test ! -s conftest.err
configure:6531: $? = 0
configure:6538: test -s conftest.o
configure:6541: $? = 0
configure:6543: result: found.
configure:6568: checking for snd_ctl_open in -lasound
configure:6603: gcc -o conftest -g -O2 conftest.c -lasound -lasound -lm -ldl -lpthread >&5
configure:6609: $? = 0
configure:6616: test -z"$ac_c_werror_flag" || test ! -s conftest.err
configure:6619: $? = 0
configure:6626: test -s conftest
configure:6629: $? = 0
configure:6643: result: yes
configure:6744: checking for xmlto
configure:6771: result: yes
configure:6797: checking how to run the C preprocessor
configure:6837: gcc -E conftest.c
configure:6843: $? = 0
configure:6881: gcc -E conftest.c
conftest.c:14:28: error: ac_nonexistent.h: No such file or directory
configure:6887: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME""
| #define PACKAGE_TARNAME""
| #define PACKAGE_VERSION""
| #define PACKAGE_STRING""
| #define PACKAGE_BUGREPORT""
| #define PACKAGE"alsa-utils"
| #define VERSION"1.0.19"
| #define ENABLE_NLS 1
| #define HAVE_GETTEXT 1
| #define HAVE_DCGETTEXT 1
| #define HAVE_LIBASOUND 1
| /* end confdefs.h. */
| #include <ac_nonexistent.h>
configure:6927: result: gcc -E
configure:6956: gcc -E conftest.c
configure:6962: $? = 0
configure:7000: gcc -E conftest.c
conftest.c:14:28: error: ac_nonexistent.h: No such file or directory
configure:7006: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME""
| #define PACKAGE_TARNAME""
| #define PACKAGE_VERSION""
| #define PACKAGE_STRING""
| #define PACKAGE_BUGREPORT""
| #define PACKAGE"alsa-utils"
| #define VERSION"1.0.19"
| #define ENABLE_NLS 1
| #define HAVE_GETTEXT 1
| #define HAVE_DCGETTEXT 1
| #define HAVE_LIBASOUND 1
| /* end confdefs.h. */
| #include <ac_nonexistent.h>
configure:7051: checking for grep that handles long lines and -e
configure:7125: result: /bin/grep
configure:7130: checking for egrep
configure:7208: result: /bin/grep -E
configure:7213: checking for ANSI C header files
configure:7243: gcc -c -g -O2 conftest.c >&5
configure:7249: $? = 0
configure:7256: test -z"$ac_c_werror_flag" || test ! -s conftest.err
configure:7259: $? = 0
configure:7266: test -s conftest.o
configure:7269: $? = 0
configure:7365: gcc -o conftest -g -O2 conftest.c -lasound -lm -ldl -lpthread >&5
configure:7368: $? = 0
configure:7374: ./conftest
configure:7377: $? = 0
configure:7394: result: yes
configure:7543: checking for ncurses5-config
configure:7559: found /usr/bin/ncurses5-config
configure:7570: result: yes
configure:7796: checking for an ANSI C-conforming const
configure:7871: gcc -c -g -O2 conftest.c >&5
configure:7877: $? = 0
configure:7884: test -z"$ac_c_werror_flag" || test ! -s conftest.err
configure:7887: $? = 0
configure:7894: test -s conftest.o
configure:7897: $? = 0
configure:7909: result: yes
configure:7919: checking for inline
configure:7945: gcc -c -g -O2 conftest.c >&5
configure:7951: $? = 0
configure:7958: test -z"$ac_c_werror_flag" || test ! -s conftest.err
configure:7961: $? = 0
configure:7968: test -s conftest.o
configure:7971: $? = 0
configure:7986: result: inline
configure:8005: checking whether time.h and sys/time.h may both be included
configure:8035: gcc -c -g -O2 conftest.c >&5
configure:8041: $? = 0
configure:8048: test -z"$ac_c_werror_flag" || test ! -s conftest.err
configure:8051: $? = 0
configure:8058: test -s conftest.o
configure:8061: $? = 0
configure:8073: result: yes
configure:8085: checking whether gcc needs -traditional
configure:8127: result: no
configure:8142: checking for special C compiler options needed for large files
configure:8269: result: no
configure:8275: checking for _FILE_OFFSET_BITS value needed for large files
configure:8311: gcc -c -g -O2 conftest.c >&5
conftest.c:24: warning: left shift count >= width of type
conftest.c:24: warning: left shift count >= width of type
conftest.c:26: error: size of array 'off_t_is_large' is negative
configure:8317: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME""
| #define PACKAGE_TARNAME""
| #define PACKAGE_VERSION""
| #define PACKAGE_STRING""
| #define PACKAGE_BUGREPORT""
| #define PACKAGE"alsa-utils"
| #define VERSION"1.0.19"
| #define ENABLE_NLS 1
| #define HAVE_GETTEXT 1
| #define HAVE_DCGETTEXT 1
| #define HAVE_LIBASOUND 1
| #define STDC_HEADERS 1
| #define SOUNDSDIR"/usr/share/sounds/alsa"
| #define DATADIR"/usr/share/alsa"
| #define TIME_WITH_SYS_TIME 1
| /* end confdefs.h. */
| #include <sys/types.h>
| /* Check that off_t can represent 2**63 - 1 correctly.
| We can't simply define LARGE_OFF_T to be 9223372036854775807,
| since some C++ compilers masquerading as C compilers
| incorrectly reject 9223372036854775807. */
| #define LARGE_OFF_T (((off_t) 1 << 62) - 1 + ((off_t) 1 << 62))
| int off_t_is_large[(LARGE_OFF_T % 2147483629 == 721
| && LARGE_OFF_T % 2147483647 == 1)
| ? 1 : -1];
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:8378: gcc -c -g -O2 conftest.c >&5
configure:8384: $? = 0
configure:8391: test -z"$ac_c_werror_flag" || test ! -s conftest.err
configure:8394: $? = 0
configure:8401: test -s conftest.o
configure:8404: $? = 0
configure:8418: result: 64
configure:8428: checking for _LARGE_FILES value needed for large files
configure:8464: gcc -c -g -O2 conftest.c >&5
configure:8470: $? = 0
configure:8477: test -z"$ac_c_werror_flag" || test ! -s conftest.err
configure:8480: $? = 0
configure:8487: test -s conftest.o
configure:8490: $? = 0
configure:8571: result: no
configure:8745: creating ./config.status
## ---------------------- ##
## Running config.status. ##
## ---------------------- ##
My googling of some of the errors have yielded only other people's config.log files and no mention of dev packages or anything. It seems that google always fails me when i need to actually make progress on something, but if i have some frivolous question it's reliable.... strange. Who would've thought the internet would contain frivolous information?
For now, since i was able to compile and install both the driver and lib packages i'm going to aptitude install the alsa-utils package again and run alsaconf. I'll post the results.
[update] well I reinstalled the the alsa-utils, and i don't think i need to even compile them anymore anyway (although i'd still like to) and i ran alsaconf. after telling it to use the cs4236 it tried to configure it and ended up giving me a"no legacy cards found" message at the end... awesome, just friggen awesome.
alsaconf failed at unloading the sound modules when it first started though, so maybe that's the problem.
Here is the error message i've always received from alsamixer no matter the distro i've used:
"alsamixer: function snd_ctl_open failed for default: No such device"
Like i said, this message is one i'm very used to seeing on this machine, as i've never had sound in linux on it.
I think i may need to change the name of the topic from"Kernel Modules needed" to something more relevant. I have a feeling that I can spend months on this and i'll still come out with no sound.
[update to the update] apparently i'm working with the wrong module entirely. While the alsa website says my card requires the cs4236 driver, the guide that supposedly works says i need the cs4232 driver. Soooo, i tried that, and i got an error message about no UART401 available, a quick search showed me that this is apparently part of the alsa-oss package, which i have just installed. more updates to come.
Last edited by indubitableness on 06 Mar 2009, 04:28, edited 1 time in total.
-
eriefisherPosts: 1,520
- Joined: 07 Oct 2007
#8
I had a look at alsa, I decided to try and compile it to recreate your errors however it compiled fine. Instead of make install I used check install to create a .deb as i did not want to install it. I would try
Code: Select all
./configure --with-cards=all
make
make install-
indubitablenessPosts: 13
- Joined: 04 Mar 2009
#9
Took a short break from this. Coming back to it now I see I do not in fact need to change the topic name. I'm very close to solving this one. Although I'm still not sure why alsa-utils won't compile alsamixer (alsa-driver compiles fine, although I haven't tried the --with-cards=all parameter yet)
I did discover that as long as i can install alsa-utils from the repos, i don't need to compile that particular package. It was just the driver package i needed so i could get my cs4236 and or cs4232 modules (it's cs4232 i actually NEED, although cs4236 is allegedly the correct driver)
Here's what I need to make any further progress. I need the uart401 module, and I need the ad1848 module. Now, from my unsuccessful googlings i've come across reference to the uart401 module in relation to OSS, but i wouldn't know how to get ahold of nor compile this module.Got the same situation with the ad1848 module.
Someone in a chat room posted a link that i don't understand how to use:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://lxr.free-electrons.com/source/sound/oss/uart401.c"
linktext was:"http://lxr.free-electrons.com/source/so ... /uart401.c"
====================================
" onclick="window.open(this.href);return false
I understand this to be the source code for the module, but I don't understand how to use the source. I guess i'd make a makefile or something? There must be a more ready to compile package that comes with a configure script or something somewhere, right? Or perhaps it's part of the alsa-oss (or some other package's) source and i would choose to compile this module when configuring (ie --with-mod=uart401 style)
The guy who posted this link disappeared after posting it. I don't even think he meant it for me, although i was there asking about the module.
As for the ad1848 module, i don't have any good leads, but neither have i spent as much time looking for it.
I have also contacted the original author of the post that outlines this solution (using these modules) and asked him or her where i can get them, so far no reply, but it's only been a day.
Thanks again y'all.
I did discover that as long as i can install alsa-utils from the repos, i don't need to compile that particular package. It was just the driver package i needed so i could get my cs4236 and or cs4232 modules (it's cs4232 i actually NEED, although cs4236 is allegedly the correct driver)
Here's what I need to make any further progress. I need the uart401 module, and I need the ad1848 module. Now, from my unsuccessful googlings i've come across reference to the uart401 module in relation to OSS, but i wouldn't know how to get ahold of nor compile this module.Got the same situation with the ad1848 module.
Someone in a chat room posted a link that i don't understand how to use:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://lxr.free-electrons.com/source/sound/oss/uart401.c"
linktext was:"http://lxr.free-electrons.com/source/so ... /uart401.c"
====================================
" onclick="window.open(this.href);return false
I understand this to be the source code for the module, but I don't understand how to use the source. I guess i'd make a makefile or something? There must be a more ready to compile package that comes with a configure script or something somewhere, right? Or perhaps it's part of the alsa-oss (or some other package's) source and i would choose to compile this module when configuring (ie --with-mod=uart401 style)
The guy who posted this link disappeared after posting it. I don't even think he meant it for me, although i was there asking about the module.
As for the ad1848 module, i don't have any good leads, but neither have i spent as much time looking for it.
I have also contacted the original author of the post that outlines this solution (using these modules) and asked him or her where i can get them, so far no reply, but it's only been a day.
Thanks again y'all.
-
eriefisherPosts: 1,520
- Joined: 07 Oct 2007
#10
If the driver compiles and installs ok then try to install alsa-oss from the repos. Once everything is installed run"alsaconf" to see if the card is detected.
-
indubitablenessPosts: 13
- Joined: 04 Mar 2009
#11
already tried that eriefisher, thanks anyway. Like i said, i know which modules i need to make any further progress, i just don't know how to get them.
I need uart401 and i need ad1848, and i need to compile them myself i'm sure.
Those are the only modules i need to make any further progress, and i'm not entirely convinced that i need the ad1848, but i want to get it anyway in case i'm wrong. Like i said though, i can't figure out what package these modules are part of or how to compile them.
[edit] Here's the error messages i get at the end of alsaconf, just so you know.
I need uart401 and i need ad1848, and i need to compile them myself i'm sure.
Those are the only modules i need to make any further progress, and i'm not entirely convinced that i need the ad1848, but i want to get it anyway in case i'm wrong. Like i said though, i can't figure out what package these modules are part of or how to compile them.
[edit] Here's the error messages i get at the end of alsaconf, just so you know.
Alsaconf is apparently GOING to work once i get the modules i need. until i get them though, any suggestion to use alsaconf is futile. Thanks anyway, but I've been working on this for days. I've tried all the standard stuff.Loading driver...
WARNING: Error inserting snd_mpu401_uart (/lib/modules/2.6.27-1-mepis-smp/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko): Unknown symbol in module, or unknown parameter (see dmesg)
WARNING: Error inserting snd_mpu401_uart (/lib/modules/2.6.27-1-mepis-smp/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting snd_cs4232 (/lib/modules/2.6.27-1-mepis-smp/kernel/sound/isa/cs423x/snd-cs4232.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error running install command for snd_cs4232
Setting default volumes...
amixer: Mixer attach default error: No such file or directory
Saving the mixer setup used for this in /var/lib/alsa/asound.state.
/usr/sbin/alsactl: save_state:1497: No soundcards found...
-
eriefisherPosts: 1,520
- Joined: 07 Oct 2007
#12
What does dmesg say? That module should be part of alsa.Unknown symbol in module, or unknown parameter (see dmesg)
-
indubitablenessPosts: 13
- Joined: 04 Mar 2009
#13
dmesg actually says quite a bit. I guess it's supposed to.
If this module is part of the alsa package then there must be a way i can compile it myself. would it be part of the --with-cards= parameter? I'll give it a shot.
Here's everything it says reguarding the sound modules:
If this module is part of the alsa package then there must be a way i can compile it myself. would it be part of the --with-cards= parameter? I'll give it a shot.
Here's everything it says reguarding the sound modules:
snd_mpu401_uart: Unknown symbol snd_rawmidi_receive
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_ack
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_peek
snd_mpu401_uart: Unknown symbol snd_rawmidi_new
snd_mpu401_uart: Unknown symbol snd_rawmidi_set_ops
ath_pci: wifi0: Atheros 2413: mem=0x14000000, irq=11
snd_mpu401_uart: Unknown symbol snd_rawmidi_receive
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_ack
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_peek
snd_mpu401_uart: Unknown symbol snd_rawmidi_new
snd_mpu401_uart: Unknown symbol snd_rawmidi_set_ops
snd_cs4232: Unknown symbol snd_mpu401_uart_new
snd_mpu401_uart: Unknown symbol snd_rawmidi_receive
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_ack
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_peek
snd_mpu401_uart: Unknown symbol snd_rawmidi_new
snd_mpu401_uart: Unknown symbol snd_rawmidi_set_ops
snd_mpu401_uart: Unknown symbol snd_rawmidi_receive
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_ack
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_peek
snd_mpu401_uart: Unknown symbol snd_rawmidi_new
snd_mpu401_uart: Unknown symbol snd_rawmidi_set_ops
snd_mpu401_uart: Unknown symbol snd_rawmidi_receive
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_ack
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_peek
snd_mpu401_uart: Unknown symbol snd_rawmidi_new
snd_mpu401_uart: Unknown symbol snd_rawmidi_set_ops
snd_mpu401_uart: Unknown symbol snd_rawmidi_receive
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_ack
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_peek
snd_mpu401_uart: Unknown symbol snd_rawmidi_new
snd_mpu401_uart: Unknown symbol snd_rawmidi_set_ops
snd_cs4232: Unknown symbol snd_mpu401_uart_new
snd_cs4232: Unknown symbol snd_mpu401_uart_new
snd_mpu401_uart: Unknown symbol snd_rawmidi_receive
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_ack
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_peek
snd_mpu401_uart: Unknown symbol snd_rawmidi_new
snd_mpu401_uart: Unknown symbol snd_rawmidi_set_ops
snd_mpu401_uart: Unknown symbol snd_rawmidi_receive
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_ack
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_peek
snd_mpu401_uart: Unknown symbol snd_rawmidi_new
snd_mpu401_uart: Unknown symbol snd_rawmidi_set_ops
snd_cs4232: Unknown symbol snd_mpu401_uart_new
snd_mpu401_uart: Unknown symbol snd_rawmidi_receive
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_ack
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_peek
snd_mpu401_uart: Unknown symbol snd_rawmidi_new
snd_mpu401_uart: Unknown symbol snd_rawmidi_set_ops
snd_mpu401_uart: Unknown symbol snd_rawmidi_receive
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_ack
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_peek
snd_mpu401_uart: Unknown symbol snd_rawmidi_new
snd_mpu401_uart: Unknown symbol snd_rawmidi_set_ops
snd_cs4232: Unknown symbol snd_mpu401_uart_new
snd_mpu401_uart: Unknown symbol snd_rawmidi_receive
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_ack
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_peek
snd_mpu401_uart: Unknown symbol snd_rawmidi_new
snd_mpu401_uart: Unknown symbol snd_rawmidi_set_ops
snd_mpu401_uart: Unknown symbol snd_rawmidi_receive
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_ack
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_peek
snd_mpu401_uart: Unknown symbol snd_rawmidi_new
snd_mpu401_uart: Unknown symbol snd_rawmidi_set_ops
snd_cs4232: Unknown symbol snd_mpu401_uart_new
snd_mpu401_uart: Unknown symbol snd_rawmidi_receive
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_ack
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_peek
snd_mpu401_uart: Unknown symbol snd_rawmidi_new
snd_mpu401_uart: Unknown symbol snd_rawmidi_set_ops
snd_mpu401_uart: Unknown symbol snd_rawmidi_receive
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_ack
snd_mpu401_uart: Unknown symbol snd_rawmidi_transmit_peek
snd_mpu401_uart: Unknown symbol snd_rawmidi_new
snd_mpu401_uart: Unknown symbol snd_rawmidi_set_ops
snd_cs4232: Unknown symbol snd_mpu401_uart_new
-
eriefisherPosts: 1,520
- Joined: 07 Oct 2007
#14
So the --with-cards=all worked? or was there something else as well?
-
indubitablenessPosts: 13
- Joined: 04 Mar 2009
#15
Well I also used the --with-sequencer=yes paramter. I've used Vector Linux, which comes with these modules, and i've had alsaconf fail me plenty. I can only assume the --with-sequencer option helped, as i've never encountered any of the errors i've seen this time arond (except the alsamixer error, not the compile errors but the one i used to get when running alsamixer)
I never tried this hard to get it to run either, though, so I can't be sure exactly what variables prevented sound from working in other distros which come with these modules out of box.
I never tried this hard to get it to run either, though, so I can't be sure exactly what variables prevented sound from working in other distros which come with these modules out of box.