Add Module, ALSA

qwijibow · 08-15-2004, 04:49 PM

recompile alsa-driver should fic the symbols error...
whatever went wrong here, its a confufing mess.

PhuckFonix · 08-16-2004, 12:14 PM

I removed the RPM package of alsa-utils and compiled the downloaded alsa-utils according to the INSTALL instructions, I will reboot, and report.

UPDATE: I am warned on startup that there are problems. Can I print to file(if so how?) the startup dialogue that eventually leads to my desktop environment being booted. I think the inetd executed messages, please correct me if I'm wrong.

I will try recompiling everything in order of lib, utils, drivers. I will first check for any other RPM alsa installed.

UPDATE(2): THERE IS A HUGE AMOUNT OF DEPENDENCY ON libalsa....

kevinalm · 08-16-2004, 12:43 PM

Install order is:
1. alsa-driver (or the alsa modules from a kernel compile make modules_install, whichever you want to use)
2. alsa-lib
3. alsa-utils

alsa-driver installs userland headers that are needed for alsa-lib which in turn is needed by alsa-utils.

qwijibow · 08-16-2004, 03:39 PM

sooo.... you installed alsa via rpm... problem solved.. you MUST have installed the wrong RPM's

the thing about drivers, is they have to compiled for your exact kernel.. which is why you should ALWAYS compile drivers yourself.

PhuckFonix · 08-16-2004, 03:46 PM

Well, I compiled everything but I do not know how to properly configure /etc/module.conf

kevinalm · 08-16-2004, 04:39 PM

alsaconf is supposed (among other things) to edit /etc/modules.conf for you, that is if
it succeeds in finding and configuring you card.

PhuckFonix · 08-16-2004, 07:35 PM

alsaconf gives me about ten options in cards, I think there should be a lot more options, no?

qwijibow · 08-16-2004, 09:13 PM

AGH ! first you ay u compiled everything, then you say you installed by RPM, now u say u compiled everything again!!!!

alsaconf gives 10 options !!!!! how many sound cards do you have !!!!!!!
there should be as many options as ou have cards and driver for !!!!

somthing is seriously wrong.

PhuckFonix · 08-16-2004, 10:48 PM

In the beginning... there was man... man installed RPM then he kinda compiled and installed alsa-driver, then he killed his first installation RPM, and for this he was banished to the land of Nod. There started a family, for which he compiled and installed all alsa files. Afterwhich he named his children, respectively: the eldest, Driver; the middle-one, Lib; and his youngest Utils. And for his family, he wanted to install a sound card. Alsaconf gave him only 10 card types to probe for. No cards were his. Alas, ALSA!

kevinalm · 08-16-2004, 11:59 PM

10 options in cards? Uh, back the truck up, something fell off.

The alsaconf command is supposed to automatically find and configure pci cards automatically. Irrc, there is an option to search for "isa legacy" or some such, is that where you found the options? You do know that alsaconf must be run as root, yes?

Is your card isa, pci or integrated on mb? If it's pci, do:

lspci

to verify the chip used.

PhuckFonix · 08-17-2004, 10:28 AM

Code:

lspci
01:08.0 Multimedia audio controller: Rockwell International: Unknown device 4310
01:08.1 Communication controller: Rockwell International Riptide HSF 56k PCI Modem
01:08.2 Input device controller: Rockwell International: Unknown device 4312

First it searches sound cards and says:

Quote:

No supported PnP or PCI card found
Would you like to probe Legacy ISA sound card/chip?

Then

Quote:

[X} opl3sa2 Yamaha OPL3SA2+
[X] cs4236 Cirrus Logic CS4235-9
[X] cs4232 Cirrus Logic CS4232
[X] es18xx ESS ES18xx AudioDrive
[X] es1688 ESS ESx688 AudioDrive
[X] sb16 Sound Blaster 16
[X] sb8 Sound Blaster 1.0/2.0/Pro
< OK > <Cancel>

The result is that no legacy cards have been found.

qwijibow · 08-17-2004, 07:27 PM

what !!! its an ISA sound card !!!!!
sorry, i just naturally assumed you were using a machine made this end of the ice age... lol.

sorry, i dont know what the policy on how long the kernel keeps support for anchant hardware.

kevinalm · 08-18-2004, 12:13 AM

Uh oh, you have one of those Riptide modem/soundcard combo's. That could explain a lot. You will have to go to the linuxant site.
They do have drivers, bad news is that if you want to use the modem at full 56k you have to pay $20 US or so. The free version is
crippled to 26k iirc. Don't know if the sound driver is alsa or oss.

You have my sympithies. It have an HCF modem. Finally gave up and bought an external com port modem.

Your sound/modem is pci by the way.

PhuckFonix · 08-20-2004, 12:52 PM

I downloaded and extracted the riptide files. I am under gentoo. I don't need modem support anyways. I have broadband : )

Quote:

make install
make[1]: Entering directory `/home/usuario/riptide-0.6lnxtbeta03122800/scripts'
install -m 755 ripconfig ripstop /usr/sbin
make[1]: Leaving directory `/home/usuario/riptide-0.6lnxtbeta03122800/scripts'
make[1]: Entering directory `/home/usuario/riptide-0.6lnxtbeta03122800/modules'
rm -rf "/usr/lib/riptide/config.mak" "/usr/lib/riptide/modules"
mkdir -m 755 -p /usr/lib/riptide/modules
prevsum=""; md5sum `find binaries -type f -print` </dev/null | sort | while read sum file ; do \
if [ "$sum" = "$prevsum" ] && cmp -s "$file" "$prevfile"; then \
rm -f "$file"; \
ln "$prevfile" "$file"; \
else \
prevsum="$sum"; \
prevfile="$file"; \
fi; \
done
(cd .. && find config.mak -depth -print | cpio -pdm /usr/lib/riptide)
2 blocks
find . $ -name '*.sh' -o -name '*.[ch]' -o -name '*.mak' -o -name '[Mm]akefile' $ -print | cpio -pdm /usr/l
ib/riptide/modules
580 blocks
find binaries -depth -print | cpio -pdm /usr/lib/riptide/modules
0 blocks
make[1]: Leaving directory `/home/usuario/riptide-0.6lnxtbeta03122800/modules'
install -m 444 LICENSE riptide.hex /usr/lib/riptide

To complete the installation and configuration of your RIPTIDE board,
please run "ripconfig" (or "/usr/sbin/ripconfig")
bash-2.05b# ripconfig
Linux RIPTIDE audio/communication drivers, version 0.6lnxtbeta03122800

WARNING: this is an EXPERIMENTAL BETA VERSION of the RIPTIDE drivers for Linux.
USE AT YOUR OWN RISK! See the file /usr/lib/riptide/LICENSE for details.

Conexant Systems neither distributes nor maintains this package.
PLEASE DO NOT CONTACT CONEXANT REGARDING THIS SOFTWARE!!!

If you require assistance or need more information, go to:
http://www.linuxant.com/drivers

When reporting a problem for the first time, please send
us the file generated by "ripconfig --dumpdiag".
grep: /proc/ksyms: No such file or directory
/usr/sbin/ripconfig: line 499: [: too many arguments

This package does not contain pre-built modules suitable for your system:
Distribution: unknown-unknown
Kernel arch: i686
Kernel version: linux-2.6.7-gentoo-r14

Trying to automatically re-compile the modules..
(this requires a C compiler and proper kernel sources to be installed)

Where is the linux source build directory that matches your running kernel?
[/lib/modules/2.6.7-gentoo-r14/build]

WARNING: missing file /lib/modules/2.6.7-gentoo-r14/build/include/linux/modversions.h
The cause of this problem is usually a missing or misconfigured
kernel source tree (and sometimes an incorrect directory or symbolic link).

First, ensure that the proper kernel source and compiler packages
from your distribution vendor and/or the community are installed.

The Linux kernel can then be reconfigured by running "make menuconfig"
under the kernel source directory (usually /usr/src/linux).

Verify that the proper options for your system are selected,
and that CONFIG_SMP ("Symmetric multi-processing support" under
"Processor type and features") is disabled, as this driver is
presently designed to work on single-processor machines.

Then compile and install your new kernel (for more information about
this procedure, see the README file under the kernel source directory),
reboot the system using the new kernel, and re-run "ripconfig".

kevinalm · 08-20-2004, 09:18 PM

Likely one of two possibilities. You have a blown /usr/lib/modules/2.6.7-gentoo-r14/include -> /usr/src/2.6.7-gentoo-r14/include symlink. Or you ran make mrproper on the kernel source (or the kernel source is corrupt). When compiling kernel modules seperately from the standard kernel build procedure, you _must_ leave the source in the state it was in at the end of the kernel compile. This is because some kernel header files are created in the compile process and make mrproper (and likely make clean) will delete these. Iirc modversions.h is one of these.