* Auto loading nls-iso8859-1kernel module @ 2014-10-31 11:43 Johnny Vestergaard 2014-10-31 11:46 ` Paul Eggleton 0 siblings, 1 reply; 9+ messages in thread From: Johnny Vestergaard @ 2014-10-31 11:43 UTC (permalink / raw) To: poky [-- Attachment #1: Type: text/plain, Size: 484 bytes --] Hi list, I have a basic image where i inherit from core-image and add a few custom packages - nothing fancy, but I am having problems auto loading a module. The module in question is the nls-cp437 module which i can load manually from the root prompt. To be able to auto load it i tried adding module_autoload_nls-cp437 = "nls-cp437" to my one of my package recipes, but not luck. In which recipe exactly are you suppose to add module_autoload? regards, Johnny [-- Attachment #2: Type: text/html, Size: 715 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Auto loading nls-iso8859-1kernel module 2014-10-31 11:43 Auto loading nls-iso8859-1kernel module Johnny Vestergaard @ 2014-10-31 11:46 ` Paul Eggleton 2014-10-31 12:01 ` Johnny Vestergaard 0 siblings, 1 reply; 9+ messages in thread From: Paul Eggleton @ 2014-10-31 11:46 UTC (permalink / raw) To: Johnny Vestergaard; +Cc: poky Hi Johnny, On Friday 31 October 2014 12:43:08 Johnny Vestergaard wrote: > I have a basic image where i inherit from core-image and add a few custom > packages - nothing fancy, but I am having problems auto loading a module. > > The module in question is the nls-cp437 module which i can load manually > from the root prompt. > To be able to auto load it i tried adding > > module_autoload_nls-cp437 = "nls-cp437" > > to my one of my package recipes, but not luck. > > In which recipe exactly are you suppose to add module_autoload? It needs to be either in the kernel recipe or set globally (i.e. in your machine config / distro config / local.conf). Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Auto loading nls-iso8859-1kernel module 2014-10-31 11:46 ` Paul Eggleton @ 2014-10-31 12:01 ` Johnny Vestergaard 2014-10-31 12:11 ` Paul Eggleton 0 siblings, 1 reply; 9+ messages in thread From: Johnny Vestergaard @ 2014-10-31 12:01 UTC (permalink / raw) To: Paul Eggleton; +Cc: poky [-- Attachment #1: Type: text/plain, Size: 1087 bytes --] Hi Paul, Thanks for the quick response. Actually i tried adding it to local.conf, but it seems like bitbake did not pick it up - at least it did not rewrite the rootfs. regards, Johnny On Fri, Oct 31, 2014 at 12:46 PM, Paul Eggleton < paul.eggleton@linux.intel.com> wrote: > Hi Johnny, > > On Friday 31 October 2014 12:43:08 Johnny Vestergaard wrote: > > I have a basic image where i inherit from core-image and add a few custom > > packages - nothing fancy, but I am having problems auto loading a module. > > > > The module in question is the nls-cp437 module which i can load manually > > from the root prompt. > > To be able to auto load it i tried adding > > > > module_autoload_nls-cp437 = "nls-cp437" > > > > to my one of my package recipes, but not luck. > > > > In which recipe exactly are you suppose to add module_autoload? > > It needs to be either in the kernel recipe or set globally (i.e. in your > machine config / distro config / local.conf). > > Cheers, > Paul > > -- > > Paul Eggleton > Intel Open Source Technology Centre > [-- Attachment #2: Type: text/html, Size: 1626 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Auto loading nls-iso8859-1kernel module 2014-10-31 12:01 ` Johnny Vestergaard @ 2014-10-31 12:11 ` Paul Eggleton 2014-10-31 14:49 ` Johnny Vestergaard 0 siblings, 1 reply; 9+ messages in thread From: Paul Eggleton @ 2014-10-31 12:11 UTC (permalink / raw) To: Johnny Vestergaard; +Cc: poky On Friday 31 October 2014 13:01:22 Johnny Vestergaard wrote: > Thanks for the quick response. Actually i tried adding it to local.conf, > but it seems like bitbake did not pick it up - at least it did not rewrite > the rootfs. Right, that is a known issue - you'll have to clean the kernel & image as it won't pick up changes to the module_autoload variable after the kernel has been built: bitbake -c clean virtual/kernel bitbake -c clean your-imagename Then you should be able to build the image with the change to module_autoload incorporated. FYI this issue has been rectified in master and the just released Yocto Project 1.7 (we use a different variable to enable autoloading now). Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Auto loading nls-iso8859-1kernel module 2014-10-31 12:11 ` Paul Eggleton @ 2014-10-31 14:49 ` Johnny Vestergaard 2014-10-31 14:53 ` Paul Eggleton 0 siblings, 1 reply; 9+ messages in thread From: Johnny Vestergaard @ 2014-10-31 14:49 UTC (permalink / raw) To: Paul Eggleton; +Cc: poky [-- Attachment #1: Type: text/plain, Size: 1046 bytes --] On Fri, Oct 31, 2014 at 1:11 PM, Paul Eggleton < paul.eggleton@linux.intel.com> wrote: > On Friday 31 October 2014 13:01:22 Johnny Vestergaard wrote: > > Thanks for the quick response. Actually i tried adding it to local.conf, > > but it seems like bitbake did not pick it up - at least it did not > rewrite > > the rootfs. > > Right, that is a known issue - you'll have to clean the kernel & image as > it > won't pick up changes to the module_autoload variable after the kernel has > been built: > > bitbake -c clean virtual/kernel > bitbake -c clean your-imagename > > Then you should be able to build the image with the change to > module_autoload > incorporated. > > Thanks for the tips. certainly get's me in the right direction. But, putting the following at the end of my local.conf: MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += " kernel-module-nls-cp437" module_autoload_nls-cp437 = "nls-cp437" and cleaning virtual/kernel afterwards still does not autoload the module - but the module is included correctly. [-- Attachment #2: Type: text/html, Size: 1659 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Auto loading nls-iso8859-1kernel module 2014-10-31 14:49 ` Johnny Vestergaard @ 2014-10-31 14:53 ` Paul Eggleton 2014-10-31 15:51 ` Johnny Vestergaard 0 siblings, 1 reply; 9+ messages in thread From: Paul Eggleton @ 2014-10-31 14:53 UTC (permalink / raw) To: Johnny Vestergaard; +Cc: poky On Friday 31 October 2014 15:49:29 Johnny Vestergaard wrote: > On Fri, Oct 31, 2014 at 1:11 PM, Paul Eggleton < > > paul.eggleton@linux.intel.com> wrote: > > On Friday 31 October 2014 13:01:22 Johnny Vestergaard wrote: > > > Thanks for the quick response. Actually i tried adding it to local.conf, > > > but it seems like bitbake did not pick it up - at least it did not > > > > rewrite > > > > > the rootfs. > > > > Right, that is a known issue - you'll have to clean the kernel & image as > > it > > won't pick up changes to the module_autoload variable after the kernel has > > been built: > > > > bitbake -c clean virtual/kernel > > bitbake -c clean your-imagename > > > > Then you should be able to build the image with the change to > > module_autoload > > incorporated. > > Thanks for the tips. certainly get's me in the right direction. > But, putting the following at the end of my local.conf: > > MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += " kernel-module-nls-cp437" > module_autoload_nls-cp437 = "nls-cp437" > > and cleaning virtual/kernel afterwards still does not autoload the module - > but the module is included correctly. Oh, sorry, I think you'd need to do: bitbake -c cleansstate virtual/kernel bitbake -c cleansstate your-imagename Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Auto loading nls-iso8859-1kernel module 2014-10-31 14:53 ` Paul Eggleton @ 2014-10-31 15:51 ` Johnny Vestergaard 2014-10-31 18:50 ` Martin Jansa 0 siblings, 1 reply; 9+ messages in thread From: Johnny Vestergaard @ 2014-10-31 15:51 UTC (permalink / raw) To: Paul Eggleton; +Cc: poky [-- Attachment #1: Type: text/plain, Size: 1646 bytes --] Still no luck, but thanks! Now i at least have a pointer to a potential root cause. On Fri, Oct 31, 2014 at 3:53 PM, Paul Eggleton < paul.eggleton@linux.intel.com> wrote: > On Friday 31 October 2014 15:49:29 Johnny Vestergaard wrote: > > On Fri, Oct 31, 2014 at 1:11 PM, Paul Eggleton < > > > > paul.eggleton@linux.intel.com> wrote: > > > On Friday 31 October 2014 13:01:22 Johnny Vestergaard wrote: > > > > Thanks for the quick response. Actually i tried adding it to > local.conf, > > > > but it seems like bitbake did not pick it up - at least it did not > > > > > > rewrite > > > > > > > the rootfs. > > > > > > Right, that is a known issue - you'll have to clean the kernel & image > as > > > it > > > won't pick up changes to the module_autoload variable after the kernel > has > > > been built: > > > > > > bitbake -c clean virtual/kernel > > > bitbake -c clean your-imagename > > > > > > Then you should be able to build the image with the change to > > > module_autoload > > > incorporated. > > > > Thanks for the tips. certainly get's me in the right direction. > > But, putting the following at the end of my local.conf: > > > > MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += " kernel-module-nls-cp437" > > module_autoload_nls-cp437 = "nls-cp437" > > > > and cleaning virtual/kernel afterwards still does not autoload the > module - > > but the module is included correctly. > > Oh, sorry, I think you'd need to do: > > bitbake -c cleansstate virtual/kernel > bitbake -c cleansstate your-imagename > > Cheers, > Paul > > -- > > Paul Eggleton > Intel Open Source Technology Centre > [-- Attachment #2: Type: text/html, Size: 2389 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Auto loading nls-iso8859-1kernel module 2014-10-31 15:51 ` Johnny Vestergaard @ 2014-10-31 18:50 ` Martin Jansa 2014-10-31 23:06 ` Johnny Vestergaard 0 siblings, 1 reply; 9+ messages in thread From: Martin Jansa @ 2014-10-31 18:50 UTC (permalink / raw) To: Johnny Vestergaard; +Cc: Paul Eggleton, poky [-- Attachment #1: Type: text/plain, Size: 2255 bytes --] On Fri, Oct 31, 2014 at 04:51:26PM +0100, Johnny Vestergaard wrote: > Still no luck, but thanks! Now i at least have a pointer to a potential > root cause. Is this with oe-core master or dizzy? In that case you need to add the module basename in KERNEL_MODULE_AUTOLOAD and in cases where module name == basename, you don't need module_autoload variable at all. > On Fri, Oct 31, 2014 at 3:53 PM, Paul Eggleton < > paul.eggleton@linux.intel.com> wrote: > > > On Friday 31 October 2014 15:49:29 Johnny Vestergaard wrote: > > > On Fri, Oct 31, 2014 at 1:11 PM, Paul Eggleton < > > > > > > paul.eggleton@linux.intel.com> wrote: > > > > On Friday 31 October 2014 13:01:22 Johnny Vestergaard wrote: > > > > > Thanks for the quick response. Actually i tried adding it to > > local.conf, > > > > > but it seems like bitbake did not pick it up - at least it did not > > > > > > > > rewrite > > > > > > > > > the rootfs. > > > > > > > > Right, that is a known issue - you'll have to clean the kernel & image > > as > > > > it > > > > won't pick up changes to the module_autoload variable after the kernel > > has > > > > been built: > > > > > > > > bitbake -c clean virtual/kernel > > > > bitbake -c clean your-imagename > > > > > > > > Then you should be able to build the image with the change to > > > > module_autoload > > > > incorporated. > > > > > > Thanks for the tips. certainly get's me in the right direction. > > > But, putting the following at the end of my local.conf: > > > > > > MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += " kernel-module-nls-cp437" > > > module_autoload_nls-cp437 = "nls-cp437" > > > > > > and cleaning virtual/kernel afterwards still does not autoload the > > module - > > > but the module is included correctly. > > > > Oh, sorry, I think you'd need to do: > > > > bitbake -c cleansstate virtual/kernel > > bitbake -c cleansstate your-imagename > > > > Cheers, > > Paul > > > > -- > > > > Paul Eggleton > > Intel Open Source Technology Centre > > > -- > _______________________________________________ > poky mailing list > poky@yoctoproject.org > https://lists.yoctoproject.org/listinfo/poky -- Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 188 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Auto loading nls-iso8859-1kernel module 2014-10-31 18:50 ` Martin Jansa @ 2014-10-31 23:06 ` Johnny Vestergaard 0 siblings, 0 replies; 9+ messages in thread From: Johnny Vestergaard @ 2014-10-31 23:06 UTC (permalink / raw) To: Martin Jansa; +Cc: Paul Eggleton, poky [-- Attachment #1: Type: text/plain, Size: 2757 bytes --] On Fri, Oct 31, 2014 at 7:50 PM, Martin Jansa <martin.jansa@gmail.com> wrote: > On Fri, Oct 31, 2014 at 04:51:26PM +0100, Johnny Vestergaard wrote: > > Still no luck, but thanks! Now i at least have a pointer to a potential > > root cause. > > Is this with oe-core master or dizzy? > I just tried with dizzy, no luck either. Added the following to local.conf: MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kernel-module-nls-iso8859-1 kernel-module-nls-cp437 kernel-module-nls-utf8" KERNEL_MODULE_AUTOLOAD += "nls-utf8 nls-iso8859-1 nls-cp437" > In that case you need to add the module basename in KERNEL_MODULE_AUTOLOAD > and in > cases where module name == basename, you don't need module_autoload > variable at all. > > > On Fri, Oct 31, 2014 at 3:53 PM, Paul Eggleton < > > paul.eggleton@linux.intel.com> wrote: > > > > > On Friday 31 October 2014 15:49:29 Johnny Vestergaard wrote: > > > > On Fri, Oct 31, 2014 at 1:11 PM, Paul Eggleton < > > > > > > > > paul.eggleton@linux.intel.com> wrote: > > > > > On Friday 31 October 2014 13:01:22 Johnny Vestergaard wrote: > > > > > > Thanks for the quick response. Actually i tried adding it to > > > local.conf, > > > > > > but it seems like bitbake did not pick it up - at least it did > not > > > > > > > > > > rewrite > > > > > > > > > > > the rootfs. > > > > > > > > > > Right, that is a known issue - you'll have to clean the kernel & > image > > > as > > > > > it > > > > > won't pick up changes to the module_autoload variable after the > kernel > > > has > > > > > been built: > > > > > > > > > > bitbake -c clean virtual/kernel > > > > > bitbake -c clean your-imagename > > > > > > > > > > Then you should be able to build the image with the change to > > > > > module_autoload > > > > > incorporated. > > > > > > > > Thanks for the tips. certainly get's me in the right direction. > > > > But, putting the following at the end of my local.conf: > > > > > > > > MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += " kernel-module-nls-cp437" > > > > module_autoload_nls-cp437 = "nls-cp437" > > > > > > > > and cleaning virtual/kernel afterwards still does not autoload the > > > module - > > > > but the module is included correctly. > > > > > > Oh, sorry, I think you'd need to do: > > > > > > bitbake -c cleansstate virtual/kernel > > > bitbake -c cleansstate your-imagename > > > > > > Cheers, > > > Paul > > > > > > -- > > > > > > Paul Eggleton > > > Intel Open Source Technology Centre > > > > > > -- > > _______________________________________________ > > poky mailing list > > poky@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/poky > > > -- > Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com > [-- Attachment #2: Type: text/html, Size: 4514 bytes --] ^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2014-10-31 23:06 UTC | newest] Thread overview: 9+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2014-10-31 11:43 Auto loading nls-iso8859-1kernel module Johnny Vestergaard 2014-10-31 11:46 ` Paul Eggleton 2014-10-31 12:01 ` Johnny Vestergaard 2014-10-31 12:11 ` Paul Eggleton 2014-10-31 14:49 ` Johnny Vestergaard 2014-10-31 14:53 ` Paul Eggleton 2014-10-31 15:51 ` Johnny Vestergaard 2014-10-31 18:50 ` Martin Jansa 2014-10-31 23:06 ` Johnny Vestergaard
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.