xorg.conf gets reset on 2nd boot after a kernel update

[Dan Hensley]

On Sat, 2005-11-12 at 09:52 -0500, Graham Campbell wrote:

> > > >How do I keep FC4 from doing this incredibly annoying thing?
> > > >  
> > > >
> > > My guess is that you installed the proprietary Nvidia driver and did a 
> > > yum update which included a new kernel got installed for which a 
> > > equivalent Nvidia module was not available. The Nvidia package probably 
> > > has some logic in it to check whether a equivalent module is available 
> > > and if not rewrite xorg.conf to fallback on the Xorg open source 'nv' 
> > > driver  included in Fedora.  There might be some packaging bug that does 
> > > it incorrectly causing your X login to fail. You have to report that to 
> > > the package maintainers if thats the case.
> > 
> > The order of events was,
> > 
> > 1.  yum update to install the new kernel.
> > 2.  Reboot, runlevel 3.
> > 3.  Run sh NVIDIA*.run to install the nVidia proprietary drivers.
> > 4.  Verify xorg.conf.  No changes, everything is fine.
> > 5.  telinit 5.  Everything is fine.
> > 6.  Reboot.  My xorg.conf has been blasted, and I have to hit the Reset
> > button to recover.
> > 
> 
> Have you installed the Livna Nvidia package at any time? It adds
> to /etc/rc.d/init.d an nvidia-glx file which is one of the very few ways
> that things would be changed on a reboot. If you have gone back to the
> nvidia procedure, remove that package.

I've never installed the Livna package.  I'm thinking of putting my own
process init.d just to make sure the xorg.conf file stops getting
clobbered, but that's just a bandaid.

Dan





> 
> > Which package would I submit the bug report against?  Note that I used
> > the exact same procedure on my old computer running FC3, and I never had
> > this problem.
> > 
> > Dan
> > 
> > 
> > 
> > 
> > > 
> > > regards
> > > Rahul
> > > 
> > > 
> >