Compilation de XFree86
make World
make install
make install.man
Là pas de problème!
configuration :xf86config + retouche à la main qui donne :
Section "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 Type1 and FreeType font modules
    Load        "type1"
    Load        "freetype"
 
# This loads the GLX module
    Load       "glx"
    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)
#
# 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/Speedo/"
    FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/"
    FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/"
 
# 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><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 "Keyboard"
# 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"    "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"
 
# These are the default XKB settings for XFree86
#    Option "XkbRules"    "xfree86"
#    Option "XkbModel"    "pc101"
#    Option "XkbLayout"   "us"
#    Option "XkbVariant"  ""
#    Option "XkbOptions"  ""
 
#    Option "XkbDisable"
 
    Option "XkbRules" "xfree86"
    Option "XkbModel" "logiinetnav"
    Option "XkbLayout" "fr"
 
EndSection
 
 
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
 
Section "InputDevice"
 
# Identifier and driver
 
    Identifier "Mouse1"
    Driver "mouse"
    Option "Protocol"    "IntelliMouse"
    Option "Device"      "/dev/psaux"
 
# 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 XF86Config 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  "qvision210"
 
# 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 - 82.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 50-90
 
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 xf86config:
 
Section "Device"
    Identifier  "Radeon All-In-Wonder"
    Driver      "ati"
    VideoRam    32768
    Option      "AGPMode" "4"
EndSection
 
Section "DRI"
    Mode 0666
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      "Radeon All-In-Wonder"
    Monitor     "qvision210"
    DefaultDepth 24
 
    Subsection "Display"
        Depth       8
        Modes       "640x480" "800x600" "1024x768" "1280x1024"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "640x480" "800x600" "1024x768" "1280x1024"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "640x480" "800x600" "1024x768" "1280x1024"
        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
 
Compilation des drivers DRI
~/drm/make -f Makefile.linux
insmod radeon.o     j'ai 2 autres fihiers .o : radeon_cp et radeon_drv.o
j'ai ce message  
[drm] AGP 0.99 on ALI M1647 @ 0xf8000000 64MB
[drm] Initialized radeon 1.1.1 20010405 on minor 0
toujours pas de problème
 
startx  
 
XFree86 Version 4.2.0 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 18 January 2002
 If the server is older than 6-12 months, or if your card is
 newer than the above date, look for a newer version before
 reporting problems.  (See http://www.XFree86.Org/)
Build Operating System: Linux 2.4.17 i686 [ELF]
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
         (++) from command line, (!!) notice, (II) informational,
         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Sat Feb  9 18:18:26 2002
(==) Using config file: "/etc/X11/XF86Config"
Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list!
xterm: no available ptys: No such file or directory
xterm: no available ptys: No such file or directory
login: no available ptys: No such file or directory
 
waiting for X server to shut down # This loads the DBE extension module.
 
là problème!!
J'ai mis dans /root/.bash_profile :
PATH=/binusr/binsbinusr/sbinusr/X11R6/bin

= ": /"

Ben, ça a l'air d'être marqué, le problème que tu as, non?
 
xterm: no available ptys: No such file or directory
xterm: no available ptys: No such file or directory
login: no available ptys: No such file or directory
 
Quels sont les droits des /dev/pty* ? Chez moi, ça ressemble à ça :

~$ ll /dev/pty*
crw-rw-rw-    1 root     tty        2, 176 mai 21  1996 /dev/ptya0
crw-rw-rw-    1 root     tty        2, 177 mai 21  1996 /dev/ptya1
crw-rw-rw-    1 root     tty        2, 178 mai 21  1996 /dev/ptya2
crw-rw-rw-    1 root     tty        2, 179 mai 21  1996 /dev/ptya3
crw-rw-rw-    1 root     tty        2, 180 mai 21  1996 /dev/ptya4
crw-rw-rw-    1 root     tty        2, 181 mai 21  1996 /dev/ptya5
crw-rw-rw-    1 root     tty        2, 182 mai 21  1996 /dev/ptya6
crw-rw-rw-    1 root     tty        2, 183 mai 21  1996 /dev/ptya7
crw-rw-rw-    1 root     tty        2, 184 mai 21  1996 /dev/ptya8
crw-rw-rw-    1 root     tty        2, 185 mai 21  1996 /dev/ptya9
...
crw-rw-rw-    1 root     tty        2, 174 mai 21  1996 /dev/ptyze
crw-rw-rw-    1 root     tty        2, 175 mai 21  1996 /dev/ptyzf
~$  

 
Ça en fait 256.

[jfdsdjhfuetppo]--Message édité par Jak--[/jfdsdjhfuetppo]

je suis trop con, je ne les ai pas créés!

Alors c'est ptet lié

 
c'est vrai qu'avec win on pert l'habitude de faire attention aux messages d'erreurs

je pensais que c'était xterm qui faisait une erreur et pas ptys.:gun:
put... il faut vraiment que je me mette à l'anglais!
ça fait 4 mois que je n'utilise plus window$.
ça merde grave mon truc (xfree86), la souris fait n'importequoi et l'écran est tout bizarre.:fou:

T'as l'affichage, c'est déjà ça. Revois ta conf, passe en résolution mini et augmente progressivement. Pour la souris, essaie tous les drivers, un par un.

tout marche!
J'ai repris la config de mon ecran et de souris sur ma RedHat!
c'est la fête

merci jak!!!

des fois la souris merde car il y a un conflit avec gpmdata  
 
alors avant de lancer x : gpm -k ou start -kx

comment lancer le module radeon.o sans "insmod radeon.o" avant de faire startx.
j'ai copié radeon.o dans /lib/modules/2.4.17/kernel/drivers/char/drm
j'ai créé les répertoires /char/drm

dans modules.conf ?

 
je dirait plutot que ca a sa place dans les scripts de démarrage. lequel? je sais pas.

[jfdsdjhfuetppo]--Message édité par daique--[/jfdsdjhfuetppo]