From owner-freebsd-net@FreeBSD.ORG Mon May 12 11:55:53 2008 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04218106566C for ; Mon, 12 May 2008 11:55:53 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from frontmail.ipactive.de (frontmail.maindns.de [85.214.95.103]) by mx1.freebsd.org (Postfix) with ESMTP id 91E8F8FC0A for ; Mon, 12 May 2008 11:55:51 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (Q7dfe.q.ppp-pool.de [89.53.125.254]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id 71A8A12881E; Mon, 12 May 2008 13:55:44 +0200 (CEST) Received: from cesar.sz.vwsoft.com (unknown [192.168.18.3]) by mail.vtec.ipme.de (Postfix) with ESMTP id F075A3F439; Mon, 12 May 2008 13:58:28 +0200 (CEST) Message-ID: <48283036.8060602@vwsoft.com> Date: Mon, 12 May 2008 13:55:34 +0200 From: Volker User-Agent: Thunderbird 2.0.0.14 (X11/20080503) MIME-Version: 1.0 To: Marius Strobl References: <48281D8F.2090501@vwsoft.com> <20080512111958.GA95632@alchemy.franken.de> In-Reply-To: <20080512111958.GA95632@alchemy.franken.de> X-Enigmail-Version: 0.95.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit MailScanner-NULL-Check: 1211198313.9915@RNe5nR70vnWx+QveYjAeog X-MailScanner-ID: F075A3F439.57A4E X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: volker@vwsoft.com Cc: net@freebsd.org Subject: Re: how to identify a PHY? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 11:55:53 -0000 On 05/12/08 13:19, Marius Strobl wrote: > On Mon, May 12, 2008 at 12:35:59PM +0200, Volker wrote: >> Hi! >> >> >From the bugbusting front, I'm often seeing network related issues with >> unknown (new) PHYs. >> >> Can please somebody explain me how one is able to identify what kind of >> PHY interface is build into a system? Does pciconf output provide some >> piece of information which leads into getting PHY information? I need to >> know that to work with the submitter and get their interfaces running >> (or retrieve information for you to work on). >> > > If the system is running the simplest thing in order to identifiy > the PHYs is to check the oui= and model= output of `devinfo -v`. > Otherwise boot verbose and check the OUI and model output of > ukphy(4). Marius, thanks for your answer. As far as I understand, the devinfo output will only contain useful information if a driver attaches to the phy. Sometimes a new mainboard hits the market and the ID of the phy's chip is unknown the FreeBSD. If a submitter files a PR and no phy driver attaches, I would like to check if the chip ID is currently known to the system. So I need to know a way to check the ID of a chip without a driver being attached. In short my original question better reads as "how do I know the kind of phy if no driver has been attached". Can one retrieve that information out of a verbose boot dmesg (from probing messages)? I would like to first check if a PR might be related to a phy problem at all and if it's just coming with an ID currently unknown to FreeBSD to prepare the PR into a state containing every piece of information needed to have the net-team working easily on it. Thanks Volker