From: Ivan Vecera <ivecera@redhat.com>
To: Julia Lawall <julia.lawall@inria.fr>
Cc: "David S. Miller" <davem@davemloft.net>, linux-kernel@vger.kernel.org
Subject: Re: Failed to start Raise network interfaces error
Date: Tue, 12 Dec 2023 16:45:46 +0100 [thread overview]
Message-ID: <a79a13b9-b4d1-45ba-a104-01e911631863@redhat.com> (raw)
In-Reply-To: <d87c79b9-d0d2-2819-030-12c7df86eb38@inria.fr>
On 12. 12. 23 16:08, Julia Lawall wrote:
>
>
> On Tue, 12 Dec 2023, Ivan Vecera wrote:
>
>> On 10. 12. 23 23:28, Julia Lawall wrote:
>>> Hello,
>>>
>>> Starting with the commit:
>>>
>>> commit 9e479d64dc58f11792f638ea2e8eff3304edaabf
>>> Author: Ivan Vecera <ivecera@redhat.com>
>>> Date: Fri Oct 13 19:07:51 2023 +0200
>>>
>>> i40e: Add initial devlink support
>>>
>>> I am not able to boot normally. The console shows the message
>>>
>>> Failed to start Raise network interfaces
>>>
>>> Searching for this message on th internet produces some old discussions
>>> that suggest to look at the file /etc/network/interfaces. That file on my
>>> system contains:
>>>
>>> # This file describes the network interfaces available on your system
>>> # and how to activate them. For more information, see interfaces(5).
>>>
>>> source /etc/network/interfaces.d/*
>>>
>>> # The loopback network interface
>>> auto lo
>>> iface lo inet loopback
>>>
>>> auto enp24s0f0
>>> iface enp24s0f0 inet dhcp
>>
>> The problem is maybe with interface name... after this commit the interface
>> should contain port_name suffix. In your case the name should be
>> `enp24s0f0np0`.
>>
>> Could you please check it?
>
> Thanks for the feedback. But I'm not clear on how this would work. Does
> there have to be one name for kernels before this patch and another name
> for kernels starting with this patch? Or is the new name also acceptable
> for older kernels?
The name of a network interface is configured by udev. And it takes
network interface attributes and compose a name for it. One of these
attributes is phys_port_name [1] and if it is provided then its value is
appended to the name.
Prior this commit the i40e driver didn't provided this attribute so the
name is (in your case) enp24s0f0. After this commit the value is
provided so it is appended -> enp24s0f0np0
Look at 'systemd.net-naming-scheme' man page for details how the
interface names are composed.
Thanks,
Ivan
[1] /sys/class/net/enp2s0f0np0/phys_port_name
next prev parent reply other threads:[~2023-12-12 15:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 22:28 Failed to start Raise network interfaces error Julia Lawall
2023-12-12 14:44 ` Julia Lawall
2023-12-12 14:52 ` Ivan Vecera
2023-12-12 15:08 ` Julia Lawall
2023-12-12 15:45 ` Ivan Vecera [this message]
2023-12-12 15:48 ` Julia Lawall
2023-12-12 16:33 ` Julia Lawall
2023-12-12 16:44 ` Ivan Vecera
2023-12-12 16:53 ` Julia Lawall
2023-12-14 14:33 ` Julia Lawall
2023-12-14 14:47 ` Ivan Vecera
2023-12-14 14:50 ` Julia Lawall
2023-12-14 20:55 ` Lucas Nussbaum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a79a13b9-b4d1-45ba-a104-01e911631863@redhat.com \
--to=ivecera@redhat.com \
--cc=davem@davemloft.net \
--cc=julia.lawall@inria.fr \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox