Nowe posty

xx Problem ze sterownikami. (5)
2024-04-13, 21:25:16
xx Instalacja xfce4 (2)
2024-04-13, 16:20:17
xx Serie kompilacji bez instalacji dla “emerge” w Gentoo (2)
2024-04-08, 18:40:04
xx Plasma 6 w Neonie ssie trochę mniej ... (17)
2024-04-05, 10:03:46
xx Problem z Linux Lite po instalacji (3)
2024-04-03, 14:23:40
xx Jak właczyć num locka przy starcie systemu debian 12? (12)
2024-04-02, 17:43:54
xx Brak dźwieku w systemie. (5)
2024-04-02, 16:13:41
xx Dystrybucja pod HP Omen (7)
2024-03-29, 11:33:05
xx [Poradnik] Wyszukiwanie Sterowników (2)
2024-03-27, 21:08:23
xx Ile pingwinów? (1)
2024-03-27, 08:59:24

Autor Wątek: Slackware 12 i radeon x1600 Problem z niewyraźnym obrazem  (Przeczytany 12274 razy)

benek14

  • Gość
Witam
Zainstalowałem sobie  SLACKA 12 i najnowsze stery ATI po wydaniu komendy aticonfig --initial --input=/etc/X11/xorg.conf Rozdzielczość automatycznie ustawia się na 2048 x xxxx nie pamiętam (bo na windzie siedzę) i wszystko było by ok gdyby nie fakt że odświeżanie jest na maks 60 hz (porażka) Jeśli zmienię ustawienia rozdzielczości na 1024 x 768 to mogę ustawić sobie odświeżanie na 85 hz, ale znowu haczyk wszystko jest takie duże czcionki i ikony przez co obraz jest nie wyraźny . Ma ktoś jakiś pomysł jak sobie z tym poradzić ?

chmooreck

  • Gość
Slackware 12 i radeon x1600 Problem z niewyraźnym obrazem
« Odpowiedź #1 dnia: 2008-01-25, 07:56:48 »
ustawić rozdzielczość pośrednią ? np. 1600x1200 ?

benek14

  • Gość
Slackware 12 i radeon x1600 Problem z niewyraźnym obrazem
« Odpowiedź #2 dnia: 2008-01-25, 17:36:45 »
To nie jest rozwiązanie ponieważ na takiej rozdzielczości maksymalne odświeżanie mogę ustawić 60 HZ. Muszę mieć rozdzielczość, 1024 X 768 , ale wtedy jak już napisałem obraz jest nie wyraźny
"Jeśli zmienię ustawienia rozdzielczości na 1024 x 768 to mogę ustawić sobie odświeżanie na 85 hz, ale znowu haczyk wszystko jest takie duże czcionki i ikony przez co obraz jest nie wyraźny"

chmooreck

  • Gość
Slackware 12 i radeon x1600 Problem z niewyraźnym obrazem
« Odpowiedź #3 dnia: 2008-01-25, 18:32:17 »
pochwal się jeszcze jaki masz monitor...

poczytaj sobie
man xorg.conf
i kilka kluczy do wyszukiwania na google'ach: modeline horizsynq vertrefresh

benek14

  • Gość
Slackware 12 i radeon x1600 Problem z niewyraźnym obrazem
« Odpowiedź #4 dnia: 2008-01-26, 15:40:40 »
Monitor HP 7500
Dołaczam jescze mój xorgconfig może ktoś doradzi co w nim porawić
 
# 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      0  "aticonfig-Screen[0]" 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/lib/xorg/modules"
RgbPath      "/usr/share/X11/rgb"
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/"
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
# This loads the GLX module
Load  "dbe"   # Double buffer extension
SubSection "extmod"
Option    "omit xfree86-dga"   # don't initialise the DGA extension
EndSubSection
Load  "type1"
Load  "freetype"
    #Load        "speedo"
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 X.Org
#
#    Option     "XkbRules"      "xorg"
#    Option     "XkbModel"      "pc105"
#    Option     "XkbLayout"     "us"
#    Option     "XkbVariant"    ""
#    Option     "XkbOptions"    ""
Identifier  "Keyboard1"
Driver      "kbd"
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 - 50.0
VertRefresh  40.0 - 90.0
EndSection

Section "Monitor"
Identifier   "aticonfig-Monitor[0]"
Option    "VendorName" "ATI Proprietary Driver"
Option    "ModelName" "Generic Autodetecting Monitor"
Option    "DPMS" "true"
EndSection

Section "Device"

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

Section "Device"
Identifier  "aticonfig-Device[0]"
Driver      "fglrx"
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
# "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    "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

Section "Screen"
Identifier "aticonfig-Screen[0]"
Device     "aticonfig-Device[0]"
Monitor    "aticonfig-Monitor[0]"
DefaultDepth     24
SubSection "Display"
Viewport   0 0
Depth     24
EndSubSection
EndSection

norbert_ramzes

  • Gość

miciak

  • Gość
Slackware 12 i radeon x1600 Problem z niewyraźnym obrazem
« Odpowiedź #6 dnia: 2008-01-29, 14:11:00 »
Witam
Ja mam podobny problem. Od 3 dni mandriva 2008 i od 3 dni usiłuję poprawić grafikę. Mogę zmieniać rozdzielczości ,dedykowana do mojego monitora (NEC LCD 1810x) to 1280/1024, ale jak taką ustawię to obraz zamiast  mi spasować do rozmiaru monitora- powiększa sie fizycznie i mogę go przesuwać po ekranie po kilka cm na boki. Nie poprawia sie natomiast jakość liter i są wręcz męczące. Zmiany rozdzielczości  sa przyjmowane bez oporów , ale za każdym razem powiększa lub pomniejsza mi to powierzchnię obszaru roboczego, a nie poprawia jakości. Rozmiar pasujący do monitora to w praktyce 1024/768, ale tutaj czcionki i obiekty tak samo wygladają . Tyle tylko że zajmuja "dopasowany" obszar roboczy. Tydzień wczesniej mioałem tu Ubuntu, a jeszcze miesiąc wcześniej Windowsa które "wymiatały" ekran całkowicie. Po prostu żyleta. Jestem laikiem totalnym a muszę ten problem rozwiązać.

norbert_ramzes

  • Gość
Slackware 12 i radeon x1600 Problem z niewyraźnym obrazem
« Odpowiedź #7 dnia: 2008-01-29, 14:19:20 »
Cytat: miciak
"wymiatały" ekran całkowicie. Po prostu żyleta.
Rozumiem że działało idealnie. jakbym się mylił to mnie popraw.

Sprawdź jakie "odświeżanie" używasz (tzn. jaka częstotliwość odchylania pionowego) i zmień na 75Hz albo 60Hz.

miciak

  • Gość
Slackware 12 i radeon x1600 Problem z niewyraźnym obrazem
« Odpowiedź #8 dnia: 2008-01-29, 16:02:25 »
Cytat: norbert_ramzes
Cytat: miciak
"wymiatały" ekran całkowicie. Po prostu żyleta.
Rozumiem że działało idealnie. jakbym się mylił to mnie popraw.

Sprawdź jakie "odświeżanie" używasz (tzn. jaka częstotliwość odchylania pionowego) i zmień na 75Hz albo 60Hz.
Mam taki monitor http://www.aurora.se/nec/nec-1810x.htm. Teraz go sprawdziłem. Na żadnym odświeżaniu w 1280/1024 nie chce zmniejszyć literek i zawsze obszar roboczy jest poza ekranem.
Jeśli można to pośle Ci na maila pare zrzutów ekranu tego jak to wygląda.??

norbert_ramzes

  • Gość

benek14

  • Gość
