Problema Xorg.conf

Se avete problemi con l'installazione e la configurazione di Slackware postate qui. Non usate questo forum per argomenti generali... per quelli usate Gnu/Linux in genere.

Moderatore: Staff

Regole del forum
1) Citare sempre la versione di Slackware usata, la versione del Kernel e magari anche la versione della libreria coinvolta. Questi dati aiutano le persone che possono rispondere.
2) Per evitare confusione prego inserire in questo forum solo topic che riguardano appunto Slackware, se l'argomento è generale usate il forum Gnu/Linux in genere.
3) Leggere attentamente le risposte ricevute.
4) Scrivere i messaggi con il colore di default, evitare altri colori.
5) Scrivere in Italiano o in Inglese, se possibile grammaticalmente corretto, evitate stili di scrittura poco chiari, quindi nessuna abbreviazione tipo telegramma o scrittura stile SMS o CHAT.
6) Appena registrati è consigliato presentarsi nel forum dedicato.

La non osservanza delle regole porta a provvedimenti di vari tipo da parte dello staff, in particolare la non osservanza della regola 5 porta alla cancellazione del post e alla segnalazione dell'utente. In caso di recidività l'utente rischia il ban temporaneo.
Rispondi
Feste
Linux 2.x
Linux 2.x
Messaggi: 388
Iscritto il: ven 21 ott 2005, 14:24
Slackware: 13
Desktop: KDE 4.2.4
Località: /home/feste

Problema Xorg.conf

Messaggio da Feste »

Ho una radeon 9600

Ho installato i driver dal sito ufficiale

Ho fatto aticonfig --initial

E' stato modificato lo xorg.conf

Quando loggo ho una risoluzione 1600x1200, ma se provo a cambiarla e metterla a 1280x1024 mi si blocca slacky, non mi fa aprire directory, console niente di niente, posso solo terminare la sessione e rifare startx e allora ritorna a 1600 e non è più bloccato

Inoltre non ho l'accelerazione grafica

Posto lo xorg.conf

Codice: Seleziona tutto

# 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" "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
devo modificare qualcosa perchè non si blocchi e funzioni l'accelerazione grafica?

o devo cercare il problema altrove?

grazie

Feste
Linux 2.x
Linux 2.x
Messaggi: 388
Iscritto il: ven 21 ott 2005, 14:24
Slackware: 13
Desktop: KDE 4.2.4
Località: /home/feste

Messaggio da Feste »

ah premetto che è 1 anno che provo a far funzionare la mia ati e tutte le soluzioni postate purtroppo non mi hanno aiutato, questa volta con la versione 11 di slacky spero di riuscire a farla funzionare

Avatar utente
zappa
Linux 1.x
Linux 1.x
Messaggi: 143
Iscritto il: gio 8 set 2005, 0:00
Slackware: 13.37 & 14
Kernel: 3.4.11-RT & 3.2.29 & 2.6.37
Desktop: KDE
Località: cagliari
Contatta:

Messaggio da zappa »

ciao,
prova a mettere da parte lo xorg.conf originale e se hai usato l'installer della ati avrai sicuramente problemi....ti consiglio di leggerti i file di log che vengono creati durante l'installazione.......io ho scaricato l'rpm dal sito ati, l'ho convertito in tgz , l'ho installato e poi sono andato nella directory /lib/modules/fglrx/build_mod ho lanciato sh make.sh poi sono andato nella directory superiore e ho lanciato sh make_install, ho caricato il modulo fglrx, ricorda di attivare il supporto agp come modulo e il supporto drm (o dri,nn mi ricordo bene) come modulo.......ho rifatto aticonfig --initial e funziona tutto bene, solo che se ricompili il kernel devi ovviamente ricompilare il modulo fglrx..........comunque prima ti conviene anche provare a lanciare xorgconfig che crea un nuovo xorg.conf..........dovresti leggere "ATI Radeon FAQ" per Gentoo, il problema e' che non mi ricordo dove l'ho trovato, e poi leggiti how to di slacky, io ho risolto cosi'..........

Feste
Linux 2.x
Linux 2.x
Messaggi: 388
Iscritto il: ven 21 ott 2005, 14:24
Slackware: 13
Desktop: KDE 4.2.4
Località: /home/feste

