[gentoo-user] openrc : autoload kernel modules

[gentoo-user] openrc : autoload kernel modules

[Helmut Jarausch]

Hi,

could anybody please explain me how to setup autoloading of some kernel  
modules of mine.

I'm using openrc.

My modules reside in /lib/modules/`uname -r`/extra/enhanceio/ .

I have added the following lines to  /etc/conf.d/modules

modules="enhanceio"
modules="enhanceio_lru"
modules="enhanceio_fifo"
modules="enhanceio_rand"


but these modules don't get loaded at boot time.

The modules are OK since using 'depmod' works fine.

What am I missing?

Many thanks for a hint,
Helmut

[gentoo-user] Re: openrc : autoload kernel modules

[Hartmut Figge]

Helmut Jarausch:

>I have added the following lines to  /etc/conf.d/modules
>
>modules="enhanceio"
>modules="enhanceio_lru"
>modules="enhanceio_fifo"
>modules="enhanceio_rand"
>
>
>but these modules don't get loaded at boot time.

Looking in my /etc/conf.d/modules there are

# for a list of modules and their options.
modprobe vboxdrv
modprobe vboxnetflt
modprobe vboxnetadp
modprobe vboxpci

Hm? ;)

Hartmut

Re: [gentoo-user] openrc : autoload kernel modules

[Michael Orlitzky]

On 12/14/2017 12:43 PM, Helmut Jarausch wrote:
> 
> I have added the following lines to  /etc/conf.d/modules
> 
> modules="enhanceio"
> modules="enhanceio_lru"
> modules="enhanceio_fifo"
> modules="enhanceio_rand"
> 

"modules" is a variable name, and it's being overwritten on each line.
The /etc/init.d/modules script does something like

  for module in $modules; do
    load $module
  done

but in your case, "modules" will contain only the last thing you set it
to, namely modules="enhanceio_rand".

Re: [gentoo-user] openrc : autoload kernel modules

[Mick]

[-- Attachment #1: Type: text/plain, Size: 720 bytes --]

On Thursday, 14 December 2017 18:43:55 GMT Michael Orlitzky wrote:
> On 12/14/2017 12:43 PM, Helmut Jarausch wrote:
> > I have added the following lines to  /etc/conf.d/modules
> > 
> > modules="enhanceio"
> > modules="enhanceio_lru"
> > modules="enhanceio_fifo"
> > modules="enhanceio_rand"
> 
> "modules" is a variable name, and it's being overwritten on each line.
> The /etc/init.d/modules script does something like
> 
>   for module in $modules; do
>     load $module
>   done
> 
> but in your case, "modules" will contain only the last thing you set it
> to, namely modules="enhanceio_rand".

Change your entries to:

#Modules for enhanceio
enhanceio
enhanceio_lru
enhanceio_fifo
enhanceio_rand

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] Re: openrc : autoload kernel modules

[Alexander Kapshuk]

On Thu, Dec 14, 2017 at 8:11 PM, Hartmut Figge <h.figge@gmx.de> wrote:
> Helmut Jarausch:
>
>>I have added the following lines to  /etc/conf.d/modules
>>
>>modules="enhanceio"
>>modules="enhanceio_lru"
>>modules="enhanceio_fifo"
>>modules="enhanceio_rand"
>>
>>
>>but these modules don't get loaded at boot time.
>
> Looking in my /etc/conf.d/modules there are
>
> # for a list of modules and their options.
> modprobe vboxdrv
> modprobe vboxnetflt
> modprobe vboxnetadp
> modprobe vboxpci
>
> Hm? ;)
>
> Hartmut
>
>

You want to verify the way you built and installed your external
modules against this doc,
https://www.kernel.org/doc/Documentation/kbuild/modules.txt.
See if you overlooked anything.

Re: [gentoo-user] openrc : autoload kernel modules

[Helmut Jarausch]

On 12/14/2017 07:43:55 PM, Michael Orlitzky wrote:
> On 12/14/2017 12:43 PM, Helmut Jarausch wrote:
> >
> > I have added the following lines to  /etc/conf.d/modules
> >
> > modules="enhanceio"
> > modules="enhanceio_lru"
> > modules="enhanceio_fifo"
> > modules="enhanceio_rand"
> >
> 
> "modules" is a variable name, and it's being overwritten on each line.
> The /etc/init.d/modules script does something like
> 
>   for module in $modules; do
>     load $module
>   done
> 
> but in your case, "modules" will contain only the last thing you set  
> it
> to, namely modules="enhanceio_rand".
> 


Many thanks, Michael and Mick.

It turned out that I had to write

modules="vboxdrv vboxnetflt vboxnetadp enhanceio enhanceio_lru  
enhanceio_fifo enhanceio_rand"

i.e. all modules in one string assignment to the variable 'modules'

Helmut

Re: [gentoo-user] openrc : autoload kernel modules

[David Haller]

Hello,

On Thu, 14 Dec 2017, Michael Orlitzky wrote:
>On 12/14/2017 12:43 PM, Helmut Jarausch wrote:
>> 
>> I have added the following lines to  /etc/conf.d/modules
>> 
>> modules="enhanceio"
>> modules="enhanceio_lru"
>> modules="enhanceio_fifo"
>> modules="enhanceio_rand"
>> 
>
>"modules" is a variable name, and it's being overwritten on each line.
>The /etc/init.d/modules script does something like
>
>  for module in $modules; do
>    load $module
>  done
>
>but in your case, "modules" will contain only the last thing you set it
>to, namely modules="enhanceio_rand".

Does openrc-run (or the old way) support adding to strings? I.e.:

====
modules+=" foo"
modules+=" bar"
====

or must one use

====
modules="${modules} foo"
modules="${modules} bar"
====

or must it even be one single string? Does that support embedded
linebreaks?

I think this should be documented better in the file.

-dnh

PS: I've had the opposite problem: modules automatically got loaded
    and I blacklisted them in /etc/modprobe.d/*.conf ;)

-- 
I find all proselytisation to be misguided at least. The way I see it, it's
not the Enlightened or the Chosen trying to save me or anyone, but just some
meme trying to survive in the great war for brain real estate.
                                                          -- Maarten Wiltink

Re: [gentoo-user] openrc : autoload kernel modules

[Michael Orlitzky]

On 12/14/2017 03:30 PM, David Haller wrote:
> 
> Does openrc-run (or the old way) support adding to strings? I.e.:
> 
> ====
> modules+=" foo"
> modules+=" bar"
> ====
> 
> or must one use
> 
> ====
> modules="${modules} foo"
> modules="${modules} bar"
> ====
> 
> or must it even be one single string? Does that support embedded
> linebreaks?

It's all shell script that gets passed through /bin/sh, so you can get
away with anything that will work in your /bin/sh. If you plan on
distributing your changes, though, then you should stick to POSIX sh
because you never know what the end user will be running.