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] file server install
Date: Wed, 19 Dec 2001 22:08:33 -0500	[thread overview]
Message-ID: <20011220030836.23BDD19A80@mail.cse.psu.edu> (raw)

On Wed Dec 19 19:53:16 EST 2001, geoff@collyer.net wrote:
> What I noticed first was this:
>
> 	scsi#0: ncr53c8xx: port 0xe1906000 irq 11
>
> I believe port numbers are limited to 16 bits even for PCI devices,
> and given that your ether is at 0x6100, that 0xe1906000 should
> probably be 0x6000.  Perhaps your BIOS's PCI P'n'P code is broken?
> I've seen breakage in assigning IRQs before.
>
> The 0Mbps thing is also worrying; have you tried plugging your
> machines into a switch (they're pretty cheap now)?
>

The 53C8xx driver uses memory-mapped accesses so the apparently
large port address is OK.

A clue to the answer is, as Geoff points out,given by the 0Mbps 'thing'.
Here's a post from last year:

 From cse.psu.edu!owner-9fans Thu Jun 15 17:29:58 EDT 2000
Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Thu Jun 15 17:29:58 EDT 2000
Date: Thu, 15 Jun 2000 17:08:38 -0400 (EDT)
From: Sam Hopkins <sah@borf.com>
Subject: [9fans] fs configuration with the ether i82557

Heya,

If you're planning on setting up a fileserver with the i82557 nic, you'll
need to edit the code in your /sys/src/fs/<kernel>/ether82557.c file.
Currently it only checks and sets for the 100 mbps setup, and otherwise
leaves it 0.  This unfortunately makes the fileserver's network capabilities
nonexistent.

Around line 1043 you'll see the conditional:
  if(bmcr & 0x2000)
    ether->mbps = 100;
Add:
  else
    ether->mbps = 10;

and you'll be set.

sam


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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-20  3:08 jmk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-20  0:52 geoff
     [not found] <20011219141904.5F49E19A67@mail.cse.psu.edu>
2001-12-19 23:52 ` William Gunnells
2001-12-19  8:52 forsyth
2001-12-18 22:32 Russ Cox
     [not found] <20011218154004.0E3A619A2C@mail.cse.psu.edu>
2001-12-18 22:18 ` William Gunnells
2001-12-18 23:06   ` Sam Ducksworth
     [not found] <20011214170104.C9FF719A0C@mail.cse.psu.edu>
2001-12-18  1:36 ` William Gunnells

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=20011220030836.23BDD19A80@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).