Re: Re^2: A persistent name for a sound device.
On 2014-02-04, pe...@easthope.ca wrote: > Alan, > > * From: Alan Greenberger > *Date: Mon, 3 Feb 2014 09:34:42 -0500 >> When I plug in a Logitech C170 webcam, /proc/asound/cards shows: >> 0 [SB ]: HDA-Intel - HDA ATI SB >> HDA ATI SB at 0xfbdf4000 irq 16 >> 1 [HDMI ]: HDA-Intel - HDA ATI HDMI >> HDA ATI HDMI at 0xfbeec000 irq 44 >> 2 [C170 ]: USB-Audio - Webcam C170 >> Webcam C170 at usb-:00:13.2-4, high speed > > Suppose you reboot the machine without changing the hardware. > Does each device always retain its card number across the reboot? > In my case no. Consequently I can reboot and find that the > VoIP ring is being sent to the headset. Not acceptable. > > A persistent name remains associated with a specific device > across a reboot. > > Regards, ... Peter E. > The point was that even though the card number may change, I can use the device as -D hw:C170 without needing the card number. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnlf4fjs.fhg.alanjg@archduke.router
Re: Re^2: A persistent name for a sound device.
On my Debian desktop I created the following file: $ cat /etc/modprobe.d/sound.conf alias snd-card-0 snd-emu10k1 options snd-emu10k1 index=0 alias snd-card-1 snd-intel8x0 options snd-intel8x0 index=1 The emu10k1 is a PCI sound card and the intel8x0 is the onboard sound. I have the emu10k1 connected to my speakers while the intel8x0 is connected to my HF amateur radio for various digital communication modes. This arrangement has served me well for several years. I can still plug in a USB inteface and use the Pulse Audio Volume Control application (pavucontrol package) to direct the playing application to it. - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Ham radio, Linux, bikes, and more: http://www.n0nb.us -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140204191824.gp12...@n0nb.us
Re^2: A persistent name for a sound device.
On Tue, 2014-02-04 at 08:57 -0800, pe...@easthope.ca wrote: > Alan, > > * From: Alan Greenberger > * Date: Mon, 3 Feb 2014 09:34:42 -0500 > > When I plug in a Logitech C170 webcam, /proc/asound/cards shows: > > 0 [SB ]: HDA-Intel - HDA ATI SB > > HDA ATI SB at 0xfbdf4000 irq 16 > > 1 [HDMI ]: HDA-Intel - HDA ATI HDMI > > HDA ATI HDMI at 0xfbeec000 irq 44 > > 2 [C170 ]: USB-Audio - Webcam C170 > > Webcam C170 at usb-:00:13.2-4, high speed > > Suppose you reboot the machine without changing the hardware. > Does each device always retain its card number across the reboot? > In my case no. Consequently I can reboot and find that the > VoIP ring is being sent to the headset. Not acceptable. > > A persistent name remains associated with a specific device > across a reboot. As already mentioned before, this is done by /etc/modprobe.d/alsa-base.conf my e.g. does look like that: Arch Linux 64-bit [rocketmouse@archlinux ~]$ cat /etc/modprobe.d/alsa-base.conf # ALSA module ordering options snd slots=snd_hdspm,snd_ice1712,snd_ice1712 Debian 32-bit [rocketmouse@archlinux ~]$ cat /mnt/debi386/etc/modprobe.d/alsa-base.conf # autoloader aliases install sound-slot-0 /sbin/modprobe snd-card-0 install sound-slot-1 /sbin/modprobe snd-card-1 install sound-slot-2 /sbin/modprobe snd-card-2 install sound-slot-3 /sbin/modprobe snd-card-3 install sound-slot-4 /sbin/modprobe snd-card-4 install sound-slot-5 /sbin/modprobe snd-card-5 install sound-slot-6 /sbin/modprobe snd-card-6 install sound-slot-7 /sbin/modprobe snd-card-7 # Cause optional modules to be loaded above generic modules install snd /sbin/modprobe --ignore-install snd && { /sbin/modprobe --quiet snd-ioctl32 ; /sbin/modprobe --quiet snd-seq ; : ; } install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi && { /sbin/modprobe --quiet snd-seq-midi ; : ; } install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 && { /sbin/modprobe --quiet snd-emu10k1-synth ; : ; } # Keep snd-pcsp from beeing loaded as first soundcard options snd-pcsp index=-2 # Keep snd-usb-audio from beeing loaded as first soundcard options snd-usb-audio index=-2 # Prevent abnormal drivers from grabbing index 0 options bt87x index=-2 options cx88_alsa index=-2 options snd-atiixp-modem index=-2 options snd-intel8x0m index=-2 options snd-via82xx-modem index=-2 # ALSA module ordering options snd slots=snd_hdspm,snd_ice1712,snd_ice1712 Since Debian comes with default crap, the OP likely needs to remove # Keep snd-usb-audio from beeing loaded as first soundcard options snd-usb-audio index=-2 and add something like options snd slots=snd_usb_audio,snd_driver_x,snd_driver_y,snd_driver_n -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1391540039.5619.50.camel@archlinux
Re^2: A persistent name for a sound device.
Alan, * From: Alan Greenberger ine without changing the hardware. Does each device always retain its card number across the reboot? In my case no. Consequently I can reboot and find that the VoIP ring is being sent to the headset. Not acceptable. A persistent name remains associated with a specific device across a reboot. Regards, ... Peter E. -- 123456789 123456789 123456789 123456789 123456789 123456789 123456789 12 Tel +1 360 639 0202 http://carnot.yi.org/ New address Bcc: peter at easthope. ca -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/E1WAjJi-0001Iq-Tp@dalton.invalid
Re(2): A persistent name for a sound device.
* From: Scott Ferguson > KERNEL=="controlC3", ATTRS{idProduct}=="0008", ATTRS{id}=="Device", > ATTRS{product}=="C-Media USB Audio Device ", SYMLINK+="USBspeakers" > GROUP=="sound" Here ATTRS{idProduct} and ATTRS{product} are in the same node and you just said "one value per parent device". <*)))-{ > It might help if you posted the full path of the udev rule in case that > (it's name and location) is a problem. Turns out that this works. peter@dalton:~$ tail --lines=4 /etc/udev/rules.d/10-local.rules # The USB audio adapter connected to the speakers. #KERNEL=="controlC3", SUBSYSTEMS=="sound", SUBSYSTEMS=="usb", \ KERNEL=="controlC3", \ ATTRS{idProduct}=="0008", SYMLINK+="USBspeakers", GROUP="sound" It fails when 'SUBSYSTEMS=="sound", SUBSYSTEMS=="usb"' is included, whereas I expected the matching to be a little more efficient. > I thought the man page was the best guide, ... "If multiple keys that match a parent device are specified in a single rule, all these keys must match at one and the same parent device." So according to the manual, multiple keys on one device are OK. But definitely room for improvement on this topic of matching. > http://www.reactivated.net/writing_udev_rules.html It explains about matching multiple keys on one device? In any case, one solution is enough and simpler is better. Thanks for the help, ... Peter E. -- 123456789 123456789 123456789 123456789 123456789 123456789 123456789 12 Tel +1 360 639 0202 http://carnot.yi.org/ New address Bcc: peter at easthope. ca -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/E1WALWU-00028N-Ve@dalton.invalid