Description of problem: When I click on the Red Hat Network Alert notification tool it tells me the following: "Your system is currently running kernel-2.4.21-4.EL, but the newest installed kernael is kernel-2.4.21-20.EL. It is recommended that you reboot at the first opportunity to test this new kernel." So I reboot and choose this new kernel version but I get the following error: "I cannot start the X server...." It asks me if I want to see the error diagnostics I say yes and it gives me some info which I have no idea about and then it asks me if I want to run the X server configuration utility. I say yes but it comes back with the ssame error message. So essentially I cannot get the GUI interface to come up if I select it to use the new kernel. I apologize if I sound vague but I am very, very, very new to Linux and am just finding my way around. Version-Release number of selected component (if applicable): kernel-2.4.21-20.EL How reproducible: Rebbot and choose the new kernel Steps to Reproduce: 1.Reboot 2.Chose new kernel 3. Actual results: Do not get GNOME gui Expected results: WOuld liek to get my GNOME window Additional info:
Created attachment 104634 [details] Xfree86.0.log
Created attachment 104635 [details] XF86Config
Does the error you see have anything to do with agpgart?
I have no idea.. That is why i posted the error here hoping someone could tell me.
Ok... I'm not seeing any errors in the attachments you included. I'm wondering if perhaps there were errors that went to the screen but did not get into the log you attached. I would suggest, if this is something for which you have any sort of time constraint, and you have a valid entitlement, that you contact Red Hat's support at 800-RedHat1, or http://www.redhat.com/support.
I just tried it again...and here is what it send to the screen.. (EE) GARTInit: Unable to open /dev/agpgart (No such device) (EE) 1810(0): AGP GART support is not available. Make sure your kernel agpgart support or that the agpgart kernel module is loaded. (EE) Screen(s) found, but none have a usable configuration. Fatal Server Error: no screens found There is no time constraint for this issue..I can still use the old kernel till we find a solution thanks
Ah! Yes, it's agpgart. In which case, this is a known bug, and it's being worked on. I shall duplicate this against the one that's being worked, which I believe you ought to be able to see as well. *** This bug has been marked as a duplicate of 131907 ***
Thanks so much Suzanne. Just one question though...should I download the "fixed" kernel submitted by a user or should I wait for the official relase from redhat? Sorry for sounding so clueless but I am...:) thanks...
Depends on how willing you are to be working from non official packages, really, and on how impatient you are to have the fix. Me, I'd probably wait, but I tend to avoid running code that is not yet officially released on a machine I am doing active work with. That said, if you decide to use it, it seems to be code with a very low probability of causing problems.
Alright.. I guess I will wait for RedHat's official release...question is..how long will that be? Are we talking a few weeks, a few months, a few years? Also, how will I know when the release is available? Will I be sent an email because I have a case opened or do I have to keep checking back? thanks
Should be before the end of the year. Are you set up with RHN? That is how updates are distributed, and how people are told that there are updates available. To check, run 'up2date'. If it tells you that you need to be registered, or something about needing a channel, you are not yet registered. In this case, you will need to activate your subscription. This can be done through the following site: https://www.redhat.com/apps/activate/ After that is done, you will need to register your machine. There is likely instructions for this on the site above, after you've activated your subscription. If not, let me know.
A fix for this problem has just been committed to the RHEL3 U4 patch pool this evening (in kernel version 2.4.21-22.EL). *** This bug has been marked as a duplicate of 131907 ***
An errata has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2004-550.html