Messaggio da Feste »

zappa ha scritto:ciao,
prova a mettere da parte lo xorg.conf originale e se hai usato l'installer della ati avrai sicuramente problemi....ti consiglio di leggerti i file di log che vengono creati durante l'installazione.......io ho scaricato l'rpm dal sito ati, l'ho convertito in tgz , l'ho installato e poi sono andato nella directory /lib/modules/fglrx/build_mod ho lanciato sh make.sh poi sono andato nella directory superiore e ho lanciato sh make_install, ho caricato il modulo fglrx, ricorda di attivare il supporto agp come modulo e il supporto drm (o dri,nn mi ricordo bene) come modulo.......ho rifatto aticonfig --initial e funziona tutto bene, solo che se ricompili il kernel devi ovviamente ricompilare il modulo fglrx..........comunque prima ti conviene anche provare a lanciare xorgconfig che crea un nuovo xorg.conf..........dovresti leggere "ATI Radeon FAQ" per Gentoo, il problema e' che non mi ricordo dove l'ho trovato, e poi leggiti how to di slacky, io ho risolto cosi'..........
l'rpm sul sito ATI è per xorg 6.8, con la slack 11 non c'è il 6.9?

Posso installare l'rpm dopo avere eseguito il run o devo prima disinstallarlo?

zappa ha scritto:ricorda di attivare il supporto agp come modulo e il supporto drm (o dri,nn mi ricordo bene) come modulo
questo non lo so fare, mi spieghi come farlo? I passaggi sopra li ho fatti ma non hanno funzionato, magari perchè non ho attivato il supporto agp e drm

Grazie

Feste
Linux 2.x
Linux 2.x
Messaggi: 388
Iscritto il: ven 21 ott 2005, 14:24
Slackware: 13
Desktop: KDE 4.2.4
Località: /home/feste

Messaggio da Feste »

ho disinstallato or ora i driver ati

ho preso il pacchetto rpm l'ho convertito in tgz

ho fatto tutto fino a modprobe fglrx

poi ho fatto aticonfig --initial

mi ha modificato lo xorg.conf , ma facendo startx mi ha dato errore, così ho dovuto mettere quello vecchio

da lsmod mi sembra che i moduli siano caricati

Codice: Seleziona tutto

Module                  Size  Used by
bsd_comp                5760  0
ipt_LOG                 6400  3
xt_tcpudp               3328  6
iptable_filter          2432  1
ip_tables              11480  1 iptable_filter
x_tables               10756  3 ipt_LOG,xt_tcpudp,ip_tables
ppp_synctty             7424  0
ppp_async               8960  1
crc_ccitt               2048  1 ppp_async
ppp_generic            22804  7 bsd_comp,ppp_synctty,ppp_async
slhc                    6400  1 ppp_generic
fglrx                 391852  0
snd_seq_dummy           2948  0
snd_seq_oss            29056  0
snd_seq_midi_event      6016  1 snd_seq_oss
snd_seq                43856  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_pcm_oss            42144  0
snd_mixer_oss          14976  1 snd_pcm_oss
ipv6                  225248  14
pcmcia                 30372  0
yenta_socket           24204  0
rsrc_nonstatic         10880  1 yenta_socket
pcmcia_core            34064  3 pcmcia,yenta_socket,rsrc_nonstatic
capability              3464  0
commoncap               5504  1 capability
lp                      9928  0
parport_pc             24260  1
parport                30152  2 lp,parport_pc
psmouse                35464  0
shpchp                 33052  0
sg                     26780  0
evdev                   8192  0
snd_via82xx            22808  0
gameport               11144  1 snd_via82xx
snd_ac97_codec         86944  1 snd_via82xx
snd_ac97_bus            2176  1 snd_ac97_codec
snd_pcm                67720  3 snd_pcm_oss,snd_via82xx,snd_ac97_codec
snd_timer              19460  2 snd_seq,snd_pcm
snd_page_alloc          7816  2 snd_via82xx,snd_pcm
snd_mpu401_uart         6528  1 snd_via82xx
snd_rawmidi            18848  1 snd_mpu401_uart
snd_seq_device          6540  4 snd_seq_dummy,snd_seq_oss,snd_seq,snd_rawmidi
snd                    42724  11 snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_via82xx,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
soundcore               7264  1 snd
sk98lin               152800  0
skge                   34064  0
serio_raw               5380  0
amd64_agp               9988  1
agpgart                28208  2 fglrx,amd64_agp
i2c_viapro              7700  0
pcspkr                  2560  0

Avatar utente
zappa
Linux 1.x
Linux 1.x
Messaggi: 143
Iscritto il: gio 8 set 2005, 0:00
Slackware: 13.37 & 14
Kernel: 3.4.11-RT & 3.2.29 & 2.6.37
Desktop: KDE
Località: cagliari
Contatta:

Messaggio da zappa »

io uso il kernel 2.6.
per vedere se hai il DRM attivo come modulo lancia da shell il seguente commando: cat /boot/config-2.6.17.13-vale | grep DRM
che ti rende piu o meno questo output :
CONFIG_DRM=m
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=m
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set

come puoi notare DRM e' attivo come modulo, in tal caso se occorre viene caricato, questo l'ho letto sulla FAQ che ti ho detto.......

facciamo prima se ti posto il mio xorg.conf:
==========================================================

# File generated by xorgconfig.
#
# Copyright 2004 The X.Org Foundation
#
# 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 X.Org Foundation 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 X.Org Foundation 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 X.Org Foundation.
#
# **********************************************************************
# Refer to the xorg.conf(5x) man page for details about the format of
# this file.
# **********************************************************************
# **********************************************************************
# 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
# **********************************************************************
# **********************************************************************
# 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 xorg.conf 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
# **********************************************************************
# Graphics device section
# **********************************************************************
# Any number of graphics device sections may be present
# Standard VGA Device:
# Device configured by xorgconfig:
# **********************************************************************
# 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)
#
#
# The module search path. The default path is shown here.
# ModulePath "/usr/X11R6/lib/modules"
RgbPath "/usr/X11R6/lib/X11/rgb"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/TTF/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/CID/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
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 "speedo"
Load "freetype"
# Load "xtt"
Load "glx"
# This loads the DRI module
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"
# 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" "pc105"
# 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 Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Identifier "Keyboard1"
Driver "kbd"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"

# Identifier and driver
# the following line.
# Option "Protocol" "Xqueue"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7. Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.
# 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" # IntelliMouse PS/2
Option "Device" "/dev/mouse"
# When using XQUEUE, comment out the above two lines, and uncomment
Option "ZAxisMapping" "4 5 6 7"
# Emulate3Buttons is an option for 2-button mice
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 - 64.3
VertRefresh 50.0 - 70.0
EndSection

Section "Monitor"
Identifier "aticonfig Monitor 0"
EndSection

Section "Device"

# 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.
# 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
Identifier "Standard VGA"
Driver "vga"
VendorName "Unknown"
BoardName "Unknown"
EndSection

Section "Device"

# unsupported card
#VideoRam 131072
# Insert Clocks lines here if appropriate
Identifier "My Video Card"
Driver "vga"
EndSection

Section "Device"
Identifier "ATI Graphics Adapter 0"
Driver "fglrx"
Option "(null)"
Option "UseInternalAGPGART" "on"
Option "Capabilities" "0x00000000"
Option "DesktopSetup" "single"
BusID "PCI:3:0:0"
EndSection

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 "ATI Graphics Adapter 0"
Monitor "aticonfig Monitor 0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Section "DRI"
Mode 0666
EndSection
=======================================================

prova ad usare questo considerando che io ho un notebook con ati radeon x300 e un mouse usb assieme a quello integrato..........

se il modulo DRM non e' abilitato devi ricompilare il kernel per includerlo come modulo, anche se non sono del tutto sicuro che sto modulo sia necessario....
Premetto anche cha la slack 11 o meglio lo X.org contenuto nella slack 11 funziona sicuramente in modo differente dal precedente contenuto nella slack 10.2 perche' ho provato col vecchio config ma il mouse usb va per i fatti suoi.......

comunque anche io ho dovuto smanettare un bel po' prima di essere soddisfatto

Avatar utente
zappa
Linux 1.x
Linux 1.x
Messaggi: 143
Iscritto il: gio 8 set 2005, 0:00
Slackware: 13.37 & 14
Kernel: 3.4.11-RT & 3.2.29 & 2.6.37
Desktop: KDE
Località: cagliari
Contatta:

Messaggio da zappa »

dimenticavo.....
ti ha dato un errore o semplicemente e' venuta fuori una schermata nera, perche' di solito nel messaggio di errore c'e' scritto il tipo di errore e se nel config c'e' qualche riga che non va ti dice quale riga e potresti provare a commentarla...

io prima avevo imposto che il touchpad venisse spento e si utilizzasse solo il mouse usb, di conseguenza se il mouse usb non era connesso kde non si avviava e mi diceva proprio che il mouse non era presente..........

spero di averti dato una mano o almeno qualche spunto......

Avatar utente
zappa
Linux 1.x
Linux 1.x
Messaggi: 143
Iscritto il: gio 8 set 2005, 0:00
Slackware: 13.37 & 14
Kernel: 3.4.11-RT & 3.2.29 & 2.6.37
Desktop: KDE
Località: cagliari
Contatta:

Messaggio da zappa »

ho ritrovato la guida che dovresti leggere assieme aquella di slacky

http://www.gentoo.it/doc/ati-radeon-faq.html

ti consiglio di leggerne alcune per capire meglio, perche' delle volte ognuno ha il suo metodo per risolvere i problemi e potrebbe darsi che alcuni problemi si risolvano in maniera casuale indipendentemente dal metodo usato...... :? :)

Feste
Linux 2.x
Linux 2.x
Messaggi: 388
Iscritto il: ven 21 ott 2005, 14:24
Slackware: 13
Desktop: KDE 4.2.4
Località: /home/feste

Messaggio da Feste »

grazie mille lo leggo subito :)

Feste
Linux 2.x
Linux 2.x
Messaggi: 388
Iscritto il: ven 21 ott 2005, 14:24
Slackware: 13
Desktop: KDE 4.2.4
Località: /home/feste

Messaggio da Feste »

zappa ha scritto:io uso il kernel 2.6.
per vedere se hai il DRM attivo come modulo lancia da shell il seguente commando: cat /boot/config-2.6.17.13-vale | grep DRM
in /boot/ ho solo config e config-ide-2.4.33.3

edit funge e ottengo

Codice: Seleziona tutto

CONFIG_DRM=m
CONFIG_DRM_TDFX=m
CONFIG_DRM_R128=m
CONFIG_DRM_RADEON=m
CONFIG_DRM_I810=m
CONFIG_DRM_I830=m
CONFIG_DRM_I915=m
CONFIG_DRM_MGA=m
CONFIG_DRM_SIS=m
CONFIG_DRM_VIA=m
CONFIG_DRM_SAVAGE=m

Feste
Linux 2.x
Linux 2.x
Messaggi: 388
Iscritto il: ven 21 ott 2005, 14:24
Slackware: 13
Desktop: KDE 4.2.4
Località: /home/feste

Messaggio da Feste »

Dall'howto di slacky leggo che facendo girare glxgears:

se il risultato è superiore a 1000 l'accelerazione grafica funge altrimenti no

se lo lancio mi da

Codice: Seleziona tutto

1062 frames in 5.0 seconds = 212.305 FPS
1186 frames in 5.0 seconds = 236.931 FPS
1286 frames in 5.0 seconds = 256.751 FPS
1301 frames in 5.0 seconds = 260.131 FPS
se lo lancio e poi cambio desktop i valori diventano

Codice: Seleziona tutto

36868 frames in 5.0 seconds = 7373.575 FPS
36301 frames in 5.0 seconds = 7260.158 FPS
36835 frames in 5.0 seconds = 7366.929 FPS
37298 frames in 5.0 seconds = 7459.572 FPS
è normale o è dovuto al fatto che non riesco a settare bene la scheda?

Feste
Linux 2.x
Linux 2.x
Messaggi: 388
Iscritto il: ven 21 ott 2005, 14:24
Slackware: 13
Desktop: KDE 4.2.4
Località: /home/feste

Messaggio da Feste »

Questo è l'errore che ottengo provando a fare andare un gioco 3d

