From: patrick reardon <swpatrick@earthlink.net>
To: Paul Davis <paul@linuxaudiosystems.com>
Cc: "alsa-devel@lists.sourceforge.net"
<alsa-devel@lists.sourceforge.net>,
"alsa-user@lists.sourceforge.net"
<alsa-user@lists.sourceforge.net>
Subject: Re: Hammerfall configuration
Date: Thu, 19 Dec 2002 13:52:26 -0600 [thread overview]
Message-ID: <3E02237A.7DC0FD55@earthlink.net> (raw)
In-Reply-To: 200212191130.18p6nx3RJ3NZFl40@penguin
Paul Davis wrote:
>
> >line added to /etc/rc.d/rc.sysinit:
> >
> >action "Loading ALSA Hammerfall driver" modprobe snd-rme9652
> >
> >/etc/modules.conf is set to load soundcore and snd-rme9652-mem before
> >snd-rme9 652, so this takes care of it.
>
> this is not quite right. rc.sysint should load just
> snd-rme9652-mem. it will work the way you have it, but there is no
> reason to load snd-rme9652 in rc.sysinit - this (unlike
> snd-rme9652-mem) will require loading of all of the ALSA
> infrastructure as well.
i go ahead and do it anyway so i don't have to bother with it later, but i see your
point. the *-mem module is the only one that really needs to be loaded early.
>
> >action "Setting Hammerfall as master clock" alsactl restore snd-rme9652
> >
> >can be added after the modprobe command.
>
> this will happen anyway if /etc/asound.state contains the relevant
> setting for the card. that is, if you've set it to master, and ALSA is
> shutdown normally, then /etc/asound.state will be used to reset the
> state when the alsasound init script runs.
ah. a few days ago i removed the alsasound init script and just did everything by hand
trying to debug this problem. guess i should put it back :-[
patrick
-------------------------------------------------------
This SF.NET email is sponsored by: Geek Gift Procrastinating?
Get the perfect geek gift now! Before the Holidays pass you by.
T H I N K G E E K . C O M http://www.thinkgeek.com/sf/
next parent reply other threads:[~2002-12-19 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200212191130.18p6nx3RJ3NZFl40@penguin>
2002-12-19 19:52 ` patrick reardon [this message]
[not found] <200212190924.18p4pc1V73NZFji0@eagle>
2002-12-19 19:15 ` Hammerfall configuration patrick reardon
2002-12-19 19:34 ` Paul Davis
2002-12-19 16:55 patrick reardon
2002-12-19 17:28 ` Paul Davis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E02237A.7DC0FD55@earthlink.net \
--to=swpatrick@earthlink.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-user@lists.sourceforge.net \
--cc=paul@linuxaudiosystems.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox