|
发表于 2004-3-25 00:25:26
|
显示全部楼层
After reading some threads at nvnews.net forum I realize the x lockup problem is common if you use nvidia related stuff. And there is no "real" solution to this problem. It seems this problem is due to a combination of different factors:
1. Hardware, what motherboard you use, nFORCE or no nFORCE
2. Framebuffer support in kernel, vesa or other.
3. APIC support, enabled or diabled based on what motherboard you got nFORCE or not.
4. Kernel series, 2.6 or 2.4
Kernel developers say that this isn't a kernel bug, and NVIDIA developers haven't said anything. There is no straight answer or workaround to this problem. It's a trade off, disable some options and hope the problem is less frequent.
For example, you can try using nv instead of nvidia driver/module. That may be better, but performance will get worse. Same thing goes for preemptive kernel. Disabling framebuffer in kernel is better though, since framebuffer is just a cosmetic thing at boot (worthless but pretty). But that may not have any effect on the problem. Some have experienced less frequent lock ups after disabling framebuffer, others have not.
I guess we can only try to find a good balance between disabling some options to make the problem less frequent and still have some speed. So our only hope is that the NVIDIA developers shall fix their goddamn drivers soon! |
|