Re: Getting ethernet to work

[Hisashi T Fujinaka <htodd%twofifty.com@localhost>]

On Sun, 22 Feb 2009, Arthur Barlow wrote:

> On Feb 22, 2009, at 5:05 PM, Andy Ruhl wrote:
>
> > On Sun, Feb 22, 2009 at 5:50 PM, Arthur Barlow
> > <arthurbarlow%earthlink.net@localhost> wrote:
> > > After some struggling, I finally got the "current" kernel to compile.  I
> > > built a striped down version of GENERIC to MYKERNEL, and everything works,
> > > except the ethernet driver.  It will not log on via dhcp.  The dmesg says
> > > the following:
> > >
> > >
> > > fxp0: at pci1 dev 1 function 0: i82559 Ethernet, rev 8
> > > fxp0: interrupting at irq 3
> > > fxp0: May need receiver lock-up workaround
> > > fxp0: Ethernet address 00:d0:b7:ab:b2:dc
> > > inphy0: at fxp0 phy 1: i82555 10/100 media interface, rev. 4
> > > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> > >
> > >
> > >
> > > I do not know what the "may need receiver lock-up workaround" means.  I
> > > assume the problem is in the ethernet driver as opposed to the DHCP 
> > > startup
> > > script.  Thanks for the help.
> >
> > Well, it says "may" for a reason. It doesn't say you "do" have this
> > problem, you may have it.
> >
> > What did the DHCP attempt say?
> >
> > Can you assign a static address and get on the network? You really
> > should try that and tell us why that doesn't work before stating you
> > have a problem with your card.
> >
> > Andy
>
> Andy,
>
> Here's what the DHCP attempt says:
>
>
> Listening on BPF/fxp0/00:d0:b7:ab:b2:dc
> Sending on  BPF/fxp0/00:d0:b7:ab:b2:dc
> Sending on  Socket /fallback
> DHCPREQUEST on fxp0 at 255.255.255.255 port 67
> DHCPREQUEST on fxp0 at 255.255.255.255 port 67
> DHCPDISCOVER on fxp0 at 255.255.255.255 port 67 interval 4
> DHCPDISCOVER on fxp0 at 255.255.255.255 port 67 interval 5
> DHCPDISCOVER on fxp0 at 255.255.255.255 port 67 interval 12
> DHCPDISCOVER on fxp0 at 255.255.255.255 port 67 interval 19
> DHCPDISCOVER on fxp0 at 255.255.255.255 port 67 interval 18
> DHCPDISCOVER on fxp0 at 255.255.255.255 port 67 interval 3
> No DHCPOFFERS received.
> Trying recorded lease 192.168.1.102
> PING 192.168.1.1 (192.168.1.1): 56 data bytes
>
> ----192.168.1.1 PING Statistics----
> 1 packets transmitted, 0 packets received, 100.0% packet loss
> No working leases in persistent database - sleeping.

I've found this to mean that dhcpcd is just plain busted and the
developer doesn't have any Intel hardware to debug and can't fix it.

I'd suggest (if this is the case) using dhclient.

--
Hisashi T Fujinaka - htodd%twofifty.com@localhost
BSEE(6/86) + BSChem(3/95) + BAEnglish(8/95) + MSCS(8/03) + $2.50 = latte