I've downloaded and installed Slackware 10. As far as I can tell the
ALSA driver is not installed.

I am planning on downloading the drivers from www.alsa-project.org. Are
there any particular versions I should try?

Any tips, comments or advice would be great

TIA

RG
===========================================

-- Sound hardware: yamaha opl3sa2 chipset. Works fine with OSS and windoze.

-- All ALSA utils are installed like: alsaconf, alsactl, alsamixer

-- alsaconf fails on modprobe with
modinfo: snd-opl3sa2: no module by that name found

-- alsamixer: function snd_ctl_open failed for default: No such device

#ls -l /lib/modules/2.4.26/kernel/drivers/sound/snd-opl3sa2*
/usr/bin/ls: /lib/modules/2.4.26/kernel/drivers/sound/snd-opl3sa2*: No
such file or directory

#ls -l /lib/modules/2.4.26/kernel/drivers/sound/snd-*
/usr/bin/ls: /lib/modules/2.4.26/kernel/drivers/sound/snd-*: No such
file or directory

# ls -l /proc/asound
/usr/bin/ls: /proc/asound: No such file or directory

# modinfo soundcore
modinfo: soundcore: no module by that name found

rg wrote:

> I've downloaded and installed Slackware 10. As far as I can tell the
> ALSA driver is not installed.
>
> I am planning on downloading the drivers from www.alsa-project.org. Are
> there any particular versions I should try?

Sure. If you build a custom kernel, build the ALSA drivers for it per their
documentation. They work great.

--
Just remember: when you go to court, you are trusting your fate to
twelve people that weren't smart enough to get out of jury duty!

rg wrote :

> I've downloaded and installed Slackware 10. As far as I can tell the
> ALSA driver is not installed.
>
Check if they are installed. Run:
ls -l /lib/modules/`uname -r`/kernel/sound/pci
ALSA modules usually starts with snd-* if none is there just install the
alsa packages from the CD.

If the modules are there then check if they actually has been loaded
into the kernel:
/sbin/lsmod

> I am planning on downloading the drivers from www.alsa-project.org. Are
> there any particular versions I should try?

First check if your card is supported, go to ALSA's Soundcard Matrix:
<URL: http://www.alsa-project.org/alsa-doc/>
--
Thomas O.

This area is designed to become quite warm during normal operation.

Thomas Overgaard wrote:
> rg wrote :
>
>
>>I've downloaded and installed Slackware 10. As far as I can tell the
>>ALSA driver is not installed.
>>
>
> Check if they are installed. Run:
> ls -l /lib/modules/`uname -r`/kernel/sound/pci
> ALSA modules usually starts with snd-* if none is there just install the
> alsa packages from the CD.
>
> If the modules are there then check if they actually has been loaded
> into the kernel:
> /sbin/lsmod
>
>
>>I am planning on downloading the drivers from www.alsa-project.org. Are
>>there any particular versions I should try?
>
>
> First check if your card is supported, go to ALSA's Soundcard Matrix:
> <URL: http://www.alsa-project.org/alsa-doc/>

Thanks for responding ... ok here are some checks

$ ls -l /lib/modules/2.4.26/kernel/sound
/usr/bin/ls: /lib/modules/2.4.26/kernel/sound: No such file or directory


$ ls -l /lib/modules/2.4.26/kernel/drivers/sound/pci
/usr/bin/ls: /lib/modules/2.4.26/kernel/drivers/sound/pci: No such file
or directory

$ ls -l /lib/modules/2.4.26/kernel/drivers/sound/snd-*
/usr/bin/ls: /lib/modules/2.4.26/kernel/drivers/sound/snd-*: No such
file or directory

And my OSS(Yamaha OPL3SAx) modules live here:

$ ls -l /lib/modules/2.4.26/kernel/drivers/sound/opl*
-rw-r--r-- 1 root root 18408 2004-09-06 09:31
/lib/modules/2.4.26/kernel/drivers/sound/opl3.o
-rw-r--r-- 1 root root 4432 2004-09-06 09:31
/lib/modules/2.4.26/kernel/drivers/sound/opl3sa.o
-rw-r--r-- 1 root root 13636 2004-09-06 09:31
/lib/modules/2.4.26/kernel/drivers/sound/opl3sa2.o

Two things:
1) I fired up xconfig and selected bluetooth and IPAQ support and
recompiled the kernel etc.
2) pkgtool shows Alsa pkg installed.


I think 1) probably wiped out the Also snd-* modules.

So ... would uninstalling and reinstalling the Alsa package work. I'm
thinking about giving that a try
before I download,compile and install the drivers from the ALSA web site.

The above OSS drivers work perfectly with the original kernel and the
recompiled one,
after manually loading the modules.

Any ideas?

TIA

On Thu, 09 Sep 2004 04:19:28 +0000, rg wrote:

> So ... would uninstalling and reinstalling the Alsa package work. I'm
> thinking about giving that a try
> before I download,compile and install the drivers from the ALSA web site.
>
> The above OSS drivers work perfectly with the original kernel and the
> recompiled one,
> after manually loading the modules.

No need to be intrigued by the fact that the ALSA drivers don't work,
while the OSS ones do; that's par for the course. Maybe some day the ALSA
guys will get their act together and come up with drivers that are easy to
configure and work. Until then, the ALSA drivers belong in /bin ;-)

rg wrote :

>
> I think 1) probably wiped out the Also snd-* modules.
>
Correct. The second you ran 'make modules_install' all your alsa modules
was wiped out.

> So ... would uninstalling and reinstalling the Alsa package work.

Yes, thats the easiest way to get your alsa modules back.

> The above OSS drivers work perfectly with the original kernel and the
> recompiled one, after manually loading the modules.
>
If the OSS modules are OK for your use then you could load these at boot
time by modifying /etc/rc.d/rc.modules and then you don't need alsa at
all.
--
Thomas O.

This area is designed to become quite warm during normal operation.

Thomas Overgaard wrote:
> rg wrote :
>
>
>>I think 1) probably wiped out the Also snd-* modules.
>>
>
> Correct. The second you ran 'make modules_install' all your alsa modules
> was wiped out.
>
>
>>So ... would uninstalling and reinstalling the Alsa package work.
>
>
> Yes, thats the easiest way to get your alsa modules back.
>
>
>>The above OSS drivers work perfectly with the original kernel and the
>>recompiled one, after manually loading the modules.
>>
>
> If the OSS modules are OK for your use then you could load these at boot
> time by modifying /etc/rc.d/rc.modules and then you don't need alsa at
> all.

One would think, there would be an option somewhere in
xconfig/menuconfig under the "sound section"
where one could select building the ALSA snd-* modules etc....or maybe I
missed it. Anyway,
after reading all the posts about getting ALSA to work, I didn't expect
it to be easy.

Although OSS works perfectly, Rosegarden, supposedly works much better
with ALSA,
which is my main reason for trying this. Hopefully, all my other sound
apps will continue to work with ALSA.

Let the battle begin .... OSS vs ALSA

Anyway, thanks for confirming my idea of uninstall/reinstall. I will
try it this weekend.

RG

On Fri, 10 Sep 2004 04:22:53 +0000, rg wrote:

> Although OSS works perfectly, Rosegarden, supposedly works much better
> with ALSA,
> which is my main reason for trying this. Hopefully, all my other sound
> apps will continue to work with ALSA.
>
> Let the battle begin .... OSS vs ALSA

One day ALSA will no doubt measure up. For the time being, it doesn't.
The annoying thing is, as far as the end user is concerned, no visible
improvement can be noticed in version 1.0. If the important open source
projects were as plain crippled as ALSA, at version 1.0, the open
source movement would have indefinitely remained a mere pasttime for
hackers.

Thomas Overgaard wrote:
> rg wrote :
>
>
>>I think 1) probably wiped out the Also snd-* modules.
>>
>
> Correct. The second you ran 'make modules_install' all your alsa modules
> was wiped out.
>
>
>>So ... would uninstalling and reinstalling the Alsa package work.
>
>
> Yes, thats the easiest way to get your alsa modules back.
>
>
>>The above OSS drivers work perfectly with the original kernel and the
>>recompiled one, after manually loading the modules.
>>
>
> If the OSS modules are OK for your use then you could load these at boot
> time by modifying /etc/rc.d/rc.modules and then you don't need alsa at
> all.

OK, I uninstalled ALSA (driver,lib,oss,utils). Then reinstalled them.
I verified that the ALSA sound modules were installed under
/lib/modules/2.4.26/kernel/sound

