Messages in this thread | | | Subject | Re: Upgrading Kernel kills X ... | From | john stultz <> | Date | 20 Nov 2003 16:46:23 -0800 |
| |
On Thu, 2003-11-20 at 10:25, Brian McGrew wrote: > I have here a very weird situation which I'm hoping that someone can help me > resolve. I'm running RedHat 9.0 on a Dell Poweredge 1600 server. Now the > stock install of RedHat 9.0 gives me the 2.4.20-8(smp) kernels accordingly. > Now if I run RedHat's up2date and pull a new kernel from there, I'm fine. > > Where I run into problems, is two fold and this is where it gets confusing. > I have tried manually upgrading my kernel in a couple different ways. The > first is that our company develops software for Linux (RedHat 7.3) and > therefor, we have a custom kernel package that we install as an RPM. Works > great on RedHat 7.3 with this Dell PE1600. The second method is installing > kernel source and building it myself (2.4-20 as well as 2.6.0-test9). If I > build and install a kernel myself or add our typical rpm kernel, my X server > is toast. Someone told me to double check that I have framebuffer support > turned on, so I did and that did not resolve the problem.
I've not found the cause of this, but I've seen a similar issue w/ RHEL 3.0. It seems to have to do w/ glibc being compiled to use some feature (futexes?) which is not available in self-compiled kernels. I found replacing the i686 compiled glibc w/ the i386 compiled package solved the issue for me. Your mileage may vary.
I'd be interested to hear the real cause.
thanks -john
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |