after kernel upgrade ..

[linux_dude]

i have done a kernel upgrade now my network access is not working. red hat 9 sees the card but does not get a dhcp address, which is a must !! its running kernel 2.42. i can recompile if thats what it will take. when i run the command dhclient it tells me the following are missing: config_packet config_filter.

[bwkaz]

when i run the command dhclient it tells me the following are missing: config_packet config_filter. That means you have to turn those options (CONFIG_PACKET and CONFIG_FILTER) on when you reconfigure your kernel and rebuild it. :)

There is no such thing as a 2.42 kernel version, but I'm going to assume you meant 2.6.24.4, since that's the newest? If so, the CONFIG_PACKET option is in the configuration at Networking -> Networking options -> Packet socket, and the CONFIG_FILTER option doesn't appear to exist.

When you compiled this kernel, what configuration did you start with? Generally it's a good idea to start with an existing kernel's configuration; that way you know you're keeping all the same settings (or at least the ones that still exist in the new kernel).

[linux_dude]

now another problem i turned on the usb but it still fails any idea??

[bwkaz]

Um, USB? The error you were getting here didn't have anything to do with USB, it had to do with the interface that the DHCP client uses to send out its packets before the network card is configured. If you haven't turned on CONFIG_PACKET and recompiled, then you need to do that before DHCP will work at all.

[linux_dude]

ok so i made this post to help me after the kernel upgrade, your solution for dhcp work but now the usb doesn't work.

[John A]

Perhaps you mistakenly disabled USB when you were configuring the kernel options? In any case, what's the output of running 'lsusb' and 'lspci' at the prompt?

[linux_dude]

lsusb gives back "Unkown line at 58 - 2335". And lspci gives back usb controller unknown device 0770, and pci bridge unknown device 0405.

[bwkaz]

OK, I think I get it. (Generally we try to discourage lumping multiple problems into a single thread, but since you're already halfway through troubleshooting it, that's fine. I'd suggest that any further problems get put into their own thread(s), though. :))

On the USB: do you have the .config file from the kernel build? That's either as a file on its own (still inside the kernel build directory), or in the file /proc/config.gz if you turned on the CONFIG_IKCONFIG_PROC option. (You will need to gunzip this file to somewhere else before you'll be able to read it, or use zgrep instead of grep, but it's the definitive kernel configuration. The .config file might possibly be out of date or from a different kernel. The file in /proc is from the running kernel.)

Anyway, grep through that file for _HCD and see what comes up. You should have CONFIG_USB_EHCI_HCD on, and either CONFIG_USB_OHCI_HCD or CONFIG_USB_UHCI_HCD on as well. (The last two are for USB 1.1 devices, and which one gets used depends on which hardware you have. The first one is for USB 2.0 devices. The USB 1.1 drivers can drive USB 2.0 devices, but only at the slower speed.)

If those are set to "y", then support is in the kernel and something else is wrong. If they're set to "m", then they were built as modules: do an lsmod | grep _hcd to see which are loaded. (The module names are ehci_hcd, ohci_hcd, and uhci_hcd.) If none of those modules are loaded, then try loading each of them in turn, and see if the USB device works.

If those settings are "#CONFIG_USB_xxx_HCD is not set" in the config file, then you'll need to reconfigure and recompile again.

What USB device are you testing with? What USB version should it be using?

(Actually, also: what does dmesg | grep -i usb say?)