major XF86Config problems... please help

[complication]

Hello,

I am using Debian Woody. After upgrading, everything worked fine; X even started up fine. After doing an xf86config X would not start. I complains of not finding modules, so I commented the module lines out, then it gets to the Input Devices section and tells me it is not a valid section. . .

Now it seems silly that xf86config would generate a bogus config file... but that's what it seems is happening, i have gone through xf86config several times...

I would/will post my XF86Config file. . . the problem is I do not know how to copy + paste at the CLI. . . can anyone help me? It would be much appreciated!

Thanks a bunch you guys.
ra

[Trounce]

If X started up, why did u do an XF86Config?
I don't know about Debian....but perhaps it has Xconfigurator. I've always preferred that to any other configurator for X.
Anyway, it is likely that something is incomplete in your Input Device section. It may be missing something as simple as an EndSection or subsection statement. Or it might be referencing a device that's not there. I don't know how to copy from the console. If u have access to a another OS, why not copy the file so the OS has access to it, and open it from in that OS and post it here? I'm sure someone else will clear up the copying text issue..

[thedexman]

which modules did it complain about? which modules did you comment out?

[complication]

Well, X started up but the background was WindowMaker in black and white and in the foreground was Gnome, which was in color, so I wanted to configure everything.

The modules I commented out are

dbe
extmod
type1
freetype
glx

If I leave these uncommented I get errors.

Once those modules are all commented it gets down to InputDevice and that's when I get the error of it being a wrong section...

Also: I have a k6-2 box and an iMac, I have no way of transporting files between the two...

Thanks for the help everyone.
ra

[thedexman]

Did you be sure to comment all of the lines for the extmod module? It comprises a section in and of it self, so it would look like this (for instance):
#SubSection "extmod"
# Option "omit XFree86-DGA"
#EndSubSection

Possibly the nesting of sections got messsed up and that's why it complained.

I would also check to make the ModulePath (in the Files section) has not gotten messed up, and that all the referenced modules exist with in that path.

If you install gpm, you will be able use your mouse to copy and paste at the console.

As far as file transfer, if you have a USB floppy drive for the iMac, both computers should be able to read MSDOS floppies (or zip disk, or cdr, etc). If the iMac has a NIC (do they?) just set up an FTP server on the Linux machine.

[ 14 November 2001: Message edited by: thedexman ]

[complication]

I did comment out all the subsections. My module path is correct, but the files for the modules are not in the directory... (not positive but when I looked at it I couldnt find any relevant files to the modules in the XF86Config file).

Right now I am at school, so once I get home I will install gpm and post my XF86Config file.

Also, I don't have both my boxes networked, I have them running off the same IP so only 1 machine can be connected to the net at the same time (i only have 1 cat5 cable running into my room), though I shall be investing in a hub soon.

thanks,
ra

[DMR]

If you think your XF86Config file is borked, you could always rename it and run your X configuration utility to generate a new, clean XF86Config.

[complication]

Here is my XF86Config file: Section "Module"

# This loads the DBE extension module.

Load "dbe" # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection

# This loads the Type1 and FreeType font modules
Load "type1"
Load "freetype"

# This loads the GLX module
# Load "glx"

EndSection

# ************************************************** ********************
# Files section. This allows default font and rgb paths to be set
# ************************************************** ********************

Section "Files"

# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.

RgbPath "/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#

# FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"

# The module search path. The default path is shown here.

# ModulePath "/usr/X11R6/lib/modules"

EndSection

# ************************************************** ********************
# Server flags section.
# ************************************************** ********************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

# Option "NoTrapSignals"

# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

# Option "DontZap"

# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.

# Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

# Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client.

# Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.

# Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

# Option "AllowNonLocalModInDev"

EndSection

# ************************************************** ********************
# Input devices
# ************************************************** ********************

# ************************************************** ********************
# Core keyboard's InputDevice section
# ************************************************** ********************

Section "InputDevice"

Identifier "Keyboard1"
Driver "Keyboard"
# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

# Option "Protocol" "Xqueue"

Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"

# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"

# These are the default XKB settings for XFree86
# Option "XkbRules" "xfree86"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

# Option "XkbDisable"

Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"

EndSection


# ************************************************** ********************
# Core Pointer's InputDevice section
# ************************************************** ********************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "PS/2"
Option "Device" "/dev/psaux"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

# Option "Protocol" "Xqueue"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

# Option "BaudRate" "9600"
# Option "SampleRate" "150"

# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"

# ChordMiddle is an option for some 3-button Logitech mice

# Option "ChordMiddle"

EndSection


# ************************************************** ********************
# Monitor section
# ************************************************** ********************

# Any number of monitor sections may be present

Section "Monitor"

Identifier "My Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

HorizSync 30-56

# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

VertRefresh 50-120

EndSection


I didn't post the whole file, just the parts i get errors on. Any insight on this problem? Thanks a lot!
ra

[complication]

This is the actual error I get:

XF86Config: /usr/X11R6/lib/X11/XF86Config
(**) stands for supplied, (--) stands for probed/default values
(--) no ModulePath specified using default: /usr/X11R6/lib/modules
dbe: Unknown error loading module

Config Error: /usr/X11R6/lib/X11/XF86Config:48

SubSection "extmod"
^^^^^^^^^^^
Module section keyword expected
giving up.
xinit: Connection refused (errno 111): unable to connect to X server
xinit: No such process (errno 3): Server error.


Hope this may help.
Note: the XF86Config file above is what xf86config generates, i have not edited it at all.
Thanks again
ra

[thedexman]

Well, what if /usr/X11R6/bin/X linked to?
Try running
ls -l /usr/X11R6/bin/X

It should be linked to /usr/X11R6/bin/XFree86

[ 15 November 2001: Message edited by: thedexman ]

[thedexman]

I'm guessing you were running X 3.3.6 before the upgrade?

Edit: I'm a dumbass.

[ 15 November 2001: Message edited by: thedexman ]

[complication]

thedexman: i am not quite sure what you mean; my /usr/X11R6/bin/ directory contains both files X and XFree86. X is not linked to XFree86 and obviously I cannot make X a link to XFree86 because it will not create a new file...

or am i totally missing something here?

i know this may sound a little out there but do you think i my installed version of X is not up to date with xf86config?
when i run 'X -version' to check the version the text scrolls past the screen so fast I cannot see the output; its at the very top. i think there is a way to tell that command to make a file and put the out put in there, but I am unaware of the program...any help here? or at least somehow let me check my X version? i am pretty sure xf86config is version 4.1.0 . . .

thanks once again...
ra

[DMR]

4.x.x versions of XFree86 use the XF86Config-4 configuration file, as opposed to the XF86Config file used by versions 3.x. If you did an upgrade, make sure you're using the correct config file.

[DMR]

Originally posted by complication:
<STRONG>This is the actual error I get:

XF86Config: ..../usr/X11R6/lib/X11/XF86Config
</STRONG>And I think that's the clue. With a fresh (clean) install of XFree86 v4.x, you'll only have XF86Config-4; there will be no XF68Config. I think you're last suspicion is on the right track- you seem to have some cross-referencing going on between your new version and the old (probably 3.3.6, yes) version.

[thedexman]

What is /usr/X11R6/bin/X linked to right now? For XFree86 versions 4.x, it should be linked to /usr/X11R6/bin/XFree86. I the 3.x versions it would be linked to the particular server for your card.

Your config file will not necessarily be named XF86Config-4 rather than XF86Config, because the locations are different now as well. they added the /etc/X11 directory, where they put the config file now.