From: Gang Yan <gang_yan@foxmail.com>
To: "David S. Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Inquiry Regarding PXE Installation Issue with Network Driver Configuration
Date: Thu, 31 Oct 2024 15:58:49 +0800 [thread overview]
Message-ID: <tencent_99262A4B390D43E22441268D3D8CC0AF2E05@qq.com> (raw)
Dear Maintainers:
I am writing to seek your expertise regarding an issue I have encountered
recently while using PXE (Preboot Execution Environment) for system
installation.
Specifically, the problem arises when the PXE network card driver is
compiled as a kernel module (.ko file). During the installation process,
the kernel gets stuck in the 'ip_auto_config' stage, waiting for the network
interface to become ready, displaying the message "Waiting up to xx more
seconds for network." However, it appears that the system does not proceed
to the ramdisk stage to load the .ko driver, ultimately leading to a failed
installation.
Based on my analysis, it seems that for a successful PXE installation,
the corresponding network card driver must be compiled directly into the
kernel rather than as a loadable module. I would like to confirm if my
understanding is correct. If so, would it be necessary to adjust the
relevant code? Because it is not suitable to compile too much ehernet drivers into vmlinux.
Best regards,
Gang Yan
reply other threads:[~2024-10-31 8:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=tencent_99262A4B390D43E22441268D3D8CC0AF2E05@qq.com \
--to=gang_yan@foxmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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
all inboxes | Powered by JetHome®