problemi con driver ati su slack 12.2

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.
Avatar utente
Darkstar89
Packager
Packager
Messaggi: 372
Iscritto il: mer 17 dic 2008, 19:06
Nome Cognome: Francesco
Slackware: 13
Località: Sassari

Re: problemi con driver ati su slack 12.2

Messaggio da Darkstar89 »

Ho scaricato i driver dal sito
ufficiale e ho dato questo comando: "sh ati-driver-installer-8.28.8.run --buildpkg Slackware/All"
questo è il debug:


Creating directory fglrx-install
Verifying archive integrity... All good.
Uncompressing ATI Proprietary Linux Driver-8.28.8.....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
==================================================
ATI Technologies Linux Driver Installer/Packager
==================================================
The distribution 'Slackware' is not supported
Removing temporary directory: fglrx-install

Avatar utente
targzeta
Iper Master
Iper Master
Messaggi: 6643
Iscritto il: gio 3 nov 2005, 14:05
Nome Cognome: Emanuele Tomasi
Slackware: 64-current
Kernel: latest stable
Desktop: IceWM
Località: Carpignano Sal. (LE) <-> Pisa

Re: problemi con driver ati su slack 12.2

Messaggio da targzeta »

Ma hai visto il mio post precedente?

Spina
Se pensi di essere troppo piccolo per fare la differenza, prova a dormire con una zanzara -- Dalai Lama

Avatar utente
lucif3r0
Linux 3.x
Linux 3.x
Messaggi: 617
Iscritto il: mer 11 mag 2005, 0:00
Slackware: 13.1
Kernel: 2.6.33.4
Desktop: KDE 4.3

Re: problemi con driver ati su slack 12.2

Messaggio da lucif3r0 »

dark con la 9200 pro gli open vanno benissimo
io ci facevo girare sia compiz che beryl, e devo
dire che preferisco beryl... devi solo aggiungere
un po' di opzioni a xorg.conf

tarqui
Linux 0.x
Linux 0.x
Messaggi: 5
Iscritto il: dom 29 mar 2009, 12:04
Slackware: 12.2
Kernel: 2.6.29.1-smp
Desktop: kde
Contatta:

Re: problemi con driver ati su slack 12.2

Messaggio da tarqui »

accodo il mio problema (strano) sperando in un vostro aiuto.

comportamento sospetto:
startx lancia kde in risoluzione 1280x960@60Hz anzichè 1152x864@75Hz come indicato in xorg.conf (che segue)
se lascio questa risoluzione va tutto bene. se imposto (tramite desktop > configura desktop > display o con la krandrtray) una risoluzione diversa succede una delle seguenti anomalie:
1) lo schermo si spegne, la tastiera è bloccata (il tutto di punto in bianco mentre faccio qualsiasi cosa) e devo spegnere tramite il pulsante di accensione del case (acpi quindi è ancora attivo e mi lancia la procedura di arresto, non è uno spegnimento brutale)
- oppure -
2) lo schermo resta bloccato tranne il movimento a scatti del mouse (che non prende nessun comando) idem tastiera e procedura di spegnimento come sopra.

escludo problema hardware (in windows xp non capita)

la prossima volta che capita vi posto il Xorg.0.log prima di lanciare X (init 3 all'avvio come predefinito della slackware 12.2)

configurazione:
ati radeon 9250 128M TVO (non collegata tv)
xorg.conf generato con xorgconfig

Codice: Seleziona tutto

# 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(5) man page for details about the format of 
# this file.
# **********************************************************************

# **********************************************************************
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

    Load        "dbe"  	# Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
    SubSection  "extmod"
      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection

# This loads the font modules
#    Load        "type1"
    Load        "freetype"
#    Load        "xtt"

# This loads the GLX module
    Load       "glx"
# This loads the DRI module
#    Load       "dri"

EndSection

# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

#    RgbPath	"/usr/share/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
# 
# 

    FontPath   "/usr/share/fonts/TTF"
    FontPath   "/usr/share/fonts/OTF"
    FontPath   "/usr/share/fonts/Type1"
    FontPath   "/usr/share/fonts/misc"
    FontPath   "/usr/share/fonts/75dpi/:unscaled"
#    FontPath   "/usr/lib/X11/fonts/local/"
    FontPath   "/usr/lib/X11/fonts/misc/"
    FontPath   "/usr/lib/X11/fonts/75dpi/:unscaled"
    FontPath   "/usr/lib/X11/fonts/100dpi/:unscaled"
    FontPath   "/usr/lib/X11/fonts/Speedo/"
    FontPath   "/usr/lib/X11/fonts/Type1/"
    FontPath   "/usr/lib/X11/fonts/TTF/"
    FontPath   "/usr/lib/X11/fonts/OTF/"
    FontPath   "/usr/lib/X11/fonts/cyrillic/"
    FontPath   "/usr/lib/X11/fonts/75dpi/"
    FontPath   "/usr/lib/X11/fonts/100dpi/"

# The module search path.  The default path is shown here.

#    ModulePath "/usr/lib/xorg/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is 
# received.  This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

#    Option "NoTrapSignals"

# Uncomment this to disable the <Ctrl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

#    Option "DontVTSwitch"

# Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

#    Option "DontZap"

# Uncomment this to disable the <Ctrl><Alt><KP_+>/<KP_-> mode switching
# sequences.  This allows clients to receive these key events.

#    Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

#    Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client. 

#    Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings. 

#    Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

#    Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

    Identifier	"Keyboard1"
    Driver	"kbd"

    Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#    Option	"Xleds"      "1 2 3"

#    Option "LeftAlt"     "Meta"
#    Option "RightAlt"    "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#    Option "XkbModel"    "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"

    Option "XkbRules"	"xorg"
    Option "XkbModel"	"pc105"
    Option "XkbLayout"	"it"

EndSection


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

Section "InputDevice"

# Identifier and driver

    Identifier	"Mouse1"
    Driver	"mouse"
    Option "Protocol"    "IMPS/2"	# IntelliMouse PS/2
    Option "Device"      "/dev/input/mice"

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

    Option "ZAxisMapping"   "4 5 6 7"

# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

#    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"

# ChordMiddle is an option for some 3-button Logitech mice

#    Option "ChordMiddle"

EndSection


# **********************************************************************
# Other input device sections 
# this is optional and is required only if you
# are using extended input devices.  This is for example only.  Refer
# to the 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

Section "Monitor"

    Identifier  "crt"

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

#    HorizSync	30-64         # multisync
#    HorizSync	31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync	15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    VertRefresh 50-120

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
    Identifier	"Standard VGA"
    VendorName	"Unknown"
    BoardName	"Unknown"

# The chipset line is optional in most cases.  It can be used to override
# the driver's chipset detection, and should not normally be specified.

#    Chipset	"generic"

# The Driver line must be present.  When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module.  Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

    Driver     "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for.  When this line isn't present, a device
# section can only match up with the primary video device.  For PCI
# devices a line like the following could be used.  This line should not
# normally be included unless there is more than one video device
# intalled.

#    BusID      "PCI:0:10:0"

#    VideoRam	256

#    Clocks	25.2 28.3

EndSection

# Device configured by xorgconfig:

Section "Device"
    Identifier  "ati radeon 9250 agp 128M tvo"
    Driver      "radeon"
    #VideoRam    131072
    # Insert Clocks lines here if appropriate
EndSection


# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
    Identifier  "Screen 1"
    Device      "ati radeon 9250 agp 128M tvo"
    Monitor     "crt"
    DefaultDepth 24

    Subsection "Display"
        Depth       8
        Modes       "1152x864" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "1152x864" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1152x864" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes
# the way multiple screens are organised.  A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option.  In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
    Identifier  "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.

    Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection

# Section "DRI"
#    Mode 0666
# EndSection


tarqui
Linux 0.x
Linux 0.x
Messaggi: 5
Iscritto il: dom 29 mar 2009, 12:04
Slackware: 12.2
Kernel: 2.6.29.1-smp
Desktop: kde
Contatta:

Re: problemi con driver ati su slack 12.2

Messaggio da tarqui »

ho notato che con un utente nuovo non capitava.
allora ho fatto un po' di pulizia nella mia directory home e adesso pare che vada tutto bene.
probabilmente mi è rimasto qualche file di impostazioni strane di altre distribuzioni che andava in conflitto con la slackware.
speriamo in bene.

Avatar utente
Darkstar89
Packager
Packager
Messaggi: 372
Iscritto il: mer 17 dic 2008, 19:06
Nome Cognome: Francesco
Slackware: 13
Località: Sassari

Re: problemi con driver ati su slack 12.2

Messaggio da Darkstar89 »

Ciao e auguri..
Ho ancora un probl con la mia ati, ho provato ad aggiornale il kernel al 2.6.29.1
e ho installato i driver ati "ati-driver-installer-9-3-x86.x86_64.run" con --Slackware/All, ma:
aticonfig --initial dà "aticonfig: No supported adapters detected"
e
modprobe fglrx dà "FATAL: Module fglrx not found."
Sapete aiutarmi grazie :D

Avatar utente
Blallo
Packager
Packager
Messaggi: 3302
Iscritto il: ven 12 ott 2007, 11:37
Nome Cognome: Savino Liguori
Slackware: 14.2 / 12.2
Kernel: 4.4.14-smp
Desktop: DWM
Località: Torino / Torremaggiore (FG)
Contatta:

Re: problemi con driver ati su slack 12.2

Messaggio da Blallo »

è sicuramente una imìncompatibilità del driver proprietario con il kernel nuovo...anche a me lo fa..
sono passato agli open...
basta aggiornare le mesa e il frame rate è abbatsnza decente...
con mesa7.2 e atix1300, driver open, 1190 fps di media con glxgears (anche se il sistema non è molto fluido)

Avatar utente
Darkstar89
Packager
Packager
Messaggi: 372
Iscritto il: mer 17 dic 2008, 19:06
Nome Cognome: Francesco
Slackware: 13
Località: Sassari

Re: problemi con driver ati su slack 12.2

Messaggio da Darkstar89 »

Grazie Jimmy, stavo provando ad aggiornare Mesa alla 7.4, ma durante la compilazione mi viene richiesta libdrm
ho modificato la path "PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/lib/pkgconfig:/usr/lib/" ma mi veniva richiesta libdrm>= 2.4.3 allora ho scaricato la 2.4.9 ma durante la compilazione ho trovato questi errori

Codice: Seleziona tutto

Making all in libdrm
make[1]: Entering directory `/home/Francesco/Desktop/libdrm-2.4.9/libdrm'
make  all-recursive
make[2]: Entering directory `/home/Francesco/Desktop/libdrm-2.4.9/libdrm'
Making all in .
make[3]: Entering directory `/home/Francesco/Desktop/libdrm-2.4.9/libdrm'
make[3]: Leaving directory `/home/Francesco/Desktop/libdrm-2.4.9/libdrm'
Making all in intel
make[3]: Entering directory `/home/Francesco/Desktop/libdrm-2.4.9/libdrm/intel'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/home/Francesco/Desktop/libdrm-2.4.9/libdrm/intel'
make[2]: Leaving directory `/home/Francesco/Desktop/libdrm-2.4.9/libdrm'
make[1]: Leaving directory `/home/Francesco/Desktop/libdrm-2.4.9/libdrm'
Making all in shared-core
make[1]: Entering directory `/home/Francesco/Desktop/libdrm-2.4.9/shared-core'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/Francesco/Desktop/libdrm-2.4.9/shared-core'
Making all in tests
make[1]: Entering directory `/home/Francesco/Desktop/libdrm-2.4.9/tests'
Making all in modeprint
make[2]: Entering directory `/home/Francesco/Desktop/libdrm-2.4.9/tests/modeprint'
/bin/sh ../../libtool --tag=CC   --mode=link gcc -I../../shared-core -I../../libdrm/intel/ -I../../libdrm -g -O2   -o modeprint modeprint.o ../../libdrm/libdrm.la ../../libdrm/intel/libdrm_intel.la
libtool: link: cannot find the library `3D/libdrm-2.4.9/libdrm/libdrm.la' or unhandled argument `3D/libdrm-2.4.9/libdrm/libdrm.la'
make[2]: *** [modeprint] Error 1
make[2]: Leaving directory `/home/Francesco/Desktop/libdrm-2.4.9/tests/modeprint'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/Francesco/Desktop/libdrm-2.4.9/tests'
make: *** [all-recursive] Error 1
Sapete come rimediare, grazie, e fatemi sapere se ho fatto qualche errore modificando la path..
Saluti :D :D

tarqui
Linux 0.x
Linux 0.x
Messaggi: 5
Iscritto il: dom 29 mar 2009, 12:04
Slackware: 12.2
Kernel: 2.6.29.1-smp
Desktop: kde
Contatta:

Re: problemi con driver ati su slack 12.2

Messaggio da tarqui »

niente da fare.
kernel-huge-smp-2.6.27.7_smp-i686-1 + xf86-video-ati-6.9.0-i486-1 (predefiniti sulla slackwre stable 12.2) = blocco video.
unica soluzione, per il momento, usare i driver vesa (60Hz :( ).
proverò al più presto ad aggiornare manualmente kernel, e mesa (e magari driver ati) e vi farò sapere.

tarqui
Linux 0.x
Linux 0.x
Messaggi: 5
Iscritto il: dom 29 mar 2009, 12:04
Slackware: 12.2
Kernel: 2.6.29.1-smp
Desktop: kde
Contatta:

Re: problemi con driver ati su slack 12.2

Messaggio da tarqui »

ho aggiornato kernel (+ modules + firmware) da 2.6.27.7 a 2.6.29.1 ma succede ancora.
provvederò al più presto ad aggiornare mesa.

Rispondi