Re: [yocto] patches to upgrade meta-jupyter layer packages

[Khem Raj]

On Mon, Nov 18, 2019 at 4:30 PM Chandana Kalluri  wrote:
>
>
> > -Original Message-
> > From: Khem Raj 
> > Sent: Monday, November 18, 2019 4:21 PM
> > To: Chandana Kalluri 
> > Cc: yocto@yoctoproject.org
> > Subject: Re: [yocto] patches to upgrade meta-jupyter layer packages
> >
> > On Mon, Nov 18, 2019 at 4:17 PM Chandana Kalluri 
> > wrote:
> > >
> > > Hello all,
> > >
> > > I have upgraded python packages from meta-jupyter layer to work with the
> > zeus branch.
> > > I am planning to send out the patches to this yocto project mailing list
> > yocto@yoctoproject.org Please let me know if this is alright or if I need to
> > send them to a different mailing list.
> >
> > have you upgraded the recipes in meta-jupyter ? if so then it should be
> > reviewed as per that layers policy, if you are looking for migrating the 
> > recipes
> > from above layer into other layers which use yocto ml for patch submission
> > then its ok
> >
> [CKalluri] Ive upgraded recipes in meta-jupyter layer. There is no mailing 
> list specific to meta-jupyter layer hence the question where to send the 
> patches for upgrade.

perhaps you should contact the manitainers, and if its on github then
github pull requests are usually accepted but
its better to find out. Its good to look at README files e.g.

https://github.com/Xilinx/meta-jupyter/blob/master/README.md

Lists that it accepts github pulls

> > >
> > > Thanks,
> > > Chandana
> > >
> > > --
> > > ___
> > > yocto mailing list
> > > yocto@yoctoproject.org
> > > https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] patches to upgrade meta-jupyter layer packages

[Chandana Kalluri]

> -Original Message-
> From: Khem Raj 
> Sent: Monday, November 18, 2019 4:21 PM
> To: Chandana Kalluri 
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] patches to upgrade meta-jupyter layer packages
> 
> On Mon, Nov 18, 2019 at 4:17 PM Chandana Kalluri 
> wrote:
> >
> > Hello all,
> >
> > I have upgraded python packages from meta-jupyter layer to work with the
> zeus branch.
> > I am planning to send out the patches to this yocto project mailing list
> yocto@yoctoproject.org Please let me know if this is alright or if I need to
> send them to a different mailing list.
> 
> have you upgraded the recipes in meta-jupyter ? if so then it should be
> reviewed as per that layers policy, if you are looking for migrating the 
> recipes
> from above layer into other layers which use yocto ml for patch submission
> then its ok
> 
[CKalluri] Ive upgraded recipes in meta-jupyter layer. There is no mailing list 
specific to meta-jupyter layer hence the question where to send the patches for 
upgrade. 
> >
> > Thanks,
> > Chandana
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] patches to upgrade meta-jupyter layer packages

[Khem Raj]

On Mon, Nov 18, 2019 at 4:17 PM Chandana Kalluri  wrote:
>
> Hello all,
>
> I have upgraded python packages from meta-jupyter layer to work with the zeus 
> branch.
> I am planning to send out the patches to this yocto project mailing list 
> yocto@yoctoproject.org Please let me know if this is alright or if I need to 
> send them to a different mailing list.

have you upgraded the recipes in meta-jupyter ? if so then it should
be reviewed as per that layers policy, if you are looking
for migrating the recipes from above layer into other layers which use
yocto ml for patch submission then its ok

>
> Thanks,
> Chandana
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [qemu] can't find qemu-native recipe

[Khem Raj]

On Mon, Nov 18, 2019 at 4:10 PM Greg Wilson-Lindberg
 wrote:
>
> Hi Khem,
>
> I found the BBCLASSEXTEND in the qemu.inc file, I also found a line in the 
> .bb file:
>
> SRC_URI_append_class-native = " \
>
>
> so I changed my SRC_URI to that and I stopped getting the 'can't find file to 
> patch' error, but the file (syscall.c) is not modified.
>
>
> Here is my qemu_3.0.0.bbappend file, 
> meta-sakura/recipes-devtools/qemu/qemu_3.0.0.bbappend:
>
> FILESEXTRAPATHS_prepend := "${FILE_DIRNAME}/${PN}:"
>
> SRC_URII_append_class-native = 
> "file://syscall.c-add_missing_sockios_header_include.patch"
   ^^
If you pasted exactly what you have then there is a typo above it
should be SRC_URI_append_class-native ...

> And here is the patch file 
> .../qemu/syscall.c-add_missing_sockios_header_include.patch:
> --- a/linux-user/syscall.c2019-11-18 09:42:39.0 -0800
> +++ b/linux-user/syscall.c2019-11-18 09:23:23.0 -0800
> @@ -34,6 +34,7 @@
>  #include 
>  #include 
>  #include 
> +#include 
>  #include 
>  #include 
>  #include 
>
> I am not getting the:
>
> ...tmp/work/x86_64-linux/qemu-native/3.0.0-r0/qemu-3.0.0/linux-user/syscall.c
>
> modified.
>
>
> I'm obviously missing something. Any help would be greatly appreciated.
>
>
> Regards,
>
> Greg
>
>
> 
> From: Khem Raj 
> Sent: Monday, November 18, 2019 3:30:27 PM
> To: Greg Wilson-Lindberg
> Cc: Yocto list discussion
> Subject: Re: [yocto] [qemu] can't find qemu-native recipe
>
> On Mon, Nov 18, 2019 at 3:27 PM Greg Wilson-Lindberg
>  wrote:
> >
> > I'm building thud for the raspberry pi3 for boot2qt on Ubuntu 18.04.
> > I've got a patch that I need to apply to to fix an include file problem and 
> > I can't find the qemu-native recipe. I can find a number of recipes that 
> > depend in one way or another on 'qemu-native', but I can't find a recipe, 
> > class for it or anything that provides it. I can see it being built, and I 
> > get an error that indicates that the patch that I have needs to be applied. 
> > I can find tmp/work/x86_64-linux/qemu-native/.
> >
> > In the cooker log I see:
> > task qemu_3.0.0
> > recipe qemu-native-3.0.0
> >
> > But I can't find a qemu-native.bb file,or bbclass.
> >
> > I'm rather confused at this point, can someone shed a bit of light on what 
> > I'm missing?
> >
>
> there must be BBCLASSEXTEND = "native" in qemu recipe which
> essentially automatically extends the recipe for native case
>
> see
> https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-BBCLASSEXTEND
>
> > Regards,
> > Greg Wilson-Lindberg
> >
> > --
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [qemu] can't find qemu-native recipe

[Greg Wilson-Lindberg]

Hi Khem,

And just after I hit send I realized that I changed 'SRC_URI' to 
'SRC_URII_append_class-native' with the 'II'. I deleted the 'II' and now the 
file is changed like it should be.

Thanks fo all of your help,

Greg Wilson-Lindberg  


 From: Greg Wilson-Lindberg 
Sent: Monday, November 18, 2019 04:10 PM
To: Khem Raj 
Cc: Yocto list discussion 
Subject: Re: [yocto] [qemu] can't find qemu-native recipe

Hi Khem,
I found the BBCLASSEXTEND in the qemu.inc file, I also found a line in the .bb 
file:
SRC_URI_append_class-native = " \

so I changed my SRC_URI to that and I stopped getting the 'can't find file to 
patch' error, but the file (syscall.c) is not modified.

Here is my qemu_3.0.0.bbappend file, 
meta-sakura/recipes-devtools/qemu/qemu_3.0.0.bbappend:
FILESEXTRAPATHS_prepend := "${FILE_DIRNAME}/${PN}:"

SRC_URII_append_class-native = 
"file://syscall.c-add_missing_sockios_header_include.patch"

And here is the patch file 
.../qemu/syscall.c-add_missing_sockios_header_include.patch:
--- a/linux-user/syscall.c    2019-11-18 09:42:39.0 -0800
+++ b/linux-user/syscall.c    2019-11-18 09:23:23.0 -0800
@@ -34,6 +34,7 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include 
 #include 
I am not getting the: 
...tmp/work/x86_64-linux/qemu-native/3.0.0-r0/qemu-3.0.0/linux-user/syscall.c
modified.

I'm obviously missing something. Any help would be greatly appreciated.

Regards,
Greg


From: Khem Raj 
Sent: Monday, November 18, 2019 3:30:27 PM
To: Greg Wilson-Lindberg
Cc: Yocto list discussion
Subject: Re: [yocto] [qemu] can't find qemu-native recipe 
 
On Mon, Nov 18, 2019 at 3:27 PM Greg Wilson-Lindberg
 wrote:
>
> I'm building thud for the raspberry pi3 for boot2qt on Ubuntu 18.04.
> I've got a patch that I need to apply to to fix an include file problem and I 
> can't find the qemu-native recipe. I can find a number of recipes that depend 
> in one way or another on 'qemu-native', but I can't find a recipe, class for 
> it or anything that provides it. I can see it being built, and I get an error 
> that indicates that the patch that I have needs to be applied. I can find 
> tmp/work/x86_64-linux/qemu-native/.
>
> In the cooker log I see:
> task qemu_3.0.0
> recipe qemu-native-3.0.0
>
> But I can't find a qemu-native.bb file,or bbclass.
>
> I'm rather confused at this point, can someone shed a bit of light on what 
> I'm missing?
>

there must be BBCLASSEXTEND = "native" in qemu recipe which
essentially automatically extends the recipe for native case

see
https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-BBCLASSEXTEND

