This bug is not fixed, and I get the failure far more often than he reports (most of the time it fails to load the nvidia module, and only occasionally can I get it to boot properly).
Ubuntu 10.04 is the first version of Ubuntu that seems to support my nvidia graphics card (GeForce GT 320M) (at least I couldn't get it to use the nvidia drivers in 9.10).
Attached are Xorg.0.log (a successful nvidia start up), Xorg.1.log (Xorg catching the failure and switching to VESA), and Xorg.2.log (a failed log).
Xorg.0.log is in one system boot while Xorg.1.log and Xorg.2.log are in the previous system boot.
Also attached is the messages file, which the nvidia driver suggests reading for an error message, but I can't find one that doesn't show up under a successful boot up, as well.
I did find in comparing the dmesg and dmesg.0 (the current and previous boot, respectively) that when the failure occurs, it seems the nForce2 driver is failing ("nForce2_smbus 0000:00:03.2: Error probing SMB2.") in dmesg.0 while in dmesg no such line can be found. Do you think it could be some sort of race condition on communicating with the nForce2 chipset between the nForce2 driver and nvidia's proprietary graphics driver? (It is a black box, it could be touching who knows what.)
This bug is not fixed, and I get the failure far more often than he reports (most of the time it fails to load the nvidia module, and only occasionally can I get it to boot properly).
Ubuntu 10.04 is the first version of Ubuntu that seems to support my nvidia graphics card (GeForce GT 320M) (at least I couldn't get it to use the nvidia drivers in 9.10).
Attached are Xorg.0.log (a successful nvidia start up), Xorg.1.log (Xorg catching the failure and switching to VESA), and Xorg.2.log (a failed log).
Xorg.0.log is in one system boot while Xorg.1.log and Xorg.2.log are in the previous system boot.
Also attached is the messages file, which the nvidia driver suggests reading for an error message, but I can't find one that doesn't show up under a successful boot up, as well.
I did find in comparing the dmesg and dmesg.0 (the current and previous boot, respectively) that when the failure occurs, it seems the nForce2 driver is failing ("nForce2_smbus 0000:00:03.2: Error probing SMB2.") in dmesg.0 while in dmesg no such line can be found. Do you think it could be some sort of race condition on communicating with the nForce2 chipset between the nForce2 driver and nvidia's proprietary graphics driver? (It is a black box, it could be touching who knows what.)