Funny issue after x system update.
 

Today there was a security update for the X System on SUSE 10, I didn't have a problem with it, but my dad did. I'm not completely sure that this is related to the update, but after he updated, his xorg.conf file was missing. I was wondering if anyone else had the same problem. Also, is there an easy way to regenerate the xorg.conf file? For now I just took the xorg.conf.install file and renamed it xorg.conf.

this was your best option.....


...It's allways good to "backup" certain config files before updating anything......

FWIW ... Yes, I apparently had this issue or something like it. Upon a reboot, X was completely hosed, so I just used a recent backup to fix it. Unfortunately, I had made some changes since that backup that required me to play with it a lot.

But, other issues have arisen, and I found the need to reinstall the ATI driver. Now I can't get 3d accel working at all, yet I had had no problems at all doing so previously. None of the variations of the install process for this have worked. I am guessing this has something to do with the patch that was installed, but I haven't a clue what.

on suse,simply run "sax2" or "yast".

Interesting that you mention that. Sax2 won't (or wouldn't) run. It seems to be loading everything and then ... nothing. Not in the process list either. Tried it both from within YaST and at the CLI.

Further, Sax2 has never worked properly for me when configuring for 3D accel, at least not the GUI version from YaST. I have better luck manually editing xorg.conf.

I eventually rolled everything back to a state near the beginning of my initial install, which is extremely annoying, but everything works now as it did.

Same thing happened with me. I never did end up getting the correct configuration in the xorg.conf file. Since I didn't find a quick solution, I ended up backing everything up and doing a fresh install.

One funny thing though, I installed the ATI propriety driver after I reformatted and now I can't access SaX2 at all.

Interesting. This suggests some problem with the ATI driver or perhaps the installer because I had the very same problem after eventually doing exactly what you did.

Luckily I had the 8.18 version of the driver, which I installed with no issues and am using now.