this post was submitted on 11 Mar 2026
463 points (97.5% liked)

linuxmemes

30765 readers
1145 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • Don't come looking for advice, this is not the right community.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. 🇬🇧 Language/язык/Sprache
  • This is primarily an English-speaking community. 🇬🇧🇦🇺🇺🇸
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    you are viewing a single comment's thread
    view the rest of the comments
    [–] lmr0x61@lemmy.ml 11 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

    Those modules, man… they’re the biggest cause of—dare I say it?—bloat in the kernel.

    For the few people here who may not know about it: there’s a utility called modprobe-db that watches what kernel modules get loaded at runtime, and can generate a kernel build config file accordingly. There’s even an ArchWiki article about it. You need to keep it around for a while (e.g. several weeks or months) so it can get a proper sample of the modules you use; that way, your kernel can have all the modules you need (ask me how I know). If you do it right, however, you can slim down your compile time significantly.

    [–] tux7350@lemmy.world 5 points 2 weeks ago (1 children)

    I'll ask! How do you know? Lol

    All jokes aside, I think this might really help me with a side project I've been working on. Ive been trying to get full disk encryption working on a NanoPi R6S running NixOS. The issue that im having is that im not sure exactly what modules I need in the initrd. When I boot, there is no output on the display after systemd-boot shows.

    The manufacturer puts out a version of Ubuntu thats works flawlessly so I know its possible. But I'll pass on the snaps and id rather not use uboot. System is working with edk2 and nixos.

    Long story short, will this software allow me to figure out what is running in the manufacturer's kernel and port it over?

    [–] lmr0x61@lemmy.ml 2 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

    How do you know?

    Zoom not having working audio—discovered right before a job interview 💀

    But yeah, I bet it would work! Just make sure you run modprobe-db with the manufacturer’s kernel long enough to run all the software you’ll actually use, so it can record the modules you need.

    Of course, make sure you read up on it with that ArchWiki article and take a look at the source code to be sure (it’s basically a simple shell script), but from what I understand it should do what you need.

    [–] tux7350@lemmy.world 2 points 2 weeks ago (1 children)

    Well if it was for a tech job im sure you could've shown off some troubleshooting skills haha

    And the ArchWiki link is perfect. Ill read up on that and ensure I'm using it correctly. Thank you very much for the pointer kind stranger! :)

    [–] lmr0x61@lemmy.ml 1 points 2 weeks ago

    True, true haha

    Oh good! Happy I could help. :)

    [–] Samskara@sh.itjust.works 3 points 2 weeks ago (1 children)

    Does that mean you need to fiddle with modules, because you plug in a new USB-device you haven’t used before?

    [–] lmr0x61@lemmy.ml 1 points 2 weeks ago

    Yeah, if you use a kernel you built off modprobe-db’s config output, but the build config was generated before you ever used that USB device, then yeah, your kernel wouldn’t have the right modules for it (if the device required some unique kernel modules). modprobe-db will only tell you what it’s seen you use.