I would like to hear your opinions on this. Which kernel should I choose for stability? So far I've had lockups with 2.2-series on 2 different computers (Debian). Also had lots of lockups with 2.6-kernels on a total of 5 or 6 computers (Mandrake, Fedora Core 2). So is it worth to try 2.4?

I was thinking of adding 2.4-kernel alongside the 2.6-kernel in Mandrake 10.

I love Linux REALLY a lot, just these annoying, very rare lockups are the only problem...


P.S. I like Fedora Core 2 a lot, but it seems to be the most unstable distribution ever (at least to me). The lockups in general can differ. Sometimes X freezes completely, so that it can't be killed. But I can SSH the computer from the network and unmount all partitions, then reset. However, often the computer freezes so badly, only the reset-button works anymore.

The lockups are totally random. Sometimes the computer is just sitting there idle, sometimes I'm using it when it happens.

Last time I had that problem, I had the wrong IDE chipset selected for the kernel. I run Gentoo and KDE and I have not had that problem since I fixed my boo boo.

Linux is really stable unless you use unstable packages. I would suspect that something is wrong with that kernel not the GUI itself.

On the hardware side, you may want to check that memory. That will make one really upset too. Does all kinds of weird stuff. It may not show up untill that cache starts to really kick in and fill up the memory.

Thats my thoughts and opinion. They may suck but there they are.

Later

First I also suspected a hardware problem, but it can't be the case on all these computers. I've had broken memory 2 years ago and it really does create all sorts of weird stuff and is difficult to notice.

I have no doubts against Linux's stability, I know many servers are running it for hundreds of days. It is also possible that I do not understand how to configure it correctly, I've always just used the kernel that comes with the distro.

I guess what I wanted to hear, would be some experiences (about stability) of 2.4- and 2.6-kernels.

I have used both versions with little problems. I have ben using 2.6.* ever since I put Gentoo on this rig. It is rock solid with mine anyway.

That kernel is very tricky. It has to be right or it will not work or will be flakey. That to me is the hardest thing for someone new and is also the most important.

I think there is a kernel how to here somewhere. Found it for you.

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

Give that a reading over. I would use the 2.6 if your rig is fairly new. It has newer drivers and such.

Post back.

Thanks, I will give a kernel recompilation one more try then.

I've tried it many times before, but always something was missing or the kernel after compilation was "too big to fit into memory", etc. and couldn't load.

I've never had a kernel problem with 2.4/6.x, even with multiple-month uptimes - are you sure the problem was with the kernel? my first guess would be a hardware problem. also, a lockup in X can be caused by many things. the Debian instability problems are a bit surprising, but I agree RH is very unstable, at least in my experience (and had particular instability problems with some RH hardware-detection app, can't remember it's name).

here's another great 2.6 thread (in Slack forum):
http://www.linuxquestions.org/questi...hreadid=127095

Since he is new to configuring a kernel, I suspect that something is not selected that should be or selected that should not be. It is not the kernels fault, it just is not configured properly. I had the exact same problem when I had the wrong IDE chipset selected. The kernel was the problem but it was only doing what I configured it to do. It did random lock-ups just like that. It was weird. I narrowed it down by watching what it was doing when it locked up. I noticed it did it during heavy drive activity. Started diggin.

He needs to research hardware and go through each screen and make sure what he needs is there and what he doesn't is not there. It is not just download and then compile and hope for the best.

It could be hardware but if it runs otherwise, windoze or something, then I would start with the kernel, especially since he is new at that part.

Later