Re: aue0 detected as ue0 on 8.0-RC2

On Tuesday 03 November 2009 11:10:47 Gavin Atkinson wrote:
> [freebsd-current cc'd, as that was where the thread started, but this
> probably belongs on -usb, replies should go there]
>
> On Sat, 2009-10-31 at 21:59 +0100, Rick van der Zwet wrote:
> > The first net interface of a aue(4) define used to be called aue0
> > afaik. But is now called ue0 (declared in usb/net/usb_ethernet.c). (no
> > sign of ue(4) btw).
> >
> > I was looking in the UPDATING, man, mailinglists freebsd-usb_at_ and
> > freebsd-current_at_. But I could not find the reason why the naming
> > convention on this aue differs from the regular stuff, anybody?
> >
> > /Rick
> >
> > quick# dmesg | tail -8
> > ugen1.3: <ADMtek> at usbus1
> > aue0: <ADMtek USB To LAN Converter, rev 2.00/1.01, addr 3> on usbus1
> > miibus1: <MII bus> on aue0
> > ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus1
> > ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> > ue0: <USB Ethernet> on aue0
> > ue0: Ethernet address: 00:00:e8:00:11:36
> > ue0: link state changed to DOWN
> >
> > quick# ifconfig -l
> > bfe0 lo0 ue0
>
> Hmm, this looks like a serious bug, possibly in the new USB subsystem
> (HPS CC'd).
>
> I've got an axe(4) device, which also does the same:
>
> ugen7.3: <vendor 0x0b95> at usbus7
> axe0: <vendor 0x0b95 product 0x7720, rev 2.00/0.01, addr 3> on usbus7
> axe0: PHYADDR 0xe0:0x10
> miibus1: <MII bus> on axe0
> ukphy0: <Generic IEEE 802.3u media interface> PHY 16 on miibus1
> ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> ue0: <USB Ethernet> on axe0
> ue0: Ethernet address: 00:50:b6:05:57:a7
> ue0: link state changed to DOWN

Hi,

All USB ethernet adapters are now named ue0. You will get one axe0 event and 
one ue0 event. So there should be no problems regarding devd.conf  .

--HPS