Hello Peter, > I'm not sure I got your question correct but I'll try to give you *a super* > *simple *network config for systemd-networkd using dhcp.
*Super simple answer.* From my previous answer (from log provided): [11982.445947] net eth0: initializing cpsw version 1.12 (0) [11982.550762] SMSC LAN8710/LAN8720 4a101000.mdio:00: attached PHY driver [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=4a101000.mdio:00, irq=POLL) Listening on LPF/eth0/64:cf:d9:ff:67:05 Sending on LPF/eth0/64:cf:d9:ff:67:05 Sending on Socket/fallback *DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7[11984.640851] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control offDHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10DHCPOFFER of 192.168.15.95 from 192.168.15.2DHCPREQUEST for 192.168.15.95 on eth0 to 255.255.255.255 port 67DHCPACK of 192.168.15.95 from 192.168.15.2* suspect value in domain_name option - discarded chown: unrecognized option '--reference=/etc/resolv.conf' BusyBox v1.29.2 (2019-01-19 17:24:17 UTC) multi-call binary. Best Regards, Zoran _______ On Tue, Jan 22, 2019 at 10:08 PM Peter Bergin <pe...@berginkonsult.se> wrote: > Hi Zoran, > > I'm not sure I got your question correct but I'll try to give you a super > simple network config for systemd-networkd using dhcp. > > Add the file '/etc/systemd/network/10-dhcp.network' with the following > content: > > [Match] > Name=* > > [Network] > DHCP=yes > > Then I hope you will get your interface up with DHCP. > > Regards, > /Peter > > > > On 2019-01-22 17:45, Nicolas Dechesne wrote: > > On Tue, Jan 22, 2019 at 5:38 PM Zoran > Stojsavljevic<zoran.stojsavlje...@gmail.com> <zoran.stojsavlje...@gmail.com> > wrote: > > Hello Nicolas, > > I build ONLY initramfs to be used on BBB DUT in order to test VMs. I > do not use mtd neither flash rootfs (as mounted on flash), although in > the BBB DUT's flash I have embedded Debian stretch. I use different > ash scripts in U-Boot to bring only ramboot. > > Here is the proof: > root@beaglebone:~# df > Filesystem 1K-blocks Used Available Use% Mounted on > devtmpfs 213596 0 213596 0% /dev > tmpfs 251260 0 251260 0% /dev/shm > tmpfs 251260 8428 242832 3% /run > tmpfs 251260 0 251260 0% /sys/fs/cgroup > tmpfs 251260 0 251260 0% /tmp > tmpfs 251260 116 251144 0% /var/volatile > > But this email thread, my best guess, addresses your > concerns:https://lists.yoctoproject.org/pipermail/yocto/2018-July/041680.html > > There is also how to build image with initramfs ONLY, in this thread, > written by > me:https://lists.yoctoproject.org/pipermail/yocto/2018-July/041696.html > > thanks, that exactly what I was looking for. > > > I hope this helps. > > Zoran > _______ > > > On Tue, Jan 22, 2019 at 4:49 PM Nicolas Dechesne<nicolas.deche...@linaro.org> > <nicolas.deche...@linaro.org> wrote: > > hi, > > On Tue, Jan 22, 2019 at 4:42 PM Zoran > Stojsavljevic<zoran.stojsavlje...@gmail.com> <zoran.stojsavlje...@gmail.com> > wrote: > > Hello Lukasz, > > Thank you very much for the advises. I did what you have suggested, and this > does work. > > And it solves my basic problem (NO GO for some reason when I had network > manager). > > I use DUT (BBB) with YOCTO initramfs linux as testing vehicle for my various > pass-through VBox VMs (several designs) via my notebook host to test them, > how different designs VMs connect and interact with DUT. > > can you share how you built your initramfs? Are you saying that you > are booting an initramfs which then mounts the rootfs where you have > core-image-minimal? > > > Lukasz and Peter, > > I also will investigate more about systemd service in order to get more > inside info about how to properly configure the service. > > Thank you, > Zoran > _______ > > Here is the transcript after I built new YOCTO BBB DUT initramfs build: > > root@beaglebone:~# uname -a > Linux beaglebone 4.19.7-jumpnow #1 Tue Jan 22 10:36:57 UTC 2019 armv7l > GNU/Linux > root@beaglebone:~# systemctl restart systemd-networkd > root@beaglebone:~# ps -elf | grep dhc > 0 S root 1521 1328 0 80 0 - 745 pipe_w 19:14 ttyO0 00:00:00 > grep dhc > root@beaglebone:~# ifconfig eth0 down > root@beaglebone:~# dhclient -4 eth0 -v > Internet Systems Consortium DHCP Client 4.4.1 > Copyright 2004-2018 Internet Systems Consortium. > All rights reserved. > For info, please visit https://www.isc.org/software/dhcp/ > > [11982.445947] net eth0: initializing cpsw version 1.12 (0) > [11982.550762] SMSC LAN8710/LAN8720 4a101000.mdio:00: attached PHY driver > [SMSC LAN8710/LAN8720] (mii_bus:phy_addr=4a101000.mdio:00, irq=POLL) > Listening on LPF/eth0/64:cf:d9:ff:67:05 > Sending on LPF/eth0/64:cf:d9:ff:67:05 > Sending on Socket/fallback > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 > [11984.640851] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow > control off > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 > DHCPOFFER of 192.168.15.95 from 192.168.15.2 > DHCPREQUEST for 192.168.15.95 on eth0 to 255.255.255.255 port 67 > DHCPACK of 192.168.15.95 from 192.168.15.2 > suspect value in domain_name option - discarded > chown: unrecognized option '--reference=/etc/resolv.conf' > BusyBox v1.29.2 (2019-01-19 17:24:17 UTC) multi-call binary. > > Usage: chown [-Rh]... USER[:[GRP]] FILE... > chmod: unrecognized option '--reference=/etc/resolv.conf' > BusyBox v1.29.2 (2019-01-19 17:24:17 UTC) multi-call binary. > > Usage: chmod [-R] MODE[,MODE]... FILE... > bound to 192.168.15.95 -- renewal in 40023 seconds. > root@beaglebone:~# > > On Mon, Jan 21, 2019 at 9:07 AM Lukasz Zemla <lukasz.ze...@woodward.com> > <lukasz.ze...@woodward.com> wrote: > > From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org > <yocto-boun...@yoctoproject.org>] On Behalf Of Zoran Stojsavljevic > Sent: Monday, January 21, 2019 7:56 AM > > [...] > > > While downloading initramfs on the target system, while bringing kernel up, > the following > happened (actual log): > [ 0.000000] Kernel command line: console=ttyO0,115200n8 root=/dev/ram0 > ip=dhcp > ... [snap]... > [ 114.064032] Sending DHCP requests ...... timed out! > [ 190.652571] IP-Config: Auto-configuration of network failed > [ 190.663158] Freeing unused kernel memory: 1024K > [ 190.668661] Run /init as init process > System time before build time, advancing clock. > Failed to mount tmpfs at /sys/fs/cgroup: No such file or directory > Failed to mount cgroup at /sys/fs/cgroup/systemd: No such file or directory > [!!!!!!] Failed to mount API filesystems, freezing. > Freezing execution. > [ 192.984442] random: crng init done > I have two questions (please, could you provide to me some help here): > [1] How to fix this run-time bug (what I should do in the configuration)? > I found some interesting explanation about possible solution > (PACKAGECONFIG): > https://lists.yoctoproject.org/pipermail/yocto/2013-November/016965.html > > Probably you are missing CONFIG_CGROUPS in your kernel configuration. > Please read README file in the systemd sources folder - it describes all > options > required to be enabled in kernel configuration. > > > [2] I would like also to include networkctl service (should I do something > specific to > enable it, or this is done by default enabling systemd)? > > Please add following to your conf/local.conf file: > PACKAGECONFIG_append_pn-systemd = " networkd" > > Best regards, > Lukasz Zemla > > *** > The information in this email is confidential and intended solely for the > individual or entity to whom it is addressed. If you have received this > email in error please notify the sender by return e-mail, delete this email, > and refrain from any disclosure or action based on the information. > *** > > -- > _______________________________________________ > yocto mailing > listyocto@yoctoproject.orghttps://lists.yoctoproject.org/listinfo/yocto > > >
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
