On Thu, Feb 12, 2009 at 01:51:47AM +0900, Hiroharu Tamaru wrote: > > At Wed, 11 Feb 2009 16:57:36 +0100, Hans Petter Selasky wrote: > > > > > ugen3.3: <ASIX Electronics> at usbus3 > > > > > axe0: <ASIX Electronics AX88178, rev 2.00/0.01, addr 3> on usbus3 > > > > > axe0: PHYADDR 0xe0:0x18 > > > > > miibus0: <MII bus> on axe0 > > > > > ciphy0: <Cicada VSC8211 10/100/1000TX PHY> PHY 24 on miibus0 > > > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > > > > 1000baseT-FDX, auto ue0: <USB Ethernet> on axe0 > > > > > ue0: Ethernet address: 00:90:cc:xx:xx:xx > > > > > ue0: link state changed to DOWN > > > > > ue0: link state changed to UP > > > > > > > > > > > > > > > Turn on debugging: > > > > > > > > sysctl hw.usb2.axe.debug=15 > > > > > > > > And repeat test. > > > > > > with hw.usb2.axe.debug=15, I have: > > > > > > ugen3.3: <ASIX Electronics> at usbus3 (disconnected) > > > pid 3244 (dhclient), uid 65: exited on signal 11 > > > ugen3.3: <ASIX Electronics> at usbus3 > > > axe0: <ASIX Electronics AX88178, rev 2.00/0.01, addr 3> on usbus3 > > > axe0: PHYADDR 0xe0:0x18 > > > miibus0: <MII bus> on axe0 > > > ciphy0: <Cicada VSC8211 10/100/1000TX PHY> PHY 24 on miibus0 > > > ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > > > 1000baseT-FDX, auto ue0: <USB Ethernet> on axe0 > > > ue0: Ethernet address: 00:90:cc:f7:bc:2e > > > ue0: link state changed to DOWN > > > ue0: link state changed to UP > > > > > > > > The hardware is a PLANEX GU-1000T ethernet adapter. > > >
I have the same USB controller and latest CURRENT works. axe0: <ASIX Electronics AX88178, rev 2.00/0.01, addr 4> on usbus1 axe0: PHYADDR 0xe0:0x18 miibus2: <MII bus> on axe0 ciphy0: <Cicada VSC8211 10/100/1000TX PHY> PHY 24 on miibus2 ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto ue0: <USB Ethernet> on axe0 ue0: Ethernet address: 00:90:cc:ef:b9:f6 ue0: link state changed to DOWN I manually loaded necessary kernel modules as my kernel does not have any USB device entries. The only regression since I tried USB2 axe(4) was failure of symbol resolving of link_elf in usb2_ethernet.ko module. Attached simple patch seems to fix that. To Hans, I think MODULE_DEPEND should come first before any reference to the module in usb2_ethernet.c. Since mii_phy_probe live in miibus(4) I added it too. > > > What can I do now? > > Hiroharu, if you unplug/replug UTP cable, does it make any difference? > > Does netstat indicate any receive errors on the AXE interface? > > > > netstat -i > > Nope. > > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs > Coll > ... > ue0 1500 <Link#4> 00:90:cc:f7:bc:2e 52 0 12 0 > 0 > ue0 1500 192.168.1.0 192.168.1.3 0 - 4 - > - > > The latter line is the result of statically asigning an address, > and then 'ping -n 192.168.1.1'ing for four seconds. > > > Maybe "Pyun YongHyeon" should have a look at this. > > > > And you are running the latest current? > > I updated to -current as of about an hour or two ago. > PS. Please CC to me I'm not subscribed to the list.
_______________________________________________ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