Codice: Seleziona tutto

check: OpenGL error 1285 detected: out of memory (GLuint meng::renderer::Stream::create_vbo_memory_block(const meng::renderer::stream_meta_data::StreamMetaData&, const meng::byte*)) (stream_memory_opengl.cpp:70)

Avatar utente
zappa
Linux 1.x
Linux 1.x
Messaggi: 143
Iscritto il: gio 8 set 2005, 0:00
Slackware: 13.37 & 14
Kernel: 3.4.11-RT & 3.2.29 & 2.6.37
Desktop: KDE
Località: cagliari
Contatta:

Messaggio da zappa »

Il problema e' sempre lo stesso non hai i driver installati oppure quei driver non supportano la tua scheda........il fatto che se cambi desktop aumenta il frame rate, e' ovvio dal momento che l'immagine (le rotelle che girano) e' nascosta e non viene disegnata sullo schermo prova anche il comando fgl_glxgears che credo seva proprio per il 3d, ame non funziona quando il driver non e' bene installato.....
mi dispiace ma non so che altro dirti.......cerca ancora con google se qualcuno ha la tua stessa scheda........... :(

Feste
Linux 2.x
Linux 2.x
Messaggi: 388
Iscritto il: ven 21 ott 2005, 14:24
Slackware: 13
Desktop: KDE 4.2.4
Località: /home/feste

Messaggio da Feste »

Codice: Seleziona tutto

i82365                 23008  1
bsd_comp                5760  0
ipt_LOG                 6400  0
xt_tcpudp               3328  0
iptable_filter          2432  0
ip_tables              11480  1 iptable_filter
x_tables               10756  3 ipt_LOG,xt_tcpudp,ip_tables
ppp_synctty             7424  0
ppp_async               8960  1
crc_ccitt               2048  1 ppp_async
ppp_generic            22804  7 bsd_comp,ppp_synctty,ppp_async
slhc                    6400  1 ppp_generic
fglrx                 391852  8
snd_seq_dummy           2948  0
snd_seq_oss            29056  0
snd_seq_midi_event      6016  1 snd_seq_oss
snd_seq                43856  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_pcm_oss            42144  0
snd_mixer_oss          14976  1 snd_pcm_oss
ipv6                  225248  22
pcmcia                 30372  0
yenta_socket           24204  0
rsrc_nonstatic         10880  2 i82365,yenta_socket
pcmcia_core            34064  4 i82365,pcmcia,yenta_socket,rsrc_nonstatic
capability              3464  0
commoncap               5504  1 capability
lp                      9928  0
parport_pc             24260  1
parport                30152  2 lp,parport_pc
psmouse                35464  0
sk98lin               152800  0
evdev                   8192  0
sg                     26780  0
shpchp                 33052  0
skge                   34064  0
snd_via82xx            22808  1
gameport               11144  1 snd_via82xx
snd_ac97_codec         86944  1 snd_via82xx
snd_ac97_bus            2176  1 snd_ac97_codec
snd_pcm                67720  3 snd_pcm_oss,snd_via82xx,snd_ac97_codec
snd_timer              19460  2 snd_seq,snd_pcm
snd_page_alloc          7816  2 snd_via82xx,snd_pcm
snd_mpu401_uart         6528  1 snd_via82xx
snd_rawmidi            18848  1 snd_mpu401_uart
snd_seq_device          6540  4 snd_seq_dummy,snd_seq_oss,snd_seq,snd_rawmidi
snd                    42724  13 snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_via82xx,snd_ac97_codec,snd_pcm,snd_timer,snd_mpu401_uart,snd_rawmidi,snd_seq_device
i2c_viapro              7700  0
soundcore               7264  1 snd
serio_raw               5380  0
pcspkr                  2560  0
amd64_agp               9988  1
agpgart                28208  2 fglrx,amd64_agp
i moduli ci sono dovrebbero essere installati correttamente

o no?

Feste
Linux 2.x
Linux 2.x
Messaggi: 388
Iscritto il: ven 21 ott 2005, 14:24
Slackware: 13
Desktop: KDE 4.2.4
Località: /home/feste

Messaggio da Feste »

nessuno mi può aiutare?

Rispondi