tempestuous wrote:Yes, that achieves the same thing as my suggestion about modifying /etc/modprobe.conf;goofeyfoot wrote:I rem'd out a line that someone had me add to the rc.d local file. Here is the line:
modprobe snd-es18xx mpu_port=0x330 irq=5 dma1=1 dma2=5 isapnp=0
it ensures that when the snd-es18xx module loads (your ALSA driver) that it loads with the correct resource values.
My suggestion is the more "Linux-approved" way of doing things, but apparently running the modprobe command from rc.local can be more reliable ... possibly because it happens later in the boot sequence.
Here's what I suggest; first put the "es1869" bios settings back to normal.
Now delete everything relating to "snd-es18xx" in /etc/modprobe.conf
Add these lines to the end of /etc/rc.d/rc.localWhat I have done is load the module with ONLY the dma1 value, then pause, then reload the module with dma1 and dma2 values.Code: Select all
rmmod snd-es18xx sleep 1 modprobe snd-es18xx isapnp=0 irq=5 dma1=1 sleep 1 modprobe snd-es18xx isapnp=0 irq=5 dma1=1 dma2=5
Don't worry about mpu_port value ... unless you need to plug a midi device into your sound card.
Reboot.
When you run alsamixer, the master slider should show "00" at the bottom. If it shows "MM" it means that it is muted. And obviously the master slider should be up - a volume between 70 and 90 is about right.
Tempestuous:
Here is what I did.
First I did what you said. Then, during bootup I got some sort of "PnP" error. "Trying to recover."
Then the computer booted. At that point no sound stuff worked. Alsamixer said that you didn't have a device, blah blah blah.
Also the little "sgmixer" thing at the bottom of the screen didn't even show up.
So I went back to modprobe.conf and made it read this way via cut and paste:
alias snd-card-0 snd-es18xx
alias sound-slot-0 snd-es18xx
snd-es18xx mpu_port=0x330
At that point, bootup became normal. I had "hiss control" meaining that with volume controls I could control the hissing coming out of the speakers. I tried this dumb DOS space-invader game that makes noise. I got a lot of repeated beeping and screeching but nothing that sounded like a real game. But the two mixers worked OK to control the mayhem.
Speaking of two mixers, maybe this whole thing is some kind of software mixup. Can you have sgmixer in the bottom of your toolbar if Alsa is in your system. In other words, can you have two mixers or am I supposed to somehow get rid of one.
Well, I know this is aggravating but it's exactly what happened, I have succeeded in making noise but not much else.
Will keep you posted.
Best regards.
Michael