Configuration 'quickscan'
Moderators: MattKingUSA, khz
- funkmuscle
- Established Member
- Posts: 2807
- Joined: Mon Jun 02, 2008 2:30 pm
- Has thanked: 131 times
- Been thanked: 33 times
Re: Configuration 'quickscan'
Sorry raboof, I meant to ask if I made the changes suggested if I would be able to still use to stock kernel or the suggestions are just so fine tuning for the system to work better over all and also improve RT useage?
- raboof
- Established Member
- Posts: 1855
- Joined: Tue Apr 08, 2008 11:58 am
- Location: Deventer, NL
- Has thanked: 50 times
- Been thanked: 74 times
- Contact:
Re: Configuration 'quickscan'
Yes, there has been for some time now:studio32 wrote:Is there a GUI for this script already?
http://code.google.com/p/realtimeconfigquickscan/
I don't like it very much though. Help from someone with Perl GUI expertise is welcome
Re: Configuration 'quickscan'
i tryed to make my own kernel with 3.2.2 (last stable ) and rt patch (patch-3.2-rt10.patch)
after first start i check it
sound's good ?
at last i tryed quickscan and i correct few error in configuration but :
i check in /boot/config-3.2.2-amd64-rt10 and /usr/src/linux-headers-3.2.2-amd64-rt10/.config
it's a bug in quickscan or i made a mistake in my kernel ?
thank's in advance
edit: debian testing/ausP8H67-M/i5 2500/8GB RAM/SB Live Platinum
http://simplest-image-hosting.net/jpeg-0-test1
after first start i check it
Code: Select all
# ./cyclictest -p 80 -t5 -n
# /dev/cpu_dma_latency set to 0us
policy: fifo: loadavg: 0.05 0.12 0.10 2/311 8917
T: 0 ( 8857) P:80 I:1000 C: 5426 Min: 0 Act: 1 Avg: 1 Max: 7
T: 1 ( 8858) P:79 I:1500 C: 3617 Min: 0 Act: 1 Avg: 1 Max: 8
T: 2 ( 8859) P:78 I:2000 C: 2713 Min: 0 Act: 1 Avg: 1 Max: 5
T: 3 ( 8860) P:77 I:2500 C: 2170 Min: 0 Act: 1 Avg: 1 Max: 4
T: 4 ( 8861) P:76 I:3000 C: 1808 Min: 0 Act: 1 Avg: 1 Max: 3
at last i tryed quickscan and i correct few error in configuration but :
Code: Select all
Kernel with Real-Time Preemption... not found - not good
Kernel without real-time capabilities found
For more information, see http://wiki.linuxmusicians.com/doku.php?id=system_configuration#installing_a_real-time_kernel
Code: Select all
$ uname -a
Linux khome 3.2.2-amd64-rt10 #1 SMP PREEMPT RT Fri Feb 3 00:32:38 CET 2012 x86_64 GNU/Linux
Code: Select all
$ uname -v
#1 SMP PREEMPT RT Fri Feb 3 00:32:38 CET 2012
Code: Select all
# CONFIG_IRQ_TIME_ACCOUNTING is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_RT_BASE=y
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT__LL is not set
# CONFIG_PREEMPT_RTB is not set
CONFIG_PREEMPT_RT_FULL=y
CONFIG_PREEMPT_COUNT=y
thank's in advance
edit: debian testing/ausP8H67-M/i5 2500/8GB RAM/SB Live Platinum
http://simplest-image-hosting.net/jpeg-0-test1
-----
I do it with Debian
I do it with Debian
Re: Configuration 'quickscan'
I recently installed a realtime kernel for Fedora from CCRMA. When I run quickscan, I get the same thing: rt kernel not found. I believe the issue is with the script, not the kernel. When I asked about this on CCRMA mail list, I was told that the issue might be with the CONFIG_PREEMPT_RT_FULL. Perhaps the script doesn't contain this, or search for it. I'm new to this, so I'm still trying to understand it all, but I would get a second opinion in addition to the quickscan results.kbusta wrote:i tryed to make my own kernel with 3.2.2 (last stable ) and rt patch (patch-3.2-rt10.patch)
after first start i check itsound's good ?Code: Select all
# ./cyclictest -p 80 -t5 -n # /dev/cpu_dma_latency set to 0us policy: fifo: loadavg: 0.05 0.12 0.10 2/311 8917 T: 0 ( 8857) P:80 I:1000 C: 5426 Min: 0 Act: 1 Avg: 1 Max: 7 T: 1 ( 8858) P:79 I:1500 C: 3617 Min: 0 Act: 1 Avg: 1 Max: 8 T: 2 ( 8859) P:78 I:2000 C: 2713 Min: 0 Act: 1 Avg: 1 Max: 5 T: 3 ( 8860) P:77 I:2500 C: 2170 Min: 0 Act: 1 Avg: 1 Max: 4 T: 4 ( 8861) P:76 I:3000 C: 1808 Min: 0 Act: 1 Avg: 1 Max: 3
at last i tryed quickscan and i correct few error in configuration but :Code: Select all
Kernel with Real-Time Preemption... not found - not good Kernel without real-time capabilities found For more information, see http://wiki.linuxmusicians.com/doku.php?id=system_configuration#installing_a_real-time_kernel
Code: Select all
$ uname -a Linux khome 3.2.2-amd64-rt10 #1 SMP PREEMPT RT Fri Feb 3 00:32:38 CET 2012 x86_64 GNU/Linux
i check in /boot/config-3.2.2-amd64-rt10 and /usr/src/linux-headers-3.2.2-amd64-rt10/.configCode: Select all
$ uname -v #1 SMP PREEMPT RT Fri Feb 3 00:32:38 CET 2012
it's a bug in quickscan or i made a mistake in my kernel ?Code: Select all
# CONFIG_IRQ_TIME_ACCOUNTING is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_RT_BASE=y # CONFIG_PREEMPT_NONE is not set # CONFIG_PREEMPT_VOLUNTARY is not set # CONFIG_PREEMPT__LL is not set # CONFIG_PREEMPT_RTB is not set CONFIG_PREEMPT_RT_FULL=y CONFIG_PREEMPT_COUNT=y
thank's in advance
edit: debian testing/ausP8H67-M/i5 2500/8GB RAM/SB Live Platinum
http://simplest-image-hosting.net/jpeg-0-test1
---Scott
- raboof
- Established Member
- Posts: 1855
- Joined: Tue Apr 08, 2008 11:58 am
- Location: Deventer, NL
- Has thanked: 50 times
- Been thanked: 74 times
- Contact:
Re: Configuration 'quickscan'
You're right, this is exactly what's going on: the script looks for CONFIG_PREEMPT_RT=y, but I guess this was recently split into CONFIG_PREEMPT_RT_BASE and CONFIG_PREEMPT_RT_FULL.sconarid wrote:I believe the issue is with the script, not the kernel. When I asked about this on CCRMA mail list, I was told that the issue might be with the CONFIG_PREEMPT_RT_FULL. Perhaps the script doesn't contain this, or search for it.
What do you think the script should check for? Should we show a warning if _BASE is enabled but _FULL is not?
- autostatic
- Established Member
- Posts: 1994
- Joined: Wed Dec 09, 2009 5:26 pm
- Location: Beverwijk, The Netherlands
- Has thanked: 32 times
- Been thanked: 104 times
- Contact:
Re: Configuration 'quickscan'
Best would be to check for the kernel version first. If it's < 3.0 then check for CONFIG_PREEMPT_RT and if it's >= 3.0 then check for CONFIG_PREEMPT_RT_FULL.raboof wrote:What do you think the script should check for? Should we show a warning if _BASE is enabled but _FULL is not?
Re: Configuration 'quickscan'
thank you this ir worked nicely! i just changed the swappiness to 10 instead of 20 not sure how much difference this makes though now i get - see below:
one thing i did notice that was screwing things up bad was the gnome ambient light sensor that was creating the xruns every time it kicked in
i couldnt find anywhere in my settings to disable so i used dconf editor and disabled in the settings for gnome ALS
then had to log out that seems to have solved all my problems!
== GUI-enabled checks ==
Checking if you are root... no - good
Checking filesystem 'noatime' parameter... 4.14.18 kernel - good
(relatime is default since 2.6.30)
Checking CPU Governors... CPU 0: 'performance' CPU 1: 'performance' CPU 2: 'performance' CPU 3: 'performance' - good
Checking swappiness... 10 - good
Checking for resource-intensive background processes... none found - good
Checking checking sysctl inotify max_user_watches... >= 524288 - good
Checking access to the high precision event timer... readable - good
Checking access to the real-time clock... readable - good
Checking whether you're in the 'audio' group... yes - good
Checking for multiple 'audio' groups... no - good
Checking the ability to prioritize processes with chrt... yes - good
Checking kernel support for high resolution timers... found - good
Kernel with Real-Time Preemption... found - good
Checking if kernel system timer is high-resolution... found - good
Checking kernel support for tickless timer... found - good
== Other checks ==
Checking filesystem types... ok.
ok.
one thing i did notice that was screwing things up bad was the gnome ambient light sensor that was creating the xruns every time it kicked in
i couldnt find anywhere in my settings to disable so i used dconf editor and disabled in the settings for gnome ALS
then had to log out that seems to have solved all my problems!
== GUI-enabled checks ==
Checking if you are root... no - good
Checking filesystem 'noatime' parameter... 4.14.18 kernel - good
(relatime is default since 2.6.30)
Checking CPU Governors... CPU 0: 'performance' CPU 1: 'performance' CPU 2: 'performance' CPU 3: 'performance' - good
Checking swappiness... 10 - good
Checking for resource-intensive background processes... none found - good
Checking checking sysctl inotify max_user_watches... >= 524288 - good
Checking access to the high precision event timer... readable - good
Checking access to the real-time clock... readable - good
Checking whether you're in the 'audio' group... yes - good
Checking for multiple 'audio' groups... no - good
Checking the ability to prioritize processes with chrt... yes - good
Checking kernel support for high resolution timers... found - good
Kernel with Real-Time Preemption... found - good
Checking if kernel system timer is high-resolution... found - good
Checking kernel support for tickless timer... found - good
== Other checks ==
Checking filesystem types... ok.
ok.
- khz
- Established Member
- Posts: 1648
- Joined: Thu Apr 17, 2008 6:29 am
- Location: German
- Has thanked: 42 times
- Been thanked: 92 times
Re: Configuration 'quickscan'
Outsourced from this thread:
The Wiki entries as well as the realTimeConfigQuickScan script should be current and ~easily verifiable/traceable and should be adapted if necessary.
@realTimeConfigQuickScan script
The Wiki entries as well as the realTimeConfigQuickScan script should be current and ~easily verifiable/traceable and should be adapted if necessary.
@realTimeConfigQuickScan script
- Shm/tmps should be clearly formulated. Or, if no longer required, removed.
https://wiki.linuxaudio.org/wiki/system ... ilesystems
Code: Select all
** Warning: no tmpfs partition mounted on /tmp
Both Jack1 and Jack2 now use /dev/shm/ so mounting /tmp/ to tmpfs is not necessary anymore. - I find the confusing.
Code: Select all
increase of max_user_watches by adding 'fs.inotify.max_user_watches = 524288
http://wiki.linuxaudio.org/wiki/system_ ... sysctlconf
.There are references on the net on adjusting the fs.inotify.max_user_watches value also for enhanced performance. But it remains very unclear where these references come from and if adjusting this value actually does anything at all. The max_user_watches parameter sets the maximum number of files your system can monitor with inotify (which is part of the kernel) for changes. Setting this parameter too low results in inotify failing. Setting it too high can make inotify needlessly consume memory. Best is to not touch the default settings as setting this parameter is unrelated to performance in an audio context.
. . . FZ - Does humor belongs in Music?
. . GNU/LINUX@AUDIO ~ /Wiki $ Howto.Info && GNU/Linux Debian installing >> Linux Audio Workstation LAW
. . GNU/LINUX@AUDIO ~ /Wiki $ Howto.Info && GNU/Linux Debian installing >> Linux Audio Workstation LAW
- I don't care about the freedom of speech because I have nothing to say.
-
- Established Member
- Posts: 381
- Joined: Sun May 28, 2017 3:52 pm
Re: Configuration 'quickscan'
My take on this is that yes /dev/shm helps with running jack, but it's enabled by default everywhere nowadays. Of course having said that someone will directly prove me wrong
Reaper/KDE/Archlinux. i7-2600k/16GB + i7-4700HQ/16GB, RME Multiface/Babyface, Behringer X32, WA273-EQ, 2 x WA-412, ADL-600, Tegeler TRC, etc For REAPER on Linux information: https://wiki.cockos.com/wiki/index.php/REAPER_for_Linux
- khz
- Established Member
- Posts: 1648
- Joined: Thu Apr 17, 2008 6:29 am
- Location: German
- Has thanked: 42 times
- Been thanked: 92 times
Re: Configuration 'quickscan'
Shm/tmps please clarify in this thread.
Thank you.
Thank you.
. . . FZ - Does humor belongs in Music?
. . GNU/LINUX@AUDIO ~ /Wiki $ Howto.Info && GNU/Linux Debian installing >> Linux Audio Workstation LAW
. . GNU/LINUX@AUDIO ~ /Wiki $ Howto.Info && GNU/Linux Debian installing >> Linux Audio Workstation LAW
- I don't care about the freedom of speech because I have nothing to say.
-
- Established Member
- Posts: 381
- Joined: Sun May 28, 2017 3:52 pm
Re: Configuration 'quickscan'
I thought I did already Think this is the last I have to say on that subject
Reaper/KDE/Archlinux. i7-2600k/16GB + i7-4700HQ/16GB, RME Multiface/Babyface, Behringer X32, WA273-EQ, 2 x WA-412, ADL-600, Tegeler TRC, etc For REAPER on Linux information: https://wiki.cockos.com/wiki/index.php/REAPER_for_Linux
Re: Configuration 'quickscan'
Code: Select all
== GUI-enabled checks ==
Checking if you are root... no - good
Checking filesystem 'noatime' parameter... 5.5.0 kernel - good
(relatime is default since 2.6.30)
Checking CPU Governors... CPU 0: 'performance' CPU 1: 'performance' CPU 2: 'performance' CPU 3: 'performance' - good
Checking swappiness... 10 - good
Checking for resource-intensive background processes... none found - good
Checking checking sysctl inotify max_user_watches... >= 524288 - good
Checking access to the high precision event timer... not readable - not good
/dev/hpet found, but not readable.
make /dev/hpet readable by the 'audio' group
For more information, see http://wiki.linuxaudio.org/wiki/system_configuration#hardware_timers
Checking access to the real-time clock... not readable - not good
/dev/rtc found, but not readable.
make /dev/rtc readable by the 'audio' group
For more information, see http://wiki.linuxaudio.org/wiki/system_configuration#hardware_timers
Checking whether you're in the 'audio' group... yes - good
Checking for multiple 'audio' groups... no - good
Checking the ability to prioritize processes with chrt... yes - good
Checking kernel support for high resolution timers... found - good
Kernel with Real-Time Preemption... 'threadirqs' kernel parameter - good
Checking if kernel system timer is high-resolution... found - good
Checking kernel support for tickless timer... found - good
== Other checks ==
Checking filesystem types... ok.
** Set $SOUND_CARD_IRQ to the IRQ of your soundcard to enable more checks.
Find your sound card's IRQ by looking at '/proc/interrupts' and lspci.
Mine atm. If something doesn't look right, feedback welcome.
-
- Established Member
- Posts: 405
- Joined: Mon Mar 13, 2017 6:07 am
- Has thanked: 11 times
- Been thanked: 101 times
Re: Configuration 'quickscan'
It looks as if the ownership of the timer devices needs fixing. Here is mine:@studio32Code: Select all
Checking access to the high precision event timer... not readable - not good /dev/hpet found, but not readable. make /dev/hpet readable by the 'audio' group For more information, see http://wiki.linuxaudio.org/wiki/system_configuration#hardware_timers Checking access to the real-time clock... not readable - not good /dev/rtc found, but not readable. make /dev/rtc readable by the 'audio' group For more information, see http://wiki.linuxaudio.org/wiki/system_configuration#hardware_timers
Code: Select all
$ ls -laF /dev/hpet
crw-rw---- 1 root audio 10, 228 May 7 16:24 /dev/hpet
$ ls -laF /dev/rtc
lrwxrwxrwx 1 root root 4 May 7 16:24 /dev/rtc -> rtc0
$ ls -laF /dev/rtc0
crw-rw---- 1 root audio 249, 0 May 7 16:24 /dev/rtc0
Code: Select all
$ sudo chown root:audio /dev/hpet /dev/rtc0
$ sudo chmod g+rw /dev/hpet /dev/rtc0
Ubuntu, Mixbus32C; acoustic blues / country / jazz