Package Details: linux-rt 4.9.27_rt18-1

Git Clone URL: https://aur.archlinux.org/linux-rt.git (read-only)
Package Base: linux-rt
Description: The Linux-rt kernel and modules
Upstream URL: https://www.kernel.org/
Licenses: GPL2
Submitter: schivmeister
Maintainer: jhernberg
Last Packager: jhernberg
Votes: 142
Popularity: 1.275168
First Submitted: 2011-08-09 20:03
Last Updated: 2017-05-19 17:45

Latest Comments

ToxicAvenger commented on 2017-04-26 16:24

Thanks jhernberg!!
That worked beautifully! The system was actually trying to compile it on swap memory. But your command saved the installation!

I actually made some tweakings in threadirq, cpufreq and noatime. Got a real music production machine now! :)
(I'm using on a i5 machine)
This kernel is a must-have for producers! Thank you guys!!

jhernberg commented on 2017-04-05 17:50

@ToxicAvenger: No need for threadirq. Cpufreq might depend on your hardware, fwiw I use pstate on my i7 cpus with no problem. No atime maybe on hdd, don't think it would matter at all on sdd. About grub I don't know, but make sure that it has an entry to boot the rt kernel.

Regarding building, maybe try something like "makepkg -ci" in the PKGBUILD dir. This will build the package, clean up and finally install.

ToxicAvenger commented on 2017-04-05 14:13

Just got an error right in the end, in the "make" step.
It says I don't have space available on the device:

drivers/message/fusion/mptctl.ko: final close failed: Não há espaço disponível no dispositivo
make[1]: *** [scripts/Makefile.modpost:125: drivers/message/fusion/mptctl.ko] Error 1
make: *** [Makefile:1123: modules] Error 2

How can I compile this kernel in other location? I used pamac in order to this, but pamac won't ask you for a specific location when compiling. Actually where is "drivers/message/fusion"?? I dont think this is in my HD. And my HD has lots of space, 460GB. How to solve this? Thanks in advance.

ToxicAvenger commented on 2017-04-05 12:56

Just a noob question:

After installing the rt kernel, do I still need to:
- Add threadirq parameter to kernel?
- Set cpufreq to performance?
- Add noatime to fstab?
- Use the command "# grub-mkconfig -o /boot/grub/grub.cfg"?

I'm guessing that I should edit grub files to make sure that the rt kernel is the default kernel to boot, but I dunno about these above.

jhernberg commented on 2017-03-01 23:11

The old ticker config of 1000Hz is obsolete :) Now days hrtimers offer a higher resolution than jiffies.

I use i7 cpus, and for me the pstate driver works very well, but you can easily change the governor if you want to.

If you want to, you can verify the kernel latencies on your system with cyclictest, and some hackbench, see: https://wiki.archlinux.org/index.php/Realtime_kernel#Latency_testing_utilities

sekret commented on 2017-03-01 11:31

May I ask why the timer frequency is set to 300Hz by default rather than 1000Hz?

Also, wouldn't it be better to use the performance governor by default?

Or in other words: Is this kernel supposed to be optimized to the highest level or some sort of compromise?

Gelmo commented on 2017-02-22 18:57

@davelis90 Take a look at this page:

https://help.ubuntu.com/community/UbuntuStudioPreparation

davelis90 commented on 2017-02-22 08:00

Hello!

Could someone write the steps I need to follow (what to type in the command prompt) in order to download and install a realtime kernel in an Ubuntu system (version 16.02)? I am new in Linux and I have no idea how to do it, I only managed to download a low latency kernel but it shouldn´t be enough for my application.

Thank you very much in advance.

jhernberg commented on 2017-02-16 17:42

FYI, nvidia-dkms ought to work again

jhernberg commented on 2017-02-07 13:40

@blackhole: I've asked the -rt devs and they seem fairly convinced that the problem lies in the vbox modules doing something that works on vanilla but breaks on realtime. They said that it's hard to tell what is going on due to Arch's low loglevel. They suggested to add the following to the kernel flags, to see if there would be better console output: "debug ignore_loglevel printk.devkmsg=off"

The debug flag might be picked up by systemd though, thus the reason for "printk.devkmsg=off". They were unsure if systemd would spam the console anyways, but let's try it?

All comments