Re: ?? user in group audio -- but only root can play sound
On Friday 22 January 2016 07:44:49 Jude DaShiell wrote:
> That has to be done inside of udev, udev is the one ring that binds
> them all.
>
Not nesessarily. When I rebooted sometime in late December, apparently a
udev update had decided that only root could use /dev/ttyUSB0 which is
connected to my cl11a, a programable X10 controller. I was un-aware of
it until a cron script that fires at 1 minute after midnight on 1 1 1
whatever, couldn't upload the next years schedule for my front deck
lights and cron sent me an email saying it had no permission. It has
only been working for 17 years folks.
I snooped thru the udev stuff without finding a specific rule
for /dev/ttyUSB*, and as that it the only device discovered at boot, I
couldn't compare it to /dev/ttyUSB1.
So I got out a root copy of nano, and put the fix in /etc/r.local, which
runs last at bootup, to readjust the ownership and rights to that
device. Now it looks like this:
crwxr-xr-x 1 gene gene 188, 0 Jan 22 08:07 /dev/ttyUSB0
And heyu is now a happy camper again.
Sure, someone is going to yell at me, but I built this box for ME to use,
and if its capable of doing a job, having some paranoid person decide I
can't use it like that, sucks dead toads thru soda straws, and tastes
about the same.
We, the users, buy or build the machine to USE and we WILL use it s/b the
message to whomever is in charge of udev presently.
My $0.02 USD, but adjust for inflation over the last 81 years...
> On Fri, 22 Jan 2016, Floris wrote:
> > Date: Fri, 22 Jan 2016 04:22:50
> > From: Floris <jkfloris@dds.nl>
> > To: debian-user@lists.debian.org
> > Subject: Re: ?? user in group audio -- but only root can play sound
> > Resent-Date: Fri, 22 Jan 2016 09:23:08 +0000 (UTC)
> > Resent-From: debian-user@lists.debian.org
> >
> > Op Fri, 22 Jan 2016 00:10:27 +0100 schreef Jude DaShiell
> >
> > <jdashiel@panix.com>:
> >> udev may be having adverse impacts on abilities to play sounds from
> >> certain cards after reboot. Anyone interested may find sound
> >> devices in black listed category they don't want to have black
> >> listed. Correcting such black listing for now is beyond my
> >> capability since I haven't done enough with udev to be safe working
> >> with ityet.
> >>
> >>>> Sorry, now I see you have multiple sound cards.
> >>>
> >>> My fault I should have mentioned it, sorry: That's it!
> >>>
> >>>
> >>> Since 2015-12-11 my /etc/modprobe/alsa-base.conf ist:
> >>> # PCH
> >>> options snd-hda-intel index=0 model=auto vid=8086 pid=9c20
> >>> # HDMI
> >>> options snd-hda-intel index=1 model=auto vid=8086 pid=0a0c
> >>>
> >>> this is (if I remember correctly) from Arch wiki and should
> >>> provide a numbering of sound devices such that the analog device
> >>> becomes default (first one). Since then I could hear music, hear
> >>> sound from movies but only till a week ago.
> >>>
> >>>
> >>> If I delete this file and reboot, the numbering of devices is:
> >>>
> >>> **** List of PLAYBACK Hardware Devices ****
> >>> card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0]
> >>> Subdevices: 1/1
> >>> Subdevice #0: subdevice #0
> >>> card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1]
> >>> Subdevices: 1/1
> >>> Subdevice #0: subdevice #0
> >>> card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2]
> >>> Subdevices: 1/1
> >>> Subdevice #0: subdevice #0
> >>> card 1: PCH [HDA Intel PCH], device 0: ALC3232 Analog [ALC3232
> >>> Analog] Subdevices: 1/1
> >>> Subdevice #0: subdevice #0
> >>>
> >>> Now mplayer -ao alsa:device=hw=1.0 works but aplay wav still does
> >>> not, mplayer does not without the command line switch and
> >>> interestingly mpd still works.
> >>>
> >>> How to tell linux that the analog device is the default device?
> >>> (I'll come back to this mailing list when I actually want to hear
> >>> sound through the HDMI device).
> >>>
> >>>
> >>>
> >>> Thanks a lot! This at least gives an explanation!
> >>>
> >>> Ciao; Gregor
> >
> > 3 Options:
> >
> > 1.
> > from http://alsa.opensrc.org/MultipleCards:
> >
> > ...
> > The newer "slots=" method
> >
> > Alternatively, you can use the slot option instead of the index
> > options: options snd slots=snd-interwave,snd-ens1371
> >
> > Then, the first slot (#0) is reserved for snd-interwave driver, and
> > the second (#1) for snd-ens1371. You can omit index option in each
> > driver if slots option is used (although you can still have them at
> > the same time as long as they don't conflict).
> > ...
> >
> > 2.
> > Move the unwanted soundcard to an empty seat:
> > find your card location with:
> > $ loginctl seat-status seat0
That command does not exist on wheezy. Sounds useful, what repo option
do I need to enable to get it?
> > [long list]
> > ...
> > /sys/devices/pci0000:00/0000:00:1b.0/sound/card0
> > ...
> > [long list]
> >
> > Attach the card to an other seat:
> > sudo loginctl attach seat1
> > /sys/devices/pci0000:00/0000:00:1b.0/sound/card0
> >
> > Now you can only use the card when you login on seat1, but as long
> > as you don't
> > attach a monitor, mouse and keyboard, the seat won't work. Note root
> > can still
> > access the card as all users in the audio group can. (That why I
> > asked you to remove yourself from the audio group)
> >
> > 3.
> > Blacklist the module, so nobody can access the card.
Thanks for reading this far.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Reply to: