VectorLinux
September 02, 2014, 03:37:08 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Visit our home page for VL info. To search the old message board go to http://vectorlinux.com/forum1. The first VL forum is temporarily offline until we can find a host for it. Thanks for your patience.
 
Now powered by KnowledgeDex.
   Home   Help Search Login Register  
Please support VectorLinux!
Pages: [1]
  Print  
Author Topic: ATI Display Driver----NEED HELP (Solved)  (Read 3680 times)
dus
Member
*
Posts: 10


« on: May 09, 2008, 10:15:11 am »

hi everyone! this is my first post as i have just recently installed vector on my laptop (Toshiba a105 s2131). but the problem is that i have 800x600 resolution.  i have downloaded the driver (ATI Radeon® Xpress 200M) but i cant open it. im only new to linux so i dont know much about how to install drivers. i even think that the driver would only install in windows, not linux.
anyway... i looking forward to any help..  Smiley 
« Last Edit: May 09, 2008, 05:55:08 pm by nightflier » Logged
nightflier
Administrator
Vectorian
*****
Posts: 4022



« Reply #1 on: May 09, 2008, 11:07:26 am »

Hi, and welcome to Vector Linux.

What version of Vector did you install? Most likely you won't have to install a new driver, it could just be a matter of tweaking what you have.
Logged
dus
Member
*
Posts: 10


« Reply #2 on: May 09, 2008, 11:09:42 am »

ive installed VL 5.9 Gold Standard
« Last Edit: May 09, 2008, 11:13:22 am by dus » Logged
nightflier
Administrator
Vectorian
*****
Posts: 4022



« Reply #3 on: May 09, 2008, 11:39:35 am »

Okay, now try to describe in some detail what you experience. I get that you only have 800x600 screen resolution. Searching for your model gives mainly hits on replacement batteries, so I assume it's not too new.. probably has 1024x768 as native resolution?

When troubleshooting via a forum like this, using the command line usually produces the best and most accurate results. Let's experiment a little. Highlight and copy the following line:
cat /etc/X11/xorg.conf

Now open a terminal (shell, command prompt) window. Hit the key combination Shift + Insert. You should see the above text being pasted into the terminal. Now hit enter. You should see text scrolling by in the terminal window. If that works, take it one step further; copy and paste this line:
cat /etc/X11/xorg.conf > $HOME/Desktop/xorg-file.txt

After this you should see a new file on your desktop "xorg-file.txt". Open it in a text editor, copy and paste the output into your next post. Hint: to make it pretty, highlight the pasted text and click the # button in the message toolbar, that will create a nice scrolling box which keeps your post more readable.
Logged
dus
Member
*
Posts: 10


« Reply #4 on: May 09, 2008, 12:50:55 pm »

the monitor is streched a little. every window is big. and yes this laptop is not new. i had xp on it, but after crashing for the 3rd time (i lost of my administrator privilages Angry) i wanted to dump windows. i heard of linux before but never had a chance to use it, and after some researching for the linux os i came to vector. it runs perfectly on this machine so i want to configure it...

 i went into setting>display setting and the highest number is 800x600. this is from the original computer specs from toshiba

Display7
• 15.4” diagonal widescreen TruBrite™ TFT active-matrix LCD
display at 1280x800 native resolution (WXGA)

Graphics8
• ATI Radeon® Xpress 200M 64MB-128MB dynamically allocated
shared graphics memory

