From: Chris Brannon <chris@the-brannons.com>
To: speakup@linux-speakup.org
Subject: Re: WARNING: Latest Linphone on Arch breaks device access
Date: Wed, 07 Sep 2016 15:01:25 -0700 [thread overview]
Message-ID: <87poofmksq.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20160907201909.GG1838@opera.rednote.net> (Janina Sajka's message of "Wed, 7 Sep 2016 16:19:09 -0400")
Janina Sajka <janina@rednote.net> writes:
> I now have in /etc/modprobe.d/alsa.conf the USB sound card device
> ordering that makes the trick you suggested work like a charm:
Aha. I had forgotten about that.
Anyway, here are the udev rules to name your cards. Unless I messed up
somewhere, these should give you the names Sennheiser and CMedia.
It's overly commented, partly for my benefit, because I don't
write udev rules too often.
Here's a link. I think mailman scrubs attachments, and I don't want it
to be mangled by pasting it inline.
http://the-brannons.com/misc/90-usbaudio-rename.rules
-- Chris
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
Janina Sajka
` Chris Brannon
` Janina Sajka
` John Covici
` Janina Sajka
` Chris Brannon
` Janina Sajka
` Janina Sajka
` Janina Sajka
` Chris Brannon [this message]
` Janina Sajka
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=87poofmksq.fsf@mushroom.localdomain \
--to=chris@the-brannons.com \
--cc=speakup@linux-speakup.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).