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: [ 0 ]  [ 1 ] 

Hate to say it, but even Red Hat is having trouble with DHCP and PCMCIA Re: Not sure if this is Caldera specific (David Hinds) Date: 2000, Jan 17 From: Nathan Hartwell MageX

I just switched out my generic PCMCIA 10/100 card for a D-Link DFE-650TX card (something on the supported list). As it would turn out, I -still- can't get dhcpcd or pump to grab an IP. At least with pump, I see the messages where it gets an offer, but the offer is never accepted for one reason or another. With dhcpcd, it just seems to sit there like a bump on a log then finally times out. I had these same troubles with the previous card which is why I switched to this D-Link. I even went so far as to re-extract the pcmcia-cs v3.1.6 package and recompile (plus a fresh copy of 8390.c and 8390.h). I have not yet forced a specific IP as I am not wanting to have it set up this way to begin with. I am certain that the card will work fine once I manually set it's IP, however. Any help will be appreciated.

Don't be so sure! Re: Hate to say it, but even Red Hat is having trouble with DHCP and PCMCIA (Nathan Hartwell) Date: 2000, Jan 17 From: David Hinds <dhinds@pcmcia.sourceforge.org>

> I have not yet forced a specific IP as > I am not wanting to have it set up this way to begin with. I am certain > that the card will work fine once I manually set it's IP, however. There is no reason whatsoever for you to be certain of this fact, and you should absolutely test it, because it is the only way to determine for sure if you are suffering from a driver problem, versus suffering from some issue with your DHCP configuration. Just do it. -- Dave

quite right....it wasn't a PCMCIA issue, but a DHCP issue Re: Don't be so sure! (David Hinds) Date: 2000, Jan 19 From: Nathan Hartwell MageX

as it turns out, the DHCP server within the Netgear RT328 does not respond properly for dhcpcd or pump to latch on to the offer, yet Win9x will. however, I run dhcpd on my home Linux server and pump grabs the ip info just fine (though I am manually running it with this setup, defined for work and manually run pump after logging in at home) I plan to configure the Linux server at work (as I'm the primary admin anyway) to run dhcpd. I hope to have a worry free setup after that's done.

[ 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 ]