sound device not found/listed on new system, reboot helps sometimes

[sabo007]

Hi,
i have a new system since last week, with an ASUS X99 Deluxe II mainboard. Intially i had no real problems with the system, especially with the sound. But as i started my system yesterday there was no sound anymore, there was not even a sound device listed in the sound settings of plasma, then after i did a reboot, the soudn device was there again and everything was fine.
Today i have the same problems.

To nail down the problem, i saved the output of

sudo lspci -v | grep -A7 -i "audio"

as the sound device was there and also when its not, here are the results:
if the sound device is there:

00:1b.0 Audio device: Intel Corporation C610/X99 series chipset HD Audio Controller (rev 05)
        Subsystem: ASUSTeK Computer Inc. Device 8699
        Flags: bus master, fast devsel, latency 0, IRQ 63, NUMA node 0
        Memory at fb430000 (64-bit, non-prefetchable) [size=16]
        Capabilities: [50] Power Management version 2
        Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
        Capabilities: [100] Virtual Channel
--
01:00.1 Audio device: NVIDIA Corporation GK104 HDMI Audio Controller (rev a1)
        Subsystem: ZOTAC International (MCO) Ltd. Device 1260
        Physical Slot: 4
        Flags: bus master, fast devsel, latency 0, IRQ 64, NUMA node 0
        Memory at fb080000 (32-bit, non-prefetchable) [size=16]
        Capabilities: [60] Power Management version 3
        Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [78] Express Endpoint, MSI 00

and this is the output when it is not there:

00:1b.0 Audio device: Intel Corporation C610/X99 series chipset HD Audio Controller (rev 05)
        Subsystem: ASUSTeK Computer Inc. Device 8699
        Flags: fast devsel, IRQ 7, NUMA node 0
        Memory at fb430000 (64-bit, non-prefetchable) [disabled] [size=16]
        Capabilities: [50] Power Management version 2
        Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
        Capabilities: [100] Virtual Channel
--
01:00.1 Audio device: NVIDIA Corporation GK104 HDMI Audio Controller (rev a1)
        Subsystem: ZOTAC International (MCO) Ltd. Device 1260
        Physical Slot: 4
        Flags: bus master, fast devsel, latency 0, IRQ 10, NUMA node 0
        Memory at fb080000 (32-bit, non-prefetchable) [size=16]
        Capabilities: [60] Power Management version 3
        Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [78] Express Endpoint, MSI 00

the second entry is for the hdmi device of my NVIDIA graphic card, but as you can see, the difference in the first entry is that in the last case there is something disabled!

I do not know what this means, i hope is not something serious (a sign that the sound device is dying or something like that). Tell me please if you need some more information and which.[/size][/size][/size][/size]

[Akoellh]

Am Tue, 22 Nov 2016 23:46:01 GMT
schrieb sabo007 <sabo007@no-mx.forums.microfocus.com>:

> Hi,
> i have a new system since last week, with an ASUS X99 Deluxe II
> mainboard. Intially i had no real problems with the system, especially
> with the sound. But as i started my system yesterday there was no sound
> anymore, there was not even a sound device listed in the sound settings
> of plasma, then after i did a reboot, the soudn device was there again
> and everything was fine.
> Today i have the same problems.
>
> To nail down the problem, i saved the output of
> Code:
> --------------------
> sudo lspci -v | grep -A7 -i “audio”
> --------------------
> as the sound device was there and also when its not, here are the
> results:
> if the sound device is there:
>
> Code:
> --------------------
> 00:1b.0 Audio device: Intel Corporation C610/X99 series chipset HD Audio
> Controller (rev 05) Subsystem: ASUSTeK Computer Inc. Device 8699
> Flags: bus master, fast devsel, latency 0, IRQ 63, NUMA node 0
> Memory at fb430000 (64-bit, non-prefetchable) [size=16]
> Capabilities: [50] Power Management version 2
> Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
> Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
> Capabilities: [100] Virtual Channel
> –
> 01:00.1 Audio device: NVIDIA Corporation GK104 HDMI Audio Controller (rev
> a1) Subsystem: ZOTAC International (MCO) Ltd. Device 1260
> Physical Slot: 4
> Flags: bus master, fast devsel, latency 0, IRQ 64, NUMA node 0
> Memory at fb080000 (32-bit, non-prefetchable) [size=16]
> Capabilities: [60] Power Management version 3
> Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
> Capabilities: [78] Express Endpoint, MSI 00
> --------------------
>
>
> and this is the output when it is not there:
>
> Code:
> --------------------
> 00:1b.0 Audio device: Intel Corporation C610/X99 series chipset HD Audio
> Controller (rev 05) Subsystem: ASUSTeK Computer Inc. Device 8699
> Flags: fast devsel, IRQ 7, NUMA node 0
> Memory at fb430000 (64-bit, non-prefetchable) [disabled] [size=16]
> Capabilities: [50] Power Management version 2
> Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+
> Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
> Capabilities: [100] Virtual Channel
> –
> 01:00.1 Audio device: NVIDIA Corporation GK104 HDMI Audio Controller (rev
> a1) Subsystem: ZOTAC International (MCO) Ltd. Device 1260
> Physical Slot: 4
> Flags: bus master, fast devsel, latency 0, IRQ 10, NUMA node 0
> Memory at fb080000 (32-bit, non-prefetchable) [size=16]
> Capabilities: [60] Power Management version 3
> Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
> Capabilities: [78] Express Endpoint, MSI 00
> --------------------
>
>
> the second entry is for the hdmi device of my NVIDIA graphic card, but
> as you can see, the difference in the first entry is that in the last
> case there is something disabled!
>
> I do not know what this means, i hope is not something serious (a sign
> that the sound device is dying or something like that). Tell me please
> if you need some more information and which.
>
>

Post the output of:

cat /proc/asound/cards

AK

–
Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)

[/size][/size][/size][/size]

[sabo007]

/proc/asound does not exist, but thats maybe because i am currently booted with non working sound, as i said in this case the device is not listed in any GUI tools and probably not existing in /proc, but i will post the result the when i do a reboot and the sound device is probably back again.

[Akoellh]

Am Wed, 23 Nov 2016 00:06:13 GMT
schrieb sabo007 <sabo007@no-mx.forums.microfocus.com>:

> /proc/asound does not exist, but thats maybe because i am currently
> booted with non working sound, as i said in this case the device is not
> listed in any GUI tools and probably not existing in /proc, but i will
> post the result the when i do a reboot and the sound device is probably
> back again.
>
>

That’s odd.

My suspicion was (as bot cards most likely will use the snd-hda-intel
module) the cards are detected in somewhat “random” order and depending on
which one gets detected first (ans gets “card0”) you have sound or not.

This is a rather common issue but not having any sound card at all is certainly
not what I expected.

Are there any sound modules loaded?

lsmod| grep snd

If not, what happens after running

modprobe -v snd-hda-intel

as root?

AK

–
Never attribute to malice that which can be adequately explained by stupidity.
(R.J. Hanlon)

[gogalthorp]

Sounds like a hardware issue. Flaky sound chip. New hardware often fails in the first few days or it runs forever

[sabo007]

Did a reboot, the the sound device is back again. Btw. when there is no sound, then no sound device is found at all.
Now the output of /proc/asound/cards is:

 0 [PCH            ]: HDA-Intel - HDA Intel PCH
                      HDA Intel PCH at 0xfb430000 irq 64
 1 [NVidia         ]: HDA-Intel - HDA NVidia
                      HDA NVidia at 0xfb080000 irq 63

the output of: lsmod | grep snd
is:

