▲ 62 ▼ Is there any point for a normal user to compile a custom kernel these days? (lemmy.world) submitted 5 months ago by Slashme@lemmy.world to c/linux@lemmy.world 21 comments fedilink hide all child comments Up until the early 2000s I used to compile my own kernel, carefully selecting only the options that I needed. Then I realised that I wasn't saving memory, because almost everything was a module anyway. Is there any actual benefit to using a custom kernel on consumer hardware that's supported by the stock kernels?
[–] frongt@lemmy.zip -1 points 5 months ago (1 child) Drivers are usually loaded as modules, aren't they? permalink fedilink source parent hideshow 1 child comment replies: [–] Kazumara@discuss.tchncs.de 2 points 5 months ago I'm not that certain to be honest. But the following is my best understanding: Most drivers are included directly in the kernel source. They can be compiled built-in directly to the kernel binary, or they can be compiled as loadable kernel modules. I don't know how the proportions between the two options look, but at least the essential drivers (chipsets, filesystems, etc) should be compiled in to allow the boot to progress enough that module loading works. There are some, like the Nvidia proprietary GPU driver, that are provided only in binary form as loadable kernel modules. I also understand that a lot of smartphone drivers are developed out-of-tree against older branches of the Linux kernel. Even those that are made public / open sourced, end up living outside the mainline kernel, and the devs of third party android builds have to cherry pick them into their kernel source. I think at least the last group should count as an example of a reason of the type for what OP was looking for. permalink fedilink source parent
[–] Kazumara@discuss.tchncs.de 2 points 5 months ago I'm not that certain to be honest. But the following is my best understanding: Most drivers are included directly in the kernel source. They can be compiled built-in directly to the kernel binary, or they can be compiled as loadable kernel modules. I don't know how the proportions between the two options look, but at least the essential drivers (chipsets, filesystems, etc) should be compiled in to allow the boot to progress enough that module loading works. There are some, like the Nvidia proprietary GPU driver, that are provided only in binary form as loadable kernel modules. I also understand that a lot of smartphone drivers are developed out-of-tree against older branches of the Linux kernel. Even those that are made public / open sourced, end up living outside the mainline kernel, and the devs of third party android builds have to cherry pick them into their kernel source. I think at least the last group should count as an example of a reason of the type for what OP was looking for. permalink fedilink source parent