9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rtl8139 ether driver
Date: Fri, 28 Jun 2002 19:37:00 +0900	[thread overview]
Message-ID: <20020628103814.15E1E19980@mail.cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 298 bytes --]

This problem was solved by replacing the onboard Realtek 8100BL chip
to Intel's i82557 chipped card (Intel XPRES-PRO100).   Now I'm using this
Pen 4 1.6GHz + AOpen AX4B Pro-533 mother happily as our Auth/CPU
server for Release 3 Plan 9. It must be same for Release 4, I believe. :-)

Kenji


[-- Attachment #2: Type: message/rfc822, Size: 2370 bytes --]

From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: [9fans] rtl8139 ether driver
Date: Wed, 26 Jun 2002 10:45:59 +0900
Message-ID: <20020626014705.4A7E0199E3@mail.cse.psu.edu>


I'm now forced to use rtl8139 nic for my new Auth/CPU server (
it's for 3ed not 4ed. I cannot update our system now, because it's
being used for the platform for our application, and the semester is
still going here).   it reboots once a day.  :-)

We had been using dual Pen III on SuperMicro motherboard, but it
crushed about a month ago.   Then, I changed that server to a Pen 4
mother board (1.6GHz) of AOpen AX4B Pro-533 which has on board
nic chip of Realtek 8100BL.   It seems to work fine, however, it may
have problem as above.

When I read the /sys/src/9/pc/ether8139.c, I found the lines of
"Error recovery for the various over/under-flow conditions may need work"
phrase.   Does my problem relate to this remark?

Kenji

             reply	other threads:[~2002-06-28 10:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-28 10:37 okamoto [this message]
2002-06-28 13:31 ` [9fans] * most USB audio devices matt
  -- strict thread matches above, loose matches on Subject: below --
2002-06-27  2:49 [9fans] rtl8139 ether driver okamoto
2002-06-26  9:22 okamoto
2002-06-26  8:07 forsyth
2002-06-26  2:31 okamoto
2002-06-26  1:58 jmk
2002-06-26  1:45 okamoto

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=20020628103814.15E1E19980@mail.cse.psu.edu \
    --to=okamoto@granite.cias.osakafu-u.ac.jp \
    --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).