audio don't work
Forum: System
Topic: audio don't work
started by: zleto
Posted by zleto on May 05 2006,16:03
Hy,First thanks to dsl developpers. Since it's on the core 2.4 it's the only live CD working on my Toshiba satellite pro 480 CDT.
After sorme problems i finally made it work.(dont know why pcmcia loading fails...).
But lauching XMMS I had no sound!! It says tha I should check if the sound card is properly installed etc.
But I'm a noob! I even don't know where to check this. So I searched through google but all I could find whas 'installing' drivers on HD.
I have two NTFS partitions and windows XP on it. So I don't want to delete it. Anyway I'd like to have the sound (and maybe video) on this laptop using dsl.
So how could I make it work?
Moreover I found some characteristics in the BIOS as WSS I/O address, SBPro I/O adress, etc... and i don't know how to use the results in insmod. io=? is it WSS I/O or SBPro I/O?dma=? I have in the BIOS dma=Channel 1??crazy little machine.
So please save me
Posted by piccolo on May 06 2006,11:25
Read this post:< http://damnsmalllinux.org/cgi-bin....t=13195 >
Posted by zleto on May 06 2006,12:02
I already read this one.REMARK: That procedure was to DSL HD Install.
-> so not for me cause I didn't installed it.
If DSL running from CDROM (Also usefull HD Install):
Open up Aterminal and do following commands:
sudo su
insmod "module" io="?" irq="?" dma="?" dma2="?" mpuio="?" mpuirq="?"
Where:
"module"= driver module for your sound chipset
You can get the resources assigns (irq, dma, port) from your Bios.
->As I told before I don't know what to put in insmod. In the BIOS dma says channel 0, do I have to put ismod 'module' dma=Channel0??!? Still don't know where to find driver names for my sound card ("module"), don't know what is mpuio, etc.
I found this:
# ALSA sound card setup
# with help from < http://www.sfu.ca/~jwendlan/laptop/ >
# and < http://www.alsa-project.org/alsa-doc/ >
alias snd-card-0 snd-opl3sa2
options snd-opl3sa2 dma1=1 dma2=0 fm_port=0x388 irq=5 isapnp=0 \
midi_port=0x330 port=0x538 sb_port=0x220 wss_port=0x530
post-install ( modprobe snd-mixer-oss; modprobe snd-pcm-oss; modprobe snd-seq-oss; amixer master 100 unmute; amixer pcm 100 unmute)
# some stuff for the OSS drivers
alias char-major-14 snd-pcm-oss
alias sound-slot-0 snd-card-0
# aliases for sound card #1
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
As configuration of modules.conf but I can't modify /KNOPPIX/etc/modules.conf ... permission denied even in root mode.
I think this is a bit like in my own laptop.
And last thing, I have a soundcore 3428 0 (autoclean) module already loaded. Don't know if it could be useful.
Posted by piccolo on May 06 2006,15:43
| Quote |
| REMARK: That procedure was to DSL HD Install |
Sorry, I have not explained well that point before.
If you run from CDROM also you can use the sndconfig utility without problems. But if you reboot the computer then sndconfig is lost because the utility was loaded and executed from the RAM memory.
Try first to use sndconfig. Using sndconfig we will find the correct resource assignations (port irq,dma).
The modules relationed to sound are several.
Some modules are the same for all systems (for example "soundcore") but from they one is specific for the sound chipset or chipset families, that module is the driver.
During the boot, DSL attempt to assign the correct driver module and if you read the messages just before the launching of desktop, you will see a line like to this:
soundcard=....
At that moment DSL is doing that process. The driver module election will be ever correct but many times on old computers fails because there are resource conflicts. For example, the sound chipset had assigned an irq value that is been used by other device from system.
Also It could be useful if you post the results from this two commands, open ATerminal and write:
lsmod
cat /proc/interrupts
The "lsmod" command will show all from driver modules and the "cat /proc/interrupts" command how the irq's was assigned.