Thanks William. I think I need to backtrack at least 1 step from the files
used. I've been stuck at tftp of 1st stage boot loader (e.g. pxelinux.0, or
grub). If I set it up to use pxelinux.0, on client side, I only saw successful
download of this file, and then it failed due to "Boot option l
Hi Robert
On Thursday, 19 April 2018 6:45:17 PM NZST Robert Yang wrote:
> On 04/19/2018 04:55 AM, Paul Eggleton wrote:
> > On Wednesday, 18 April 2018 11:04:33 PM NZST Robert Yang wrote:
> >> The utils.setup_django() costs a lot of time, but both update.py and
> >> update_layer.py calls it, so mov
On 04/18/2018 05:42 AM, Adrian Dudau wrote:
> On mån, 2018-04-16 at 08:03 -0700, Armin Kuster wrote:
>> I understand some of these changes a harsh. This set of changes allow
>> this layer to pass the
>> yocto-check-layer. This is one of many options to address passing.
>>
> Hi Armin,
>
> Thanks f
On 04/19/2018 10:05 PM, akuster808 wrote:
On 04/19/2018 12:15 AM, wenzong@windriver.com wrote:
From: Wenzong Fan
The systemd-backlight@.service which called after selinux-init.service
will create /var/lib/systemd/backlight with incorrect security labels,
this causes the systemd-backlig
On 2018-04-10 5:31 AM, Mark Junghanns wrote:
Hello Bruce,
unfortunately, there is not a single warning or error message whatsoever thrown. The
first occasion, some error message is thrown, occurs during do_rootfs where it complains
about the missing package "docker" - which is obviously missin
Robert,
I assume no one responded to you because you did not supply enough
information to understand your situation. (You don't specify what HW
you are using, version of Yocto Project, what DHCP server, etc.)
>From the second message I can tell you are using a X86_64 based
platform. Is this a c
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 6:33 PM
On 04/19/2018 09:17 AM, Richard Purdie wrote:
> [Widely cross posted but please reply to openembedded-core only for
> want of picking somewhere to discuss this]
>
> The next big question facing us is what would we like to do in 2.6?
> What can we do with the resources we have?
>
> I'm proposing t
I've yet to receive any response to my post below. I've gone through fair
amount of experimentation to get my board downloaded successfully the
first-stage boot loader. I'd tried pxelinux.0 for legacy BIOS and bootx64.efi
(also generated in build process) to work with UEFI on client side. How
[Widely cross posted but please reply to openembedded-core only for
want of picking somewhere to discuss this]
The next big question facing us is what would we like to do in 2.6?
What can we do with the resources we have?
I'm proposing to hijack the next monthly Yocto Project technical
call[1] an
On 04/19/2018 12:15 AM, wenzong@windriver.com wrote:
> From: Wenzong Fan
>
> The systemd-backlight@.service which called after selinux-init.service
> will create /var/lib/systemd/backlight with incorrect security labels,
> this causes the systemd-backlight service fails to start and stop.
>
From: Wenzong Fan
The systemd-backlight@.service which called after selinux-init.service
will create /var/lib/systemd/backlight with incorrect security labels,
this causes the systemd-backlight service fails to start and stop.
Creating /var/lib/systemd/backlight in advance to make sure it could
12 matches
Mail list logo
