Re: r8169 driver problem with RTL8110SB chip (on iop3xx ARM board)

[Jamal Hadi Salim <hadi@cyberus.ca>]

On Fri, 2006-28-07 at 13:15 +0200, Lennert Buytenhek wrote:
> On Fri, Jul 28, 2006 at 12:49:46PM +0200, Francois Romieu wrote:
> 
> > > The in-kernel 'r8169' drivers in 2.6.17 and 2.6.18-rc2 appear to work
> > > initially, but they don't actually seem to transmit any packets on the
> > > wire, nor do they receive any.
> > > 
> > > Boot logs from 2.6.17 and 2.6.18-rc2 attached.  Apart from the MAC
> > > address for eth1 being incorrect (boot loader bug, being worked on)
> > > there don't seem to be any strange messages or errors.
> > 
> > Can you send:
> > - the output of 'lspci -vvx' 
> 


Since you mention an incorrect MAC address: The one thing that has
bitten me in the past(twice) is misprograming of the eeprom (where
typically the MAC address would sit as well). Vendor in a hurry to put
out the NIC/board forgets to do something at manufacturing time. The
most recent was about 9 months back where the same chip was used in the
board but in one port copper was used and in another hooking up via
serdes. The eeprom claimed both to be copper. It worked for sometime
until you pulled a link and then plugged it back in. A little ethtool
magic to change the device id to match 0x107B
(E1000_DEV_ID_82546GB_SERDES) instead of 0x1079
(E1000_DEV_ID_82546GB_COPPER) fixed it.

cheers,
jamal

PS:- That box looks interesting - priced correctly i may even buy
one ;->