The 64-bit version of F9 freezes when xserver starts using startx. Mouse and keyboard locks. I have to power down to recover. I have used nv, vesa, nouveau, and nvidia drivers with the same result. The nvidia akmod is from livna. The system is up-to-date via yum update. xorg.conf and Xorg.0.log files are in the attached zip. I have an HP Pavillion desktop d4100e with dual AMD 64-bit processors, 2 GB ram, and an Nvidia Geforce 6800 video card. This problem has existed since the initial F9 release.
The 32-bit version works fine. 32-bit and 64-bit Live CD versions also work.
In the 64-bit version, xinit and twm work.
After xserver locks in 64-bit, I have seen the machine lock when trying the same 32-bit and 64-bit Live Cds. It almost seems that the 64-bit version is doing something to the card (bios?) that affects it later. It does recover if I leave it powered down for a few minutes. There are some v_bios checksum errors in some of the logs.
I had run this by Hlingler in another thread starting with post #12: http://forums.fedoraforum.org/showthread.php?t=188241
Is there anything that I need to check? Is there a setting that needs to be fixed?
Is this problem a bug that I should report? If so, is it an xorg, nvidia, or fedora bug?
Thanks in advance,
Retract above cause.
Real problem identified.
USB port on monitor causes Xserver to freeze in F9 x86_64.
For a long time, I had a Logitech webcam plugged into a USB port on the HP f2105 monitor. For other reasons, I had unplugged the web cam from the monitor around the time that the latest kernel and nvidia driver were released. Xserver did start working and I could log in normally. However, when I plugged the web cam back into the monitor USB port, Xserver locked up again just as it had since the release of F9. I plugged the web cam into a port on the back of the desktop and Xserver worked fine. BTW, I have noticed that F9 x86_64 shows errors failing to enumerate some USB ports. I have USB ports on the front of the desktop and as mentioned 2 USB ports on the monitor itself.
Sounds like a bug report. Where should it be reported?