LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
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


Reply
  Search this Thread
Old 08-10-2004, 11:44 AM   #1
agaspar
LQ Newbie
 
Registered: Aug 2004
Posts: 9

Rep: Reputation: 0
Question Higher screen resolution in Slackware


I recently installed Slackware 9.1 on an older Dell with an 800Mhz processor and 256MB of RAM. It seems to be running fine, except that I cannot get it to give me a screen resolution in Xwindows greater than 640x480.

I took the /etc/X11/XF86Config-vesa, copied it to XF86Config, and modified it to fit my monitor (Dell 1900FP; HZ: 30-80; VT: 56-76). /var/log/messages showed the system having found 4MB of video ram on the machine (it uses an Intel generic chipset on the motherboard); so I modified the file to reflect that.

Xwindows comes up fine, but even though I see other modes in the file, I can't get out of 640x480. This replaces a much less capable machine running RedHat 7.x, which had no trouble giving my 1024x768.

I don't know where to look. Any help would be greatly appreciated.

Al Gaspar

Last edited by agaspar; 08-11-2004 at 07:59 AM.
 
Old 08-10-2004, 12:39 PM   #2
Komakino
Senior Member
 
Registered: Feb 2004
Location: Somerset, England
Distribution: Slackware 10.2, Slackware 10.0, Ubuntu 9.10
Posts: 1,938

Rep: Reputation: 55
Does your XF86Config file have multiple modes specified? i.e.:
Code:
Subsection "Display"
        Depth       24
        Modes "1024x768" "800x600" "640x480"
EndSubsection
?

If it does then pressing CTRL and ALT and + (on the numeric keypad) should rotate through available resolutions. If alternative resolutions at your default depth aren't specified then add them in the same fashion as above - the first on the line will be the first used.
 
Old 08-10-2004, 01:08 PM   #3
agaspar
LQ Newbie
 
Registered: Aug 2004
Posts: 9

Original Poster
Rep: Reputation: 0
Thank you for your quick response. Yes, the XF86Config file does have display entries for depths of 8, 16, 24, and 32. The default is set to 24. <CTRL><ALT>+ or - has no effect. :-(

--Al
 
Old 08-10-2004, 01:46 PM   #4
ravinder
LQ Newbie
 
Registered: Aug 2004
Posts: 5

Rep: Reputation: 0
Al,

It seems that I am also facing similar problem with my Red Hat 9.0 installation on a Dell machine, with an integrated video having 16M memory. My display always stays at 640x480, no matter what I do with the configuration. If you were able to fix your problem then please let me know the solution.

Thanks.

Regards, Ravinder
 
Old 08-10-2004, 02:03 PM   #5
pixelbaker
LQ Newbie
 
Registered: Aug 2004
Location: Missouri, USA
Distribution: In Limbo...
Posts: 5

Rep: Reputation: 0
I had the exact same problem with my Redhat 9 Shrike setup. I had all the modes enabled in my XF86Config file yet everytime I would try and switch to a higher resolution I would only get a blank screen and nothing else. I have a Matsonic 8157E motherboard with onboard S3 Savage video set to 16mb of shared RAM. I had been using the defaults that XF86 detected when installing Redhat. The video card detected correctly and my monitor, a Lite-On rebranded, had detected correctly also. I had tried editing monitor refresh rates and nothing changed. Finally a friend suggested changing my Driver in the VideoCard section to "VESA" from the default "savage". This fixed my problem immediately and I can now work at 800x600 and 1024x768. Hope the same works well for you.
 
Old 08-10-2004, 02:16 PM   #6
agaspar
LQ Newbie
 
Registered: Aug 2004
Posts: 9

Original Poster
Rep: Reputation: 0
Unhappy

Well, mine doesn't go blank when you attempt to switch resolutions; nothing happens. Unfortunately, I already have my card set to VESA. I'll have to see if maybe I can find a video card that I can use rather than this chipset on the mother board. Around here, that isn't too likely; I scraped the bottom of the barrel getting this box...

Any other ideas?

Last edited by agaspar; 08-10-2004 at 02:26 PM.
 
Old 08-10-2004, 02:41 PM   #7
Komakino
Senior Member
 
Registered: Feb 2004
Location: Somerset, England
Distribution: Slackware 10.2, Slackware 10.0, Ubuntu 9.10
Posts: 1,938

Rep: Reputation: 55
Although you said you have all the different modes set (8, 16, 24, 32 etc) do you actually have different resolutions specified for them? For example, for whichever is your default colour depth, try setting the ONLY resolution to something higher than 640x480. i.e. if your default colour depth is 24 bpp, then only have one resolution specified:
Code:
Subsection "Display"
        Depth       24
        Modes "1024x768"
EndSubsection
then restart X.
 
Old 08-10-2004, 02:51 PM   #8
ravinder
LQ Newbie
 
Registered: Aug 2004
Posts: 5

Rep: Reputation: 0
Thanks a lot for your suggestion. I used redhat-config-xfree86 script to change the display settings to VESA. After startup, the screen was garbled for a while and then switched back to 640x480. Even though my display adapter has 16M shared RAM, the log always shows only 832 KB RAM. I guess I too will have to look for a stand-alone video card rather than using the integrated video adapter.

Regards, Ravinder
 
Old 08-10-2004, 03:05 PM   #9
agaspar
LQ Newbie
 
Registered: Aug 2004
Posts: 9

Original Poster
Rep: Reputation: 0
Unhappy Still no luck...

I did as you suggested and edited the entries for my default mode of 24 so that it only had 1024x768. When I did this, X failed with the log file stating that it could not find any such mode. I tried again with 800x600 and 640x480. The 800x600 behaved the same. The 640x480 came up just fine. Would it help anyone for me to post my log file or my XF86Config file?

--Al
 
Old 08-10-2004, 03:10 PM   #10
Komakino
Senior Member
 
Registered: Feb 2004
Location: Somerset, England
Distribution: Slackware 10.2, Slackware 10.0, Ubuntu 9.10
Posts: 1,938

Rep: Reputation: 55
Re: Still no luck...

Quote:
Originally posted by agaspar
I did as you suggested and edited the entries for my default mode of 24 so that it only had 1024x768. When I did this, X failed with the log file stating that it could not find any such mode. I tried again with 800x600 and 640x480. The 800x600 behaved the same. The 640x480 came up just fine. Would it help anyone for me to post my log file or my XF86Config file?
--Al

There's a line in the XF86Config file that says VideoRam, if you have 4MB of VRAM, try changing that line so it says:
VideoRam 4096

Yes, post your XF86Config file and we can see if anything is obviously amiss.
 
Old 08-10-2004, 03:45 PM   #11
agaspar
LQ Newbie
 
Registered: Aug 2004
Posts: 9

Original Poster
Rep: Reputation: 0
Here's my XF86Config file...

I already set my videoram to 4096 :-(... Anyway, here is my XF86Config file. I'd appreciate any help. I put back all the modes for the 24 bit resolution...

Code:
# 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.
# **********************************************************************
#
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 font modules
    Load        "type1"
    Load        "freetype"
    Load        "speedo"

# 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/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/"

# 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"

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     "DontZoom"

# 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"

# Set the basic blanking screen saver timeout.

#    Option      "blank time"    "10"    # 10 minutes

# Set the DPMS timeouts.  These are set here because they are global
# rather than screen-specific.  These settings alone don't enable DPMS.
# It is enabled per-screen (or per-monitor), and even then only when
# the driver supports it.

#    Option      "standby time"  "20"
#    Option      "suspend time"  "30"
#    Option      "off time"      "60"

# On some platform the server needs to estimate the sizes of PCI
# memory and pio ranges. This is done by assuming that PCI ranges
# don't overlap. Some broken BIOSes tend to set ranges of inactive
# devices wrong. Here one can adjust how aggressive the assumptions
# should be. Default is 0.

# Option   "EstimateSizesAggresively" "0"

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"

# 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"    ""

EndSection


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

Section "InputDevice"

# Identifier and driver

    Identifier  "Mouse1"
    Driver      "mouse"

# 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
    Option "Protocol"    "PS/2"

# The mouse device.  The device is normally set to /dev/mouse,
# which is usually a symbolic link to the real device.

    Option "Device"      "/dev/mouse"
#   Option "Device"      "/dev/psaux"
#   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"

EndSection

# 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

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-80

#    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 56-76

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

Section "Device"
    Identifier  "VESA Framebuffer"
    Driver      "vesa"
    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      "VESA Framebuffer"
    Monitor     "My Monitor"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.

#   DefaultDepth 8
#   DefaultDepth 16
   DefaultDepth 24
#   DefaultDepth 32

# "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)

    Subsection "Display"
        Depth       8
        Modes "1024x768" "800x600" "640x480"
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes "1024x768" "800x600" "640x480"
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes "1024x768" "800x600" "640x480"
    EndSubsection
    Subsection "Display"
        Depth       32
        Modes "1024x768" "800x600" "640x480"
    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

Last edited by agaspar; 08-10-2004 at 03:47 PM.
 
Old 08-10-2004, 04:21 PM   #12
Komakino
Senior Member
 
Registered: Feb 2004
Location: Somerset, England
Distribution: Slackware 10.2, Slackware 10.0, Ubuntu 9.10
Posts: 1,938

Rep: Reputation: 55
The only other thing I can think of is that you have monitor horizontal and vertical refresh rates that don't support higher resolutions....are they the right settings for your monitor?
 
Old 08-10-2004, 04:49 PM   #13
VincentB
Member
 
Registered: Jun 2003
Location: Brussels, Belgium
Distribution: Ubuntu 6.10
Posts: 139

Rep: Reputation: 15
I have a similar problem in a new Dell 610m.

I have downloaded a patch and installed it ...
it works very well. You can find it here : http://perso.wanadoo.fr/apoirier/
Hope this will help...
 
Old 08-11-2004, 07:10 AM   #14
agaspar
LQ Newbie
 
Registered: Aug 2004
Posts: 9

Original Poster
Rep: Reputation: 0
The horizontal and vertical refresh rates come straight from the Dell support page for the 1900FP monitor. They are also the settings that I used on my old IBM box under RedHat with no problems. Here is the info off of the Dell support page :

Resolution
Horizontal frequency range 30 kHz to 80 kHz (automatic)
Vertical frequency range 56 Hz to 76 Hz (automatic)
Optimal preset resolution 1280 x 1024 at 60 Hz
Highest preset resolution 1280 x 1024 at 75 Hz
Dell guarantees image size and centering for all preset modes listed in the following table.


--------------------------------------------------------------------------------

Preset Display Modes
Display Mode Horizontal Frequency (kHz) Vertical Frequency (Hz) Pixel Clock (MHz) Sync Polarity (Horizontal/Vertical)
IBM, VGA2, 720 x 400 31.469 70.087 28.3 -/+
IBM, VGA3, 640 x 480 31.469 59.940 25.2 -/-
VESA, 640 x 480 37.500 75.000 31.5 -/-
VESA, 800 x 600 37.879 60.317 49.5 +/+
VESA, 800 x 600 46.875 75.000 49.5 +/+
VESA, 1024 x 768 48.363 60.004 65.0 -/-
VESA, 1024 x 768 60.023 75.029 78.8 +/+
VESA, 1280 x 1024 64.000 60.000 135.0 +/+
VESA, 1280 x 1024 79.976 75.025 135.0 +/+


--------------------------------------------------------------------------------



Now I am working with an old desktop rather than a laptop. Is Alaine's patch to the 855 Intel graphic chipset going to do me any good? This is the information that I see on my chipset from the XFree86.0.log file:

Intel Corp. 82810E DC-133 CGC [Chipset Graphic Controler] Rev. 3 Mem @ 0xf8000000/26, 0xff000000/19

Thanks--

Al

Last edited by agaspar; 08-11-2004 at 07:57 AM.
 
Old 08-11-2004, 08:57 AM   #15
tuxrules
Senior Member
 
Registered: Jun 2004
Location: Chicago
Distribution: Slackware64 -current
Posts: 1,144

Rep: Reputation: 56
I kind of have the same problem, only thing is that I have a 1024x768 display. I have Nvidia GeForce 2 MX with 64 MB RAM (compiled kernel 2.6.7 with module agpgart). I installed the nvidia drivers from its site but then apparently the driver didnt do anything. I had installed NVIDIA driver previously on RH9 and now on FC2 but the was XF86Config, Slack 10 has Xorg. Now where should I make the change so that the system uses the nvidia drivers. Also when installing drivers I got an error regarding module rivafb. Can i just rmmod rivafb and then reinstall the nvidia drivers? Or can i just add a section "Device" as indicated below in the xorg so that it uses nvidia drivers.

# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

Section "Device"
Identifier "VESA Framebuffer"
Driver "vesa"
VideoRam 4096
# Insert Clocks lines here if appropriate
EndSection
__________________
Thanks, Tux
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Why can't you get a higher screen resolution than 800x600 on SUSE? yekrahs SUSE / openSUSE 11 02-09-2006 04:58 PM
Cannot change screen resolution (atir 3) in slackware 10 mmarkvillanueva Slackware 6 05-27-2005 06:31 PM
changing the screen resolution in slackware 9.1 derfaust Linux - Newbie 3 07-23-2004 03:44 AM
Can't change screen resolution on Slackware 9.1... luptinpitman Slackware 5 05-01-2004 04:27 PM
slackware - xserver screen resolution fatum Linux - Software 6 01-20-2004 08:47 PM


All times are GMT -5. The time now is 08:31 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration