8 Jan
2012
8 Jan
'12
12:17 a.m.
Hi,
cannot set tick on /dev/rtc permission denied
How important is it to solve this? It seems /dev/rtc is not in the
Debian kernel, are there (lowlatency / RT) kernels for Debian with this
feature included?
Regards,
\r
8 Jan
8 Jan
12:40 a.m.
On 1/7/12, rosea.grammostola <rosea.grammostola(a)gmail.com> wrote:
Hi,
cannot set tick on /dev/rtc permission denied
How important is it to solve this? It seems /dev/rtc is not in the
Debian kernel, are there (lowlatency / RT) kernels for Debian with this
feature included?
Seems to be there on my system.
3.0.0-1-686-pae #1 SMP Sat Aug 27 16:41:03 UTC 2011 i686 GNU/Linux
(Debian SID).
ls -l /dev/rtc
lrwxrwxrwx 1 root root 4 Jan 7 09:20 /dev/rtc -> rtc0
James
7:14 p.m.
On 01/08/2012 12:40 AM, James Stone wrote:
On 1/7/12,
rosea.grammostola<rosea.grammostola(a)gmail.com> wrote:
same here, but the audio group has also the rights for /dev/rtc
But still I get the message when launching Oostudio (openoctave / oom).
Regards,
\r
Hi,
cannot set tick on /dev/rtc permission denied
How important is it to solve this? It seems /dev/rtc is not in the
Debian kernel, are there (lowlatency / RT) kernels for Debian with this
feature included?
Seems to be there on my system.
3.0.0-1-686-pae #1 SMP Sat Aug 27 16:41:03 UTC 2011 i686 GNU/Linux
(Debian SID).
ls -l /dev/rtc
lrwxrwxrwx 1 root root 4 Jan 7 09:20 /dev/rtc -> rtc0
James 
7:50 p.m.
On Sun, 08 Jan 2012 19:14:39 +0100, rosea.grammostola wrote
On 01/08/2012 12:40 AM, James Stone wrote:
> On 1/7/12, rosea.grammostola<rosea.grammostola(a)gmail.com> wrote:
>> Hi,
>>
>> cannot set tick on /dev/rtc permission denied
What a unhelpful error message! can't they at least include information
on the value that was supposed to be used?
same here, but the audio group has also the rights for /dev/rtc
We need the permissions of the actual device file (/dev/rtc0) , _not_
the link since the link permission only describes who is allowed to
follow the link.
But still I get the message when launching Oostudio
(openoctave /
oom).
You might have your settings for the maximum value set too low. What does
the following show:
$ cat /sys/class/rtc/rtc0/max_user_freq
On older kernels that should be:
$ cat /proc/sys/dev/rtc/max-user-freq
Also relevant:
$ cat /proc/sys/dev/hpet/max-user-freq
You can set these values like this:
$ sudo echo 2048 > /sys/class/rtc/rtc0/max_user_freq
$ sudo echo 2048 > /proc/sys/dev/hpet/max-user-freq
or set them in /etc/sysctl.conf
HTH Ralf Mattes
8:09 p.m.
This is the full message:
RtcTimer::setTimerFreq(): cannot set tick on /dev/rtc: Permission denied
precise timer not available
AlsaTimer::initTimer(): best available ALSA timer: system timer
On 01/08/2012 07:50 PM, R. Mattes wrote:
cat /proc/sys/dev/hpet/max-user-freq
cat /sys/class/rtc/rtc0/max_user_freq
64
2048 is a good value?
Thanks
Regards,
\r
8:11 p.m.
On 01/08/2012 08:09 PM, rosea.grammostola wrote:
This is the full message:
RtcTimer::setTimerFreq(): cannot set tick on /dev/rtc: Permission denied
precise timer not available
AlsaTimer::initTimer(): best available ALSA timer: system timer
On 01/08/2012 07:50 PM, R. Mattes wrote:
$ cat /proc/sys/dev/hpet/max-user-freq
64
cat /proc/sys/dev/hpet/max-user-freq
cat /sys/class/rtc/rtc0/max_user_freq
64
2048 is a good value?
Thanks
Regards,
\r
9 Jan
9 Jan
9:37 p.m.
Did you get any further with this? I had a look at the program, but
it's a bit of a hefty compile what with all the dependencies. Looks
pretty nice though!
I seem to remember rosegarden used to complain about rtc access (at
least it did in the past), but it never seemed to have a noticable
impact on performance (at least to my ears).
Thanks Ralf for the info on max-user-freq. I didn't realise this had
anything to do with rtc, but I did have to change it in the past to
get round some bad midi timing inconsistencies in seq24. Didn't know
the new way to set it.
James
On 1/8/12, rosea.grammostola <rosea.grammostola(a)gmail.com> wrote:
On 01/08/2012 08:09 PM, rosea.grammostola wrote:
This is the full message:
RtcTimer::setTimerFreq(): cannot set tick on /dev/rtc: Permission denied
precise timer not available
AlsaTimer::initTimer(): best available ALSA timer: system timer
On 01/08/2012 07:50 PM, R. Mattes wrote:
$ cat /proc/sys/dev/hpet/max-user-freq
64
cat /proc/sys/dev/hpet/max-user-freq
cat /sys/class/rtc/rtc0/max_user_freq
64
2048 is a good value?
Thanks
Regards,
\r 
10:10 p.m.
On 01/09/2012 09:37 PM, James Stone wrote:
Did you get any further with this? I had a look at the
program, but
it's a bit of a hefty compile what with all the dependencies. Looks
pretty nice though!
I seem to remember rosegarden used to complain about rtc access (at
least it did in the past), but it never seemed to have a noticable
impact on performance (at least to my ears).
Thanks Ralf for the info on max-user-freq. I didn't realise this had
anything to do with rtc, but I did have to change it in the past to
get round some bad midi timing inconsistencies in seq24. Didn't know
the new way to set it.
James
Good to know. I always wondered what the audio performance improvements
on http://rosegardenmusic.com/wiki/low-latency_kernels act were for.
Best,
Jeremy
10:30 p.m.
On 01/09/2012 09:37 PM, James Stone wrote:
Did you get any further with this? I had a look at the
program, but
it's a bit of a hefty compile what with all the dependencies. Looks
pretty nice though!
I seem to remember rosegarden used to complain about rtc access (at
least it did in the past), but it never seemed to have a noticable
impact on performance (at least to my ears).
Thanks Ralf for the info on max-user-freq. I didn't realise this had
anything to do with rtc, but I did have to change it in the past to
get round some bad midi timing inconsistencies in seq24. Didn't know
the new way to set it.
James
Yes, followed the instructions by Ralf, seems to be ok now. Thanks!
Didn't realize this was a configuration step which has to be done still
these days.
Regards,
\r
On 1/8/12,
rosea.grammostola<rosea.grammostola(a)gmail.com> wrote:
> On 01/08/2012 08:09 PM, rosea.grammostola wrote:
>> This is the full message:
>> RtcTimer::setTimerFreq(): cannot set tick on /dev/rtc: Permission denied
>> precise timer not available
>>
>> AlsaTimer::initTimer(): best available ALSA timer: system timer
>>
>>
>> On 01/08/2012 07:50 PM, R. Mattes wrote:
>>> cat /proc/sys/dev/hpet/max-user-freq
>>
>> cat /sys/class/rtc/rtc0/max_user_freq
>> 64
>>
>> 2048 is a good value?
>>
>> Thanks
>>
>> Regards,
>> \r
>
> $ cat /proc/sys/dev/hpet/max-user-freq
> 64
>
>
11:45 p.m.
Hi Rosea,
2012/1/9 rosea.grammostola <rosea.grammostola(a)gmail.com>om>:
On 01/09/2012 09:37 PM, James Stone wrote:
<....>
Did you get any further with this? I had a look at the program, but
it's a bit of a hefty compile what with all the dependencies. Looks
pretty nice though!
I seem to remember rosegarden used to complain about rtc access (at
least it did in the past), but it never seemed to have a noticable
impact on performance (at least to my ears).
Thanks Ralf for the info on max-user-freq. I didn't realise this had
anything to do with rtc, but I did have to change it in the past to
get round some bad midi timing inconsistencies in seq24. Didn't know
the new way to set it.
James
Yes, followed the instructions by Ralf, seems to be ok now. Thanks!
Didn't realize this was a configuration step which has to be done still
these days. >>> RtcTimer::setTimerFreq(): cannot set tick
on /dev/rtc: Permission denied
Just some clarification as to the nature, Oom is based on MusE so the
same error can occur for us (with MusE that is).
I can see that the error message can be improved after reading Ralfs
reply, usually the reason is due to device file permissions, didn't
know it could actually be because of a value limitation. I'll give it
a look for improvements.
Also, having rtc timing is as someone noted not a strict requirement,
as it will fall back on the system timer, though on many systems this
is set too low.
Regards,
Robert
10 Jan
10 Jan
1:03 a.m.
Robert Jonsson wrote:
Hi Rosea,
2012/1/9 rosea.grammostola <rosea.grammostola(a)gmail.com>om>:
https://github.com/ccherrett/oom/wiki/Troubleshooting
We have it listed in our trouble shooting section of our docs.
Look down at the bottom of that page.
Thanks!
--
Christopher Cherrett
ccherrett(a)openoctave.org
http://www.openoctave.org
On 01/09/2012 09:37 PM, James Stone wrote:
<....>
Did you get any further with this? I had a look
at the program, but
it's a bit of a hefty compile what with all the dependencies. Looks
pretty nice though!
I seem to remember rosegarden used to complain about rtc access (at
least it did in the past), but it never seemed to have a noticable
impact on performance (at least to my ears).
Thanks Ralf for the info on max-user-freq. I didn't realise this had
anything to do with rtc, but I did have to change it in the past to
get round some bad midi timing inconsistencies in seq24. Didn't know
the new way to set it.
James
Yes, followed the instructions by Ralf, seems to be ok now. Thanks!
Didn't realize this was a configuration step which has to be done still
these days. >>> RtcTimer::setTimerFreq(): cannot set
tick on /dev/rtc: Permission denied
Just some clarification as to the nature, Oom
is based on MusE so the
same error can occur for us (with MusE that is).
I can see that the error message can be improved after reading Ralfs
reply, usually the reason is due to device file permissions, didn't
know it could actually be because of a value limitation. I'll give it
a look for improvements.
Also, having rtc timing is as someone noted not a strict requirement,
as it will fall back on the system timer, though on many systems this
is set too low.
Regards,
Robert
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
9:54 a.m.
On 01/08/12 19:50, R. Mattes wrote:
On Sun, 08 Jan 2012 19:14:39 +0100, rosea.grammostola
wrote
Hello,
How does this all relate to the snd-hrtimer ALSA module? Or is this a
software timer while hpet and rtc0 are hardware timers? This is a bit
uncharted territory for me and I like to get things straight for the
LinuxMusicians system configuration page
(http://wiki.linuxmusicians.com/doku.php?id=system_configuration), and
also for myself as I use MIDI a lot (Qtractor, seq24, Hydrogen etc.).
Best,
Jeremy
On 01/08/2012 12:40 AM, James Stone wrote:
> On 1/7/12, rosea.grammostola<rosea.grammostola(a)gmail.com> wrote:
>> Hi,
>>
>> cannot set tick on /dev/rtc permission denied
What a unhelpful error message! can't they at least include information
on the value that was supposed to be used?
same here, but the audio group has also the rights for /dev/rtc
We need the permissions of the actual device file (/dev/rtc0) , _not_
the link since the link permission only describes who is allowed to
follow the link.
But still I get the message when launching
Oostudio (openoctave /
oom).
You might have your settings for the maximum value set too low. What does
the following show:
$ cat /sys/class/rtc/rtc0/max_user_freq
On older kernels that should be:
$ cat /proc/sys/dev/rtc/max-user-freq
Also relevant:
$ cat /proc/sys/dev/hpet/max-user-freq
You can set these values like this:
$ sudo echo 2048> /sys/class/rtc/rtc0/max_user_freq
$ sudo echo 2048> /proc/sys/dev/hpet/max-user-freq
or set them in /etc/sysctl.conf
HTH Ralf Mattes
9 Mar
9 Mar
12:19 p.m.
On 01/08/2012 07:50 PM, R. Mattes wrote:
On Sun, 08 Jan 2012 19:14:39 +0100, rosea.grammostola
wrote
This seems to be gone after reboot
On 01/08/2012 12:40 AM, James Stone wrote:
> On 1/7/12, rosea.grammostola<rosea.grammostola(a)gmail.com> wrote:
>> Hi,
>>
>> cannot set tick on /dev/rtc permission denied
What a unhelpful error message! can't they at least include information
on the value that was supposed to be used?
same here, but the audio group has also the rights for /dev/rtc
We need the permissions of the actual device file (/dev/rtc0) , _not_
the link since the link permission only describes who is allowed to
follow the link.
But still I get the message when launching
Oostudio (openoctave /
oom).
You might have your settings for the maximum value set too low. What does
the following show:
$ cat /sys/class/rtc/rtc0/max_user_freq
On older kernels that should be:
$ cat /proc/sys/dev/rtc/max-user-freq
Also relevant:
$ cat /proc/sys/dev/hpet/max-user-freq
You can set these values like this:
$ sudo echo 2048> /sys/class/rtc/rtc0/max_user_freq
$ sudo echo 2048> /proc/sys/dev/hpet/max-user-freq
or set them in /etc/sysctl.conf
is this permanent? How do I do that exactly?
\r
HTH Ralf Mattes
5:40 p.m.
On 03/09/2012 12:19 PM, rosea.grammostola wrote:
is this permanent? How do I do that exactly?
\r
Yes. You can add lines in /etc/sysctl.conf and load them with sudo sysctl -p
But only kernel parameters that are set under /proc/sys/
And instead of:
$ sudo echo 2048> /proc/sys/dev/hpet/max-user-freq
You can also do:
$ sudo sysctl -w dev.hpet.max-user-freq=2048
This will write an entry in /etc/sysctl.conf
But again this only applies for parameters under /proc/sys/, I have no
idea if there is an equivalent tool to sysctl for parameters under
/sys/class so you'll probably have to script it.
Best,
Jeremy
10 Mar
10 Mar
2:28 p.m.
On 03/09/2012 05:40 PM, Jeremy Jongepier wrote:
On 03/09/2012 12:19 PM, rosea.grammostola wrote:
I think you can put it in
$ cat /etc/rc.local
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
echo 2048 > /sys/class/rtc/rtc0/max_user_freq
exit 0
is this permanent? How do I do that exactly?
\r
Yes. You can add lines in /etc/sysctl.conf and load them with sudo
sysctl -p
But only kernel parameters that are set under /proc/sys/
And instead of:
$ sudo echo 2048> /proc/sys/dev/hpet/max-user-freq
You can also do:
$ sudo sysctl -w dev.hpet.max-user-freq=2048
This will write an entry in /etc/sysctl.conf
But again this only applies for parameters under /proc/sys/, I have no
idea if there is an equivalent tool to sysctl for parameters under
/sys/class so you'll probably have to script it.
9:07 p.m.
On 03/10/2012 01:25 PM, rosea.grammostola wrote:
I think you can put it in
$ cat /etc/rc.local
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
echo 2048 > /sys/class/rtc/rtc0/max_user_freq
exit 0
True. Or create a dedicated init script to set these kind of parameters.
Best,
Jeremy
4428
days inactive
4491
days old
linux-audio-user@lists.linuxaudio.org
15 comments
6 participants
participants (6)
-
Christopher Cherrett -
James Stone -
Jeremy Jongepier -
R. Mattes -
Robert Jonsson -
rosea.grammostola