Click to See Complete Forum and Search --> : Can't go above 1024 resolution


aNoob
01-11-2004, 05:28 AM
Hi there!

This is shameful for me since I did it once but I forgot how to do it again.next time I will take a note to make sure I will know how to do it properly next time.

Here's my problem.Installed Slack once again. Then Droplne Gnome. No matter what I do , I cannot select a resolution above 1024. Played with xf66cfg and this one messed up my XF86Config file so I had to revert to VESA in order to start gdm. Can anyone show me what I am doing wrong?
I have a GF 4 Ti4600/128VRAM and an LG Monitor that can do 1280 resolution. Here's my XF86Config file:
(Sorry if is too long but is better if you have it now)
TA!

=============================

# File generated by xf86config.
#
#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# 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 the XFree86 Project 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
# XFree86 Project.
#
# ************************************************** ********************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# ************************************************** ********************
# NOTE: This is a NEW IMPROVED version of XF86Config-fbdev that uses the vesa
# driver instead of the fbdev driver. Thanks to Kenneth Fanyo who pointed
# this out to me. :)
# This XF86Config file is designed for use with the VESA framebuffer.
# This generic interface should work with nearly all video cards
# (although not every card will support every resolution).
# With the new driver, it should no longer be required to have frame buffer
# support in the kernel, or to run it on the console.
#
# Enjoy! :)
# -- volkerdi@slackware.com
#
# ************************************************** ********************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# ************************************************** ********************
#
# ************************************************** ********************
# Files section. This allows default font and rgb paths to be set
# ************************************************** ********************
# ************************************************** ********************
# Server flags section.
# ************************************************** ********************
# ************************************************** ********************
# Input devices
# ************************************************** ********************
# ************************************************** ********************
# Core keyboard's InputDevice section
# ************************************************** ********************
# ************************************************** ********************
# Core Pointer's InputDevice section
# ************************************************** ********************
# Some examples of extended input devices
# 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
# ************************************************** ********************
# Graphics device section
# ************************************************** ********************
# Any number of graphics device sections may be present
# ************************************************** ********************
# 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.
# ************************************************** ********************
# 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
# 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.
# 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".
Identifier "Simple Layout"
Screen "Screen 1" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection

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.
# 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).
#
# ModulePath can be used to set a search path for the X server modules.
# The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
RgbPath "/usr/X11R6/lib/X11/rgb"
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/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/"
EndSection

Section "Module"

# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "type1"
Load "freetype"
Load "speedo"
# This loads the GLX module
Load "glx"
EndSection

Section "InputDevice"

# 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"
# Set the keyboard auto repeat parameters. Not all platforms implement
# this.
# Option "AutoRepeat" "500 5"
# Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)).
# Option "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a European
# keyboard, you will probably want to use one of:
#
# Option "XkbModel" "pc102"
# Option "XkbModel" "pc105"
#
# If you have a Microsoft Natural keyboard, you can use:
#
# Option "XkbModel" "microsoft"
#
# If you have a US "windows" keyboard you will want:
#
# Option "XkbModel" "pc104"
#
# 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" ""
Identifier "Keyboard1"
Driver "Keyboard"
EndSection

Section "InputDevice"

# Identifier and driver
# On platforms where PnP mouse detection is supported the following
# protocol setting can be used when using a newer PnP mouse:
# Option "Protocol" "Auto"
# The available mouse protocols types that you can set below are:
# Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2
# Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2
# MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse
# ThinkingMouse ThinkingMousePS/2 Xqueue
# which is usually a symbolic link to the real device.
# Option "Device" "/dev/ttyS0"
# Option "Device" "/dev/ttyS1"
# 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"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "PS/2"
# The mouse device. The device is normally set to /dev/mouse,
Option "Device" "/dev/mouse"
# Option "Device" "/dev/psaux"
EndSection

Section "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-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.
Identifier "My Monitor"
HorizSync 31.5 - 64.3
VertRefresh 40.0 - 90.0
EndSection

Section "Device"

#VideoRam 4096
# Insert Clocks lines here if appropriate
Identifier "VESA Framebuffer"
Driver "nvidia"
EndSection

Section "Screen"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.
# DefaultDepth 8
# DefaultDepth 16
# DefaultDepth 32
DefaultDepth 24
# "1024x768" is also a conservative usable default resolution. If you
# have a better monitor, feel free to try resolutions such as
# "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your
# card/monitor can produce)
Identifier "Screen 1"
Device "VESA Framebuffer"
Monitor "My Monitor"
DefaultDepth 24
SubSection "Display"
Depth 8
Modes "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 32
Modes "1152x864" "1024x768" "800x600" "640x480"
EndSubSection
EndSection


=============================

