The problem is with xfs not starting properly because it can't write to /var/run/xfs.pid as xfs user. If you creart this file like this:
touch /var/run/xfs.pid chown xfs /var/run/xfs.pid your xfs will start and X will start to. The way the xfs was start in -12 was daemon --check xfs xfs -port -1 -daemon -droppriv -user xfs The way the xfs is staring in -14 daemon --check xfs su xfs -c \"xfs -port -1 -daemon\" -s /bin/sh I'm not sure way this was change since it was working fine. Andrew Bielecki -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Charles A Edwards Sent: Saturday, June 15, 2002 12:39 PM To: [EMAIL PROTECTED] Subject: Re: [Cooker] Re: [CHRPM] XFree86-4.2.0-14mdk On Sat, 15 Jun 2002 16:03:47 +0200 "J.A. Magallon" <[EMAIL PROTECTED]> wrote: > > On 2002.06.15 Frederic Lepied wrote: > >--=-=-= > >Name : XFree86 Relocations: (not > >relocateable) Version : 4.2.0 Vendor: > >MandrakeSoft Release : 14mdk Build Date: > >Sat Jun 15 00:27:36 > > Something more has changed. Just after the update, reboot and xfs can > not start. > Unfortunately I also had the pleasure of installing -14 and rebooting. Using NVIDIA drivers nvidia splash would come up and then system would drop out of X, nvidia splash would come up and system over and over. I could not even get to a console but had to do reset. Log showed glxinit errors as well as fixed font failed. I can not operate from pure CmdL I need the X. Luckily I have the CookerSnap ISOs so I was able to rpm -e 14 and go back to -12. My advise to others is if they have already installed -14 DO NOT reboot or restart the X server. If you have not updated DON'T. Charles -------------- Q: How can you tell when a Burroughs salesman is lying? A: When his lips move. ---------------------- Charles A Edwards [EMAIL PROTECTED] ----------------------
