On Tue, 05 Aug 2008 14:40:24 +0930, Tim wrote:
If having one makes it work, then have one. You don't not have to have
one. I do see your point about not having to do something special to
make things work, but I wouldn't fret too much about having an xorg.conf
file.
I liked not having the
I was away last week and updated my laptop around last
Wednesday while on
vacation (bad move). I noticed that
xorg-x11-server-Xorg-1.4.99-905.2.20080702
and the corresponding xorg-x11-server-common were updated.
I am not sure
whether evdev was also updated then, or whether it had been
I tried that, but it refused to start X with the generated file. The message
said something about some intel module not existing. Very strange, as that
module is not loaded, now that I have sort of solved the problem.
What I did was sftp the old archived xorg.conf from my desktop and now the
On Mon, 2008-08-04 at 12:59 -0600, kwhiskerz wrote:
I am not sure whether evdev was also updated then, or whether it had
been updated a week or so earlier (if so, then it is not the problem,
but most likely the xserver would be).
If the update was through yum, then /var/log/yum.log will list
On Mon, 2008-08-04 at 15:46 -0600, kwhiskerz wrote:
The problem remains, however, as one is not supposed to use an
xorg.conf at all, and it was working just fine without right up until
last week when I installed those updates (likely the xserver ones, I
think).
If having one makes it work,
