Hardy X autoconfig doesn't like my hardware - can I use a xorg.conf from a previous version?

Asked by Caroline Ford

This is request for help with dealing with the effects of Bug #185440.

The new xorg autoconfiguratiion stuff does *not* like my hardware. Xorg.conf is full of items called "Configured Foo" without explaining how and where they are configured..

As it hasn't configured itself properly and reconfiguring just produces the same can I use a xorg.conf from an earlier version of X? Can you still edit these new almost content-free xorg.confs?

With old(er) hardware there are loads of workrounds that involve changing options in xorg.conf.

I know that the bug has been filed against the Trident driver, but I can't see how it's going to get fixed.. I just want a usable machine!

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Hendrick Musche
Solved:
Last query:
Last reply:
Revision history for this message
Brandon McGlumphy (brandonmcglumphy) said :
#1

Could you please post your current xorg.conf and the one you're wanting to replace it with?

Revision history for this message
Caroline Ford (secretlondon) said :
#2

This is the current xorg.conf. sudo dpkg-reconfigure -phigh xserver-xorg produces an identical file.

xorg.conf (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "InputDevice"
 Identifier "Generic Keyboard"
 Driver "kbd"
 Option "XkbRules" "xorg"
 Option "XkbModel" "pc105"
 Option "XkbLayout" "gb"
 Option "XkbOptions" "lv3:ralt_switch"
EndSection

Section "InputDevice"
 Identifier "Configured Mouse"
 Driver "mouse"
EndSection

Section "Device"
 Identifier "Configured Video Device"
EndSection

Section "Monitor"
 Identifier "Configured Monitor"
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
EndSection

I'm not sure what to add. I've found the following in google:

Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Toshiba TOS5082"
DisplaySize 240 180
HorizSync 31.0 - 48.0
VertRefresh 50.0 - 70.0
Option "dpms"
EndSection

Section "Device"
Identifier "Videocard0"
Driver "trident"
VendorName "Videocard vendor"
BoardName "Trident CyberBlade (generic)"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 16
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport 0 0

Revision history for this message
Best Hendrick Musche (hmu) said :
#3

Its totally safe to alter the xorg.conf to your liking, and to change it to an older state. What the new autoconfiguration does is filling in the gaps if no options are set in the xorg.conf, thats why it is relatively empty. As soon as there are options and values defined in the conf file, X uses these.

Revision history for this message
Caroline Ford (secretlondon) said :
#4

Thanks Hendrick Musche, that solved my question.

Revision history for this message
J Posey (jpo) said :
#5

In some cases X reverts to low resolution and creates a new conf file, instead of using entries manually added to the default file created by dpkg-reconfigure -phigh xserver-xorg. Not even VESA (let alone NVIDIA) works.