Re: Low timer resolution (but it shouldn't be!)

   The "system timer" setting should indeed do the check and it does 
not.  I will add the check to that part of the code to avoid misleading 
users.

   It is odd that Debian would not offer a 1000Hz kernel.  Ubuntu's 
default kernel is now real-time and 1000Hz.  Debian must offer 
something.  Check the kernel packages.

   Worst-case you'll have to build your own.  Fortunately that's easier 
than it sounds.  My (slightly outdated) instructions are here if you 
need them:

http://www.tedfelix.com/linux/kernel-build.html

Ted.

On 2/7/25 9:29 AM, Jeronimo Pellegrini wrote:
> On 2025-02-05 14:52, Ted Felix wrote:
>> On 1/31/25 6:18 AM, Jeronimo Pellegrini wrote:
>>> So... It was already set to "auto". Then, I changed to "system 
>>> timer", restarted Rosegarden, and now it shows the timer as 
>>> "OK" (Thanks for pointing me to the right place in the config). So 
>>> perhaps the "auto" setting is not working as expected?
>>
>>   Actually, it looks like the "system timer" setting does not perform 
>> the resolution checks.  Can you try the following on your system:
>>
>>   $ grep ^CONFIG_HZ /boot/config-`uname -r`
> 
> Oh, I see. You mean this:
> 
> CONFIG_HZ_250=y
> CONFIG_HZ=250
> 
> It seems then that Debian ships a kernel patched for real-time, that 
> operates at 250Hz (?)
> 
> But shouldn't the "system timer" setting actually do check if the timer 
> is good?
> 
> J.



_______________________________________________
Rosegarden-user mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user