Thanks Stan for the help! See my other comments below.
On 6/25/08, stan <[EMAIL PROTECTED]> wrote:
Stan S wrote:
>> Date: Sun, 18 May 08
>> From: stan <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
>> Subject: Re: [Alsa-user] kppp & ALSA incompatible for me: can have one
or the other but not both together and working
>> To: Stan S <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
>> Cc: alsa-user@lists.sourceforge.net <mailto:
alsa-user@lists.sourceforge.net>
>>Stan S wrote:
>[snip]
>>Any ideas or thoughts about this and how to fix it?
>>
>>
>> Thanks
>>> I probably can't help you, but it would help if you ran the script at
>>> http://hg.alsa-project.org/alsa/raw-file/tip/alsa-info.sh
>>> and pasted the link back here. That will give information about your
>>> setup and someone else might be able to help.
>>> It sounds like alsa might be interpreting your modem as a sound device
>>> and putting the real sound device in second position. But that is just
>>> speculation.
>> I just today ran the script told to me and to this list by Stan. I don't
know if the output is useful or not, but it's found at
>> http://www.pastebin.ca/1055338
>> [More about this is found at the sidux forum:
http://www.sidux.com/PNphpBB2-viewtopic-t-11196.html ]
stan, first taking some lines from my automatic pastebin posting, wrote:
> 1. snd-atiixp-modem: index=-2
> 2. snd-intel8x0m: index=-2
> 3. snd-via82xx-modem: index=-2
> This indicates that you have modems that alsa is recognizing as sound
devices. You should change it to something like:
> 1. snd-intel8x0m: index=0
> 2. snd-atiixp-modem: index=1
> 3. snd-via82xx-modem: index=2
> I think the -2 says to take the first available slot, but not sure. This
specifies that your soundcard will always be device 0, regardless of the
order > the devices are loaded; that order varies on every boot. This is
good because the alsa default device is device 0, so sound should always
work.
> Oh, this is in /etc/modprobe.conf
I've not yet done what you say above-- I'm currently using another desktop
computer which has the Linux distro MEPIS as OS. Maybe I'll test it tomorrow
or on Friday or perhaps I'll wait to see what you or someone else might say
about the statements below.
My other desktop computer that had this kppp-alsa problem is the one in
which I have sidux (a Linux distro) as the OS. I told readers in a sidux
forum what you told me above (but I didn't use your name nor email address--
I called you "a helpful guy"). One man in Germany - a guy named Michaa -
wonders what you think about another sound card found when I ran the script
you told me about and the output of which is presented at
http://www.pastebin.ca/1055338
Michaa wonders about line 49 in the output:
PCI Soundcards installed in the system:
02:01.0 Communication controller: NetMos Technology PCI 9815 Multi-I/O
Controller (rev 01)
You can read Michaa's comments in the sidux forum at
http://tinyurl.com/6aqz8o
[Incidentally, for each of my Linux desktop computers, I use an external,
serial, 56K US Robotics modem which is known to work well with Linux.]
Thanks,
Stan
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
