Let's say I've a working run-time system running 2016 April release (Krogoth)
Poky image. I've it installed previously from a USB thumb drive onto a much
bigger SSD with all partitions setup. I don't need to change the partition
from here onward.
Is there an easy way to replace it with, say 2
ted in the following path:
tmp/work/intel_corei7_64-poky-linux/core-image-sato/1.0-r0/rootfs/lib/modules/4.4.26-yocto-standard/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
Thanks,
Raymond
From: Kosta Zertsekel
Sent: Saturday, October 13, 2018 2:01 AM
To:
I've a Intel Ethernet driver, ixgbe.ko. I made some changes (debug logs) to
the source file. How do I force the .ko to be regenerated within yocto
environment, without rebuilding the entire yocto code base?
I tried to do bitbake of the image name earlier, but bitbake decides that
there's noth
ut of this image to multiple
partitions. The reason I'm thinking this way is that our real H/W (vs. the
evaluation platform I've been using) doesn't support USB port, thus no run-time
installer.
From: Burton, Ross
Sent: Monday, July 9, 2018 2:0
July 9, 2018 7:31 AM
To: Raymond Yeung
Cc: Burton, Ross; yocto@yoctoproject.org
Subject: Re: [yocto] How to remove openssl from sysroots
Just fix the build issue. Look into how opensslconf.h gets created and where
the -32 suffix comes from and why the included file is absent.
Seriously - that is
+ yocto mailing list.
From: Raymond Yeung
Sent: Sunday, July 8, 2018 5:31 PM
To: Burton, Ross
Subject: Re: [yocto] How to remove openssl from sysroots
We're not going to integrate everything into one homogeneous package. Poky and
BSP would be together.
dd one or more partitions to
it as well.
From: Burton, Ross
Sent: Saturday, July 7, 2018 3:39 PM
To: Raymond Yeung
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Any Linux/Yocto Image Installer (for target system)
The easiest thing would be to edit the installer script that g
ymond
From: Burton, Ross
Sent: Saturday, July 7, 2018 3:41 PM
To: Raymond Yeung
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] How to remove openssl from sysroots
Presumably you've a recipe for the vendor openssl. If it has the same
name but is a different version the
l" instead of "base" or "sato" cannot exclude it.
Any idea [e.g. how do we systematically find out how it's included now, and
possibly what other packages/recipes we may also need to remove due to
dependency]?
Thanks,
Raymond
____
F
image, I have this USB device
removed first, so SSD should come up as /dev/sda. Yet, boot fails, with a
blank screen.
Any idea what might have gone wrong?
________
From: Raymond Yeung
Sent: Friday, July 6, 2018 2:52 PM
To: yocto@yoctoproject.org
Subject: Any Linux/Yoc
Is there any installer that I could download along with the .hddimg (or .iso)
image to the RAM, invoke the installer, so we could have a bootable image
installed on a SSD?
History:
I can already create USB live image with dd and .hddimg. I could also dd the
.hddimg onto SSD and make it boota
We've our own non-yocto openssl that we want to use. At the moment, we're
using "sato" image, rather than "minimal" and includes its openssl that is
out-of-date. What is the best way to exclude it from our image (and from
sysroots)?
We have thought about two ideas -
1. Use smaller image
Our project currently uses Krogoth 2.1. It's a mid-2016 release. I'm looking
into logistic of upgrading to Rocko 2.4 (a late-2017 release).
Is it possible to keep the toolchain in Krogoth 2.1 revisions, while migrating
the sources to Rocko 2.4 revisions? Has anyone done that?
Upgrading toolc
e git://git.yoctoproject.org/linux-yocto-contrib
And so I did the clone. However, I'm unable to find the file after all. Am I
on the right track? And how do I check history to see perhaps it was removed
later?
Thanks,
Raymond
____
From: Raymond Yeung
Sent: Tu
elved this NFS
approach. If you get this working, would appreciate it if you could publish
it, and any issues you run into implementing it.
Raymond
From: Vincent Daanen
Sent: Thursday, May 3, 2018 11:43 PM
To: Raymond Yeung; yocto@yoctoproject.org
Subject:
Hi Vincent,
I'd recently gone through similar issue that you're experiencing. The "Waiting
for Removable Media" hang had been there for at least 7-8 years. A workaround
was put in around 2013. See here:
https://patchwork.openembedded.org/patch/42291/
Add "debugshell=30" (30 is in second,
_
From: Zoran Stojsavljevic
Sent: Tuesday, May 1, 2018 11:19 PM
To: Raymond Yeung
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Problem with Python when running oe-init-build-env
Hello Raymond,
The problem is that you (talking about your host distro):
[1] Do NOT have p
What is the best way to search for existing driver support (in particular,
driver for TLK10031) in YP? I search my own Poky source and its build tree,
but find nothing. I saw on google returned result mentioning of one instance
for a similar chip (TLK10232), but don't know which branch/repo it
I'd just git cloned Rocko and meta-ti. When I try to source oe-init-build-env,
I got errors:
-bash: python3: command not found
BitBake requires Python 3.4.0 or later as 'python3'. "python -V" gives "Python
2.7.9". "python3" is not in $PATH. I'd followed some detailed online
description to
I use Krogoth (released 4/2016) Camelback Mountain BSP, trying to do network
boot. Initialization hangs indefinitely with "Waiting for Removable Media".
This is a big issue for us, because we need to deal with the diskless situation.
It looks like this issue was here some 7-8 years ago. It w
I'd proceed to investigate the other
issue - why my kernel initialization would need to wait for any "removable
media" indefinitely, and see if I could fix/change this.
Thanks,
Raymond
From: Hussin, Mohamad Noor Alim
Sent: Thursday, April 26, 2018
build (and what yocto tool to use, if any) in order
to get my network driver part of kernel, instead of being a LKM that isn't
there when I need it for NFS boot?
From: Hussin, Mohamad Noor Alim
Sent: Thursday, April 26, 2018 12:26 AM
To: Raymond Yeung; yo
I've an Intel Xeon-D board. I could boot up the board with PXE booting.
However, this seems to be always looking for "removable media"; if there is
none, it would hang (in a .sh file). I want to explore NFS approach. So far,
I've read up, experimented on NFS setup via pxelinux.cfg/default fi
Thanks for all who extended helping hands. I finally resolved my issues, and
the target PXE-boot'ed up. I'd like to provide some updates, for reference to
someone that may run into this in the future.
I'm able to use legacy mode (in BIOS) instead of UEFI mode. While I haven't
worked out the
tx64.efi";
vendor-option-space PXE;
option PXE.discovery-control 11;
}
Thanks,
Raymond
________
From: William Mills
Sent: Thursday, April 19, 2018 1:56 PM
To: Raymond Yeung; yocto@yoctoproject.org
Subject: Re: [yocto] Linux Files needed for PXE network b
Another thing I haven't tried is to set up NFS. Can we simply specify ONE file
(similar to .hddimg) that could be tftp over to target, and expect it to boot
up? Could this be the cause of my problem?
From: Raymond Yeung
Sent: Wednesday, April 18, 2018
inux.0, I got
"PXE-E16: No offer received. ERROR: Boot option loading failed".
Any idea anyone?
From: Raymond Yeung
Sent: Monday, April 16, 2018 12:42 PM
To: yocto@yoctoproject.org
Subject: Linux Files needed for PXE network boot
I've a .hddim
I've a .hddimg image bootable from USB thumb drive. As part of the boot-up, I
also could invoke "Serial Install" to transfer such an image to SSD, such that
in the next round, I could boot from SSD instead.
What are the files and where do I get them (relative to where I find .hddimg)
from the
_
From: Mohammad, Jamal M
Sent: Tuesday, April 10, 2018 9:48 PM
To: Raymond Yeung; yocto@yoctoproject.org
Subject: RE: Yocto Boot Question
I also faced a similar issue while installing on Intel machine, switching to
other machine I was able to install and boot successfully
se for the source and the destination
to prepare for the root filesystem. Any tip/help?
From: Mohammad, Jamal M
Sent: Monday, April 9, 2018 9:04 PM
To: Raymond Yeung; yocto@yoctoproject.org
Subject: RE: MACHINE .conf file
Did you add meta-intel lay
Hi,
I've successfully booted a BSP using USB thumb drive (.hddimg type). I've two
follow-up questions -
1. The BIOS offers "Serial Install" which seems to copy the USB boot image
over to SSD. Would SSD be using the same .hddimg type? Right now, after the
above install, when I switch bo
Some questions about MACHINE:
1. I'd customized MACHINE (="intel-corei7-64") variable in conf/local.conf
under my build directory, as per document, and had successfully generated an
image for my H/W. However, I don't seem to find "intel-corei7-64.conf" file in
meta/conf/machine under poky sour
Want to comment on this part of an earlier reply from Anuj:
"Use EXTRA_OEMAKE += "='${STAGING_KERNEL_DIR}'" if the variable
name used in your Makefile is different from KERNEL_PATH or KERNEL_SRC."
A "bitbake -e " confirms that EXTRA_OEMAKE is already setup to use
KERNEL_SRC. And I'd manually m
I suppose, as a possible final solution, I could do:
$(CC) --sysroot=$(KERNEL_SRC) ...
I'm really looking for simpler, more intuitive solution. What about the
missing "-m64 -march=corei7 -mtune=corei7 -mfpmath=sse -msse4.2" in the export?
Raymond
_________
ges to original vendor files)?
Thanks,
Raymond
From: Anuj Mittal
Sent: Thursday, April 5, 2018 11:39 PM
To: Raymond Yeung; yocto@yoctoproject.org
Subject: Re: [yocto] Adding debug output in recipe
On 04/06/2018 02:05 PM, Raymond Yeung wrote:
> Hi Anuj,
>
>
From: Robert Berger
Sent: Thursday, April 5, 2018 11:48 AM
To: Raymond Yeung
Cc: Khem Raj; yocto@yoctoproject.org
Subject: Re: [yocto] Problem with packages during "devtool build"
Hi,
On 2018-04-05 21:02, Raymond Yeung wrote:
> "inherit module" is already in recipes/cgosapi.bb
I've some 3rd party Makefile-based software I'd like to integrate to a working
Poky snapshot. The following are done:
1. devtool add cgosapi
2. Edit workspace/recipe/cgosapi/cgosapi.bb.
* Implement do_install to move files on build machine to directories on
target.
* Files
Is there a way to add simple debug output (ideally don't need to control debug
level) to echo out values of variables? I tried the bb.xxx variants, but
couldn't get them to work.
Raymond
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists
I figured out a way out of my do_compile problem in my last post.
By accident, I stumbled on "bitbake -e virtual/kernel" command in one of the
many manuals. Executing this in directory where belayer.conf is defined would
give me all the expanded values of all variables.
Some of these variabl
ot;
inherit module
EXTRA_OEMAKE_append_task-install = " -C ${STAGING_KERNEL_DIR} M=${S}"
KERNELDIR = "${KERNEL_SRC}"
________
From: Khem Raj
Sent: Thursday, April 5, 2018 9:56 AM
To: Raymond Yeung
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] P
Resent, after subscribing to the list.
From: Raymond Yeung
Sent: Wednesday, April 4, 2018 6:40 PM
To: yocto@yoctoproject.org
Subject: Problem with packages during "devtool build"
I've some 3rd party Makefile-based software I'd like to in
41 matches
Mail list logo
