Package Base Details: linux-rt

Git Clone URL: https://aur.archlinux.org/linux-rt.git (read-only, click to copy)
Submitter: schivmeister
Maintainer: jhernberg (dvzrv)
Last Packager: dvzrv
Votes: 172
Popularity: 0.30
First Submitted: 2011-08-09 20:03
Last Updated: 2021-01-22 00:28

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 1 2 3 4 5 6 7 ... Next › Last »

kyak commented on 2020-10-29 13:45

@dvzrv thanks a lot for maintaining this package! I'm considering switching to repository, but for now building it from source.

Previously, PKGBUILD would just fetch the kernel tarball. Now, it's using git to fetch sources from https://gitlab.archlinux.org/dvzrv/linux-rt.git.

Is it possible to ask PKGBUILD not to fetch the whole git history? I think it is not needed for makepkg. It will save huge amount of bandwidth and disk.

Maybe something like git clone --depth=1?

P.S. Maybe I need to clarify my use case a bit. I'm not keeping the build artifacts, including sources, once the build has finished (building it in tmpfs). So I will not gain speedup you might expect if you keep build directory between different releases.

dvzrv commented on 2020-10-28 21:30

@nixit: That key is in the archlinux-keyring package.

If you want to retrieve it for your own user you can do gpg --auto-key-locate wkd --search-keys dvzrv@archlinux.org.

nixit commented on 2020-10-28 19:27

when I try to update, I get the following:

:: PGP keys need importing: -> C7E7849466FE2358343588377258734B41C31549, required by: linux-rt (linux-rt->headers linux-rt) ==> Import? [Y/n] y :: Importing keys with gpg... gpg: keyserver receive failed: No name problem importing keys"

any idea what is going on?

jempe commented on 2020-10-22 11:05

@dvzrv I will do that for the new vm Thanks @jhernberg Very usefull thanks

dvzrv commented on 2020-10-21 21:47

@jempe: virtualbox is known to break quite frequently. I'd suggest using something more integrated (e.g. qemu) if you can.

jhernberg commented on 2020-10-21 21:27

Well just don't run this version! :) Wait until the major problems are fixed!

jempe commented on 2020-10-21 20:38

It's doesn't boot if virtualbox-host-dkms is instaled...

dvzrv commented on 2020-10-21 15:50

As @jhernberg has mentioned earlier, please be aware of the nvidia related limitations irt the kernel > 5.9 (see related news article).

Note: The upstream of this PKGBUILD has now changed to https://gitlab.archlinux.org/dvzrv/linux-rt, which is a mirror of the canonical upstream. Here I apply Arch Linux specific patches on top of the canonical upstream releases and tag them specifically afterwards.

This ensures a less complicated workflow (all sources soon integrated) and as the upstream pace increased recently it also means not downloading tons of Gb of sources every time (but only once). This is how core/linux and extra/linux-{hardened,zen} are handled btw.

jhernberg commented on 2020-10-21 08:05

5.9 has problems with nvidia among other things, for instance cuda and opencl are broken. My recommendation is to wait with the upgrade until there is a compatible nvidia driver, and other miscellaneous problems have been taken care or.

dvzrv commented on 2020-09-03 19:03

@Ralf_Mardorf: Sorry for the late reply. I have been very busy and then on vacation.

The CONFIG_HZ=1000 setting is indeed thought to improve performance under certain workloads (and it doesn't seem to have much of a negative effect altogether). Note, that according to this article the effects of a higher resolution timer might be diametral on systems with high I/O.

If you encounter any issues let me know!

If you have time to do benchmarks between this setting and e.g. the default CONFIG_HZ=300, please do share!