ls -l /lib/modules/2.4.26/kernel/sound/isa
-rw-r--r-- 1 root root 10885 2004-06-13 20:39 snd-als100.o
-rw-r--r-- 1 root root 11418 2004-06-13 20:39 snd-azt2320.o
-rw-r--r-- 1 root root 13129 2004-06-13 20:39 snd-cmi8330.o
-rw-r--r-- 1 root root 10105 2004-06-13 20:39 snd-dt019x.o
-rw-r--r-- 1 root root 32114 2004-06-13 20:39 snd-es18xx.o
-rw-r--r-- 1 root root 17555 2004-06-13 20:39 snd-opl3sa2.o <-- the
driver I need
-rw-r--r-- 1 root root 8476 2004-06-13 20:39 snd-sgalaxy.o
-rw-r--r-- 1 root root 15466 2004-06-13 20:39 snd-sscape.o
drwxr-xr-x 2 root root 1024 2004-06-13 20:39 wavefront/

So far so good. I then ran "alsaconf". It probed and found: snd-opl3sa2.o
i got prompted to update /etc/modules.conf, here's the result:

# cat /etc/modules.conf

# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF verion 1.0.5 ---
alias char-major-116 snd
alias char-major-14 soundcore
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
alias snd-card-0 snd-opl3sa2
alias sound-slot-0 snd-opl3sa2
# --- END: Generated by ALSACONF, do not edit. ---

Configuration ended successfully according to "alsaconf"

To load the modules I tried:

# modprobe snd
/lib/modules/2.4.26/kernel/sound/acore/snd.o: unresolved symbol
request_module
/lib/modules/2.4.26/kernel/sound/acore/snd.o: insmod
/lib/modules/2.4.26/kernel/sound/acore/snd.o failed
/lib/modules/2.4.26/kernel/sound/acore/snd.o: insmod snd failed

# modprobe snd-opl3sa2
/lib/modules/2.4.26/kernel/sound/acore/snd.o: unresolved symbol
request_module
/lib/modules/2.4.26/kernel/sound/acore/snd.o: insmod
/lib/modules/2.4.26/kernel/sound/acore/snd.o failed
/lib/modules/2.4.26/kernel/sound/acore/snd.o: insmod snd-opl3sa2 failed

So, something is sill not right. Maybe something needs to be selected
when configuring the kernel
I built a custom 2.4.26 kernel for bluetooth and ipaq. I used my 2.4.24
config file.

I would like to get this working *without* installing drivers from the
Alsa web-site, if at all possible.

Any ideas, comments or advice would be very welcome.

TIA

RG

On Sat, 11 Sep 2004 16:07:42 +0000, rg wrote:
>>>So ... would uninstalling and reinstalling the Alsa package work.
>>
>> Yes, thats the easiest way to get your alsa modules back.

No, that does not work when you've built a custom kernel.

> OK, I uninstalled ALSA (driver,lib,oss,utils). Then reinstalled them.
> I verified that the ALSA sound modules were installed under
> /lib/modules/2.4.26/kernel/sound
>
> ls -l /lib/modules/2.4.26/kernel/sound/isa
> -rw-r--r-- 1 root root 10885 2004-06-13 20:39 snd-als100.o

On 2004/June/13 you built a custom kernel with the $VERSION string of
"2.4.26". You ran the Makefile "modules_install" target at 20:39 your
time. These are not the Slackeware modules. The Slackware modules are
gzipped.

> So far so good. I then ran "alsaconf". It probed and found: snd-opl3sa2.o

Or was it snd-opl3sa2.o.gz?

> # modprobe snd-opl3sa2
> /lib/modules/2.4.26/kernel/sound/acore/snd.o: unresolved symbol
> request_module
> [snip]
> So, something is sill not right. Maybe something needs to be selected
> when configuring the kernel

Yes, it's a misconfigured kernel. Start with the Slackware .config and
work from there.

> I built a custom 2.4.26 kernel for bluetooth and ipaq. I used my 2.4.24
> config file.

Then it's hard to say what went wrong, but the error quoted above
suggests that your custom kernel lacks support for loading modules.

> I would like to get this working *without* installing drivers from the
> Alsa web-site, if at all possible.

In general you should plan on recompiling third-party kernel modules
for each custom kernel. That may not ALWAYS be necessary, but IME it
usually is.

> Any ideas, comments or advice would be very welcome.

A good trick when you're building a kernel of the same version as you
got from the distro is to add something to the $VERSION string in the
top-level Makefile. (EXTRAVERSION is provided for this purpose.) That
way your custom modules don't conflict with the Slackware ones.
--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply