S3 Graphics ProSavageDDR DRIVER

[n3tfr33]

Salve a tutti...avrei bisogno che qualcuno mi dicesse come configurare questa scheda video del mio portatile (S3 Graphics ProSavageDDR)...Grazie

[phobos3576]

Prima di tutto, apri una console ed esegui il comando /sbin/lspci.

Nell'output che ottieni, prendi nota della riga nella quale si parla di AGP Bridge (se non erro, la tua scheda è di tipo AGP).

Ad esempio, nel mio caso la riga in questione dice:

00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-751 [Irongate] AGP Bridge (rev 01)

Nel kernel devi abilitare il modulo agpgart, quello relativo all'AGP Bridge che ti dà lspci e l'opportuno modulo per il supporto della tua S3 Savage.

Dopo aver ricompilato il kernel e riavviato il computer, esegui da root il comando

modprobe savage

Ora edita il file /etc/X11/xorg.conf e modificalo in base alle informazioni che trovi qui:

http://www.xfree.org/current/savage.4.html

Eseguendo ora startx, dovresti avere l'accelerazione hardware per la tua scheda video.

Il comando modprobe savage lo puoi insterire anche in uno script che viene eseguito durante l'avvio di Linux; ad esempio, noi Slackwariani utilizziamo spesso /etc/rc.d/rc.local.

[n3tfr33]

grazie mille ma ti chiedo, per favore, di spiegarmi più chiaramente il passaggio"Nel kernel devi abilitare il modulo agpgart, quello relativo all'AGP Bridge che ti dà lspci e l'opportuno modulo per il supporto della tua S3 Savage"...grazie è per merito di persone pazienti come voi che linux si diffonde...

[phobos3576]

Naturalmente mi riferivo alla ricompilazione del kernel; non so se tu sei già in grado di affrontare questo passo, che è molto delicato, però è indispensabile per ottenere una linux-box più che efficiente.
Qui su Slacky.it puoi trovare i migliori tutorial in assoluto su tale argomento.

Durante la ricompilazione del kernel ad un certo punto si entra in un menu di configurazione attraverso il quale puoi gestire qualunque caratteristica hardware del tuo computer; naturalmente, in questa fase è importante avere a disposizione tutte le informazioni sull'hardware del proprio PC.

Comunque, se stai utilizzando una distribuzione Linux recente, è molto probabile che il tuo kernel sia già pre-configurato a dovere.

Da utente root, prima di entrare in modalità grafica, prova ad eseguire il comando

modprobe savage

e guarda quello che succede; se non compare nessun messaggio, vuol dire che è tutto a posto.

Puoi anche eseguire il comando:

lsmod | less

per vedere quali moduli del kernel sono stati caricati; controlla che siano presenti moduli del tipo agpgart, savage etc.

Modifica poi il file /etc/X11/xorg.conf come ti ho già spiegato e poi lancia startx.
Una volta che sei in modalità grafica, esegui da una console il programma glxinfo per sapere se l'accelerazione grafica è attiva (dovrebbe essere presente la riga Direct Rendering: Yes).

[n3tfr33]

Ok sei stato chiarissimo...ora mi metto al lavoro e ti faccio sapere come va!!! Gazie ancora

[n3tfr33]

Allora la parte di modprobe savage e di lsmod | less tutto ok...
i problemi arrivano con la modifica del file /etc/X11/xorg.conf ...sono andato a vedere la pagina di riferimento che mi hai indicato ma nonostante abbia aggiunto le opzioni necessarie ad attivare l'accellerazione grafica, ma quando lancio startx mi da errore e si blocca tutto...ho bisogno di aiuto per sapere cosa devo aggiungere e modificare esattamente nel file /etc/X11/xorg.conf ...ti ringrazio anticipatamente

[phobos3576]

Prova a postare il contenuto del file /etc/X11/xorg.conf (anche se è un po lunghetto).

Magari se mi dici anche quale modello di notebook hai ...

[n3tfr33]

Allora cominciamo con il modello del portatile che è più facile:
packardbell EASYNOTE E1266 e qui ci sono tutte le specifiche: http://support.packardbell.com/it/item/ ... 238&g=1400
Ora ti posto il file:
# 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.
# **********************************************************************
#
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 "speedo"

# This loads the GLX module
Load "glx"

EndSection

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

Section "Files"

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

RgbPath "/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#

FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/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/"

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

EndSection

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

Section "ServerFlags"

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

# Option "NoTrapSignals"

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

# Option "DontVTSwitch"

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

# Option "DontZap"

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

# Option "DontZoom"

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

# Set the basic blanking screen saver timeout.

# Option "blank time" "10" # 10 minutes

