Skip to content
Update after install System configuration authored by Projekt:Root's avatar Projekt:Root
...@@ -85,96 +85,81 @@ and by WorkFlow > Studio (enable) > Daily (disable) ...@@ -85,96 +85,81 @@ and by WorkFlow > Studio (enable) > Daily (disable)
Add threadirqs to GRUB_CMDLINE_LINUX_DEFAULT: Add threadirqs to GRUB_CMDLINE_LINUX_DEFAULT:
First copy cpupower config to this files:
First copy cpupower config to this files: `sudo cp /etc/default/grub ~/.config/openbox/obconfigs/grub.default`
sudo cp /etc/default/grub ~/.config/openbox/obconfigs/grub.default
sudo cp /etc/default/grub ~/.config/openbox/obconfigs/grub.daily
sudo cp /etc/default/grub ~/.config/openbox/obconfigs/grub.studio
(cpupower.default is backup just in case)
then
sudo nano ~/.config/openbox/obconfigs/grub.studio `sudo cp /etc/default/grub ~/.config/openbox/obconfigs/grub.daily`
GRUB_CMDLINE_LINUX_DEFAULT="quiet threadirqs" `sudo cp /etc/default/grub ~/.config/openbox/obconfigs/grub.studio`
Save changes with Ctrl+o and exit Ctrl+x (cpupower.default is backup just in case)
in grub.daily store your configuration for daily use. then
`sudo nano ~/.config/openbox/obconfigs/grub.studio`
```
GRUB_CMDLINE_LINUX_DEFAULT="quiet threadirqs"
```
Save changes with Ctrl+o and exit Ctrl+x
in grub.daily store your configuration for daily use.
Usually we're making this changes in /etc/default/grub but in this case default grub config file is overwritten by grub.daily and grub.studio when we are changing WorkFlow. Usually we're making this changes in /etc/default/grub but in this case default grub config file is overwritten by grub.daily and grub.studio when we are changing WorkFlow.
## Unlocking memory: ## Unlocking memory:
`sudo nano /etc/security/limits.d/99-realtime-privileges.conf`
sudo nano /etc/security/limits.d/99-realtime-privileges.conf and paste:
```
and paste: @realtime - rtprio 99
@realtime - memlock unlimited
@realtime - rtprio 99 @audio - rtprio 99
@realtime - memlock unlimited @audio - memlock unlimited
@audio - rtprio 99 ```
@audio - memlock unlimited
## Increasing Open Files Limit: ## Increasing Open Files Limit:
`sudo nano /etc/security/limits.conf`
sudo nano /etc/security/limits.conf and paste:
```
and paste: * hard nofile 500000
* soft nofile 500000
* hard nofile 500000 root hard nofile 500000
* soft nofile 500000 root soft nofile 500000
root hard nofile 500000 ```
root soft nofile 500000
Increase “Open Files Limit”
## Increasing the highest requested RTC interrupt frequency
That part is automated via recbox-install.sh script (recbox-dev) and package installation so no need to configure it manually.
What this script doing is:
## Increasing the highest requested RTC interrupt frequency and HPET
That part is automated via recbox-install.sh script (recbox-dev) so no need to configure it manually.
echo 3072 > /sys/class/rtc/rtc0/max_user_freq What this scripts doing is:
echo 3072 > /proc/sys/dev/hpet/max-user-freq
rtc.sh
```
echo 3072 > /sys/class/rtc/rtc0/max_user_freq
```
hpet.sh
```
echo 3072 > /proc/sys/dev/hpet/max-user-freq
```
To enable, disable RTC at boot go to obmenu To enable, disable RTC at boot go to obmenu
Recbox Settings > Increas RTC Recbox Settings > Increas RTC
or change WorkFlow > Daily (disable) or change WorkFlow > Daily (disable)
> Studio (enable) > Studio (enable)
## Setting up High Precision Event Timer ## Setting up High Precision Event Timer
`sudo nano /etc/udev/rules.d/40-timer-permissions.rules`
sudo nano /etc/udev/rules.d/40-timer-permissions.rules ```
KERNEL=="rtc0", GROUP="audio"
KERNEL=="rtc0", GROUP="audio" KERNEL=="hpet", GROUP="audio"
KERNEL=="hpet", GROUP="audio" ```
> “Using hardware timers to achieve more accurate MIDI timing is questionable. Applications that use ALSA MIDI (via either the Sequencer or the Raw MIDI Interface) may be affected by using hardware timers but it might be better to rely on a high resolution software-based timer like the snd-hrtimer kernel module.
“Using hardware timers to achieve more accurate MIDI timing is questionable. Applications that use ALSA MIDI (via either the Sequencer or the Raw MIDI Interface) may be affected by using hardware timers but it might be better to rely on a high resolution software-based timer like the snd-hrtimer kernel module.
Some MIDI sequencers or DAWs that rely on ALSA MIDI might benefit from being able to use hardware timers like the real-time clock (/dev/rtc) or the High Precision Event Timer (/dev/hpet).” Some MIDI sequencers or DAWs that rely on ALSA MIDI might benefit from being able to use hardware timers like the real-time clock (/dev/rtc) or the High Precision Event Timer (/dev/hpet).”
10. Check if noatime is set 10. Check if noatime is set
... ...
......