9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] new igbe network card not activated
Date: Sat,  1 Sep 2007 07:28:03 -0400	[thread overview]
Message-ID: <977fcdfd84b98db54c16747177c6e612@quanstro.net> (raw)
In-Reply-To: <20070831061526.GA6231@mob.mteege.de>

> I put a new Intel PRO/1000 in my Plan 9 server. The card is detected
> by 9load (?) as ether#0 igbe and then as #l1: i82543. There is another
> network interface on board which ist detected as elnk3. I put
> ether0=igbe, ether1=elnk3 in my plan9.ini.
>
> My problem is, that /net/ether0 points always to the elnk3 card. There
> is no /net/ether1. How do I enable the second card? I don't need the
> elnk3 so disable the elnk3 in the kernel maybe an option.

the previous posts were correct, you need "ether0=type=$TYPE".
however ether1 won't just appear in /net.  if you want to use ether1,
you've got to bind it into the default network stack with
	# bind -a '#l1' /net
typically, though, second network cards are bound into a different
network stack
	# bind -a '#I1' /net.alt
	# bind -a '#l1' /net.alt
	# ip/ipconfig -x/net.alt [other options here]

by the way, i have a driver that should do all intel pro/1000
pcie cards.  i'll try to get it submitted soon.  coraid are using the 82563,
82571 and 82573.  i am using two 82572 at home.

http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=2276643&CatId=2380

i don't have an 82566 to test with, but it should work as well unless i
have the wrong device id.  intel have a habit of publishing incorrect
device ids in their yellow books.

- erik



      parent reply	other threads:[~2007-09-01 11:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31  6:15 Matthias Teege
2007-09-01  8:25 ` Anthony Martin
2007-08-31 11:08   ` Matthias Teege
2007-09-01  9:09   ` lucio
2007-09-01 11:28 ` erik quanstrom [this message]

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=977fcdfd84b98db54c16747177c6e612@quanstro.net \
    --to=quanstro@quanstro.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).