snd_hda_codec_hdmi     53248  1
snd_hda_codec_realtek    94208  1
snd_hda_codec_generic    77824  1 snd_hda_codec_realtek
snd_hda_intel          40960  5
snd_hda_codec         147456  4 snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
snd_hda_core           90112  5 snd_hda_intel,snd_hda_codec,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek
snd_hwdep              16384  1 snd_hda_codec
snd_pcm               135168  4 snd_hda_intel,snd_hda_codec,snd_hda_core,snd_hda_codec_hdmi
snd_timer              36864  1 snd_pcm
snd                    94208  18 snd_hda_intel,snd_hwdep,snd_hda_codec,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek,snd_pcm
soundcore              16384  1 snd

I can post the output again on next boot when the sound probably will be gone again.

I hope it is not the sound chip, that would be very stressful.

[sabo007]

Maybe the problem is related to this here?

Also i had no problems with the older kernel, just with 4.8.8-1 maybe this will get fixed in a newer kernel.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1551880

[sabo007]

Ok i have an update:
since the device was gone again after e rebooted the system, actually both devices, (no entry in /proc, the vlume settings hat only “dummy device” listed as output device).
i took a look in Yast Sound device configuration and surprisingly both devices where listed here, but in an uninitialised / non configured state.
So i selected the onput sound device, and did a automatic normal configuration. As that was finished the device was there again and usable.

So it seems that on every other boot the device (both devices) are simply not configured.
What can the the cause of this? Probably i kernel issue i guess, until the next kernel update i can live with the current situation, because i can reinstate the device without rebooting .

[oldcpu]

@sabo007

Ok i have an update:
since the device was gone again after e rebooted the system, actually both devices, (no entry in /proc, the vlume settings hat only “dummy device” listed as output device).
i took a look in Yast Sound device configuration and surprisingly both devices where listed here, but in an uninitialised / non configured state.
So i selected the onput sound device, and did a automatic normal configuration. As that was finished the device was there again and usable.

So it seems that on every other boot the device (both devices) are simply not configured.
What can the the cause of this? Probably i kernel issue i guess, until the next kernel update i can live with the current situation, because i can reinstate the device without rebooting .

I may be able to fix this if both devices (HDMI and analog sound) use the snd-hda-intel module - but to do so I need more info.

(1) Please post here the content of /etc/modprobe.d/50-sound.conf (only if there is such a file - there may not be), and

(2) Please in a konsole/xterm, with pc connected to the internet, as a regular user, send this command:

/usr/sbin/alsa-info.sh

and select the SHARE/UPLOAD option. Let the script complete. When it completes, look in the konsole/xterm and it will have passed to you a web-address/URL that you are to share with the person trying to help. Please post that URL/web address here.

The script will give information on your hardware, including the precise PCI hardware numbers of the audio devices. Armed with that information I can provide code to add to the /etc/modprobe.d/50-sound conf file that will force the appropriate device to be sound card-0 on every boot (and not change randomly at different boots).
.

[Tyler_K]

[quote="“oldcpu,post:9,topic:122210”]
I may be able to fix this if both devices (HDMI and analog sound) use the snd-hda-intel module - but to do so I need more info

@sabo007"

To nail down the problem, i saved the output of

sudo lspci -v | grep -A7 -i "audio"

as the sound device was there and also when its not, here are the results:…Tell me please if you need some more information and which.

[/QUOTE]In this case*, grepping with the “-A7” may still truncate relevant information from the lspci command’s output … such as what oldcpu was inquiring about. You can get it via several different ways, but for giggles (at using an ugly method) try:

/sbin/lspci |grep Audio | for x in `awk '{ print $1 }'`; do /sbin/lspci -vnn -s $x; done

• you’ll get a slightly different level of output when running the command as user than when running as root/su

[sabo007]

@oldcpu
thank you, that is very nice of you.

here is the content of /etc/modprobe.d/50-sound.conf
but it could be that this file was created as i manually activated / configured the onboard sound device only, after the last boot where both devices where deactivated/not configured.

options snd slots=snd-hda-intel
# u1Nb.Drl6lWjwJZB:C610/X99 series chipset HD Audio Controller
alias snd-card-0 snd-hda-intel

This boot, both devices where properly activated (but i also did a kernel update, maybe this is relevant).
Anyway here is the link to the results of /usr/sbin/alsa-info.sh as a regular user:
http://www.alsa-project.org/db/?f=0105d6146635d7aed764ae267635b760618ff0e1

but as stated in the beginning of the thread, i am not sure if the device number is the problem here, but i will try want you provide anyway.

[oldcpu]

@sabo007

here is the content of /etc/modprobe.d/50-sound.conf

options snd slots=snd-hda-intel
# u1Nb.Drl6lWjwJZB:C610/X99 series chipset HD Audio Controller
alias snd-card-0 snd-hda-intel

This boot, both devices where properly activated (but i also did a kernel update, maybe this is relevant).
Anyway here is the link to the results of /usr/sbin/alsa-info.sh as a regular user:
http://www.alsa-project.org/db/?f=0105d6146635d7aed764ae267635b760618ff0e1

Thankyou

From the diagnostic script I note:

!!Loaded ALSA modules
!!-------------------
snd_hda_intel
snd_hda_intel

ie you have two instances of the same sound module, one associated with each different hardware audio device. Unfortunately YaST hardware sound application does not work well in configuring this sort of setup.

Note also

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

 0 **PCH**            ]: HDA-Intel - HDA Intel PCH
                      HDA Intel PCH at 0xfb430000 irq 64
 1 **NVidia**         ]: HDA-Intel - HDA NVidia
                      HDA NVidia at 0xfb080000 irq 63


!!PCI Soundcards installed in the system
!!--------------------------------------

**00:1b.0** Audio device: **Intel** Corporation C610/X99 series chipset HD Audio Controller (rev 05)
**01:00.1** Audio device: **NVIDIA** Corporation GK104 **HDMI** Audio Controller (rev a1)

**
!!Advanced information - PCI Vendor/Device/Subsystem ID's**
!!-------------------------------------------------------

**00:1b.0** 0403: **8086:8d20** (rev 05)
    Subsystem: 1043:8699
--
**01:00.1** 0403: **10de:0e0a** (rev a1)
    Subsystem: 19da:1260

From that we can see for this boot, the analog audio (PCH) 00:1b.0 (8086:8d20) is sound card-0 and further Nvidia HDMI is 01:00.1 (10de:0e0a). Note in particular the PCI assignments.

By default, audio works with sound card-0. So I am assuming you do not use HDMI and that you use analog audio.

So lets force the sound module associated with the analog hardware to be sound card-0 (and the other sound card-1).

Apply this edit to the /etc/modprobe.d/50-sound.conf file (replacing the previous content):

options snd_hda_intel index=0 vid=8086 pid=8d20
options snd_hda_intel index=1 vid=10de pid=0e0a

reboot and test your audio. You may need to install and then launch the application pavucontrol to configure each application to use sound card-0, in case for some reason that is not the default setup.

[sabo007]

Thank you, i applied the changes and at least the first reboot came with working sound! Both devices are listed and are working (i only tested the onboard sound because i have no HDMI device for testing).
So at least we can say, that your configuration seems to work in principle (the configuration i had before also worked in 50% of all boots)

[oldcpu]

@sabo007

Thank you, i applied the changes and at least the first reboot came with working sound! Both devices are listed and are working (i only tested the onboard sound because i have no HDMI device for testing).
So at least we can say, that your configuration seems to work in principle (the configuration i had before also worked in 50% of all boots)

OK …glad to read the first reboot worked. Subsequent ones should also work if my understanding was correct.

Again the assumption and philosophy was as follows: The assumption is in your PC, upon different boots, sometimes HDMI hardware device would be assigned to sound-card-0 and sometimes the analog sound hardware would be assigned to soundcard-0. The openSUSE “standard” is the default sound device used by all applications is sound card-0. So by your /etc/modprobe.d/50-sound.conf file edit, you have configured alsa that upon boot it is to assign (via using the PCI designation) the analogue sound device to always be sound card-0.