Skip to contentSkip to conversation

Problem genrerating module autoloading commands

DISCUSSION Marc Ferland 3 participants 4 messages Oct 18, 2012

lore
Share & tools
lore
#0 lore raw

Hi,

I'm having trouble generating the module auto-loading instructions in /etc for one of my modules. I have already many modules that all work fine, but for some reason this one does not get listed in /etc/modules nor /etc/modules-load.d.

The only thing that distinguishes this module from the other ones is that it has the same name has the MACHINE and layer. So basically I have something like:

build/conf/local.conf:
MACHINE = foo

poky/meta-foo/conf/machine/foo.conf:
module_autoload_foo = "foo"

The module gets built correctly and is included in the images. Running 'modprobe foo' works as intended on the target hardware.

Did I fall in some edge case?

Regards,

Marc

#1 lore raw
Quoted 14 lines · Marc Ferland

Hi,

I'm having trouble generating the module auto-loading instructions in /etc for one of my modules. I have already many modules that all work fine, but for some reason this one does not get listed in /etc/modules nor /etc/modules-load.d.

The only thing that distinguishes this module from the other ones is that it has the same name has the MACHINE and layer. So basically I have something like:

build/conf/local.conf:
MACHINE = foo

Quoted 7 lines

poky/meta-foo/conf/machine/foo.conf:
module_autoload_foo = "foo"

The module gets built correctly and is included in the images. Running 'modprobe foo' works as intended on the target hardware.

Did I fall in some edge case?

Does foo have any '-' or '_'?

If yes then foo needs to match module name, not name of kernel module package (where we always have '-').

Quoted 8 lines

Regards,

Marc
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#2 lore raw
Quoted 18 lines · Martin Jansa
Quoted 17 lines · Marc Ferland

Hi,

I'm having trouble generating the module auto-loading instructions in /etc for one of my modules. I have already many modules that all work fine, but for some reason this one does not get listed in /etc/modules nor /etc/modules-load.d.

The only thing that distinguishes this module from the other ones is that it has the same name has the MACHINE and layer. So basically I have something like:

build/conf/local.conf:
MACHINE = foo

poky/meta-foo/conf/machine/foo.conf:
module_autoload_foo = "foo"

Quoted 7 lines
Quoted 4 lines

The module gets built correctly and is included in the images. Running 'modprobe foo' works as intended on the target hardware.

Did I fall in some edge case?

Does foo have any '-' or '_'?

No. Just lower case letters.
Marc

#3 lore raw
Quoted 22 lines · On Thursday 18 October 2012 11:29:58 Marc Ferland wrote:
Quoted 21 lines · Martin Jansa
Quoted 20 lines · Marc Ferland

Hi,

I'm having trouble generating the module auto-loading instructions in /etc for one of my modules. I have already many modules that all work fine, but for some reason this one does not get listed in /etc/modules nor /etc/modules-load.d.

The only thing that distinguishes this module from the other ones is that it has the same name has the MACHINE and layer. So basically I have something like:

build/conf/local.conf:
MACHINE = foo

poky/meta-foo/conf/machine/foo.conf:
module_autoload_foo = "foo"

The module gets built correctly and is included in the images. Running 'modprobe foo' works as intended on the target hardware.

Quoted 6 lines
Quoted 3 lines
Quoted 1 line

Did I fall in some edge case?

Does foo have any '-' or '_'?

No. Just lower case letters.
Marc

I suspect this is falling foul of OVERRIDES since it matches ${MACHINE} which is in OVERRIDES. What the workaround would be for this I'm not sure.

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre