pavucontrol shows USB headphones, but does not show HDA Intel device - openSuse 12.1

[rcbell]

Hi,
I'm using skype 2.2 on openSuse 12.1. On the sound device options, it will only let me select PulseAudio as a device. I use pavucontrol to set the devices, but the configuration tab only shows profiles for my HDMI Audio (on my Radeon HD graphics card) and my WebCam (which includes a mic). The motherboard-attached speakers (that work fine for all other apps) are not there, so I can't get skype to use them.

However, if I plug in a USB headset/microphone it then appears on the configuration tab, and I can configure and use it with skype. What do I need to do to get pavucontrol see my motherboard speakers?

My alsa-info:
http://www.alsa-project.org/db/?f=98...5c88e77da807f4

rpm -qa '*alsa*'
alsa-devel-1.0.24.1-23.1.2.x86_64
alsa-plugins-pulse-32bit-1.0.24-18.1.2.x86_64
alsa-plugins-pulse-1.0.24-18.1.2.x86_64
alsa-plugins-32bit-1.0.24-18.1.2.x86_64
alsa-oss-1.0.17-37.1.2.x86_64
alsa-plugins-1.0.24-18.1.2.x86_64
alsa-utils-1.0.24.2-12.8.1.x86_64
alsa-1.0.24.1-23.1.2.x86_64
alsa-oss-32bit-1.0.17-37.1.2.x86_64

rpm -qa '*pulse*'
pulseaudio-module-x11-1.1-1.2.x86_64
alsa-plugins-pulse-32bit-1.0.24-18.1.2.x86_64
libxine1-pulse-1.1.20-59.4.x86_64
libpulse-devel-1.1-1.2.x86_64
alsa-plugins-pulse-1.0.24-18.1.2.x86_64
pulseaudio-utils-1.1-1.2.x86_64
pulseaudio-module-jack-1.1-1.2.x86_64
pulseaudio-module-bluetooth-1.1-1.2.x86_64
pulseaudio-module-zeroconf-1.1-1.2.x86_64
libpulse0-1.1-1.2.x86_64
libpulse0-32bit-1.1-1.2.x86_64
pulseaudio-module-gconf-1.1-1.2.x86_64
libpulse-mainloop-glib0-1.1-1.2.x86_64
pulseaudio-1.1-1.2.x86_64
pulseaudio-lang-1.1-1.2.noarch
pulseaudio-module-lirc-1.1-1.2.x86_64

rpm -q libasound2
libasound2-1.0.24.1-23.1.2.x86_64


uname -a
Linux vicksburg 3.1.0-1.2-desktop #1 SMP PREEMPT Thu Nov 3 14:45:45 UTC 2011 (187dde0) x86_64 x86_64 x86_64 GNU/Linux

[jdmcdaniel3]

Hi,
I'm using skype 2.2 on openSuse 12.1. On the sound device options, it will only let me select PulseAudio as a device. I use pavucontrol to set the devices, but the configuration tab only shows profiles for my HDMI Audio (on my Radeon HD graphics card) and my WebCam (which includes a mic). The motherboard-attached speakers (that work fine for all other apps) are not there, so I can't get skype to use them.

However, if I plug in a USB headset/microphone it then appears on the configuration tab, and I can configure and use it with skype. What do I need to do to get pavucontrol see my motherboard speakers?

My alsa-info:
http://www.alsa-project.org/db/?f=98...5c88e77da807f4

rpm -qa '*alsa*'
alsa-devel-1.0.24.1-23.1.2.x86_64
alsa-plugins-pulse-32bit-1.0.24-18.1.2.x86_64
alsa-plugins-pulse-1.0.24-18.1.2.x86_64
alsa-plugins-32bit-1.0.24-18.1.2.x86_64
alsa-oss-1.0.17-37.1.2.x86_64
alsa-plugins-1.0.24-18.1.2.x86_64
alsa-utils-1.0.24.2-12.8.1.x86_64
alsa-1.0.24.1-23.1.2.x86_64
alsa-oss-32bit-1.0.17-37.1.2.x86_64