je_fro
01-11-2004, 07:18 AM
Have a look at this part and edit it:
Depth 24
Modes "1600x1200" "1280x1024" "1152x864" "1024x768" "800x600" "640x480"


Did you set up "nvidia" (the module) to be automatically loaded at boot?

aNoob
01-11-2004, 08:45 AM
Originally posted by je_fro
Have a look at this part and edit it:
Depth 24
Modes "1600x1200" "1280x1024" "1152x864" "1024x768" "800x600" "640x480"


Did you set up "nvidia" (the module) to be automatically loaded at boot?

Hi,
Did that to no avail before,although I did not added 1600x1200 as option.
I did set nvidia automatically loaded at start , in fact I can see the nvidia logo when entering X. Fact is that even without nvidia I should be able to go up to 1280 resolution,is not necessary a driver problem as far as I remember.Is somehow related. Noticed that xf86cfg only adds a line:

Chipset GeForce 4 Ti4600

in the config file , this one makes X unusable for some reasons , as soon as I remove it I can log into X.
I will add 1600x1200 as well , to see what happens.
Thx!

aNoob
01-11-2004, 01:08 PM
OK,managed to reach those resolutions by playing with the monitor frequency.Now I see them in the dropdown list.
Thx for the effort answering me.

bwkaz
01-11-2004, 05:16 PM
Look at your monitor's manual and make ABSOLUTELY SURE you don't set the ranges higher than the monitor can go!

Actually, set them to exactly what the manual tells you the ranges are. Then save those numbers somewhere safe (like... well, the manual, actually ;)).

aNoob
01-12-2004, 05:06 AM
I always make sure I have a very conservative frequency in my X config , say 60 Hz. Point is that some resolutions plus bit colors are not supported in the frequency the monitor is set to run. But yes , at least now is working and couldn't be happier.
Now ,if I can manage to work on the sound (i810_rng failed at startup) , I'll be happy like a pig in the mud.But I'm working on this :D

mrBen
01-12-2004, 05:43 AM
The whole 'this can kill your monitor' thing is actually a little bit out of date in most cases these days; most modern monitors will give an 'out of range' message if you try and go outwith their sync ranges.

bwkaz
01-12-2004, 09:31 PM
mrBen -- true, of course. I guess I just can't let go of that warning, though. :D

aNoob -- i810_rng or i810_audio? i810_rng is for driving the hardware random number generator on your motherboard, not your sound device. i810_audio is for the sound device.

aNoob
01-13-2004, 06:54 AM
Yes,I did a mistake.Is rng , not the audio one. I was writing fast and since my sound didn't worked put it fast on the post. Managed to make the sound working by taking out the crappy PCI card I have and let the integrated one to work.Now I can listen to the radio.Works like a charm.
Yes , I still see that error on boot , that i810_rng.o.tgz failed , don't know what to do with it. Is somehow embarrasingto show my friends my linuxbox with that error.I tell them , see , linux still works like a flaw even with a module failed :D.
I would very much like to get rid of it , but it doesn't bother me while working.
TA!

bwkaz
01-13-2004, 08:59 PM
Is there an i810_rng.o.gz file in /lib/modules/$(uname -r)/kernel/drivers/ anywhere?

Is there anything relevant (like "device not found" errors from the i810_rng module) in the output of dmesg after you boot?

hyp_spec
01-13-2004, 09:07 PM
edit /etc/hotplug/blacklist and add "i810_rng"

that should take care of your 'error'

aNoob
01-15-2004, 02:46 PM
Is there an i810_rng.o.gz file in /lib/modules/$(uname -r)/kernel/drivers/ anywhere?

Is there anything relevant (like "device not found" errors from the i810_rng module) in the output of dmesg after you boot?


No sir , I have checked this and there's nothing like it. dmesg said something like i810_rng failed. Must be a module not added for my kernel? Dunno.


edit /etc/hotplug/blacklist and add "i810_rng"

that should take care of your 'error'


Yep , I don't see the message anymore. A vey clean startup now :D


One thing bothers me though. By blacklisting this guy , do I miss any functionality from my OS? Coz if it's so , I would very much like to fix this problem.

TA!

bwkaz
01-15-2004, 08:36 PM
If your motherboard chipset is not an Intel chipset, then no, you're missing nothing.

If you don't have the module in /lib/modules/, then that means that that driver was either configured out of the kernel, or was configured to compile into the kernel statically, when the kernel was configured. If it was configured into the kernel statically, then dd if=/dev/i810_rng of=/home/username/temp bs=512 count=1 won't give a "no such device" error (and you also won't be missing anything).

If it was configured out, then the dd command will give a "no such device" error, and you will be missing out on something fairly minor -- but again, only if you have an Intel chipset.