Re: chpasswd not working in yocto-2019
Raghu Icecraft Software Trainings
Hello, Thanks for the reply. I mailed to
Thanks, Raghu On Mon, Dec 28, 2020 at 7:28 PM Philip Balister <philip@...> wrote: On 12/28/20 7:33 AM, Raghu Icecraft Software Trainings wrote: |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Need to disable IPV6 completely from the yocto image for Raspberrypi
md.sadiq@...
Hi,
To remove completely ipv6 from distro disable all the kernel configurations related to ipv6, add the the below line in the local.conf file DISTRO_FEATURES_remove = "ipv6". If above doesnot help create your own distro file owndistro.conf and add below lines to remove unwanted features as follows DISTRO_FEATURES_remove = " ipv6 x11 wayland" and change local.conf as follows DISTRO ?= "owndistro" Regards, Sadiq |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Help regarding yocto receipe (bluez5)
chandra naik <chandumail05@...>
Hi can we get obexpush open source package for yocto build ? we are not able to find .
kernel version - 4.14
DISTRO_VERSION = "2.5.1" On Tue, Dec 29, 2020 at 3:40 PM Konrad Weihmann <kweihmann@...> wrote: I would recommend that you go for a systemd drop-in file [1]. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Issue regarding with .wic image
chandra naik <chandumail05@...>
Hi ,
we are a .wic (production image) image for ostree , in these core-image-sato.wic image everything is read only ,
Here when i am trying to edit something it will show file is readonly. so how we can edit a file or service in .wic image ? |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
#yocto #gstreamer #gstreamer1.0-plugins-bad
#yocto
#gstreamer
#aom
#av1
safouane maaloul <maaloulsafouane@...>
Bonjour, j'essaye d'ajouter le aom plugin au niveau de la gstreamer1.0-plugins-bad. J'ai basculé sur gatesgarth version. Je commence à faire lebuild. J'avais un problème de lisence. Je l'ai résolu. Et maintenant j'ai un problème "no such file or directory automake-native yocto" et j'arrive pas à la résoudre ? Est-ce que vous pouvez m'aider ?
Cordialement,
Safouane.Maalou |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Making partitions in .hddimg image
NIKHIL PATIL <nikhilvp29@...>
Hi, For .wic image partiotions ( EFI , OTAROOT ) are already created likewise ; How to create a partiotions in core-image-intel.hddimg image ? in .hddimg only one partition ( boot ) is there . |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: quit-native issue
#yocto
Michael Nazzareno Trimarchi
Hi On Wed, Dec 30, 2020, 7:46 AM sateesh m <sateesh0457@...> wrote: Hi Guys, mktemp -d seems to fail so you could have a broken permission on your temp directory Can you run it manually? Michael |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
quit-native issue
#yocto
sateesh m
Hi Guys,
I am trying to build core-image-sato using dunfell sources. i am facing bug quilt-native configure issue. its present in meta/recipes-devtools. Below i am attaching my issue odt file. can please check it . help me to solve this issue. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What to do when a patch isn't needed?
Paul D. DeRocco
I'm upgrading a project from Pyro to Gatesgarth. Building the toolchain, it
barfs on a patch which isn't needed. Here's one of the error messages: ERROR: binutils-native-2.35-r0 do_patch: Command Error: 'quilt --quiltrc /home/pauld/yocto-gatesgarth/build-intel32/tmp/work/x86_64-linux/binutils-na tive/2.35-r0/recipe-sysroot-native/etc/quiltrc push' exited with 0 Output: Applying patch gas_as.h.patch patching file gas/as.h Hunk #1 FAILED at 486. 1 out of 1 hunk FAILED -- rejects in file gas/as.h Patch gas_as.h.patch can be reverse-applied There are two more just like it, for the cross and target versions. All it is is a patch to add one external function definition, but it's already there. Is there a preferred way to fix this with a bbappend? Perhaps replacing the patch file with an empty one? -- Ciao, Paul D. DeRocco Paul mailto:pderocco@... |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Prevent WIC image from being built?
Robert P. J. Day
On Tue, 29 Dec 2020, Howard wrote:
Yup, thank you Bruce:pedantry, but i'm fairly sure "=" would have sufficed; there was no need to use "+=" here. rday |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Prevent WIC image from being built?
Howard
Yup, thank you Bruce:
Using IMAGE_FSTYPES_remove += "wic" Didn't do it for me, but IMAGE_TYPES_remove += "wic" did the trick. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Help regarding yocto receipe (bluez5)
Konrad Weihmann <kweihmann@...>
I would recommend that you go for a systemd drop-in file [1].
toggle quoted message
Show quoted text
That would be something like a small snippet placed to /etc/systemd/system/dbus-org.bluez.service/override.conf In that file place something like [Service] ExecStart= ExecStart=<new command line with your custom options> this way you don't need to alter the upstream recipe with weird sed hacks or similar. This drop-in file could be packaged by any recipe or bbappend. [1] https://coreos.com/os/docs/latest/using-systemd-drop-in-units.html On 29.12.20 07:48, chandra naik wrote:
Hi |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Help regarding yocto receipe (bluez5)
chandumail05@...
Hi After board boot up , we are editing vi /etc/systemd/system/dbus-org.bluez.service these file as ExecStart=/usr/lib/bluetooth/bluetoothd -C (here we are adding -C means bluetooth running in compact mode). but these is not good practice , so how we can change these service at compiling time itself , any idea ? main agenda is Run bluetoothd daemon in compatibility mode while building yocto image. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Module.symvers failed with error: No such file or directory:
jjvazha@...
Are you able to resolve this issue ? I am seeing the similar issue
p: cannot stat ‘Module.symvers’: No such file or directory WARNING: /home/jojan.vazhaeparampil/workspace/distro/build/tmp/work/cyclone5-poky-linux-gnueabi/linux-altera/5.8+gitAUTOINC+eb446787ab-r0/temp/run.do_shared_workdir.21085:1 exit 1 from 'cp Module.symvers $kerneldir/' |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
M+ & H bugs with Milestone Movements WW52
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Enhancements/Bugs closed WW52!
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Current high bug count owners for Yocto Project 3.3
Stephen Jolley
All,
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Yocto Project Newcomer & Unassigned Bugs - Help Needed
Stephen 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 Also please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi 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 343 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.2”, “3.3, "3.99" and "Future", the more pressing/urgent issues being in "3.2" and then “3.3”.
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.pm@...) 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_Archive#Unassigned_or_Newcomer_Bugs
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Prevent WIC image from being built?
Bruce Ashfield
On Mon, Dec 28, 2020 at 7:12 PM Howard <howard.egan@...> wrote:
If you remove "wic" from the IMAGE_TYPES, it won't be built. https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-IMAGE_TYPES Bruce Many thanks, and Happy New year. -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: How to develop kernel modules on the target?
Bruce Ashfield
On Mon, Dec 28, 2020 at 2:06 PM p32 via lists.yoctoproject.org
<p32=tuta.io@...> wrote: Nope. There is no way to do this on the build host. Not without complex use of qemu-user to generate and package for the target architecture. We cannot package the output of scripts in the target package, since it matches the host architecture and this will trigger a QA error. If you happen to be x86 build host and x86 target (or ARM/ARM), you can partially get away with just invoking the steps .. but this needs to be in your own layer and is a hack, and not appropriate for core. About 4 years ago, we were partially through doing this work, when the person doing the qemu parts stopped working on the project. The partial work is captured in bugzilla. Cheers, Bruce Thanks! -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|