Aller au contenu

Acceleration 3d avec rage128, xorg 6.8 (gentoo)

jeredox

Par jeredox
dans GNU/Linux, *BSD et dérivés d'UNIX

Messages recommandés

jeredox Nouveau

jeredox

Posté(e)
Posté(e)

Bonjour, j'ai suivi le topic officiel de tuxxx pour installer l'acceleration 3d (DRI) pour ma rage 128 (nom complet: ati all in wonder 128).

Malheureusement, j'en arrive à l'étape du flgrxconfig qui me présente une liste de cartes supportées: MAIS il n'y a pas de rage 128. Quelle carte choisir?

Deuxièmement, j'utilise Xorg 6.8 (je ne sais pas si cette version supporte le dri pour les rages 128) et il est marqué dans le tuto de tuxxx que si on utilise Xorg, il faut déplacer un fichier:

dommage pour ceux qui utilisent xorg, ils devront bouger le fichier généré)

Et comme dit Sandeman "pis voilà :)"

(c'est à dire "charger le module et relancer X, éventuellement mettre le module en autoload... voir dans la partie nvidia)

Je saisis pas exactement ce qu'il faut faire à cette étape.

Je ne peux donc pas terminer l'installation. merce d'avance pour votre aide.

Jérémy.

Lien vers le commentaire
Partager sur d’autres sites
Duke98 Expérimenté

Duke98

Posté(e)
Posté(e)

dans mon souvenir il suffit de mettre r128 pour la carte dans xorg.conf, c'est tout :chinois:

de toute facon , elle doit avoir été configuré lors de l'installation.

par contre pour bénéficier du aiw, c'est un peu plus du sport, faut regarder du coté de gatos (jamais réussi a faire tourner, mais j'ai pas trop insisté non plus :incline: )

pour le tuner je sais pas si xdtv le supporte, je crois pas

Lien vers le commentaire
Partager sur d’autres sites
lorinc Mentor

lorinc

Posté(e)
Posté(e)
C'est plutôt "pas besoin de fglrx car le driver inclu dans xorg gère toutes les radeon <= 9200"

(et au moins le driver libre est rapide, pratique, ne plante pas, etc...

oui, c'est exactement ça, en fait :byebye:

je me demande même si le driver libre n'est pas plus rapide que fglrx sur les cartes supportées par les deux :D

Lien vers le commentaire
Partager sur d’autres sites
jeredox Nouveau

jeredox

Posté(e)
  • Auteur
Posté(e)

Voilà, j'ai fait mon xorg.conf et comment je mets en place l'acceleration 3d .? Gatos?

Je l'avais fait sous deb avec une gatos, mais je ne vois que des pacakges debian dans les tutos. Comment faire sous ma gentoo?

Merci d'utiliser votre temps pour me répondre aussi rapidement, c'est vraiment sympa!

Au fait, et si je mets le supprt drm uniquement en module dans mon kernel, et ce que je peux me dispenser des gatos?

Lien vers le commentaire
Partager sur d’autres sites
jeredox Nouveau

jeredox

Posté(e)
  • Auteur
Posté(e)

Voilà le xorg.conf que j'utilise et qui me permet de démarrer X (je vois pas pourquoi le dri ne fonctionne pas,il m'a l'air correct): 

# XFree86 4 configuration created by pyxf86config

Section "ServerLayout"
Identifier     "Default Layout"
Screen      0  "Screen0" 0 0
InputDevice    "Mouse0" "CorePointer"
InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
# RgbPath is 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 (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.

RgbPath      "/usr/X11R6/lib/X11/rgb"
FontPath     "unix/:-1"
EndSection

Section "Module"
Load  "dbe"
Load  "extmod"
Load  "fbdevhw"
Load  "glx"
Load  "record"
Load  "freetype"
Load  "type1"
Load  "dri"
EndSection

Section "InputDevice"
# Specify 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 non-U.S.
# keyboard, you will probably want to use:
#	Option	"XkbModel"	"pc102"
# 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"
# Or if you just want both to be control, use:
#	Option	"XkbOptions"	"ctrl:nocaps"
#
Identifier  "Keyboard0"
Driver      "kbd"
Option     "XkbModel" "pc105"
Option     "XkbLayout" "fr"
EndSection

Section "InputDevice"
Identifier  "Mouse0"
Driver      "mouse"
Option     "Protocol" "IMPS/2"
Option     "Device" "/dev/input/mice"
Option     "ZAxisMapping" "4 5"
Option     "Emulate3Buttons" "yes"
EndSection

Section "Monitor"
Identifier   "Monitor0"
VendorName   "Monitor Vendor"
ModelName    "19.900"
DisplaySize  360	270
HorizSync    30.0 - 110.0
VertRefresh  50.0 - 160.0
Option     "dpms"
EndSection

Section "Device"
Identifier  "Videocard0"
Driver      "r128"
VendorName  "Videocard vendor"
BoardName   "ATI Rage 128"
EndSection

Section "Screen"
Identifier "Screen0"
Device     "Videocard0"
Monitor    "Monitor0"
DefaultDepth     24
SubSection "Display"
 Viewport   0 0
 Depth     24
 Modes    "1024x768" "800x600" "640x480"
EndSubSection
EndSection

Section "DRI"
Group        0
Mode         0666
EndSection

Et voilà, le xorg.conf que xorgconfig me génère. Celui ci refuse de démarrer X avec une erreur:


# 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.
# **********************************************************************
#
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        "speedo"
   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/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)
# 
# 

   FontPath   "/usr/share/fonts/misc/"
   FontPath   "/usr/share/fonts/TTF/"
   FontPath   "/usr/share/fonts/Type1/"
#    FontPath   "/usr/share/fonts/CID/"
   FontPath   "/usr/share/fonts/75dpi/"
   FontPath   "/usr/share/fonts/100dpi/"
   FontPath   "/usr/share/fonts/local/"
#    FontPath   "/usr/share/fonts/Speedo/"
#    FontPath   "/usr/share/fonts/TrueType/"
#    FontPath   "/usr/share/fonts/freefont/"

# The module search path.  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 "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"

# 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 "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"	"pc101"
   Option "XkbLayout"	"fr"

EndSection


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

Section "InputDevice"

# Identifier and driver

   Identifier	"Mouse1"
   Driver	"mouse"
   Option "Protocol"    "Auto"
   Option "Device"      "/dev/mouse"

# Mouse-speed setting for PS/2 mouse.

#    Option "Resolution"	"256"

# 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


# **********************************************************************
# 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  "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 - 79.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 160

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 Rage 128 based (generic)       [r128]"
   Driver      "r128"
   #VideoRam    32768
   # 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 Rage 128 based (generic)       [r128]"
   Monitor     "My Monitor"
   DefaultDepth 24

   Subsection "Display"
       Depth       8
       Modes       "1280x1024" "1024x768" "800x600" "640x480"
       ViewPort    0 0
   EndSubsection
   Subsection "Display"
       Depth       16
       Modes       "1280x1024" "1024x768" "800x600" "640x480"
       ViewPort    0 0
   EndSubsection
   Subsection "Display"
       Depth       24
       Modes       "1280x1024" "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

et voici l'erreur qd je veux démarrer X 

(EE) R128(o) : No valid modes found.
Symbol XF86 HH cursor from module /usr/lib/modules/drivers/r128-dr-vo

Merci pour votre aide.

Lien vers le commentaire
Partager sur d’autres sites
jeredox Nouveau

jeredox

Posté(e)
  • Auteur
Posté(e)

Tu penses vraiement que c'est ca? ca m'a l'air louche mais tu as raison je n'y perds rien! :yes:

Mais, pour les habitués, ne manque t-il pas une section indispensable au démarrage de X dans le nouveau Xorg.conf: par exemple, la section "ServerLayout" est un peu pauvre dans le fichier généré. (elle n'est qu'à la fin avant le dri.

Merci pour votre aide encore une fois.

Lien vers le commentaire
Partager sur d’autres sites
jeredox Nouveau

jeredox

Posté(e)
  • Auteur
Posté(e)

Donc, dans le log du xorg.conf qui démarre, voici ce que j'obtiens pour les erreurs (lignes commencant par WW):

WW) warning, (EE) error, (NI) not implemented, (??) unknown.

(WW) Open APM failed (/dev/apm_bios) (No such file or directory)

(WW) R128(0): Can't determine panel dimensions, and none specified.

(WW) R128(0): [agp] AGP not available (<<-- A mon avis le probleme vient de là!)

(WW) R128(0): [agp] AGP failed to initialize -- falling back to PCI mode.

(WW) R128(0): [agp] Make sure you have the agpgart kernel module loaded.

Voilà, en espérant que ca vous permette de me donner des indications car j'y comprends pas grand chose mis à part le fait que mon support agp n'est pas utilisé dans mon noyau!

Merci

Lien vers le commentaire
Partager sur d’autres sites
lorinc Mentor

lorinc

Posté(e)
Posté(e)

oui, m'est aussi d'avis que si tu fais un lsmod | grep agpgart , il ne va rien te renvoyer...

donc un coup de modprobe agpgart est déjà nécéssaire.

ensuite, il faudrait savoir quel est ton chip agp (intel, via, nvidia ou sis pour les plus courrant) et un coup de modprobe via-agp (ou un autre, hein, on se comprend :francais: ) devrait faire l'affaire :sucre:

Lien vers le commentaire
Partager sur d’autres sites
jeredox Nouveau

jeredox

Posté(e)
  • Auteur
Posté(e)

voilà les lignes demandées de var/log/xorg.conf:

drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: open result is -1, (Unknown error 999)
drmOpenDevice: Open failed
drmOpenByBusid: Searching for BusID pci:0000:01:00.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenByBusid: drmOpenMinor returns 6
drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0
(II) R128(0): [drm] loaded kernel module for "r128" driver
(II) R128(0): [drm] DRM interface version 1.2
(II) R128(0): [drm] created "r128" driver at busid "pci:0000:01:00.0"
(II) R128(0): [drm] added 8192 byte SAREA at 0xd9007000
(II) R128(0): [drm] mapped SAREA 0xd9007000 to 0xb5cc8000
(II) R128(0): [drm] framebuffer handle = 0xf8000000
(II) R128(0): [drm] added 1 reserved context for kernel
(WW) R128(0): [agp] AGP not available
(WW) R128(0): [agp] AGP failed to initialize -- falling back to PCI mode.
(WW) R128(0): [agp] Make sure you have the agpgart kernel module loaded.

et qd je lance la commande : lsmod | agp , il me dit que la commande agp n'existe pas . (en effet ca existe cette commande?)

Si grace à toi, j'arrive à obtenir mon support dri, je ne saurai comment te remercier. :francais:

NB: Au fait, mon AGP est de type pention 2 ou 3 (donc intel je suppose)

Lien vers le commentaire
Partager sur d’autres sites
jeredox Nouveau

jeredox

Posté(e)
  • Auteur
Posté(e) 

jeredox@localhost ~ $ lsmod | grep drm
drm                    60052  2 r128
agpgart                29640  1 drm

.

Y-a-t il un truc radical que je pourrais faire pour que ca marche puisque mon module drm est également présent.

Est-il possible que l'installation des drivers ati (emerge ati-drivers) est un lien avec mes problèmes, j'y comprends tellement plus rien que je propose des solutions...?

Lien vers le commentaire
Partager sur d’autres sites

Archivé

Ce sujet est désormais archivé et ne peut plus recevoir de nouvelles réponses.

Aller sur la liste des sujets
×
×
  • Créer...