Upgrading kernel help

[eXtremist]

I want to upgrade my kernel.. I am running RH7 and have kernel 2.2.16-22. Now, the configuration of the current kernel is ideal. Is there any way I can import these settings into the new kernel, and then just change the NEW settings?

The reason I ask is that I don't know how this kernel is configured. The last time I upgraded my kernel I configured it as best I could, but I lost some functionality in linux. I want this kernel to WORK.

[Strike]

I really think you should keep plugging away at making your own kernel with your own configuration.

But, if you have the kernel source installed, then just move/copy /usr/src/linux/.config somewhere safe and then when you untar the source of the new kernel tree into /usr/src, just move it back there and the options should all be there.

[eXtremist]

Making my own kernel is cool and all, but thing is, I don't know what half the stuff does.

I don't remember the exact setting, but last time I compiled I read every description of every setting. There were a few that said things like "unless you use xxx you don't need this". So I think "I don't use xxx" so I disable this setting.

Then, when I boot with my new kernel, something doesn't work!
If I knew what the settings of the default RH7 kernel were, then I could probably use that info to build my own kernel, making sure everything I needed was enabled.

[jwilson]

I've just upgraded my RH7 2.2.16 kernel to 2.4.2.

I first unzipped the kernel package, read the INSTALL and /Documentation/Changes file and download all the other upgrades that are needed (i.e. modutils, etc.).

I installed my new kernel under the /root directory, then when I ran "make xconfig", I clicked the "load from file" button and typed in "/usr/src/linux/configs/kernel-2.2.16.config" I had no /usr/src/linux/.config"

Anyway, that worked for me, except a few options that i needed for USB support I had to enable.

[ph34r]

Copy your old (known good) .config from /usr/src/linux to somewhere safe.

Untar a new kernel tree (2.2.18 is latest 2.2 series) and put your .config file in /usr/src/linux again. You can then do 2 things:

1) make oldconfig - keeps all your current settings, only asking about new/changed things

2) make xconfig - keeps all your current settings, gives a nice gui to the whole process, and allows you to add/remove/change as you like.

[eXtremist]

I also tried the "make oldconfig" command, and my new kernel ended up worse than the old one..

:(

[Molecule Man]

You really need to know what all your hardware is and what items should be modules and what needs to be compiled intot he kernel.

The basics is that you need support for your hard drive in the kernel. I find that it is useful to compile in items that I always use. So my ethernet card is in the kernel. I find it works easier if compile in my scsi card. Generally you want to compile in your agp chipset and DRI, but leave your video chipset as a module. You need your filesystem compiled in (technically there are wrok arounds but...). If you only rarely mount your vfat drive then leave it a module (though if you mount them on boot, then you might as well compile in) the same goes for other file systems. I personally do'nt have any ext2 partions, so I leave it as a module, just in case. The best way to think of a module is as a maybe.