Slackware 12 i radeon x1600 Problem z niewyraźnym obrazem
« Odpowiedź #10 dnia: 2008-02-12, 17:16:58 »
Witam próbowałem nic nie pomaga obraz dalej jest nie wyraźny
Może ktoś zobaczy na mój xorgconf i coś doradzi
 
# 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      0  "aticonfig-Screen[0]" 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/lib/xorg/modules"
RgbPath      "/usr/share/X11/rgb"
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/"
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
# This loads the GLX module
Load  "dbe"   # Double buffer extension
SubSection "extmod"
Option    "omit xfree86-dga"   # don't initialise the DGA extension
EndSubSection
Load  "type1"
Load  "freetype"
    #Load        "speedo"
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 X.Org
#
#    Option     "XkbRules"      "xorg"
#    Option     "XkbModel"      "pc105"
#    Option     "XkbLayout"     "us"
#    Option     "XkbVariant"    ""
#    Option     "XkbOptions"    ""
Identifier  "Keyboard1"
Driver      "kbd"
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 - 50.0
VertRefresh  40.0 - 90.0
EndSection

Section "Monitor"
Identifier   "aticonfig-Monitor[0]"
Option    "VendorName" "ATI Proprietary Driver"
Option    "ModelName" "Generic Autodetecting Monitor"
Option    "DPMS" "true"
EndSection

Section "Device"

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

Section "Device"
Identifier  "aticonfig-Device[0]"
Driver      "fglrx"
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
# "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    "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

Section "Screen"
Identifier "aticonfig-Screen[0]"
Device     "aticonfig-Device[0]"
Monitor    "aticonfig-Monitor[0]"
DefaultDepth     24
SubSection "Display"
Viewport   0 0
Depth     24
EndSubSection
EndSection

arctgx

  • Gość
Slackware 12 i radeon x1600 Problem z niewyraźnym obrazem
« Odpowiedź #11 dnia: 2008-02-12, 18:07:40 »
miciak, spodziewałbym się, kiedy programowy ekran wychodzi poza fizyczny (i można myszą się dostać do zasłoniętych miejsc), to masz w "Screen" ustawiony "Virtual" na większą niż fizyczną rozdzielczość.

benek14, możesz dać zawartość /var/log/Xorg.0.log - może DisplaySize warto by dopracować dla odpowiedniego DPI. Sprawdź też jakie masz na 1024x768 ("xdpyinfo | grep -i inch"). Zależnie od DPI czcionka o tym samym pikselowym rozmiarze ma fizycznie różną fizyczną wielkość.

Ostatnio zdałem się na automatyczne wykrycie rozmiaru w xserver-xorg 1.4 i wyliczył mi o wiele większy rozmiar niż fizyczny, ściskając go potem do prawdziwego, co dawało w szczególności mniejsze czcionki.

chmooreck

  • Gość
Slackware 12 i radeon x1600 Problem z niewyraźnym obrazem
« Odpowiedź #12 dnia: 2008-02-12, 19:00:43 »
interesuje cie sekcja
Section "Screen"
w liniach trybów dopisz na początku "1280x1024", czylii maja one wyglądać tak:
		Modes    "1280x1024" "1024x768" "800x600" "640x480"

benek14

  • Gość