ok here is what ive got.... (thanks for # tip Smiley)

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/share/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/share/fonts/local/"
    FontPath   "/usr/share/fonts/misc/"
    FontPath   "/usr/share/fonts/OTF/"
    FontPath   "/usr/share/fonts/TTF/"
    FontPath   "/usr/share/fonts/Type1/"
    FontPath   "/usr/share/fonts/CID/"
    FontPath   "/usr/share/fonts/Speedo/"
    FontPath   "/usr/share/fonts/75dpi/:unscaled"
    FontPath   "/usr/share/fonts/100dpi/:unscaled"
    FontPath   "/usr/share/fonts/75dpi/"
    FontPath   "/usr/share/fonts/100dpi/"
    FontPath   "/usr/share/fonts/cyrillic/"

# ModulePath can be used to set a search path for the X server modules.
# The default path is shown here.

#    ModulePath "/usr/lib/xorg/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 "kbd"
# 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 X.Org
#
#    Option     "XkbRules"      "xorg"
#    Option     "XkbModel"      "pc105"
#    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"
 DisplaySize 269 201 # 96 DPI @ 1024x768
# 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 - 50.0

#    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 40-90

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 Edit: May 09, 2008, 01:06:46 pm by dus » Logged
nightflier
Administrator
Vectorian
*****
Posts: 4022



« Reply #5 on: May 09, 2008, 01:36:01 pm »

We're getting closer. Looks like you are operating with the default xorg file. Do you remember if you went through a series of questions regarding your video configuration during install?

Anyways, next thing I'd do is try Vector's video configure tool.
Reboot the computer. When the selection screen appears, select "linux-tui" and log in as root.

Run command "vasm" (without the quotes) and continue to XWINDOW > XCONF, then follow the prompts.
You want to select "vlati" for your driver and 1280x800 for your resolution.
If all goes well, back out vasm of until you are back to the command prompt.
Run command "aticonfig --initial"
Finally, run "startx" to test your video.
Logged
dus
Member
*
Posts: 10


« Reply #6 on: May 09, 2008, 02:17:21 pm »

when i was installing the system i had some problems with the resolution, first i choose full auto-no qs> and that led my resolution to like 100x200. the only things that could fit on my monitor were the "file, edit, and view" tools icons... then i went into vxconf and selected the ati chipset, and the resolution. that led me to the same screen  Sad with 100x200 (or something like that). now after reading ur manual i tried again because i didnt run the "aticonfig --initial". but it did Not run after i went thru all the steps. it gave me something like "command not found"... i had to go back to vesa xserver. i still have the low resolution
Logged
nightflier
Administrator
Vectorian
*****
Posts: 4022



« Reply #7 on: May 09, 2008, 02:45:31 pm »

Sounds like your kernel sources may not be installed, they are required to compile and install the ATI driver. Find gslapt on your start menu. Enter "kernel-src" in the search field and hit enter. See if you have a solid blue square next the kernel-src entry.
Logged
dus
Member
*
Posts: 10


« Reply #8 on: May 09, 2008, 03:06:12 pm »

yes... but its blue with a lock on it, is it suppose to be just solid?
Logged
nightflier
Administrator
Vectorian
*****
Posts: 4022



« Reply #9 on: May 09, 2008, 03:37:44 pm »

Blue with a lock on it is fine.

At this point, go ahead and install the driver you downloaded from ATI. You can do so while in X-windows.

Open a terminal, type "su" and enter your root password. Navigate to the folder where your downloaded file is. It is possibly on your desktop. Type "ls" and hit enter to see the files in the folder. If you are in your home folder, type "cd Desktop" to get to the desktop. Remember that Linux is case sensitive. "Desktop" is not the same as "desktop".

When in the proper location, type "sh ati-driver-installer-8-4-x86.x86_64.run" Hint: just type "sh ati" and hit the Tab key. This should auto-complete your entry. Once running, just follow the prompts. When all done, type "aticonfig --initial" at the command line. Reboot the computer to activate new driver.
Logged
dus
Member
*
Posts: 10


« Reply #10 on: May 09, 2008, 05:22:28 pm »

AWESOME!!!!!!!!!!   Grin Grin Grin   all i needed was to log in as root from x-window, find the driver file and run it from there, after the installation i rebooted, went into tui mode, logged in root, ran "aticonfig-- initial", and thats it.... thank you SO much nightflier!!!!

btw- do i always have to start programs thru terminal?
« Last Edit: May 09, 2008, 05:24:16 pm by dus » Logged
nightflier
Administrator
Vectorian
*****
Posts: 4022



« Reply #11 on: May 09, 2008, 05:54:18 pm »

Glad to be of any help  Smiley

You do not always have to start programs though a terminal. There are many ways of accomplishing tasks.
Think of command line as "lowest common denominator". Every Linux install will have one, and it pretty much works the same on most of them. That way we can help people running different GUI's (as an example, I would not be able to tell you where to click in Gnome). As you can see, it is easy to copy and paste commands. I also wanted to help you learn something useful with this exercise  Wink

I'm marking this one as solved.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!