Package Base Details: linux-rt-bfq

Git Clone URL: (read-only)
Submitter: sir_lucjan
Maintainer: sir_lucjan
Last Packager: sir_lucjan
Votes: 11
Popularity: 0.000308
First Submitted: 2015-06-12 16:19
Last Updated: 2019-06-20 14:29

Pinned Comments

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 ... Next › Last »

Turbo commented on 2019-03-25 17:03

@sir-lucjan Will it be or does it mean that there will be no more update of your package?

sir_lucjan commented on 2019-03-24 17:41

@ Turbo

bfq-mq doesn't support 5.0 line

JasonP commented on 2019-03-09 13:37

@kureta Finally I went for the easy solution. Run 'sudo modprobed-db recall' before doing the build and remove that part from the PKGBUILD. No need to have it available inside the container.

After compilation I have 134 modules in lib/modules directory.

JasonP commented on 2019-03-08 12:10

@kureta Thanks for your reply. The thing I didn't realize is that I'm compiling in a clean chroot so modprobed-db has to be available inside. My fault :)

I've changed modprobed-db to makedepends array so it will pulled by makepkg when doing building. Also the modules database has to be available inside the container. This can be done with a bind mount.

Later today I'll try to compile and see if all this works as expected.

sir_lucjan commented on 2019-03-08 12:04


Latest bfq-mq is broken - I'll downgrade patchset

kureta commented on 2019-03-08 12:01

I am getting an error during compilation:

ld: block/bfq-mq-iosched.o: in function `bfq_pid_to_str':
bfq-mq-iosched.c:(.text+0x1e60): multiple definition of `bfq_pid_to_str'; block/bfq-sq-iosched.o:bfq-sq-iosched.c:(.text+0x2170): first defined here
make: *** [Makefile:1027: vmlinux] Error 1
==> ERROR: A failure occurred in build().
Error making: linux-rt-bfq (linux-rt-bfq linux-rt-bfq-headers linux-rt-bfq-docs)

kureta commented on 2019-03-08 11:41

@JasonP I have been using modprobed-db for some time now and mine has only 162 modules listed. modprobed-db stores only the modules that were loaded at one point after you have installed and enabled it. Its purpose is to filter out modules that will never be used.

Just boot up your computer using a kernel that was not compiled with modprobed-db, plug in and use all the devices you have/normally use, connect to VPN or do what ever you do. Or you can just use your computer normally for a couple of weeks with a none modeprobed-db kernel. During this time modprobed-db will store all the modules you have used. After that you can compile this kernel using modeprobed-db and it will have all the modules you'll ever need, which I doubt will be more than 200.

JasonP commented on 2019-03-01 20:28


I've installed modprobed-db as explained in the wiki and later on, after having the database populated, I've enabled localmodcfg in PKKGBUILD.

Compilation went fine (no error messages) but I'm not quite sure that modprobed-db was able to recall modules. Database only has 114 modules loaded but kernel's lib folder has a way bigger amount:

➜ % ~ find /lib/modules/4.19.25-rt16-2-rt-bfq/kernel -name '*.ko.xz' | wc -l


I'm using aurutils to compile with a dedicated user for the build:

➜ # ~ [cd to PKGBUILD directory]

➜ # ~ sudo -u build aur build -c -D /var/cache/build/x86_64 -M /etc/makepkg.conf

Turbo commented on 2018-12-26 15:24

Thanks A lot ..

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 =>