[PlanetCCRMA] (The continuing saga) Now for sound output

Fernando Lopez-Lezcano nando@ccrma.Stanford.EDU
Fri Mar 11 09:17:01 2005


On Thu, 2005-03-10 at 20:44, Peter Howard wrote:
> On Thu, 2005-03-10 at 19:15 -0800, Mark Knecht wrote:
> > On Fri, 11 Mar 2005 14:02:51 +1100, Peter Howard <pjh@coastal.net.au> wrote:
> > > Having got JACK running and my keyboard working under FC3, I come to the
> > > next hurdle - sound.  I have a suspicion that something like this was
> > > mentioned here recently, so sorry if I'm repeating.
> > > 
> > > (Again, this was working under FC2)
> > > 
> > > Here is the /var/log/messages output from restarting alsasound:
> > > 
> > > Mar 11 13:56:16 wagner alsasound: sound driver stop succeeded
> > > Mar 11 13:56:38 wagner kernel: ACPI: PCI interrupt 0000:00:1f.5[B] ->
> > > GSI 11 (level, low) -> IRQ 11
> > > Mar 11 13:56:39 wagner kernel: intel8x0_measure_ac97_clock: measured
> > > 49439 usecsMar 11 13:56:39 wagner kernel: intel8x0: clocking to 48000
> > > Mar 11 13:56:39 wagner alsasound: Starting sound driver snd-intel8x0
> > > succeeded
> > > Mar 11 13:56:39 wagner alsasound: Starting sound driver snd-intel8x0
> > > succeeded
> > > Mar 11 13:56:39 wagner alsasound: Starting sequencer succeeded
> > > Mar 11 13:56:39 wagner alsactl: /usr/sbin/alsactl: load_state:1267: No
> > > soundcards found...
> > > Mar 11 13:56:39 wagner alsasound: Restoring sound driver settings failed
> > 
> > No promises but delete the /etc/asound.state file. Alsa will recreate
> > it and hpefully the contents will be more in tune.
> 
> It's not getting recreated.  The errors for that just get skipped and it
> still makes the sysfs/udev complaint.

You have to use alsamixer or gamix (or your favorite mixer) to unmute
the channels you are interested in and set their gains. After that do a:
  /usr/sbin/alsactl store
that will create the /etc/asound.state file (and that one will get
reloaded on a boot). At any point you can do a:
  /usr/sbin/alsactl restore
to reload the saved settings.

-- Fernando