0n Mon, May 12, 2008 at 01:19:58PM +0200, Marius Strobl wrote:
>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).
Curiou
On Mon, May 12, 2008 at 01:55:34PM +0200, Volker wrote:
> 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 som
Volker wrote:
...
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)?
You can't determine which PHY is in use unless a driver is attached,
because
Marius Strobl wrote:
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).
There's a project for someone in there I'm sure.
Linux has mii-tool
On 05/12/08 13:45, Bruce M. Simpson wrote:
> Marius Strobl wrote:
>> 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).
>>
>
> There's a p
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 interfa
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
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 informa
