This is a bug report I sent off to NVIDIA concerning my MX440 card. I'm posting it here in case someone has this problem and needs to find a work around. I'm not attaching the log files. But when I sent the log files to NVIDIA, I zip'ed them (using zip, not tar gzip) because I didn't know what they wanted and that would make it more universal. The response I got back seemed to indicate they couldn't open a simple zip file.
Gus SUMMARY: When a system is set up for TwinView and clones the CRT to TV-OUT, X will hang on startup. SYSTEM: NVIDIA GeForce4 MX440 64MB AGP, Jetway 663AS Ultra Motherboard w/Via KT133A chipset, Athlon 1.4GHz processor, 1GB RAM, 200GB Seagate harddrive. SOFTWARE: NVIDIA drivers 7676 release, KnoppMyth R5V16 (based on Knoppix/Debian 3.1), XFree86 4.3.0.1, kernel 2.6.11 with patches DESCRIPTION: The system is set up using TwinView so that the TV-OUT connection is a clone of the CRT. With the SVIDEO/Composite connector connected to the card, the system boots to a command line interface. The output is seen on both the CRT and the composite TV-OUT. When X is started, X will hang. Review of the logs indicates that X hangs when the TV portion of the card capabilities is being probed. If the system is started without the SVIDEO/Composite connector connected, the system can be brought up to a command line interface. If the SVIDEO/Composite connector is then attached, X will start fully and will display on both the CRT and the TV-OUT. WORKAROUND: Start the system without the SVIDEO/Composite connector attached until the system is at a command line interface. Attach the SVIDEO/Composite connector, then start X. I have attached the output of the nvidia-bug-report.sh program, with one modification. When X was attempting to start up, running the script would hang on the "cat /proc/drivers/nvidia/cards/*". I remarked out that line so that all the system info could be gathered while X was in a hung state. I also did an strace of the X process and have attached that as well; the file is named Xfail-nvidia. The important point to know in that file is the last line showing a hang in an IOCTL. The strace was accomplished by using the following command: sudo -b strace -o Xfail-nvidia X -verbose 5 -logverbose 5 I also created a process list using "ps -ef". The result is a file called ps-ef.txt. Other than the X failure, the system continued to function. Logs and reports were generated by ssh'ing into the box. Running top showed no CPU activity attributable to X when it was in the hung state. Gus Wirth Kernel-Panic Linux Users Group San Diego, California, USA -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
