[RÉSOLU] avec 2.6.18-4-486 OK avec 2.6.18-4-686 NIET ?

Tt est ds le titre et je précise que j’ai un P4 et que le “recommandé” est bien le … -686 :question:
J’ai chargé un “nvidia” à la place du ‘nv’ et j’ai donc laissé le "dri " de côté.
Là je suis sous 2.6.18-4-486 avec exactement la m^ config et tt fonctionne à merveille.
Voilà mon xorg, y-a-t-il qq chose qui cloche ?

[code]Section "Module"
Load "bitmap"
Load "ddc"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "vbe"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option “XkbRules” "xorg"
Option “XkbModel” "pc105"
Option “XkbLayout” "fr"
Option “XkbVariant” "latin9"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option “Device” "/dev/input/mice"
Option “Protocol” "ImPS/2"
Option “Emulate3Buttons” "true"
EndSection

Section "Device"
Identifier "nVidia Corporation NV44A [GeForce 6200]"
Driver "nvidia"
BusID "PCI:1:0:0"
EndSection

Section "Monitor"
Identifier "FUJITSU TE77"
Option "DPMS"
HorizSync 30-68
VertRefresh 50-85
EndSection

Section "Screen"
Identifier "Default Screen"
Device "nVidia Corporation NV44A [GeForce 6200]"
Monitor "FUJITSU TE77"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes “1280x1024” “1280x768” “1200x800” “1152x864” “1152x768” "1024x768"
EndSubSection
SubSection "Display"
Depth 4
Modes “1280x1024” “1280x768” “1200x800” “1152x864” “1152x768” "1024x768"
EndSubSection
SubSection "Display"
Depth 8
Modes “1280x1024” “1280x768” “1200x800” “1152x864” “1152x768” "1024x768"
EndSubSection
SubSection "Display"
Depth 15
Modes “1280x1024” “1280x768” “1200x800” “1152x864” “1152x768” "1024x768"
EndSubSection
SubSection "Display"
Depth 16
Modes “1280x1024” “1280x768” “1200x800” “1152x864” “1152x768” "1024x768"
EndSubSection
SubSection "Display"
Depth 24
Modes “1280x1024” “1280x768” “1200x800” “1152x864” “1152x768” "1024x768"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection

Section “DRI”

Mode 0666

EndSection[/code]

Et voilà la partie du log concernée

Mar 9 00:37:41 localhost kdm: :0[2779]: IO Error in XOpenDisplay Mar 9 00:37:41 localhost kdm[2735]: X server for display :0 terminated unexpectedly Mar 9 00:37:41 localhost kdm[2735]: Display :0 cannot be opened Mar 9 00:37:41 localhost kdm[2735]: Unable to fire up local display :0; disabling. Mar 9 00:38:10 localhost shutdown[2816]: shutting down for system halt Mar 9 00:38:10 localhost init: Switching to runlevel: 0 Mar 9 00:38:13 localhost avahi-daemon[2495]: Got SIGTERM, quitting. Mar 9 00:38:13 localhost avahi-daemon[2495]: Leaving mDNS multicast group on interface eth1.IPv4 with address 82.253.241.155. Mar 9 00:38:13 localhost avahi-daemon[2495]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.3.1. Mar 9 00:38:13 localhost ddclient[2505]: WARNING: caught SIGTERM; exiting Mar 9 00:38:16 localhost rpc.statd[2684]: Caught signal 15, un-registering and exiting. Mar 9 00:38:16 localhost kernel: Kernel logging (proc) stopped. Mar 9 00:38:16 localhost kernel: Kernel log daemon terminating. Mar 9 00:38:17 localhost exiting on signal 15

RÉSOLU :
j’avais tt simplement oublié d’installer le nvidia-kernel qui_va_bien :blush:
C’est en lisant une précision du petit Chat Noir, que j’ai vérifié si j’avais tt bien installé. Ô rage, ô désespoir … putain de neurone qui fout le camp et dire que c’était le dernier. :unamused:

Parce que tu dois avoir un module nvidia pour le noyau 486 et non le 686 probablement. Sans doute qu’en recompilant le nodule pour le 686 ça ira mieux.

J’ai édité pour expliqué où était mon erreur.
RÉSOLU
Merci Fran.