Next-in-Thread Next Message

None Not sure if this is Caldera specific 

Forum: PCMCIA Network Adapter Issues
Re: Question DHCP with PCMCIA (Christopher Keller)
Date: 1999, Dec 06
From: David Hinds <dhinds@pcmcia.sourceforge.org>

I don't think it is possible to narrow down the problem based on just
this information.  Are you sure that dhcpcd is being started prior to
when PCMCIA loads?  (are there system log messages from a second copy
of dhcpcd?)  I am not familiar with Caldera, but to the extent it is
based on Red Hat, I know that Red Hat checks for and delays startup of
a PCMCIA network device to avoid exactly this problem.  It would be
strange for Caldera to have un-done this.

Another simple thing to try, is to boot with the card out, then plug
it in and see what happens.  That will distinguish between various
sorts of boot-time sequencing problems, and PCMCIA startup problems.

> cardmgr[572]: + Trying to obtain network configuration via DHCP.
> kernel: eth0: found link beat
> kernel: eth0: autonegotiation complete: 100baseT-HD selected
> kernel: eth0: remote fault detected
> dhcpcd[587]: timed out waiting for a valid DHCP server response

The timing here concerns me, because it looks like dhcpcd may be
having trouble because the card has a delay before it has properly
sensed the link speed.

-- Dave

Next-in-Thread Next Message

Messages Inline: 1 All Outline: 1 2 All

1. None Hate to say it, but even Red Hat is having trouble with DHCP and PCMCIA by Nathan Hartwell, 2000, Jan 17
(_ None Don't be so sure! by David Hinds, 2000, Jan 17
(_ None quite right....it wasn't a PCMCIA issue, but a DHCP issue by Nathan Hartwell, 2000, Jan 19

Add Message to: "Not sure if this is Caldera specific"

Members Subscribe Admin Mode Show Frames Help for HyperNews at pcmcia-cs.sourceforge.net 1.10