Hi Mandrake experts.

I have an IBM eServer xSeries 335 server with a Serverworks chip. This server is currently running Mandrake Multi-Network-Firewall (MNF) which is the 2.4.18-8mdk kernel (I think the same version as Mandrake 8.2). I paid a significant amount of money for this OS in order to get support from Mandrake which I did not receive.

Anyway, I think that 2.4.18 is the latest version of MNF but obviously outdated. In addition, I have this problem , a known incompatibility between my kernel and the Serverworks chip, that I would like to resolve. I should probably mention this server ran fine for just over a year until this problem started last week.

I believe this issue applies to kernels 2.4.18 through 2.4.20. My Mandrake 9.1 workstation has the 2.4.22-10 kernel and I have the installation CD's for that. But, I like the features of MNF, in addition, I have my iptables firewall, proxy server - squid, internet filtering, hardware, and everything set up just the way I need it.

My question is: is it possible to upgrade my kernel from 2.4.18 to 2.4.22 from my 9.1 CD, while preserving the configuration of my existing system, in order to resolve my problem ?

Thank you very much in advance.

--A

Why not! Just back up your config files first.

theres an option someplace to use your old kernel config file as a template for a new kernel compile

Then I'd save that to a new hard drive, and re-setup.

BTW you might as well go for a newer kernel, the current one is 2.6.8, which will give you better/more hardware support and security too.

to disable dma add this to your bootloader line ide=nodma.

It will slow thigs down a bit, I really noticed the difference on my box when I used it.

I think the error message is just a symptom of the problem and disabling dma may not fix it. But you can try it.

I looks more like a memory prob. Ram or HD.

You could try a few bench marking programs to check, memtest86+ is a good ram checker, if you get through all up test 6, it's probably OK.

Live cd's like UBCD and EBCD have them on it, no installing involved. (bootable cd's)

Worst case, you've been hacked, I don't know how to check(iptables?) or fix it. http://www.linuxquestions.org/questi...icle&artid=216

Any way, try the nodma line

see how you go.

PS. there are some good kernel tutes here in the tutorial section, and look at the Linux Documentation Project too.

have you got a fat pipe to the net?

read this post.....

http://www.linuxquestions.org/questi...hreadid=267841

Takes a lot of the hassel out. only upgrades the installed packages, not install everything available.

You might want to check out your firewall prog too before you do it, it may need to be upgraded as well

I have no experience with your type.

cheers

http://www.linuxquestions.org/questi...icle&artid=251

This article talks about using your old kernel config file to configure a new kernel compile.

It is a graphics card install article, but don't be thown, It still talks about the kernel.

read from here.....(just a marker to lead by, but I think you'll see it)

" VERSION = 2
PATCHLEVEL = 4
SUBLEVEL = 26
EXTRAVERSION =

So EXTRAVERSION should equal nothing. If has the word "custom", then this needs to be removed, but it's a good thing to know about for the future*.
6) make mrproper (this sets up your kernel sources properly)
7) make xconfig (this loads the config program, use make menuconfig if in console mode)
8) Now this stage is very important. You can't just pick any old stuff and try to compile. You must use a config file from the working kernel that you usually use. This will be found in the boot directory. Open another terminal window and do an:

ls /boot

You'll most likely see something like config-2.4.22-1.2115.nptl for Fedora Core 1 and config-2.4.20-8 for redhat 9 (although the kernel versions change a lot in redhat 9 releases).
9) Load in the old config file by clicking the "Load Configuration From File" button. Then in the Enter Filename box, enter:


/boot/config.2.4.<whatever>

Obviously, replace <whatever> with the filename you saw listed in step 8.
10) When you click ok, there is no success message. If you are returned to the screen with all the options, then the config loaded fine. If it didn't, it would have shown an error.
11) Now to set the required options:"

hope this helps.

If you want to use the settings from your current configuration, use 'make oldconfig' before 'make xconfig'.

In the 'make xconfig', you tweak the settings from your old configuration, such as new features.

Wow thanks for all the great replies. I will read all that. Sooooo.. what your saying is I **do** or **do NOT** have to back up all my config files? My greatest fear is having to hunt through every directory looking for *.conf and *./config files and find somewhere to put them and remember where they go. (I might miss something important.)

I don't know if this will work in your case, but I have about six different kernel in my machine. I have two computers. One is running 2.4, it has three kernels, just take a look at sixbone.com to see one of them, and my laptop which is the one that has about six different kernels. Any way, this what I do to upgrade to a different kernel:

urpmi --fuzzy kernel

and I get a list of the kernel available, pick the one I want, installe it, and reboot.

Of course, you will be using a CD, probably you will not see as many kernel as I see.

The beauty of the command above is that automaticly uptade my lilo, puts the respective stanza, etc.

Raxxal

To back up, use tar and target /etc/* to/some/place/safe

I find using RCS is handy for backing up config files before changing them. You can have several versions backed up and make a short comment when you check-in a config file. Later, if you need to you can read these comments and restore the version that you want.