| Re: [proaudio] realtime problems (maybe pam) |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [proaudio] realtime problems (maybe pam)
- From: Dominique Michel <dominique.michel@xxxxxxxxx>
- Date: Sat, 11 Oct 2008 12:59:10 +0200
- Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEXy8ubtkoXo7+b1+fbN cGKCeWDtamweFA8eMkmKPkPtvcWRoqyV0Pn7AAACbElEQVQ4jXXTMWvbQBQA4MOlizsdXEXp KAi09mKcLZ0EJxONDRJVkikg9AtqTm63gtHDmVJs1GsnC0JiaTMJGN2f67uzznJb+gZj9PFO 7717IqdtvCAmem4bxMLp/2BEyEBF1+U/0H8uhI6rv+BVLNrY/gH9T0L8yAxk2yMY3YuZxDCn TY/gpBByyTGktIcZOIvFjPNJmqYJDwrx3cIoBrE0zzG4FF8tfBAwM+DonKCYWjgROZ6Upjcm 5Qje58JAmlKKGfIAjzaDUuogZBY2Bjg14eDbywMIqZvwqgqFBcVFB0seYONLb00ZZlh4p0F6 FHNoUMyKAzxowJSQTyj+XloYs3MN3GeMpzyYSTMshLM00ODpWlPp4SDbqs4cViDcGAgmlK/a PsaOg7DvIQ3wzANMqB/iQW/XTkoTLO6XhSeHUoQKe+NLjyY/Ldx7CW2D4WTYhZ3V0GP64RpP Q/E66IUWMLj3+nDn4w2ejMACyXFeHZy6ETcZehc49bv1GQ/0bazNuzm97mDkhnoie9i30WYM w/YCnYT7Fx308s98n0IT//Jod1+aOzdzYXLVbftol+PC+REG3u+0AxdEtuSMB6G+DLGwMH4E vXGmJn8VCLM9LhmrOAMQYt5Wi/DFgIC52iFkUzMpDVmjAaDZRGC+JGwDqzJ/G5fUUcWZAaE7 YfvPLYtIU1Wb4A2IeS7uDMgcIFutiCr766qGfKHyuxvTIERKXVNSN27lDgCuBuojlpxIyJV6 ritS1uWWuHF2Ww7qcIKbqEFVNbmtmm3vGSCHbVXjikrY3SpVxwQWw2aIjwG+ueXTJDmHeK6a HfwGyU5ZSlGeSRQAAAAASUVORK5CYII=
Le Wed, 8 Oct 2008 17:58:00 +0000,
"kRAkEn/gORe" <kunitoki@xxxxxxxxx> a écrit :
> i'm having the same problems too, same pam settings, same .config (as
> 2.6.25.8-rt7) but with 2.6.26.5-rt9 i'm unable to get realtime, privileges
> or not. maybe doing oldconfig (with everything default) introduced some
> other changes under the hood to the config so that we have no privileges ?
> running with root is ok, but that's not the case...
>
>
> On Sun, Oct 5, 2008 at 1:18 PM, Dominique Michel <dominique.michel@xxxxxxxxxx
> > wrote:
>
> > Le Tue, 30 Sep 2008 22:55:37 +0200,
> > Frieder Bürzele <evermind@xxxxxxxxxxxxx> a écrit :
> >
> > > Hi folks,
> > >
> > > I've switched to amd64 and now hav the problem not getting realtime stuff
> > > running ATM I'm using sabayon-gentoo-linux as a base -- later I want to
> > > switch to new gentoo install, but for now I hav to get realtime stuff
> > working
> > > with this distro
> > >
> > > I think I've setup pam correctly (user into autogroup, params added to
> > > limits.conf), pam version is 1.0.2
> > >
> > >
> > > ulimit -r gives me 99
> > > as set in pam securiy stuff
> > >
> > > the kernel config gives me:
> > >
> > > zcat /proc/config.gz |grep -v '#' |grep 'CONFIG_SECURITY'
> > > CONFIG_SECURITY=y
> > > CONFIG_SECURITY_DEFAULT_MMAP_MIN_ADDR=0
> > >
> > >
> > > I'm using 2.6.27-rc6-git5: The config options
> > > CONFIG_SECURITY_CAPABILITIES
> > > is gone -- now it is compiled per default into the kernel
> > >
> > >
> >
> > I get the same problem with one of my amd64 kernels. I don't know exactly
> > what
> > triggered it out, but the only change I made was in the kernel and now with
> > 2.6.26.3-rt3, I get:
> >
What I mean is not 100% clear in my preceding message, but rt work fine with
those settings:
> > $ zcat /proc/config.gz |grep -v '#' |grep 'CONFIG_SECURITY'
> > CONFIG_SECURITY=y
> > CONFIG_SECURITY_NETWORK=y
> > CONFIG_SECURITY_NETWORK_XFRM=y
> > CONFIG_SECURITY_CAPABILITIES=y
> > CONFIG_SECURITY_DEFAULT_MMAP_MIN_ADDR=0
> > CONFIG_SECURITY_SELINUX=y
> > CONFIG_SECURITY_SELINUX_BOOTPARAM=y
> > CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=0
> > CONFIG_SECURITY_SELINUX_DISABLE=y
> > CONFIG_SECURITY_SELINUX_DEVELOP=y
> > CONFIG_SECURITY_SELINUX_AVC_STATS=y
> > CONFIG_SECURITY_SELINUX_CHECKREQPROT_VALUE=1
> >
> > This has maybe something to do with selinux. Otherwise, I can send my
> > whole .config file.
> >
> > Ciao,
> > Dominque
> >
> >
> >