9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Harri Haataja" <realblades@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] VIA Rhine II mii problems
Date: Sat, 19 Apr 2008 19:36:48 +0300	[thread overview]
Message-ID: <74e3492a0804190936k3d44bfbft12bff1a3f805d96a@mail.gmail.com> (raw)
In-Reply-To: <fbd9d3990804190912h5758a32fo709ec9269fdd19e4@mail.gmail.com>

On 19/04/2008, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> I initialised the mii struct to use phy 1, as mii() would have if it
>  had succeeded.  Unfortunately running ip/ipconfig simply sat there,
>  running it with the debug flag showed recv timeouts.  I could not see
>  any packets on the network.

On the slight chance that this is useful, I have never seen a VIA chip
that worked reliably (never tried their processors, though).
Especially the Rhine based pci cards my then employer once had would
periodically freeze and require a full power cycle before they'd work
for a while again if at all. This happened under several windows
versions on PC, Linux, possibly some BSD. Varied drivers and other
hardware anyway. We quickly decided it wasn't worth even trying and
went with another chip since eth cards aren't hugely expensive.

Finns can also cheerfully call anything with a VIA chip "viallinen",
which literally meens "something with via" while being a word meaning
"defective". It's pretty much true on both counts.

--
I appear to be temporarily using gmail's horrible interface. I
apologise for any failure in my part in trying to make it do the right
thing with post formatting.


  reply	other threads:[~2008-04-19 16:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-19  7:48 Stefan Hajnoczi
2008-04-19 14:10 ` erik quanstrom
2008-04-19 16:12   ` Stefan Hajnoczi
2008-04-19 16:36     ` Harri Haataja [this message]
2008-04-19 17:16       ` Stefan Hajnoczi
2008-04-20 16:03         ` erik quanstrom

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=74e3492a0804190936k3d44bfbft12bff1a3f805d96a@mail.gmail.com \
    --to=realblades@gmail.com \
    --cc=9fans@9fans.net \
    /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).