9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Brantley Coile <brantley@coraid.com>
To: 9fans@cse.psu.edu
Subject: [9fans] PXE bootings
Date: Tue,  5 Apr 2005 18:20:17 -0400	[thread overview]
Message-ID: <5b123c52699f7c2156627cfb5034b77b@coraid.com> (raw)

I'm booting a new box with new Intel GbE
interfaces and I have a question.  Here is my
ndb/local entry for the box:


ip=205.185.197.25 ether=00304881bd66 sys=rb1
	dom=rb1.coraid.com
	bootf=/386/9pxeload
	

Here's my /cfg/pxe/00304881bd66

*nomp=1
ether0=type=igbe
ether1=type=igbe
fs=205.185.197.1
auth=205.185.197.2
console=0
bootfile=ether0!/386/9pccpu
bootargs=il -g 205.185.197.254 ether /net/ether0 205.185.197.25 255.255.255.0

On the serial console I see: bootp timed out
Then I load the kernel

atlas (205.185.197.2!67): /386/9pccpu
664555+521640+124596=1310791
entry: 0x80100020

Plan 9
cpu0: 2995MHz GenuineIntel P4 (cpuid: AX 0x0F29 DX 0xBFEBFBFF)
ELCR: 0E20
pcirouting: ignoring south bridge PCI.0.31.0 8086/25A1


That's the last I see of it.  I'm putting entries
into certain switch statements to id the part.
Etherigbe.c doesn't include the 82541 or the 82547.  I have
both on this motherboard.

What do I need to do to keep it form waiting on
the bootp?

Has anyone already put the did's in for the 82541 and the 82547?

  Brantley



             reply	other threads:[~2005-04-05 22:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-05 22:20 Brantley Coile [this message]
2005-04-05 23:53 ` jmk
2005-04-06  0:03   ` Brantley Coile
2005-04-06  0:15     ` jmk
2005-04-06  0:16     ` geoff

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=5b123c52699f7c2156627cfb5034b77b@coraid.com \
    --to=brantley@coraid.com \
    --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).