Pagina 1 di 1

Aiuto per risoluzione video

Inviato: sab 21 ott 2006, 4:24
da Tux1973
Ciao a tutti, proprio ora ho finito di tirare sù, la slack 11.0 con kernel 2.6.18, sembra andare tutto ok, ora la mia domanda è avendo installato dei driver ATI 8.29.6, nonstante ho letto che non funzionavano devo dire che almeno nel mio caso non è cosi nel senso, che una volta finito di installarli con il file .run,ho inserito nel fstab "tmpfs......", ho riavviato e devo dire la verità una volta ripartita ho notato che facendo tutti i controlli come dalla guida di samiel è andato tutto ok,inoltre ho verificato tramite i screen saver 3d e sembra tutto bene, l unica cosa che mi è poco chiara come mai ad ogni riavvio la risoluzione mi parte a 1400x1050, nonstante nel file xorg.conf, sia settato
DefaultDepth 24
SubSection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480",
ed inoltre anche andando tramite kde a cambiarla manualmente a 1024x768, quasi tutto ritorna ok, ma alcune cose tipo la shell e varie, rimangono con dei caratteri molto piccoli, come posso risolvere questa situazione.

Grazie a tutti coloro che mi vorranno aiutare

Tux :oops: ;)

Inviato: sab 21 ott 2006, 7:48
da linus.bash
Prova Xorg come è da me...cambia solo i dati della scheda.

Codice: Seleziona tutto

Section "Screen"
    Identifier  "Screen 1"
    Device      "i915gm"
    Monitor     "intel"
    DefaultDepth 24

    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       "1024x768"
        ViewPort    0 0
    EndSubsection
EndSection

Sempre driver video ati

Inviato: sab 21 ott 2006, 11:53
da Tux1973
Grazie per la risposta ma nisba, qualche altro suggerimento sul da farsi??

GRazie sempre a tutti

P.s. voglio ricordare che il mio è un portatile

Tux

:cry: ;)

Inviato: sab 21 ott 2006, 13:50
da pino.giaquinto
Fammi dare un'occhiata al tuo xorg.conf che provo ad aiutarti...

Sempre Driver Video

Inviato: sab 21 ott 2006, 14:50
da Tux1973
Ti ringrazio anticipatamente, questo è il mio xorg.conf


# 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/X11R6/lib/modules"
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/"
EndSection

Section "Module"

# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
# 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"
Load "dri"
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" "pc101"
# 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" "IMPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
# 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"
ViewPort 0 0
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubSection
SubSection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubSection
SubSection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
ViewPort 0 0
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

GRazie a tutti

Tux :roll: ;)

Inviato: sab 21 ott 2006, 17:14
da pino.giaquinto
Cancella (o commenta se preferisci) la sezione Monitor:

Codice: Seleziona tutto

Section "Monitor"
  Identifier "My Monitor" 
  HorizSync 31.5 - 50.0 
  VertRefresh 40.0 - 90.0 
EndSection
e lascia solo quella che segue:

Codice: Seleziona tutto

Section "Monitor" 
  Identifier "aticonfig-Monitor[0]" 
  Option "VendorName" "ATI Proprietary Driver" 
  Option "ModelName" "Generic Autodetecting Monitor" 
  Option "DPMS" "true" 
EndSection
Cancella (o commenta... se vuoi) la sezione Screen:

Codice: Seleziona tutto

Section "Screen"
  Identifier "Screen 1" 
  Device "VESA Framebuffer" 
  Monitor "My Monitor" 
  DefaultDepth 24 
  SubSection "Display" 
  Depth 8 
  Modes "1024x768" "800x600" "640x480" 
  ViewPort 0 0 
  EndSubSection 
  SubSection "Display" 
  Depth 16 
  Modes "1024x768" "800x600" "640x480" 
  ViewPort 0 0 
  EndSubSection 
  SubSection "Display" 
  Depth 24 
  Modes "1024x768" "800x600" "640x480" 
  ViewPort 0 0 
  EndSubSection 
  SubSection "Display" 
  Depth 32 
  Modes "1024x768" "800x600" "640x480" 
  ViewPort 0 0 
  EndSubSection 
EndSection
e modifica l'altra sezione Screen come segue:

Codice: Seleziona tutto

Section "Screen" 
  Identifier "aticonfig-Screen[0]" 
  Device "aticonfig-Device[0]" 
  Monitor "aticonfig-Monitor[0]" 
  DefaultDepth 24 
  SubSection "Display" 
    Viewport 0 0 
    Depth 8
    Modes "1024x768"
  EndSubSection 
  SubSection "Display" 
    Viewport 0 0 
    Depth 16
    Modes "1024x768"
  EndSubSection
  SubSection "Display" 
    Viewport 0 0 
    Depth 24
    Modes "1024x768"
  EndSubSection
  SubSection "Display" 
    Viewport 0 0 
    Depth 32
    Modes "1024x768"
  EndSubSection
EndSection
Se non funziona, fammi sapere qual'è l'output di:

Codice: Seleziona tutto

grep 'Using config file' /var/log/Xorg.0.log
Spero di esserti stato utile ;-)

Aiuto per caratteri piccoli

Inviato: sab 21 ott 2006, 19:34
da Tux1973
Ti ringrazio per la risposta, allora la situazione attuale è che la risoluzione è ok a 1024x768, solo che adesso mi è rimasto un altro problema cioè , che tutti i caratteri del menu K ,della shell , e varie sono diventati molto piccoli, mi daresti una manina per risolvere quest ultimo arcano.....

Grazie

Tux :roll: :oops: ;)

Inviato: sab 21 ott 2006, 19:37
da linus.bash
Puoi settarli dal pannello di kde...ma comunque samiel ha messo a disposizione un pacchetto font che prelevai l'anno scorso...non ricordo ora dove si trova...domanda a lui o cerca in download di slacky ;)

E dopo

Inviato: sab 21 ott 2006, 19:44
da Tux1973
Scusami per la mia ignoranza e dopo come procedo???

:oops: :oops: :oops: :oops: :oops: ;)

Inviato: sab 21 ott 2006, 20:12
da pino.giaquinto
Per cambiare la dimensione ed il tipo di font: Centro di controllo->Aspetto e Temi->Tipi di carattere.

Re: Aiuto per caratteri piccoli

Inviato: sab 21 ott 2006, 20:54
da slacky4ever
Tux1973 ha scritto:Ti ringrazio per la risposta, allora la situazione attuale è che la risoluzione è ok a 1024x768, solo che adesso mi è rimasto un altro problema cioè , che tutti i caratteri del menu K ,della shell , e varie sono diventati molto piccoli, mi daresti una manina per risolvere quest ultimo arcano.....

Grazie

Tux :roll: :oops: ;)
Per caso è abilitata la funzione antivirus nel BIOS?
La cosa sembra non avere molto senso. Però ...
Tempo fa mi è capitato installando la 10.0.
Avevo il tuo stesso problema: risoluzione OK ma caratteri microscopici e illegibili.
Il tutto si è risolto come per magia disabilitando, appunto, l'antivirus del BIOS.
In questo caso mi è stato d'aiuto Windows XP, che alla partenza mi si è piantato segnalandomi il problema.
Saluti.
S.Bellomo.