求救,和显卡有关,谢谢

yjomega

我的 机器 是 P4,显卡是 FG4 MX440 , 用 的 RH9,驱动用 的 是 NVIDIA-Linux-x86-1.0-4496-pkg2.run
退出X后用 sh NVIDIA-Linux-x86-1.0-4496-pkg2.run 安装的
然后就重新启动 到 X里面改/etc/X11/XF86Config
把 Load  "dri" 去掉  Driver  "nv"改成Driver  "nvidia"

Section "Device"
        Identifier  "Videocard0"
        Driver      "nvidia"
        VendorName  "Videocard vendor"
        BoardName   "NVIDIA GeForce 4 (generic)"
        VideoRam    65536
EndSection

再重新启动就进不了 X了
这个是 /var/log/XFree86.setup.log 里给的错误信息
(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module!
(EE) NVIDIA(0):  *** Aborting ***
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
请高手们帮我 想想办法,谢谢大家了~

樱家冢

请参见硬件配置版我的置顶帖，虽然是针对当初src.rpm方式的安装，不过关于XF86Config文件的修改道理是一样的。

yjomega

在ＲＥＡＤＭＥ　里找到了，但是我英语太烂，哪个大哥帮忙翻译一下嘛～感谢感谢～
Q: My X server fails to start, and my XFree86 log file contains the error:

   "(EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module!"

A: Nothing will work if the NVIDIA kernel module doesn't function
   properly.  If you see anything in the X log file like "(EE)
   NVIDIA(0): Failed to initialize the NVIDIA kernel module!" then
   there is most likely a problem with the NVIDIA kernel module.
   First, you should verify that if you installed from rpm that
   the rpm was built specifically for the kernel you are using.
   You should also check that the module is loaded ('/sbin/lsmod');
   if it is not loaded try loading it explicitly with 'insmod' or
   'modprobe' (be sure to exit the X server before installing a new
   kernel module).  If you receive errors about unresolved symbols,
   then the kernel module has most likely been built using header files
   for a different kernel revision than what you are running.  You can
   explicitly control what kernel header files are used when building
   the NVIDIA kernel module with the --kernel-include-dir option (see
   `sh NVIDIA-Linux-x86-1.0-4496-pkg1.run --advanced-options`
   for details).

   Please note that the convention for the location of kernel header
   files changed approximately at the time of the 2.4.0 kernel release,
   as did the location of kernel modules.  If the kernel module fails to
   load properly, modprobe/insmod may be trying to load an older kernel
   module (assuming you've upgraded).  cd'ing into the directory with
   the new kernel module and doing 'insmod ./nvidia.o' may help.

   Another cause may be that the /dev/nvidia* device files may be missing.

   Finally, the NVIDIA kernel module may print error messages indicating
   a problem -- to view these messages please check /var/log/messages, or
   wherever syslog is directed to place kernel messages.  These messages
   are prepended with "NVRM".