piccolo
Group: Members
Posts: 286
Joined: Mar. 2006 |
 |
Posted: July 09 2006,21:55 |
 |
| Quote | Take a look at THIS - The module snd-azt2320 is included in the ALSA-Drivers extension. It may be as simple to load the extension and run the command, sudo modprobe snd-azt2320.
I agree that it is possible to get alot of cards going with the soundblaster drivers, but this might be worth trying. |
I have hard time installing ALSA package from MyDSL extensions using myself an ISA PnP sound card as well as helping other people on this forum.
My conclusions were:
-For old sound cards (ISA PnP sound cards):
The ALSA install process from the MyDSL extesions neither require to know how to compile, nor to install, nor to insert the sound modules. The process is automatic. This is very good. However if the default resources assignation used (irq, dma) is being used by another hardware of the system, the ALSA sound driver will not work by the same problem before did not work OSS.
Manual configuration or sound configuration utility is required, either OSS or ALSA and difficulty grade is the same for both sound systems.
The utility for OSS is "sndconfig" while the utility for ALSA is "alsaconf". Both utilities are Debian utilities that must be downloaded from internet.
-For newer sound cards (Not ISA PnP sound card):
No sound problem is rare. If OSS work, for sure ALSA will work. Moreover, ALSA can work in the cases where OSS not.
| Quote | | i entered all the lines as you said and there were no reports-or errors. didnt seem to do anything. must have been accepted as the were no file not found reports |
That is good. If no messages mean that the driver Sound Blaster was accepted by the system.
Then try this play sound test without sound file:
Using XMMS, chosse "Play Location" and write "tone://1000" (without quotation marks).
That should generate a 1000 hertz tone.
If you can't hear the tone and error messages then the values for either "irq" or "dma1" or "dma16" parameters can be incorrects for your system.
No problem, you can try other set of parameters.
If you can see the result from the "cat /proc/interrupts" command (without quotation marks) it should be very useful.
Below a example of result from "cat /proc/interrupts"
CPU0
0: 10784844 XT-PIC timer
1: 27945 XT-PIC keyboard
2: 0 XT-PIC cascade
3: 310046 XT-PIC orinoco_cs
8: 1 XT-PIC rtc
11: 0 XT-PIC Texas Instruments PCI1251A, usb-uhci
12: 1380425 XT-PIC PS/2 Mouse
14: 74469 XT-PIC ide0
15: 2202 XT-PIC ide1
NMI: 0
LOC: 0
ERR: 0
MIS: 0
First column is the assigned interrupts (the assigned irqs are being values used by the system).
In this example, free irqs are: 4, 6, 7, 9, 10, 13. (The free irqs are values not used by the system yet)
The free irq are possibles values that you can assign to "irq" parameter when you will do:
modprobe sb io=0x220 irq=<<here free irq value>> dma=1 dma16=5 mpu_io=0x330
Either with or without that information you must do this:
Again commands:
sudo su
rmmod ad1848
rmmod sound
rmmod soundcore
modprobe soundcore
modprobe sound
Now the following command but changing the value for "irq" with: either some free irq value, if you was able to see result from "cat /proc/interrupts" command, or if you don't know, any value from 1 to 13 range:
modprobe sb io=0x220 irq=? dma=1 dma16=5 mpu_io=0x330
Then try this play sound test without sound file.
If the test fails, then:
rmmod sb
That remove the Sound Blaster driver. (It is imperative before insert it again but with another values for his parameters).
Now, again the same command but changing the value for "irq" by another value.
modprobe sb io=0x220 irq=? dma=1 dma16=5 mpu_io=0x330
Then try this play sound test without sound file again.
If the test fails, then:
rmmod sb
..... so and so.
Also you could try different values for "dma1" and "dma16" parameters.
The possibles values are: 0,1,2,3 and 5
The values must be differents between they. (dma1 different of dma16)
--------------
Robin Hood used Linux
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
