It looks like in langdale/master do_start() was stripped of essential functionality [1] [1] https://git.yoctoproject.org/poky/tree/meta/recipes-connectivity/connman/connman/connman?h=langdale In kirkstone this functionality is still there[2] [2] https://git.yoctoproject.org/poky/tree/meta/recipes-connectivity/connman/connman/connman?h=kirkstone --> nfsroot=0 exec 9<&0 < /proc/mounts while read dev mtpt fstype rest; do if test $mtpt = "/" ; then case $fstype in nfs | nfs4) nfsroot=1 break ;; *) ;; esac fi done do_start() { if test $nfsroot -eq 1 ; then NET_DEVS=`cat /proc/net/dev | sed -ne 's/^\([a-zA-Z0-9 ]*\):.*$/\1/p'` NET_ADDR=`cat /proc/cmdline | sed -ne 's/^.*ip=\([^ :]*\).*$/\1/p'` if [ ! -z "$NET_ADDR" ]; then if [ "$NET_ADDR" = dhcp ]; then ethn=`ifconfig | grep "^eth" | sed -e "s/\(eth[0-9]\)\(.*\)/\1/"` if [ ! -z "$ethn" ]; then EXTRA_PARAM="$EXTRA_PARAM -I $ethn" fi else for i in $NET_DEVS; do ADDR=`ifconfig $i | sed 's/addr://g' | sed -ne 's/^.*inet \([0-9.]*\) .*$/\1/p'` if [ "$NET_ADDR" = "$ADDR" ]; then EXTRA_PARAM="$EXTRA_PARAM -I $i" break fi done fi fi fi if [ -f @DATADIR@/connman/wired-setup ] ; then . @DATADIR@/connman/wired-setup fi $DAEMON $EXTRA_PARAM } <-- Without this extra checks connman needs to be disabled if you boot with a rootfs over nfs, so I suggest to add it back in.
Zheng's co-op term is over so moving to unassigned.
Bulk move of 64 bugs to 4.3 M3 after a quick review. If a bug is actually fixed, please add a commit link and resolve it. -- Randy for YP bug team.
Moved to M4.
Would it be worth a thought to replace conman with NetworkManager? Basically move conman to meta-oe and NetworkManager to poky? I haven't compared the two in their current versions, but there is probably a lot more activity on the NetworkManager side than the conman side.
Bulk move to 5.0 M1. -- Randy
Bulk move of 52 5.0-M1 bugs to M2.
Bulk move of bugs owned by "unassigned" from 5.0-M2 to 5.0-M3.
Bulk move of bugs from 5.0-M3 to 5.99. The bugs in this list are all unassigned and are ones that I consider to be nice to do some time but not essential track from milestone to milestone in 5.0 or 5.1. We agreed on this bug handling approach in the YP bug review on Feb 22, 2024. If you disagree, please move back to a 5.[012...]-M* milestone.
Is the reproducible on current oe-core/master ?