Package Base Details: linux-rt-bfq

Git Clone URL: (read-only, click to copy)
Submitter: sir_lucjan
Maintainer: sir_lucjan
Last Packager: sir_lucjan
Votes: 13
Popularity: 0.180004
First Submitted: 2015-06-12 16:19
Last Updated: 2020-01-21 02:28

Pinned Comments

sir_lucjan commented on 2019-10-07 11:43

Some patches for BFQ conflict with patches for BFQ-dev.

To use linux-rt-bfq smoothly apply bfq-reverts before bfq-dev patch. Otherwise the kernel will not compile.

sir_lucjan commented on 2018-01-11 22:32

linux-rt-bfq git version:


Latest Comments

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

Turbo commented on 2018-12-26 15:24

According to Phoronix this was merge to 4.19 [] ...I think you can find the patch there =>

sir_lucjan commented on 2018-12-26 12:46

Please send me patch and I'll try.

Turbo commented on 2018-12-26 09:15

I am not sure to have the skills to make a good PKGBUILD lol. i can can try by copying one of yours ..

sir_lucjan commented on 2018-12-25 15:29


Could you try? I can't reproduce this bug.

Turbo commented on 2018-12-24 14:20

Hi Sir, I have noticed, since 4.18 series [i think] that i have to wait a long time before i get something on my screen. i guess i have this issue like few other people []. I found this task today and i am pretty sure that is why i have to wait so long [a CPU hardware random number generator issue] because when i press any key during boot, boot is quick as before. Apparently there is a patch, so can you take of it and decide to apply it [or not ..] in one of next build.

Thank you for all your work.

sir_lucjan commented on 2018-12-19 00:20


Not out-of-the-date.

The newest version is 4.19.8-rt6.

UlrichH commented on 2018-11-20 18:49


Thanks !!!

kureta commented on 2018-11-18 17:37

For people who are using EFI/UEFI boot, as opposed to BIOS: In some versions of the rt patch there is a problem with efivars/efivarfs. Apparently this is a bug in the rt patch itself. If you have warnings like unknown file system type efivarfs during boot or if your /sys/firmware/efi/efivars directory is empty try adding efi=runtime to your kernel boot options.

I have spent a whole day to solve this problem, so again, this is a note for future people who might come across the same problem.

sir_lucjan commented on 2018-11-11 17:09


I'll bump to 4.19 series when 4.19 hits [core].

blackhole commented on 2018-10-15 09:37

@kureta Yes it works!