While building a custom kernel using 2.2.5-22 i used the following steps. make mrproper make xconfig In xconfig i noticed that when i save the configuration with either the <store configuration> or <save and exit> buttons i received the following message in the xterm window. ERROR - Attempting to write value for unconfigured variable (CONFIG_FB_ATY) After experimentation found that this error can be replicated by doing only the following make mrproper make xconfig <console drivers> 'do not change anything! <main menu> <store configuration> or <save and exit> Do not know if this is related, but have been unable to gen a custom kernel with 2.2.5-22 if anything is changed with xconfig. All attempts so far result in hang on reboot at module dependencies, or depmod -a 2.2.5-22 with unresolved dependencies. And yes, before you ask, i deleted /lib/modules/2.2.5-22 before i did make modules_install.
I would recommend "make menuconfig" instead. "make xconfig is hardly maintained these days...
"make xconfig is hardly maintained these days... If this is true remove xconfig from the distribution, as it is the one most people will attempt to use due to the gui interface. Leaving a guaranteed failure in an important aspect to your product is ensuring the failure of the adoption of that product.
To get rid of the hang on depmod, upgrade to the latest initscripts from Raw Hide - there's a very silly bug in it.