Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #58023 > unrolled thread

Bug#864716: modules and custom kernels

Started byHenrique de Moraes Holschuh <hmh@debian.org>
First post2017-06-13 17:20 +0200
Last post2017-06-13 17:20 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.debian.kernel


Contents

  Bug#864716: modules and custom kernels Henrique de Moraes Holschuh <hmh@debian.org> - 2017-06-13 17:20 +0200

#58023 — Bug#864716: modules and custom kernels

FromHenrique de Moraes Holschuh <hmh@debian.org>
Date2017-06-13 17:20 +0200
SubjectBug#864716: modules and custom kernels
Message-ID<tRVLP-19S-7@gated-at.bofh.it>
It is recommended that users building their own kernels never configure
as a module any driver that Debian doesn't configure as a module.

Anyway, essential modules for system operation should preferably be
added to /etc/modules.  They will be early-loaded by whatever gets to
them first (be it the initramfs, or systemd, or sysvinit).  Both
initramfs-tools and dracut know to always add modules present in
/etc/modules to the initramfs, and attempt to manually load them.

Adding essential modules to /etc/initramfs-tools/modules works, but it
is specific to initramfs-tools.

-- 
  Henrique Holschuh

[toc] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web