From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Sat, 19 Apr 2008 17:12:31 +0100 From: "Stefan Hajnoczi" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> In-Reply-To: <165a6b9d60bce2dd5cce90c5f18c1069@quanstro.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <165a6b9d60bce2dd5cce90c5f18c1069@quanstro.net> Subject: Re: [9fans] VIA Rhine II mii problems Topicbox-Message-UUID: 9525c1fc-ead3-11e9-9d60-3106f5b1d025 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 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. > > >