# Set the DPMS timeouts. These are set here because they are global
# rather than screen-specific. These settings alone don't enable DPMS.
# It is enabled per-screen (or per-monitor), and even then only when
# the driver supports it.

# Option "standby time" "20"
# Option "suspend time" "30"
# Option "off time" "60"

# On some platform the server needs to estimate the sizes of PCI
# memory and pio ranges. This is done by assuming that PCI ranges
# don't overlap. Some broken BIOSes tend to set ranges of inactive
# devices wrong. Here one can adjust how aggressive the assumptions
# should be. Default is 0.

# Option "EstimateSizesAggresively" "0"

EndSection

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

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

Section "InputDevice"

Identifier "Keyboard1"
Driver "kbd"
# 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" ""

EndSection


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

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"

Option "ZAxisMapping" "4 5"
Option "Buttons" "3"

# 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
Option "Protocol" "IMPS/2"

# The mouse device. The device is normally set to /dev/mouse,
# which is usually a symbolic link to the real device.

Option "Device" "/dev/mouse"
# Option "Device" "/dev/psaux"
# 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"

EndSection

# 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

Section "Monitor"

Identifier "My 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 31.5 - 150.0

# 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 75-85

EndSection


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

# Any number of graphics device sections may be present

Section "Device"
Identifier "VESA Framebuffer"
Driver "vesa"
#VideoRam 4096
# 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 "VESA Framebuffer"
Monitor "My Monitor"

# If your card can handle it, a higher default color depth (like 24 or 32)
# is highly recommended.

# DefaultDepth 8
# DefaultDepth 16
DefaultDepth 24
# 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)

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

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

[phobos3576]

Per la Section "Module" prova così

Codice: Seleziona tutto

Section "Module"

	Load			"dbe"			# Double buffer extension
	Load			"v4l"			# Video For Linux
	Load			"extmod"		# Miscellaneous extension module

	Load			"type1"
	Load			"freetype"
#	Load			"speedo"

	Load			"glx"
	Load			"dri"
    
EndSection

Subito dopo aggiungi la seguente sezione

Codice: Seleziona tutto

Section "DRI"
     Mode       0666
EndSection

Nella Section "Device" metti

Codice: Seleziona tutto

Section "Device"
	Identifier "VESA Framebuffer" 
	Driver		"savage"
EndSection

Mi restano dei dubbi in relazione al mouse e alla sezione "Monitor".
Magari, posta gli errori che vedi sulla console quando dai startx

[n3tfr33]

ho fatto tutto quello che mi hai detto e startx funziona senza nessun errore. ma una volta in modalità grafica lanciando da shell glxinfo leggo che l'accelerazione è ancora non attiva

[phobos3576]

Subito dopo che sei entrato in modalità grafica, apri il file /var/log/Xorg.0.log e controlla se ci sono delle righe che iniziano con (EE).
Quelle righe indicano gli errori che si sono verificati durante l'esecuzione di startx.

[n3tfr33]

Controllato...nessun errore

[phobos3576]

Mi sembra impossibile!

Nella Section "Device" di /etc/X11/xorg.conf prova ad aggiungere:

Option "UseBIOS" "false"

Prova anche a ridurre la profondità di colore; apri /etc/X11/xorg.conf, nella Section "Screen" commenta (con #) la linea

DefaultDepth 24

e decommenta la linea

DefaultDepth 16

Controlla, inoltre, che in /dev/dri sia presente il device card0; se non esiste, vuol dire che non hai configurato correttamente il kernel per il DRI.

Come ti ho già detto, anche se non c'entra nulla con l'accelerazione hardware,nella Section "Monitor" devi impostare dei valori adeguati per HorizSync e VertRefresh; quelli presenti in xorg.conf sono solo un esempio.

Gli sviluppatori del driver savage suggeriscono:

HorizSync 30-70
VertRefresh 50-90


Comunque, nella documentazione allegata al tuo notebook dovrebbero essere presenti informazioni più dettagliate.

[n3tfr33]

in /dev/dri è presente il device card0...quindi quello è Ok...le frequenze dello schermo sistemate senza problemi e anche ridotta la profondità del colore...Ma aggiungendo Option "UseBIOS" "false" , startx si carica ma sullo schermo escono tante righe senza senso e si blocca tutto, ho dovuto riavviare a mano...Quindi siamo ancora al punto di partenza...

[phobos3576]

Scusa, volevo dire:

Option "UseBIOS" "true" (che, in ogni caso, è l'opzione predefinita)

Non ti ho chiesto che versione stai usando del kernel e di Xorg; tieni presente che il supporto completo per l'accelerazione grafica delle savage è piuttosto recente e quindi è necessario munirsi di uno degli ultimi kernel (2.6.16 o superiore) e di Xorg 6.9.0 o superiore.