From: "Stefan Hajnoczi" <stefanha@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 17:12:31 +0100 [thread overview]
Message-ID: <fbd9d3990804190912h5758a32fo709ec9269fdd19e4@mail.gmail.com> (raw)
In-Reply-To: <165a6b9d60bce2dd5cce90c5f18c1069@quanstro.net>
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.
Stefan
On Sat, Apr 19, 2008 at 3:10 PM, erik quanstrom <quanstro@quanstro.net> wrote:
> i don't have this part (that i know of) and the datasheet didn't
> immediately pop up, but the linux driver hardcodes the phy_id to 1.
> the part you have claims to have an integrated phy.
>
> you may wish to try that.
>
> - erik
>
> p.s. lspci -n will give you vid/did numbers.
>
>
>
> > Hi,
> > I just installed Plan 9 on a machine using a VIA Rhine II NIC.
> > Unfortunately the driver is not successfully initializing the device.
> >
> > Placing print statements in ethervt6102.c shows that vt6102reset() is
> > failing when mii() returns an empty PHY mask. The mii() function is
> > probing each PHY from 0 to 31, but always finds that oui == 0. It
> > never finds a PHY.
> >
> > Any hints? I understand the high-level details but don't have the
> > knowledge to do anything other than poke around blindly now.
>
>
>
next prev parent reply other threads:[~2008-04-19 16:12 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 [this message]
2008-04-19 16:36 ` Harri Haataja
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=fbd9d3990804190912h5758a32fo709ec9269fdd19e4@mail.gmail.com \
--to=stefanha@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).