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
Refer to my post here
https://lists.yoctoproject.org/pipermail/yocto/2018-April/040860.html
Don't use initramfs/initrd as it not working.
Regards,
Alim Hussin
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Raymond Yeung
Sent: Thursday, April 26, 2018
Can you elaborate little more.
On Thu, Apr 26, 2018 at 12:24 PM, Nishina A. Pervin <
nishina.per...@nestgroup.net> wrote:
> Hi
>
>
>
>
>
> I am using yocto Krogoth build for imx6q Sabreauto board.
>
>
>
> What is the rate at which data is read from SD card? Can we configure it
> for higher spe
Hi Sir ,
We are using weston (1.9.0) for loading our application on IMx6Q sabreauto
board.
sometimes it fails to start and sometime it works after reboot or after restart
Weston services.
I found that there is some synchronisation issue occurred in loading western
service at the boot time.
A lo
Hi,
I am building an image using rocko branch and installing ifupdown package:
http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-core/ifupdown/ifupdown_0.8.16.bb?h=rocko
If there is no loopback definition in /etc/network/interfaces file, then
"ifup -a" brings lo interface up a
Hello forum.
I have two questions related with the generation of images when the distro
is configured to use a repository of rpm packages signed with gpg.
First question: after running the "bitbake my-image.bb" command, the build
process stops with this message of error:
ERROR: myimage-1.0-r0 do
On 25/04/18, Andre McCurdy wrote:
> On Wed, Apr 25, 2018 at 8:03 AM, Oliver Graute
> wrote:
> > Hello list,
> >
> > I try to compile yocto jethro environment which is working
> > on a Ubuntu 14.04 installation. But not on a Kubuntu 16.04.
> >
> > The compilations stops on gettext-native.
> >
> >
> I deleted all the build-imx6ulevk folder and build everything from
> scratch with only one thread, waited a few hours for compilation and now
> its working ;)
Still, I am struggling to understand why??? What is the requirement
behind this ask?
As we see, it is much longer (one thread only) than
Hello Folks,
I am trying to integrate an SDK which is very simple and small. Building the
SDK generates an executable and few .so libraries.
“bitbake sdk” command goes through fine but when I run “bitbake
wrlinux-image-glibc-std” to generate an ISO with SDK packages I am get
following error
On Thu, Apr 26, 2018 at 11:03 AM, Shakthi Pradeep (tpradeep)
wrote:
> Hello Folks,
>
> I am trying to integrate an SDK which is very simple and small. Building the
> SDK generates an executable and few .so libraries.
>
> “bitbake sdk” command goes through fine but when I run “bitbake
> wrlinux-ima
Thanks for the info Andre. What you are suggesting it to be done while building
an application over these libraries right?
Any idea why the packaging is failing?
Regards,
Shakthi
On 27/04/18, 12:00 AM, "Andre McCurdy" wrote:
On Thu, Apr 26, 2018 at 11:03 AM, Shakthi Pradeep (tpradeep)
> A log file (/var/log/weston.log)is mentioned in the western-start script file
> .
Western or Weston? I never saw anything as western, considering GFX
(you mentioned western twice)?! Probably you meant Weston.
Weston is Wayland backend, actually, Wayland is more of a GFX
communication protocol,
On Thu, Apr 26, 2018 at 11:36 AM, Shakthi Pradeep (tpradeep)
wrote:
> Thanks for the info Andre. What you are suggesting it to be done while
> building an application over these libraries right?
No. The soname needs to be set when the library is linked.
> Any idea why the packaging is failing?
Follow-up to my previous post, after seeing the reply below suggesting me not
to use initramfs (but initrd is usable, right?). BTW, I don't use bootx64.efi.
Instead, I use pxelinux.0 along with the other lib***.c32 files.
1. Is there a way to verify if GRUB (that I'm using) supports networ
You are using PXE with legacy BIOS as you use pxelinux.0 . To configure PXE
with legacy BIOS follow these instruction
Note: PXE server IP = 192.168.1.2
Target IP = 192.168.1.1
On PXE server
1. make sure DHCP, NFS & TFTP services are up and running.
2. change the filename "pxelinux.0
Thanks a lot Alim for the detail step-by-step, for both modes. I'd like to
stay with legacy mode with pxelinux.0 for now. I'm doing pretty much the same
as what you described below, with exceptions -
1. I'm not using vesamenu.c32. Instead menu.32 is used, though I don't
think that would
On 26/04/18, Zoran Stojsavljevic wrote:
> > I deleted all the build-imx6ulevk folder and build everything from
> > scratch with only one thread, waited a few hours for compilation and now
> > its working ;)
>
> Still, I am struggling to understand why??? What is the requirement
> behind this ask?
17 matches
Mail list logo
