On Tue, 2023-08-08 at 12:13 -0400, Bruce Ashfield wrote:
> On Tue, Aug 8, 2023 at 11:35 AM Chen Qi via lists.openembedded.org
> wrote:
> >
> > I found some clue, but not the root cause yet.
> > The eth0 is renamed to enp0s2 by 80-net-setup-link.rules udev rule in
> > systemd. And the
server
when upgrading to a "newer" 6.2 kernel,
I had to disable interface renaming in order to get a consistent
network configuration, and did that via "net.ifnames=0" on the kernel
command line.
Bruce
>
> Regards,
> Qi
>
>
> -----Original Message-----
> From
On 2023-08-08 17:34, Chen Qi via lists.openembedded.org wrote:
Maybe some changes in new kernel allows renaming network interface while it's
up?
Seems correct!
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit?id=bd039b5ea2a91ea707ee8539df26456bd5be80af
That was added
network interface while it's
up?
Regards,
Qi
-Original Message-
From: openembedded-core@lists.openembedded.org
On Behalf Of Richard Purdie
Sent: Tuesday, August 8, 2023 7:51 PM
To: openembedded-core
Cc: Luca Boccassi ; Alexandre Belloni
Subject: [OE-core] systemd issue with network commandline confi
Hi,
We'd like to switch to the 6.4 kernel and there are two blockers. One
of them is that systemd appears to be breaking the network device
config with 6.4 kernels.
This happens with core-image-sato but not with core-image-minimal.
In the sato image, I can see the kernel gets the ip=
