Package Base Details: linux-rt

Git Clone URL: (read-only, click to copy)
Submitter: schivmeister
Maintainer: jhernberg (dvzrv, sangy)
Last Packager: dvzrv
Votes: 177
Popularity: 0.042755
First Submitted: 2011-08-09 20:03
Last Updated: 2021-12-18 19:40

Pinned Comments

dvzrv commented on 2021-01-12 21:52

The repository for linux-rt and linux-rt-lts has moved to a new location.

If you use the custom repository, please update your pacman.conf accordingly, as the other one is going away by the end of the month (January 2021)!

Latest Comments

« First ‹ Previous ... 3 4 5 6 7 8 9 10 11 12 13 ... Next › Last »

aquilarubra commented on 2019-12-29 20:58

Thanks for answers. I didn't have the time to try again, but I will give it a shot again. It was a pain to go back to AMD, after so many years. I experienced issues of any kind, but now that I solved each of them one by one, the result is impressive - compared to Intel, where I wasn't able to solve everything. Being my machine new, I don't have the older kernels. I'm not sure how to get them. But it's just fine to experiment with the 5.4.3 kernel. You mentioned 5.4.5... any new update?

Ralf_Mardorf commented on 2019-12-26 14:00

Hi aquilarubra, I just want to let you know that virtualbox seems not to work on an Intel machine, when booted into "my" 5.4.5_rt3, but it works when booted into 5.4.6.arch3-1. Sorry, there's no time for further investigations. Regards, Ralf

Ralf_Mardorf commented on 2019-12-26 08:19

Hi aquilarubra, first of all, I migrated from AMD CPUs with ATI and NVIDIA graphics to an Intel CPU with an Intel GPU, to get rid of issues with linux-rt, as well as audio and MIDI issues in general. I already experienced all kinds of trouble with AMD CPUs, ATI and NVIDIA graphics years before Ryzen 3000 was released. I can't comment on 5.4.3-rt1, but I build 5.4.5-rt3 and it works without issues, at least dkms did build modules for the AUR package virtualbox-bin 6.1.0-1, it boots and runs with all disks detected and without crashing. The kernel was build with some differences to the AUR package. I did not apply any other patch, but the rt patch only. I used the same config, but disabled AppArmor and Auditing support with menuconfig and while this doesn't affect functionality, for the sake of completeness PKGBUILD does use pkgver="${_pkgver}_rt${_rtpatchver}" instead of pkgver="${_pkgver}.${_rtpatchver}" and echo "${pkgbase#linux-rt}" > localversion.20-pkgname instead of echo "${pkgbase#linux}" > localversion.20-pkgname . You need to take a look at the log files. Does a 5.2 kernel work for you or at least a 4.19 kernel? I didn't experience issues with any of the listed kernels.

$ pacman -Q linux{,-rt{,-pussytoes,-cornflower,-securityink}}|cut -d\  -f2
$ echo $(uname -srvm;zgrep CONFIG_AUDIT\  /proc/config.gz)
Linux 5.4.5-rt3-0 #1 SMP PREEMPT_RT @1577303715 x86_64 # CONFIG_AUDIT is not set

Consider to write to linux-rt-users. Regards, Ralf

PS: FWIW did you try to load and unload the vbox modules on demand, instead of doing this at startup?

modprobe -av $(ls /lib/modules/$(uname -r)/kernel/misc/ | cut -d. -f1)
modprobe -rv $(ls -r /lib/modules/$(uname -r)/kernel/misc/ | cut -d. -f1)

It requires some modification, if there should be other modules, than just the vbox* modules in misc/, too.

aquilarubra commented on 2019-12-26 06:13

Any idea why it doesn't work (crashes at boot, doesn't recognize disks, etc.) with virtualbox-host-dkms?

aquilarubra commented on 2019-12-21 11:03

Now it's working with nvidia-dkms

aquilarubra commented on 2019-12-20 07:23

I tested the kernel again, once removing both of my 2 dkms modules (nvidia and virtualbox), once with only the nvidia dkms, and once with only the virtualbox dkms. The result is that, every time there is a dkms module, the kernel will hang at boot with a stack trace. So, there are definitely issues with dkms modules in general.

aquilarubra commented on 2019-12-19 20:58

I could narrow down the issue, in my case. If I remove nvidia-dkms, the kernel works, but nouveau is buggy and I get a garbled screen, which tends to end up in a loop. If I have nvidia-dkms, I get the stack trace. There are lines saying that preemption was disabled. So, they are apparently incompatible.

aquilarubra commented on 2019-12-17 21:46

I cannot boot this kernel with the Ryzen 3000 either. I added the unofficial repository and no luck. Compiled the kernel myself, it could load just once (I really cannot figure out how it worked once), then no more. The first message I always see is: /sys/firmware/efi/efivars: unknown filesystem type 'efivars' Then, I get a sort of stack trace. Every time it hangs at a different place, but it never completes the boot process. I call the rt kernel the same way of the default arch kernel, prepending amd-ucode: initrd /boot/amd-ucode.img /boot/initramfs-linux-rt.img I wonder if it must be compiled with some other options for AMD.

dvzrv commented on 2019-11-01 13:54

Please note, that there have been substantial changes to how mkinitcpio (>=27) works with vmlinuz images to create initramfs images. This change is reflected in the PKGBUILD for in alignment with all vanilla kernels in the main repositories.

dvzrv commented on 2019-10-08 07:49

@daniel712: Please be more specific than "cannot boot".