I am currently running RedHat 8.0. The default build works fine for connectivity using both a wireless (Linksys WPC11) and wired (NetGear FA510) PCMCIA card.

I upgraded the kernel and while doing the build must have gotten something wrong. Whenever I try to bring up either interface I get a message saying they couldn't activate the card.

When I look at /var/log/messages this is what I see:

Jan 19 18:26:26 localhost kernel: eth1: found link beat
Jan 19 18:26:26 localhost kernel: eth1: autonegotiation complete: 100baseT-FD selected
Jan 19 18:27:11 localhost dhclient: socket: Protocol not available - make sure
Jan 19 18:27:11 localhost dhclient: CONFIG_PACKET (Packet socket) and CONFIG_FILTER
Jan 19 18:27:11 localhost dhclient: (Socket Filtering) are enabled in your kernel
Jan 19 18:27:11 localhost dhclient: configuration!
Jan 19 18:27:11 localhost dhclient:
Jan 19 18:27:11 localhost dhclient: If you did not get this software from ftp.isc.org, please
Jan 19 18:27:11 localhost dhclient: get the latest from ftp.isc.org and install that before
Jan 19 18:27:11 localhost dhclient: requesting help.
Jan 19 18:27:11 localhost dhclient:
Jan 19 18:27:11 localhost dhclient: If you did get this software from ftp.isc.org and have not
Jan 19 18:27:11 localhost dhclient: yet read the README, please read it before requesting help.
Jan 19 18:27:11 localhost dhclient: If you intend to request help from the dhcp-server@isc.org
Jan 19 18:27:11 localhost dhclient: mailing list, please read the section on the README about
Jan 19 18:27:11 localhost dhclient: submitting bug reports and requests for help.
Jan 19 18:27:11 localhost dhclient:
Jan 19 18:27:11 localhost dhclient: Please do not under any circumstances send requests for
Jan 19 18:27:11 localhost dhclient: help directly to the authors of this software - please
Jan 19 18:27:11 localhost dhclient: send them to the appropriate mailing list as described in
Jan 19 18:27:11 localhost dhclient: the README file.
Jan 19 18:27:11 localhost dhclient:
Jan 19 18:27:11 localhost dhclient: exiting.

I have checked and the new kernel does have the to CONFIG_... parameters marked as yes. But I just can't seem to get it to load a DHCP address.

Any thoughts?

TIA

Wade

One follow-up. If I boot back into the original kernel, everything works fine.

-Wade

"Packet Socket" and "Socket Filtering" must be set to "Yes" in "Networking options" (xconfig).

>Jan 19 18:27:11 localhost dhclient: socket: Protocol not available - make sure

Sounds like your missing something, do you have dhcp client installed? enabled? Did you leave out something else in the kernel like the right PCMCIA socket support? Did you build the pcmcia driver into the kernel or modularize it? Is there a DHCP server? Does the network show activity when the card starts, like activity on your hub showing the DHCP request? Does it work if you assign an IP address?

This could help pin it down. Iif it works with an assigned address then you have a problem in the DHCP client setup somewhere. If it shows activity on your hub then it may not be getting a response from the DHCP server on your network. If the driver is not modularized it may not work right since the card can be removed though I'm not 100% on that. Try manually starting the card by modprobe {netcard module name} and then "dhcpd -t 10 -d eth1" or "ifconfig eth1 10.10.10.10 255.255.255.0"

To answer the above. Yes, there is a DHCP client installed, and it seems operational. If I boot into the original kernel, I do get an IP address, and the error messages above are from the dhclient program, which I assume is DHCP. PCMCIA socket support is enabled in the configuration, and the drivers are modularized. When I do an lsmod after booting, I do see the appropriate modules loaded. The DHCP server is working fine (My other 3 machines don't have any issues, and it works with the original kernel). If I manually assign an IP address to the card it works fine. (In both kernels).

Wow, good info on the response! So you have an issue with DHCP not working if you can manually assign an IP address. One option since I'm not as familiar with redhat is to take the happy-clicky-gui approach and run whatever the network configuration tool is that redhat uses which will hopefully change any config files that may need to match whatever options are different with the new kernel. Also I'm not sure I have much more info for you if that doesn't work but it might help someone find an answer if you posted what versions the old and new kernel were? I know that redhat modifies the kernel source so if you have the RPM or stock install kernel and switch to a plain kernel some things will change, you can spot the plain kernels because they have versions like 2.2.8 or 2.4.20 while redhat modified ones have numbers like 2.4.18-4 or 2.2.10-12

Thanks. I have tried to adjust the DHCP configuration, both through 'neat' (the GUI interface), and through manually adjusting the actual files. Neither seemed to work. Downloaded the newest DHCP software from the producers website, with no success after install. I also tried recompiling the newer kernel with the .config file from the original kernel. Figuring that should be the same config then. Still no dice. The original kernel is 2.4.18-4, and I have tried 2.4.19 and 2.4.20 (both downloaded from ftp.kernel.org). The whole reason for the recompile is to incorporate a patch for USBD Network (Encapsulated) Host to Host Link. This will allow connectivity to my Zaurus. And it didn't work with the RedHat SRPMs for the kernel. I will just keep plugging away until I figure something out. Thanks for the thoughts.

Sorry for not reading your message more clearly... You *did* say after all that the required flags were enabled.

It's just that I compiled the latest kernel (2.4.20) on my RH8 system 2 days ago, and I got the exact same message. I went into xconfig, enabled Socket Filtering, and then it worked. Now I have another problem (see http://www.linuxquestions.org/questi...threadid=42093) but that's another story.

BTW, where did you get the .config file from the old kernel from? The kernel SRPMS?

I the config file was located in /usr/src/linux-2.4/ I am not sure where it came from, I assumed it was created when the OS was installed, since it looked right as far as the modules that were loading, etc.