From owner-freebsd-mobile Thu May 17 10: 7: 8 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from EM550.home.com (a24b161n147client49.hawaii.rr.com [24.161.147.49]) by hub.freebsd.org (Postfix) with ESMTP id 7177137B422 for ; Thu, 17 May 2001 10:07:05 -0700 (PDT) (envelope-from randal@mailrelay.hits.net) Received: from vaio (h105.home.com [10.0.0.105]) by EM550.home.com (8.11.3/8.11.3) with ESMTP id f4HGwhV00425; Thu, 17 May 2001 06:58:43 -1000 (HST) (envelope-from randal@mailrelay.hits.net) From: "Randal Masutani" To: Scott Mitchell , randal@mailrelay.hits.net, Dave Tweten , mobile@FreeBSD.ORG Date: Thu, 17 May 2001 01:10:05 -1000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Xircom Watchdog Time-out Bug Reply-To: randal@mailrelay.hits.net Message-ID: <3B0324ED.28683.358E3A@localhost> In-reply-to: <20010516222722.38753@localhost> References: <3AFD13D0.15883.1D4F00@localhost>; from Randal Masutani on Sat, May 12, 2001 at 10:43:28AM -1000 X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 16 May 2001, at 22:27, Scott Mitchell wrote: > On Sat, May 12, 2001 at 10:43:28AM -1000, Randal Masutani wrote: > > Dave, > > > > I have been having the same problem on my VAIO F560 with the Xircom CE3 > > card. I have turned on XE_DEBUG in the driver to see whats going on. I > > appears to have a problem with Autonegotiation. The driver is not > > detecting the PHY chip correctly? It tries at least 6 times before it > > detects it and then autonegotiation works okay and then DHCP will get > > done. > > > > Anyone who understands the Autonegotiation process or more on MII PHY > > process? > > This has been the biggest issue with the xe driver for a long time now. I > wrote the PHY-handling code to do the same thing as the Linux driver it was > ported from, which seemed to match fairly well with the docs I had > available. However, it's always had trouble with autonegotiation in some > configurations, although I've never worked out what the defining features > of those configurations are :-( > > I might have done more about it, except that the driver works for me on > all-but-one of the hubs/switches I've ever plugged it into, from the cheapo > Linksys on my desk here to the monster racks of Cisco kit at work, and I no > longer have access to the one that didn't work. > > So, have you tried connecting to a different autonegotiating hub/switch, if > you have access to such a beast? How about inserting the card after boot, > and manually ifconfig-ing it to force a particular media type? Do you > still get bad behaviour in those cases? Yes, I have tried different hub/switches. I always get a time-out but sometimes only one and at other times many. Yes, I eventually get it to work most times after removing and reinserting the card. Forcing it to a particular type didn't seem to work to well. > > You may be right that the PHY isn't being detected correctly -- the Xircom > docs hint at several different PHYs having been used in the CE3 and > RealPort products, but I'm not sure there's a reliable way to tell exactly > what you've got... From what I gather from the debug statements it appears that it is not reading the PHY status (BMSR register) properly, since it is getting back a 0 (null) result. Maybe there is not enough delay or wait states between reading or writing to the PHY registers? I have looked at the source code and also source from the Linux driver and the sdk kit from Xircom, they all are a little different in the procedure on how to read and write data to the MII registers. Randal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message