Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place! |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
|
07-19-2005, 11:12 PM
|
#1
|
LQ Newbie
Registered: Jul 2005
Distribution: Slackware 10.0
Posts: 12
Rep:
|
Screen Resolution problems connected with xorg.conf and xorgconfig with Slackware 10
Hey Everyone!
First time poster in here. Looks like a nice forum, good job!
Anyway, on with my problem.
I'm a new linux user with an apple background under their distribution of unix and X11 operating systems.
My hardware, unfortunately, is largely unknown to me. I have an old Dell computer (donated), 433mhz, 90MB RAM... and that's really all I know about it.
I recently completely reformatted the harddrive with cfdisk off of the Linux Format boot disks of slackware 10.0. Everything is cool, give myself a username, set the root password etc. etc. and then I boot into X11 with startx using the KDE window manager and I find myself staring at a 640x480 desktop. Not so excited anymore.
I poke around a little and find that I'm supposed to xorgconfig for a basic setup before I want to go too poweruser so I do that. The only thing I don't know about is what kind of video card I have because it's whatever came with the computer and I don't have the computer information on that. It's not external though, it's internal. Anyway, I check out the xorg.conf file in /etc/X11/ and it looks fine then I startx again and I boot into a 300x120 screen! Not only that, but this is the "only" screen res available, I can't even CTRL-ALT-'+' through the screen resolutions, let alone switch through them with the screen resize and rotate utility.
The weirdest thing is that 300x120 doesn't even show up in the xorg.conf file, and if I delete that file, the problem is immediately fixed except that my only choice is still 640x480 at 60Hz.
This is my entire xorg.conf file
Code:
# File generated by xf86config.
#
# Copyright (c) 2004, by the X.Org
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of X.Org shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# X.Org.
#
# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************
# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
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 "speedo"
Load "freetype"
# Load "xtt"
# This loads the GLX module
Load "glx"
# This loads the DRI module
# Load "dri"
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/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/TTF/"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/"
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><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.
# Option "DontVTSwitch"
# 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 X.Org
# Option "XkbRules" "__XKBDEFRULES__"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xorg"
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/mouse"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# 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
# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the XF86Config man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# **********************************************************************
# Monitor section
# **********************************************************************
# Any number of monitor sections may be present
Section "Monitor"
Identifier "mainMonitor"
# 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 31.5 - 64.3
# 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-100
EndSection
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# Standard VGA Device:
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
EndSection
# Device configured by xf86config:
Section "Device"
Identifier "vidCard"
Driver "vga"
# unsupported card
#VideoRam 4096
# Insert Clocks lines here if appropriate
EndSection
# **********************************************************************
# Screen sections
# **********************************************************************
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "vidCard"
Monitor "mainMonitor"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
EndSection
# **********************************************************************
# ServerLayout sections.
# **********************************************************************
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
Section "ServerLayout"
# The Identifier line must be present
Identifier "Simple Layout"
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
Screen "Screen 1"
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
# Section "DRI"
# Mode 0666
# EndSection
This problem also shows up no matter which default depth I choose.
Any help would be much appreciated!
Tim
|
|
|
07-19-2005, 11:25 PM
|
#2
|
Moderator
Registered: Apr 2002
Location: earth
Distribution: slackware by choice, others too :} ... android.
Posts: 23,067
|
Hi, and welcome to LQ,
Thanks for the praise :}
Have a look at
grep "Using config file" /var/log/Xorg.0.log
What does it use, the one you're editing?
Cheers,
Tink
Last edited by Tinkster; 07-19-2005 at 11:26 PM.
|
|
|
07-19-2005, 11:53 PM
|
#3
|
LQ Newbie
Registered: Jul 2005
Distribution: Slackware 10.0
Posts: 12
Original Poster
Rep:
|
Well, therein lies the rub.
k... tried both of these things...
Code:
$ grep "Using config file" /var/log/Xorg.0.log
Code:
$ less /var/log/Xorg.0.log | grep "Using config file"
As well as the following command as root
Code:
$ ls -R / | grep "xorg.conf"
these are the strange things that happen.
the first two commands print nothing, and that third command returns that the only xorg.conf files that exists on the system is the one that currently resides in my home folder because I decided to generate one without putting it someplace that X would notice so as to be able to talk with you wonderful people in a screen that is decidedly NOT 300x120.
Does that confuse you? Because it sure as hell confuses me!
Thanx for your help!
Tim
|
|
|
07-20-2005, 03:43 PM
|
#4
|
LQ Newbie
Registered: Jul 2005
Distribution: Slackware 10.0
Posts: 12
Original Poster
Rep:
|
just as a small update I also tried as root
Code:
find / -name "xorg.conf" -print
and it only printed the xorg.conf file in my ~ directory.
Tim
|
|
|
07-20-2005, 03:58 PM
|
#5
|
Senior Member
Registered: May 2005
Distribution: Ubuntu with IceWM
Posts: 1,775
Rep:
|
This part is what you need to fix. Find out from your monitor's manufacturer/manual what the vertical and horizontal ranges are supposed to be:
Quote:
Section "Monitor"
Identifier "mainMonitor"
# 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 31.5 - 64.3
# 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-100
EndSection
|
|
|
|
07-20-2005, 05:08 PM
|
#6
|
LQ Newbie
Registered: Jul 2005
Distribution: Slackware 10.0
Posts: 12
Original Poster
Rep:
|
Thanx for the quick response!
I'm not at my linux computer at the moment so I can't try your suggestion but just as a quick response from a noob, I'm confused as to what exactly you're refering to. The Horizontal Refresh rate is 31.5-64.3, and the Vertical Refresh is 50-100. The exact manual specs are 30-64. Now I'm gonna have to try to switch the Horizontal Referesh to the exacts specs, but if you care to, why would that small difference be causing this particular problem?
If there's a document out there that has this kind of info in it, could anyone point me to it? Just to satisfy my own curiosity.
Thanx again!
Tim
|
|
|
07-20-2005, 06:35 PM
|
#7
|
LQ Newbie
Registered: Jul 2005
Distribution: Slackware 10.0
Posts: 12
Original Poster
Rep:
|
OK!
tried the new suggestion out. This is the new Monitor Section
Code:
Section "Monitor"
Identifier "mainMonitor"
HorizSync 30 - 64
VertRefresh 50-100
EndSection
Good news and bad news. Now the screen res does not do that weird 300x120 res, but it still only supports 640x480 at 60hz.
So, partial defeat of the problem and partial defeat of me...
Just as an aside that might be of use, I noticed upon starting up today that I had "passed an undefined mode number" to the system (or something to that effect, I can probably copy it down if it is useful in anyway) that had something to do with the display. Is that a possible cause of this problem, or does it have nothing at all whatsoever to do with this problem?
Thanx so much again! I'm still baffled
Tim
|
|
|
07-20-2005, 07:15 PM
|
#8
|
Senior Member
Registered: Jul 2005
Distribution: Slackware
Posts: 2,012
Rep:
|
1. move /etc/X11/xorg.conf to a safe location
2. run xorgsetup
3. fine-tune with xorgcfg -textmode
4. test X out
|
|
|
07-20-2005, 11:24 PM
|
#9
|
LQ Newbie
Registered: Jul 2005
Distribution: Slackware 10.0
Posts: 12
Original Poster
Rep:
|
once again, good and bad news
the xorgsetup command did better in regards to my hardware. it automatically looked some of that stuff up which was nice.
Then, I fine tuned it with xorgcfg -textmode like you suggested, and it did indeed make some changes to the file.
then I started into X, and the same thing happened. 640x480 only option.
good news is that grep "Using config file" /var/log/Xorg.0.log now returns /etc/X11/xorg.conf
I really am a nearly complete noob when it comes to this stuff. X11 on my ibook doesn't even use xorg.conf, or it has found a way to very neatly hide it from root. I used Enlightenment as my WM over there and it always seems to work. My point is that I don't even know where to begin "playing" with this part of X and I simply haven't had time to sit down with the man pages... Is that the next step?
Thanks for everyones help so far!
Tim
|
|
|
07-23-2005, 12:06 AM
|
#10
|
LQ Newbie
Registered: Jul 2005
Distribution: Slackware 10.0
Posts: 12
Original Poster
Rep:
|
Have I become unhelpable? LOL
Tim
|
|
|
07-23-2005, 01:26 AM
|
#11
|
Moderator
Registered: Apr 2002
Location: earth
Distribution: slackware by choice, others too :} ... android.
Posts: 23,067
|
Maybe we're putting too much emphasis on the monitor section.
Chances are that you got yourself a video card with only 512KB
of RAM, in which case it wouldn't matter what you try to do in
terms of resolution.
Let's examine your video hardware! :)
lspci - what do you get?
Cheers,
Tink
|
|
|
07-23-2005, 03:42 PM
|
#12
|
LQ Newbie
Registered: Jul 2005
Distribution: Slackware 10.0
Posts: 12
Original Poster
Rep:
|
Code:
# lspci
00:00.0 Host bridge: Intel Corp. 82810 DC-100 GMCH [Graphics Memory Controller Hub] (rev 02)
00:01.0 VGA compatible controller: Intel Corp. 82810 DC-100 CGC [Chipset Graphics Controller] (rev 02)
00:1e.0 PCI bridge: Intel Corp. 82801AA PCI Bridge (rev 02)
00:1f.0 ISA bridge: Intel Corp. 82801AA ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801AA IDE (rev 02)
00:1f.2 USB Controller: Intel Corp. 82801AA USB (rev 02)
00:1f.3 SMBus: Intel Corp. 82801AA SMBus (rev 02)
01:09.0 Multimedia audio controller: Ensoniq ES1371 [AudioPCI-97] (rev 06)
01:0a.0 Ethernet controller: National Semiconductor Corporation DP83815 (MacPhyter) Ethernet Controller
01:0b.0 Communication controller: Conexant HCF 56k Data/Fax Modem (rev 08)
Are we getting somewhere?
Thanks so much for your help tink!
Tim
|
|
|
07-23-2005, 04:41 PM
|
#13
|
Moderator
Registered: Apr 2002
Location: earth
Distribution: slackware by choice, others too :} ... android.
Posts: 23,067
|
Unfortunately I can't find much info about that particular
chipset, google comes back with hardly any hits in conjunction
with X11 or xorg.
I assume that this is an integrated chipset (shared RAM). Maybe
you can check the machines BIOS to see how much RAM has
been allotted to it, and then put a matching VideoRAM size entry
in your xorg.conf.
Another thing I miss in your subsequent posts is information
about which chipset was picked after the original setup. The
first xorg.conf you posted had "vga" as the driver, I think it
should be "i810" (or "svga" or "fb" if the i810 actes up).
Cheers,
Tink
|
|
|
07-23-2005, 11:58 PM
|
#14
|
LQ Newbie
Registered: Jul 2005
Distribution: Slackware 10.0
Posts: 12
Original Poster
Rep:
|
YAAAAAAAAAAAAAAAAAAAAAAAAAAAY!!
LOL! Finally, we have victory!
Here's the final xorg.conf file.
Code:
ection "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
RgbPath "/usr/X11R6/lib/X11/rgb"
ModulePath "/usr/X11R6/lib/modules"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/TTF/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
EndSection
Section "Module"
Load "record"
Load "extmod"
Load "dbe"
Load "dri"
Load "glx"
Load "xtrap"
Load "freetype"
Load "type1"
Load "freetype"
Load "speedo"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "PS/2"
Option "Device" "/dev/mouse"
Option "Emulate3Buttons"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 30 - 64
VertRefresh 50-100
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "NoAccel" # [<bool>]
#Option "SWcursor" # [<bool>]
#Option "ColorKey" # <i>
#Option "CacheLines" # <i>
#Option "Dac6Bit" # [<bool>]
#Option "DRI" # [<bool>]
#Option "NoDDC" # [<bool>]
#Option "ShowCache" # [<bool>]
#Option "XvMCSurfaces" # <i>
#Option "PageFlip" # [<bool>]
Identifier "Card0"
Driver "i810"
VendorName "Intel Corp."
BoardName "82810 DC-100 CGC [Chipset Graphics Controller]"
BusID "PCI:0:1:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x960" "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
EndSection
So, after all the trials and tribulations it turns out that it was the hardware issue that you just pointed out, tink, and then it was that xorgsetup doesn't by default put any HorizSync or VertRefresh values into the xorg.conf.
Thanks sooooo much for all of your help, especially you tink. I'm now happily at 1152 x 768 and I have options!!
Thanks so much!
Tim
|
|
|
07-24-2005, 12:42 AM
|
#15
|
Member
Registered: Jul 2005
Location: USA - IL
Distribution: Mepis
Posts: 131
Rep:
|
Hi,
I am a complete noob when it comes to Linux and have no knowledge of any type of computer programing.
Anyhow, i was reading through this thread and was wondering, what did you do to make your resolution work? by adding more text to that file you posted? and where do you access that?
Im learning alot from peoples issues
Thanks and i hope you dont mind the question
|
|
|
All times are GMT -5. The time now is 04:20 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|