Results 1 to 6 of 6

Thread: What's the best way to force a module to load?

  1. #1
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,893
    Blog Entries
    3

    Default What's the best way to force a module to load?

    The title line says it all.

    I am experimenting with ecryptfs. And it seems to not work properly unless I first use "modprobe ecryptfs" as root.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  2. #2

    Default Re: What's the best way to force a module to load?

    Quote Originally Posted by nrickert View Post
    The title line says it all.

    I am experimenting with ecryptfs. And it seems to not work properly unless I first use "modprobe ecryptfs" as root.
    Would it be a problem to add it initrd? Just a thought.

  3. #3
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,893
    Blog Entries
    3

    Default Re: What's the best way to force a module to load?

    Quote Originally Posted by please_try_again View Post
    Would it be a problem to add it initrd? Just a thought.
    I guess that could be done. It doesn't need to be that early. Adding to the "after.local" initscript would be plenty early enough. I think that still runs with systemd.

    I'm just wondering if there is an official place to list modules that should always be loaded.

    Let me give a little more detail. I used "ecryptfs-setup-private" to set things up. That just gave a message that modprobe is needed. Well, no big deal, since you only run the setup once.

    Now, after boot and login, I run ecryptfs-mount-private to make the private files available. And that sort-of works. If I first run the modprobe it works well. But without the prior modprobe, it still mounts - presumably it is loading the module itself. But the mounted Private file system has only encrypted filenames, which makes it pretty hard to use. I'll probably report this as a bug after a bit more experimenting. Forcing the module to load before running ecryptfs-mount-private works just fine.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  4. #4

    Default Re: What's the best way to force a module to load?

    Quote Originally Posted by nrickert View Post
    I'm just wondering if there is an official place to list modules that should always be loaded.
    It should be MODULES_LOADED_ON_BOOT in /etc/sysconfig/kernel. You can add modules to this list from YaST sysconfig Editor too... and/or the files in /etc/modprob.d. Did you try to load it in /etc/modprobe.d/99-local.conf?

  5. #5
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,893
    Blog Entries
    3

    Default Re: What's the best way to force a module to load?

    Thanks. That's the kind of information I was looking for.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  6. #6
    Join Date
    Jun 2008
    Location
    UTC+10
    Posts
    9,686
    Blog Entries
    4

    Default Re: What's the best way to force a module to load?

    I think it's fixed in the recent systemd update, but in case not, you can list the modules, one per line, in /etc/modules-load.d/something.conf

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •