|
Re: chpasswd not working in yocto-2019
Paul,
Thanks for the reply.
I am using Xilinx-SDK based : Linux version 4.19.0-rt1-xilinx-v2019.1
Can you please let me know how to verify the yocto version running on target.
Thanks,
Raghu
Paul,
Thanks for the reply.
I am using Xilinx-SDK based : Linux version 4.19.0-rt1-xilinx-v2019.1
Can you please let me know how to verify the yocto version running on target.
Thanks,
Raghu
|
By
Raghu Icecraft Software Trainings
·
#51839
·
|
|
Re: chpasswd not working in yocto-2019
<raghu.icecraft@...> wrote:
Yocto Project doesn't have a version "2019.1", see
https://wiki.yoctoproject.org/wiki/Releases.
I guess you're using a vendor supplied BSP or SDK with that
<raghu.icecraft@...> wrote:
Yocto Project doesn't have a version "2019.1", see
https://wiki.yoctoproject.org/wiki/Releases.
I guess you're using a vendor supplied BSP or SDK with that
|
By
Paul Barker
·
#51838
·
|
|
chpasswd not working in yocto-2019
Hello,
I have upgraded my kernel poky to 2019.1 version, here i am unable to find chpasswd utility because of which i am unable to set password to my root-user.
Can you please let me know if the
Hello,
I have upgraded my kernel poky to 2019.1 version, here i am unable to find chpasswd utility because of which i am unable to set password to my root-user.
Can you please let me know if the
|
By
Raghu Icecraft Software Trainings
·
#51837
·
|
|
Re: Error during do_install for linux-libc-headers_5.8 recipe during 'bitbake core-image-minimal'
Bisect points at the commit that introduced the hard pseudo abort:
/MR
On Sun, Dec 27, 2020 at 8:43 PM matthias.rampke via lists.yoctoproject.org <matthias.rampke=googlemail.com@...> wrote:
Bisect points at the commit that introduced the hard pseudo abort:
/MR
On Sun, Dec 27, 2020 at 8:43 PM matthias.rampke via lists.yoctoproject.org <matthias.rampke=googlemail.com@...> wrote:
|
By
Matthias Rampke
·
#51836
·
|
|
Re: Error during do_install for linux-libc-headers_5.8 recipe during 'bitbake core-image-minimal'
One more thing: I tried reverting the linux-libc-headers version change (57d5f4ad410d4e9d55bdd9734bf5ab8fa6667a53) and that fails in the same way, so it's not that.
I also realized that the yocto-3.2
One more thing: I tried reverting the linux-libc-headers version change (57d5f4ad410d4e9d55bdd9734bf5ab8fa6667a53) and that fails in the same way, so it's not that.
I also realized that the yocto-3.2
|
By
Matthias Rampke
·
#51835
·
|
|
Re: Error during do_install for linux-libc-headers_5.8 recipe during 'bitbake core-image-minimal'
Hi,
I hit the same issue, also while trying things out on WSL2 (not committed enough to build a dedicated workstation/VM). I found a few more things:
This seems to be a pseudo abort with:
I tried to
Hi,
I hit the same issue, also while trying things out on WSL2 (not committed enough to build a dedicated workstation/VM). I found a few more things:
This seems to be a pseudo abort with:
I tried to
|
By
Matthias Rampke
·
#51834
·
|
|
obvious(?) ruby error: adding erroneous second ".gemspec" suffix
i'm not fluent enough in ruby to want to submit a patch for this, so
i'll let someone higher up the food chain handle it.
trying to build a number of "native" ruby recipes from
meta-openstack, and
i'm not fluent enough in ruby to want to submit a patch for this, so
i'll let someone higher up the food chain handle it.
trying to build a number of "native" ruby recipes from
meta-openstack, and
|
By
Robert P. J. Day
·
#51833
·
|
|
is there a focused place to ask about ruby/gems WRT yocto building?
to prepare for trying to build a number of ruby gems for WR LTS19
(effectively zeus, as always), i thought i'd start simple and begin
with building for qemux86-64 with gatesgarth so i could
to prepare for trying to build a number of ruby gems for WR LTS19
(effectively zeus, as always), i thought i'd start simple and begin
with building for qemux86-64 with gatesgarth so i could
|
By
Robert P. J. Day
·
#51832
·
|
|
[meta-selinux][PATCH] audit: enable arm/aarch64 processor support by default
We encountered a runtime error for auditctl on lib32 image for aarch64:
root@qemuarm64:~# auditctl -a always,exit -F arch=b32 -S adjtimex -S settimeofday -k time_change
arch elf mapping not
We encountered a runtime error for auditctl on lib32 image for aarch64:
root@qemuarm64:~# auditctl -a always,exit -F arch=b32 -S adjtimex -S settimeofday -k time_change
arch elf mapping not
|
By
Yi Zhao
·
#51831
·
|
|
Need to disable IPV6 completely from the yocto image for Raspberrypi
Dear Team,
I'm using yocto dunfell version 3.1.3 . in my image ipv6 configuration is coming, which I don't need. I need to disable it completely.
Please assist me the correct way to do the
Dear Team,
I'm using yocto dunfell version 3.1.3 . in my image ipv6 configuration is coming, which I don't need. I need to disable it completely.
Please assist me the correct way to do the
|
By
@prashant2314
·
#51830
·
|
|
Re: [ANNOUNCEMENT] Yocto Project 3.2.1 (gatesgarth-24.0.1) is Released
By
Peter Kjellerstedt
·
#51829
·
|
|
Re: [ANNOUNCEMENT] Yocto Project 3.2.1 (gatesgarth-24.0.1) is Released
Vineela isn't working this week I think so she might not be able to
help but it looks like the commit tagged is on gatesgarth
Vineela isn't working this week I think so she might not be able to
help but it looks like the commit tagged is on gatesgarth
|
By
Anuj Mittal
·
#51828
·
|
|
Re: [ANNOUNCEMENT] Yocto Project 3.2.1 (gatesgarth-24.0.1) is Released
By
Peter Kjellerstedt
·
#51827
·
|
|
Automatic addition of trailing slashes on layers.openembedded.org
Hi folks,
Working on the docs recently we noticed that there is no automatic
addition of a trailing slash on layers.openembedded.org when
Hi folks,
Working on the docs recently we noticed that there is no automatic
addition of a trailing slash on layers.openembedded.org when
|
By
Paul Barker
·
#51826
·
|
|
M+ & H bugs with Milestone Movements WW51
All,
YP M+ or high bugs which moved to a new milestone in WW51 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
Medium+
5322
Global DNS fallback mechanism not
All,
YP M+ or high bugs which moved to a new milestone in WW51 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
Medium+
5322
Global DNS fallback mechanism not
|
By
Stephen Jolley
·
#51825
·
|
|
Enhancements/Bugs closed WW51!
All,
The below were the owners of enhancements or bugs closed during the last week!
Who
Count
mhalstead@...
3
richard.purdie@...
1
jay.shen.teoh@...
1
Grand Total
5
Thanks,
Stephen K.
All,
The below were the owners of enhancements or bugs closed during the last week!
Who
Count
mhalstead@...
3
richard.purdie@...
1
jay.shen.teoh@...
1
Grand Total
5
Thanks,
Stephen K.
|
By
Stephen Jolley
·
#51824
·
|
|
Current high bug count owners for Yocto Project 3.3
All,
Below is the list as of top 47 bug owners as of the end of WW51 of who have open medium or higher bugs and enhancements against YP 3.3. There are 98 possible work days left until the final
All,
Below is the list as of top 47 bug owners as of the end of WW51 of who have open medium or higher bugs and enhancements against YP 3.3. There are 98 possible work days left until the final
|
By
Stephen Jolley
·
#51823
·
|
|
Yocto Project Newcomer & Unassigned Bugs - Help Needed
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
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
|
By
Stephen Jolley
·
#51822
·
|
|
[auh][PATCH] upgrade-helper.py: handle unassigned recipes correctly
Attempting to send to unassigned@... bounces immediately,
which means the CC recipients (such as oe-core list) won't get the email
either.
Instead, send to cc directly.
Signed-off-by:
Attempting to send to unassigned@... bounces immediately,
which means the CC recipients (such as oe-core list) won't get the email
either.
Instead, send to cc directly.
Signed-off-by:
|
By
Alexander Kanavin
·
#51821
·
|
|
Re: hostapd_free_hapd_data: Interface wlan0 wasn't started
#linux
#kernel
#dunfell
Hi VR,
Please make sure that the interface name in hostapd.conf matches with the wireless interface name of your target.
By default it is set to wlan0, but it could be different in your target (for
Hi VR,
Please make sure that the interface name in hostapd.conf matches with the wireless interface name of your target.
By default it is set to wlan0, but it could be different in your target (for
|
By
Shamil Khan
·
#51820
·
|