Red Hat Bugzilla – Bug 314601
xen kernel cannot start X server
Last modified: 2008-11-24 06:23:07 EST
Description of problem:
If I start xen kernel 18-8.el5xen or 18-8-1-14.el5xen, the X-server won't start.
With the non xen kernel there is no problem.
I have this problem with both the vesa drivers as with the nvidia ones.
With the vesa X11 drivers the screen goes blank, but the system remains responsive.
With the nvidia X11 drivers gdm is unable to start and I'm left with a message
that X server is reverting to a default config. At that time the Xserver seems
able to start.
My videocard is a Gforce 8600GTS.
Version-Release number of selected component (if applicable):
nvidia driver 100.14.19 (latest)
Steps to Reproduce:
Thanks for the bug report. We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf; note, that we are
interested only in free drivers) and X server log file (/var/log/Xorg.*.log) to
the bug report as individual uncompressed file attachments using the bugzilla
file attachment link below.
Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
a) don't talk about nvidia driver to me; clear your computer from files it left you (http://fedoraproject.org/wiki/Xorg/3rdPartyVideoDrivers; especially if you didn't use packaged drivers, but the ones from nvidia.com website) and retest with vesa drivers.
b) could we get these files I asked for in the previous comment, please?
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.
Closing as INSUFFICIENT_DATA.