bios.bios.version="V2.7"
>> >> >> >> smbios.chassis.maker="MSI"
>> >> >> >> smbios.chassis.serial="To Be Filled By O.E.M."
>> >> >> >> smbios.chassis.tag="To Be Filled By O.E.M."
>> &
mbios.chassis.tag="To Be Filled By O.E.M."
> >> >> >> smbios.chassis.version="2.0"
> >> >> >> smbios.memory.enabled="2097152"
> >> >> >> smbios.planar.maker="MSI"
> >> >> >> sm
;> smbios.chassis.version="2.0"
>> >> >> smbios.memory.enabled="2097152"
>> >> >> smbios.planar.maker="MSI"
>> >> >> smbios.planar.product="K9N6PGM2-V2 (MS-7309)"
>> >> >> smbios.planar
filled by O.E.M."
> >> >> smbios.planar.version="2.0"
> >> >> smbios.socket.enabled="1"
> >> >> smbios.socket.populated="1"
> >> >> smbios.system.maker="MSI"
> >> >> smbios.syste
smbios.planar.version="2.0"
>> >> smbios.socket.enabled="1"
>> >> smbios.socket.populated="1"
>> >> smbios.system.maker="MSI"
>> >> smbios.system.product="MS-7309"
>> >> smbios.system.serial
S-7309"
> >> smbios.system.serial="To Be Filled By O.E.M."
> >> smbios.system.uuid="----406186cd4497"
> >> smbios.system.version="2.0"
> >> smbios.version="2.6"
> >>
> >> Hope th
smbios.system.uuid="----406186cd4497"
>> smbios.system.version="2.0"
>> smbios.version="2.6"
>>
>> Hope this helps, and thank you for all your time, and trouble.
>>
>
> Thanks for the info. Try attached pa
On Tue, Apr 01, 2014 at 05:53:51PM -0700, Chris H wrote:
> > On Tue, Apr 01, 2014 at 01:40:58PM -0700, Chris H wrote:
> >> > On Tue, 2014-04-01 at 13:19 -0700, Chris H wrote:
> >> >> [...]
> >> >> miibus0: on nfe0
> >> >> rlphy0: PHY 0 on miibus0
> >> >> rlphy0: 10baseT, 10baseT-FDX, 100baseTX,
> On Tue, Apr 01, 2014 at 01:40:58PM -0700, Chris H wrote:
>> > On Tue, 2014-04-01 at 13:19 -0700, Chris H wrote:
>> >> [...]
>> >> miibus0: on nfe0
>> >> rlphy0: PHY 0 on miibus0
>> >> rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
>> >> rlphy1: PHY 1 on miibus0
>> > [
On Tue, Apr 01, 2014 at 01:40:58PM -0700, Chris H wrote:
> > On Tue, 2014-04-01 at 13:19 -0700, Chris H wrote:
> >> [...]
> >> miibus0: on nfe0
> >> rlphy0: PHY 0 on miibus0
> >> rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
> >> rlphy1: PHY 1 on miibus0
> > [...]---bi
n net@, or stable@
>>>> so I'm using both. :)
>>>> I'm testing both releng_9, and MB, and I encountered a new
>>>> message I don't usually see using the nfe(4) driver:
>>>>
>>>> miibus0: mii_mediachg: can't handle non-zero P
>> On Tue, 2014-04-01 at 13:19 -0700, Chris H wrote:
>>> [...]
>>> miibus0: on nfe0
>>> rlphy0: PHY 0 on miibus0
>>> rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
>>> rlphy1: PHY 1 on miibus0
>> [...]---big-snip--8<---
>>> miibus0: mii_mediachg: can't handle non-zero P
> On Tue, 2014-04-01 at 13:19 -0700, Chris H wrote:
>> [...]
>> miibus0: on nfe0
>> rlphy0: PHY 0 on miibus0
>> rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
>> rlphy1: PHY 1 on miibus0
> [...]---big-snip--8<---
>> miibus0: mii_mediachg: can't handle non-zero PHY insta
, auto-flow
> rlphy29: PHY 29 on miibus0
> rlphy29: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
> rlphy30: PHY 30 on miibus0
> rlphy30: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
> rlphy31: PHY 31 on miibus0
> rlphy31: 10baseT, 10baseT-FDX,
ng both. :)
>> >> I'm testing both releng_9, and MB, and I encountered a new
>> >> message I don't usually see using the nfe(4) driver:
>> >>
>> >> miibus0: mii_mediachg: can't handle non-zero PHY instance 1
>> >> ...
>>
t; >> I'm testing both releng_9, and MB, and I encountered a new
> >> message I don't usually see using the nfe(4) driver:
> >>
> >> miibus0: mii_mediachg: can't handle non-zero PHY instance 1
> >> ...
> >> miibus0: mii_mediachg: can
usually see using the nfe(4) driver:
>
> miibus0: mii_mediachg: can't handle non-zero PHY instance 1
> ...
> miibus0: mii_mediachg: can't handle non-zero PHY instance 31
>
> Truncated for brevity (31 lines in total; 1-31). I don't know
> how interpret this. An issue with
...
miibus0: mii_mediachg: can't handle non-zero PHY instance 31
Truncated for brevity (31 lines in total; 1-31). I don't know
how interpret this. An issue with my version of the driver, or
the hardware itself? This occurred with both GENERIC, as well
as my custom kernel.
# uname -a
FreeBSD d
18 matches
Mail list logo