Re: X Display unable to start under Fedora Core 2

From: noi (noi_at_siam.com)
Date: 11/11/04


Date: Thu, 11 Nov 2004 17:47:20 GMT

On Wed, 10 Nov 2004 09:38:21 -0700, John McFee thoughtfully wrote:

> I just yum upgraded my 5 year old Dell 40 MHz computer (ATI Mack 64
> graphics card, Dell 1226H 19" CRT) from Fedora Core 1 to FC2. (I have yum
> upgraded other computers in the last while from FC1 to FC2 with no
> trouble.) The upgrade went fine and everything worked OK for the next 2
> days (shut down and started up several times, operated under Gnome
> desktop, no problems).
>
> Yesterday, on booting up, all was normal until it got to the part where it
> should generate the login gui screen. The screen went blue (with the hour
> glass turning), then switched back to the login text screen, then back to
> the blue screen, etc. This continued for six tries and then a screen
> appeared that said:
> "The display server has been shutdown about 6 times in the last 90 sec, it
> is likely that something bad is going on. I wait 2 minutes before trying
> again on display :0."
>
> This whole process (flashing attempts at X windows, then error message)
> kept repeating roughly every 2 minutes.
>
> In between error messages, I logged in as root in the text mode and
> loooked at the /etc/X11/xorg.conf file. It had been generated by
> system-display-config and looked fine. I then looked at the output of
> /var/log/xorg.0.log. It looked normal, no errors or warnings until the
> very last lines:
>
> Right after loading module pcidata (which went OK), it said:
>
> Fatal Sever Error
> xf 860 Open Console: cannot open virtual console 7.
>
> I logged out and shutdown, then rebooted under the old FC1 kernel
> (2.4.22.2194.npt1) and everything was just fine! Booting under my new FC2
> kernel (2.6.8-1.521) gives the same problem.
>
> I am stumped. This occurred well after the upgrade, as though a file got
> clobbered, but I have no idea what. Hardware must be fine, since it works
> under the old kernel. And for 2 days, it worked under the new kernel. Any
> help is really appreciated.
>
> John McFee

I didn't have a problem with multiple attempts to load X. There were
times that .Xauthority ownership changed while sudoing k3b to root
which prevented X from starting. I used sudo in a Failsafe session to
change ownership back to user.

Also suggest googling the complete error message if you diff Xorg.0.log to
Xorg.0.log.old and there's no difference.



Relevant Pages

  • Re: upgrade to Solaris 10 11/06 fails - problems with mirrored disks
    ... Solaris 11/06 using a custom jumpstart profile. ... The upgrade fails ... The specified root and/or boot was not found or was not upgradeable ... change the error message. ...
    (comp.unix.solaris)
  • Re: [opensuse] mkinitrd failure (raid related?)
    ... Since you claimed you installed kernel from KOTD, I'm assuming you installed all of required dependencies. ... It seems, according to your menu.lst file, that you've been doing upgrade after upgrades. ... After all this is done, just issue as root, the mkinitrd command and check if all builds well. ...
    (SuSE)
  • X Display unable to start under Fedora Core 2
    ... The upgrade went fine and everything worked OK for the next 2 ... This whole process (flashing attempts at X windows, then error message) ... FC2 kernel gives the same problem. ...
    (comp.os.linux.hardware)
  • Re: The problem of SATA in Thinkpad T43
    ... the VFS error message you posted above doesn't ... VFS: Cannot open root device 03:03 ... kernel parses that argument and tries to mount that partition as /. ...
    (comp.os.linux.misc)
  • Re: The problem of SATA in Thinkpad T43
    ... the VFS error message you posted above doesn't ... VFS: Cannot open root device 03:03 ... kernel parses that argument and tries to mount that partition as /. ...
    (comp.os.linux.misc)