Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 12
Hello I am really newbie at Linux, I installed Suse 9.0 in my computer and everything is being really smoothly, until I tried to change the resolution of the screen. ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Mar 2004
    Posts
    4

    Changing resolution under Suse 9.0


    Hello

    I am really newbie at Linux, I installed Suse 9.0 in my computer and everything is being really smoothly, until I tried to change the resolution of the screen.
    I tried to use SaX2 to change it, I went to "Geometry", I try to change the size and each time I try to make it bigger, it just restart my session. It just reload KDE or what ever Desktop env I have but there is no change on the resolution.

    I have a resolution of 640x480 @ 60, I can't see all the windows completely and its kind of annoying,

    My video card is embeeded and is a PCI Chips and Technologies 69030.

    I tried using X86config but I have the same result. I input the correct values for my monitor frequencies and I selected the correct Chips and technologies video card, reboot the computer and go to Yast and try to change Geometry, my computer just logme out and restart the session. Please any help, I feel kind of frustated

    Thanks

  2. #2
    Linux Engineer
    Join Date
    Jul 2003
    Location
    Farnborough, UK
    Posts
    1,305
    You can use ctrl alt + and ctrl alt - to cycle through the available resolutions.. But these have to be set up in your XF86Config file first. Your box will resolve to the biggest available in the list by default.

    Try posting your /etc/X11/XF86Config or XF86Config-4 here.
    Lansbury's Lido

    thekiadriver on #linuxforums - fleetingly

  3. #3
    Just Joined!
    Join Date
    Feb 2004
    Posts
    47
    i have this problem too

    i think my problem is the xf86 file never got overwritten or somthing

  4. #4
    Just Joined!
    Join Date
    Mar 2004
    Posts
    4
    Thanks for the reply,

    I tried ctl + alt + plus/minus and it didn't work, I beleive I have the correct settings, but still not getting results, here is my xconfig86

    Thank you

    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/TrueType/"
    # FontPath "/usr/X11R6/lib/X11/fonts/freefont/"
    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 XFree86
    # Option "XkbRules" "xfree86"
    # Option "XkbModel" "pc101"
    # Option "XkbLayout" "us"
    # Option "XkbVariant" ""
    # Option "XkbOptions" ""

    # Option "XkbDisable"

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

    EndSection


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

    Section "InputDevice"

    # Identifier and driver

    Identifier "Mouse1"
    Driver "mouse"
    Option "Protocol" "PS/2"
    Option "Device" "/dev/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 "GatewayEV700"

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

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

    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 "VideoCard"
    Driver "chips"
    #VideoRam 4096
    # Option "noaccel"
    # Option "no_bitblt"
    # Option "xaa_no_color_exp"
    # Option "xaa_benchmark"
    # Option "hw_cursor"
    # Option "sync_on_green"
    # Option "fast_dram"
    # Option "use_vclk1"
    # Textclockfreq 25.175
    # Option "nolinear"
    # MemBase 0x03b00000
    # Device section for C&T cards.
    # Option "suspend_hack"
    # Option "STN"
    # Option "no_stretch"
    # Option "no_center"
    # Option "use_modeline"
    # Option "fix_panel_size"
    # videoram 512
    # 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 "VideoCard"
    Monitor "GatewayEV700"
    DefaultDepth 16

    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

  5. #5
    Linux Engineer
    Join Date
    Jul 2003
    Location
    Farnborough, UK
    Posts
    1,305
    edited - see below
    Lansbury's Lido

    thekiadriver on #linuxforums - fleetingly

  6. #6
    Linux Engineer
    Join Date
    Jul 2003
    Location
    Farnborough, UK
    Posts
    1,305
    Just had a nose on the net, suggest you try the following changes. Edit it with your favourite text editor and then restart X. Let us know how it goes.

    Section "Device"
    Identifier "ct69030"
    Driver "chips"

    Section "Screen"
    Identifier "Screen 1"
    Device "ct69030"
    Monitor "GatewayEV700"
    DefaultDepth 16
    Lansbury's Lido

    thekiadriver on #linuxforums - fleetingly

  7. #7
    Just Joined!
    Join Date
    Mar 2004
    Posts
    4
    Hello

    I tried but It did not work, I found that my chip is not the CT69030, it is a 69030.

    I found in a website a driver for what seems to be my video card at www.humboldt.co.uk/matc.html,

    If this is correct, now I have to compile the kernel to install this driver,

    How can I compile the kernel and add this driver?, also after recompiling the kernel, Would I need to use xf86config to re-configure my system and the new added video card will show up in the list of recognized video cards?

    Thanks

  8. #8
    Linux Engineer
    Join Date
    Jul 2003
    Location
    Farnborough, UK
    Posts
    1,305
    You sure it's not ct? ct would stand for Chips & Technologies.

    Recompiling kernel. Probably easy, but I treat it like going to the dentist.

    Anyone else help here?
    Lansbury's Lido

    thekiadriver on #linuxforums - fleetingly

  9. #9
    Just Joined!
    Join Date
    Mar 2004
    Posts
    4
    Hello

    I can't find in the web any description or difference between CT69030 ad 69030, you are probably correct, we are talking about the same chip.

    I went to the website of Assiliant, who has the control of the former chips and technologies, and found description for the 69030, and says that it has 4MB of ram.

    is that a low amount of memory that my video card cannot display better resolution?

  10. #10
    Just Joined!
    Join Date
    Feb 2004
    Posts
    47
    here what i did

    i deleted all my xfree86config files even the backups

    i went in to my setup which is
    Code:
    vasm
    and made a new one

    still no luck it stays in 640X?? whatever that is resolution

    ill post my xfree86 file soon

Page 1 of 2 1 2 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •