Dear Elimar,
Sorry for the late reply. I ran some more tests.
On 12/18/16 21:12, Elimar Riesebieter wrote:
* Paul Menzel <pmen...@molgen.mpg.de> [2016-12-18 20:52 +0100]:
[...]
As you found out by quoting alsactl's manpage that your device is not
known.
Do you have an idea, why it wasn’t initialized on my system?
Does sound work on your system?
Just starting the system to the graphical login manager (LightDM,
lightdm-gtk-greeter) no sound cards are detected, and no sound can be
played (MPlayer outputs `Audio device got stuck!`) when logging in over SSH.
```
$ aplay -l
aplay: device_list:268: no soundcards found...
```
As soon as I log into a graphical session, sound devices are detected
and I can play sound with no problem.
```
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
```
As mentioned before try
# alsactl init
Does it work?
```
$ sudo alsactl init
alsactl: sysfs_init:48: sysfs path '/sys' is invalid
Found hardware: "HDA-Intel" "Realtek ALC269VB"
"HDA:10ec0269,10280577,00100100 HDA:80862806,80860101,00100000" "0x1028"
"0x0577"
Hardware is initialized using a generic method
$ echo $?
99
$ ls -l /var/lib/alsa/
total 0
```
So that didn’t seem to have worked.
```
$ sudo alsactl store
$ ls -l /var/lib/alsa/
total 12
-rw-r--r-- 1 root root 9233 Dec 19 17:23 asound.state
```
After restarting the system, the udev error message is gone, as expected.
But functionality wise, nothing changed. Until I log in in the graphical
session no sound devices are found.
```
$ ls -l /var/lib/alsa/asound.state
-rw-r--r-- 1 root root 9233 Dec 19 17:23 /var/lib/alsa/asound.state
$ aplay -l
aplay: device_list:268: no soundcards found...
```
Kind regards,
Paul
