| 1 |
On Monday 10 Jul 2017 18:38:17 Ian Zimmerman wrote: |
| 2 |
> On 2017-07-11 00:11, Mick wrote: |
| 3 |
> > A few days ago I noticed as the operc messages pass by at boot time, |
| 4 |
> > alsasound boot service was complaining it can't find some |
| 5 |
> > files/settings. |
| 6 |
> |
| 7 |
> This may not be relevant, but just in case: I often get ALSA warnings |
| 8 |
> when booting with a newly built kernel. Apparently the way it stores |
| 9 |
> the mixer settings depends on the kernel version, and it gets slightly |
| 10 |
> confused when it finds ones saved under an earlier kernel. |
| 11 |
> |
| 12 |
> This has been happening for as long as I remember, on any distro, and I |
| 13 |
> learned to ignore it, because sound always works okay in spite of it. |
| 14 |
|
| 15 |
The boot error messages of alsasound not being able to set this or that do not |
| 16 |
come up every time. They showed up when I booted first thing this morn, then |
| 17 |
I set up rc logging and rebooted. No messages from alsa. :-/ |
| 18 |
|
| 19 |
Speakers & microphone work fine each time here too. |
| 20 |
|
| 21 |
What perplexes me is why alsa comes up with all these messages when an |
| 22 |
application calls it - linphone in this instance. Specifically why is it |
| 23 |
trying to find conf.c file from the fs path it happened to have been compiled |
| 24 |
in ... |
| 25 |
-- |
| 26 |
Regards, |
| 27 |
Mick |
Archives