On Tuesday 22 July 2008 19:54:03 Emanuel Rumpf wrote:
> 2008/7/22 David Baron <d_baron@email-addr-hidden>:
> > On Tuesday 22 July 2008 17:49:28 Emanuel Rumpf wrote:
> >> but create a link:
> >> ln -s /dev/rtc0 /dev/rtc
> >> for the new rtc-device, so that muse can find it.
> >
> > Actually, without that link, I get:
> > Trying RTC timer...
> > fatal error: open /dev/rtc failed: No such file or directory
> > Trying ALSA timer...
> > got timer = 20
> >
> > With the symlink I get.
> > Trying RTC timer...
> > got timer = 20
> >
> > So nothing is really different.
>
> Nothing different?
> In the first output it uses alsa-timer
> In the second rtc-timer
> I would call that different at least :-)
What is the practical difference. How would I get udev to place this symlink
since /dev is generated.
>
> > How do I get the realtime scheduler?
>
> If you have "PREEMPT RT" in output of
> uname -v
> you allready have it.
It does. That's how we built this kernel
>
> > The rlimits is for the audio group to have that!
>
> ?
> If you can run jackd as user in realtime-mode rlimit (we use PAM now)
> should already be set right.
It does start. So why does muse kick?
>
> > Also get
> > watchdog process 7192 _NOT_ running SCHED_FIFO
>
> where? don't know what this is.
Message follows the others here.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
Received on Tue Jul 22 20:15:04 2008
This archive was generated by hypermail 2.1.8 : Tue Jul 22 2008 - 20:15:04 EEST