Alsa soundcard driver install problem
 

I am trying to install the alsa driver for my als120 sound card.
The driver install script ran when I entered './configure&&make&&make install' but left the following: 'checking for kernel version...the file /lib/modules/2.4.22-1.2115.nptl/build/include/linux/version.h does not exist. Please, install the package with full kernel sources for your distribution or use --with-kernel=dir option to specity another directory with kernel sources (default is /lib/modules/2.4.22-1.2115.nptl/build).

Ok, it looks like the directory does not exist? How does one install the required directory and files so the dirver install can proceed?

hi sirius57, welcome to lq. you should be able to install the kernel source rpm from the install cd's. open your package manager and look for the kernel source, once selected it should ask you for a cd. hope that helps.
good luck.

I just tried the package manager and ran into the following error:
In the package manager, I chose kernel developement, it checked the system and prompted me for the 3rd cd to install. I ok'd my way through, then when the cd drive spun up, it said 'Error installing packages'. What problem would prevent the package manager from working? I am using the same cd set and same drive that I originally installed the Linux system on originally. Could a folder be write protected? I ran into that problem where I had to give permissions to the desktop folder so I could launch a script in the terminal window.

it looks as if fedora's package manager has some problems, this thread may help you w/that

http://www.linuxquestions.org/questi...lling+packages

good luck.

I followed the link in your reply and was able to find the solution which was to use the Red Hat update tool. Now the package manager is updated and the kernel source is installed. Which brings me back to my original question: installing the alsa sound driver. Is this the correct command to use in the terminal window: ./configure&&make&&make install? Then, the part that I do not fully understand, installing the module. Is that where the modprobe command is used and if so, how does one use it?

first let's figure out what card you have, then we'll address the install. i say this because, some cards require things such as configure -with, etc, so open a teminal, or konsole, and type

/sbin/lspci -v

copy and paste the results here.

This is the info. I do not see the audio card, but it worked under windows 98 and is an
als120 sound card. Hope the below info helps.

00:00.0 Host bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3] (rev 04)
Flags: bus master, medium devsel, latency 16
Memory at e0000000 (32-bit, prefetchable) [size=64M]
Capabilities: <available only to root>

00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AG P] (prog-if 00 [Normal decode])
Flags: bus master, 66Mhz, medium devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000c000-0000cfff
Memory behind bridge: e4000000-e5ffffff
Prefetchable memory behind bridge: e7000000-e77fffff

00:07.0 ISA bridge: VIA Technologies, Inc. VT82C586/A/B PCI-to-ISA [Apollo VP] ( rev 47)
Flags: bus master, stepping, medium devsel, latency 0

00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/ C/VT8235 PIPC Bus Master IDE (rev 06) (prog-if 8a [Master SecP PriP])
Flags: bus master, medium devsel, latency 64
I/O ports at e400 [size=16]

00:07.2 USB Controller: VIA Technologies, Inc. USB (rev 02) (prog-if 00 [UHCI])
Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller
Flags: bus master, medium devsel, latency 64, IRQ 9
I/O ports at e000 [size=32]

00:07.3 PCI bridge: VIA Technologies, Inc. VT82C586B ACPI (rev 10) (prog-if 00 [ Normal decode])
!!! Invalid class 0604 for header type 00
Flags: medium devsel, IRQ 9

00:09.0 Ethernet controller: National Semiconductor Corporation DP83815 (MacPhyt er) Ethernet Controller
Subsystem: Netgear FA311 / FA312 (FA311 with WoL HW)
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at e800 [size=256]
Memory at e7800000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at e6000000 [disabled] [size=64K]
Capabilities: <available only to root>

00:0a.0 Communication controller: ESS Technology ES2898 Modem (rev 03)
Subsystem: DIGICOM Systems, Inc.: Unknown device 1062
Flags: fast devsel, IRQ 9
I/O ports at ec00 [size=8]
Capabilities: <available only to root>

01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 86C326 5598/ 6326 (rev 0b) (prog-if 00 [VGA])
Flags: bus master, 66Mhz, medium devsel, latency 64
Memory at e7000000 (32-bit, prefetchable) [size=8M]
Memory at e5000000 (32-bit, non-prefetchable) [size=64K]
I/O ports at c000 [size=128]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: <available only to root>

i don't see the sound card either, try a pnpdump, it may be an isa card.

you may have a look at this if the card actually has the avance logic chipset.

http://www.alsa-project.org/alsa-doc...&module=als100

good luck.

The driver, library and utilities are all compiled, however, the modprobe failed to find the modules. It said: modprobe; cant locate module snd-als100
snd-pcm-oss
snd-mixer-oss
snd-seq-oss

I do not have a clue where the modules would be located or how to find them or if I searched, what the files are called. The directory tree where the files were compiled is: /home/sailboat/Desktop/mp3files/alsasoundmodules/.......
Also, the instructions in the link from your last post talks about the modules.conf file. Is it necessary to past the text in the instructions into the .conf file for the driver to work? And do I have to run autodetect after all is said and done?

try modprobe from the directory you compiled in.

I reread the alsa docs and it looks like the packages are installed in the wrong place. So I tried to move the directories to /usr/src/alsa, however, the nautalus file system will not allow me to copy the extracted folders. So I tried it in the terminal window (as root), but being a Linux newbie, ran into 'omitting directory' or 'cannot stat' or 'no such file or directory'. Would you recommend the above approach to move everything and then modprobe or just delete and start over? Can you give me a clear example of how to use the cp command? I need to see an example of a copy from and a copy to.

you'll probably be better off deleting/uninstalling, and starting from scratch. an example of the cp command would go something like this

cp path/to/filename path/to/newfilename

hope that's clear enough.
good luck.

I made the location change and was able to modprobe, however, I did get some errors. Here is a cut and paste of the results:

[root@localhost alsa-utils-1.0.5]# cd ..
[root@localhost alsa]# modprobe snd-als100;modprobe snd-pcm-oss;modprobe snd-mix er-oss;modprobe snd-seq-oss
/lib/modules/2.4.22-1.2115.nptl/kernel/sound/isa/snd-als100.o: init_module: No s uch device
Hint: insmod errors can be caused by incorrect module parameters, including inva lid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.22-1.2115.nptl/kernel/sound/isa/snd-als100.o: insmod /lib/modul es/2.4.22-1.2115.nptl/kernel/sound/isa/snd-als100.o failed
/lib/modules/2.4.22-1.2115.nptl/kernel/sound/isa/snd-als100.o: insmod snd-als100 failed
/lib/modules/2.4.22-1.2115.nptl/kernel/sound/acore/seq/oss/snd-seq-oss.o: init_m odule: Device or resource busy
Hint: insmod errors can be caused by incorrect module parameters, including inva lid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg
/lib/modules/2.4.22-1.2115.nptl/kernel/sound/acore/seq/oss/snd-seq-oss.o: insmod /lib/modules/2.4.22-1.2115.nptl/kernel/sound/acore/seq/oss/snd-seq-oss.o failed
/lib/modules/2.4.22-1.2115.nptl/kernel/sound/acore/seq/oss/snd-seq-oss.o: insmod snd-seq-oss failed
[root@localhost alsa]# alsamixer

alsamixer: function snd_ctl_open failed for default: No such file or directory
[root@localhost alsa]# ossmixer

When it says no such device, I would suspect it has to do with hardware at this point. I know that the card worked fine under windows. Also, under windows, the modem would not work and that was traced to no irq sharing after I added the network card. Now, maybe it is the other way around where the modem is recognized and not the sound card? Only guessing at this point. Is a sound card swap the only option?

try a pnpdump and see if it finds the card, if it does you may be able to modprobe w/parameters.