> Regards,
> Greg Wilson-Lindberg
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] patches to upgrade meta-jupyter layer packages

[Chandana Kalluri]

Hello all,

I have upgraded python packages from meta-jupyter layer to work with the zeus 
branch.
I am planning to send out the patches to this yocto project mailing list 
yocto@yoctoproject.org Please let me know if this is alright or if I need to 
send them to a different mailing list.

Thanks,
Chandana

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [qemu] can't find qemu-native recipe

[Greg Wilson-Lindberg]

Hi Khem,

I found the BBCLASSEXTEND in the qemu.inc file, I also found a line in the .bb 
file:

SRC_URI_append_class-native = " \


so I changed my SRC_URI to that and I stopped getting the 'can't find file to 
patch' error, but the file (syscall.c) is not modified.


Here is my qemu_3.0.0.bbappend file, 
meta-sakura/recipes-devtools/qemu/qemu_3.0.0.bbappend:

FILESEXTRAPATHS_prepend := "${FILE_DIRNAME}/${PN}:"

SRC_URII_append_class-native = 
"file://syscall.c-add_missing_sockios_header_include.patch"

And here is the patch file 
.../qemu/syscall.c-add_missing_sockios_header_include.patch:
--- a/linux-user/syscall.c2019-11-18 09:42:39.0 -0800
+++ b/linux-user/syscall.c2019-11-18 09:23:23.0 -0800
@@ -34,6 +34,7 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include 
 #include 

I am not getting the:

...tmp/work/x86_64-linux/qemu-native/3.0.0-r0/qemu-3.0.0/linux-user/syscall.c

modified.


I'm obviously missing something. Any help would be greatly appreciated.


Regards,

Greg



From: Khem Raj 
Sent: Monday, November 18, 2019 3:30:27 PM
To: Greg Wilson-Lindberg
Cc: Yocto list discussion
Subject: Re: [yocto] [qemu] can't find qemu-native recipe

On Mon, Nov 18, 2019 at 3:27 PM Greg Wilson-Lindberg
 wrote:
>
> I'm building thud for the raspberry pi3 for boot2qt on Ubuntu 18.04.
> I've got a patch that I need to apply to to fix an include file problem and I 
> can't find the qemu-native recipe. I can find a number of recipes that depend 
> in one way or another on 'qemu-native', but I can't find a recipe, class for 
> it or anything that provides it. I can see it being built, and I get an error 
> that indicates that the patch that I have needs to be applied. I can find 
> tmp/work/x86_64-linux/qemu-native/.
>
> In the cooker log I see:
> task qemu_3.0.0
> recipe qemu-native-3.0.0
>
> But I can't find a qemu-native.bb file,or bbclass.
>
> I'm rather confused at this point, can someone shed a bit of light on what 
> I'm missing?
>

there must be BBCLASSEXTEND = "native" in qemu recipe which
essentially automatically extends the recipe for native case

see
https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-BBCLASSEXTEND

> Regards,
> Greg Wilson-Lindberg
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [qemu] can't find qemu-native recipe

[Khem Raj]

On Mon, Nov 18, 2019 at 3:27 PM Greg Wilson-Lindberg
 wrote:
>
> I'm building thud for the raspberry pi3 for boot2qt on Ubuntu 18.04.
> I've got a patch that I need to apply to to fix an include file problem and I 
> can't find the qemu-native recipe. I can find a number of recipes that depend 
> in one way or another on 'qemu-native', but I can't find a recipe, class for 
> it or anything that provides it. I can see it being built, and I get an error 
> that indicates that the patch that I have needs to be applied. I can find 
> tmp/work/x86_64-linux/qemu-native/.
>
> In the cooker log I see:
> task qemu_3.0.0
> recipe qemu-native-3.0.0
>
> But I can't find a qemu-native.bb file,or bbclass.
>
> I'm rather confused at this point, can someone shed a bit of light on what 
> I'm missing?
>

there must be BBCLASSEXTEND = "native" in qemu recipe which
essentially automatically extends the recipe for native case

see
https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-BBCLASSEXTEND

> Regards,
> Greg Wilson-Lindberg
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [qemu] can't find qemu-native recipe

[Greg Wilson-Lindberg]

I'm building thud for the raspberry pi3 for boot2qt on Ubuntu 18.04.
I've got a patch that I need to apply to to fix an include file problem and I 
can't find the qemu-native recipe. I can find a number of recipes that depend 
in one way or another on 'qemu-native', but I can't find a recipe, class for it 
or anything that provides it. I can see it being built, and I get an error that 
indicates that the patch that I have needs to be applied. I can find 
tmp/work/x86_64-linux/qemu-native/. 

In the cooker log I see:
task qemu_3.0.0
recipe qemu-native-3.0.0

But I can't find a qemu-native.bb file,or bbclass.

