MODULES.DEP(5)

โœจ modules.dep, modules.dep.bin โ€” Module dependency information โœจ

okay bestie, gather round, because today we're talking about the little files that make your kernel modules actually know about each other ๐Ÿ’… this is MODULES.DEP(5), the manual page for modules.dep and modules.dep.bin, and yes it's short but it's important, okay?


๐Ÿฆ‹ SYNOPSIS ๐Ÿฆ‹

/lib/modules/modules.dep

/lib/modules/modules.dep.bin

that's it. those are the paths. no flags, no nothing, they just exist there living their lives ๐ŸŒธ


๐Ÿ’– DESCRIPTION ๐Ÿ’–

so modules.dep.bin is a binary file that gets generated by depmod, and it lists out the dependencies for every single module in the directories under /lib/modules/version. the kmod tools use it โ€” think modprobe and libkmod โ€” they be reading this thing constantly. it's giving main character energy tbh ๐Ÿ‘‘

its text counterpart sits in the same directory and is literally just named modules.dep. and here's the tea, bestie: the text version is maintained only so that humans can read it with their eyeballs. like, it's there for the vibes and for your comprehension. it is in no way used by any kmod tool. none of them. zero. not a single one. the binary one does all the actual work ๐Ÿ™ˆ

okay now the serious part, and I mean it fr fr:

these files are not intended for editing and they're not intended for use by any additional utilities, because their format is subject to change in the future. like, it will change on you, no cap. so if you want information about modules, use the modinfo(8) command instead โ€” that's the future proof, compatible, correct way to do it. do not be out here touching these files with your bare hands, I'm begging you ๐Ÿ˜ญ

this manual page was originally Copyright 2002, Rusty Russell, IBM Corporation. shoutout to the OGs ๐Ÿซถ


๐ŸŒˆ SEE ALSO ๐ŸŒˆ

go read those too, iykyk ๐Ÿ’œ


๐Ÿ’€ BUGS ๐Ÿ’€

found a bug? bestie, please direct any bug reports to kmod's issue tracker at

https://github.com/kmod-project/kmod/issues/

and when you do, bring receipts: the version you used, the steps to reproduce the problem, and the expected outcome. all three. not two, not one. all three. the maintainers will love you for it โœจ


๐Ÿ‘‘ AUTHORS ๐Ÿ‘‘

so many contributions have come from the linux-modules mailing list <linux-modules@vger.kernel.org> and from Github โ€” it's a whole community effort, iconic behavior honestly ๐ŸŒธ

if you have a clone of kmod.git itself, you can run the output of git-shortlog(1) and git-blame(1) to see exactly who wrote which specific parts of the project. detective work, but make it git ๐Ÿ•ต๏ธโ™€๏ธ

and Lucas De Marchi <lucas.de.marchi@gmail.com> is the current maintainer of the project. protect him at all costs ๐Ÿ’–


aaaand that's the whole page, bestie! this was kmod version 2026-10-30, from the MODULES.DEP(5) manual. slay, stay modular, and don't edit the binary file ๐Ÿ’…โœจ๐ŸŒธ

๐Ÿ“ฆ where this page comes from
  • arch rolling: kmod 34.3-1 ยท LGPL-2.1-or-later AND GPL-2.0-or-later
  • ๐Ÿ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms