9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Fileserver question
Date: Thu, 16 Aug 2001 23:08:22 -0400	[thread overview]
Message-ID: <20010817031059.534BD199E7@mail.cse.psu.edu> (raw)

yes, at the moment some cards require that, we only do chip setup
at boot time. usually it's not a problem as the cards don't hop around
from switch to switch and we usually boot over the network, so if the
cable's not connected you find out pretty quickly.

we've been doing some work recently to allow insertion and removal
of pc cards and this will utimately require the ethernet drivers to
deal with link going up and down.

On Thu Aug 16 22:26:22 EDT 2001, martin@Princeton.EDU wrote:
> jmk@plan9.bell-labs.com wrote:
> > 
> >         ether0: i82557: 0Mbps port 0xe400 irq 12: 0002630325a0
> >                        ^^^^^^
> > 
> > that means the driver did not detect link on the card when it
> > initialised. check the cable - check the lights on the back of the
> > card.
> 
> Does this mean that you have to have the cable connected when the system
> boots, or can you subsequently connect a cable and make it happy?
> 
> I remember seeing this message once and thinking that the card in
> question (which was of dubious origin) was bad.
> 
> Martin


             reply	other threads:[~2001-08-17  3:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-17  3:08 jmk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-17  5:03 forsyth
     [not found] <200108170018.f7H0ISh43350@ducksworth.com>
2001-08-17  2:37 ` Sam Ducksworth
2001-08-17  1:00 jmk
2001-08-17  2:25 ` Martin Harriss
2001-08-16 17:15 jmk
2001-08-16 17:36 ` Sam Ducksworth
2001-08-16 22:50   ` Sam Ducksworth
2001-08-16 16:59 Sam Ducksworth

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=20010817031059.534BD199E7@mail.cse.psu.edu \
    --to=jmk@plan9.bell-labs.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).