LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   Debian 8 - no sound at startup (https://www.linuxquestions.org/questions/linux-hardware-18/debian-8-no-sound-at-startup-4175563842/)

platypo 01-13-2016 11:33 AM

Debian 8 - no sound at startup
 
Hello! Problem is: When i power on the system (debian 8) tere is no sound by default. I have to unplug and replug the cinch cable to the pci soundcard, then it works.

I figured so far:
Daemons-log shows following entry after replugging the cable

Code:

01/13/16 06:18:31 PM        computer        rtkit-daemon[1416]        Successfully made thread 1910 of process 1769 (/usr/bin/pulseaudio) owned by '1000' RT at priority 5.
before i replug the cable top -H -p 1910 shows

Code:

1769 admin        9 -11  164304  8832  6740 S  0.0  0.4  0:00.08 pulseaudio                         
 1775 admin        -6  0  164304  8832  6740 S  0.0  0.4  0:00.00 alsa-source-AD1                     
 1776 admin        20  0  164304  8832  6740 S  0.0  0.4  0:00.00 null-sink

before and


Code:

1910 admin        -6  0  239136  9276  7132 S  1.0  0.4  0:01.50 alsa-sink-AD198                     
 1769 admin        9 -11  239136  9276  7132 S  0.3  0.4  0:00.86 pulseaudio                         
 1775 admin        -6  0  239136  9276  7132 S  0.0  0.4  0:00.00 alsa-source-AD1

afterwards.


lspci | grep audio shows:
Code:

00:0f.1 Audio device: NVIDIA Corporation MCP55 High Definition Audio (rev a2)
01:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1)

pulseaudio is started by systemd at boot, but i don't understand what's going on when i replug the cinch cable nor what to change to make it work again. I suppose it has to do with ownership because 'speaker-test' run by root gives output whereas no sound soundoutput when run by 1000. When replugging the cable it works fine Thanks in advance

Ztcoracat 01-13-2016 11:50 AM

You might want to post what sound card you have so others can give you a hand with this.
The command for finding out the snd crd is aplay -l (small letter L)

I can't imagine constantly having to unplug and re plug in the cable to the card.
I had the same problem with no sound and no matter what I tried nothing worked.

Hopefully other members will know how to fix this and chime in to advise you.
Sorry I don't know more.

https://wiki.debian.org/SoundFAQ
https://wiki.debian.org/PulseAudio
http://www.linuxquestions.org/questi...-sound-917079/

Shadow_7 01-14-2016 01:10 AM

Before replugging, check dmesg for if the module was loaded for the soundcard. And check again after replugging. It could be blacklisted in the /etc/modprobe.d/ stuff. Or pcspkr and other modules getting in the way. Or something less obvious like missing a .asoundrc. Or installing a package or two will auto-fix the issue.

# apt-get install alsa-base alsa-utils alsa-tools alsa-oss libasound2

Most of which is not installed by default or grabbed by pulse if you start with a minimum install with something like debootstrap.

platypo 01-14-2016 03:30 AM

Quote:

You might want to post what sound card you have so others can give you a hand with this.
The command for finding out the snd crd is aplay -l (small letter L)
it says:

Quote:

No protocol specified
xcb_connection_has_error() returned true
XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
card 0: NVidia_1 [HDA NVidia], device 0: AD1988B Analog [AD1988B Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia_1 [HDA NVidia], device 1: AD1988B Digital [AD1988B Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: NVidia_1 [HDA NVidia], device 2: AD1988B Alt Analog [AD1988B Alt Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 7: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 8: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: NVidia [HDA NVidia], device 9: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
The line about non-root-pulseaudio is the same as when i type 'alsactl --start' as root but i don't know what that means exactly. It seems to be 2 devices, a onboard soundcard for front side plugs and a pci device.

Quote:

Before replugging, check dmesg for if the module was loaded for the soundcard. And check again after replugging.
dmesg -wH doesn't show any changes, the only messages are shown in the daemon-log.
Quote:

It could be blacklisted in the /etc/modprobe.d/ stuff. Or pcspkr and other modules getting in the way. Or something less obvious like missing a .asoundrc.
It seems to be loaded scince 'speaker-test' run as root works fine, when run by admin it doesn't.

Quote:

Or installing a package or two will auto-fix the issue.
# apt-get install alsa-base alsa-utils alsa-tools alsa-oss libasound2

Most of which is not installed by default or grabbed by pulse if you start with a minimum install with something like debootstrap.

I consider something like 'dpkg-reconfigure pulseaudio' but as sort of a noob i am not fully aware of possible followup-issues. Could that cause any trouble?

Anyhow, thank you for answers.

Drakeo 01-14-2016 04:08 AM

apt-get install pavucontrol log out log back in. now open pavucontrol and set your device you want to use.

Shadow_7 01-14-2016 09:48 AM

If it works as root and doesn't as a user (admin/non-root), then you're probably not in the audio group.

$ groups

platypo 01-14-2016 10:40 AM

Quote:

If it works as root and doesn't as a user (admin/non-root), then you're probably not in the audio group.

$ groups
strangely that isn't the case. admin is in audio group. I guess it has something to do with the ownership (or the priority) of the thread of pulseaudio.

Quote:

apt-get install pavucontrol log out log back in. now open pavucontrol and set your device you want to use.
thanks, i'll try that on next boot.

platypo 01-15-2016 01:52 AM

Thanks! pavucontrol did the trick


All times are GMT -5. The time now is 08:53 PM.