I _strongly_ suggest you do not use any kernel configuration utility other than those that come as a part of the kernel distibution.
Most people find menuconfig to be easy and fast. Open a console window. then -
When you type the last, you will get a "CHUI" interface to configuring the menu. Just go through each option in turn. Up and down arrows move between options, left and right arrows move between <Select> <Exit> and <Help>. Enter will Select, Exit or Help depending on which is highlighted.
When an option is highlighted, the 'N' key disables, the 'Y' key enables, and the 'M' key enables and builds it as a module.
When you are done with all your options, keep selecting <Exit> and hitting enter till it asks you if you want to save your configuration. Select <Yes> if you are happy, or <No> if not, and hit enter.
For sanities sake DO THE FOLLOWING!
Edit Makefile. At the top of the file you will see four lines, VERSION, PATCHLEVEL, SUBLEVEL and EXTRAVERSION. Set EXTRAVERSION equal to something, like b2 for build 2. Save your edit and exit.
Now continue at the command line:
Then copy arch/i386/boot/bzImage to /boot/<somefile>, where <somefile> is replaced by a unique name, such as vmlinuz-4.22.b2
Notice the b2 here matches the b2 that we used for EXTRAVERSION. Why do this? Because this way, if you screw something up, you can roll back to your working version. When you run 'make modules_install' it is going to put your modules in a directory called /lib/modules/V.P.S.E, where V equals VERSION, P equals PATCHLEVEL, S equals SUBLEVEL and E equals EXTRAVERSION. Because you changed EXTRAVERSION your current module directory remains untouched.
Notice that the name of your kernel, the name of the module directory, and the result of 'uname -r' all match up.
Now go ahead and update your grub or lilo and try it out.