|02-28-05, 07:31 AM||#1|
Join Date: Aug 2002
If you have a problem, PLEASE read this first
If you have a problem, and would like assistance, please follow these steps:
1) If you have a stability problem, please read this thread, first: http://www.nvnews.net/vbulletin/showthread.php?t=58498.
2) If you have a problem with VDPAU and/or MPlayer/VDPAU, please read this thread, first: http://www.nvnews.net/vbulletin/showthread.php?t=123819.
3) Please search the NVIDIA Linux/FreeBSD/Solaris Forums for existing threads discussing the problem you are experiencing, it may have been resolved (or a workaround may have been found). If you cannot find such a thread, please start a new thread - it is really hard to keep track of bugs/problems if they are discussed in generic (such as '1.0-8756 for Linux x86-64 released') and/or very long threads.
4) Please always include a detailed description of the problem (both when starting a new thread and when posting to existing threads), as distinct problems can have nearly identical symptoms (e.g. black screens, hung X servers, ...). Reliable reproduction steps are especially useful. If you post a reply reading "I have the same problem" in response to another user's bug report without the information requested in this post, you may make it more difficult for NVIDIA to track and diagnose the problem.
4a) Please always include a copy of an nvidia-bug-report.log file, which can be generated with the `nvidia-bug-report.sh` script shipped with the NVIDIA Linux/FreeBSD graphics drivers and installed in your PATH; the log file will be placed in the current working directory. Newer versions of the script will automatically compress the log file renaming it to nvidia-bug-report.log.gz.
To make sure this log file includes as much relevant information as possible, please start the X server with `startx -- -logverbose 6` and run `nvidia-bug-report.sh` after the problem has occurred. If X can not be started or the machine appears to have crashed, please check if you can log into it remotely (e.g. via ssh or telnet) and run `nvidia-bug-report.sh` in the remote shell, if possible.
If the machine can not be logged into remotely, please run the bug report script with X running (this will ensure that data points only available when the device is initialized, such as the VBIOS revision, are captured in the log file). All requests for assistance from NVIDIA must include the bug report, per the instructions above.
If `nvidia-bug-report.sh` appears to hang, it may still have collected enough useful information about your problem. In this case, please provide the partial log file generated, if any.
4b) In case of NVIDIA Linux graphics driver installation problems (when using one of the official .run installers), please attach the NVIDIA installer log file, /var/log/nvidia-installer.log.
4c) If you have collected additional information, but are not sure if it is relevant /appropriate, please attach it, anyway.
Please note: if nvidia-bug-report.log, nvidia-installer.log and/or any other log/support files are too large to be attached to nV News forum posts as-is, you can create and attach .bz2 or .gz archives, instead.
4d) When creating a new thread, please make the thread subject as descriptive as possible. For example,
This information will help us help you.
|Thread||Thread Starter||Forum||Replies||Last Post|
|APM (nonsuspend) hard-lockups - I READ THE FAQ||idangazit||NVIDIA Linux||9||12-27-02 08:43 AM|
|Post working out problem with 40.xx trying to work problem out, ONLY system specs||b5fan||NVIDIA Windows Graphics Drivers||11||10-19-02 10:17 AM|
|nv30 problem rumor||bob747b||Rumor Mill||37||10-10-02 04:14 PM|
|Problem when compiling with SDL on Nvidia/Nforce...||superconti||NVIDIA Linux||3||09-13-02 01:25 AM|
|Nvidia Go on laptop, black border within XFree86 problem||raxip||NVIDIA Linux||3||07-31-02 11:58 AM|