[opensuse] Sound and SuSE11.1
Well, I might as well join in the 11.1 upgrade frolics as well.. I am trying to do a complete install (not an upgrade) of SuSE 11.1 and it has not been an easy process! But am making progress nonetheless... My major headache at the moment is getting the sound system to work. I think I know where the trouble lies but I do not know how to fix it... My system has both a sound chip on the motherboard and I have the Creative Labs Audigy Pro 4 card installed. I suspect that having two sound systems is at the root of my troubles... I can not say a whole lot about the sound system that is on the motherboard itself, other than to say that drivers which are installed for it have a name prefix of CX88. I never use (or want to) this sound chip and in fact have disabled it in the BIOS. But despite that, SuSE and ALSA seem to be finding it. And if that is the chip that is in fact being activated for my sound, then it is no wonder I cannot hear any sound. (since nothing is hooked up to it) The sound setup tool in YaST only reports the Audigy Sound card BUT when I run Alsaconf to set it up I am getting the following error messages - Loading driver... Shutting down sound driver ERROR: Module snd_pcm is in use by cx88_alsa ERROR: Module snd_timer is in use by snd_pcm ERROR: Module snd_page_alloc is in use by snd_pcm ERROR: Module snd is in use by cx88_alsa, snd_pmc, snd_timer so this is why I suspect that SuSE is finding this sound chip on my motherboard and trying to use it instead of the Creative Labs Soundblaster Audigy 4 Pro card. In SuSE 10.3 it was sufficient to simply disable this chip in the BIOS and Alsaconf was quite happy to install the Audigy Pro sound card as my main sound system. Dunno why that is not the case any more, but can someone tell me how to completely disable the CX88 sound chip so SuSE will not find it or attempt to use it? As an FYI for those who put SuSE 11.1 installation together... I had to remove the OpenOffice modules from the set of packages to be installed. No matter whether I tried to install KDE4.1 or KDE3.5 the installation process ALWAYs hung on me when trying to install OpenOffice. I had a heck of a time getting the display to work. I am using an nVidia display card, and the installation failed to correctly set up my display. Trying to use Yast2 or Sax made it far worse and both left me with an unusable display. (I did eventually find and use the one button setup for nVidia that was described on the OpenSuSE website, and that part seemed to work fine, but I don't understand why it should have been necessary for me to hunt that down and not have the installation process automatically set up the drivers and such for me..) Also, after much hunting around I finally discovered that nVidia supplies their own X11 configuration tool and it is the ONLY way I was able to get the display to work properly. It would have been real nice if I had been told, during the installation process, that since I had an nVidia display card that I should go to the nVidia web site and use their X11 configuration tool instead. I spent hours fooling around with YaST2 and Sax trying to get this working. While on the subject of displays, why is it that the main part of YaST2 honors the font settings as defined by the KDE Control Center tool, but none of the subcomponents of YaST, like the software manager, Boot Loader, System Services (Runlevel) etc do... For me, the font is coming up so small as to be almost unreadable... While KDE4 looks promising, I had to give up on it as well and drop back to KDE3.5. There is little/no help available in it for configuring the display or sound system in KDE4.1 and I found it confusing to use. So, since I am unfamiliar with it, I had to drop back to an environment, KDE3.5, that I am familiar with and am having more luck with it, but as I mention still no joy with the sound.... Marc.. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 23 December 2008 11:31:11 Marc Chamberlin wrote:
[...]
I can not say a whole lot about the sound system that is on the motherboard itself, other than to say that drivers which are installed for it have a name prefix of CX88. I never use (or want to) this sound chip and in fact have disabled it in the BIOS. But despite that, SuSE and ALSA seem to be finding it. And if that is the chip that is in fact being activated for my sound, then it is no wonder I cannot hear any sound. (since nothing is hooked up to it)
The sound setup tool in YaST only reports the Audigy Sound card BUT when I run Alsaconf to set it up I am getting the following error messages -
Loading driver... Shutting down sound driver ERROR: Module snd_pcm is in use by cx88_alsa ERROR: Module snd_timer is in use by snd_pcm ERROR: Module snd_page_alloc is in use by snd_pcm ERROR: Module snd is in use by cx88_alsa, snd_pmc, snd_timer
Try running rmmod cx88_alsa (or modprobe -r cx88_alsa), then re-run alsaconf. You may need to manually run modprobe -i <audigy driver module> but I'm not sure. If that works, try blacklisting the cx88_alsa module by adding it to /etc/modprobe.d/blacklist - this will tell the system not to load that module automatically, despite apparently finding the hardware. You can still explicitly load it via modprobe. It may also be worth checking to see that the module for the audigy card is not actually blacklisted too. If it is, even though you can load it as described above it will not be loaded automatically. Hope this helps. Rodney. -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ===================================================
Rodney Baker wrote:
On Tuesday 23 December 2008 11:31:11 Marc Chamberlin wrote:
[...]
I can not say a whole lot about the sound system that is on the motherboard itself, other than to say that drivers which are installed for it have a name prefix of CX88. I never use (or want to) this sound chip and in fact have disabled it in the BIOS. But despite that, SuSE and ALSA seem to be finding it. And if that is the chip that is in fact being activated for my sound, then it is no wonder I cannot hear any sound. (since nothing is hooked up to it)
The sound setup tool in YaST only reports the Audigy Sound card BUT when I run Alsaconf to set it up I am getting the following error messages -
Loading driver... Shutting down sound driver ERROR: Module snd_pcm is in use by cx88_alsa ERROR: Module snd_timer is in use by snd_pcm ERROR: Module snd_page_alloc is in use by snd_pcm ERROR: Module snd is in use by cx88_alsa, snd_pmc, snd_timer
Try running rmmod cx88_alsa (or modprobe -r cx88_alsa), then re-run alsaconf. You may need to manually run modprobe -i <audigy driver module> but I'm not sure.
If that works, try blacklisting the cx88_alsa module by adding it to /etc/modprobe.d/blacklist - this will tell the system not to load that module automatically, despite apparently finding the hardware. You can still explicitly load it via modprobe.
It may also be worth checking to see that the module for the audigy card is not actually blacklisted too. If it is, even though you can load it as described above it will not be loaded automatically.
Hope this helps. Rodney.
Thanks Rodney for your suggestions, I really thought you had the answer but still no joy with my sound! So another look at the log files has revealed what to me appears to be a new angle on this problem, and again I am not sure how to fix. So do you and anyone else got an idea on this? - Dec 23 09:38:19 nova pulseaudio[4237]: pid.c: Stale PID file, overwriting. Dec 23 09:38:20 nova pulseaudio[4237]: alsa-util.c: Error opening PCM device hw:0: Device or resource busy Dec 23 09:38:20 nova pulseaudio[4237]: module.c: Failed to load module "module-alsa-sink" (argument: "device_id=0 sink_name=alsa_out put.usb_device_8bb_2900_noserial_if0_sound_card_0_alsa_playback_0 tsched=1"): initialization failed. Dec 23 09:38:20 nova pulseaudio[4237]: alsa-util.c: Cannot find fallback mixer control "Mic". BTW running alsaconf now seems to work in that no errors are reported.. just no sound yet... Marc... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Marc Chamberlin wrote:
Rodney Baker wrote:
On Tuesday 23 December 2008 11:31:11 Marc Chamberlin wrote:
[...]
I can not say a whole lot about the sound system that is on the motherboard itself, other than to say that drivers which are installed for it have a name prefix of CX88. I never use (or want to) this sound chip and in fact have disabled it in the BIOS. But despite that, SuSE and ALSA seem to be finding it. And if that is the chip that is in fact being activated for my sound, then it is no wonder I cannot hear any sound. (since nothing is hooked up to it)
The sound setup tool in YaST only reports the Audigy Sound card BUT when I run Alsaconf to set it up I am getting the following error messages -
Loading driver... Shutting down sound driver ERROR: Module snd_pcm is in use by cx88_alsa ERROR: Module snd_timer is in use by snd_pcm ERROR: Module snd_page_alloc is in use by snd_pcm ERROR: Module snd is in use by cx88_alsa, snd_pmc, snd_timer
Try running rmmod cx88_alsa (or modprobe -r cx88_alsa), then re-run alsaconf. You may need to manually run modprobe -i <audigy driver module> but I'm not sure.
If that works, try blacklisting the cx88_alsa module by adding it to /etc/modprobe.d/blacklist - this will tell the system not to load that module automatically, despite apparently finding the hardware. You can still explicitly load it via modprobe.
It may also be worth checking to see that the module for the audigy card is not actually blacklisted too. If it is, even though you can load it as described above it will not be loaded automatically.
Hope this helps. Rodney.
Thanks Rodney for your suggestions, I really thought you had the answer but still no joy with my sound! So another look at the log files has revealed what to me appears to be a new angle on this problem, and again I am not sure how to fix. So do you and anyone else got an idea on this? -
Dec 23 09:38:19 nova pulseaudio[4237]: pid.c: Stale PID file, overwriting. Dec 23 09:38:20 nova pulseaudio[4237]: alsa-util.c: Error opening PCM device hw:0: Device or resource busy Dec 23 09:38:20 nova pulseaudio[4237]: module.c: Failed to load module "module-alsa-sink" (argument: "device_id=0 sink_name=alsa_out put.usb_device_8bb_2900_noserial_if0_sound_card_0_alsa_playback_0 tsched=1"): initialization failed. Dec 23 09:38:20 nova pulseaudio[4237]: alsa-util.c: Cannot find fallback mixer control "Mic".
BTW running alsaconf now seems to work in that no errors are reported.. just no sound yet...
Marc...
As a follow up, I have dropped back to SuSE11.0 and tried to bring up the sound system. Still no joy! So apparently this sound system failure has occurred for my sound card since 11.0??? I am rather stuck now, I tried to drop back to 10.3, which was working, but my installation CD failed. I would really like to get SuSE11.1 working, but I will start downloading 10.3 just in case I must go back to it... Marc... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sat, Dec 27, 2008 at 9:48 AM, Marc Chamberlin <marc@marcchamberlin.com> wrote:
As a follow up, I have dropped back to SuSE11.0 and tried to bring up the sound system. Still no joy! So apparently this sound system failure has occurred for my sound card since 11.0??? I am rather stuck now, I tried to drop back to 10.3, which was working, but my installation CD failed. I would really like to get SuSE11.1 working, but I will start downloading 10.3 just in case I must go back to it...
Can you give the result of "cat /proc/asound/card0/codec# | grep Codec" also "cat /etc/modprobe.d/sound" Please also inform rpm -qa | grep alsa rpm -qa | grep pulse rpm -q libasound2 regards, medwinz -- P. J. O'Rourke - "Cleanliness becomes more important when godliness is unlikely." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello List Members, I'm finding that my sound using the Intel ICH9 is working less a couple of items.... 1. No speaker audio output on the built-in laptop speakers. When I hook up a headset, then audio works fine. Under KMixer, there are not any options to turn on the laptop speakers as in SuSE 10.3, KDE 3.5. This may be part of the over all issue? 2. No internal or external microphone muting whether selected or not. 3. Slider control for external microphone doesn't have any effect when adjusted. I get the same issues whether I have pulse audio installed or not. I'm using SuSE 11.1 Released, KDE 4.1 on a Lenovo W500 laptop. /etc/modprobe.d/sound # u1Nb.kXwNWe4doZB:82801I (ICH9 Family) HD Audio Controller alias snd-card-0 snd-hda-intel options snd-hda-intel enable=1 index=0 options snd slots=snd-hda-intel options snd-hda-intel model=thinkpad 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03) 00:1c.4 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 5 (rev 03) rpm -qa | grep alsa alsa-1.0.18-8.9 alsa-plugins-pulse-1.0.18-6.6 alsa-devel-1.0.18-8.9 alsa-firmware-1.0.17-1.39 alsa-plugins-1.0.18-6.13 alsa-oss-1.0.17-1.43 alsa-oss-32bit-1.0.17-1.37 alsa-utils-1.0.18-6.4 kg7hq@linux-8zkt:~> rpm -qa | grep pulse alsa-plugins-pulse-1.0.18-6.6 pulseaudio-module-x11-0.9.12-8.6 libpulse0-0.9.12-9.5 libpulse-mainloop-glib0-0.9.12-9.5 pulseaudio-module-lirc-0.9.12-8.6 pulseaudio-module-bluetooth-0.9.12-8.6 pulseaudio-utils-0.9.12-8.6 pulseaudio-0.9.12-8.6 pulseaudio-module-jack-0.9.12-8.6 libpulse-browse0-0.9.12-9.5 audacious-plugins-output-pulse-1.5.1-0.pm.9 libxine1-pulse-1.1.15-44.pm.2 libao-pulse-0.9.3-1.152 libpulsecore4-0.9.12-9.5 pulseaudio-module-zeroconf-0.9.12-8.6 pulseaudio-esound-compat-0.9.12-8.6 kg7hq@linux-8zkt:~> rpm -q libasound2 libasound2-1.0.18-8.9 -- ***************** Thank You, Michael A. Sterba ARS - KG7HQ Assistant Director/Technical Specialist Northwest Division - ARRL kg7hq@arrl.net http://www.kg7hq.wetnet.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello List Members,
I'm finding that my sound using the Intel ICH9 is working less a couple of items....
1. No speaker audio output on the built-in laptop speakers. When I hook up a headset, then audio works fine. Under KMixer, there are not any options to turn on the laptop speakers as in SuSE 10.3, KDE 3.5. This may be part of the over all issue? 2. No internal or external microphone muting whether selected or not. 3. Slider control for external microphone doesn't have any effect when adjusted. I get the same issues whether I have pulse audio installed or not.
I'm using SuSE 11.1 Released, KDE 4.1 on a Lenovo W500 laptop.
Open the mixer and enable all channels. Make sure that the analog loopbacks are checked (disabled). Clark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 27 December 2008 14:28:26 clarkt@cnsp.com wrote:
Hello List Members,
I'm finding that my sound using the Intel ICH9 is working less a couple of items....
1. No speaker audio output on the built-in laptop speakers. When I hook up a headset, then audio works fine. Under KMixer, there are not any options to turn on the laptop speakers as in SuSE 10.3, KDE 3.5. This may be part of the over all issue? 2. No internal or external microphone muting whether selected or not. 3. Slider control for external microphone doesn't have any effect when adjusted. I get the same issues whether I have pulse audio installed or not.
I'm using SuSE 11.1 Released, KDE 4.1 on a Lenovo W500 laptop.
Open the mixer and enable all channels. Make sure that the analog loopbacks are checked (disabled).
Clark
Hello Clark, I have enabled all channels... These are what's available.... Front, PCM, IEC958 (Only with mute function), IEC958 Default PCM (Only with mute function), Digital, External Mic (capture), Internal Mic and Internal Mic (capture). The title of the window is HDA Intel -- Michael -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Dec 28, 2008 at 5:34 AM, Michael A. Sterba <cwo.usnr@verizon.net> wrote:
I have enabled all channels... These are what's available.... Front, PCM, IEC958 (Only with mute function), IEC958 Default PCM (Only with mute function), Digital, External Mic (capture), Internal Mic and Internal Mic (capture).
The title of the window is HDA Intel
Could you post the result of "cat /proc/asound/card0/codec#* | grep Codec" How is /etc/modprobe.d/sound configured? using Yast or alsaconf? regards, medwinz -- Bill Cosby - "Human beings are the only creatures on earth that allow their children to come back home." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 27 December 2008 19:02:14 medwinz wrote:
Could you post the result of "cat /proc/asound/card0/codec#* | grep Codec"
How is /etc/modprobe.d/sound configured? using Yast or alsaconf?
Hello medwinz and Group, The system was configured by Yast as I'm not familiar with alsaconf as of yet.... But I may be learning it real soon! cat /proc/asound/card0/codec#* | grep Codec Codec: Conexant CX20561 (Hermosa) Codec: Conexant ID 2c06 less /etc/modprobe.d/sound options snd-hda-intel enable=1 index=0 # u1Nb.kXwNWe4doZB:82801I (ICH9 Family) HD Audio Controller alias snd-card-0 snd-hda-intel options snd slots=snd-hda-intel options snd-hda-intel model=thinkpad ##Added manually to engage speakers(no effect) The speakers did work with pre-release before SuSE 11.1 RC1 if that helps any. I did a full clean install when I upgraded. from the above, I'm suspecting that Yast is identifiying the Intel chipset incorrectly? Thank you, Michael -- ***************** Thank You, Michael A. Sterba ARS - KG7HQ Assistant Director/Technical Specialist Northwest Division - ARRL kg7hq@arrl.net http://www.kg7hq.wetnet.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Dec 28, 2008 at 8:00 PM, Michael A. Sterba <cwo.usnr@verizon.net> wrote:
On Saturday 27 December 2008 19:02:14 medwinz wrote: cat /proc/asound/card0/codec#* | grep Codec Codec: Conexant CX20561 (Hermosa) Codec: Conexant ID 2c06
Please chek if CX20561 or 2c06 is in the list of your /usr/src/linux-2.6.27.7-9/Documentation/sound/alsa/ALSA-Configuration.txt
less /etc/modprobe.d/sound options snd-hda-intel enable=1 index=0 # u1Nb.kXwNWe4doZB:82801I (ICH9 Family) HD Audio Controller alias snd-card-0 snd-hda-intel options snd slots=snd-hda-intel options snd-hda-intel model=thinkpad ##Added manually to engage speakers(no effect)
backup your /etc/modprobe.d/sound, and could you change it a bit become options snd slots=snd-hda-intel options snd-hda-intel model=thinkpad # u1Nb.kXwNWe4doZB:82801I (ICH9 Family) HD Audio Controller alias snd-card-0 snd-hda-intel alias sound-slot-0 snd-hda-intel and see what happen. regards, medwinz -- Fran Lebowitz - "My favorite animal is steak." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 28 December 2008 06:12:08 medwinz wrote: Hello medwinz,
Please chek if CX20561 or 2c06 is in the list of your /usr/src/linux-2.6.27.7-9/Documentation/sound/alsa/ALSA-Configuration.txt
I had checked this before the last email and didn't find any references to either CX20561 or 2c06. I had saw an earlier post you sent out as I thought this would be a possible solution.
backup your /etc/modprobe.d/sound, and could you change it a bit become
options snd slots=snd-hda-intel options snd-hda-intel model=thinkpad # u1Nb.kXwNWe4doZB:82801I (ICH9 Family) HD Audio Controller alias snd-card-0 snd-hda-intel alias sound-slot-0 snd-hda-intel
End result is no change. I rechecked Kmixer to see if a option for the speakers to be selected had shown and I wasn't successful. I see there are many posts on the CX20561 for windows but haven't found anything for driver or setup information for Linux. I'm still looking though as I'm sure I'm not the only one with this situation. I'm surprised to not see the AD1984 series instead of the Conexant hardware. -- ***************** Thank You, Michael -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello Team I found when I remove esound from my system it allows for speaker audio now. But.... There is always a but...... It doesn't work unless I issue a rcalsasound restart command from root after I boot up. Pulse audio didn't seem to be the issue on this laptop. Thoughts?? -- ***************** Thank You, Michael A. Sterba ARS - KG7HQ Assistant Director/Technical Specialist Northwest Division - ARRL kg7hq@arrl.net http://www.kg7hq.wetnet.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, Dec 30, 2008 at 7:57 AM, Michael A. Sterba <cwo.usnr@verizon.net> wrote:
Hello Team
I found when I remove esound from my system it allows for speaker audio now. But.... There is always a but...... It doesn't work unless I issue a rcalsasound restart command from root after I boot up.
Pulse audio didn't seem to be the issue on this laptop.
Thoughts??
CMIIW, pulseaudio is a replacement for esound. So you just need one of them. Seems like alsa still confuse to initiate the soundcard module so there is always a but .... :-) I hope openSUSE-team will fix this problem soon. regards, medwinz -- W. C. Fields - "I never drink water; that is the stuff that rusts pipes." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
medwinz schreef:
On Sun, Dec 28, 2008 at 8:00 PM, Michael A. Sterba <cwo.usnr@verizon.net> wrote:
On Saturday 27 December 2008 19:02:14 medwinz wrote: cat /proc/asound/card0/codec#* | grep Codec Codec: Conexant CX20561 (Hermosa) Codec: Conexant ID 2c06
Please chek if CX20561 or 2c06 is in the list of your /usr/src/linux-2.6.27.7-9/Documentation/sound/alsa/ALSA-Configuration.txt
less /etc/modprobe.d/sound options snd-hda-intel enable=1 index=0 # u1Nb.kXwNWe4doZB:82801I (ICH9 Family) HD Audio Controller alias snd-card-0 snd-hda-intel options snd slots=snd-hda-intel options snd-hda-intel model=thinkpad ##Added manually to engage speakers(no effect)
backup your /etc/modprobe.d/sound, and could you change it a bit become
options snd slots=snd-hda-intel options snd-hda-intel model=thinkpad # u1Nb.kXwNWe4doZB:82801I (ICH9 Family) HD Audio Controller alias snd-card-0 snd-hda-intel alias sound-slot-0 snd-hda-intel
and see what happen.
regards, medwinz
I have a Acer Laptop Aspire 5315 In Yast I find: 82801H (ICH8 Family) HD Audio Controller configured as sound card number 0 driverprogram snd-hda-intel In /modprobe.d/sound: options snd slots=snd-hda-intel #u1Nb.xqPQcijbrk4:82801H (Audio Controller alias snd-card-0 snd-hda-intel Should I add the lines: options snd-hda-intel model=thinkpad and alias sound-slot-0 snd-hda-intel But what instead of thinkpad? TIA André den Oudsten -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 30 December 2008 04:12:33 Andre den Oudsten wrote: Hello Andre,
Should I add the lines:
options snd-hda-intel model=thinkpad
and alias sound-slot-0 snd-hda-intel
But what instead of thinkpad?
I'm by far not the expert but instead of "thinkpad", I'd use "laptop". I hope that helps.... -- ***************** Thank You, Michael A. Sterba -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Michael A. Sterba schreef:
On Tuesday 30 December 2008 04:12:33 Andre den Oudsten wrote:
Hello Andre,
Should I add the lines:
options snd-hda-intel model=thinkpad
and alias sound-slot-0 snd-hda-intel
But what instead of thinkpad?
I'm by far not the expert but instead of "thinkpad", I'd use "laptop". I hope that helps....
It did not. So I'm lost now. André den Oudsten -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 31 December 2008 02:54:07 am Andre den Oudsten wrote:
I'm by far not the expert but instead of "thinkpad", I'd use "laptop". I hope that helps....
It did not. So I'm lost now. André den Oudsten
Hello Andre, I finally downgraded the desktop from KDE 4.1 to KDE 3.5. I now don't have any issues with sound. There is something that still needs work on Kmixer's interface. :( It is a work in progress. Michael -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, Dec 30, 2008 at 7:12 PM, Andre den Oudsten <AdenOudsten@wxs.nl> wrote:
I have a Acer Laptop Aspire 5315 In Yast I find: 82801H (ICH8 Family) HD Audio Controller configured as sound card number 0 driverprogram snd-hda-intel
In /modprobe.d/sound:
options snd slots=snd-hda-intel #u1Nb.xqPQcijbrk4:82801H (Audio Controller alias snd-card-0 snd-hda-intel
Should I add the lines:
options snd-hda-intel model=thinkpad
and alias sound-slot-0 snd-hda-intel
But what instead of thinkpad?
Andre, if you really have problem with the sound please invoke "cat /proc/asound/card0/codec#* | grep Codec" in terminal as root and compare the result with /usr/src/linux-2.6.27.7-9/Documentation/sound/alsa/ALSA-Configuration.txt. You can see there are a lot of model for snd-hda-intel module in that file. Then you can modify the /etc/modprobe.d/sound. You can always refer to http://en.opensuse.org/SDB:Intel-HDA_sound_problems, I also write my experience on http://medwinz.blogsome.com/2008/12/26/workaround-for-sound-problem-on-opens... regards, medwinz -- Samuel Goldwyn - "Include me out." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
medwinz wrote:
On Sun, Dec 28, 2008 at 5:34 AM, Michael A. Sterba <cwo.usnr@verizon.net> wrote:
I have enabled all channels... These are what's available.... Front, PCM, IEC958 (Only with mute function), IEC958 Default PCM (Only with mute function), Digital, External Mic (capture), Internal Mic and Internal Mic (capture).
The title of the window is HDA Intel
Could you post the result of "cat /proc/asound/card0/codec#* | grep Codec"
How is /etc/modprobe.d/sound configured? using Yast or alsaconf?
regards, medwinz
Thanks medwinz for replying... (I think you are replying to me, at least to the thread I started, but you cut and pasted something from a different thread...) Anywise this may be an interesting lead? The results of doing the cat and grep for Codec did not produce any result. However I investigated a bit and discovered the following - nova:/ # cd /proc/asound/card0 nova:/proc/asound/card0 # ls capture-rates fx8010_tram_addr midi2 pcm2c ptr_regs00b wavetableD1 codec97#0 fx8010_tram_data midi3 pcm2p ptr_regs20a emu10k1 id oss_mixer pcm3p ptr_regs20b fx8010_acode io_regs pcm0c pcm4c ptr_regs20c fx8010_code midi0 pcm0p pcm4p spdif-in fx8010_gpr midi1 pcm1c ptr_regs00a voices So taking a guess I did the grep on the one directory that seems to have anything to do with codecs - nova:/etc/modprobe.d # cd /proc/asound/card0/codec97#0/ nova:/proc/asound/card0/codec97#0 # ls ac97#0-0 ac97#0-0+regs nova:/proc/asound/card0 # cat /proc/asound/card0/codec97#0/ac97#0-0* | grep -i codec Extended ID : codec=0 rev=1 AMAP DSA=0 SPDIF VRA Does this mean I am missing a Codec and if so how do I acquire it? As for your question on how I am configuring the sound system, I have tried using both Yast and alsaconf. (initially Yast, then alsaconf) I do not see any errors detected when I use either tool now. (after having blacklisted the module for cx88_alsa and restoring from the default blacklisted set emu10k1) Marc... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
medwinz wrote:
On Sat, Dec 27, 2008 at 9:48 AM, Marc Chamberlin <marc@marcchamberlin.com> wrote:
As a follow up, I have dropped back to SuSE11.0 and tried to bring up the sound system. Still no joy! So apparently this sound system failure has occurred for my sound card since 11.0??? I am rather stuck now, I tried to drop back to 10.3, which was working, but my installation CD failed. I would really like to get SuSE11.1 working, but I will start downloading 10.3 just in case I must go back to it...
Can you give the result of "cat /proc/asound/card0/codec# | grep Codec" also "cat /etc/modprobe.d/sound"
Please also inform rpm -qa | grep alsa rpm -qa | grep pulse rpm -q libasound2
regards, medwinz
Hello again medwinz - I just found this reply from you also, (spam filter caught it for some darn reason..) looks like another person has joined this thread with sound issues also, so hope this is not confusing you.. And again thanks for replying... I will put all the answers together in this response so you have everything to work with... Here is my previous response - Thanks medwinz for replying... (I think you are replying to me, at least to the thread I started, but you cut and pasted something from a different thread...) Anywise this may be an interesting lead? The results of doing the cat and grep for Codec did not produce any result. However I investigated a bit and discovered the following - nova:/ # cd /proc/asound/card0 nova:/proc/asound/card0 # ls capture-rates fx8010_tram_addr midi2 pcm2c ptr_regs00b wavetableD1 codec97#0 fx8010_tram_data midi3 pcm2p ptr_regs20a emu10k1 id oss_mixer pcm3p ptr_regs20b fx8010_acode io_regs pcm0c pcm4c ptr_regs20c fx8010_code midi0 pcm0p pcm4p spdif-in fx8010_gpr midi1 pcm1c ptr_regs00a voices So taking a guess I did the grep on the one directory that seems to have anything to do with codecs - nova:/etc/modprobe.d # cd /proc/asound/card0/codec97#0/ nova:/proc/asound/card0/codec97#0 # ls ac97#0-0 ac97#0-0+regs nova:/proc/asound/card0 # cat /proc/asound/card0/codec97#0/ac97#0-0* | grep -i codec Extended ID : codec=0 rev=1 AMAP DSA=0 SPDIF VRA Does this mean I am missing a Codec and if so how do I acquire it? As for your question on how I am configuring the sound system, I have tried using both Yast and alsaconf. (initially Yast, then alsaconf) I do not see any errors detected when I use either tool now. (after having blacklisted the module for cx88_alsa and restoring from the default blacklisted set emu10k1) ----- And here is the rest of the info that you requested - nova:/proc/asound/card0/codec97#0 # cat /etc/modprobe.d/sound alias snd-card-0 snd-emu10k1 alias sound-slot-0 snd-emu10k1 nova:/proc/asound/card0/codec97#0 # rpm -qa | grep alsa alsa-utils-1.0.18-6.4 alsa-firmware-1.0.17-1.42 alsa-1.0.18-8.7 alsa-plugins-1.0.18-6.12 alsa-plugins-pulse-1.0.18-6.12 alsa-oss-1.0.17-1.37 nova:/proc/asound/card0/codec97#0 # rpm -qa | grep pulse pulseaudio-module-zeroconf-0.9.12-9.6 libpulsecore4-0.9.12-9.6 libpulse-browse0-0.9.12-9.6 pulseaudio-utils-0.9.12-9.6 pulseaudio-module-x11-0.9.12-9.6 pulseaudio-module-bluetooth-0.9.12-9.6 pulseaudio-module-lirc-0.9.12-9.6 libpulse0-0.9.12-9.6 libxine1-pulse-1.1.15-20.8 pulseaudio-0.9.12-9.6 pulseaudio-esound-compat-0.9.12-9.6 libpulse-mainloop-glib0-0.9.12-9.6 alsa-plugins-pulse-1.0.18-6.12 pulseaudio-module-jack-0.9.12-9.6 nova:/proc/asound/card0/codec97#0 # rpm -q libasound2 libasound2-1.0.18-8.7 Marc... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon, Dec 29, 2008 at 8:15 AM, Marc Chamberlin <marc@marcchamberlin.com> wrote:
nova:/ # cd /proc/asound/card0 nova:/proc/asound/card0 # ls capture-rates fx8010_tram_addr midi2 pcm2c ptr_regs00b wavetableD1 codec97#0 fx8010_tram_data midi3 pcm2p ptr_regs20a emu10k1 id oss_mixer pcm3p ptr_regs20b fx8010_acode io_regs pcm0c pcm4c ptr_regs20c fx8010_code midi0 pcm0p pcm4p spdif-in fx8010_gpr midi1 pcm1c ptr_regs00a voices
nova:/etc/modprobe.d # cd /proc/asound/card0/codec97#0/ nova:/proc/asound/card0/codec97#0 # ls ac97#0-0 ac97#0-0+regs
Does this mean I am missing a Codec and if so how do I acquire it?
It looks like you miss it, but I' m not sure. You have emu10k1, but why ac97 listed here?
As for your question on how I am configuring the sound system, I have tried using both Yast and alsaconf. (initially Yast, then alsaconf) I do not see any errors detected when I use either tool now. (after having blacklisted the module for cx88_alsa and restoring from the default blacklisted set emu10k1)
That's also, blacklist also contains emu10k1. So I guess it should use the firmware or something, but according to /usr/src/linux-2.6.27.7-9/Documentation/sound/alsa/ALSA-Configuration.txt, emu10k1 is supported by the kernel. Check this document and search the word Audigy or snd-emu10k1 , you already install kernel-source, don't you? Please install it.
nova:/proc/asound/card0/codec97#0 # cat /etc/modprobe.d/sound alias snd-card-0 snd-emu10k1 alias sound-slot-0 snd-emu10k1
Try to follow the SDB, you can see the list here http://en.opensuse.org/Category:SDB:Sound and also troubleshooting from here http://en.opensuse.org/SDB:AudioTroubleshooting, make modification if needed. Hope this help. regards, medwinz -- Samuel Goldwyn - "Include me out." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Well I will top post and start a new thread, since I think this is a new topic, but leave my previous conversation with mdewinz attached below. I have made some progress getting my sound working but am not out of the woods yet. At this point I have sound but it is badly distorted so that still needs to be fixed... If anyone has gotten the Creative Labs Audigy Pro 4 sound card working under SuSE11.1 I would greatly appreciate knowing what you did. I have followed the openSuSE and ALSA documentation as best as I can figure and in the course of attempting different things, I discovered a few nasty side effects along the way. It appears that Yast and KDE are not really getting along well together. If I attempt to configure the sound system with Yast, it immediately kills the KMix sound controller and upon restarting it, I find that all my settings are reset to max volume levels and critical parts of the sound system are muted. KMix has also changed apparently in a significant manner, kinda for the better but also for the worse (IMHO) It allows me to decide what controls I want displayed in the mixer, which is a good idea because many are not used. But it also hides controls, and in particular those which have been muted somehow. Nor does it persist the selections properly and keeps forgetting which controls I have chosen to display and which ones I want hidden. Once I discovered all this, and track down which control was being muted, I was able to hear sound, though as I said it is badly distorted. I know that a right click on the KMix icon brings up a context sensitive menu which has a menu item for mute, but it is always checked and clicking on this item does not change the state of whether sound is muted or not. Nor does it change the state of the check mark... So I don't understand what that mute menu item is suppose to do, but would guess it is broken? If one is working on configuring the sound system, it sure seems like it would be a good idea to turn all mute controls off, automatically, for the duration of the time one is spending on configuring and setting up a sound system!!!! And since KMix or some other sound mixer is needed in order to hear sounds, why does YaST kill it? I don't understand how the sound tests in Yast will ever work, and so far I have been totally unsuccessful at getting any sound from the test buttons within the sound tool of YaST.... (I have mostly been using the KDE4 desktop configuration tool to experiment with instead.) Another oddity with YaST, why is it that every time I start up the sound configuration tool I find it telling me that my sound card is no longer configured? I keep going through the edit process to configure it, when I get done it seems to be OK, but when I come back later I find I have to configure it again!!?? Setting up this sound system has been a serious challenge, dunno why it had to be when it was working fine in SuSE10.3.... Anywise, enough throwing rocks ;-)... What I need most now is to figure out how to get the sound card working properly with undistorted sound.. So any and all help is much appreciated! Thanks in advance... Marc... Marc Chamberlin wrote:
medwinz wrote:
On Sat, Dec 27, 2008 at 9:48 AM, Marc Chamberlin <marc@marcchamberlin.com> wrote:
As a follow up, I have dropped back to SuSE11.0 and tried to bring up the sound system. Still no joy! So apparently this sound system failure has occurred for my sound card since 11.0??? I am rather stuck now, I tried to drop back to 10.3, which was working, but my installation CD failed. I would really like to get SuSE11.1 working, but I will start downloading 10.3 just in case I must go back to it...
Can you give the result of "cat /proc/asound/card0/codec# | grep Codec" also "cat /etc/modprobe.d/sound"
Please also inform rpm -qa | grep alsa rpm -qa | grep pulse rpm -q libasound2
regards, medwinz
Hello again medwinz - I just found this reply from you also, (spam filter caught it for some darn reason..) looks like another person has joined this thread with sound issues also, so hope this is not confusing you.. And again thanks for replying... I will put all the answers together in this response so you have everything to work with...
Here is my previous response -
Thanks medwinz for replying... (I think you are replying to me, at least to the thread I started, but you cut and pasted something from a different thread...) Anywise this may be an interesting lead? The results of doing the cat and grep for Codec did not produce any result. However I investigated a bit and discovered the following -
nova:/ # cd /proc/asound/card0 nova:/proc/asound/card0 # ls capture-rates fx8010_tram_addr midi2 pcm2c ptr_regs00b wavetableD1 codec97#0 fx8010_tram_data midi3 pcm2p ptr_regs20a emu10k1 id oss_mixer pcm3p ptr_regs20b fx8010_acode io_regs pcm0c pcm4c ptr_regs20c fx8010_code midi0 pcm0p pcm4p spdif-in fx8010_gpr midi1 pcm1c ptr_regs00a voices
So taking a guess I did the grep on the one directory that seems to have anything to do with codecs -
nova:/etc/modprobe.d # cd /proc/asound/card0/codec97#0/ nova:/proc/asound/card0/codec97#0 # ls ac97#0-0 ac97#0-0+regs
nova:/proc/asound/card0 # cat /proc/asound/card0/codec97#0/ac97#0-0* | grep -i codec Extended ID : codec=0 rev=1 AMAP DSA=0 SPDIF VRA
Does this mean I am missing a Codec and if so how do I acquire it?
As for your question on how I am configuring the sound system, I have tried using both Yast and alsaconf. (initially Yast, then alsaconf) I do not see any errors detected when I use either tool now. (after having blacklisted the module for cx88_alsa and restoring from the default blacklisted set emu10k1)
----- And here is the rest of the info that you requested -
nova:/proc/asound/card0/codec97#0 # cat /etc/modprobe.d/sound alias snd-card-0 snd-emu10k1 alias sound-slot-0 snd-emu10k1
nova:/proc/asound/card0/codec97#0 # rpm -qa | grep alsa alsa-utils-1.0.18-6.4 alsa-firmware-1.0.17-1.42 alsa-1.0.18-8.7 alsa-plugins-1.0.18-6.12 alsa-plugins-pulse-1.0.18-6.12 alsa-oss-1.0.17-1.37
nova:/proc/asound/card0/codec97#0 # rpm -qa | grep pulse pulseaudio-module-zeroconf-0.9.12-9.6 libpulsecore4-0.9.12-9.6 libpulse-browse0-0.9.12-9.6 pulseaudio-utils-0.9.12-9.6 pulseaudio-module-x11-0.9.12-9.6 pulseaudio-module-bluetooth-0.9.12-9.6 pulseaudio-module-lirc-0.9.12-9.6 libpulse0-0.9.12-9.6 libxine1-pulse-1.1.15-20.8 pulseaudio-0.9.12-9.6 pulseaudio-esound-compat-0.9.12-9.6 libpulse-mainloop-glib0-0.9.12-9.6 alsa-plugins-pulse-1.0.18-6.12 pulseaudio-module-jack-0.9.12-9.6
nova:/proc/asound/card0/codec97#0 # rpm -q libasound2 libasound2-1.0.18-8.7
Marc...
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Andre den Oudsten -
clarkt＠cnsp.com -
Marc Chamberlin -
medwinz -
Michael A. Sterba -
Rodney Baker