rpm -qa '*pulse*'
pulseaudio-module-x11-1.1-1.2.x86_64
alsa-plugins-pulse-32bit-1.0.24-18.1.2.x86_64
libxine1-pulse-1.1.20-59.4.x86_64
libpulse-devel-1.1-1.2.x86_64
alsa-plugins-pulse-1.0.24-18.1.2.x86_64
pulseaudio-utils-1.1-1.2.x86_64
pulseaudio-module-jack-1.1-1.2.x86_64
pulseaudio-module-bluetooth-1.1-1.2.x86_64
pulseaudio-module-zeroconf-1.1-1.2.x86_64
libpulse0-1.1-1.2.x86_64
libpulse0-32bit-1.1-1.2.x86_64
pulseaudio-module-gconf-1.1-1.2.x86_64
libpulse-mainloop-glib0-1.1-1.2.x86_64
pulseaudio-1.1-1.2.x86_64
pulseaudio-lang-1.1-1.2.noarch
pulseaudio-module-lirc-1.1-1.2.x86_64

rpm -q libasound2
libasound2-1.0.24.1-23.1.2.x86_64


uname -a
Linux vicksburg 3.1.0-1.2-desktop #1 SMP PREEMPT Thu Nov 3 14:45:45 UTC 2011 (187dde0) x86_64 x86_64 x86_64 GNU/Linux

Here is a trick that will switch KMIX, if you are using KDE, to look like the mixer of old and see if your sound card is there.

You need to edit your .bashrc file:

Alt-F2 kdesu ~/.bashrc

and add the following line and restart KDE (Logout and back in or just restart openSUSE)

export KMIX_PULSEAUDIO_DISABLE=1

You can revert back by removing the line and logout and back in again.

Thank You,

[oldcpu]

I note a 64-bit openSUSE-12.1 on a Dell Studio XPS 435MT with the 1.0.24 alsa driver, 1.24.1 alsa libraries and 1.24.2 alsa utilities. The hardare is an ALC1200 and also a USB device that provides a microphone.

I also note:

!!Soundcards recognised by ALSA
!!-----------------------------

 0 [Intel          ]: HDA-Intel - HDA Intel
                      HDA Intel at 0xfbdf8000 irq 44
 1 [HDMI           ]: HDA-Intel - HDA ATI HDMI
                      HDA ATI HDMI at 0xfbefc000 irq 45
 2 [U0x46d0x805    ]: USB-Audio - USB Device 0x46d:0x805
                      USB Device 0x46d:0x805 at usb-0000:00:1d.7-2, high speed

and note two instances of kernel module snd_hda_intel running (I speculate one for analog speakers and one for HDMI) and one instance of kernel module snd_usb_audio running (for your USB mic).

I also note this for playback

!!Aplay/Arecord output
!!------------

APLAY