Slackware 12 i radeon x1600 Problem z niewyraźnym obrazem
« Odpowiedź #13 dnia: 2008-02-14, 14:19:03 »
Przecież tam już coś takiego jest jeśli o to chodzi
Section "Screen"
Identifier "Screen 1"
Device     "My Video Card"
Monitor    "My Monitor"
DefaultDepth     24
SubSection "Display"
Viewport   0 0
Depth     8
Modes    "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport   0 0
Depth     16
Modes    "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Viewport   0 0
Depth     24
Modes    "1280x1024" "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "Screen"
Identifier "aticonfig-Screen[0]"
Device     "aticonfig-Device[0]"
Monitor    "aticonfig-Monitor[0]"
DefaultDepth     24
SubSection "Display"
Viewport   0 0
Depth     24
EndSubSection
EndSection
Dołacze jescze dane techniczne mojego minitora które w końcu znalazłem
Technical Specifications
Tube Type                   Color, Conventional FST, Multi-frequency
Picture Tube Size           17-inch (43.18 cm)
(diagonal)
Viewable Image Area         16-inch (40.64 cm)
(diagonal)
Trio Dot Pitch              0.28 mm
Horizontal Dot Pitch        0.24 mm
Horizontal Frequency (kHz) 30 to 70 kHz
Vertical Frequency (Hz)     50 to 140 Hz
Maximum Pre-set             1280 x 1024 @ 60 Hz
Resolution
Preferred Flicker Free      1024 x 768 @ 85 Hz
Resolution
Preset Graphic Modes        1024 x 768 @ 85 Hz and 75 Hz
NOTE: All modes are non-    800 x 600 @ 85 Hz and 75 Hz
interlaced unless specified 720 x 400 @ 70 Hz
otherwise.
                            640 x 480 @ 85 Hz, 75 Hz and 60 Hz
User-Modes                  Yes, 8 modes
Anti-Glare/Anti-Static      Yes/Yes
Asset Control               Yes, supported
Plug and Play               Yes
Icon Based On-Screen        Yes
Display Controls
User Controls               Brightness, Contrast            Yes
                            Size and Positioning            Yes
                            Pincushion (barrel)             Yes
                            Trapezoid                       Yes
                            Tilt (rotation)                 Yes
                            Selectable Color                Yes
                            temperature
                            Parallelogram                   Yes
                            Pincushion Balance              Yes
                            Exit                            Yes
                            Degauss                         Yes
                            Factory Reset/Recall            Yes
                            Current Display Mode            Yes
Approvals/                  UL/CSA/CUL Approval             Yes
Certifications              ISO9241-3, -7, -8 VDT           Yes
                            Guidelines Approval
                            MPR-II Compliant                Yes, select models
                            TCO ‘99                         Yes, select models
                            FCC Approval                    Yes
                            Microsoft® WHQL                 Yes
                            Certified
                            Energy Star Compliant           Yes
                            CE                              Yes
Maximum Pixel Clock         110 MHz
Speed
Power Supply                Universal; 100 to 240 V, 50 ± 3Hz and 60 ± 3Hz
Maximum Power Rating        = 100 W
                                            DA - 11017      North America — Version 3 — August 22, 2003 Page
QuickSpecs                                                                                                     HP CRT Monitor s750
Technical Specifications
Low Power Sleep Mode   <5W
Signal Cable           15-pin miniature D-sub, attached, 4.9 ft (1.5 m)
Dimensions (H x W x D) Unpacked                         17 x 16.6 x 17.5 in (43.2 x 41 x 44.5 cm)
                       Packaged                         18.9 x 20.3 x 22.1 in (48 x 51.6 x 56.1 cm)
Weight                 Unpacked                         38 lb (17.23 kg)
                       Packaged                         46.2 lb (20.9 kg)
Operating Temperature  50° to 95° F (10° to 35° C)
(non-condensing)
Operating Humidity     20% to 80%
(non-condensing)
Warranty               Limited one-year parts, one-year repair labor and one-year on-site service warranty 48 hour advanced exchange service
                       available during warranty period. Certain restrictions and exclusions apply. For details, contact HP Customer Support.

chmooreck

  • Gość
Slackware 12 i radeon x1600 Problem z niewyraźnym obrazem
« Odpowiedź #14 dnia: 2008-02-14, 15:42:44 »
Cytat: benek14
Przecież tam już coś takiego jest jeśli o to chodzi
W poście z 2008-02-12 17:16:58 nie było...
Dodaj tą linie jeszcze w sekcji używanej przez Ciebie konfiguracji (aticonfig-Screen[0]).

Do sekcji monitora nie zaszkodzi dopisać wartości odświeżania pionowego i poziomego.

I przeproś się z logami X'ów - tam na pewno jest napisane jakie tryby odrzucił i dlaczego.