Nvidia GT240 screen corruption after boot

In my case, the fan of the video card is simply not running, so it turns off after some time to prevent dying because of overheating.
This could also be your problem.

Status changed to 'Confirmed' because the bug affects multiple users.

I'm affected by this, too. Basically, any acceleration seems to be problematic on NVA3 chips. Passing nouveau.noaccel=1 to kernel fixes this: booting works normally, albeit X is unaccelerated.

This patch disables acceleration completely for certain known chipsets. This is not ideal, but certainly better than an unusuable, crashing system.

This patch disables acceleration completely for certain known chipsets. This is not ideal, but certainly better than an unusuable, crashing system.

The attachment "drm-nouveau-nva3-noaccel.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

Can you provide some information on the status of the patch with regards to getting it merged upstream? Has it been sent upstream, what sort of feedback has it received, is it getting applied to a subsystem maintainer's tree, etc?

People affected by this bug are probably wondering why the kernel team doesn't just apply the patch and fix it. The reason is that the kernel team is reluctant (not opposed) to apply any patch to a stable kernel that is not from upstream. Applying patches that don't come from upstream add greatly to the support of the kernel as other upstream patches may touch the same area as the non-upstream patch and may prevent them from applying cleanly.

@Nukam, @Ben,

This bug was filed over a year ago and the attached patched is from 1.5 years ago. Can you please verify that this is still an issue for you and let us know? Thanks.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

This is definitely still an issue. There are multiple bug reports about this upstream, but nobody cared about them.

Greg - Support for Ubuntu 10.10 "Maverick Meerkat" has ended. Maverick's 2.6.35 kernel might also be too old to contain support for the GT240.

If this issue is still occurring on Ubuntu 12.04 "Precise Pangolin" please file a new bug.

There are already quite a few bugs open regarding GT 240, I do not think opening another one would be helpful.
(list at https://bugs.freedesktop.org/show_bug.cgi?id=33165)

Upstream seems unresponsive, I do not think this will be solved anytime soon.

Attaching updated patch disabling acceleration.

This is still a problem with 13.04.

Please just apply the patch. This problem is well documented and while upstream is unresponsive the patch is known to fix this. I hope Ubuntu developers know how frustrating this has been. It is a critical bug (the system won't even boot properly), there is a simple and known working fix available, yet nothing ever happens.

Just checked and confirmed that this is still a problem on 3.8.0-19-generic

Nukam, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Still shows corruption and locks up on latest saucy kernel.
nouveau.noaccel=1 still allows boot.

Cybjit, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documention in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

Closed, 13.04 is longer supported