Installazione Xorg driver

[dexter]

Ho aggiunto Load "dri" e Load "glcore" sotto a Load "glx" ho aggiunto
<BR>l´ultimo pezzo che hai postato, ho controllato se agpgart era abilitato
<BR>e infatti era abilitato. Ma come si fanno a dare i permessi root.video
<BR>0666??? e come mi aggiungo al gruppo video????<br />
<BR><br />
<BR><br />
<BR>grazie <br />
<BR><br />
<BR><br />
<BR>dexter<br />
<BR><br>

[clodo]

Ehmmm....., non è il modulo ad avere permessi, ma il device agpgart. se
<BR>usi kernel 2.6.x, è udev a dare i permessi ai vari dispositivi: quindi
<BR>devi editare il file /etc/udev/permissions.d/udev.permissions( mi
<BR>sembra giusto........), vedrai che la sintassi è banale, troverai o
<BR>devi aggiungere la riga:<br />
<BR>misc/agpgart root.video 0666<br />
<BR>per associarti al gruppo video, edita il file /etc/group, anche questo di facile comprensione.<br />
<BR>Se usi kernel 2.4, allora :<br />
<BR>chown root.video /dev/agpgart<br />
<BR>Ciao.<br /><br>

[pennega]

prova a controllare se hai le zlib installate... vedi se trovi il pkg sotto /var/log/package/<br />
<BR><br />
<BR>poi x i driver della scheda dai uno sguardo qui <br />
<BR><br />
<BR>http://dri.freedesktop.org/snapshots/<br />
<BR><br />
<BR>io ci prendo regolarmente i driver x la mia savage e non ho avuto mai problemi...<br />
<BR><br />
<BR>x gli screensaver se cerchi nel forum ho lasciato un post dove indicavo + o - lo stesso problema dacci uno sguardo...<br /><br>

[dexter]

purtroppo mi da lo stesso errore!!!!!!!!<br />
<BR>Ho inserito quella riga che mancava in
<BR>/etc/udev/permissions.d/udev.permissions, quando sono andato in
<BR>/etc/group dove c´era video:18: ho aggiunto il mio user facendolo
<BR>diventare: video:18:dexter<br />
<BR><br />
<BR>Le zlib ci sono in /var/log/package<br />
<BR>Perchè..... perchè............ma soprattutto perchèèèèèèèèèèèèèèèèèèèèèèèèèèèèè<br />
<BR><br />
<BR>dexter<br />
<BR><br>

[clodo]

Usare driver pacchettizzati rpm o altro e trasformarli in altro tipo di
<BR>pacchetto è SEMPRE cosa da evitare se possibile, specie driver video
<BR>(vedi ati che pensa solo che linux=rpm=red hat e che per ogni sua gpu
<BR>ne confeziona uno diverso, così se hai ati8700 trovi sul suo sito
<BR>quelli per la 8600 e 8800,in più rpm, per cui?....cosa ...zzo fai?Perdi
<BR>tempo, bestemmi e alla fine non funzia niente, poi  ati= "sedere
<BR>& camicia" con quelli di XP, si fanno le API l´un con l´altro come
<BR>le librerie.........va bè lasciamo perdere sennò......tra l´altro i
<BR>negozi tengono 3456 schede ati e 2 nvidia......BENE!!!)<br />
<BR>DOMANDONE: perchè non usi i driver sis presenti in xorg?c´è tutto l´occorrente<br />
<BR>Posta anche il tuo xorg.conf, non si sa mai.......<br />
<BR>Ultimo: errori con modprobe agpgart? <br />
<BR><br>

[dexter]

# 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"
Load "dri"
Load "glcore"

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"

# 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" "PS/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 - 50.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 40-90

EndSection


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

# Any number of graphics device sections may be present

Section "Device"
Identifier "VESA Framebuffer"
Driver "sis"
#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

Section "DRI"

Mode 0666

EndSection

-----------------------------------------------------------------------------------


questo è il mio xorg.conf, il comando modprobe agpgart non mi da problemi......


grazie



dexter

[DarkNeo]

Adesso come faccio a sistemare l´accellerazione 3D? Come si configura?

Sinceramente l'accelerazione 3D credo che non si configuri la si sfrutta installando i driver della scheda video... la puoi vedere dando glxgears dalla consol.

PS: ne approfitto pure io per fare una domanda... io ho un monitor LCD che essendo da 19" supporta alte risoluzioni... ma di default dopo aver ricompilato il kernel la risoluzione è a 800x600 senza grafica.... come faccio a settarla? ho provato a modificare /etc/X11/xorg.conf ma è stato un tentativo invano.... please help me ByE

[clodo]

Dexter:
decommenta la riga "ModulePath", è un tentativo..........

DarkNeo:
bisogna sapere un sacco di parametri, scheda video, file xorg.conf, etc: non è facile rispondere!
ciao!

[dexter]

Se scrivo "glxgears" mi da lo stesso errore di sempre:
"[sis_alloc.c:154]: Failure to allocate Z buffer."

decommentando la riga : "ModulePath" non succede niente... sempre lo stesso errore.

Avevo pensato di installare i driver nuovi della sis su quel sito che mi avete consigliato. Che ne pensate?



dexter

[dexter]

ma i driver su quel sito che mi avete dato sono per Xorg???
Avevo già provato ad avviare l'installazionre e mi diceva che sarebbero stati installati i driver per Xfree86 e anche nella licenza parlava di Xfree86.... come devo fare se sono per Xfree86?????

dexter

[DarkNeo]

DarkNeo:
bisogna sapere un sacco di parametri, scheda video, file xorg.conf, etc: non è facile rispondere!
ciao!

Se interessa posso copiarti il mio xorg.conf la scheda viedo è "nvidia geforce fx5700 vivo"

[clodo]

Ho anch'io una fx5700, uso driver nvidia ufficiale (2 minuti di installazione), kernel 2.6.10 non ricompilato (non ne ho necessità), monitor lcd da 17', slackware 10.1. comunque posta xorg.conf, ma prova prima ad installare il driver nvidia e DOPO lancia da root xorgsetup. In genere produce una buona configurazione, che con poche e facili modifiche funzia....

[dexter]

si ma la mia scheda???????.......................

[DarkNeo]

Ho scaricato i driver qui:
http://www.nvidia.com/object/linux_disp ... -7664.html
non so se sono giusti dato che quando li lancio mi da:

bash-3.00# sh NVIDIA-Linux-x86_64-1.0-7664-pkg2.run

ERROR: this .run file is intended for the
Linux-x86_64 platform, but you appear to be
running on Linux-x86. Aborting installation.

anche se il mio processore è un amd opteron a 64bit... che posso inventarmi?

Grazie

[clodo]

DarkNeo :
scarica e usa la versione a 32 bit

Dexter:
posta /var/log/Xorg.0.log