10Mbps+ throughput usb based ethernet recommendation

[Nenhum_de_Nos]

On Sun, April 4, 2010 22:12, Pyun YongHyeon wrote:
> On Sat, Apr 03, 2010 at 09:46:59PM -0300, Nenhum_de_Nos wrote:
>> On Wed, 31 Mar 2010 12:06:31 -0700
>> Pyun YongHyeon <pyunyh at gmail.com> wrote:
>>
>> > On Fri, Mar 26, 2010 at 11:31:50PM -0300, Nenhum_de_Nos wrote:
>> >
>> > [...]
>> >
>> > > >> I changed and got this:
>> > > >>
>> > > >> miibus1: <MII bus> on axe0
>> > > >> ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus1
>> > > >> ukphy0: XXX ID1 = 0x0282, ID2 = 0xf012
>> > > >   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> > > >
>> > > > This is *NOT* bogus value. It's Agere Systems' ET1011 gigabit PHY.
>> > > > FreeBSD has truephy(4) for Agere Systems' PHY but it does not have
>> > > > support code for the model yet.
>> > >
>> > > so I can think that's the issue, right ?
>> >
>> > Probably. But this does not explain sometimes why you get some
>> > bogus value form PHY id registers.
>> > >
>> > > >> ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX,
>> 1000baseT,
>> > > >> 1000baseT-FDX, auto
>> > > >> ue0: <USB Ethernet> on axe0
>> > > >> ue0: Ethernet address: xxxxxxxxxxxxxx
>> > > >> ue0: link state changed to DOWN
>> > > >>
>> > > >> so it didn't now. other thing is that not every time it works:
>> > > >>
>> > > >
>> > > > Yeah, that is real issue here. I guess there should be some magic
>> > > > to wakeup the PHY from deep sleep state. I'll see what can be
>> done.
>> > >
>> > > ok, great it was found :)
>> > >
>> > > let me know if I can help in anything :)
>> > >
>> >
>> > Would you try attached patch and let me know how it goes?
>>
>> axe0: PHYADDR 0xe0:0x01
>> miibus1: <MII bus> on axe0
>> ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus1
>> ukphy0: XXX ID1 = 0x7949, ID2 = 0x7949
>
> Due to other issues previous patch didn't have chance to make it
> work. This time, PHY id started to reporting garbage again which
> means all MII register access may return garbage too. Don't know
> this could be related with USB subsystem though.
>
>> ukphy0:  10baseT-FDX
>> ue0: <USB Ethernet> on axe0
>> ue0: Ethernet address: 00:11:50:e7:39:e9
>> ue0: link state changed to DOWN
>
> [...]
>
>> and I can't ping the other host :(
>>
>> ue0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
>> 1500
>>         options=80000<LINKSTATE>
>>         ether 00:11:50:e7:39:e9
>>         inet 10.2.1.2 netmask 0xffffff00 broadcast 10.2.1.255
>>         media: Ethernet none
>> arroway# ifconfig ue0
>> ue0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
>> 1500
>>         options=80000<LINKSTATE>
>>         ether 00:11:50:e7:39:e9
>>         inet 10.2.1.2 netmask 0xffffff00 broadcast 10.2.1.255
>>         media: Ethernet none (none <hw-loopback>)
>>         status: active
>> arroway# ifconfig ue0
>> ue0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
>> 1500
>>         options=80000<LINKSTATE>
>>         ether 00:11:50:e7:39:e9
>>         inet 10.2.1.2 netmask 0xffffff00 broadcast 10.2.1.255
>>         media: Ethernet none
>>
>> and it is still crazy media changing.
>>
>
> Because your PHY is not recognized it's expected result. :-(

waiting for any leads :)

I bought a linksys axe based fast ethernet to see what happens. waiting
till it arrives.

thanks as usual,

matheus

-- 
We will call you cygnus,
The God of balance you shall be

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

http://en.wikipedia.org/wiki/Posting_style