From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Fileserver question
Date: Fri, 17 Aug 2001 06:03:04 +0100 [thread overview]
Message-ID: <20010817050744.9B292199E7@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 578 bytes --]
you're right about the ne2000 and the file server.
the file server device set is a fairly small subset
of the cpu/terminal support, based on what has been
used to build file servers. since
those are typically built to give some degree of
performance, ne2000/8390-based things might not
be the cards of choice. one way or another that
device support will improve, but that doesn't do you
a lot of good now.
in ether82557.c make sure it reads
if(bmcr & 0x2000)
ether->mbps = 100;
else
ether->mbps = 10;
and specifically that the else isn't missing.
[-- Attachment #2: Type: message/rfc822, Size: 2422 bytes --]
From: Sam Ducksworth <sam@ducksworth.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Fileserver question
Date: Thu, 16 Aug 2001 15:50:55 -0700 (PDT)
Message-ID: <Pine.BSF.4.33.0108161542240.43051-100000@lucifer.ducksworth.com>
well i spoke too soon. now i am having problems
with the network card. first i had a ne2000 card
in it, but after looking at the fs src i do not
see a driver for the ne2000. next i changed the
plan9.ini and installed a i82557 compatable intel
card that was in my terminal.
the fs kernel detects the card and boots fine but
nothing works. i noticed the following during boot:
ether0: i82557: 0Mbps port 0xe400 irq 12: 0002630325a0
^^^^^^
i even did like the man page said and tried to force
it using the '10BASE-T' option in the plan9.ini file.
--sam
> the trailing '0' was the problem. finally, i have
> a real file server...thanks!
next reply other threads:[~2001-08-17 5:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 5:03 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-17 3:08 jmk
[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=20010817050744.9B292199E7@mail.cse.psu.edu \
--to=forsyth@caldo.demon.co.uk \
--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).