Hi all first off i am a newbie to linux bu not to programming.

Now i have installed 3.0 r2 woody vanilla flavour on my laptop and everything is running smoothly including x-server. Now i am currently going through all the manual pages provided by debian.

Now i want to customize the X startup (Chapter 10 ) but, i can't find any config file in my /etc/X11. I am not too familiar with the X11 folder as not much has been written about it in previous chapters i have managed to go on through the chapters and am currently on chapter 13.

Now i did a search using the find command for config and found one in folders inside X11 but not actually in the X11 folder.

Could anyone explain why this is. The Xfree86 version in my laptop is 4.1. The kernel version is 2.2X i haven't upgraded yet since i am still learning linux properly and don't want to cut corners by going straight to the howto's.

I can't help, but is there a reason why you use ye old woody?

Sarge is the latest stable release from debian.

I got it off a friend of mine who i no longer have contact with anymore and can't get help from.

I don't have any comflicts using woody but i guess tha'ts because i'm doing simple stuff at the moment and have not got to the installing of programs or using them yet.

I'm not sure about how to fix your problem, but if you have an internet connection, to upgrade to sarge is very simple. Open up a shell and type apt-get update; apt-get dist-upgrade

edit: Actually I just remembered something about this where some guys went to upgrade their server from woody to sarge and ran into alot of problems, anyone else heard about this?

It's not too big a deal at the moment but i was just wondering why this discrepancy was there.

I only said that because x refused to work for me with woody, but ran fine on sarge (I'm now on etch)

I found that the majority of problems occur when people select the wrong driver for their graphics. I manually went through a couple by editing the XF86Config-4 file until settling with VESA also i found that enabling frambuffer also makes it less likely for X to work unless you know framebuffer works. I also found that selecting 24bit depth would keep X from working. Evem thou i know the card can support such depth must be an issue with the driver at that resolution.