**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC1200 Analog [ALC1200 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 1: ALC1200 Digital [ALC1200 Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 1: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
  Subdevices: 0/1
  Subdevice #0: subdevice #0

ie hw:0,0 is for your analog audio (speakers) and hw:0,1 is for analog (digital if you have digital connection) and hw:1,3 for your HDMI. I see NO reference to USB headphone, although I do see a USB mic in the arecord section.

Hence you should be able to play sound back to speakers (if using analog) with the command:

speaker-test -D hw:0,0 -c2 -l5 -twav

or if using digital with the command:

speaker-test -D hw:0,1 -c2 -l5 -twav

and play sound to HDMI with the command:

speaker-test -D hw:1,3 -c2 -l5 -twav

As to why you do not see anything in pavucontrol that is surprising.

I do note from the dmesg this error:

[   19.363752] ALSA patch_realtek.c:1277 realtek: No valid SSID, checking pincfg 0x4016a619 for NID 0x1d
[   19.363754] ALSA patch_realtek.c:1293 realtek: Enabling init ASM_ID=0xa619 CODEC_ID=10ec0888

which may or may not suggest the proper alsa configuration was not identified/applied upon boot. There is no model option for the ALC1200 that I am aware of, although I do recall my PC with an AD1989B was once upon a time misidentified as an ALC1200.

Can you provide a screen print of the pavucontrol 'configuration tab' so we can better understand your problem ?? Specifically I want to see what selection options are available. Take a look at the sample prints I provided in my blog for guidance as to the sort of print that would be useful: Pulseaudio Basics for openSUSE with pavucontrol - Blogs

[rcbell]

Thanks for your interest, oldcpu.

I did not have USB headset plugged in when I ran the alsa script, which is why you don't see it.

I'm attaching my pavucontrol snapshots. As you can see on my Configuration tab, my Radeon HD has a profile that only offers "Digital Stereo (HDMI) Output" and "Off". The webcam-microphone offers "Analog Mono Input" and "Off".

ImageBam - Fast, Free Image Hosting and Photo Sharing
ImageBam - Fast, Free Image Hosting and Photo Sharing

When I plug in my headset, it appears in the configuration tab with several options:
ImageBam - Fast, Free Image Hosting and Photo Sharing

You can also see my KDE-system settings for phonon:
ImageBam - Fast, Free Image Hosting and Photo Sharing

The ALC1200 analog is the device-speakers that I'm trying to get PA to use. It also shows up fine in KMix. In the device list, I'm able to get sound from it by clicking the "test" button, and all the devices work that way except the PulseAudio sound Server and the hw:0,1 (which doesn't have speakers plugged into it). When I test the devices with speaker test, both hw:0,0 and hw:1,3 respond with "Playback open error: -16,Device or resource busy", but as I said they are working.

Craig

[oldcpu]

The ALC1200 analog is the device-speakers that I'm trying to get PA to use. It also shows up fine in KMix. In the device list, I'm able to get sound from it by clicking the "test" button, and all the devices work that way except the PulseAudio sound Server and the hw:0,1 (which doesn't have speakers plugged into it). When I test the devices with speaker test, both hw:0,0 and hw:1,3 respond with "Playback open error: -16,Device or resource busy", but as I said they are working.

Thanks. I understand a bit better now, with a picture being worth a thousand words. I do not have an HDMI setup in our apartment, so its a bit more difficult for me to visualize.

I pulled out my Dell Studio 1537 laptop from storage (our apartment is small, and I only use this laptop on vacation or business trips) and took a look at its pavucontrol application gui. This laptop has an HDMI output that I never use. I noted this:

The configuration tab:

one can clearly see an extra entry there for the analog sound

The HDMI selections:


The analog audio selections:


... so that is sort of what you should be seeing, but are not. I understand now, but I don't know the solution.

The questions I ask myself are, why does this 'just work for me' and not for you. Please, no offence, but were you editing anything in the /etc/pulse directory ? or in the 'user' level equivalent ?

If not (no edits) than as a minimum we are in bug reporting territory. There is guidance on how to raise a bug report here: openSUSE:Submitting bug reports - openSUSE You can use your openSUSE forum user name and password when logging on to buzilla. Raise the bug against component 'sound'. Attach to the bug report the alsa-info.txt file you get by running:

/usr/sbin/alsa-info.sh --no-upload

and ensure your bug report is complete. Do not bother referencing this thread, as the openSUSE sound packager (who is also an alsa sound developer) will not read a forum thread. Watch the bug report (check every couple of days or so) and wait for a question from the packager. After answering a question, please be certain to CLEAR the NEED INFO flag, as that will tell the packager to look again at the bug report.

I don't know HDMI at all so there is not much else I can offer. I suppose we could compare the content of the four files in the /etc/pulse directory (client.conf, daemon.conf, default.pa, and system.pa) to see if my laptop has something obvious setup that is missing from your PC. However note that even if successful, it would not stop the bug from coming back next re-install, and it is far better to have a bug report and get this fixed.

I have access only in the evening (or very early morning) to this laptop, so if we are to compare file content, my replies may be a bit slow.

Good Luck.

[oldcpu]

I forgot to add ... my KDE phonon settings are MUCH more basic than yours. Yours is a surprise ...

Device preferences:


Audio Hardware setup: