1 |
On Sat, 12 Aug 2017 12:31:45 -0400, |
2 |
Mick wrote: |
3 |
> |
4 |
> [1 <text/plain; us-ascii (quoted-printable)>] |
5 |
> On Saturday 12 Aug 2017 09:05:10 Ian Zimmerman wrote: |
6 |
> > On 2017-08-12 17:39, Alexander Kapshuk wrote: |
7 |
> > > (5). Postinst message for alsa-utils: |
8 |
> > > pkg_postinst() { |
9 |
> > > if [[ -z ${REPLACING_VERSIONS} ]]; then |
10 |
> > > elog |
11 |
> > > elog "To take advantage of the init script, and automate the process of" |
12 |
> > > elog "saving and restoring sound-card mixer levels you should" |
13 |
> > > elog "add alsasound to the boot runlevel. You can do this as" |
14 |
> > > elog "root like so:" |
15 |
> > > elog "# rc-update add alsasound boot" |
16 |
> > > ewarn |
17 |
> > > ewarn "The ALSA core should be built into the kernel or loaded through |
18 |
> > > other" ewarn "means. There is no longer any modular auto(un)loading in |
19 |
> > > alsa-utils." |
20 |
> > I don't get this last part. |
21 |
> > |
22 |
> > My ALSA is built as modules, including the core (I'm guessing that means |
23 |
> > snd.ko, right?). I don't do anything particular to load them, they're |
24 |
> > not listed in /etc/conf.d/modules. Yet the mixer save and restore via |
25 |
> > alsasound works. |
26 |
> > |
27 |
> > Could it be that alsasound itself loads the modules on demand, and the |
28 |
> > warning above is misleading? |
29 |
> |
30 |
> Did you run alsactl init to see if the alsa modules are probed and loaded |
31 |
> without errors? |
32 |
|
33 |
|
34 |
How about checking the various volumes rather than muting maybe some |
35 |
of them are 0 or rather some negative number or something? Also, you |
36 |
might delete the asound.state and let the system start over. Last |
37 |
resort, there is an alsa users mailing list. |
38 |
|
39 |
One other thought, get pulse audio out of the way and see if alsa is |
40 |
working. |
41 |
|
42 |
-- |
43 |
Your life is like a penny. You're going to lose it. The question is: |
44 |
How do |
45 |
you spend it? |
46 |
|
47 |
John Covici |
48 |
covici@××××××××××.com |