Bonjour a tous J'ai profité de la sortie du nouveau driver Nvidia ( hier je crois), pour l'installer Donc l'install se passe sans aucun probleme Je passe ensuite a la modif de mon fichier xorg.conf ou je met ceci: Section "Module" . .. #Load "dri" Load "glx" . .. EndSection Section "Device" . .. #Driver "nv" Driver "nvidia" Option "DPMS" Option "RenderAccel" "1" Option "UseEdidFreqs" "1" Option "EnablePageFlip" "true" Option "NoBandWidthTest" "1" Option "DigitalVibrance" "3" Option "NvAGP" "3" Screen 0 . .. EndSection Je rajoute ausi nvidia a mon fichier /etc/rc.conf Je teste : glxinfo | head -n 3 J'obtiens bien cette reponse: name of display: :0.0 display: :0 screen: 0 direct rendering: Yes Je reboote le pc.Tout va bien , j'obtiens le Logo Nvidia au demarrage Le seul hic c'est qu'au bout de quelques minutes mon ecran se gele Je m'explique: La souris reste active car je peux la bouger sur mon ecran mais meme si je peux la bouger , je ne peux plus rien cliquer.Tout est inactif Le clavier lui meme ne repond plus puiisque meme en faisant un Ctrl-Alt-Backspace ( pour quitter X) , rien ne se passe Je precise que le driver n'est surement pas en cause car avec la version precedente ca me faisait exactement pareil et j'avais donc pensé a un probleme le concernant.Mais maintenant qu'avec un nouveau driver le probleme se repete , je pense que c'est a ecarter comme Diagnostic Ma question est donc la suivante : Quelqu'un "voit" il de ou le probleme peut il venir ??? Je suis bien decu de ne pouvoir utiliser Nvidia avec ma configuration Je vous fais un copier/coller de mon fichier xorg.conf au cas ou ************************************************************* # File generated by xorgconfig. # 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/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/TTF/" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/CID/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" FontPath "/usr/X11R6/lib/X11/fonts/local/" # FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" # FontPath "/usr/X11R6/lib/X11/fonts/TrueType/" # FontPath "/usr/X11R6/lib/X11/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" "ltcd" Option "XkbLayout" "fr" EndSection # ********************************************************************** # Core Pointer's InputDevice section # ********************************************************************** Section "InputDevice" # Identifier and driver Identifier "Mouse1" Driver "mouse" Option "Protocol" "Auto" # Option "Device" "/dev/input/mouse1" Option "Device" "/dev/input/mice # 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" Option "Buttons" "5" Option "ZAxisMapping" " 4 5" 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 "Acer" # 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-81 # 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 60-85 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 "Nvidia" Driver "nv" #VideoRam 65536 # 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 "Nvidia" Monitor "Acer" 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 ************************************************************

Kan tu met le driver "nv" ou "vesa", tout fonctionne ??

Bonsoir.. que donne : cat /proc/driver/nvidia/agp/status ou mieux que les mots: - http://forum.pcastuces.com/sujet.asp?SUJET_ID=161109 (Dark_Raziel a tt dit)

re -- s'cuse Cinna, je viens de relire le chef-d'oeuvre de Dark-Raziel.. et je m'apercois que tu l'as consulte deja..

Modifié par selim,b. le 02/04/2005 19:14

ici #Driver "nv" Driver "nv" Option "DPMS" Option "RenderAccel" "1" .... et non : Driver "Nvidia"

Oui bien sur Je reprecise que lorsque je remet en standard et que je remplace nividia par nv , tout remarche normalement sans blocage Celui ci arrive des que je mets en fonction le driver nvidia

Ben Cinna!!.. c la solution.. Complete juste les options d'optimisation (s'il y a lieu de le faire) \bye. selim,b.

Salut Sel Tu veux donc dire qu'il faut que je me passe du driver nvidia ???

re.. je reste perplexe en lisant: ftp://download.nvidia.com/XFree86/Linux-x86/1.0-7174/README.txt .. c que j'utilise ati ... .. mieux vaut attendre confirmation/infirmation d'un habitue nvidia.. Allô Dark_Raziel!!.. sorry.. si pas de reponse precise.. J'attendrai comme toi