I'm rather confused at this point, can someone shed a bit of light on what I'm 
missing?

Regards,
Greg Wilson-Lindberg  
 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] GRUB without UEFI

[Maciej Pijanowski]

Hi,

I'm wondering whether anyone here uses Yocto to build images
for legacy x86 systems (without UEFI) with GRUB as a bootloader.
I know that the GRUB with UEFI is well supported in Yocto.

I'm looking for a way to create a bootable disk (ideally using WIC)
for legacy BIOS with GRUB preinstalled.

i know there is a bootimg-pcbios wic plugin:
http://git.yoctoproject.org/cgit.cgi/poky/tree/scripts/lib/wic/plugins/source/bootimg-pcbios.py?id=38125456ffa6112941a3608fcba9ed2032353740
which uses SYSLINUX.

Thoughts welcome.

Thanks

--
Maciej Pijanowski
Embedded Systems Engineer
https://3mdeb.com | @3mdeb_com

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] KVM kernel modules missing from Yocto kernel

[Wayne Li]

So it looks like KVM is built in (at least it's supposed to be).  I'm
pretty sure that is the case after looking at my kernel configuration file:

https://gist.github.com/WayneZhenLi/4172cd4a819b71a11b85fc5aaa57ebd1

I then changed the CONFIG_KVM=y line to CONFIG_KVM=m and also added the
IMAGE_INSTALL += "kernel-modules" line to my local.conf file.
Unfortunately, again nothing seemed to have changed and there are no new
KVM-related .ko files in the image.  However, this does bring up some
questions.  I have a kernel loaded onto the SD card from that was built
right after we added the content from the KVM .config file to the kernel
configuration file. This kernel is currently up and running on my T4240 RDB
board.  The KVM kernel module doesn't show up when I run lsmod nor does it
show up in the file /lib/modules/4.1.8-rt8+gdb51baf/modules.builtin (a file
that is supposed to list all built-in modules).  However, if I go into the
/sys/module folder, there is a kvm folder in there.  So I guess this means
the kvm module can potentially be built into the system but for whatever
reason it isn't being built in?

On Mon, Nov 18, 2019 at 1:12 PM Maciej Pijanowski <
maciej.pijanow...@3mdeb.com> wrote:

>
> On 18.11.2019 19:22, Wayne Li wrote:
>
> Dear Yocto Developers,
>
> I'm trying to incorporate KVM into a Yocto kernel me and my coworker build
> for a T4240 RDB (which has a PowerPC CPU).  The problem is, no matter what
> I do the KVM kernel module (I'm expecting a kvm.ko or any .ko file along
> those lines) is not present in the image.
>
> First I tried adding the content of the .config file generated when
> configuring the kernel for KVM support into the kernel configuration file.
> This resulted in KVM source directories appearing in the kernel but no KVM
> related kernel modules are present.  I explain this in more detail in a
> previous email conversation I had with the Yocto community (saved in a
> Github gist for readability):
>
> What is your kenel config? Is KVM built-in (y) or built as module (m)?
>
>
> https://gist.github.com/WayneZhenLi/d5d7a5e8c30e6d4b7cd4541d0c24cab5
>
> Since then I've tried a few things.  First, I added the following lines to
> the local.conf file (found in build_t4240rdb-64b/conf folder):
>
> MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kernel-modules"
> MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kvm-image-minimal"
>
> I din't know which image you are building. Those variables are tricky,
> since
> they only applies when basing on the packagegroup-core-boot packagegroup.
> Please refer to the documentation.
>
>
> But that didn't seem to work as there weren't any new .ko files in the
> final image.  Next I tried adding the following lines to the same
> local.conf file:
>
> CORE_IMAGE_EXTRA_INSTALL += "kernel-modules"
> CORE_IMAGE_EXTRA_INSTALL += "kvm-image-minimal"
>
> Why trying to install the image into image? kvm-image-minimal is not a
> package, it is image recipe.
> The build can definitely break in this case.
>
> This time I get an error saying "ERROR: kvm-image-minimal not found in the
> base feeds (t4240rdb-64b ppc64e6500 powerpc64 noarch any all)".  Also if
> just run a "ERROR: bitbake kvm-image-minimal" to see what's going on with
> that particular recipe I get an error saying "kernel-module-kvm-intel" not
> found in the base feeds (t4240rdb-64b ppc64e6500 powerpc64 noarch any all).
>
> Would I have to write recipes for the packages listed in kvm-image-minimal
> such as kernel-module-kvm-intel or kernel-module-kvm?  Note that I'm not
> even building the image for intel; I'm building it for PowerPC.  Anyway, I
> just feel like writing recipes for the KVM kernel modules isn't the correct
> step.  Like maybe I just messed up my with my configuration somehow?  What
> are your thoughts?
>
> IMHO: Simply use IMAGE_INSTALL += "kernel-modules" (IMAGE_INSTALL +=
> "kernel-module-kvm" will likely install just the KVM module)
> in your local.conf to install all built kernel modules. If KVM module
> won't be present in the rootfs, it means it was not built.
>
> Please inspect your kernel work dir (packages-split dir) to find out which
> packages were produced by
> the kernel recipe. It will be something like
> build/tmp/work/XX/linux-yocto/XX/packages-split
>
>
> -Thanks!, Wayne Li
>
>
> --
> Maciej Pijanowski
> Embedded Systems Engineerhttps://3mdeb.com | @3mdeb_com
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] KVM kernel modules missing from Yocto kernel

[Maciej Pijanowski]

On 18.11.2019 19:22, Wayne Li wrote:

Dear Yocto Developers,

I'm trying to incorporate KVM into a Yocto kernel me and my coworker 
build for a T4240 RDB (which has a PowerPC CPU).  The problem is, no 
matter what I do the KVM kernel module (I'm expecting a kvm.ko or any 
.ko file along those lines) is not present in the image.


First I tried adding the content of the .config file generated when 
configuring the kernel for KVM support into the kernel configuration 
file.  This resulted in KVM source directories appearing in the kernel 
but no KVM related kernel modules are present.  I explain this in more 
detail in a previous email conversation I had with the Yocto community 
(saved in a Github gist for readability):

What is your kenel config? Is KVM built-in (y) or built as module (m)?


https://gist.github.com/WayneZhenLi/d5d7a5e8c30e6d4b7cd4541d0c24cab5

Since then I've tried a few things.  First, I added the following 
lines to the local.conf file (found in build_t4240rdb-64b/conf folder):


MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kernel-modules"
MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kvm-image-minimal"

I din't know which image you are building. Those variables are tricky, since
they only applies when basing on the packagegroup-core-boot packagegroup.
Please refer to the documentation.


But that didn't seem to work as there weren't any new .ko files in the 
final image.  Next I tried adding the following lines to the same 
local.conf file:


CORE_IMAGE_EXTRA_INSTALL += "kernel-modules"
CORE_IMAGE_EXTRA_INSTALL += "kvm-image-minimal"

Why trying to install the image into image? kvm-image-minimal is not a 
package, it is image recipe.

The build can definitely break in this case.
This time I get an error saying "ERROR: kvm-image-minimal not found in 
the base feeds (t4240rdb-64b ppc64e6500 powerpc64 noarch any all)".  
Also if just run a "ERROR: bitbake kvm-image-minimal" to see what's 
going on with that particular recipe I get an error saying 
"kernel-module-kvm-intel" not found in the base feeds (t4240rdb-64b 
ppc64e6500 powerpc64 noarch any all).


Would I have to write recipes for the packages listed in 
kvm-image-minimal such as kernel-module-kvm-intel or 
kernel-module-kvm?  Note that I'm not even building the image for 
intel; I'm building it for PowerPC.  Anyway, I just feel like writing 
recipes for the KVM kernel modules isn't the correct step.  Like maybe 
I just messed up my with my configuration somehow?  What are your 
thoughts?
IMHO: Simply use IMAGE_INSTALL += "kernel-modules" (IMAGE_INSTALL += 
"kernel-module-kvm" will likely install just the KVM module)
in your local.conf to install all built kernel modules. If KVM module 
won't be present in the rootfs, it means it was not built.


Please inspect your kernel work dir (packages-split dir) to find out 
which packages were produced by
the kernel recipe. It will be something like 
build/tmp/work/XX/linux-yocto/XX/packages-split


-Thanks!, Wayne Li



--
Maciej Pijanowski
Embedded Systems Engineer
https://3mdeb.com | @3mdeb_com

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] KVM kernel modules missing from Yocto kernel

[Wayne Li]

Dear Yocto Developers,

I'm trying to incorporate KVM into a Yocto kernel me and my coworker build
for a T4240 RDB (which has a PowerPC CPU).  The problem is, no matter what
I do the KVM kernel module (I'm expecting a kvm.ko or any .ko file along
those lines) is not present in the image.

First I tried adding the content of the .config file generated when
configuring the kernel for KVM support into the kernel configuration file.
This resulted in KVM source directories appearing in the kernel but no KVM
related kernel modules are present.  I explain this in more detail in a
previous email conversation I had with the Yocto community (saved in a
Github gist for readability):

https://gist.github.com/WayneZhenLi/d5d7a5e8c30e6d4b7cd4541d0c24cab5

Since then I've tried a few things.  First, I added the following lines to
the local.conf file (found in build_t4240rdb-64b/conf folder):

MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kernel-modules"
MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS += "kvm-image-minimal"

But that didn't seem to work as there weren't any new .ko files in the
final image.  Next I tried adding the following lines to the same
local.conf file:

CORE_IMAGE_EXTRA_INSTALL += "kernel-modules"
CORE_IMAGE_EXTRA_INSTALL += "kvm-image-minimal"

This time I get an error saying "ERROR: kvm-image-minimal not found in the
base feeds (t4240rdb-64b ppc64e6500 powerpc64 noarch any all)".  Also if
just run a "ERROR: bitbake kvm-image-minimal" to see what's going on with
that particular recipe I get an error saying "kernel-module-kvm-intel" not
found in the base feeds (t4240rdb-64b ppc64e6500 powerpc64 noarch any all).

Would I have to write recipes for the packages listed in kvm-image-minimal
such as kernel-module-kvm-intel or kernel-module-kvm?  Note that I'm not
even building the image for intel; I'm building it for PowerPC.  Anyway, I
just feel like writing recipes for the KVM kernel modules isn't the correct
step.  Like maybe I just messed up my with my configuration somehow?  What
are your thoughts?

-Thanks!, Wayne Li
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] QA notification for completed autobuilder build (yocto-2.7.2.rc1)

[Khem Raj]

looks good to me.

On Sun, Nov 17, 2019 at 11:00 PM Jain, Sangeeta  wrote:
>
> Hello all,
>
> This is the full report for 2.7.2 RC1:
> https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
>
> === Summary 
> No high milestone defects.
> No new defect found in this cycle.
>
>
> Thanks & Regards,
> Sangeeta Jain
>
> >-Original Message-
> >From: Pokybuild User 
> >Sent: Thursday, October 31, 2019 1:23 AM
> >To: yocto@yoctoproject.org
> >Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv
> >; Yeoh, Ee Peng ; Chan,
> >Aaron Chun Yew ; Ang, Chin Huat
> >; richard.pur...@linuxfoundation.org;
> >akuster...@gmail.com; sjolley.yp...@gmail.com; Jain, Sangeeta
> >
> >Subject: QA notification for completed autobuilder build (yocto-2.7.2.rc1)
> >
> >
> >A build flagged for QA (yocto-2.7.2.rc1) was completed on the autobuilder 
> >and is
> >available at:
> >
> >
> >https://autobuilder.yocto.io/pub/releases/yocto-2.7.2.rc1
> >
> >
> >Build hash information:
> >
> >bitbake: 75d6648f232a06b99c54a1e33324a7fc1cd15b38
> >meta-gplv2: d5d9fc9a4bbd365d6cd6fe4d6a8558f7115c17da
> >meta-intel: ca26bed652722167b2dbe0042cfc2406029e9c6c
> >meta-mingw: 10695afe8cd406844e0d0dd868c11677e07557d4
> >oecore: 726c3b92298981f5aa2f2449ceeec7b4bf84ed29
> >poky: d0f73121551dc98f6924cd77952bf9ebf5ef3dd7
> >
> >
> >
> >This is an automated message from the Yocto Project Autobuilder
> >Git: git://git.yoctoproject.org/yocto-autobuilder2
> >Email: richard.pur...@linuxfoundation.org
> >
> >
> >
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

[Stephen K Jolley]

All,

 

The triage team is starting to try and collect up and classify bugs which a 
newcomer to the project would be able to work on in a way which means people 
can find them. They're being listed on the triage page under the appropriate 
heading:

 

  
https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work on 
who doesn't have deep experience with the project.  If anyone can help, please 
take ownership of the bug and send patches!  If anyone needs help/advice there 
are people on irc who can likely do so, or some of the more experienced 
contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs 
reported into the Bugzilla. The number of people attending that meeting has 
fallen, as have the number of people available to help fix bugs. One of the 
things we hear users report is they don't know how to help. We (the triage 
team) are therefore going to start reporting out the currently 298 unassigned 
or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out 
with these.  Bugs are split into two types, "true bugs" where things don't work 
as they should and "enhancements" which are features we'd want to add to the 
system.  There are also roughly four different "priority" classes right now, 
“3.1”, “3.2, "3.99" and "Future", the more pressing/urgent issues being in 
"3.1" and then “3.2”.

 

Please review this link and if a bug is something you would be able to help 
with either take ownership of the bug, or send me ( 
 sjolley.yp...@gmail.com) an e-mail with the 
bug number you would like and I will assign it to you (please make sure you 
have a Bugzilla account).  The list is at:  
 
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs

 

Thanks,

Stephen K. Jolley

Yocto Project Program Manager

7867 SW Bayberry Dr., Beaverton, OR 97007

*Cell:(208) 244-4460

* Email: s  
jolley.yp...@gmail.com  

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] :how to solve the basehash value changed from 'xxx' to 'aaaa' ?

[Mark Hatle]

You are changing the value of something in there dynamically.  Most likely
you've done something like embed the current date and time.

If you do something like that, you need to evaluate it -once- during parse time
and not again.  This will fix the hash value at parse time and not change it 
later.

--Mark

On 11/12/19 10:20 PM, www wrote:
> Dear all,
> 
> When I modify the os-release file in my yocto project, it appear some error, 
> and
> how can I solve it ? Who can give me some help or advice? Thank you！
> I carried out the recommended order and it didn't work.
> 
> /ERROR: os-release-1.0-r0 do_compile: Taskhash mismatch
> ce133f0458608e03aa55224df28156e523e54903115efbbcd62946f84a867201 versus
> 7269881f0eb1759ed420a2db4c04fb477cd8c1288bc5f82df5c8161bb926ea1f for
> /home/temp/wanghp/wsp/git_s/local-source/obmc-sugon/entity_fruu/meta/recipes-core/os-release/os-release.bb.do_compile/
> /ERROR: Taskhash mismatch
> ce133f0458608e03aa55224df28156e523e54903115efbbcd62946f84a867201 versus
> 7269881f0eb1759ed420a2db4c04fb477cd8c1288bc5f82df5c8161bb926ea1f for
> /home/temp/wanghp/wsp/git_s/local-source/obmc-sugon/entity_fruu/meta/recipes-core/os-release/os-release.bb.do_compile/
> /ERROR: When reparsing
> /home/temp/wanghp/wsp/git_s/local-source/obmc-sugon/entity_fruu/meta/recipes-core/os-release/os-release.bb.do_compile,//
>  //the
> basehash value changed from
> 99a42a1a3b1a151de604267b159558ecaf1031a3bec8917df132c81302e729a5 to
> 4f3288a8763e2e1af78e4b3cdd9c0c0ccb3b0d5c78a3073c188b22200df2a9b0.// //The
> metadata is not deterministic and this needs to be fixed./
> /ERROR: The following commands may help:/
> /ERROR: $ bitbake os-release -cdo_compile -Snone/
> /ERROR: Then:/
> /ERROR: $ bitbake os-release -cdo_compile -Sprintdiff/
> 
> /ERROR: When reparsing
> /home/temp/wanghp/wsp/git_s/local-source/obmc-sugon/entity_fruu/meta/recipes-core/os-release/os-release.bb.do_compile,
>  //the
> basehash value changed from
> 99a42a1a3b1a151de604267b159558ecaf1031a3bec8917df132c81302e729a5 to
> 47c30012daa6aa77be09a93fe21e66995361ef26b4487111005617db8cb4de59. The metadata
> is not deterministic and this needs to be fixed./
> /ERROR: The following commands may help:/
> /ERROR: $ bitbake os-release -cdo_compile -Snone/
> /ERROR: Then:/
> /ERROR: $ bitbake os-release -cdo_compile -Sprintdiff/
> 
> thanks,
> Byron
> 
> 
> 
>  
> 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Enable systemd service with parameter

[Mateusz Majchrzycki]

Thanks for you help, finally I've got it working.

Just for clarification, I'm using Yocto rocko. I've checked and support for
parametrized systemd services is available in systemd.bbclass.
Also I've tried to make a dummy profile file and populate it on rootfs
instead of symlink. It also didn't work.

Finally I've change my recipe from standalone to append. My
openvpn_%.bbappend looks like:

inherit systemd
SYSTEMD_SERVICE_${PN} = "openvpn@clientprofile.service"
SYSTEMD_AUTO_ENABLE = "enable"

do_install_append() {
install -d ${D}${sysconfdir}/openvpn/
ln -sf /data/etc/openvpn/clientprofile.conf
${D}${sysconfdir}/openvpn/clientprofile.conf
}

And it works. I suppose my standalone recipe has been missing something
that prevents systemd from finding/enabling the service.
Hope it helps someone.

Mateusz


On Mon, Nov 18, 2019 at 10:47 AM Ross Burton  wrote:

> On 17/11/2019 19:44, Mateusz Majchrzycki wrote:
> > What am I doing wrong? I suppose the symlink is not a problem as
> > normally systemctl enables service with non-existent file as a parameter
> > (it fails on start, but not enabling).
>
> The problem is that the systemd class doesn't know what to do here.  I
> thought there were patches to handle this already, what release of yocto
> are you using?
>
> Ross
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>


-- 
Pozdrawiam
Mateusz Majchrzycki
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Enable systemd service with parameter

[Ross Burton]

On 17/11/2019 19:44, Mateusz Majchrzycki wrote:
What am I doing wrong? I suppose the symlink is not a problem as 
normally systemctl enables service with non-existent file as a parameter 
(it fails on start, but not enabling).


The problem is that the systemd class doesn't know what to do here.  I 
thought there were patches to handle this already, what release of yocto 
are you using?


Ross
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] :how to solve the basehash value changed from 'xxx' to 'aaaa' ?

[www]

Dear all,


When I modify the os-release file in my yocto project, it appear some error, 
and how can I solve it ? Who can give me some help or advice? Thank you！
I carried out the recommended order and it didn't work.


ERROR: os-release-1.0-r0 do_compile: Taskhash mismatch 
ce133f0458608e03aa55224df28156e523e54903115efbbcd62946f84a867201 versus 
7269881f0eb1759ed420a2db4c04fb477cd8c1288bc5f82df5c8161bb926ea1f for 
/home/temp/wanghp/wsp/git_s/local-source/obmc-sugon/entity_fruu/meta/recipes-core/os-release/os-release.bb.do_compile
ERROR: Taskhash mismatch 
ce133f0458608e03aa55224df28156e523e54903115efbbcd62946f84a867201 versus 
7269881f0eb1759ed420a2db4c04fb477cd8c1288bc5f82df5c8161bb926ea1f for 
/home/temp/wanghp/wsp/git_s/local-source/obmc-sugon/entity_fruu/meta/recipes-core/os-release/os-release.bb.do_compile
ERROR: When reparsing 
/home/temp/wanghp/wsp/git_s/local-source/obmc-sugon/entity_fruu/meta/recipes-core/os-release/os-release.bb.do_compile,
 the basehash value changed from 
99a42a1a3b1a151de604267b159558ecaf1031a3bec8917df132c81302e729a5 to 
4f3288a8763e2e1af78e4b3cdd9c0c0ccb3b0d5c78a3073c188b22200df2a9b0. The metadata 
is not deterministic and this needs to be fixed.
ERROR: The following commands may help:
ERROR: $ bitbake os-release -cdo_compile -Snone
ERROR: Then:
ERROR: $ bitbake os-release -cdo_compile -Sprintdiff


ERROR: When reparsing 
/home/temp/wanghp/wsp/git_s/local-source/obmc-sugon/entity_fruu/meta/recipes-core/os-release/os-release.bb.do_compile,
 the basehash value changed from 
99a42a1a3b1a151de604267b159558ecaf1031a3bec8917df132c81302e729a5 to 
47c30012daa6aa77be09a93fe21e66995361ef26b4487111005617db8cb4de59. The metadata 
is not deterministic and this needs to be fixed.
ERROR: The following commands may help:
ERROR: $ bitbake os-release -cdo_compile -Snone
ERROR: Then:
ERROR: $ bitbake os-release -cdo_compile -Sprintdiff


thanks,
Byron

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] :how to solve the basehash value changed from 'xxx' to 'aaaa' ?

[www]

Dear all,


When I modify the os-release file in my yocto project, it appear some error, 
and how can I solve it ? Who can give me some help or advice? Thank you！
I carried out the recommended order and it didn't work.


ERROR: os-release-1.0-r0 do_compile: Taskhash mismatch 
ce133f0458608e03aa55224df28156e523e54903115efbbcd62946f84a867201 versus 
7269881f0eb1759ed420a2db4c04fb477cd8c1288bc5f82df5c8161bb926ea1f for 
/home/temp/wanghp/wsp/git_s/local-source/obmc-sugon/entity_fruu/meta/recipes-core/os-release/os-release.bb.do_compile
ERROR: Taskhash mismatch 
ce133f0458608e03aa55224df28156e523e54903115efbbcd62946f84a867201 versus 
7269881f0eb1759ed420a2db4c04fb477cd8c1288bc5f82df5c8161bb926ea1f for 
/home/temp/wanghp/wsp/git_s/local-source/obmc-sugon/entity_fruu/meta/recipes-core/os-release/os-release.bb.do_compile
ERROR: When reparsing 
/home/temp/wanghp/wsp/git_s/local-source/obmc-sugon/entity_fruu/meta/recipes-core/os-release/os-release.bb.do_compile,
 the basehash value changed from 
99a42a1a3b1a151de604267b159558ecaf1031a3bec8917df132c81302e729a5 to 
4f3288a8763e2e1af78e4b3cdd9c0c0ccb3b0d5c78a3073c188b22200df2a9b0. The metadata 
is not deterministic and this needs to be fixed.
ERROR: The following commands may help:
ERROR: $ bitbake os-release -cdo_compile -Snone
ERROR: Then:
ERROR: $ bitbake os-release -cdo_compile -Sprintdiff


ERROR: When reparsing 
/home/temp/wanghp/wsp/git_s/local-source/obmc-sugon/entity_fruu/meta/recipes-core/os-release/os-release.bb.do_compile,
 the basehash value changed from 
99a42a1a3b1a151de604267b159558ecaf1031a3bec8917df132c81302e729a5 to 
47c30012daa6aa77be09a93fe21e66995361ef26b4487111005617db8cb4de59. The metadata 
is not deterministic and this needs to be fixed.
ERROR: The following commands may help:
ERROR: $ bitbake os-release -cdo_compile -Snone
ERROR: Then:
ERROR: $ bitbake os-release -cdo_compile -Sprintdiff


thanks,
Byron-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto