On Thu, May 03, 2018 at 02:11:24PM -0700, Dieter BSD wrote:
> > 10.3-RELEASE
[...]
> pyunyh> Which phy driver is used for axge(4)?
> pyunyh> You can see the phy driver name below axge(4) attachment in dmesg
> pyunyh> output.
>
> axge0: on usbus2
> axge1: on usbus0
> miibus4:
> on axge0
>
> 10.3-RELEASE
> amd64 with ECC memory
> VIA VL805 USB 3.0 controller
> ue0 is Siig USB-to-Ethernet Chipset: AX88179
>
> ugen0.7: at usbus0, cfg=0 md=HOST
>spd=SUPER (5.0Gbps) pwr=ON (124mA)
>
> ue0: flags=8c43 metric 0
> mtu 1500
> options=8000b
> inet 10.0.210.66 netmas
On Tue, Apr 10, 2018 at 03:54:58PM -0700, Dieter BSD wrote:
> 10.3-RELEASE
> amd64 with ECC memory
> VIA VL805 USB 3.0 controller
> ue0 is Siig USB-to-Ethernet Chipset: AX88179
>
> ugen0.7: at usbus0, cfg=0 md=HOST
>spd=SUPER (5.0Gbps) pwr=ON (124mA)
>
> ue0: flags=8c43 metric 0
> mtu
I have one of these (I think it's the same chipset, I know it's AX88xxx)
and I've used it before without issue.
If I can find it at home and it's the same chipset I'll give it a whirl
and check to confirm that it's not a hardware issue. Problem with these
cheap USB-whatever adapters is that the
10.3-RELEASE
amd64 with ECC memory
VIA VL805 USB 3.0 controller
ue0 is Siig USB-to-Ethernet Chipset: AX88179
ugen0.7: at usbus0, cfg=0 md=HOST
spd=SUPER (5.0Gbps) pwr=ON (124mA)
ue0: flags=8c43 metric 0
mtu 1500
options=8000b
inet 10.0.210.66 netmask 0xff00 broadcast