ca n'a surement aucun rapport , du moins je pense, mais je viens de me rendre compte que dans mon Bios , l'option Plug & Play OS etait sur Yes Je l'ai desactivé (NO) car de ttes facons je pense qu'avec linux ca n'est pas necessaire Me trompe-je ???

Euh, soit plus precis, t'es perplexe sur quoi ??

Bonsoir Dark_Raziel mettre nv ou nvidia ..lors d'une maj du driver..

Salut, Je viens de mettre à jour avec la version précédente, la version 7167, sortie quelques jours plus tôt. Je l'ai installée avec un apt-get install nvidia-glx donc je n'ai pas utilisé la même méthode. Je ne vois pour l'instant pas de PB particuliers. Tu pourrais essayer de garder le minimum d'options dans xorg.conf Je vois que tu as déjà dévalidé pas mal d'options... Sous Mandrake, j'avais un fichier avec très peu d'options mais depuis que je suis sur Mepis, le fichier configuré par défaut par la distribution a beaucoup trop d'options à mon goût, probablement pour être compatible avec un maximum de configurations. Tu peux aussi lancer en console un tail -f /var/log/messages pour regarder si tu as quelques chose au moment du plantage. Il y aussi peut être des infos dans var/log/Xorg.O.log @+

Rebonsoir J'ai refait l'essai de mettre le driver Nvidia et naturellement ca n'a pas "tenu" tres longtemps J'ai regardé les logs : Dans le log Xorg.0.log , je note les lignes commencant par WW ( qui sont des Warnings: (WW) NVIDIA(0): Failure reading EDID parameters for display device CRT-0 (WW) NVIDIA(0): Not using mode "360x200": (WW) NVIDIA(0): horizontal sync start (378) not a multiple of 8 (WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x0000e730, 0x0000e76c, 1) (WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x0000e730, 0x0000e76c, 1) Le messages.log ne contient rien de particulier au moment du blocage (j'avais noté l'heure exacte) Il semblerait donc que le mystere soit dans le Xorg.0.log Quelqu'un comprendrait il la signification des ces "warnings" ???

Ah ca!! non non, rien a voir, je lui demandais juste si kan il mettait "nv" ou "vesa" le X démarrait correctement C tout [langue] Y a pas a changer ca kan on maj le driver [smile] N.B : 7174 ok chez moi aussi...installé sur 2 machines, aucuns problemes [smile]

Bjr a tous J'ai eu le même prob avec KDE3.3 (Mandrake 10.1) ----------- Editer le fichier (/etc/kde/kdm/kdmrc) Dans la section [General], Ajouter ServerVTs=-7 ---------- But: Reassigner le clavier au tty qui lance kdm. Info : solution recue sur forum MandrakeClub (nov 2004) A+

Bonjour et merci pour la reponse Malheureusement ce n'est pâs la solution , pour 2 raisons: 1:) Je n'utilise pas KDE mais plutot fluxbox 2:) J'ai tout de meme trouvé ce fichier kdmrc situé a un autre nedroit ( /opt/kde/share/config/kdm/kdmrc ) et dans la section general se trouve deja: ServerVTs=-7 Merci tout de meme

[quote]Message original par Cinna Section "Module" . .. #Load "dri" Load "glx" . .. EndSection ----------- # File generated by xorgconfig. # 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 GLX module # Load "glx" # This loads the DRI module Load "dri" EndSection !!!!!!!!!!!!!!!!!!!!!!!!!!! /[quote] Je peux peut-être me tromper mais le fichier conf que tu poste fait toujours appel au 'DRI' et non a "GLX" Dans la section module de mon install, j'ai en plus la lib spécifique en lieu et place du load "glx": Section "Module" .... Load "/usr/X11R6/lib/modules/extensions/libglx.so" ..... EndSection Que dit l'utilitaire nvidia-settings ?

Re oui bien sur , j'avais oublié de preciser que le fichier que j'ai posté est le fichier remodifié en normal et non avec le driver nvidia , puisque ca bloque au bout de quelques minutes Mais nturellement j'avais bien mis les bons parametres pour faire l'essai avec nvidia Merci de te pencher sur ce probleme