From: geoff@collyer.net
To: 9fans@cse.psu.edu, geoff@collyer.net
Subject: [9fans] booting & igbe
Date: Tue, 17 Aug 2004 01:04:13 -0700 [thread overview]
Message-ID: <2e44aa9ac8b270827a30c09349cc4a35@collyer.net> (raw)
(9fans is constipated tonight, so my messages will probably all arrive
at once.)
The builtin-PXE booting on the Intel gigabit Ethernet cards is nice.
Unfortunately, it currently has to load 9pxeload in order to get
plan9.ini parsed and then load the kernel itself, which requires a
bootstrap igbe driver, which I think I have *this close* to working.
I know jmk's away until the end of the month; anybody else who's
familiar with the card (82540EM Intel PRO/1000 MT) who thinks this
sounds familiar, please let me know:
9(pxe)load sends broadcast BOOTP requests, get a BOOTP reply,
prints the IP & server name, sends a TFTP request, which is
never seen by the server (verified with snoopy and prints in
tftpd). It's going at 1Gb/s, full-duplex through an SMC 8508T
gigabit switch, which otherwise has been working fine. The
cpu server is also connected via igbe to the SMC switch at
full duplex, 1Gb/s. Sending multiple BOOTP requests works as
expected, drawing multiple replies. prints in the boot driver
suggest that the packets are getting into the transmit ring
buffer and that the card is draining the buffer. The bits are
set to pad short packets, which shouldn't be necessary anyway
since we're running full duplex. openbsd with an i82557 card
can tftp from the same cpu server through the same SMC switch.
Ether & IP addresses all look right. I've run out of theories
of what could be going wrong, short of nasty bugs or
deliberate malice somewhere.
I'm trying to load fs kernels (i.e., small kernels that PXE can
handle) currently, so it's tempting to just stick 1K of (possibly
preprocessed plan9.ini) on the front of the kernel being loaded and
let PXE load the whole mess and avoid 9pxeload completely.
reply other threads:[~2004-08-17 8:04 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=2e44aa9ac8b270827a30c09349cc4a35@collyer.net \
--to=geoff@collyer.net \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).