Hi all,
I'm quite new to yocto and currently am playing around with all kinds of basic
functions and procedures of yocto to step by step learn and get to know yocto
and bitbake.
Currently I'm trying to store the kernel config settings in some way in my
layer to have it modular. So I read about
> -Ursprüngliche Nachricht-
> Von: Samuel Stirtzel [mailto:s.stirt...@googlemail.com]
> Gesendet: Freitag, 28. November 2014 11:09
> An: Heise, Matthias
> Cc: yocto@yoctoproject.org
> Betreff: Re: [yocto] do_fetch linux hangs after defconfig/conf-fragment
> change
>
> 2014-11-28 10:29 GM
> -Ursprüngliche Nachricht-
> Von: Samuel Stirtzel [mailto:s.stirt...@googlemail.com]
> Gesendet: Freitag, 28. November 2014 13:55
> An: Heise, Matthias
> Cc: yocto@yoctoproject.org
> Betreff: Re: [yocto] do_fetch linux hangs after defconfig/conf-fragment
> change
>
> 2014-11-28 11:29 GM
> -Ursprüngliche Nachricht-
> Von: Samuel Stirtzel [mailto:s.stirt...@googlemail.com]
> Gesendet: Freitag, 28. November 2014 14:24
> An: Heise, Matthias
> Cc: yocto@yoctoproject.org
> Betreff: Re: [yocto] do_fetch linux hangs after defconfig/conf-fragment
> change
>
> 2014-11-28 14:09 GM
Hi there,
I'm still trying to add a user via recipe. The method with
inherit extrausers
EXTRA_USER_PARAMS = "useradd -p
'\$6\$53uYm/0Fnll\$Nc0RbHSvqRrd63Tw98TO3V1n25ORK9oR4QHqRIriXzLy0il/7.LIacX7mz7RJ1tdPIWiCJLNyQa7dKBNURqEg1'
fstuser;"
Does not work (no errors just no user in image), as well
Hi ChenQui,
thanks very much for your reply, the ROOTFS_POSTPROCESS_COMMAND does work now
with
"useradd -root ${IMAGE_ROOTFS} -p . " as you suggested
However with the EXTRA_USERS_PARAMS the user is now added (thanks to the
removed typo) but I can't add a valid password, neither encrypted no
Ok, the EXTRA_USERS_PARAMS method now also works, it was the typo with USER and
USERS and an encrypted password with ' ' around it which is needed, strangely
the encrypted string for one and the same password all of a sudden was
different, after re-generating it, it worked
Von: yocto-boun...@y
Hi all,
I'm aware of the fact, that this is probably not the right point to ask, but
maybe you still can give me some hints and/or point me to the right place to
ask.
What I would like to do is to connect a certain interface-chip to the
freescale imx6. I have a wandboard which doesn't use it,
Hi all,
I'm still trying to find out basic things about getting a system up and
running. This question is about U-Boot, is it right that for example for my
wandboard a pre-compiled *.imx is just downloaded ?
So if I want to make settings to U-Boot I make them directly in the source,
compile it
Even if this is a stupid question a little advise would be nice ... like "don't
ask so stupid questions, go read this and that" or something... no time ?
Should I rather unsubscribe from this list until I'm an expert?
Von: Heise, Matthias
Gesendet: Mittwoch, 3. Dezember 2014 15:15
An: 'yocto@yoc
Hello Matt,
thanks very much for your reply, I was able to create a simple patch changing
an u-boot setting as test and "bbappended" it. I just didn't believe before
that the various u-boot settings are "hard-coded" but they obviously are in the
".h", so patching it seems to be the only way for
> -Ursprüngliche Nachricht-
> Von: yocto-boun...@yoctoproject.org [mailto:yocto-
> boun...@yoctoproject.org] Im Auftrag von Gary Thomas
> Gesendet: Freitag, 5. Dezember 2014 15:22
> An: yocto@yoctoproject.org
> Betreff: Re: [yocto] u-boot precompiled ?
>
> On 2014-12-05 05:48, matthias.h
Hello,
I'm struggling getting my wandboard booting via tftp/nfs.
The first part was easy I just set up the tftp server and pointed it to the
kernel image and *.dtb file,
in the wandboard.h of u-boot I set
#define CONFIG_BOOTCOMMAND \
"run netboot;"
The kernel star
Hello Jim,
thank you for your reply, yes in the meantime I found out why that nfsroot path
isn't set correctly, there is a wrong line in the "wandboard.h" in u-boot.
Now the regarding line looks like this
Kernel command line: console=ttymxc0,115200 root=/dev/nfs ip=dhcp
nfsroot=192.168.1.1:/home/
Update :
1. I added a "rw" obviously at the right place as the nfs filesystem
isn't marked as read-only anymore. Still there obviously is some write/rights
issue as I get a lot of permission-related logs. (see below)
2. About the rootfs : I tried the unpacked filesystem from the *.
Hi Anders,
> -Ursprüngliche Nachricht-
> Von: Anders Darander [mailto:and...@chargestorm.se]
> Gesendet: Mittwoch, 10. Dezember 2014 11:24
> An: Heise, Matthias
> Cc: j...@spectralogic.com; yocto@yoctoproject.org
> Betreff: Re: [yocto] nfs-boot problem
>
> * matthias.he...@atlas-elektroni
> -Ursprüngliche Nachricht-
> Von: Anders Darander [mailto:and...@chargestorm.se]
> Gesendet: Mittwoch, 10. Dezember 2014 12:17
> An: Heise, Matthias
> Cc: j...@spectralogic.com; yocto@yoctoproject.org
> Betreff: Re: [yocto] nfs-boot problem
>
> * matthias.he...@atlas-elektronik.com ele
Hi,
I'm not able to pull any sources for a little time now. As test I re-tried an
already working setup by again following some tutorial and trying to setup a
fresh repo. The repo init works but the sync fails. I should mention that due
to network limitations I replace git:// urls with https://
Hello Saul,
thanks for your reply, I'm running the "repo init" command as in many
tutorials, this is the line :
repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b dizzy
after the init I find following in the manifest.xml :
Hi Anders,
yes, in my git config I replace git:// with https:// I'm forced to do so as git
doesn't go through the company network. If I change the url in the manifest.xml
to
https://git.yoctoproject.org/git/poky/ it works on that part but I didn't find
out yet how the other links should look l
20 matches
Mail list logo
