On Thu, 2007-08-16 at 13:24 -0700, Wallace, Brooke wrote:
> Is having an audio group and making the devices owned by audio hardcoded
> into the software? Shouldn't defining groups and ownership be left upto
> the user/sysadmin and not the product?
>
No it's in the runtime configuration.
See the
Doesn't that also imply that anyone (or any app) must now also be a
member of the audio group? I think I'd much prefer to just allow anyone
in the users group access to the audio hardware.
-Brooke
> -Original Message-
> From: Wallace, Brooke
> Subject: RE: [Alsa-use
] On Behalf Of
> Jonathan Stowe
> Sent: Thursday, August 16, 2007 12:55 AM
> To: alsa-user@lists.sourceforge.net
> Subject: Re: [Alsa-user] Loading new ALSA modules
>
> On Thu, 2007-08-16 at 07:45 +0100, Jonathan Stowe wrote:
> > On Wed, 2007-08-15 at 16:42 -0700, Wallace, Broo
On Thu, 2007-08-16 at 07:45 +0100, Jonathan Stowe wrote:
> On Wed, 2007-08-15 at 16:42 -0700, Wallace, Brooke wrote:
...
> > brookew z: aplay testpcm1.wav
> > ALSA lib pcm_direct.c:1590:(snd_pcm_direct_parse_open_conf) The field
> > ipc_gid
> > must be a valid group (create group audio)
> > aplay:
On Wed, 2007-08-15 at 16:42 -0700, Wallace, Brooke wrote:
> Thanks, I fixed up the symlink to point to the new version.
> Unfortunately ALSA and RedHat disagree about where the libs should be
> installed - /lib vs /usr/lib...
>
> Seems like I'm closer, I was able to run alsamixer. But now aplay gi
PM
> To: alsa-user@lists.sourceforge.net
> Cc: Wallace, Brooke
> Subject: Re: [Alsa-user] Loading new ALSA modules
>
> > From: "Wallace, Brooke" <[EMAIL PROTECTED]>
>
> > I was able to unload the remaining snd* modules and then
> use insmod to
>
> From: "Wallace, Brooke" <[EMAIL PROTECTED]>
> I was able to unload the remaining snd* modules and then use insmod to
> loadup the modules generated by my compile of the alsa-drivers 1.0.14
> drop. However I'm not getting any sound now, and some utilities such as
> amixer and alsamixer are giving
That was indeed the case.
I was able to unload the remaining snd* modules and then use insmod to
loadup the modules generated by my compile of the alsa-drivers 1.0.14
drop. However I'm not getting any sound now, and some utilities such as
amixer and alsamixer are giving me Seg fault errors. What
On Tue, 14 Aug 2007, Wallace, Brooke wrote:
> This may be a sily question, but I just compiled that latest version of
> Alsa drivers for my system and I'd like to load them and test them out.
>
> The problem I have is that I've already got alsa drivers installed (as
> return by lsmod). So when I t
