Driver/Module build

[harrywangca]

Hello Everyone,

Years ago I built a kernel and put into a production. Right now customer needs to upgrade a hardware and I need to build a new driver for this upgrade hardware. But there is a problem to me, before I built the kernel to put to production, but I lost my kernel build configuration file (.config), if I download the same version kernel, create a new .config file and rebuilt kernel, then based on this to build the new driver, but the new driver won't be inserted into the production, I tried insmod and modprobe, all are failed with unknown symbol or invalid module.

I know if I have the original .config file which was used to build the kernel, it will work.

Can any one help how to solve this kind of issue?

Thank you!!!
Harry

[Whoever]

Depending on how you built the kernel, you may have a pseudo file: /proc/config.gz which contains the .config file.

Why are you not using a pre-built kernel?

[jlehtone]

... upgrade a hardware and I need to build a new driver for this upgrade hardware.

Is that so exotic hardware that nobody else has kernel module for it?

How do say dkms or folks at ELRepo build kernel modules? I don't think that they rebuild the kernel in that process.

[toracat]

You can always get to the kernel config file by looking into the /boot directory. For example the current config is:

/boot/config-3.10.0-1160.92.1.el7.x86_64