Package Details: linux-ck 6.12.1-1

Git Clone URL: https://aur.archlinux.org/linux-ck.git (read-only, click to copy)
Package Base: linux-ck
Description: The Linux kernel and modules with ck's hrtimer patches
Upstream URL: https://wiki.archlinux.org/index.php/Linux-ck
Licenses: GPL-2.0-only
Provides: KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Replaces: virtualbox-guest-modules-arch, wireguard-arch
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 459
Popularity: 0.25
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-11-23 13:58 (UTC)

Dependencies (14)

Required by (6)

Sources (6)

Latest Comments

« First ‹ Previous 1 .. 59 60 61 62 63 64 65 66 67 68 69 .. 307 Next › Last »

artafinde commented on 2017-11-22 18:05 (UTC)

@Terence: modprobed-db is snapshotting your loaded modules and adds them into a database. Provided you run the system long enough and use it you should have all the modules you are using. localmodconfig is a tool to configure the kernel to use the modules which are currently used from the kernel dkms is using the kernel-headers to create new modules for nvidia/virtualbox etc. During linux-ck compilation and if you have set the localmodconfig parameter in PKGBUILD we load all modules which are referenced in modprobed-db prior to calling localmodconfig. Then kernel is configured according to the loaded modules and compiles etc. If you want to make sure you have a clean modprobed-db follow these steps: 1. clean up modprobed-db from modules which don't belong on kernel (nvidia, vbox etc) 2. add those to IGNORE list (optionally test by calling modprobed-db store nd check they are not added) 3. reboot and load -ARCH kernel (to make sure all the modules are available) 4. edit PKGBUILD and set localmodconfig - compile and install 5. dkms should build new modules (nvidia, vbox, exfat etc) 6. reboot to your new kernel The above process is what I follow and works fine with nvidia, vbox and exfat -dkms packages. As a fallback I have -ARCH kernel always installed.

Terence commented on 2017-11-22 17:42 (UTC) (edited on 2017-11-22 23:07 (UTC) by Terence)

@artafinde sorry I didn't make it clear enough but that's what I did :) To me it's like modprobe-db just loads all the modules it detected has been loaded at some point and then localmodconfig just lsmod, which includes dkms modules... There has to be a way to exclude them.

artafinde commented on 2017-11-22 17:38 (UTC)

Open the modprobed-db database (it's a file) and remove them from the list.

Terence commented on 2017-11-22 17:30 (UTC)

@artafinde @graysky Thanks but I knew that, that's why they are built using dkms and I took care of blacklisting all of them, making sure they are not appearing in the modprobe-db file, but problem persists.

artafinde commented on 2017-11-22 17:25 (UTC)

@Terence: The nvidia is external same as virtualbox modules. If you have dkms packages it should trigger a build after you install (provided you have headers). modprobed-db should probably exclude them with IGNORE list - see wiki.

graysky commented on 2017-11-22 17:19 (UTC)

@Terence - These are either provided by some other package or not included in the kernel anymore. See man modprobed-db.

Terence commented on 2017-11-22 17:10 (UTC)

I've never been able to find anywhere a solution to this problem with localmodconfig, modprobed-db and dkms modules: ==> If you have modprobed-db installed, running it in recall mode now Modprobed-db v2.37 164 modules currently loaded per /proc/modules 168 modules are in /home/terence/.config/modprobed.db Attempting to modprobe the contents of /home/terence/.config/modprobed.db 164 modules are now loaded per /proc/modules ==> Running Steven Rostedt's make localmodconfig now using config: '.config' vboxpci config not found!! nvidia config not found!! nvidia_uvm config not found!! vboxnetflt config not found!! vboxnetadp config not found!! vboxdrv config not found!! 8812au config not found!! nvidia_drm config not found!! nvidia_modeset config not found!! Any insight?

sir_lucjan commented on 2017-11-21 21:04 (UTC)

@johnnybegood I also recommended blk-mq patches.

johnnybegood commented on 2017-11-21 20:55 (UTC)

Works perfect for me as well. However, I still miss the old single queue bfq, the now called "bfq-sq" that was never merged into the official kernel, so I compiled ck with sirlucjan latest patch for 4.14 (https://raw.githubusercontent.com/sirlucjan/kernel-patches/master/4.14/4.14-bfq-sq-mq-git-20171114.patch) I find the combination of -ck and bfq-sq unbeatable. Maybe it's just me but it could be an addition to this excellent kernel. Graysky, thanks for your work and CK's!

zebulon commented on 2017-11-21 12:07 (UTC)

Works for me. Need to use scsi_mod.use_blk_mq=1 init option for blq as expected. @silvik: I do not need to use elevator=bfq, scsi_mod.use_blk_mq=1 is sufficient. I need however to set udev rules to set bfq.

« First ‹ Previous 1 .. 59 60 61 62 63 64 65 66 67 68 69 .. 307 Next › Last »